Re: [Announce] Pebble Watch Connector daemon
 

Well said. There's a bit too much crowdfunding round here these days.

Re: [Announce] Pebble Watch Connector daemon
 

Being hired as a software developer full time pays much, much, much better than any croudfunding campaign. :D

Impossible.
Any useful API is banned from Harbour.
Background daemons - banned.
Installation scripts - banned.
Multiple binaries apps - banned.
[...]

Basically, you cannot put anything more useful than a FartApp to Harbour Store. (Unless you're called Jolla.com)

Re: [Announce] Pebble Watch Connector daemon
 

... there have been some additional 'privileges' for TOH drivers, too. So maybe exceptions are made for high visibility packages. For the rest of us, "is there really an store?".

BTW, in case you ever wondered why some caller IDs fail to match to a contact.

Re: [Announce] Pebble Watch Connector daemon
 

Good find!
I've updated https://github.com/smokku/pebble/issues/36

Re: [Announce] Pebble Watch Connector daemon
 

Anyone having trouble with uploading certain apps, please test this pre-release https://github.com/smokku/pebble/releases/tag/7cdadf0 and check whether it fixes your app installation issue.

Re: [Announce] Pebble Watch Connector daemon
 

Love Weather now installs (didn't before), but since several releases I can't open any configuration page - the app sits not responding for up to a minute, then opens empty configuration page (with only cancel on top).

Re: [Announce] Pebble Watch Connector daemon
 

Same here configuration pages don't work even when they worked before the upgrade.

Re: [Announce] Pebble Watch Connector daemon
 

Yes, he is right - I was able to open some configuration pages before. With the new update however none work.

Re: [Announce] Pebble Watch Connector daemon
 

Re: [Announce] Pebble Watch Connector daemon
 

Can we get an RPM? :)

Re: [Announce] Pebble Watch Connector daemon
 

Just released 1.0 (feature complete) to OpenRepos.

Main new features:

• Firmware Upgrade support
• Music volume controls alter the system volume (thanks to Andrew Branson)

Re: [Announce] Pebble Watch Connector daemon
 

Hi,
I'm new here, and want to say thanks a lot for your great work on this! I bought a used Pebble Steel last week, and was happy to see how nicely it plays with my Jolla through the pebble daemon and app - especially after the last update, which solved the app uploading problem. Thank you!

I now want to try writing a Pebble+Sailfish companion app. For this I've started playing around with the org.pebbled interface through dbus-python, but I must admit that I'm very much of a DBus novice. I manage to ping my pebble and to upload, unload and remove apps, as well as to read the various properties. But I can not figure out how to call SendAppMessage. Does it need any more argument in addition to uuid and message? I get 'TypeError: More items found in D-Bus signature than in Python arguments'. (And 'a{sv]' means that the message argument should be a dictionary with strings as keys, right?) Please excuse me for what might be stupid questions!

Also, is there any way to send a notification text to the Pebble from a script on the phone (through org.pebbled or otherwise)?

Re: [Announce] Pebble Watch Connector daemon
 

You should note that Firmware upgrade support is a paid option ;).

Re: [Announce] Pebble Watch Connector daemon
 

Only the UI screen. ;-)

All the mechanic is present and you are free to upgrade the firmware using any other tool (i.e. qdbus command line).

Re: [Announce] Pebble Watch Connector daemon
 

Good work!

By the way - what with installation of custom fw? f.ex. one from pebblebits?

Re: [Announce] Pebble Watch Connector daemon
 

No idea. I didn't try it.

Re: [Announce] Pebble Watch Connector daemon
 

Well, custom sw is a .pbz file - so when I'm d'loading it on the phone and clicked on it - app is opened but no action is taken.
So far custom fw is a good option (at least to read messages in still not supported languages) - so it will be a good option to add such a feature.

Re: [Announce] Pebble Watch Connector daemon
 

You may try uploading it manually using DBus interface.
But I do not support it, so do it on your own risk.

Re: [Announce] Pebble Watch Connector daemon
 

It's basically the same file as the original though.
Just not picked from the Pebble servers.

Re: [Announce] Pebble Watch Connector daemon
 

Writing platform specific companion apps is not that good idea. They are not portable and restrict your companion app to one platform only.

Pebble SDKv2 introduced JavaScript based companion apps you should use. We support them very well. Also pebbled will make sure your JS companion app gets started whenever user opens the app on the watch and it does not have to be run manually or always in background. Just read Pebble SDKv2 documentation and follow.

Re: [Announce] Pebble Watch Connector daemon
 

So it should be possible to upload it.

Though I advise against it, do not support it and can't be hold responsible if your watch becomes a paper holder etc. etc.

Re: [Announce] Pebble Watch Connector daemon
 

off: well, at least while Pebble do not support all encodings for text messages - custom FW is the only one option f.ex. for Russian

Re: [Announce] Pebble Watch Connector daemon
 

I recall mention of some GPS issues in the earlier posts of this thread. Was there any solution to it?

I have some apps which work fine pulling information from GPS while others can't find any location.

working:
Minimalist Weather
Weather 2.0

not working:
World Metric 2
GetMeOut

Any idea why? All of them are supposed to work without any companion app.

Re: [Announce] Pebble Watch Connector daemon
 

Maybe this is the problem - the only GPS support we have is available for companion js-app.

Re: [Announce] Pebble Watch Connector daemon 0.15
 

Aaand I've just started doing that:
https://git.javispedro.com/cgit/libwatchfish.git/
Still in development though, and does not support actions, etc. But it can detect dismissed notifications and editions.

The goal is to build a utility library to save some "code duplication" from all different types of Sailfish smartwatch programs, which can be statically linked or included. Not a complicated framework or anything like that. Both my Toq and Gear 2 programs are now using it.

In the future I hope to add the MPRIS client/media player from pebbled, and maybe some other features (e.g. reading calendar?). Feel free to send in patches or fork in Github, etc.

Re: [Announce] Pebble Watch Connector daemon
 

Just released 1.1

Re: [Announce] Pebble Watch Connector daemon
 

I can't get it to work. The native browser can use GPS, but e.g. Maptastic or Get Back To can't get a position on the watch. I noticed, even with these apps active, the GPS-active icon on the phone doesn't appear. Is there an app which is known to work, so I can test?

Re: [Announce] Pebble Watch Connector daemon
 

For me Yelp! works without problem. But only if I am not on Wlan. Everytime I enable Wlan location for Yelp! stops working.

Re: [Announce] Pebble Watch Connector daemon
 

I use Crowex watchface as my main and it gets my local weather just fine.

Re: [Announce] Pebble Watch Connector daemon
 

Crowex seems to be able to get some location, but I'm not too sure it's the correct one. Yelp works, but might use geolocation based on IP. Pity. I was hoping Get Back To or an alternative works, as that might come in handy at times.

Also, neither webcat nor webpirate can get the current geolocation, but I don't know if that's because of this issue, or it simply isn't implemented. Since they also use Qt's webview instead of Gecko, it might be related.

Some serendipity though: scrolling in the app store is really hard. But I noticed that if you first move your finger to the left, and then up/down, it works consistently. Seems like there's some conflict on what to scroll: the webview content or the Silica-stuff around. Or something like that.

Re: [Announce] Pebble Watch Connector daemon
 

Hi Smoku,

Thank you so much for the pebble app. I can't believe how lucky we are to have such a high quality open source app for Sailfish, especially when the app for Android is proprietary!

I now have it working well, but one thing I noticed is that I wasn't getting XMPP messages through until I unchecked and re-checked the option for Messaging notifications. Is this something you've seen before? I was thinking maybe the default config file might have different options to what's shown in the GUI or something like that?

Thanks again! :)

Re: [Announce] Pebble Watch Connector daemon
 

Yes. We have had an issue with setting default value of setting to true. Even though UI "thinks" it is true, the demon "thinks" it is false. Looks like it is back with new Qt version. Checking off/on fixes it.

I have no good idea how to fix it... :(

Re: [Announce] Pebble Watch Connector daemon
 

Thanks for the reply. Out of curiosity i had a look at the code, it's very readable! I wish I could write like that.

So are you saying the bug disappeared and reappeared with the last couple of updates to qt? Do you know of any other sailfish apps that have had similar issues?

Re: [Announce] Pebble Watch Connector daemon
 

We fixed it.
But it looks like the fix stopped working with the upgrade to Qt 5.2.
It is hard to debug, as it does not have a stable reproduction.


Are there any other apps architectured as a daemon + configuration app tandem?

Re: [Announce] Pebble Watch Connector daemon
 

I already mentioned about it in here:
http://talk.maemo.org/showpost.php?p...&postcount=216

It is not easily reproducible because an unitialized variable (e.g. Settings::incomingCallNotification) is being read (valgrind should complain).

QObject->property() will only return an invalid variant if the property does not exist. The property exists (it is not dynamic, since it is declared via Q_PROPERTY), and therefore the isValid() check is useless (always returns true).

Thus, even if the dconf setting does not exist, the current value of Settings::incomingCallNotification is read. This is not initialized in the constructor (which doesn't initialize much), and certainly is not initialized by MDConfGroup (because the setting does not exist in dconf yet).

Therefore, a random value is read.

Sorry I don't have time to make a patch atm, but it should be as trivial as changing the settings.h constructor to initialize the member variables to the proper default values.

Re: [Announce] Pebble Watch Connector daemon
 

Thanks both of you!

I don't have much programming experience (I'm a Civil Engineer) but am keen to learn - I use Plasma Desktop on my laptop so learning some Qt will be a double win because I can use it with both Sailfish and any desktop apps I write.

Explanations like above really help with the learning, I hope I'll be good enough to contribute to projects like this soon.

Thanks again :)

Re: [Announce] Pebble Watch Connector daemon
 

Ouch! I missed that.
MDConf returns invalid QVariant for non-existing values. But in MDConfGroup there is an explicit check not to store invalid QVariant.
Also like you noticed, QObject would not return one anyway.


I'm hesistant to such change as it would mean storing default values both in daemon and app and a need to keep them synchronized.

Re: [Announce] Pebble Watch Connector daemon
 

But... If I see correctly, we could in constructor: set defaults, resolveProperties() and then call MDConfGroup::propertyChanged() to flush all (defaults + read properties) back to DConf, right?

Re: [Announce] Pebble Watch Connector daemon
 

The current situation is much worse where you're doing that implicitly depending on how the ->isValid() checks are wired :)

But generally I agree, I just wish there was an easy way to package+install dconf schemas in Mer... I have hit this in almost every Jolla program I've made.

Re: [Announce] Pebble Watch Connector daemon
 

Agreed of course. :D
But I would like to fix it once-for-all well, not with some cludges.