yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] JungleJiujitsu:
Yup! Just rooted and then flashed this kernel immediately after, and can also confirm that it works on the WiFi model!...too am OC'ed @ 1.54Ghz on the Performance Governor, getting 59.625 MFLOPS in Linpack & 2954 in Quadrant!
[Xoom Android Development] Holsum:
does.anyone have vpnconnections working or anything else that allows cisco ipsec vpn with group and rsa secureid working with this tun.ko?
[Xoom Android Development] conmeo8ya:
Do i need to use setcpu to 1.5Ghz ? or original speed ? :D
[Xoom Android Development] funnycreature:
That's what I have. Minimum around 200MHz, max to 1.5GHz. But honestly, all those numbers don't necessarily reflect the great user experience that Honeycomb offers on the Xoom (at least for me). :)
[Xoom Android Development] xlGmanlx:
Your not the only ones, before the xoom my mistress was my evo, now she doesn't even get pity quality time haha
[Xoom Android Development] kcrudup:
Ya know?! Just phone calls and Google Voice notifications now. :)

In fact, getting the Xoom has led me to where I'm considering rooting my Evo now- I have to have a rock-stable phone for my business, and I wouldn't run any ROM other than "stock", but now that I've offloaded most of my portability-based workload to the Xoom I can back up as much as I can (as I'll need to wipe) and start over again (which I need to do anyway, I've got a rogue app somewhere that's keeping the Evo's CPU lower frequency bounded all the way up around 500MHz).
[Xoom Android Development] 760hacker:
Delete this sorry.
[Xoom Android Development] jroid:
OP: can you please post a stock zimage to allow for revert? Forgot to pull my boot.img in excitement to root and building tegra platform from source is giving me errors. Geting kernel panics on any clock speed

Sent from my Nexus S
[Xoom Android Development] tekmunki:
Originally rooted with the One-Click root method, then flashed the 1.1.6 kernel using that utility. After CIFS functions failed to work, I followed the instructions at the beginning of this thread...

OK. I flashed the kernel and did the instructions as outlined in this thread and copied all the .so files to their respective positions, rebooted.

su

mount -t cifs -o username=johndoe,password=secret,domain=fqdn.org //172.16.0.3/Operations /mnt/cifs/ops

returns:

[1] + Stopped (signal) mount -t cifs -o username=johndoe,password=secret,domain=fqdn.org //172.16.0.3/Operations /mnt/cifs/ops

In cifsmanager I get this error:

[1] Segmentation Fault mount -o usernam

Do you have any clue as to why I can't get CIFS to work? I have a fleet of 8 Xooms waiting to launch, all tetering on this function. Thanks a ton. =)

*note, the Xoom is encrypted--- is that related??!
[Xoom Android Development] xlGmanlx:
I don't see why encryption on the drive would have anything to do with streaming, could be wrong. Did you try reverting to 100% stock?
[Xoom Android Development] tekmunki:
Not streaming, just using it to access network shares for Word Document editing, mostly. CIFS will allow me to map a folder to a network share, which allows live editing of the documents without the need to download and re-upload.

Flashed to 1.5... (same errors)

Can I add CIFS support with only the stock kernel?? I was under the impression that's why I needed the custom kernel.
[Xoom Android Development] xguntherc:
I wanna overclock higher!
[Xoom Android Development] Xezuka:
Haha yeah me too :D
[Xoom Android Development] patass:
quick question - setcpu is still required for OC correct? Also which governor do you recommend in SetCPU?
[Xoom Android Development] Steady Hawkin:
Yea or Droid overclock. I prefer interactive.
[Xoom Android Development] myv6mustang:
Will this wipe the Xoom?
[Xoom Android Development] stigmax:
rebooting

I can not use the interactive governor. Freeze/reboots all the time. Ondemand is working for me so far. Anyone else having this issue?
[Xoom Android Development] graffixnyc:
nope, interactive works fine for me. Set at 1.5

I did notice though if you clock it lower say at 1ghz it will still jump to 1.5. Tried rebooting, tried re detecting and rebooting and it still happens. Still will climb up to 1.5 even when it's set at 1. I read in the other kernel thread it's happening to others using that kernel too.

Big already knows just figured I'd post so you guys can see if it's happening to you as well
[Xoom Android Development] Steady Hawkin:
No but unlocking the device will
[Xoom Android Development] Xezuka:
Does the same for me. Once I set it to 'ondemand' I have yet to have a single reboot all day. This morning I had 2 reboot within an hour using 'interactive' -- which seemed to be fine until it randomly went instantly to a crawl/freeze for a quick second, then bam, reboot. Very frustrating.... saw this post... no reboot since. :D

I can also now go to the full 1.5 and remain reboot-free. Whereas with interactive I had more reboots the higher I overclocked.
[Xoom Android Development] harish3110:
thanks....

thanks alot!!!!!!!
[Xoom Android Development] harish3110:
not able to overclock to 1.5 ghz...

the flashing went about perfectly...but when i use setcpu or droid overclock cannot go upto 1.5 ghz......only upto 1ghz....
[Xoom Android Development] ClydeB1:
Did you run auto detect in SetCPU?
[Xoom Android Development] stevefxp:
I had a full system reboot this morning when using the 1.6 option. I dropped back to the 1.5 option, and will continue to use.
[Xoom Android Development] harish3110:
is 1.6ghz stable compared to 1.5 ghz for xoom

i have installed the 1.5ghz kernel for nw...is the 1.6 ghz kernel stable as compared to 1.5ghz kernel....
[Xoom Android Development] Stealyourface:
Ditto. Weird.
[Xoom Android Development] Sodikop:
It's dependent on your particular Xoom. Some processors can handle the higher frequencies, others can't. Mine personally seems to do fine with the 1.6 option, although I haven't really noticed a "real world" improvement over the previous 1.5 option. Hope the GPU overclock will be more beneficial, going to test it out tonight.
[Xoom Android Development] willverduzco:
Screen uses up FAR more power than the CPU, which uses up significantly more power than the GPU.

Basically: Screen >>> CPU > GPU in terms of usage. Even turning down the screen brightness just a smidgen will more than compensate.

In other words, you won't notice the difference in battery life too much.

*Note: This is assuming that you are using interactive or on demand governors. If you're in performance "governor," you're needlessly wasting tons of battery.
[Xoom Android Development] despich:
I had some crashes at 1.6, sometimes it would just be the app that crashed, other times the whole thing would reboot. Usually would happen when I started a app or I started a video or a activated flash on a web page.

1.5 with the overclocked GPU has been rock solid so far for me. I put about 4 hours of use on it last night after I put the 1.5 kernel on with lots of high CPU usage without a single glitch. Looks like for me 1.5 is about as fast as I should go. It's hard to gauge how much the overclocked GPU makes a difference. I played some 720p MP4 videos today that have always been very laggy and they do appear to be less laggy with the new GPU. Tried them with MoboPlayer, RockPlayer and VitalPlayer with no issues so it appears the overclocked GPU doesn't introduce any problems for me anyways.
[Xoom Android Development] abn.geek:
Just my experience with the 1.6 and 1.5 GPU OC kernels...

The 1.6Ghz kernel was stable on my Xoom, but in terms of "real world improvement," the 1.5Ghz kernel with the GPU OC makes a far more dramatic impact on overall UI smoothness (e.g. scrolling and animations) and in a lot of apps where where scrolling was jittery.

Haven't had time to do any solid benchmarking yet, but it's really a huge improvement. Things are downright buttery. Not quite iPad 2 buttery, but getting there.
[Xoom Android Development] lrs421:
I agree with the smoothness. I'm running the 1.5 kernel at 1.2 w/interactive governor and its sick. Incredibly smooth and fast. With screen off profile in setcpu battery life is great as well. Very happy. BRD is awesome.

Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
[Xoom Android Development] Prod1702:
so sry if this is a dumb question but is there anyway to know if the GPU OC is working. I ran Quadrant but the FPS didn't cahnge from what it was without the GPU OC, so i wasn't sure if the GPU OC is working or not. Is there a app or anything to tell me what the GPU is clocked at right now. I am unable to run smartbench with the OC ever since i started to use a OC kernel tells me that one of the tests failed to run, but it looks like they all ran no clue. Is there a benchmark to test other then quadrant mainly.
[Xoom Android Development] Elysian893:
Quadrant didn't change for me either, it's mostly a joke benchmark anyways. Nenamarks fps and Glbenchmark are both up quite a bit.
[Xoom Android Development] Prod1702:
Thanks will have to try those out. Moving around like opening somethings that have video of pictures feels abit quicker as well. I also see that Flash based games like the games on facebook run fastter with the GPU OC one as well.
[Xoom Android Development] bigrushdog:
just a couple things in the pipeline... gpuoc on all kernels, ums on all kernels, a standard frequency kernel with all the goodies. Eventually, I'm shooting for a single kernel with voltage and scaling in perfect harmony.
[Xoom Android Development] gerald410:
That sounds just awesome(drool) Thx BRD!
[Xoom Android Development] malaeus:
kinda stupid question. if i root a xoom that magically came with 3.1 installed. do i still need to reflash using your method in the first page?

i would assume i wouldnt need to. just figured i would ask, in case you did something special in your method vs. out of the box.
[Xoom Android Development] lrs421:
I'm noticing less keyboard lag with the 1.5 gpuoc kernel. This is how my xoom should have been out of the box.
[Xoom Android Development] phil50:
No hdmi

Can someone tell if the kernel can stop the hdmi from Woking

As mine dosent work at all besides that its great

I'm on the 1.5 with gnu thanks
[Xoom Android Development] siscim23:
When I first plugged it in, the signal was going in and out, but when I unplugged it from the Xoom and plugged back in, worked just fine. I'm pretty sure it's my adapter that was causing that, though.
[Xoom Android Development] kapeedp:
hello all,

I am in UK and have a 3g + wifi xoom

I rooted my xoom following the instructions on the [GUIDE] XOOM 3G Euro Root Instructions + Files.(http://xdaforums.com/show....php?t=1049901) thread and then installed CWM from http://xdaforums.com/show....php?t=1038870

I later installed Tiamat Xoom Kernel Boot Image and Kernel from http://xdaforums.com/showthread.php?t=978013

My xoom wont pass the motorola dual core screen

tried the power button n volume down n up options but on my command prompt am getting Error: device not found

any suggestions how can I get my Xoom to work

any help would be much appreciated

many thanks
[Xoom Android Development] bigrushdog:
Anybody check out Riptide yet? This game is truly insane! So, I figured, why not do a Special Release. Tiamat Riptide Edition. 1.6Ghz, OC'd GPU, UMS, SLUB Allocator, smoking fast for killer FPS and HDMI output!
[Xoom Android Development] malaeus:
bumping for some reason
[Xoom Android Development] gerald410:
I'll take one please!:) Rockin' Riptide version now. Thx BRD
[Xoom Android Development] Psychokitty:
Loadin' her up right now...:
[Xoom Android Development] starcms:
I just noticed something with the new 1.6ghz RIPTIDE kernel with GPU OC. My battery usage stats in settings are resetting after every reboot instead of only after the battery is fully charged and then unplugged. Is everyone else seeing the same results? If so, BRD, can you plz restore it back to the original way? Thx!!
[Xoom Android Development] ClydeB1:
It must be something else on your side. I've just rebooted to check and my battery usage stats stay put.
[Xoom Android Development] kev0153:
wow :) I like it
[Xoom Android Development] starcms:
Weird. Rebooted again and it wiped again. Anyone have any ideas of what would be causing this?
[Xoom Android Development] flombs:
Thanks for your hard work once again, BRD!
[Xoom Android Development] zonk7ate9:
Any difference between the 1.6 Riptide and the 1.5 OC GPU other than the clock speed? I ask because I don't like how hot the Xoom gets during heavy use (i.e. gaming)when running @ 1.6, but the 1.5 kernel is perfect. Thanks.
[Xoom Android Development] bigrushdog:
Ain't nothing different. Just a smoking Riptide kernel

:cool: :cool:
[Xoom Android Development] joeski27:
Agreed, mine heats up the same way under those conditions, definitely makes me nervous. While I'm super grateful for all of BRDs work with these kernels, I'd really feel more comfortable if I heard that he tested these out and intentionally and specifically pushed his xoom to the limit to where he could vouch for the kernel 100%, even under (or especially under) these conditions. Previously this wasn't an issue, but it would seem that we are clearly approaching the limits of the hardware and any dev should be willing and able to fully risk his hardware in order to assure everyone else that there is little to no risk of damage. Up until now nothing has been said about overheatthe processor, but that's because this is the first kernel that has caused this.

And I know some may just say not to run the 1.6 ghz kernel on performance mode...but if yo can't use 1.6 ghz for extended use, then what's the point of having such a setting?
[Xoom Android Development] dubie76:
Just to confirm, if I don't use setcpu or something similar the new kernel will run default correct?
[Xoom Android Development] PaulG1488:
So you are telling me that you think that brd releases kernels without he himself testing it why on earth would you make a remedial assumption like that?
[Xoom Android Development] Archangel:
I would say I have to agree with Paul, I have seen these guys test like it is cool on IRC, trust there are no issues, if so test for yourself, this is the reason for setcpu and temp settings, if you dont like scale back
[Xoom Android Development] phouse1025:
stuck at boot animation!! please help

i got the new riptide kernel, i flashed the boot.img, flashed the riptide kernel, then flashed the ua string mod all through clockwork. now after rebooting my xoom is stuck in a repeat of the boot animation. held vol.up and power to reboot again and im still stuck! any ideas? somebody please help. ive used every other kernel that BRD has come out with and this is the only time it has happened.
[Xoom Android Development] abn.geek:
Are you sure you used the right ua string mod? That's what happened to me when I used the one for 3.0 instead of 3.1.

Edit - I ran though this sequence on my device with no problems. The 3.1 compatible ua string mod isn't the one in the op of the thread for that mod. It's further in, and like halfway maybe.

I'm using a US version WiFi.
[Xoom Android Development] joeski27:
You want to know why I made this assumption? Because myself and others have made comments in this very thread about possible overheating and not once have we gotten an official comment from brd about this issue. I mean call me crazy,but i would have thought that with the release of the first xoom kernel thatcouod cause such overheating that there would have been a note with that release at least mentioning possible heating issues and, for example, saying "this is normal" or "this heating issue was fully tested and showed now ill effects on the xoom." Forgive me, but I'm far more concerned with looking out for the well-being of my device than I am worried about offending anyone by making "remedial" assumptions. Again nothing against brd or anyone else, just my opinion, and I can't believe I'm the only one speaking up about it.
[Xoom Android Development] dubie76:
Over clocking any CPU is a risk. Heating up or not, if you do it, your risking damage to your device. Bottom line. I don't see why people are arguing about this. Do we really need to go back and forth about this anymore?
[Xoom Android Development] bigrushdog:
Tiamat Xoom Liquid Helium Cooling Systems now on sale on the accessory board! Buy one, get one half off!

Running any device overclocked for an extended period can cause warming. Keep your device on Interactive. That is my official statement.
[Xoom Android Development] gerald410:
I will take 3 lol:)
[Xoom Android Development] dscribe:
I suppose I'm glad you made an "official statement" but it should be obvious to people. I just think we have a lot of people these days that are rooting and modding their devices and they really shouldn't be. Good grief.
[Xoom Android Development] tangiers:
Running new 1.5 kernel. Perfect as usual with all these kernels. Never had a problem with bigrusdog's various kernels. My impression of his work is that he is very careful with everything he releases.
[Xoom Android Development] Psychokitty:
No, absolutely not. Anyone taking overclocking advice from the internet and holding someone else responsible, even the developer, no matter how safe he may proclaim it to be, is a FOOL. Any of this; rooting, over clocking, installing a custom ROM, etc. - it's all understood to be done at your own risk.
[Xoom Android Development] mulletcutter:
At risk....my mytouch3g, slide, mytouch4g and xoom are at risk haha let me know when something bad happens.

XOOM
[Xoom Android Development] Prod1702:
Running great on the 1.5ghz and GPU OC BRD great work man keep it up.
[Xoom Android Development] chbennett:
Riptide=amazing.
[Xoom Android Development] JFMFT:
If already on a previous Tiamat 3.1 kernel, can we just flash Riptide, or do we still have to flash the boot image and the kernel back to back?
[Xoom Android Development] Mr Bland:
I just flashed Riptide, no problems.
[Xoom Android Development] JFMFT:
I flashed it too, but I didn't flash any boot image so I wasn't sure. I was on the 1.6Ghz before, but I wanted the GPU overclock... I wasn't sure if it flashed successfully (even though it appeared to in Clockwork Recovery). I must say, it appears to have worked. My keyboard is 100% lag free (software keyboard). This is phenomenal! Amazing work BRD!

Can I ask, how much is the GPU overclocked? More a curiosity than anything. Won't change anything for me :-P
[Xoom Android Development] Mr Bland:
I did run into a little quirk while trying to transfer Riptide to my SD. It would not transfer with root explorer though other kernels would. I tried with androzip and got a system permissions error. Then instead of just clicking to download like I usually do I long clicked the link and chose "save link". Riptide now downloaded as mCZhRd.zip, instead of the usual taimat_zoom(etc.).zip. This file transferred fine with no arguement from my file explorers. After I flashed mCZRd.zip I checked "about tablet"/"kernal" and everything looks right. My Zoom is running better than ever before. Even downloaded Riptide, ran beautifully :) Thanks BRD. Just though I'd share that one quirk I ran into.
[Xoom Android Development] sfld:
Set CPU working wit Riptide?
[Xoom Android Development] gerald410:
Yes sir! 10chars
[Xoom Android Development] Salpula:
Are there updated cifs modules available for any of these kernels?

Also can you control the gpu overclock? For the sake of battery and what not, I'd like to have the option to not overclock the 95% of the time that I don't need it, it if I switch to that kernel.
[Xoom Android Development] ruvort:
Yes it would be nice to control the gpu. Even if we don't have a fancy app to do it right away, I would be just fine with running commands in a terminal or running some sort of script.
[Xoom Android Development] malaeus:
still no answer. is there a difference between rooting a stock 3.1, or upgrading one that came with 3.0.1?

if mine has 3.1 installed out of box, can i safely root and flash this? or is there something special in the upgrade process that BRD has done differently?
[Xoom Android Development] KING SKILLZ:
Thanks 4 sharing, was stuck also.
[Xoom Android Development] jase33:
Root however you like. Flash the boot image and kernel as directed from the op. You should be fine.

Sent from my HTC HD2
[Xoom Android Development] drawde:
is anyone hitting the 4800 quadrant on riptide? unless i'm doing something wrong, i'm getting about 2200-2300 on performance.

EDIT: ah, forgot the new boot.img's. getting 4100-4200 now. It's not 4800 but i'll take it.
[Xoom Android Development] MrGinger:
Hi BRD, just wondering if there's a technical reason why you don't release just one kernel with all the oc steps available?
[Xoom Android Development] Lolento:
Brd,

Does either the Riptide kernel or the 1.5ghz of have USB mass storage working?
[Xoom Android Development] sportedwood:
I get some artifacts in riptide after about 4 or 5 min of gameplay, it gets pretty bad sometimes then just goes away, guess I have a weak xoom :mad:.
[Xoom Android Development] pyrator:
there is a limited number of steps available
[Xoom Android Development] xjack:
I got a few artifacts also. Check your temps, I used setcpu to clock it down at 35 degrees. (95 Fahrenheit). Tegra gets hot quickly at these speeds.
[Xoom Android Development] Psychokitty:
Which one is getting hot, the CPU or the gpu?
[Xoom Android Development] mulletcutter:
This fix lag when typing on browser?
[Xoom Android Development] lrs421:
I'm not sure if it officially does but I've been runnjg the 1.5 gpu oc version and typing in the browser has gotten much faster.

Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
[Xoom Android Development] RoryPG:
No lag issues typing. Looking good. But, I am having issues typing numbers with appear as their corresponding symbols appear, instead. Don't, - Also back key not always working, as displayed at beginning of this sentence. Not sure if this is brd's hc3.! or something else. But, lag is gone, gone, gone!!!
[Xoom Android Development] yoda1:
Sd Card support

my question is this if the sd card is able be use in the recovery but why cant you use it like another form of storage in the device or am i missing some thing. i have fallowed all the steps to use it but nothing :(
[Xoom Android Development] hm1b:
BRD, love your work...I noticed some delay on booting after updating to !!Riptide version..the rest are pefect...thank u for making our xoom worth the excitment
[Xoom Android Development] sooner2k1:
I've installed everything for the Riptide Edition, and everything seems to be working perfectly, except my Xoom is acting like it doesn't have root access when it does. I get a message in SetCPU that the Xoom can't tell its rooted, and i'm also unable to perform root functionality in Quickboot to reboot into recovery. I've tried restarting, but no luck.

Superuser isn't even giving me notification that these apps need root access.

I've confirmed I have root via adb shell (receiving "#"), so i'm not sure what to do.

Any suggestions are appreciated.
[Xoom Android Development] lrs421:
Weird, is busybox installed? You may want to try there.
[Xoom Android Development] sooner2k1:
I just tried to run busybox and it error-ed out and said root access was denied. Now i'm in a tough situation. Is there a way to re-root once you already have Tiamat installed, or am I going to have to flash back to something else, root and then start over?

This stinks.
[Xoom Android Development] lrs421:
Stinks indeed, if you already verifed root in adb it sounds like a permissions issue. It might be a long shot but try fixing permissions in recovery.
[Xoom Android Development] sooner2k1:
I was able to fix it by running the root instructions for stock 3.1 and then re-flashing Tiamat RipTide.

Thanks for your help on this.