Here are my current stable settings:
SetCPU
Min: 100mhz
Max: 1000mhz
Governor: Ondemand
Profile: Screen Off
--Min: 100mhz
--Max: 200mhz
--Priority: 100
--Governor: Ondemand
Tegrak:
Governor: Ondemand
Scaling: 100-1000mhz
Optimization:
--200mhz Core Voltage: 1025mv
--100mhz Core Voltage: 925mv
Both SetCPU and Tegrak are running side by side.
No random reboots for over a week.
Battery should last between 20-25 hours with normal usage.
Certain phones might need a higher voltage, you may need to do some experimenting to get things stable.
Old text
Anyone experiencing random reboots should try using SetCPU or Tegrak to set the CPU to 1000mhz-1000mhz instead of 100mhz-1000mhz.
I was previously getting 3-4 reboots per day. I set my CPU to 1000mhz-1000mhz using Tegrak four days ago and have not had a single reboot since.
Sure, my battery only lasts about 10 hours vs 20 or so, but at least I can rely on my phone.
Of course I could just be lucky, and who knows it might just randomly reboot any time now.. So, obviously there is no guarantee it will work for anyone else.
Just as a note I also tried 200-1000 and 400-1000, but still had random reboots every few hours.
I am currently testing 200mhz-200mhz with the screen off and 1000mhz-1000mhz with the screen on using SetCPU. I will update this thread in a few days or if it randomly reboots.
Update: 200mhz during screen off causes the phone to not wake up (happened three times). I'm currently testing 400mhz.
Update 2: I got a random reboot last night while asleep using 400mhz. I will see if it continues.
Update 3: Got another reboot at 400mhz. I am now testing 100mhz-1000mhz at 1.275v Core and 1.100v Internal for all frequencies, this should rule out any voltage issues.
Update 4: Made a spreadsheet with my findings, it does not seem to be a voltage issue.
Update 5: Scratch that, I have been using a [email protected] screen off profile for the last 20h... No black screen of death or random reboots. Next up is [email protected]
Update 6: [email protected] is unstable, rebooted after 3 hours. Testing [email protected], 6 hours in and no reboots yet.
Update 7: [email protected] seems to be stable, 24 hours and no reboots yet.
Old text
Click to expand...
Click to collapse
Here is a spreadsheet of my current findings.
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, but for some odd reason this (seems to have) fixed it for me. Although, on EG22 I also got a lot of random reboots, so maybe I have a different issue.
I did not get reboots on ED12, EE03, or EF02..
EG22, EH06, and EH17 randomly reboot for me.
I thought it might be similiar to the sleep of death phones would get going from 100 Mhz to deep sleep and also tried boosting to 200 Mhz on EH17 but it didn't help. It may be related and your discovery may aid Devs in fixing the problem If it is still there when source is released.
Sent from my SPH-D700 using XDA App
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
xopher.hunter said:
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1 That's what I think.
That would explain why my phone never reboots with the screen on.
I think we may be onto something in this thread.
Sent from my SPH-D700 using XDA App
Agreed. My phone has always randomly rebooted when the screen is off. I set the minimum to 400 Mhz as well. Will let you know what goes down.
Someone should point the SamSprint devs to this thread lol. That would be amusing if it was in fact the problem/solution to random reboots.
Sent from my SPH-D700 using xda premium
Ok, so far 400mhz screen off has been stable, 12:56 on battery, and 1:01 screen on time.
I noticed something.. Here is what CPU Spy says:
1000mhz: 00:55:03
400mhz: 1:35:09
Deep Sleep: 9:22:42
I reset the stats once, which is why 1000mhz is 6 min different from the screen on time.
The phone was asleep for 11:55, but it was only in deep sleep for 9:22, what this tells me is when the screen is off and the phone needs to "do something" (I have Skype open 24/7, and 3 accounts in k9)it will jump up to 400mhz (or normally, anywhere between 100-1000mhz) for a time until it is finished, and then drop back into deep sleep.
It might be worth a try to bump up the voltage for 100mhz and 200mhz and see if that helps anything.
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
If its really this simple as far as clock and voltage how the hell does Samsung not find that.
Sent from my SPH-D700 using xda premium
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
ss4rob said:
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
Click to expand...
Click to collapse
SetCPU is free for xda members
Sent from my SPH-D700 using Tapatalk
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
radugb said:
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
Click to expand...
Click to collapse
What scaling are you using?
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
omair2005 said:
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
Click to expand...
Click to collapse
Good catch. Here are the voltages on EH06 (as reported by Tegrak):
1000mhz
Core Voltage: 1275mv
Internal Voltage: 1100mv
800mhz
Core Voltage: 1200mv
Internal Voltage: 1100mv
400mhz
Core Voltage: 1050mv
Internal Voltage: 1100mv
200mhz
Core Voltage: 950mv
Internal Voltage: 1100mv
100mhz
Core Voltage: 950mv
Internal Voltage: 1000mv
Could someone list out the stock voltages on EC05?
Lord-Anubis said:
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
Click to expand...
Click to collapse
That is what I thought at first... But then I tried the EF02, and EE03 modems and still experienced reboots (I am currently on the EE03 modem).
poit said:
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
Click to expand...
Click to collapse
While this is true (for now) it could lead to a more viable fix. If the voltage actually is lower in GB, that could be at least part of the problem.
I have Exynos note 3 SM-N9000 . It's been a month since the purchase. I have already rooted the phone and knox is tripped.
I have been experiencing battery drain , so i looked up my cpu consumption , it was running on 1900 for the maximum time , there are no apps consuming such cpu load. My friend have the same mobile , when i checked with him, his cell was ruuning on 600 Mhz for max time.
Everything is stock, no custom rom .
Is there a solution to it , Can anyone help ?
Has no one experienced this problem???
Dear users of the forum
I am very worried about rapid discharge sine Z9 mini phone
If you do not use the Internet the phone behaves with dignity
But it is worth it to the Internet and download the client social network Vkontakte - here right away we decrease interest charge.
Through the program Kernel Adiutor I changed frequency: c 800 -1436 at 400-1133, set Scheduler Ondemand. Bates GPU frequency from 533 to 400 (because the standard is always working frequency of 533 regardless of the load). Launching any tweaks to the kernel, the performance of the battery and the like, and the phone began to live a little longer.
But for example a game like World of Tanks Blitz eats battery all in 40 minutes - my colleagues at work are the result of one hour and a half with batteries 2200 and phones that have 3-4 years (with bad batteries that must be replaced) and then 3050 mAh spent 40 minutes.
With offline 4pda curator of one of the others he said he compiled the kernel by phone 410 snapdragon is not 64 bit and 32 - and everything was just better (and at the moment is trying to do the same for about 615 snapdragon for nashago phone still will not make unnecessarily . he did not have much time available.
And in consequence, any firmware ported keeps the battery as little as they use official sources supplied by ZTE.
I am sure that my question is not the first of its kind, and on the processor and can have a solution
Must be some problems in phone
Hey if it apps.....first of all uninstall xender.....it autostarts and drain battery even in standby or otherwise root your device and install root booster(dominik Nozka)(free but in app purchase) in playstore and purchase the extreme modes.......(0.99$ only)
But of it is hardware i guess change the battery as it is nearly dead.....this happens even in my dad's old symbian-java phone(7yrs old but still on stock battery. Which was with handset suffering drom rapid discharge.)
Hey all,
I was looking around in aida64 and I saw that the big core is always active. At idle it's staying at 633mhz. Only after boot I saw "sleeping" , but after few mins it just stayed at 633mhz. More people experiencing this? I'm on the second 7.1.2 beta.
Screenshot: https://s11.postimg.org/d2a4kcyir/Screenshot_20170324-090259.png
I'd like to hear your thoughts!
It seems that when they're stopped or sleeping, that's because of thermal throttling: https://forum.xda-developers.com/nexus-6p/help/4-cores-allways-stopped-whats-t3390543. So I guess they should always be running and not sleeping/stopped. If not, your phone runs too hot.
Would be great if someone can give a clear answer on this!
When the phone reboots it works hard to start the OS and apps and therefore has to thermal throttle to cool the cpu down. Once it fully boots and the cpu load is lower it cools down and the big cluster comes back online and idles at 633, the stock big cluster governor setting.
hawkswind1 said:
When the phone reboots it works hard to start the OS and apps and therefore has to thermal throttle to cool the cpu down. Once it fully boots and the cpu load is lower it cools down and the big cluster comes back online and idles at 633, the stock big cluster governor setting.
Click to expand...
Click to collapse
Thanks for the info. But what's up with this comment on Reddit then? "my nexus 6p is working properly on 7.1.2 apparently, my uptime is ~189 hours, 4 cores are on low frequency 384 mHz and the other 4, the A57s are sleeping, see the screenshot below.
http://m.imgur.com/UZhZxd8". More people are reporting this . So it seems that for some people it's idling at 633mhz and for some people it's sleeping.
Hi all,
I have cpu z installed and I'm not rooted. It generally uses all 8 cores but when I accidentally opened it I saw that it was only using 4 cores. I decided to restart and it is still using 4 cores. Is this normal because my g5 plus always uses all 8 cores.
Your in low power or battery saver mode... look at the battery symbol.. I can't remember if it kicks in at 5% or 15% battery automatically, then turns off when you connect the charger... It sometimes takes a few minutes for everything to kick back in. I would bet after getting a decent charge it was back to normal?
There is also a issue with Nougat at newer reporting CPU usage incorrectly even in rooted devices... been talked about a lot, something in the stock Moto firmware (or maybe that was a different Moto, I get them confused sometimes).
Ok thanks. Apparently cpu z was wrong.
the cores are reduced to 4 when u are on battery saver.
On thanks. The weird part was I didn't turn the battery saver.
DarthMaul14 said:
On thanks. The weird part was I didn't turn the battery saver.
Click to expand...
Click to collapse
It's automatic at a certain battery level by default.
Oh ok. Does the same thing apply for quad cores and hexacores.
DarthMaul14 said:
Oh ok. Does the same thing apply for quad cores and hexacores.
Click to expand...
Click to collapse
It will throttle them, although the exact implementation varies somewhat depending on the actual processor. littleBIG architecture tends to be that the BIG cores get shutdown, on more standard architecture like the SD625 they will get throttled to 50-75% of maximum speed, and others may just get a couple random cores disabled, it depends on the CPU and how Qualcomm/MediaTek/whoever engineered it.
Ok thanks!