Related
worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know
(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.
Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me
I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel
Had that issue at the Gym the other day, not even on Bionix.
I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App
Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.
r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.
i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/
There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.
Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL
Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!
sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..
I think it's hardware.... One of the unlucky ones....
Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.
First of all, for anyone who has not yet tried the new Manhattan Project 1.6ghz kernel by Team Whiskey, i suggest you do so (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=821514). It is currently in alpha but so far has gotten outstanding feedback. Ive personally been running it and I'm not looking back.
Up until now its been well known that SetCPU profiles not only dont work on our phone, but also causes crashes and severe instability. However, SINCE I FLASHED THIS NEW KERNEL (and running Bionix Fusion 1.1), I have successfully profiled my phone. Here is what I've been running all day with absolutely no issues, and my phone running like LIGHTNING:
Main: 1600-200 Conserv.
Screen Off: 200-200 Conserv.
Temp > 50: 800-200 Conserv.
I posted these results in the kernel forum, but I also wanted to post them here for everyone to see because i know that the lack of SetCPU profiles has been a major complaint around here. If anyone would like to try this out and verify that it works for them also with this kernel, please post here, so everyone can finally enjoy the beauty of overclocking AND underclocking.
Once again, I'm running Manhattan Project Kernel and Bionix Fusion 1.1
Outstanding!
Appreciate the profiles. Should be a great help. I personally lowered my Temp to 40c but thats just my opinion
Excited to get the running will tell results soon!
So had my phone sitting for a bit, it became unresponsive and i think it had something to do with the sleep profile. I went ahead and changed it to 400/200 conserv for testing.
Awesome. But is the set on boot option still not working?
Oh and just an educated guess bit I would figure no Voodoo on this kernel. So disabling just in case before I update
YatimaMeiji said:
Awesome. But is the set on boot option still not working?
Click to expand...
Click to collapse
i dont even bother, its not really needed....even if its unchecked yoru settings are preserbed upon reboot
----------------
UPDATE #2: after 5 hours of no problems my phone finally started crashing, so i have may have spoken prematurely. But I'm stubborn, so Im still gonna try every damn combination possible until my phone tells me to go f*ck myself haha
I will post my feedback as well...
OP, are you running any lag fixes?
drizze99 said:
I will post my feedback as well...
OP, are you running any lag fixes?
Click to expand...
Click to collapse
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
TopShelf10 said:
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
Click to expand...
Click to collapse
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
jnp1974 said:
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
Click to expand...
Click to collapse
probably not going to help, but i certainly hope it does!!!
TopShelf10 said:
probably not going to help, but i certainly hope it does!!!
Click to expand...
Click to collapse
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
EDIT: I was testing different benchmarks with scaling on conservative, on-demand and performance to see if they altered my benchmark results. The difference was minimal, but I forgot to change scaling back to conservative and it wouldn't wake. When I pulled the battery, rebooted and checked SetCPU, it said conservative, but was stuck on performance. Changed to on-demand, left SetCPU, back in and changed to Conservative. It worked.
jnp1974 said:
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
Click to expand...
Click to collapse
dont be fooled, it can often work for a while before it shows its ugly side, be patient
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
edit: for screen off don't be so stingy trying to set it to 200/200, if you need more battery life then get a bigger battery or spare batteries or Juice Defender , I usually set it to 200/800 and I have no issues.
TopShelf10 said:
dont be fooled, it can often work for a while before it shows its ugly side, be patient
Click to expand...
Click to collapse
I was fooled, ditching profiles altogether, boo
Can conferm that both profiles and set on boot work.
Sent from my Vibrant.
Mouahmong said:
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
Click to expand...
Click to collapse
i never check set on boot....what are your profile settings and what ROM/kernel are you running?
OK, I don't have mine OCLF yet but so far so good.
I have run Sleep profiles of 200/200 and 400/200 and the phone wakes up every time. I have gotten a txt message as well during my test and the screen lit up just like Bionix should! Will continue to kep messing with it....
turbosix said:
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
Click to expand...
Click to collapse
if it does so automatically then why is there an option to adjust "screen off" values?
Setcpu automatically scales between the high/low you set. SO if you let the main value stay at 1600-100..when the screen is off it will scale at a lower value of course cus you're not using the phone..but it wont stay at 200, because it has a Max of 1600! So depending on background processes it could scale back up to 4 or even 600 while screen is off
MY suggestions:
Download superpower battery saver from market, tweak to turn data on/off with screen and force ondemand cpu scaling
Download Autokiller--donate to get extra functions-- and set the value to Extreme or Ultimate when screen is off and Moderate or Optimal when it is on
I did that without setcpu profiles and it took 4 1/2 hrs to go from 81 % to 70
Im running Fusion 1.1 w/ Manhattan Project
http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.3-T1.zip
Dragon 3.2 w/ a fix that seems to work for setCPU screen off profiles setting the CPU to low values. Please note: The max freq in setCPU for that profile is what will be used, no scaling. I set it to 200Mhz and it's working fine every time I fire it back up.
The original patch is from here: https://review.source.android.com//#change,20804
Created by coolbho3k for the Nexus S, I backported it to Froyo. If we get good test reports from others, I'll push the changes to github tomorrow so other devs can use it.
When testing, please either use known good OC/UV settings, or don't OC/UV at all. Phantom OC/UV crashes won't help us know if this is working well for others. I've tested it with and without, turning my phone on/off like a madman... working fine so far.
Hmmm... early reports aren't looking good. Perhaps something isn't quite right. lol... Be warned if you try it, read all the comments. Might have to declare this one a fail. Too bad the NS cpu-freq driver is so different.. maybe I'll try pulling the whole thing over..
Downloading now report back tomorrow! This sounds promising.
Sent from my SGH-T959 using XDA App
Will test as soon as i get mine back to stock! Its just what I felt like doing today.
I did have a question..
Do we need to adjust it to say.. performance,on demand powersave? or will it just default?
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
coolkid893 said:
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
Click to expand...
Click to collapse
wow that can't be good. Sounds like the phone is overheating..
PaiPiePia said:
wow that can't be good. Sounds like the phone is overheating..
Click to expand...
Click to collapse
ya i know an its not even o/c its set to only max at 800mhz lol i think im gonna reflash to 3.2 to be safe but its a step in the right direction good try
Ok Im gunna have to try and install setcpu first.. otherwise my phone loads and restarts a few minutes into being on the desktop.
Testing now, Just UV'ed my clocks, and now setting profiles.
Observation so far:
SetCPU, and Uvolting seems to lock up my phone, and cause a reboot, and phone is pretty warm/hot.
Confirmed I can not run this either.
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
junxracr said:
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im having better luck using profiles with 3.2 than with this one. I've been using set cpu since 3.2 came out with no problems @1.4 and on powersave when screen is off. I have made no changes to the UV settings.
yikes ! i smell quadrant score in few min lemme install it
Has anyone got a "kernel panic" on this before? I'm not sure what I could have done wrong.. had to Odin back to stock. Forgot to back up before I flashed, shame on me. lol.
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
bartek25 said:
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
Click to expand...
Click to collapse
Nah, it didn't wipe my data. I had to Odin back to stock because I couldn't go into Clockwork Mod Recovery Mode. It would go into Kernel Panic and it reset all my launcher settings....
Was running hot for me also. Back to stock and then to bionix .
I think that when you get things fine tuned you will have a great Kernal.
FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
At least you got it installed, I couldn't even get that!
Sent from my Gingervolt-ed VS910 4G using xda premium
Mark Once Again said:
FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
Click to expand...
Click to collapse
Was it still unstable if you turned it down to 1GHz instead of keeping it at 1.5GHz?
I never could get that far. As soon as the phone was almost up it would restart. I tried about 5 or six times. I am happy with the phone without Blitzkrieg. Just thought I would pass along the info.
Thanks to all!
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
vortmax said:
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
Click to expand...
Click to collapse
I wonder why of all things, that would make a difference. You must've figured that out by chance? Haha
Sent from my Supercharged, Blitzed LG Revolution using xda premium.
I tried plugged into the usb on my pc, plugged into the charger and not plugged in at all. Same result each time. No complaint, just thought it might help having the info out there.
Thanks again!
You might try first installing a CPU utility like setcpu, and setting it to do no more than 1ghz on boot, and then flash it
Sent from my VS910 4G
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
Turn up the min. That fixed it for me
brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
You can turn off the haptic feedback to minimize that vibration reboot but it won't solve the issue tho
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
For those who use blitzkrieg kernel I recommend using cpu tuner instead of setcpu
I've been testing both app extensively for the past 2 weeks and notice cpu tuner is much more stable than set cpu and both have the same features
I use the free set cpu verison that you can download on the xda site that's the same as the paid version you get on the market
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
keynith said:
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
Click to expand...
Click to collapse
keynith, try to set the min cpu speed to 768 in setcpu.
So far after changing the min cpu speed i haven't had any issues again.
Did that yesterday and no problems since seemed to work
Sent from my VS910 4G using XDA App
brad08stanggt said:
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
Click to expand...
Click to collapse
Best thing I can say to do is to Restore to default and install things one or two at a time. It's likely an App causing the issue. I have had that happen a few times on my Droid 2 Global. Every time I would run the Goggle Nav App, my phone would randomly reboot. Don't have it installed, would be perfectly fine, until I installed Pandora app. Some buggy apps can cause such issue, and also bad settings. So, I would suggest going the 'long way' and starting from scratch and installing only necessary apps one or two at a time. If things work good, move on to next apps. When things go bad, recall the apps you just installed where the problem occurred. Restore your phone, install only those apps and see if you have reboot issues. If so, you are closing in to finding the real problem. I doubt, even by the post you wrote, that it's the phone or hardware. You need a factory fresh restore, including wiping ALL data, including settings for your apps.
-Cybie
Well?
I don't know if you guys fixed your problems yet, but I kinda had some of the same issues and I do not use CPU Tuner or Set CPU! Also I know that when you install Blitz 1.3 It defaults to normal CPU speeds that are already in phone settings as checked by CPU Spy after flashing Blitz. I have been using Antutu CPU Master Pro to set speeds and profiles works great for the price I use it on my Viewsonic G-tablet as well! Anyway what my first issue is the screen locks I had them all the time and the only way I kept them from happening was to set my min at the 245.76 MHz and my all the time max at 1200MHz. I also set the screen off at 122.88MHz - 245.76MHz On demand scaling profile to keep it not wakening from sleep quick enough. Antutu has all kinds of settings in the Pro version and If you want a overclock I think its the best to use.
The only Issue I have not figured out is you guys get a 10 sec vibrate then a reboot I get a Vibrate forever until I reboot I got woke up this morning at 4:00 A.M. by my phone vibrating next to my bed only happens at night and only when I start receiving emails early in the morning. I tried several screen off settings and not having vibration on at all and still happens figure that one out and I will gladly try anything you come up with!!! The only time it doesn't do it is if it is plugged in and charging!
Softkey lights
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
EDIT: charging to 100% fixed this.
Thanks for the quick reply and all your other posts too mt, they are very informative.
anangelablaze said:
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
Click to expand...
Click to collapse
Charge it to 100% and it will stop