[KERNEL INFO] Test Battery Life Nexus 5 [Comparisons, differences and more] -> HERE
First: sorry for my bad english xD
These tests are to understand what ROM is more battery friendly .
I use code blue at all for equality in comparison
I imagine that changing custom kernel will be the same thing (the duration of the ROM)
3 things:
- This is not a topic of war. (clashes on which is better and stuff like that, we should try to avoid them)
- As usual, no one is perfect; if I make some mistakes or do you think I rate incorrectly just say so and we discuss what to improve
- There will not only test but also personal opinions
how does it work (test) -> Read!
Requirements:
- ROM installed on secondary MultiROM
- ROM "stock" without being configured and no applications (only AnTuTu tester)
- Same Build kernel to compare better.
NB: I have randomly chosen code blue
- Temperature between 24 and 26 degrees during the beginning of the test
- Same surface (table)
- Kernel "stock" without being configured (no UV etc.)
- Antutu Tester:
This application is incredible.
It isn't a benchmark scores and will explain how it works:
It allows you to test the device without you touch it!
this application always works in the same way:
- Open web pages
- Use the cpu 100%, then to 70% etc.
- It opens a test for games
- It opens a test for video and other
The test stresses our phone.
Do not expect amazing SOT. The important thing is the comparison!
[ROM]Test Battery life
boostpop_hammerhead-ota-3.2.zip + Kernel Code Blue r923
Details Test: //
Euphoria-OS-1.1-hammerhead-20150428 + Kernel Code Blue r923
Details Test: I forgot the most important screenshots: SOT is: 1h55m -> trust me
Optipop_Layers_N5-2015-05-12-GCC49.zip + Kernel Code Blue r923
Details Test: //
OLD TEST: (don't compare with others above because this are with adaptive brightness!)
Rom chroma_hammerhead-ota-2015-04-10.zip + Kernel Code Blue r923
{
"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"
}
Rom Euphoria-OS-1.1-hammerhead-20150331.zip + Kernel Code Blue r923
Rom Rastapop_rascarlo_hammerhead-ota-2015-04-14 + Kernel Code Blue r923
Details test:
Rom Purity_hammerhead_ota_2015-04-13.zip + Kernel Code Blue r923
Details test:
Rom terminus_hammerhead-ota-2015-04-12.zip + Kernel Code Blue r923
Details test:
Rom OptiPop_5.1_Layers_N5-2015-04-13-GCC49.zip + Kernel Code Blue r923
Details test:
Rom Screw'd_hammerhead-1.1.0-OFFICIAL-20150419-1630.zip + Kernel Code Blue r923
Details test:
Rom boostpop_hammerhead-ota-3.2.zip + Kernel Code Blue r923
Details test:
Rom Resurrection Remix_LP_v5.4.2-20150419-hammerhead.zip + Kernel Code Blue r923
Details test:
Rom CataclysmApr_14_2015-HAMMERHEAD-Lollipop-5.1.0_r3_Stable.zip + Kernel Code Blue r923
Details test: //
Rom blisspop-v3.2-hammerhead-NIGHTLY-20150426-1219.zip + Kernel Code Blue r923
Details test:
Rom Dirty Unicorns_hammerhead_5.1.1_20150426-2219.v9.3-OFFICIAL.zip + Kernel Code Blue r923
Details test: //
[ROM]Test Battery life EXTRA
Factory Stock Google 5.1 + Kernel Stock Google
Details test: //
boostpop_hammerhead-ota-3.2.zip + Kernel Stock Build-in
Details Test: //
Euphoria-OS-1.1-hammerhead-20150428 + Kernel Stock Build-in
Details Test: //
Optipop_Layers_N5-2015-05-12-GCC49.zip + Kernel Stock Build-in
Details Test: //
Optipop_Layers_N5-2015-05-12-GCC49.zip + Kernel Code Blue r923 (governor: ondemand - scheduler: noop)
Details Test: //
OLD TEST: (don't compare with others above because this are with adaptive brightness!)
As we have seen, these ROMs are more or less all the same battery life with the same custom kernel.
The kernel is the thing that affects more.
For this reason, I would try some stock kernel built in .
For example, look at the example:
boostpop + kernel code blue VS boostpop + stock kernel built in.
There's a big difference
Rom Factory Stock Google 5.1 + Kernel Code Blue r923
Details test: //
Rom boostpop_hammerhead-ota-3.2.zip + Kernel Stock ROM built-in
Details test: //
I didn't knew that the stock Kernel was that good
rap1em said:
I didn't knew that the stock Kernel was that good
Click to expand...
Click to collapse
confirm.
The truth is that now the modding is a passion; a hobby.
Currently I saw ROM faster than factory google.
But as battery, google is the best.
I use the ROM because I love customizations. I lose something in battery life, but I feel good.
But if you only want a better battery, I suggest you go back on stock google
(canceled. I did it at night and adaptive brightness ruined everything. I will disable it)
fabi_92 said:
confirm.
The truth is that now the modding is a passion; a hobby.
Currently I saw ROM faster than factory google.
But as battery, google is the best.
I use the ROM because I love customizations. I lose something in battery life, but I feel good.
But if you only want a better battery, I suggest you go back on stock google
Click to expand...
Click to collapse
I prefer custom ROMs too (I love Chroma). But what do you suggest me, Stock kernel or CodeBlue?
rap1em said:
I prefer custom ROMs too (I love Chroma). But what do you suggest me, Stock kernel or CodeBlue?
Click to expand...
Click to collapse
I should do: Rom chroma_hammerhead-ota-2015-04-10.zip + Kernel Stock ROM built-in
When i finished, you can figure out which is best in battery. (code blue or kernel stock ROM)
A note:
usually, the kernel built-in ROM, have fewer customizations. (no dt2w, no faux audio and others).
The kernel of chroma not remember
Big like for you because u spend long time to test it. I'm impressed how Google kernel is battery friendly. I just installed stock from cataclysm. I hope it's the same.
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
Can you please maybe give Franco a try?
KyraOfFire said:
Can you please maybe give Franco a try?
Click to expand...
Click to collapse
I have also tested all the kernels with the same rom. (for a better compare)
Screw'd + Franco
Screw'd + Hells Core
Screw'd + Code Blude
Screw'd + Elemental x
and more....
The problem? tests are old.
When i will start those test, i'll create a new topic about the custom kernel (If I have time)
PS: if you want to know the old test, please send me a pm xP
hey guys.
i've added a new test: factory google + kernel stock.
I am sorry.
The last test was wrong. Now it's correct
The adaptive brightness ruined everything.
I'll have to do boostpop + code blue again and others
Also the story that google is the best battery friendly is false.
Now, everything is possible.
Stay tuned xD
Rom Factory Stock Google 5.1 + Kernel Stock Google
Details test: //
fabi_92 said:
Rom boostpop_hammerhead-ota-3.2.zip + Kernel Stock ROM built-in
Details test: //
Click to expand...
Click to collapse
Thanks for your testing. This is the only one that seems to have extended the battery time, but I can't understand why. You tested the same ROM and the same kernel in other configurations and did not see any increase, how come boostpop + stock kernel can go for longer? This seems unlikely.
bblzd said:
Thanks for your testing. This is the only one that seems to have extended the battery time, but I can't understand why. You tested the same ROM and the same kernel in other configurations and did not see any increase, how come boostpop + stock kernel can go for longer? This seems unlikely.
Click to expand...
Click to collapse
nope, i tested the same ROM with code blue. This test is with a stock kernel built-in rom.
it doesn't the same like kernel stock from factory image google.
anyway, the last test (except the last) are made with adaptive brightness. This I did not like. I'll have to make up and turn it off. The positive thing, however, is that they were made in the same times more or less (same light), then the same are accurate.
Deactivating the adaptive brightness, the result will overwrite the current one. Will surely change but now you know why
In short, the new tests should not be compared with the old.
at times, I tried to repeat the various tests and gave the same result, so I am happy and I hope it will be useful
fabi_92 said:
nope, i tested the same ROM with code blue. This test is with a stock kernel built-in rom.
it doesn't the same like kernel stock from factory image google.
anyway, the last test (except the last) are made with adaptive brightness. This I did not like. I'll have to make up and turn it off. The positive thing, however, is that they were made in the same times more or less (same light), then the same are accurate.
Deactivating the adaptive brightness, the result will overwrite the current one. Will surely change but now you know why
In short, the new tests should not be compared with the old.
at times, I tried to repeat the various tests and gave the same result, so I am happy and I hope it will be useful
Click to expand...
Click to collapse
It's just that stock Kernel + Stock ROM don't see the longer battery time. Only Stock Kernel + Boostpop ROM. So are you saying that somehow Boostpop ROM can extend battery time, but only when used with Stock Kernel yet stock kernel with another ROM does not? I think something is off with that measurement there, was it with a different brightness level as well perhaps?
Otherwise everything being the same with each kernel and ROM is exactly what I would expect with such a workload (constant, heavy, benchmark).
The reason why custom kernels can increase battery life is by reducing performance using different CPU governors. However those should only come into affect with lighter work loads where the CPU doesn't max itself out. ROMs on the other hand, have nothing really battery wise.
bblzd said:
It's just that stock Kernel + Stock ROM don't see the longer battery time. Only Stock Kernel + Boostpop ROM. So are you saying that somehow Boostpop ROM can extend battery time, but only when used with Stock Kernel yet stock kernel with another ROM does not? I think something is off with that measurement there, was it with a different brightness level as well perhaps?
Otherwise everything being the same with each kernel and ROM is exactly what I would expect with such a workload (constant, heavy, benchmark).
The reason why custom kernels can increase battery life is by reducing performance using different CPU governors. However those should only come into affect with lighter work loads where the CPU doesn't max itself out. ROMs on the other hand, have nothing really battery wise.
Click to expand...
Click to collapse
I agree with you in everything.
I'm pretty sure that if you use the Kerner built into the BoostPop ROM to another rom, you would get benefits.
Currently, I believe that only boostpop has that kind of kernel. (I would not say things that are not true)
Unfortunately, I'm not good with English and this doesn't allow me to express well.
Sorry and be patient xD
I read many times people who say: "how is the battery life on this ROM?"
I believe that all these AOSP, factory rom (such as cataclysm, pure white) stock google ... , more or less, are all the same in battery.
It is also seen in the test!
In my opinion, the most important thing is the kernel.
I'm just comparing some stock kernel built into the ROM with code blue kernel
for now, the various stock kernels have better battery life than code blue. also the kernel of google.
I know, also it depends on governors etc. but not all change it. many use the default governor
it will be interesting, when I return to try the same ROM with different kernel.
Battery stats and benchmark score on video review
Hey guys checkout this video review of N5X rom.....I have tested five different kernel with this rom. All the comparison between battery stats and benchmark scores are shown......
link : https://www.youtube.com/watch?v=VSPWBybFzPo
Check it out....
hi
I'm not dead.
I'm testing the ROM hidden
Why?
because the new tests should not be compared with previous ones. This reason because now i have disabled adaptive brightness and everything will be more accurate.
i will add coming soon when there will be many tests. so we don't confuses
There will be results with SOT lower. you are not afraid, it is normal. I increased the brightness and the results are lower
For now, i have tested:
Factory google 5.1 + stock kernel (in OP)
boostpop + kernel code blue
boostpop + kernel stock built in
euphoria + kernel code blue
euphoria + kernel stock built in
Update OP
The tests are more or less the same.
For this reason, I decided to slow down.
kernel is the most important for battery life and i've open a new topic -> http://forum.xda-developers.com/goo...st-battery-life-nexus-5-t3108824#post60744006
While I wait the new update of screw'd ROM (for kernel test), i will test new rom such us Cataclysm (rom factory that i miss) and ... bho ... i don't know :laugh:
Is that showing all the stock kernels are better than the codeblue?
I can't really see those images, they were very small.
natsuke said:
Is that showing all the stock kernels are better than the codeblue?
I can't really see those images, they were very small.
Click to expand...
Click to collapse
yes, for now .. the governor of the stock kernel tested, pass code blue.
No small
I see them with good size. it's strange
fabi_92 said:
yes, for now .. the governor of the stock kernel tested, pass code blue.
No small
I see them with good size. it's strange
Click to expand...
Click to collapse
i can see them just fine. strange that stock kernel gives better battery...could you please repeat one of the tests made with custom kernel(code blue for example) but this time with ondemand governor + noop scheduler to see if there is any difference?
Related
{
"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"
}
Tweaked Kernel v2
Work well on 1.9.23, 1.9.30 and CM7 nightly builds. Need Feedback.
Dont forget to read review from link at bottom of post if using CM7 builds.
Features :
Original Upgraded & Latest Kernel Base & its features (with UV/OC) --> Battery Saver Kernel
Juwe's Tweak --> Best RAM optimization - best balance between free memory, multitask, speed of launching apps and system speed
Darky's Zipalign --> Zip Aligning Files
Loopy Smoothness Tweaks (On Testing) --> Smoother Response & Less Delay while unlocking, notification pulldown, etc
Voodoo Support
FFC Support (EXPERIMENTAL)
What To Expect in Next Versions :
GPS Tweaks <== Couldn't work on these for v2 since 1.9.30 came out early and FFC experimentation began.
More Optimization Scripting
Better FFC Support
Steps to follow :
Reboot in Recovery Mode.
Flash this zip file, it takes care of all.
Reboot.
> Most of the Tweaks are already added to 360 Productions Released ROMs.
> This kernel is NOT coded by me, and is only for people who would like to add tweaks with original kernel taste.
> This can be also used by those already flashed/using other Kernel and want to step to original Kernel.
> I don't take credit for this original kernel's base work.
> I just made CWM flashable (didn't found anywhere & I need badly to test different kernels' performance) and added tweaks.
> This will reset your GPS to stock! .
Tested by me ON MIUI & CM7 nightly builds. Flash on your own risk. Feedback needed.
Neither me nor 360 Productions will be held responsible if something goes wrong.
Tweaked Kernel v2: Download
Original Kernel v2: Download
Experimental (Don't Flash; BROKEN BROKEN BROKEN) :
Tweaked Kernel v2 (FFC version A): Download
Tweaked Kernel v2 (FFC version B): Download
Older Versions:
Tweaked Kernel v1: Download
Original Kernel v1: Download
Hope you read OP properly.
Changelog for Tweaked Kernel:
Code:
[B]v2:[/B]
Base Kernel Upgraded as of 1.9.30
Now has Voodoo Support
FFC Support (Experimental)
Loopy Tweak Fixed for MIUI Launcher.
[B]v1:[/B]
Base Kernel as of 1.9.23
Loopy Smoothness Tweak
Juwe's RAM script
Added Darky's Zipalign script
Tested on CM7 builds: Read Review.
NOTE: If you using MIUI SS-10, please flash Tweaked Kernel v2.
Ffc support?
Sent from my GT-I9000 using Tapatalk
mohitmoudgil said:
Ffc support?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
NO. Not for v1.
I will see if I can add in next version.
can u please give the option for voodoo color other than that the kernal seems to fly its just when coming from another kernal the colors look like a lcd screen so its not that great
mohitmoudgil said:
Ffc support?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
FFC Support Definitely Coming in v2.
ceoesquad said:
can u please give the option for voodoo color other than that the kernal seems to fly its just when coming from another kernal the colors look like a lcd screen so its not that great
Click to expand...
Click to collapse
Not sure for Voodoo Color.
As mentioned in OP, kernel base not coded by me.
I am learning to code kernel myself, when done voodoo profile would be available.
If you want voodoo now, please reinstall Glitch.
this is what i am looking for, thanks.
neobuddy89 said:
Tweaked Kernel v1
Features :
Original Upgraded Kernel & its features (no voodoo color profile) by Atinm --> Battery Saver Kernel
Juwe's Tweak --> Best RAM optimization - best balance between free memory, multitask, speed of launching apps and system speed
Darky's Zipalign --> Zip Aligning Files
Loopy Smoothness Tweaks (On Testing) --> Smoother Response & Less Delay while unlocking, notification pulldown, etc
What To Expect in Next Versions :
GPS Tweaks
More Optimization Scripting
FFC Support
Steps to follow :
Reboot in Recovery Mode.
Flash this zip file, it takes care of all.
Reboot.
> Most of the Tweaks are already added to 360 Productions Released ROMs.
> This kernel is NOT coded by me, and is only for people who would like to add tweaks with original kernel taste.
> This can be also used by those already flashed/using other Kernel and want to step to original Kernel.
> I don't take credit for this original kernel's work.
> I just made CWM flashable (didn't found anywhere & I need badly to test different kernels' performance) and added tweaks.
> This will reset your GPS to stock! Please confirm if its working or not for v1.
Tested by me ON MIUI not CM7. Flash on your own risk. Feedback needed.
Neither me nor 360 Productions will be held responsible if something goes wrong.
Tweaked Kernel v1: Download
Original Kernel: Download
Hope you read OP properly.
Click to expand...
Click to collapse
ok so i been using it for some hours now and its fast but seems to run warm all the time my temp has been 40.2 c and thats with the screen off i dont have data on my phone so it couldnt be that any ideas?
ceoesquad said:
ok so i been using it for some hours now and its fast but seems to run warm all the time my temp has been 40.2 c and thats with the screen off i dont have data on my phone so it couldnt be that any ideas?
Click to expand...
Click to collapse
What was your previous kernel? Did you reboot your phone again after feeling warm? I faced this same while on Glitch Kernel. The lithium build had Glitch Kernel and I wanted to switch to Atinm's build, hence this release. Everything working quite good this side.
EDIT: Here are screenshots of system info from my phone, I believe battery life to improve with calibration cycles.
some gps fix on the next build makes me excited.
and here i share you something about vibrant GPS. as you know, even if replacing the gpsd and changing settings by angrygps.apk,vibrant GPS works randomly.
i am now aware that only if gpsd is appeared in the battery-consuming list(settings-system-battery-battery use), GPS works well!!!! BUT the dilemma is that gpsd don't launch every time you boot your phone.
nesson said:
some gps fix on the next build makes me excited.
and here i share you something about vibrant GPS. as you know, even if replacing the gpsd and changing settings by angrygps.apk,vibrant GPS works randomly.
i am now aware that only if gpsd is appeared in the battery-consuming list(settings-system-battery-battery use), GPS works well!!!! BUT the dilemma is that gpsd don't launch every time you boot your phone.
Click to expand...
Click to collapse
That dilemma can be resolved using some scripting, I think.
Thanks for the info.
FFC Support Definitely Coming in v2.
oh man...i love u for this......no homo
Thread updated with latest kernel.
FFC Experimental Support added.
Need feedback which version is better since both version have different files.
Please read OP carefully before flashing.
Hey neobuddy,
Glad to see a new updated kernel around here
So if Im not mistaken, the original kernel is the kernel atinm was creating correct?
Also, what would you say has the best battery life for CM7? And will these kernels give better battery life than the kernel that comes with CM7?
jzero88 said:
Hey neobuddy,
Glad to see a new updated kernel around here
So if Im not mistaken, the original kernel is the kernel atinm was creating correct?
Also, what would you say has the best battery life for CM7? And will these kernels give better battery life than the kernel that comes with CM7?
Click to expand...
Click to collapse
Suppose to work well on CM7.
Working smooth on MIUI.
I will test myself within couple of hours.
And will post results in the OP.
I'm not getting Screen V1 gamma hack in voodoo control with your kernel. Can you add that to next version?
hurtz777 said:
I'm not getting Screen V1 gamma hack in voodoo control with your kernel. Can you add that to next version?
Click to expand...
Click to collapse
Did you flashed latest v2 from the OP? If no, please do so.
And what ROM are you on?
I just checked with Tweaked Kernel v2. And I am getting gamma hack.
Note: If you cannot see gamma hack, you probably are on Tweaked/original Kernel v1.
Is this kernel based off of cm7 #134?
hurtz777 said:
Is this kernel based off of cm7 #134?
Click to expand...
Click to collapse
Nope, this kernel is based on MIUI 1.9.30.
I just added changelog, maybe that will solve some of doubts.
I am testing CM7 Builds and kernels.
Will report back and introduce if any better findings.
I just reflashed v2 tweaked and I still don't get screen v1 gamma hacks and the screen is dim at full brightness. I am using the new 2.37 cm7. I am back to Neo17r16 and the screen v1 gamma hacks shows up and works properly with no brightness issues.
Just wanna ask about ffc orientation.. I'm on miui 1. 9. 30 with ffc-6.. (glitch) ang I have a wrong orientation..
Samsung vibrant miui
pinadala gamit ang
XDA PREMIUM APP
{
"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"
}
ARM.
The Next Reliable Managed Architecture.
NOTE
- ARM or Android Reliant Management, Aims to bring full battery saving to our devices and add features not introduced. This would of course reduce battery hunger and at the same time, sustain the performance of our phones.
THIS IS A MODDED Kernel with Many fantastic features within. I am not responsible or credited for the kernel source codes whatsoever. I only modify the kernel to my needs and add more features not available from the base which will be beneficial to all of us. This Kernel is GPL Compliant and is fully Open Source. Please provide a CLEAR Credit should you use this Source as your base.
Click to expand...
Click to collapse
- Undervolted Clock values for more battery life
- Various Tweaks In Kernel
- Optional OC
- Each Clock Speed fully utililises its Voltage
- Powersave Tweaks on various modules
- Dimmer LED Lights for more Energy savings
- Lower Battery Consumption
- Maximised Minimal Brightness ! >v5.10 !
- UnderClocked minimal value to <300MHz
Click to expand...
Click to collapse
Source Code Distribution
Github [CM] - Source
Github [Stock] - Source
===============CHANGELOG=================
Base : CyanogenMod 10
Maintainers : nicholaschw & JaredMLG
v5.06
- Initial Release
v5.11
- Fixed 5.10 Wakelock Bug
v5.11a
- Fixed Issues on Source
- Final Compile for KU Only Source
- Tweaked 200Mhz again
v5.12b
- Changed Source for v30B
- Removed v5.12a Commits
- Compile with v30b Drop commit
v5.2 FINAL
Milestone Codename : EXO
- Fix OPP Segmentation Fault
- Fully implement Smartreflex fixes
- Add Voltage Control for AOKP
- Bump down Vibration
- Added 2012 SIO Scheduler
- Re-added SmartAssV2
- Re-added InteractiveX
- Re-added OndemandX
- Fix SmartAssV2 Lags
NEXT RELEASE : v5.2
Following Release : v5.2a
Click to expand...
Click to collapse
====================
Base: Stock v30B bproj
Maintainer: nicholaschw
NOTE: ALL v0 are not released publicly.
v0.01
- Re-build from bproj source
v0.02
- Switch in toolchain to better fit source
- Fix a few compile errors
v0.03
- Integrate LED 1mA
- Integrate Minimal Brightness
- Cleaned Source
v0.04
- Update 4.4.3 tool chain
- Fix a few flickering LED bugs
- Bump up the value for OPP
- Add 1.1GHz OC
- Reduced Minimal Sleep Clock to bypass minimum limit
NEXT RELEASE : v1
Following Release : v1.1
Click to expand...
Click to collapse
Bugs + CM +
--------
- LED on errors as shown in dmesg (All CM10 versions has this)
- Setting brightness flickers the LEDs
Bugs + STOCK +
--------
- LED on errors as shown in dmesg (All CM10 versions has this)
- Setting brightness flickers the LEDs
-Credits-
CyanogenMod, for providing AND fixing the source codes actively
YOU, Readers, for providing me a place to allow you to give me suggestions
Xonar, For assisting in many parts of the modifications
cyclon, for introducing new modifications
Google, For allowing me to identify whatever errors i face.
> XDA Community, Giving comments on whatevers best for implementations
This Thread is Started due to our previous moderator, Reinbeau who suggested not to re-open the old thread and instead, start a fresh one.
ANY FLAMING OR CRITICISM WILL BE REPORTED.
ARM., Is not to be mistaken with ARM. ARM. Is not related to ARM Whatsoever in terms of name.(We use ARM for our processor, so we are related somehow abit.)
+DO NOT MIRROR+
EVERYTHING IS GOING ACCORDING TO DATE OF RELEASE.
How To Install
- Download the flashable zip below
- Put it into your sdcard (Anywhere you like. Just remember its location)
- Boot into recovery
- Wipe cache, Dalvik Cache (NO NEED TO WIPE DATA UNLESS YOU WANT TO)
- Install the zip package
- Reboot
- Enjoy the Excitement!
Link List - CYANOGENMOD BASED
AVAILABLE ON ROM MANAGER!
ARM-Project-v5.06.zip - 4.68 MB
ARM-Project-v5.10.zip - 4.68 MB
ARM-Project-v5.11.zip - 4.68 MB - *Current Most Stable*
+ Should there be wakelocks, Flash the Official CyanogenMod and then flash the kernel.
+ Flashing on other CyanogenMod-based ROMs are experimental. Always ask in the thread of the ROM whether it works with ARM. . Never attempt anything that fails.
EXPERIMENTAL/NIGHTLY BUILDS
==================
All Builds below are experimental. Flash at your own risk.
ARM-Project-v5.10N2.zip - 4.68 MB
ARM-Project-v5.10N3.zip - 4.68 MB
ARM-Project-v5.12b.zip - 4.68 MB
Link List - STOCK BASED
None yet
EXPERIMENTAL/NIGHTLY BUILDS
==================
All Builds below are experimental. Flash at your own risk.
None yet
FAQs
+ Q: Whats the difference?
A: Read the disclaimer.
+ Q: Will I get worse performance than the Official CyanogenMod Kernel?
A: It depends on what commits are added. My Kernel only fixes bugs i can fix and which are unsolved and Of course, I will add more features not available in CyanogenMod Official
+ Q: What makes the stock kernel different?
A: You get goodies, and furthermore, better battery life and performance in this project.
After I flashed your kernel, I noticed Google Now's voice response does not work anymore - English (United States) is set as default.
chuayx1 said:
After I flashed your kernel, I noticed Google Now's voice response does not work anymore - English (United States) is set as default.
Click to expand...
Click to collapse
The point is that CM10 Nightlies dont even have Google Now Working properly. Besides, tell me how Google Now links to the Kernel. What, it needs more power? Note that Google Now may or may not work on each CM10 Build.
Afternoon.
nicholaschw said:
The point is that CM10 Nightlies dont even have Google Now Working properly. Besides, tell me how Google Now links to the Kernel. What, it needs more power? Note that Google Now may or may not work on each CM10 Build.
Click to expand...
Click to collapse
Most of the nightlies have the Google Now working....
@skate4life stop the hate dude, if you don't like Nick's work, just ignore him. Maybe he is crazy maybe he is not, but one crazy in this forum is enough.
sent from my Optimus Black V28c
chuayx1 said:
Most of the nightlies have the Google Now working....
Click to expand...
Click to collapse
I will see to that issue if its related to my kernel. But one thing sure is my kernel stops BLN from working.
Sent from my GT-I9300 using xda app-developers app
chuayx1 said:
Most of the nightlies have the Google Now working....
Click to expand...
Click to collapse
Sry for OT but apparently Google Now voice thingamabob does not work for me and im on stock kernel.Weird cuz the first few nightlies has it working
EDIT: I found a fix,First set your language in the language and input settings to Engish(United States)
then set the language of Google Now to English(US).After that,it should work with or without ARM kernel.Thanks for trying the kernel though...
re4lsk said:
@skate4life stop the hate dude, if you don't like Nick's work, just ignore him. Maybe he is crazy maybe he is not, but one crazy in this forum is enough.
sent from my Optimus Black V28c
Click to expand...
Click to collapse
Because of this I really wonder if this is really a custom kernel or not. *refers to Jellybam thread*.
chuayx1 said:
Because of this I really wonder if this is really a custom kernel or not. *refers to Jellybam thread*.
Click to expand...
Click to collapse
It is because the kernel now has a noticeable feature from CM kernel. It has a dimmer Backlight.
Sent from my GT-I9300 using xda app-developers app
nicholaschw said:
It is because the kernel now has a noticeable feature from CM kernel. It has a dimmer Backlight.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
The dimmer backlight only works fine if you also mod the rom. So i would (like i did) release a rom with kernel.
I have a link somewhere how to do it, someone on xda is the original source for backlight modifications, if you're interested i can send you the diffs for the mod.
cyclon1978 said:
The dimmer backlight only works fine if you also mod the rom. So i would (like i did) release a rom with kernel.
I have a link somewhere how to do it, someone on xda is the original source for backlight modifications, if you're interested i can send you the diffs for the mod.
Click to expand...
Click to collapse
Its better if you inject it into your ROM. That way i do not have to add a ROM into this thread. I told myself to fully work ONLY on kernels and thus this thread will only be purely kernels.
Hope you understand
So, inject my kernel into your ROM if, you want to combine both of our works. You should notice Dark Mod has still a bright backlight,which if you add this, will benefit into a darker environment
...i'm not trying to be pushy or anything, but will there be a chance of OC to 1.3 just like the Zeus Rom??
xX3m0Xx said:
...i'm not trying to be pushy or anything, but will there be a chance of OC to 1.3 just like the Zeus Rom??
Click to expand...
Click to collapse
Yes. Definitely.
Please try this out, Its been tested. I just need to see if Underclocking works to reduce battery drain.
This Nightly has reduced battery drain with 200MHz Underclocking
ARM-Project-v5.10N2.zip - 4.68 MB
nicholaschw said:
Its better if you inject it into your ROM. That way i do not have to add a ROM into this thread. I told myself to fully work ONLY on kernels and thus this thread will only be purely kernels.
Hope you understand
So, inject my kernel into your ROM if, you want to combine both of our works. You should notice Dark Mod has still a bright backlight,which if you add this, will benefit into a darker environment
Click to expand...
Click to collapse
The dark mod sets the brightness in aat2870_bl.c
val = (unsigned char) (level * 0x1F / 255);
val = 0xE0 | val;
aat2870_write_reg(client, AAT2870_REG1, val);
so we set in the register 0XE0 as lowest value for the brightness.
This is according to the aat2870 doku (http://www1.futureelectronics.com/doc/ANALOGICTECH - AATI/AAT2870IUW-DB1.pdf)
the absolute lowest technically possible value for the chip.
So, no, nothing is darker than dark mod
Except you use screen filters, but that wont save battery.
There are some really interesting information about ALS, and other things in the document. You'll realize that the driver is badly written and the hardware is... not assembled as optimal according to the document. lg should have used an additional cheap part of hardware for the als....
nicholaschw said:
Yes. Definitely.
Please try this out, Its been tested. I just need to see if Underclocking works to reduce battery drain.
This Nightly has reduced battery drain with 200MHz Underclocking
ARM-Project-v5.10N2.zip - 4.68 MB
Click to expand...
Click to collapse
After reading your posts history...well, can I trust your words on your developing?
I've flashed this kernel once more, I hope you're really committed and not repeat the same mistakes as said by the others on your previous thread..
All 4 touch LED buttons blue light up when one key is pressed. That's a bug. And if you can make an option somewhere to turn the entire front lights off/on at free will maybe you can try it. It it flickers when it's turned on from standby mode. Also, the screen getting brighter for 1 sec before returning to normal when the screen is turned on from standby mode, maybe that can be fixed too. I'm not a dev, but i'm testing out all.
have set your 200Mhz for underclocking, but I think it's best to leave the 1000Mhz clock frequency for those who don't wish to overclock their device - 900Mhz is what i'm using now, and not everyone might want to be on 1100mhz. just my 2 cents.
nicholaschw said:
ARM-Project-v5.10N2.zip - 4.68 MB
Click to expand...
Click to collapse
One question: what's not working in this? Cause there's just "LED on errors as shown in dmesg (All CM10 versions has this)" in OP... and last time I got SOD...
So I asked.
chuayx1 said:
All 4 touch LED buttons blue light up when one key is pressed. That's a bug. And if you can make an option somewhere to turn the entire front lights off/on at free will maybe you can try it. It it flickers when it's turned on from standby mode. Also, the screen getting brighter for 1 sec before returning to normal when the screen is turned on from standby mode, maybe that can be fixed too. I'm not a dev, but i'm testing out all.
Click to expand...
Click to collapse
... i'm having the same exact problems... hopefully, this will be fixed soon
Sent from my LG-P970 using xda premium
nicholaschw said:
ARM.
The Next Reliable Managed Architecture.
NOTE
- ARM or Android Reliant Management, Aims to bring full battery saving to our devices and add features not introduced. This would of course reduce battery hunger and at the same time, sustain the performance of our phones.
COMPATIBLE WITH (Kernel)
- ALL CyanogenMod 10 Based ROMs
Source Code - Github
Last Commits: 6 December 2012
Screenies
Base : CyanogenMod 10
Maintainer : nicholaschw
v5.06
- Re-Initialized Release
- Initital Public Release
- Reduce both White and Blue LEDs to 1mA
- Added SmartAssV2
- Fixed SmartAssV2 Compiling errors
- Reduce 400MHz clock rate to 300MHz
- Reduce voltages on all clock rates
v5.10 Nightly 1
- Attempted 1.2GHz
v5.10 Nightly 2
- Removed Previous attempt for further OC
- Added 200MHz Underclocking for more battery life
Click to expand...
Click to collapse
Bugs
--------
- LED on errors as shown in dmesg (All CM10 versions has this)
-Credits-
+ CyanogenMod, for providing AND fixing the source codes actively
+ YOU, Readers, for providing me a place to allow you to give me suggestions
+ Xonar, For assisting in many parts of the modifications
+ Google, For allowing me to identify whatever errors i face.
♥ XDA Community, Giving comments on whatevers best for implementations
This Thread is Started due to our previous moderator, Reinbeau who suggested not to re-open the old thread and instead, start a fresh one.
ANY FLAMING OR CRITICISM WILL BE REPORTED.
Click to expand...
Click to collapse
The main theme to use some KERNEL is to get good speed and performance of phone.
After seeing the benchmark in ur post, it looks funny for me.
Bcoz, without using ur Kernel, I am getting the same or above benchmark of CM10 ROM, then why to use ur Kernel ?
Click to expand...
Click to collapse
{
"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"
}
Base: N7100 KK Sources
Linux 3.0.31
Compiled using latest ArchiToolchain 5.2.0
ArchiDroid Optimizations
Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
And many other awesome things I have no time to list
ArchiDroid Optimizations:
- Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
- Compiled with O3 optimization level (-O3)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
Click to expand...
Click to collapse
Download
What to expect:
- Awesome stock battery life on AOSP ROMs (due to Samsung sources and not smdk4x12)
- Blazing fast (Deep advanced optimizations, Linaro toolchain, this is the beast)
- High compatibility (AnyKernel method, the kernel should work on all ROMs)
What to expect in future:
- You tell me
What to NOT expect:
- Many CPU or I/O governors # We don't need overhead, you can achieve nearly the same just by tweaking governor to your needs
- Features I don't like/need
- Dualboot (see above ^)
- F2FS (see above ^, however this one depends on kernel upstreaming, as f2fs is merged)
ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.
AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.
AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.
SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)
SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port
ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
Flashing instructions:
1. Make sure that you have stock kernel already flashed (the one which comes with your ROM), if you're running custom kernel already, reflash your ROM without wipe, this will also flash stock kernel. This is ultimately important, DON'T FLASH ARCHIKERNEL ON ANOTHER CUSTOM KERNEL, you may face various issues you've never seen before.
* This is because ArchiKernel uses AnyKernel method - it pulls ramdisk from your current kernel. If you brick your phone by flashing AK on top of custom kernel, you know who will be responsible for that.
2. Flash ArchiKernel zip.
3. Profit!
Updating instructions:
1. If you arleady have older ArchiKernel version flashed properly with above instructions, and changelog doesn't state otherwise, just flash the .zip with new version of AK.
2. No wipes, cleaning dalvik cache or anything else is required, flashing zip is enough.
3. Profit!
Bugs:
None known
XDA:DevDB Information
[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1, Kernel for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2
Source Code: https://github.com/ArchiDroid/ArchiKernel
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-06-17
Last Updated 2015-11-12
Reserved
Reserved
Last one.
Great job! Amazing to see a dedicated thread for this beauty.
Will report the experience
V1 uploaded in download section on the top of the thread. It should work with all AOSP ROMs but you tell me if it does. Don't flash it on Sammy (yet). Let me know if I screwed up something, it's late .
will test on omni,thanks
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
coto39 said:
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
Click to expand...
Click to collapse
At some point I'll definitely consider adding ArchiKernel support in ArchiDroid app, but it won't come too fast.
However, you can still "tweak it' in various ways. SetCPU, TricksterMod and similar apps are only a few examples. Boeffla Sound Control app (not boeffla config) will work as well. But think twice if you want to do, as ArchiKernel is pretty damn tweaked right after booting.
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
beeeto said:
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
Click to expand...
Click to collapse
If you want to know my opinion - Current smdk4x12 source used in all AOSP kernels is a crap. Somebody screwed up something really hard, I looked at the sources and there are over 7 hundred of different files (comparing to Update13), half of the updates from Update11, Update12 are not even included, while Update13 is not included at all. Whole kernel is one big mess and I have no idea how it even boots. It contains so many merge derps and hacks/workarounds that it hurts. I didn't even want to fix it, too much work to do. I started from clean stable and battery friendly Update13 base.
After flashing first alpha version of my kernel I immediately noticed significantly improved battery life, same as on Sammy ROM. So now I have my perfect combo, ArchiDroid 2.X AOSP speed and ArchiKernel Sammy battery life. Whatever you say, I'm keeping this baby. I love this kernel.
Big credit goes to @Yank555 and @Lord Boeffla because they're true kernel developers, I've made my own kernel based mostly on their commits (but not only, I added my own part as well and I'll add more soon).
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Add it to the OP!
While not everyone actually reads even the first post, even fewer people would actually bother reading the whole first page.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
skim0322 said:
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If need be, but the stock kernel alone should be enough if you get hands on a .zip.
Awesome
Sent from my GT-I9300 using Tapatalk
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
May I ask for a flashable zip file of the stock kernel..Thanks.:good: I would like to try this
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
i am on archidroid 2.4.6 with boeffla kernel.u mean that i cannot flash your kernel over my current kernel?
Are cam bugs gone since you did not upstream it to the 3.101?
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
brisK Kernel
brisK is a KitKat kernel for stock-based ROMs for the Samsung Galaxy S4 mini LTE (GT-I9195).
It aims to be faster and more a bit more battery-friendly than the stock kernel, while retaining its stability.
To prevent bloat I will only apply useful features like BLN. Adding 10 random governors and schedulers is not useful in my eyes, and is also not the goal of this kernel.
Goals
Stability: The original Samsung kernel is stable, so let's not go too far away from it. This kernel doesn't need bleeding edge code - it just works(TM).
Efficiency: Less power consumption by faster computation.
Battery: A battery drain patch is included, which is not in Samsungs original code.
Speed: Minor changes, for example: Trade some screen smoothness for less kernel overhead. Should not be noticeable, though. Also lowers power consumption slightly.
Changelog
v6 (brisk_kk-stock_2015-07-28_15-07-08_64d9234.zip)
Removed more KNOX stuff (--> This fixed some random reboots!)
Finally upgraded to new toolchain: Linaro GCC 4.9.4-2015.06 (Cortex-A15)
Thanks @impactor and @SilviuMik for providing help!
v5
Revert default IO scheduler back to CFQ
Apply changes from new released kernel source (GT-I9195_EUR_KK_Opensource.zip - I9195XXUCOA2)
Apply changes from new released kernel source (GT-I9195_EUR_KK_Opensource.zip - I9195XXUCOE4)
Older versions
v4
Fixed USB-to-PC problems by re-enabling some debugging code
v3
Users reported: USB-to-PC (MTP) doesn't work? (Logfiles appreciated)
Apply changes from Samsungs GT-I9195_EUR_KK_Opensource_Update1.zip
Replace stock Wlan module with kk_2.7_rb1.43
Various kernel config changes:
Disable various unused and debugging features
Re-enable heap randomization
Enable "Optimize very unlikely/likely branches"
Set default IO scheduler to noop
Reduce preemption from "Low-latency desktop" to "Desktop"
Disable Samsungs Rooting Restriction
Added init.d support
v2
Added OTG support (UNTESTED) - Edit: NOT WORKING YET
Removed TIMA
Change to XZ compression
Add BLN support (UNTESTED) - Edit: NOT WORKING YET
v1
Added battery drain patches
Optimize kernel for speed, not size
Preparation for init.d support
Permissive SELinux
Future plans
Add proper Prima WLAN driver - Done!
Add a few more optimizations - Done!
Add init.d - Done!
JellyBean Kernel
The old JellyBean kernel is no longer maintained, but it is stable and its uptime was above 2000 hours on my device. I published it here too, in case someone is happy with their JellyBean ROM and wants this.
Features: BLN, Battery drain patches, kernel config optimized, most debugging code deactivated
Source: https://github.com/TheBootloader/android_kernel_samsung_msm8930-common/tree/jb-stock
Awesome people
@SilviuMik for helping me getting started and providing useful tips - You rock!
@Christopher83 for his toolchains
@F4k for providing source code where I can snoop around
@junkyde for his kernel and his OTG and BLN patches
@arco68 for being another great resource
Downloads & Sources
Source code is on my GitHub.
Releases are at the bottom of this post and on GitHub.
See 2nd post if you need checksums.
PLEASE MAKE FULL BACKUP (/system TOO!) BEFORE FLASHING ANYTHING. The strangest things can happen if you don't have a backup - even if it *should* work.
Downloads are ordered from oldest to newest, so the newest release is at the bottom.
Checksums
brisK JB (brisk_jb_2014-05-16_16-40-39.zip)
MD5: 0f916929e85ae1f8d7b2d1aa8c4e5e1f
SHA256: 8cb1b01358eeb6bc7fb68bbb2fd641d5cda852b78d7e22605ffb28eba6da4156
brisK KK v1 (brisk_kk_2014-08-19_17-33-50_cd36751.zip)
MD5: 8edf28d8a2d1d89d40f8a8f1863d7b57
SHA256: aed1caf0d13ada04888e7c3a020fa6b679fc0fc36ad89678e617ae9a36d637e6
brisK KK v2 (brisk_kk-stock_2014-08-21_01-04-03_765f3f6.zip)
MD5: c004e49779f21f706e76a00233f8fb80
SHA256: df57729a66d425a970d8c8ef222edf6073e4cfc562d8dccea96f12ac0eac7aef
brisK KK v3 (brisk_kk-stock_2014-12-07_00-57-00_23da34c.zip)
MD5: d64b2c7049339eaed9d14bafdc8a9ee3
SHA256: 47741a492077d3e385e120c3596bf6df63426930fffcaa7aa84c924ff43fee91
brisK KK v4 (brisk_kk-stock_2014-12-07_15-31-03_1091455.zip)
MD5: d5fb48434fe9a206a9544968081ee654
SHA256: 122189fb11068be07e6d24cbe179ed57a9872944664e028d0d288fcf804ea4d2
brisK KK v5 (brisk_kk-stock_2015-07-23_23-57-24_518a15c.zip)
MD5: 2a5086c1354e6f475d73b77b41bcfe40
SHA256: 7dce6a173c9e6ddf6f573c802cc8aea7900239a2253ca31722e651e791bb6e6e
brisK KK v6 (brisk_kk-stock_2015-07-28_15-07-08_64d9234.zip)
MD5: 567d7e6ea8762559d218bb092c4cdac4
SHA256: b5b3b41fa7ed10210e4964fa2cd98d14d4572a30b68f7b939e945a3458063a43
Samsungs stock JellyBean Kernel (samsung_jb.zip)
Description: Reverts all changes made by brisK JB by overwriting it with Samsungs original JB kernel (extracted from I9195XXUBML4).
MD5: 388336cec2e9686e258985d0dded0dc9
SHA256: 35777926edee3558208175d5359ef1c466dc3d4dbb1276e233f6727d64b83aa3
Samsungs stock KitKat Kernel (samsung_kk2.zip)
Description: Reverts all changes made by brisK KK by overwriting it with Samsungs original KK kernel and files (extracted from I9195XXUCNE6).
MD5: c71112214620a50841731f4899dd2ca2
SHA256: d2d70f212ee898cf1cedef2d84b3e6345e2388a13579a7112181a254a2c2f3de
Installing
To flash any of these zip-files, you need to install a custom recovery on your phone. (For example: http://forum.xda-developers.com/showthread.php?t=2364980 )
Put zip file on your phone or on its microSD
Boot into recovery: Hold "Volume UP", "Home Button", and "Power Button" when it is off or rebooting
MAKE A FULL BACKUP BY USING THE BACKUP-MENU
Select "Install from zip" or something similar
Navigate to your zip file, select it, and flash it
Reboot your phone
Uninstalling
If you want to go back to Samsungs stock kernel or flash another kernel, you need to install "samsung_jb.zip" or "samsung_kk.zip" first.
brisK uses custom kernel modules. When you run on brisK and then directly install another custom kernel which has no custom modules, you will probably experience issues with WLAN and other stuff. To solve this, flash "samsung_jb.zip" or "samsung_kk.zip" (which flashes the stock modules), and THEN flash whatever custom kernel you want. - Of course you do NOT need to do this if you update to a newer version of brisK.
thank !
GREAT !!!
but for governors and schedulers , i agree with you in half ... but "few" of them are very useful !
what do you think about the recent "zen" ...or "row" ( by default in all customs like cyanogenmod ) ?
for you ,what are the "best" (more adapted ) for better compromise in performance/baterry save ?
why you don't add just 1 or 2 among the best of ones ?
Now running on brisK
{
"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"
}
Loulou-13 said:
but for governors and schedulers , i agree with you in half ... but "few" of them are very useful !
Click to expand...
Click to collapse
I agree that some governors might actually improve performance, but there isn't much information available, some people say governor A is better, some say B is best...
But also: Kernel goal nr. 1 is stability, and ondemand is well tested. That's why I probably won't add any new governor before testing them a lot.
Can you suggest any governors? And do you have proof or URLs why they are better? Thanks!
If you want more features, more governors, etc, f4k will probably release a stock kernel soon. So keep an eye out for that!
Loulou-13 said:
what do you think about the recent "zen" ...or "row" ( by default in all customs like cyanogenmod ) ?
for you ,what are the "best" (more adapted ) for better compromise in performance/baterry save ?
why you don't add just 1 or 2 among the best of ones ?
Click to expand...
Click to collapse
Zen: I don't know what this does different than other schedulers, I have to read about this first.
I considered "row" when I had an Evo 3D, but I didn't notice a difference between "noop" and "row" in normal daily usage, so I'm not sure yet if I will include it or not - needs more testing.
ladislav.heller said:
Now running on brisK
Click to expand...
Click to collapse
Awesome!
If you have any problems, please report them here. And if you don't have any problems at all, please report that here too!
TheBootloader said:
I agree that some governors might actually improve performance, but there isn't much information available, some people governor A is better, some say B is best...
But also: Kernel goal nr. 1 is stability, and ondemand is well tested. That's why I probably won't add any new governor before testing them a lot.
Can you suggest any governors? And do you have proof or URLs why they are better? Thank!
If you want more features, more governors, etc, f4k will probably release a stock kernel soon. So keep an eye out for that!
Zen: I don't know what this does different than other schedulers, I have to read about this first.
I considered "row" when I had an Evo 3D, but I didn't notice a difference between "noop" and "row" in normal daily usage, so I'm not sure yet if I will include it or not - needs more testing.
Click to expand...
Click to collapse
Same thinking as me ...
ondemand for CPU Gov / No-op for I/O sched , they work great and don`t cause problems
SilviuMik said:
Same thinking as me ...
ondemand for CPU Gov / No-op for I/O sched , they work great and don`t cause problems
Click to expand...
Click to collapse
Yes, my experience too!
Although, when I copy big files with "noop", android freezes for the duration of the copy process. That's the nature of "noop", but "row" might actually fix that. But then again: I rarely need to copy big files, so "noop" is okay for now.
TheBootloader said:
Awesome!
If you have any problems, please report them here. And if you don't have any problems at all, please report that here too!
Click to expand...
Click to collapse
No problems, everything works well.
Please add support for USB Host with additional power supply, is very necessary !!!!
killov1982 said:
Please add support for USB Host with additional power supply, is very necessary !!!!
Click to expand...
Click to collapse
+1 for USB OTG support.
Working good so far
Thanks
TheBootloader said:
Yes, my experience too!
Although, when I copy big files with "noop", android freezes for the duration of the copy process. That's the nature of "noop", but "row" might actually fix that. But then again: I rarely need to copy big files, so "noop" is okay for now.
Click to expand...
Click to collapse
NOOP hangs in general when the read/write task becomes too intensive. Consider CFQ if you're going to do a bit write operation, else ROW is better. That my two cent when I tried on my S3 with Boffela kernel.
PS. ZEN hangs even worse than NOOP.
ladislav.heller said:
+1 for USB OTG support.
Click to expand...
Click to collapse
I second that
thank for your work...
is your kernel working with old knox-free bootloaders like Silviumik's kernel?
thanks
battery life compared with carbon 4.4.4 ? PLEASE
s.goten said:
thank for your work...
is your kernel working with old knox-free bootloaders like Silviumik's kernel?
thanks
Click to expand...
Click to collapse
For now i think no, because he did not remove Knox reference from source, i could be wrong tho !
I just released a new version!
A lot people asked for OTG, so here you go! I added OTG and BLN (untested!!!), thanks to junkyDE!
The highest kernel goal is stability, but I don't have time to test these features right now - maybe I can do one quick emergency fix tomorrow if something breaks, but after that I will probably not respond for 2 weeks or more.
So, have fun and enjoy!
brisK v2
Added OTG support (UNTESTED)
Removed TIMA
Change to XZ compression
Add BLN support (UNTESTED)
-----
s.goten said:
thank for your work... is your kernel working with old knox-free bootloaders like Silviumik's kernel?
Click to expand...
Click to collapse
SilviuMik said:
For now i think no, because he did not remove Knox reference from source, i could be wrong tho !
Click to expand...
Click to collapse
I removed TIMA in brisK v2, so.... it -should- work now right?
If it doesn't boot, just restore your boot partition from a backup or re-flash your previous kernel if you had any.
-----
TNCS said:
NOOP hangs in general when the read/write task becomes too intensive. Consider CFQ if you're going to do a bit write operation, else ROW is better. That my two cent when I tried on my S3 with Boffela kernel. PS. ZEN hangs even worse than NOOP.
Click to expand...
Click to collapse
Thanks a lot for your input! Now I know I don't need to consider ZEN, and will stay with NOOP, and aim for ROW when I have time to add it.
I9192?
Sent from my GT-I9192 using XDA Premium 4 mobile app
SilviuMik made a 9192 kernel:
http://forum.xda-developers.com/showthread.php?t=2592308
{
"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"
}
I am not responsible for bricked devices, dead sd cards, explosions, nuclear wars, alarm applications getting failed, please read the first 3 posts (features, faq, settings) carefully before flashing this kernel to make sure everything goes well with your installation.
This kernel will focus on quality over quantity, I will add only those features which don't cause instability and really improve performance or battery life of our device. I like to test my changes properly before release and keep stability the topmost priority, I don't guarantee weekly or nightly builds, updates will be given whenever required.
Some Kernel Features-
Cpu Improvements -
Balanced, Battery and Gaming modes available for interactive governor
Mild undervolt for our cpu, reduces heat, helps battery backup
All basic governors and relaxed governors available, default is interactive
Toggles for wakeup boost, hotplug boost, touch boost
IO & Memory Improvements -
Added fiops, bfq, zen, maple, sio io schedulers
Disabled io crc check for more performance
Zram with lz4 & lz0 compression support available
NTFS, exFAT, F2FS, EXT filesystems support
Gpu/Display Improvements -
Fixed wrong gpu frequency reflected in sysfs
Optional enhanced color profile, choose while flashing
Adreno idler and adreno boost are available, off by default
Savoca's kcal color control, full control over colors
Wake gestures, dt2w, s2s and s2w for all panels
Charging/Battery Improvements -
Option to select 2000mA or 2400mA charging rates
Tuned interactive governor for better battery backup
Mild stable undervolt for both cpu and gpu
Optimizations for better load and power management
Other Improvements -
Sound control for speaker, earphones, mic etc
Option to select selinux mode while installing
Compiled with aosp 4.9.4 aarch64 toolchain
Fsync toggle available, enabled by default
Custom vibration intensity control available
Confirmed working or not working on -
Works on all lineage and aosp based nougat roms
Works on all lineage and aosp based marshmallow roms
Works on all MIUI 8+ marshmallow roms
Flashing Instructions -
Prefer flashing over your rom's stock kernel for best results
Read post #2 for some frequently asked questions
Download correct version of Radon kernel
Make backup of system, boot in twrp
Now, wipe dalvik cache and cache
Flash the kernel zip and reboot
Note - In case the kernel doesn't boot for you, restore your system and boot partition from twrp and you will not lose any data.
Stable build downloads -
Radon V6.3 Stable Builds ( Android 8.1.0, 7.1.2 & 6.0.1 )
Kernel control app -
Radon kernel control
If you like my work, consider donating -
Paypal
XDA:DevDB Information
Radon Kernel For Kenzo, Kernel for the Xiaomi Redmi Note 3
Contributors
Umang96, TheStrix, Balika011, ktomov, abhishek987
GuneetAtwal, MOVZX, franciscofranco, flar2
alex9yust, billchen1977
These are not in any specific order, please pm me If I missed anyone
Version Information
Source: Github
Status: Stable
Current Stable Version: V6.1
Created 2016-07-09
Last Updated 2017-12-10
Frequently Asked Questions -
Q ) I like this kernel, can I be a part and contribute to this project ?
It takes many hours to maintain this kernel, If you are a user then donations are appreciated. If you want to contribute to development then you can create your pull requests on my github or pm me with your patch.
Click to expand...
Click to collapse
Q ) I flashed this kernel, what next ? How and where do I configure kernel related settings ?
Recommended app is Radon kernel control, it offers very easy to use custom profile based tweaking, you may check post #3 for some tuning tips if you like to tune kernel settings yourself.
Click to expand...
Click to collapse
Q ) Read mode in miui is not working after flashing this kernel ?
Xiaomi hasn't provided the opensource code for this feature, so read mode is not going to work on custom kernels, but you can try going into display tab of radon kernel control app and make a custom profile with R,G,B(254,234,195) and saturation 40 for very similar experience to miui read mode.
Click to expand...
Click to collapse
Q ) My fingerprint doesn't work, what to do ?
Kenzo comes with two different sensors, fpc and goodix, all nougat roms have fixed support for both sensors, but if you use miui rom and you have goodix sensor then you might need to flash the patch from post #6196.
Click to expand...
Click to collapse
Q ) I flashed this kernel, but I want to return to my stock kernel, how to do that ?
If you read flashing instructions in first post, you will see that I asked you to make backup of boot and system partitions before flashing my kernel, now you can restore that backup and you will have your stock kernel back. In case you didn't take a backup, just dirty flash your rom zip without wiping data and that will restore stock kernel and modules.
Click to expand...
Click to collapse
Q ) How much battery backup does this kernel give ? Will it give me x hours of SOT ?
The battery backup depends a lot on your usage, like screen brightness, wifi, 3g/4g data. Changing your kernel or rom will not make battery backup double. If you are just wifi user, your device can give 9+ hrs screen on time. Heavy 3G, 4G, Bluetooth users shouldn't expect huge battery backup. Regarding battery consumption when display is off, I normally lose 2% battery for about 8-9 hours of standby, but if you you keep wifi and data off in night, then you should get 0-1% drain per night.
Click to expand...
Click to collapse
Kernel tuning tips -
Cpu -
Governor: Interactive for all kind of users, select battery/balanced/gaming mode while installing according to your need, balanced and gaming modes are totally smooth but battery mode might have little lags.
Users who wish to further push battery backup can try using relaxed cpu governor on small cluster, reducing max frequency of small cluster will also improve battery backup.
By default, I use these min cpu frequencies 691Mhz (small cluster) and 883Mhz(big cluster), there is also 400Mhz option but I don't recommend using that since it saves negligible battery.
Input boost and touch boost should be kept on by balanced/gaming users, battery biased users can consider turning them off.
Memory -
Adaptive lmk should be enabled by all users
Z-RAM 512MB with at least 40 swappiness
Z-RAM will increase battery consumption a little bit
Keep Z-RAM off if you need extra battery backup
IO Scheduler -
FIOPS for good performance and battery
Read ahead at least 512 KB on both internal and external
Screen -
Adjust this yourself, I don't know what you like.
Gpu -
Adreno idler - only battery biased users should keep this on.
Adreno boost - gamers or performance biased users should keep this on.
Misc -
Fsync -Enabled for more stability, disabled for more performance.
Vibration intensity - I use 60, select whatever you like here.
Note - All settings are compatible with Radon kernel control.
I am using RADON Kernel From very first Build and to be honest ,
RADON is Awesome In Performance , Super Smooth and Fully Stable Kernel.
It Rocks Redmi note 3 Development :highfive:
please bring the Over clock feature
Will try to boot it on mokee! Will update !
Edit : Doesnot boots on Mokee
Sent from my Redmi Note 3 using Tapatalk
biku123 said:
please bring the Over clock feature
Click to expand...
Click to collapse
Our phones performance is already great
No point in over clock.
Sent from my Redmi Note 3 using Tapatalk
picarito said:
Our phones performance is already great
No point in over clock.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Right, overclock is not useful unless you are using a low end or outdated device.
Umang96 said:
Right, overclock is never useful unelss you are using a low end device.
Click to expand...
Click to collapse
Are you using the stock frequency table?
Umang96 said:
Right, overclock is never useful unelss you are using a low end device.
Click to expand...
Click to collapse
Yes so please don't add over clock lol maybe any sound changes like faux sound or Franco sound? If it's possible of course.
Sent from my Redmi Note 3 using Tapatalk
Pls add Exfat support
Please consider adding color control and Intel gov and if possible Westwood TCP algorithm, since data is not stable in bsnl sim and radio of our device is also not perfect it would be useful.
Sent from my Redmi Note 3 using Tapatalk
Its the any posibility to add manual features to the camera by kernel?
Enviado desde mi Redmi Note 3 mediante Tapatalk
please add color saturation control support ,is it already there?? if not please add .Then only i will be able to use cm13 roms.:good:
@Umang96 Can u share the voltage for each frequency?
shubham tech said:
please add color saturation control support ,is it already there?? if not please add .Then only i will be able to use cm13 roms.:good:
Click to expand...
Click to collapse
That should not be the only reason to switch to cm13.cm13 is way superior than miui.
Sent from my Redmi Note 3 using Tapatalk
Umang96 said:
Cpu Big -
400 - 1747 Impulse
Cpu Small -
400 - 1401 Impulse
IO Scheduler -
BFQ on both external and internal
Read ahead 1024 on both
Click to expand...
Click to collapse
In official RR....minimum frequency is not staying in CPU small.....its coming back to 1305
Add qnovo fast charging in a future update please
sanjeev7 said:
In official RR....minimum frequency is not staying in CPU small.....its coming back to 1305
Click to expand...
Click to collapse
That is fine, it shows wrong, it's cm feature, cpu is boosted in input, it will jump from 400 to 1305 sometimes but will come back.
Was Expecting Cyanpro :3 Btw cool u rocket In Yu forums Man hatf off !
Sent from my Redmi Note 3 using Redmi Note 3 Forums