Notices

Originally Posted by Astaoth

Ok, so here is the logs when I start rockpoold from the command line : pastebin.com/p4brZPED .
If we take a look at the end, we can read that the new version is detected, but the internal status about available update is set to false. And with the calls from qdbus, I have the same results than before.
Maybe because my version number has an unexpected format rockpool can't define if my version is the latest or not ?

Originally Posted by Fuzzillogic

It's elegant, but will it be enough?

Originally Posted by ruff

Daemons are controlled by systemd or by user. Even when it is dbus unit it's still called and spawned via systemd. So either you start it in cli manually or via systemd.
Conflict statement allows isolation of the services to avoid "strange unpredictable" behaviour.
Pebbled app allows start/stopping the service and see its status. rockpoold is autostarted by app, moreover app locks down when daemon is not running (falls to waiting for service page).
This basically grants certain predictability, not providing ultimate solution. Bcz ultimate solution should be a user's choice, nor programmer's.

To be completely on the safe side we might implement checks for the stray pebbled processes (eg service is down but process is running) but that's too much overhead and unless reported with certain persistence by users - should be avoided.

Originally Posted by abranson

What would you think about having the same service control in Rockpool as Pebbled? I'd already partially migrated the ServiceControl over. It would be easy to add methods to enable or disable the service.

Originally Posted by abranson

Thanks for that. I think Michael only anticipated that vX.Y.X format, probably because everyone was stopped on 3.9.1. I'll fix that tonight for you.

Edit: version 0.5-2 should be able to cope with you now.

Originally Posted by Astaoth

Thank you, it's working now.

I have a feature to suggest, if you have enough time. Do you think it will be possible to use the PT microphone during a phone call, and to have the call sound from the phone speaker ? It could be usefull when driving for example.

Originally Posted by ruff

Ok, so with latest commit interface is somewhat usable.
I didn't touch yet DeveloperPage part (includes screenshot page), firmware update and side-load (import page). The rest is more or less usable. (Finally I've set my fav. apps from jolla )

Originally Posted by ruff

I've noticed that rockpoold segfaults occasionally on reconnection (need to enable coredumps to debug)

Code:

[D] Pebble::onPebbleDisconnected:494 - Pebble disconnected: "Pebble Time C229" 
[D] WatchConnection::scheduleReconnect:38 - Attempting to reconnect in 10 seconds 
Segmentation fault

Originally Posted by ruff

Another observation is that app_icon is mostly generic. I.e. I'm receiving mail notifications however icon is still generic. probably because the source is still system event hub, will need to monitor dbus attributes and probably perform certain remapping.

Originally Posted by abranson

I'm not sure what you mean here, do you mean the icons on the notifications on watch? The current mapping of notifications to pebble icons is in SailfishPlatform:: onNotification. That chooses an icon based on notification owner, category, android package etc.