Screen on screen off problem Vision rom - G2 and Desire Z Q&A, Help & Troubleshooting

I just flashed the vision rom on g2 about 6 hours ago earlier today from Rom Manager and its running great except that when the phone goes into screen off mode, and then i try to turn the phone back screen on the screen stays black but the bottom 4 buttons still glow, and when i click stuff on the screen it clicks them but its black and there is NO brightness at all NO LIGHT lol, now this isn't the phones problem because on the normal froyo backup i have it works fine, but i am in love with sense, except it really pisses me off that it does this, if anyone can help it would be great or if someone has experienced this issue and found any way to solve it, please let me know how. If you want a video let me know i can make one.

TheRealEvo said:
I just flashed the vision rom on g2 about 6 hours ago earlier today from Rom Manager and its running great except that when the phone goes into screen off mode, and then i try to turn the phone back screen on the screen stays black but the bottom 4 buttons still glow, and when i click stuff on the screen it clicks them but its black and there is NO brightness at all NO LIGHT lol, now this isn't the phones problem because on the normal froyo backup i have it works fine, but i am in love with sense, except it really pisses me off that it does this, if anyone can help it would be great or if someone has experienced this issue and found any way to solve it, please let me know how. If you want a video let me know i can make one.
Click to expand...
Click to collapse
You have overclocked right?
this is a very common problem
what you need to do is set up a screen of profile on setcpu
min:245
max:368
scaling : powersave
and make sure you tick Enable on profiles menu
this should solve your problem.

bahmanxda said:
You have overclocked right?
this is a very common problem
what you need to do is set up a screen of profile on setcpu
min:245
max:368
scaling : powersave
and make sure you tick Enable on profiles menu
this should solve your problem.
Click to expand...
Click to collapse
Thank you for the information, just set everything up the way you said to and gonna give it a test now, thank you!!
Edit: also, i have it clocked at 1420 max and 800 min, and a set profile for the one that you gave me and one so if it overheats to clock itself down, should i keep the min to 800 or should i make it lower, this is for when the phone is on, when it goes screen off it goes into the profile you gave me, thanks.

TheRealEvo said:
Thank you for the information, just set everything up the way you said to and gonna give it a test now, thank you!!
Edit: also, i have it clocked at 1420 max and 800 min, and a set profile for the one that you gave me and one so if it overheats to clock itself down, should i keep the min to 800 or should i make it lower, this is for when the phone is on, when it goes screen off it goes into the profile you gave me, thanks.
Click to expand...
Click to collapse
why do you have your min at 800 mhz anyway?
there is no need for that put the min at 245 your phone will scale up when it needs
to. and for scalling, ondemand works for me best ,you can can try different ones to see which on gives you better performance and battery life. dont use performance scaling for everyday use though .

Related

Cyanogenmod screen delay

I love cyanogenmod for many reasons, but everytime I try, one thing kills me.
It I hit the power button when the screen is off, it often takes 5 or 6 seconds to turn on. Has anyone else had this problem and solved it?
Mind you, this has happened under many versions of CM (but on 6.1 right now) with different kernels and sometimes having setcpu profiles.
Any ideas?
Thanks in advance.
newsoundwave said:
I love cyanogenmod for many reasons, but everytime I try, one thing kills me.
It I hit the power button when the screen is off, it often takes 5 or 6 seconds to turn on. Has anyone else had this problem and solved it?
Mind you, this has happened under many versions of CM (but on 6.1 right now) with different kernels and sometimes having setcpu profiles.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
it normally has something to do with setcpu being clocked to low, try raising the min freq up to 245mhz
Actually, set the SetCPU minimum frequency to 384 MHz. That usually solves problems like this, or with the screen not turning on for a call, whereas 245 doesn't always.

[Q] CM6.1 wake issue

So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Only thing anyone can probably suggest is turning up your min clock speed. What are your profiles set to?
My screen off is 245/368 just to give it that bit extra to guarantee no wakeup issues, not that I had any to begin with, better safe than wanting to throw her up the wall (I get annoyed easy).
bahmanxda said:
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Click to expand...
Click to collapse
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Possible explination posted here by rmk40:
http://forum.xda-developers.com/showthread.php?t=884237
dhkr123 said:
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Click to expand...
Click to collapse
Thanks
no i didnt make any customization its just CM6.1 although my max clock speed is at 1497 mhz
setCPU
Screen off max 368
min 245
and profiles for temp and battery as well
the wierd thing is it doesnt happen at all when im just waking the phone up it only happens when its ringing i am thinking its my CPU issue ,i dont think it handles overclocking well ,i couldnt go over 1.1ghz (it would freeze instantly) with virouos that was the main reason i switched im gonna play with with cpu profiles for a while and see if i can get it fixed.
btw i have never flashed any radio so im guessing its the stock one
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
bahmanxda said:
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
Click to expand...
Click to collapse
With my experience I've noticed the phone runs better, and lasts longer on a single charge WITHOUT setCPU profiles. Just my opinion
bahmanxda said:
although my max clock speed is at 1497 mhz
setCPU
Click to expand...
Click to collapse
And there you have it. Overclocking can do weird things.
dhkr123 said:
And there you have it. Overclocking can do weird things.
Click to expand...
Click to collapse
Fair enough
Sent from my HTC Vision using XDA App

[Q] SetCPU and battery life - am I doing this right?

I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g

[Q] CM7 usually shuts down suddenly with direct screen black

CM7 version:
cm7.1.0-RC0-jordan
I flashed CM7 with new version,but usually shuts down suddenly,it goes black screen directly.I do not know if it's the clock rate's problem,this version switchs the default max clock rate to 1G .Do other people have the same issue?
Does your phone reboot? Because mine has twice since I installed this rom.
try to reduce the clock using 2nd int also may be your ram fills up...try to use advanced task manger and end task before playing heavy games...like plants vs zombiesHD, other Tegra games and others
Its most likely your device wont like the vsel settings of the rom try higher numbers and test it out every device is different this problem happened to me on another rom it would just suddenly turn off i set the vsel up and no problems after it
memz180 said:
Its most likely your device wont like the vsel settings of the rom try higher numbers and test it out every device is different this problem happened to me on another rom it would just suddenly turn off i set the vsel up and no problems after it
Click to expand...
Click to collapse
Thank all of you,and I reset the rate to 800MHz ,vsel to the default value,it seems this work.
You can run 1ghz it still wont shut down 1ghz is safe @58vsel to just letting you know because i find 800mhz to be a little laggy for my needs

cpu speed

since i cant post this in the dev for cm10 i have to post this here. i installed it last night on my phone and everything has been running pretty good. i understand its still a wip so im not complaining. what has come to my attention is the fact that my phone now likes to run at 1026 no matter how low i set it at. if its sitting there itll change to 384. when i was on stock rom rooted and unlocked, it would never change speed on powersave. now if i go into antutu or just performance under settings minimum will always change to 1026. i havent had a chance to really test if its affecting my battery life but i can let someone know. im bringing it up so maybe the devs can have their way with it. if theres any way i can help, just let me know.
0328 update
with the latest update the speed issue is still there and the camera has been improved although i havent tried video yet. but on 0327 it has like a staircase set up on the upper lefthand side of the screen. did a wipe and fresh 0328 so ill see how that goes. keep up the great work and as always let me know if there is anything i can do to help.
update:recorded video still has issue but nexus7 camera apps work perfectly to get to camera here. flash or the camera worked once and hasnt worked since. still a great rom.
It looks like you're not using the latest cm10 builds, you need to hit the "next" thing on the top right of the download page.
I recommend taking a spin with the houcha kernel. It's pretty much fixed the cpu stuff, and intellidemand governor is amazing; Turns off 3 cores when nothing is taxing and idles at correct minimums.
They are always up to date with the cm10 kernel commits as well.
I get amazing battery life.
Sent from my LG-LS970 using xda app-developers app
0429 update
yeah. its running pretty good. the video recording is fixed so that helps me out at work. with all the phones and tablets i have, i havent installed another kernal so thats the only thing im a little sketchy on doing. but since you recommend it i think i have to give it a look. if theres anything i should know about it, just let me know.
I was on the latest update but I just fat fingered my posts and wasn't double checking it. Just had to install a keyboard that better suites me.
update-flash on the camera work only when i use touch to focus. does that kernal help with that?
clean install of 5/5
Did a clean install last night with standard 4.2.2 gapps. Camera icon has has appeared without the need to install a 3rd party app to access it. Battery life is about the same as before with installing a different kernel. As my daily driver I would recommend it all the way. Follow the forums specific to the ROM and you can't go wrong. I'll keep updating about the progress until I can post on there.
powersave for cm10.1
If you want to get powersave to work correctly; 1.set both speeds to the same number 2.must be below 1026.
If you set them both to 1026, they will stay at that speed. If you set them to two different numbers the minimum and maximum will default to 1026 and1350, respectively, when the system feels it needs the power above 384 and will stay there. Hopefully this will help someone out.
The reason the cpu speed gets raised to 1026 is due to mpdecision. It boosts the cpu speed on touch to increase the interactivity and decrease the lag. mpdecision is a qcom blob and since we are trying to stay as close to mako as possible these is nothing I can do about that blob.
Then I guess my question is why on stock I can run at 384 min with max at 1512 on powersave and it'll actually run at 384 but this cant?
fine for me
I have not really had this problem at all weird
harrybear25 said:
I have not really had this problem at all weird
Click to expand...
Click to collapse
So what min and max speeds is your phone set at? What speed does it end up at after using it for 5 mins on the net?
5/14
my powersave settings with the max at 1512 and min at 384 seemed to stick longer than normal with this rom. im going to backup everything, revert back to zvb and then do a clean install of the latest and see how that fairs.
Did a full restore of my phone back to zvb. Did all the GPS stuff I needed to, rooted and unlocked. Proceeded to do a full wipe and install of 5/27 ROM. Speed issue still there but as noted before I found a small workaround and randomly today I got a message that maps had stopped working.
I did play around with the ROM before install gapps and found some interesting things. None really stuck out except Bluetooth not working at all.
After installing gapps, everything seems to work perfectly. Downloading 5/28 right now and dont expect much to change. Some updates hold my speed settings and some dont. Not really an issue.
6/1 build
powersave function was working correctly with the max at 1512 and the min at 384 right after initial update. using antutu the temp and battery level would be displayed incorrectly. after the first reboot though, everything went back to "normal." but on the brightside if you set the max to 918 and the min at 384 on powersave, it appears to now stay that way. no more having to set them both at the same speed. i will continue to play with the speed settings and see if anything else comes up.

Categories

Resources