hehe yeah, but i have the UP

You should have the Fitbit ;-)
Did some quite heavy research & it seemed to be the best (the Fitbit Force that is, not available in many countries yet).
But we digress....

Got my Pebble today and have had my first plays with it. Everything has worked great so far, really love your app. Great job.

Noticed that one has to leave the Rockwatch app to background to make notifications work. Would there be an daemon option in the future so one does not have to remember to leave the app open?

What are peoples opinions on battery effects with pebble and rockwatch app? Do these do bad damage?

For some reason the watch clock goes off by one hour if I use this function. Something to do with GMT? My watch gets one extra hour with this

Thanks for reporting this, I'll take a look into it .

Tsk, tsk, go open!
http://www.angelsensor.com/

Hmmm, need to look more closely at that one, looks like it might surpass even the Fitbit Force, nice find!

Some notions, questions and suggestions after a week with Pebble and Rockwatch


First of all, thank you really much for this app. For me this combo is exactly what I needed.

I have not noted any unusually high battery drainage with this app. Then again I don't keep it open all the time, only when I am in a meeting, place where I need/want to keep my phone in silent mode or away from me.

Notifications seem to work well. However, could it be possible that the clock would inform also of incoming call before it is unanswered? Now it only informs me after the caller has ended the call. I understand that this is not notification per se, but would serve similar purpose.

Installing apps and watchfaces has so far worked flawlessly. Really nicely done. I think someone already mentioned it here, but some other indication on N9 than that the spinner goes away when app install is finished would be nice.

httpPebble is another story. So far I have only tested it with the two available Fair forecast watchfaces and results have not been that good. I often get no updates at all. Watch tells me to restart httpPebble (this not possible right?) and when it manages to get connection the location is often wrong. It seems not to matter whether I am using Wlan or GSM network. But again, it is great to see that the functionality is there.

Music control is also working quite nicely.

I know that this is definitely reaching too far, but hey, you can always have hope, right U planning to implement anything like this? https://play.google.com/store/apps/d...leglance&hl=en

One setback I have noticed so far. If the rockwatch app is left open and unused for long time, it seems to freeze. In normal usage this have not been a problem for me, but if I leave it on for whole workday or night and do nothing with it, it usually ends up in a state where it needs to be closed (phone informs of this) and restarted.

I was hoping to have Billboard script show me whether connection is on or not. But don't have skills for that. Anyone here have tried that or knows how to do it? Maybe better ask this in the Billboard thread.

But all in all just a great app. Ones again N9 has something that Lumias don't have

So my pebble finally arrived.

I paired with the N9 with no problem but when I ran the firmware update it looks like it works, the display on the watch shows progress from 1 to 100% and then it returns to normal but the spinner in Rockwatch just keeps spinning. When I go to About on the watch it still shows the original firmware version 1.10.0.

After about an hour I closed Rockwatch but then it won't re-open without a phone reboot.

I tried turning the pebble off and on again but when it rebooted the font is really small. Factory reset doesn't fix it either.

I'm using Rockwatch 1.1-1 Are there any logs or anything I can look at to try to figure out what's wrong? I'm hoping that if I get a sucessful update the display will return to normal.

You can view debug output by runing Rockwatch from a terminal (or via ssh), to do so run:
PYTHONPATH=/opt/rockwatch/deps/ /opt/rockwatch/rockwatch.py

or save the output by running:

PYTHONPATH=/opt/rockwatch/deps/ /opt/rockwatch/rockwatch.py > /home/user/MyDocs/rockwatch.log 2>&1

If you could do so and upload the output that'd be helpful in seeing what's happening.

You can also try manually upgrading the firmware via libpebble on a desktop computer, by checking out libpebble from https://github.com/Hexxeh/libpebble

and running:

./p.py load_fw <path_to_firmware_file>

Although this should do exactly the same as Rockwatch (which is based around libpebble).