espruino / espruino/BangleApps

Watch stucks on "Loading..." after long waiting

Open
#3,026 7 comments 0 reactions 0 assignees View on GitHub
area-apps state-started type-bug
Dominant language
JavaScript
Stars
571
Forks
1.3k
Avg merge
17h 38m
Merged PRs (30d)
17

Description

### Affected hardware version

Bangle 2

### Your firmware version

2v19

### The bug

Previously I installed several new apps. I thought that any of new app is the reason of the issue. I suspected `cassioWatch` , but after the rallback to the the previous clock app - the problem still reproduces permanently.

After several hours of waiting display stucks with "Loading..." message, with no further actions. Also I noticed that the battery is becoming low much faster.
![image](https://github.com/espruino/BangleApps/assets/12295591/e15dacef-f594-4645-b962-f8d9f206c749)

While rebooting the watch, I also noticed `BUFFER_FULL` message:
![image](https://github.com/espruino/BangleApps/assets/12295591/440244f0-c858-4a1a-93f0-b0f378aa9632)

After reboot I still get the same behavior.

There's still a free memory on the device:
![image](https://github.com/espruino/BangleApps/assets/12295591/088d2bb9-0aea-4db9-93dd-ed0dbc9d1d62)

For now I don't understan if it's app related issue. And if it's app related issue, how can I find out what app affects this behavior (maybe there are tools for that?)?
Is there a workaround for this issue?

### Installed apps

dragboard (0.08), android (0.31), messages (0.60), messagegui (0.73), widbat (0.11), alarm (0.42), boot (0.59), notify (0.13), health (0.27), setting (0.63), about (0.14), sched (0.22), widalarm (0.01), widbt (0.09), widlock (0.08), widid (0.03), messageicons (0.05), widmessages (0.05), showimg (0.02), fileman (0.03), dtlaunch (0.24), weather (0.25), owmweather (0.03), dvdbounce (0.01), compass (0.09), espruinoterm (0.01), waypoints (0.01), speedalt (0.13), gbmusic (0.12), antonclk (0.11)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue on a Bangle 2 running firmware 2v19, paying attention to the prolonged wait, battery drain, and BUFFER_FULL message. Isolate the installed apps to determine whether one causes the failure; done means identifying the trigger or establishing a reproducible device-level cause and documenting a workaround.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.