I am having an issue with 7.0.2 and #58 with Pershoot, where the phone boots up to the maximum 1516MHz, no matter where I have it set to. I have to go into SetCPU, and for an instant, I can see that it is sitting at 1516, and then it jumps down to where I have it set (1152). Until I go into SetCPU, I have the screen wake issues, and occasionally a reboot. Has anyone else seen this?
Related
It seems to me my desire sometimes gets stuck at the max frequency. It happened to me using OpenDesire and Deforst.
I was wondering if anyone had this problem before? It shows me in setcpu that it's at the max frequency. I know its not a display/visual error in setcpu because when I use linpack I get around 5-7Mflops.
I'm not downloading or syncing anything in the background. I tried leaving the phone alone for a few mins and it's still stuck.
I have to reboot the phone to fix the problem. Does anyone know of an application that shows what the CPU is doing so maybe I can find the problem.
Thanks
im having a problem with incoming calls. half the time it works fine, screen pops up...no issues. the other half the phone will ring/vibrate/light will blink but the screen wont pop up.
rooted, currently running CM 7 RC4, but any rom ive loaded does the same thing. any fixes anyone knows of? i also downgraded to CM stable 6.1 and it does the same thing.
is your phone overclocked or underclocked? are you using set cpu and have a screen profile set?
Are you overclocked? If you are, search for "wake issue" to find a solution. Basically, you need to increase the max of your screen off clock speeds until it goes away.
Sent from my HTC Vision
yes overclocked, using setcpu. not using a screen profile set...i will look into that now. also look into the wake issue. thank you.
make sure if you set a screen profile no to set cpu speed to low or you will have the same issue
Sometimes when I set my phone down - regardless of battery level - my epic shuts itself down - anyone seen this issue - boots right up when I notice it is off but no shut down sound or any other warning - any ideas? his has happened on multiple roms, stock, SRF, a couple of others - thanks
Are you under clocking and/or undervolting your phone at all? Mine was doing this like 3-4 times a week. I was underclocked to 200 on Twilight 1.1.1 using conservative setting.
I haven't experienced a shutdown since I reverted back to stock lowest speed of 400. You may want to try that or jump to a different kernel.
I tried using CPU Tuner and also SetCPU (not at the same time). Both have significant problems on my phone. At first, both seem to work just fine, but after a few hours they each cause my system to freeze. The problem goes away if I restart and disable whichever one is active.
I'm running 4.0.3 on T989UVLE1
Kernel 3.0.8-perf-T989UVLE1-CL508451
Build IML74K.UVLE1
Anyone else seeing this?
Hi all
I'm experiencing issue with phone app. As you know, in call, the screen turns off when the phone detects something on the glass. The Note II is pretty fast to do that. But when you want to open contacts, or record the phone call, or find a mail without hanging up, it takes 3 seconds for the screen to switch on. Really annoying.
Sometimes it works pretty perfect, sometime not. I don't think it is a hardware problem.
3 seconds is pretty short but very long when you are in a hurry.
Is anybody else experiencing this kind of problem ?
I've tried to change the CPU governor and also the CPU idling rules.
=_=_=_ OMEGA 7.3 / redpill or Perseus
I've also flashed the stock kernel XXDLJ2 (seems to be a "little" more responsive)
Maybe I'm missing a tweak in stweaks that could solve this problem (ie: no underclock when calling or more CPU power....)
Thank you for help