DESCRIPTION
So this is a cooked RazR i boot.img that contains a custom compiled Kernel for our device, it was patched to be kept up to date and has some changes to help on battery savings, plus some cpu-freq drivers which which help our device a lot.
InteractiveX2 CPU Governor -- Like Interactive, and fine tweaked to only jump to 1.8 GHz on lighter/faster load increases, comes with a screen-off profile to lock down the frequency and offlinining of the rest of the CPU's defined as non-boot -- being an SMT processor this makes it easier to get the phone to deep sleep even when it wakes up to do something by reducing the complexity of the system.
Conservative CPU Governor -- Similar to ondemand. However, before the governor takes this lower frequency and slower clocked in the upper area, which has positive effects on the battery life.
Ondemand CPU Governor (Re)added -- it was originaly on ICS stock Kernel, it adjusts the CPU frequency to the given requirements, however quickly clocked in the upper frequency range to ensure smooth working.
Performance CPU Governor -- this will clock the CPU frequency to the top, not recommended for prolonged use.
SimpleIO Scheduler (Default) -- is a mixture of Noop & Deadline and one of my favorites.
V(R) IO Scheduler -- is the best scheduler for benchmarks, in everyday use can become unstable.
BFQ IO Scheduler -- A proportional-share storage-I/O scheduler that also supports hierarchical scheduling with a cgroups interface with Low latency and high throughput.
ROW IO Scheduler -- This one is very battery friendly and now my favorite for mobile decies by it's simplicity and responsiveness.
It is known to work on stock & stock based ROM's (such as this one where it is included).
As of other differences there are a lot of GNU compiler flags optimizations, by knowing that the compiler wouldn't know some vital information since it is a remote target different than from where I am compiling so I decided to be pretty explicit.
DOWNLOADS
[For Motorola's Android 4.4 KitKat, unsure if this works at the moment]
boot.custom.gamma_v6.0.2.img
[For Motorola's Android 4.1 JellyBean]
boot.custom.gamma_v5.0.2.img
boot.custom.gamma_v3.0.0.img
boot.custom.gamma_v2.2.1.img
boot.custom.gamma_v1.8.0.img
SOURCE
XT890-Kernel-Gamma GitHub Source
NOTES
For more information regarding governors, schedulers, modules, etc visit this thread by forum member droidphile.
This is my personal experience to other people on compiler flags, if you guys want to try -O3 straight ahead you will face issues on battery readings unless you remove the -ftree-vectorize flags on the battery modules that get compiled.
[IMPORTANT] For changing the CPU governor please use No-frills CPU Control, Since other apps such as SetCPU and AnTuTu CPU Master both only change CPU0 and may cause conflicts.
INSTRUCTIONS
You MUST be unlocked, and to take full advantage of other modules it is recommend to be rooted.
I will put something more descriptive here, but you can flash it with fastboot by doing: fastboot -i 8888 flash boot <boot.img>.
THANKS TO OTHERS
First of all thanks to Matorola/Intel for putting the main source and for Turl on giving me some info when unpacking/packing the boot images. Also to mattlgroff for the tutorial on unlocking the phone, more thanks to imoseyon and Mike Chan for providing the interactiveX2 source code and changes, it it is now my favorite CPU governor and also to HSD-Pilot for posting this originally on another forum -- I based my formatting from his post.
<< If you like my work here is my hat, please donate! >>
<< And thanks to you guys for the support and help >>
So is this kernel designed for speed or battery life, or a mixture of both?
Also will this work on the 91.2.26001 JB.EU rom?
cuben said:
So is this kernel designed for speed or battery life, or a mixture of both?
Also will this work on the 91.2.26001 JB.EU rom?
Click to expand...
Click to collapse
By default for a mixture of both. But can be further chose different governors and parameters of the governors for different choices for the user. You can for example choose conservative governor and get more battery life and less performance.
And yes It can be used on that ROM. :good:
It works on jelly bean alright... but with this I'm missing the features of the Arman AIO boot v4 and I just can't live without it...
Updated the OP, added SavagedZen CPU governor.
Omar-Avelar said:
Updated the OP, added SavagedZen CPU governor.
Click to expand...
Click to collapse
Any changelog will be great , last version 1.4 now 1.7 its only "added SavagedZen CPU governor"?
skupi20 said:
Any changelog will be great , last version 1.4 now 1.7 its only "added SavagedZen CPU governor"?
Click to expand...
Click to collapse
Yeah, it was internal changes and some screwing around while playing with it. Aiming for more features and once a 'finalized' kernel build is there I will probably do change-logs and change the scheme of numbering.
Hey, what are the changes in V1.7.1 compared to 1.7?
HSD-Pilot said:
Hey, what are the changes in V1.7.1 compared to 1.7?
Click to expand...
Click to collapse
Tried to fix and make SavagedZen more reponsive, but it is a weird governor, and also included InteractiveX in the meantime (no bug there).
Will probably just put into Github after this change so other people can see the changelogs.
Thanks for reply - Flashed it already :good:
well I would comment on your topic of rom ([ROM] Stock 4.1.2 JB optimized - Deblurred AOSP + 4.2 Kernel + extras). but as it only involves the kernel decided to post it here ..
good this new government "SavagedZen" is weird! I did not like, played some games, subway surfers, temple run 2, etc ... all caught. then modified to smartassV2, and now games are perfect and without lagg, I have helped with my feedback
Paulinhip said:
well I would comment on your topic of rom ([ROM] Stock 4.1.2 JB optimized - Deblurred AOSP + 4.2 Kernel + extras). but as it only involves the kernel decided to post it here ..
good this new government "SavagedZen" is weird! I did not like, played some games, subway surfers, temple run 2, etc ... all caught. then modified to smartassV2, and now games are perfect and without lagg, I have helped with my feedback
Click to expand...
Click to collapse
Yeah, I am defaulting to smartassV2 back again...
sounds great your kernel mods.
i will try your stuf spin, i wait for a more stable release.
but think at weekend i will go with IT.
regards
Little Bug Report: I get some freezes and Hot reboots with the Interactive X Governor. No big deal, just to let ya know
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
Little Bug Report: I get some freezes and Hot reboots with the Interactive X Governor. No big deal, just to let ya know
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Attempted to fix that on 1.7.3 -- unsure on the results yet. :highfive: Thanks for helping man!
Alright, just flashed V1.7.3 and set Interactive X as default. Will report back if I get any issues.
I'm @ work so I had to pack an flashable Zip with the Smartphone. It's a lot faster on my PC
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:09 PM ---------- Previous post was at 05:28 PM ----------
Sorry dude, again no luck. As soon as I turn off my Screen my Phone is dead. I have to force the reboot by Power + Vol. down.
Tried it 3 times now > back to SA V2 :thumbup:
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
Alright, just flashed V1.7.3 and set Interactive X as default. Will report back if I get any issues.
I'm @ work so I had to pack an flashable Zip with the Smartphone. It's a lot faster on my PC
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:09 PM ---------- Previous post was at 05:28 PM ----------
Sorry dude, again no luck. As soon as I turn off my Screen my Phone is dead. I have to force the reboot by Power + Vol. down.
Tried it 3 times now > back to SA V2 :thumbup:
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Damn, ok and thanks! ... so InteractiveX is not functional yet sounds like it must have something to do with the early suspend portion -- will eventually fix it. Good thing is that smartassV2 works flawless!
Nice work on the governors!
I remembered some governor benchmarks I read a while ago on this forum, and I thought you might be interested in it:
[REF][GUIDE] Battery Saving Governor Benchmarks
Some interesting quotes from the above thread:
the difference between the best (smartassV2) and worst drain (lazy) is 0.05mA (a tiny amount)
Click to expand...
Click to collapse
choosing SmartassV2 over Lazy would prevent about 600mA being wasted in one hour. To put this in context, that is enough to power your screen for 3 seconds (assuming a drain of 200mA).
Click to expand...
Click to collapse
Furthermore, I remember another thread (which I have not found), which showed that governors which did not jump straight to the highest frequency could actually negatively impact the battery life. The reason behind it is that CPU usage is only a fraction of the battery drain, and having a slower CPU means applications have to spend longer in active state, thereby also causing other components battery drain over a longer period of time. The display is the biggest battery eater, followed by the radios.
Basically, what I trying to say, is (most) governors have no perceptible impact on battery life, and I believe users who report otherwise suffer from the placebo effect. So I think focusing on a stable default governor which gives a smooth lag free experience is the way to go.
arman68 said:
Nice work on the governors!
I remembered some governor benchmarks I read a while ago on this forum, and I thought you might be interested in it:
[REF][GUIDE] Battery Saving Governor Benchmarks
Some interesting quotes from the above thread:
Furthermore, I remember another thread (which I have not found), which showed that governors which did not jump straight to the highest frequency could actually negatively impact the battery life. The reason behind it is that CPU usage is only a fraction of the battery drain, and having a slower CPU means applications have to spend longer in active state, thereby also causing other components battery drain over a longer period of time. The display is the biggest battery eater, followed by the radios.
Basically, what I trying to say, is (most) governors have no perceptible impact on battery life, and I believe users who report otherwise suffer from the placebo effect. So I think focusing on a stable default governor which gives a smooth lag free experience is the way to go.
Click to expand...
Click to collapse
I agree for the most part but that really depends a lot on the type of processor and SoC capabilities, for phones like us I focused on the tweaked smartassV2 further to get it to ramp up and down faster, and it is noticeable smoother. , good battery life since it ramps down better than the on-demand or interactive governors here!
SmartassV2 was the winner on our testing too so we left that one . I just wanted to get InteractiveX working on it for future flexibility and the days that I messed up with SavagedZen it was just an experiment as I had never tried it before -- the results was that I did not like it a lot or I ported it wrong! haha
Friend'm using interactiveX governor since yesterday, andthe results seem to be good and had no lagg dabateria useful life is good (since I am a hard-user).
but honestly the samatassV2 is better, it seems that runs smoother on my device!
but just wanted to note that the InteractiveX is working!
sorry for bad english
Related
I am proud to announce Savage-Kernel to the xda forms. Currently in beta testing we worked from the latest invisiblek kernel newly undervolted, HAVS with the SBC mod.
JUST FOR @PonsAsinorem:::::: DISCLAIMER!!!! IM NOT RESPONSIBLE FOR BRICKING YOUR PHONE... EVEN THOUGH THE KERNEL CANNOT BRICK A ROOTED PHONE UNLESS YOU FLASH A BAD RECOVERY..... DON'T MODIFY THE UPDATER-SCRIPT TO FLASH THIS TO YOUR RECOVERY!!!!!! .... ALL CHANGES TO THIS KERNEL STILL MEET THE MINIMUM SPECS OF THE INC.... UNLESS YOU OVERCLOCK... WHICH IS UNDERVOLTED... WHICH IS RUNNING AT THE STOCK VOLTAGE AND SHOULDN'T HARM YOUR PHONE ANYWAY.
SENSE BASED ROMS NOT SUPPORTED THIS IS FOR AOSP ROM'S ONLY
So far the Kernel works great in conservative governor. which all the devs prefer.
Devs:
jsseidel1 (co-creator)
luisrcastillo (co-creator)
ms79723 (SBC mod updates)
lithid-cm (contributer. Updater-script guru)
Credits:
invisiblek--> base kernel!!
ms79723 --> the SBC mod.
netarchy --> smartass gov
intersectRaven --> HAVS
(credits are given to the dev's where we got some code from, may no be original designer)
CFS Builds:
Alpha1 : Click Here to download
Stable v1 : Click Here to download
BFS Builds:
Follow the github on twitter @evokernelsrc
If you like our kernel and want to support us... donate (no obligation)
Change log
Code:
[B]Alpha 1[/B]
Undervolted to 925
HAVS implemented configured for conservative
smartass added for fans
SBC Mod added (trickle Charging)
Enabled OC to 1.19 and stable
conservative governor tweaks
HAVS tweaks
smartass governor tweaks
voltage tweaks
BFS360 (latest version) and CFS VERSION!!!
Added SBC v7
BFS tweaks to ondemand gov
tweaks to interactive gov
bad ass CFS tweaks!!!!!
aggressive swap drop
misc tweaks
[B]Stable v1[/B]
SBC v7 ported from Evo (better battery life, this is a HTC mod so doesnt matter that it came from Evo)
FAQ's
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
jsseidel1 said:
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
Click to expand...
Click to collapse
What kind of battery life are you getting with this? I know results vary, but just curious.
Sent from my ADR6300 using XDA App
excited to try this
jsseidel1 said:
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
Click to expand...
Click to collapse
How did you determine that conservative is the most power-friendly?
I would post a disclaimer about the SBC mod.
Sent from my ADR6300 using Tapatalk
Am I missing the link here or has it not been posted yet? I'm excited to test.
Guys, SBC *really* isn't good for the battery. Li-Ion batteries aren't designed to use trickle charging. IMO this will kill the batteries faster and isn't worth the extra charging.
waiting to try this... dont think it will hurt my battery in the short run... who keeps phones longer than 2 years anways?
True. I've gotten better battery life off of it, but I feel like my MIUI build recently has been getting worse due to the SBC mod.
Works on gingerbread roms?
Sent from my ADR6300 using XDA App
If it's AOSP, it should, but sometimes I've gotten weird reactions using kernels that are claimed to work on all AOSP ROMs (Kingx Kernel + MIUI = no-no. Also, MIUI + Hydra = no-no).
Point being, we should probably get this clarified. I've seen instances where people have lost touchscreen functionality (though usually that's due to a failure to wipe cache/dalvik) among other issues. Until we field test this on GB ROMs or until the OP states that it works on them, we should probably refrain from flashing it over a GB ROM. You can do it if you want, I'm in no way trying to make you turn away from it; I'm just saying take it with a grain of salt.
Plus there's the SBC issue to worry about; trickle-charging has negatively affected the battery performance of my MIUI ROM, so I'm going to switch kernels whenever I go back to it. Better charging in the short run < not needing to buy new batteries in the long run (and therefore saving money).
link??????
*sigh*...
Ok, clearly I need to start citing the comments I make. Here you go:
http://forum.xda-developers.com/showthread.php?t=885476&page=25
The first post on this last page pretty much sums it up (actually, read 23-25 to sum up the main issues, it also has links to OTHER posts talking about the issues), but if you want other chronological examples of touchscreen failure or other issues you can read examples from pages 2, 5, and some places past page 15. SBC is bad news on its own, and adding overclocking to it just makes it worse. Again, you can use the kernel if you want, I'm not gonna stop you, I'm just saying that there have BEEN problems with it on other AOSP ROMs. MIUI seems to take pretty well to SBC in terms of battery, as I've seen; but, it's been getting worse as of late. UltimateDroid had a touchscreen failure (page 5) in v1; I don't believe that's been fixed yet, but feel free to correct me. MIUI had a touchscreen failure in v2 (though I think there might have been a bad flash involved, because I flashed SBC to my MIUI 12.24 at the time and it worked fine), cited page 23. Need I go on? Lol.
Point is (I've said that a lot, I know) that it does damage, multiple AOSP ROMs are getting touchscreen failure, and there's more harm than good that comes out of it.
Read: http://www.ziggy471.com/2011/01/02/overcharging-batteries/
That's a good link also. It's actually in the thread I posted, but its equally as important if not more important than my post. Good job man XD
Sent from my HTC Incredible running Carbonite Red 1.5.
Ok you all need to relax. SBC does not over charge your battery. The trickle charging is essentially the battery staying at 100% while on the charger. Lithium ion batteries have tech built into them to protect from over charging and such. SBC just means when you take it off the charger it will really be at 100%. You can't over charge aanyway. This kernel allows you to overclock but it doesn't force it. You need to choose overclocking yourself in setcpu. ... and 90% of the kernels in this forum have SBC they just either don't say it or they call it the battery fix. You can see it in their gits. On the evo forums we just call it SBC. Ill be posting the kernel today. If you don't want to use it. Then don't. It was just requested that I port my evo kernel over to the Inc. So I am.
Sent from my PC36100 using XDA App
gmichaelow said:
How did you determine that conservative is the most power-friendly?
Click to expand...
Click to collapse
Conservative by nature is more power friendly as it only ramps up the processor as requested then brings it right back down to your min.
The way we have set our Governor is to optimize the Conservative Governor to get the most speed stability and battery life out of your phone.
I just got a config from one of your rom dev's to build the kernel so this should be posted by tomorrow.
I for one appreciate what you are doing. There is nothing wrong with having a variety of kernels to choose from. If you disagree with what this dev is doing, then use another kernel. We don't need to be running them off.
Sent from my ADR6300 using XDA App
/Discuss
In previous ROMs for other devices I had good experience with smoothass/brazillianwax and savagedzen but ever since I tried MinMax it's the best one for me.
What do you guys think?
(I/O Sched is Simple by far, there's no chance to others like V(R) or BFQ)
ondemand...
Stock user have to use
hectorrent said:
I miss one option: "What's a governor?" xDDDDDDDDD
Click to expand...
Click to collapse
The "governor" is that piece of software that switches the CPU of you phone between the different speeds and voltages, thus it is responsible to some performance issues and the power consumption of the battery.
Or in other words:
The "wrong" governor results in poor battery duration, while another "wrong" governor may result in great battery duration but poor performance. The "best" governor is the one that switches the CPU to exactly that speed that is really needed so the system can run with full performance and best battery duration.
As user of the stock ROM you do not have the choice as the kernel supports exactly one specific governor (named ondemand). If you want to try the differnt governors try the Nova ROM of Noejn: this great ROM allows you to switch between several different governors.
Noejn said:
What do you guys think?
Click to expand...
Click to collapse
I only tried MinMax and ondemand. To make it short: ondemand sucks, MinMax works great for me.
Aves83 said:
I only tried MinMax and ondemand. To make it short: ondemand sucks, MinMax works great for me.
Click to expand...
Click to collapse
Ondemand make lags.. But damn Stock kernel only supports craps..
This kernel is built for and from codeworkx's CM9 with hardware acceleration.
Again this is for codeworkx's cm9.
One more time, this is for codeworkx's cyanogenmod 9.
Finally, this is for cm9 and cm9 only!
Don't let the "alpha" title fool you into thinking it's not stable... it is... It's only alpha because it's still in the "testing" phase.
Works on the P31XX. I don't know about other models.
FEATURES/CHANGES
Overclockable to 1.38GHz
Underclockable to 150MHz
GPU overclocked to 384MHz (highest possible without bottlenecking and battery waste)
Tuned OnDemand Governor (recommended)
Interactive Governor with time view concept (learns from your use and adjust parameters accordingly)
Wheatley Governor (optimized use of C4 state)
Hotplug Governor (turns of one of the cpus to save power when load is very low)
Pegasusq Governor (A better version of Hotplug, but experimental and not designed for our devices)
SIO scheduler for speed/performance with flash storage
Linaro Toolchain
Linaro optimizations and patches
Linaro makefile compiler flags
Makefile Optimizations to boost performance
Optimized CRC32
Optimized ARM RWSEM algorithm
Tiler Memory increased to 32MB (linaro)
Other Tiler patches/tweaks to improve 2D gpu performance
SLQB allocator
lib/string use glibc version for speed
lib/memcopy use glibc version for speed
lib/sha1: use the git implementation of SHA-1 and removed ARM sha1 routines
I/O backport from 3.2 linux kernel for less dirty throttling
Tweak CPUIDLE to enter deep sleep faster thus saving battery
LowMemoryKiller backported from 3.4 kernel
Disable GENTLE_FAIR_SLEEPERS for improved performance
Allow Deep Sleep to occur when media decoder is active allowing the cpu to shut off when playing music or video.
Allow MPU logic to power down when in deep sleep to save power.
Increased default readahead value to 1024KB for faster sdcard reads
A lot of stuff I probably forgot I did.
Also includes a ridiculous amount of bugfixes, patches, and tweaks that can found on my github commit log.
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
Let me know how it "feels" especially by default without overclocking or underclocking. Also I'd be interested in how the battery treats you. Thanks!
DOWNLOAD
a1 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a1.zip
a2 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a2.zip - Changes to: Wifi, GPU, Low Memory Killer, others
a3 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a3.zip - Changes to: ondemand, interactive, add wheatley, add pegasusq, deep idle, compiler flags, SDcard read, others
a4 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a4.zip - Changes to: Compiler flags, CPUidle, RCU, others.
a5 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a5.zip - reverts and bugfixes, use 10.1 ramdisk in 10.1 version
a6 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a6.zip - CLASSIFIED change, NEED feedback on speed, slowness, smoothness, and lag compared to stock and a5. Reverted some revets. Reverted changes to RCU to fix SODs. Graphics. For 10.1 fixed overclocking.
If you would like to overclock but your device can't handle it... and are willing to suffer through extreme battery drain to try this - Link
Thanks go out to - CodeworkX, Ezekeel, Francisco Franco, Imoseyon, Faux123, Fugumod, Sonicxml, Texas Instruments, Samsung, Google, and all the others I probably forgot about. Sorry!
Source
https://github.com/Metallice
______________________________________________________________________________________________________________________
So, I'm a broke college student without a job this summer - instead taking extra classes and studying like crazy for the MCAT. If you like my work and want to thank me, feel free to buy a coffee or an energy drink so I can continue to stay up late studying and working on Android stuff (or help me pay for med school ). I don't want to have to choose! Thanks and I appreciate your support!
I like this format, just like Trinity kernel. Much less placebo for added things. Like, "zOmg, linaro made my phone fly! Thanks for including it, it rocks!!!!!" With the things being changed kept hidden, I'd LOVE for you to release a couple builds, with different compile dates, without changing a thing, but telling people you did. Watch the placebo roll in, ha
Thank god you released this. Seriously the only thing this ROM was missing was a little OC. You guys are really making this purchase (Getting the GTab 2) a really good idea!
Sent from my GT-P3113 using Tapatalk 2
Will this kernel work on p3100 becaise all i see around here all the custom roms and kernels are for p3113 so please just confirm the models on whicj it would be flashable.
Thanx
Sent from my GT-P3100 using Tapatalk 2
tapan15in said:
Will this kernel work on p3100 becaise all i see around here all the custom roms and kernels are for p3113 so please just confirm the models on whicj it would be flashable.
Thanx
Sent from my GT-P3100 using Tapatalk 2
Click to expand...
Click to collapse
I don't know. I have no way of testing.
Sent from my GT-P3113 using xda premium
Oh yeah. You da man!
Just flashed... will give updates on how it is running.. so far so good!!
Sent from my GT-P3113 using xda app-developers app
cannt wait for this, thank u so much
I will tell my feeling about this after I flashed it
Sent from my GT-P3110 using Tapatalk 2
Runs smooth and stable at 1380mhz on my 3113. Thank you for your hard work! On a related note, what governor do you recommend? In your experience, does using hotplug actually save battery?
yes it is working with 3100. great job.
Flashed this on my P3110, and it bricked it NOT.
Thanks for this. Waiting to see what more you will add to the kernel.
Cheers.
I've got a question. Does the tab 2 not have a CPU temp Senser?
Sent from my GT-P3113 using xda premium
Been using this since last night and so far no RR or SOD's. Everything is running smooth without any errors, glitches, etc. Great work, as always, Metallice!
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
Kidney Poker said:
I've got a question. Does the tab 2 not have a CPU temp Senser?
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
I don't know, but wander why you would ask?
miketoasty said:
Been using this since last night and so far no RR or SOD's. Everything is running smooth without any errors, glitches, etc. Great work, as always, Metallice!
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
I don't know, but wander why you would ask?
Click to expand...
Click to collapse
CPU controllers have a temp read out. I like having one. I know most apps pull the info from kernel. Was trying to find out if we have the hardware built in and the kernel isn't passing info or if the hardware is just not there.
Sent from my GT-P3113 using xda premium
Maybe it's just my tablet, but I can't get any clock speed greater than stock to work. Tried it on this kernel and one I did myself.
Kidney Poker said:
I've got a question. Does the tab 2 not have a CPU temp Senser?
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
Yeah the omap does. Not sure if I turned it on or not. If its on you can get the temp from dmesg I believe.
Sent from my Galaxy Nexus using xda premium
imnuts said:
Maybe it's just my tablet, but I can't get any clock speed greater than stock to work. Tried it on this kernel and one I did myself.
Click to expand...
Click to collapse
I can try adding a 1.1ghz slot?
Sent from my Galaxy Nexus using xda premium
Kidney Poker said:
CPU controllers have a temp read out. I like having one. I know most apps pull the info from kernel. Was trying to find out if we have the hardware built in and the kernel isn't passing info or if the hardware is just not there.
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
Most apps actually pull their info from the battery temp and are unreliable.
Sent from my Galaxy Nexus using xda premium
nphil said:
Runs smooth and stable at 1380mhz on my 3113. Thank you for your hard work! On a related note, what governor do you recommend? In your experience, does using hotplug actually save battery?
Click to expand...
Click to collapse
OnDemand. I don't bother with hot plug as I don't see any benefit. If you do a lot of non interactive activities like reading or music it may be helpful, but I would try the 200mhz min before I try hot plug.
Sent from my Galaxy Nexus using xda premium
Have you flashed on cm9 or stock rom??
Sent from my GT-P3100 using Tapatalk 2
Which combination of governor and scheduler gives the best performance for ICS Stock ? And which one for better battery life ?
Akilesh said:
Which combination of governor and scheduler gives the best performance for ICS Stock ? And which one for better battery life ?
Click to expand...
Click to collapse
Other said it is pegasus and devs say it is all the same just a little difference.
jonpaslim said:
Other said it is pegasus and devs say it is all the same just a little difference.
Click to expand...
Click to collapse
I was told by the majority it goes in this order:
1) Pegasusq
2) Lulzactive
3) SmartassV2
4) Ondemand
5) Hotplug
6) Interactive
... and the rest.
And for IO Scheduler:
1) VR
2) CFQ
3) SIO
The truth is that, this is a Dual Core Phone with 1GB RAM, and improved Android 4.03+ kernel. So the previous hardware and software limitations NO LONGER applies. Coming FROM the DEVELOPERS of governors and schedulers the best ones seem to be:
1) InteractiveX2
2) HotplugX
3) Ondemand
... then lulzactive ~ pegasusq > smartassV2
And for IO Schedulers:
1) SIO
... then the rest
The truth is you should use the DEVELOPER recommended governor and sio scheduler, for an extensive period (1-2 days) and compare them. Finding what works best for you. After that's done, then you should go further stability testing with Voltage Control. Eg, UC your lowest frequency, OC your highest frequency and UV each step to the NEEDS of your device, each device is UNIQUE and functions DIFFERENTLY.
I think doing so you should extend your battery life by 1 or 1.5hour per cycle, while maintaining or increasing performance.
it all depends on the ROM + Kernel and more importantly the user and how they use their Note.
For me, I use Performance + Noop.. But ive had good results with pegasusq + sio
The only way to get the best combination is to try them all, But give them time to perform, Dont make a decision after 5 mins of usage, Test them heavily, Do some serious Gaming + Multitasking and chose one that outperforms the rest !
I'll start testing and post results from time to time.
Sent from my GT-N7000 using xda premium
azzledazzle said:
it all depends on the ROM + Kernel and more importantly the user and how they use their Note.
For me, I use Performance + Noop.. But ive had good results with pegasusq + sio
Click to expand...
Click to collapse
But the performance governor never scales down but always runs at maximum frequency. How is battery life with that? Must be horrible?!
Kangal said:
I was told by the majority it goes in this order:
The truth is you should use the DEVELOPER recommended governor and sio scheduler, for an extensive period (1-2 days) and compare them. Finding what works best for you. After that's done, then you should go further stability testing with Voltage Control. Eg, UC your lowest frequency, OC your highest frequency and UV each step to the NEEDS of your device, each device is UNIQUE and functions DIFFERENTLY.
I think doing so you should extend your battery life by 1 or 1.5hour per cycle, while maintaining or increasing performance.
Click to expand...
Click to collapse
I agree, governors even if they have the same stock names(i.e ondemand) has been heavily tweaked by the kernel dev so that you maximize performance and batt life. Start off by using the kernel/scheduler suggested by the kernel dev.
The only thing I care about is running out of juice when I don't have access to something that can charge my phone, as long as i get 10-15hrs off batt life and solid performance I'm good. Still I always bring a wall charger/usb cord with me if i really needed the extra juice.
Remember you can charge the battery but you can't charge performance
Coxeroni42 said:
But the performance governor never scales down but always runs at maximum frequency. How is battery life with that? Must be horrible?!
Click to expand...
Click to collapse
I get around 24 hours from my battery and I'm happy with that, besides I'm always somewhere where I can charge my phone should by battery run out
Sent from my GT-N7000 using Tapatalk 2
chickentuna said:
Remember you can charge the battery but you can't charge performance
Click to expand...
Click to collapse
This sentence doesn't make sense at all.
Unless you mean you can change or recharge the battery, which is straight-forward.
But you can "change" (increase) the performance. Just clear all background tasks, go to Voltage Control and overclock the cpu frequency upto 1.704GHz (with +1400mV) and keep it at that frequency by using the Performance governor. Also overclock your gpu upto 400MHz (with +1,000mV).
Though I don't recommend that, stability issues, warming issues and possible physical damage to your processor. But use the same concept, just not Overclock too much!
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
azzledazzle said:
I get around 24 hours from my battery and I'm happy with that, besides I'm always somewhere where I can charge my phone should by battery run out
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
That's simply NOT true.
Otherwise you have your phone in deep sleep/idle far more than the average user, barely using your phone.
Other possibility is that you've severely underclocked your maximum frequency, and have a long time in idle.
Performance governor = Always on maximum frequency.
NOTE's maximum frequency uses 1300+ mV. The NOTE's battery size is 2,500 mAh. Simple maths will tell you 24hrs is impossible ; )
But it is true I'm not saying my phone will be awake for 24 hours I'm saying I charge it roughly every 24 hours, I know performance keeps the phone at max speeds but I am human I will sleep for about 8-9 hours, so in result so will my phone.
And I don't use my phone every minute of the day I do have work to do so my battery life is what I say it is. What I consider 'average use' might be absolute minimal use to you so maybe that's why you doubt me,
I personally don't mess with voltages and things cause I don't understand them but I use note core kernel which is highly tweaked and one of the best kernels for battery life
Sent from my GT-N7000 using Tapatalk 2
My recommendation is lulzactive.
i use hotplug+sio on maclaws slim bean,, awesome battery life
This is the BOJ1 version of NN-kernel. It's going to go in a little different direction than the previous kernel. And I'm not very good with Git. So may I present to you.....
NN-J-Kernel
This will work on the T710 and 810 Wifi only models. I built this for my BNN Nook, but it works with other 710's and 810's.
You flash this at your own risk. There's the discaimer. :silly:
Install instructions:
You MUST HAVE ROOT and TWRP installed to flash this!!
It's built on Lollipop 5.1.1 - I have no idea what will happen if you flash this on anything else!!
REMOVE SYNAPSE "set on boot" BEFORE INSTALLING!!!
Flash kernel then wipe cache and dalvic
Reboot and profit!!
Changelog
V1.3
GPU Control
UV now possible as well as select frequency
Samsung has the Max listed as 600Mhz. I'm pretty sure its 700 as thats what I've been using this at. Just an FYI
V1.2
Charge Control for battery - It's the best I can do for a "Faster Charge". Be careful. This can shorten the life of your battery. Or worse, ruin it if you change from default. You have been warned.
Maybe some other minor stuff
Also see/read this post
_______________
V1.1
Hotplug Big cores - They are the only ones that can be
OC/UC Big and Little - 2.1Ghz-500Mhz, 1.6Ghz-200Mhz
UV all CPU's
650Mhz step added to GPU
FIOPS Scheduler
Booting freq to 1.4Ghz
Lots of Optimizations
Gentle Fair Sleepers
Synapse stuff added
HMP controls - Big little cores
Memory controls
_______________
V1
OJ1 source
Synapse tuner - it's the only one that seems to work. Finally, after much effort.
Selinux Permissive
KNOX removed
Init.d support
Enabled OTG
Updated Frandom
Govs enabled- Powersave, Conservative, Ondemand - removed Userspace
Some optimizations
_____________________________
This is a Tablet, so I won't be adding things like I would for a phone.
Use "Synapse" from the Playstore for your Kernel tuner
______________________________
Downloads:
NNJ-Kernel-V1.3-710
NNJ-Kernel-V1.3-810
NNJ-Kernel-V1.2-710
NNJ-Kernel-V1.2-810
NNJ-Kernel-V1.1-710
NNJ-Kernel-V1.1-810
NNJ-Kernel-V1-710
NNJ-Kernel-V1-810
Thanks to:
ashyx
BigBot96
UpInTheAir
djmax81
And other peoples gits I can't remember
XDA:DevDB Information
NN-J-Kernel-LP-T710/810, Kernel for the Samsung Galaxy Tab S2
Contributors
engine95
Source Code: https://github.com/engine95/Exynos5433-BOJ1-gts28-210wifi.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-02-24
Created 2016-02-24
Last Updated 2016-02-24
And yes, Schedulers are fixed in this.
Flashed, running perfectly so far....
Thank you for your work.
Gesendet von meinem SM-T810 mit Tapatalk
I flashed this kernel (oj1-based) and the NN kernel (oh7-based) and let antutu benchmark the performance of both kernels (both default settings). This kernel wins outstanding!
Is this the "newer" one yes ?
Awesome! Thanks, it's nice to see some development on thus tablet. Otherwise there is nothing to flash
Sent from my LG-D855 using Tapatalk
halloarno said:
I flashed this kernel (oj1-based) and the NN kernel (oh7-based) and let antutu benchmark the performance of both kernels (both default settings). This kernel wins outstanding!
Click to expand...
Click to collapse
I did the same and the OJ Kernel is slower for me. Did 2 tests. 69-70k in old Kernel while i getting 62-65 with OJ1. Any idea ? How much do you get?
I tried setting max core to 2.x ghz but its not working, is it fixed to 1.9 ghz=no oc enabled so far?
Very strange, worked before i think. Just have Synapse installed and also wiped caches after flashing.
Any idea?
IngoPan said:
I tried setting max core to 2.x ghz but its not working, is it fixed to 1.9 ghz=no oc enabled so far?
Very strange, worked before i think. Just have Synapse installed and also wiped caches after flashing.
Any idea?
Click to expand...
Click to collapse
This kernel has no OC function, at least until now.
Actually, right now, it has no OC or extras. This is just the start. It's in the changelog.
Antutu scores, for me are 66-67000.
OC/UC and UV will be coming shortly. It's done. I just can't find out why Big 1500 ghz and Little 1300ghz are favored. Messed with a lot of stuff to no avail. Yet
V1.1 is up!!
SEE/READ changelog as there is a ton of stuff in it now. Both Kernel and Synapse. Yea for Hotplug!!!
Google "HMP" so you can understand it better. Big/Little core control. Little cores are ALWAYS online.
Think I found a way to get us a Fast Charge. Gotta finish and test it. So far it's looking good.
engine95 said:
Think I found a way to get us a Fast Charge. Gotta finish and test it. So far it's looking good.
Click to expand...
Click to collapse
Incredible. Fast charge on our tab s2? I hope so?
Great job! Thanks! Flashed and works perfectly, new synapse settings seems cool. UC seems to work fine.
Shiuldnwebuse the DVFS app as mentioned in synapse?
Sent from my SM-T810 using Tapatalk
whynottoday said:
Incredible. Fast charge on our tab s2? I hope so
Click to expand...
Click to collapse
Gugus38 said:
Great job! Thanks! Flashed and works perfectly, new synapse settings seems cool. UC seems to work fine.
Shiuldnwebuse the DVFS app as mentioned in synapse?
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Thanks. I have no idea if that app helps as I'm new to Samsung. If you try it, make a backup first.
Everything works fine without it though.
Can you say Fast Charge?!!!!!
I had to port Hotplug and Fast charge, but I think we're good to go. I still need to put finishing touches and build for both 710/810. But it should be out tomorrow IF my Tab doesn't meltdown while charging tonight. :silly:
Edit: Also, remember that as with everything computer, Fast Charge will be limited by Thermals. Just like CPU/GPU.
engine95 said:
Thanks. I have no idea if that app helps as I'm new to Samsung. If you try it, make a backup first.
Everything works fine without it though.
Can you say Fast Charge?!!!!!
I had to port Hotplug and Fast charge, but I think we're good to go. I still need to put finishing touches and build for both 710/810. But it should be out tomorrow IF my Tab doesn't meltdown while charging tonight. :silly:
Edit: Also, remember that as with everything computer, Fast Charge will be limited by Thermals. Just like CPU/GPU.
Click to expand...
Click to collapse
It wont really be fast charge as our tab doesn't support it
Reuben_skelz92 said:
It wont really be fast charge as our tab doesn't support it
Click to expand...
Click to collapse
Interesting. Guess we'll find out. I have been able to vary the voltages while charging. Up and down. But as I said, thermals will probably limit it.
Edit. Let's call it "Charge Control" then.
engine95 said:
Interesting. Guess we'll find out. I have been able to vary the voltages while charging. Up and down. But as I said, thermals will probably limit it.
Edit. Let's call it "Charge Control" then.
Click to expand...
Click to collapse
Sorry me being an idiot. Will be cool to see our tabs charge a little.bit quicker
Thank you very much for the kernel!
Running 1.1 with
A57 cores at 1300/500 and UV 50mV
A53 cores at 1000/200 and UV 25mV
2 A57 cores online
FIOPS scheduler, 2048 readahead
Gentle Fair Sleepers enabled
It's running snappy! Will watch battery life
P. S.: Why doesn't Synapse have live monitoring where one can see which frequency each core has at the moment? Just like other kernel tuners?
hasenbein196601 said:
Thank you very much for the kernel!
Running 1.1 with
A57 cores at 1300/500 and UV 50mV
A53 cores at 1000/200 and UV 25mV
2 A57 cores online
FIOPS scheduler, 2048 readahead
Gentle Fair Sleepers enabled
It's running snappy! Will watch battery life
P. S.: Why doesn't Synapse have live monitoring where one can see which frequency each core has at the moment? Just like other kernel tuners?
Click to expand...
Click to collapse
They are there. On the core screen at the top. Just wiggle the screen and you'll see it change. Big cores don't move as much until there is demand for them.
V1.2 is in the OP! With "Charge Control" See/read changelog for warnings.
This was a big port, and everything seems to be working. Just watch your tab for temps just to be sure it can handle the voltages. We should be ok, as it's built in and not on it's own. Meaning that all of Samsungs limits are still there. So Thermals should hold it from melting down. My Tab has been plugged in all night and is just fine.
This has all kinds of cable configurations, so it should cover about everything out there. I only use AC and USB but left all the others in for all of you.
One more time, we should be OK using Charge Control, but BE WARNED that it may ruin your battery and shorten battery life span. You use this at your own risk.