• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Honeycomb 3.2 update rolling out.

Just got the update on both off my xoom's. sd card and zoom feature are working fine, but swype is not working in portrait mode.
 
Just got mine. I have a new 32gb sdcard in there. How can I tell if its working? I have ES file explorer but it seems to only be reading the system memory. To confuse things, system memory has a folder labeled "sdcard". File manager says I have 13gb of 29.xx remaining.
 
I also received my update this morning. Most everything is operating as it did on 3.1. I can't say I notice much of a speed difference, myself (non-rooted).

Swype works fine in landscape, but not so good in portrait view. It detects touches about 3 keys left to what I'm actually pressing.

I'll be throwing in my 32GB SD card later today.
 
Mitchrapp said:
Just got it now. It gave me a error about swype but it still works for me. Wifi only here.
Click to expand...

I was getting the error every time the keyboard came up, so I tried to uninstall and reinstall it. In retrospect, that was a mistake, because when I try to install, it's telling me the resolution isn't supported.

Oh well, I should be getting a bluetooth keyboard today that I can use until Swype figures out how to patch this.
 
you cats should try swift key. its now avail in the market for 50% off. i use it on the 3D and the xoom and its a great board. its come a long way from the beta days...
 
marctronixx said:
use file managr HD which is optimized for tablets. you have to back out of the root folder to see the external Sd card.
Click to expand...

Thanks for that heads-up, marctronixx, re. File Manager HD...I'll have to check that out.

The thing I think is coolest about this is how apps (specifically my Market apps ;)) are now full-size on the screen and not imcorrectly shrunken-down (its like Honeycomb selected the smallest possible phone's screen (like the original G1) to use for a screen size for apps that are not yet optimized for the large screen).

I do know that I need to figure-out how to update my apps for Honeycomb and larger resolution devices, but that's why I got my Xoom in the first place, eh? (just haven't had time yet, ugh :p).

Cheers!
 
Just got the update. Interesting thing is the SD card now mounts but it looks like its write permissions are not set correctly. Tried to transfer files from internal mem to /mnt/external1 but its not letting me. Reformatted the SD card just in case. But no luck so far. :mad:

wifi zoom, non-root running stock 3.2
 
The problem (found on another forum) is that the API used to write the apps did not have the ability to utilize the new path, "mnt/external1", only the old path "mnt/sdcard". Once the new API is released to developers, they will then be able to update the apps for the new path.
 
lowboydrvr said:
The problem (found on another forum) is that the API used to write the apps did not have the ability to utilize the new path, "mnt/external1", only the old path "mnt/sdcard". Once the new API is released to developers, they will then be able to update the apps for the new path.
Click to expand...

Didn't have time to test / check this out last night when my update came in...(it was already was past bedtime, LOL).

I changed my two apps several months ago (thanks to a nice heads-up from Andrew P. Moore, the developer of Light Flow) on how to dynamically determine the external storage directory (I had previously hard-coded "/sdcard" or "/mnt/sdcard").

Here's the code I now use that I hope still works:

File sdCard = Environment.getExternalStorageDirectory();
ext_storage_dir = sdCard.getAbsolutePath();

I'll test / verify and report back that this still works when I get home tonight...my hope / thought is that apps written using something like the above will already work on a 3.2 Xoom.

Cheers!
 
ok got my update yesterday.. mounted the sd card but cant do nothing with it.. ok , let me get this right.. enable sd card but cant do shit with it anyway? what was the pint
 
marctronixx said:
use file managr HD which is optimized for tablets. you have to back out of the root folder to see the external Sd card.
Click to expand...

I'm using File Manager HD now - I agree a much better explorer tool.

But - my problem is not much better. I checked the permissions on the folder /mnt/external1 - and it is listed as "dr-" - which seems to mean it is a directory and it is readable. But not writable. From what I have heard, I can't change the permissions on this unless I am rooted - which I am not.

So - whats the point of enabling SD Card support only to have a read only micro sd card? :mad:
 
^^^ although that is a very acceptable and highly probable reason, its not an official release from Moto or Google, so lets keep that in perspective. :)

I know from which forum you speak however.. ;)
 
Guys,

I've stickied this thread...seems fair since the 3.1 roll-out thread has been sticked for a while...:D

Any thoughts to un-sticky-ing (is that a word?) the 3.1 thread...

Cheers!
 
I was having problems playing my media files on the sdcard or reading any type of document. I have a class 4 Kingston 32gb sdcard.

I decided to format my 32gb sdcard even though it was already formated as
32 fat. I formatted it again as 32 fat, reinserted the sdcard. Using the USB cable from my PC I added a movie file, mp3, a pdf and picture to the sdcard. On the xoom I used Astro manager to access the sdcard (mnt/external1) and I was able to play the movie and mp3 files, I was able to read the pdf file and view the picture file. I am still unable to move or copy files from another xoom directory to the sdcard but I can copy files from the sdcard to a directory on the xoom. Hopefully the write to bug to the sdcard from within xoom will be rectified soon. I am fairly happy with version 3.2.:)
 
Okay, didn't get time to report back last night, but here's what I've found (and not found), so far (much of it you've already gathered):

1. I can't find or figure-out which API will return the "/mnt/external1" value for Honeycomb 3.2.

So, I thought perhaps the Environment.getExternalStoragePublicDirectory() method would return a different value than the Environment.getExternalStorageDirectory() method.

Unfortunately, it still returns "/mnt/sdcard" as the directory prefix instead of "/mnt/external1" on my Xoom:

Code: 
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_ALARMS).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_DCIM).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_DOWNLOADS).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_MOVIES).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_MUSIC).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_NOTIFICATIONS).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_PICTURES).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_PODCASTS).getAbsolutePath()
Environment.getExternalStoragePublicDirectory (Environment.DIRECTORY_RINGTONES).getAbsolutePath()

Here's the logcat LOG entries that I recorded for this simple test:

Code: 
V/testme  (15151): testme(): DIRECTORY_ALARMS:        /mnt/sdcard/Alarms
V/testme  (15151): testme(): DIRECTORY_DCIM:          /mnt/sdcard/DCIM
V/testme  (15151): testme(): DIRECTORY_DOWNLOADS:     /mnt/sdcard/Download
V/testme  (15151): testme(): DIRECTORY_MOVIES:        /mnt/sdcard/Movies
V/testme  (15151): testme(): DIRECTORY_MUSIC:         /mnt/sdcard/Music
V/testme  (15151): testme(): DIRECTORY_NOTIFICATIONS: /mnt/sdcard/Notifications
V/testme  (15151): testme(): DIRECTORY_PICTURES:      /mnt/sdcard/Pictures
V/testme  (15151): testme(): DIRECTORY_PODCASTS:      /mnt/sdcard/Podcasts
V/testme  (15151): testme(): DIRECTORY_RINGTONES:     /mnt/sdcard/Ringtones

2. There's lots of discussion going on over at the Moto Support forums re. this:

https://supportforums.motorola.com/thread/53816

as well as at least one formal issue reported to Google:

Issue 18559 - android - 3.2 SD card read-only - Android - An Open Handset Alliance Project - Google Project Hosting

I'm sure you can modify the mount permissions of the /mnt/external1 mount point from "dr-" to "drw" if/when you are rooted, but its not here yet for non-rooted Xooms :( :mad:.

3. It is certainly going to be interesting to see how a developer knows when its appropriate to use /mnt/sdcard vs. /mnt/external1. I can sort-of understand Google / Moto not wanting to break apps by having the aforementioned APIs start automatically returning a new / different mount-path for the "SD card" (which is obviously internal to the Xoom). Its going to be "interesting", for sure...;)

Anyway, I'm betting that there'll be a patch / update out "soon" for us...

Cheers!
 
skiahh said:
OK, just got my update and the bluetooth tethering still works!

Another little change I noticed is when you activate the screen, it shows the name of the wireless network next to the wifi icon. That's a nice touch. Once you swipe to unlock, it goes away, but when you tap the corner, it shows it again in the notification/status box.

Haven't noticed anything else, but I've only had the thing for a week, so probably won't notice any of the subtle changes.
Click to expand...


OK so please let us known if you actually disabled your wifi and actually surfed the web only using your Bluetooth tethering from your moto droid phone. I need to know because I just accepted the new 3.2 update which was pushed to my xoom and now allows use of SD card slot, however, my bluetooth tethering connection via rooted moto droid which was working before but no longer functions after update to 3.2. I cannot load webpages despite having a "using [bluetooth] connection for internet access" message under Bluetooth settings. Now I get a message next to my clock indicating "no internet access" despite everything looking like it should have an active connection. Has anyone else experienced this? I'm really pissed if there isn't a workaround to this.:mad:
 
You must log in or register to reply here.
Back
Top Bottom