Re: [Announce] Pebble Watch Connector daemon 0.12
 

Thank you!

So far config page is working fine.
However I can't manage to make new version work with GPS - neither TCW nor Weather apps can't detect my location (and no GPS icon is shown on phone during weather update so it looks like positioning is not working).
Second problem is that now there is no notifications for incoming calls/SMS messages (e-mail works fine)

I'm running latest version of Saifish - 1.1.1.27. Will check logs today later...

Re: [Announce] Pebble Watch Connector daemon 0.12
 

Suspect daemon is crashing. There's a reason I call them "testing" releases :)

Re: [Announce] Pebble Watch Connector daemon 0.12
 

As a QA in real life I can test it and write back logs/bugs if needed :) There is no problem for me to use testing releases :)

Re: [Announce] Pebble Watch Connector daemon 0.12
 

Seems that I messed up something with settings. Will check at some point.
No idea about lack of GPS access, check pebbled logs for that.

Another thing that's bothering me. The DataLog messages from the watch. They seem to be sent every minute or so, which has a noticeable impact on battery life. This also happens on the original daemon, but it can't decode them because of fragmentation. Still pondering how to get rid of them...

Re: [Announce] Pebble Watch Connector daemon 0.12
 

Just released 0.13 https://openrepos.net/content/smoku/pebble with fixes for Sailfish OS 1.1.

Re: [Announce] Pebble Watch Connector daemon 0.12
 

Ok it seems that the definition of "default" settings between the daemon and the UI app are different. I had just erased my Jolla to upgrade to the latest release, so I had an empty dconf database. In this situation, the UI will say that e.g. "Messaging notifications" are enabled, but the daemon will interpret an empty dconf database as "messaging notifications disabled" instead.

A simple workaround is to toggle all the notification enabled checkboxes in the UI twice. That way you're actually writing the defauls to the dconf DB. Can you test that?

I am not sure how this worked in the daemon before, because it now seems obvious that checking for "isValid()" on the result of settings->property(...) is redundant, since the property is _always_ valid, and is initialized to whatever is on the settings member variable at that time. Which means that we were taking random setting values?

Re: [Announce] Pebble Watch Connector daemon 0.13
 

Seems like it is a Qt 5.2 or SOS 1.1 change, as we had this issue before, and added isValid checks to detect unset values.

Re: [Announce] Pebble Watch Connector daemon 0.13
 

Can i push watchfaces to my pebble from jolla or do i need an android phone to do it?

Pebble v2.8.1
SailfishOS Vaarainjärvi
Pebble app version 0.13-1

Re: [Announce] Pebble Watch Connector daemon 0.13
 

No, you just need to download the .pbw file and upload it to the Jolla phone.
Then configure using Pebbled, by clicking on the name of the Pebble (like Pebble XXXX).

Re: [Announce] Pebble Watch Connector daemon 0.13
 

I wonder if it is possible to have companion apps on the Jolla. I would like to have an integration of TaskList on my pebble. But I don't know what exactly is necessary to achieve that.

Or what API such an APP (eg TaskList) has to provide to make it possible.