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?
Related
I first started using CM at 6.1.2. I'm now on CM7 RC2 and the same problem still occurs. I have no idea why this happens but I'll provide as much info as possible in the hope that someone will be able to figure it out.
My phone will work completely normally for several days after I initially flash CM6.1.2 or CM7. After a few days, a crash will occur where the screen stays on but the phone is completely unresponsive to all input -- touch, softkeys, or hardware keys. The power button stops functioning. After a while, the screen dims and the phone reboots. After the reboot the phone chugs along for a few hours and then the same thing happens. This crash almost always occurs in the Browser, in the middle of loading a page. I don't think it's a memory issue because I consistently have ~100MB free for RAM.
Also, I don't know if this is at all related, but I often notice just before the crash, the haptic feedback from the phone for keyboard presses and the softkeys becomes very erratic and inconsistent.
I can never get a logcat because the phone restarts after the crash. Has anyone else seen this or know what might be the problem? Again, this has been happening all the way since CM6.1.2 (and possibly earlier, I haven't tried anything earlier than 6.1.2 though). This is driving me pretty crazy, and I really love CM and would like to continue using it, but this is kind of a dealbreaker.
Did you wipe between flashing CM6 and CM7?
Yes, I always wipe data/cache/dalvik between flashing.
hi, had my desire z about a year now, since ive had it, quite rarely ive had a problem of it seeming to have a mind of its own, for example, icons may be selected, or the home screen will slide accross by itself etc. ive always put this down to a trackpad problem.
the other day (after having a miui rom installed for about 2-3 weeks, which was fine untill now), it started acting up strangely, the above problem started happening, but more severe, also the touch screen and softkey buttons would stop working for periods of time (or stop completely untill reset), but screen rotation etc would still be working, which shows that the O/S has not frose and is still working behind the scenes (making me think its a hardware problem).
now, i think ive worked out that this seems to be triggered (mostly) when i open the keyboard. (as also, when the touchscreen stops working etc, sometimes, sliding the keyboard open and close several times, will sometimes seem to unfreeze the touchscreen etc, and will be back to normal, for a while). ive tried doing full wipe and reflashing etc, but i still have the same problems mainly when using the slide out keyboard, which again, makes me think its hardware (possibly keyboard ribbon cable?)
i really dont want to send it off as that means getting it all back to stock etc, and last time i needed the screen replaced, took 6 weeks to get it back!
if anyone could pinpoint the likely source of the problem, id rather replace the part myself..
would anyone have any ideas, as they would be very much appriciated... Thanks...
anyone at all?
I got 2 Zs meanwhile but dont have any problem with the keyboard.
But sometimes when its charging i got the same issues like you - no touch is working and the screens are sliding nearly automatically.
I think this has nothing to do with the keyboard...
Hope this had helped you a bit
Sent from my HTC Vision using XDA Premium App
thanks for the reply, unfortunately im still no closer to finding source of the problem, its intermittant, happened lots yesterday, not so much today, maybe the digitiser? its like there is another invisible finger touching the screen..
This would happen when i was on stock froyo, like it would cause the home screen to hang, but if i was ion an app it worked fine. I would use it to refresh of sorts when my phone was hung up or i need to reload my apps from sd lol. Sounds weird I know, but even with stock froyo i had problems with my keyboard but with the prerooted GB its as smooth as butter...
still going on, and getting more frequent, i dont think it is to do with the keyboard anymore. im now guessing it is the digitizer, its like someone is pressing an invisible finger on the screen, roughly in the center. it comes and goes, it happens for about 3 days, then goes away for a couple of days etc.
also there is very little info anywhere on the net that can help, including replaceing the digitizer itself
anyone ever replaced one on a disire z/g2?
I recently (yesterday) updated my one X to jellybean (official OTA ROM update) and since then it's suffering from phantom touches.
I tried everything I could think off, even a hard reset (btw, that also deletes your storage data, very nice to discover this afterwards) but even that didn't help.
It doesn't happen all the time but when it does it's seriously annoying.. it start apps, calls people, just anything that's on the touched place.
I turned on the development option for visual touch feedback and it actually shows the phantom touches.
I've been googling for similar cases but nothing useful except some broken digitizers.
If it were the digitizer it would have happened before the upgrade too, right? but it didn't, it started right after I upgraded.
It's not an app, I booted my phone in safe mode and it happened, it even happened during the first boot setup.
Any suggestions? Is there anything else to clear that's not cleared after a hard reset?
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.
So.. i have had a weird problem for quite awhile now but have been putting up with it..
When on a voice call when the screen goes off it will mute the mic, leaving the other person asking if i am there.. i have to shake the phone or hit the power button a bunch. It also doesn't wake up instantly when that happens, almost like its in a deep sleep. I don't have any battery saver apps or anything installed....
I am using CM11 right now with FL24 modem, i have tried other modems.. same issue.. This issue also happened on other roms incluing vanir and others...
I did a search and found one other person with the same exact issue.. but no fix posted, was hoping someone might have an idea on how to figure this out.. thanks..
Experiencing Similar Problem
I've been experiencing a similar issue for a bit over a month, too. I'm not quite sure if it was when the screen went off, but certainly within 15 seconds of making or receiving a call my mic cuts off. It sometimes comes back after -- I don't know if that's because I shake the phone around or otherwise get the screen to come on, although the mic turning back on and the screen turning back on do not happen at the same time.
I'm also on CM11 with FL24 modem on a Samsung Epic 4G Touch, which makes me suspect it's the same problem. Do you have a link to the other forum post?
I suspect it's a relatively recent regression with CM, because I installed CM11 on the phone at the end of October and everything was fine. I first started experiencing the issue a few weeks thereafter. I can't recall if it happened after upgrading CM, or if It was after I installed Google Voice (since removed,) or if there was no particular prompt.