Thread: [SailfishOS] [Announce] Rockpool - Pebble daemon for Sailfish
View Single Post
Fuzzillogic is offline Fuzzillogic
2016-03-17 , 22:01
Posts: 479 | Thanked: 1,284 times | Joined on Jan 2012 @ Enschede, The Netherlands
#34
I bit the bullet, moved from pebbled to rockpool. I'm using a Pebble Steel, which was still on firmware v2.9. Updating using rockpool seemed to go smoothly, but at some point the watch booted to recovery mode (v3.8-prf9), and rockpool couldn't make a connection anymore. (Didn't record the log, sorry)

It took me a few hours to realize the normal Android Pebble app won't work, you'd need the Pebble [b]Time[/]b app, to update to v3.10.1. Thanks Pebble . (Also, I don't have an Android device, which makes it even harder)

My PS now sports v3.10.1, but unfortunately Rockpool v0.4 won't connect, even though the Pebble is paired to Jolla. Log:

Code:
Mar 17 22:53:14 Jolla [9201]: [D] Pebble::connect:139 - Connecting to Pebble: "Pebble 0A47" "00:17:E9:AD:0A:47" 
Mar 17 22:53:14 Jolla [9201]: [D] WatchConnection::socketError:154 - SocketError QBluetoothSocket::UnknownSocketError 
Mar 17 22:53:14 Jolla [9201]: [D] WatchConnection::pebbleDisconnected:143 - Disconnected 
Mar 17 22:53:14 Jolla [9201]: [D] Pebble::onPebbleDisconnected:493 - Pebble disconnected: "Pebble 0A47"
Any clues?

[edit] Uggh, I have a clue: pebbled was mysteriously running again, and happy to (try) to connect. Also, Jolla forgot about the pairing.

Code:
[nemo@Jolla ~]$ /usr/lib/qt5/bin/qdbus org.rockwork /org/rockwork/00_17_E9_AD_0A_47 org.rockwork.Pebble.IsConnected
true
Last edited by Fuzzillogic; 2016-03-17 at 22:15.
 

The Following 4 Users Say Thank You to Fuzzillogic For This Useful Post: