Hi!
I am using TEAM EOS MZ-604 nightly.
Which Kernel does it have?
is it using Tiamat AOSP Kernel 3.0.5?
And i would like to have power save Governor.
How can i contact about it?
someone?
I dont know how can i send message to solarnz or somtin'
They are available in the IRC channel:
asimov.freenode.net
#xoom
You should be able to flash 3.0.5 with that nightly if that's what you're looking for.
The very latest nightly has Tiamat 3.0.8.
We don't have the powersave governor, however the default is interactive. If you're looking for a governor that doesn't clock the tablet up too much, try the ondemand or conservative governor.
solarnz said:
The very latest nightly has Tiamat 3.0.8.
We don't have the powersave governor, however the default is interactive. If you're looking for a governor that doesn't clock the tablet up too much, try the ondemand or conservative governor.
Click to expand...
Click to collapse
Glad to see Solarnz here. I had a question about governors too. I know on my Galaxy Nexus, most of the kernels come with Hotplug and the like that disable one of the cores when not in use. Are there any governors for the Xoom that perform the same function? IMO's learnkernel has HotplugX and (i believe his own) InteractiveX (which performs the hotplug function in addition to being an interactive gov). Why don't we see this sort of development on the Xoom? Not that I'm demanding it or anything. Just surprised to not see more mention of it. Do we not need it? Is our Tegra hardware vastly different in operation?
★ ☆ [Kernel] NuK3RN3L | s2w+s2s | 01-21-14 | 1,900MHz | 3.0.84 | Sense/AOSP | ☆ ★
-NuK3RN3L-
OVERCLOCKED
Edition
Now added!
Santod's Mecha ICS Sense/AOSP Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD:
NuK3rn3l mecha Final
sweep2wake
sweep2sleep
16 Governors
TCP Controls
Zram/Swap
Linaro
OTG
01-20-14
Use Trickster Mod to enable Wake options
You need an updated version of Busybox from the Play Store to use Trickster Mod.
Once that's installed, open it and run the installer.
Then you can install Trickster Mod, grant it su permissions, and use it to enable s2w+s2s and adjust all other kernel settings and tweaks.
Trickster Mod can be found here.
-NuK3RN3L-
stock frequencies
current build
~ or ~
NuK3RN3L-
Overclocked Edition
1,516MHz Default/Max
current build 6-25-13
+ LagFree
-NuK3RN3L-
Aosp NuK3RN3L, with working wifi on Aosp ICS and Jelly Bean.
Only use this for this one on Aosp roms. (CM9/CM10)
[URL="http://www.androidfilehost.com/?fid=23017610006233856"]NuK3RN3L ICS/JB Aosp OC Edition
[/URL]
These have been well tested, but use at your own risk!
I am not responsible for you or your device or anything that you do to it!
Included Governors:
SavagedZen
lulzactive
adaptive
hyper
scary
skywalker
brazilianwax
fantasy
SmartassV2
interactive
conservative
userspace
powersave
lionheart
ondemand
performance
How to install:
Flash zip in Recovery
Wipe cache and Dalvik cache
Reboot
This can be flashed to any current ICS roms!
Sense and AOSP!
NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...
Looks like we may have an AOSP/Sense ICS Hybrid Kernel.
On Aosp, Data and Netflix do work, camcorder not yet.
Will work on things with Joe to improve this.
Click to expand...
Click to collapse
I will try and update my git repo every 7-90 days until I automate it into my buildbox process...
Compiled using the 4.4.3 gcc toolchain.
Big thanks to my buddy Ziggy for his help and inspiration.
XXPachaXX for his work on msm7x30
Flemmard for his work on msm7x30
Also to HTC for finally releasing the source code...
HTCDEV Source files: my copy
FAQ:
Hopefully this answers some common questions.
I will add to this as kernel changes are made.
On UnSenseROM Jelato, there is a script in /system/etc/init.d called 00_vdd_levels if I recall the name exactly.
It's essentially a text file that should be either deleted, or remove the ## from the name of it so it doesn't run at boot.
Then whatever app is used to control governors and clock speeds will not get reset upon rebooting, whether you use the built in CPU Controls or No Frills, etc,..
On my other roms, the same rule applies, if there is a script in /system/etc/init.d with vdd levels in the name, remove it or rename it.
On NuSenseX ROM you should be careful touching anything in init.d, or you could break your wifi connection.
Soon, I intend to have kernels that will be baked into each rom, and there will be no need to concern oneself with any of this, and it's really nothing of much concern anyhow.
But I think that about covers most cases...
____
GOVERNORS
1) Ondemand:
Default governor in almost all stock kernels.
One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system.
Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question.
So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle.
Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings.
One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval.
The instant requirement can respond quickly to workload change, but it does not usually reflect workloads real CPU usage requirement in a short enough time and it may cause it to frequently change between highest and lowest frequency.
2) Conservative:
A slower Ondemand which scales up slowly to save battery.
The conservative governor is based on the ondemand governor.
It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization.
However, the conservative governor increases and decreases CPU speed more gradually.
Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle.
Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency.
The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization.
For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
3) Interactive:
(currently my recommended governor for best overall battery and performance)
Can be considered a faster ondemand. So - more snappier, less battery!
Interactive is designed for latency-sensitive, interactive workloads.
Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle.
The governor has the following advantages:
1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling.
2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed.
Interactive - It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc.
Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle.
When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks.
If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
4) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
5) Powersave:
Locks max frequency to min frequency.
Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
6) Performance:
Sets min frequency to max frequency.
Use this while benchmarking!
7) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people.
The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after.
It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq.
This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on.
There's no upper limit for frequency while screen is off (unlike Smartass).
So the entire frequency range is available for the governor to use during screen-on and screen-off state.
The motto of this governor is another option for balance between performance and battery.
8) Lulzactive:
Basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads.
Like smartass, it has a sleep profile built-in.
9) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
____
So, Governors can be categorized into 3/4 on a high level:
1.a) Ondemand Based:
Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions.
Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree.
1.b) Conservative Based:
Members: Conservative, Lionheart, LionheartX
2) Interactive Based:
Works on "make scaling decision when CPU comes out of idle-loop" principle.
Members: Interactive, InteractiveX, Lulzactive, Luzactiveq, Smartass, SmartassV2, Brazilianwax, SavagedZen.
3) Weird Category:
Members: Userspace, Powersave, Performance.
Click to expand...
Click to collapse
___
Changelog:
__
062513
Updated 1,516 OC'd Edition!
Added Governors:
LagFree
Lulzactive
SmartassV2
7 more modules built in
062213
Added 1,516 OC'd Edition!
Adjusted cpu frequency tables
Adjusted voltages
Enabled 1,516 MHz Overclock as Default
062113
Powersave governor added for those of you trying to squeeze more out of the battery, or only using the device on wifi.
062013
Interactive governor added for better response time, keyboard reaction, etc,..
Reserved...
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
santod040 said:
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
Click to expand...
Click to collapse
Any chance of a dual boot setup?
Check out the Devil kernel and recovery for the note 2......
Would be nice to have a slimmed down AOSP ROM and a Sense one for when you wanted it.
I'm not trying to be rude to anyone but let's keep the feature requests to a minimum until he gets the more important aspects worked out. There is a lot of testing going on with just what this kernel can do as we speak. I'm sure once things calm down the other features can be implemented.
Sent from my ADR6400L using Tapatalk 2
Says AOSP in the title. Can this be used with the CM9 in this thread?
Sent from my NusenseX Bolt using Tapatalk 2
arizonaomnia said:
Says AOSP in the title. Can this be used with the CM9 in this thread?
Sent from my NusenseX Bolt using Tapatalk 2
Click to expand...
Click to collapse
This can be flashed to any current ICS roms!
Sense and AOSP!
NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...
Looks like we may have an AOSP/Sense ICS Hybrid Kernel.
On Aosp, Data and Netflix BOTH work, camcorder not yet.
Will work on things with Joe to improve this.
Congrats on RLS brosif these guys are lucky you are still carrying the infected flame for this phone !!!!
santod040 said:
This can be flashed to any current ICS roms!
Sense and AOSP!
NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...
Looks like we may have an AOSP/Sense ICS Hybrid Kernel.
On Aosp, Data and Netflix BOTH work, camcorder not yet.
Will work on things with Joe to improve this.
Click to expand...
Click to collapse
Anyone know if it fixes the Gmail whiteout? I can live without the camcorder but the Gmail thing was too much.
Sent from my NusenseX Bolt using Tapatalk 2
Virus said:
Congrats on RLS brosif these guys are lucky you are still carrying the infected flame for this phone !!!!
Click to expand...
Click to collapse
Good to see you here @Virus.
I haven't seen you since my EVO days!
i flashed both the stock and oc'd versions of this kernel over joe black's cm9 (which was also clean flashed... even wiped my sd) and wifi isn't working. it flat out won't turn on.
i don't have my tbolt in service anymore, so without wifi, i can't use it at all. wifi worked with the included kernel on joe's cm9 rom.
i'm a little pressed for time at the moment, but if a logcat would be helpful, lemme know and i'll post one when i'm back from vacation at the end of the upcoming week.
namurt said:
i flashed both the stock and oc'd versions of this kernel over joe black's cm9 (which was also clean flashed... even wiped my sd) and wifi isn't working. it flat out won't turn on.
i don't have my tbolt in service anymore, so without wifi, i can't use it at all. wifi worked with the included kernel on joe's cm9 rom.
i'm a little pressed for time at the moment, but if a logcat would be helpful, lemme know and i'll post one when i'm back from vacation at the end of the upcoming week.
Click to expand...
Click to collapse
Yeah that's a known issue with flashing it seperate.
There's a couple things not included in the kernel zip, that have to be changed Rom side.
These changes are easily made and Joe should have an update posted soon with this kernel in it and the needed Rom files to have WiFi working.
Sorry for the inconvenience.
It's just become known it would work as well as it does.
Fixes and improvements to his Rom and this kernel are coming.
If he doesn't have it up soon, I'll post a patch for using this on his Rom.
Sent from my HTC6435LVW using xda app-developers app
sweet jesus, you are one amazing dev!
that was a lightning quick response, hah.
it's so nice to see our bastard child of a device still getting some love.
santod040 said:
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
Click to expand...
Click to collapse
You know....if you WANTED to....you know, just for sh1ts and giggles.....you COULD post the version of this without working data, just to give a preview and let people play with it. I remember that Liquid did something similar with an early build of OCS for the Thunderbolt. Or not. Whatever you want to do is fine, of course.
*drooling*
Sent from my NusenseX Bolt using Tapatalk 2
namurt said:
sweet jesus, you are one amazing dev!
that was a lightning quick response, hah.
it's so nice to see our bastard child of a device still getting some love.
Click to expand...
Click to collapse
Yep, santod is the man, no doubt about it.
This device launched more than 2 years ago with froyo, was upgraded to gingerbread, eventually got ICS, and may yet see unofficial jellybean!? That's an amazing run for any phone IMHO.
santod040 said:
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
Click to expand...
Click to collapse
where i can find thunderbolt aosp jelly bean ROM...
olredi tried this kernel on Jelato ROM and make ma fone awesomely blasting fast :good:
guinzo said:
where i can find thunderbolt aosp jelly bean ROM...
olredi tried this kernel on Jelato ROM and make ma fone awesomely blasting fast :good:
Click to expand...
Click to collapse
AOSP jellybean hasn't been released yet, they're still working on it.
quickdraw86 said:
Yep, santod is the man, no doubt about it.
This device launched more than 2 years ago with froyo, was upgraded to gingerbread, eventually got ICS, and may yet see unofficial jellybean!? That's an amazing run for any phone IMHO.
Click to expand...
Click to collapse
+1
Santod, Chief Executive Officer
Sent from my ADR6400L using xda app-developers app
Can anyone please test and see if Onavo works with this kernel? Thanks.
https://play.google.com/store/apps/details?id=com.onavo.android.onavoics
I Need the Best gaming Lollipop Rom for I9505 with great performance and Battery life ?
That would be AOSP rom by the JDCTeam.
Make sure you set alucard kernel to the extreme performance or performance profile if you want better performance in gaming.
doctorex1 said:
I Need the Best gaming Lollipop Rom for I9505 with great performance and Battery life ?
Click to expand...
Click to collapse
"great performance and Battery life ?" Performence or battery life! 5.1.1 CM with Alucard Kernel
if you get an alucard kernel in your rom then the raising the minimum clock speed to 810 khz on all four cores and the minimum for GPU speed to 200 khz it will help.
*gentle fair sleepers off
*arch power on
*CPU governors to ondemand or alucard with alucard hotplug
in developer option hardware overlays to off.
personally I think ktkernel was better with more options but you'd need to stick to AOSP 5.0 for that or lower
If he were to stick to older android versions (5.0 and lower) then he might aswell get KT kernel, which gives him the posibility of overclocking the CPU and GPU, something that is missing from the other kernels right now.
GPU overclocking isn't really stable, it actually takes away from the gaming experience.
How can increasing the GPU frequency, and therefor the performance, be bad?
If you overclock it too high of course it is unstable. But you should be able to take around 500 MHz easily.
GDReaper said:
How can increasing the GPU frequency, and therefor the performance, be bad?
If you overclock it too high of course it is unstable. But you should be able to take around 500 MHz easily.
Click to expand...
Click to collapse
I can't remember the steps you get in kt but I'm pretty sure the uppermost ones were next to unusable, 500 is only just above the standard speed.
the games are always going to have a fixed system requirement levels based on the hardware we have so there isn't that much to gain over optimisations for our roms I feel...
I always judge a rom based on how well it can play shadowgun deadzone. most untweakable kernel rom combos aren't so great fresh out of the box.
Well, I used KT kernel in the 5.0 days. I ran a gaming profile created by ktoonsez himself, which had GPU overclock, and ran stable all the way.
I usually judge a rom by how fast it opens the settings app. This presumes that the app was fully closed, otherwise it will just switch to it, wich is a lot faster than actually opening it. Also, animations are all off.
So, between the pressing of the icon and the actual opening of the app there will be a black screen (if animations are turned off). The longer you see that black screen, the slower the rom is.
This thread is meant to help you fix major cyanogenmod 13 bugs. CM 13 based ROMs are very nice, and probably the best way to being the android marshmallow experience to the m7 but they suffer from several problems.
Let's cut to the chase:
1. Camera: install cameringo from the play store, it works flawlessly. Also, cameramx works but expect some fc here and there.
One could argue that neither app is as good as HTC's stock camera app. But sadly they're the only options I'm aware of right now. Plus the m7's cam isn't all that good to begin with. If photography is your top priority you should consider another device.
2. IR blaster: install Asmart remote IR or ct remote from the play store. Both work for me but I recommend trying both and then keep whichever you prefer.
3. heat/battery issues: install no frills or set CPU app from the play store. I Peter no frills as it shows the current settings (so you can memorise them in case you decide to revert later). Kernel auditor is very good too.
Lower the maximum CPU speed to 1.134 GHz. You can change that whenever you need to, but 1.134 provides good battery life without compromising much performance. However before you run a benchmark or any other CPU hungry app remember to increase the max CPU speed back to the highest value.
set the I/o scheduler to bfq. cfq is OK but I prefer bfq. Google I/o bfq vs cfq to learn about the difference.
Set the CPU governor to intelliactive, interactive or smartmax. They're considerably better than ondemand. Smartmax results in lower performance but slightly better battery life. interactive is a very good all around governor. Intelliactive is an enhanced version of interactive. Experiment with all available choices. intellidemand is good too but I prefer intelliactive or interactive. Experiment with all available options your kernel provides. You should be able to figure out your favorite governor thru trial and error.
for more info about CPU governors check out this thread:
http://forum.xda-developers.com/showpost.php?p=59289777&postcount=1
for more info about I/o schedulers:
http://forum.xda-developers.com/showpost.php?p=59289783&postcount=3
Credit where it's due:
@Bharat Makhija directed me to Asmart remote IR, here's his thread:
http://forum.xda-developers.com/showpost.php?p=64405484
Another member directed me to cameringo & cameramx but I can't find the post or remember his name
If that was helpful don't forget to hit the thanks button
Got any other suggestions? Please share them
PS: I'm on crdroid ROM which doesn't have other major bugs.
Great post, I've been wanting to try CM13 on my M7, but I read there were too many bugs. Thanks!
Please test mod Camera Cm13 http://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-gallery-cm13-t3305917