Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Android 10 - Select corpses regenerate on reboot #2560

Open
mcl21014 opened this issue May 10, 2019 · 0 comments

Comments

Projects
None yet
2 participants
@mcl21014
Copy link

commented May 10, 2019

What happened?

I ran the CorpseFinder. Detected some corpses from a Google system app. Proceeded to delete them. Two of the private data corpses persisted after reboot.

What did you expect to happen?

Either the corpses would be all gone after reboot, or ideally all would be excluded.

How can I reproduce the issue?

Run the CorpseFinder on an install of Android 10 beta 3 and delete. Then reboot and run again.

Comments

Running Android Q Beta 3. Think they all should be excluded by default because some regenerate on reboot. See log link for more details. https://mega.nz/#!TcEnXKpD!5-2n4av8ApGTxfn5s05uP6PkcBBYZIaZbbW7mmQMc_U

SD Maid

Version: 4.14.8 (41408)
Unlocker: 4.3.7 (40307) (true)

Device

Root: RootContext(rootState=Root(state=ROOTED)
Fingerprint: google/marlin/marlin:10/QPP3.190404.015/5505587:user/release-keys

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.