Hi :) On Thu, Jul 2, 2015 at 10:00 PM, Oliver Grawert <[email protected]> wrote: > Am Donnerstag, den 02.07.2015, 20:20 +0300 schrieb Juhapekka Piiroinen: >> Hi, >> >> Issue 1: >> I have ran all the recent updates for the MX4 via the UI. It looks >> like that even few reboots and enabling the developer mode etc, I am >> unable to connect to the device via adb. Is this some kind of known issue? >> I can see that the adbd is running on the MX4 via the terminal app. > > do you use the phablet-tools PPA and specifically the android-tools-adb > and libmtp packages from there ? i think older libmtp and android-tools > versions (i.e. from the archive) might be missing the MX4 bits. >
I think that this might be the case, at least I did not find any mention/line for the MX from usb_vendors.c file from the android-tools-4.2.2+git20130218. This was the source package from the phablet-tools PPA for trusty (14.04 LTS). One thing is also what I am seeing that the lsusb does not contain any string identifier. <lsusb line for mx4> Bus 001 Device 017: ID 2a45:0c02 </lsusb> I have managed to see the MX4 on vivid (15.04) vmware image once with adb, last week, while I gave a quick test with it. With that image I think that I was using a slower usb emulation as well, instead of the USB 3.0 which I have on this native installation. I tried to patch that usb_vendors.c file with the usb vendor id, but it looks like that it did not either work, but I am sure that it is still part of the solution. I somewhat managed to send the original email twice for the mailing list, and in the other thread it was suggested that part of the solution is to find a different usb hub etc. Cheers, JP -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
