I am having a problem with my screen staying on long enough to unlock it. It also happens when in a call and I need to push a number. When I push power to unlock the screen, it only stays on for a fraction of a second then goes out. The bottom row of buttons stays light and will vibrate if i push them but nothing happens. It will do this over and over until finally it lets me unlock the phone. Also when I am on a call and remove the phone from my ear the screen does the same exact thing. Stays on only for a fraction of a second and so on........... This is my third G2X and my first one did this as well. I don't use any kind of lock screen app such as widget locker and when I do try it, it still does the same thing. Anyone have any Ideas???
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
jcbofkc said:
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
Click to expand...
Click to collapse
I do, and I use the same profile you mentioned. I am going to switch it now and try that. Thanks for your quick help!!
(Edit) Yes, that seems to be the culprit. I froze SetCPU for now and problem solved. Now I will change the settings to 312-216. Thanks Again
Happy to help. I am new to this android stuff, but I am beginning to figure things out through trial and error.
Related
I am running Tiamat 1.3.2 and after a reboot setcpu ignores my settings and and the zoom runs at 216mhz. I can go in and move the slider and it will work fine until next reboot. Any ideas?
Is there a checkmark in the "set on boot" box?
Yes, should it not be there?
It should be checked. Did you set up any profiles? Before i had any profiles set up when i powered off the screen my xoom would scale down to something absurdly slow, like 256mhz. (Guessing since i dont have it with me currently) See if that makes a difference.
i haven't set up any profiles. I am still researching what profiles would suit me best. I will go in and set up a temp profile just to see if it resolves the issue
I have the opposite (sort of) problem. No matter what i set the max rate to on setcpu, it sometimes still maxes out to 1504. Anyone have this issue?
I had the same problem with it jumping to 1504 when I had it set to 1200. I tried Droid overclock as well and still had instability issues. I've went back to stock until there is more development. I could care less about overclocking and am pretty sure it was causing my Xoom to force reboot all the time.
Sent from my Xoom using Tapatalk
Brenardo said:
I am running Tiamat 1.3.2 and after a reboot setcpu ignores my settings and and the zoom runs at 216mhz. I can go in and move the slider and it will work fine until next reboot. Any ideas?
Click to expand...
Click to collapse
Are you moving the minimum slider or the maximum? It will run at 216 when you aren't doing anything, then when it will run at whatever you have set as maximum when you're doing something.
Move the slider if tge numbers at the top doesnt move then u may have to disable perflock
Sent from my HTC Desire using XDA Premium App
Just noticed the same issue. Had it set to performance 200/1500 and it would never go above 1500 after I rebooted untill I touched one of the sliders.
Flashed 1.4.0 and now I don't seem to be having any issues.... who knows? Anyway I hope it is fixed as it was quite annoying when unlocking to use to have to mess with SetCPU everytime.
I hope everyone else gets their fix too.
I actually first noticed this on timian 1.4.0, but that was also the first time I tried changing to the performance profile.
Does anyone knows how to use SETCPU app for G2x? I read somewhere states that if setting the min at 312 will help/reduce the freeze problem. I downloaded the SETCPU app but has no clue what to do, under menu/devices it does not list G2x phone. Please helps. I'm running EB 1.04, besides the freeze problem, no complains. Thanks much.
Open SetCpu. Click the bottom left key (settings). Click on device selction. Choose Tegra 2. It will check for root. Follow the steps. Next click profiles. Choose Screen Off. Set to max 312, min 216, prority 100.
On the main screen, I use max 1000, min 216.
Those are the settings that have seemed to work the best for me.
Be sure to clink on the "set on boot" option on the main screen. Hope that helps.
jcbofkc said:
Open SetCpu. Click the bottom left key (settings). Click on device selction. Choose Tegra 2. It will check for root. Follow the steps. Next click profiles. Choose Screen Off. Set to max 312, min 216, prority 100.
On the main screen, I use max 1000, min 216.
Those are the settings that have seemed to work the best for me.
Be sure to clink on the "set on boot" option on the main screen. Hope that helps.
Click to expand...
Click to collapse
Thank you for your help.
Mine are
general
1000max 216min
screen off
216/216
Running same settings as OP. Really love the extra battery life with the screen off profile.
The only problem I have with running that profile on screen off is sometimes when I get a call it takes too long for the phone to "wake up" and I end up missing the call. However since i adjusted it to min 600 (something) it hasn't been an issue.
dreggs said:
The only problem I have with running that profile on screen off is sometimes when I get a call it takes too long for the phone to "wake up" and I end up missing the call. However since i adjusted it to min 600 (something) it hasn't been an issue.
Click to expand...
Click to collapse
Same here. I also added an In Call profile so that when the screen turns off during a call it doesnt lower the CPU speed.
Hey guys,
I noticed another issue but don't know if it's rom-related.
When I push the power or volume-button to wake up the device, it sometimes takes 3-5 seconds until it wakes up and display powers on.
It seems that this issue is showing up more often than a few days before. I would say it happens every 5th to 8th time I wake up the device. :-/
Can anyone confirm this?
Check your minimum Clock speed i.e. in SetCPU or NoFrills what is the minimum speed the processor can run at?
If it's very low then increase it a little.
Minimum CPU-speed is 384Mhz set through SebastianFMs kernel I think. Will NoFrills overwrite kernel settings for testing?
I've tried to understand this app, even paid for it but can't seem to "get it" now that it is running. I set max to 1900 and min to 384. The settings hold on reboot, but screen says max is only 1350. I don't understand the profiles, regardless of which I choose nothing changes. Anyone willing to give me a 101 on this please?
jcool13 said:
I've tried to understand this app, even paid for it but can't seem to "get it" now that it is running. I set max to 1900 and min to 384. The settings hold on reboot, but screen says max is only 1350. I don't understand the profiles, regardless of which I choose nothing changes. Anyone willing to give me a 101 on this please?
Click to expand...
Click to collapse
power saving mode (in the notification bar... the stock function from the factory) limits it to 1350 when on. turn it off, and BAM back up to full speed. at least on my phone.
That did it, much THANKS!!!!!