3 ms·

There is an alternative if you have the android sdk running on your laptop. Use adb to forward a port from your machine to your Android device. Run a SOCKS pro

There is an alternative if you have the android sdk running on your laptop. Use adb to forward a port from your machine to your Android device. Run a SOCKS proxy app on your Android. http://graha.ms/androidproxy/ http://graha.ms/androidproxy/ I use a similar method for transferring media, since mtp doesn't work very well on Linux. I wonder why did Google decide to implement mtp as the protocol of choice. I know why MSC was not ideal anymore, but it already has working tcp over usb. That can be used to implement so many different things like file sync, tethering, etc.

rogerbinns 14y ago
> I wonder why did Google decide to implement mtp as the protocol of choice They presumably had iTunes in mind as the competition, MTP is a "standard" and many apps already implemented it. Of course it turned out to be 4 steps forward and one step back.
- sandGorgon 14y ago
  Actually iTunes uses tcp over usb[1] . Which is why this is so counterintuitive - adb already does everything on tcp over usb, why didn't they just use it for everything. I hope it is not patent encumbered - I'm hoping at least Cyanogenmod can implement it. [1] rant warning -http://sandeep.wordpress.com/2012/10/15/the-fastest-way-to-transfer-files-on-a-one-xs-or-samsung-s3-why-mtp-sucks-and-a-note-to-google-engineers/ http://sandeep.wordpress.com/2012/10/15/the-fastest-way-to-t...
  - rogerbinns 14y ago
    Apologies for not being clear - I meant iTunes' functionality (sync collections of media) not implementation. Presumably Google thought it would be a neat shortcut using MTP since others would then write the media sync functionality (eg Media Monkey, Double Twist). It was a good short term choice, but a bad one for the long term. And there is nothing stopping them adding a TCP based sync later. You'll note however that they prefer you sync to the cloud and then Google handles cloud to your device rather going direct from local machines to the device. See Google Music etc. Thanks for the rant!

rogerbinns 14y ago

> I wonder why did Google decide to implement mtp as the protocol of choice They presumably had iTunes in mind as the competition, MTP is a "standard" and many apps already implemented it. Of course it turned out to be 4 steps forward and one step back.

sandGorgon 14y ago
Actually iTunes uses tcp over usb[1] . Which is why this is so counterintuitive - adb already does everything on tcp over usb, why didn't they just use it for everything. I hope it is not patent encumbered - I'm hoping at least Cyanogenmod can implement it. [1] rant warning -http://sandeep.wordpress.com/2012/10/15/the-fastest-way-to-transfer-files-on-a-one-xs-or-samsung-s3-why-mtp-sucks-and-a-note-to-google-engineers/ http://sandeep.wordpress.com/2012/10/15/the-fastest-way-to-t...
- rogerbinns 14y ago
  Apologies for not being clear - I meant iTunes' functionality (sync collections of media) not implementation. Presumably Google thought it would be a neat shortcut using MTP since others would then write the media sync functionality (eg Media Monkey, Double Twist). It was a good short term choice, but a bad one for the long term. And there is nothing stopping them adding a TCP based sync later. You'll note however that they prefer you sync to the cloud and then Google handles cloud to your device rather going direct from local machines to the device. See Google Music etc. Thanks for the rant!