Database Users

Sprint Hero screen issues had CM6 installed

Hello all and thanks in advance for the help.
I just got a refurb Hero from Sprint a couple weeks ago. I Rooted with Z4Root and started trying out Roms. I had just went from CM 6.2 to 6.1. Had everything working fine until my screen would stop coming out of hibernate mode. I would have to reset the phone to get the screen back on. It has gradually gotten worse (over the course of one day). Now when I reset the phone I might get the screen to turn on 1 out of 40 times, but the screen is now all messed up even when it does turn on now. I cant figure anything out other than to answer a call because I know where the slider is supposed to be on the screen for answering calls, so if someone calls I cant see anything I just swipe the screen and it answers fine.
Any ideas what might be causing this issue? Would it be a harware issue?
Thanks again

Yea I would try a different download you might have gotton a bad one. Also you should try a different rom after a full wipe. If that didn't work then I would say its a hardware issue.
Something.About.Me.U.Don’t
Like.Its.Cool.I.Understand.
.AWAH.

Thanks for the reply. I did nandroid back to every previous backup I had. Now I cant get the screen to turn on at all so, Im guessing its hardware. taking it to Sprint Today, we'll see what they say.
Thanks again

Yup, They replaced the screen and I'm back in business!

Swwet, glad to hear it man now enjoy more xda
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.

I was just wondering if there was something to do with installing different roms that could have cause the screen to go out? I am thinking not, but I am new to the whole rooting and rom-ing thing. Is it possible that something I did caused the screen to go out?

Na I doubt it. Hardware usually is the manufacturers fault or user error. Unless you droped it, banged it up real bad or flashed a gsm radio your good. And a screen issue such as yours is most def not a rom issue.The rom dev's on here are solid. And XDA is a well known and respected site. If you need any help with anything just let me know.
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.

cool thanks for the response. I was just worried that maybe I messed it up somehow. Glad that was likely not the case

[Q] Froyo puts my screen to sleep. . .?

I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??

dw77x said:
I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??
Click to expand...
Click to collapse
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?

jenisiz said:
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?
Click to expand...
Click to collapse
Stock charger and not happening on DL09. It does it really bad (2.2) whenever the charger is plugged in, I have heard this is a known issue. Perhaps somehow related to my problem?

do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...

M00NEY said:
do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...
Click to expand...
Click to collapse
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!

dw77x said:
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!
Click to expand...
Click to collapse
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.

this dosent help but i have the same problem at least we not alone

micdawg12 said:
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.
Click to expand...
Click to collapse
Yes, I forgot to mention it happening in certain spots, then eventually the whole screen.
It "seems" to me that the touch screen is prematurely shutting down with the back light still on. Although, sometimes this happens right after I unlock it. Grrr frustrating!

bubbleywine said:
this dosent help but i have the same problem at least we not alone
Click to expand...
Click to collapse
How bad have you had it? bad enough to flash back to eclair or have you been dealing with it? It drove me nuts, I went back. I sure would like to figure it out though!

I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.

jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it?
Click to expand...
Click to collapse
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.

jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.
Click to expand...
Click to collapse
I have the issue on and off the charger, mostly off.. I don't think thats the case.

dw77x said:
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.
Click to expand...
Click to collapse
Yeah for me it ended up being the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. Then after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.

jenisiz said:
Yeah...it's as a result of the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. The after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.
Click to expand...
Click to collapse
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?

dw77x said:
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?
Click to expand...
Click to collapse
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.

jenisiz said:
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Click to expand...
Click to collapse
I guess when an oem Froyo comes out <sinkers quietly> I will odiin back to E101 and try and ota and see what happens.

jenisiz said:
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.
Click to expand...
Click to collapse
Not to bash Samsung but sheesh, if they are that fussy, I will probably not buy again.

Weird HD2 unresponsive screen

Now I've read about a problem of the hd2 having digitizer problems and that only a replacement will fix the unresponsive touchscreen issue. But why is it that when I can get my touchscreen to work that it works flawlessly until it goes to sleep? Then i have to continually wake and swype and sleep over and over until it responds. It just seems very weird that after it wakes that it never seems to have a problem. I'm using the miui rom right now and have set the screen to never go to sleep. So I want to see how long it will go without this problem. Has anyone else seen this happening with their phone as well?

Make sure the kernel, and Rom are up to date.

I have that too on an AOSP Gingerbread rom. The screen is not unresposive per se but calibration seems off some times, strage for a capacitive screen.

ive had the problem with android before and there were a few different fixes ...
one fix was to turn off compatibility mode
another was kernel
ive also had the problem with wp7 ( nothing a few hard resets and patience couldnt cure )
either way good luck

well since my first post, i hadn't let the phone go to sleep once and it worked perfectly fine. so i decided to turn off compatibility mode and let it go to sleep.... and when i woke it and i slid my fingers down it actually worked. so far it's worked every time. why would compatibility mode mess up the touchscreen though?

i have NO earthly idea! just a little tidbit i picked from a dev. i would speculate but would end up looking and sounding foolish. so im going to quit while im ahead and have actually been of help :-D cheers

Where can i disable compatibility mode?

I get the same problem. I've used a ICS rom for a day or so and suddenly the lockscreen was unresponsive. I thought it was ROM problem, so I flashed Cyanogen 7, but the screen didn't respond as well... I flashed everything to stock (removing magldr and hspl) and the problem stayed... After several restarts the screen started to respond and now it works (sort of). The tricky thing is: sometimes when I go out from some app in android, the screen doesn't respond again. Locking and unlocking the screen fixes this, but only temporarily.
Did this ICS rom screw something (...hardware?!) or is it a pure coincidence that a few people encounters the same problem for the first time in such a short period of time...
And one more thing... my warranty expired 5 days ago... please help!!!

I had this same problem with my phone before my warranty expired; before I flashed any android roms on it, and while it still had stock WM6.5. I called HTC customer support and they had me send in the phone for repair. They replaced the digitizer and I haven't had the same problem since. It was wierd because in my mind is seemed like a software problem because it would respond nicely as long as the screen was unlocked and the instant it was locked the response was very crappy, sometimes it took forever to unlock my phone. So it might somehow be a hardware issue
WaspVL1

Machupichu2 said:
Where can i disable compatibility mode?
Click to expand...
Click to collapse
spare parts!

I repair phone myself and i can say that i get A LOT of hd2's with this problem. For the most part it is the hardware because no matter what software you put on the phone it is just a matter of the luck you have to get it working. My hd2 broke 2 times b4 and it was always hardware. Htc must of messed up with the hd2 digitizer

cmacia06 said:
I repair phone myself and i can say that i get A LOT of hd2's with this problem. For the most part it is the hardware because no matter what software you put on the phone it is just a matter of the luck you have to get it working. My hd2 broke 2 times b4 and it was always hardware. Htc must of messed up with the hd2 digitizer
Click to expand...
Click to collapse
from what ive seen in photos of the leo mobo it looks like the connection for the screen/digitizer (not sure on hardware) is located right behind red end call/power button and from being mashed off,on,off,on,etc loosens/damages connection.
or is the hardware screen issue just a complete shot in the darks chance?
OH ... ive had the software issue (fixed as i mentioned earlier) AND unrepairable (with my limited tools and balls to physically tear into this badboy) hardware issues.

well, it's been a few days and my phone still seems to be fine. it hasn't once locked up on me yet. i don't know why turning compatibility mode would fix this. or maybe the phones connectors were loose and are now miraculously back in at the same time i unchecked compaibility mode. the only bad thing was that this was happening the last couple weeks and i had given up and already ordered a sensation 4g. or well, guess i have 2 phones now

Its seems possible. Every since I replaced my digitizer with a non OEM one its has never failed on me again. And I hope it never does. There dam expensive.
rubledub said:
from what ive seen in photos of the leo mobo it looks like the connection for the screen/digitizer (not sure on hardware) is located right behind red end call/power button and from being mashed off,on,off,on,etc loosens/damages connection.
or is the hardware screen issue just a complete shot in the darks chance?
OH ... ive had the software issue (fixed as i mentioned earlier) AND unrepairable (with my limited tools and balls to physically tear into this badboy) hardware issues.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App

Compatibility Mode
I also have this issue, therefore I just recently flashed my hd2 with Tytung's 4.0 ICS Rom. As expected, this didn't help very much.. What I am now going to try before I send my phone to HTC is to disable compatiblity mode. BUT, I can't seem to find this compatibility mode check anywhere. Could someone please guide me there?

..

Windows 7
I will be flashing my phone with w7 now, to see wether this is an android kernel bug / softare issue or if this relates to hardware. I also see a lot of people saying that after fixing the digitizer it works again, so it might actually be a hardware issue. I will post my feedback when I have tried with w7.

Dead spots on screen...

Really weird.. Out of nowhere , the bottom right corner of my screen has become almost totally unresponsive to touch. The L and the backspace button on my keyboard are nearly unusable.. Anyone have any idea as to how I may be able to fix this? Its like there is a 2 inch by 1cm gap on my touch screen that doesn't respond to touch.. Thanks guys
Sent from my Nexus 4 using Tapatalk 2

Warranty exchange..

Wish I could... Bought the phone through tmobile and I'm getting the run around.
Sent from my Nexus 4 using Tapatalk 2

I have the same problem, but its a band across upper 1/3 of the screen causing weird typing and such, but only in portrait.
Sent from my Nexus 4 using xda app-developers app

Nexus 4 touch screen defect (dead zone, phantom touch)
I have the same problem, I have a permanent ~1cm tall dead zone spanning the width of my Nexus 4, right about the location of the SIM card tray.
On occasion it is not a dead zone, but rather a "very haunted zone" where there are MANY phantom clicks/drags on different areas of the dead zone in VERY QUICK SUCCESSION. When this happens I have found that constantly resetting the phone (maybe 5-6 times) until it returns to normal (see: dead zone) is the only way to fix it.
That whole situation can take up to an hour to sort out, especially since during the orgy of phantom clicks/drags on the dead zone, the touchscreen is essentially a write off and turning it off is next to impossible, meaning that my phone is bricked for a portion of the day. This happens arbitrarily about once every 5 days.
I purchased my phone from Australia one month ago. Was not aware of any problem until I had returned to where I am currently living in China. I'm absolutely gutted that my first android experience has soured, especially after shirking apple because of (living through years of) their own hardware/software issues.
Why can't I just have a quality, working piece of tech?
So far the warranty options available:
1) Store I bought it from says: Send it to LG Australia (1 non-international warranty)
2) Google says: No google store purchase number, no return
3) LG China? - Can't find any information about LG warranty claims in China.
If I send it back to Australia for repair I will be waiting without phone for weeks, AND I'll get taxed at least $100 by greedy China customs when the phone comes back in. (not to mention the postage there and back)
The problem has become worse and worse as have used the phone. Can any of ye android bros possibly offer any sort of advice or even better, a fix, for solving this problem?

tobiakazmer said:
I have the same problem, but its a band across upper 1/3 of the screen causing weird typing and such, but only in portrait.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have this right now. It's about a third of an inch located near the middle of the screen. It spans the entire width of the screen.
I sure hope it's just a software and not a hardware issue. I bought this in the US and I am now halfway around the world.

I had the same problem. For me it was right where the middle row of keys on the keyboard are or where the ring is on the lock screen.
5mm thick bar across the screen. I sent it back to be fixed and it's been fine ever since touch wood.
They replaced the entire screen on mine. This is definitely a hardware issue. I did a factory reset before I sent it back and the problem was still there.
Digitiser is too close to surface I think causing problems.
Sent from my Nexus 4 using xda app-developers app

Guys i have the same problem since this morning.
I tried everything change roms 4.3 / 4,4 and finally returned to stock.
Nothing worked although i had never the same problem before.
So i tried my last chance. Changed radio image with the help of a Toolkit of our forum ( thanks N-Cry Toolkit )
It seems to be fixed for now , i just rebooted.
Hope it will be ok and you could fix yours too

Hey!
denpeirazei said:
Guys i have the same problem since this morning.
I tried everything change roms 4.3 / 4,4 and finally returned to stock.
Nothing worked although i had never the same problem before.
So i tried my last chance. Changed radio image with the help of a Toolkit of our forum ( thanks N-Cry Toolkit )
It seems to be fixed for now , i just rebooted.
Hope it will be ok and you could fix yours too
Click to expand...
Click to collapse
This really worked for you?

em.faris said:
This really worked for you?
Click to expand...
Click to collapse
Well it worked. I cant understand the reason yet but it keeps showing after some time. I m trying changing roms / baseband / bootloader and return to stock trying to identify when it doesnt work and why. It's really annoying and i m tired of it.

denpeirazei said:
Well it worked. I cant understand the reason yet but it keeps showing after some time. I m trying changing roms / baseband / bootloader and return to stock trying to identify when it doesnt work and why. It's really annoying and i m tired of it.
Click to expand...
Click to collapse
well for me its a hardware issue, but since you said it worked fine when you changed the baseband it really surprised me up
actually happy, cuz there are many users who has this problem.
do keep us updated when you find your fix for this. will be of much help may be in future if something goes wrong on my N4

em.faris said:
well for me its a hardware issue, but since you said it worked fine when you changed the baseband it really surprised me up
actually happy, cuz there are many users who has this problem.
do keep us updated when you find your fix for this. will be of much help may be in future if something goes wrong on my N4
Click to expand...
Click to collapse
Had the same touch screen issue for months; had a dead spot in the middle of the screen that would interfere with browsing and games.
Updated OTA to stock KitKat just last week and the problem went away. Hope you guys get lucky as well. :cyclops:

Possible Deadzone fix!
capcanuck said:
Really weird.. Out of nowhere , the bottom right corner of my screen has become almost totally unresponsive to touch. The L and the backspace button on my keyboard are nearly unusable.. Anyone have any idea as to how I may be able to fix this? Its like there is a 2 inch by 1cm gap on my touch screen that doesn't respond to touch.. Thanks guys
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ok... i created an account here because ive had this same problem for the past month at least, but I think i found a fix. It may take a few people to try it as well to see if its definitive.
I have the same 1cm high deadzone spanning the width of my device just lower than halfway from the top.
My troubleshooting led me to this: If its hardware, its only because the software is telling it something it shouldnt be. I'm sure nothing is broken (i.e., from being dropped, etc.) Something is wrong, for sure, but not broken per se.
I took screen shots of temperature and voltage (using CPU-Z app) trying to figure it out. I paid attention to when it happened and when it did not. I boiled it down to two possibilities: temperature and/or voltage (i can explain how i came to this conclusion if you want... would take a bit more explanation).
I charge my phone with the charger plugged into the wall typically. I live in asia so the voltage is a lot higher (but within the appropriate range of the phone). Yet, lately when i go to sleep, I plug my phone into my laptop to charge, rather than the wall... when i wake up the problem isnt there. About 2 hours later or so the problem comes back.
I tried this for a week (charging my phone with my laptop) and the problem is dissipating. As quickly as it escalated (getting gradually worse) it is now getting gradually better.
Try it and see if it works for you. At night when your phone is nearly dead, charge your phone with your USB port attached to your laptop. Try this for a few days. Maybe it will help. Im still troubleshooting specifics to see if it is definitive.
UPDATE: today, the day of writing this, i haven't had the problem at all and it's been nearly 7 hours and the 3rd consecutive night of charging with USB on my laptop.
Nexus 4 - 4.4.2

My dead zone appeared post-Lollipop update
I created an account for the purpose of also reporting this "dead zone" issue.
I elected, on the Tuesday before Thanksgiving, to opt into the OTA Lollipop update. During the process of updating, I noticed my battery drained all the way to 0, while I thought nothing of it.
When the update was complete, I started to notice a dead zone in the middle of my screen when in portrait mode.
Actually, my dead zone spans an inch of my screen.
I have performed several hard resets, soft resets, learned about the ADK & adb, and downgraded all the way to 4.2.
I took the phone, this morning, to a cell repair shop and the technician said that it's not a hardware issue (although I'm not sure he's right).
So, that's my story. If I find a solution, I'll post it.

these dead spots IMO , are because of bad battery or bad charging ...
have any of you facing these issues have used any wall charger other than the default nexus 4 LG charger ?? maybe ur battery was not charged the way its suppose to be .. or maybe ur battery is getting bad.. can sm1 with the problem replace the battery and see if the problem get solved ???and u can try charging it from the original lg charger for 12hrs straight .. it may(temporary) fix the problem /...

Any new ideas for this post? Or is it dead.

Shubhamqweasd said:
these dead spots IMO , are because of bad battery or bad charging ...
have any of you facing these issues have used any wall charger other than the default nexus 4 LG charger ?? maybe ur battery was not charged the way its suppose to be .. or maybe ur battery is getting bad.. can sm1 with the problem replace the battery and see if the problem get solved ???and u can try charging it from the original lg charger for 12hrs straight .. it may(temporary) fix the problem /...
Click to expand...
Click to collapse
i could try the battery replacement on my nexus, when i get the time, ill get back to you if it works....

ok got the dreaded dead spot where the sim card is, i can't unlock my phone. i dont have usb debug enabled, i can push/pull files in recovery but not much more.
ive tried to change the dpi to move the pattern away from the dead zone by editing build.prop manually and pushing it to the phone but cm13 doesn't seem to take the change to build.prop so the dpi is stuck at 320.
now, im trying to set up usb otg and unlock my phone using a wired mouse and y-cable. but quanta doesn't have otg for marshmallow enabled out of the box and i dont have root access to enable it in an app.
is there a file that i can edit and push to the phone to enable otg_hack?

techparkour12 said:
i could try the battery replacement on my nexus, when i get the time, ill get back to you if it works....
Click to expand...
Click to collapse
Did you ever try this?

buffering.... said:
Did you ever try this?
Click to expand...
Click to collapse
i did it, battery has nothing to do with the screen, its better to just replace it.

[Q] screen touch test results

This morning my touchscreen started to make me angry and i dowloaded a test program. There is two lines that is seems to broken? is this a hardware problem? What should i do?

kadirnadir said:
This morning my touchscreen started to make me angry and i dowloaded a test program. There is two lines that is seems to broken? is this a hardware problem? What should i do?
Click to expand...
Click to collapse
Try installing different roms to check if its not just a software-bug. if that doesnt work your digitizer is probably broken.

kadirnadir said:
This morning my touchscreen started to make me angry and i dowloaded a test program. There is two lines that is seems to broken? is this a hardware problem? What should i do?
Click to expand...
Click to collapse
sorry to bring bad news mate, but my first guess would be that your digitizer has failed. Unfortunately it's a relatively common problem with the Nexus 4. To rule out easily the software, just boot the phone in recovery mode and check if the touch screen responds properly in there. If not, i wouldn't even bother flashing other roms or doing a factory reset: your only option remains sending it in for repairs... or you could always try replacing the screen by yourself.
Here are some other threads that deal with the issue:
http://forum.xda-developers.com/nexus-4/help/ultimate-nexus-4-digitizer-failure-t2818144
http://forum.xda-developers.com/nexus-4/help/q-t2810588
http://forum.xda-developers.com/nexus-4/help/screen-touch-test-results-t2822075
There are also a lot of similar problems reported on google's official product forum.