Ge0rG on Nostr: nprofile1q…uktud Okay, this is weird. Normally I'd ask for adb logs from when it ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqudr6t3ma5srclvn2vm5gtpr7s6fvfkjx8pe7dy2hna76perpaqmqhuktud (nprofile…ktud)
Okay, this is weird. Normally I'd ask for adb logs from when it was woken up, but that's pretty moot on a device that's in actual use.
You might try to force stop it via Debug tools:
adb shell am force-stop <PACKAGE>
And then monitor its state from time to time with
adb shell dumpsys package <PACKAGE>
Source: https://stackoverflow.com/questions/37464726/how-to-tell-if-an-android-app-is-in-the-stopped-state#comment104068975_41088309
There should also be a list of registered receivers in the dumpsys data.
Okay, this is weird. Normally I'd ask for adb logs from when it was woken up, but that's pretty moot on a device that's in actual use.
You might try to force stop it via Debug tools:
adb shell am force-stop <PACKAGE>
And then monitor its state from time to time with
adb shell dumpsys package <PACKAGE>
Source: https://stackoverflow.com/questions/37464726/how-to-tell-if-an-android-app-is-in-the-stopped-state#comment104068975_41088309
There should also be a list of registered receivers in the dumpsys data.