Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Out of memory when using OpenTrack #3581

Open
dror3go opened this issue Sep 21, 2024 · 4 comments
Open

Out of memory when using OpenTrack #3581

dror3go opened this issue Sep 21, 2024 · 4 comments

Comments

@dror3go
Copy link

dror3go commented Sep 21, 2024

Affected hardware version

Bangle 2

Your firmware version

2v24

The bug

Using OpenTracks app while the phone is connected to the Banglejs2 watch - at some point the phone turns blank with a blurry message at the bottom starting with FIFO_EOWL and ending with MEMORY. The rest is overlapping letters which makes it impossible to read.
From that point - the phone becomes useless: long press on the button reloads it, but it doesn't update the clock, it doesn't show notifications, and the screen is not interactive.

Installed apps

No response

@bobrippling
Copy link
Collaborator

Which is the OpenTracks app? Do you mean Open Street Map?

@dror3go
Copy link
Author

dror3go commented Sep 23, 2024

No, I mean the Android OpenTracks app, which probably generates many notifications on the Banglejs watch during activity.
I ended up doing a factory reset on the watch since it became unusable.

@bobrippling
Copy link
Collaborator

Gotya - sounds like a problem with either Android or the Messages App (if you're using the default messages app?)

@gfwilliams what do you think? Notification throttling?

@gfwilliams
Copy link
Member

I think this may have come up before - as I understand it it's kind of an issue with OpenTrack - it creates literally hundreds of notifications (I think when it's downloading something or displaying some kind of progress?). I think other apps use 'local' notifications which get ignored by Gadgetbridge but OpenTrack makes them global.

You can go into Gadgetbridge, notification settings and block all notifications from OpenTrack and I think that'll fix it though. It shouldn't have been anything wrong with the Bangle itself - once Gadgetbridge disconnected and stopped throwing notifications at it I think it would have deleted the existing notification file and it all would have been fine.

We could try and push something to Gadgetbridge that blocks OpenTrack by default - I guess throttling is possible but it sounds problematic - someone's going to complain that something didn't get through

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants