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

android: settings' storage usage != system's storage usage #2149

Closed
bassosimone opened this issue Jun 14, 2022 · 0 comments · Fixed by ooni/probe-android#528
Closed

android: settings' storage usage != system's storage usage #2149

bassosimone opened this issue Jun 14, 2022 · 0 comments · Fixed by ooni/probe-android#528
Assignees
Labels
bug Something isn't working needs investigation This issue needs extra data and investigation ooni/probe-mobile issues related to OONI Probe mobile platform/android priority/low

Comments

@bassosimone
Copy link
Member

I just noticed that the storage usage according to the OONI settings does not match the storage usage according to the Android system settings. In my test case, OONI says it's using 5 MiB of storage, while Android says it's using 19 MiB.

We should investigate why that is the case, and whether we could improve out estimate. I am also wondering whether we should not report the storage we think we are using and let the system do this job (which probably it does better than us).

Another possible fix could be to say that the number we report on is just the database size (which is what we're reporting according to https://github.com/ooni/probe-android/blob/master/app/src/main/java/org/openobservatory/ooniprobe/model/database/Measurement.java#L205). Even just a change in the copy would be an improvement, I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs investigation This issue needs extra data and investigation ooni/probe-mobile issues related to OONI Probe mobile platform/android priority/low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants