Hello, today i was browsing the net and then my GNote suddendly became slow...
i had rooted it with superOneClick, and i hadn't had any problem till now. I installed SetCPU and i saw it is running at 200/500mhz. How can i solve this problem? I tried to reboot many times and i pulled out the battery, but nothing changed.
I previously had installed cpu tuner, but also uninstalled it without problems and when the slow down started, i hadn't any overclock app on my phone. Thanks!
You have to scale it up to 1400MHz again using SetCPU. Since you don't have a clue on using it, i recommend that you uninstall it after you've clocked it to its normal state.
maybe it was low on power and it started using system power saving
It is charging (65%) although the battery level decreases...
And i used scale it up to 1400mhz, but nothing changes, only for a few seconds it runs normally and than back to be laggy
It seems that something is fighting against setcpu, any clues? I think that with a hard reset i will solve the problem, but this is my last willing.
And I installed setcpu after the lag started, i wanted to see the clock of the cpu because it was too slow.
Don't use SetCPU or any OC tools to check the CPU. Install Elixir 2 from the Market and see if it goes up to 1400MHz when you stress the phone.
Sent from my GT-N7000 using xda premium
Related
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
fifedogg said:
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
Click to expand...
Click to collapse
Your phone going to 245 is completely normal. It only gives your phone power when it needs it, and sitting on Setcpu screen isnt going to make it throttle up. You dont want your phone running at 528mhz at all times. It will KILL your battery. Our phones have a setting of "Ondemand", like gives the power on demand, if its not demanding a lot of power it will go back down saving battery life, CPU life and keeping temperatures down.
If you have problems with the phone running slow, i recommend checking out an overclocked kernel. You can run it at stock speeds, if you dont feel comfortable running OC. But if you want the extra power, the choice is always there.
Sounds like something to do with conserving battery by dropping the cpu speed.
-------------------------------------
Sent via the XDA Tapatalk App
Had thr same problem in the beginning way back idk how i guxed it i guess its the stock rom idk
-------------------------------------
Sent via the XDA Tapatalk App
Well on a stock rom setcpu cant do anything other then read the cpu and it will only update when it is force refresh. If you want setcpu to be able to control or change your cpu speeds this will require installing a rom that is overclock enabled. There are several located on this forum.
For some reason SetCpu was doing this. I just set it back to 480/528 and rebooted it and then uninstalled SetCpu and now everything is fine. For some reason SetCpu was the cause of this. I reinstalled to make sure and sure enough it was happenening again. I'm glad I figured it all out
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
If it is not a ROM running an overclockable kernel apps like setCpu and OC widget will actually slow your phone down. If you would like to see your clock speed without this side-effect, I suggest SystemPanel.
Click to expand...
Click to collapse
For future reference, anyone not using a ROM based on Toast's kernel DO NOT install an OC program. This is the typical behavior and it is not fun to deal with because you will have to be patient waiting for the phone to start up and open the OC program to set it back and uninstall. I believe that just uninstalling and rebooting is sufficient, but am not 100%.
lineman78 said:
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
Click to expand...
Click to collapse
I actually made that thread at the same time last night. I didnt know where to put it exactly...
fifedogg said:
I actually made that thread at the same time last night. I didnt know where to put it exactly...
Click to expand...
Click to collapse
Aw, this must be the one from the Dev section and got moved over here. I noticed it over there, but had already posted on the one in Q&A... So now there are 2 in Q&A.
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
after using setcpu for a few weeks and getting similar problems, i removed it.
There is pretty much no use in it for this phone, they allready scale from 100mhz - max speed (even oc if you have one) automatically
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Yes. I have the same problem on my stock SGS.
Setcpu is not working good on sgs. Try to remove it, and you'll get better battery life.
Sent from my GT-I9000 using Tapatalk
I don't know of anyone who has tested it on the I9000 (and there may even be alternatives or the same thing floating around the development subforum), but they claim to have a 1.2ghz overclocked kernel here for the I9000. Maybe best to be avoided, but a 100% use at your own risk alternative, especially if you're a bit unsure on any of the translated steps, is available here.
http://translate.google.com/transla.../matpclub.com/board/index.html?id=tipn&no=144
been using it on a vibrant for about 10 days and had my first issue last nite - it froze the phone - had to remove battery to reboot, tried again, froze it again
i thought it was the last two apps i'd installed so i removed them, then there was an update, downloaded and installed, so i did a number of settngs changes, closing setcpu, running benchmark quad, reopening & changing settings etc
about half dozen times
and it's been fine so far -
I had the same issue. I would pull my phone out of my pocket and it wouldn't wake up. I could call my phone and it would ring but my phone would do nothing until I removed the battery and re-booted. This happened numerous times until I uninstalled SETCPU and it stopped doing that so I knew I found the culprit and haven't tried it again since (I need to receive calls as priority 1)
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
lgkahn said:
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
Click to expand...
Click to collapse
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
tt4079 said:
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
Click to expand...
Click to collapse
I killed my task manager service, and it didn't freeze up! I'm going to uninstall the task manager and see if I have any more freezing issues in the future.
Edit: Nope, didn't work. Removing SetCPU.
mekwall said:
What's your experience with SetCPU on Galaxy S?
Click to expand...
Click to collapse
I have the Vibrant version with T-Mo. After rooting, Titanium, Barnacle and Root Explorer all seem to be working fine.
After a few minutes of installing SetCPU, my phone wouldn't wake up. Rebooted twice, same results.
Removed SetCPU and the phone's working fine again. Maybe the minimum speed should be set at 250 or so?
George
To begin with, you don't even need SetCPU
SGS phone automatically regulates the speed of the CPU depending on your usage.
most of the time in Stock ROM it hover around 200 Mhz, very few times it uses the max 1000 Mhz
only when there are lots of background apps running
when you runt he CPU at 1000 Mhz it gets hot fast, and it consumes more battery
good thing is it drops back down to 100~200 Mhz as soon as it's done with the heavy tasks
so having the SetCPU installed will defeat the whole purpose of power saving and CPU cycle on demand
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
I don't even remember the last time where we had a fixed clock on a cpu Allgamer. The point of setcpu is to either downclock or overclock your cpu. You might want to limit your clock to 0.6GHz just to save some juice.
Anyway, after a few hours of head scratching and 2 reboots, I uninstalled and refunded it.
I agree. Setcpu is rather unstable. I have feeling lots of the kernel overclockers have problems but blame the kernel while they should blame setcpu
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
toansta said:
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
Click to expand...
Click to collapse
It depends on what you're using it for. If you know what you're doing, it can be a useful tool. If you want to overclock, you'll want setcpu. If you want to underclock (lets say you're out and about, with 40% battery), then you can set the maximum cpu speed lower so that the battery will last longer.
You don't need setcpu if you're simply going to tell it that you want your max speed to be 1ghz, with a min of 100mhz and you want it to be "conservative". Your phone does that by default, and frankly the SGS is pretty good on its own when it comes to battery management.
thanks reuthermonkey, i will keep that in mind.
What are the perfect setcpu 2.0.3 settings for froyo JP6 I9000 rooted? Thanx in advance
Telanis said:
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
Click to expand...
Click to collapse
Menu and rescan the device should restore the normal values. those values are not the ones actually used!
Hello guys,
I recently installed an app from the market called Temp+CPUV2. All the app does is it displays CPU Clock speed, CPU Utilization %, CPU Temperature, and Free RAM on a tile as a Widget.
lately, I have been observing fluctuations in the clock which ranges from 100MHz to 1GHz. I thought the widget was faulty. Then later on, I began observing constantly time to time and I found out that the phone really operates on different frequency at different times. Apart from changing the clock speed, I think the self-assessing algorithm eats too much RAM figuring out next clock speed and slows down the phone.
I assume that this features is implemented to save battery, but at the same time, this feature kills the phone by slowing it down so badly that I sometimes feel like smashing the phone against a wall or something.
I use a rooted JM1 with SU and no other mods.
Is there any way to stop the phone from assessing the clock and change it from time to time? I think that's the real reason why the phone lags in he first place.
Nope, thats just the way it works. Install a overclocking kernel and SetCPU if you want to control the clock speed but I advise you just uninstall that widget and not bother worrying about it as you are getting worked up over nothing. SetCPU and a kernel is more trouble then its worth and is very unstable
That's a powersave mechanic.
Save your battery.
It also try to keep your phone cold.
In fact it work well.
It same in computers.
Sent from GT-I9000 Jpm with z4mod
I doubt the lag you are getting has anything to do with this. Look for the lag fixes like Voodoo, Z4mod, or OCLF.
I use z4mod myself, flawless performance
Took me 2 hours to figure out why my phone was lagging out even more than it was prior to root. Slow dialing, lagged texting, lagged screen on, etc. Once I reverted back to "moto_hotplug" governor in SetCPU, everything is perfect.
Sent from my DROID3 using Tapatalk
That's strange my default setting in setcpu was ondemand and all is well
I was experiencing the same issue every time I turned my screen off, except my phone would completely freeze and my only option was pulling the battery. Finally I discovered it was the one profile in SetCpu that was set to clock down and scale to ondemand when the screen was off.
Can anyone confirm that clocking down with profiles works as long as the scaling is ondemand?
djdmbrwsk said:
Can anyone confirm that clocking down with profiles works as long as the scaling is ondemand?
Click to expand...
Click to collapse
I tried that out and it doesn't seem to work even if I leave the scaling as moto_hotplug. It takes a few minutes, but it definitely completely freezes up.
djdmbrwsk said:
I tried that out and it doesn't seem to work even if I leave the scaling as moto_hotplug. It takes a few minutes, but it definitely completely freezes up.
Click to expand...
Click to collapse
Same here, but others are still reporting that they are underclocking with SetCPU just fine. I'm leaving it alone for now, since I'd rather overclock to be completely honest with you. My battery life isn't a problem at all. 17-21 hours on average unplugged before 10%. Perfectly fine for me.
Lyxdeslic said:
Took me 2 hours to figure out why my phone was lagging out even more than it was prior to root. Slow dialing, lagged texting, lagged screen on, etc. Once I reverted back to "moto_hotplug" governor in SetCPU, everything is perfect.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
I can second this issue. I played around with a bunch of different settings and found it was most stable when the max was no lower than 800, but it still froze on occasion even with hotplug selected. Overall it seems SetCPU is not really compatible with the Droid 3.
I switched mine to Ondemand as well and it was quickly obvious the phone didn't like it. Quadrant scores dropped to 1000-1500 range. Setting back to moto_hotplug and Quadrant scores back over 2200 and everything is running smooth.
I learned this the hard way as well. I had it changed to the settings I used on my thunderbolt back then, using ondemand screen off 300 max 300 min. When Handcent received a message, texting would lag, etc and once I changed back to moto_hotplug everything was great again!
Sent from my DROID3 using Tapatalk
Hii.i've got a i9001 running cm9 ics.sometimes, when i'm ussing the phone or just walking trough the menu, it heats up.i nearly can't touch it.i installed mininfo and it shows that the battery has 55°C/60°C.what should i do?
P.S: when it's superheating, the phone becomes very lagy
Try a cache/dalivk wipe? Clear ram? If that doesn't work fix permissions or try a full wipe use a kernel script cleaner and reflash I have no problems with heat unless I'm doing a lot on it, and I I'm using it a lot while charging it becomes hotter but this is normal but not from simple menu scrolling, check the CPU settings as well make sure its not got a high min cpu frequency. If all this doesn't work undervolt a bit this will lower the temp as well
Sent from my GT-I9000 running remICS-UX using XDA premium
What kernel r u using?