yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] LynnL:
This is a lot of steps so I wrote myself some instructions for the first method. Can someone check me so I know I'm not missing something important? (N00b! Sorry!)

My Current Status:

A rooted 3.1 wifi Xoom with 2.6.46.4 Tiamat 1.4.4

Already have Java, Android SDK, Moto drivers on PC, CWM on Xoom

Have a recent Nandroid backup & Titanium backup of apps & data

Files to Download:

Stock 3.1 image

stachre's modded 3.2 update

Tiamat 2.0 kernel (stock gpu)

Steps:

1. Plug Xoom into PC

2. Rename files to update.zip and kernel.zip. Drag and drop the files into the root of the SD card.

3. Open Android SDK, make sure Xoom is recognized -- in command window, 'adb devices'

4. Flash files to go back to stock 3.1 (instructions from here)

a. Unzip 3.1 image files into Android directory

b. Run:

adb reboot bootloader

(do I need to re-run "fastboot oem unlock" if I'm already rooted?)

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img (is this required?)

fastboot flash userdata userdata.img (is this required?)

fastboot erase cache

fastboot reboot

c. Xoom should now show 3.1 stock in Settings

5. Flash 3.2 update (instructions from here)

a. Boot into CWM

b. "Mount /sdcard" if it isn't already

c. "install zip from sdcard"

d. Select update.zip, yes

e. "Reboot system now" -- Xoom should now show Android 3.2 in Settings

f. Check Superuser -- if not running correctly or not updating in market, delete superuser.apk in Root Explorer then redownload

6. Flash Tiamat 2.0 kernel (instructions from here)

a. Boot into CWM

b. "Mount /sdcard" if it isn't already

c. install zip from sdcard"

d. Select kernel.zip, yes

e. "Reboot system now" -- Xoom should now show Android 3.2 Tiamat kernel 2.0 in settings

Did I miss anything? Thanks again! I will get the hang of this! (Eventually!)
[Xoom Android Development] tutech:
I feel like I'm not really experiencing problems due to WiFi sleep. I also feel like there are other problems with the Katana kernel in terms of interactivity that manifests in choppier scrolling in the launcher and browser compared to the stock kernel. Not to mention the EGL ERRORs and libjpeg.so errors in logcat when using the browser.

So, it is safe for me to reflash the wifi 3.2 system and boot image from http://xdaforums.com/showthread.php?t=1165998 to restore the stock kernel for my Xoom? Or could this cause other problems that I'm not forseeing?
[Xoom Android Development] okantomi:
It sounds like you are very well prepared, but I don't think you have to go back to stock 3.1 to flash stachre's modded 3.2 update and the new Tiamat Katana kernel 2.0.

Just follow stachre's instructions. You may have to wipe user data, but only if you get into a bootloop. Otherwise, wipe the cache before rebooting , then if all goes well, you can get back into recovery and flash the kernel.
[Xoom Android Development] okantomi:
I think there is something going on that's not related to the kernel. Hionestly, I'm not experiencing any of those issues. Perhaps you had a corrupted or incomplete file download. I would advise that you download again, and reflash the kernel before trying to revert to stock, unless you can just restore a nand backup.
[Xoom Android Development] LynnL:
Ok... I will give it a try tonight. It would be easier not to have to go back to stock 3.1 first. Thanks very much for your help.
[Xoom Android Development] okantomi:
I think you've got it...let us know how it goes.
[Xoom Android Development] icecreammm:
Thanks for the kernel! I went from Tiamat 1.1 rom to Android 3.2 with Katana Kernal and I was afraid that I couldn't connect my external drive anymore, but eventually I found I can mount my 640GB 2.5 inch drive with USB Mass Storage Watcher OTG!

In root explorer I created a new folder /mnt/extdrive and could mount my drive without a problem. Then in a file explorer I only have to browse to the extdrive folder and voila, there are my files.

I notice not all drives work with USB Mass Storage Watcher OTG, for example my USB Thumb drive 4GB, the software force closes.
[Xoom Android Development] Nusince:
Katana 2.0 will NOT run on Honeycomb 3.0, 3.1, or Tiamat 1.0 or 1.1. This kernel is for Honeycomb 3.2 ONLY. Running this kernel on an older OS will result in bootloops like you are experiencing.
[Xoom Android Development] MrGinger:
Seemed to have missed a trick along the way... can someone let me know what folder i need to create under mnt\sdcard\ in order to be able to access my external microsd card?

Do i need to make a symbolic link to mnt\external1?

Only ask as poweramp only uses music folders under \mnt\sdcard!

Thanks
[Xoom Android Development] publicanimal:
I am not experiencing random reboots, instead I've been experiencing random shutdowns. It seems like every time I pick up my Xoom to do something, it's powered off even though I never manually shut it down.

Like you, the issue is persistent regardless of whether I am using OC GPU version or the Stock GPU version. Until there's another update I'm going to stick with the stock 3.2 kernel.
[Xoom Android Development] publicanimal:
Are you running Android 3.2? If so, you don't need to create any folder, SD contents can be found in /mnt/external1. Google enabled the SD card with 3.2.

It sounds like you'll have to put your music files on internal storage to use that app. As a Xoom owner, shouldn't you be using Google Music anyhow? :)
[Xoom Android Development] LynnL:
Ok, running into an issue. I rebooted into clockwork mod, but it's not seeing my external SD card at all now. It sees the internal SD card as the SD card. Under Mounts & Storage there is no option to mount the SD card (or unmount either).

This is very weird as it saw the card fine last week when I rooted.
[Xoom Android Development] Lolento:
Yes, please post how it goes after reflashing cuz i'm getting random reboot as well.

The thing is that it only reboot when the tab is sleeping and idling....don't know what's going on here

I ran a stress test on my tab for an hour and no errors....during heavy use, no reboots....but it reboots itself when idle...
[Xoom Android Development] Namheul:
Have since reflashed the old kernel and its back to normal. How do I flash this new kernel if I have 3.1 with the 1.4.5 kernel?
[Xoom Android Development] Nusince:
Please go back and read the OP and my previous post. This kernel WILL NOT RUN on Honeycomb 3.1. ANY attempt to flash this kernel on Honeycomb 3.1 WILL RESULT IN YOUR XOOM FAILING TO BOOT.

Again, DO NOT flash Tiamat 2.0 Katana on Honeycomb 3.0, Honeycomb 3.1, Tiamat 1.0, Tiamat 1.1, or any other HC 3.1 based rom. It will NOT BOOT.

tl;dr : Tiamat 2.0 Katana DOES NOT RUN ON HONEYCOMB 3.1
[Xoom Android Development] bwcorvus:
So let me get this straight, tiamat 2.0 doesn't run on honeycomb 3.1?
[Xoom Android Development] Nusince:
Correct, Tiamat Kernel 2.0 Katana does not run on Honeycomb 3.1
[Xoom Android Development] ryan562:
Remember this a Kernel. The OP states this Kernel, Tiamat 2.0 will NOT be compatible with android 3.1.
[Xoom Android Development] okantomi:
Did you update to version 4.x.x.x of CWM recovery since last week? That version doesn't recognize the external sd card.
[Xoom Android Development] LynnL:
Not... intentionally? But I had to try two different root methods, so one of them may have updated... anyway, yes, I'm running 4.0.0.4

If I put the update files in the root of the internal "SD" will that work?
[Xoom Android Development] Namheul:
Sorry what I meant was how do I get 3.2 when I have tiamat 1.4.5 and 3.1?

Also, in the op it says under the installation instructions that you need to have android 3.1 which is why I thought I could flash it.
[Xoom Android Development] okantomi:
I guess that would work but maybe you can just get back to your previous recovery version. I think that you can do that from Rom Manager. Scroll down to All ClockWork Recoveries and choose an earlier version and install that. You should have the ability to flash from your external sdcard back. You may still have to go to solarnz' thread to get the latest tiamat recovery.
[Xoom Android Development] fsunoles157:
Sweetness this is badass
[Xoom Android Development] Nusince:
No. Use the recovery from Solarnz 3.2.0.0 R4c. This will address your sd card issue
[Xoom Android Development] LynnL:
Okay, that's what I did, and looking at ROM Manager, I'm pretty sure it's what did the sneak update to CWM.

I am updated and re-kerneled, and the Xoom boots :)

Two things I've noticed --

-- I seem to have lost the OTG ability. The USB Mass Storage app says the drive is mounted (same one I was using before) but I can't see it in Astro or Root Explorer.

-- Videos in the Gallery and stock Video app -- even ones that have not moved -- seem to be hosed. If you tap them, the screen darkens a tad but nothing seems to happen. The path shows correctly when you click "i" though. I can still open the files in MoboPlayer but it's nice to have a working Gallery.

Thanks again, okantomi, for getting me going on this.
[Xoom Android Development] vsc:
Perhaps the absolute clock frequencies are not completely meaningful, but version 1.4.4 of the kernel was able to run at 1.7 GHz on my Xoom without any issues. With 2.0.0 at 1.7 GHz I get lock ups especially using the web browser. At 1.6 GHz the tablet is solid with no issues.

Was the voltage or scaling of chip subsystems changed between 1.4.4 and 2.0.0?
[Xoom Android Development] Psychokitty:
Why are people posting that they have tiamat 1.4.5? Is 1..4.5 called by another name? Where is it located for download? Can you over and under volt with it? If so, is the table correct with SetCPU? Does it work for 3.1?

Sorry for the barrage of questions but I've been waiting for an update that will allow 1.4.4 to be undervolted properly via SetCPU.

I've spent a lot of time getting used to and setting up my Xoom on 3.1, and there isn't enough to be gained from upgrading to 3.2 for me to have to reconfigure everything from scratch. It still feels like I finally just got everything set to my liking.

I was told to load Steady's 1.2.3, which I did, but the voltage table is reversed, and my OTG acts differently.
[Xoom Android Development] ChadH42:
I am having no issue with v2.0 oc.
[Xoom Android Development] Lolento:
Setting wifi sleep to never worked for me too to resolve the random reboot during idle problem

I checked it by checking my recently opened app button....no reboots for a day already.

How did you figure that? Is that a known issue?
[Xoom Android Development] Marshall1975:
Bigrushdog

Im having an issue with kernal 1.4.4 on a UK 3g xoom running 3.1 Australian rom. The kernal installs fine but if I try to go into storage under settings it just forces close every time. The same happens with launchpad which is based on this kernal. I wondering if you have come across this before or know of any reason why its happening.

Cheers
[Xoom Android Development] CraigQ:
A huge thank you to the devs. Running like a dream oc at 1.5 interactive. Came across from Team Tiamat 1.0 in 2 steps - first to rooted stock 3.2 (full wipe in CWM for that move) and then just straightforward move to deodexed ROM and stock GPU Katana in one hit without the need to wipe. Followed the OPs (after waiting for initial updates) and they were all spot on. Great team working on all of this - very happy to have moved from that i-thing!
[Xoom Android Development] RasputinAXP:
Call me a guinea pig, but I just bumped to rooted 3.2 and threw Tiamat 2.0 on there with the stock GPU settings. Gonna run all night and see what happens. Thanks gang!
[Xoom Android Development] kurttrail:
I know the answer. ;)

Sent from my Bolt
[Xoom Android Development] BigBadBuddy:
Two questions:

1. Has anyone had an issue with serious screen flicker when using the notification tray? I fixed it with a re-flash of the OC'd GPU kernel, so I'm sure it's a fluke.

2. Other than gaming or other graphic intensive use, is there really a need for the OC'd GPU kernal for the average user? I need to play HD video once in a while, but would I really see a difference? I switched to the stock GPU kernal, but I'm just curious.

Thanks to the devs for all of this!
[Xoom Android Development] tasomaniac:
device going crazy

I had upgraded HC 3.2 yesterday. And I have just installed Katana 2.0.0, things was going well. I had also "USB Mass Storage Watcher OTG" program installed before the new kernel. When I disconnect USB cable from the PC, my Xoom gone crazy. I had to reboot. I have just uninstalled this program and things are OK now.
[Xoom Android Development] okantomi:
There may be some incompatibility with that app and the 3.2 update/Katana 2.0 kernel.

It's not working for me anymore and some are reporting force closes when they try to mount a thumb drive. It had been working...maybe there was an app update that caused the problem.
[Xoom Android Development] bigrushdog:
Wow you got one heck of a combination going on. You would have to produce a logcat of the fc so I could see what's going on. I'd hang tight for a couple days for our 3.2 rom release. Also we have a new kernel to go with it. And the new kernel is rock solid stable with killer battery life. I I went three days and had 20% left.
[Xoom Android Development] okantomi:
Yes!!! The Team Tiamat productions have been unbelievably great. Well worth waiting for. You guys have built up some fierce brand loyalty!
[Xoom Android Development] Marshall1975:
Bigrushdog

Thanks for the quick reply. Lol I know but its the only way to get a working 3.1 with fully working 3G on a UK 3G xoom. 3G does for the most partwork on the US rom with a bit of messing but the signal bar neverworks and its prone to just losing connection. Pardon my ignorance but how do I get a logcat for the force close. Its a pain as everything else works great but im unable to unmount the SD.

Have to admit though will have myarm twisted to try out the new rom I think when its released.

Cheers
[Xoom Android Development] jkrueger35:
Camera Force Close

My camera is force closing as soon as I take a picture. The pictures are saving to the internal, but they aren't found by going to gallery. The gallery shows no images available. Help please. I read some have problems when "Store location" is On. Well, it is Off.
[Xoom Android Development] Marshall1975:
Bigrushdog

Ive worked out how to get a logcat for you. Have attached it for you to have a look at when you get a chance.

Much appreciated

Thanks
[Xoom Android Development] Epedemic:
Seems this kernel gives me reboots if wifi sleep is set to screen off... Just like 1.4.5 :/
[Xoom Android Development] solarnz:
This is a known issue. I have been able to replicate but is giving me problems debugging it.

If you set your wifi sleep policy to never it will be rock solid.
[Xoom Android Development] dew.man:
How does that effect battery life though?
[Xoom Android Development] Brolloks:
Great, thanks, makes sense why mine goes into reboot while in sleep mode
[Xoom Android Development] bjarnia:
I have wifi always on and my battery life is very good. It's basically dictated by screen use.. If I don't use the display it lasts for days. Wifi is at 5% battery usage for me right now, less than "tablet idle"
[Xoom Android Development] BigBadBuddy:
Anyone have any thoughts on this?

Thanks
[Xoom Android Development] mcdevtingz:
Hey, I have a uk wifi xoom running us 3.2...

I'm new to xoom roming... advantages of this ROM over stock?

Also how to install?
[Xoom Android Development] thebomber:
one question please, i installed your kernal, and installed set cpu, i dont find anything above 1 ghz , whats wrong,

as well as one question does the kernal have some kernel modules... like option.ko and wwan.ko added or not as im looking to let my huawei modem work on the xoom, and if you could tell me how to add them

thx alot
[Xoom Android Development] okantomi:
Tiamat Katana 2.0 is actually a custom kernel and not a rom, but the rom appears to be in the final testing phase. This kernel's biggest advantage over stock is the ability to overclock the cpu and gpu beyond stock speeds.

Are you unlocked and rooted? If so, just follow installation instructions in the OP. If not, you need to be rooted.
[Xoom Android Development] mcdevtingz:
I am unlocked but not rooted... how do I root? Also when applying this is wipe needed? (Sorry for the questions we were all newbs once! )
[Xoom Android Development] playya:
I would say if you found this thread then it will be easy for you to find the thread that corresponds to your particular Xoom for rooting. Look in the development section where we are right now and alongside this thread there are quite a few that say (Root) then the different models of Xoom, I suggest you find yours read the OP and give it a go...

Good Luck and make sure to read it over several times before proceeding
[Xoom Android Development] playya:
did you install the right one. sounds like yo installed the stock kernel and not the overclocked one
[Xoom Android Development] thebomber:
i did install the oc one, dont know why its not showing though to over clock
[Xoom Android Development] okantomi:
The gpu overclock is not user controllable. It is just overclocked to 400ghz? iirc.
[Xoom Android Development] davidsos:
Since be said, "i dont find anything above 1 ghz" I think he might be referring to the cpu clock since he's finding 1 Ghz and below. I've seen people botch an install and not realize it. He might be running stock android.
[Xoom Android Development] Alxoom33:
New 3.2 ROM, AWWWWSOME!

Awsome!!! Can't wait for your new ROM. Been using the deodexed 3.2 ROM v 1.2 with your 2.0 oc kernal running all day at 1.504 khz. Heavy office use of citrix word ect. Typing has been pretty stedy w/o much lag or stutter. No forced reboots or freezes.

Btw, do you know of a fix to be able to use Netflix on the Xoom or google movies from the mkt. It says it dosen't play on rooted devices. It would be great to be able to use Netflix ect n the Xoom.:D

Keep up the great work. Looking forward to your new innovations in tour 3.2 ROM an beyond.:)
[Xoom Android Development] thebomber:
well its a stock and rooted and i have the oc kernal, all i want is oc to 1.5, but set cpu had a maximum value of 1ghz, and when i go to voltage tab, it crashes

why is this happening
[Xoom Android Development] OniKyanAE86:
Is OTG Host features included in the "Katana" kernel? I no longer see the OTG folder and can not access memory card readers and external hard drives like I was able to with 1.4.4 using my host adapter. Am I missing something or if its possible, can this feature be added back in the next update?
[Xoom Android Development] LynnL:
I have the same issue.

Also I am unable to view any video from the gallery -- it sees the files but is unresponsive when they are clicked on.
[Xoom Android Development] okantomi:
LynnL.

About the videos in the gallery, what players do you have installed? When I choose all videos I then choose movies (that's what they're filed under) then none are grayed-out. When I choose a video, I get a drop down box with every video player I have installed, and I usually choose mobo player or rockplayer lite but the stock video player works too. You don't have this drop down box to select your choice of players?
[Xoom Android Development] LynnL:
I have moboplayer and rockplayer installed. Videos play fine in those. I can see the videos in the gallery, but when I click on them, nothing happens, no selection dialogue, nothing. Same if I click on the file in Astro.
[Xoom Android Development] OniKyanAE86:
Well I don't have any video issues. I use Rockplayer and all videos play fine, even video files compatible with the Zoom play in my gallery...... wonder what could be causing those issues. I just fixed an issue with my market not letting me download and install free or paid apps. Had to flash back to 3.1 and flashed to the newer version of the v1.2 Honeycomb 3.2 deodexed/zipaligned update and all started working again. Noticed the market issue after I restored my apps and system data with Titanium Backup.
[Xoom Android Development] okantomi:
I just wish I knew more about the way everything works together (or in this case, doesn't). What I have often seen is an incomplete or corrupted file flashed, which causes strange problems, and the solution, like the previous found is usually to re-download and re-flash the file that went awry. The problem may be due to a specific setting change or an app incompatibility. In this case, a step by step investigation/testing has to be done to try to isolate the problem. Often it's something simple that you'd never think of.

Where are your videos stored? Are they in your internal storage or on an external source (sdcard, etc.)? I really can't think of why your videos in internal storage would not play through the gallery. Maybe someone else can add to this discussion.
[Xoom Android Development] Sistema1927:
As to the camera/video/images issues,, this is what I am seeing after updating to 3.2 configured as seen in my sig line:

1) Taking a picture using the camera results in a force close.

2) The Gallery is showing no images or videos, just empty boxes with the number of what should be there.

3) Clicking on an image (I have only tried .jpg) in any file explorer (Root Explorer, OI File Manger, Astro, etc.) causes the screen to dim. It remains in this state until you hit the back button.

4) File managers correctly display thumbnails for the images.

5) Videos play in Mobo and other video players if you select them from within the app.

6) Netlix and Hulu are working. Netflix in the new app, Hulu in Dolphin browser.
[Xoom Android Development] okantomi:
Could your camera and gallery issues be related to the oc gpu? Mine is oc'd too, but each Xoom has different tolerances.
[Xoom Android Development] Sistema1927:
Could be. I was using the OC GPU on 1.2 w/no problems, but anything is possible. Only one way to find out, time to grap the standard kernel (after a full nandroid back-up.)
[Xoom Android Development] OniKyanAE86:
I'm using the OC'd version and I have no issues...... Camera, gallery, videos, etc. are all ok. Would be perfect with OTG Host features back in this kernel.
[Xoom Android Development] Sistema1927:
Flashing the standard kernel didn't change anything, but thanks for the suggestion.

I have discovered something, quite by accident. Even though the camera still FCs, I am able to view images by changing screen orientation after receiving the greyed out screen. Changing pprtrait/landscape allows the image viewer selector to become available and then allows images to be viewed in any viewer, either portrait or landscape.

Also just discovered that the camera actually saves the photo prior to FC, so thhis is more nit than problem (at least for me.)
[Xoom Android Development] LynnL:
And... I went to poke around some more and my gallery is suddenly working again. The "complete action using" dialogue comes up again when a video is clicked, and the videos play in the gallery. Go figure!
[Xoom Android Development] okantomi:
I have the OTG host feature with the Drive Mount app. Works great.
[Xoom Android Development] okantomi:
This is a known solution to the grayed-out default app picker. Force a redraw of the window by changing the orientation. I already posted this solution on one of these threads.
[Xoom Android Development] blee00:
I have a quick question.

I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).

After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.

Is this it for my Xoom? Should I prepare my mind to buy a new tablet?

Other than my lack of patiance, nice work with the kernel =)
[Xoom Android Development] Sistema1927:
Probably not. Did you wipe prior to flashing?