To successfully connect to my Note 5, I have to:
1. Run MGD
2. Try to connect
3. It will show an 'Error' entry in the list of android devices.
4. Quit MGD
5. In Task Manager, adb will start running as soon as MGD quits.
6. Re-run MGD
7. Try to connect again
8. Go to task manager and close the running instance of adb
9. MGD will now show my device properly and allow me to connect.
If I do anything in a different order - if I close adb before re-running MGD, for instance - I keep getting the 'Error' entry in the list of android devices.
Hi Peeling,
Can I get a bit more information about your system because it seems to be very unsual:
1) What version of MGD are you currently using?
2) What OS are you working on: Is it Linux, Windows or Mac? I am guessing Windows as you mentioned the task manager.
3) What version of the Android SDK have you currently installed or what is your adb version?
4) Can you connect to your device without MGD using adb from command line?
Hope this helps,
Stephen
Latest MGD
Windows 10
SDK tools are showing 26.1.1
SDK platform tools are showing as 27.0.1
ADB version returns:
version 1.0.39
Version 0.0.1-4500957
ADB works fine otherwise (Android studio debugging, profiling etc)
EDIT: Also, the above voodoo works on my PC in the office. On my home laptop, nothing works; I can't connect at all.
A similar thing happens though: when I try to search for devices it waits for a bit and then shows an 'error' entry. If I close MGD, ADB starts up immediately as though it was blocked waiting for MGD to quit.
EDIT2: //FIXED// Can't seem to win here. Am trying to reinstall the interceptors and the phone just resets every time I try to touch anything in the egl folder, including the libGLES_mgd.so file, either through adb or a root explorer program. //FIXED//
EDIT3: Still no joy connecting via USB. Can now connect via IP address, having successfully updated the 64 bit interceptor (if anyone else struggles with this, deleting the old _mgd.so file before copying across the new one seemed to do the trick)