Develop Bugs

CDMA galaxy nexus - unresponsive to touch

Hello everyone,
Basically went to unlock my phone today and touch screen is not responding, however the hardware buttons work fine. Now i've done some research and found other posts of people with the same problem, however their touchscreen problems seem to be fixed(temporarily, at least) with a battery pull.. mine however is still unresponsive after half a day and multiple battery pulls.
Id rather not have to send in for certified to replace an otherwise perfectly working phone.
Any ideas/suggestions would be greatly appreciated!

bigdeezer20 said:
Hello everyone,
Basically went to unlock my phone today and touch screen is not responding, however the hardware buttons work fine. Now i've done some research and found other posts of people with the same problem, however their touchscreen problems seem to be fixed(temporarily, at least) with a battery pull.. mine however is still unresponsive after half a day and multiple battery pulls.
Id rather not have to send in for certified to replace an otherwise perfectly working phone.
Any ideas/suggestions would be greatly appreciated!
Click to expand...
Click to collapse
are u undervolting?

Nope, sorry forgot to say. Completely stock never unlocked or rooted.
Also i tried getting into recovery to try and do a factory reset but when i select recovery i just get the android on his back with the red triangle..
so instead i just went through the steps and unlocked the bootloader and booted up (in order to give me the factory reset without having to touch the screen)
It unlocked and booted up fine but still no response..
No new recent app installed and never had this happen before.

Mine did this after a few days of owning it, and luckily the store took it back and swapped it out with a perfectly working unit. Is yours within a few weeks of purchase?

Figured this out randomly. Remove battery cover. With phone turned on, press on the area to the to the left of the camera lens until the screen is responsive. My screen becomes unresponsive when the phone is dropped and this fixes it.

dailong said:
Figured this out randomly. Remove battery cover. With phone turned on, press on the area to the to the left of the camera lens until the screen is responsive. My screen becomes unresponsive when the phone is dropped and this fixes it.
Click to expand...
Click to collapse
hrmm this does not seem to fix either. I also have never dropped my phone, although this seems to be worrisome if the issue is hardware related.
@ tmellen i purchased the phone from amazon and am a few days past my return date :-/
Guess ill just give them a call and hope for the best. Thanks for the ideas everyone.
(update) called amazon and they are sending me a brand new phone.
Knowing this i thought i'd try dailong's method again only this time i was quite a bit more "rough" with pressing down on that area, and it actually worked!
Ill still be taking the new phone once it gets here but for anyone who is having this problem there's a sweet spot on the left edge of the phone towards the top (looking at it with the back cover off) there should be a circle shape. press on that area really hard and it should fix.. weird

Experienced the same on my GSM version a few minutes ago. I had to call my mobile to get it to respond. After that it worked again as normal. I'll see if I get this issue again in the next few days. Hope it's just random

Had the same happen earlier to mine and I was on AOKP. I've had this happen to other phone before, shouldn't be a a cause for alarm unless it happens very frequently. Btw, next time it happens to me I'll give that left side of the camera trick a try.

mine got fixed by removing battery.

[Q] Random reboot and hang

Hey all! I've had my T989 for about half a year now, and since I've gotten it, it's had this strange issue that has persisted across multiple complete hardware and software swaps. I'm pretty convinced I won't be free of it until I can afford to upgrade, but I figured I'd post here since NOTHING seems to work, and see if anyone can come up with something.
To start off, I got the device from Koodo, as they had a great deal on it that allowed me to get it cheap. Ever since the first device, it's occasionally rebooted for seemingly no reason, and hung after the initial boot screen. In order to reset it, I have to hold the power button for a good 10 seconds, causing it to fully reboot again after two short vibrates, following which it will boot up normally.
I initially had a broken speaker, so I took it back and had it replaced, only for the second device to have the same issue. I took that back, and temporarily tried a few other carriers with different phones, but came back to Koodo because I love the T989 too much for the price.
This third phone still had the issue, so I took it back and called Koodo's support line. They fedexed me a new model, which STILL had the same issue.
That would make me think it's a software issue, and a friend suggested that perhaps I had a bad root, but after the phone finally slowed down to near-unusability on Jedi Knight 6, I flashed a few stock ROMs back onto it, until finding one that returned it to normal speed.
I've re-rooted and tried multiple ROMS, with no success. The issue seems to persist across hardware and software. The only thing that seems to be common among them all is that I had a ghost armor screen protector applied to them all. I've since heard that ghost armor was using what was basically soapy water to clean the phone before applying the protector, and that this could have entered the phone and caused some kind of problem.
It seems to happen far more frequently when the phone is in my pocket, which leads me to think that it may have something to do with the power button, and perhaps the moisture or something else causing partial pressure on the button to trigger an incorrect reboot. This seems like a long shot to me, but it's the only commonality I can find.
I should note that I have seen the phone do this randomly while sitting on the desk in front of me after I set it down, so it may be that turning the screen off manually causes the same incorrect reboot issue, or it could be that I simply have some kind of magnetic aura that is insistent on trolling me.
Either way, thanks in advance to anyone who replies!

Screen Issues: Right side of screen lags

After using my Pixel daily for 6 months (got the first batch, pre December 25th) and having next to no issues with it (wifi strength sucks, even with Xceed kernel, but it's better than it was), half of my screen decided it wanted to go goofy. I was using it two days ago and everything was working fine, I used it yesterday morning for a few minutes and then plugged it into the Google charger that came with it and let it sit on my couch for a few hours while it was charging. I got on the bus, and pressed the power button to wake the screen and nothing happened. Thinking I had it turned off I held the power button for a few second, and still nothing. So I held it for 30 seconds and when it brought up the bootloader warning the right side of the screen was glitching, same thing happened on the Google logo, boot animation, and continued into Android. I powered it off, hoping it would go away but it didn't. The slight glitch then turned into static "snow" which will then change sporadically based on what I'm doing on the tablet. That area of the screen still works perfectly because touch input works, and when I take a screenshot and view that area of the screen it shows up just as it should. It seems like there is an overlay on the right side of the screen that won't go away. Since it happens from the moment you turn it on makes me think it's a hardware issue but the fact that the screen itself still works perfectly makes me think it's a software issue. I haven't flashed the stock ROM back on it yet or locked it backup yet since I don't have a type c to type a adapter with me, it's still under warranty but I wanted to see if you guys could help me fix it before I sent it back.
TL; DR

This just started happening to me today, exactly as you described.

Interesting. I just RMA'd mine, should be receiving it within the next few days.

I'm returning mine too. I've determined that it's hardware because when I applied pressure around the edges of the screen I felt something slightly pop into place and then the problem was temporarily corrected. If I apply slight pressure to parts of the screen it happens again.
At this point I've flashed back to stock and I'm in an eternal recovery bootloop that I can't fix because acquiring USB drivers that work is incomprehensively difficult.

Just had mine go as well :crying:

Oh wow, that sucks. At least I'm not the only one though. I just got my new one a few days ago and all is well so far, hopefully this one won't screw up. RMA process was very smooth.
As for the USB drivers I usually have to install them manually by using the "select driver from a list"
Sent from my Pixel C using Tapatalk

Same issue on my first one
Here's my post from the mapping problems to serial # thread.
Google RMA process was fine once I was finally able to get a chat window with them.
Be sure to post to the problem mapping thread to help others!!

Add me to the list. Just went through the RMA process and am now waiting for the replacement to come. I can deal with the wifi issue and the random reboots, but having half of your screen corrupted is unacceptable. I don't even know how this is possible unless some genius at the pixel C team decided that it's cheaper to source half a screen and glue them together.

It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.

brando56894 said:
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
Click to expand...
Click to collapse
Most likely some latently defective silicon from Nvidia.
Sent from my Pixel C using Tapatalk

pkelly517 said:
Most likely some latently defective silicon from Nvidia.
Click to expand...
Click to collapse
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.

brando56894 said:
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
Click to expand...
Click to collapse
Of course screenshots would come out perfectly. It's just a memory dump of the video RAM. This is a problem with getting that memory to the display. I think the display driver is part of the SoC. I could be wrong. Maybe it's a cable.
But it seems like a bit in the display driver is never getting enabled.
Sent from my Nexus 5X using Tapatalk

I'm fairly certain that it's a physical issue with the screen or the connection to the screen. When I had this issue I saw a visible change when I applied some light pressure around the edges of the screen. At one point it almost felt like something popped into place and the problem went away (then resumed.) Also, if I applied some pressure on the lagging side of the screen I would see some odd behavior as if the connection was fluctuating. I didn't squeeze hard, but it didn't take much.

I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?

Wow really? That's no good!

Pixel C Screen Issues
Add me to the list, as of this morning. 8 months old.

SpaceGooner said:
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?
Click to expand...
Click to collapse
what's the serial# of your replacement?

lude219 said:
what's the serial# of your replacement?
Click to expand...
Click to collapse
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.

SpaceGooner said:
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
Click to expand...
Click to collapse
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.

lude219 said:
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
Click to expand...
Click to collapse
Thanks for the info. Not sure I'll be able to determine what s/n Google sends me next time, but here's hoping I get a good one and that I've just been unlucky so far. I won't be able to RMA until I get home from vacation later in the week anyway. If they send me another Pixel C that develops the half screen problem down the line, I will surely have to get a refund and maybe go for a top end Chromebook (with Google Play of course) next time.

Second Pixel C with same issue - backlight stops working.

I am on my second Pixel C where the backlight has stopped working after a month. The screen still works, if I shine a light at it just right I can see the contents (especially when they are white), but the backlight just doesn't come on. The previous one did this on and off for about a week while waiting for the replacement, meaning it would occasionally come back on and work for a little while. But, right before the replacement arrived, it went off and never came back on. My replacement did it for the first time today (it is one month old now), I connected to my laptop when I got home and issued an "adb reboot", and it appears to be working again. I have requested a refund from Google, but they said they couldn't authorize it, so I have filed a dispute with my credit card company in order to get my money back.
Overall, I like the device. I have had to work around a few of its shortcomings, but everything was satisfactory. I just can't keep replacing something every month.
Has anyone else experienced this? I mean, I know how to search and have found similar reports, this exact issue. Where the screen still comes on and is visible under the right lighting conditions, but the backlight is just non-functional. If so, what was the recourse you took to solve it? I have tried not putting it in my case (thinking that was the problem), rebooting (which occasionally has worked, but not always), factory resets (real tough without being able to see), plugging it in when malfunctioning, leaving adaptive brightness disabled, cursing at it and throwing my hands up in the air in frustration, etc. Nothing reliably works, and now I am afraid to let it go to sleep seeing how it came back after the reboot today.
Thanks for reading this...

My Pixel C started doing this last week. Wasn't so bad at first, but it's slowly gotten worse and starting last night the backlight will go hours without turning on. I've tried charging it, hooking it up to my computer, and just finished a factory reset and nothing has worked. Just like you if I shine a light at the right angle I can see things, but that's not exactly fun to do. Bought it at the end of March, so it almost made it 4 months.
One thing I should add, and this is probably a coincidence, is it started happening right after I downloaded the July updates. I only mention this in case someone else has had a similar experience.

My second one had gotten even worse, the screen sometimes comes on now, but the right half is either just fuzz or completely distorted, and the touch screen is non functioning.
I have ordered a Samsung galaxy tab s2, and will get my money back either from Google (doubtful), or my credit card company. Hope Samsung updates it at least to N.
I'm so torn, when it worked the pixel was awesome, I love the screen, closest any has come to the ratio of my camera. But two in a row only lasting a month each, and it's hard to consider a third, or fourth...
Sorry yours is glitching out on you, hope you get a satisfactory resolution.

I have the same problem. Exactly like you describe above. Since my Pixel C is one month out of warranty there is nothing I can do except warn others not to buy this product,
Oliver Browne.

Same here for me. First one started with screen issues as described above, lucky for me i was 3 days before the end of waranty, second one lasted 93 days... 3 days out of waranty for a replacement device! Thanks Google for a cheap device...
Envoyé de mon iPad en utilisant Tapatalk

I face the same issue, and was able to turn on the backlight by adjusting its brightness using the touch screen. Try shining a torch onto it while locating the brightness setting. This temporary fix works for me every time, and hope it helps someone.

Trying the torch was very useful! I now know for a 100% that the backlight doesn't work. I used the torch to see what I was actually doing on the screen, and erased all data & cleaned the cache.
Unfortunately the backlight stayed off, so I assume it's a hardware issue.
I've sent an email to Google support, hopefully they can get this one fixed or replaced.

did you manage to fix your issue ?

Same issue here, and no not resolved.
The only thing I can do to work around it is keep tapping the power button every second. Eventually you get lucky and the backlight will turn on. (Rebooting doesn't seem to be needed.)

Hi all,
I bought this tablet as a gift for my little brother. He encountered the very same issue 2 or 3 weeks ago, and it became worse today, as now backlight won't turn on anymore, even after a reboot and a factory reset.
It must be a hardware issue...
I will try to contact their after sales service, as the tablet isn't even 6 months old.

HI, my first Pixel c met this issues after 20 months... first it was only sometimes and backlight came back after some pushes on the power button... but it get worst and worst: 2 days without backlight and at the end half screen fuzzy issues. I order a replacement product with my warranty (2 years in Europe)... and now my second Pixel meets the same issue... with a no responding screen issue too... it's awful and my warranty is over yet... nothing can fix this...! something seems to be bad quality in this device....

I'm on my 2nd pixel c and final. Google support said that because they had replaced it under warranty the warranty only applies to the original purchase date not the replacement which seemed BS to me because I was shipped a refurb tablet
Never the less using adb/ fast boot I was able to get the device into bootloader and blindly reload the entire operating system. It was only until I performed a wipe within TWRP that the screen started working again. Interesting and now off it is working for the past hour or so. Currently applying latest updates but not holding my breath. Unfortunately it looks like Google is killing off the tablets and I don't know if any of their Engineers have actually tried to use a Chromebook in place of a tablet but it just doesn't translate well. If I cannot get this device working reliably I may buy another refurb to get a few more years out of it. The pixelbook is way too heavy for Couchsurfing

The screen comes and goes with no particular interaction. I'm really bummed because I had gotten so used to this device. I buy another but I'm afraid it's going to happen again. I don't see any tablets that are upgrades either. The Android tablet days are over. Pixelbook is not intuitive. Although it runs Android apps it does so very poorly with in Chrome OS and it's very bulky. I'm a try my luck with another refurb off eBay. Have not been able to find anyone that can repair it

Part of Note 10+ Screen Goes Black

This problem just started today, I've done nothing with settings, have not installed any apps recently, did not drop it, expose it to water, or anything that could possibly cause damage. What's happening is that basically about 1 inch-1 inch 1/8 of the bottom of the screen turns black, and at almost random, sometimes it could go a minute and half or so, sometimes 30 seconds, sometimes within 5 or less seconds. The strangest part? The part that goes black still operates fine to touch, so if an icon or letter of the keyboard, or whatever, is located in that area, it can still be selected/operates. Taking a screenshot to try to show it is worthless since it'll show the screen as just fine, so I attached a picture and a video of the problem from an old phone of mine. The blacked out are will go right back to normal if you turn the screen off, wait a second, and turn it back on. Also, if the blacked out area is there, it'll go away after about a half a second when the screen dims right before the screen inactivity turns the screen off. I've only had this phone for a couple months, I got it back on December 7th 2019.

I learned something else. If I manually lower the brightness to a particularly low level, the black goes away, so it seems to in some strange way be related to the phones brightness level (I use auto brightness), this also might explain why the black comes at differing intervals, as my brightness is adjusting constantly to my surroundings, the time before it comes is either shortened or lengthend based on the brightness.

It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.

willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
I was just thinking I might have to do factory reset, if that doesn't work, and it needs repair/replacement, do I go to an authorized Samsung repair place (I know I have one within about a couple miles of my house), it's
obviously well within warranty, or take it to At&t store as I do have that AT&T Protect Advantage coverage for my phone?

willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
Did the factory reset, turned out to be a waste of time. That black bar was showing immediately, right at the setup screen. So I guess it's safe to say that it's a hardware issue, defective whatever. Funny story is that when I bought this phone, my att store only had two of them left, one was immediately defective, it wouldnt get past the main logo screen, and now I got this one and it became defective within just a couple months, got to love it.

willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
Just left AT&T store where I initially purchased the phone. They're shipping out a brand new note 10+ to me today and I'll get it tomorrow ?

Glad to hear! That definitely sounded like faulty hardware. Funny you saw two failures, I guess it will happen with such complex devices.

Note 10 plus screen goes black
Hi i thought i was crazy until i saw your thread. The same thing is happening to me but it does not go continuously so id see two red squares first theyre really small and they appear anywhere on the screen then if try to screenshot them they show upblack in the screenshots instead of red . I just need to know if anyone found a solution yet because my phone came with the warranty booklet but it wasnt filled out.

Tech girl99 said:
Hi i thought i was crazy until i saw your thread. The same thing is happening to me but it does not go continuously so id see two red squares first theyre really small and they appear anywhere on the screen then if try to screenshot them they show upblack in the screenshots instead of red . I just need to know if anyone found a solution yet because my phone came with the warranty booklet but it wasnt filled out.
Click to expand...
Click to collapse
You just need the proof of purchase, or, if you got it on contract, the contract itself will suffice