Can't pair with a bluetooth keyboard in XE16

[GoogleCodeExporter]

(This is not a GDK bug, it is a general Glass software bug. I am reporting it 
here because there is no bug tracker for general Glass software bugs, and this 
is a blocking issue for development).

In XE16, it is not possible to pair with a bluetooth keyboard/touchpad. Prior 
to XE16, the procedure was to install Launcher2 and a legacy Android Settings 
app, use Launcher2 to open Settings, then use Settings to pair with a keyboard. 
Currently, Launcher2 crashes on start, and the Settings app is inoperable 
because of https://code.google.com/p/google-glass-api/issues/detail?id=494 .

Original issue reported on code.google.com by jimrandomh@gmail.com on 29 Apr 2014 at 2:01

[GoogleCodeExporter]

On Tue, May 6, 2014 at 7:24 PM, Jenny Murphy <mimming@google.com> wrote:
> Hey James,
>
> The best place to report this kind of issue is in our issue tracker. It
> looks like you've already filed this in #495. Let's continue this
> conversation on that thread.

Looking forward to continuing the conversation here. See also See also #442, 
#479, #483, #482, #494 and #502, all of which represent facets of essentially 
the same issue.

Original comment by jimrandomh@gmail.com on 7 May 2014 at 12:14

[GoogleCodeExporter]

*Crickets*

Kaze0 pointed out a workaround to the broken launcher and settings app 
(https://github.com/DDRBoxman/Bluetooth-Manager-for-Glass), but when I use that 
to pair, it ends up in a half-paired state: Glass recognizes the pairing code 
and thinks it's finished pairing, but the keyboard keeps blinking its 
pairing-mode LED and all keystrokes disappear into the bit-bucket. This is on 
XE16.2 (XE17 isn't available for download so I haven't tested it), with a Favi 
FE02BT-BL and a Perixx Periboard-805L, with enough retries and reboots to be 
certain that it's not just random flakiness.

Original comment by jimrandomh@gmail.com on 7 May 2014 at 8:42

[GoogleCodeExporter]

Got the XE 17 update, it half pairs like in XE 16, but I only tried a few times.

Original comment by Lu.Lesl...@gmail.com on 7 May 2014 at 11:01

[GoogleCodeExporter]

Got the XE17 update, it's still broken in the same ways as XE16. Still waiting 
for a response. See also 
http://www.reddit.com/r/googleglass/comments/24vwja/glass_used_to_be_compatible_
with_most_android/ .

Original comment by jimrandomh@gmail.com on 8 May 2014 at 5:26

[GoogleCodeExporter]

I've been looking into this as part of 
https://github.com/DDRBoxman/Bluetooth-Manager-for-Glass/issues/6

The pairing is indeed happening using this app (in both XE 16.11 and XE 17). 
The problem appears to be in the next step which is connecting the devices 
(BluetoothSocket) and handling their BluetoothProfile correctly. 

This is normally automatically handled by Android but hasn't been working in 
Glass for some period of time now (some say since XE 11, others since XE 16).

I have verified that this works fine on a Nexus 5 (4.4.2) and that Android 
automatically takes care of all of the device and profile management.

On Glass, the pairing process works just the same. You are requested to type in 
a code on the keyboard followed by Enter. This works on Glass and the pairing 
is completed. This seems to indicate that the BT connection functions because 
the input of the code is successful.

I've been looking into trying to find a workaround related to the 
BluetoothInputDevice class and Bluetooth HID profile but I don't have a 
solution yet.

For a headset, I am able to open a RFCOMM socket to the device and connect to 
it. Using a keyboard, I always get a connection read failed.

If there is any debugging info or output that would be helpful, please let me 
know. There are some logs in the referenced GitHub issue.

Original comment by Splak...@gmail.com on 10 May 2014 at 4:28

[GoogleCodeExporter]

Echo #c5 with my own reproduction in XE17. I'd stopped by to file this issue if 
it wasn't already present, actually!

I have also been experiencing issue 484 and this issue. Beyond the extant 
discussion on these, I've observed the following anomalies:

1. During the upgrade to XE17, all of my paired keyboards and mice appear to 
have come unpaired. I believe this is because a crash-loop under XE17 related 
to WordFinder caused a recovery installation to be initiated on my unit. I 
believe this is expected behavior.
2. When attempting to use a fresh build of 
[https://github.com/justindriggers/Glass-Launcher Glass Launcher] and 
Settings.apk to initiate pairing under XE17, I experienced issue 484. I believe 
this is because my prior version before these issues was XE15.
3. I was able to successfully load an earlier build of Bluetooth Manager for 
Glass (as above) on my device, by loading its MainActivity from an adb 
connected shell. From here, I was able to successfully initiate and complete 
pairing, and my devices displayed in this program's list of paired devices.
4. However, all previously observed behavior prior to XE17, such as all 
keyboard interactions in 
[https://code.google.com/p/connectbot/issues/detail?id=677#c3 my patched build 
of ConnectBot and mouse connectivity], appeared to no longer function. This is 
the same physical hardware that worked prior to XE17.

I am able to provide dumpsys, remote debugging, and observed pairing 
information from my own unit if it would be helpful. However, I suspect this is 
OS-level, and like issue 484, may be a matter of the upgrade to Kit Kat under 
the hood.

As a user orthogonal to the technical discussion here, this is blocking my 
ability to use ConnectBot, Kindle for Android on the device (which, I might 
add, works brilliantly provided a working mouse and keyboard), and Yelp, all of 
which are applications that are part of the gamut I desire to continue using 
with my unit. An acceptable working input model that interfaces with these 
applications is strongly desired here.

Original comment by itisd...@gmail.com on 12 May 2014 at 9:06

[GoogleCodeExporter]

Still no change in XE17.1. Still no communication from anyone at Google 
whatsoever.

Original comment by jimrandomh@gmail.com on 15 May 2014 at 3:17

[GoogleCodeExporter]

Still broken as of XE17.3. Still no communication whatsoever from anyone at 
Google.

Original comment by jimrandomh@gmail.com on 4 Jun 2014 at 7:48

[GoogleCodeExporter]

Glad to find this discussion. At least I know nothing's wrong with my Glass or 
Keyboard. Still broken as of XE18.11

Original comment by nightfl...@gmail.com on 14 Jun 2014 at 3:21

[GoogleCodeExporter]

This was the first question asked at the "Innovating with Glass" talk at Google 
I/O today. They said that it is "not a priority". They suggested, as a 
workaround, using "adb input" to inject key events. However, this is only works 
when you have a computer to tether to, and is very high latency, which makes it 
unsuitable for using Android applications for real.

Original comment by jimrandomh@gmail.com on 26 Jun 2014 at 11:57

[GoogleCodeExporter]

They also said "we are obviously interested in remote peripherals" and "we are 
working hard to bring it [HID functionality] back". 

It seems there's a desire to not encourage the use of traditional keyboard on 
Glass.
Which makes sense, as traditional keyboards are not suitable for the mobile 
experience that Glass offers.

That doesn't mean text input is not suitable for Glass. There are keyers (= 
keyboard - board) that can offer quite a great way to input text into Glass. 
For example this one: http://twiddler.tekgear.com/

Text input with keys is sometimes quite useful on Glass, like spelling Contacts 
and addresses. This is not easily done with the voice...

Original comment by m...@alexbravo.com on 27 Jun 2014 at 7:14

[GoogleCodeExporter]

Still not working with 19.1 . :( This is highly discouraging, I would like to 
add more  control for games and controlling robots without voice commands. I 
have created a few working apps that are now useless without HID or bluetooth 
functionality.. I fear I may have to root and run older releases if these 
issues are not fixed soon. 

Original comment by diabolic...@gmail.com on 18 Jul 2014 at 10:24

[GoogleCodeExporter]

Does anyone have steps to get this working on an older version?

Original comment by stanchio...@gmail.com on 25 Jul 2014 at 12:09

[GoogleCodeExporter]

I know this is not a solution, but a workaround for BT keyboard is to use an 
external BT dingle plugged into a USB port. Both mouse and keyboard work. Usb 
keyboard can work too, but might to be plugged in through a USB hub. 

Original comment by m...@alexbravo.com on 25 Jul 2014 at 2:40

[GoogleCodeExporter]

It's August already. Any update?

Original comment by lanfear4...@gmail.com on 14 Aug 2014 at 11:13

[GoogleCodeExporter]

Another month has gone by with no fix

Original comment by lanfear4...@gmail.com on 3 Sep 2014 at 8:21

[GoogleCodeExporter]

Original comment by ala...@google.com on 3 Sep 2014 at 10:02

• Changed state: Accepted
• Added labels: Component-GDK, log-17314698

[GoogleCodeExporter]

Not counting chickens, but... hallelujah!

Original comment by noaz...@gmail.com on 4 Sep 2014 at 11:21

[GoogleCodeExporter]

I purchased my Glass specifically in order to use it with my one-handed 
chording bluetooth keyboard. The Glass team promptly took that ability away. 
:-( Yes, I understand that an ordinary keyboard is completely inappropriate for 
Glass. However there are a number of HID Bluetooth dongles out now which are 
very easy to use. For example, you could have a myo-electric interface that 
sends a keystroke whenever you flex a particular muscle. There's all SORTS of 
devices we could invent, except that the Glass team doesn't understand the 
importance of having bluetooth keyboard support.

Original comment by russnel...@gmail.com on 29 Sep 2014 at 5:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Come on please put this feature back. 

Original comment by lyl...@gmail.com on 7 Nov 2014 at 6:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This remains to be an issue. XE22 1/3/2015

Original comment by lanfear4...@gmail.com on 3 Jan 2015 at 10:29