Develop Bugs

OverClocking on the HTC Incredible -

I've tried using, I'm not a slow learner. I just don't quite understand how to overclock it.
I'm curious if my profiles settings are correct -
1.113Mhz Max
275Mhz Min on Performance - Are those correct if your trying to run your HTC at its highest quality while sacrificing battery?
I had one -
1.113Mhz Max
1.113Mhz Min and performance. It seemed fast and kept my temperature down to 95.8° instead of being at 108.3° all day and it also saved battery life alot. The reason its normally that hot is because I'm constantly using my Droid. My screen is why my Droid mainly dies half the time.
But can anyone tell me if I'm working this right?
Sent from my ADR6300 using XDA App

The performance governor keep your processor at the highest clock speed, so unless your running benchmarks, I wouldn't recommed using it. What kernel are you using and which app are you using for overclocking?

{
"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"
}
Set CPU root user access.
Also what do you mean by Benchmarks? Like testing or running certain apps?
Sent from my ADR6300 using XDA App

withbloodskies said:
Set CPU root user access.
Also what do you mean by Benchmarks? Like testing or running certain apps?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Like testing with quadrant or linpack.
Sent from my Droid Incredible running a random CM7 nightly.

withbloodskies said:
I've tried using, I'm not a slow learner. I just don't quite understand how to overclock it.
I'm curious if my profiles settings are correct -
1.113Mhz Max
275Mhz Min on Performance - Are those correct if your trying to run your HTC at its highest quality while sacrificing battery?
I had one -
1.113Mhz Max
1.113Mhz Min and performance. It seemed fast and kept my temperature down to 95.8° instead of being at 108.3° all day and it also saved battery life alot. The reason its normally that hot is because I'm constantly using my Droid. My screen is why my Droid mainly dies half the time.
But can anyone tell me if I'm working this right?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
use 128-1113 smartass

withbloodskies said:
Set CPU root user access.
Also what do you mean by Benchmarks? Like testing or running certain apps?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Benchmark apps like linpack or quadrant measure the general amount of processing power the phone is capable of. People generally run these apps to test how fast their phone is. On another note; since it looks like you are using cyanogenmod why are you using setcpu and not the built in overclocking feature built into the rom?

N-Forced said:
Benchmark apps like linpack or quadrant measure the general amount of processing power the phone is capable of. People generally run these apps to test how fast their phone is. On another note; since it looks like you are using cyanogenmod why are you using setcpu and not the built in overclocking feature built into the rom?
Click to expand...
Click to collapse
Ahh, well with Set CPU it allows me to use a widget etc. Also by installing one of these CPU apps it controls cyanogens built in CPU.
I'd also like to ask about the updated Nightlies roms they come out with constantly, what do they do?
Improve performance, battery, more options etc?
Sorry I'm a bit new to the world of root.
EDIT-- I tested quadrant and hit the 1,381 mark. Weather that is good or not I don't know.
Sent from my ADR6300 using XDA App

With CM7 there's really no need for a separate CPU controlling app, and I've heard it can actually cause conflicts, so I'd recommend just using the built in performance settings in the CM settings menu.
If you're using the stock kernel, I'd set the governor to on demand (I'd recommend smartass but I don't think the stock kernel has it), and set you minimum speed to the lowest possible, max speed to 998mhz. I underclock a little bit (883mhz) and you can experiment with lower or higher max clock speeds if you want to. I've found that overclocking produces no difference in real world performance, everything is just as snappy at 883mhz as it is at 1113mhz and if you choose to underclock, you may notice slightly better battery life.
As for the nightlies, they're usually pretty small changes at this point. They've been perfectly stable and bug free for a while now. There are feature additions that go in to the nightlies, a few things they've added recently are built in screenshot, lockscreen wallpaper, and dBm in the status bar instead of signal bars.
So to answer your question, there isn't really any difference between the nightlies and stable release as far as performance and battery life, but there are more features and options. With the nightlies as stable and bug free as they are, I wouldn't think twice about recommending them.

N-Forced said:
Benchmark apps like linpack or quadrant measure the general amount of processing power the phone is capable of. People generally run these apps to test how fast their phone is. On another note; since it looks like you are using cyanogenmod why are you using setcpu and not the built in overclocking feature built into the rom?
Click to expand...
Click to collapse
Benchmarks only very remotely indicate processing power of the device. They mainly measure an abstract of what the ROM and kernel are able to do given certain parameters. I can set my Tbolt up to run in the 1900 on Quadrant or run AOSP and pull down 4000+ scores. CM kernels are good, but I think there are better ones. There's no way running a performance governor yields better life than smartass, ondemand, or interactive. The reason you might want to use performance is if you're using it for a screen off setting. Performance doesn't use clock cycles to constantly measure CPU load so its a good choice when you need the CPU to switch governors and ramp up quickly or when there is no need for the CPU to change speed. Every kernel has its own custom tweaked govs so they will all act differently. I currently run my dInc at 245-1.153 on a smartass gov and my Tbolt at 61MHz-1.49GHz on a modified ondemand gov. Running a setting that simply pulls good scores isn't even always indicative of the quickest, most useful setup. Plus, on many ROMs, running the SetCPU widget will cause serious lag issues regardless of how amazing your benchmark scores. There's a lot to be learned from playing and a lot to be learned from reading and benchmark scores are anything but a gold standard of performance measurement.

k_nivesout said:
With CM7 there's really no need for a separate CPU controlling app, and I've heard it can actually cause conflicts, so I'd recommend just using the built in performance settings in the CM settings menu.
If you're using the stock kernel, I'd set the governor to on demand (I'd recommend smartass but I don't think the stock kernel has it), and set you minimum speed to the lowest possible, max speed to 998mhz. I underclock a little bit (883mhz) and you can experiment with lower or higher max clock speeds if you want to. I've found that overclocking produces no difference in real world performance, everything is just as snappy at 883mhz as it is at 1113mhz and if you choose to underclock, you may notice slightly better battery life.
As for the nightlies, they're usually pretty small changes at this point. They've been perfectly stable and bug free for a while now. There are feature additions that go in to the nightlies, a few things they've added recently are built in screenshot, lockscreen wallpaper, and dBm in the status bar instead of signal bars.
So to answer your question, there isn't really any difference between the nightlies and stable release as far as performance and battery life, but there are more features and options. With the nightlies as stable and bug free as they are, I wouldn't think twice about recommending them.
Click to expand...
Click to collapse
I have to agree with him on the multiple clock setting apps. They work my running scripts and the scripts can conflict. If you're not running profiles, don't use SetCPU. If you are, ditch the other app.

Hmm, alright thanks. Well definitely learned alot from Over/Underclocking thank you.
Guess I'll get rid of the app? Should I use a different kernal though then the one I'm using depicted in that picture?
Sent from my ADR6300 using XDA App

withbloodskies said:
Hmm, alright thanks. Well definitely learned alot from Over/Underclocking thank you.
Guess I'll get rid of the app? Should I use a different kernal though then the one I'm using depicted in that picture?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
if you want. The cm kernel is just a generic kernel they port for each device so there isn't a lot of customization built into it. It's not a bad kernel, but there are certainly faster ones.

I just caught this thread and wanted to say Thanks for the input...
and ask for your recommendations on a few Kernels to try on a Dinc running CM7, and if you have the time what benefits they might provide?

I'd have to recommend Chad's incredikernel. It has the smartass governor, which tends to yield the best battery life as well as good performance. A feature it has that I find essential now is fast charge, as well as USB fast charge. There's also a flashable SD speed fix that remedies the slow transfer speeds on AOSP roms. It also goes hand in hand with the incredicontrol app, which allows for undervolting to extend your battery life even further.
I'd go to the incredikernel thread in the development forum, and also www.incredikernel.com to read up a bit on all the features and how to utilize them.

k_nivesout said:
I'd have to recommend Chad's incredikernel. It has the smartass governor, which tends to yield the best battery life as well as good performance. A feature it has that I find essential now is fast charge, as well as USB fast charge. There's also a flashable SD speed fix that remedies the slow transfer speeds on AOSP roms. It also goes hand in hand with the incredicontrol app, which allows for undervolting to extend your battery life even further.
I'd go to the incredikernel thread in the development forum, and also www.incredikernel.com to read up a bit on all the features and how to utilize them.
Click to expand...
Click to collapse
I installed the lastest, now you said I should get faster USB charge correct? Cause that would be absolutely wonderful, I broke my original cord and got this 1in cord that barely works and it works USB. If this is true this Guy is a God! Anyway so smartass is the best between saving battery and performance?
Sent from my ADR6300 using XDA App

Yes, I'd use recommend the smartass governor for the best combo of battery life and performance, and to enable USB fastcharge I use his incredicontrol app. Obviously the fast charge will only work if the USB port is putting out enough power to support it.

k_nivesout said:
Yes, I'd use recommend the smartass governor for the best combo of battery life and performance, and to enable USB fastcharge I use his incredicontrol app. Obviously the fast charge will only work if the USB port is putting out enough power to support it.
Click to expand...
Click to collapse
Dude seriously thank you! Is there a personal thread started from Chad declaring his awesome kernel? Ill join his alliance, this **** is literally the best thing my phone could have got.
- Before IncrediKernel, my phone died within 1-2 hours heavy use.
- After Installing, heavy use gives me 4-5 hours.
- Before IncrediKernel, my phone took 3-4 hours to fully charge.
- After installing, my phone charges within 1 hour and 30 mintues roughly upon heavy use. So estimated 40 minutes - 1 hour for full charge without use?
This kernel seriously did wonders. Thanks a ****ing alot chad! Best **** ever!
Sent from my ADR6300 using XDA App

[HOWTO] Detecting the LP Core + Disabling the other 4 (maybe)!

Nothing in this post should be considered gospel; These are simply conclusions I've drawn from testing. Everything written here could be (and probably is) very, very wrong!
Click to expand...
Click to collapse
YOU MUST BE ROOTED TO ATTEMPT ANYTHING IN THIS THREAD
I don't take full credit for this, someone posted information about the file I listen to but I can't for the life of me find the post. If someone locates it let me know so I can give credit where it's due!
Detecting the Companion Core
The 5th Core (Companion Core/Low Power - LP - Core) is invisible to the android system and cannot be controlled at the moment. However, the kernel can see the 5th core and can detect whether it's running or not.
This is a simple demonstration of this, nothing particularly interesting or useful yet!
Results with screen ON
{
"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"
}
Results with screen OFF
So yeah, this is why we get such great screen-off battery life!
I know pretty much everything written here is already known I just thought it would be nice to see some proof!
For those of you that want to try this out yourself, make a service that runs in the background that reads from: "/sys/kernel/cluster/active". It will be either "G" or "LP" (G meaning it's running from the normal cores, LP is the Low Power core.)
Interestingly, while the screen is on but nothing much is happening on the device it will constantly switch between G and LP (like in the first screenshot) but when doing CPU intensive tasks it runs as G constantly. When the screen is off, it never switches to G which is giving us the insane screen-off battery life.
Disabling 4 Cores and just running the LP Core!
NOTE: This may not be the case. The phone kinda gets a bit screwy and reports different things. I'm pretty sure this is just the throttle that happens when the CPU hits 90°c but I'm not sure (it's hard to make it hit 90°c!). If anyone knows what else it does please let me know!
WARNING: This can, and most probably will, crash your phone after a while. When running CM9 I even had to reflash the ROM (This hasn't happened on Android Revolution yet). Basically PLEASE make a backup and don't blame me if you mess anything up!
This is a strange one. If you navigate to "/sys/kernel/debug/cpu-tegra" there's a file called 'Throttling'. Changing this file to '1' makes the system throttle CPU usage drastically.
Interestingly though, it also makes the "sys/kernel/cluster/active" file report nothing but 'LP' even when doing tasks, indicating that it's running solely off the LP Core. However, I'm using TegraStats to monitor what's active and what isn't and when throttling is enabled it reports that 'cpu0' is also active, contrary to what the "sys/kernel/cluster/active" file says.
If you apply this mod you will instantly see why I think it's running soley off the LP Core: It makes the phone almost unusable and I wouldn't recommend doing it for any great length of time!
Another wierd thing is that TegraStats also reports that CPU1 activates at random points while the phone stays as slow as ever.
Of course, CPU1 could indeed be active and just throttled to a low clock speed (102mhz is pretty much the average when doing anything. It can go as high as 304 though) but it still doesn't explain the LP Core results.
So, if this is running off only the companion core, what does it mean? Well, you could ultimately gain massive battery improvements. The only problem is, the mod renders the phone unusable as it stands. The throttle would probably need to be modified from kernel source to not be quite as aggressive or something, so not useful at the moment but it has potential
I hope you found this interesting!

Reserved for future info!

Nothing to add, sorry, but very cool.

how to disable lp core.
i need to disable it completly. it has ****ty performance
or maybe you know how to change governor on that core or something with him

kragnegrozor said:
how to disable lp core.
i need to disable it completly. it has ****ty performance
or maybe you know how to change governor on that core or something with him
Click to expand...
Click to collapse
it's not good to disable the core because after that you wont have good standy battery life.....and what do you mean with it has bad performance?

man, newest update in youtube APP uses only 1 core, and this core is this sh****ty fifth one. in 720p films there are stuttering and other sh** sometimes. If you demand something powerful from phone at this time, other 4 cores are ON and video is playing smoothly.

Lolwut? The companion core should only be used once your screen is off or goes into deep sleep. Not for the main system to use or for playing YouTube videos.
Sent from my HTC One X using Tapatalk 2

Well done on bumping a 7 month old thread that obviously isn't relevant any more, guys...

so can somebody tell me how to disable it or change governor? it is for research

kragnegrozor said:
so can somebody tell me how to disable it or change governor? it is for research
Click to expand...
Click to collapse
Try System Tuner or any similar app.

kragnegrozor said:
so can somebody tell me how to disable it or change governor? it is for research
Click to expand...
Click to collapse
neuTrue said:
Try System Tuner or any similar app.
Click to expand...
Click to collapse
no app can disable it until a kernel dev can something do for it ...also nothing else can disable it ...try to search for example for youtube a fix that it will work better ...because the 5th core doesn't work in youtube or other ...youtube is stuttering because of other things not the 5th core

Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.

XxVcVxX said:
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
No it doesn't.
Sent from my HTC One X using Tapatalk 2

Learn about the topology of tegra3 unit. Different core technology, Different performance.
Wysyłane z mojego HTC One X za pomocą Tapatalk 2

XxVcVxX said:
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
it has only 500 mhz and it will be used for apps which wont take much or if the screen is off/deep sleep...it wont be used in apps like youtube and other ...
like messaging/sms app or e-mail or so

One-X-master said:
it has only 500 mhz and it will be used for apps which wont take much or if the screen is off/deep sleep...it wont be used in apps like youtube and other ...
like messaging/sms app or e-mail or so
Click to expand...
Click to collapse
It has the exact same performance.
It's still ARM Cortex A9, only manufactured with low power silicon. It doesn't scale well into high clock speeds so thus its limited to 500 MHz, but it still has the same performance at same frequency.
Sent from my faster than SGS3 HOX.

XxVcVxX said:
It has the exact same performance.
It's still ARM Cortex A9, only manufactured with low power silicon. It doesn't scale well into high clock speeds so thus its limited to 500 MHz, but it still has the same performance at same frequency.
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
yes but it it isn't working while apps like youtube I have no problems when i use youtube he also had to write which kernel he use because some of the custom kernels or the stock don't know what it was have problems in some apps also figuered that out i had also with a kernel problems in youtube in other no problems...but don't know which because i don't have the phone here because of the f*cking repair center...

i am using kernels
,doing some research about performance.
Just some observations for now
i am need to know how to disable it.
Got some knowledge from many other phones\kernels\roms
But here is tegra3 topology

kragnegrozor said:
i am using kernels
,doing some research about performance.
Just some observations for now
i am need to know how to disable it.
Got some knowledge from many other phones\kernels\roms
But here is tegra3 topology
Click to expand...
Click to collapse
you know that EVERY android build has kernels because without they can't work? i meant with stock kernel that's the kernel in the stock RUU/ rom and custom kernels were edited by devs like faux etc...you CAN'T disable it try to ask a kernel dev you can see them in original development thread but like i know it's impossible because the 5th is for android unvisible ^^

i am gonna think about that.
i am seen somewhere OCed 5th core. Gonna find where and ask in that kernel thread.
thanks

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.

[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.

Batterry drain by Android system and stand-by

Does anybody else noticed the huge amount of batterry drain that goes on all day long. I got this phone for about half a year and I think it's worse than before. I'm not the only one with this problem, most of my family got this phone as well and are having the same problem.
In the screenshots you can see how it drained. The screenshots were made after a day of work where I barely used my phone. It seems like it won't get in the Android sleep or Doze.
{
"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 tried several things as hard restting my device and I tried ForceDoze, but all of this didn't work. What can I do?

Stock or custom ROM ?
I got mine yesterday, flashed LineageOS right then..
And I do find battery life extremely poor compared to my older Moto G first gen.
But this might not mean anything for your case though.

matmutant said:
Stock or custom ROM ?
I got mine yesterday, flashed LineageOS right then..
And I do find battery life extremely poor compared to my older Moto G first gen.
But this might not mean anything for your case though.
Click to expand...
Click to collapse
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.

Aaapiie said:
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Click to expand...
Click to collapse
As I didn't try stock rom for more than 5 minutes, I have no idea if it is better or worse on Lineage...
Only thing I can say is that I am very disappointed with the battery life, I could get 2 days on my old G where I can only get half one on this device with similar usage...
When I bought it (rushed buy as my G died), I didn't figure that doubling the screen res and and the CPU cores will cut by more than half the battery life with a only 35% bigger battery.
for your specific problem you might try to recalibrate your battery (cf : here)

Stock is not configured the best. It's running in performance mode and not running BigLittle configuration even tho we have slow cores and fast ones. Latest lineage has a BigLittle setup that will help a lot. Battery still not the best tho but way better for sure.

trotter2000 said:
Stock is not configured the best. It's running in performance mode and not running BigLittle configuration even tho we have slow cores and fast ones. Latest lineage has a BigLittle setup that will help a lot. Battery still not the best tho but way better for sure.
Click to expand...
Click to collapse
Are you sure msm8937 really supports big.LITTLE configuration? I can't find it anywhere :\
If I remember well (but I didn't follow SoC dev since msm8926), Qualcomm way of running CPUs was using MPdecision and such to shut down unneeded Cores and work on the minimum needed active cores, instead of having four or eight cores powered at anytime (and at blazing 900-1094MHz -_- )

matmutant said:
Are you sure msm8937 really supports big.LITTLE configuration? I can't find it anywhere :\
If I remember well (but I didn't follow SoC dev since msm8926), Qualcomm way of running CPUs was using MPdecision and such to shut down unneeded Cores and work on the minimum needed active cores, instead of having four or eight cores powered at anytime (and at blazing 900-1094MHz -_- )
Click to expand...
Click to collapse
Well it seems to be working OK. Kernel auditer is showing big.LITTLE. Updated 2 days ago self compiled lineageos. If you set powersave on big you get loads of deeps sleep on the cores. On stock there was never any deep sleep they was always running.

well, that's interesting,
I'll try to investigate a little [no pun intended] more, but at first sight, touching cpu0 freq affects the whole 4 core cluster (0 to 3)

Iv never had any problems with battery
As the screenshot shows - Iv been using my phone pretty much constantly the last 7 hours & Iv still got 7 hours left
So with constant Internet usage as well as spotify/pandora YouTube games etc I get at least 14 hours use out of this phone and normally longer - I only charge once a day
Iv always been using lineageos

TheFixItMan said:
Iv never had any problems with battery
As the screenshot shows - Iv been using my phone pretty much constantly the last 7 hours & Iv still got 7 hours left
So with constant Internet usage as well as spotify/pandora YouTube games etc I get at least 14 hours use out of this phone and normally longer - I only charge once a day
Iv always been using lineageos
Click to expand...
Click to collapse
could you please post a screenshot of cpuZ showing CPU freq when idle?
what I have here, and that looks quite strange to me :
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
960000 1094400 1209600 1248000 1344000 1401000
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_available_frequencies
768000 902400 998400 1094400
which looks to me that the High perf Cores are 0 to 3 and low power ones 4 to 7...
but 4 to 7 seem stuck at 1094400Hz and 0 to 3 are 960000Hz when idle
I would expect that the High perf cores should turn off when idle, and that the low power ones go down to 768000... which would save quite some juice... isn't it?
I'm using LineageOS 14.1 by @wzedlare (lineage-14.1-20171018-UNOFFICIAL-cedric.zip)

matmutant said:
could you please post a screenshot of cpuZ showing CPU freq when idle?
what I have here, and that looks quite strange to me :
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
960000 1094400 1209600 1248000 1344000 1401000
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_available_frequencies
768000 902400 998400 1094400
which looks to me that the High perf Cores are 0 to 3 and low power ones 4 to 7...
but 4 to 7 seem stuck at 1094400Hz and 0 to 3 are 960000Hz when idle
I would expect that the High perf cores should turn off when idle, and that the low power ones go down to 768000... which would save quite some juice... isn't it?
I'm using LineageOS 14.1 by @wzedlare (lineage-14.1-20171018-UNOFFICIAL-cedric.zip)
Click to expand...
Click to collapse
Here are some screenshots
The lowest frequency the kernel is set to run at is 960mhz
You would need a custom kernel to play with the scailing & min frequency

Add screenshot
TheFixItMan said:
Here are some screenshots
The lowest frequency the kernel is set to run at is 960mhz
You would need a custom kernel to play with the scailing & min frequency
Click to expand...
Click to collapse
I understand that the big are good to go with 960MHz as long as they should be off most of the time when idle,
But why the LITTLE cores are at 1GHz wen they could be much lower clocked when nothing is going on xD
from what I can see, it is possible to shutdown one or more core(s) manually :
Code:
echo 0 > /sys/devices/system/cpu/cpu3/online
So I hope we can implement some hotplug driver to save some battery life.

Aaapiie said:
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Click to expand...
Click to collapse
Could you please post a screenshot of cpuZ like I did?
I'd like to have an idea of the stock behavior
Sorry to hijack this thread BTW, but that might help more than it seems

matmutant said:
Could you please post a screenshot of cpuZ like I did?
I'd like to have an idea of the stock behavior
Sorry to hijack this thread BTW, but that might help more than it seems
Click to expand...
Click to collapse
No problem at all, thanks for your thoughts.
Here are some screenshots, hope this is what you are looking for (the cpu core values may vary).

At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...

matmutant said:
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
Click to expand...
Click to collapse
Sorry for the late response. But what do you mean? You mean the field in the bottom of cpuz? Cuz that is saying interactive

Aaapiie said:
Sorry for the late response. But what do you mean? You mean the field in the bottom of cpuz? Cuz that is saying interactive
Click to expand...
Click to collapse
cpuZ fails to detect the two different clusters and assumes core 1-7 are slave of core 0
If you are rooted, the app "Kernel Adiutor" can tell us more about this by looking at CPU menu, and governor for the LITTLE cluster
Or
Code:
cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor

matmutant said:
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
Click to expand...
Click to collapse
matmutant said:
cpuZ fails to detect the two different clusters and assumes core 1-7 are slave of core 0
If you are rooted, the app "Kernel Adiutor" can tell us more about this by looking at CPU menu, and governor for the LITTLE cluster
Or
Code:
cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
Click to expand...
Click to collapse
I don't have root access. If I'm right I can run that command using an terminal app like Termux? If so see the result in attachment.
Edit: I think I'll try out lineage os tommorow or on Wednesday and I'll see what happens for the battery

Aaapiie said:
I don't have root access. If I'm right I can run that command using an terminal app like Termux? If so see the result in attachment.
Edit: I think I'll try out lineage os tommorow or on Wednesday and I'll see what happens for the battery
View attachment 4312018
Click to expand...
Click to collapse
At least the governor is properly configured for the 4-7 cluster on stock ROM (that's something that I was starting to doubt about...)
If you ever install LinageOS in the next days (but I hope it will be fixed before) you may need to force the governor of the cluster 4-7 by 'echoing' it to core 4 (of use Kernel Adiutor for that matter)
did you search for any service that could be running in the background all time?

matmutant said:
At least the governor is properly configured for the 4-7 cluster on stock ROM (that's something that I was starting to doubt about...)
If you ever install LinageOS in the next days (but I hope it will be fixed before) you may need to force the governor of the cluster 4-7 by 'echoing' it to core 4 (of use Kernel Adiutor for that matter)
did you search for any service that could be running in the background all time?
Click to expand...
Click to collapse
No I cannot point a finger to a specific app. I've done serveral factory resets, but no success with a clean reset.