BQ M10 HD adb does not work

Gerben · 24 Jun 2018, 20:36

The BQ Aquaris M10 HD with ubports 16.04/rc has developer mode enabled and is connected with a proper cable to my laptop running Ubuntu 16.04. adb devices does not return the connected device. According to the documentation on https://docs.ubports.com/en/latest/userguide/advanceduse/adb.html I can add the hardware id to ~/.android/adb_usb.ini. Unfortunately I do not know the hardware id of the BQ M10 HD. Does anyone know this hardware id? Or does anyone know how to fetch the hardware id? Is it the USB device id? I tried to add the USB vendor and product id but both do not result in a working adb connection.

$ adb devices
List of devices attached

$ adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

$ lsusb
Bus 001 Device 029: ID 2a47:201d

Marathon2422 · 24 Jun 2018, 20:47

@gerben
Try,
Pc with open terminal
Device on developer,page ( not connected )
Now switch developer mode ON
Next connect device, keep watching screen,you should get a window open,look for ALLOW click on allow.
If you get nothing
Then in terminal sudo adb devices, look for the window with allow.
you get no adb till you get this.

Reboot your device after entering developer mode, and try again from that screen.

Lakotaubp · 24 Jun 2018, 21:03

@marathon2422 I never got the "allow" box on Ubuntu with bq devices. I had to use Linux Mint in the end not sure I even tried on windows.

libremax · 24 Jun 2018, 21:04

May be wrong but would say the value you search for adb is 0x2a47 (idVendor), from
https://ubuntuforums.org/archive/index.php/t-2352688.html
and
https://forums.ubports.com/topic/360/connecting-calibre-to-bq-aquaris-m10-fhd-via-mtp/15

and by comparison with 0x2ae5 for Fairphone 2

Gerben · 24 Jun 2018, 21:04

Thank you for the answer! The reboot after enabling developer mode did the trick. I did not get a window with an allow button though.

advocatux · 24 Jun 2018, 21:08

@gerben that "allow" pop-up only appears the first time you plug your device to your computer using an usb cable. Once you've trusted that device ("allow") that's all.

In your case, if you have plugged that device before, it's trusted then.

Gerben · 24 Jun 2018, 21:19

@libremax
The 'hardware id' for the Fairphone 2 mentioned in the ubports docs matches with their USB vendor id indeed. I still had the 0x2a47 id in the ini file and this might be required for the M10 HD.

I am not sure though. After trying some combinations I find that sometimes it works and sometimes not. So there seems to be something else going on.

Marathon2422 · 24 Jun 2018, 21:26

Glad it came together for you.

I have gone back an forth with my m10 fhd a few times.
Always something different happens

Gerben · 24 Jun 2018, 21:29

@advocatux said in BQ M10 HD adb does not work:

@gerben that "allow" pop-up only appears the first time you plug your device to your computer using an usb cable. Once you've trusted that device ("allow") that's all.

In your case, if you have plugged that device before, it's trusted then.

That could well be the case. I tried it late last night.

Gerben · 24 Jun 2018, 21:42

After just plugging and unplugging I notice that 1 in 5 times I get an ADB connection. MTP seems to always work properly, except for one time when I got an 'Unable to open a folder for Aquaris M10 HD' error. At which time I got an ADB connection. After unmounting MTP I sometimes loose the ADB connection, but not always.

How do ADB and MTP automount play together? Do I need to disable MTP?

ThePossessor · 25 Jun 2018, 20:04

@Gerben Sometimes adb does not work well when you plug the device over a USB hub. If you are using a desktop system you can try to connect directly to an onboard USB port of your PC. (usually at the back of the PC)
This eliminates trouble due to bad cabling or a bad quality USB hub or else due to a missing power supply for the hub.

Gerben · 26 Jun 2018, 16:13

@thepossessor Thank you for the tip. I always connect directly to my laptop without a hub.