This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Weird voodoo required to connect MGD

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.

Parents
  • 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

Reply
  • 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

Children