Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Found another issue with reminders where they were orphaned hence not allowing to execute any action except dismiss. With latest fix snooze and open work properly, snoozing the reminder and opening original calendar entry. Snooze works only in relation to pebble, not relaying information back to the phone yet - that part is not covered/documented in the libpebble so I'm currently reverse-engineering the protocol. Already found the way how to extract required info but still not clear what are options which are driving this particular reply format.
To get current calendar entries fixed would need to use Reset Timeline button to re-populate calendar to the timeline.
So new timeline9 beta now looks like a good candidate for another pull request.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I seem to be able to reliably crash the watch by phoning the Jolla, answering the call, then hitting the 'back' button on the Pebble while the call is ongoing.

Not sure if that's anything to do with Rockpool though (using 1.0-alpha1timeline9).

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yes, previously rockpool was crashing during such ops, now pebble is crashing instead. Rockpoold remains rock solid though :) I'm going to capture call progress on android to see what goes in and out, I think we miss some param or dialog which makes pebble crash. Previously it was getting nack due to daemon crash and hence survived.
Although it is intermittent, sometimes call goes through with no crash. Sometimes it crashes on call start, sometimes on call end.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

My pebble crashes on every call end :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

The only difference I found between android and rockpool is that rockpool spams with phone progress messages while android just switches states. So if pebble internally lacks state machine implementation - such flood may cause it to hang/crash/reset
Eg. this is android session
And this is rockpool
So need to implement internal state machine in endpoint. Which means it would not support concurrent calls. Otherwise with dynamic call list - that list will be trashed with garbage over time.
Or actually state track could be implemented in platform which has visibility on active calls, so can clean up the mess.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Also seems I've spotted again that issue when on phone reboot watch is spammed with old messages. Cannot reliable reproduce it but i suspect this happens when
a) rockpoold starts very early
b) at this phase comhistoryd repopulates its events from persistent storage, emitting them on dbus.

Attempted to fix it by filtering out old events. I.e. if timestamp of event is out if timeline window - just ignore it (this actually is proper behaviour which was missing).
And if event is inside window - there two outcomes:
* If event is delivered to pebble and hence exists in persistent storage - will be ignored as duplicate.
* If event was discarded/dismissed/removed - it will be re-delivered to pebble (cant stop this to happen really).

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Posted new beta with pebble crash on call fix, with stale messages fix (as above) and with new feature - Send Text message.

Send text applies as for ad-hock SMS sending using new builtin Send Text app for fav contacts, so to Call Manager app where you can reject the call with excuse SMS.

Setting these canned messages is currently not yet implemented, however you can connect pebble to android, set them and connect back to Jolla - jolla does not reset blobDBs with these configs so they are preserved from android.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Can confirm my Pebble doesn't crash after call now. Thanks! :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

How could i contribute when wanting to correct german translation?
Is there a transifex link?
Awesome work guys!
All works smooth on Jolla C. Anything i could test for you, do you like to see any logs?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

at the moment we don't have any community driven online service for translation management. I've posted request for free hosting to some - will see if anyone replies back.

For the testing - nothing specific atm, the only remaining concern so far is still power-profiling. As always - if you notice anything not working properly - there're basically 3 ways to collect logs - devel-su+journalctl, pebble sdk+devcon, stop service+run from cli.

thanks for feedback :)