How much time should the watch face take to be battery efficient?

Hello I have pretty complicated watch face - sun and moon calculations, tens of transforms between polar and cartesian coodinates for watch hands and moving objects. I measured time it takes to draw the watch face and it is about 200ms. Is it too much for the battery?

Thanks, Jan

0 jim_m_58 over 5 years ago

How are you measuring this? In the sim or a real device? You want to test this on a real device, and it could vary by device.

Based on what you're doing, it won't be the minimum impact for a CIQ WF. For that, you can use the WF template in Eclipse to get a feel for that (File>New>Connect IQ Project>WF) and run a multi hour/day test (maybe over night) - Charge to 100% and see how long it is before you hit 50%, 75%, or whatever it is after 8 hours - don't just run for an hour) and then do the same with your WF.

Another thing to look for is the time it takes to update when you move to the the widget loop and back. Users will notice if there is a delay in painting when you return from the widget loop, maybe as much as battery

0 JayBee over 5 years ago in reply to jim_m_58

I store miliseconds from System.getTimer() at various points and then display differences. I tested it on the watch. The SunCalc calculation for various Sun events take about 100ms and the rest, sin/cos functions and drawing plus Moon calculation another 100ms. So far it does not seem to have impact on battery (3% in 12 hrs with oxymeter always on). Jan

0 jim_m_58 over 5 years ago in reply to JayBee

It can vary by device. For example, a f6 has a bigger battery than a va4, so 3% on a f6 would be more on a va4. That's why benchmarking with something like a really simple CIQ WF comes into play.