What Android 3.1 DIDN'T Fix!

Berzerker7

Senior Member
Jan 17, 2010
847
257
0
Its not a debate. Its a known fact that its a Google issue. Any other manuf that has sdcard support are just hacked in.

Sent from my Xoom using Tapatalk
 

chbennett

Senior Member
Feb 5, 2011
270
11
0
Portland
Still no sdcard slot!
Still no USB On-The-Go memory device support (we have USB joystick support but still no memory devices)

I haven't tried abusing the Camera Connection Kit yet to see if I can use a camera as a memory card reader.
Look around the forums. These problems have been solved.

Sent from my Xoom the way it should be, rooted and with SD card.
 

Wiggz

Senior Member
Aug 1, 2006
591
21
0
Look around the forums. These problems have been solved.

Sent from my Xoom the way it should be, rooted and with SD card.
Apologies up front but - Absolute rubbish!. The problems have not been solved at all. They have simply been worked around.

As far as I know the SD-Card requires a completed non-stock kernel, root and some adb pushing!
 

kennych

New member
Mar 9, 2011
2
0
0
Denver, CO
Apologies up front but - Absolute rubbish!. The problems have not been solved at all. They have simply been worked around.

As far as I know the SD-Card requires a completed non-stock kernel, root and some adb pushing!
Exactly. The issues with the stock/standard Xoom are far from "solved."

I want my SD Card to work.
 

JayBomb999

Senior Member
Jan 10, 2010
70
13
0
I agree that MTP is pretty unreliable on Linux at the moment. Also, I can see how MTP would be an improvement for the Windows using masses. It just isn't for me. One of the things I love(d) about Android is it's simple compatibility with with my operating system of choice.

Allow me to get back to the topic of this thread: "What Android 3.1 DIDN'T Fix". I can confirm that the laggy, low framerates are still present when using the Xoom in any orientation other than the default/normal landscape position (Camera up, HDMI down).

Romain Guy suggested in one of his Google IO talks that they are aware of this issue an that it might be fixed in 3.1. Well, it's not. :-/
 

stevebakh

Member
Apr 30, 2011
24
2
0
You're right, it's a cross-platform solution for transferring MEDIA, being the Media Transfer Protocol.

It's smart enough to detect the media files that it supports and put them in the right place. I prefer it over the old way, I hated having to unmount the sdcard every single time.

A poorly made Linux MTP library doesn't make it not cross-platform. It's an open standard for transferring media to USB devices.

It's not perfect, but it's great for a device like the Xoom where unmounting the internal memory is not desirable.

Honestly users get really confused by all of the extra directories when mounting an android sd-card anyways.
I don't mean to start a massive argument or anything, but in this instance, you're wrong. It is an open protocol, sure, but it's not cross platform. The distinction needs to be made.

I could list a ton of free, useful and open protocols that aren't cross-platform because they haven't been implemented (fully, or at all) on all three major systems (osx, windows & linux).

As I already pointed out, I clearly understand Google's reasons for switching to MTP, but I don't think they should be claiming that it's a cross platform solution. I could cheat the system and zip my files, or rename the file extension, but I shouldn't be required to. At the moment, MTP simply isn't cross-platform and I can't really use it get my files on the XOOM without having to jump through hoops. When/if it ever works properly and the user experience is shared across the three major platforms, then we can call it cross-platform.