Seite 1 von 1

[Solved] Can't access files on the phone after recent update

Verfasst: Do 22. Jun 2023, 18:47
von Novgorod
After an update of the Android app within the past few weeks, the phone's files are not shown in MPE anymore. It shows the "internal storage" root folder but the file window is empty. I tried both Wifi and USB connection with the same results; the Android app has all permissions enabled and the screen is unlocked. I also tried removing the phone profile in the Windows app and linking it again with the QR code, still no file access. I can see the phone stats under "Monitor" and can access SMS and calendar; contacts only show up over USB and files not at all.

The phone is a Samsung Galaxy S22 Ultra (Android 13, internal storage only). File access worked fine last time I used it (some weeks ago) and the only change was an update to the Android app (3.0). I also tried the nightly build of the Windows app (22-Jun-23) with the same results. I saw someone had an issue accessing the data folder, but in my case no files are shown at all.

I use MPE primarily for file transfer over Wifi because it's by far the best app for that, so it's quite a bummer if that's now broken.

Verfasst: Mo 26. Jun 2023, 20:14
von FJ
This issue was known for MyPhoneExplorer Client 2.8 und 2.9 in combination with Android 10 but it was fixed with Version 3.0
Did you enable the special permission "All file access" in the app list?
Maybe the best choice is to uninstall MyPhoneExplorer Client and then install it again from Store so that you are able to commit all permissions on the first launch

Verfasst: Di 27. Jun 2023, 06:10
von Novgorod
FJ hat geschrieben:Maybe the best choice is to uninstall MyPhoneExplorer Client and then install it again from Store so that you are able to commit all permissions on the first launch
That was the solution, thanks!

As I said, all permissions were previously enabled including all file access (enabled it manually in the app settings), but it wouldn't show files in the Windows app. Doing the proper first launch procedure after reinstalling the phone app fixed it.