Existing phone connection stopped working for no reason

[icke1954]

There was no AndroidDebug.txt in %appdata%\MyPhoneExplorer folder...

In your screenshot I see that you did not start MPE in debug mode ('C:Program Files (x86)MyPhoneExplorerMyPhoneExplorer.exe' debug). The AndroidDebug.txt is only created in this mode!

[nocturnal]

In your screenshot I see that you did not start MPE in debug mode ('C:Program Files (x86)MyPhoneExplorerMyPhoneExplorer.exe' debug). The AndroidDebug.txt is only created in this mode!

Re-tested and emailed both files.

[FJ]

Really strange logs. You made everything right but the client on the phone did not launch in debugging mode, so no relevant info in the AndroidDebug.txt. Please install the current beta of the client on the phone - tbhis is in debugging mode all the time: https://www.fjsoft.at/mpeclient.apk
Also install the current beta of MyPhoneExplorer on the PC. There were no changes in the connection management but its always better to have the same code base: https://www.fjsoft.at/files/MyPhoneExpl ... Update.exe

The logs are also difffrent in the log of the 27th march the connectrion was etablished but MyPhoneExplorer was not able ti receive any data from the client. In the new logfile the connection channel could not be set up

When you open MyPhoneExplorer Client on the phone you see the WiFi IP of the phone. What happens when you send a ping-Command to the WiFi IP of the phone? Do you get answer?

[nocturnal]

New debug logs emailed. Used both Windows and Android debug app versions in testing.

Here is the answer to your question:


C:\Users\<REDACTED>>ping 192.168.1.252

Pinging 192.168.1.252 with 32 bytes of data:
Reply from 192.168.1.252: bytes=32 time=96ms TTL=64
Reply from 192.168.1.252: bytes=32 time=15ms TTL=64
Reply from 192.168.1.252: bytes=32 time=28ms TTL=64
Reply from 192.168.1.252: bytes=32 time=7ms TTL=64

Ping statistics for 192.168.1.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 96ms, Average = 36ms

[nocturnal]

I was forced to switch to using another sync software, because I needed to sync my contacts, and no solution here for a long time, but would still prefer if MPE worked properly, as a backup option.

Any update, or is this never getting resolved? I've collected and provided all the debug logs 2 weeks ago...

My personal opinion is that MPE code needs to be changed to NOT require phone device model inquiry to be successful, in order to establish connection. Chinese phones like Vivo, with built-in intrusive and overbearing Security app, can easily be blocking access to some internal functions, such as query for phone's model.

This limitation should be bypassed in MPE code.

[FJ]

Its not a limitation inside MyPhoneExplorer. According to the logfiles MyPhoneExplorer is able to open the communication channel to the phone and he is also able to send a request but he never gets a answer. The next steps would be to check the behaviour with another PC and if possible i another LAN.

[nocturnal]

Another PC was already tried earlier, per your request. The result was the same. LAN has nothing to do with this, because this error described in the OP occurs using all 3 supported connection types: BT, WiFi and USB.

[nocturnal]

I thought I'd give this thread one last shot and ask for an update, before I move off MPE permanently.

[nocturnal]

Just for the record - I saw there was July 14th latest MPE update. I installed it and tested the sync again - this update did NOT fix the issue. MPE still throws the same phone identification error. Tried all 3 connection methods again.

[icke1954]

Another PC was already tried earlier, per your request. The result was the same. LAN has nothing to do with this, because this error described in the OP occurs using all 3 supported connection types: BT, WiFi and USB.

If, for whatever reason, MPE doesn't have full access to your phone (what phone is that anyway?), it's going to be difficult.
Do you have a security app installed on your phone?

[nocturnal]

Phone model is already stated in the OP. I do not have additional security apps installed, but there is a built-in Security app, which is part of the OriginOS. It cannot be turned off or uninstalled.

On the phone MPE client during the connection attempt, briefly says "Connected" on top, then it disconnects very quickly and then that "phone cannot be identified" error appears on PC screen from MPE desktop app, screenshots for which I provided in earlier posts.

I dont beleive your assumption that "MPE cannot get access to phone" is correct. My personal impression is that MPE queries the phone for it's model/version, and/or whatever other info it needs, but then fails to parse the response, because the response is either in unknown format, or no response from phone at all, or it's in Chinese language.

[icke1954]

I dont beleive your assumption that "MPE cannot get access to phone" is correct. My personal impression is that MPE queries the phone for it's model/version, and/or whatever other info it needs, but then fails to parse the response, because the response is either in unknown format, or no response from phone at all, or it's in Chinese language.

Assuming you're right, then FJ would have to completely rewrite the MPE registration for you, because somehow the connected Android devices have to be identified?!
I'll ask FJ again about this, I can't promise you anything

[nocturnal]

Vivo is top 4 Chinese phone brand. There are hundreds of millions of Vivo phones out there, most of them are Android based. While I'd appreciate a solution that helps me personally - this fix would hardly be just for me...

It's not unreasonable to assume other Chinese brands, which use similar Android skins as Vivo's OriginOS, could be affected as well. Huawei, Xiaomi, Oppo, etc. do have similar security features. The fact that no one has reported issues with other Chinese phone brands on this forum does not mean MPE is working without issues on those phones.

[FJ]

Normally this message gets thrown when MyPhoneExplorer is not able to read the registration ID of the phone because a permission issue. Its the first command when the connection is etablished to the phone. In your case - i did already check your logs in the past - there is NO answer at all, also not an error answer.

I dont think that this issue will affect all Vivo phones, especially because i never had a support request from a user with exactly this problem.

As i said also in the past:
- i need access to the logcat of the phone, otherwise i am not able to help you

Please install the current beta of the client on the phone - this is in debugging mode all the time: https://www.fjsoft.at/mpeclient.apk

- were you able to try the behaviour in another LAN on another PC?

[nocturnal]

Normally this message gets thrown when MyPhoneExplorer is not able to read the registration ID of the phone because a permission issue. Its the first command when the connection is etablished to the phone. In your case - i did already check your logs in the past - there is NO answer at all, also not an error answer.

I dont think that this issue will affect all Vivo phones, especially because i never had a support request from a user with exactly this problem.

As i said also in the past:
- i need access to the logcat of the phone, otherwise i am not able to help you

Please install the current beta of the client on the phone - this is in debugging mode all the time: https://www.fjsoft.at/mpeclient.apk

- were you able to try the behaviour in another LAN on another PC?

I have installed the debug always on client per your request long ago.

What does LAN have to do with anything? MPE does not use Ethernet connections, and phones dont have RJ45 ports. Did you mean another WAN? If so - No. First because I only have 1 home and 1 home network, and second because no PCs on another WAN would have Outlook with my contacts pre-installed, so there would be nothing to synchronize the phone to. For that same reason I have not tried another PC - the Desktop version of Outlook I use with all my contacts is installed on 1 PC only, and my phone contacts are synchronized only to that contacts database.

As for the logcat - I dont recall you asking for it. I suppose I could email it to you - just let me know what kind of test you want me to run first, so it would be reflected in the logcat.

Previously you only wanted to remote into my PC, which I explained to you was not a possiblity I would ever consider. I said then I'm available to work with you on this any other way, except giving you access to my computer. That still holds true.

If you're suggesting this issue affects my Vivo phone only - that's highly unlikely, because my phone is not even rooted and has locked bootloader, meaning no system settings customized in any significant way, and it's running stock Vivo firmware - same version installed on millions other Vivo X Folds sold. There is no valid reason to think this issue is specific to my phone only. As I mentioned earlier - just because no one took the time to report it here, like I have, does not mean other Vivo phones aren't affected.

[FJ]

LAN = Local Area Network . This contains Ethernet connections and also WiFi connections. MyPhoneExplorer uses this connection
WAN = Wide Area Network. This is the connection between your router and your internet provider, this has nothing to do with MyPhoneExplorer

I have the emails from our older conversion and i asked you for the Logcat, but i can explain it again:
- run MyPhoneExplorer in debugmode: Win-Key+R -> myphoneexplorer debug -> OK
- try to connect via USB-Cable (USB-Debugging has to be enabled on the phone)
- open the datafolder of MyPhoneExplorer: Win-Key+R -> %appdata%\MyPhoneExplorer -> OK
- send me the files Debug.txt and also the file AndroidDebug.txt

But probably it saves alot of time if you try the establish the WiFi connection first on another LAN (maybe your neighbor or buddy) and to try it on another PC. This makes it easier to locate the problem - technically it can be the PC, the Router and also the phone.

[nocturnal]

Installed MPE on another Windows PC on the home network and tried to add user - same result, same message.

I do not have the kind of buddy or neighbor, where I could go to their home, ask to install your software on their personal computers and ask them to let me run tests on their personal PCs.

As for the instructions in the previous message to collect Debug.txt and AndroidDebug.txt - we have done this exercise already. I distinctly remember emailing you the logs. You looked at them and called them really strange.

If you want me to collect the exact same logs again please let me know, but as Einstein said - doing the exact same thing and expecting different results is the definition of insanity. I haven't changed any configuration on either the PC or the phone, so you'll almost certainly see the same information you already saw in previous logs.

There has to be something more you can do/try, other than ask me for the same logs again and test on different PCs, which I have already done... Like creating another debug apk, which generates more debug output for phone connection/registration process.

[FJ]

You could allow me to make a TeamViewer session but since you don't want this too i don't have better ways to evaluate the issue.

[nocturnal]

You could allow me to make a TeamViewer session but since you don't want this too i don't have better ways to evaluate the issue.

Respectfully, as a software engineer myself, I strongly disagree with your assessment that you "don't have better ways to evaluate the issue". Giving a user an ultimatum to connect and access his personal PC, and primary computer at that, which contains tons of sensitive personal, and confidential business information would violate my privacy and personal security, and every software development company or individual in the world (besides you, apparently) has alternative ways to troubleshoot customer issue, other than ultimatums to access their personal PCs and home networks.

I'll take it as your final refusal to fix a defect with your software - for all intents and purposes that's what your ultimatum really is.

[Koelner]

FJ has been trying to find a solution to your problem for almost five months now.
And after carefully reading everything in this thread, I have to say that I find it really insulting that you are talking about an ultimatum, especially since it is not even certain yet that it is really a bug in the MPE software.
You should perhaps be clear about what you are asking for here and from whom. FJ is not a tech company, he is a private person who has written good software and is making it available for free. So please spare us your digital d**k comparison and your babble about data security. If your data is oh so sensitive, then maybe you should buy software that meets your high standards. But to demand that the MPE be rewritten especially for you is simply ridiculous.
I'm assuming that English is not your first language, so my well-intentioned advice is to think about how your demands will be received here, especially in the context of MPE and its many satisfied users.
Over the years a number of people have tried to put a gun to FJ's head and none have ever succeeded.
So you can jump over your shadow and work with FJ to find a solution or try to be an a*hole.

So, this little rant had to be done.