I tested it once and I'm losing 4% per hour. Its 800-200 on demand as main, screen off at 500-200 and less than 50% battery also at 500-200.
I haven't toyed around with different kernels, I'm using the kernal that came with Zedomax's root instructions. Also, 200, 500, 800, 1000 and 1200 are my only options, this is because of the kernel that I'm using correct?
In your experience is -4%/hour average or does it seem like SetCPU is working? 500-200 is the lowest I can go otherwise it would be 200-200.
Thanks
Sent from my SAMSUNG-SGH-I777 using xda premium
Sounds like you have some apps or widgets draining your battery. I've overclocked mine to 1.6 and get less than 1%/hr drain on idle.
First off, what rom are you running. Try unnamed or serendipity. Don't do the 50% or less at 500-200 its gonna slow you down. Also switching to entropys daily driver should net you an improvement. Also try out the conservative governor. Its just as good as ondemand but with better battery.
Sent from my SAMSUNG-SGH-I777 using XDA App
I am running stock ROM. Should I bump the 50% up to 800-200? I don't have many options with this kernel/rom.
Im still new to this process as well
CollegeProfesor said:
I am running stock ROM. Should I bump the 50% up to 800-200? I don't have many options with this kernel/rom.
Im still new to this process as well
Click to expand...
Click to collapse
800 should be fine for most things, only adds a tiny bit of lag to paging around the apps and home screens. I just benchmarked mine at 800 and got a 2721 on Quadrant, which is only ~500 less than what I got at 1200mhz on stock.
Also, I was wondering, is the issue with screen-off speeds below 500mhz still around? I have mine at 200-1600 conservative and I haven't had any issues yet.
Thanks. I flashed UnNamed and now I can finally overclock, but SetCPU won't allow me to set my main to conservative. Ive tried it multiple times and re-booted as well.
I also want to undervolt, I've reduced each one by 50, thoughts? Is this too little?
Thanks again, im trying to get the hang of this
CollegeProfesor said:
Thanks. I flashed UnNamed and now I can finally overclock, but SetCPU won't allow me to set my main to conservative. Ive tried it multiple times and re-booted as well.
I also want to undervolt, I've reduced each one by 50, thoughts?
Click to expand...
Click to collapse
Is it giving a error could be the new kernel didn't flash. Go to entropy's thread download the newest version and flash via CWM. See what it does then.
nh5 said:
Is it giving a error could be the new kernel didn't flash. Go to entropy's thread download the newest version and flash via CWM. See what it does then.
Click to expand...
Click to collapse
Nevermind, it worked. SetCPU was just using a different governor for a profile that I set.
Related
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
xsalientx said:
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
Click to expand...
Click to collapse
setcpu is the only and the best overclocking app. If u want to be able to overclock ur phone us have to flash jt1134s 1.2ghz voodoo kernel then use can use setcpu to overclock to 1.2ghz!
sent from my fascinate rooted and ocl'd to 1.2ghz with voodoo
xsalientx said:
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
Click to expand...
Click to collapse
SetCPU is the most popular one. You'll need root to even use SetCPU. And you'll need CWM to flash the OC Kernels. If you dont OC SetCPU is pointless
On that note.
SetCPU must be ran on conservative and with no profiles and no load on boot.
If you do reboot your phone, mine reverts back to 800, so I need to manually change it to 1200.
Do u have to set both min & Max to 1200???
no just the max
Sent from my LV-Voodoo Fascinate using XDA App
saps said:
SetCPU is the most popular one. You'll need root to even use SetCPU. And you'll need CWM to flash the OC Kernels. If you dont OC SetCPU is pointless
Click to expand...
Click to collapse
Not pointless. You can always underclock to spare your battery life
Sent from my SCH-I500 using XDA App
jt1134 said:
Not pointless. You can always underclock to spare your battery life
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes, of course you are right. Actually the other day I forgot to slide sliders up from 800 to 1200 and I was getting really good battery life for like 2 hours my % only dropped 1% and I was like wow.
Im just pleased as punch that there are OC/UV kernels out, its the best of both worlds.
Actually my battery life is above average it seems; either that or my usage is below average so Im not draining it as much. I'd gladly mildly overvolt to something like 1350mV if it meant I'd be rock solid stable at say 1.4Ghz
BTW, jt I heard you might be getting out the kernel speed chase after these 1.2Ghz's? Just don't feel like chasing 1.3 or 1.4?
I am running Dirrk's D012 LV 1200 Kernel with SetCPU
Luckily, the LV runs EXTREMELY smooth on my phone..
So smooth, that for the past day now I have been able to run with "set on boot" and constant restarts on my phone..and with Profiles for Screen Off, Temp (probably wont get there), and Charging. I can say that I have had no problems with my profiles and set on boot. Then again, I don't want to contribute to hurting anyone's phone
Just thought I'd let everyone know how my phone (and potentially others) can seem to handle profiles and set on boot.
johnz1 said:
I am running Dirrk's D012 LV 1200 Kernel with SetCPU
Luckily, the LV runs EXTREMELY smooth on my phone..
So smooth, that for the past day now I have been able to run with "set on boot" and constant restarts on my phone..and with Profiles for Screen Off, Temp (probably wont get there), and Charging. I can say that I have had no problems with my profiles and set on boot. Then again, I don't want to contribute to hurting anyone's phone
Just thought I'd let everyone know how my phone (and potentially others) can seem to handle profiles and set on boot.
Click to expand...
Click to collapse
No problems with set on boot here either. I keep it on.
so how do i use setcpu/what are the steps i need to take?
xsalientx said:
so how do i use setcpu/what are the steps i need to take?
Click to expand...
Click to collapse
Install it, tell it to auto detect, set the max where you want, leave the min at 100, and then leave it alone.
Sent from my SCH-I500 using XDA App
I was hoping to get some help. I have installed jt's 1200 voodoo kernal, and I can't seem to get Setcpu to clock at 1200. It still says that the max is 800, however, on the slide it is only giving me the option to goto 528. Bellow are my facts, any help would be great!
Facts:
1. flashed jt's overclocked voodoo use clockwork, but did it through "install ROM from sd card". I am not sure if this is correct, but it seems to be running voodoo.
2. I have no idea how I need to have Setcpu set up.
I feel like I am blindfolded and I am trying to wack at a pinata.
thanks.
Edit: never mind...even a blind folded monkey hits the pinata every now and then
Hey guys, anyone have a good idea of what some safe undervolting values would be? I was just going to play around with them and not set it on reboot so I could just pull the battery, but I am unsure of how irreversible the damage could possibly be, if any.
I am running: Senseless 1.0
dsb's kernel
I actually have it underclocked slightly because I don't play games, and when I do they are something like Angry Birds, or Words when I am bored.
Bump, out of all of you who have undervolted none of you know any good values?
AtLemacks said:
Bump, out of all of you who have undervolted none of you know any good values?
Click to expand...
Click to collapse
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
WasabiWa83 said:
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
Click to expand...
Click to collapse
Cool, I didn't know what was "too much". How much better battery life did you see from -50?
Evo4gLI said:
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
Click to expand...
Click to collapse
Which Kernel are you running?
At -50mV across all frequencies, it reeeally varies. I never have a "normal" day with this phone. But, the shortest I've had using Ziggy's kernel from 192-1836gHz with on demand governor is around 7 hours. That was pretty heavy usage for me. Some games like Dead Space and Captain America, tons of internet, Pulse, texting, a few phone calls, music, and a little Netflix at night. The longest I've had has been 20+ hours. That's with very little gaming, a little internet, and mostly just texting. Stock battery, bump charged.
I'm really afraid to go too low, though. One time I was just seeing what would happen if I kept lowering it across all of the frequencies and it froze, then crashed. Had to battery pull to get it to work again.
I run DSB Kernel with SmartAssV2 underclocked to 1296, and before undervolting on my OEM battery I got 13 hours with a little over normal usage. Screen was on for about 2 hours total. On my extended battery I got like 27 1/2 hours, but obviously some of that time was overnight.
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
AtLemacks said:
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
Click to expand...
Click to collapse
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
nosympathy said:
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just -50, but I updated the kernel and forgot to remove the PH98IMG prior so I set the phone into bootloops. Had to factory reset(after trying everything else) and start over from backups.
Evo4gLI said:
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
Click to expand...
Click to collapse
See, I don't get the overclocking hype. It isn't hard to overclock when needed, so I feel underclocking is the better choice for battery life. The phone is fast as hell no matter what.
I may try to do some undervolting...but I am running clean rom 1.3 and dsb's smartass kernel, and I have been getting good battery life for what I use my phone for. I do have it overclocked though (on demand).
You won't damage the phone with undervolting. I mean a lockup might be a pain, but it won't damage the phone. Overvolting on the other hand could ruin the phone.
I will probably just stick with -50 across the board for now, I am tempted to pay for the full version just so I can save profiles and not have to set on boot.
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Running -75 on everything with incredikernel
bendirkss said:
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Click to expand...
Click to collapse
You sir must be using a Gnex. LOL
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.
I have recently just hopped back onto ICS AGAIN. I have used ICS ever since its been out for my region and every single try i will revert due to the same issue. Either battery life or random freezes.
This time i am really lost hope. I was hoping samsung could release something that worked for me but it never came. I have to seek help from all the pros
The situation:
I have flashed afew ICS ROMs and kernel combo. I tried
DXLP9 w/ stock, siyah, NEAK
DXLPB w/ stock, siyah, NEAK
Sensation ROM 3.5 with siyah.
They all had the same issue whether i UV them or not. I tried factory resets, clear cache, kernel cleaning scripts, even SD format.
They all will have random freezes on load. Its random so sometimes i cant recreate the situation. Most common ones are updating or downloading from market, when its near or starts to install. But i can watch videos and everything fine. GMaps sometimes freezes it too.
As for governer i use smartassv2 for siyah and lulzactive for NEAK and SIO as scheduler. Did try ondemand on stock and sometimes noop and NEAK. Same responses.
I ran sensation rom fine ytd with 1 widget and downloaded whatsapp and extweaks and UV and everything was stable. Watched pps the whole night. Totally fine and this morning i wanted to load my normal apps from market and it started to freeze on me.
Im really lost someone pls help me. If not i really have to go back to GB again.
Sent from my GT-I9100 using xda app-developers app
sianzb0i said:
I have recently just hopped back onto ICS AGAIN. I have used ICS ever since its been out for my region and every single try i will revert due to the same issue. Either battery life or random freezes.
This time i am really lost hope. I was hoping samsung could release something that worked for me but it never came. I have to seek help from all the pros
The situation:
I have flashed afew ICS ROMs and kernel combo. I tried
DXLP9 w/ stock, siyah, NEAK
DXLPB w/ stock, siyah, NEAK
Sensation ROM 3.5 with siyah.
They all had the same issue whether i UV them or not. I tried factory resets, clear cache, kernel cleaning scripts, even SD format.
They all will have random freezes on load. Its random so sometimes i cant recreate the situation. Most common ones are updating or downloading from market, when its near or starts to install. But i can watch videos and everything fine. GMaps sometimes freezes it too.
As for governer i use smartassv2 for siyah and lulzactive for NEAK and SIO as scheduler. Did try ondemand on stock and sometimes noop and NEAK. Same responses.
I ran sensation rom fine ytd with 1 widget and downloaded whatsapp and extweaks and UV and everything was stable. Watched pps the whole night. Totally fine and this morning i wanted to load my normal apps from market and it started to freeze on me.
Im really lost someone pls help me. If not i really have to go back to GB again.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
try with less UV, and more bus freq
pelpa87 said:
try with less UV, and more bus freq
Click to expand...
Click to collapse
but i even tried no UV and with stock. ytd i tried no UV again. seems to be performing well but i cannot let my phone run without UV cos it will drain battery very fast
Btw im using the same 5 cpu states but i turned off the 1.2GHz state. So its 200 to 1000. What do you mean more bus freq? Up cpu speed?
sianzb0i said:
but i even tried no UV and with stock. ytd i tried no UV again. seems to be performing well but i cannot let my phone run without UV cos it will drain battery very fast
Btw im using the same 5 cpu states but i turned off the 1.2GHz state. So its 200 to 1000. What do you mean more bus freq? Up cpu speed?
Click to expand...
Click to collapse
dunno about siyah, i use fluxi, u can ov bus. I think in siyah too.
The thing is simple, not every phone reacts equal. My phone for example doesn't handle strongs uv. I have to slightly uv it. Same as bus.
I even saw some phones that couldn't handle aokp without over volting. Ir getting higher bus.
In the other hand, uv is overrated. It doesnt saves as battery as everyone thinks. The screen is battety's worst enemy
Sent from my GT-I9100 using xda premium