I notice some epics have issues with the 100mhz step in kernels. Some freezes and lockups as well as battery drain. I know we can disable 100mhz with setcpu and voltage control. And that usually fixes the epics with the problem. However i'm curious to know how many people are suffering from this and what else u did to fix it.
Sent from my SPH-D700 using Tapatalk
DaKillaWilla said:
I notice some epics have issues with the 100mhz step in kernels. Some freezes and lockups as well as battery drain. I know we can disable 100mhz with setcpu and voltage control. And that usually fixes the epics with the problem. However i'm curious to know how many people are suffering from this and what else u did to fix it.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Interesting, I have mine set to bottom out at 100Mhz stepping too, and I've been experiencing lock-ups, force-closes and video out-of-synche issues. I'll see if they go away when setting it to 200Mhz bottom speed. 200Mhz should be sufficient to save CPU heat and battery.
Lag should be normal, but lockups shouldn't. Thanks for the heads up.
As of why this happens, there are four possibilities.
1. The kernel has a problem stepping into that particular mode on that particular CPU.
2. There is some issue with hardware buffer overruns in 100Mhz. This is a known nasty problem with under-clocking. Best case the system looses data from the buffer, worst case, the buffer overwrites it's data elsewhere.
3. The CPU, chipset, board configuration or combination thereof is unstable at 100Mhz for any number of reasons (these range from RAM timing issues, to bouncing and glitching issues, to the ever annoying EMI resonance.)
4. Two or more of the above.
Possibility 1 is fixable with an upgrade to a newer kernel that has that particular ARM CPU's clock-scaling mechanism fixed. You can check for it on the Linux kernel change-logs and known bugs lists.
Possibility 2 is fixable with an anticipatory user-space governor that will increase clock speed when activity levels exceed a threshold on the CPU's external bus, a microcode patch or a written kernel patch could also work. (I have a slight clue of a few things that might work, but no clue how to implement them.)
Possibility 3 can only be fixed by means of sanity checks that would drain battery life and defeat the purpose of underclocking to 100Mhz to begin with.
The only exception to the unfixable nature of of Possibility 3 would be if the device is ECC capable, but ECC is deactivated because Samsung and/or Sprint in their allknowing wisdom saw it as the unnecessary bottleneck it was and wanted to squeeze out one or two more points on a benchmark.
They already deactivated CPU clock scaling on the device for the same inspired reasoning, so I wouldn't put it past them to deactivate ECC as well.
Anyways, if anyone wants to run a log check of these freezes, it would be nice. I don't have the time right now to search through long excessive logs, as I have several projects ahead. After my current project I will probably fix it.
p.s.
Sorry for rambling, It's a bad tendency of mine. I normally can control it but I'm a little overtired and have a bad migraine, so please bare with me. Thanks.
On Froyo custom ROMs I would get Sleep of Death at 100 Mhz occasionally. Would remove 100Mhz step with SetCPU but does not happen on Gingerbread ROMs.
Sent from my SPH-D700 using XDA App
Ruedii said:
Interesting, I have mine set to bottom out at 100Mhz stepping too, and I've been experiencing lock-ups, force-closes and video out-of-synche issues. I'll see if they go away when setting it to 200Mhz bottom speed. 200Mhz should be sufficient to save CPU heat and battery.
Lag should be normal, but lockups shouldn't. Thanks for the heads up.
As of why this happens, there are four possibilities.
1. The kernel has a problem stepping into that particular mode on that particular CPU.
2. There is some issue with hardware buffer overruns in 100Mhz. This is a known nasty problem with under-clocking. Best case the system looses data from the buffer, worst case, the buffer overwrites it's data elsewhere.
3. The CPU, chipset, board configuration or combination thereof is unstable at 100Mhz for any number of reasons (these range from RAM timing issues, to bouncing and glitching issues, to the ever annoying EMI resonance.)
4. Two or more of the above.
Possibility 1 is fixable with an upgrade to a newer kernel that has that particular ARM CPU's clock-scaling mechanism fixed. You can check for it on the Linux kernel change-logs and known bugs lists.
Possibility 2 is fixable with an anticipatory user-space governor that will increase clock speed when activity levels exceed a threshold on the CPU's external bus, a microcode patch or a written kernel patch could also work. (I have a slight clue of a few things that might work, but no clue how to implement them.)
Possibility 3 can only be fixed by means of sanity checks that would drain battery life and defeat the purpose of underclocking to 100Mhz to begin with.
The only exception to the unfixable nature of of Possibility 3 would be if the device is ECC capable, but ECC is deactivated because Samsung and/or Sprint in their allknowing wisdom saw it as the unnecessary bottleneck it was and wanted to squeeze out one or two more points on a benchmark.
They already deactivated CPU clock scaling on the device for the same inspired reasoning, so I wouldn't put it past them to deactivate ECC as well.
Anyways, if anyone wants to run a log check of these freezes, it would be nice. I don't have the time right now to search through long excessive logs, as I have several projects ahead. After my current project I will probably fix it.
p.s.
Sorry for rambling, It's a bad tendency of mine. I normally can control it but I'm a little overtired and have a bad migraine, so please bare with me. Thanks.
Click to expand...
Click to collapse
Wow, now that's an explanation! Some phones can hang at 100 some have to be 200 just like not all phones overclock the same but Ruedii's explanation really gets down to the reasons why. Nice
Sent from my Nexus S 4G using Tapatalk
Damnnn Reudii where u been hiding at.... lol
I do believe the people who own epics that can't go to 100mhz are suffering serious data corruption. I think most people don't know it, and there popping up with bugs in a rom thinking it was something else that was causing it. I also believe that they also have a serious battery drain. This the reason some people get 20hrs or less battery life and some people claim 40hrs or more. I don't understand why they even put a 100mhz step in the kernel when the 200mhz uses the same voltage. So whether it be 100mhz or 200mhz it wouldn't make a difference on battery being used. I'm sticking with 200mhz.
Sent from my SPH-D700 using Tapatalk
I have no problems running at 100mhz
I am stable at these frequencies with these voltages - I really don't go wild with undervolting - this setting has worked on 4 of my epics, as they were all set up the same (I also have 145'ish 3rd part apps both paid and free).
1400mhz - stock voltage only - otherwise unstable less than 50% of the time - has the worst battery drain if I play a game and gets warm also
1300mhz - minus 25mv
1200mhz - minus 25mv
1120mhz - minus 25mv
1000mhz - minus 25mv
800mhz - minus 25mv
600mhz - minus 50mv
400mhz - minus 50mv
200mhz - minus 50mv
100mhz - minus 50mv
Not a single glitch, but you can see, I do things very mildly. All for epics run with what is in my signuture.
Hi, i have a Oneplus 2 with snapdragon 810 and im doing some research, i edited the thermal-engine.conf to have good performance for a long period of time with heavy tasks.
I would be greatefull if someone pm me the thermal-engine.conf located on system/etc (on op2, probabbly the same for m9) or tell me at what temperature it throttle and how much.
Thanks in advance!
Here it is: https://www.dropbox.com/s/et3lx317adk0dtg/thermal-engine.conf?dl=0
Sent from my HTC One M9!
Luhccas-X10 said:
Here it is: https://www.dropbox.com/s/et3lx317adk0dtg/thermal-engine.conf?dl=0
Sent from my HTC One M9!
Click to expand...
Click to collapse
Thank you.
Hi again, I already tested a lot and I have my profile for gaming and no throttle in normal usage.
For gaming I have a profile that turns on only 2 little cores at 1,3ghz and 2min and 4max big cores at 1,4ghz. GPU at 450mhz or 510mhz (as you want) I have 450mhz. Interactive governor. And stock for normal usage, 4 little cores online at 1,5ghz and 2min 4max at 1,8ghz, GPU at 630mhz. The reason I throttle it more for gaming is to have better performance as time goes by, so it will get hot later and it takes a lot of time to throttle.
Throttle file has almost no LCD throttle so you have to do it manually, if gets too hot (its not gonna happen) it throttles automatically.
At 53,6c° of skin temp it throttle both clusters to 1,2ghz and gpu to 390mhz. Games still running smoothly and it doesn't get hotter, it mainten the temperature.
Remember this file is done for oneplus 2 by @i9100g user , I tested it for games and tweak it a little. I guess it wont work on droid turbo 2 because of the names of the sensor that are differents, and maybe frequencies too but I don't think so. You will need someone to "port it" Later I will test to add a sooner throttle at 1,3ghz both clusters and raise the max freqs for cpu on gaming profile.
English is not my native language, I'm sorry if I made some mistakes.
Thats it,cheers.
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Deep.cdy said:
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Click to expand...
Click to collapse
You should try them and find out the most suitable for you, use them for 1-2 days, you'll see the difference.... personally, I'm using NoName kernel with RR
NoName for Lineage based.
Deep.cdy said:
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Click to expand...
Click to collapse
i think currently is noname.
we hope a bunch of recognised developers in the near future as franco as many others.
Kirks, for battery...
Dude unlocked the lower cpu freqs...
m666p said:
Kirks, for battery...
Dude unlocked the lower cpu freqs...
Click to expand...
Click to collapse
It operates on lower Volts using this unlocked freqs?
peter-k said:
It operates on lower Volts using this unlocked freqs?
Click to expand...
Click to collapse
God knows, but what I do know is that it should produce less heat at the very least and it performs pretty gud on powersave governor. The gpu on the other hand is garbage at min freq (160mhz), even the launcher lags....
peter-k said:
NoName for Lineage based.
Click to expand...
Click to collapse
But after flashing no name 1.3 the WiFi doesn't work for me on rr 12th June
Deep.cdy said:
But after flashing no name 1.3 the WiFi doesn't work for me on rr 12th June
Click to expand...
Click to collapse
Mine was fine but now I'm on Aosip.
i think for now the best is to use a stock kernel, be careful with the charging limits.
peter-k said:
It operates on lower Volts using this unlocked freqs?
Click to expand...
Click to collapse
m666p said:
God knows, but what I do know is that it should produce less heat at the very least and it performs pretty gud on powersave governor. The gpu on the other hand is garbage at min freq (160mhz), even the launcher lags....
Click to expand...
Click to collapse
Of course it operates at lower voltage as it's a lower frequency and requires less power draw. Lower voltages should mean lower heat, however you don't magically get that lower freqs to operate, you need to tweak the interactive governor to make use of them all efficiently. So far I'm on Kirks kernel and AOSiP and it's a quite good combo.
The lag is not caused by low GPU freqs, it's because of low CPU freqs for that particular load, so governor tweaking is needed.
Cirra92 said:
Of course it operates at lower voltage as it's a lower frequency and requires less power draw. Lower voltages should mean lower heat, however you don't magically get that lower freqs to operate, you need to tweak the interactive governor to make use of them all efficiently. So far I'm on Kirks kernel and AOSiP and it's a quite good combo.
The lag is not caused by low GPU freqs, it's because of low CPU freqs for that particular load, so governor tweaking is needed.
Click to expand...
Click to collapse
Lol, I tested what you said out. Because you said it with such confidence...
I changed the cpu governor to performance and set the gpu to 160mhz max...
That made the experience a bit better but it would still lag a lot in recents and app launcher scrolling...
I've attached a screen shot to prove it too...
Another thing, just because the clock is lower does not mean that the voltage is lower as well, many devices that ive owned over the years have had the same voltage's for lower clocks( moto g2, Sony xperia z1)
And lastly, you should "magically" get those lower frequencies(if they are truly unlocked) since governors will always operate within the min/max frequencies that are set by the user or by default(unless it reverts parameters back to stock, like our device does on interactive)...
Forgot screenshot....
m666p said:
Lol, I tested what you said out. Because you said it with such confidence...
I changed the cpu governor to performance and set the gpu to 160mhz max...
That made the experience a bit better but it would still lag a lot in recents and app launcher scrolling...
I've attached a screen shot to prove it too...
Another thing, just because the clock is lower does not mean that the voltage is lower as well, many devices that ive owned over the years have had the same voltage's for lower clocks( moto g2, Sony xperia z1)
And lastly, you should "magically" get those lower frequencies(if they are truly unlocked) since governors will always operate within the min/max frequencies that are set by the user or by default(unless it reverts parameters back to stock, like our device does on interactive)...
Click to expand...
Click to collapse
First of all, we are talking here about difference in voltage between stock minimum freq for big cluster, which is 1.1ghz and actual possible minimum which is 300mhz, and there is a difference in voltage, that was the point. The devices I owned, S5 and Z3compact had more CPU steps, therefore the difference between some of the steps was really small or there wasn't any, but the CPU scaling made a jump to the freq with bigger difference (higher or lower, that was the stock behavior so some freqs weren't used). Here it might use all of the freq steps as there are less of them and the difference in voltage is significant enough, which might be the case, I said that because of my experience with previous devices. But you've missed the point anyway, I have said that even if unlocked, some freqs won't be used just because they are there if the governor parameters aren't set properly (or will be barely used). That was my point, I said that as a general note, so users won't jump the gun and blame devs for whatever.
And another one, regarding your test and lag with GPU, now I'm confused why would you set your max at 160mhz? I know it was for testing purposes in this case, but you did complain about it in original post and I said it won't lag because the max would still be set to 430mhz in which case the GPU freq scaling would do the job which it does very good so far. It would lag of course if you set max GPU freq to 160, but that's not what would you do for daily usage, right? Sorry if I misunderstood something.
Cirra92 said:
First of all, we are talking here about difference in voltage between stock minimum freq for big cluster, which is 1.1ghz and actual possible minimum which is 300mhz, and there is a difference in voltage, that was the point. The devices I owned, S5 and Z3compact had more CPU steps, therefore the difference between some of the steps was really small or there wasn't any, but the CPU scaling made a jump to the freq with bigger difference (higher or lower, that was the stock behavior so some freqs weren't used). Here it might use all of the freq steps as there are less of them and the difference in voltage is significant enough, which might be the case, I said that because of my experience with previous devices. But you've missed the point anyway, I have said that even if unlocked, some freqs won't be used just because they are there if the governor parameters aren't set properly (or will be barely used). That was my point, I said that as a general note, so users won't jump the gun and blame devs for whatever.
And another one, regarding your test and lag with GPU, now I'm confused why would you set your max at 160mhz? I know it was for testing purposes in this case, but you did complain about it in original post and I said it won't lag because the max would still be set to 430mhz in which case the GPU freq scaling would do the job which it does very good so far. It would lag of course if you set max GPU freq to 160, but that's not what would you do for daily usage, right? Sorry if I misunderstood something.
Click to expand...
Click to collapse
I kinda get what you mean, but the min freqs should kick in by default. They don't though on kirks, you need to change the governor to something like alucard or zzmove once before it actually starts clocking down to 300mhz...
On a side I would just disable the big. Cluster if I could, I don't really need that much cpu performance...
I was trying to find the min gpu freq that would be usable and I was disappointed, cuz my Sony z1 had a smooth ui experience with the gpu clocked at 200mhz max and that thing had a sd800...
Btw, I do all this to get better battery life...
I found out something else, I can't use power save governor any more because it can't handle audio processing(ainur, v4a) when the screen is off...
Just like my old z1, Lol...
Makes me think that the performance is really identical to the snapdragon 800...
I wonder how pissed I would be if a I got the redmi 5 plus, the 625 would have been even worse...
m666p said:
I kinda get what you mean, but the min freqs should kick in by default. They don't though on kirks, you need to change the governor to something like alucard or zzmove once before it actually starts clocking down to 300mhz...
On a side I would just disable the big. Cluster if I could, I don't really need that much cpu performance...
I was trying to find the min gpu freq that would be usable and I was disappointed, cuz my Sony z1 had a smooth ui experience with the gpu clocked at 200mhz max and that thing had a sd800...
Btw, I do all this to get better battery life...
Click to expand...
Click to collapse
m666p said:
I found out something else, I can't use power save governor any more because it can't handle audio processing(ainur, v4a) when the screen is off...
Just like my old z1, Lol...
Makes me think that the performance is really identical to the snapdragon 800...
I wonder how pissed I would be if a I got the redmi 5 plus, the 625 would have been even worse...
Click to expand...
Click to collapse
Yeah I agree, it should, but how much it stays on minimum freq is dependent on couple of governor parameters (talking about interactive). On mine though it does stay on 300mhz when idling, on stock Kirks settings. Big cluster can be disabled through new hotplug solution, like Intelliplug, which I used on my old devices, and it performed great, 1 core was active when screen was off, screen on and light usage required only 2 cores, while all 4 were active under heavy load. Here however there is only Qualcomm's hotplug solution, until that changes, no luck. Regarding GPU freq, I don't think any device would work smoothly under 200mhz, you can set 266mhz here, it will be smooth, I've tested today, on my old SD801 it performed at 233mhz IIRC.
I've seen that, V4A requires higher freq than 300mhz, or even 422mhz which SD801 had, it's more about the freq rather than the chipset, as I've read on multiple threads that even the devices with SD820 were struggling a lot when processing audio at 300mhz when the screen was off. Don't worry, it's a general issue. There is also the optimization of the rom and audio mods as well, background tasks, kernel, it all goes into the mix.
This is actually a very good chipset, it's technically SD660 just with lower clocks on both CPU and GPU.
EDIT: I forgot, this is my usage on AOSiP + Kirks, stock interactive tunables, min freq 300mhz (big/little), GPU initial/min freq 160mhz, max 430mhz. Using microG instead off GApps, I have used FB, Instagram, Messenger app for 1,5h each, Viber was couple of hours, Chrome some 30mins, Panini sticker album 30+ minutes, 30 minutes of 2G calls. Network mode was LTE, though I was on wifi on whole charge.
Started measuring from 92%.
Thanks bro, that explains a lot...
Hi.
I'm running LineageOS 20 on my F3.
In the thread of the OS, someone recently discovered that the quickest CPU-core (cpu7) wasn't ramping up to 3.2GHz, but rather to 2.8GHz (see https://forum.xda-developers.com/t/...i-11x-redmi-k40.4418635/page-37#post-88455155 and beyond).
Somewhere, recently, this issue has been fixed, with multiple people (including myself) reporting that cpu7 spikes up to 3.2GHz on occasion.
Now.... that sounds nice and all.... howeverrrrr.....
Right after a bootup, my device does properly spike up to 3.2, but, at some point it will no longer do that.... rather back to 2.8, 2.4 and I've even seen 1.3GHz as the max on cpu7.
My suspicion is that it's related to the device having been throttled at some point.
Me playing a couple of minutes of Pokemon Go tends to warm up the device enough to get it throttling. Afterwards, even when cooled down again, the device won't ever get back up to 3.2, not unless I reboot anyway.
Any thoughts, or even better: fixes? Thanks!
In some roms you have to set the battery usage of each app to the performance/benchmark setting. And in newer versions of miui you can set battery mode to performance in settings. That allows full cpu performance.
Otherwise the OS throttles the cores whenever it sees fit to do so.