Hello, i have my s3 overclocked and undervolted, at most stable values in the overclocking thread.
my frequencies goes at Min 1.1ghz Max 1.8ghz.
the problem is, when i launch a heavy app like a game (ex: ppsspp) the governor works 30 seconds, then swap to the previous. in other words
if i have pegasusq active, when i launch the app 30 seconds later swap to powersave governor, i try with the performance governor, and was the same, 30 seconds later works performance governor and then swap to pegasusq... i dont know what is happen...
someone can help me?
PD: sorry my bad english :s
#Push
Please anybody? i really need help woth this issue D:
Related
I have made a lot of searches and read a lot about battery calibration... and of course i know what the hell is kernel panic, its definition and its symptoms.
However I still have some confusions and I hope some of you may be able to solve them
Maybe some of them are noobie questions but I honestly sorry for that also this may help others who has these confusions too
My situation:
The system stats are shown in my signature.
on 5/9 I have flashed franco.Kernel v19.4 bfs and then started a lot of OC tests,
finally I was stable on stress test (SetCPU) 729mhz for 2 hours non-stop,
and also I used the phone stably for over 24 hours without reboot.
However I faced a problem which is related to Darktremor scripts.
I used 2 weeks to solve it and finally it is gone now.
I started battery calibration which is the final process before I use my phone normally in my daily lives.
But in these two days, my kernel panics after ~4 hours of usage of 729mhz max CPU frequency.
without the need of advice, surely i have downclocked to 710mhz max and its all good. but however i am super curious about why 729 becomes from stable to unstable before and after.
1) Does battery stats related to kernel panics in ANY extent? if yes, how?
Ignore all questions under 1 if the answer is No.
1.1) Does wiping battery stats before flashing a kernel helps you OC higher?
1.2) Does wiping battery stats before flashing a ROM helps you OC higher?
1.3) Does wiping battery stats (for calibration purposes) has possibilities to produce kernel panics?
2) Why is there a sudden drop of battery level (~4-5%) after kernel panics?
3) Is there any other possible causes of kernel panics BESIDES overclocking too high?
3.1) *2sd scripts?
3.2) ext4 barrier = 0?
3.3) inputting EXT4 data writeback?
(tune2fs -o journal_data_writeback /dev/block/mmcblk0p2)
4) Is SetCPU the problem?
Some says "dont use SetCPU when you can overclock using CM7 settings."
Is that true?
5) BESIDES the max speed, does it also depends on Governors?
Ignore powersave governor or others which forces the clock to the minimum frequencies.
So, is there any difference between setting the same maximum speed, different governors?
(for example) Would smartass gives a panic at 729mhz but ondemand doesnt?
6) Does the "change of frequencies" gives easier kernel panics?
Situation A: 729min, 729 max
Situation B: 480min, 729max
In situation B, the system makes the frequencies change due to load, means it may switch from 480 -> 600 -> 729 -> 710 -> 691 -> 480 etc.
so does this "change of frequencies" makes the kernel loads more and finally gets it to panic?
Thanks for your time reading and answering my questions!
Please just quote one of them if you would just like to answer one of the above
Thank you very much!
1) no.
2) It happens when u remove the battery and put it back.
3) There are some strange reports of kernel panic at 600Mhz which are weird. Sometimes Roms/kernel play a part(unknown).
4) it is because you can overclock in Cm7 settings menu, so no need to install another app such as SetCpu
5) Maybe, a governor who stays more on the highest frequencies i think are easy to panic because hardware can't handle it.
6) for me, i would say situation A would be easier to kernel panic, as it is constantly on the highest frequency and stressing your cpu too much that it can't handle it.
Since you get stable at 729mhz for 2h and panicked when 4h of use, that means the cpu can't handle 729mhz for above 4h.
@terratrix
thanks for your reply!! at least im not using my stupidity to wipe battery stats and trying to avoid kernel panics, lol.
@info update and conclusion after 1 more day of testing
And there, after some readings on the forum and the experiences myself, i think i have found the critical point already - QUESTION NO.5
Conclusion : kernel panics are related to governors, at least, our new amazing profiled one - SmartassV2!!
On the thread of Franco's .35 v1 kernel, there are some users reporting the panic issues faced with ONLY SmartassV2.
And me myself, has joined the party as well
Smartass(v1) has been my best bud all the time at 729mhz or even higher for more than 6 months. And when I left it and went to choose his next generation, my phone got a generation gap with Mr.V2, lol.
On my phone: (Franco.kernel 19.4bfs and no any reflash or stuffs between testings)
SmartassV2 ---
very unstable panics AND random shutdowns at random times
729mhz - sometimes 2 hours, sometimes 4 hours
710mhz - yeah I justnow kernel paniced with this also, you know how long after boot? 30minutes!!!
Why 30minutes? I suspect that it.is related to franco's network speed hack. I'm on EDGE data plan and because of Franco, I can enable HSDPA with 4x more speed.
On 710mhz, my phone was stable for over 8 hours with EDGE on (I intended to save battery), but after a reboot (manual one for some other purposes) I started to use (the hacked) HSDPA. After 30 minutes, panic. I remembered when I was at 729 on smartassv2 I panicked after 3 hours and at that time I was using HSDPA too.
Smartass (v1) ---
Well now I'm on smartass v1 at 729mhz stably typing this message. Funny huh...?
Results:
Franco's network speed hack
OR
3G network/HSDPA network
OR
Even just because of specific phone hardwares
IS NOT COMPATIBLE WITH THE ALMIGHTY SMARTASS-V2 GOVERNOR AND WOULD RESULT IN KERNEL PANICS AT THE FREQUENCIES WHERE THE PHONE CAN BE STABLE WITH OTHER COMMON GOVERNORS.
If I am wrong or you can confirm this by testing yourself, please let me know!!! thanks and hope I have provided some useful information
Goodnight and I'm going to continue working with my old friend smartass-v1 despite v2 has better profiling tweaks, lol
Sent from my LG-P500 using XDA Premium App
Dude, as i had mentioned earlier in franco's thread, that it had to do with the governors... cause i usually try and find out the cause of the issue myself before posting a bug..
SO all i tried were playing around with the performance settings... and i start off with changing the governors... the best targeted experimental ones are MINMAX (my personal fav), SMARTASS, SMOOTHASS (now removed but one AWESOME governor), and INTERACTIVE-X (rewritten by franco i guess).... About the frequencies... from what i have observed so far apart from reading stuffs is that, at 729 Mhz our optimus DOES pretty much stay stable even in the ****TIEST devices.. LOL i can say that cause we indians get the crappiest hardware of all... the point is... if you got a kernel panic at 729, it is most likely that you would get it again at 600 Mhz too cause its not overclock related..!!!
Bottom-line: Avoid SmartassV2 unless your phone is made of the finest hardware i.e. you can easily overclock it to 806 Mhz (ive seen some users using it at this frequency without any issues at all .. :O ) Use Smartass older or Minmax instead...!! And avoid overclocking above 729..!!!
P.s.: mine works fine even at 768 BTW....
We have to wait for Franco's next release for more smartass2 updates
Sent from my LG-P500
SmartassV2 is kind of strange, at least in my phone. I notice my battery draining faster while I use it, and it's probably because it stays in the max frequency longer for some reason, despite screen off. I use NoFrills for my CPU setting and it has the ability to view stats, and when I'm using V2 it stays longer at the max than at the min (65 vs 35%). The opposite is true for Smartass v1, which to me makes more sense because my phone stays at standby more often than being used.
As comparison data, my phone with smartass v1 can typically be OCed up to 787 MHz. 748 MHz on v2 is stable, but I haven't extensively tested higher freqs.
I have a Indian phone , smartass v2 oc to 768 stable xD
Sent from my LG-P500
hey guys.
i have been wondering about this problem for a long time, and i could not find a solution to it. Thus, i wanted to ask you guys about it. The max i can overclock my phone to is 748. whenever i try to raise it to about 768 or 787, the phone will freeze and restart. is it due to the hardware limitations of my phone? or isit due to some software limitations?
Please help.
Just Hardware.
(I can overclock to 729 )
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
SacredGuy said:
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
Click to expand...
Click to collapse
I use the performance gov. and it's worked well.
SacredGuy said:
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
Click to expand...
Click to collapse
I use stock 2.3.3 v20g + franco kernel and set max clock at 729Mhz, sometimes it freeze, but normally work fine (with any gov).
Each CPU is a little different. My OV is stable at 600 with smartassv2 but once I step it up to 729 the phone will randomly freeze or reboot.
Sometimes you get a good cpu that can be OCed a bit, and sometimes you get one that can go no further then stock. If you can OC then consider yourself lucky.
Whenever you try to increase the max frequency beyond a certain limit the CPU can not handle that and tells the kernel about that and kernel starts to Panic... (reboots or freeze)
For example My phone remains stable upto 768 MHz (usually i keep it at 748Mhz....)
but if i increase it to beyond 806 MHz it starts to panic...
Hardware
Has differences on hardware, already tried with 2 differents P500, one could overclock to 768 Mhz, the other can reach 800Mhz without freeze.
karven said:
Has differences on hardware, already tried with 2 differents P500, one could overclock to 768 Mhz, the other can reach 800Mhz without freeze.
Click to expand...
Click to collapse
Since all the p500 have same hardware, they can be OC to same max frequency if they have same software config...
806! never freezes but she gets warm! can get over 40 celcius
EDIT
Mind you i only get about 16 hours of battery life LOL
shubhamjain001 said:
Since all the p500 have same hardware, they can be OC to same max frequency if they have same software config...
Click to expand...
Click to collapse
where did u get ur facts?
are u smart or just effin noob?
yours preferred governors????
actually the best one is....
Dude keep it around 652 and interactive otherwise UR Battery will drain fast
depends on ur ROM+kernel combo.
on oxygen v1.1 i smoothly ran on 480-768 and battery lasted around 2 days with average use.
Now on Cm7 nightly, equally smooth at 729-480 and battery is awesome too..
Overclock
Ohhh!!! lucky guys.. my phone only accepts 672Mhz at max or anything above that value leads to rebooting or freezing.
Rom: Cyanogenmod 9 (Android 4.0.3)[BETA4]
Kernal: Franco Kernal - 4
OC: 480/672 Max
I get 748MHz completely stable when pushing "performance" governor with franco #4.
But irrespective, this is not about bragging...one would see LITTLE real life difference (save for frying the CPU faster) going above 672MHz. Don't just look at synthetic benchmarks...feel your phone.
Oh...and it was mentioned multiple times that 600->806MHz uses the same voltage hence the same power consumption for Sidestep CPUs.
I am running max CPU @ 729 and it has been running smooth for days with no freeze/reboots, I also noticed having the Governer on Performance has helped my battery life and such, i havent noticed the phone getting any warmer whatsoever so no problems with heat, Also I am using a LG-P504 Optimus One which Ive heard is the final release for this phone, so maybe its more stable than the pervious versions.
My p500 can handle 768 max. With some kernels 787mhz. But i am running 245-710 with miui v4: lol:
Sent from my LG-P500 using XDA App
Yea mine can handle that too but it drains my battery faster I've noticed. So now I run Max @ around 720 which seems quite stable!! Only time I use the nitrous feature also is with playing more top end games which I otherwise wouldn't be able to play without really low fps.
Sent from my LG-P504 using XDA App
Im using cyanogenmod nightly 7.2.0 build 34 on 748 mhz with any governer and it's working very well.OC also depends on ROM's.each ROM has different capabilities to OC...
Hi guys, please can u tell me whats the best overclock for our U20i ? Most stable and fast, i **** battery life
thank u
--------> GingerDX v.029
--------> nAa kernel 14
!_XperiaFan_! said:
Hi guys, please can u tell me whats the best overclock for our U20i ? Most stable and fast, i **** battery life
thank u
--------> GingerDX v.029
--------> nAa kernel 14
Click to expand...
Click to collapse
As you mention :silly:
!_XperiaFan_! said:
Hi guys, please can u tell me whats the best overclock for our U20i ? Most stable and fast, i **** battery life
thank u
--------> GingerDX v.029
--------> nAa kernel 14
Click to expand...
Click to collapse
There is no definitive answer to that, because not all phones are the same quality... most of the time they will run fine on 729Mhz, but some of them even run on 800+ frequencies... It's a matter of trying out what works for you. (don't tick the 'set on boot' button until you are really really really sure your phone is stable at the frequency chosen, or it won't boot)
If you want the most responsive and snappy system, go for the performance-governor, it will put your phone on max-freqency whenever you do even the smallest things so it will usually complete tasks a bit quicker or have power left over to compensate for system-hickups.
My Setting
Min freq : 120 MHz
Max freq : 748 MHz
Governor : SmartAssV2
safe overclock.
I used D4's SIMPLE OVERCLOCK app and make two profiles for the powersave and task mode. And BOTH profiles use SMARTASSv2
POWERSAVE
MIN:19MHz
MAX:480MHz
TASK MODE
MIN:245MHz
MAX:748MHz
SMARTASSv2 governor to have your frequency to the MIN when it's on standby and goes half way between your MIN & MAX and can go MAX if is still in need of higher frequency.
While i knew the official sony update slows the phone down i tried it anyway and i really regret doing that. The phone was really slow. So after quite some time spent rooting and flashing it with a custom kernel I overclocked it. The problem now is that SetCPU ignores what I set to minimum. Im using the smartAssv2 governor (it is the same with all the other governors) and when I'm not using any apps It quite oftenly sets the cpu to 200mhz slowing the phone to a crawl. So is there a way to fix this and make it so that it doesn't clock it at 200mhz at random ?
try no frills cpu controller or rom toolbox pro to overclock
Hi
Can some one help me , i will like to know witch should be the bes cpu settings?
my cel. only have as max1512mhz , and a freind told me that try to run as min less than 500 mhz.
But on the governor witch should i select interactive , conservative, ondemand, userspace, powersave, or performance?
and on Io scheduler noop , deadline , row or cfq ?
I am using [4.3.1] Official LiquidSmooth [Ver 2.25].
If someone can give me any info on this i will apreciate it.
snipekill said:
Hi
Can some one help me , i will like to know witch should be the bes cpu settings?
my cel. only have as max1512mhz , and a freind told me that try to run as min less than 500 mhz.
But on the governor witch should i select interactive , conservative, ondemand, userspace, powersave, or performance?
and on Io scheduler noop , deadline , row or cfq ?
I am using [4.3.1] Official LiquidSmooth [Ver 2.25].
If someone can give me any info on this i will apreciate it.
Click to expand...
Click to collapse
nobody can tell you what the best is. what works best on mine, may not work best on yours. it depends on what kind of user you are.
I can only tell you what my settings are and how it works for me.
I always go 1 up from the bottom on min to 384
I set my max to 1512 usually, just because I don't want to redline my rpm's (car reference)
on liquid smooth, I had set my governor to Userspace to get rid of my wake problem.
my scheduler, I left it alone. I haven't noticed it do anything for me.
I am not hardcore user. I barely game or call. mostly text and my music along with XDA and Facebook. I will get all day with about 40% battery left. cause I charge every night, that's all I am worried about getting.
hope this helps
captemo said:
nobody can tell you what the best is. what works best on mine, may not work best on yours. it depends on what kind of user you are.
I can only tell you what my settings are and how it works for me.
I always go 1 up from the bottom on min to 384
I set my max to 1512 usually, just because I don't want to redline my rpm's (car reference)
on liquid smooth, I had set my governor to Userspace to get rid of my wake problem.
my scheduler, I left it alone. I haven't noticed it do anything for me.
I am not hardcore user. I barely game or call. mostly text and my music along with XDA and Facebook. I will get all day with about 40% battery left. cause I charge every night, that's all I am worried about getting.
hope this helps
Click to expand...
Click to collapse
Thaks for the info i will try setting only the governor :good: