Related
So I've had my Nexus One since release at the beginning of 2010, and I'm finally coming out to ask: does anyone else have occasional trouble with their touchscreen detecting touches at completely the wrong places? At random points while using the Browser (maybe once or twice a week) I'll be trying to scroll and I'll get a quick zoom instead. Also, if I touch about 1 inch above the Back/Menu/Home/Search keys, they will be recognized as those keys instead of touching the screen! This bug happens outside of Browser too (though it always seems to start there) and has been consistent across CM6, MM's Gingerbread Builds, and several other ROMs. It always goes away with a reboot, but I just wanted to see if anyone else has had similar problems
I'd bet 99% of Nexus owners have this problem. You don't have to reboot, just turn your screen off and on again to reset it.
It's a hardware problem, the touchscreen panel isn't very good in the Nexus One..
But, It's fine in the newer phones like G2 and Nexus S
yup I have the same issue not a major issue I think battery draining & memory has been my main issue at the moment.
http://forum.xda-developers.com/showthread.php?t=878477
Since getting mine back from repair the problem occurs less often but is still there.
QuacoreZX said:
So I've had my Nexus One since release at the beginning of 2010, and I'm finally coming out to ask: does anyone else have occasional trouble with their touchscreen detecting touches at completely the wrong places? At random points while using the Browser (maybe once or twice a week) I'll be trying to scroll and I'll get a quick zoom instead. Also, if I touch about 1 inch above the Back/Menu/Home/Search keys, they will be recognized as those keys instead of touching the screen! This bug happens outside of Browser too (though it always seems to start there) and has been consistent across CM6, MM's Gingerbread Builds, and several other ROMs. It always goes away with a reboot, but I just wanted to see if anyone else has had similar problems
Click to expand...
Click to collapse
Same to you, I have this problem either.
I have swapped my n1 3 times and finally got one without this problem. I mean completely gone, not occur even once. So I suggest you swap it.
Same here. Yesterday, the half upper screen doesn't recoginze any input
helloworld1 said:
I have swapped my n1 3 times and finally got one without this problem. I mean completely gone, not occur even once. So I suggest you swap it.
Click to expand...
Click to collapse
Same here. My first one had the issue a couple times a day, the next phone was particularly bad with my screen screwing up every few minutes. This current phone hasn't had the issue in the month I've owned it.
Part numbers and the touchscreen panel part numbers are the exact same in the last two.phones.
This bug is a year old.
Amazingly I've never had that issue so I don't think its universal though my screen sometimes fails to respond at all but that'll go away after a minute or so.
RogerPodacter said:
This bug is a year old.
Click to expand...
Click to collapse
It's not a bug, it's a hardware defect. There is no way to prevent this in the software.
I only seem to get it when on charge, and there is a thread about the same thing in the NS forum, so it's not just us.
GldRush98 said:
It's not a bug, it's a hardware defect. There is no way to prevent this in the software.
Click to expand...
Click to collapse
Granted. However I can envisage a piece of software that cycles the screen off/on momentarily every few minutes that may in practical terms fix it.
My first N1 was only slightly effected by the screen fault, even after going back to HTC for a new power button. When the power button failed a second time I elected to go for a refurb on the second warranty return. Unfortunately the refurb is quite badly effected by the screen alignment fault.
Most annoying thing is when the alignment goes out, I have no choice but to use the power button to cycle it off. I am trying at all cost to avoid using the power button on my N1 to defer its inevitable next failure.
There's a fix for it
I can confirm that replacing Radio to "Korean Radio" solves this problem!
Verified in 4-5 different devices.
You can find the radio here:
http://forum.xda-developers.com/showthread.php?t=816917
Tomer
tomerbn said:
I can confirm that replacing Radio to "Korean Radio" solves this problem!
Verified in 4-5 different devices.
You can find the radio here:
http://forum.xda-developers.com/showthread.php?t=816917
Tomer
Click to expand...
Click to collapse
That's not entirely true... I'm on that radio and I have this issue from time to time.
As above, radio isn't a fix, can't think why it would be.
logger said:
Granted. However I can envisage a piece of software that cycles the screen off/on momentarily every few minutes that may in practical terms fix it.
My first N1 was only slightly effected by the screen fault, even after going back to HTC for a new power button. When the power button failed a second time I elected to go for a refurb on the second warranty return. Unfortunately the refurb is quite badly effected by the screen alignment fault.
Most annoying thing is when the alignment goes out, I have no choice but to use the power button to cycle it off. I am trying at all cost to avoid using the power button on my N1 to defer its inevitable next failure.
Click to expand...
Click to collapse
i avoid the power button too when i need to cycle the screen. i use cyanogen ROM which has the Zzz button in the drop down shade, which blacks out the screen. then just hit trackball to wake it back up. power button avoided!
RogerPodacter said:
i avoid the power button too when i need to cycle the screen. i use cyanogen ROM which has the Zzz button in the drop down shade, which blacks out the screen. then just hit trackball to wake it back up. power button avoided!
Click to expand...
Click to collapse
There is an app in the market for a buck, it's called screen off. It comes with a widget or app and one of the choices is an invisible widget so if you don't want to see it you don't, (just remember where you put it)...........
I use it for shutting my screen down all the time for saving battery life.
vinnyjr said:
There is an app in the market for a buck, it's called screen off. It comes with a widget or app and one of the choices is an invisible widget so if you don't want to see it you don't, (just remember where you put it)...........
I use it for shutting my screen down all the time for saving battery life.
Click to expand...
Click to collapse
I'm using the Lock widget to power down...it's free on the market! There's a transparent version in the Android theme section.
Hi,
I've been intending to post about this ever since I bought my refurbished Nook Color several months ago, and can't put it off any longer. It's driving me crazy.
Does anyone else have problems with responsiveness of the Nook Color to touch? Occasionally, when running in native Nook e-reader mode, I will tap on the screen and nothing happens. Sometimes it takes several taps and rarely, I can get no response no matter how times I tap.
Worse yet, the problem is multiplied in "root" mode. I have installed racks11479's Dualboot Phiremod/Honeydcomb Image (http://forum.xda-developers.com/showthread.php?t=1045018) on my SD card (thanks very, very much, racks!) and usually work in Phiremod Gingerbread (2.3.3) mode. I get extremely frustrated at the number of times I have to give up and back out to try something else because I simply cannot get the screen to respond no matter what I do.
Do I need to replace or repair my device, or is there something I can do about this?
Thanks for you help!
I would say 99% of us do not experience this kind of laggy responsiveness.
in the market there is an app called "nook screen recalibrate" If you haven't already, I would try that.
nook711 said:
in the market there is an app called "nook screen recalibrate" If you haven't already, I would try that.
Click to expand...
Click to collapse
That is what I typically run if my screen ever seems a little strange.
Clean your screen, run nook screen recalibrate and then get a screen protector. Also are you overclocked? If not you will want to.
Sent from space
MagicSpeller, I also have this problem with my (barely month old) refurbished Nook. In addition, tapping the screen often results in the incorrect selection. I don't have this problem with Android phones or the iPad, so I'm pretty sure it's not my finger. Do you have this, too?
I'll try out the recommended nook screen recalibrate app tonight.
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then it goes to a black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. Playing around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried downgrading to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. laying around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried going down to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
Sorry, this post isn't going to help, but I literally laughed out loud when I saw
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Click to expand...
Click to collapse
in the preview of the post. Lol
Maybe I should delete my original Karma-Killing post as a start.
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
a.mcdear said:
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
Click to expand...
Click to collapse
It might not be software but I can see the recovery screen so I have some reasons to believe it could still be software. Unfortunately, if I try to RMA, they're going to say that I voided the warranty....because I probably did by opening the case AND running a cooked ROM. So, they'll fix it but as a service. I'm not sure it would be worth the cost.
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
yanbo2012 said:
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
Click to expand...
Click to collapse
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Skyeclad said:
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Click to expand...
Click to collapse
Yea, you screwed up by opening it. You might as well upgrade if all else fails. I'd hold off on another transformer for as long as I can though if I were you...already hearing about minor defects in tf300s such as light bleeding.
Then there's always the...iPad...but make sure you update if you get one! Jailbreak that MF first and then you'd be good to go. My dad wants me to jailbreak his iPad 2, but it doesn't help that he's "update happy"
Skyeclad said:
I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
farsight73 said:
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
Click to expand...
Click to collapse
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Skyeclad said:
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Click to expand...
Click to collapse
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
1) NVflash works on B60 and below.. check yours
2) Put it in a freezer for a night
3) Dissemble again and see if anything disconnected or loose since the last time you open it.
4) Smell it and see if anything like burn smell around the motherboard(this could be over voltage from a weak components).
.
.
.
.
.
If all above still yielled the same result..
5) Check and see if your TF101 could survive 2 storey height drop..
Good Luck..
farsight73 said:
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
...
2) Put it in a freezer for a night
...
Good Luck..
Click to expand...
Click to collapse
A lot of LCD screens can be damaged by freezing, unless you know that the TF is safe I would not freeze it.
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Skyeclad said:
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Click to expand...
Click to collapse
Lol, didn't you already take it apart before?
I2IEAILiiTY said:
Lol, didn't you already take it apart before?
Click to expand...
Click to collapse
Yes, but at the time I was looking for a cable that I could loosen, now I'm looking for a cable to tighten. Fml, yes it sounds stupid but I'm at the point where I need to decide if a repair or replacement is the next step. I'm not thrilled with anything out there.
Almost exactly the same problem here...
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
I had the same problem of the backlight being on but no video. It worked over the hdmi but that was it. I had to send in my unit via a RMA to get it fixed.
Thankfully it was under warranty so they fixed it. Did you drop your unit?
MeLikes said:
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
Click to expand...
Click to collapse
Just out of curiosity, why not nvflash your way back to stock? I did because I couldn't find my HDMI mini cable. I haven't opened my tablet again. I'm going to try to RMA it.
try to nvflash stock rom and start over? that would your best chance....
Sent from my Transformer TF101 using xda premium
Well first of all i don't know how to use NVflash, and secondly i have a B70 transformer so i don't know if it will work. Also i need to flash the stock Taiwan firmware because that's the original firmware that came with it and i can't find instructions for that. Just wondering though does flashing the stock rom using NVflash also install the stock recovery?
Hello,
I have a Nook Color 8gb first gen that I have put CM 10 (10-20130414-nightly-encore) on. My problem is that sometimes the tablet seems to take on a life of its own and what it seems to be doing is to be persisting screen taps. So for example you will be typing with the on screen keyboard and all of a sudden it will keep hitting a key even while your not still touching the screen. This also occurs while playing games the game will keep on playing even while your not tapping the screen again I think it is persisting previous taps.
I have tried two CM 10 builds with no luck. I have cleaned the screen - no luck. I have rebuilt the tablet - no luck.
I was wondering if anyone else had the same issue and how they resolved it if at all?
Thanks
Check out Nook Screen Recalibrate from the market and make sure the screen is very clean. I know you said you cleaned it but they can be really picky.
Sent from my HTC Fireball
wmuflyer said:
Check out Nook Screen Recalibrate from the market and make sure the screen is very clean. I know you said you cleaned it but they can be really picky.
Sent from my HTC Fireball
Click to expand...
Click to collapse
Thanks I recalibrated the screen and tried it for a few weeks. Strange thing is that for a little while the frequency of the stuck key problem went down but it still happens. Not sure if there is anything else I can do might try a new Cyanogenmod build but I don't think that is the problem I have a kindle fire that has Cyanogenmod on it with no problems so maybe just the device.
Thanks
Hi guys
I have moved from iPhone to a note 4 and loving it!
I was just wondering if anyone has found the touch screen occasionally doesn't respond to their touch and you have to touch it again. On the iPhone it only ever missed a touch if my finger was in the wrong place, but it never happened on the keyboard. Every so often maybe 5/6 times a day I touch a key on the keyboard and nothing happens, when I try again it's fine. I can't reproduce it, because when I tap anywhere on the keyboard something gets pressed. I was just wondering if this was normal?
Hope you are enjoying your phones!!
Anyone?
It's most likely cause your palm is on the phone. One of the downsides of a slim bezel on a big phone. Also keep in mind if your spen is on the screen, your fingers won't work. A case might help.
I thought about another part of my hand touching the screen, however with half my hand layed across my keyboard I can still type with the other hand. Thanks for the response
I Pele tried factory resetting today and not installed any apps, but it is still happening
I rang Samsung this morning and they advised I return I to the store and get an exchange. Luckily my local store got its first batch of note 4s in this morning and they swapped it out. I restored it all firmware updates put on it and now works fine! The only thing I haven't installed is a Google play system update thing. I was wondering if that was the cause x
Similar issues
I've had similar issues (in fact, that's what brought me here in the first place). Initially, I was able to tap on the screen in the text box and then continue typing (I use Swype). However, now my messaging app (default Messages) just freezes up, forcing me to close the app, clear the memory, and relaunch the app before continuing.
Were you using the default app and/or Swype when you had issues? I'm going to try to factory reset my phone to see if it helps.
It's taken a couple of weeks for this problem to develop, so please keep us posted if this problem arises again on your new phone!
Edit: Also want to point out that when I text, I use one hand to hold the phone and only a finger to swipe my text. As such, only the one finger touches the screen.
unable to use touch screen. only hard key were working >>Note4
Hi everyone,
today i just had the same problem with the touch screen. no response at all .. after i tried and took out the spen .. and surprise it worked with the pen.
tried again with fingers still nothing worked, so i used the pen to reboot the note4.
hope my experience helps.
cheers,
djvaliro said:
Hi everyone,
today i just had the same problem with the touch screen. no response at all .. after i tried and took out the spen .. and surprise it worked with the pen.
tried again with fingers still nothing worked, so i used the pen to reboot the note4.
hope my experience helps.
cheers,
Click to expand...
Click to collapse
Same thing happened to me last night. The touchscreen became unresponsive while using chrome. The phone was a little warm but not bad. I didn't try the pen, sounds like a good idea. I am not certain it was a touch screen issue with mine. Almost more of a processor issue. I got the phone to lock. After pressing the menu or lock button to wake the screen it would take 5-10 seconds to wake. Then I could swipe my unlock pattern. It would not show any lines. I would wait, the screen would turn black after timing out in about 5s. The about 5s after I could hear the speaker make the unlock sound. I ended up doing a battery pull and that fixed the issue. Anyone else have something similar?
Should I try and replace it?
badtoy1986 said:
Same thing happened to me last night. The touchscreen became unresponsive while using chrome. The phone was a little warm but not bad. I didn't try the pen, sounds like a good idea. I am not certain it was a touch screen issue with mine. Almost more of a processor issue. I got the phone to lock. After pressing the menu or lock button to wake the screen it would take 5-10 seconds to wake. Then I could swipe my unlock pattern. It would not show any lines. I would wait, the screen would turn black after timing out in about 5s. The about 5s after I could hear the speaker make the unlock sound. I ended up doing a battery pull and that fixed the issue. Anyone else have something similar?
Should I try and replace it?
Click to expand...
Click to collapse
Observe to see if it happens when you're using other apps too. Chrome has been notorious for causing all sorts of problems, like reboots, freezes, etc on some devices.
Also it may be worth installing Chrome Samsung Support Library.
Sent from my SM-P600 using Tapatalk
iridaki said:
Observe to see if it happens when you're using other apps too. Chrome has been notorious for causing all sorts of problems, like reboots, freezes, etc on some devices.
Also it may be worth installing Chrome Samsung Support Library.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Thank you for the app. I installed it and will keep watching for it again.
swampystorm said:
Hi guys
I have moved from iPhone to a note 4 and loving it!
I was just wondering if anyone has found the touch screen occasionally doesn't respond to their touch and you have to touch it again. On the iPhone it only ever missed a touch if my finger was in the wrong place, but it never happened on the keyboard. Every so often maybe 5/6 times a day I touch a key on the keyboard and nothing happens, when I try again it's fine. I can't reproduce it, because when I tap anywhere on the keyboard something gets pressed. I was just wondering if this was normal?
Hope you are enjoying your phones!!
Click to expand...
Click to collapse
Got the same problem after 2 months of normal usage... I initially though I had installed a third party application which was causing the system freeze but this was not the problem.
- tried factory resetting and not installed any apps, but it is still happening
- When this happens if I take out the spen .... surprise it work. The pen allows me to do anything... But the touch screen does not work with fingers...
- I used the pen to reboot the note4... Still the same problem after reboot... I ended up doing a battery pull and that fixed the issue for.... a couple of minutes... Then the problem came back....
The only solution remaining was to return the phone.... They gave me a Note3 while my Note4 is being repaired...
That's a shame for a product of that price!
:crying:
Same thing is happening with my 2 months old note4 since two weeks ago. An horizontal line 1.5cm in width about 1/3 from the bottom of the screen, became unresponsive. At reboot it works sometimes then it becomes unresponsive again. It looks like in the image I attached, the difference is that the area is horizontal, not vertical. I'm taking my note4 to the store today for warranty, hopefully they will replace it. I haven't abused the device in any way, I have a screen protector since its first day.. I really hope this isn't a serious problem that affects many users.
Just like some of you mentioned above, the pen has no issues on any area of the screen.
Cheers!
amwebexpert said:
Got the same problem after 2 months of normal usage... I initially though I had installed a third party application which was causing the system freeze but this was not the problem.
- tried factory resetting and not installed any apps, but it is still happening
- When this happens if I take out the spen .... surprise it work. The pen allows me to do anything... But the touch screen does not work with fingers...
- I used the pen to reboot the note4... Still the same problem after reboot... I ended up doing a battery pull and that fixed the issue for.... a couple of minutes... Then the problem came back....
The only solution remaining was to return the phone.... They gave me a Note3 while my Note4 is being repaired...
That's a shame for a product of that price!
:crying:
Click to expand...
Click to collapse
same thing happen to my note4 today. the only difference is that yours was fixed for a couple of minutes after removing the battery. my note4 wasn't fixed after that. Only S-pen works, touch screen with fingers wont work. you mentioned you're note4 is getting repaired, did they tell you what may have happened to it so that i'll get an idea of the cause..
You found the appropriate thread, I was just now going to share the link to this thread with you as well as quoting what others experienced,
http://forum.xda-developers.com/showpost.php?p=56313609&postcount=6
http://forum.xda-developers.com/showpost.php?p=56464866&postcount=8
http://forum.xda-developers.com/showpost.php?p=57302776&postcount=9
http://forum.xda-developers.com/showpost.php?p=57304242&postcount=10
http://forum.xda-developers.com/showpost.php?p=58421560&postcount=12
http://forum.xda-developers.com/showpost.php?p=58452707&postcount=13
Never purchase a device without a return / DOA policy. Not worth the hassle. If it hasn't been 30 days, you should call your credit card company or Paypal and place the amount on dispute, wait, you purchased from another market, please tell you didn't pay by cash.
vjevardone said:
same thing happen to my note4 today. the only difference is that yours was fixed for a couple of minutes after removing the battery. my note4 wasn't fixed after that. Only S-pen works, touch screen with fingers wont work. you mentioned you're note4 is getting repaired, did they tell you what may have happened to it so that i'll get an idea of the cause..
Click to expand...
Click to collapse
I have this problem after I flash CWM recovery, before this was flashed with twrp recovery, I reflash stock rom with odin, I flash many times CWM and TWRP and I still have the problem, my warranty it's void now but I think to go at Samsung store to see if they solve my problem. This problem look like a driver for touch corrupted, if somebody find it out how to fix or have any ideea please weritte here, thanks you
I've started to have this problem as well, lower part of the left side of the screen sometimes registers touch instead of scrolling! Very annoying, tried to update recovery, tried tapping screen, doesn't help. The worst thing is I cannot reproduce the issue at will... It seems pretty random.
hi
inter *#2663#
and select fw software.
farnam-ferdosi said:
hi
inter *#2663#
and select fw software.
Click to expand...
Click to collapse
Unfortunately, if the phone is on Verizon, the dialing codes will be disabled.
Potential fix.
Please excuse the necropost But I came here looking for a solution from google and others may too. I found a way to solve this issue/s.
There appear to be two issues affecting this.
1. Overloading the processor.
2. Static.
If your touch input is lagging or doesn't register at all but then suddenly does a few moments later, its likely a type 1. problem. I fixed this by disabling resource intensive features such as s voice. This also improved battery life and overall performance considerably.
If touch simply doesn't work at all, but s pen works fine then the problem is more likely type 2. That being static buildup in your person. Simply touch something that can ground you and it should fix the issue. A metal tap should work. Be wary, you might even get a little zap as you discharge