Hi,
I saw the previous question about root access and your explanation. I'd like to add some context from my own investigation.
When I first launched the app on my rooted device (custom ROM, Android 12.1, Magisk), Magisk showed a root grant dialog for Safe Space. Not knowing this was just a detection routine, I ran a strace session to check what the app was actually doing with root.
The trace confirmed your explanation: the app runs su with no arguments, cycling through common paths until it finds one - a standard root detection pattern. After that, no privileged file operations were observed. The app only accessed its own internal storage directories, as expected.
Just a suggestion: it might be worth adding a short note to the README along the lines of - "On rooted devices, your root manager may show a permission dialog. This is caused by the root detection check and the app does not actually require or use root access." This would save other users the same confusion.
Thanks for the app.
Hi,
I saw the previous question about root access and your explanation. I'd like to add some context from my own investigation.
When I first launched the app on my rooted device (custom ROM, Android 12.1, Magisk), Magisk showed a root grant dialog for Safe Space. Not knowing this was just a detection routine, I ran a strace session to check what the app was actually doing with root.
The trace confirmed your explanation: the app runs
suwith no arguments, cycling through common paths until it finds one - a standard root detection pattern. After that, no privileged file operations were observed. The app only accessed its own internal storage directories, as expected.Just a suggestion: it might be worth adding a short note to the README along the lines of - "On rooted devices, your root manager may show a permission dialog. This is caused by the root detection check and the app does not actually require or use root access." This would save other users the same confusion.
Thanks for the app.