[BUG] Shizuku/Sui/Root installer automatic updates that fail keep retrying so badly that they burn through system resources.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by tracing the Shizuku automatic-update flow and reproduce the repeated failed-update behavior with the steps in this issue, while considering the related failure in #1266. Done should mean a failed automatic update is detected and does not continue retrying in a way that drains the device's battery or resources.
Written by the indexing model from the issue text.
Description
Before you submit
- I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
- This issue contains only one bug.
What's going wrong?
This may be a symptom of other issues that cause updates to fail, like #1266 , but before I diagnosed it it was actually proving to be a pretty massive issue, burning through my phone's battery in two hours where it normally lasts upwards of eighteen.
Since it was a background app, it didn't even show properly in battery manager, hiding behind the apps in the foreground, but when I disabled auto updates the phone cooled down for the first time since #1266 began and my battery life is back to normal.
If an automatic update fails, it needs to be detected somehow and disabled. Perhaps a check to see if it's the same signature or reported version as before the update?
How do we reproduce it?
1: Enable automatic updates with Shizuku
2: install some outdated apps on purpose
3: wait, feel back of device, compare battery drain with updates off.
What did you expect?
No response
Screenshots
No response
Your phone
Google Pixel 7 Pro
Android version
CalyxOS 15 EoL release
Droid-ify version
0.7.0
Anything else?
No response
- Dominant language
- Kotlin
- Stars
- 7.7k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Droid-ify/client
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in Droid-ify/client
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
liberation-data/drivine4j#547 ·
Maintainers usually reply within 1 day
-
App asks for diameter for emergency=hydrant + water_source=groundwater. But should probably not.Openfeedback required
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
streetcomplete/StreetComplete#7354 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Lists import errorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PimpinPumpkin/Vela#921 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day