Most recent activity
-
So what's actually happening? Between 10 PM and 11 PM what actually gets displayed on the screen?
As far as I can tell, at some point between 10 and 11 pm, the time gets set to some random value in the past and step count drops to zero. This incorrect info gets displayed on the clock, as if that was the current time. Or, if I have some other app open, the clock widget (widclk) displays the incorrect time. Also, since my own stopwatch app works by storing the start time and displaying time since start, it displays a very large negative time.
And does pressing the button once to enter the launcher and again to exit it fix the issue?
No. Doing that, or just generally switching apps, does not fix it. I've been disconnecting and reconnecting my phone to force a time sync to get the time back.
I guess as a starting point, it'd be good to make a note of the actual time when it happens and to make a screenshot (you can do that from the app loader now).
I don't catch it at the exact moment it happens. I only notice it some amount of time later when I look at my watch to check the time and notice it's displaying 2 AM or something. But I guess I can make a note of when I noticed it. And nothing weird shows on the screen, but I can definitely still take a screenshot
If you can be connected with the Web IDE when it happens, you might find there's an error message displayed which really helps to track it down.
Good idea. I'll try to have my watch connected to the web IDE at 9 PM and look for any error messages.
Also, very importantly, what clock face is it?
My own clock face, infoclk. Maybe I'll try another one if it keeps happening.
It could well be there's some bug in the clock face - I guess maybe if some code fails, it could not update the time/step count variables correctly and then they end up displaying the wrong info.
I thought the clock face only displayed info, and wasn't responsible for actually setting it?
Also, it did not happen last night. But I will try to be prepared tonight.
-
For the past few days, there have been times when I looked at my watch and saw a displayed time that didn't make sense. So far, it has happened between once and three times per day, always between 10 PM and 11 PM. My first thought was that these were reboots, as the time is set to some random point in the past and step count to zero. However, I do not see the watch lighting up on its own and if I leave an app open, it stays open, so it's not actually rebooting.
This is not correlated with any software updates. Last time I updated anything was weeks ago, but I updated earlier today as a troubleshooting step, bringing the firmware version from 2v23 to 2v24, settings to 0.74, and sky spy to 0.03. Updating made no difference.
Is there anywhere I can begin to troubleshoot this?
-
Agreed. I personally far prefer using the touchscreen over buttons when I can, but having more buttons won't hurt anything when I can still use the touchscreen. It will only make the watch more usable with gloves. Having the watch be usable with gloves would be a major improvement and serious advantage over other smartwatches.
-
You could definitely bypass that by taking apart the watch and reading the flash chip externally. You could possibly also bypass that by running something over the SWD pins that dumps the file contents. Also, I don't know whether Bluetooth passkey and whitelist are still active even after a reboot without loading code or in DFU mode.
-
Reflective LCDs work by reflecting ambient light. They are readable without a backlight, but cannot be backlit well if at all. They work well if there's enough light, but not very well in the dark. At best, you might have a frontlight that lights the screen unevenly.
Transmissive LCDs instead pass light through. They have a backlight to cover dark environments, but they are only properly visible with the backlight. In brighter environments, you need to turn up the brightness to compete with the ambient light. In sunlight, you end up needing to use a lot of power, if your backlight can even get that bright at all.
Transflective LCDs are capable of doing both reasonably well. In a dark environment, they can be lit evenly with a backlight. In a bright environment, the ambient light helps rather than competes, so the backlight can be turned off and the display remains visible. This saves a lot of power. As halemmerich has pointed out, we already have one on the Bangle 2. This is a huge reason why we can have multi-week battery life with an always-on display.
-
I do not know how to fix the error that the IDE is throwing. But once that's fixed, you can click the cylinder icon to view the list of files in the device storage, and then each file will have a couple buttons, including a trash can to delete it. Or, you can use the Storage module. Specifically,
require("Storage").erase(".boot0")andrequire("Storage").erase(".bootcde"). -
It sounds like you didn't actually break the firmware, just the JS code that gets run on boot. The files that get run are described here.
Follow the procedure to reset without loading any code. That should get you to a Banglejs logo screen. From there, use the IDE to delete any of the following that exist: .varimg, .boot0, .boot1, .boot2, .boot3, .bootrst, and .bootcde. (You probably only have .boot0 and .bootcde.) Then, go to the app loader and reinstall the Bootloader app. That should fix it.
-
I personally like using the "event" option for one-time reminders, and I delete them after. I'm thinking that adding a delete after expiration option just like the timers have would be a good idea, and I'm willing to attempt to implement it. To avoid duplicating work, is anyone else already doing that?
It didn't happen last night either. I recently took a flight that involved changing time zones, which seems to correlate with the issue stopping, so maybe time zones had something to do with it? My home time zone is UTC -7, and I was visiting UTC -4 for 2 weeks. The flight was from UTC -4 back to UTC -7. I forgot the watch had a time zone option in the settings until now, so unless it got updated automatically when my phone changed time zones, it was on -7 the whole time while the watch actually had -4 time on it.
My full list of apps is gpsautotime (0.04), magnav (0.07), messageicons (0.07), mtnclock (0.04), openstmap (0.30), pomoplus (0.06), powermanager (0.11), qmsched (0.10), qrcode (0.06), random (0.03), rescalc (0.04), rgb (0.01), rgbvest (0.01), rpnsci (0.04), slevel (0.04), snaky (0.01), speedo (0.06), stlap (0.04), stlapview (0.03), tetris (0.12), tictactoe (0.03), torch (0.11), twentyeightbysix (0.04), waternet (0.03), waypoint_editor (0.02), waypointer (0.11), waypoints (0.04), weather (0.26), wid_a_battery_widget (0.04), widadjust (0.03), widalarm (0.02), widbt_notify (0.17), widclk (0.08), widclose (0.02), wid_edit (0.05), widlock (0.08), widmessages (0.06), wpmoto (0.04), 2047pp (0.04), agpsdata (0.06), acmaze (0.05), agenda (0.15), altimeter (0.04), files (0.08), balltastic (0.04), bikespeedo (0.07), blackjack (0.03), dvdbounce (0.01), calendar (0.18), chess (0.05), compass (0.09), counter (0.04), dtlaunch (0.25), drinkcounter (0.26), fastload (0.06), fileman (0.03), flightdash (1.01), gallery (0.03), health (0.30), info (0.03), infoclk (0.10), keytimer (0.04), loadingscreen (0.01), messages (0.62), multidice (1.30), locale (0.19), kbmulti (0.09), messagegui (0.79), gpsinfo (0.13), drained (0.05), sleeplog (0.18), sched (0.26), recorder (0.43), hidmsicswipe (0.01), android (0.36), alarm (0.48), folderlaunch (0.04), notify (0.14), boot (0.63), flipper (0.02), skyspy (0.03), setting (0.74)
(rgbvest is not on the public app loader. It's an app I made for controlling one of my personal projects, and it does not run in the background or set the time.)
I imagine gpsautotime or widadjust are the likely suspects here?