Notices

Isn't the new version backwards compatible?

No, it is not; if you open the new version in the old firmware, the daemon will also crash on startup, as does the old version if you open it in the new firmware.

By the way, I've been working on some UI for uploading/unloading apps from the Pebble:

Apart from this, I've added support for the getWatchToken / getAccountToken JavaScript functions. The first one will return a (MD5) hash of the watch serial number; the second one will return a random number that is persisted between reboots. This means setpebble.com apps should now work and configure properly. I'd still like to add some "per-app" randomly generated salt instead of using the app UUID in order to actually make the hash secure.

Here is the updated testing package.

You still need to manually unpack .pbw files in ~/.local/share/pebble/apps for everything to work. The plan is to eventually register a file association so that downloading .pbw files from the browser will automatically unpack them there.

Smoku, did you get your Jolla back? I would like to send all these changes back, if you are OK with that. Would you prefer small patches, or is a "big" pull request OK?

Apart from the UI + bank/app manager changes, I've done some design ones, such as entirely changing the D-Bus interface (D-Bus naming conventions + lots of new methods), using autogenerated d-bus interfaces/adaptors (still on top of the existing PebbledProxy/Interfaces), rewrote the WatchConnector's read loop (so that it handles fragmented packets), moving the music functionality out into musicmanager.cpp (so that it always uses the last MPRIS service which sent a signal instead of listening for name registrations), and detecting ICU via pkgconfig.

I am not sure if Pebble can recover from a completely botched firmware upgrade. The watch supposedly stores two firmware versions, so it should be able to roll back to the second one, but I'm not sure how much damage can you do to it from the Bluetooth protocol.

It turned out the damage is not that big that I thaught. The screen does not degrade anymore and is in usable state. And the fall broke the speaker, so I have to rely on Pebble to get the calls. ;-)
So, it generally works...

You can create one big pull request. I can see that you read my intentions for the watch page exactly as I thought it of.

Please rebase on the current master though, as yesterday I removed Log4Qt dependency, so the logging is a bit different now.

But for historical reasons it would be better if you would create a separate commit for every functional change - like you described. It does not even have to be atomic - changes can be interrelated. But it's always better to see a separate reasoning in 'git blame' than one big "Added support for JS apps" line.

Just installed the upgraded version. I like the watch page with the applications very much .

The new version is awesome so far!.

Just a silly question, how do I get the weather to work? Do I need to use a specific watchface or app on either the pebble or my jolla?

Just follow the instructions of javispedro. Download the weather app from pebble store of your choice. Extract it and put it in the right directories and install it on the watch.

how to get the github version? mind to show me how with step by step? thanks

You need to download this version:
http://smurfy.de/files/jolla/pebble-..._2.armv7hl.rpm

Then stop the running pebbled and uninstall it. Afterwards via developer mode and "su-devel" run rpm -ivh pebble-0.12-1-update9_2.armv7hl.rpm

sorry Maemouser, what command do I use to stop pebbled and uninstall it?. Whenever I try by uninstalling via warehouse, I get amissing dependency problem when installing the new package....