Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[xenial] Bluetooth daemon issue #766

Open
tomoqv opened this issue Jul 13, 2018 · 13 comments

Comments

@tomoqv
Copy link

commented Jul 13, 2018

  • Device: Turbo
  • Channel: xenial
  • Build: RC4

Steps to reproduce

Connect a Pebble watch with Bluetooth on the phone. Open the app Rockwork.

Expected behavior

Rockwork recognize the connection to the watch.

Actual behavior

Rockwork doesn't recognize the connection to the watch, instead thinks it is not connected despite a bluetooth connection being established.

Logfiles and additional information

UTlogcat.txt
UTdmesg.txt
pebble_time_round
screenshot20180713_180016895
screenshot20180713_175924335
screenshot20180713_175906570
https://paste.ubuntu.com/p/QXCyBfFV53/

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Jul 13, 2018

Please file a bug with rockwork for that. It might be that they just did not compile for xenial yet.

@tomoqv

This comment has been minimized.

Copy link
Author

commented Jul 13, 2018

I filed this bug after conferring with @bhdouglass. He believes it to be an issue with bluetooth rather than Rockwork. I know this probably needs to be complemented, but I am not sure how to label it and what info is needed.

@NeoTheThird NeoTheThird reopened this Jul 13, 2018

@NeoTheThird NeoTheThird added this to the 16.04 Backlog milestone Jul 13, 2018

@Flohack74

This comment has been minimized.

Copy link
Member

commented Jul 18, 2018

The problem is rather that none of the devs I know has got such a watch for testing...

@tomoqv

This comment has been minimized.

Copy link
Author

commented Jul 18, 2018

I understand. Is there anyway I can help you track this issue down? It seems to me that either bluetooth doesn't report the connection status correctly or that Rockwork doesn't read the connection status.

@j2g2rp

This comment has been minimized.

Copy link

commented Jul 23, 2018

I had the same problem about a week ago. Because of some problems i decided to make a wipe of the phone in xenial. After that I couldn't pair the watch. When I validated the pin the watch was waiting to confirmation. To pair the phone I had to back to Vivid and back again to xenial.

@Dave1152000

This comment has been minimized.

Copy link

commented Aug 1, 2018

Same issue with OPO and Pebble 2

@mariogrip mariogrip modified the milestones: 16.04 Backlog, 16.04 OTA-5 Aug 3, 2018

@tomoqv

This comment has been minimized.

Copy link
Author

commented Sep 13, 2018

I don't really know what I did, if anything new, but my Pebble watch is now recognized by Rockwork when connected in the bluetooth system settings. I went through the same hooplas as above having the same problem, but after letting it sit for a while it suddenly kicked in. No idea what was different this time around.

It seems the bluetooth daemon is still problematic and doesn't always report the connection status to apps, but I am glad it works again.

@mariogrip mariogrip modified the milestones: 16.04 OTA-5, 16.04 OTA-6 Sep 24, 2018

@mariogrip

This comment has been minimized.

Copy link
Member

commented Sep 24, 2018

I have to move this for now, I need to get a hold of a pebble to be able to debug, i'll try get my hands on one by OTA-6

@tomoqv

This comment has been minimized.

Copy link
Author

commented Sep 24, 2018

@mariogrip That's OK. As stated above the connection finally worked for me, but I sincerely think there is something strange going on with the daemon not always exposing the connection to apps that depend on bluetooth.

@tomoqv

This comment has been minimized.

Copy link
Author

commented Oct 2, 2018

After upgrading to the latest RC (W39) last week, the connection between my watch and phone broke again. I haven't yet been able to reconnect. When I go to bluetooth settings, it briefly connects before disconnecting again.

@nighthawk321

This comment has been minimized.

Copy link

commented Oct 28, 2018

Hi,
I have been been getting the same issue with my pebble time, device is a Nexus 5.
I have also tried my pebble OG, I am able to connect and stay connected but I am unable to dismiss notifications and stop/play music from the watch.

@tomoqv

This comment has been minimized.

Copy link
Author

commented Dec 7, 2018

I have managed to successfully pair my watch recently both to Pro 5 and OPO. The trick seems to be to open the Rockwork app before attempting to connect the watch through bluetooth. Also, I have connected to Pebble Time F77D and not the other instance Pebble Time LE F77D that is visible in available devices.

This is still very weird behaviour. Apps should honor established BT connections and those BT connections should remain even if not yet set up by the app. But then again, maybe the watch lets go of the connection if it can't talk to Rockwork...

@mariogrip mariogrip modified the milestones: 16.04 OTA-7, 16.04 OTA-8 Dec 29, 2018

@mariogrip

This comment has been minimized.

Copy link
Member

commented May 11, 2019

I have pushed the latest version (5.50) of bluez to xenial_-_new-bluez please try this to see if it fixes the issue :)

sudo ubports-qa install xenial_-_new-bluez

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.