Database Users

G1 Doesnt Always Wake Up

Does anyone elses G1 not wake up when Menu is pressed? Sometimes I have to press it like 6 times before the phone wakes up, does anyone know why?

Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.

momentarylapseofreason said:
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
Click to expand...
Click to collapse
Yea, i was thinkin the same, i should try runnin a ton of apps and find out if [email protected] the problem

mine does the same things sometimes. gets annoying at times. usually i just open and close the keyboard

Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!

brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
Shop Savvy?

I also started having the wake up problem and quicker then normal battery drain. I have an ADP1 phone which I updated to 1.1 a few days before noticing issue
I think that the theory of something sucking clock cycles is a good one. I noticed my CPU Usage (when nothing was running other then System Monitor) went from 0-40% to 20-70%.
I couldn't be bothered with the finer points of troubleshooting, so I took the thermo-nuclear approach and did a factory wipe.
Just before the mystery CPU cycle and wake up issue, I hadn't installed any new apps, BUT I did update a bunch of existing apps. After the factory wipe, I left off installing the following list:
Watts
StreamFurious
DroidFTP
Telnet
e-VoiceRecorder
VoiceRecorder
Constitution
Barcode Scanner
Astro
RingDroid
SlovoEd Classic English Dictionary
Things are fine now.

both of my g1's do this, and have done this out of the box, anyone turn off there screen with the keyboard out, and then close the screen and the screen comes back on with the lock screen up and then having to turn the screen back off? annoying

try the swapper app?
or turn phone off and back on, it might becuase you are usingahome or openhome or dxtop or sweeterhome, these app may slow down the interface a bit, try downloading droid sans tweak lite and fool around with that..
goodluck i also get this sometimes

brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.

Hmm, im not experiencing any of the above posted issues, it may be a particular app that u have installed. I only have the wakeup issue sometimes, most likely when the phone is running slow from the browser or another memory draining app, but no app in particular.

Hmm, when mine fails to wake up, I never waited long enough for it to come back, just reseated the battery for a reboot.
Of the other problems, I have the "screen-black-for-a-few-before-caller-picture-shows-up" issue.

JayBachatero said:
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Click to expand...
Click to collapse
what firmware do you have?
btw, dont count on Locale to turn off your stuff all the time, its not very accurate imo, at times its great, but thanks to the crappy g1 battery, they have a choice, constantly check time/location/.ect and drain the battery in a hour flat, or periodically check it and reduce battery drain, do you have any wifi programs that keep wifi on when phone sleeps (such as wifi lock and so on)? if so use the program on the market that writes up a log of its actions and see if its acting up
as for #1 (sorry im unorganized) my phone does that too, i believe its because i have 2 programs that run when the phone rings, let alone im sure locale is checking to see who is coming since thats a condition, which would make 3, and then i have a mp3 that plays when the phone rings, and i have a class 4 sd card (i know, i know), the way that programs work is that it has to go line by line of the code, if it is slowed down, or it has to execute other items before continuing that are slow to execute, than everything has a delay, but yeah from time to time i have this issue, phoneplus was a program that made me miss a few calls (1/4th of the time)
i think 3 and 4 are directly related, could be wrong

I was having the same problem right after I installed the app "Contact Owner"
No amount of reboots fixed the problem. Uninstalled and everything was back to normal.

@wootroot - I have stock RC30. Haven't rooted yet.

JayBachatero said:
@wootroot - I have stock RC30. Haven't rooted yet.
Click to expand...
Click to collapse
consider upgrading to the rc33 ota update yet? i had better battery life (and my battery didnt get as hot) when i used rc33
also, if youve had your phone since it first came out (rc19 i believe) and your battery used to get very hot, you might of damaged some of the cells (especially of the battery has expanded), if this is the case simply call tmobile and tell them that your noticing even after wiping the phone that your battery life is lasting shorter and shorted, even with out any programs installed from the market, i even went as far as to say that i made sure wifi was off, only 2g was on, gps was off, screen was dimmed, timeout set at 30 secs, and im still only getting a hour of life (none of which is true but it got through all the "well how about trying this and calling back if you still have a problem" bs, with the ota rc33 and the new battery, i noticed a pretty good difference

I have a modified version of this "doesnt always wake up". The phone is less than 24 hours old, it was a refurb they sent me for the last one that went dead. I used it with the rc33 it came with and found the problem, then figured it was hosed so i rooted and installed 3 of the versions of cupcake (The Dude, JF, and Haykuro) to see if they all had the issue- they do. Here is a video, hope you can see the attempted keypresses. There will be lines that appear, like the screen is broke..then, they will go away. Sometimes it takes 5 minutes to get the phone to turn on, however if I leave it on (never goes to sleep) it works flawlessly.
http://www.youtube.com/watch?v=ecQo2Ly2WUM

I get this all the time also...
Uninstalling dxTop doesn't change anything for me...it still acts the same...
I also get the problem that when someone calls me the screen stays blank for about 5 seconds and I can't tell who calling...

wake up issue
I am experiencing the same problem, with a brand new warranty replaced G1, what happens is when the phone goes to sleep it completely locks up, when I try to wake it up via menu, it does not wake. Plugging the phone in and trying ddms or adb does not work, ddms shows the phone as offline, also the device seems to get really hot when this happens, sometimes Call + Menu + Power resets it, and sometimes I have to pull the battery.
I think this may have to do with wifi turned on. Because when the screen goes off your phone switches wifi off and goes to 3G as default setting.
I think we should try leaving wifi on all the time and see if that solves the issue, im about to try that now.
It seems this is a known issue over at tmo forums

A couple questions:
When this happens to you guys is wifi enabled and connected when the phone is shut off?
What Rom, SPL, and Radio is installed?
I noticed this didnt happen to me until I enabled wifi, maybe I didnt wait long enough because its completely random, please send back your results
defcon

Screen wont come on after Sleep

Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?

This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.

Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.

Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?

Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?

http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11

My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.

anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.

Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.

I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.

Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse

my atrix locks up

i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one

kga943 said:
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
Click to expand...
Click to collapse
Did you install any applications from the market? Is your phone freezing while a certain application is open or does it freeze even on the homescreen? If you have a lot of applications installed try to deinstall and look if it becomes better. If not try a factory reset. If it still freezes than return it for a new one.

Would you mind saying what you were doing when it locks up?
If it's during Music, it doesn't actually lock up, it just shows a black screen for about half a minute. Everything still functions, it just doesn't show.

Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App

I have a feeling there is a bad batch of units out there.
Try factory reset and see if it continues to lock up, if it does, return it for another.

kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sounds like a broken phone. Try a factory reset (if you return it they anyway ask if you did that) and if that won't help get a new one....

kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same thing happened to me yesterday, the light was very dim green and the phone did not respond until I pulled the battery. It hasn't happened again.
I've already had to replace my Atrix for another issue. Right now my confidence in this phone is not very high, but it is brand new. Lots of issues will probably pop up and be fixed via software updates- at least I hope thats the case.

It really feels like all the issues people are having with this phone are software related. Maybe motorolla will just cave and give us gingerbread with no blur

I've had the same problem while playing music...over the past 3 days after about 30 minutes of tunes it'll lock up and after another 5 reset itself...i've done the reset after the second and it still does it...i'm bout to take it back and exchange it...i expect glitches but damn.
Motorola Atrix (stock)
AT&T Fuze (Energy.RAPHAEL.21916.Sense2.5.Cookie.2.0.sencity)

I have had the issue happen 2 me twice in 3 days, the last time was when adding the note widget to screen. It was not completely locked up just the touch screen, i could press the power off button but the touch screen would not let me shutdown

something you might want to try if a factory reset doesn't work would be a reinstall from the recovery menu.
power your phone off
hold the down volume key and the power button
release the power button once the phone begins to boot
keep holding the down volume button until you see "fastboot" at the top of the screen
now be careful, the down volume button navigates through the boot options and the up volume selects one
so press the down volume button until you come across "android recovery"
once you see it press the up volume button to select it
once you get to the screen with the exclamation mark tap the bottom right of the touchscreen, this should pop up the recovery menu
select wipe data/factory reset
let the phone do it's thing
good luck
I've seen this resolve some audio codec issues that were causing the phone's mic to not work, dunno if it'll work for your issue but it can't hurt to try.
best of luck
bl4ck0ut

I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.

mrlinux11 said:
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
Click to expand...
Click to collapse
I have the same problem (screen randomly locks up once or twice a day, buttons dead) and have found the above "solution" to work perfectly, also. The problem however is that pressing the power button twice and unlocking the phone is not exactly elegant especially if the screen locks while you are trying to answer an incoming call.
I changed my battery settings to "performance mode" as I read somewhere that that might help. I will let you know if that seems to resolve the issue.

Changing battery setting doesn't seem to do anything. I still get my share of frozen/locked up screens a few times a day. Still have not figured out how to replicate the behavior. It really does seem random.

I've been suffering from this as well, I'm going to try to exchange my phone and see if that helps.

Exchanged my phone today. So far I haven't seen any locked/frozen screen issues. I am relieved. Maybe there are just a few bad units out there.
Also for what it is worth ... the lady at AT&T told me that taking out the battery while the phone is on would fix it. Since I never figured out how to replicate the behavior I couldn't verify that her suggestion would indeed actually fix the problem and demanded an exchange anyways.

atrix does lock up and have glitches
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)

It happened to me as well. I had installed some apps but when it froze it had been off (the screen that is) so it was sitting then when I tried to open it by pressing the power button the green light came on but it would not wake. I removed the battery, replaced it then it did the same thing again (including the green light). I removed and installed the battery once more then it was fine. It must have been something in the backround but not sure as to what that was. Hasnt happened again though.

pedroosan said:
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
Click to expand...
Click to collapse
strange, skype worked for me... oh well.
did you ever find a solution for the lockup issue, have the same thing, very frustrating but not as frequent as you thankfully.

My Atrix started to freeze up when I undervolted the CPU using SetCPU and I would have to pull the battery out and restart it. I increased the voltage settings and it hasn't locked up since, so if you have undervolted your CPU and your phone is locking up, you should increase the voltages.

Xperia Play Continually Freezes/Blank Screen/Buttons Unresponsive

Hi All
This problem happens to be quite frequently when using my xperia play. The problem consists of the phone itself basically freezing with the screen going blank and the buttons go unresponsive.
This problem usually occurs if I have to force close a program or there is a long download in the background. When I key lock the phone after a force close or the phone key locks itself during a long download this issue occurs.
Just to let you guys know, the phone itself is actually still on but the screen is blank and off. It still gives msg alert tones, it still rings when someone calls and it even clicks when the phone is unlocked but I cannot attend to these things as the phone is unresponsive.
My only solution at this point in time is removing the battery and putting it back in to reboot the phone. I have also tried to repair the phone using PC companion and also re-flashing the ROM with no resolution.
If anyone is having any similar experiences or if anyone knows of any fixes please let me and others know.
Thanks Guys and Girls

Are you running a custom kernel at lowest clock speed? (122mhz afaik) and/or are you undervolting it? Do you have a profile in setcpu for screen off, with lower clockspeed or/and undervolting?
If yes that might be the problem and then try to run it at 256 mhz normal voltage and see how that goes.
Regards Dousan...

I've had similar problems ever since I got this phone, happens randomly, just slows down and screen takes a while to go back on. I've never had to pull the battery cause of it, is like the phone is doing a lot of stuff or a lot of apps are running so it slows down and won't perform done tasks like turning on the screen
Sent from my R800i using XDA App

Me too
came across the same problem on all roms. try changing cpu governer. read at rootzwiki that smartass can cause those issues.

screen becomes unresponsive just seconds after reboot

First off, I'm on PA 3.1 and faux 3.4.
Just like the title says, the screen becomes unresponsive and the only way to fix it is to do a reboot through long press of the power button, I'd have to sit there and wait for the phone to reboot, it enters the lock screen, and immediately slide to unlock, then everything works fine afaik.
So the problem happens when I reboot the phone, and it enters the lock screen, I don't touch it and the screen turns off. I come back to the phone, pressing the power button wakes it, but the screen is never responsive.
Anyone experienced anything like this?

Could it be PA includes the touchscreen fix? AFAIK the touchscreen fix requires ~30 seconds to install after a fresh boot.

Plus there's no telling what he's modded or edited too. The Op never specified what he has done.

I had this same problem when I updated to the latest pa and flashed acid audio mod one after the other. The problem was the acid mod, the problem was gone after I deleted it.
Sent from my Nexus 4 using Tapatalk 2

I've never heard of acid audio mode, couldn't find it in titanium backup...

Have you flashed anything else other than the rom and the faux kernel? if not, Try flashing stock kernel see if that make a difference.

AftermatH101 said:
First off, I'm on PA 3.1 and faux 3.4.
Just like the title says, the screen becomes unresponsive and the only way to fix it is to do a reboot through long press of the power button, I'd have to sit there and wait for the phone to reboot, it enters the lock screen, and immediately slide to unlock, then everything works fine afaik.
So the problem happens when I reboot the phone, and it enters the lock screen, I don't touch it and the screen turns off. I come back to the phone, pressing the power button wakes it, but the screen is never responsive.
Anyone experienced anything like this?
Click to expand...
Click to collapse
Are you modifying your voltages by any chance? If your voltage is too low then your phone will become unstable. I can imagine a scenario where immediately upon start up, your phone is running at high clock speeds, and the voltages for that are just fine; but then when it goes into idle mode, the voltage for the lowest frequency step might be too low and therefore causes instability. Pressing the power button creates a demand that suddenly chokes the processor, and bam, unresponsive screen. Otherwise, it might be some startup scripts causing issues, and you should double check those (but I have no experience with startup scripts).

amartolos said:
Are you modifying your voltages by any chance? If your voltage is too low then your phone will become unstable. I can imagine a scenario where immediately upon start up, your phone is running at high clock speeds, and the voltages for that are just fine; but then when it goes into idle mode, the voltage for the lowest frequency step might be too low and therefore causes instability. Pressing the power button creates a demand that suddenly chokes the processor, and bam, unresponsive screen. Otherwise, it might be some startup scripts causing issues, and you should double check those (but I have no experience with startup scripts).
Click to expand...
Click to collapse
I don't understand how it only happens at that time... but not the hundreds of other times when I unlock the phone from idle mode.

I have the same problem. I used PA versions with FrancoKernels ( from 111 to 122 ) and i had no issues, Then i jumped to the Faux kernel cause i was reading about exreme battery stats. I used the recomended settings from his post via his app. And i UV to -100mv and i used the setting that let you wake it via touch , SleeptoWake. Still havent cleared what is it. Now i play with some settings. With -87.5mv i managed to reboot it and respond.
The one thing that i want to mention is its randomness. It happens only in reboots - turn on and not every time. I guess the problem its in my settings/Uv maybe .Respect to all developers
Waiting for others who have face it.