Related
I just rooted by buddy TB and from time to time it lock's up on me. I read that I should stop using my task-killing app (Andrio Boost -Android Optimizer) and wait see if it happens again.
I have been removing the battery in order to unlock the phone. Has anyone else exprience this same issue...help?
What ROM are you running? Sounds like it's time to wipe via clockworkmod and start fresh.
Could be an issue with your kernel speeds or undervolting as well. If your lower clock levels are too low or your upper levels don't get enough voltage you could experience crashes.
I am currently using "Stock Rom" and this happen after watching a movie and listening to music.
These are my current SetCPU settings:
Overall 1024 max 245 min
Profiles
In call - 768 max / 245 min
Batt <25% - 768 max / 245 min
Temp >50.0 - 368 max / 245 min
Screen Off - 245 max / 245 min
Charging - 1024 max / 1024 min
Battey <10% - 245 max / 245 min
Thank you advance!
Moyeto said:
Stock Rom and this happen after watching a movie and listening to music.
These are my current SetCPU settings:
Overall 1024 max 245 min
Profiles
In call - 768 max / 245 min
Batt <25% - 768 max / 245 min
Temp >50.0 - 368 max / 245 min
Screen Off - 245 max / 245 min
Charging - 1024 max / 1024 min
Battey <10% - 245 max / 245 min
Click to expand...
Click to collapse
Try changing some of your min settings to a bit higher, like 368, to see if it fixes the issue. Also, are you using a kernel that supports speedtweak.sh such as Imoseyons? I believe these kernels need to have a setting changed in the speedtweak.sh to allow the use of SetCPU.
On a side note, you may wana check that Charging profile you have as well. That will be one toasty phone if you have it charging and the CPU maxed at the same time.
Thanks! Please see my SetCPU settings; are they close to being correct?
They arent bad you just need to make sure that you have the correct logic there when it comes to the level of importance of each setting.
For example this is how i would list the importance:
Temp >50.0 - 368 max / 245 min - 100
Battery <10% - 245 max / 245 min - 90
Battery <25% - 768 max / 245 min - 80
In call - 768 max / 245 min - 70
Charging - 1024 max / 1024 min - 60
Screen Off - 245 max / 245 min - 50
This way you have the temperature profile as the most important so regardless of what is going on, such as charging, the phone will lower the processor speed to account for dangerous temperatures. You need to have the battery profiles in this order as well because if the Battery < 25% has a higher importance than the Battery < 10% then it will never get to the Battery < 10% profile, it will always hit the Battery < 25% profile first, test as true, and you wont ramp down your phone as much as you wanted to in order to save battery.
Roger!! I did not pay attention to the order of the profiles. Thank you, this makes sense.
Should I still freeze my task killing application?
Sent from my ADR6400L using XDA Premium App
Automatic task-killers are redundant in Android 2.2 and higher so you can go ahead and get rid of them.
Your profiles look good but go ahead and drop the Battery < 10% importance down to like 99 or something because you dont want to have two profiles at 100. It could cause issues.
Should I still freeze my task killing application?
Sent from my ADR6400L using XDA Premium App
Roger that! Thanks.
hi guys..,
pls share ur setcpu settings here...so that we can get some idea...we can choose the better ones...
To start with..,
i 've kyrillos rom 9.2 oc.., g3mod v2.2.2
My Settings:
- Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
- Profile (1): In call: 83min, 400max, Scaling: Ondemand, Priority:100
- Profile (2): Time profile: 1AM - 7AM (here put the time you sleep), min/max 83MHz, Scaling: Powersave, Priority: 99
- no voltage profile...
but it lags a bit at times....
pls share ur setcpu settings....here...
G3Mod 2.2.2.
Main profile : - Min 83, Max 800, Profile Lagfree.
Profiles, priorities in descending order.
1) Battery<15 : 400 Max 83 Min, Powersave.
2) Screen off : 400 Max 83 Min, On Demand.
3) Charging : 600 Max 83 Min, On Demand.
4) In call : 400 Max 83 Min, On Demand.
Kyrillos 9.3 and G3Mod 2.2.2 OC
main profile: 400-1000 - ondemand
time profile (00:00-06:59): 83-200 - conservative (priority: 100)
screen off profile: 400-500 - ondemand (priority: 99)
no undervolting and other settings, just sampling rate set to: 10000
guys...,only a few reply...
i don't know...why nobody show any interest to share ur setcpu settings...
LooksLikeSmart said:
guys...,only a few reply...
i don't know...why nobody show any interest to share ur setcpu settings...
Click to expand...
Click to collapse
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
lovelyprincess said:
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
Click to expand...
Click to collapse
I dont think so... It will just shorten the life of the cpu.
Sent from my GT-I9003 using xda premium
hi bscraze.,
i've posted my setcpu settings above...is it safe...?? whether i've to change max to 800Mhz...what about scaling...conservative or lag free..
pls post urs if u have...
My profiles for i5801:
Main tab - 200~700mhz on demand/lag free both works for me
Charging - 300~1200mhz on demand
Screen off - 83~500mhz on demand
Time 1am to 5.30am 83~83mhz powersave
You can try my profile, may work, may not but i advise you to change to 800mhz for your main tab.
Sent from my GT-I9003 using xda premium
lovelyprincess said:
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
Click to expand...
Click to collapse
. No it won t.
hi..,dhirend_6d
i've set cpu settings used for 3 months...Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
no harm done...everything working fine...
but..is it safe...to continue always...? or
whether i've change it to 800MHz as suggested by bscraze...
LooksLikeSmart said:
hi..,dhirend_6d
i've set cpu settings used for 3 months...Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
no harm done...everything working fine...
but..is it safe...to continue always...? or
whether i've change it to 800MHz as suggested by bscraze...
Click to expand...
Click to collapse
You should keep it 800 max for normal usage because keeping high frequencies shortens processor life. Use higher frequencies(1000+) only when needed like when playing games and etc. At 800, in normal usage, all works smooth. Note I use lagfree as main profile. I suggest you also try lagfree once.
Kyrillos 9.3 and G3Mod 2.2.2 OC
main profile: min 83 - max 700 - ondemand
In call: min 83 - max 400 ondemand(priority: 100)
screen off profile: min 83 - max 400 - ondemand (priority: 98)
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
cecenac said:
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
Click to expand...
Click to collapse
They are perfect. You don t have to worry about anything with those settings. If you use 1000+ frequencies for longer periods continuously then it may reduce your CPU life. Use only when required.
cecenac said:
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
Click to expand...
Click to collapse
Cpu chips are made to last at least 5 yrs so dont worry about it and like what dhirend said, only if you keep it at high frequencies for long times will it dmg the cpu more.
Sent from my GT-I9003 using xda premium
Hi, I have Kyrillos 9.4 & g3mod 2.2.2 OC.
My settings:
Main: 83-700Mhz ondemand
InCall 83-600Mhz ondemand
Screen Off 83-400Mhz ondemand
and I my i5800 freezes 3 times per day.
I don't have game, only necessary aps.
Please help me.
lefar333 said:
Hi, I have Kyrillos 9.4 & g3mod 2.2.2 OC.
My settings:
Main: 83-700Mhz ondemand
InCall 83-600Mhz ondemand
Screen Off 83-400Mhz ondemand
and I my i5800 freezes 3 times per day.
I don't have game, only necessary aps.
Please help me.
Click to expand...
Click to collapse
try cm7 marcellusbe or kyrillos, then you will never have a freeze again!
I'm on Kyrillos v9.4, kernel G3Mod v2.3
83Mhz, Max 800-1200MHz, Scaling: Ondemand
In call: 83min, 400max, Scaling: Ondemand, Priority:100
Time profile: 1AM - 7AM (here put the time you sleep), min/max 83MHz, Scaling: Powersave, Priority: 99
Screen off: 83min, 400max, Scaling: Ondemand, Priority:98
my battery lasts three days with normal/heavy usage
Hi,
I'm on kyorarom 0.5.1 with kernel G3MOD-Kyorarom-0.5.0
main: 83 - 800 lagfree
1. in call: 300 - 800 lagfree (if less I have to wait a lot to see the screen waking up) priority 100
2. screen off: 83 - 600 lagfree priority 100
3. charging: 83 - 900 lagfree priority 99
no freese, no FC, only one thing: when I wake up the phone from screen off I sometimes see the last screen before the lockscreen appears and I tried to change the off screen values and it was all the same...
baterry lasts at least 3 days with some wifi use, low BT use, some apps and games, but a lot of phone calls and sms
Everybody over here just check out this(forum.xda-developers.com/showthread.php?t=1369817) thread to understand the things better. (about governers, modules, etc) . Must see thread!!!
What are people using for their setCPU settings? I'm just now rooting and will be installing this to help with battery life. Unless for some reason this isn't necessary on the S3. It was essential on the S2 (in my opinion) to keep my battery life going longer.
I'll start it off apparently!
Not messing with any governor, just the profiles.
Charging - CPU can run at 1512 max, 594 min - priority 100
Screen Off - CPU max of 594, min 384 - priority 99
Battery <80% - CPU max of 1242, min 594 - priority 80
Battery < 60% - CPU max of 810, min 384 - priority 60
Battery < 50% - CPU max of 594, min 384 - priority 50
No profile is exclusive
stalked_r/t said:
I'll start it off apparently!
Not messing with any governor, just the profiles.
Charging - CPU can run at 1512 max, 594 min - priority 100
Screen Off - CPU max of 594, min 384 - priority 99
Battery <80% - CPU max of 1242, min 594 - priority 80
Battery < 60% - CPU max of 810, min 384 - priority 60
Battery < 50% - CPU max of 594, min 384 - priority 50
No profile is exclusive
Click to expand...
Click to collapse
How well does it work if you're playing music and the screen is off?
I use 384 for both max & min when screen off and it works just fine for music player I have.
Sent from my SCH-I535 using Tapatalk 2
I don't have any music on my phone. I just use Pandora for everything, though i should probably put something on my phone.
stalked_r/t said:
I'll start it off apparently!
Not messing with any governor, just the profiles.
Charging - CPU can run at 1512 max, 594 min - priority 100
Screen Off - CPU max of 594, min 384 - priority 99
Battery <80% - CPU max of 1242, min 594 - priority 80
Battery < 60% - CPU max of 810, min 384 - priority 60
Battery < 50% - CPU max of 594, min 384 - priority 50
No profile is exclusive
Click to expand...
Click to collapse
What at are you using to set all this? Have you noticed any improvement in battery life of issues with apps running/ starting/ crashing??
ssnapier said:
What at are you using to set all this? Have you noticed any improvement in battery life of issues with apps running/ starting/ crashing??
Click to expand...
Click to collapse
I just set this up this morning and my phone has been sitting in my dock at work, so i can't say for sure about battery life. As for apps. I've not noticed a single problem. Again, I rooted my phone last night, so I don't have a ton of apps on my phone. Currently I have
Waze
Pandora
One More Clock
SetCPU
Betterbatterystats
MetroStation Icon Pack
Apex Launcher
NFC Task Launcher
Mynetdiary
Rom Manager Pro
Zedge.
Most of those are supporting apps. so it's hard to say if anything is flaking out yet. I'll slowly add more apps. I'm going to start a thread about known battery drain apps so we can start identifying those.
My Settings
Here are some settings I use that seem to work well for me. Id say these settings aren't the most conservative but they aren't battery hungry either. I didn't mess with any of the governors or voltages I just simply added these profiles to control my leankernel. Hope this helps! -Cheers
Screen Off
810 max
384 min
OnDemand
Priority 58
Charging
1900 max
384 min
OnDemand
Priority 54
Battery < 60
Condition Screen On
1026 max
384 min
OnDemand
Priority 53
Battery < 40
810 max
384 min
OnDemand
Priority 52
Gaming
Condition Screen On
1900 max
1026 min
OnDemand
Priority 57
Web
Condition Screen On
1512 max
1026 min
OnDemand
Priority 55
Default
1900 max
384 min
OnDemand
Dont click "make this profile exclusive"
*This gives you a default profile notification
[PHONE] Samsung Galaxy S III i535
[ROM] CM10 M1 9/11 w/ 7/26 GApps
[KERNEL] imo leankernel 0.13
[MODEM] I535VRLG7
[EXTRAS] turning heads with Google Wallet
Set CPU
Do these settings still work good for you? I entered them into my SG3 so will see how it goes for the next few days. I am really looking for battery life more than anything.
thanks
THISisTIG said:
Here are some settings I use that seem to work well for me. Id say these settings aren't the most conservative but they aren't battery hungry either. I didn't mess with any of the governors or voltages I just simply added these profiles to control my leankernel. Hope this helps! -Cheers
Screen Off
810 max
384 min
OnDemand
Priority 58
Charging
1900 max
384 min
OnDemand
Priority 54
Battery < 60
Condition Screen On
1026 max
384 min
OnDemand
Priority 53
Battery < 40
810 max
384 min
OnDemand
Priority 52
Gaming
Condition Screen On
1900 max
1026 min
OnDemand
Priority 57
Web
Condition Screen On
1512 max
1026 min
OnDemand
Priority 55
Default
1900 max
384 min
OnDemand
Dont click "make this profile exclusive"
*This gives you a default profile notification
[PHONE] Samsung Galaxy S III i535
[ROM] CM10 M1 9/11 w/ 7/26 GApps
[KERNEL] imo leankernel 0.13
[MODEM] I535VRLG7
[EXTRAS] turning heads with Google Wallet
Click to expand...
Click to collapse
How about this over clocking going on here? So I finally rooted, got a ROM, flashed a kernel.. Then bought SETCPU and turned it up to 1.9ghz. This seemed to work right well, but then I discovered a tool from chainfire and found that it wasn't sticking. So I was told about and edited this thermald.conf file.
But I wanna know, what temp was it that caused this to occur, and what I have just changed?
I've overclocked 3 phones now (8125/fuze/inspire) but none were this nice (dual core for example.) and this one gets warm. But I cannot tell how warm? And now I've even changed something and don't even know what. And it was related to warm.
Tl;dr how hard is are you Pushin yer phone?
The change:
sampling 5000
[pa_therm0]
sampling 5000
thresholds 70 80 90
thresholds_clr 65 75 85
actions none none none
action_info 0 0 0
[tsens_tz_sensor0]
sampling 1000
thresholds 50 65 75 80 99 102 105
thresholds_clr 40 62 72 77 96 99 102
actions cpu cpu cpu cpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu+shutdown
action_info 1809000 1242000 1134000 918000 594000+255+0+0+0+200000000 384000+30+1+3+1+27000000 384000+30+1+3+1+27000000+5000
[tsens_tz_sensor1]
sampling 1000
thresholds 75
thresholds_clr 72
actions none
action_info 0
[tsens_tz_sensor2]
sampling 1000
thresholds 100
thresholds_clr 80
actions none
action_info 0
[tsens_tz_sensor3]
sampling 1000
thresholds 75 78 81 84 87 90
thresholds_clr 72 75 78 81 84 87
actions cpu cpu cpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu cpu+lcd+flashlight+battery+vibrator+gpu+shutdown
action_info 1242000 1134000 918000 594000+255+0+0+0+200000000 384000+30+1+3+1+27000000 384000+30+1+3+1+27000000+5000
[tsens_tz_sensor4]
sampling 1000
thresholds 50 65 80 86
thresholds_clr 40 62 77 84
actions gpu gpu gpu gpu
action_info 400000000 300000000 200000000 27000000
Kom op nu
my phone keeps on overheating as I am playing clash of clans for a prolonged period of time. is there any way to fix it? i am running purity rom with franco kernel.
onecrzyasian said:
my phone keeps on overheating as I am playing clash of clans for a prolonged period of time. is there any way to fix it? i am running purity rom with franco kernel.
Click to expand...
Click to collapse
describe "overheating". what cpu temp is it reaching?
Hi,
Another one...
You have a quadcore at 2,26 Ghz device, under certain conditions (heavy games, browsing in 4g, long run heavy tasks, etc...) it's absolutely normal that the phone runs hot... And you sais it by yourself "I am playing clash of clans for a prolonged period of time."...
In any case there is a thermal protection called thermal throttling that reduces the CPU freq, the number of cores online and the screen brightness when the CPU (and/or battery) reaches some different temperature ranges, so no worries...
And even if Franciscofranco modified the thermal management, the thermal throttle is always present (you can also adjust it to reduce the heat by decreasing the CPU temp limit before thermal throttling).
But guys... in all scenarios there is the thermal throttling, and it does its job when needed. In extreme conditions the phone shutdown itself to prevent any damage. This CPU can handle more than 100 °C. Use your phone as normal, as you need... Or don't use GPS, don't play games, don't run benchs...
As an example on how thermal throttling works:
Code:
sampling 5000
[battery_LCD_monitor]
algo_type monitor
sensor batt_therm
sampling 10000
thresholds 100000 340000 350000 360000 370000
thresholds_clr 50000 330000 340000 350000 350000
actions override override override override override
action_info 10000 7500 5000 2500 0
[SKIN_THERMAL_management_1]
algo_type monitor
sensor xo_therm_pu2
sampling 10000
thresholds 40000 42000 44000
thresholds_clr 38500 40500 42500
actions cpu+lcd cpu+lcd cpu+lcd
action_info 1958400+229 1574400+204 1190400+178
[battery_monitor]
algo_type monitor
sensor batt_therm
sampling 10000
thresholds 480000 550000
thresholds_clr 460000 500000
actions battery battery
action_info 2 3
[CPU0_MONITOR]
algo_type monitor
sensor cpu0
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU1_MONITOR]
algo_type monitor
sensor cpu1
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU2_MONITOR]
algo_type monitor
sensor cpu2
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU3_MONITOR]
algo_type monitor
sensor cpu3
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[HOTPLUG-CPU1]
algo_type monitor
sensor cpu1
sampling 65
thresholds 105000
thresholds_clr 85000
actions hotplug_1
action_info 1
[HOTPLUG-CPU2]
algo_type monitor
sensor cpu2
sampling 65
thresholds 105000
thresholds_clr 85000
actions hotplug_2
action_info 1
[HOTPLUG-CPU3]
algo_type monitor
sensor cpu3
sampling 65
thresholds 105000
thresholds_clr 85000
actions hotplug_3
action_info 1
[PID-CPU0]
disable 1
[PID-CPU1]
disable 1
[PID-CPU2]
disable 1
[PID-CPU3]
disable 1
[PID-POPMEM]
disable 1
[SS-CPU0]
algo_type ss
sampling 65
sensor cpu0
device cpu
set_point 80000
set_point_clr 55000
[SS-CPU1]
algo_type ss
sampling 65
sensor cpu1
device cpu
set_point 80000
set_point_clr 55000
[SS-CPU2]
algo_type ss
sampling 65
sensor cpu2
device cpu
set_point 80000
set_point_clr 55000
[SS-CPU3]
algo_type ss
sampling 65
sensor cpu3
device cpu
set_point 80000
set_point_clr 55000
[SS-POPMEM]
algo_type ss
sampling 65
sensor pop_mem
device cpu
set_point 80000
set_point_clr 55000
time_constant 16
It's a quadcore at 2,26 Ghz completely enclosed without any additional cooling system, so...
It remembers me the Nexus 4 all these threads/questions about "pseudo" heating/overheating...
Like simms22 said check your temperatures and provide them to have an approach a bit more real, because "it feels hot", "it is overheating", etc... is very subjective (for example I go outdoor with a 2 °C room temperature, I take my phone stays indoor and I feel it "hot", I check the CPU temperature and it's at about 30 °C...if you know what I try to say even if it's not your case here but it's a general idea).
Also you provide more information like overclock? Undervolt? Governor (even if in Franciscofranco kernel there is only Interactive and Performance)?
I am not sure what the temp was before it shut down, but i shall try lowering the throttle temp
onecrzyasian said:
I am not sure what the temp was before it shut down, but i shall try lowering the throttle temp
Click to expand...
Click to collapse
Re,
Because your phone shutdown when you were playing? You did not mentioned it in the OP... (it could be caused by another things too, undervolt, kernel panic, etc...).
Before shutdown, it's the ultimate thermal protection, the CPU freq decreases according to different CPU/battery temperatures to cool down the CPU (thermal throttling)... Post a last_kmsg if you have a hard-reboot to see... Post it in the kernel thread, here, or in this thread: http://forum.xda-developers.com/showthread.php?t=2532422.