Hi again Wilhelm. Yes this has always been an issue - sometimes the app simply doesn’t wake up. I think it’s a firmware bug and have reported it as such. I’ve put quite a bit of code around this to help prevent it but sometimes the wake up simply does not happen when scheduled.
Ok, bit of an update. From another user - apparently at least one of the 4.x firmware updates broke it. However, the latest is fine, so if you update all should be well.
2.8 is now available. It has some shorter snooze options, memory usage is less and the Aplite crashes should no longer happen.
Oh yes, and it now supports Pebble 2.
Thanks a lot for that great app! Just got my Pebble 2 and that was the first app I found useful and I had installed
What API did you use to make this watchapp’s main function, WorkerAPI or WakeupAPI ?
Sorry I’m new to pebble SDK, not sure what’s different between them.
It uses both.
The WorkerAPI is one that allows you to run a process or part of your app in the background. The WakeupAPI allows you to schedule the launch of your app at a specific time.
Is there a possibility to add more specific time to schedule? Example - i want to set start time to 7:30 AM instead of 8 AM.
Thanks for using the app! I’ll look into it.
App is really nice. More detailed time to pick would be really useful for
me. I am using Nag for Pebble from time to time, and there are different
vibration patterns, this is also nice.
There is something wrong with app. I’ve set schedule end time for 3 PM, and
yesterday it stopped notyfying me from 2PM. Today it sometimes vibrate,
sometimes not. I don’t know what is going on.
Next suggestion. Could you add step limit for motion sensing? For example i dont want to abort next alert if my steps count from previous alert is too low.