yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] nsxz0o7:
Anyone with us wifi get this to work? If so did you have 3.1 ota or did you upgrade to 3.1 brds method? I really want to flash the rom but dont want to go through the hassle of fixing if it boot loops..
[Xoom Android Development] comagnum:
i have a wifi only and flashed using brd's method. No issues. Just follow his instructions and you'll be fine. Read through and follow to the t. Never had a bootloop, never had any snags, nothing
[Xoom Android Development] kymikes:
Thanks. Actually found a different way by flashing back to Tiamat 1.4.2, fixing my Setcpu issue (I had clicked on 'set on boot' without knowing better). Then was able to flash back 1.4.4 and to this this rom. Now all is well. I can relate to your issue of restoring 324 apps thru Titanium. I started like that on my DroidX. This time I decided that I would work through the kernals & ROMs before I started loading any apps that weren't necessary. Getting 'smart' by trial and error is painful and time consuming but these forums grow faster than I can read them. Many thanks again.
[Xoom Android Development] pantherzfinest:
i like the new rom. Works beautifully. Didn't even have to wipe completely (xoom wifi). Can someone fix the battery life? Its very draining. Otherwise this is probably the best setup on the whole internets.
[Xoom Android Development] jonbot81:
That is just what happened to me. I tried to restore a nandroid backup with Clockwork (4.0.0.1) and now I am stuck on the Motorola logo. I think it messed up the boot img restore. I tried reflashing tiamat's boot img from his kernal page, as that was the one I previously had, but no go. I am running out of ideas.
[Xoom Android Development] Sic123:
i did the same thing i had solarnz recovery still on my internal memory and flashed that and then reflashed the rom and it fixed it so if you can adb push his recovery to the internal storage you should be able to flash it and fix your problem
[Xoom Android Development] Almighty1:
That should work too except what does the 1.4.2 Tiamat kernel contain that unsets the set on boot? After flashing Tiamat 1.4.2 to fix the Setcpu issue, you should actually flash this rom first, followed by the Light on fix and then the 1.4.4 Tiamat kernel since if you flash back to 1.4.4 first before the ROM, the rom will basically replace the 1.4.4 kernel you had with the standard tiamat 1.4.4 kernel.

Titanium Backup restoring isn't the problem except I always install each thing one at a time so it will take atleast 2 days if not more before I restore it all and ofcourse what I'm more worried about is it breaking market links. Wiping is time consuming since that's like a band-aid approach of fixing things which is just like a computer where they will tell you to format to fix problems but getting everything back after formatting is a time consuming process.
[Xoom Android Development] Sic123:
why not batch install titanium backups?
[Xoom Android Development] Almighty1:
You're taking the wrong approach since the boot image is only to get it to boot and it's the recovery that's messed up so you need the help of fastboot to fix the recovery and then you can restore nandroid from the external sdcard.

What you should do is:

1) Turn the Xoom off

2) Connect the MicroUSB cable to the Xoom and probably the power too just in case

3) Hold the power and vol - until it says starting fastboot

4) Download the clockwork mod recovery 3.2.0.0 .img file and follow instructions in method #1 in this thread:

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

And then you should be good to go.
[Xoom Android Development] Almighty1:
After using titanium backup for a year, I have always manually backed up each thing individually after checking to make sure it runs or whenever I update the config for the app. Doing the batch can be good if everything works but I like to make sure each app works correctly first so there are two ways to do it:

Either

1) Manually restore each app individually, run the app to make sure it works

2) Batch install and then still have to make sure each app works
[Xoom Android Development] Almighty1:
adb push won't work if he can't boot into the OS completely since he's stuck at the

Motorola Dual Core logo so the fix is really the same way as flashing the img version of clockwork recovery modified by solarnz by getting into fastboot and then using adb's fastboot to flash the latest 3.2.0.0 recovery img file to the Xoom and then it should all work. Ofcourse, if one can't get into fastboot, that's a more serious issue which I am not sure can be fixed or not since I'm sure one can use the bootloader patch which is just the HC 3.1 Xoom bootloader in BRD's HC3.1 upgrade without using fastboot thread.
[Xoom Android Development] jonbot81:
I did this should I try to restore again?

And the 4.0.0.1 clockwork lost sccard support so my backup is in the data folder. so I have to pull it then move it to sd card. What a pain.

Thanks for the quick responses
[Xoom Android Development] bigrushdog:
Next release, I'm gonna fix all this wiping nonsense. It will be a simple process of flashing rom, flashing your appropriate service package, and rebooting. My script will take care of everything. There's too many device configurations for one set of instructions.
[Xoom Android Development] rschenck:
Titanium Backup is a great way to preserve data for many apps, but I agree that the batch restore should be avoided. If you must batch restore, use the Restore Missing Apps batch command.

However it is best practice to restore apps one by one, only restoring app + data when there is a reason to. Also this gives you a chance to consider whether you really WANT or USE an app or if you just had it around because you couldn't be bothered to delete it. Think of it as a spring cleaning.
[Xoom Android Development] rschenck:
I think we all assumed the install process would be streamlined in the next versions after you got feedback on how things actually work. That is the purpose of early releases so no worries.

Also it means we can hassle people who install later versions. "You call THIS hard????? When I first installed the Tiamat ROM I had to wipe it three times, use adb on a commodore 64 and solder a special jig to an unused USB port on the motherboard...and THEN I had to sacrifice a cat to stop those bootloopy things! You have it too damn easy, now get off my damn lawn!
[Xoom Android Development] jonbot81:
I got clockwork mod recovery 3.2.0.0 on and ran a restore but no dice. still wont get past dual core logo.

If i have 3.2.0.0 on does it matter if it was put on by the clockwork zip install method or the fast boot img install method?
[Xoom Android Development] nsxz0o7:
Were you coming from the regular 3.1ota? I'm on it so I noticed the dl rom file has verizon on it...just nervous. From the instructions it seems pretty easy, download rom, since I don't have brds Verizon's 3.1rom I should do a factory reset in the rom, then boot into recovery and flash the rom, if downloads don't work then do a reset again in rom.... am I missing something?
[Xoom Android Development] Almighty1:
I think what you should do at this point depends if you want to go back to your nandroid backup or if you want to use this rom. The problem when you restore I think is that when you restore, it's supposed to replace the boot, system, data so what you have in data won't survive.
[Xoom Android Development] Almighty1:
Good points, how do you use the Restore Missing Apps batch command? What I did originally was just copy the Titanium Backup folder from my Motorola Droid 1's sdcard and then went through each item to see which ones work on the Xoom and which don't and then decide on if I want it or not. If I want it, I will just delete the old backup for that app and create a new backup. If I don't want it, I will just delete the backup after uninstalling the app.
[Xoom Android Development] Sic123:
if you can boot into recovery and mount the /system you can adb
[Xoom Android Development] Almighty1:
LOL. I think maybe the better way to do it is to label the versions as Alpha, Beta and then release versions so that people will have a idea of what level of risk they want to take.
[Xoom Android Development] jonbot81:
At this point I would just be happy to get a booting xoom again. Restores are not working. So I guess I could somehow start fresh or load this rom. I don't know.
[Xoom Android Development] Almighty1:
Don't think it matters as long as you didn't try to fastboot on the .zip file since fastboot requires the .img file while clockwork zip should be done inside clockwork recovery's install from a zip file. Did the restore complete the entire process? What you might want to do is do the:

1) Power Off

2) Make sure the MicroUSB is connected

3) Hold Power and Vol - until it says Starting fastboot

4) on the computer, issue the following command:

fastboot -w

After that completes, do "fastboot reboot"

and see if it works.
[Xoom Android Development] Almighty1:
After you do what I mention in post #479, hopefully it works, what you should do is probably do BRD's HC3.1 without using fastboot here:

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

so you will install the HC3.1 bootloader, boot image, system image and then when that works, you can just put this ROM over it if you desire.
[Xoom Android Development] rschenck:
Under the Batch commands you can select Restore Missing Apps or Restore Missing Apps with Data. It is very useful for avoiding problems when a ROM already includes a different version of a program you have backed up, for instance.
[Xoom Android Development] ryan562:
okay guys here's a quick question..but before that here's the following steps..

i went from tiamat kernel latest (with gpu overclock)

then rebooted in to clockwork recovery and did the following steps.

1. flashed the new deodexed rom

2. flashed the 3g fix

3. flashed the charge light-on update

okay after i rebooted, every thing seems to have run normally. i was able to install market apps without any reboots so it didn't seem i needed to wipe.

although it shows the new circular battery, it does not show i'm on rom v 1.0 when i check the settings on "about tablet" option. it still says i'm on kernel 1.4.4 full throttle. android version still says "3.1". but no where does it say that i'm on rom v1.0.

is this normal and did i successfully flash? the only indicator to me that i flashed correctly is the new circular battery icon/gauge and that the UA string on the stock browser seems to have worked as all the homepages show up in desktop version.
[Xoom Android Development] rschenck:
As far as I know, that is normal. If you have the circle battery indicator, then you are golden.

I admit it would be nice to be able to easily check to see which Rom is installed (and will likely be more important as more versions come down) and I am sure indicating that the ROM is installed in Build or Kernel version is on Team Tiamat's ToDo list...but likely way down there near the bottom, right before "Port Windows Mobile 5.5 to Xoom for dual boot"

...maybe after.

It will come in time.
[Xoom Android Development] ryan562:
thanks for the help and quick reply. overall, this rom seems to run faster/quicker then the stock rom. it indeed would be nice to see what rom we're on. since i consider myself a "crack flasher" when it comes to flashing roms :D
[Xoom Android Development] rschenck:
I know the feeling.

How are you liking that Streak? Considering picking up a Streak 7 in a couple weeks.
[Xoom Android Development] Almighty1:
Thanks, never checked out that feature of Titanium Backup. I always double check to see if the ROM has something that is a different version, all those in red before I even do the restore but ofcourse this will help speed up the process.
[Xoom Android Development] phouse1025:
OK I know this may have been asked already, but as most of you guys know the search doesn't work as well as it should in the xda app. But how can I use the SIP and SMS on my wifi only xoom? Is it possible, and what is required.
[Xoom Android Development] kymikes:
From what I deduced was that the earlier version of Tiamat kernel limits the max clock speed. That was my logic. Seemed to work as it came up w/o the rebooting. On your other comment, I don't know what differences there might be between the 2 Tiamat 1.4.4 versions. Hard to tell from my viewpoint which is most current or more advanced from what I could see. Your point certainly seems valid. Thanks for all your help.
[Xoom Android Development] ryan562:
the number of developers are some what lacking for the Streak. DJ Steve (team Cyanogen) is its only major dev and he's done wonders to it in terms of unlocking performance potential.

i have the original streak mini/5" tablet phone. Rooted and with Steve's latest streakdroid build, it runs perfectly, even for an outdated device with an outdated 1ghz snapdragon processor. Quadrant scores went from 800's to higher 2000's.

steve's also done wonders to the bigger streak 7 in terms of performance enhancements from what i've been reading. Dell's StageUI looks nice and all but it seriously bogs down both devices. If you're thinking about getting one, i'd seriously look in to rooting it and installing some of steve's performance mods. Steve is also working on Honeycomb builds for both streaks 5 and 7 as we speak.
[Xoom Android Development] Almighty1:
Makes sense. I just didn't know the speed was still set even when SetCPU isn't even installed anymore. There are 2 versions of Tiamat 1.4.4, one just overclocks the CPU while the other overclocks the Graphics Processor (GPU) as well. The one in the rom is the former. Glad I was able to help...
[Xoom Android Development] Chelseablue:
Well, I finally took the leap after growing a ripe set and flashed the ROM and 3g fix. I feel as if I'm definitely one of the lucky ones as I didn't factory reset and everything worked the first time.

Thanks for all the hard work that went into this, excellent job!

I can't wait to see where this train stops next.
[Xoom Android Development] phouse1025:
Like alot of others my battery has been discharging alot faster than it did before the new rom. Hopefully this issue can be resolved at some point. But other than that the rom kicks butt! Can't wait for future updates with even more options built in. Keep up the great work Team Tiamat, without y'all we would be stuck in the dark waiting on Motorola.
[Xoom Android Development] Epedemic:
Ok yesterday something strange happened... Just want to share it with you in case someone else experiences the same.

I noticed that my thumb keyboard was acting strange on multitouch, so i did a hot reboot via quick boot. Still acting strange. I then did a full reboot, but got stuck on "Dual core technology screen". That persisted, so i flashed a boot.img from the kernel thread. That helped, and the device booted. However after aprox. 5 minutes the wifi dropped, and wifi got stuck in "error" state. Then i tried flashing kernel again, didn't work. Then i booted into recovery and flashed the rom again, works now, and no data lost...

Running Tiamat ROM 1.0 with the kernel that came with it on a UK MZ604 wi-fi xoom.
[Xoom Android Development] solarnz:
Yes, you will get errors if you flash a boot.img from the kernel thread.

This is because those boot images are only supposed to be used for changing your ramdisk and you MUST flash another kernel afterwards.

This is because those boot images don't contain the latest version of the kernel, and the wifi module doesn't work unless it is the version that came with the kernel.

Hope this helps...
[Xoom Android Development] Turkawa:
it is 3.2.0.5 i think.

I downloaded the 3.2.0.0 version and failed to flash it multiple times.

After i flashed it and rebooted it still shows 3.2.0.5

I did the same after your post and stuck at motorola! Data and cache problem maybe

Yes.. exactly this..

like i said.. failed to install the correct version

This method worked just fine..

I re flashed the rom from cwm. Deleted data partition and cache, booted without a problem, then like you did wiped inside the system this time and everything is working smooth for now..

Thanks for this guys..I was not in good shape :)
[Xoom Android Development] okantomi:
Glad I wasn't drinking my coffee!
[Xoom Android Development] thebreezer:
Thanks, I shall give it a try.:)
[Xoom Android Development] Epedemic:
Alright. I do believe that i flashed 1.4.4 after the wifi crapped up... But i honestly can't remember... I was pretty scared that the wifi chip was dead :P
[Xoom Android Development] rschenck:
Don't worry, there is next to no chance you will blitz the hardware, and the Xoom is quite hard to brick (unless you use CWM to try to partition the SD...NEVER DO THAT).

As long as you can get into Fastboot or Recovery, you will be fine.

It is also a good safety tip to keep a working boot image and kernel and the ROM you are using in your external SD card, just in case.
[Xoom Android Development] Epedemic:
Yeah i have always done that on my android devices :)
[Xoom Android Development] lpasq:
Anyone else US WiFi w/Tiamat1.0 unable to load Swype Beta 3.0? For me, Swype Installer only downloaded after UAstring set to Froyo/N1 to register online; but then Swype Installer will not login to download because of fail "data error...bad network connection".

...xoom posted...
[Xoom Android Development] ftgg99:
SU binary broke by itself for me. Also, inordinate battery use with this rom.
[Xoom Android Development] sfld:
What is the best way to return to stock rooted rom with a stock kernel?

i have a 3g model
[Xoom Android Development] davidsos:
A pure stock kernel will not be rooted, the closest to it would be at:

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

This is full root with support for OTG USB and MicroSD. So it's not quite 100% stock.

Otherwise you can go back to the below, then get an OTA upgrade and root that.

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

Good luck.
[Xoom Android Development] crackmulah:
how can i take advantage of internet calling and SMS from my WIFI xoom model?
[Xoom Android Development] andr0id23:
Just flashed the ROM & 3g fix, no wipe, and all is working well. Haven't had a chance to play around, but no problems as of now. Market installs working. Love the battery indicator. Great job and thanks to Team Tiamat!
[Xoom Android Development] davidsos:
Skype works with this ROM, I just made a test voice call to my landline. As far as texting goes, I don't think there's a simple clean solution. If you are verizon wireless customer, you can use their browser/web based SMS/MMS message from your Xoom. I just tested that and it worked as well. Perhaps you can find a similar service with your carrier.
[Xoom Android Development] bigrushdog:
See guys! I knew my rom worked! Lol. Glad to hear things went smooth.
[Xoom Android Development] TsaiKimon:
Question for you BRD. Does the Ua string hack mean its impossible to use any other UA string besides desktop? If not I can't seem to do it. If so is there a way to simply have the UA string default to desktop but still be switchable which I feel is still necessary from time to time?

PS. Love the kernel and rom, thanks for all the hard work :-)
[Xoom Android Development] davidsos:
Yep, it runs nice and smooth, way better then stock. Motorola should outsource Xoom development to you and the team.

Did you have a nice time away this weekend?
[Xoom Android Development] dowenprs:
The install went smooth as could be for me as well BRD, i've been LOVING the rom, so fast! Can't wait to see what you have in store next!

I do have one question though, what version of CWM recovery do you recommend using? I saw they had an update through RM, but i haven't updated yet.

Peace

Dan
[Xoom Android Development] ClydeB1:
+1 I find the treatment of the usb host in this rom to be more cumbersome than the BRD HC3.1 update.

I don't know if it's just me doing something stupid, but I found that under the BRD HC3.1 update rom, I could just plug my Xoom into my pc via usb and have access to all the standard folders on my Xoom, ie both internal sd card and external sd card and could just drag and drop from pc to copy files across. Then plug in a otg cable and a flash drive and it gets picked up and automatically mounted and can again easily move files around. Then connect my 1TB (NTFS) hdd, run NTFS Mount (or the new Drive Mount app), and the hdd is picked up and can be mounted with access to all files again.

On the new rom and using the USM Watcher app from dinomight, this is all very different. First after installing this app, when connecting to the pc I get the option to mount as a disk drive, but then I only have access to my external sd card and can no longer view the internal sd card. So I uninstalled this app, and also had to restore to my HC3.1 nandroid backup and then re-installed the new rom. Ok, now I could at least access my internal sd card again. Then trying to run NTFS mount resulted in immediate FC as mentioned above. I provided a logcat of the FC to hellcat and he fixed his latest version of Drive Mount (available via Market) and it now no longer FC's, but it does not pick up any drive connected to my otg cable.

Restored back to the HC3.1 rom again, installed Drive Mount and viola, all works perfectly again.

Please team Tiamat, can you revert to the same usb host methods of the BRD HC3.1 rom as this is so much more versatile and useful than the current methods IMHO, because no matter how many tweaks etc are applied to the rom, ease of use for daily tasks is much more important. Again, as mentioned I don't know if I just have done something wrong, but can't get this to work simply. I'd love to have the best of both worlds :D
[Xoom Android Development] jonbot81:
Thanks for the replie, last night I gave up. This morning I did a wipe inside clockwork then tried the restore. And that worked. So I am back up in action. I hope anyone else who had this problem finds these posts.
[Xoom Android Development] okantomi:
Don't do it!!! I'm saying this because it messed me up big time and I had a heck of a time fixing it. That update (4.0.0.X) is bad news for the Xoom.
[Xoom Android Development] cam30era:
I have no problem seeing and accessing my Xoom files from my PC (Win X64). Wifi only Xoom, running ROM 1.0. No other tweeks, nor any apps for file management (except Root Explorer on my Xoom).

I just plug it in, and Windows Explorer immediately recognizes the Xoom with a popup to open Explorer.
[Xoom Android Development] ClydeB1:
It does for me as well (after uninstalling the USM Watcher app and reflashing the rom), but the problem is I can't access flash drives or hdd via the otg cable any more which I could on the old rom.
[Xoom Android Development] cam30era:
Curious. I am able to access my Incredible's SD card with a host cable, and USB tether it as well. I can't check my flash drive, because I loaned it to a friend with some files he wanted, and don't have it back yet.
[Xoom Android Development] ClydeB1:
Yes, FAT32 format will work automatically but not NTFS.
[Xoom Android Development] REHolt218:
Both UMS Watcher and Drive Mount have new versions out. For UMS Watcher you have to get the otg version from the market, not just an update of the old version.

So far Drive Mount works better, but the developer is working to solve problems with UMS Watcher as well.

This seems to resolve my problems with USB HDD's on the Tom very 1.0 drop 2.
[Xoom Android Development] ClydeB1:
I tried the new versions of both apps. I agree that Drive Mount seems the better of the 2. On Tiamat Rom 1.0, Drive Mount however doesn't pick up any drives that I plug in. Works fine on the older rom though. Perhaps I need to reflash Tiamat 1.0 and check again but as I'm off on an 11 hour long flight tomorrow and need some in-flight entertainment, I will probably wait until I get back.
[Xoom Android Development] Almighty1:
Interesting, I only started using adb recently so I thought adb required the OS to be fully loaded, atleast one would think it does in order to do all the shell stuff but probably it's just like Unix in general, single user mode so everything just isn't mounted yet.