You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently trying to troubleshoot installation issues with an application and would like to access /storage/emulated/0/Android/data/, however its contents seem to be cached by libmtp or gvfs because the file explorer (desktop PC) and the terminal report the same, outdated, directory layout.
Desktop OS: Ubuntu 22.04 (LTS)
libmtp version: 1.1.19 (there is no mention of "cache" in newer release notes, thus I did not recompile a newer version)
gvfs version: 1.48.2
Mobile OS: Android 6.0
Are there any configuration options that I could change or cache file to delete? I did reconnect the phone a few times (by software and physically) and restarted gvfs-mtp-volume-monitor without any progress. Any help is greatly appreciated.
EDIT: To clarify: /storage/emulated/0/ and its immediate child directories are not affected. Even though capturing a new image requires re-mounting, it does show the correct contents afterwards. Hence this must be a different issue (due to permissions, perhaps?)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I am currently trying to troubleshoot installation issues with an application and would like to access
/storage/emulated/0/Android/data/, however its contents seem to be cached by libmtp or gvfs because the file explorer (desktop PC) and the terminal report the same, outdated, directory layout.Are there any configuration options that I could change or cache file to delete? I did reconnect the phone a few times (by software and physically) and restarted
gvfs-mtp-volume-monitorwithout any progress. Any help is greatly appreciated.EDIT: To clarify:
/storage/emulated/0/and its immediate child directories are not affected. Even though capturing a new image requires re-mounting, it does show the correct contents afterwards. Hence this must be a different issue (due to permissions, perhaps?)The text was updated successfully, but these errors were encountered: