AppCleaner can't figure Screen Layout on RealmeUI RMX3760export_15_F.59

[AndyMagnom]

Describe the bug
Realme C53 Device just recently updated to Android 15 (RMX3760export_15_F.59), Now AppCleaner can't figure out screen layout and can't find "Storage & cache" (Image of the normal App Info page below).

To Reproduce
Steps to reproduce the behavior:

1. Go to AppCleaner
2. Click on Delete
3. SDMaid starts the full-screen cleaning
4. It can't find 'Storage & cache'

Expected behavior
Find 'Storage & cache', Click on it and Complete cleaning process successfully.

Smartphone

• Device: Realme C53
• OS: Android 15
• Root status: Non-Rooted
• SD Maid 2/SE version: v1.4.16-beta1 (10416010) FOSS [BETA]

Error Message

SD Maid couldn’t figure out the screen layout. If this keeps happening, your language or setup might not be fully supported. Check for updates or reach out to me so I can fix it.


Information for the developer:
v1.4.16-beta1 (10416010) FOSS [BETA]
realme/RMX3760/RE58C2:15/AP3A.240905.015.A2/T.R4T2.1752155619:user/release-keys

Screenshots Below

Additional context
Phone Language: en-us
Tried with and without Automatic system detection.

[AndyMagnom]

The debug log i provided earlier were probably useless, I think that debug log recorder also has a bug.

Recording then Ending the recording without doing anything will generate a Debug Log normally, But when i start recording and start the AppCleaner process and then end the recording, It results in an error and the Debug Log doesn't exist.

Debug Log Recorder Error

Image
Image

Debug Log doesn't exist in cache folder (Opened in MiXplorer):

Image

[d4rken]

Hm, can't really fix it without the debug log, need to know how the screen looks like from an accessibility service's POV.

Strange though that the debug log is failing. While the debug log is running, is there any file being created in the debug log path area (Android/data/eu.darken.sdmse/cache)?

edit: I prevent SD Maid from creating the log directory/files and then stopped the log. My error looks very similar to yours. So now the question is why SD Maid can't create these files? 🤔

[d4rken]

I've put some work into the debug screen and logic for the next update (including fallback paths and better errors), see #1914.

But maybe we can still get a log from the current version somehow 🤔

[AndyMagnom]

Hey, So i tried again few times to record it, Here is what i found out.

When i start the recording it makes the log file normally, I click the Scan button of AppCleaner tool and it goes well in the log file, But once i click the Delete button of AppCleaner tool, It instantly deletes the log file.

Here is what the log file looks like before getting deleted:

adb.log

I just noticed these lines at the end:

Removing: eu.darken.sdmse.common.debug.logging.LogCatLogger@9edf15a
2025-08-21T18:50:07.346Z  D/SDMSE:ADB:Host: Removing FileLogger: FileLogger(file=/storage/emulated/0/Android/data/eu.darken.sdmse/cache/debug/logs/eu.darken.sdmse_10416010_2025-08-21_21-45-30-473/adb.log)
2025-08-21T18:50:07.346Z  I/SDMSE:Logging:ADB: Removing: FileLogger(file=/storage/emulated/0/Android/data/eu.darken.sdmse/cache/debug/logs/eu.darken.sdmse_10416010_2025-08-21_21-45-30-473/adb.log)

So I tried instead of clicking the main Delete button of the tool, I tried deleting cache of a single app (Eye Button > Delete button of a singe app), Then i ended the log recording.

And it actually successfully creates the Debug Log file.

eu.darken.sdmse_10416010_2025-08-21_21-55-17-127.zip

I have no idea why the main Delete button deletes the debug log.

[d4rken]

Thanks for diving deeper into this.

I just noticed these lines at the end:

Good idea, but these lines just mean that when the ADB hosted process is winding down, the logging module that writes to the file is removed. This does not remove the log file only the code that writes to it.

sdmaid-se/app-common/src/main/java/eu/darken/sdmse/common/debug/logging/FileLogger.kt

Lines 42 to 48 in b8a7de1

	} catch (e: IOException) {
	Log.e(TAG, "Log writer failed to start", e)
	e.printStackTrace()
	logFile.delete()
	if (logWriter != null) logWriter!!.close()
	}

There is some code that deletes the log file if it fails writing to it, but then I would expect it to not work in any case.

My current assumption would be that when pressing the general "clear all", SD Maid uses Shizuku + the system call for "trim caches" to clear space. This is only executed when pressing "clear all", because SD Maid can't influence which apps get their cache cleared like this. Possibly, SD Maid is clearing its own cache... (which contains the debug log). Maybe we should move them 🤔

[d4rken]

Regarding the ACS based cache deletion, SD Maid finds the correct entry, but fails to click anything because no entry is marked clickable=true 🤔

-------7: text='null', class=androidx.compose.ui.viewinterop.ViewFactoryHolder, clickable=false, checkable=false enabled=true, id=null pkg=com.android.settings, identity=66ceb0c, bounds=Rect(0, 1133 - 720, 1237)
--------8: text='null', class=android.widget.LinearLayout, clickable=false, checkable=false enabled=true, id=com.android.settings:id/coui_preference pkg=com.android.settings, identity=6638064, bounds=Rect(0, 1133 - 720, 1237)
---------9: text='null', class=android.widget.RelativeLayout, clickable=false, checkable=false enabled=true, id=null pkg=com.android.settings, identity=52fe782, bounds=Rect(51, 1133 - 593, 1234)
----------10: text='Storage & cache', class=android.widget.TextView, clickable=false, checkable=false enabled=true, id=android:id/title pkg=com.android.settings, identity=a0a3ed0, bounds=Rect(51, 1149 - 593, 1185)
----------10: text='589 MB used in Internal storage', class=android.widget.TextView, clickable=false, checkable=false enabled=true, id=android:id/summary pkg=com.android.settings, identity=e7b5e93, bounds=Rect(51, 1188 - 593, 1218)

I assume, you can manually click that storage entry if you try it?

Maybe this is similar to this HyperOS issue where they designed the UI in an accessibility unfriendly way. There was an element that had to be clicked, but was not marked as clickable either. ☹️

Fixed that in #1544 by having SD Maid "manually" create the click gesture instead of using the system provided click action. We could do the same here, but this would make it much slower, especially if animations are involved. The manual gesture has to be put at the right coordinates when clicking, while the click action just works on a target.

Can you show me a video of you manually clearing the cache for an app? I want to see how many animations there are and if it would be easy to place a "click" at the right coordinates 🤔