ubuntu-phone team mailing list archive

[ubuntu.mexon@xxxxxxxxxxxxxxx]

I have progress to report!  Both ADB and MTP work somewhat better on my 
iMac at work (21.5-inch, Late 2013.  My Macbook is Mid-2010. Both 
running El Capitan.)

The results are quite confusing.  I can consistently use Android File 
Transfer, it pops up automatically every time I plug in the phone.  I 
can transfer photos no problem.

adb devices was working for a while, and I could even use adb shell.  
Then it dropped out.  Replugging allowed me to see adb devices again for 
a while, but now replugging is doing nothing for me.  I would guess that 
rebooting the computer would get it working again but I don't have time 
to do that.  adb version is 1.0.32.  I have developer mode enabled 
throughout this.

None of this is qualitatively different to what I get on my Macbook or 
the Raspberry Pi.  It's just that the iMac drops out rather less often.

I can't really use the computer at work to reflash my phone, and anyway 
if the connection is going to drop out I'd be extremely nervous about 
accidentally bricking the device.  I will be getting a new Macbook Pro 
soon so I can test with that, perhaps that will be reliable enough.  But 
it's all pretty worrying.

On 2016-04-11 23:59, Ondrej Kubik wrote:
> for MTP on Mac you should be able to use Android tools from Android 
> SDK. It used to bundle mtp client.
>
> // Ondra
>
> On Mon, Apr 11, 2016 at 2:00 PM, <ubuntu.mexon@xxxxxxxxxxxxxxx 
> <mailto:ubuntu.mexon@xxxxxxxxxxxxxxx>> wrote:
>
>     On 2016-04-11 17:37 , Ondrej Kubik wrote:
>     > 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.
>     >
>     >