Most the problems with adb are caused by the flaky usb on MX4, but could be
others.
1) can you see MTP interface and transfer files to device?
-> no) your USB is flaky, test different port, different USB cable....
-> yes) what adb client (host binary) are you using?
-> one from Google, aka Android studio): make sure you update
~/.android/adb_usb.ini it should contain 0x2a45, without that file, adb
client will ignore any connected device not blessed by Google.
-> one from Ubuntu ppa, you should see device or at least as
"unauthorised device" otherwise make sure you have developer mode enabled.
Using old adb client with new adb daemon should still show you as minimum
unauthorised device.
cheers
// Ondra
On Sun, Apr 10, 2016 at 2:06 AM, <ubuntu.me...@spamgourmet.com> wrote:
> On 2016-04-10 04:39 , Sergio Schvezov wrote:
> >
> > Using adb is the most depressing thing from the mx4. I only started to
> > noticed after I got a new laptop; on usb2 ports it is not as noticeable.
> >
> Is this a software problem or a hardware problem? I don't even know how
> it's possible for a phone manufacturer to get their USB port
> implementation wrong, it's all in the SoC surely?
>
> If it's a firmware problem I can understand. I'm learning a lot about
> the quality of Android phone manufacturers' design decisions, and I'm
> not learning anything that makes me happy.
>
> If it's a system software problem... any chance of getting it fixed?
>
> BTW my Macbook is a 2010 model and doesn't hold with any of this
> new-fangled USB 3 nonsense. My Raspberry Pi is a Raspberry Pi and is
> definitely USB 2 only.
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help : https://help.launchpad.net/ListHelp
>
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
