-
-
Wow, what a clickbait-like subject :) But I really understand what you mean. I had a Pebble and looked for a replacement. They did a really good job with their UX (hardware AND software). But they had a lot more staff to work with. If you could multiply @Gordon by 5, we would have the perfect eco system and the watch would be perfect reagrdless the hardware flaws we have :)
My main pain points are:
Reliability:
I still get things like fifo overflows or memory leaks as well as Gadgebridge errors. I know this is probably only me because no one else is complaining.Battery:
My watch lasts about 4-5 days which is awesome compared to any WearOS or so. I know, I use some widgets and so on, but I was hoping that it would last even longer.App Loader:
Same issues like Pebble had: There are more and more Apps and Watchfaces. I still don't have a good overview over the things I potentially like. Also there are some duplicates with slightly different features.Lack of developers:
We have really talented people here who spend much of their free time for the community. I really appreciate that. But having a couple more full time developers would push the whole eco system. Maybe we can archive something with donations like patreon.com or so? Having only one full time developer who keeps everything together also results in Apps that don't look like "from the same mould". I also really liked that on other watches, but I understand that everyone is required to participate. So having a UX that looks like a watch with APPS instead of a blank platform on which you can start any app is a bit hard to archive.Water:
Well, I am actually concerned having it on while it's raining - just from reading in this forum :)Despite all that I am a daily user and I still love it.
-
-
-
-
I would give that a try, but I can't find it.
Need to mention that I have https://play.google.com/store/apps/details?id=tk.drlue.icalimportexport.premium running. I deletes the whole calendar on the phone and imports an ics file nightly. Maybe that is some issue. -
-
-
-
Current code attached (the bottom one) . There seems to still be a memory leak issue. Any advice?
Do I need to do something like
delete queueDraw; delete def; delete queueDrawSeconds; delete doublenum; delete draw; delete drawSeconds; delete getCurrentTimeFromOffset; delete updatePos; delete secondsMode; // etc.
?
-
-
-
Current code attached.
When I change
var drawTimeoutSeconds; to let drawTimeoutSeconds;
in Line 123,
if (drawTimeoutSeconds) clearTimeout(drawTimeoutSeconds);
it does work when I open the launcher from the watchface. But when I get back to the watchface and open the launcher AGAIN, drawTimeoutSeconds seems to be undefined (and the seconds run behind the launcher) and the Timeout doesn't get cleared.
Any suggestions what I'm doing wrong here?
-
-
YAY, now it worked.
That is soooo strange!
I have theconst BANGLEJS2 = process.env.HWVERSION == 2;
at the top of my code.
console.log BANGLEJS2;
shows "true".
But the following "if (BANGLEJS2) { " is not entered! No clue what happens there.When I remove the check fpr BJS2, it works.
Another problem is that I get
Uncaught Clock has no widgets, can't fast load
When leaving the launcher despite i do load and show widgets at the end of my code.
-
-
-
-
-
-
https://banglejs.com/apps/?id=widbt_notify does this pretty good. It can be set to buzz when connection is lost. So when I leave the house without the phone, I get notified.
-
I'd like that feature.
(TLTR - sorry, may be off topic:)
And I'm a real fan of privacy, but wouldn't be an additional log report feature be awesome?
From the user point of view:
In the settings of each registered app and in the general settings we could have a "send crash reports to author" (default=off). Then the watch could accumulate all console.log of each app (and the firmware) and send it to the correspondent developer once a day.
From the developer point of view:
An app could optionally register for this feature with an email address. Logs would be gathered on a server and the server would send it to the developers.
I know, with the current eco system this sounds like science ficture, but wouldn't it be neat to see where useres are struggeling even befor they know?