3.2 for Xoom

I hear its being pushed out now to a small set of users. Does anyone know if this includes WiFi and 3G versions?
 
Its coming out today little bit at a time. I'm sure rooted users will see a zip sooner than later.

sent by CyanogenMod X
 
Can somebody please tell me what this is supposed to bring me? If I don't know, I'm not going to be as excited if I get it. :|
 
Can somebody please tell me what this is supposed to bring me? If I don't know, I'm not going to be as excited if I get it. :|

official Google SD card support for Wi-Fi Xooms. Verizon Xoom still hasn't received 3.2, so no news there. Also, ability to stretch apps that are not optimized for honeycomb yet. Official list of features in this update is still not complete given that it pushed out in small batch less than an hour ago.

3.2 makes Xoom the only honeycomb tablet with official Google SD support.
 
  • Like
Reactions: grimreaver
What about the "Mobile Site" problem? I'd much rather that get fixed.

Or maybe an HTML5 improvement, or a speed increase for the stock browser.
 
What about the "Mobile Site" problem? I'd much rather that get fixed.

Or maybe an HTML5 improvement, or a speed increase for the stock browser.

I don't think the "Mobile Site" thing is a real problem that needs to be fixed. Its an Android thing. This is working as designed.
 
So a tablet computer is working 'as designed' when it transfers me to a mobile site immediately? Then they need to fix the design, because that's a bad idea. This is a tablet, not a smartphone.
 
I agree with Goff, its a tablet not a smart phone I would prefer it to be desktop than mobile
 
Myself, I don't remember the last time I used the stock browser. I've been pretty happy with Dolphin (now using v6 beta) and have it set to desktop view by default.
 
I'm still waiting for my 3.2 update on my wifi xoom and sure the check for update button will be broken by time I get the update
 
Mine popped up today unexpectedly. It was nice. Wasn't looking for it at all, it just popped up ready to download. I clicked yes, and went with it. Biggest thing so far is that "unoptimized" apps can be expanded to fit screen. Not sure how to check the SD card. Should I just stick an extra SD card in and see if it reads it?
 
Also (im)patiently waiting for 3.2 update... It will be interesting to see how well the 'zoom' feature on the xoom really works. It may end up making apps look horribly pixelated. The biggest addition for me would have been the functionality of the sd slot, however, the google music beta has eliminated much of my need for the extra storage...
 
Mine popped up today unexpectedly. It was nice. Wasn't looking for it at all, it just popped up ready to download. I clicked yes, and went with it. Biggest thing so far is that "unoptimized" apps can be expanded to fit screen. Not sure how to check the SD card. Should I just stick an extra SD card in and see if it reads it?

yeah, power it off, slide in the SD, power on and see if it recognizes it . . .let us know.
 
Mine popped up today unexpectedly. It was nice. Wasn't looking for it at all, it just popped up ready to download. I clicked yes, and went with it. Biggest thing so far is that "unoptimized" apps can be expanded to fit screen. Not sure how to check the SD card. Should I just stick an extra SD card in and see if it reads it?
The unoptimzed app is a big plus. And please stick a SD card in n can't wait to load it up with my own movies for those long airflghts and stop giving Google all my money
 
So a tablet computer is working 'as designed' when it transfers me to a mobile site immediately? Then they need to fix the design, because that's a bad idea. This is a tablet, not a smartphone.

Why don't people understand this. Its not just an issue with the Xoom/Honeycomb, but with the websites themselves. Android uses the user agent of 'Android <Version number>' (so Android 3.1 or Android 2.3.3). Most websites ignore the version number and just check for Android and determine if the site should be mobile or normal.

Now yes it would be great of Google made a user-agents that said Android Tablet <version #> and Android Phone <ver #> or just made the option to choose desktop as default, but it is not entirely their fault that web developers take the easy way out.
 
This is poorly thought out coding in Honeycomb. They easily could have coded the user-agent to say "linux" instead of "Android" and avoided the entire issue.