Hey guys I have the Optimus G E971 Rogers. I've been using it for a couple days but suddenly today I would have times where it wouldn't recognize my touch randomly. I am unrooted and on the latest OTA from Rogers. Think this is an actual screen issue or software bug? Usually if I turn off and on the screen the touch comes back. I have also tried restarting but it seems it is still there at times. Any tips?
UPDATE: After doing a factory reset it seems to have stopped. I didn't install many apps but the last setting I changed was to set Wifi to sleep when screen off instead of always on but I can't imagine that would cause that problem. I'll let you guys know if it acts up again.
-I have a weird inkling it might be the Google Currents app. As I said we'll see with me using this for a week without Google Currents.
UPDATE 2: Still happened after a factory reset. I used KDZ method to put back to stock before the OTA update. I'm going to be running this to see if it happens again. So far so good.
Some people says they got touch problems when the phone charger plugged in.
This happened both when plugged in via usb and not plugges in. Either way going back to stock seems to have fixed it. Something is funky with the new OTA. It loses sensitivity and then eventually loses all touchscreen responsiveness. Weird stuff.
I think you should swap/exchange your unit, its definitely has touch defect, cause my one works fine.
Btw is it only the touch stops working? Cause high cpu load can cause it as well.
Tim4 said:
I think you should swap/exchange your unit, its definitely has touch defect, cause my one works fine.
Btw is it only the touch stops working? Cause high cpu load can cause it as well.
Click to expand...
Click to collapse
Yes only the touch stops working the capacitive buttons are still working and stuff. Yeah it seemed like when I was using it at high CPU load it caused it, when I was on the new OTA it happened when I played a game and when I was browsing the web with Java. The phone seems to be fine right now without the OTA. Is there a fixed for the high cpu problem or should I still get it exchanged?
If the rest things working its not high cpu load, so i think you should exchange it.
Tim4 said:
If the rest things working its not high cpu load, so i think you should exchange it.
Click to expand...
Click to collapse
I just updated again to the latest OTA to see if it would happen again. It stopped happening. I don't know what would have caused it last night.
In conclusion, had the phone for 3 days. Touch screen issues appeared last night.
LAST NIGHT:
Latest OTA (E97110E) - Non-responsive touch screen at random times
Latest OTA AFTER Factory reset (E97110E) - Still non-responsive at random times (usually high load like playing a game or using youtube)
Flashed Stock KDZ (E97110D) - No touchscreen issues
TODAY:
Used Stock KDZ for full day (E97110D) - No touch screen issues, was playing many games as well + youtube
Updated to latest OTA (E97110E) - No touch screen issues to speak of yet
Anybody think it might be just static charge? I still have the phone in the plastic film all over it with an SGP screen protector.
Related
Hey all, today I just started having a problem with my touch input. Sometimes, it won't register my touches at all, including the hardware capacitive buttons at the bottom. Sometimes, turning the screen off and on will fix it, sometimes it won't.
Other times, I'll get what people call "ghost touches"; the screen is reacting as if I was touching it in certain spots when I'm not. Honestly, I can sit back and watch as my phone uses itself (it's really creepy actually).
The weird thing is that this just happened out of the blue. This morning my phone worked perfectly fine; I had never seen this issue before. Then all of a sudden this started happening. I am using CM6 nightlies and I have tried everything. I wiped everything, flashed the new nightly, flashed a stock 2.2 ROM (with Sense), changed the NovaFreq values, tried a kernel without the FPS unlock, and the problem persists.
Does anyone know how to fix this issue? If it has been over 30 days since I bought the phone, will Sprint still replace it?
Hi folks,
since monday I have got my HTC Desire Z and it's my favourite phone of all time until now.
But there is a small problem with the touchscreen.
I get SMS messages and read them.
After that I want to answer the messages and begin to write with the HW-Keyboard.
Then the party begins. The Screen which shows my answer while I'm writing begins to jump up and down. If I try to stop it with my finger, like hunting a small bug or something , it shows me the little zoom windows for marking,copying and cutting text.
I've factory resetted the phone, but the problem is still there.
It has got the Stock ROM and 2.6.32.21-gd2764ed Kernel.
(I overclocked the phone yesterday, bu the problem appears since the first day, not since the OC)
Thanks guys,
sergioka
There's a known issue described at http://forum.xda-developers.com/showthread.php?t=829535
But on my phone at least, it just "jumps" once, it doesn't go up and down if that's what you're seeing (unless you specifically go and start swiping it etc).
Hi, I made two videos.
This time such a thing didn't happen in the Messaging Mode, but in the homescreen.
Should I send this phone back?
Thanks in advance
Sorry for the bad quality, had to record and recode it as fast as possible.
Edit:
second video had problems
sergioka said:
Hi, I made two videos.
This time such a thing didn't happen in the Messaging Mode, but in the homescreen.
Click to expand...
Click to collapse
I've had some weird things happening with my touchscreen in the last few days. But I'm pretty sure this is connected with a new screen protector that I put on, because the problems happened around the same time. If I lift the screen protector and touch the screen when it's gone non-responsive, it works.
Have you got a screen protector ?
Hi, I have a screen protector,
but the problem happened the same before.
....
....
Now, I have lifted my protector to test the device again without it.
The Screen responses in the same way without the protector and in cyanogenmod
It's like having a high end gaming pc which has sometimes problems with fifa soccer 2000
Did you do full wipes when flashing your rom? It looks to me like it's the rom glitching as it gets stuck between screens, then like a millisecond freeze up before it catches up again?
Does it happen all the time? Is it ever OK after a reboot? Do you have setcpu installed?... settings please. Any setcpu profiles?..if so, are the frequencies being set correctly at wake up?
Download your rom again, check the md5 checksum. Full wipes.
Sent from my HTC Vision using XDA App
Tried all the things you've described. At first I thought that it's ok, but after a while in some situations the saga continued
I'll send it back to get a new one
Your problem looks exactly like mine, except that mine seems to have been the particular screen protector. Given that's not the case for you, I can only think that your touch screen is faulty.
Send it back.
It's on its way to the grave now I think
Now, after I've sold my Nokia N900 and lent my homeboy my HTC Kaiser,
I don't have a phone with me.
Time for morsing my messages!
i agree. send it back. i just tried it with mine and it was fine no matter how i held it. This is supposed to be a high end phone that isnt very cheap...
you need to get your money's worth.
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Do you have setCPU ?
i know sometimes when people set screen off properties to low it freezes and needs a batt pull
Funny enough, I guess the problem started after I installed that. I cleared its settings and cache and uninstalled the program hoping it would fix it, but no dice. I figured that would fix the issue if it was related
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
I tried that once, didn't seem to help but I will give it another shot.
I am running stock DK28 ROM, maybe a fresh install will help?
o and you wouldn't happen to be on viper rom would you ?
iSaint said:
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
Click to expand...
Click to collapse
Set it at 200 min.
not running viper ROM. I am running stock froyo with root access.
DiGi: Is that what you have it set on? I thought I read somewhere not to set it that low.
I was running on 200 min just fine. I haven't had setcpu on my phone for a little while though. I think 100 is too low and causing the problem. 200 didn't cause crashes for me.
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
djbacon06 said:
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
Click to expand...
Click to collapse
Odin
reflash your rom
probably something went wrong when flashing
this happens to me when my battery is low (stock dk28)
it's working for me
djbacon06 said:
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Click to expand...
Click to collapse
Recently changed my phone to android and my phone wouldn't wake up every time it goes to sleep more. (Radio 2.10.50.2)
looked and tried a lot of suggestions (format SD, flash ROM, update setup.txt file and etc) but nothing worked until I flashed the new radio 2.14.50.
And it's been working fine for a day now (finger crossed).
Do you have adjbrightness? Theres a problem with it on galaxy s phone where it won't wake up that they haven't been able to fix and that may be your problem.
Did you ever figure out how to fix this "no wake up" issue? I had this problem out of the box with my mini. So does my friend.
I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.
Ok, so like the title says, every 3-4 days I must reboot my phone.
When I play games, the game icon will show up in the lower right corner, I have everything for the game stuff turned off. I can click on the icon and it will ask me to turn on. I back out and it's gone for a few minutes. Mostly until I swipe back, then it will reappear. I can reboot the phone and it will work fine again for a another 3-4 days.
There are other instances that force me to reboot as well, one happened last night. I was scrolling through a local news app and the touch stopped working. I could not scroll up or down, and swiping back did not work. I had to lock the phone and just as the screen went dark, the phone scrolled in the directions I did and it backed out. This only happened when I hit the lock screen.
Is there a fix for this? Has anyone else experienced this?
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Mine does not reboot or shutdown on it own, not once... I have to reboot every so often to keep it functional.
@thepersona My phone doesn't auto reboot either. I'd say do a backup and run https://flash.android.com/welcome to fully Factory Reset the phone and see if that helps (Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Like the OP I do have to reboot my phone about every 3-4 days, but I don't attribute that just to Google Android, coders have become lax on how tight they keep their code, and I say that because in Windows 10 and Windows 11 you have to reboot every few days as well or see an increase in weird issues.
card13 said:
@thepersona Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Click to expand...
Click to collapse
Just to clarify this, most carriers prevented the December update from releasing as Google has asked them to prevent it from going through, primarily due to an issue with calls dropping.
I always manually update my phone, however, I noticed the call dropping bug one day for about an hour straight.
But aside from this meaningless info, I agree with what you said: Attempt a factory reset and see what happens. I turn my phone off every night and charge it, so I don't notice any issues similar to what OP has mentioned.
thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
wilpang said:
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
Click to expand...
Click to collapse
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
thepersona said:
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
Click to expand...
Click to collapse
Yeah I was lucky and it was only once a week which was tolerable!
Something is definitely not right, hopefully is not a dodgy app but that would be preferable than something unfixable.
Ok guys you are missing my point and question. I DO NOT have the random reboots most have, but I have other issues that no one seem to have. Example, I listen to Spotify over night, I fall asleep to music, but 2 days ago it would randomly pause. At first I thought it was do not disturb that I just turned on, on my watch. It was not. Then I thought I may have been hitting my watch, I took it off and it still paused. I rebooted my phone and it's been fine since, no random pauses. Another example is, I play a game but I have the game dashboard turned off, but there times where the icon will pop up in the lower right. When I go into the settings for it, it shows it's off. When I go back to the game the icon is gone for a few minutes then it reappears. The only way for me to get it to stop showing for a few days is to reboot my phone.
I know you shouldn't have to reboot your phone every few days, and by few I mean sometimes it's 3-4 times a week. That tells me something is wrong.
Are you on the November or December update?
If November, I would try the December one.
Rooted or not rooted?
Either way, I would try a factory refresh and don't restore your apps from backup. Manually install only your most critical apps and see if you have the problem. Even better would be not install any additional apps at all and see if the problem happens. If it doesn't happen, install another small group of your most important apps and test again for long enough. Etc.
If you try thre update and/or factory reset, you could try restoring your cloud backup as normal and see if you have any problems still, but if you do, be prepared to factory reset and try like I mentioned in the above paragraph.
Until you can narrow down if the phone has this problem on the December update before you even change settings and add your favorite apps, then you won't know if it's the phone itself (possibly hardware problem), an app you have installed, a problem particular to a combination of factors including if you're on the November update, or what.
Good luck! Please let us know what happens.
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
darbylonia said:
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
Click to expand...
Click to collapse
Awesome!!! This is the kind of news I like to hear..... Just waiting for att to send it through. I checked this morning as my work Verizon Samsung phone got an update.