Is this driving anyone else bonkers, or just me ??
Sometimes, it will just say "nope not gonna listen" then 5 minutes later it works just fine. I've noticed sometimes when it doesn't respond, if i turn it portrait it works fine. Sometimes the screen works but the soft keys dont, sometimes none of it works.. I've even been in recovery to backup a rom and the home and back keys didn't work..
I'm running the latest vegan, and the "calibration" fix has been made..
It's driving my wife crazy, and in turn me ..
aaron19953:
I don't know how much you have added to your tablet -- but if it were me I would flash back to 3452 or one of the other recent stock versions. Get everything working and see if your hardware is good.
If you continue to have problems with a plain, stock version then warranty or return actions are in order.
If the stock works without complaint, then you can start your mod quest again!!!
When I have trouble, I always try to work my way out with a known good.
Rev
aaron19953 said:
Is this driving anyone else bonkers, or just me ??
Sometimes, it will just say "nope not gonna listen" then 5 minutes later it works just fine. I've noticed sometimes when it doesn't respond, if i turn it portrait it works fine. Sometimes the screen works but the soft keys dont, sometimes none of it works.. I've even been in recovery to backup a rom and the home and back keys didn't work..
I'm running the latest vegan, and the "calibration" fix has been made..
It's driving my wife crazy, and in turn me ..
Click to expand...
Click to collapse
My guess is this - you left the calibration.ini file in place on your internal SD card and the screen is getting recalibrated on every boot. Sometimes you are booting up while touching the screen, which completely screws up the calibration.
You should only reboot the tablet once with calibration.ini in place, without touching the tablet during the bootup process.
Then remove calibration.ini so it doesn't calibrate again on the next reboot.
forgot to mention.. occasionally i'd walk outside in the cold with the tablet and noticed it didn't respond quite so well.. after putting the tablet in front of a space heater for a few seconds, the touch works fine..
This morning, i noticed the tablet not responding (and i did recalibrate and rename the file last night) I put the tablet in front of a hair dryer for a few seconds and it works fine .. Don't tell me i have to keep a hair dryer with me now ! haha
No, you just have to give it a hug Aaron
lifeisfun said:
No, you just have to give it a hug Aaron
Click to expand...
Click to collapse
oh ok, and here all this time i've been spanking it in anger ... haha
hehe, get a dog instead
This is sounding more and more like your Gtab has some kind of hardware problem.
Jim
Try a soft reset. You'll have to open the tablet up to get to the button. I had to do this when my screen would not respond.
Related
i purchased g1 from ebay, right from day1 the screen does not respond properly in fact most of the times. i need to reset soft one to at least g1 working. i upgraded to jesusfrake adp1.1 but issue is same. looks like a s/w bug or problem as if it were a h/w problem it would not have worked at all. if iam lucky it works like a charm but stops responding once i get some sms/email alert or install any app from market. can someone help here!!
Have you already tried reflashing the firmware? If not, do that. Otherwise, why don't you contact the person you bought the phone from. It sounds like it may be a hardware problem which might be why that person was selling it.
i did flash everything from bootloader to firmware to rooting. but problem remains same...it works for 5 minutes and again screen stops responding but trackball is active....right now iam on latest JF formware..
is anyone facing a simillar problem??? any work arounds....
Sometimes my home screen goes completely blank on me and seems nonresponsive for about 30 seconds. Can be pretty annoying. It seems to happen when I'm switching from an app to the home screen.
Contact HTC directly and ask for an exchange or something. All G1's have been out for less than a year and so they should be covered by warranty.
I put a new screen protector on my G1. I noticed that it had a bad reaction with the touch and I took it off. After I took it off, my touch screen got much worse. It was very jumpy and unuseable. There was a practically invisible film on the screen (couldn't even really feel it. I took a little bit of soap on a lint free cloth and wiped the screen down and let it sit for just a minute (to soak any residue) and wiped away. My screen worked perfect after that.
I was ready to call in for a replacement.
could it be a bug as if it were a hardware problem it would prevent touch screen responding at all!!!
i downgraded to rc 30 and rooted the phone, now its working like a charm!! strange though.......
sometimes when im typing away in a message on my phone, some parts of the phone turn into resistant areas making me press hard on my phone for a touch response to occur...so the phone turns from a capacitive touch screen, to a resistant one that requires a considerable amount of pressure from my fingers. Why!!! is this because of a rom im using? when i click the sleep button on and off the screen returns to normal, but this is so frustrating when im attempting to type long messages. any answers? thanks!!!
I had that issue once.. I tried calibrating the screen but it didnt help so I did a battery pull and it went back to normal.. Havent had the problem since then but im scared itll show its face again..
hah yeaa aafter posting this i havent had the problem, lol lets hope it doesnt come back!
OP are you using a gingerbread rom? it's a VERY VERY common/known issue in all gingerbread roms from gingerbeast to ARHD. I don't know if there's a fix in the works or if anyone cares to make one but i think everyone just flashes teh screen on/off to get around it.
I'm not sure if it's lag or what, but my phone screen won't come on. I think it's a ribbon that was disconnected or something though. For about a few hours if I were to press power to see the lock screen, all I saw where a bunch of rainbow static. Then I powered my phone on and off because nothing would work and now it's jut black! Does anyone know what's wrong? I can't boot into clockwork so I don't think it's a rom problem. Does anyone know the problem or have any idea to fix? Anyone I should ask specifically?
maybe water? even having my phone in the bathroom while i take a shower cause me that
It's not water, I never bring my phone close to place with water :/
can you boot into the screen where there are 3 droids with the skateboards? (i not sure whats the name)
I think I can boot and my phone still works, because it still rings when someone calls and it still vibrates when someone text it, but I just can't pick up or reply (because the screen won't come on). I should be able to boot into that thing, but I can't anything :/
well bro sorry i cant help you :/ maybe it could be the screen,the ribons or somethings loose. did it fell?
aznangel1408 said:
I think I can boot and my phone still works, because it still rings when someone calls and it still vibrates when someone text it, but I just can't pick up or reply (because the screen won't come on). I should be able to boot into that thing, but I can't anything :/
Click to expand...
Click to collapse
Seems like either broken ribbon that connects the screen to the "motherboard', or dead screen itself. That's exactly how 1 of my phones died (it was too complicated to disassemble and fix it myself)
But once I had similar problem with my TP2, the screen first become unresponsive to any touch, and then it went just black after restart (and every next restart). However all keys did work.
Hard reset somewhat helped, the screen actually came back, but it was still stuck on setting up Windows Mobile (if you know WinMo: the part where you calibrate touchscreen), apparently "touch" part of the screen didn't work.
I thought it is ribbon or screen assembly, but since all the keys worked I flashed another ROM and what do you know: all problems went away. It worked fine for as long as I had it. I never figured out what caused it/was the problem.
koete said:
well bro sorry i cant help you :/ maybe it could be the screen,the ribons or somethings loose. did it fell?
Click to expand...
Click to collapse
MT4GS said:
Seems like either broken ribbon that connects the screen to the "motherboard', or dead screen itself. That's exactly how 1 of my phones died (it was too complicated to disassemble and fix it myself)
Click to expand...
Click to collapse
Yea I think that's the problem here. I think I'm just going to borrow a friends mt4gs to use and navigate recovery and do a back up and just buy a new one and restore. Thanks for all the help guys
Some weeks before my sg3 got drenched a bit(I went to a beach & sg3 was in my pocket). Now its touchscreen is acting weird. Sometimes it works just fine, sometimes not.
Anyways all hard buttons are working. I tested soft keys in CWM recovery. They failed to work on recovery sometimes, so that means it is not a ROM problem. I reflashed CM7 twice. Problem remained.
I noticed, in moisted weather, it becomes unresponsive.
Any suggestion or trick/tweak or fix?
i_rnb said:
Some weeks before my sg3 got drenched a bit(I went to a beach & sg3 was in my pocket). Now its touchscreen is acting weird. Sometimes it works just fine, sometimes not.
Anyways all hard buttons are working. I tested soft keys in CWM recovery. They failed to work on recovery sometimes, so that means it is not a ROM problem. I reflashed CM7 twice. Problem remained.
I noticed, in moisted weather, it becomes unresponsive.
Any suggestion or trick/tweak or fix?
Click to expand...
Click to collapse
The connection between the input circuitry and the board must hav got shortcrcuited as sea water contains salt;;thus giving rise to unresponsive soft keys n touch screen..
Even i had dropped ma G3 into a bucket of water...The same thing happend....
I dint go to the service centre rathr i googled it..
Landed on a reliable solution...
Just chck it out..
Steps to take if u drop ur fone into water
The rice trick worked for me !
Let me know if it works 4 u as well...
i_rnb said:
Some weeks before my sg3 got drenched a bit(I went to a beach & sg3 was in my pocket). Now its touchscreen is acting weird. Sometimes it works just fine, sometimes not.
Anyways all hard buttons are working. I tested soft keys in CWM recovery. They failed to work on recovery sometimes, so that means it is not a ROM problem. I reflashed CM7 twice. Problem remained.
I noticed, in moisted weather, it becomes unresponsive.
Any suggestion or trick/tweak or fix?
Click to expand...
Click to collapse
^AFAIK, there isn't any other option but to replace your touch panel. And trust me, I'm telling this from my experience. I faced the exact same problem a little over a year back. The touchscreen as well as the soft keys would occasionally behave weirdly. I even tried a few fixes that I found on the internet (like putting it in a bowl of uncooked rice for a few hours, etc..), but to no avail.
So finally I gave up and went to Samsung Care. Although my phone was still under warranty back then, water damage wasn't covered under it. The guy initially demanded 1.5k to replace the touch panel, but after a l'il pleading, he agreed to do it for free.
Anyways, so I'd suggest you to simply walk into the nearest Samsung service center or your local mobile repair wala and get it replaced. Initially they might demand ~2k, but try bringing them down to around 1.5k!
Hope that helps.
When my sg3 fell into the water i quickly put it in a jar full of rice and it sucked out all the moisture from the phone...
Sent from my GT-I5800 using xda app-developers app
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
thelestat said:
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
Click to expand...
Click to collapse
It's weird...I flip back between AK and the stock CM kernel, and the touchscreen works for maybe an hour, then it goes completely dead again (including when in recovery). And the touchscreen is dead no matter which recovery I use, whether it be TWRP or CWM.
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
demkantor said:
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
Click to expand...
Click to collapse
I've got it back to working by messing with the kernel a little bit. How's the progress with the LOGO partition going? I saw that in the other thread, you almost bricked your OPO
Yeah it was an unfortunate mistake on my behalf while digging into it deeper, luckily all worked out in the end
Haven't had the chance to make more progress, the wife and I had our first child on Friday and I still have one more week of finals left (until I'm done with college for good!)
I hope to have some more time this next week to figure the rest out, I'm sure its doable but I don't want to risk anything before I know more!
Touch screen unresponsive
Any solution to this problem? Running 11.0-XNPH30O
Android 4.4.4 that was updated two days ago.
The touchscreen becomes unresponsive every hour or two and need to force turn off the phone by holding down the power and restarting.
Have had the phone for a little over a week and annoyed by little issues here and there. The orientation change (when turning phone for auto rotate) on a picture takes too long. Speaker phone was a problem initially, fixed with an update and now this touch screen unresponsiveness.
Doesn't matter if it's Synaptics or not. cyanogenmod and one plus need to figure out a solution and not sell a buggy phone on the most important features of a touch screen phone. ITS TOUCH SCREEN.
If I don't see a fix in 48 hours, I'll be returning the phone or selling it on eBay.
treChoy said:
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
Click to expand...
Click to collapse
treChoy said:
I've got it back to working by messing with the kernel a little bit.
Click to expand...
Click to collapse
I've got a touchscreen dead zone at the bottom, just all the navbar area. I wonder if it could be possible to get it back to working by messing with the kernel as you did. Which kernel and tweaks.
Thanks.
Edit: now the dead zone has extended to the hardware buttons. I have to rotate the screen 180° in order to be able to use the navbar.
Thanks