OpenMTP not working with Sonoma 14.6.1

[meerestier]

OpenMTP not working with Sonoma 14.6.1

This issue is related to many others having trouble connecting to Android devices with the latest Sonoma 14.6.1 release.
Is there a solution? I Am having trouble with android based drones (DJI Mavic 3)

[ganeshrvel]

Could you check the steps mentioned in this thread to see if doing them fixes your connectivity issue?

#276

[Abhaykumar2021]

OpenMTP not working with Sonoma 14.6.1

This issue is related to many others having trouble connecting to Android devices with the latest Sonoma 14.6.1 release. Is there a solution? I Am having trouble with android based drones (DJI Mavic 3)

Same

[meerestier]

Could you check the steps mentioned in this thread to see if doing them fixes your connectivity issue?

#276

None of the steps helps…

[Abhaykumar2021]

Now It's working for my Samsung phone

[nickhydeviolin]

I upgraded to 14.6 recently and it seems this no longer works for me. Both a Pixel 3 and a Pixel 5 can't connect - both get "error while setting up the phone". I've tried everything - nothing in #276 works, I've made sure and searched hard for anything that's taking over the USB ports, etc. I noticed that both show up as "internal shared storage" in Disk Utility now. I'm not sure if they did before, I don't think so?

[juddmod2]

I'm having the same problem with Sonoma 14.5 and a Pixel 6. In the past I could get the connection to work by repeatedly restarting computer, reinstalling OpenMTP, and restarting phone---a pain in the neck, but it did eventually work. Today I've been trying that for nearly an hour with no success. Always "Android device is either busy or not connected".

[ganeshrvel]

I’m not sure why this is happening. I’ll take a look at it.

[juddmod2]

Thank you.

[ganeshrvel]

Hey everyone, I've got some interesting updates to share about my MTP testing.

So, I've been working with a Pixel 8 phone and running macOS 14.6 Sonoma on my MacBook. OpenMTP was able to detect and work fine with the Pixel 8. But here's where it gets interesting...

I've been developing a new MTP implementation in Rust (part of a complete rewrite of OpenMTP for better performance), and I ran it through a comprehensive test suite - we're talking over 1500 tests. The results were, well, pretty disturbing when it came to the Pixel.

Here's the thing: I always thought Samsung devices were the ones deviating from MTP standards. I had to make quite a few compromises in the MTP implementation to get things working smoothly on Samsung phones. But the Pixel? It's completely changed my perspective.

The Pixel's internal MTP server is incredibly unstable under these tests. It's slow to process MTP requests, throws inconsistent data transfer errors, and sometimes just gives really strange errors. Some MTP functions work on the Pixel, and then suddenly they don't. It's all over the place.

The irony is, once I fixed all the MTP incompatibility issues for Samsung, those devices passed the tests with flying colors. They're running smooth as butter now.

I'm still digging into why this is happening with the Pixel. It's like it's living in its own little MTP world, and it's definitely not playing nice with standard implementations.

I'll keep investigating and let you all know what I find. If anyone has had similar experiences with Pixel devices and MTP, do let me know.

[juddmod2]

FWIW, OpenMTP was able to detect my Pixel 6 after I restarted the Pixel in safe mode.