yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] mutiny:
Mine are in my sig. 1.4.1 is noticably faster since 1.3.2. In Quadrant, I get north of 3200. Always. That's the very minimum. I get 3400+ easily.
[Xoom Android Development] ericdabbs:
It was weird cuz my linpack scores were terrible using 1.4.1 with getting values of 38-41 at 1.5 GHz (I made sure I was using performance governor from droid OC before conducting test). I just reflashed 1.4.0 and my linpack scores are now back to 65. Also my quadrant scores were normal at around 3400 for 1.4.0 and 2200-2500 for 1.4.1.

Maybe it is just my machine but since I don't have the changelog in 1.4.1, I am going to stay away from 1.4.1 until the next version.
[Xoom Android Development] s_piccand:
Did you try to rescan SetCPU and set it again to 1.5Ghz because it look like you are running @1Ghz.
[Xoom Android Development] Archangel:
Linpack was around 63-65
[Xoom Android Development] ericdabbs:
Actually I use droid overclock and not SetCPU as my overclock program. No I made sure I was using 1.5GHz with performance governor so that it stays 1.5Ghz at all times. I already reflashed to 1.4.0 about 20 mins ago. I may reflash to 1.4.1 if I am curious but I think I'll just wait until the next version of Tiamat kernel before updating.

I don't think there are any significant changes from 1.4.0 to 1.4.1 that I have to update. I don't know what BRD means in his 1.4.1 changelog of "Google AOSP updates". If someone can enlighten me on what those changes I appreciate it.
[Xoom Android Development] bigrushdog:
I updated OP with minor changelog and a modpack section. Regarding changelogs, here on xda, I will only be posting any major updates such as a Linux version upgrade. Please understand that most changes are highly technical in nature and most users will have no idea what they mean. That is why I encourage the more advanced users to visit my Githhub repo to see commit history. However, I do apologize for the lag on updating changelog here.
[Xoom Android Development] bigrushdog:
Dude, you can't run performance governor all the time. It will cause serious lag and jitter. Bump it up to performance when u wanna benchmark. Then bump back down to interactive afterwards. We have a lot of work to do on cpu scaling. Trust me, I know. Let me clarify a few things you mentioned. AOSP stands for Android Open Source Project. AOSP is the master code repository for everything android. Everything from the rom, sdk, tools, kernel, and other things are all based there. Hardware vendors, CyanogenMod, kernel devs, and anybody else can "fork" source from there. Also, anybody can contribute if you are good enough. For example, Google just forked TeamWin's wimax code into AOSP. Contributors genereally include software engineers from Google, hardware vendors like HTC and Motorola,

Linux kernel developers, and others. The tegra2 kernel source is based there, and is where much of the updates to Tiamat and Cyber's kernel come from. As the software engineers "commit" or publish code to the repo, we grab it and add to our repo's. However, we usually don't grab everything they post up there. If there is a commit that we will not enhance kernel performance, we will not grab it. For example, the "L2 Cache" patch was commited but then reverted. We did not grab the revert because the patch significantly improved the device performance. I hope maybe that clears things up just a little. :cool::cool::rolleyes::rolleyes:
[Xoom Android Development] Archangel:
Does the new modpacks allow the charging light go to green when fully charged? Some of the modded kernels out allow the light to stay on but not green when fully charged?
[Xoom Android Development] Land Master:
Heads Up

Repository Link in Post #2 appears broken.

As Always..... Thanks for your contributions BRD!
[Xoom Android Development] BGrutter:
According to the OP, "4. Your SD Card will now be mounted on your computer. Drop the kernel onto SD Card."

Sorry if this is a stupid question, but what SD card are you referring to, the Xoom HD or the True-SDcard? I ask because I'm looking Flash 1.4.1 from 1.1.6 that I just got after finally rooting. My primary reason for Flashing is to get SD card support. I've tried going the adb cmd route, but I keep getting errors. I have little experience with adb.

So, what I'm wondering is how am I going to get my Xoom to recognize the True-SDcard slot to update to a Kernal that allows access, from a Kernal that does not? Hope that wasn't too confusing.
[Xoom Android Development] thefredelement:
Put clockworkmod recovery on the xoom, boot in to recovery, mount the sdcard, it will be the real sdcard you put in the xoom. Then drop the kernel on to the sdcard, back out to the main menu in clockwork and install the zip.
[Xoom Android Development] BGrutter:
Just tried. It says, "Error Mounting /sdcard!

I'm assuming that is because I still have a pre-sdcard support Kernal. I feel like I'm doing everything right in ADB, but I must not be.
[Xoom Android Development] bigrushdog:
You have to actually put the sdcard in the slot. Recovery does not see internal storage.
[Xoom Android Development] BGrutter:
For reference, what I'm currently running:

Kernel: 2.6.36Tiamat_Xoom-v1.1.6

So, even though I'm running a pre-1.3.0 Kernel, CWM should be able to recognize my microSD card? I have put it in the slot in the Xoom, entered Recovery (via Rom Manager), selected "mounts and storage", and selected "mount USB storage" (first time selected "mount /sdcard").

Now, I'm getting the message:

"E: Unable to write to ums lunfile (No such file or directory)"

Have I done something wrong?
[Xoom Android Development] Land Master:
Try entering recovery through adb. I recall people having issues when trying to start it through ROM manager or Quick Boot.

Just a thought hope it works.

Edit: Also, what kernel you are running has no bearing on this. CWR has a kernel all to itself that loads when you enter recovery. Excuse my basic understanding of this and my terminology but that is the jist of it.
[Xoom Android Development] forsaken82:
so after using the one click root method my sd card is being read. so does thaqt mean i can just flash 1.4.1 straight off my sd? i never had to install a different kernal, im not sure if that is included in it now.
[Xoom Android Development] BGrutter:
Apparently, some of the newer packages DO come with that ability. I, on the other hand, must have used an outdated method. BOOOOOO.
[Xoom Android Development] BGrutter:
Here is a quick screenshot of what I'm encountering. I've included both the cmd window and the windows explorer to show that I'm entering the correct directory. For some reason, it doesn't like my "adb" command.

Am I super stupid and missing the obvious? I've opened the SDK Manager and Updated EVERYTHING, even all the old 1.5, 1.6, etc BS. I feel like a bit of an idiot for not figuring this out on my own. I MUST be missing something simple.
[Xoom Android Development] mulletcutter:
Go to theunlockr and u can find the adB file u need to make adb work.

XOOM
[Xoom Android Development] mulletcutter:
Idk maybe im just not reading it right, flashed the module then 1.3.2 went to root explorer but couldnt find my removable sdcard, had external under sdcard but it was empty and couldnt transfer any files to it, also just flashed 1.4.1 and the same. Plus i only got 2511 on quadrant on 1504 performance.

XOOM
[Xoom Android Development] BGrutter:
That directs me to this post. That was the root method I used. It came packaged with 1.1.6. I checked Post #3 for the "changelog" and saw that he's stated he's pulled something. Is that my problems? Is the latest version (packaged with 1.4.*) no longer available?
[Xoom Android Development] Land Master:
You have not installed the ADB component. That is why it isn't working. See my guide in the Q&A Section:

Link Here

Perform step A-3.

Edit: I read where you stated that you opened SDK Manager and that is indeed where you need to be. I checked settings and do not see any place to change the path for the installed packages so I'm not sure what happened. You do NOT need to install "everything".

Play around in there until you achieve adding an "C:\android-sdk-windows\platform-tools" directory that should contain the adb executable OR attempt to locate the adb file as recommend by others above.
[Xoom Android Development] BGrutter:
Thanks for trying to help. I didn't see your response, but I got it figured out. I have 13 tabs open on my Chrome Browser right now. I ran into every hick up imaginable. I ended up have to go into my "Environment" settings on my laptop to change a "path" (whatever that means). Odd thing, what I had to swap out was a command to "Gmote" which is an app I use to remotely control my laptop. Oh well.

Add to that, I had to write the whole directory for each ADB command. For instance:

Instead of typing this: adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko

I had to type this: adb push c:\android-sdk-windows\tools\system\lib\modules\scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko

That was like 7 times. Anyway, it worked out in the end. Now, to upgrade to 1.4.1. Perhaps another time. I have to get up for work in about 7 hours, work for 3.5 hours, and then catch a flight to Florida. Tomorrow is going to be EXHAUSTING. Thanks again for helping out.

GOOGLE.com is your friend ;)
[Xoom Android Development] c0t0d0s2:
I went 1.3.1 -> 1.3.2 -> 1.4.0 -> 1.4.1

I had random reboots from the beginning.

Just for the heck of it, I did a wipe and reroot, and flashed 1.4.1 from kernel manager, and I still get reboots. (or, I have gotten at least one since doing it, but will keep an eye on.)

EDIT: By wiping, what i really meant to say was, I flashed via fastboot the generic, stock image, then rerooted and reflashed tiamat.
[Xoom Android Development] mutiny:
And you were the one who said you don't OC, right?
[Xoom Android Development] c0t0d0s2:
correct, no overclocking.
[Xoom Android Development] Sodikop:
Simple question, just covering bases.

Did you wipe cache, dalvik, etc. in recovery after your last flash?
[Xoom Android Development] c0t0d0s2:
By wiping, what i really meant to say was, I flashed via fastboot the generic, stock image, then rerooted and reflashed tiamat.
[Xoom Android Development] saleum:
Thank you for your comment. I understand: I must change to Window$ for maintaining a nice relationship with this great an strange Xoom :-)
[Xoom Android Development] Acer99:
I have got my xoom friday afternoon (German T-Mobile Version, no branding)

First things was unlocking via fastboot and rooting right after the book.

After that I installed that kernel from sd card viy clockwork recovy.

Everything bu wifi works fine. First time, a got a mistake (Fehler) displayed at the wlan settings, no avtivation possible.

Now everthing looks fine, see the wlans an can connect to them. But no datatransfer at all. It seems if there were a missing link (module) between the apps an the wlan connection?! Data transfer via UMTS works fine.

I am not very familiar with linux/android, so any help is appriciated? Have I to push a *.ko or something like that?

Olli
[Xoom Android Development] eusthebest:
Hello all,

Let me start by saying that the kernel is working great, I'm not having any mayor issues, battery life seems to be better on the stock kernel but that's minor compared to all the stuff u get with this kernel.

I noticed that ever since I updated to tiamat the charging LED does not work anymore, its this a known issue? If not, is there a way to fix it?
[Xoom Android Development] cam30era:
Go back and read the OP by BRD. Look at his third post. You will find mods for the charging indicator light.
[Xoom Android Development] ClydeB1:
The bcm4329.ko file handles the wifi AFAIK. try pushing that file again via ADB.
[Xoom Android Development] eusthebest:
Wow, thanks for the quick reply, it worked pretty good, again thanks
[Xoom Android Development] zehkaiser:
Take a look at your original screenshot. Open the file named "adb has moved.txt". Threw me for a loop, too. :-)
[Xoom Android Development] totolita:
Same here

Hi, I'm having the same issue. I can't even put some widgets in the home page, cause it reboots. It happens when in chrome, firefox, market, etc.

It started in 1.3.0 and went on until now with 1.4.1. What can this be? I can't even use it anymore, it is really annoying.
[Xoom Android Development] gerbick:
I dare say otherwise. I've been using Mac OS X 10.6.7 this entire time without any real issues. Only one that bothers me was that everybody writes fastboot for some of the (older) stuff when you have to get fastboot-mac to work.

But other than that, all Mac, all day for me with my Xoom.
[Xoom Android Development] macknup:
Blank "External" Listing

Hi.

I Used RootMyXoom to root my device. Then added RomManger. Have rebooted into CWM and updated to 1.4.1. Am reading now that there seems to be some SD errors.

What my problem is is the "External" is listed both under my Xoom and my PC (when connected) but the folder is always blank and I cannot create anything in it.

I read you should go to 1.40 then 1.4.1.. I then rebooted into CWM, flashed to 1.40, rebooted into Xoom. Once in I rebooted to CWM then flashed again to 1.4.1. My External is still blank.

I want to be able to use and access my External SD Slot.. Any ideas on what to do?
[Xoom Android Development] cam30era:
Is your SD card formatted fat32? Try formatting it in an Android phone.
[Xoom Android Development] mutiny:
Was the one-click you used version 1.3.2?
[Xoom Android Development] mulletcutter:
Im in the same boat as you. Clockwork can see my external sdcard but not honeycomb. Root explorer has /sdcard/external but i cant move anything there. Ive flashed 1.3.2,1.4.0,1.4.1 cleared cache and dalvik after each one. And what ever the one click root method was last week is what i used. And ive formated sdcard with my mytouch4g so its fat32

XOOM
[Xoom Android Development] siscim23:
Did you flash using CWM? If so, can you see the tiamat zip file when reading the card on your computer?

Try moving files to the card on your computer then putting the card in your Xoom. Keep in mind you need to reboot for these files to show in Root Explorer (or any other file manager)

Edit: Try creating /sdcard/sdcard2 and rebooting, see if the card can be read/used with that folder instead.
[Xoom Android Development] mulletcutter:
Yes they all got flashed through cwm. Ill try the sdcard2 when i get back inside

Edit, i made /sdcard/sdcard2 and moved a zip file there, but clockwork still says the card is empty. I also made /sdcard2 and rebooted it was deleted when i checked after reboot
[Xoom Android Development] fanello123:
Just flashed "Enable Charging LED with Device On", but my LED stays white all the time, anybody else having this problem? Or maybe my device is broken? Is it possible to test if the LED ist fully funtional?
[Xoom Android Development] kev0153:
so any hints on what the next release is going to bring?
[Xoom Android Development] siscim23:
If you flashed through CWM, you should be able to see the zip files from CWM... now it says empty? What about on your computer, does it say empty?
[Xoom Android Development] mulletcutter:
Yes i did flash through cwm, but since the i formated it to make sure it was fat32. So the sd is empty. But im trying to make the sd viewable in honeycomb and not have to rely on my computer .

XOOM
[Xoom Android Development] forsaken82:
anyone know what the file size is on the new kernal?
[Xoom Android Development] mulletcutter:
Like 3.56mb...
[Xoom Android Development] forsaken82:
Would it work to just download the kernal to my PC and place it on the sdcard. Then put it in the xoom and flash it? I realize that it is pretty much the same as the directions, I just want to make sure it is not required to do it the other way.
[Xoom Android Development] niwa2:
working on EU model?

has anyone successfully tested this kernal on an EU (german) 3G model?

i am hopefully getting my XOOM next week and would like to change the kernel as soon as it gets here but only if it is working like expected.

can i somehow make a backup of the original software before a start messing with it?
[Xoom Android Development] macknup:
I am using RoomtMYXoom.03.exe when I bring up details it says file version 1.0.96.0

Similar to Mulletcutter I am able to see .Zip files contained on the SD Card when I am in CWM but when I boot to Android it has "external" listed as a subfolder of SDCARD but the folder is blank and I can't write to it from computer.

Also computer is finiky with showing folders I sometimes have to plug and unplug several times (the usb that is).

Any Ideas/Suggestions?
[Xoom Android Development] mulletcutter:
The computer is the only way i can put files on my sdcard. Then once u put the zip on sdcard put it in xoom and u can flash it through cwm

XOOM
[Xoom Android Development] Acer99:
Thanks for the hint. Pushed the file via adb

adb push bcm4329.ko /system/lib/modules/bcm4329.ko

Now I got the "Mistake" message again.

Hmmh, any idea what that comes from. I have the "german" Telekommodel. Perhaps the have a different wlan-board?

Or perhaps i have the wrong 4329. I pushed a file with 269636 bytes

Olli
[Xoom Android Development] Acer99:
upps posted twice sorry :-(
[Xoom Android Development] xjack:
I had this same issue after on 1.3.0, while trying to upgrade to .1, .2. I did everything recommended as far as reformat card, re installing kernel, try different card, etc. It always showed in CWM but not Honeycomb.

The end result that got the card working in Honeycomb was to format it on an Android phone (friend's Droid X in my case).

It's been flawless ever since.
[Xoom Android Development] xjack:
Mine does turn green once fully charged with this modpack.
[Xoom Android Development] wheeeler:
If WiFi and 3G are handled by the same board, you might be in a bit of a bind. I am also in Germany, but my Xoom is the U.S. version. I hoped that I could use 3G through Telekom, but my Xoom does not even find 3G service. My biggest problem with flashing my Xoom is breaking my WLAN, but flashing a good bcm4329 module fixes the problem. I don't think the 3G radio is the same as the U.S. version, so maybe you need a Europe-specific bcm4329.ko. I have no idea how much of this is true, but thought I would offer my opinion anyways. Tchus!
[Xoom Android Development] Acer99:
Problem solved

I pusehd the bcm4329.ko coming with this kernel again and now it works.

Some posts ago someone asked if this kernel is doing fine with the german telekom model....

For the moment I have no issues while using this kernel and the unlocking/rooting procedures described in this forum.
[Xoom Android Development] niwa2:
great. that is good to hear.
[Xoom Android Development] judison:
My xoom is "brazilian", ie: I don't know if its European or US version... how do I know??

It's also WiFi Only...

The rooting process is device specific, like, some files for wifi devices and some files for 3g devices.

Mine is already rooted and with Tiamat 1.4.1, but my question is, is this kernel for both wifi and 3g ?

How does this (wifi only vs wifi+3g) works when we are talking about the kernel??
[Xoom Android Development] BGrutter:
At yet another impasse.

Question, I am trying to push 1.3.1 so that I can then flash 1.4.0. For some reason, whenever I "adb reboot bootloader", my Xoom simply reboots completely, no bootloader screen. Any ideas why?

Currently running 1.3.0.

Thanks in advance.
[Xoom Android Development] mulletcutter:
Do u have clockwork recovery?
[Xoom Android Development] siscim23:
What does that have to do with booting into bootloader?
[Xoom Android Development] BGrutter:
I was thinking the same exact thing. But, I thought I'd check anyway. It said I had recovery onboard, but I Flashed anyway. Just ran the command and voila, bootloader.

I'm not gonna ask questions, just going to accept it. lol Thank.
[Xoom Android Development] siscim23:
Don't you have to boot into bootloader to flash recovery....?
[Xoom Android Development] BGrutter:
No, just use Rom Manager to flash recovery. Or at least that's how I did it.

Weird thing, I was able to run all adb commands without incident. However, when I enter Settings>About tablet, it lists 2.6.36.3Tiamat_Xoom-v1.3.0 as my kernel. That doesn't make sense.
[Xoom Android Development] mulletcutter:
Wow, must of missed read something...disregard what I said.
[Xoom Android Development] bigrushdog:
One word. Stability. Regarding model compatibility with tiamat, tiamat kernel 1.4.1 as well as recovery work on all known models. Reason being the kernel zip does not alter your boot image.
[Xoom Android Development] BGrutter:
Can't disregard it, for whatever reason, after I re-flashed recovery, it worked. I hadn't Flashed it since going from 1.1.6 to 1.3.0. Don't know how recovery has anything to do with it, but I'm happy.

Anyway, I've just finished flashing 1.4.1.

Follow-up question. What folder should I be looking for to see what's on my SDcard. I don't see a folder anywhere. I see sdcard/sdcard2, but "root file explorer" says it's empty, and that's definitely not the case.
[Xoom Android Development] mulletcutter:
Well shot...glad it worked.

On the sdcard, a few of us are like that, I have a sdcard in but can't see it in root explorer
[Xoom Android Development] siscim23:
Ah yes, forgot about ROM Manager.

And since 1.3.1 didn't have any major changes, BRD didn't update the name of the kernel. 1.3.1 shows 1.3.0. When you update to 1.3.2 or 1.4.x you will see the change again.
[Xoom Android Development] siscim23:
/sdcard/external
[Xoom Android Development] mulletcutter:
I've tried that...can't move any files there from zoom and it doesn't see files on my SD
[Xoom Android Development] forsaken82:
so since im at 1.3.0 now straight outta root, do i still need to flash 1.4.0 then 1.4.1? i ask because i cant seem to find 1.4.0. Also any progress on being able to hot swap? i know the iconia can do this, could it be pulled from them?
[Xoom Android Development] mulletcutter:
I think kernel manager has it. And it can flash from there

XOOM
[Xoom Android Development] dscribe:
Could the installation of this kernel be the reason for the problem described in this link?

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

NEVER MIND: I figured out the cause. It is not the kernel.
[Xoom Android Development] forsaken82:
ive always done stuff in clockwork, does km have any advantages or disadvantages?
[Xoom Android Development] siscim23:
It's quicker and easier.

Some people have had download/flashing issues, but a simple redo fixes it.
[Xoom Android Development] dj_ghosie:
It had been mentioned previously that you have to manually copy and delete the file instead to moving it due to some Linux limitation.
[Xoom Android Development] mulletcutter:
Thats what ive been doing...simple but android needs to drop the source already
[Xoom Android Development] BGrutter:
I'm having the same issue. I can't see any of my sdcard files from my Zoom or when I've tethered it to my PC via USB. I've tried putting files directly from my PC onto my sdcard, but when I insert the card, nothing. I've tried rebooting, but that doesn't work either.

What's really weird is that the kernel .zip files I flashed are recognized just fine when in CWM. It seems that my actual OS is just having difficulty identifying the files (I currently have a video, picture, and word document as test files).

Anybody have experience with this issue?
[Xoom Android Development] hkfriends:
hi there,

what does it mean 1.4.1 removed for mass storage, but your SDcard is still working????

I tested, if using 1.4.1 there will not has mounted for /sdcard/external

unless i flashed back to 1.4.0 then I can see /sdcard/external ==> which is my real external micro SDcard.

Is there anyone tell me what happen? Am I stay with 1.40 or I miss something when update to kernal 1.4.1 ?

many thanks:confused:
[Xoom Android Development] forsaken82:
kernal manager lite isnt doing anything. i hit download and flash and nothing happens. do i need the paid version for it to actually work?
[Xoom Android Development] siscim23:
No, lite works. It may still be down though.