![]() |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I'm using a Nexus 5. I tried that, and now the watch says "connected" in the Pebble Bluetooth menu, but it still shows as "disconnected" in Rockpool (although the name of the watch is there now, and it shows an image of it).
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
You don't by any chance have the old pebbled installed and running, do you? That was the case last time someone found themselves in that situation.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Code:
ps axf|egrep 'pebble|rockpoold' a) whether there's pebbled service running b) how many instances of rockpoold are running P.S. probably need to add a check for dbus before acquiring service path to avoid multiple instances running |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I have new observations on the "Rockpool crash/freeze when call ends on Jolla C"
Today i left my pebble at home but had rookpool service running. I connected to my cheap Car Bluetooth, "Blaupunkt IF". Got a call, ended it and had the same symptoms as if pebble was connected. Jolla C froze for 2 minutes, i left it alone and it recovered without rebooting. I stopped the service from Rockpool app -> developertools and tried again, no problem without rockpool running. I will test with an Alpine unit in second car and Nokia Headset when i am @ home. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
yes, according to preliminary investigation the affected part is platform integration layer which is not bound to pebble connection. It is a glue between jolla's voicecall-ui/voicecall-manager which presumably causes the crash. I've just upgraded my os to 2.0.2.14 - will see if I experience same symptoms.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Code:
[nemo@Jolla ~]$ ps ax | egrep 'pebble|rockpoold' |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
when you watch is connected - in Bluetooth system settings is it also shown as connected? or you can try in CLI Code:
hcitool con |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Code:
hcitool con Code:
[nemo@Jolla ~]$ hcitool con Edit: I rebooted and now Code:
hcitool con |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Paired is not equal to connected. Paired means system knows the devce, knows how to connect to it (mac, profiles, auth key). Connected means the channel is actually established. Actual connection is triggered by rockpoold. If rockpoold does not see pebble it would not attempt to connect so paired but not connected after reboot is wrong but kind of expected based on your description.
To make a fresh start try following: * stop rockpoold service (eg. disable in client) * remove .local/share/rockpoold dir (eg. rm -rf .local/share/rockpoold) (this will remove all saved configuration of the rockpool. if any) * Do not remove paired pebble in the system. Leave it as is. Or if you're not sure it's paired properly - you may again re-pair it, removing from both system and pebble existing connection. * start rockpoold service again. At this point rockpool should a) see it has no pebbles at all b) detect paired pebble in the system and add it internally, initiating connection. |
All times are GMT. The time now is 04:17. |
vBulletin® Version 3.8.8