Related
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
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
Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk
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...
Every ROM I've tried on T959 (Vibrant) seems to lag or lock up.
What are the best ROM's that won't lag or lock up my phone?
PuritanHope said:
Every ROM I've tried on T959 (Vibrant) seems to lag or lock up.
What are the best ROM's that won't lag or lock up my phone?
Click to expand...
Click to collapse
O-o that's very odd...which roms have you used exactly? Have you stayed mostly with froyo roms? GB roms or ICS?
Also- what kind of settings do you use? Governors and schedulers? frequencies? Do you OC or UV? Etc. Etc.
Xenoism said:
O-o that's very odd...which roms have you used exactly? Have you stayed mostly with froyo roms? GB roms or ICS?
Also- what kind of settings do you use? Governors and schedulers? frequencies? Do you OC or UV? Etc. Etc.
Click to expand...
Click to collapse
I've stayed mostly with the ICS roms.
No governors/schedulers whatever...nothing else on top of the ROM.
ICZen with sub-Zero's kernel was always my favorite ICS build, but you're going to have to accept some kinks when you're running ROM that's been ported over for a device that had official support stop at 2.2. Just be sure to pick a ROM that has some active development. And despite how good a lot of the ICS ROMs are for the Vibrant I don't know if the hardware is going to give you a completely lag-free experience 100% of the time; especially with multitasking (at least from my experience).
You can try to address the lag by changing your CPU Governor to something like ondemand or scary since those will ramp up the CPU clocks to your max frequency the fastest. Smartass and smartass v2 try to balance performance vs battery and were the usual defaults from when I was testing ICZen, but I always found it better to just go for broke since I'm just looking for a full 18 hours off a charge.
Another thing to try is tinkering with the number of apps the system will keep in memory. Try setting it low (3 or 4) if you're experiencing unusual lag.
PuritanHope said:
I've stayed mostly with the ICS roms.
No governors/schedulers whatever...nothing else on top of the ROM.
Click to expand...
Click to collapse
Well, no matter what...your rom is going to have a certain scheduler and governor set...same with cpu frequencies.
If you haven't changed them at all, then you are running on the default that the rom creator set it to...or if you flashed another kernel on top of the rom, then you are running the kernel creator's default. I'd suggest, the person above me suggested...going with ICzen with subzero or devil...then I would suggest downloading NStools free from the market place and experimenting a little with the governors and schedulers....
some good schedulars are: sio, vr, deadline, or noop
and some good governors are: smartassv2, lulzactive, lagfree (if that's what you're going for)
...personally...to avoid lag and get good battery, I go with a modified conservative governor with a slightly higher max frequency of 1200 normally and 1300 if i'm playing a very taxing game like idk,...dungeon defenders or something.
Now, you'll definitely experience better performance by chancing the governor and max frequency.
For reference go here: http://forum.xda-developers.com/showthread.php?t=1420742
and to see what I meant when I said that I "modified" the conservative governor to fit my needs...
go here: http://forum.xda-developers.com/showthread.php?t=1369817
If you have any question, just ask! But I really think that your lag will go away once you become more familiar with tweaking the settings to run smooth.
If you are really interested in tweaking your phone a bit more than this however...
you can also try running this: http://forum.xda-developers.com/showthread.php?t=991276/
with the free app "script manager" from the market. It's definitely worth it in my opinion.
Good luck!
PuritanHope said:
Every ROM I've tried on T959 (Vibrant) seems to lag or lock up.
What are the best ROM's that won't lag or lock up my phone?
Click to expand...
Click to collapse
i'm running FE's CM10 jb preview. disclaimer: it's still in alpha. everything works for me; gps is so-so.
the kernal i have is devil3 1.0.4test3 found here. the governor is set to smartassv2 with min of 200 and max of 1000.
also, animations in developer options settings are set to 0.