Here's a weird one. I've got a Moto 360 running the latest 5.0.2 with ambient mode
turned on. I looked down at the watch earlier today and it was reading 1:28 or thereabouts, in ambient mode, and with some sort of peek card pushing up from below. The actual time was 1:43. Uh oh! I bumped the watch, waking it up, and it refreshed properly to the current time.
I extracted the logcat when I got home (https://github.com/danwallach/CalWatch/blob/master/logdumps/refreshrate-01mar2015.txt
). You'll see that precisely nothing was logged from 13:28 to 13:43. My CalWatch watchface is built from the standard demo template and does all the same things as the SweepFaceWatchService example from Google. So, at least in theory, this shouldn't be happening.
(Actually, CalWatch tries to refresh every 12 seconds in ambient mode, using a Handler, so the minute hand is more communicative. This only ever works sporadically. The handler, demonstrably, does nothing to wake up the watchface if it's deeply asleep, so at least I'm not being anti-social with overusing the battery.)
Has anybody else run into something like this? Back before we had the official watchface API, it was standard practice to use AlarmManager to wake you up once a minute. Is anybody still doing that?