Shizuku Doesn't Work - App Cleaner

[SyCoREAPER]

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

[d4rken]

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]

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]

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]

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.

[d4rken]

Is this still a current issue?

[SyCoREAPER]

Is this still a current issue?

Thanks for following up, figured this was closed but was going to reach out yesterday.

Yes and No.

Release/Beta is not. The newest RC is leaps and bounds better. Feel like freeloader using the FOSS version (despite having paid for GP version). Shizuku is as the log says way faster now and works consistently. Amazing job, huge props!

One curiosity is the accessibility in the RC doesn't clear all apps cache. I ran it 4 times on inactive/not used in a long time (but still enabled state) apps. Same 48 apps have their cache during repeated scans.
Same goes for empty folders and curiously one games logs. Some empty folders I can understand but there are bunch from no longer installed apps. For the game, logs cleared for all but the one.
Accessibility missing those 48 is a bigger issue in my mind over a few tiny logs and empty folders.

Subscription in GP for my parents phones each as well, like it that much. As I mentioned, you put a s-ton of work in and yet have a very reasonable subscription fee that isn't greedy and still update, reply to tickets and GitHub. That smaller fee vs greedy devs allowed me to get more subscriptions and willingness/happy to do so.

Otherwise again, amazing work, keep it up. This app is invaluable.

[d4rken]

Don't know about the accessibility issue you are describing. We have to distinguish between two cases:

• SD Maid is not clicking the button correctly
• Clicking the button does not clear all cache

The first I can fix, the second one I can not, what happens when the clear cache button is clicked, is up to the system (#1136 might help here).

I'm closing this ticket as it seems to be fixed.

If you think the other issues are worth following up upon, please create new tickets with debug logs.

Thanks for your support ☕🫶

[SyCoREAPER]

Don't know about the accessibility issue you are describing. We have to distinguish between two cases:

• SD Maid is not clicking the button correctly
• Clicking the button does not clear all cache

The first I can fix, the second one I can not, what happens when the clear cache button is clicked, is up to the system (#1136 might help here).

I'm closing this ticket as it seems to be fixed.

If you think the other issues are worth following up upon, please create new tickets with debug logs.

Thanks for your support ☕🫶

That does appear to be the case with the cache. I tried clearing one of the ones that pops up again

Obviously the simplest solution is not to click it again but can the scan have a cool down where it ignores previously cleared cache in say past 15 minutes or 1 hour and basically just hides them?

Anyway thanks for the above and solid Release Candidate, seems very stable to me for being RC

[d4rken]

Obviously the simplest solution is not to click it again but can the scan have a cool down where it ignores previously cleared cache in say past 15 minutes or 1 hour and basically just hides them?

Then users would accuse of dishonest things...