Related
I've been using FreshToast for a few weeks now, the latest one.
I have it OC'ed with OC Widget as I was having issues with SetCPU as others are.
One thine I notice is that when I wake my phone up sometimes the CPU usage is very very high, for upto about a minute after waking the phone up. To the point where it is unusable.
I have been using "SeePU" for a while, which puts a nice CPU activity monitor at the taskbar. It uses VERY LITTLE to NO CPU usage (confirmed with the adb shell "TOP" command) never more than 2%.
The other issue I'm having is once or twice a day when I get a phone call, the screen comes on but to the HTC Lock screen. When I pull the lock screen down, its usually a blank screen with a FC dialog saying com.android.phone or something is busy. The ring tone keeps ringing and ringing and ringing. I have to do a battery pull.
I've even ran the phone with NO DOWNLOADED APPS to rule out any variables. Its definitely a bug in the ROM.
Are you getting any of the problems I've listed?
The symptoms you describe have been noticed by others using setCpu. Another cause that has been discovered is that when using OC Widget DO NOT enable a different setting when the screen is off as this has been proven to cause the wake-up and phone call problem you described.
system_server is being a real pain for me. I found it may have something to do with the location services.
I had too many problems so I installed the normal Fresh Rom
http://forum.xda-developers.com/showthread.php?t=681856
and then I flashed the OC kernel over that
http://forum.xda-developers.com/showthread.php?t=690238
That combo has been working great for me and is basically what Fresh Toast should be.
I have moved over to Fresh and have been extremely pleased. I think it actually runs faster than Fresh Toast even with correct overclocking(on fresh toast that is). Just remember not to put OC programs on, or it will actually underclock.
Aside from being able to Wirelessly Tether my 3G connection from my Vibrant, I wanted to also control my CPU speeds. But with SET CPU, I tend to come across a particular problem. I would underclock to 100000 (min&max) with the screen off, but as a result, the screen won't turn back on and I would have to take the battery off and restart my phone. Clocking it to 400000 (both min and max) screen off leads to the same problem. Is anyone else going through the same situation? If not, what are you setting your CPU to, in regards to both screen on and off?
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
lqaddict said:
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
Click to expand...
Click to collapse
Yeah I have all my profiles set to conservative. Do you guys think it has to do with the priorities, cause I have all of them set to 100.
It could, since there is no telling how to prioritize the settings, hardware/software might get confused.
you know I just noticed I got the same issue, sort of.
I have multiple profiles setup, and one is for charging via USB 800max/100min.
If the screen is off (400max/100min), and I connect the USB cable, guess what happens, three finger salute gets it back, hmmm.
OK I got it working for those who are having the same problem as I. All I did was I made my screen off frequency 200max/100min. For both charging and battery use, I have my cpu set at 1000max/800 min. It works flawlessly and I am noticing an increaSe in battery life...
Sent from my SGH-T959 using XDA App
OverClock?
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Halieus said:
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Click to expand...
Click to collapse
we need a kernel that will enable it. its apparently not possible on the stock kernel...
I have been having the exact same freezing issue when the screen times out, I'm unable to revive the phone without pulling the battery. I have tried many different setting in Setcpu including those posted here. I finally just uninstalled it and everythings right again. Best to avoid this app for now.
Hey man i did that and i still did not work any other way to set it up.
Vibrant wont come out of Blank Screen
I used Set CPU and put it to the max 1000 and then the max on the other readings it forced closed and after the tmobile and Galaxy animations it goes to a blank screen.
Yeah, I uninstalled it after a week because it was just too unstable. I was getting freezes several times a day, which is unacceptable. Other people might have better luck, but my phone did not like it at all.
So far the only way I can get the program to work 100% is to not have any screen off profile. If I just set it to 1200 max - 200 min / conservative it works fine. Yet once I use profiles and screen off at 100, 200 or 400 it won't turn back on. Every morning it's the same thing, battery pull.
I have similar problem. As long as I am not using "Profiles" at all it is fine. Playing with profiles setting for a while, but not being able to make them 100% stable.
Another thing, if your screen does not come on, you don't have to pull the battery out. Just keep holding on/off button for 5-7 seconds, it'll reboot. It's not a complete freeze, I believe only display system (whatever it is) fails.
Stuck at Recovery Mode
Guyz,
I have firetrap sugar on Spice Mi300. Installed Set CPU.
Tried entering the recovery mode, the phone gets stuck at 1st screen with a line "Enter recovery Mode" displayed on top.
Please help.
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html
I tried to search for a thread relating to this but couldn't find anything, if anyone knows of one a link would be appreciated.
OK, so I flashed Motleys kernel 2 days ago. Everything was running fine, I had it OC'd to 1.6 and it was super fast and smooth. I had set the governor to "on-demand" to try and save some battery life(over "performance"), and also because it seemed like the CPU would run at full 1.6 constantly if it was set to performance (I don't know if that's how it should be or not, but this isn't the issue). I used System Tuner to OC it like he recommended in his thread.
Yesterday I set it to performance to run some benchmarks, and then continued using it on performance to see how it felt. About an hour and a half later I also started messing with my home screen and apps and ended up accidentally using Quick Boot to take me to the bootloader. After powering it back on I checked System Tuner to set the governor and once I did I noticed, according to System Tuner, that 2-4 of the cores are running at full 1.6 and the CPU usage is from 25%-100% even though I have nothing open.
I flashed my recovery via Clockworkmod Recovery, Motleys kernel is now replaced by the stock kernel, however I'm still having the same issue, but just at 1.3. Any idea why the CPU is running so high, for apparently no reason?
.....
OK, so I just checked System Tuner again and the CPU doesn't seem to be doing as bad now, but it's still all over the place and I don't have anything else open. Here are the times:
Offline - 77%
340MHz -11%
475Mhz 1%
1.2Ghz - 5%
1.3Ghz - 1%
Compared to yesterday when it had said 1.3GHz 79% or something like that (and was running nothing but system tuner).
So, yeah, that does seem a lot better but one thing remains; the CPU usage still jumps up to almost 50% and once again, I am running nothing but System Tuner, so something still doesn't feel right.
I think ondemand governor is causing the CPU to shoot up so often and quickly.(That's all I can think of.) I always use interactive and it's usually the preferred governor. Ondemand is more for people who play lots of games and they need the extra boost. If you game a lot then I guess you should still to it.
Sent from my Nexus 4 using Tapatalk 2