You are reading a single comment by @Ganblejs and its replies.
Click here to read the full conversation.
-
Well, hopefully you'll get a stack trace which will point straight to the Android app 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).
Now I've tried twice with this setup:
- Watch is connected to Gadgetbridge.
- I use the new remote connection feature of App Loader to get logs/prints to the console in Web IDE. The App Loader is open inside Gadgetbridge.
- I have the bootcode you gave me on the watch.
- My android device is set up to keep screen on while charging.
- My laptop is set up to also keep awake.
But the connection between App Loader and Web IDE is soon lost.
I'll try this once more I think, or I'll try adding in Android Studios logcat in the mix as suggested as well.
- Watch is connected to Gadgetbridge.
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.