yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] tinpusher:
From the SETCPU website:

7. CPU Scaling Governors

CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability

ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.

interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.

conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.

performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.

powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.

userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.

smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
[Xoom Android Development] jiwengang:
Flashed 1.4.4 with overclock GPU.

Smooth as SILK!!!

Another big hit BRD, BRAVO!
[Xoom Android Development] b0ricua:
Flashed 1.4.4 with GPU overclock and seemed to be stable at 1.7 at first. Not sure what changed but now I'm getting reboots.

I'm back at 1.6 and things seem to be fine. Hmmm!
[Xoom Android Development] mulletcutter:
Put on 1700 performance, no reboots but samauri 2 didnt load, rip tide had some weird random colors while driving. Put on 1600 and everything worked fine.

XOOM
[Xoom Android Development] TaIz82:
Got random reboot on mine so i'm back to 1.6 O.o
[Xoom Android Development] Psychokitty:
Mine had a seizure @ 1700. Back to 1500. Happy to have the latest goodies and be able to clock to 1500 instead of 1400, though!:)
[Xoom Android Development] phouse1025:
Reboots for me on 1.7 interactive and performance. Couldn't even finish running quadrant. Backed up to 1.5, 1.6 still reboots for me while web browsing. 50% oc is still awesome but I do hope that the voltages will get worked out down the road cause I would love to be able to make this xoom fly more than it already does.
[Xoom Android Development] ax0r:
Stable for me on 1.7 silky smooth
[Xoom Android Development] patass:
Im going to do some testing to double check, but I feel like I was getting better performance on the Kernel prior to Riptide as far as emulators and benchmarks go. Gensoid is stuttering now, SNESOID has slowdowns, and FPSE is more or less unusable. My benchmarks were at like 4250 @ 1.5 ghz, now they're around 3000 @ 1.7 ghz.
[Xoom Android Development] KING SKILLZ:
1.4.4 Is the kernel that i am really noticing a difference, things seem almost instant. Good job.
[Xoom Android Development] ryan562:
awesome work once again BRD. my xoom is stable at 1.7 up to a few minutes where it begins to get hot and reboots. no biggy here just excited to see how far we can test tegra2 limits.

and btw, are you planning to add voltage control (Undervolting mainly) on the next update?
[Xoom Android Development] LNKNPRKFN:
Use "no-Frills" cpu, SETCPU slows and messes with the xoom...
[Xoom Android Development] faylix:
Got lots of reboots and lots of force closes at 1.7ghz.

Manged to get it back down to 1.5 still seeing lots of force closes

going to flash back to 1.6ghz if this keeps up. *sigh*

edited to say I love the good work of Bigrushdog and know this kernel will be fixed up soon enough

- faylix / local
[Xoom Android Development] dota-lina:
mine doesnt work on 1.7 at all :(

done the linpack and get 72 then died on quad, and keep rebooting, even cant get into the setcpu to change the freq, flashed back to .4.3 kernel and get it back to life :D
[Xoom Android Development] RinTinTigger:
Same here!

It ran great for some days, but then, setting it to 1.7 full throttle, it went dead and not back to life untill i flashed 4.3
[Xoom Android Development] faylix:
flashed back to 1.4.3 - all sorts of things still force closing...

ruh roh.

going to try a few things... does anyone have a fix permissions script for the xoom?

It looks like I can't write to the file system anymore.. I tried restoring a backup and it didn't work... i tried wiping /data that didn't work... I'm back to the 1.4.3 kernel but everything force closes...

Looks like it can't write to data, even in recovery data seems to be mounted read only.

/dev/block/mmcblk1p10 on /data type ext4 (ro,nodev,noatime,nodiratime,barrier=1,data=ordered)

So I can restore up to data... it won't let me mount data.

I rebooted, now i manually mounted data

mount /dev/block/mmcblk1p10 data

and mount shows

/dev/block/mmcblk1p10 on /data type ext2 (rw,relatime,barrier=1,data=ordered)

tried to restore and it went up to data and failed on writing to data again...

now mount shows

/dev/block/mmcblk1p10 on /data type ext2 (ro,relatime,barrier=1,data=ordered)

****... I'm starting to feel lost here..

is there an SBF?

- faylix / local
[Xoom Android Development] faylix:
Okay, I found the US 3.1 images, and flashed those all through fastboot.

Xoom restarted and I had a dead stock xoom 3.1 (PHEW)

next i rebooted into fastboot, flashed the modified recovery, and did the 3 seconds and caught it so it entered clockworkmod.

Now i'm trying to flash one of my restores from last night.

DATA IS FLASHING!!!! WOOT.

now the only issue is kept a lot of files (incuding my whole ebook and comic book collection) on the internal memory.. I wonder if its still around...

guess we will have to see. Thank god i got my xoom back. Not being able to write to data even from recovery was very scary.

- faylix / local
[Xoom Android Development] shmigao:
couple of ideas:

1) here is the fix_permissions script that works for me on Xoom

extract fix_permissions.sh and place it in your /sdcard folder

invoke it with ADB or on the XOOM with Terminal Emulator:

sh /sdcard/fix_permissions.sh

2) prior to flashing 1.4.3, wipe cache and dalvik cache, then flash 1.4.3 and check whether that sorts out your force-closing issue

3) if 2) didn't help, full factory reset / wipe user data, flash 1.4.3 and see whether that works

4) I also noticed today that my Xoom got very hot (i am still using 1.4.3) on trying to write a LinkedIn post in the browser (extreme lag either...). Probably bad browser software... anyway, i put it in my bag, had a 1.5 hr negotiation with my client, take the Xoom out, and it had been in a boot loop (honeycomb screen) for the entire time, and very hot. Switched it off, turned it on, prayed, it turned on, but immediately i get all sorts of stuff force-closing (device still hot).

switched it off, waited 20 min to let it cool down, started up, and haven't had any problems since then.

lesson: if the device is hot and all sorts of stuff is crashing - cool down, and let the Xoom cool down too :-)

hope the points above 1-4 help,

cheers
[Xoom Android Development] faylix:
Much appreciated sir....

I managed to get back to working form. Just lost all my data on the internal storage in the process.

I ended up having to fastboot flash images over the current ones.. then re-root and re-apply my backup.

it worked, but that sucked.

I'm wondering what the real culprit was.

- faylix
[Xoom Android Development] Archangel:
Market force closes like it is the thing to do lol. Too many reboots to count, wipe cache and dalvik back to 1.4.3 all fine now
[Xoom Android Development] xlGmanlx:
1700 on interactive baby its silky smooth
[Xoom Android Development] mcfisch:
D-Link DUB-E100 USB-Eth. is working with 1.4.3

I've seen in the release notes that support for RTL8150 has been added. I don't have one, but I own a D-Link DUB-E100 USB-Ethernet-adapter and some USB-OTG-cables. So I thaught "let's try it, maybe it's working, maybe not..." - and voila, it works "out of the box". :cool:

I've tested it by opening a terminal and do some networking stuff (ping, traceroute, ssh, etc.) to verify the function.

Wish I would had it in the bag 2 days ago when I tried to got the 3G connecting while setting some servers in the datacenter up and needed to connect through an external VPN... :D

The next time this will be my "plan B"...

Note that I didn't update to 1.4.4 yet, still using 1.4.3.
[Xoom Android Development] JaymZ37:
Hello guys,

As Motorola just released news Stock Images, including French MZ604 build, I'd like to flash CWM Recovery, and Tiamat Kernel.

But actually, French users are on 3.0.1 HoneyComb. So I need to update to 3.1 prior to flash Tiamat Kernel ? They didn't released yet 3.1 update, but apparently there's a way to get 3.1 update for non-US users, is it correct ?

Thanks a lot
[Xoom Android Development] Galaid:
Could anyone please try Sunspider benchmark at

http://www.webkit.org/perf/sunspider-0.9.1/sunspider-0.9.1/driver.html

?

Galaxy S2 @1.5GHz has score around 2000.
[Xoom Android Development] willverduzco:
1609 at 1.5 GHz using the stock browser
[Xoom Android Development] Galaid:
very nice score :)

btw. ipad2 has 2100
[Xoom Android Development] airbillion:
Are there any updates on the release of the 1.2?
[Xoom Android Development] Kamau54:
Ok, is there a video that can show how to install this Tiamat?
[Xoom Android Development] PaulG1488:
There's no need for a video just follow the directions they're pretty straight forward
[Xoom Android Development] Kamau54:
1. Reboot into the bootloader by running: adb reboot bootloader

2. Flash the boot image to your boot partition, then boot back into Android by running: fastboot flash boot boot.img fastboot reboot

3. Push the bcm4329.ko, scsi_wait_scan.ko, and any other modules to your /system/lib/modules folder and reboot. adb remount adb push bcm4329.ko /system/lib/modules/bcm4329.ko adb push tun.ko /system/lib/modules/tun.ko adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko adb push cifs.ko /system/lib/modules/cifs.ko

adb push vold.fstab /system/etc/vold.fstab adb reboot

You'll have to forgive me, but it is not that simple for me, being new to this all.

Don't know how to reboot into bootloader.

How do you flash?

Do I do all this from my computer, or from the xoom?

When it says "adb", what exactly is that? Command? How do I enter it?

As I say, a video would be more help to me as I feel like I'm becoming an annoyance to some for asking for exact instructions.
[Xoom Android Development] PaulG1488:
Here's a good post on explaining and installing adb

http://xdaforums.com/showpost.php?p=12189122&postcount=2
[Xoom Android Development] Cybertronicz:
If you arent too sure on what those things mean, you might not want to go fiddeling with your kernel.

This is an advanced thing, and you are not carefull and know what you are doing, you could damage your device.

Be warned... Until someone comes out with a "One click" tool like they did for rooting, installing kernels should be performed by people who are familiar with the process.
[Xoom Android Development] Kamau54:
Which is why I have not done so. I thought overclocking my xoom was as easy as it was when I rooted my DX. I see that it is not.
[Xoom Android Development] :
1.2 hasn't been release to the public yet. still in testing phase. I have 1.2 loaded right now on my xoom and it is running really smooth. the only problem is throws some wifi xooms in boot loop so he is still working on it. should be release soon. keep looking for updates.

And wifi - edit
[Xoom Android Development] JeffR714:
I'm grateful to bigrushdog for all his excellent work but I can't get these kernels stable and I think I know what I'm doing. I get force closes apps don't function right I myself am sticking with a rooted xoom as well as the stock kernel
[Xoom Android Development] PaulG1488:
Its also happening to the 3g models since I'm one of them
[Xoom Android Development] stiffspliff:
running 1.2.1 since this morning ;) also donated a few bucks, get some animal-style fries on me bro!
[Xoom Android Development] :
I forgot about that. I edited the post.
[Xoom Android Development] stigmax:
just loaded v1.2.1, checking it out
[Xoom Android Development] airbillion:
Can you tell me where to get the newest v1.2.1 kernel please? I would like to try it as well.
[Xoom Android Development] qubz:
+1

10char
[Xoom Android Development] PaulG1488:
Rush dog is normally in the #xoom channel in freenode at night that's where he usually releases his kernels for testing before going public
[Xoom Android Development] bigrushdog:
Ya freenode #xoom is where all the action is for brave souls ;) . I'll be on tonight for my graveyard shift. Stop by and be my Guinea Pig! :eek::eek::eek: :D:D:D
[Xoom Android Development] :
I hate graveyard shift lol you suck brd. Im staying up for ya lol. Just thought you should know haha!
[Xoom Android Development] stigmax:
is anyone else running ondemand governor? it feels horrible compared to interactive.

1000mhz at interactive feels so much smoother then 1.4 at ondemand. I wish i can run OC'd at interactive:( scrolling homescreens is lagggy ..bleh

edit: back to 1.2.0 for me. i get random reboots with 1.2.1
[Xoom Android Development] Cybertronicz:
Thats because the Interactive gov is much faster at scaling the cpu. The ondemand gov polls cpu load, and then when it sees increased load will THEN scale up the CPU. This is fine for something that is going to take cpu load for a while (like watching a video) but for things that are quick spikes, (like navigating around, or launching a small app) the Interactive gov will do a much better job. I am running 1.2Ghz + Interactive and its great!
[Xoom Android Development] siscim23:
1327.5 at 1.6GHz
[Xoom Android Development] sandro.bertini:
Just run it, in performance mode, just afer a reboot.

Total: 1393.3ms +/- 0.8%

Breakdown:

3D: 202.7ms

access: 138.2ms

bitops: 107.7ms

controlflow: 8.8ms

crypto: 92.1ms

date: 203.8ms

math: 134.2ms

regexp: 76.5ms

string: 429.3ms

I think its prety good, doesn't it?

Regards,
[Xoom Android Development] willverduzco:
Looks like I need to try SunSpider in performance mode, as apparently it didn't lock up my CPU at 100% as expected. :P
[Xoom Android Development] siscim23:
Mine is at interactive, and I haven't rebooted since installing 1.4.4 yesterday morning.
[Xoom Android Development] willverduzco:
Thank you. That's interesting. I just installed 1.4.4 and am running it now... Let's see how it goes.

Edit:

Interactive: 1735 ms

Performance:1626 ms

Edit 2: I was on a test version of 1.4.3 before that had 1.504 GHz added in. Perhaps 1.4.4 is a decent amount faster than 1.4.3. :)
[Xoom Android Development] siscim23:
Wow it goes through the whole benchmark in less than half the time now. Must have cached it.

Final result at 1.7GHz performance is 1487.9ms. Weird that it's 150ms slower than 1.6.

Tried at 1.7GHz interactive, got 1480.1ms.
[Xoom Android Development] willverduzco:
My understanding is that it runs fewer iterations of the same tests when there's less variability, since it tries to achieve a low variance.
[Xoom Android Development] RinTinTigger:
Hear ya Will :)

still need to get drunk wif u ;)
[Xoom Android Development] patass:
i'm going to wipe and reflash everything later tonight
[Xoom Android Development] sqx:
can i use the boot.images (that are for verizon 3g) for the EU xoom 3g aswell?
[Xoom Android Development] adamtuba:
Yes you can. I have been using them fine on my Aussie one (same as euro) since I bought it.

Make sure you use 'no frills' CPU from market, not setcpu. Setcpu was causing reboots, but someone recommended no frills a few pages back and its working great on 1.7ghz.

This goes for everyone, ATM 'no frills' CPU is working better than setcpu.
[Xoom Android Development] Sistema1927:
First, thanks to BRD for all of his hard work. I have been able to successfully flash all kernel versions, OC to 1.6, and also use USB tether w/o difficulty.

I have been using AnTuTu's CPU Master(Free) w/o problems, is "no frills" better?
[Xoom Android Development] adamtuba:
Never used antutu's sorry. All I know is that with SetCPU I was getting fc's and restarts all the time. But since using no frills I've hardly had a hiccup. Only reason I chose no frills was that someone a few pages back (sorry can't remember who it was) said to try it because setcpu was having issues. I guess if it's working fine with what you're using then no reason to change, more aimed at those doing it for the first time.
[Xoom Android Development] Vanhoud:
Sunspider results 1.6ghz performance

1403.5ms +/- 1.6%
[Xoom Android Development] PlinXoom:
Anyone else having issues with flashing the kernel?

I keep getting

E:Can't open /sdcard/Tiamat_Xoom-2.6.36.4-v1.4.4_Full-Throttle.zip

(bad)

Installation aborted.

EDIT: turns out I can't use the kernel with OC GPU? any reason for this? the stock gpu one works fine.
[Xoom Android Development] shmigao:
What means can't use? Maybe just a bad download / file corrupted?
[Xoom Android Development] willverduzco:
Your download got corrupted. Delete and try again.
[Xoom Android Development] PlinXoom:
Ive tried it on the mirror the original on the xoom and also on the pc. The oc gpu one is the one that doesnt work, the stock gpu one works fine....

EDIT: Downloaded a fourth time from http://bigrushmods.com/tiamat.html and now finally flashed OC GPU kernel.

EDIT2: 1.7 is unstable for me and hangs/freezes. 1.6 seems to be fine.
[Xoom Android Development] Chelseablue:
Man, 1.7ghz and I can't run it long enough to blink. 1.5 works just fine though so I'm happy. Awesome work on the kernel.
[Xoom Android Development] ClydeB1:
I've run Quadrant on both 1.7Ghz Performance and 1.6Ghz Performance with very strange results. @1.7 = 2965, @1.6 = 4270
[Xoom Android Development] flombs:
Is there a natural progression of installing tiamat kernels, for example, I'm on 1.1.6, do I need to install 1.3.0 then onwards? I can't find 1.3.0 to download anywhere. I don't even know where to start in the github.
[Xoom Android Development] adamtuba:
No, you can install latest now no problems.
[Xoom Android Development] jgrizz:
im running 1.7 interactive no issues. Zero reboots.
[Xoom Android Development] SwampNutz:
So I'm trying to get in on some of this 1.5-1.7ghz action but I'm not having much success, or maybe I am and I'm missing something really simple (hopefully). I rooted and upgraded my Xoom WiFi to 3.1 using BRDs instructions and files which worked perfectly so no issues there. I flashed the Light On boot image and then the OC'd GPU 1.4.4 kernel and I'm back in action, no issues except for the lack of overclocking. I purchased and installed SetCPU which only registers 1GHz as the max speed. I can't select anything higher when creating a profile. What am I missing?

I'd love to see what this thing can do overclocked but at least I have CIFS support now. Thanks BRD and thanks in advance to whomever can help me get the OC settings working.
[Xoom Android Development] @prime:
Thanks to all the devs who make this possible. I went from stock unrooted 3.1 to Tiamat 1.4.4 in under half an hour with absolutely no problems. Very sweet.

I tried the GPU overlock with 1.7GHZ using "no frills", it was highly unstable for me though and after numerous reboots decided to drop it back to 1.6. No problems now, very stable.

I did a sunspider test on 1.6 with "interactive" set, and got a 1368ms.
[Xoom Android Development] ClydeB1:
When you started SetCPU, did you choose the option to Autodetect speeds? You need to do that to pick up the fact that you have a new kernel. Also, to be certain, check that the kernel did actually install. Go to Settings/About Tablet and check that the kernel version shows as Tiamat 1.4.4-Full_Throttle
[Xoom Android Development] SwampNutz:
That did the trick! I remember choosing the bottom option when I started setcpu for the first time. I uninstalled the app and reinstalled choosing Autodetect. So 1.7 is a no go for me but 1.6 is working so far. I have to stress test and see how this thing holds up. Thank you!
[Xoom Android Development] opsahl:
1.7 extremely unstable for me, wifi only. Went back to 1.6 under 1.4.3.
[Xoom Android Development] ClydeB1:
You could also just have used 1.6Ghz while still on 1.4.4
[Xoom Android Development] SwampNutz:
Damn, 1.6 ghz resulted in automatic reboots while browsing. Guess its 1.5 for me.
[Xoom Android Development] knifer:
I'm sort of in the same boat. I bought my Xoom in Hong Kong (MZ604) and it is 3.0.1 and rooted. I don't know if I have SD support to be honest. I see sdcard/sdcard2 in astro but doesn't show up in settings-storage. Also, I tried following these instructions http://xdaforums.com/showthread.php?t=1074609 but flashing with CW doesn't seem to flash the files I put in sdcard/sdcard2. Can anyone point me in the right direction? How can I get SD support and then install 3.1?

Thanks.
[Xoom Android Development] BeagleBoy:
Got my first lockups and reboots running @ 1.7. Stepped it back to 1.6, and all seems well.
[Xoom Android Development] opsahl:
No need for the other features, and 1.4.3 stable, for me.
[Xoom Android Development] kbluebig:
Help!

I have been running xoom wifi rooted and with tiamat kernel 1.4.2 and then 1.4.3 for a while now with no problems. Than all of a sudden around 30 minutes ago, xoom started running extremely slow. Finally got to the point it was frozen. I have no idea what caused it.

So I had to do the force power off (hold down power button and volume up button) which I did before with no issues. So this time I do it, goes down and it comes back up, its stuck on the motorola logo splash screen. I let it sit for around 20 minutes and no change.

So I do the force power off again and now I get a screen I never saw before. I see a green highlight of that android logo (that robot dude) and then I get a screen that just says "Enter your password".

I do not have any passwords set up on the Xoom so now I am stuck.

Please do not tell me it is bricked. I do have a clockwork rom manager backup I did a few days ago to the SD card.

Is there anyway to get it to boot normal again ? Or do I have to some how reset it and then possibly restore the clockwork backup I made ?
[Xoom Android Development] JaymZ37:
Ok, so that's what I did :

- I was on 3.0.1 Stock, Wifi Only model, French, Build H.6.2-24

- I unlocked my Xoom

- I flashed the CWM Recovery 3.0.2.8

- I used this topic to update to 3.1 HMJ37 with root and SD support

- Then I flashed the language pack to restore french on my Xoom

Everything was fine, took about 20-30min long.

But now, I want to know if there's a way to get back to stock kernel if I flash Tiamat Kernel and doesn't want to use it anymore ?

Simply by doing a nandroid backup before flashing Tiamat ?

And by using the topic below tu update to 3.1, I get SDCard support, and it's already implented in Tiamat...

Any risk ?
[Xoom Android Development] shmigao:
1.7ghz no go for me either
[Xoom Android Development] davidsos:
You can find a link to your stock kernel at the below thread.

http://xdaforums.com/showthread.php?t=1049485
[Xoom Android Development] Psychokitty:
Please consider participating in a Tiamat kernel CPU speed poll, located here: http://xdaforums.com/showthread.php?t=1110066

Thanks!:)
[Xoom Android Development] shmigao:
Let me be an a$$ and support the moderator... the poll could have been kept here. Why a new thread?
[Xoom Android Development] xxspark89xx:
This thread is long enough to follow in its own topics of "general" discussions about Tiamat, I think it was a good idea to start a new thread focused on performance.

Besides, I don't think BRD wants to waste screen real estate to a poll on "feedback" when the OP of this thread is focused on intro and installation.