OC Question - G2 and Desire Z Q&A, Help & Troubleshooting

I installed the latest Virtuous 1.0.2 rom with the latest advanced kernel and before I can even open up the setcpu app, my screen is completely unresponsive. I'm guessing that means my phone can't handle 1.51GHz? I wanted to tone it down to 1.2ish, but can't even get into the app.

Download cpu tuner and change it back to 806. Ur phone is running at 1.5 now and that's what's messing up.
Sent from my HTC Vision using XDA Premium App

ericc191 said:
I installed the latest Virtuous 1.0.2 rom with the latest advanced kernel and before I can even open up the setcpu app, my screen is completely unresponsive. I'm guessing that means my phone can't handle 1.51GHz? I wanted to tone it down to 1.2ish, but can't even get into the app.
Click to expand...
Click to collapse
open up the file information for setcpu, tap force stop, tap clear data, uninstall.
then reinstall setcpu and reset the clock speed to something that wont destroy your cpu in 2 months.

mputtr said:
open up the file information for setcpu, tap force stop, tap clear data, uninstall.
then reinstall setcpu and reset the clock speed to something that wont destroy your cpu in 2 months.
Click to expand...
Click to collapse
Yeah I don't want to fry this phone lol. It's supposed to be my backup and that means a good 2 or 3 years. In any case, I think I'll just stick with 1.2GHz for awhile. Are MoDaCo roms still considered top notch for something simple, clean, and fast?

Related

[Q] setcpu on baked snack question.

So I'm running baked snack here and really beginning to enjoy it and this whole root thing. I've installed setcpu but every time I back out of the interface it goes down to 691 no matter how high I set it or on any profile. Does this not work with baked snack? Am I overlooking something or did I set it up wrong(I used auto detect when I started)?
Did you flash a different kernal?
Sent from my PC36100 using XDA App
Nope I flashed kernel 3 I think or what ever came included in the baked snack.
should I DL that kernel by itself and then flash over the Baked snack with it? and whats the difference between flash over and flash ontop of?
Damn the stupidity of it all... lol. I set my profile to 691 if my battery was under 40% which it was... but now when I plug my phone in the cpu goes up to 1ghz which I have it set to but my battery keeps going down. Now this is a problem here if I'm not able to charge my phone while the setcpu is running it will get really annoying really fast. Considering the app manager that I have refuses to close it so I have to manually go to settings > applications > manage applications then go to setcup and force close it to charge my phone it seems. Do you guys think its a problem with my cpu being set to high while charging should I drop it down a whole bunch for the charge process too? That doesn't seem like a very needed thing to do I would assume it would be able to charge just fine without that. Looks like I got a lot to learn about this whole rooted phone thing.
Check your profiles in setcpu and make sure you don't have one that's at that speed with the highest priority. If that all checks out fine I would flash kernal 2 (my favorite) don't wipe just flash. And as for your question over or on top they mean the same thing and that's flashing the kernal without wiping.
Sent from my PC36100 using XDA App
Also do you have overclock widget running as well? If so they might be fighting eachother
Sent from my PC36100 using XDA App
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
crimeslunk said:
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
Click to expand...
Click to collapse
Overclock widget is just another widget you can download that runs seperatly from SetCPU. You should have a SetCPU widget though. I would try reinstalling SetCPU also

Need educated!!!

I need educated on a few things, I'm concerned with the performance of my phone so I have it rooted and I have installed system panel to monitor things, autokill memory optimizer for ram of course as well as watchdog to alert me if any apps are outta control. Am I crazy for having these or is it a good idea? Also is there anything better I should use rather then what I already have? I just want my phone to run smooth and my battery to last bc I use my phone all day long
Sent from my ADR6300 using XDA App
trembly01 said:
I need educated on a few things, I'm concerned with the performance of my phone so I have it rooted and I have installed system panel to monitor things, autokill memory optimizer for ram of course as well as watchdog to alert me if any apps are outta control. Am I crazy for having these or is it a good idea? Also is there anything better I should use rather then what I already have? I just want my phone to run smooth and my battery to last bc I use my phone all day long
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
A lot of that is unneeded. I have System Panel, but only use it if I'm having problems with an app. Rarely is there a use for watchdog. On stable ROMs, I've never seen an app get out of control, and rarely on betas. So it justs sits in the background eating battery itself. Also try, using a stock speed, undervolted battery with SetCPU. If I'm trying to make mine last, I have a screen off profile of powersave 384/245, and regular of 700-800ish (I forget)/245 conservative.
PonsAsinorem said:
A lot of that is unneeded. I have System Panel, but only use it if I'm having problems with an app. Rarely is there a use for watchdog. On stable ROMs, I've never seen an app get out of control, and rarely on betas. So it justs sits in the background eating battery itself. Also try, using a stock speed, undervolted battery with SetCPU. If I'm trying to make mine last, I have a screen off profile of powersave 384/245, and regular of 700-800ish (I forget)/245 conservative.
Click to expand...
Click to collapse
ok thanks, i installed setcpu and have two profiles set, one for when screen is off with settings similar to yours and another set to when my battery is >30%. could you please tell me what the governor options of on demand, userspace, or performance mean ?? also should i set priority's to anything other then the default 50 % ? thanks for the help

[Q] overclock issue

I'm using the virus rom airborne rc6 and the netarchy 4.3.4 kernel. I went to the app market and downloaded the overclock widget since I had used it on another evo. Whenever I set it up or go to set it up I should say the phone locks up and requires a battery pull. Start the phone back up and it freezes again on the lock screen not allowing you to use it. A restore or wipe is required. I was thinking it was the Rom or kernel so I downloaded valpeak Rom and a kernel and it did the same thing on it. Just wondering if anyone had heard seen or experienced something like this before ? Is there another over clock program that's good and stable ?
Thanks in advance
Virus Rom airborne rc6
Netarchy toastmod kernel
jshaddix865 said:
I'm using the virus rom airborne rc6 and the netarchy 4.3.4 kernel. I went to the app market and downloaded the overclock widget since I had used it on another evo. Whenever I set it up or go to set it up I should say the phone locks up and requires a battery pull. Start the phone back up and it freezes again on the lock screen not allowing you to use it. A restore or wipe is required. I was thinking it was the Rom or kernel so I downloaded valpeak Rom and a kernel and it did the same thing on it. Just wondering if anyone had heard seen or experienced something like this before ? Is there another over clock program that's good and stable ?
Thanks in advance
Virus Rom airborne rc6
Netarchy toastmod kernel
Click to expand...
Click to collapse
You need to clock it at a lower maximum speed. Some chips can't handle overclocking as well as other chips can. My phone can only be overclocked to like 1.1, and anything over that, I have the same issues you are explaining. Set the maximum speed a little lower and see if that helps.
That's just it when I try to set it up it freezes. I contacted the developer of the app and they said its on my end. I used the valpak before and could clock to 1.2 I'm wondering if there isnt something wrong with the kernels lime maybe they did a software update on the app and it doesn't agree with Rom or kernel. I've heard good things about set cpu I may try it. Thanks for your help
jshaddix865 said:
That's just it when I try to set it up it freezes. I contacted the developer of the app and they said its on my end. I used the valpak before and could clock to 1.2 I'm wondering if there isnt something wrong with the kernels lime maybe they did a software update on the app and it doesn't agree with Rom or kernel. I've heard good things about set cpu I may try it. Thanks for your help
Click to expand...
Click to collapse
Yeah I know what you mean, you just gotta hurry and get into the app and lower the max speed before the app gets superuser permission and freezes again. Or if you have the SDK on your pc and know how to use adb, you could remove the app from the phone while connected to a pc in recovery. Also, I use setCPU, and I've had nothing but good experiences with it. I've never used Overclock widget so I can say anything about it.
try flashing a different kernel its happened to me before and thats what i had to do then i changed the max and flashed back to the other kernel
re
Leukay said:
Yeah I know what you mean, you just gotta hurry and get into the app and lower the max speed before the app gets superuser permission and freezes again. Or if you have the SDK on your pc and know how to use adb, you could remove the app from the phone while connected to a pc in recovery. Also, I use setCPU, and I've had nothing but good experiences with it. I've never used Overclock widget so I can say anything about it.
Click to expand...
Click to collapse
Thats how i fixed it. I ended up using the computer to remove the app and used setcpu. I normally dont care about the over clocking ability but the battery life sucks on the virus Rom. The roms great just crappy battery life. Thankfully that worked we will see if by underclocking it helps if not ill have to look for a different Rom. Thanks for your help man.

[Q] SleeperRom DRM Service killing battery?

I froze all of the DRM services as shown in the picture below, yet it is still hogging battery resources as shown below.
Does anyone know how this is possible and how to fix this?
I'm using SleeperRom 1.0.11 and Shadow Kernel 1.03+.
Thanks.
That doesn't help. Percentages don't mean anything. ALL your applications have to run through android system. Take off android from your phone and you can't run anything. To see what is using your battery check Betterbatterystats. What files have the most time on them? Check processes and partial wakes if your battery drains while your phone is in standby. Also get CPUSpy and make sure your phone goes into deep sleep when in standby and not on charge.
Just because it lists DRM in the android system does not mean it is using more than a second or two of quick checking services. This is why some apps screw up if it is removed instead of just frozen. It has to check if the files are still on your phone.
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
after checking betterbatterystats, I don't even see the DRM service anywhere within the app, so I guess that is good.
I guess my phone just doesn't agree with the update to sleeper 1.0.11 and shadow 1.03+
akuentzler said:
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
Click to expand...
Click to collapse
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
kennyglass123 said:
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
Click to expand...
Click to collapse
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
akuentzler said:
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
Click to expand...
Click to collapse
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
kennyglass123 said:
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
Click to expand...
Click to collapse
I think the major difference is the shadow kernel and the use of voodoo color. I was previously on samurai 2.0.6 or 2.0.8 i think.
I have always had auto brightness on. Betterbatterystats did not reveal anything out of the ordinary.
I guess i'll just try a new rom/kernel combo and see if I can get better results. Thanks for your help Kenny. Betterbatterystats is a nice tool i had not known about.
No problem. I did find that voodoo color and the voodoo control app use a little extra battery plus having to increase brightness a little with voodoo color used up a little more battery.
Sent from my SPH-D700 using XDA App

[Q] KT747 Kernel Help

Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah I read your post earlier in that thread and was using your settings. I've come across a newer problem, my phone randomly reboots. I don't know what was causing this so I restored default settings.
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
DarthDerron said:
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
Click to expand...
Click to collapse
I doubt locking the frequencies has anything to do with your reboot problems, this simply dissallows any apps that are capable to override the voltage settings for any particular frequency step. In fact, unchecking this may actually give you a false positive of it 'fixing' the problem when it is actually just using the default (or higher) voltages, burning up more battery in the process. As mentioned by jethro and liltitiz its more likely your UV settings, keep playing with them until you find the happy spot (works on other things too....:silly.
jethro650 said:
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
Click to expand...
Click to collapse
Or just move the ktweaker apk from the /system/app directory from a recovery based file manager. This will keep it from launching on startup and then can either be moved back or ran to reinstall. This way you dont have to cleark the dalvik cache, which should be done any time a kernel is installed, eliminating the extra long boot time when this is done. Either the built in TWRP explorer or the Aroma File Manager which can be 'flashed' in recovery. It doesn't actually flash anything, just unpacks, runs, and then is dumped from memory on reboot...very handy if you dont have TWRP or can't get into android.
liltitiz said:
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I was wondering what was going on. I restored stock Voltage and realized that it was the problem.

Categories

Resources