Related
Hello boys
from about 1 week i have this problem on my device, if i have the keyboard out and write an sms or typing an url when slide the keyboard in the device automatically reset itself...
anyone knwo this problem or the solution ?
Thanks for the help
Nicola
Hi,
I have a problem with my keyboard too, I've searched the forum but i didn't see the same problem as i have or the solution. My phone's screen turns off when i slide out the keyboard. Actually phone stays on but the light of the screen goes off. when i slide it out i'm able to write something or make calls. when i slide it back, screen keeps itself off and i press the sleep key "2 times"!(screen looks like off but it isn't) to reopen it again. I press the sleep key for the first time to turn the screen actually off, and press it one more time to turn it on again. i did a soft and a hard reset to the phone, didn't solve it. I don't think it is a software problem but i hope it is
img714.imageshack.us/img714/167/70305198.png
These are the photos of the occasion.
The screen keeps itself on until the end of the slide. it turns off then. when I slide it back, i can see the backlight of the screen and the light of the buttons.( i don't think that you would see it on the photo, 3rd photo).
I'm waitin for your help guys, thank you so much.
Isn't there anyone to help my problem? I'm waiting for your answers..
I'm also having this same issue. When I slide the keyboard in it just turns off sometimes. At first I thought it might be a physical issue with the internals of the phone and the sliding impact of the keyboard was causing it to reset, but it doesn't do it all the time for me. I can jam on it and nothing happens sometimes, or other times it resets from a gentle nudge. I am running Energy GTX from August 26 or 28, whatever version that was.
I also have this issue now where my end key is unresponsive. Doesn't. Work. Ever. and that is so freaking annoying. If anyone has any insight here PLEASE share it.
Thank you.
Wow i just saw your message and suprised. Is that my phone you're using? Because I have that end key problem too. It works when I press too hard. And I have 3rd problem now. I think my phone's microphone is not working. People i'm talking on the phone is always complaning about that they can not hear my voice or it's too low. Now I have three problems:
1. Phone is turning itself off when i slide the keyboard out.
2. End key is not responsive.
3. Microphone is low or its broken..
Maybe reflash your phone to origional rom.
I was using WM 6.5 without hardspl when the problem occured. then i did hardspl and installed custom roms, i even tried with WM 6.1. It didn't help about any of it. I'm used to not using the keyboard actually, but the problem with microphone is annoying..
Same problem with the keyboard
gurcanmerdal said:
Wow i just saw your message and suprised. Is that my phone you're using? Because I have that end key problem too. It works when I press too hard. And I have 3rd problem now. I think my phone's microphone is not working. People i'm talking on the phone is always complaning about that they can not hear my voice or it's too low. Now I have three problems:
1. Phone is turning itself off when i slide the keyboard out.
2. End key is not responsive.
3. Microphone is low or its broken..
Click to expand...
Click to collapse
I have the same problem !!!! Did you manage to resolve because I am sure this is software relatred. I had android on my phone prior to this and fixated that the issue is coming from this
Had the same keyboard issues, found that it was a battery issue. when you shut the phone, the battery would loose connection.
bluewaterkayak,
more info on the loose battery connection.
i have the same problem with sliding the keyboard down and the screen turning off. closing it, pressing the sleep button 2x, turns the phone back on. i can slide the keyboard down just enough and hold it to type out a text, any more and it'll go off.
THIS IS SUPER ANNOYING
Bumpski. Really need this fixed.
What ever you last installed take it off. If not you might have to go factory restore
It's definitely not a software issue. The screen itself somehow gets disconnected when slid up all the way.
Took it apart and found nothing obvious wrong. Is there something to look at exactly when the slider is at the end of it's travel? The cables seemed fine. The problem only happens at the end of travel.
I cleaned the slider area and pried some contacts down. Nothing. Put it back together and same problem.
Ideas??
See here:
http://forum.xda-developers.com/showthread.php?t=561151
Tried the fix posted in the last link with Kapton Tape.
Didn't work.
Any ideas?
I have the same issue. My old VZW TP2 is sitting in a drawer in my house because people kept saying they couldn't hear me on the other end. Also on my new one, when i slide the keyboard in/out sometimes it turns off, not always though. I figured it has to be a hardware issue as well, if i do it slowly nothing happens but if i just slide it open and let the springs kick in, it usually cuts off once it 'snaps' to the end of the sliding path.
I need some help/advice.
I have a launch Evo(hardware v.2) and recently I have an issue where the screen will randomly become un responsive. I usually have to press the power button a few times to toggle between the black screen and lock screen to get it to work.
The other issue I am having is the status bar will not drag down. Sometimes it does, and there are also other times where it will sporadically lower and hide over and over.
I am rooted, and this has happened with Mym's and Ava-Froyo's roms with different kernel combinations. I have wiped and flashed the rom each time to make sure nothing is hanging over from a previous install.
Is it something software related or is it possible the hardware is going bad?
Thanks in advance for the help!
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app
hi guys, does any one else experience this problem..
i usually wake the phone up with the home button, but sometimes i press it, the image will pop up and then close and it will be asleep again, it will keep doing this for a while, but then a couple of hours later it will be fine..
ive experience this a number of times, abit annoying but the power button is there so not a major issue
Using: stock lockscreen with picture. Happened here as well, triggering the home button works for me.
I also have same problem sometime. Not a big deal, just an annoyance.
Sent from my SD4930UR using XDA Forums
glad im not the only one..haha
quite the same
This really bothers me, so does the absence of the amazon feedback or technical support.
I don´t think this is a problem caused by the home button.
I guess this comes from the proximity sensor under the front camera.
Cover it and it will be the same.
Sometimes i had the same problem in an dark environment with an screen protector at the phone.
Changing the screen protection worked for me.
I have the same problem. My phone is still in the clear plastic to protect as I'm not sure what I'm going to do with the device. My home button has never worked to awake the device.
The plastic protective cover is causing this.
Greeting,
I have a weird issue where occasionally after I unlock my phone, my screen doesn't respond to touches.
The phone works and responds to physical button presses but not touch.
Not sure exactly when it started happening but I've noticed this since last week.
Any idea what might be causing this?
I'm running Android Pie 52.0.A.3.202.
Sydrox said:
Greeting,
I have a weird issue where occasionally after I unlock my phone, my screen doesn't respond to touches.
The phone works and responds to physical button presses but not touch.
Not sure exactly when it started happening but I've noticed this since last week.
Any idea what might be causing this?
I'm running Android Pie 52.0.A.3.202.
Click to expand...
Click to collapse
Please upgrade to the newest firmware.
Sydrox said:
Greeting,
I have a weird issue where occasionally after I unlock my phone, my screen doesn't respond to touches.
The phone works and responds to physical button presses but not touch.
Not sure exactly when it started happening but I've noticed this since last week.
Any idea what might be causing this?
I'm running Android Pie 52.0.A.3.202.
Click to expand...
Click to collapse
Got the same issue on 52.0.A.8.50. Usually opening the app drawer then hitting back solves it - otherwise none of the virtual buttons work.
Searching the web it seems touch screen issues are pretty common on this phone. I'm a bit surprised there isn't more being said here about it. Some experience delayed response, dead areas and no response at all. I have all those issues. Yes I am on the latest firmware. I bought the phone used with a cracked screen. I checked it out and everything seemed fine. I didn't use the phone, just set it aside til replacement screen came. I should have used the phone to thoroughly check it out but didn't want to go through the set up process as I was thinking of B/L unlock and root. New screen came, put it on and seemed to be working fine then screen would be unresponsive. I did factory reset, software update, software repair, went into settings and made sure sure everything was good there, nothing helped. The center of the screen (it's low and a bit off center) is pretty much dead. To open launcher I have to touch and hold near the top of the display. Touch and hold apps is tricky. Usually the app just opens. When I do get it to hold, I can't drag it anywhere. Also, icons in the drop down menu cannot be rearranged or edited. I can swipe up/down, side to no problem. Whenever touch goes dead completely, the home, back and minimize buttons go grey. Tapping the power button gets them back functioning again. . Function test fail. Free draw lets me make a few seconds of scribbles then freezes. The x and rectangle block draw does the same. Tapping power button does nothing to unfreeze either. The color test pass even the block one where you toggle on/off sections of the screen in blocks. It's really weird. First impression would lead me to the screen but it really acts like a software issue. From what I've read so far this phone uses two different display drivers. I not seen anything on how to change that and it would more than likely mean B/L unlock and root, which I'm not against doing. I would just like to know definitively if it's hardware or software. Any input would be greatly appreciated.
Thanks
bobsright said:
Searching the web it seems touch screen issues are pretty common on this phone. I'm a bit surprised there isn't more being said here about it. Some experience delayed response, dead areas and no response at all. I have all those issues. Yes I am on the latest firmware. I bought the phone used with a cracked screen. I checked it out and everything seemed fine. I didn't use the phone, just set it aside til replacement screen came. I should have used the phone to thoroughly check it out but didn't want to go through the set up process as I was thinking of B/L unlock and root. New screen came, put it on and seemed to be working fine then screen would be unresponsive. I did factory reset, software update, software repair, went into settings and made sure sure everything was good there, nothing helped. The center of the screen (it's low and a bit off center) is pretty much dead. To open launcher I have to touch and hold near the top of the display. Touch and hold apps is tricky. Usually the app just opens. When I do get it to hold, I can't drag it anywhere. Also, icons in the drop down menu cannot be rearranged or edited. I can swipe up/down, side to no problem. Whenever touch goes dead completely, the home, back and minimize buttons go grey. Tapping the power button gets them back functioning again. . Function test fail. Free draw lets me make a few seconds of scribbles then freezes. The x and rectangle block draw does the same. Tapping power button does nothing to unfreeze either. The color test pass even the block one where you toggle on/off sections of the screen in blocks. It's really weird. First impression would lead me to the screen but it really acts like a software issue. From what I've read so far this phone uses two different display drivers. I not seen anything on how to change that and it would more than likely mean B/L unlock and root, which I'm not against doing. I would just like to know definitively if it's hardware or software. Any input would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Maybe the Screen Connector wasn't 100% clean.
Or not only the screen is damaged.
I heard that the touch problems are mostly fixed with PIE. The closed source clearpad touch driver is..... Hoping Q gives us an further updated driver.
You still get sometimes ghost touches on higher workload or if the keyboard app is slow, but if you have dead spots the hardware sounds damaged.