yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] cunnie84:
Hey guys ive just spent the last hour or so reading everyones comments on here and im still unsure if i want to install this on my everest xoom so here's the question . . . what do you guys think ???? Should i install it and do i have to install it everytime i flash a new nightly ???
[Xoom Android Development] shpitz461:
It's very easy to go back to the ROM's kernel, you can extract it from the zip (boot.img) and then flash using fastboot.

Tablet needs to be in fastboot/bootloader mode.
[Xoom Android Development] flar2:
New for testing. The kernel itself is working great for me, I think it will be stable but I need testers. I tried to improve battery life in this version. The biggest thing to test is the universal installer, I can't possibly test this with every ROM and variant of the Xoom, so please try this out and let me know if there are any issues with the installation. It should work on any combination of wingray, stingray, everest, EOS4, CM10.1, My Android, and Baked BB-8.

Download:

ElementalX-Xoom-v1.0 *beta*

ElementalX-Xoom-v1.0_vanilla *beta*

Changes:

-vanilla version does not overclock graphics (oc version is recommended unless you have problems)

-s2w: choose 1 or 2 finger sweep

-s2w: fixed to ensure only single motion is detected

-add ROW scheduler

-ROW is now default scheduler

-automatic process group scheduling

-added Joes' RCU

-screen off max frequency of 486MHz

-cpu1 off when screen is off

-enable extra CIFS stuff

-avoid loadavg moire

-add arm cpu topology

-properly detect BB8 stingray

I updated sweep2wake.

Now it only registers a single swipe, if you lift your finger it won't work. This fixes a bug where you could turn the screen on or off by touching each edge of the screen.

I've also added a new feature. You can choose whether sweep2wake uses one finger or two. Default is one, like before. I added the two finger option because my daughter plays a game where you sweep all the way across the screen sometimes. You are much less likely to accidentally turn off the screen with two finger enabled.

You can change this option in etc/elementalx.conf

S2W=0 sweep2wake disabled

S2W=1 sweep2wake with one finger

S2W=2 sweep2wake using two fingers
[Xoom Android Development] Winesnob:
Re: [KERNEL][March 18] ElementalX-Xoom-v0.8 | OC | UV | S2W | Now works with CM10.1

Just tried to install vanilla on My Android 4.2.2 and it didn't take. Using CWM touch 6.0.2.9, recovery display indicated that all was well. Wiped cache and dalvik prior to install attempt.
[Xoom Android Development] flar2:
Could you send me the install log?

Otherwise I have no clue why it didn't install.

I've only tested it with TWRP
[Xoom Android Development] Winesnob:
Re: [KERNEL][March 18] ElementalX-Xoom-v0.8 | OC | UV | S2W | Now works with CM10.1

Can you give me some idea of where that log is located?
[Xoom Android Development] flar2:
/tmp/recovery.log

Unless it's different in CWM. You have to grab it while you're still in recovery.
[Xoom Android Development] Winesnob:
Re: [KERNEL][March 18] ElementalX-Xoom-v0.8 | OC | UV | S2W | Now works with CM10.1

Yeah, nothing I was able to locate. Sorry.
[Xoom Android Development] flar2:
Any error message or anything?

What exactly happened?
[Xoom Android Development] Winesnob:
Re: [KERNEL][March 18] ElementalX-Xoom-v0.8 | OC | UV | S2W | Now works with CM10.1

No error messages, display showed Wingray, went through the elemental X drawing, and then showed installation complete. When I rebooted, the My Android kernel was fully intact as displayed in 'about tablet', none of the s2w functions were present.
[Xoom Android Development] flar2:
Alright I figured it out, reposting...

New for testing. The kernel itself is working great for me, I think it will be stable but I need testers. I tried to improve battery life in this version. The biggest thing to test is the universal installer, I can't possibly test this with every ROM and variant of the Xoom, so please try this out and let me know if there are any issues with the installation. It should work on any combination of wingray, stingray, everest, EOS4, CM10.1, My Android, and Baked BB-8.

Download:

ElementalX-Xoom-v1.0 *beta*

ElementalX-Xoom-v1.0_vanilla *beta*

Changes:

-vanilla version does not overclock graphics (oc version is recommended unless you have problems)

-s2w: choose 1 or 2 finger sweep

-s2w: fixed to ensure only single motion is detected

-add ROW scheduler

-ROW is now default scheduler

-automatic process group scheduling

-added Joes' RCU

-screen off max frequency of 486MHz

-cpu1 off when screen is off

-enable extra CIFS stuff

-avoid loadavg moire

-add arm cpu topology

-properly detect BB8 stingray

I updated sweep2wake.

Now it only registers a single swipe, if you lift your finger it won't work. This fixes a bug where you could turn the screen on or off by touching each edge of the screen.

I've also added a new feature. You can choose whether sweep2wake uses one finger or two. Default is one, like before. I added the two finger option because my daughter plays a game where you sweep all the way across the screen sometimes. You are much less likely to accidentally turn off the screen with two finger enabled.

You can change this option in etc/elementalx.conf

S2W=0 sweep2wake disabled

S2W=1 sweep2wake with one finger

S2W=2 sweep2wake using two fingers
[Xoom Android Development] flar2:
Anyone who downloaded this earlier should do it again, it definitely didn't install. I had the wrong boot size when it tried to build the boot images, and therefore it didn't install anything. Sorry about that.
[Xoom Android Development] shpitz461:
Installed (Sting), enabled intellidemand/row, set on boot

rebooted once, now it boot-loops

going to dig up a log
[Xoom Android Development] notbrodie:
dude, you're awesome. have a drink on me

#2VV25236NF097673W
[Xoom Android Development] LQQKS:
Re: [KERNEL][March 18] ElementalX-Xoom-v0.8 | OC | UV | S2W | Now works with CM10.1

1.0 booted perfectly on Everest CM10.1. Wait a few charge cycles to report back.

Thanks again \o/

Edit: set to intellidemand and row and still boots - no boot loops

And also changed s2w to 2 fingers with no dramas \o/

sent from Evita
[Xoom Android Development] shpitz461:
OK, it boots fine the 1st time i flash, then once i reboot, it boot-loops.

Attached is kmsg, do you see anything? Sting EOS4 182
[Xoom Android Development] flar2:
The log is from a CyanogenMod kernel. What ROM are you on and did you redownload? The first files I posted didn't work.
[Xoom Android Development] shpitz461:
The 1st download link was gone, so i d/l'd the 2nd (most current).

Could it be it didn't flash the kernel? cause i went to about upon initial boot and it showed elemental v1.0 .

going to try again...

Looks like i pulled the wrong file, sorry. going to flash v1.0 again and report back.

---------- Post added 4th April 2013 at 12:08 AM ---------- Previous post was 3rd April 2013 at 11:53 PM ----------

Could it be there's no last_kmsg under /proc/?

After flashing, it boots up fine. Once I reboot, the EOS logo appears for a second then it reboots, over and over.

There's no last_kmsg, only kmsg.
[Xoom Android Development] uzi2:
Installed (Wing dream ROM) enabled intellidemand/row - edited conf for 2 fingered s2w - reboot - all is good.

Possibly a Stingray or ROM related issue?

Edit: S2W sleeping, but not waking in 2 fingered mode... power button required to wake screen.
[Xoom Android Development] flar2:
If it showed 1.0, then it must have flashed. If it boots up the first time, it must be some setting that prevents it from booting again. Check that no apps are are trying to set something and disable anything that sets freqs or governor at boot.

Could you verify that s2w works normally in one finger mode
[Xoom Android Development] uzi2:
Re: [KERNEL][March 18] ElementalX-Xoom-v0.8 | OC | UV | S2W | Now works with CM10.1

Yes, it works fine in one finger mode. Two finger is ok with sleeping, but hit and miss with waking.

Swyped from my Xoom
[Xoom Android Development] tselling:
Bootlooping on Dual Core screen with Baked BB-8 stingray.

FYI, it is detecting stingray and BB on install but bootlooping.
[Xoom Android Development] Winesnob:
Not sure if my settings are completely off (1408 Mhz, interactive governor), but felt like I was fighting with the tablet while running this kernel. I went back to the My Android kernel with the same performance settings and this tablet flies.
[Xoom Android Development] shpitz461:
I uninstalled TricksterMOD, so all I had was EOS' own cpu control working, and it bootloops.

There was no last_kmsg, is that normal?

The EOS logo would appear for a second or two then it reboots. Only way to get back to normal is to reflash the EOS kernel.
[Xoom Android Development] tselling:
oops wrong thread.
[Xoom Android Development] flar2:
Strange, I get excellent performance, better battery life and higher benchmarks than ever before with v1.0.

If there's no last_kmsg it means the kernel didn't load at all. Perhaps the boot.img has changed or something.

It's too bad the xoom is so fragmented, it's really hard for me to keep up with all the different models and ROMs and nightlies.
[Xoom Android Development] shpitz461:
Maybe it's cause I used CWM? I can try with TWRP 2.3.3 and report back.

Very strange since it did boot up with elemental1.0, but then once I reboot, it boot-loops.

So i go into recovery and look for last_kmsg and there's none, only kmsg.
[Xoom Android Development] hochoch:
Booted and rebooted fine for me using latest twrp, eos4 wingray and trickster installed. Thanks!!!!
[Xoom Android Development] flar2:
Download:

ElementalX-Xoom-v1.0 *beta*

ElementalX-Xoom-v1.0_vanilla *beta*

I made a minor adjustment to get intellidemand as default and I think it will now work with Baked bb8 stingray
[Xoom Android Development] flar2:
You could try grabbing the installation log too. Right after installing, while still in recovery:

adb shell cat /tmp/recovery.log > recovery.log
[Xoom Android Development] shpitz461:
Cool, i'll try that as well.

Flar, I compared the following files:

bootimg.cfg.stingray, bootsize = 0x46b800

and

bootimg.cfg.cm.stingray, bootsize = 0x46b000

The other XOOM types do not have a difference in the bootsize, could that be the problem with Stingray? All other types are bootsize = 0x46b000.
[Xoom Android Development] flar2:
For some reason it needs a different boot size than the others. I think I'll download the latest eos stingray and see if the boot.IMG was changed. I know they've done some work on the eos kernel recently.

I'm also going to see if I can make new install method that injects the kernel into existing boot.IMG. it would be easier to maintain.
[Xoom Android Development] shpitz461:
I can upload the boot.img from EOS4 182 if you'd like...
[Xoom Android Development] flar2:
Thanks, that would be helpful
[Xoom Android Development] shpitz461:
There you go: boot.img

MD5: 507b388c7dc73293b39dd6c7da8c372b

Ok, i flashed the newest zip with TWRP 2.3.3, attached is log.

Going to reboot and report.

UPDATE: Flashed with TWRP, works fine, no issues, must've been CWM...
[Xoom Android Development] flar2:
^^thanks, it looks TWRP is necessary for the installer to work properly.

I did a bunch of testing tonight.

ElementalX-v1.0 Installed fine on:

EOS4

Baked BB8

My Android

CM10.1

Orca

I also installed CM10 and the kernel works on it too, but I have to fix the installer to include the correct boot.img for it.

So it looks like this kernel will work on any ROM for the Xoom, but they all have different ramdisks and command lines. I'm going to experiment with injecting the ElementalX zImage into the installed boot.img.
[Xoom Android Development] LQQKS:
Good news for streamlining the kernel \o/

any update on aroma installer?

sent from Evita <3, my rooted, S-Off Elemental Venomized HTC One XL 4G \o/
[Xoom Android Development] TheMainCat:
Team Eos has made some significant changes to their kernel on their 188 build. You may not want to use their 182 version when tweaking yours.
[Xoom Android Development] flar2:
I tested on the latest version of all them, including EOS 188 wingray and 183 stingray. It shouldn't matter if they make any changes to the kernel. Mine diverged pretty far from all of them over the past few releases. As long as the board-specific files stay the same the kernel will work on any Rom for this device.
[Xoom Android Development] tselling:
cifs doesn't seem to be working right. I can mount the share but when I go to the mounted directory, its empty.
[Xoom Android Development] shpitz461:
What do you use to mount CIFS?
[Xoom Android Development] tselling:
cifsmanager.

BTW this is with the My Android for Wingray (on my stingray) with Elemental X 1.0

Baked BB-8 stingray still bootloops when I install Elemental X 1.0 (and I replaced CWM with TWRP but no difference).
[Xoom Android Development] shpitz461:
Oh, I see. I could never get 4G to work right on BB so I stopped trying.

Also had issues with ORCA, but EOS4 seems stable.
[Xoom Android Development] flar2:
Download:

ElementalX-Xoom-v1.0

ElementalX-Xoom-v1.0_vanilla (no GPU overclock)

New universal installer, this one is truly universal. It should install on any ROM for any variant of the Xoom (Wingray/Stingray/Everest)

Yes, this means you can use it on CM10 (tested) and should work on EOS3 and others (not tested)

TWRP recovery is suggested, I haven't tested it with CWM.
[Xoom Android Development] dsbnz:
Works great on Orca Wingray. Using vanilla version.
[Xoom Android Development] tselling:
The newest version 1 works now for me with baked bb-8 stingray and cifs is working...great job! However, I cannot find where to set overclock and governor. Where are these settings located? Thanks.
[Xoom Android Development] LQQKS:
Androidfilehost is playing up :(

Edit: got it \o/

sent from Evita

---------- Post added at 12:41 PM ---------- Previous post was at 11:57 AM ----------

Installs with no dramas but governor by default is still set to on-demand, not intellidemand.

Cheers

sent from Evita <3, my rooted, S-Off Elemental Venomized HTC One XL 4G \o/
[Xoom Android Development] flar2:
I don't think they have those built in on Baked. You'll have to download an app like No Frills CPU control.

A lot of the ROMs have settings for cpu, governor and scheduler that will override whatever I try to make it. It's best to set it as you like it with the built-in settings on EOS, CyanogenMod, etc.
[Xoom Android Development] LQQKS:
I'll try that, the intellidemand doesn't stick on reboot but I'll have a play with CM settings

Edit: they do stick when selected in CM ssetting - if only there was a s2w option there I could dump KT altogether
[Xoom Android Development] flar2:
Version 1.0 is official. The kernel is very stable, I've been running it for quite a while now. My battery life has increased and the ROW scheduler is quite snappy. I have the very latest version of ROW, and had to backport some stuff to get it working. Because of that, and the newly implemented screen-off stuff, I really tested it thoroughly.

Also, please let me know what ROMs this sucessfully works with.
[Xoom Android Development] mcarrion78:
Just flashed. Nice and easy install. Running on BB8 lagfree @1504 with row scheduler. Everything running nice and smooth. Nice work keep it up.
[Xoom Android Development] LQQKS:
Just wanted to share this

Starting from 100%. Even tho she's been in Deep Sleep for 12 hours (96% of the time), she's still lost 40% battery.

This was on the first 1.0 uploaded

Sent from my rooted Xoom MZ601

running CM10.1 JellyBean 4.2.2

using XDA Premium app \o/
[Xoom Android Development] Farik335:
I've installed it on CM10, and overall kernel is good, but when screen turns off, device reboots after couple of seconds
[Xoom Android Development] b8892778:
Can't install on EOS4...

In TWRP install fail.
[Xoom Android Development] badaas:
Eos 3 freezes on boot then reboots. I noticed on boot max GHz was 1700 but standard eos kernel on 1700 runs fine. I now can't get to CPU settings at all just freezes even with fresh install.

installed with team rogue and twrp same results :-$
[Xoom Android Development] NeoPreacher:
the kernel runs quite fine on cm10.1 :) . but s2w don´t work for me. got deep freeze with black screen while trying to wake up and sometimes screen is white and freezes. has anybody tips for makin it work? :confused:
[Xoom Android Development] flar2:
Could you install gsam battery monitor? It will tell you exactly what is using battery.

Does this happen every time? Do you have s2w enabled? Do you have any apps that try to set screen off profiles? Wingray, Stingray or Everest? Did you try the vanilla version (without GPU oc)?

Any time there is a reboot, it is helpful to me if you provide a log:

adb shell cat /proc/last_kmsg > last_kmsg.txt

Error message? Recovery log?

adb shell cat /tmp/recovery.log > recovery.log

Did you try lowering the overclock? Did you try the vanilla version (without GPU oc)?

Freezing is a sign of pushing the hardware too far.

Does it work alright with s2w disabled? Have you tried the vanilla version (without GPU oc)?
[Xoom Android Development] bigrushdog:
Flar2 you should get a github up and running. I started playing with the xoom kernel again and have some good commits.
[Xoom Android Development] nodnarb:
I'm running CM 10.1 Nightly 4/5/13.

S2W worked by default.

Seems stable overall and I'm using version 1.0.

Many Thanks!
[Xoom Android Development] flar2:
https://github.com/flar2/xoom-ElementalX

You will probably want the updated s2w and I have a newer version of ROW that required many changes
[Xoom Android Development] LQQKS:
Hope this might help?

I've since uninstalled KT (no point since i choose everything in CM10.1 settings now and s2w with a text editor) but it hasn't gone into Deep Sleep overnight

Sent from my rooted Xoom MZ601

running CM10.1 JellyBean 4.2.2

using XDA Premium app \o/
[Xoom Android Development] flar2:
I can't really tell much from that, you have to look around within gsam a bit to see if there are any wakelocks or anything. Your previous screenshot showed it was in deep sleep for all but a few minutes.

For reference, I'm also on CM10.1. I have 73% battery left, just over 15 hours since last unplugged, just under 2 hours of screen time, and 52% of the battery use has been by the browser.

I would charge it up to 100% and reboot it. Then use it as normal for a while and see what happens.
[Xoom Android Development] extremetempz:
EOS 3 Fails To Boot

I have tried both versions of 1.0 and it gets stuck on boot screen and reboots I'm on 155 BTW I was really looking forward to using this :( on mz604
[Xoom Android Development] flar2:
I'll download eos3 and see if I can get it to work
[Xoom Android Development] LQQKS:
Thanks flar I'll give that a try :) but I don't think I ever get battery life like that

Would a full and restore from nandroid help? Haven't wiped in over a year

Sent from my rooted Xoom MZ601

running CM10.1 JellyBean 4.2.2

using XDA Premium app \o/
[Xoom Android Development] flar2:
Couldn't hurt, if you've been using it that long without a clean slate there could be all kinds of things going on.

I installed EOS 3 and then installed ElementalX 1.0 and it worked fine. However, the max cpu frequency was set to 1700. This is probably why it's not working for you.

I will do something to limit the frequency to 1GHz by default.
[Xoom Android Development] shpitz461:
Flar, awesome work with the latest, works silky smooth with EOS4 184 Stingray.
[Xoom Android Development] extremetempz:
could a init.d script make it 1GHz by default
[Xoom Android Development] NeoPreacher:
without s2w everything runs fine on non-vanilla and vanilla. but no chance for me to get s2w working. i regcognized an issue difference. when i sweep from top to bottom i get a white screen that goes off after seconds and i can wake the screen normally with the button. but when i do it from left to right i get big freezes. i tried to wait and wake the screen as usual using button and screen lights up after a minute or two but i am unable to unlock. need to hard reboot and set s2w off.
[Xoom Android Development] badaas:
Yep on eos 3 its blind luck you can boot due to startup freq of 1700, works fine else. Just can't get it to boot less than 1700 :-$

Same with vanilla

Thanks
[Xoom Android Development] NeoPreacher:
i made some antutu benchmark tests. the difference is not really big. with vanilla i got 7255 score and with the non-vanilla one i got 7343. i set govenor to lagfree and scheduler to ROW.
[Xoom Android Development] flar2:
I've got a fix for the boot frequency, I'll post it later.

Do you have a different launcher or some app that uses the edge of the screen?

Also, could you send me /proc/last_kmsg
[Xoom Android Development] NeoPreacher:
no I don't use any other launcher. and please excuse but I can't find the file you need in that folder, just kmsg and I'm unable to copy that.
[Xoom Android Development] Sparty73:
I'm having the same issue occur. Does not freeze up or anything while screen is on, but reboots after a few seconds with screen off.

Also, I'm having issues changing Sweep2wake. I'll change the value from 1 to either 0 or 2, but it still stays on one finger wake. I'm editing the ElementalX.conf with ES Text Editor, and the value seems to be saving correctly. Issue persists after reboot.

Baked - Stingray

1400mhz max/300mhz min

interactivex2/row
[Xoom Android Development] flar2:
Something else must be changing the s2w value. Ensure that you don't have any other apps trying to change it.

I'm releasing an update that has a toggle for the max screen off feature.

Try the new version and set MAXSCROFF=0 in /etc/elementalx.conf

This will disable max screen off frequency and hopefully fix the issue of reboots while screen is off.
[Xoom Android Development] flar2:
This update ensure that the maximum frequency is 1000MHz during startup. Should help those with bootloops or freezes due to it clocking up to 1700.

I've also added a toggle for max screen off, you can change this in /etc/elementalx.conf. You can also change the max screen off frequency

If you want to edit the settings directly, the sysfs entries are at /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_enabled and /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq

DOWNLOAD

ElementalX-Xoom-v1.1

ElementalX-Xoom-v1.1_vanilla (no GPU overclock)

Changes:

-fix: boot frequency is max 1000MHz

-add toggle for max screen off

-add adjustable max screen off frequency

NOTE: two or three people downloaded this before I fixed a typo in /etc/elementalx.conf. If you downloaded this right away and want to change screen off defaults, make sure it says MAXSCROFF and MAXSCROFF_FREQ (the typo had them as MAX_SCROFF and MAX_SCROFF_FREQ)
[Xoom Android Development] Sparty73:
Same issues persist, even after switching to 1.1 and changing MAXSCROFF to 0.

I'm using SetCPU. Could that have anything to do with it?
[Xoom Android Development] NeoPreacher:
also still the same issues, plus when i set cpu to 1,7 i got reboots and the govenor and scheduler settings didn´t change. i set it back to 1,6 everything runs fine.

now i got last_kmsg files for you if needed ( can´t attach them because of size restrictions, so you get links :) )

https://docs.google.com/file/d/0B_hPS_PKbQ2-eEU0eWZZdDkxUEk/edit?usp=sharing

https://docs.google.com/file/d/0B_hPS_PKbQ2-Z0tnaUtCQmFRRUU/edit?usp=sharing
[Xoom Android Development] badaas:
Eos 3 now booting
[Xoom Android Development] lepa71:
May be your Xoom can't run at 1.7. Mine can't either.
[Xoom Android Development] shpitz461:
How much you can O/C depends on your hardware, not all XOOMs were created equal. Mine are unstable @ 1.6+, I'm happy with 1.5GHz.
[Xoom Android Development] drewski_1:
+1

Mine does 1.6, but unstable mess @ 1.7
[Xoom Android Development] NeoPreacher:
+1
[Xoom Android Development] thenemis:
so i can set 1300 for boot ?