Develop Bugs

Insane battery life and throttling the Companion Core (I think).

This doesn't represent real-world use. This is an extreme example of how long you can make the battery last by severely throttling the CPU!
I posted another thread about the method used to apply this mod (you can find it here) but I made this thread to concentrate purely on the side effect of it, which is insanely good battery life. Firstly, I'd just like to make this point clear: I would not recommend doing this mod. It makes your device get pretty screwy and renders it fairly unusable. It needs further development before it can be useful.
Yes, this mod gives you absolutely incredible battery life but it only does so by severely limiting the CPU speed and limiting the CPU to a single core (It might even just run off the companion core and nothing else. I've had conflicting results) which makes the phone insanely laggy. I believe, however, that this throttling could be made less aggressive and then toggled on and off at will. From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life (which is already pretty amazing). This isn't definite though and needs more tests
Anyway, less chit-chat, here are my results:
{
"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"
}
That's right, 12 hours and 35 minutes screen-on time!
It would probably last about 4 or 5 days if the screen was off!
ROM: Android Revolution HD
Kernel: stock ARHD kernel
Screen on lowest brightness
No other modifications (apart from the throttling mod)

"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone

SartoriXX said:
"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone
Click to expand...
Click to collapse

If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS

Might aswell do that!

I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.

Meltus said:
I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.
Click to expand...
Click to collapse
I think it sounds awesome and happy to see people like you try to developing the power consumption!
Sent from my HTC One X using Tapatalk 2

sure beats my battery life with only 30 minutes screen on time

ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse

ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse
Comments like that are a complete waste, if they are on to something you should be more encouraging.

Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get

I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.

lamenramen said:
I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.
Click to expand...
Click to collapse
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA

Meltus said:
Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get
Click to expand...
Click to collapse
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium

Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.

punyategar said:
Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.
Click to expand...
Click to collapse
The hox has 5 cores, 4 main cores and 1 super low power core.
What this does is turn off the main cores and run on the super low power core which is great for battery life but it only goes to 500 MHz and in respect to CPUs is slower at processing stuff then almost all CPUs price you pay for power saving.
Sent from my HTC One X using xda premium

Applaud your investigations, so many Haters on this forum!
This phone has masses of potential for some awesome custom Roms (and even a decent official Rom if HTC ever sort themselves out!). Battery life pretty much whole day for me but improvements always welcome.

xchasa said:
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
He is probably talking screen-on time. 4-5 Hours screentime is great, unfortunately you do not fall under the average hours of screen-on time. The average time would be anywhere between 2 and a half to 3 and a half hours.
Which in my opinion is nothing special, admittedly, it does get me through a day but hey! I wouldn't mind having more screen-on time. If 4-5 hours screen on time was the average than you wouldn't see many if anyone complaining at all.
Good day!

treebill said:
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium
Click to expand...
Click to collapse
Ah, that makes more sense
So, were you able to get the 'throttle' file to stick to anything but '1'?
I noticed the throttle_table and tried to use a few of them but they all just defaulted to 1.
It's a shame the 'throttle_table' file isn't editable too, that would make modifying it so much easier!
My first test failed miserably I'm afraid, I forgot to turn off an alarm and it rang out for about 3 hours and then ran out of battery! I'll remember to turn off the alarm next time

Bloody good effort. Despite the idiotic comments from those who clearly haven't grasped the idea behind this, it's impressive homework.
Research like this can only help improve custom-ROM's, which is kinda the point of XDA Dev's, no?
I think some people should focus on the comments section of sites like Engadget, where their funny pictures will be much better suited.

CPU management idea for CPU control

I've been wondering is it possible to govern the CPU based on what app or process it is doing, surely by managing CPU in this way could maximize battery life and possibly improve performance.
For instance so your on Facebook or emails at present they say it should use the 5th power core but this is not the case surely Facebook app only requires about 500-700mhz to run so limit CPU load to 700mhz whilst Facebook is in the foreground process.
Background processes should run on a separate core than that of the foreground process.
If your playing a simple low end game than that should be limited to 2cores to reduce hogging of CPU and reduce lag
High-end games run the 4cores and background processes run on 5th core to reduce lag ingame.
Is this a good idea or am I missing some points
sent from a powerhouse HTC one X quad core nvidia beast

Yes it's possible and there's already an app for that. Try Setcpu. Allows you to set individual settings for individual apps. Good app to have. Hope this is what you're looking for.
Sent from my HTC One X using xda premium

grinder19 said:
I've been wondering is it possible to govern the CPU based on what app or process it is doing, surely by managing CPU in this way could maximize battery life and possibly improve performance.
For instance so your on Facebook or emails at present they say it should use the 5th power core but this is not the case surely Facebook app only requires about 500-700mhz to run so limit CPU load to 700mhz whilst Facebook is in the foreground process.
Background processes should run on a separate core than that of the foreground process.
If your playing a simple low end game than that should be limited to 2cores to reduce hogging of CPU and reduce lag
High-end games run the 4cores and background processes run on 5th core to reduce lag ingame.
Is this a good idea or am I missing some points
sent from a powerhouse HTC one X quad core nvidia beast
Click to expand...
Click to collapse
I think you're missing the point a little bit, the CPU automatically chooses how many cores and when and how to use them based upon what you are doing on the phone at any given time. (Or so I believe anyway, I may be wrong)...
You can set the clock frequency with SetCPU and choose individual Apps to have certain frequencies, but as the +1 core is hidden you can't choose to set that manually anyway, so a bit pointless.

The-Last-Hylian said:
I think you're missing the point a little bit, the CPU automatically chooses how many cores and when and how to use them based upon what you are doing on the phone at any given time. (Or so I believe anyway, I may be wrong)...
You can set the clock frequency with SetCPU and choose individual Apps to have certain frequencies, but as the +1 core is hidden you can't choose to set that manually anyway, so a bit pointless.
Click to expand...
Click to collapse
I'm aware the CPU automatically chooses but I believe it's trigger sometimes and it doesn't need to be so there should be a limiter that you can set for individual apps. Setcpu doesn't let you choose settings for individual apps but rather set limits based on phone state
sent from a powerhouse HTC one X quad core nvidia beast

grinder19 said:
I'm aware the CPU automatically chooses but I believe it's trigger sometimes and it doesn't need to be so there should be a limiter that you can set for individual apps. Setcpu doesn't let you choose settings for individual apps but rather set limits based on phone state
sent from a powerhouse HTC one X quad core nvidia beast
Click to expand...
Click to collapse
I stand corrected lol Setcpu does allow it doesn't seem to work I limited gmail to 760mhz to test and still used max load on 2cores
sent from a powerhouse HTC one X quad core nvidia beast

{
"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"
}
sent from a powerhouse HTC one X quad core nvidia beast

It's because we can't yet let the CPU uc by that much. Only 1400mhz works on faux. Any lower than that and it just goes back to 1.5ghz. I'm still trying to find a way to underclock it to less than 1400mhz.
Sent from my HTC One X using xda premium

timlambo said:
It's because we can't yet let the CPU uc by that much. Only 1400mhz works on faux. Any lower than that and it just goes back to 1.5ghz. I'm still trying to find a way to underclock it to less than 1400mhz.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
If they had released the base code for the processor it would be a lot easier to alter the clock settings
sent from a powerhouse HTC one X quad core nvidia beast

Hi
It is unlikely to really save much power by limiting the cores on a per application basis, the manufacturer has already spent millions on R&D designing the chip and drivers and optimising it as much as possible, why would a free/few dollar App be any better? The reason you are unlikely to see any benefit is that if you slow the core down, yes it will use less power, but it also takes longer to do the work, so uses less power but over a longer period of time, end result is a slower phone for next to no benefit.
Regards
Phil

PhilipL said:
Hi
It is unlikely to really save much power by limiting the cores on a per application basis, the manufacturer has already spent millions on R&D designing the chip and drivers and optimising it as much as possible, why would a free/few dollar App be any better? The reason you are unlikely to see any benefit is that if you slow the core down, yes it will use less power, but it also takes longer to do the work, so uses less power but over a longer period of time, end result is a slower phone for next to no benefit.
Regards
Phil
Click to expand...
Click to collapse
You are right in some way. But if we can lower the clock below 1400mhz and it sticks, we can modify it to increase quicker and decrease slower. This way we will do the same job in more or less the same time with less power. But to keep an app open in the background like setcpu can actually take more battery.
Sent from my HTC One X using xda premium

timlambo said:
You are right in some way. But if we can lower the clock below 1400mhz and it sticks, we can modify it to increase quicker and decrease slower. This way we will do the same job in more or less the same time with less power. But to keep an app open in the background like setcpu can actually take more battery.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Doesn't have to be an app it cud be jus messing with the code somewhere it's power optimisation that's needed as Facebook works on a single core processor phone e.g my old xperia x10 without any sign of a stutter so why does it need 3or4 cores running exactly the same thing on this phone. Google spends millions on android but it's still open source as they even admit they are not perfect.
sent from a powerhouse HTC one X quad core nvidia beast

Comments on p6 huawei ascend after a day of use

Yesterday I bought a Huawei ascend p6 for my wife. Even when holding it in hand, I feel like its design. After a day of use, I feel quite disappointed in its performance. When running the game like candy crush, subway surf, ... I find it does not run smoothly, or say exactly shocked. I wondered if I run the game require higher configuration will how?
According to you, is caused by the configuration of the machine or the rom? Is there any way to solve this problem?

U can try to run it in performance mode.
Sent from my P6-U06 using Tapatalk 2
{
"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"
}

The performance mode just reduces the resolution...

try
try rooting and installing clockworkmod and then flash a rom or install cynogen mod or install game booster on playstore
good luck
hit the thanks button:cyclops:

savio_mascarenhas said:
try rooting and installing clockworkmod and then flash a rom or install cynogen mod or install game booster on playstore
good luck
hit the thanks button:cyclops:
Click to expand...
Click to collapse
there is no clockworkmod until now ...
But which firmware does your phne have?
B104 is not very smoothy, try the official B107 if it is ... good luck

i dont
i dont have a ascend p6 so try to flash a new rom but becareful if you need further help i can help you
hit the thanks button please
good luck tell me if you need help
i have a huawei idoes x5:highfive:

i am an android developer
:laugh:I come from china.now i am in ShenZhen.I have already competly made the customer recovery for Huawei P6.I will upload it soon .Hope you gays enjoy it.

zhenaguo said:
:laugh:I come from china.now i am in ShenZhen.I have already competly made the customer recovery for Huawei P6.I will upload it soon .Hope you gays enjoy it.
Click to expand...
Click to collapse

solve your problem
The cpu and GPU locked in a certain frequency power can be achieved not so serious and fluent game approach.
The first machine to ROOT then RE Manager to set inside the file!
1. Open sys-devices-system-cpu-cpu0-cpufreq-cpuinfo_block_freq, use a text editor to open, modify the value of 600,000 or 800,000 or 700,000 are cpu frequency is locked, save and exit after completion of editing,
2. Locate scaling_cpu_lock_nun, a method using phase inside the 0 modified to 4. It is locked cpu cores. Save and exit editing can! In power management policy settings in a super-power standby.
GPU in accordance with slim post to unlock! But I set 480000 360000.
Heat is also not so great to play the game is very smooth! Power consumption is not serious enough for everyday use heat is also better!
I charge 100% after setting the screen brightness is not open to the minimum WIFI playing whitewater boats two effects 30 minutes of high power consumption 23% is power! But look at the beep beep miles 720 miles to see 24 minutes of animation power at about 7%! Several times hovering at about 7%.
After rebooting modify things will revert to re-edit

zhenaguo said:
The cpu and GPU locked in a certain frequency power can be achieved not so serious and fluent game approach.
The first machine to ROOT then RE Manager to set inside the file!
1. Open sys-devices-system-cpu-cpu0-cpufreq-cpuinfo_block_freq, use a text editor to open, modify the value of 600,000 or 800,000 or 700,000 are cpu frequency is locked, save and exit after completion of editing,
2. Locate scaling_cpu_lock_nun, a method using phase inside the 0 modified to 4. It is locked cpu cores. Save and exit editing can! In power management policy settings in a super-power standby.
GPU in accordance with slim post to unlock! But I set 480000 360000.
Heat is also not so great to play the game is very smooth! Power consumption is not serious enough for everyday use heat is also better!
I charge 100% after setting the screen brightness is not open to the minimum WIFI playing whitewater boats two effects 30 minutes of high power consumption 23% is power! But look at the beep beep miles 720 miles to see 24 minutes of animation power at about 7%! Several times hovering at about 7%.
After rebooting modify things will revert to re-edit
Click to expand...
Click to collapse
Hi there, im not very code technical, From what I can see, have you made the phone not get as hot and gave it better proformance, the only thing thats putting me off buying this phone is that even though it has a snapdragon S4 pro it isnt as good as the Nexus 4 which is cheaper and that it gets way to hot ( someone had a screen shot of the phone getting so hot that asked to close apps )
Many thanks

JackHanAnLG said:
Hi there, im not very code technical, From what I can see, have you made the phone not get as hot and gave it better proformance, the only thing thats putting me off buying this phone is that even though it has a snapdragon S4 pro it isnt as good as the Nexus 4 which is cheaper and that it gets way to hot ( someone had a screen shot of the phone getting so hot that asked to close apps )
Many thanks
Click to expand...
Click to collapse
well... Based on what I know about this phone, the CPU is not a Snapdragon S4 pro but a K3V2E developed by Huawei itself. That might explains the performance issue. Huawei locked the CPU frequency and GPU frequency for power saving reasons, but it locked it too much.

beodenls said:
Yesterday I bought a Huawei ascend p6 for my wife. Even when holding it in hand, I feel like its design. After a day of use, I feel quite disappointed in its performance. When running the game like candy crush, subway surf, ... I find it does not run smoothly, or say exactly shocked. I wondered if I run the game require higher configuration will how?
According to you, is caused by the configuration of the machine or the rom? Is there any way to solve this problem?
Click to expand...
Click to collapse
Yes the solution is go to settings>power manager>select normal
Then go to manage apps>subway surfers>enable the perfomance mode
Hope this helps and tell the results
Sent from my HUAWEI P6-U06 using xda premium

yfnew said:
well... Based on what I know about this phone, the CPU is not a Snapdragon S4 pro but a K3V2E developed by Huawei itself. That might explains the performance issue. Huawei locked the CPU frequency and GPU frequency for power saving reasons, but it locked it too much.
Click to expand...
Click to collapse
No way! How could they lie? Do you think its a Cortex A7? I only ask because the battery life seems pretty good and as far as i know 1.5ghz is the max an A7 can go, also if the performance isnt great, that would be why?

JackHanAnLG said:
No way! How could they lie? Do you think its a Cortex A7? I only ask because the battery life seems pretty good and as far as i know 1.5ghz is the max an A7 can go, also if the performance isnt great, that would be why?
Click to expand...
Click to collapse
Yes, you are right ! The cpu's are cortex A7.

any idea what GPU it has? any info about it?

Immersion. 16, and we got Cortex A9, not 7
Sent from my HUAWEI P6-U06 using xda app-developers app

S34Qu4K3 said:
Immersion. 16, and we got Cortex A9, not 7
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
never heart of that gpu....
no one has any specs list about it?
yeah A9, gsmarena sayed it.
loooks like a cute phone

Hi
Im satisfied with my new P6, but honestly the battery life is very bad. My phone 's been 5 hours on battery, and has 50%. I have disabled Google services, wifi, gps and cleaned background apps. I dont even keep my screen brightness high !
I also get sometimes mobile data lost, i've 3g/h on statusbar, but data is not moving. Going to airplane mode and back makes it work again. This happens few times a day.
I have B106, the build which came with the phone. Should i update to B107 or something else? Im in Finland with Elisa / Saunalahti network and i've heard about connection issues on B107. Is it still better than 106, or is there some other build that i should try?
And have you any info about coming versions from Huawei? Thanks alot

We have in Germany by default B104 and the B107 is much better ... at the moment I have a beta B111 on my phone and that is still better than B107 ... I think there will be better roms soon.
Hope that there will be custom rom possible soon, the test possibility is much better then ...

Find out whats causing the drain. Go to settings-battery(asetukset-akku) and see if there is a program misbehaving. Stopwatch prevents the phone from going to deep sleep and therefore drains lots of power even when the screens off, other programs might do it aswell.
If you get 4-7 hours of screen on time id say that its pretty normal, although i do not play any games that consume loads of power. And i think browsing with wifi consumes less power than mobile data.
Ill try to take some battery stats with syncs, gps and google now on. So youll have something to compare with.

[KERNEL][Stock 224/253][Z5/Z5 DSDS][6.0.x]OM5Z Kernel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am NOT resposible for any damage done to your device, your neighbor, or any other things you like/hate.​
Introduction:
@oshmoun and I were in need for a custom stock kernel to mess with. Since all the available Options were not fitting our needs, or gave us bad experience on some aspects, and we knew about Zombie Kernel from Tom, we decided to start working on that. So I brought up support for the Z5, we ported Kexec to it, updated it to 224 and added various things. Since the kernel gave us very good experiences, we decided to make it accessible to the public.
About:
This Kernel is based on @Tommy-Geenexus Zombie Kernel. He was ok with us continuing/porting his projects, so oshmoun, and me started to create the "oshmoun Myself5 Zombie Kernel" aka OM5Z Kernel.
Features and Commit History:
Check 2nd Post!
Installation Instruction:
THIS DOES ONLY WORK ON UNLOCKED BOOTLOADER!
You can either flash the provided boot.img via fastboot, or flash the zip in recovery.
Additional Information:
The Kernel is underclocked by default. Both Cluster are underclocked to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements. However, due to public demand, V2 features the ability to disable the underclock (in case you need to make some baked Eggs real quick, whatever). All you need to do is run this code after boot (Kernel Adiutor has the abilty to execute scripts at startup, just a reminder).
Code:
echo "0:4294967295 1:4294967295 2:4294967295 3:4294967295 4:4294967295 5:4294967295 6:4294967295 7:4294967295" > /sys/module/msm_performance/parameters/max_cpu_freq
What it effectively does, is resetting the max clock limit for each core to the default (unset) values, allowing you to set whatever frequency (from the ones available ofc) you want.
Download:
For Dual SIM phones download the sumire_dsds Versions.
OM5Z Kernel (Release Versions)
https://dl.myself5.de
OM5Z Kernel (Testing Versions)
https://testing.myself5.de
Thanks/Credits:
Tommy-Geenexus - You can guess why
oshmoun - for obvious reasons
FreeXperia Team (especially Jerpelea) - for too many things!
CarbonRom Team - for too many things!
phaseburn - for being a good friend and helping me with almost everything !
infected_ - for help with SM!
My Big Brother Eric - for helping me keeping focused on Development!
My friend Silas - for letting me use his servers and being awesome!
If I forgot you, please tell me.
If you think we deserve a donation, I won't stop you
To Donate to Tommy-Geenexus:
To Donate to me:
To Donate to oshmoun:
PM Spam him to create a PayPal Donation system, he doens't have one yet
Thanks a lot to those who have donated!​
Additional Information:
As you might have seen in my MultiROM Thread, some stock kernels require different Recovery Images than AOSP Kernels. We set an end too this, and fixed init_sony, rather than using some very outdated software which somehow works. This means, you might need to use a different recovery with this kernel if you're currently on a "stock" recovery. We're hoping that other stock kernel devs adapt our solution, so we can set an end to the old scripts.
XDA:DevDB Information
OM5Z Kernel, Kernel for the Sony Xperia Z5
Contributors
Myself5, oshmoun, Tommy-Geenexus
Source Code: https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z
Kernel Special Features:
Version Information
Status: Stable
Created 2016-06-25
Last Updated 2016-07-16

Reserved
Latest Version: V2.0
Changelog:
Version 1:
Add kexec-hardboot
ramdisk: use init_sony, no outdated bootrec scripts
ramdisk: fix USB on Stock when using MultiROM
Remove broken Sony MHL driver
Update to 32.2.A.0.224
Merge caf/LA.BF64.1.2.2_rb4.40
Various CVE Fixes
Initial Z5 and Z5C bringup, based on Zombie Kernel with these features
Bug fixes for touchscreen / fingerprint / scheduler drivers
Stripped unnecessary debug nodes, legacy code and disabled KSM
Turquoise LED when EOC is reached (when battery is fully charged)
CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
Calibrated JDI Novatek Panel to 6500K Color Temperature and 2.2 Gamma
Tomtom-Codec Digital Speaker-, Mic- and Cam-mic-Control
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Version 2:
Ability to disable the underclock (added on public demand) See OP for instructions
Removed TomTom Audio
Update to 32.2.A.0.253
Update init_sony
include DRM Fix by @tobias.waldvogel
Add support for sumire_dsds (E6633 and E6683). Thanks to @tOrNadO™ for testing
For a detailed Changelog, check the Github Commit history:
https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z/commits/

sounds cool! I'll give it a try.

Does it works for z5 dual?
Brilliant work anyway!

is it possible for you to make a build for Z3+/Z4 ? as both Z5 and Z4/Z3+ are similar mostly and Zach's kernel is ported similarly.
Thanks

JerryLaiHMmmmmm said:
Does it works for z5 dual?
Brilliant work anyway!
Click to expand...
Click to collapse
Yes it should. I was not able to test it, but we picked necessary code for compatibility with both devices.
GryTEcHoG said:
is it possible for you to make a build for Z3+/Z4 ? as both Z5 and Z4/Z3+ are similar mostly and Zach's kernel is ported similarly.
Thanks
Click to expand...
Click to collapse
It would be possible, but I don't want to do that. I don't have a Z3+/Z4, so I would not be able to test things prior to releasing it. Thats not what I want to do. Even with testers, I couldn't guarantee on my own that things work, and thats not ok for me.
Sent from my E6653 using Tapatalk

Is ıt work on E6603?
Thanks for kernel

Lptrex9 said:
Is ıt work on E6603?
Thanks for kernel
Click to expand...
Click to collapse
It should workflawless with all Z5 variants (E6603, E6653, E6633, E6683), I am only able to test it on a E6653 though, so please report if it doesnt work on the E6603.

Hi,
I've just proved that it works on the Dual model (e6683)
And it should work on E6633 as well.
Thanks for your hard work!
EDIT:
Oh……… No SD card detection.

JerryLaiHMmmmmm said:
Hi,
I've just proved that it works on the Dual model (e6683)
And it should work on E6633 as well.
Thanks for your hard work!
EDIT:
Oh……… No SD card detection.
Click to expand...
Click to collapse
Needs to be compiled separately for the Dual devices,
otherwise the microSD detection is toast

JerryLaiHMmmmmm said:
Hi,
I've just proved that it works on the Dual model (e6683)
And it should work on E6633 as well.
Thanks for your hard work!
EDIT:
Oh……… No SD card detection.
Click to expand...
Click to collapse
Do me a favour and test if V1.1 here (https://testing.myself5.de/sumire/OM5Z Kernel/) works please.
Thanks in advance.

Myself5 said:
Do me a favour and test if V1.1 here (https://testing.myself5.de/sumire/OM5Z Kernel/) works please.
Thanks in advance.
Click to expand...
Click to collapse
Good to see some development going on for the device..

What recovery should I use for this kernel?

Myself5 said:
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Click to expand...
Click to collapse
I want a powerful device, so I'll wait until you remove this restriction, I even want a OC kernel as Zach's one did. I heard about your kernel a lot but didn't have chance to try it, on Z2 I tried yours but got Android is upgrading on every booting. But, I don't know what your kernel's aim to? Zach's one is aiming to as close stock as possible with fixing and improvement.

RyTekk said:
I want a powerful device, so I'll wait until you remove this restriction, I even want a OC kernel as Zach's one did. I heard about your kernel a lot but didn't have chance to try it, on Z2 I tried yours but got Android is upgrading on every booting. But, I don't know what your kernel's aim to? Zach's one is aiming to as close stock as possible with fixing and improvement.
Click to expand...
Click to collapse
This kernel aims for the best performance and temperatures on the Z5. Its known, that the Z5 sometimes has heating issues, or turns off 4k Recording after short times. I needed to abort my 4k testings after a straight 40min of recording, not because my phone got hot, but because I was running out of space. The "extra" performance other kernels promise you, will result into heat and therefore thermal throttling, which ends up the same as Underclocking it slightly from the beginning, if not worse.
Also: @infected_ was one of the early adopters of my Kernel (before the release, he gave feedback and stuff). After the release, he asked me since when there is a Underclock as he never really experienced any performance drawbacks, so he didnt notice that there actually IS a underclock. (Let running Benchmarks aside here, we all know thats just for showing off).
GPU is running at full speeds btw, so no drawbacks in games whatsoever.
V2 (which will be completely reworked on Top of Toms reworked Kernel) might as well allow setting the default clock with tools like Kernel Auditor, but will most likely be underclocked by default again.
Sent from my E6653 using Tapatalk

RyTekk said:
I want a powerful device, so I'll wait until you remove this restriction, I even want a OC kernel as Zach's one did. I heard about your kernel a lot but didn't have chance to try it, on Z2 I tried yours but got Android is upgrading on every booting. But, I don't know what your kernel's aim to? Zach's one is aiming to as close stock as possible with fixing and improvement.
Click to expand...
Click to collapse
Myself5 said:
This kernel aims for the best performance and temperatures on the Z5. Its known, that the Z5 sometimes has heating issues, or turns off 4k Recording after short times. I needed to abort my 4k testings after a straight 40min of recording, not because my phone got hot, but because I was running out of space. The "extra" performance other kernels promise you, will result into heat and therefore thermal throttling, which ends up the same as Underclocking it slightly from the beginning, if not worse.
Also: @infected_ was one of the early adopters of my Kernel (before the release, he gave feedback and stuff). After the release, he asked me since when there is a Underclock as he never really experienced any performance drawbacks, so he didnt notice that there actually IS a underclock. (Let running Benchmarks aside here, we all know thats just for showing off).
GPU is running at full speeds btw, so no drawbacks in games whatsoever.
V2 (which will be completely reworked on Top of Toms reworked Kernel) might as well allow setting the default clock with tools like Kernel Auditor, but will most likely be underclocked by default again.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
ill subscribe what @Myself5 said.
your device doesn't stop being "powerful"... does a snapdragon 810, 8 core device that reaches 1.3Ghz on the LITTLE cores, and 1.5Ghz on the big cores, stop being powerful?
image it as a car. let's say the "car engine" was adjusted for the best air intake/fuel intake/thermal handling.
you don't notice the underclock, the phone is fast, fluid, responsive, and excellent on the thermals.
make a test, see how much time you can record 4K (one of the most demanding and heating stuff on the phone) with stock kernel.
then try OM5Z kernel, and compare.
regards.
ps: you can even make a stress test with antutu (15m), and compare the thermal/core shutdown/frequency throttling, of both kernels.

Myself5 said:
This kernel aims for the best performance and temperatures on the Z5. Its known, that the Z5 sometimes has heating issues, or turns off 4k Recording after short times. I needed to abort my 4k testings after a straight 40min of recording, not because my phone got hot, but because I was running out of space. The "extra" performance other kernels promise you, will result into heat and therefore thermal throttling, which ends up the same as Underclocking it slightly from the beginning, if not worse.
Also: @infected_ was one of the early adopters of my Kernel (before the release, he gave feedback and stuff). After the release, he asked me since when there is a Underclock as he never really experienced any performance drawbacks, so he didnt notice that there actually IS a underclock. (Let running Benchmarks aside here, we all know thats just for showing off).
GPU is running at full speeds btw, so no drawbacks in games whatsoever.
V2 (which will be completely reworked on Top of Toms reworked Kernel) might as well allow setting the default clock with tools like Kernel Auditor, but will most likely be underclocked by default again.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
infected_ said:
ill subscribe what @Myself5 said.
your device doesn't stop being "powerful"... does a snapdragon 810, 8 core device that reaches 1.3Ghz on the LITTLE cores, and 1.5Ghz on the big cores, stop being powerful?
image it as a car. let's say the "car engine" was adjusted for the best air intake/fuel intake/thermal handling.
you don't notice the underclock, the phone is fast, fluid, responsive, and excellent on the thermals.
make a test, see how much time you can record 4K (one of the most demanding and heating stuff on the phone) with stock kernel.
then try OM5Z kernel, and compare.
regards.
ps: you can even make a stress test with antutu (15m), and compare the thermal/core shutdown/frequency throttling, of both kernels.
Click to expand...
Click to collapse
Actually I don't stress my phone a lot, but I need all tasks to be done in the fastest way, about 4K recording, I don't use it since I don't have a 4K display, but I can handle it by my custom thermal-engine (you can find it in General section). I belong to what kind of people, you know, instead of I buy a normal motor for daily and a powerful motor for long trips, I'll just buy a powerful one for both, that's me , I always choose a higher requirement thing for a lower task that it's required.

@Myself5 @infected_
I use this mod by Rytekk now for a while, and I have to say, sometimes the phone feels a bit warm indeed but I'm monitoring GPU and cpu temperature in statusbar with cooltool and it barely exceeds 65°c on intensive jobs like 4K recording and timeshift video.
(btw, aside from that, it seems timeshift video heat up the phone much faster than 4K)
So when our chip is spec'd up to 85°c as max emmc temperature, 65°c is nothing.
The phone might feel hot or warm but it's the heatsinking doing its job.
If it would stay cool on timeshift video it'll probably shows the message to close the app in no-time because it can't dissipate the heat.
In that case, the thermal paste between the emmc and the heatsinking isn't applied correctly or doesn't make enough contact.
But if it's applied correctly, and emmc runs up to 65°c, ofcourse the phone feels warm.
Imagine a boil of water, 60°c, put your hand in it.
Now my second point, I was monitoring temperature for a few weeks and what I noticed is the GPU heats up faster than cpu0 and Cpu1 almost every time, on every task.
So you might want to throttle GPU if u like lower temperatures but in my opinion, when emmc doesn't exceed 65°c, there's nothing to worry about.
Cheers!
Sent from my E6653 using XDA-Developers mobile app

What RyTekk efficiently did, was adjusting the thermal throttling curve. This at no point however means, that the phone will always stay at the stock frequency. Effectively it will probably result in the same throttling as Underclocking the device does.
I know the whish of having the fastest things,my build PC has a i7 5820k overclocked to 4GHz, BUT that one also has a proper cooling solution, and is not known across the world as a easy overheating CPU. Until you show me a usecase, where you can clearly experience performance drawbacks (other than Benchmarks) I wont accept the fact that you really "need" 2GHz on the S810.
Sent from my E6653 using Tapatalk

Hmm, I can't show you so you just do whatever you think it's right, your restriction is just "masking" device that it's at 52 Celcius (JK :laugh: ). Btw, I pushed request, hope you would take a look on it, and also fix SD card not detected on dsds devices.

[KERNEL][6th Dec] Helix Kernel (Nougat) v001

{
"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"
}
...Presents...
Helix Kernel
Features:
- Based on 2.28.617.8 HTC source code
- Various patches/fixes (look in source commits)
- Big cluster overclocked to 2.34GHz + GPU overclocked to 652MHz
- Sched tweaks (task migration tweaks that aim to achieve good performance while maintaining battery life)
Click to expand...
Click to collapse
AFTER INSTALLING:
Because pnpmgr overwrites some of my sched tweaks, 3 tuneables will have to be applied manually via EX Kernel Manager app.
You will have to go into the CPU section then scroll down and tap on "Advanced options" where you see some tunable options. Here is what you will have to change:
sched_upmigrate = 95
sched_upmigrate_min_nice = 0
sched_restrict_cluster_spill = 1
sched_downmigrate = 90
sched_small_wakee_task_load = 5
sched_big_waker_task_load = 30
sched_enable_thread_grouping = 1
AND MAKE SURE TO ENABLE APPLY ON BOOT OPTION AT THE TOP!
Additionally, this kernel works best with ivicask's pnpmgr mode on BALANCED MODE!
Click to expand...
Click to collapse
DOWNLOAD v001
MIRROR
I have not tested this on US variants of the HTC 10, nor on any AOSP-based ROMs so please make a backup of your boot.img before flashing!
​SOURCE: https://github.com/ZeroInfinityXDA/HelixKernel_Nougat

Oh yeah, can't wait to get er done. And reserved.
Sent from my HTC 10 using Tapatalk

Whoop... Here we go..
Great kernel dude....

I have not tested this on other US variants of the HTC 10, so please make a backup before flashing!
Sent from my HTC 10 using XDA Labs

Here I go too
Subscribed to the thread already hahaha

Install has been great on US Unlocked variant for me, I'm on Viper 3.5.0 on the ATT network, and so far it's running good.
Sent from my HTC 10 using Tapatalk

HElix FTw whoop whoop

- Big cluster overclocked to 2.34GHz + GPU overclocked to 652MHz like the maximum freq of S821 chip
- Sched tweaks (task migration tweaks that aim to achieve good performance while maintaining battery life)
Click to expand...
Click to collapse
No further overclock on the small cores? Does it get unstable that fast?
And about the Scheduler tweaks, pnpmgr likes to take tasks off the big cores as soon as the phone gets a little bit too hot. Are your tweaks mainly for cold/light usage or work better when the phone is hot/throttling?

Haldi4803 said:
No further overclock on the small cores? Does it get unstable that fast?
And about the Scheduler tweaks, pnpmgr likes to take tasks off the big cores as soon as the phone gets a little bit too hot. Are your tweaks mainly for cold/light usage or work better when the phone is hot/throttling?
Click to expand...
Click to collapse
In order to conserve optimal temps and power consumption, imo the little cluster is best to be left alone and let it do its intended usage rather than be overclocked to 1.7GHz. During experimentation phase, overclocking little cluster to 2.1GHz will simply not get past the splash screen, my guess is that there isn't enough voltage to run it without making tweaks to the voltage table.
My sched tweaks is basically like this: more tasks with slightly higher priority are restricted for little cluster ONLY, meaning they will never be migrated to the big cluster (don't worry, these priority tasks should not be intensive anyway). Additionally, the little cluster has been tweaked to prevent being overloaded easily (lower the threshold for when a task will be spilled to the big cluster. Task migration is triggered faster when the little cluster is about to be overloaded and "spills" some tasks to the big cluster to handle. This should aim for good battery life on normal usage (more non intensive power tasks are strictly handled by little cluster) as well as good performance (tasks which are more intensive is faster spilled onto the big cluster to process, lessen the chance of the little cluster being overloaded before spill initiates.).
Using this with balanced mode pnpmgr tweaks is best, when the cpu gets warmer the pnpmgr will throttle the phone but seeing that the s820 can still perform pretty well under throttling there should be no major performance loss with my tweaks.
I've done gaming endurance tests which achieved a 1 hour endurance on Marvel Future Fight (medium graphics high performance setting in game), around 21-22% battery drain + temperatures were.capped at absolute 40C (sometimes even less!)
Sent from my HTC 10 using XDA Labs

My battery hasn't even had time to fully settle and battery life is surprising me, even with flashing and being in recovery some time today, and telegram running. Nice job @ZeroInfinity
Sent from my HTC 10 using Tapatalk

Flashed 10 mins ago on top if ice rom 2.4, made the 3 changes, must say, it seems very whizzy. Will test over the next few days, Thanks
Sent from my HTC 10 using XDA-Developers mobile app

Just wanted to say I got it booted and running on Verizon 10 on Viper ROM. Will report my experience as I usually run Elite kernel. Thank you for sharing.

nice to see you here with a kernel zero! On day 2 now. US T-Mobile variant running ICE, running great so far and great battery life. Will check back in later =P

Sooo... This just kind of happened. I would have removed some of the variables for better testing but the battery life caught me by surprise, so I have what I have.
Im going to post my battery life yesterday. I wasn't intentionally testing or I wouldn't have had so much extra stuff running. I was just shocked with the usage I had, how well it worked. I was on a road trip last night and streaming YouTube on 4G with the screen on playing HD video, because I don't pay for YouTube red or use the app that allows background play.
Like I said, this was with Google Maps running w/ GPS, Bluetooth connected to stereo, Pandora in background, and streaming YouTube on 4G for about 3 hours of the screen on time, and also had auxillary connected for YouTube streaming so I could use acoustix and boom sound.
Sent from my HTC 10 using Tapatalk

I had to restore the elite kernel, my signal was only showing 1x on Verizon.

LibertyMonger said:
I had to restore the elite kernel, my signal was only showing 1x on Verizon.
Click to expand...
Click to collapse
My signal only shows once. .
How many times do you want to see your signal?

p50kombi said:
My signal only shows once. .
How many times do you want to see your signal?
Click to expand...
Click to collapse
You shouldn't reply to posts you do not understand. Why not just ignore my post and move on? For clarification I am showing 1x on my status bar instead of 4g which means I lost my signal and data. It might be an issue with the Verizon 10's, we'll have to see from other Verizon users experience.

LibertyMonger said:
You shouldn't reply to posts you do not understand. Why not just ignore my post and move on? For clarification I am showing 1x on my status bar instead of 4g which means I lost my signal and data. It might be an issue with the Verizon 10's, we'll have to see from other Verizon users experience.
Click to expand...
Click to collapse
Hmm is it the same with Clean Slate kernel?

Mostafa Wael said:
Hmm is it the same with Clean Slate kernel?
Click to expand...
Click to collapse
not too sure if anything extra needs to be done to make it work on verizon variants, works on AT&T variants though.

Mostafa Wael said:
Hmm is it the same with Clean Slate kernel?
Click to expand...
Click to collapse
No works with Clean Slate but I mostly use elite kernel it seems to work best for me. It may have been just a fluke, I didn't have time to test today cause I was at work I just know I never have that problem, flashed this kernel last night and went to bed not noticing till after I got to work this morning. Hopefully someone else on Verizon can test.