[13.09.2017] Rom & Kernel - HTC 10 Questions & Answers

Hello, which rom and kernel are recommendable for that time ? I want battery friendly and don't overheating so much.
Thanks,
Best Regards

dzesiu2002 said:
Hello, which rom and kernel are recommendable for that time ? I want battery friendly and don't overheating so much.
Thanks,
Best Regards
Click to expand...
Click to collapse
Latest aosip rom with nebula v10 is the best I can do when it comes to battery and performance, you'll need kernel auditor or ex kernel manager to get 100% the best battery possible my friend.

Dlind said:
Latest aosip rom with nebula v10 is the best I can do when it comes to battery and performance, you'll need kernel auditor or ex kernel manager to get 100% the best battery possible my friend.
Click to expand...
Click to collapse
@Dlind could you help with the setup that you've found working the best? So you are running latest AOSiP ROM and Nebula EAS kernel, so how's Nebula compared to the one which is included with the ROM? What kind of tweaks you've applied with kernel configuration apps? Anything else?

Kaedin said:
@Dlind could you help with the setup that you've found working the best? So you are running latest AOSiP ROM and Nebula EAS kernel, so how's Nebula compared to the one which is included with the ROM? What kind of tweaks you've applied with kernel configuration apps? Anything else?
Click to expand...
Click to collapse
I like the kernel in the regular aosip. But what nebula has over the aosip regular kernel is, the cpu governors. I've ALWAYS, ALWAYS, ALWAYS! had issues with sched/schedutil. They lag with youtube. And are biased toward power to much for my liking, but if you don't watch youtube much that's ok. But sched/schedutil also has given me the best results when multi tasking. I personally love cultivation. Its a smarter version of good old interactive. There's also options for using a slight over clock to cpu and gpu. Also with this kernel there is an adjustable throttle for when the cpu overheats it in Celsius btw. All these settings are in ex kernel manager and in kernel auditor, they both are great apps. Under cpu mic spot in the bottom turn off perfd and leave wq_power_saving on.

Dlind said:
I like the kernel in the regular aosip. But what nebula has over the aosip regular kernel is, the cpu governors. I've ALWAYS, ALWAYS, ALWAYS! had issues with sched/schedutil. They lag with youtube. And are biased toward power to much for my liking, but if you don't watch youtube much that's ok. But sched/schedutil also has given me the best results when multi tasking. I personally love cultivation. Its a smarter version of good old interactive. There's also options for using a slight over clock to cpu and gpu. Also with this kernel there is an adjustable throttle for when the cpu overheats it in Celsius btw. All these settings are in ex kernel manager and in kernel auditor, they both are great apps. Under cpu mic spot in the bottom turn off perfd and leave wq_power_saving on.
Click to expand...
Click to collapse
There are some advantages leaving perfd on. Search it on google..

Related

[Q] Best kernel for MIUI

I am currently using MIUI 1.7.29 Osimood with the Tiamat 1.04 kernel, and I am wondering what the best kernel is for battery life. I am also using the V6 supercharger ram script. I am running my CPU at 960mHz at the moment, using the smartass governer. I also undervolted using vipermod, 960MHz at 950mV.
My choice consists of the latest Pershoot, UmaroKernel 1.06 or Tiamat 1.04
What differences would I see between those kernels, are they noticeable for a regular user?
Sorry man, but wehre do you find the vipermod for desire z? http://vipermod.tiamat-dev.com/faq.php it's not compatibile with desire z/g2....
Uh...what's wrong with the kernel it comes with? Can OC to 1.5GHz stock ya know. Battery life is great with it too. People always want to flash something weather it be a radio or a kernel.
Sent from my HTC Desire Z using XDA Premium App
Spastic909 said:
Uh...what's wrong with the kernel it comes with? Can OC to 1.5GHz stock ya know. Battery life is great with it too. People always want to flash something weather it be a radio or a kernel.
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
Isn't flashing stuff and trying new things basicly the point of this whole site?
ostinq said:
Isn't flashing stuff and trying new things basicly the point of this whole site?
Click to expand...
Click to collapse
damn straight,
1) pershoot is a sense kernel? (i am proabably wrong but i have never tried this kernel)
2) umaro kernel i found had issues with wifi, high underclock freq (leading to poorer battery life), but fun if you have the time to tweak voltages and fast!
3) tiamat kernel i found had issues with sleep of death/random reboots on wakeup couldnt test it past that. (setcpu was set to screen off was: conservative 125min -345 max and would still crash)
if you are up for another kernel, i am now using this kernel (streamline5)
no voltage tweaking (pretweaked) but it has good batt, speedy and stable cant ask for much
http://forum.androidspin.com/showthread.php/6555-Streamline5-Nightly-CM7-Test-Kernel-2.6.35.13
lalalandrus said:
damn straight,
1) pershoot is a sense kernel? (i am proabably wrong but i have never tried this kernel)
2) umaro kernel i found had issues with wifi, high underclock freq (leading to poorer battery life), but fun if you have the time to tweak voltages and fast!
3) tiamat kernel i found had issues with sleep of death/random reboots on wakeup couldnt test it past that. (setcpu was set to screen off was: conservative 125min -345 max and would still crash)
if you are up for another kernel, i am now using this kernel (streamline5)
no voltage tweaking (pretweaked) but it has good batt, speedy and stable cant ask for much
http://forum.androidspin.com/showthread.php/6555-Streamline5-Nightly-CM7-Test-Kernel-2.6.35.13
Click to expand...
Click to collapse
Pershoot is actually for non-sense roms. The downfall people have with it is lack of governors. Some don't mind, some want variety. I've had great experiences with Pershoot's kernel and it's the baseline that all others are compared to (not to mention the foundation of almost ALL G2/DZ kernels).
Umaro's just needs to have voltage tweaks done manually but on the plus side - keeping the voltages normal (not UV) allows some people to reach higher OC speeds. It keeps the processor from bottoming out due to insufficient voltage which can easily happen when you UV. The main issue is with the Greased lightening governor - it's new and still a bit buggy.
Tiamat 1.0.4 is outstanding. I can sit all day at 2+ GHz (not literally, see: Chernobyl). I personally have an issue with the interactive governor but other than that it's my favorite kernel (Umaro may take that soon, once greased lightening is perfected).
Basically you just need to try out a few and see which you like. There is no 'best'. Most kernels will work with any ROM (Sense being the only exception).
Bumping a thread that is relevant to my interests.
It's about time for me to jump ship from an outdated CM ROM and try something new like a MIUI ROM.
With that said, I'd like to read more opinions & experiences from people using the various Kernels AND how the latest radio (the one released today) is working for them. I'm just trying to get the optimal experience here
Speaking of MIUI would anyone mind telling me some differences between OsiMood's ROM compared to the official MIUI-US ROM (or even DarkSpadez ROM)?
Thanks a ton guys!
I downloaded the official rom . . .then ignored it downloaded osimood and iv been using it since. Osimood is a lighter rom, which is always a good thing, unwanted languages etc are removed for a smaller faster rom. Also he preinstalls tweaks like an adblocker and extended settings mod.
Kernal wise iv been looking for the same info as you but couldn't find it. So I eneded up trying them all:
- Eugenes streamline5 is a nice kernal, preundervolted. Only probly is its not being updated so will become redundant.
-Tiamats kernal allows over clock to 2ghz and seems to support higher overclocks stably where other kernals can't. Except battery life has decreased with recent kernals
-Umarokernal this is the kernal iv come back to twice and am still on. It allows overclock to 1.9ghz and is kept updated by umaro. Performance per frequency seems as good if not better than most and osimoods miui runs smooth with this kernal on 800ghz with scarey governer (which saves battery) Another plus for me with this kernal is the scarey governer which for me definatly provides the best performance per battery ratio.
I'm currently running MIUI 1.8.5 with Eugene-Streamline 5 Kernel with the latest radio update Vision_Radio_12.57.60.25_26.10.04.12.
SetCPU with Governor ondemand provides me with better usage, power and responsive time then Smartass or Interactive.
OC to 1.2ghz
Battery life, about 30hrs with the regular 1350mah.
Screen cap
fluxgfx said:
I'm currently running MIUI 1.8.5 with Eugene-Streamline 5 Kernel with the latest radio update Vision_Radio_12.57.60.25_26.10.04.12.
SetCPU with Governor ondemand provides me with better usage, power and responsive time then Smartass or Interactive.
OC to 1.2ghz
Battery life, about 30hrs with the regular 1350mah.
Click to expand...
Click to collapse
i just got 40 hours with similar setup but i use virtuous o/c daemon instead of setcpu
big fan of streamline5 and hope that it will get updated eventually
How do you get the virtuos o/c daemon?
maxietheboss said:
How do you get the virtuos o/c daemon?
Click to expand...
Click to collapse
Its basically like an automatic setcpu (which can't be changed on the fly) built into the rom, its in virtuous unity roms
What sleep profiles are you guys usein. I seem to have rebooting issues with any kernel I try unless I go to a sense rom. I've tried the vipermod now to see how it goes
Sent from my T-Mobile G2 using XDA App
But how do you get the virtuos O/C daemon to work on MIUI?
You can download it threw rom manager. Even with that kernel I get reboot issues. I assume its cause system ram isn't being cleard fast enough. I'm gonna try 100mv increase to see if there's a difference.
Sent from my T-Mobile G2 using XDA App

ICS kernel with conservative governor.

Are there any ICS kernels that have the conservative governor included? Battery life is a big issue for me on AOKP and CM9, which prevents me from using them as a daily driver.
At the same time, I love them for being so slick and having the Bluetooth audio issues fixed.
Any help is appreciated.
Sunsparc said:
Are there any ICS kernels that have the conservative governor included? Battery life is a big issue for me on AOKP and CM9, which prevents me from using them as a daily driver.
At the same time, I love them for being so slick and having the Bluetooth audio issues fixed.
Any help is appreciated.
Click to expand...
Click to collapse
No, because there are no custom kernels yet that are compatible with ICS.
I think we can fix that one without the custom repacked kernel.
Do you know which governors being used for AOKP and what CPU frequencies?
What I'm thinking about is, we could take the cpu tweaks on my thread http://forum.xda-developers.com/showthread.php?t=1625299, http://forum.xda-developers.com/showthread.php?t=1610741 (all_in_here.zip, there are two cpu tweak files) and make the modification to fit to AOKP.
Currently on these tweak, I'm using 'ondemand' governor as default because conservative governor is not supported on ICS stock kernel yet. By changing the values on ondemand governor, we may get the same result.
(with some other tweaks, I'm getting 24hours now with 50% battery still left on Stock rom/kernel)
kobridge said:
I think we can fix that one without the custom repacked kernel.
Do you know which governors being used for AOKP and what CPU frequencies?
What I'm thinking about is, we could take the cpu tweaks on my thread , (all_in_here.zip, there are two cpu tweak files) and make the modification to fit to AOKP.
Currently on these tweak, I'm using 'ondemand' governor as default because conservative governor is not supported on ICS stock kernel yet. By changing the values on ondemand governor, we may get the same result.
(with some other tweaks, I'm getting 24hours now with 50% battery still left on Stock rom/kernel)
Click to expand...
Click to collapse
That's actually phenomenal. I'm at 46% after 6 1/2 hours.

[Kernel] [CM9 - RC2 & RC3] honeyx 7up 2.6.35 kernel [for better battery life]

Due to some requests via PM´s I decided to make my kernel finally public, but remember:
This kernel is a personal kernel for my private use, so it´s only containing the tweaks I´m also really using
It´s the older 2.6.35 kernel basing on latest 2.6.35 sources from Arco, so only use it with Arcos CM9 RC2 or RC3 or a custom ROM with 2.6.35 kernel
This kernel is not filled with a lot of governors and schedulers, but only the ones I´m also personally using.
I have made this kernel because non of the custom kernels worked stable for me in the past, even at stock voltages. With this kernel I´m able to run at extreme Undervolting rock solid.
So this kernel was created with stability and battery life in mind. Each modification was tested separately, so everytime I added a tweak or a new feature, I tested the new kernel for a couple of days before adding the next one.
So why I decided to tweak this older kernel rather than going with 3.x kernel?
- Because this kernel is giving me a much better battery life than the 3.x kernel, is running rock solid and also because I don´t really need the new features added into 3.x kernel.
So what it has included:
- UV and OC options
- lowered WiFi voltage
- lowered lcd voltage
- slightly lowered standby / deepsleep voltage
- Battery life extender
- Fixed 100% battery notification after charger unplug
- 377MB RAM
- NO-OP scheduler as default scheduler
- Lulzactive governor as default governor
- tweaked Lulzactive for battery life and smoothness
- added 518, 633 and 902 MHz (new)
- screen off frequency set to 518 MHz max.(new)
- some more voltage tweaks
- no other compilation tweaks just to make the list longer
With this kernel and a new battery my SGW can last up to 7 days in standby. This is without WiFi and Mobile Data. With the stock kernel I got 3-5 days. It´s also working absolutely stable and smooth for me without any issues.
So if you run into some issues that are/were also discussed i the CM9 Bug report thread, don´t blame me for them.
other suggestions:
- enable KSM
- enable 16bit Dithering
- disable CPU rendering
- greenify your apps
If you follow these suggestions, your ROM should run absolutely smooth without the need for other tweaks.
To use Battery Life eXtender:
Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions.
Just as a note. Should you encounter the white screen bug in some apps, this is because you whiped the cache in CWM Recovery after flashing the kernel. To fix this go into settings -> apps and delete data and cache of those specific apps.
Credits are going to:
- Arco (for his great work and sources)
- educk (for helping me doing the first steps)
- Christopher83 (for his great commits)
- ivendor (for his tweaks)
- Ezekeel (for Battery Life eXtender)
----------- 18.08.2013 -----------
- added frequencies
- incrased RAM
- lowered screen off frequency in Lulzactive
- some voltage finetunning
CM_9-2.6.35-7up-kernel.zip
----------- first release -----------
Download.
XDA:DevDB Information
[Kernel] [CM9 - RC2 & RC3] honeyx 7up 2.6.35 kernel [for better battery life], a Kernel for the Samsung Galaxy W I8150
Contributors
honeyx, http://forum.xda-developers.com/member.php?u=4410351
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2013-09-24
Last Updated 2013-09-24
First, thanks :good:
Edit: can i have your permission to use this kernel on my ROM?
ipromeh said:
First, thanks :good:
Edit: can i have your permission to use this kernel on my ROM?
Click to expand...
Click to collapse
Sure No problem mate.
honeyx said:
Sure No problem mate.
Click to expand...
Click to collapse
nicely done
I have tested this before with rc2 and I have to say battery life was very significantly longer compared to hurtsky 2.5 + QAsR v2.3. However, the white screen issue persisted in 2 of the apps I used the most, namely boat browser and Gmail so I have opted out again. But if you guys don't care about white screen, do give this kernel a try
Yeah, kernel 2.6 is always better battery life... i recomended it
- screen off frequency set to 768 MHz
Click to expand...
Click to collapse
What mean of that ?
is we get trun off the screen it auto lock on 768Mhz ? it's not deepsleep any way CMIIW
hepi_hape said:
Yeah, kernel 2.6 is always better battery life... i recomended it
What mean of that ?
is we get trun off the screen it auto lock on 768Mhz ? it's not deepsleep any way CMIIW
Click to expand...
Click to collapse
This is the max frequency the clock might rise to if the screen is off but for example an app or a service awakes the phone from deepsleep. So it will not drain so much the battery if the phone gets awake for some reason and if you undervolt your cpu, you can reduce the consumption for such a case even more.
This is preset in the Lulzactive governor, which Christopher83 fixed to make this working, so it´s only related to this governor, which is also my default governor.
So when in screenoff the phone only maximum can use CPU clock at 768Mhz
Yeah i get it. .thx for explain it
I think arco might be able to help you fix the white screen. Long back skull kernel experienced the same and acro helped him to fix it.
coolbuy said:
I think arco might be able to help you fix the white screen. Long back skull kernel experienced the same and acro helped him to fix it.
Click to expand...
Click to collapse
Uhm, well I´m not sure this is exactly the same because Keff (Woohooo..) is modding the 3.x kernel for CM10. But thanks for the suggestion. I will aks Keff first to not to bother Arco in the first place. It will be for sure interesting what caused it for him.
Just to clarify some things about the white screen bug. The one I described in my first post is not the real white screen bug, but only what happens to some apps after whiping the cache in CWM Recovery. This can easily be fixed like described above and will not bother you anymore.
The real white screen bug came all of the sudden (without whiping anything before). So for example you opened facebook, everything was fine, but a few minutes later by relaunching facebook you got a white screen. The procedure to get rid of this was the same as I already mentioned but with the difference it happened again after a while.
So well I have had this issue with facebook too in the past, but it´s gone and now even not happening after whiping the cache in CWM Recovery. It´s not gone because I updated the rom (still using RC2), but because facebook updated their app.
Edit:
I already found what you was talking about. It´s called the white noise issue where you get a white screen by turning the screen on, so it´s not the same.
And how is games performance ?
Sent from my GT-I8150 using xda premium
mps42 said:
And how is games performance ?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Mind you: This is battery saving rom. It is meant to have low game performance. It MUST have a lower gaming performance than those v3.0 kernels. If you want gaming, this is not for you.
Doplgangr said:
Mind you: This is battery saving rom. It is meant to have low game performance. It MUST have a lower gaming performance than those v3.0 kernels. If you want gaming, this is not for you.
Click to expand...
Click to collapse
Yes, this is a battery saving kernel, but why should it have low gaming performance? Just because it´s optimized for low consumption in standby and because you can undervolt it? It´s like you were comparing an older Pentium4 against an Intel Atom CPU and saying the Atom must be faster because its newer. Or by comparing a Atom against a 286 CPU and saying the 286 will be faster than the Atom because the Atom is more battery friendly.
Sure, it´s not optimized to get the highest scores in benchmarks, but the games I´m playing once in a while are running totally smooth.
The newer releases of CM9 might be of course faster in games, but not just because of the 3.x kernel, but also because Arcos ocessionaly is updating the GPU drivers.
honeyx said:
Yes, this is a battery saving kernel, but why should it have low gaming performance? Just because it´s optimized for low consumption in standby and because you can undervolt it? It´s like you were comparing an older Pentium4 against an Intel Atom CPU and saying the Atom must be faster because its newer. Or by comparing a Atom against a 286 CPU and saying the 286 will be faster than the Atom because the Atom is more battery friendly.
Sure, it´s not optimized to get the highest scores in benchmarks, but the games I´m playing once in a while are running totally smooth.
The newer releases of CM9 might be of course faster in games, but not just because of the 3.x kernel, but also because Arcos ocessionaly is updating the GPU drivers.
Click to expand...
Click to collapse
Thank you for correcting my ignorance. :laugh: Maybe I'll give the kernel a try and tell more about that
Honeyx, I hope you continue to develop and share this kernel in the future because I decided to start everything over from scratch because of your work here. I love this kernel. I get so much better battery life now. If you would ever consider adding Lionheart in the future, I would be very grateful. Is there any way to add Row or does it require kernel 3? Thanks again!
Sent from my GT-I8150 using xda app-developers app
honeyx said:
Yes, this is a battery saving kernel, but why should it have low gaming performance? Just because it´s optimized for low consumption in standby and because you can undervolt it? It´s like you were comparing an older Pentium4 against an Intel Atom CPU and saying the Atom must be faster because its newer. Or by comparing a Atom against a 286 CPU and saying the 286 will be faster than the Atom because the Atom is more battery friendly.
Sure, it´s not optimized to get the highest scores in benchmarks, but the games I´m playing once in a while are running totally smooth.
The newer releases of CM9 might be of course faster in games, but not just because of the 3.x kernel, but also because Arcos ocessionaly is updating the GPU drivers.
Click to expand...
Click to collapse
Not for hard gaming.....thats sure....if you want battery play with puzzlebubbles
Inviato dal mio GT-I8150 con Tapatalk 2
tebor8 said:
Honeyx, I hope you continue to develop and share this kernel in the future because I decided to start everything over from scratch because of your work here. I love this kernel. I get so much better battery life now. If you would ever consider adding Lionheart in the future, I would be very grateful. Is there any way to add Row or does it require kernel 3? Thanks again!
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I may add some tweaks in the future, but this may take a while till I have some spare time to test them. About adding other governors...well I tested a lot of them but finally decided to use Lulzactive because it was the most battery friendly governor in the one hand and because there is also the Lulzactive app you can use to tweak it to your needs. So for example tweak it that way it behaves like for example Lionheart. I also tested the ROW scheduler but it wasn´t as stable as I presupposed to be. So the best compromise between stability and performance was to use the noop scheduler. It´s nearly as fast as the row but way more stable.
djdu90 said:
Not for hard gaming.....thats sure....if you want battery play with puzzlebubbles
Inviato dal mio GT-I8150 con Tapatalk 2
Click to expand...
Click to collapse
LoL. I´m quite sure with extreme undervolting you can still save some battery juice even while playing action games on this device. Beside this it´s not the CPU or GPU that consumes most, but the display and its backlight LED´s.
it is for battery saving but for me its not good to play with games cuz playing for like 40-60 minutes consume 60% battery ? lol
thats quite alot and might burnt up my battery life.
Dwama said:
it is for battery saving but for me its not good to play with games cuz playing for like 40-60 minutes consume 60% battery ? lol
thats quite alot and might burnt up my battery life.
Click to expand...
Click to collapse
So did you thought it will consume just as much as being in deepsleep????????? The kernel is tweaked to consume less in deepsleep and in daily use but not to consume less in games. Beside this it´s not the CPU nor the GPU that consumes most, but the backlight LEDs in your screen. So even by undervolting and underclocking it will still drain a lot if playing games.
There is no and will not be a magical Kernel that is using witchcraft to reduce the consumption of the LEDs, exept someone compiles you a kernel which turns out the LEDs completely, if you can with a complete dark screen.
honeyx said:
So did you thought it will consume just as much as being in deepsleep????????? The kernel is tweaked to consume less in deepsleep and in daily use but not to consume less in games. Beside this it´s not the CPU nor the GPU that consumes most, but the backlight LEDs in your screen. So even by undervolting and underclocking it will still drain a lot if playing games.
There is no and will not be a magical Kernel that is using witchcraft to reduce the consumption of the LEDs, exept someone compiles you a kernel which turns out the LEDs completely, if you can with a complete dark screen.
Click to expand...
Click to collapse
Im not expecting anything from ur kernel, im glad that u shared ur kernel taht could last longer than arco's stock kernel.
I was just giving up my comments about ur kernel that i have used for 2 months , Not complaining and whining lol.
I am sorry and thanks for sharing ur kernel , keep it up. :fingers-crossed:

[KERNEL] [Nougat] [Voltage Control] Kawori Kernel for Oneplus 2 (r7, 2017/08/16)

Some of you know me from the OOS3 kernel I built, and now I am moving to Nougat and starting working on it.
It mainly majors in keeping a balance between features and stabilities, so I did not add too many features (And I think features like adding 10+ governors is a bad practice), but the features I added is of great use. Some of the features are unique in existing OP2 kernels.
I am sick of those kernels which say it is the smoother than butter or is more powersaving than Nokia 1100, and I do not think that could happen. What I provide is an average kernel with some little tweaks. If you are looking for some specific features, this is not the place for you.
The features list:
Features:
- Catch up with latest Linux upstream 3.10.107
- Catch up with latest CAF source
- Catch up with latest sdcardfs, f2fs, exfat, xpad source
- Add flash and electron governor (both based on interactive, credits to The Flash and frap129)
- Tweaked interactive governor based on CAF MSM8996 branch
- CPU voltage control (The first for MSM8994?)
- Replace H-cube with core_ctl from CAF MSM8996 branch
- Remove powersave, conservative governor
- Add maple, sio, fiops, zen I/O scheduler
- Partly Faux sound control
- Partly thermal control
- KCAL
- Dynamic Sync control
- Wakeblock toggle
- Fingerprint boost tweaks
- Sultanxda's I/O switcher
- TheCrazyLex's memory automatic compaction mechanism
- Various improvements from AOSPA (thanks to TheCrazyLex)
- Various improvements from Sultanxda and myfluxi (The people I really admire)
- Various improvements from CAF
- Fix some ROM's ramdisk bug (why should I fix these?)
- ...
Usages:
Note that LineageOS based roms and other roms use different sysfs nodes for gestures. So I provide 3 versions, just use the one that your rom is based on, otherwise gestures may be broken. For non los based Roms, use other version, if it does not work (such as Pure Nexus), use pn version.
Use kernel adiutor to tweak it.
Source:
https://github.com/aviraxp/ONEPLUS_MSM8994_KAWORI
Credits:
Fist of all, thanks to Linux upstream and CAF. Without them, doing this work is impossible.
Of course, thanks to Lord Boeffla for a good picking source.
Then I want to thank to Sultanxda and myfluxi for the 30+ commits I picked and the guidance he provided. You are the real MVP!
I also want to say thanks to dorimanx, Joe Maples and Franco for the good features they provided.
Support:
Just like many other so-called "developers" for OP2, I do not major in computer science and know little about C. All my codes are written by guessing. Feel free to provide feedbacks, though I may not know how to fix it.
reserved
Nice to see new kernels popping up for the device. Good work @aviraxp
MZO said:
Nice to see new kernels popping up for the device. Good work @aviraxp
Click to expand...
Click to collapse
I am using your Purenexus
aviraxp said:
I am using your Purenexus
Click to expand...
Click to collapse
That's awesome ?
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
chxei said:
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
Click to expand...
Click to collapse
Phone should technically reboot and discard changes before any damage occurs
Sorry if I missed it.. Is this kernel compatible with official lineage weekly?
Sent from my ONEPLUS A3003 using Tapatalk
chxei said:
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
Click to expand...
Click to collapse
I have tested, and think undercoating about 80mV is fine. Lower voltage will make it reboot.
infatality said:
Sorry if I missed it.. Is this kernel compatible with official lineage weekly?
Click to expand...
Click to collapse
Of course
r2 will be soon uploaded , thanks to @MZO for pointing out a different implementation of gestures that I missed.
First of all: nice to see a new kernel of OP2, and I love new features! Good work!
Second: Unfortunatly, flashing this kernel for me kills WiFi on latest Unofficial RR. Had to flash stock boot.img to make it work again. Other than that it seems to work fine.
Defineatly gonna give it a try as my daily driver after WiFi issue is gone.
chxei said:
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
Click to expand...
Click to collapse
No problems for the hardware with undervolting but the system may become a bit unstable
almlex said:
First of all: nice to see a new kernel of OP2, and I love new features! Good work!
Second: Unfortunatly, flashing this kernel for me kills WiFi on latest Unofficial RR. Had to flash stock boot.img to make it work again. Other than that it seems to work fine.
Defineatly gonna give it a try as my daily driver after WiFi issue is gone.
Click to expand...
Click to collapse
I have tested my kernel on omni, du, aex and pn, no issues so far. Some lineage guys also flashed and encounter no issues. But I will try to look at it.
Using this kernel for Almost 12hrs, so far everthing working here with decent battery life.
Cpu cores implementation is the same as in Franco kernel (all cores always online) or different from it?
almlex said:
First of all: nice to see a new kernel of OP2, and I love new features! Good work!
Second: Unfortunatly, flashing this kernel for me kills WiFi on latest Unofficial RR. Had to flash stock boot.img to make it work again. Other than that it seems to work fine.
Defineatly gonna give it a try as my daily driver after WiFi issue is gone.
Click to expand...
Click to collapse
Could you please flash boeffla kernel and report if it works? I suspect it is a toolchain issue.
parasthakur37 said:
Cpu cores implementation is the same as in Franco kernel (all cores always online) or different from it?
Click to expand...
Click to collapse
Different. It is actually same as stock, just built in kernel to keep stability.
aviraxp said:
Different. It is actually same as stock, just built in kernel to keep stability.
Click to expand...
Click to collapse
And I suppose there's no way we can use franco's implementation if we wanted to?
parasthakur37 said:
And I suppose there's no way we can use franco's implementation if we wanted to?
Click to expand...
Click to collapse
I don't know what Franco's implementation is. I don't care either. If you want to keep all cores on, use kernel adiutor and change the min cpus to 4.

how to disable CPU cores

I want to know how to disable CPU cores to save power. It was possible on my nexus 5. but on my nexus 6p and now on my htc 10, I'm not sure if it's possible. I read that it's would need a kernel rewrite or something along those lines.
So does anyone know how to do this? I'm running latest LeeDroid ROM if that helps. thanks :good:
That's what I also wanted to know about the 10.
I had the mind before and there I could run with only one core, if not needed the other three cores. But if I needed power, the 4 cores are running.
It would be great, if there is an option in kernel settings to run all the cores only if they are really needed.
So the 10 is only a battery eater... Especially with sense roms I don't come through the day without charging.
On CM 14 or AOSP the battery is much more better, but with better core management it would be famous.
anyone got any info on this?
less cores doesn't mean better battery life, look at u11, "octa-core" and getting better battery life than 10 and anything else. it's een like if you have less cores, the cores which are online have to do all the work and might end up with locked max freq which will result in heat and more drain. so just keep the core control like it is and maybe just underclock
drago10029 said:
I want to know how to disable CPU cores to save power. It was possible on my nexus 5. but on my nexus 6p and now on my htc 10, I'm not sure if it's possible. I read that it's would need a kernel rewrite or something along those lines.
So does anyone know how to do this? I'm running latest LeeDroid ROM if that helps. thanks :good:
Click to expand...
Click to collapse
It is possible to disable cores with the custom kernel, and I believe force them to remain off at boot, but the HTC 10 uses a big/little cluster CPU setup and disabling cores isn't how you want to conserve power in my humble opinion.
The HTC 10 and some other modern devices uses BIG.little core ARM processor technology.
So the hardware and software is optimized to use all the cores to chase the best battery life and performance. I'm guessing that unless it's very specific usage scenarios, if you manage to force disable the cores with a custom kernel, you'll see both performance and battery life drop.
I would highly recommend installing a custom kernel, and tweaking the kernel settings while letting the hardware make full use of the BIG.little cluster system for efficiency. For high performance, I'd recommend one of the sense based kernel's that uses the HTC PnP Manager system. Something like Flar's ElementalX or TBalden's cleanslate kernel.
For battery efficiency, since you're really wanting to customize things for the best efficiency and battery life, try out the Helix kernel, by zeroinfinity. It's using a technology to optimize control of the processor based on "EAS" technology. EAS stands for "Energy Aware Scheduling" and zeroinfinity has written his "Helix Engine" to control the power profiles and thus power consumption of different apps, and you can customize the profiles to put any other apps you have in the profiles you want them.
This was a very basic and non technical summary, you can find tons of info on the kernels in the OP of each kernel thread. I would recommend making a backup with TWRP and trying both ElementalX and Helix kernels and seeing what works best in your usage scenario, before you start trying to force disable cores.
Here's a quick article I found on google, I'm at work and only briefly skimmed it, so no promises it's any good, but you can google BIG.little procs on Android mobile devices to find more imformation. https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little
CharliesTheMan said:
It is possible to disable cores with the custom kernel, and I believe force them to remain off at boot, but the HTC 10 uses a big/little cluster CPU setup and disabling cores isn't how you want to conserve power in my humble opinion.
The HTC 10 and some other modern devices uses BIG.little core ARM processor technology.
So the hardware and software is optimized to use all the cores to chase the best battery life and performance. I'm guessing that unless it's very specific usage scenarios, if you manage to force disable the cores with a custom kernel, you'll see both performance and battery life drop.
I would highly recommend installing a custom kernel, and tweaking the kernel settings while letting the hardware make full use of the BIG.little cluster system for efficiency. For high performance, I'd recommend one of the sense based kernel's that uses the HTC PnP Manager system. Something like Flar's ElementalX or TBalden's cleanslate kernel.
For battery efficiency, since you're really wanting to customize things for the best efficiency and battery life, try out the Helix kernel, by zeroinfinity. It's using a technology to optimize control of the processor based on "EAS" technology. EAS stands for "Energy Aware Scheduling" and zeroinfinity has written his "Helix Engine" to control the power profiles and thus power consumption of different apps, and you can customize the profiles to put any other apps you have in the profiles you want them.
This was a very basic and non technical summary, you can find tons of info on the kernels in the OP of each kernel thread. I would recommend making a backup with TWRP and trying both ElementalX and Helix kernels and seeing what works best in your usage scenario, before you start trying to force disable cores.
Here's a quick article I found on google, I'm at work and only briefly skimmed it, so no promises it's any good, but you can google BIG.little procs on Android mobile devices to find more imformation. https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little
Click to expand...
Click to collapse
was a good read, thanks! based on the quote from below from that website sounds like the little cores can drive the most battery savings the most .... which is my goal.
The LITTLE cores can be implemented to target lower leakage and a more moderate performance point, independently from the physical implementation of the big cores that are often tuned for higher frequency.
Click to expand...
Click to collapse
and seeing that you were a tester for helix htc 10 kernel, is it designed to with stock based ROM or just any magisk based ROMs? I did see that ASOP is not supported.
drago10029 said:
was a good read, thanks! based on the quote from below from that website sounds like the little cores can drive the most battery savings the most .... which is my goal.
and seeing that you were a tester for helix htc 10 kernel, is it designed to with stock based ROM or just any magisk based ROMs? I did see that ASOP is not supported.
Click to expand...
Click to collapse
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
CharliesTheMan said:
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
magisk version works same as the version which writes to system
CharliesTheMan said:
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Great I also use supersu not magisk, probably same old school thing...also too tough getting things to play nice with magisk IMO. So for supersu do i just install v012 r1 systemless kernel and it should just work w/ leedoird? did you notice any functions on lee droid not working?
also do you underclock? recommend any kernel managers?
drago10029 said:
Great I also use supersu not magisk, probably same old school thing...also too tough getting things to play nice with magisk IMO. So for supersu do i just install v012 r1 systemless kernel and it should just work w/ leedoird? did you notice any functions on lee droid not working?
also do you underclock? recommend any kernel managers?
Click to expand...
Click to collapse
It's version 17, you'll download it from this post https://forum.xda-developers.com/showpost.php?p=73068312&postcount=1216 , sorry that link you had shouldn't be there, but systemless is the magisk version but now there's only one version, and the Aroma installer will let you choose the normal non-magisk version.
In the installer, there's a question that asks about installing custom scripts, I use the @ZeroInfinity script, the one from @roger81 and @TotallyAnxious are good too so you can't really go wrong, but I recommend starting with zero's, and you can reflash to experiment once you get going good with it. Rogers is great for battery life but his is a little more custom and extreme, which is why I'd start.
I use EXKM kernel manager, but I really recommend not changing many settings at first. Definitely leave the governor default with this kernel. I would run it like it comes out of the box, and see how your apps and battery life goes, and if you have apps causing a lot of drainage, maybe add them to the helix engine profiles before you start changing clock speeds.
You'll notice with EXKM the core frequencies reported in real time will look different from how it looks with a stock based kernel, but don't let that scare you.
My only other recommendation is if you use any other power saving apps like greenify or doze (I don't use any of them personally but some do) I would first get used to the kernel without them, so you kind of have a better idea of baseline.
CharliesTheMan said:
It's version 17, you'll download it from this post https://forum.xda-developers.com/showpost.php?p=73068312&postcount=1216 , sorry that link you had shouldn't be there, but systemless is the magisk version but now there's only one version, and the Aroma installer will let you choose the normal non-magisk version.
In the installer, there's a question that asks about installing custom scripts, I use the @ZeroInfinity script, the one from @roger81 and @TotallyAnxious are good too so you can't really go wrong, but I recommend starting with zero's, and you can reflash to experiment once you get going good with it. Rogers is great for battery life but his is a little more custom and extreme, which is why I'd start.
I use EXKM kernel manager, but I really recommend not changing many settings at first. Definitely leave the governor default with this kernel. I would run it like it comes out of the box, and see how your apps and battery life goes, and if you have apps causing a lot of drainage, maybe add them to the helix engine profiles before you start changing clock speeds.
You'll notice with EXKM the core frequencies reported in real time will look different from how it looks with a stock based kernel, but don't let that scare you.
My only other recommendation is if you use any other power saving apps like greenify or doze (I don't use any of them personally but some do) I would first get used to the kernel without them, so you kind of have a better idea of baseline.
Click to expand...
Click to collapse
Bonus points for being the least confusing AROMA installer I have used! and I used zero's as well. thanks for all your help! and one last thing.. isn't doze built into android nougat? or am I highly misinformed.
drago10029 said:
Bonus points for being the least confusing AROMA installer I have used! and I used zero's as well. thanks for all your help! and one last thing.. isn't doze built into android nougat? or am I highly misinformed.
Click to expand...
Click to collapse
It is you're correct, but there's a lot of "super doze" and dozingest doze around" sort of mods and tweaks people use, it's the extra modified stuff I would avoid for now, until baseline is established. However once you get things ironed out, @RogerF81 (if I spelled that Right) has tons of good info on further tweaking. He once tweaked his battery life to something like 7 or 8 hours screen on time with the Helix EAS kernel. That's just showing off.
Glad you like the Aroma installer, it nearly killed the poor dev trying to get it set up when he first started implementing it, he still probably throws keyboards if I ask for a black theme lol.
Sent from my HTC 10 using Tapatalk

Categories

Resources