Most recent activity
-
I see that the "TOTAL" memory is increasing constantly at a rate of about 1MB/s.
Oh wow, that's huge.
It is possible there's a memory leak, yes. I keep an eye on Bangle.js itself but a leak on the Android side is not something I've tested for myself.
I'm not an Android developer so I'm not sure I can really be more help than Google about how to track it down... I think you'd have to do your own build, but the code responsible for the HTTP request is https://codeberg.org/Freeyourgadget/Gadgetbridge/src/branch/master/app/src/main/java/nodomain/freeyourgadget/gadgetbridge/service/devices/banglejs/BangleJSDeviceSupport.java#L591-L701
I wonder if it's related to
Volley.newRequestQueue
- maybe that should just be called once?I'm afraid I'm on holiday next week so I'm not going to be able to help tracking this down until my return though
-
That's great - thanks for that graph. It does seem like it's quite 'close' extracting sleep + not sleep. I wonder if there's anything we could do better.
Also makes me think that we could potentially have a '60s health' event if that was useful - it wouldn't be too hard to do, and might give apps like this a lot finer-grain data to work with if it's useful?
-
-
I still feel I need to order second watch, just in case my one breaks down
Well if you want to that's great, but I wouldn't do it because you'll be worried you'll break it - they're made for this. Look at it this way - we've sold around 10,000 Bangle.js 2s, mostly to folks who spend a lot of time messing around with all kinds of things on them, and I don't believe I've had a single one returned that was broken by something done in software.
is there there bangle.js 3 coming with gyro?
Not any time soon I'm afraid, I'll be sticking with Bangle.js 2 for quite a while!
-
-
There's no reason the caller name couldn't be in the middle of the screen, it's just how it was implemented originally. It'd be very easy to change at https://github.com/espruino/BangleApps/blob/master/apps/android/boot.js#L60-L65 and I doubt anyone would have an issue with it.
Pull requests very welcome :)
-
-
Thanks! A lot of those are on my wishlist too.
I'm very tempted to overmould the case with rubber and have rubber buttons and wireless charging so there was a really nice water resistance and maybe an unscrewable rear cover - but that probably makes USB/baro/mic/speaker a no-go.
I think there's got a be a decision about whether we go for water resistance or not - because to be properly able to go underwater it really means no holes at all.