This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
First off, thanks for letting me know SetCPU is up to 2.0b. I was still running 1.6.0. I get mine free (and legally) but I have to do manual updates as a result and I hadn't checked in a few days.
Okay, have you read Overclocking 101 by Skull One? If not, take a look, it tells you a lot.
Secondly, you're running the vanilla FRF57 FroYo RC? I thought I was the only one left (though I did Black Glass theme it)!
Without a CPU temperature monitor we really don't know what's going on inside our phones. Battery temperatures tend to be more stable (on both ends) than the CPU temperature, so you could be spiking insanely high really quickly and you wouldn't know till it hits your battery, though the issues you're having sound very much like an overheating CPU.
Since you can only push the phone to 1Ghz right now, I'd suggest you try a higher-clocked kernel, push it to 900 or 1000 mhz for now, let the phone charge overnight (so it can cool off) and try pushing it higher and see if you have the same issue and if it's an instant thing or not. If it still happens instantly there's an issue with your hardware not handling the increased speeds under 2.2 (I think it might be a JIT issue), if it takes a moment it's heat. If it doesn't happen at all, it's heat.
If you don't want to put up with the crap, just run it at 900 and be grateful you're not stuck with one of the ones that can only run 600, 700, or 800mhz kernels!
Of course, someone else might know more than I do and have other suggestions, but that's my opinion.
Oh, and ChevyNo1's ULV kernel, if it works for you, will generate the least amount of heat and use the least amount of juice, so if you're stuck at 1Ghz, you might as well run 1Ghz as long as possible, right?
If you got SetCPU on the market it's legal. I was just making sure nobody thought I was warezing their favorite program.
From what you've said it sounds like temperature is the most likely culprit here. I had issues the first time I tried to push past 1.1Ghz on mine because it was a flipping hot day and I'd been wifi tethering for a while so my battery as well as the CPU were both hot to begin with. 1.1 is the upper limit for my phone, heat-wise, and even then if I do heavy browsing I can overheat it. 1.0 is stable and cool all day long, so that's where I leave it.
Oh, and make sure you're not running on performance mode all the time. If you're having any kind of heat issue to begin with that'll make it ten times worse.
I'm not sure I like the new SetCPU, but I'll admit it gives the user a lot more control.
Let us know how it behaves tomorrow once it's had a chance to really cool off.
it's the same as the old set cpu just looks different. You can still add in all you're profiles (battery and all the other profiles in the old version) and add in more if you see fit. You're no longer limited to the number of profiles the dev put.If you got SetCPU on the market it's legal. I was just making sure nobody thought I was warezing their favorite program.
From what you've said it sounds like temperature is the most likely culprit here. I had issues the first time I tried to push past 1.1Ghz on mine because it was a flipping hot day and I'd been wifi tethering for a while so my battery as well as the CPU were both hot to begin with. 1.1 is the upper limit for my phone, heat-wise, and even then if I do heavy browsing I can overheat it. 1.0 is stable and cool all day long, so that's where I leave it.
Oh, and make sure you're not running on performance mode all the time. If you're having any kind of heat issue to begin with that'll make it ten times worse.
I'm not sure I like the new SetCPU, but I'll admit it gives the user a lot more control.
Let us know how it behaves tomorrow once it's had a chance to really cool off.
Could you explain how it gives the user more control? I see it as giving the user less control, specially with battery. Am I missing something?
HIit's the same as the old set cpu just looks different. You can still add in all you're profiles (battery and all the other profiles in the old version) and add in more if you see fit. You're no longer limited to the number of profiles the dev put.If you got SetCPU on the market it's legal. I was just making sure nobody thought I was warezing their favorite program.
From what you've said it sounds like temperature is the most likely culprit here. I had issues the first time I tried to push past 1.1Ghz on mine because it was a flipping hot day and I'd been wifi tethering for a while so my battery as well as the CPU were both hot to begin with. 1.1 is the upper limit for my phone, heat-wise, and even then if I do heavy browsing I can overheat it. 1.0 is stable and cool all day long, so that's where I leave it.
Oh, and make sure you're not running on performance mode all the time. If you're having any kind of heat issue to begin with that'll make it ten times worse.
I'm not sure I like the new SetCPU, but I'll admit it gives the user a lot more control.
Let us know how it behaves tomorrow once it's had a chance to really cool off.
Could you explain how it gives the user more control? I see it as giving the user less control, specially with battery. Am I missing something?
Sent from my Tapatalk using Droid
