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

Shizuku Doesn't Work - App Cleaner #1390

Open
SyCoREAPER opened this issue Sep 8, 2024 · 4 comments
Open

Shizuku Doesn't Work - App Cleaner #1390

SyCoREAPER opened this issue Sep 8, 2024 · 4 comments
Labels
ADB ADB/Shizuku related api: 34 A14 (Upside Down Cake) bug Something isn't working as expected c: AppCleaner

Comments

@SyCoREAPER
Copy link

Describe the bug
Shizuku is not used to process App Cache Cleaning. Reverts to Accessibility despite Shizuku having granted access. Also Logs cannot be recorded/generated in Shizuku mode to help you troubleshoot. May occur with other nodes but I only use the App Cleaner.

To Reproduce
Steps to reproduce the behavior:
Setup app. Select use Shizuku. Grant Access from Shizuku prompt. Run SDMaid. App Cleaner. Search for Cache. Delete Cache.

Expected behavior
Cache should be cleared in the background. It appears to fail and revert to Accessibility.

Smartphone (please complete the following information):

  • Device: Samsung
  • OS: Android 14
  • Root status: No. Shizuku Only.
  • SD Maid 2/SE version: Current SDMaid SE. Has not worked since purchase 3 months ago.

Debug log
Debug log runs, produces a 0KB file, IOW, nothing. Debug log works in non-Shizuku mode.

Screenshots/Video
N/A

Additional context
Full/Paid SDMaid SE

@SyCoREAPER SyCoREAPER added bug Something isn't working as expected triage This ticket needs to be sorted and labeled. labels Sep 8, 2024
@d4rken d4rken added c: AppCleaner api: 34 A14 (Upside Down Cake) ADB ADB/Shizuku related and removed triage This ticket needs to be sorted and labeled. labels Sep 8, 2024
@d4rken
Copy link
Member

d4rken commented Sep 8, 2024

Not being able to record logs in Shizuku mode is a weird bug 🤔 Turning on the debug log recording, should theoretically also turn on the logcat logger. If you can record a logcat directly through ADB it might help shed some light one the cause.

The accessibility service is still used with Shizuku, if you are including system apps. Can you? If system apps are not included, then the accessibility service should not launch when using Shizuku.

@SyCoREAPER
Copy link
Author

I mean logs in your app don't work with Shizuku enabled.

In regards to System apps, no system apps. It triggers Accessibility on user apps from the play store. I recorded the screen and played back in slow motion to make sure I didn't miss anything.

@d4rken
Copy link
Member

d4rken commented Sep 14, 2024

Debug logs should be fixed via #1401 👍

Are you selecting "Delete" from the Dashboard?
Shizuku only works when selecting all apps, and all apps user apps.

Selecting single apps will fallback to the accessibility service.

Cleaning all apps via Shizuku works like this:

  • If the app has public cache in Android/data then we delete that directly via ADB-level access through Shizuku
  • If the app has private cache (and all apps are selected) then we call the system trimCache API.
  • Now we wait and monitor all apps and wait for their size to change, to indicate that the trimCache is successful (there is sadly no better API)
  • At the latest after 10 seconds (timeout) if there are any apps, for which the size has not changed, we clear these via accessibility

@SyCoREAPER
Copy link
Author

I'll have to run a log next time around if it's fixed.

I just deleted every app cache one by one and every time it was Accessibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ADB ADB/Shizuku related api: 34 A14 (Upside Down Cake) bug Something isn't working as expected c: AppCleaner
Projects
None yet
Development

No branches or pull requests

2 participants