Hi, I have a problem with the touch screen of the Nexus: a few days ago I realized that a central band of the screen, more or less half an inch high, no longer responds to touch ... To understand, I attach a picture made with 'Position pointer ' from 'Developer options'.
I wonder if anyone has ever had experiences like this, and what do you advise me to do,namely if trying to change the screen, or maybe other most basic solutions (I've read on the web of people who recommend 'squeeze' the screen). Unfortunately the warranty has expired three months ago ...
Thanks in advance
Exact same problem with my nexus, strange:screwy:
Sent from my Nexus S using xda app-developers app
So, what have you done?
hekomat said:
Exact same problem with my nexus, strange:screwy:
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Nothing yet, living with it for the past two weeks, I don't have the time to bring it to an expert yet
Sent from my Nexus S using xda app-developers app
Bump, anyone?
Sent from my Nexus S using xda app-developers app
Had the exact same problem with my old android phone, it was after a great fall... I assume that it is a hardware problem and you have to replace your touchscreen to fix it...
But its not a big deal as you dont use that part most of the time and also "auto-rotate" is always present to help you... And if still you cant touch some things then use VNC viewer...
http//it.kioskea.net/forum/affich-16636-touch-screen-samsung-s5320-non-funziona-piu
I do not know if it can be somehow help .. The page is in Italian, use google translate .. It is said to 'squeeze' the screen, many people seem to have solved .. Do you say that is our case?
Thanks
MD
Related
Hello,
my Backbutton activates itself. While I am watching Videos, or whatever I do it stops shining and I am out of every application I'm using. After about half a minute it's shining again and I can use it normally. It's like pushing the button multiple times. Does anyone has an idea how to fix it? I tried different roms but it looks like an hardware failure to me.
Sent from my Nexus S using xda app-developers app
Happened to me as well it is an issue sometimes with samsung but covered under warranty bring it in to sprint
Hit the thanks button if i helped
Sending it back for support is not an option for me. I imported my device from the US to Germany. The support at Samsung Germany told me that they are not responsible for AMOLED devices.
My second problem ist that my IMEI is crashed since I flashed a rom where the dev made a little mistake. So Samsung won't give me any support.
I thought about changing the display but the price for a new one is about 190 Euro. Way too much... I can assemble and disassemble the device but I think that cleaning the device will not solve the problem.
Any suggestions?
Sent from my Nexus S using xda app-developers app
srichter said:
Sending it back for support is not an option for me. I imported my device from the US to Germany. The support at Samsung Germany told me that they are not responsible for AMOLED devices.
My second problem ist that my IMEI is crashed since I flashed a rom where the dev made a little mistake. So Samsung won't give me any support.
I thought about changing the display but the price for a new one is about 190 Euro. Way too much... I can assemble and disassemble the device but I think that cleaning the device will not solve the problem.
Any suggestions?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
It has nothing to do with the display though.
That's likely the part failing:
http://www.globaldirectparts.com/Nexus-S-Navigator-Flex-Ribbon-p/smsng6098595.htm
http://stellatech.com/samsung-gt-i9020-nexus-s-ui-flex,a,en,810423.html
Verify that the one you currently have isn't simply not connected right.
Thank you. I will have a look if the part is not right connected.
Maybe I have to replace it. But in that case 25 Euro are much cheaper than 190.
Sent from my Nexus S using xda app-developers app
This happened to me once. A day later my display completely died. I could turn on my phone, answer calls, etc the touchscreen worked, but I couldnt see anything. I had to get a new one..
I had this problem too.
I flashed a different radio, and boom!! issue resolved
I occasionally get this too. It only comes up when I'm using cm/cm based kernels though, very odd. I'm on matrix right now and it seems to Beowulf, anybody have some tips or suggestions?
Sent from my iPad using Tapatalk HD
I tried a different kernel and it looks like the problem is solved. I know that you should not count your chickens before they are hatched. But I really think that the kernel was the problem.
Anyway, I am just happy that my phone is working properly.
And now I am waiting for jellybean.
Sent from my Nexus S using xda app-developers app
srichter said:
I tried a different kernel and it looks like the problem is solved. I know that you should not count your chickens before they are hatched. But I really think that the kernel was the problem.
Anyway, I am just happy that my phone is working properly.
And now I am waiting for jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
What kernel were you using?
It was not the Kernel!
Changing the radio solved the problem.
Sent from my Nexus S using xda app-developers app
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1277226
I had same problem and fixed it that way.
Sent from my Nexus S 4G using xda premium
It's Alive!
I don't see how the kernel would have anything to do with the backbutton. Although if it worked out then hey that's awesome. Amazing how much I have learned by reading the forums on this site.:victory:
Just clean off the the backbutton, and maybe it will stop or you have a software bug.
Problem Details below:
The problem is with the screen, though there is not a single scratch or anything wrong physically..
the screen misbehaves from left side of screen, only that portion.
it automatically starts touching itself... :cyclops:
had found its solution too but it which works temporary.
have to use an electric lighter on the screen to make it stop misbehaving.
This way phone works easily for almost a day without troubles.
Please let me know if any one has a permanent solution for the problem!
In case of any further query, please post in or pm me, any help in this regard will be appreciated.
Thanks & best regards,
Mortal Eternity!
Seems to me that digitizer is broken. You'll need to replace it.
Sent from my Nexus S using xda app-developers app
Ted Mosby said:
Seems to me that digitizer is broken. You'll need to replace it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
by digitilizer you mean screen? no sir the screen is not damaged form any where....
I mean glass or touchscreen. It doesn't matter if u can see the damage or not, it can be faulty either way...
Sent from my Nexus S using xda app-developers app
You tried changing roms, kernels, etc? This can help you identify the solution.
My epic 4g touch has been dying at random and the screen flickers before doing so. Many times it tells me theres at least 60% but it dies but usually its very random when it shuts off. I'm running android 4.2 and my galaxy s2 is fairly new. Does anyone know what I can do to fix this?
Sent from my SPH-D710 using xda app-developers app
Getxrealx said:
My epic 4g touch has been dying at random and the screen flickers before doing so. Many times it tells me theres at least 60% but it dies but usually its very random when it shuts off. I'm running android 4.2 and my galaxy s2 is fairly new. Does anyone know what I can do to fix this?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I have no experience with that particular device, but any time there are actual non-binary hardware issues (screen flickering as opposed to, say, simple hard reboot) I get concerned that it's going to be a quagmire rather than a simple fix. Are you still under warranty? Unless others have had similar issues (which should be subject to a Google search) I would say a) replace the batter or b) contact the manufacturer. Sorry for the lack of insight.
By flickering do you mean getting a jagged black screen around the edges,a second before it dies? (I have this problem on my mango, still looking for the reason. )
Sent from my Xperia Mini Pro
Its just the whole screen flickering. My guess is that my battery calculation is off or something thinking there's more/less battery than what really is there.
Sent from my SPH-D710 using xda app-developers app
Thanks for the info, I think the battery is just messed up because the battery terminals are a little faded. I sure hope its not a hardware error in my phone because I don't have a warranty
Sent from my SPH-D710 using xda app-developers app
Hi all, I post here, because I found something very strange on my Nexus 5.
I bought it two weeks ago. Last week I found 4 dead pixels on the screen, so I planned to call Google.
But yesterday I wanted to watch a film with "MX Player" and when the software start, all dead pixels disappear ! Does anyone know what is happening and how solve this problem ? This will avoid me having to contact Google...
Thank you
Most likely they were " stuck pixels " not dead
Sent from my Nexus 5 using xda app-developers app
dia_naji said:
Most likely they were " stuck pixels " not dead
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, but when I leave "MX Player", they appear again..
I can see them in recovery too.
Thanks for the help.
Hello! Sorry if my English is not great, it's not my first language.
I have a Prestigio 3400 Duo and I have two issues with my touchscreen, the multitouch function in particular. My phone is freshly factory reset, done while trying to solve this problem, and
The first problem is pretty apparent, when I'm holding two fingers on the screen in a horizontal line it registers only one point at the center of the two I'm actually pressing (that's what a multitouch test app sees, at least). This happens exclusively in an horizontal line.
The second problem I have is when I'm holding two fingers on the screen and I let one go, the other one - the one that's still holding - is not getting registered for an instant before appearing again. So when, say, I'm playing a game on the phone and my character walks and I press a button at the same time, the character stops for a second. Really annoying stuff.
Is there any solution for either of these? I saw some fix for other phones but they're exclusively for those, not mine.
gyrozeppeli said:
Hello! Sorry if my English is not great, it's not my first language.
I have a Prestigio 3400 Duo and I have two issues with my touchscreen, the multitouch function in particular. My phone is freshly factory reset, done while trying to solve this problem, and
The first problem is pretty apparent, when I'm holding two fingers on the screen in a horizontal line it registers only one point at the center of the two I'm actually pressing (that's what a multitouch test app sees, at least). This happens exclusively in an horizontal line.
The second problem I have is when I'm holding two fingers on the screen and I let one go, the other one - the one that's still holding - is not getting registered for an instant before appearing again. So when, say, I'm playing a game on the phone and my character walks and I press a button at the same time, the character stops for a second. Really annoying stuff.
Is there any solution for either of these? I saw some fix for other phones but they're exclusively for those, not mine.
Click to expand...
Click to collapse
Maybe it's a hardware problem.
What did you do before it happened?
Sent from my A706 using XDA Premium 4 mobile app
Ragkhuza said:
Maybe it's a hardware problem.
What did you do before it happened?
Sent from my A706 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I don't know if it was something that I've done that caused this, I don't play many games so I've noticed it only recently. I can tell you that for a while the phone was rooted - now it isn't - but I've never installed CFWs or stuff like that.
gyrozeppeli said:
Well I don't know if it was something that I've done that caused this, I don't play many games so I've noticed it only recently. I can tell you that for a while the phone was rooted - now it isn't - but I've never installed CFWs or stuff like that.
Click to expand...
Click to collapse
What do you mean by recently the phone was root - now it isn't. Can you explain specifically.
Sent from my A706 using XDA Premium 4 mobile app
Try intalling custom rom or reinstalling stock
Sent from my GT-I9300 using XDA Free mobile app
Ragkhuza said:
What do you mean by recently the phone was root - now it isn't. Can you explain specifically.
Sent from my A706 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I took off the root thing because I wanted to play a game that doesn't accept rooted phones.
tchen100 said:
Try intalling custom rom or reinstalling stock
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Can you direct me to a good custom rom or how to reinstall stock? I'm not good at these things, I don't know much about it.
gyrozeppeli said:
I took off the root thing because I wanted to play a game that doesn't accept rooted phones.
Can you direct me to a good custom rom or how to reinstall stock? I'm not good at these things, I don't know much about it.
Click to expand...
Click to collapse
Take a look at this thread --> http://forum.xda-developers.com/showthread.php?t=2578187
Ragkhuza said:
Take a look at this thread --> http://forum.xda-developers.com/showthread.php?t=2578187
Click to expand...
Click to collapse
Thank you, but there's no stock rom or a tutorial there, so...
I'm bumping the thread, hoping that someone that knows how to fix the problem can see this.
I'd like to at least solve the second problem, because the first one is barely noticeable to me. I basically can't play any game with the second issue because it's really annoying. I read that sometimes these kinds of problems are when you have an app that is used to block the touchscreen of the phone, but I've never used any of those so I don't know.