BluetoothLE isn't reliable enough on SFOS devices to support new Pebbles

[almindor]

This is with SFOS 5.0.0.62 on Xperia X III. The BT connection in settings is established, and visible as connected on the watch itself too, however the app does not seem to recognize it. It always just shows disconnected, restarting the service does not help.

I tried enabling logging but the file in /tmp does not seem to be populated with any logs.

[almindor]

NOTE: one thing I noticed is that while in pebble watch/settings/bluetooth I can see "connected", in the watchface the bluetooth icon is off, whereas with the iphone it's there, so I wonder if this is a deeper SFOS/BT issue.

[almindor]

I managed to build and run a debug run of the project from source now, via the SailfishSDK. Is there an easy way to get logging from rockpoold to show? From what I can see the gui app is logging but the daemon is not.

I tried using journalctl --user -f -u rockpoold.service but that seems to come up empty. How do you view the daemon logs?

[almindor]

Found it using systemctl --user status rockpoold.service

It seems there's a socket connection issue:

nov 11 04:49:20 Xperia10III systemd[2852]: Started Rockpool daemon for Pebble smartwatches.
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] watchfish::NotificationMonitorPrivate::NotificationMonitorPrivate:70 - Starting notification monitor
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] VoiceCallManager::onVoiceCallsChanged:238 - VoiceCallsChanged
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] VoiceCallManager::onActiveVoiceCallChanged:305 - ActiveVoiceCallChanged
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] watchfish::MusicController::connectPulseBus:166 - PulseAudio Bus address:  "unix:path=/run/user/100000/pulse/dbus-socket"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] watchfish::MusicController::connectPulseBus:176 - Max volume:  12
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] OrganizerAdapter::refresh:91 - Refreshing organizer from "ne nov 9 04:49:20 2025" to "ut nov 18 04:49:20 2025"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] OrganizerAdapter::refresh:183 - Alarm enabled for  "redacted"  at  "redacted"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] OrganizerAdapter::refresh:141 - Preparing all-day event, the reported duration is (sec) 0
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] OrganizerAdapter::refresh:183 - Alarm enabled for  "redacted"  at  "redacted"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] BluezClient::addDevice:102 - Found new Pebble: "E1:64:2E:EF:AF:77" "Pebble AF77"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] BluezClient::addDevice:108 - emitting added
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] PebbleManager::loadPebbles:31 - loading pebble "E1:64:2E:EF:AF:77"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] PebbleManager::loadPebbles:34 - creating new pebble
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] TimelineManager::reloadLayouts:408 - Loading layouts file from "/home/defaultuser/.local/share/rockpoold/E1_64_2E_EF_AF_77/timeline/../layouts.json.auto" "Unknown error"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] TimelineManager::reloadLayouts:412 - Parsed with results "no error occurred"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] TimelineManager::reloadLayouts:432 - Added 35 attributes
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] TimelineManager::reloadLayouts:437 - Added 102 resources
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] TimelineManager::reloadLayouts:442 - Added 7 layout types
nov 11 04:49:20 Xperia10III rockpoold[53004]: [W] TimelinePin::TimelinePin:102 - Cannot thaw pin "3fc1c094-5789-4664-9614-e7a3175b6023" "garbage at the end of the document"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] TimelineManager::TimelineManager:381 - Ignoring broken pin "3fc1c094-5789-4664-9614-e7a3175b6023"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] MusicEndpoint::setMusicMetadata:20 - setMusicMetadata
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] AppManager::AppManager:28 - install apps in "/home/defaultuser/.local/share/rockpoold/E1_64_2E_EF_AF_77/apps"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] Pebble::getWeatherLocations:659 - Deserialized 0 locations
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] WeatherApp::setLocations:369 - Entering locations () false
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] VoiceEndpoint::VoiceEndpoint:16 - Attaching endpoint to bus 11000 10000
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] DevConnection::installLogging:30 - Acquiring logging channel, use DevConnection to manage verbosity
nov 11 04:49:20 Xperia10III rockpoold[53004]: [W] Pebble::Pebble:182 - Dumping logs to "/tmp/rockpoold.u53004.log"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] PebbleManager::loadPebbles:39 - have pebbles: 1 PebbleManager(0x70fc005b40)
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] Pebble::connect:225 - Connecting to Pebble: "Pebble AF77" "E1:64:2E:EF:AF:77"
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] DBusInterface::DBusInterface:570 - pebble manager has: 1 PebbleManager(0x70fc005b40)
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] DBusInterface::pebbleAdded:596 - pebble added
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] DBusInterface::pebbleAdded:602 - registering dbus iface
nov 11 04:49:20 Xperia10III rockpoold[53004]: [D] DBusInterface::DBusInterface:575 - connecting dbus iface
nov 11 04:49:20 Xperia10III rockpoold[53004]: [W] WatchConnection::writeToPebble:100 - Socket not open. Cannot send data to Pebble. (Endpoint: 8000 )
nov 11 04:49:25 Xperia10III rockpoold[53004]: [D] WatchConnection::socketError:163 - SocketError QBluetoothSocket::UnknownSocketError
nov 11 04:49:25 Xperia10III rockpoold[53004]: [D] WatchConnection::pebbleDisconnected:153 - Disconnected
nov 11 04:49:25 Xperia10III rockpoold[53004]: [D] Pebble::onPebbleDisconnected:1328 - Pebble disconnected: "Pebble AF77"
nov 11 04:49:25 Xperia10III rockpoold[53004]: [D] WatchConnection::scheduleReconnect:38 - Attempting to reconnect in 10 seconds

[abranson]

What version of qtbluetooth do you have installed? The version from my OBS repo?

[almindor]

What version of qtbluetooth do you have installed? The version from my OBS repo?

The one from your OBS repo yes.

This is however with the new Core 2 Duo watch from the "re-pebble reboot". Is it possible it requires BLE to function correctly?

I've started looking into the patch mentioned by #114 but as you said the kernel side is probably not there for sailfish so we might be stuck?

[abranson]

I haven't got one of those, but I think it's the same as the Pebble 2 which has never been supported by Rockpool as it's BLE only. I've roughly applied that patch myself to try it out on my X10ii, but it's not really working yet.

[almindor]

I haven't got one of those, but I think it's the same as the Pebble 2 which has never been supported by Rockpool as it's BLE only. I've roughly applied that patch myself to try it out on my X10ii, but it's not really working yet.

Do you have the applied version floating somewhere? I tried applying manually as well but got stuck on the invoke problem with QMetaObject::invokeMethod not existing in such overloaded form in Qt5.6 and not understanding the templating logic fully (it's been years since I did C++/Sailfish/Qt stuff).
I'd like to try and hack around to see what's happening.

[abranson]

Pushed to a branch called 'WIP'. I think he has more fixes for BLE, and then some for the Core 2 Duo, but they might be easier cherry-picks.

[almindor]

Pushed to a branch called 'WIP'. I think he has more fixes for BLE, and then some for the Core 2 Duo, but they might be easier cherry-picks.

Thank you! I'll play around and see where I can get.

[almindor]

Ok I managed to get it all running and there's an interesting logline:

nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] Pebble::connect:225 - Connecting to Pebble: "Pebble AF77" "E1:64:2E:EF:AF:77"
nov 11 18:44:19 Xperia10III rockpoold[3611]: [W] WatchConnection::reconnect:87 - Attempting to reconnect, 1 false
nov 11 18:44:19 Xperia10III rockpoold[3611]: [W] WatchConnection::pebbleDiscovered:257 - Pebble discovered! ("{00001800-0000-1000-8000-00805f9b34fb}", "{00001801-0000-1000-8000-00805f9b34fb}", "{0000180a-0000-1000-8000-00805f9b34fb}", "{0000180f-0000-1000-8000-00805f9b34fb}", "{0000fed9-0000-1000-8000-00805f9b34fb}") 0
nov 11 18:44:19 Xperia10III rockpoold[3611]: [W] GATTServer::run:38 - GATT server started!
nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] unknown:0 - Starting to advertise
nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] unknown:0 - advertising parameters: "000800080000000000000000000700"
nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] unknown:0 - advertising data: "0302010400000000000000000000000000000000000000000000000000000000"
nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] unknown:0 - sending command; ogf: 8 ocf: 10
nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] unknown:0 - hci command failure: Operácia nie je povolená
nov 11 18:44:19 Xperia10III rockpoold[3611]: [W] unknown:0 - received advertising error

specifically nov 11 18:44:19 Xperia10III rockpoold[3611]: [D] unknown:0 - hci command failure: Operácia nie je povolená not sure if this is the ultimate cause of the problem, but it means "operation not permitted" in Slovak (my phone's language).

[almindor]

To see if I can get further, I copied the .local/share/rockpoold to root home and ran rockpoold as root, and sure enough the permission issue is gone, sadly it still didn't work, as there's now a new received advertising error

[D] PebbleManager::loadPebbles:31 - loading pebble "E1:64:2E:EF:AF:77"
[D] PebbleManager::loadPebbles:34 - creating new pebble
[D] TimelineManager::reloadLayouts:413 - Loading layouts file from "/root/.local/share/rockpoold/E1_64_2E_EF_AF_77/timeline/../layouts.json.auto" "Unknown error"
[D] TimelineManager::reloadLayouts:417 - Parsed with results "no error occurred"
[D] TimelineManager::reloadLayouts:437 - Added 35 attributes
[D] TimelineManager::reloadLayouts:442 - Added 102 resources
[D] TimelineManager::reloadLayouts:447 - Added 7 layout types
[W] TimelinePin::TimelinePin:102 - Cannot thaw pin "3fc1c094-5789-4664-9614-e7a3175b6023" "garbage at the end of the document"
[D] TimelineManager::TimelineManager:386 - Ignoring broken pin "3fc1c094-5789-4664-9614-e7a3175b6023"
[D] MusicEndpoint::setMusicMetadata:20 - setMusicMetadata
[D] AppManager::AppManager:28 - install apps in "/root/.local/share/rockpoold/E1_64_2E_EF_AF_77/apps"
[D] Pebble::getWeatherLocations:659 - Deserialized 0 locations
[D] WeatherApp::setLocations:369 - Entering locations () false
[D] VoiceEndpoint::VoiceEndpoint:16 - Attaching endpoint to bus 11000 10000
[D] DevConnection::installLogging:30 - Acquiring logging channel, use DevConnection to manage verbosity
[W] Pebble::Pebble:182 - Dumping logs to "/tmp/rockpoold.h18918.log"
[D] PebbleManager::loadPebbles:39 - have pebbles: 1 PebbleManager(0x5955183dd0)
[D] Pebble::connect:225 - Connecting to Pebble: "Pebble AF77" "E1:64:2E:EF:AF:77"
[W] WatchConnection::reconnect:87 - Attempting to reconnect, 1 false
[W] WatchConnection::pebbleDiscovered:257 - Pebble discovered! ("{00001800-0000-1000-8000-00805f9b34fb}", "{00001801-0000-1000-8000-00805f9b34fb}", "{0000180a-0000-1000-8000-00805f9b34fb}", "{0000180f-0000-1000-8000-00805f9b34fb}", "{0000fed9-0000-1000-8000-00805f9b34fb}") 0
[W] GATTServer::run:38 - GATT server started!
[D] unknown:0 - Starting to advertise
[D] unknown:0 - advertising parameters: "000800080000000000000000000700"
[D] unknown:0 - advertising data: "0302010400000000000000000000000000000000000000000000000000000000"
[D] unknown:0 - sending command; ogf: 8 ocf: 10
[D] unknown:0 - command sent successfully
[D] unknown:0 - void QBluetoothDeviceDiscoveryAgentPrivate::stop()
[D] DBusInterface::DBusInterface:578 - pebble manager has: 1 PebbleManager(0x5955183dd0)
[D] DBusInterface::pebbleAdded:604 - pebble added
[D] DBusInterface::pebbleAdded:610 - registering dbus iface
[D] DBusInterface::DBusInterface:583 - connecting dbus iface
[D] unknown:0 - HCI event triggered, type: e
[D] unknown:0 - command 10 failed with status 12
[D] unknown:0 - initial advertising disable failed, ignoring
[D] unknown:0 - sending command; ogf: 8 ocf: 6
[D] unknown:0 - command sent successfully
[D] unknown:0 - HCI event triggered, type: e
[D] unknown:0 - HCI event triggered, type: e
[D] unknown:0 - command 6 failed with status 12
[W] unknown:0 - received advertising error

[abranson]

I checked back, and the Rockwork author said he needed the backported kernel code to get 'dual-mode BLE'. Perhaps that's what's needed to avoid these errors. Though shouldn't you be paired with 'Pebble LE AF77' instead of you're using BLE? Or not paired at all?

[slalomsk8er]

I also only see one connection not a classical and a dedicated LE one.

Details form the Sailfish GUI:

Pebble CE92 (Pebble 2 Duo from https://store.repebble.com/)
Supported profiles: GAP,GATT
Low energy services: DIS,BAS

Device details:

Similar to Pebble 2, it features

• Ultra crisp 1.26” black and white e-paper display
• Runs 10,000+ Pebble apps and watchfaces
• Lightweight polycarbonate frame in two colour options - White or Black
• Water resistant (targeting IPX8)
• Microphone
• Step and sleep tracking
• Standard interchangeable 22mm watchstrap with quick release pins

Improvements from Pebble 2

• 30 day battery life (up from 7)
• Nordic nRF52840 BLE chip
• Speaker
• Linear resonance actuator (quieter and stronger than vibrating motor)
• More reliable buttons (up to 30% longer lifetime in testing)
• Barometer and compass sensors

From: https://ericmigi.com/blog/introducing-two-new-pebbleos-watches

[almindor]

I checked back, and the Rockwork author said he needed the backported kernel code to get 'dual-mode BLE'. Perhaps that's what's needed to avoid these errors. Though shouldn't you be paired with 'Pebble LE AF77' instead of you're using BLE? Or not paired at all?

The pebble device only shows, paris and connects as Pebble LE AF77 but that seems ok to me? The connection does show on the watch as well and the watch displays the phone name so basics are definitely working, and LE would suggest this is low energy.

I'm not that familiar with BT to know about what dual mode BLE is.

[almindor]

Also Nordic Semiconductor's nRF52840 is designed specifically for Bluetooth Low Energy (BLE) so I don't think it supports dual mode at all. source

I don't think dual mode is our problem with this particular model.

Interestingly I'm also able to pair and connect from my desktop, and it shows the same name etc. but the connection times out in ~10s. The watch sees this, does show connected (with <untitled> in this case), but as with the phone, even while the connection is open, the watchface BT indicator is not on.

Interestingly the phone does not time out, I wonder what the difference is there, but I doubt it's important to us here.