I have MyphoneExplorer client 3.10 on both of my identical phones (Samsung A15 on Android 14, UI 6.1) and all has been OK. I have been a happy user of MPE since 2013.
Today on one phone when I tried to open MyphoneExplorer, nothing happened then I get an error message saying 'MyphoneExplorer Client keeps stopping'. I cannot get into the app at all to allow me to sync with my PC.
I have uninstalled, reinstalled, restarted the phone, deleted data/cache, reinstalled repeatedly and it still will not work.
When I do a reinstall and first run, the app asks me to grant all of the usual permissions, which I allow, but then crashes.
My other Samsung phone is identical, but MPE v3.10 client works OK on that one.
There have been no other updates on my phone (no OS or app updates).
I am at a complete loss as to what to do. NO I DO NOT WANT TO DO A FACTORY RESET.
I wonder if anyone else has seen this problem.
Thanks for looking, Steve
'MyphoneExplorer Client keeps stopping' v3.10 on Android 14
Many thanks for report. I already fixed the issue and i hope the Google Play Store will publish soon. If you do not want to wait then you can install the current beta of the client manually: https://www.fjsoft.at/mpeclient.apk
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.
Bitte benutzt auch die Forum-Suche bzw. die FAQ
Bitte benutzt auch die Forum-Suche bzw. die FAQ
Same issue, I already tried uninstalling and reinstalling. Can you provide instructions on how to load the Beta? TIAFJ hat geschrieben:Many thanks for report. I already fixed the issue and i hope the Google Play Store will publish soon. If you do not want to wait then you can install the current beta of the client manually: https://www.fjsoft.at/mpeclient.apk
This fix is working, but needs additional cleanup first...
I was experiencing the same issue, and Uninstalling/Reinstalling/Clear cache/etc. via the Play Store did not help, since (as is mentioned here) the APK file on the Play Store has not yet been updated with the fixed code.
To apply the fix manually, open any browser to the URL provided, and go to that page; this should trigger a download of the file "mpeclient.apk". Once the download is complete, Open the APK file. My DuckDuckGo browser then requested a setting change to be allowed to install the downloaded APK file. (This is a security setting to prevent apps from being installed from any random source, and you should disable it when you are done.)
In my case, first opening the APK file resulted in a message that the app was "updating", after which the sync failure still occurred. (This failed twice.) After uninstalling the MPE Client via the Play Store, I again opened the APK file, and the message stated the app was being "installed". With this message, and enabling all permissions, I am now successfully syncing again.
Note about permissions: Keep an eye out during your first sync, as the calendar/contacts/etc. permission requests will not occur until you perform a sync that includes those.
How was this sync error introduced, and why does it seem to only impact some devices?
P.S. Don't forget: Once the fix is published in the Play Store, you will need to go back and uninstall/reinstall the Play Store version of the MPE Client in order to get back into the cycle of automatic Play Store updates.
Update: My original comment on the Play Store is now displayed above in italics and blue. After Herr Koelner's comment, I checked the Play Store and I see that the MPE Client is in fact listed as having been installed via the Play Store, so he is correct. I was expecting it not to be listed that way. Clearly, there is perhaps a newer interaction between the APK file and the Play Store which I have not seen in my various manual applications of APK files in the past.
Update: Coming back to perform another sync, I now see there are multiple versions of both Note and Calendar entries which had been modified prior to my post-fix successful sync, so there is something else going on with MPE Client that needs consideration. This could be an artifact of the previous bug, or something else, but please look closely at your data to ensure it is correct.
To apply the fix manually, open any browser to the URL provided, and go to that page; this should trigger a download of the file "mpeclient.apk". Once the download is complete, Open the APK file. My DuckDuckGo browser then requested a setting change to be allowed to install the downloaded APK file. (This is a security setting to prevent apps from being installed from any random source, and you should disable it when you are done.)
In my case, first opening the APK file resulted in a message that the app was "updating", after which the sync failure still occurred. (This failed twice.) After uninstalling the MPE Client via the Play Store, I again opened the APK file, and the message stated the app was being "installed". With this message, and enabling all permissions, I am now successfully syncing again.
Note about permissions: Keep an eye out during your first sync, as the calendar/contacts/etc. permission requests will not occur until you perform a sync that includes those.
How was this sync error introduced, and why does it seem to only impact some devices?
P.S. Don't forget: Once the fix is published in the Play Store, you will need to go back and uninstall/reinstall the Play Store version of the MPE Client in order to get back into the cycle of automatic Play Store updates.
Update: My original comment on the Play Store is now displayed above in italics and blue. After Herr Koelner's comment, I checked the Play Store and I see that the MPE Client is in fact listed as having been installed via the Play Store, so he is correct. I was expecting it not to be listed that way. Clearly, there is perhaps a newer interaction between the APK file and the Play Store which I have not seen in my various manual applications of APK files in the past.
Update: Coming back to perform another sync, I now see there are multiple versions of both Note and Calendar entries which had been modified prior to my post-fix successful sync, so there is something else going on with MPE Client that needs consideration. This could be an artifact of the previous bug, or something else, but please look closely at your data to ensure it is correct.
Zuletzt geändert von RayParker am Di 23. Jul 2024, 02:49, insgesamt 1-mal geändert.
...Ray
Re: This fix is working, but needs additional cleanup first.
No, there is no need for that.RayParker hat geschrieben:P.S. Don't forget: Once the fix is published in the Play Store, you will need to go back and uninstall/reinstall the Play Store version of the MPE Client in order to get back into the cycle of automatic Play Store updates.
Nur Geduld! Mit der Zeit wird aus Gras Milch.
The downloaded version works. I have 2 Samsung phones A55 - Android 14, UI 6.1 (not working) & A7 2018 - Android 10 (working from Google play installation). I've uninstalled and re-installed using the version (V3.10 beta3) from this site. Thx for the fix!!......Luckily this is not like CrowdStrike....FJ hat geschrieben:Many thanks for report. I already fixed the issue and i hope the Google Play Store will publish soon. If you do not want to wait then you can install the current beta of the client manually: https://www.fjsoft.at/mpeclient.apk