yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] davidsos:
So I finally flashed it and joined the ranks of the lab rats. I followed the directions and it came up without incident. One problem I had is that the included hulufied flash player was not stable and it also screwed up the browser, requiring a reboot. I uninstalled it and got the latest from the market, which doesn't hulu but doesn't cause any trouble. I reinstall the hulufied flash player and the problems come right back. Other than that, so far so good. If I find anything else I'll pop in and report it.
[Xoom Android Development] Almighty1:
Actually,Clockword Mod, the one from solarnz skips the /data/media or /sdcard when doing a nandroid backup but it backs up everything on the internal SD card unless you put a blank "eraseData" file in /sdcard/external/clockworkmod which can easily be done with:

adb shell touch /sdcard/external/clockworkmod/eraseData

I think the reason is probably there will be some people who have a big /sdcard used up and no physical SD card will be able to back everything up as the cards are only 32GB at this point for the largest. Ax0r's method would work only when I have a working HC as all the SD Card readers I have can't handle cards more than 4GB.
[Xoom Android Development] Almighty1:
Did you try the newer version, modified current market version of the flash player?

http://xdaforums.com/showthread.php?t=1115167
[Xoom Android Development] solarnz:
If your external sdcard isnt appearing, create a new folder in /sdcard called external. Then reboot.

This should fix the issue of you not seeing the sdcard.
[Xoom Android Development] Alxoom33:
Thanks BRD

Thanks BRD! Although I did not have any problems with the earlier version, I flashed the updated 1.0 ROM and the earlier OC'd 1.4.4 Full throtle Kernal. It shows up as Tron #3. Is that what needed to be done for the best performance?

It worked flawlessly, no wipe or other fixes were needed. It seems like my blutooth keyboard works better with this version. I used to get lot of repeated keystrokes, Likkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkke thiiiiiiiiiiiis. I had to force above.

Thank you for your hard work. Will definitely donate.:):D:)
[Xoom Android Development] cat2115:
Just want let u know that after flashing rom v1, ntfs mount 1.3 cause fc
[Xoom Android Development] REHolt218:
I seem to have a new problem with the ROM. It loaded fine and I didn't have to do a factory reset. The only thing I found not working are the NTFS drive mount and the charging light. I tried flashing the light on zip and it causes my wifi to not work (I have a 3g enabled device). I reinstalled the Tom and the 3g fix and wifi works again. Tried this several times to be sure with the same results.

By the way, great work and thanks to the whole team. I'm loving it.
[Xoom Android Development] bigrushdog:
lol. Guys charging light IS NOT A STOCK FEATURE. Its not broke. Soon u will have the option to control that and things dynamically.
[Xoom Android Development] StrifeSoldierVII:
Here are some wise words by me for Team Tiamat:

"Team Tiamat has become the Cyanogenmod team for the Xoom community, being that they are the original devs that everyone will base most/all their sources from when creating a custom kernel or a custom ROM. If you ask me I am staying with Tiamat and everything they release/do. That's just my opinion but... look at how it turned out for the Cyanogenmod team. I'm gonna say that 90-95% of the community custom ROMs were based off of CM's source. The future looks great for Team Tiamat."

Keep up the good work you guys! :)
[Xoom Android Development] REHolt218:
I know it's not a stock feature, that is why I loaded the light on zip that you provided with 1.4.2 (I think that's right). I just didn't expect it to break my wifi access. It has worked fine in the past.
[Xoom Android Development] imneveral0ne:
Has anyone else lost the ability to find market apps?
[Xoom Android Development] solarnz:
If you flashed only the boot.img, flash the kernel again.

In our kernels, we only update the kernel and not the ramdisk.
[Xoom Android Development] aronslusa:
Anyone else having issues with the Appstore from Amazon on this ROM?

Mine won't let me see the apps I've purchased no matter what I do. And when I go to purchase one, free or not, it says that I have to enable 1-click settings, which I have about a million times now, and nothing I do is helping to make it work again lol.
[Xoom Android Development] REHolt218:
what I did was to reflash the ROM 1.0 Deodexed and the 3g fix.

I had also tried to reflash the 1.4.4 Full Throttle kernal in order to get the OC GPU. That didn't seem to help either.
[Xoom Android Development] lrs421:
Can anyone advise you to change the LCD density other than using the app (doesn't save on reboot). Text looks smaller compared to stock rom and I didn't see the option to adjust in the build.prop
[Xoom Android Development] joeski27:
With all due respect, this was a feature that *was* working until I flashed this rom, and now it does not....which means that it is now broken :) The fact that it isn't stock is in fact irrelevant. No need for you to call it something that it isn't, we were all just trying to figure out why it wasn't working anymore, no worries :D. Thanks for all the hard work, looking forward to future updates!!!:cool::cool::cool::cool:
[Xoom Android Development] joeski27:
Agreed, same thing happened to me, and I too wasnt expecting a total wifi crap out. I would have assumed that if this was going to happen we would have gotten we would have gotten a heads up that we shouldnt bother because it wouldn't fly...but oh well:D.
[Xoom Android Development] lpasq:
Is it like impossible to develop an option to cloak or temporarily disable root so root-sniffers can be faked-out? Just wondering if it is even technically feasable.

...xoom posted...
[Xoom Android Development] Kippui:
Will we have a rom built specifically for xoom us wifi? I'm avoiding roms for now until I can flash things over like Verizon users can without any extra steps.
[Xoom Android Development] alex2792:
I had problems with Amazon appstore telling me that my SD card wasn't mounted,I repaired permissions in Rom Manager then rebooted and its been working fine since.
[Xoom Android Development] davidsos:
That worked. I'm surprised that the adobe flash that was packaged with the ROM was funky. Though for a 1.0 release, not bad at all.
[Xoom Android Development] rschenck:
Interesting ....I'll file that fix away. Thanks!
[Xoom Android Development] Almighty1:
Glad it worked, that one is nothing more than a hack to fool hulu.com into thinking you're running a Microsoft Windows desktop version of flash, nothing else has been touched. The one packaged with the ROM might actually be the version on the market prior as there was a new version that came out I think a day before the ROM came out.
[Xoom Android Development] rschenck:
I would definetly agree with this sentiment. TEAM TIAMAT is setting the standard. I am excited to be involved with this ROM from the first version.

Great work. Already looking forward to 1.1.
[Xoom Android Development] brandenk0:
I installed this rom a few days ago and it has been AMAZING! Thanks so much! One thing I have experienced a problem with is trying to install the app made by hellcat82 to mount external USB HDDs. After installing, when you try to open the app, it immediately force closes. The only reason why I believe it is the rom that is causing the problem is because someone else was experiencing the issue and the only similarities between our Xooms were that we both had the Tiamat Rom installed. Would this be because the rom is deodexed?

Edit: Just restored to my previous backup before i installed the rom and installed the app. No force closes at all and the app is running smoothly.
[Xoom Android Development] jfvidalc:
I had originally flashed the tiamat rom when it first came out and had the 3g problem, so I nandroid restored my original stock rom with tiamat kernel and got back normal. When the 3g fix came out I reflashed again with the 3g fix and its been running great since.

Another happy camper.

Thanks Tiamat team. :-)
[Xoom Android Development] solarnz:
Glad you like the 3g fix, it took us 2 days to get it in #xoom.
[Xoom Android Development] solarnz:
OK.

For whoever wanted the led charging light to be enabled again - you request has been fulfilled.

Grab the optional update 2 from the original post and flash it :) through CWM.
[Xoom Android Development] gerald410:
Thx guys for the rom and the additional features see ya in #xoom.
[Xoom Android Development] jsms0905:
anyone having problems with superuser? mine wont update, allow access to anything, i cant even flash the update because it says its bad..idk what to do. i even tried the SU updater fixer..
[Xoom Android Development] rschenck:
Try flashing the ROM again, see if that corrects it.
[Xoom Android Development] MidwestDrummer:
I'm a bit lost here, and hoping someone can point me in the right direction. I've tried to root my Xoom and flash CWR per this thread: [GUIDE]How To Root Stock 3.1 Xoom and More![3G][Updated 6/2]. I get hung up when I get to the steps on how to flash a kernal.

When I select "mount USB storage" in CWR, my Xoom's SD card mounts to my PC, but it only shows about 3 MB worth of free space. This is, of course, nowhere near enough to drop a kernal or ROM zip file, and obviously it should show a lot more free space.

On the other hand, I tried dropping the kernal and ROM zips on the root of the Xoom. After that I connect it via USB with USB debugging active, and when I go int CWR, I am able to select install zip from sdcard > choose zip from sdcard > tiamat_xoom_rom-v1.0-deodexed_release.zip.zip Yes - Install tiamat_xoom_rom-v1.0-deodexed_release.zip.zip. It appears to go through the ROM isntallation, wiping cache, flashing kernal, etc., but when I reboot by Xoom and go to Settings > About tablet, I still see the following info:

Kernal version:

2.6.36.3-gc2bee64

android-build@apa28 #1

Build number:

HMJ37

I've tried completing all of the steps a second and third time, but without success. I'm sure there's some small, but important, step that I'm missing, but I can't seem to figure out what that is. Any ideas?

Thanks!
[Xoom Android Development] pyrator:
Its not just you, same here. I reverted to old backup and all is well again. There is something breaking the otg in the rom.
[Xoom Android Development] cam30era:
I am able to USB tether my Incredible to my Xoom via OTG host cable, and mount the storage from same on my Xoom. So OTG is working for me with this ROM.
[Xoom Android Development] davidsos:
I just did that, the led is now on, however, wifi is now dead. The "wifi on" checkbox in settings, says "error." I then reflashed 1.4.4 full throttle but no change, same story. Any ideas would be helpful as well as welcome.
[Xoom Android Development] rschenck:
I had this the other day...reflash the ROM itself to restore WiFi. Someone may know an easier way, but that is what worked for me.
[Xoom Android Development] Salpula:
So happy to finally see a custom rom! Donations to BRD may be in order (and overdue after the kernel, hulu flash, etc.).

I'm gonna take the plnge after school.

Sent from my Motorola "Hey, is that an iPad?" Xoom
[Xoom Android Development] BUMP THAT:
Originally Posted by ax0r View Post

This thread contains a framework-res.apk that is used for the contacts fix which reverts the battery icon back to stock

thank you. I ill give it a shot

----

I flashed the 3g fix and it kept the circle battery, is there something i skipped to get the stock battery back? I want to keep the xoom looking stock. :)
[Xoom Android Development] davidsos:
Cool, I was hoping to hear that. That means that I'll have to redo some other fixes that I've done since. I can live with that. Luckily I have the zip on my external SD card so I can reflash in a blink or two.
[Xoom Android Development] rschenck:
Very wise..I always keep the current rom and kernel I am running and any other relevant zips on the SD card for quick CWM rescues.
[Xoom Android Development] REHolt218:
OK, I loaded the update 2 file and I now have the charging light AND WIFI works. Thanks for taking the time to look at this. I wasn't trying to start trouble, just reporting an issue.

You guys will definitely be receiving a donation from me! This rocks!

Now, if the NTFS mount issue could be fixed we would be at 100%++:rolleyes:

Robert
[Xoom Android Development] davidsos:
I reflashed the ROM to restore wifi, however, the charging LED is not staying on. Doesn't look like that fix works for me. I'll live without it for now as it's not critical and the rest is AOK.
[Xoom Android Development] rschenck:
I should have mentioned it would likely overwrite the fix...but you seem like a reasonable sort who would not be willing to trade wifi for little green light.
[Xoom Android Development] Steady Hawkin:
Team Tiamat has changed the game once again, well done!
[Xoom Android Development] davidsos:
Since it worked properly for Robert (post just above my last one) and doing what you said recovered my setup. I decided to download the zip and flash it once again, heck no big risk. This time the LED is working, go figure, I won't argue only smile.

This Kernel/ROM is pretty responsive :) One day we'll have universal docking station and only carry a tablet and cellphone. No more notebooks or desktops, well, one day......It'll bad news for Microsoft :eek: 3 service packs into Windows 8 will be too late.
[Xoom Android Development] Turkawa:
i had a total backup from rom manager.

then installed tiamat rom from cwm

boot animation loop

back to cwn and pushed restore

now it says error while erasing boot image!!

any ideas?

what do i do now?
[Xoom Android Development] davidsos:
Which version of cwm are you using? That might be the problem. I think you should be using 3.2.0.0 R4c
[Xoom Android Development] rschenck:
I had the same problem. I reflashed the tiamat boot image, then used advanced restore to restore everything but the boot image. In that way I was able to get up and running again.
[Xoom Android Development] davidsos:
Did you get the "error while erasing boot image?" You'd think that the correct version of cwm should be able to do this, even if one selected that by mistake, by not using the advanced restore.
[Xoom Android Development] kymikes:
I am running into the same boot animation loop. I do have cwm 3.2.0.0 and was at Tiamat 1.4.4 running fine. I have a USA WiFi only and have had it for just a few days. I had upgraded to 3.1 via OTA. The only app that I have loaded was SetCPU. After flashing the v 1.0 ROM, I got stuck in the boot animation loop. Tried re-flashing the boot image (light off) and the kernal for 1.4.4 but I still have the boot animation loop. Do I have any choice short of ax0r's method of going back to 3.0.1 images and working my way back?

I am a bit of a noob on the Xoom but have done a bit with my DroidX so I am fairly practiced with ADB and fastboot. Thanks for any help.
[Xoom Android Development] comagnum:
because I feel this thread get's more activity than the "rom request one" I have a few ideas/feature requests.

With that being said, i, personally, would love to see better performance and less lag while in portrait mode. It's aggrivating, mostly because I like to read things in that format. Secondly, I don't know if this is possible, but could it be possible to add two extra windows to the home screen on the top and bottom? Like a swipe down returns you to the previous window, swipe up brings you to settings, or however anyone would like to do it. Having the home screen just for launching apps seems like a waste of space to me. Having the home screen be more customizable would do the UI justice. Lastly, and from what I can tell has already been mentioned, is the ability to change things on the fly like theme, customizing said theme, ability to change colors/looks/what have you of certain things.

And as i was typing this I had another couple come to me. Ability to play back a larger variety of audio/video types with the stock players. I'm sure that would be as simple as adding the needed codecs, but i don't know for sure. And geting rid of that god awful and horribly placed volume popup/slider. The positioning of it makes no sense to me what-so-ever. It sits in the middle of the damn screen.. moving it to a more traditional vertical slider down to the bottom in the tool bar would be ideal, or just having it be a simple translucent text somewhere else that doesn't obstruct the screen. Also, for a lot of apps the ability to hide the toolbar would be awesome as well, when browsing the web, videos, office work, emailing, games. If this is possible I haven't discovered it yet.

If it would be better to post this elsewhere, please let me know.
[Xoom Android Development] troy22:
i need help bc i cant get out of the activation screen.... what do i do?

i think its because i wiped in recovery.... how can i fix this?
[Xoom Android Development] xlGmanlx:
Restore a nand or flash the 3.1 all over again
[Xoom Android Development] Sic123:
don't flash the light off boot img that is most likely what is causing the bootloops
[Xoom Android Development] Brenardo:
Ey solanarz do you think you could rework CWR to disable the ability to wipe.
[Xoom Android Development] phonepersonality:
Wrong thread. Please delete :(
[Xoom Android Development] Psychokitty:
Uhmm...

WTF?!:confused:
[Xoom Android Development] Almighty1:
Are you talking about Superuser or su the binary?

The problem is the su installed by SuperUser app is not compatible with the Xoom. All you have to do is do a terminal session or use adb with the "adb shell" command which will get you to:

$

type "su" and hit the enter key and it should give you back:

#

If it doesn't, and you get the following:

reloc_library[1315]: 2756 cannot locate '_mktemp'...

CANNOT LINK EXECUTABLE

The 1315 and 2756 might not be the exact numbers since I didn't note down the exact numbers before I looked up how to root a Android device when one has lost root.

See post #340 in the following thread for the fix:

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

This is the previous version of the su binary that was modified to work on the XOOM which is version 2.3.1-ef, hopefully there will be a modified version of 2.3.1-efg available soon.
[Xoom Android Development] Almighty1:
You have to use a PC and run

fastboot -w

followed by

fastboot reboot

then go into recovery and flash the ROM again. I tried this on a friends new Xoom which used a nandroid backup of my working Xoom which had the same boot looping issue, USA WiFi Xooms and that fixed it. I don't know if flashing the ROM again is really needed but it seems like the fastboot -w might have wiped some of the apps that came with the ROM as I didn't see the other apps mentioned in the OP #1 being there and the only thing not on the stock WiFi 3.1 is the "Video" app.
[Xoom Android Development] Salpula:
The hardest part of flashing this was getting everything backed up and restoring the clockwork recovery modified for xoom after accidently updating it. No wipe necessary(so far) coming from BRDs 3.1 update. Painless. Did the Rom -> 3g update -> update2 -> wipe cache -> wipe dalvik -> reboot.

Flashed without a hitch, will be donating shortly.

Sent from my Motorola "Hey, is that an iPad?" Xoom
[Xoom Android Development] MidwestDrummer:
I hate to bump my own post, because I don't wanna be that guy, but does anyone have any idea as to what my problem might be?

Thanks!
[Xoom Android Development] thebreezer:
Since I will need to root and unlock my Canadian Wifi Xoom, I am in the need of a good guide. Any links! :confused:
[Xoom Android Development] Sic123:
have you tried a different sdcard or possibly moving from your xoom internal storage to your sdcard using a file explorer inside honeycomb? my kernel is different from yours cause i flashed the oc'd gpu version but my build number is the same are you trying to root or install the rom?
[Xoom Android Development] kymikes:
That did the trick. What was your logic to wipe the uda from fastboot (just trying to better understand the mechanics/interactions of boot image, kernal and ROM in this environment). Definitely sent 'thanks' your way. You were a great help. ;) ;)
[Xoom Android Development] Sic123:
you can always try searching its quick and painless but since you didnt look here

http://xdaforums.com/showthread.php?t=1011196
[Xoom Android Development] thebreezer:
Thanks very much :-)
[Xoom Android Development] thebreezer:
Oops, 1 click root not available anymore, any other links?

I know I could search, but I want a tried and true guide that worked successfully.

Thanks for your help.
[Xoom Android Development] Sic123:
Are you on 3.0.1 or 3.1?
[Xoom Android Development] thebreezer:
3.0.1
[Xoom Android Development] Sic123:
3.0.1 | http://xdaforums.com/showthread.php?t=1010568&highlight=root+wifi+3.0.1

3.1 | http://xdaforums.com/showthread.php?t=1078019
[Xoom Android Development] kymikes:
Oops, now I have a different problem. Since I got back up, the Xoom keeps rebooting. My guess is that the CPU speed is too high but SetCPU was erased by the wipe. When I try to get it back from the market, when it starts to install, the Xoom reboots again. Is there a way to reset the speed without an app?? I had been running at 1.6 without problems before I installed the ROM. Thanks for any help.
[Xoom Android Development] okantomi:
Have you tried placing the files you're going to flash on th sd card using your pc? If you know for a fact that your card is good, you can use an adaptor to drop the files on the card. When you put the card back in the Xoom CWR should see it. Anyway that's how I do it. I also use a 2gb sdcard that was formated in an android phone, for flashing.
[Xoom Android Development] Almighty1:
Haha, you don't want to know. I'm playing with a 2nd xoom which is my friends that I opened fresh out of the box and I basically did a nandroid restore of my Xoom to it and basically got the bootloop problem which I experienced on mines too but I never fixed the bootloop problem on mines yet due to the pain of having to install/titanium backup restore 324 apps after a wipe. My logic is since we know clockwork recovery's wipe is a no no and the one inside Honeycomb is good, one would assume that Google's own adb and the tools has to be good as well and remember I was bootlooping so there isn't really any other way to wipe without either restoring a known good nandroid backup or having to do the long route to 3.0.1 and then back so I was studying all the options of fastboot and notice that -w says wipe user data and cache. The only drawback is this one does wipe the /sdcard aka internal storage as well so after you get things working, you have to basically:

adb shell

su

mkdir /sdcard/external

as the directory external got wiped as part of the fastboot -w so you won't be able to mount the external sdcard there. So basically, it's either the /data or the cache that is messing up and causing the bootloops. It would actually be better if one can pinpoint the exact culprit so that it will be a simple delete of just a few files and then one will know what to restore after things are working.
[Xoom Android Development] Almighty1:
If Setcpu is wiped, then the settings should be gone already but try this, you're lucky I actually read about this a few days ago... :rolleyes:

adb shell

su

touch /sdcard/setcpu_safemode

exit

exit

adb reboot

After rebooting, delete the /sdcard/setcpu_safemode file and then proceed to market to download Setcpu again. And after everything works, might be wise to flash the latest tiamat kernel except do not flash the boot image from that thread, use the one in the OP #1 here.
[Xoom Android Development] okantomi:
I would advise against using a "one click" methodbecause I've seen a lot of people get into bricks using them.

This is a pretty good guide:

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

Be careful not to update to the newest Xoom recovery in the Clockwork Mod app (4.0.0.x) as it will mess you up.