Search results for:

Can we request a phone ID or e.g the MAC address or something from the watch via Gadgetbridge? It would be cool to just encrypt the data with e.g. the phones MAC address.

Noob GIT question:
Since a couple of weeks I get duplicate entries in my GIT actions when I sync my fork. Is that anything I can resolve without setting everything up from scratch? See screenshot.

I am not affected, but won't a 3D printer's printing bed do the job? You could easily set it to 70°c preheat (without printing) and set the watch with the display down on the bed for some longer time.
Just an idea...

In the Apps view or at https://banglejs.com/apps/ you can set "Always update time when we connect" in the tab "more". Maybe that helps. Also make sure the time zone of your phone is right. Also maybe post a list of apps installed on the watch.

Changed to the f-droid apk and no fifo_full so far. Knocking on wood.

It's the Play Store app.

I still get the fifo_full error more and more. Any Ideas?
I'm running the bangle GB app on my Galaxy S20 with Stock Android 13. In GB the MTU option ist disabled.

Maybe this helps to work around:
https://forum.espruino.com/comments/1614­9905/

Or... we'd do it online via something like Teams or Discord. However, this has to be prepared very detailed I guess.

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?

I got both messages from time to time (not always, but frequently).

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.

Awesome, I see the full dropdown now... Thanks!

The loader schould be 100% the original source. I acutally do not get the error on my PC using Chrome, but I get it on the phone with Chrome.
Chrome remote debugger shows this on the phone

I wanted to check out translations. In my own app loader under settings, only "none (English)" is shown. How do I add all the languages there?

I would give that a try, but I can't find it.
Need to mention that I have https://play.google.com/store/apps/detai­ls?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.

I frequently get this error when gadgetbridge reconnects to the watch.

Is there anything i can do? I actually turned of calendar syncing.

Currently the rotation is set back to 0° when set to "off". I will not touch rotation settings when set to "off" from the next version on.
Maybe I'll also distinguish 0° and off eventually; not sure yet.

It is https://github.com/espruino/BangleApps/t­ree/master/apps/widbt_notify

In https://github.com/espruino/BangleApps/b­lob/master/apps/hworldclock/app.js I got the remove handler.

So, my watchface shows the seconds using setTimeout. I noticed that it will still redraw them even if a widget shows an E.showMessage above it. How do I handle that? Can I check for it somehow and then temporarily stop the timeout?

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.

?

Sorted it out. Looks if it is working so far. Thanks a million!

Sorry, still learning. How does this work if I want to pass something to the function?

function doublenum(x) {

will that be like

let doublenum= function(x) {

?

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?

@Serj i was thinking of a config setting that allows you to set the rotation level to 180(default), disabled, 90 and 270.
That way you can swipe from 0 to the configured value and back.
Would that fit your use case?