Touch keyboard doesn't show up after disconnecting a bluetooth keyboard

ubports / ubuntu-touch

Ubuntu Touch's issue inbox is now migrated to GitLab.

https://gitlab.com/ubports/ubuntu-touch

1.29k stars 110 forks source link

Touch keyboard doesn't show up after disconnecting a bluetooth keyboard #351

Open samueldevqc opened 6 years ago

samueldevqc commented 6 years ago

Device: BQ Aquaris M10 HD
Channel: stable
Build: version 2

Steps to reproduce

Connect a bluetooth keyboard
Disconnect the keyboard
Try to type text

Expected behavoir

After disconnecting the physical keyboard, I should be able to type text with the touch keyboard.

Actual behavior

After disconnecting the physical keyboard, the touch keyboard doesn't show up, so I have to reboot the device to type text without the bluetooth keyboard.

Logfiles and additional information

...

tomoqv commented 6 years ago

I have noticed this too when using a BLE keyboard. BT keyboards that are not low energy hasn't been a problem.

samueldevqc commented 6 years ago

For my part it does it with a little BT keyboard for tablet. The touch keyboard is not reactivated after disconnecting it. I know it didn't do that with previous versions of Ubuntu Touch. I'm not sure for version 1 of UBports, but i'm pretty sure it didn't do that with Cannonical OTA-15.

Valkhir commented 6 years ago

I have the same issue.

Devices: OnePlus One and Nexus 5 Software: UBports OTA 1 and 2

As @tomoqv reports, it may be limited to Bluetooth LE keyboards - I cannot reproduce the issue on my Apple BT Keyboard (2010), but it happens on my Microsoft Universal Foldable Keyboard (2014(?)). In practice, I never want to use the non LE keyboard, as it is not very portable, so using a non-LE keyboard is not a useful workaround, at least for me
other than rebooting, going into bluetooth settings and choosing "forget this device" for the keyboard will also restore the on-screen keyboard. This is a useful workaround, as it is faster than rebooting and will not otherwise affect device state. However, it is incovenient and can be difficult in an environment saturated with signal.

Valkhir commented 6 years ago

@NeoTheThird I can help with logs, if you let me know what is needed. I also currently have two devices, so I am more than happy to install dev/test builds on one of them if you need help testing fixes.

arubislander commented 6 years ago

I have an Aquaris BQ M10 FHD and I have had this issue happen to me on every instance of Ubuntu Touch, from at least Canonical's OTA 15 up to UBPorts OTA 3. I recently purchased a Meizu PRO 5 to be on the bandwagon for Anbox, and the issue also occurs on this device. My bluetooth keyboard is a Microsoft Designer Bluetooth.

ezickler commented 6 years ago

I can confirm this bug. With OTA3 and xenial r304 on nexus 5.