Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I guess ssh in, devel-su, then run

journalctl -fl

then cause the crash.

Congratulations, and thanks for the 1.0 (even if disputed ;) ) release - great work all round!

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

The update to the latest version just made rockpool useless for some reason. All notifications are just empty.
https://github.com/abranson/rockpool/issues/44

//Edit: Fixed

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

What happened? How did you fix it?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

After the upgrade, I only got empty notifications and changes for the Timeline interface did not get set.

After a second manual restart of the rockpool daemon it worked. But I had to redo all settings.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Another issue on Nexus 5 (not sure whether this is something you can fix): the Pebble connection stops working after the phone goes to sleep and wake up again. The Pebble thinks it is connected, and Rockpool shows it as connected, but it no longer receives notifications, is no longer able to control media, and things like watch faces can no longer be uploaded.

If this happens while something is uploading to the watch, the upload hangs for half a minute and then it says "Failed" (on the watch).

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

If I remember correctly, Nexus 5 had severe BT problems when I tested it. That was CM11 though. Are you on the newest port?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I installed using CM11, and SFOS 1.1.9 - is there a newer one?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yeah, though it has other tradeoffs.

http://talk.maemo.org/showthread.php?t=96932

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I think I spotted it this morning - although on a different occasion.

Tonight I left my phone at 15% bat - so it was whining all the night with low battery beeps. This morning I put it on a charger with 5% but noticed that pebble is disconnected. On the way to the office I've turned on my BT headset and realized it cannot connect to the phone. I've checked BT - it was on, however showing only devices which were on nearby - pebble, headset and my BT speaker. In fact I have smth like 10 devices paired - they just disappeared from BT settings screen (I've seen such behaviour before though).

Any attempt to connect the phone from headset failed. When I initiated connection from the phone - it connected.

Attempting to reset BT (off/on) does nothing - pebble is still disconnected, headset still cannot initiate connection.

Looking into syslog I see kernel reporting l2cap_sock_connect: failed -115 and followed by standard rockpool's QBluetoothSocket::UnknownSocketError.

So it seems there's still a problem in the BT stack implementation on jolla, where when BT adapter goes into deep sleep - it cannot be recovered back into proper state.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Not sure if that is the same case. I turn BT explicitely off from the phone in the evening, and on again in the morning. The devices get connected quickly (Pebble vibrates and BT marker disappears), only Rockpoold does not notice the connection. So, the connection is fine just by restarting the Rockpoold, no further actions to BT needed. And the phone connects e.g. to my car's hands-free every time.