search

RikkaApps / Shizuku

Using system APIs directly with adb/root privileges from normal apps through a Java process started with app_process.
Apache License 2.0
11.49k stars 660 forks source link

The system is possibly kept waked up with shizuku #3

Closed kcschan closed 5 years ago

kcschan commented 7 years ago

I recently observed the device(7.1.2) kept waked up which seems to be caused by shizuku(0.2.5).

Though I could not find any concrete evidence for now, there is still some clues:

1, The issue occurred after using shizuku as the privileged action proxy for your AppOps wrapper app. On another device running the same Android version and same AppOps wrapper without shizuku, the issue does not occur.

The version 0.1.99 is involved in this case: https://play.google.com/store/apps/details?id=rikka.appops

2, The issue(on the first device) disappears after a reboot, but some time(around a day) later, it occurs again.

3, I used the wakelock detector to gather statistics about wakelock duration of each app. When it happened, the device did not sleep at all after screen off for hours(suggesting partial wakelock was hold by some owner), however I could not observe any app that was responsible for the long wakelock.

Usually the wakelock issue is due to play service's NLP(network location provider) components when there is a connectivity issue, and more importantly can be observed by such tools as "an app has been holding a wakelock for a very long time "

Note: The wakelock tool app used: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

kcschan commented 7 years ago

Addition: I did find exception report in the logcat during when shizuku is in use(enabled), however it was not kept and shizuku has been uninstalled after the incident.

Please notify me in case you need these logcat output.