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
Speicheranalyse -> Hauptspeicher -> Systemdaten kein zugriff trotz ROOT #917
Comments
Scanning these areas is currently not supported because every phone company sets up their system storage differently. I have not found a way yet to scan it in a way that consistently makes sense to the user. |
Thank you for your answer. Unfortunately I can't quite understand the statement because SD Maid 1 can scan this area and also shows me all folders, subfolders and files. |
SD Maid 1 mostly scans just by path, this does not give an accurate image of occupied storage to the user as multiple paths may share the same storage chip (hardware). SD Maid 2 takes more care to only scan the individual storage chip, to show what data is explicitly on that chip. The storage analyzer is not primarily a file browser, but a way to find out what takes up most space on a specific storage device. So to scan additional areas, I need ways to determine on what storage chip they reside, which is difficult, and something I left as TODO for future me :) |
Ok, now I understand the problem. A very good approach. Then, in my opinion, a "file browser" like in SD maid with display of memory usage would be useful. Since I found a wifi log folder that was filled with 80gb+ which I can delete with my own filter. |
Describe the bug
Kein Zugriff auf Systemdatenordner über die Funktion Speicheranalyse -> Hauptspeicher -> Systemdaten
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Hier sollten wie in der ersten Version von Sd Maid die Unterordner aufgerufen werden.
Smartphone (please complete the following information):
Debug log
If you can reproduce the bug, record the event in a debug log.
Screenshots/Video
If applicable, add screenshots or a video if it helps to explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: