You are reading a single comment by @Ganblejs and its replies.
Click here to read the full conversation.
-
or use the new 'remote connection' in the Gadgetbridge app loader).
I tried this once, but for some reason somewhere along the way the watch was disconnected from the web ide where I was checking for the error message. So that time it didn't yield to much.
Tonight I had the battery fall of a cliff once again when Podcast Addict was active (Fastload utils not installed). Unfortunately I only have the gadgetbridge battery graph and nothing else. But I'll try connecting it to the web ide as suggested again.
3 Attachments
-
Ganblejs
Well, hopefully you'll get a stack trace which will point straight to the
Androidapp on the watch, which would help a lot - but as you say you wouldn't see that message if you were then connected to Gadgetbridge (unless you used logcat, or use the new 'remote connection' in the Gadgetbridge app loader).You could definitely try and enable logging and see what happens - there is even logging in Gadgetbridge itself (or you obviously have Android Studio set up so you could look at logcat to see what's being sent).
I think if you're looking at the Gadgetbridge logcat while using Podcast Addict and you're seeing a bunch of data transferred to the Bangle, that could be a good step to see what's going wrong. If you can isolate the
GB(...)message that's being sent, we could try running that in the IDE withdebugger;GB(...)and trace through exactly what happens.