yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] andr0id23:
Video Player

OK I think I have read about problems playing videos, but can't find it now. I read thru 28 pages in this thread, but didn't see nothing. Are other people having problems with videos they take or put on their Xoom themselves(I.E. Not concerned with Google rentals right now)? I thought I was good after doing a quick check right after updating to 3.1 last night, but now I can't play videos. I watch a lot of HD movies on my Xoom, but just get error messages now. I've tried the stock player along with 2 market players. Also, I can play an occasional streaming video from Jetflicks(which I swear worked flawlessly directly after the update), but many of those fail as well now.

So basically, just looking for verification that there are issues with playing video. From what I can tell, it's not just limited to me. I'm assuming this can be fixed with an updated kernel and I would also assume that it would be a pretty high priority for one of the first kernel releases by BRD. Does everything I posted sound about right? I can live without playing videos for a few days until we get a BRD kernel, but it's not something I can live without for long!

Again, I'm almost positive I've seen people post they have video problems, but I read the first 28 pages and didn't see any mention. Maybe this will help someone who decides to start from the back and real the last 28 pages(which, by the way, is what I usually do. But I swear I read this pretty quickly after release...).
[Xoom Android Development] strat_player:
I havent had any issues playing video on mine. Tried with the installed player and Rockplayer and both work great. TBH, I dont recall seeing anyone else mentioning other than market video issues.
[Xoom Android Development] andr0id23:
Hmm wonder what's happening on my end then. I've tried stock player, Act 1, Mobo, and Rock and I get an error saying this video cant be played or something along the lines of The Android stock media player has stopped. Restart it or reboot your system now. Then I think it gives an error code, but always flashes so fast I cant read it. Hmm I swear others were having problems with video. Maybe that's why I can't find any posts regarding it. But damn, wonder whats goin on :confused:

OK I can play video I took with the device, and videos downloaded from youtube, just not my movies. I've never had any problems playing any movies before, and I've always converted them the same way, with the same tools. It says "The Android Media Server died" Then the "code" it gives is (100, 0) Thats all it says at the end of the error message. Anyone have any ideas?

Now "An unknown error with Android media subsystem"

*Edit* Ok it looks something is going on with my media/video service. When I open up any video/picture viewing app, sometimes some of the movie thumbnails will show up, and I can play them. Most times tho, no thumbnails will show up and I will only get a little black screen instead of the movie thumbnail. When this happens, I get an error playing, no matter what video app I try. I get different error messages about the video not being able to be played, or the Android Media Server/server subsystem. Along with the error messages I get two numerical "codes" at different times. One is (100, 0) and the other is something like (10, -274857589).

This is affecting videos on both internal and external storage.
[Xoom Android Development] teo91:
Do you know if there is somewhere the French language and how to install :confused:
[Xoom Android Development] teo91:
When I want to put a 4GB movie I get the message: File too large

Any idea ?
[Xoom Android Development] ClydeB1:
If the location you are saving your file to is formatted to FAT32, 4GB (less 1 byte) is the maximum file size that can be saved (limitation of FAT32 format). To go bigger than 4GB you need to format to NTFS, but AFAIK Android doesn't recognize NTFS formatted sd cards. There is a way to mount an external hard drive formatted to NTFS using an OTG cable and the usb host capabilities built into HC3.1 which is posted here.
[Xoom Android Development] kschuyler:
Thanks for your hard work!

Just a thank you to BRD... and please get that new kernel out to us :)

Donation coming your way... Confirmation number: 7LJ92140PW215082J
[Xoom Android Development] teo91:
Before update, i could use my sdcard and copy all video (4GO).

But the link that you spent: http://xdaforums.com/showthread.php?t=1020174 walking there with HC3.1, and wifi only?
[Xoom Android Development] ClydeB1:
Then it must have been formatted to another format. The largest file size FAT32 can accommodate is 4GB minus 1 byte - http://en.wikipedia.org/wiki/FAT32

I don't have an OTG cable so can't confirm. Ask in the thread.
[Xoom Android Development] Psychokitty:
Decided to pull the trigger on this after all the dust settled, but two of the download links seem to be dead.
[Xoom Android Development] ClydeB1:
Just tried again and they all work for me. If 2 and 3 give problems - some error about internal error, just close the link and open again and it should work.
[Xoom Android Development] merkman:
Worked great for me. Movies I've converted to apple format, typically ripped from Blu-Ray, and are usually about 2GB fit on my SDCard and run fine from External. Apps are reinstalled, and most everything looks great!

I did want to ask about overclocking. I reinstalled CPU Master Free, which was working fine with 3.0 up to 1.5GHz, but after installing 3.1 I'm maxxed out at 1GHz. Am I doing something wrong? Or is overclocking just not available at this point?
[Xoom Android Development] ClydeB1:
You need a kernel capable of OC before SetCPU can allow you to OC. BRD is currently working on one ;)
[Xoom Android Development] strat_player:
You're fine as this version wasn't overclocked when released.
[Xoom Android Development] teo91:
I just want access to my sdcard and put a large video. How do I do ? Any idea ?
[Xoom Android Development] UnMonk:
So wait, My Internal Storage will be unaltered? so everything will be untouched?
[Xoom Android Development] teo91:
Anybody for help me ?

How i can use my scdard (ntfs) (no external disk), just micro sd in ntfs format ?

But the link : http://xdaforums.com/show....php?t=1020174 walking there with HC3.1, and wifi only?
[Xoom Android Development] sfam:
I followed the instructions, and some things seem to work (OTG for USB Host), but I cannot see my SD card. Do I need to create the "External" subdirectory for this to show up?

And yes, I definitely have a microSD card - this is where I got all the zips installed in ClockworkRecovery.
[Xoom Android Development] LNKNPRKFN:
Oops forgot to Quote :) my bad
[Xoom Android Development] LNKNPRKFN:
If you have another android device, format the Micro SD in that device, then place in your Xoom reboot the Xoom and use root explorer and go to SDCARD---> EXTERNAL and voila there she be...formatting it with another android device puts the "android" type file setting and folders on the disc making it easier for the Xoom to recognize, hope this helped
[Xoom Android Development] sfam:
OK, this was maybe the easiest fix ever - I just rebooted it a second time and there it was! So yeah, everything appears to be working great now. Thanks all!

Previously on the first reboot after the install the External wasn't there. Second reboot it was. Go figure.
[Xoom Android Development] sfam:
I have an app question - is there a way to get the gallery app to recognize the images on a thumb drive? So far, the only way I've tried getting to thumb drive files is via the file explorer.
[Xoom Android Development] ClydeB1:
AFAIK Android will not recognize an ntfs formatted sd card. It only picks up FAT32. You will need to find an app such as DVD Catalyst or Handbrake to convert your video file so that it is less than 4GB. Otherwise you will need to get a USB OTG cable and then use an external hard drive (ntfs). You will need to go to the thread I pointed you to earlier to see if it works with HC3.1 and wifi only model.
[Xoom Android Development] Vanhoud:
Htm I formatted my SD card in my droid x and it still doesn't operate correctly inthe xoom. I can see the external folder but cannot copy anything into it
[Xoom Android Development] dscribe:
I am one of those who used the original files that were posted before they were removed and then replaced due to the discovery of a problem for some people. My zoom is wifi only. I simply need to know if I should reflash with the newer files or else if there is something I need to know or do regarding any future mods I might want to apply since I used those files. I hope this makes sense. TIA.
[Xoom Android Development] ryan562:
x2. my sd card was working perfectly for me before this 3.1 update.
[Xoom Android Development] pOOBAH1973:
RSD lite 4.9 might be too old.
[Xoom Android Development] kevdog:
Just to put a rumor to rest -- I haven't tried with the Xoom but on the OG my sdcard is formatted with ext3 and swap, and android can see the sdcard quite well. This is specifically to address that the card doesn't need to be exclusively formatted with fat32 to work.
[Xoom Android Development] ClydeB1:
I was wondering the same thing, but didn't want to reformat my new 32gb card to ext3 or 4. Have you tried putting the ext3 card into your xoom to see if it is picked up?
[Xoom Android Development] teo91:
I confirm for sdcard, it's need fat32
[Xoom Android Development] ebaca:
Ok, I flashed the 3.1 BRD rooted update from the dev forum and my xoom says I am at 3.1 and everything is working fine. Only problem now is that I keep getting the update notice that it has been downloaded and ready to install.

Is there a way to clear it? When I go to settings and update it doesn't say up to date. It keeps popping up when I reboot.

Also, if I am already on 3.1, why is the update still pushing to my xoom? I looked in the cache folder in the root directory and found what looks like the 3.1 update zip file. I deleted it but the damn ota update message keeps pestering me!!!!!!
[Xoom Android Development] jconner05:
Yes. IF you reboot back into recovery after flashing the new recovery. I forgot that step and lost all of my stuffs. :(
[Xoom Android Development] Thalinor:
Worked perfect, thank you!

Needed to reinstall my apps via Ti Backup, but not a big deal. /sdcard was all still there w/ all my data. Busybox needed to be installed, and there is still the SU app issue where sometimes you need to restart an app again after it gets SU priv, or it will not work. I think this is a known issue with SU and again, restarting or refreshing the app will fix the problem.

Again, thanks you very much!

EDIT: FYI Quadrant Pro is giving a score of 1670 with the stock 3.1 setup. Wow, that number sucks. was over 3000 with Tiamat, and even stock 3.0.1 was over 2000 if I can remember correctly.
[Xoom Android Development] osoft:
Is the charging indicator disabled in honeycomb 3.1?

Or this modified rom just breaks it?

Other than that , this rom works great on my wifi xoom
[Xoom Android Development] Didact74:
Well, I guess I am just another idiot (at least thats how I feel anyway) because I went through this very simple process and now it just boots to the Motorola screen then right back into clockwork recovery. It will not get to the honeycomb boot screen at all. Just Moto screen for about 10 seconds then right into Clockwork recovery. I followed the directions exactly, it seemed very simple. Any help would be appreciated. WIFI only US Model.

Thanks,
[Xoom Android Development] Didact74:
well it keeps getting better. Now it will not make it into recovery, it just sits at the Moto screen with "Reading OEM FUSE: 1" in the upper left.

Is there anything I can do from ADB, or am I heading to Best buy tomorrow to trade this sucker in?
[Xoom Android Development] okantomi:
Thanks so much for all your hard work. You saved my bacon...I was trying to recover from crashing my Android Market...and I had just compounded my problems when I saw this thread. This method was so easy to follow and even at midnight, I was able to make it work. I thought that the update to HC three point one took away the use of my external sdcard, but today I realized that it's still working! I sent you a donation. I wish it could have been more. You have made my Xoom work so well!
[Xoom Android Development] jland22:
Hold power and volume up for a few seconds after it reboots. Then press volume down and you should see reboot in recovery. Press volume up and it should boot back into CWM. If I was you, I would re-try the entire process again: it is simple enough to do in minutes. Maybe you didnt wipe data/factory reset before rebooting? I dunno...
[Xoom Android Development] validoption:
The charging indicator works the same as stock 3.0.1, which is to say, only when the device is powered off.
[Xoom Android Development] Didact74:
When i do that is just sits on "Starting fastboot protocol support." No other options.

I did the process correctly with the wipe. I tried to do the process again when i was still able to get back to clockwork, b ut now it just sits on the Moto screen with the message i posted earlier "Reading OEM FUSE: 1" in the upper left corner.

Any other ideas?
[Xoom Android Development] Thalinor:
I wanted to point out one thing for Xoom Wi-Fi only users. I kind of wish I had grabbed the Wi-Fi package before it was modified to include the 3g & Wi-Fi bundle update because while its not been a problem, when I go online to my market account I now have two Xooms listed. One says Xoom and the other that was added today after this update says Verizon Xoom.

Apparently, whatever was added to this new "Complete" package is causing the Wi-Fi only [at least on the market] xoom to act like the Verizon one.

I don't know if this is going to effect anything else, but it might be a good idea next time to keep the Wi-Fi and 3g software packages separate? Again, everything seems cool, and once again XDA users come to the rescue and save the day, for that thank you very much. I am just not sure if the device thinking its Verizon's version is going to cause any issues. If the market thinks its a different device, then I would assume something has to be different on the software side too? I don't know enough about this to make the judgment call, I just know that after 10 years with VZW they love to lock stuff down and have manufactures throw in extra pieces of hidden code. IMO keeping everything Verizon off my Wi-Fi only would be preferred. Again, Thank you very much for this update!
[Xoom Android Development] slatejones:
I noticed the verizon xoom in the web market also.... So I renamed it.lol. I do want to point out that us wifi users that used brd's update now have the movies tab in the market. Stock wifi'rs will not have it for some time.

Thanks for all your hard work BRD. I love my wifi only verizon xoom.lol.
[Xoom Android Development] Didact74:
okay, got back into clockwork recovery. Reinstalled all the zips in the correct order again with the data wipe at the end. It still keeps rebooting into clockwork, never makes it to the honeycomb boot screen. The zips all flash with no errors so I am not sure whats wrong. I guess I could redownload all the files and try again. Any ideas?
[Xoom Android Development] jland22:
Yeah but the movies are not viewable so dont waste your money. Seems the 3G users cant watch them either: hypothesis is that it is because of the DRM protection and our tabs being rooted.
[Xoom Android Development] slatejones:
Yeah, roger that.. but its only a matter of time before a dev fixes that for us to.lol.
[Xoom Android Development] ryan562:
for those who lost sdcard support after flashing this upgrade, try reflashing the boot.img. follow the steps in this link here:

http://www.xoomforums.com/forum/motorola-xoom-development/4370-just-brd.html

i just reflashed the boot img found in that link via adb commands and voila. my 32gb sd card is working again.

****this is for those who flashed the 3.1 update from tiamat 4.1 but still can't get the external sdcard to work*****
[Xoom Android Development] tekmunki:
I've had my tablet encrypted since the day I rooted it, I proceeded with these instructions and everything went as planned; however I was shocked to see my settings in-tact. The 'about' reads it's on 3.1, however none of the interface or app improvements exist and basically anything that would have written to /sdcard seems to have been passive- as well, the external sd card ONLY works in CWM.

I assume this is all because the tablet was encrypted--- but I'm unsure how to 'unencrypt' it--- perhaps just formatting /sdcard and then running the updates over again... I'll try that now...

No go, being I can't access /data (?) to mount or format it, I assume it involves the encryption- I'm going to flash the stock image, reroot, flash the update and then re-encrypt after the update... (I hope I don't have to do this every time)
[Xoom Android Development] ankorez:
plz

i'm in HC 3.1 Root

how access to my sdcard?

i have folder "external" on my tablet but can't create folder and not see files on my sdcard
[Xoom Android Development] ClydeB1:
Did you try the solution 2 posts up?
[Xoom Android Development] ankorez:
what solution ?

format to fat32?

i have 2 post up but i don't see solution
[Xoom Android Development] ClydeB1:
http://xdaforums.com/showpost.php?p=13804723&postcount=501
[Xoom Android Development] 05GT:
Everything worked smoothly. Thanks for providing quality work!
[Xoom Android Development] shmigao:
need a NO EURO 3G Xoom warning

would be better if the OP had a "not for European 3G Xoom" warning

yes it does say "Verizon 3G only", but not everybody understands what that means (CDMA vs. GSM/UMTS/WDCMA)...

there are some EU guys who flashed and can't get access to their 3G network now, naturally...

wonder whether we can find a DEV that can make this method available for EU 3G Xooms... should actually be just a few files different (e.g. build.prop, etc.).

but great that you in the States (and all other WIFI only guys) have it running on HC3.1 already! :-)
[Xoom Android Development] RoryPG:
For Canadians, the benefit of following the process and using the files in this thread is that you now have Google Books Honeycomb version and can download public domain books. It is also the US version of App Market and Music beta. Music beta still needs an invite, though, but the apk is a different version. I used a proxy to request a Music beta invite but I'm not holding my breath that I'll get it or that it will work when I get it. I can't buy books via Google Books, for example.
[Xoom Android Development] ankorez:
ok tks

i try it

but if i flash bootloader i can't boot recovery with power down :(
[Xoom Android Development] shinjibra:
can anyone tell me if it is safe to do this procedure on a wifi only brazillian xoom?
[Xoom Android Development] jrezin:
as long you follow the instructions (but only wifi-only version)... but you'll lose interface languages and typing dictionary... also, some wallpapers US version doesn't include... (but you'll have books othe other hand...)
[Xoom Android Development] shinjibra:
And can I use the oneclickroot with my wifi xoom from brazil? I ask cause I dont know if it is based on us or uk versions...
[Xoom Android Development] grasshoxda:
went from canadian wifi xoom tiamat newest to 3.1 no problem!
[Xoom Android Development] vitosans:
Worked with out any issues on US WIFI,

How ever I did loose root after doing this, what do I have to do to get root back?
[Xoom Android Development] jrezin:
not sure about 1click root, but if there's instructions to the canadian one, it should work... but any way, all you need is the clockwork recovery to use BRD's instructions... your system partition will be formated and restored to the us one, and your data partition will be wiped (except for /sdcard/).
[Xoom Android Development] Hexbug:
Here ya go!

http://xdaforums.com/showthread.php?t=1078019
[Xoom Android Development] Fangs87:
I did this and all of a sudden when i was booting up , it came to an ota update for the bootloader?? Just making sure this is normal.
[Xoom Android Development] cam30era:
I don't think this is normal. I never heard of an OTA for the bootloader.
[Xoom Android Development] shinjibra:
But don't I need to be rooted in order to install Clockwork? Or I am gettin it all wrong? (sorry for the noob-ism, I'm new to android)
[Xoom Android Development] tonyb15re:
From the STOCK 3.01 image I followed these instructions

http://xdaforums.com/showthread.php?t=1010568

Installed Clockwork from the APP Store then followed the guide in the OP of this thread..

I have just flashed Tiamat 1.42 using Clockwork over the top from this thread I am running the OC 1.6 file at the moment and the device is stable and steaming along nicely..:

http://xdaforums.com/showthread.php?t=978013

Usual Caveat of course, these arent my instructions, if you break it it aint my fault, they just worked for me..
[Xoom Android Development] jrezin:
No, you can use Method 2 in this thread:

http://xdaforums.com/showthread.php?t=1074979
[Xoom Android Development] vitosans:
Root seems to be flaky, a bit further back I had stated that I had lost root after doing this, but it turns out I have only lost root for some things, like screenshoter says my device is not rooted, but rootexplorer doesnt seem to have any issues,

Anyone else notice root is not working 100% of the time? I also noticed when I did busybox install, the first time it said my phone (tablet) was not rooted, but when I ran it a second time I said nothing.
[Xoom Android Development] Sodikop:
I had an issue trying to install busybox from Jrummy16, but I turned off the "sys link" I think...and installed busybox to both /bin and /xbin. Before it would keep telling me I wasn't rooted.. :confused:

Everything seems fine (though I DID forget to follow the full instructions and flash the new boot.img along with kernel, so that may have been my issue. Going to corect that later tonight.)
[Xoom Android Development] shinjibra:
Everything went fine on my brazillian Wi-fi only model. Thanks to everyone that helped me and, of course, the developers.

I believe I'm the first brazillian to confirm that it works flawslessly. I had no root, just flashed the clockworkmod thru fastboot and followed this guide.

I have 3.1, huhuhuuuuuuuu
[Xoom Android Development] wnrussell:
I had no problem following the instructions in the OP and then advanced restoring my 3.01 data partition only, with CWM.
[Xoom Android Development] rinaldop:
Hi...what about the portugusese-br language?
[Xoom Android Development] rinaldop:
Hi....what about the Portuguese-br language? Only English and Spanish?
[Xoom Android Development] shinjibra:
Yes. Only english and spanish, but thats fine for me. It actually keeps me in shape hehehe
[Xoom Android Development] volta:
ruh roh... just about all of my apps force close upon open. I did do a titanium backup restore of my data, but even after clearing the data through Settings-->Manage Applications-->Clear Data they still FC.

Any advice?
[Xoom Android Development] ClydeB1:
Either use ROM Manager or Spare Parts and fix permissions (oh and you got a free thanks from me - meant to press quote LOL)

Also, when you did the Titanium restore, did you restore everything? You should ideally only restore apps and data as a full restore can restore certain system settings which may not be compatible with 3.1
[Xoom Android Development] volta:
free thanks back at ya lol... but why fix permissions? which permissions do i need to fix?

I'm currently flashing tiamat 1.4.2 1.6OC and considering re-wipe. So please convince me it's not necessary :P
[Xoom Android Development] ClydeB1:
Fix permissions is a function in ROM Manager /Spare Parts which can resolve FC's (sometimes).

PS! See the additional bit I added to my post above in case you do still need to do start over.
[Xoom Android Development] volta:
Word. I only restored apps+data, of course. Most of the apps were already pre-synced via Google.

I'm going to try a re-wipe and try the apps that get pushed via Google before restoring from Titanium, just to rule that out.

I'm still not exactly sure what the Fix Permissions in Spare Parts will do for me, but will heed your advice and check that out. Thanks dude.