Has anyone else had this with their G Pad?
When you knock on, or use the power button, the screen will turn on (you can see the lockscreen, unlock and run things etc) but the backlight looks to be extremely dim or not on at all! Locking and unlocking brings it back to normal, and there's no issues using the device at all after this, just this random occurrence occasionally. When I say occasionally, if I was to lock and unlock constantly to test the issue, it'll happen maybe once every 10 tries. So far I've only noticed it when I go to unlock it after being locked for 30+ minutes.
I know there are bleeding issues and blue line issues and the likes, but I've not seen this one before. Just don't fancy it being a duff unit!
I have a similar issue... With my device this only happens if I try to turn it on immediately after the screen goes off. It seems to me more ROM related than a hardware issue, but I can't say for sure.
Enviado do meu LG-V500 através de Tapatalk
filipe.co said:
I have a similar issue... With my device this only happens if I try to turn it on immediately after the screen goes off. It seems to me more ROM related than a hardware issue, but I can't say for sure.
Enviado do meu LG-V500 através de Tapatalk
Click to expand...
Click to collapse
Yeah, the more I see it the more I think it may be software related, but reluctant to do a restore on the tab in-case it's a wasted venture. I still can't find anything online, but mine is defiantly more likely to do it after longer periods of time. Had it three times in a row yesterday morning!
rockbigdave said:
Yeah, the more I see it the more I think it may be software related, but reluctant to do a restore on the tab in-case it's a wasted venture. I still can't find anything online, but mine is defiantly more likely to do it after longer periods of time. Had it three times in a row yesterday morning!
Click to expand...
Click to collapse
I have had this since day 1. Though I have also been custom romming since day 1. I can't remember if this happened on stock. But would love to know if these units are defective or if everyone get this.
stock rom same behaviour
Hi just in case someone is still wondering, i have a stock g pad and it shows the same behaviour... sometimes (especially right after locking) when i unlock the backlight doesn't come on. Locking again and unlocking works in this case.
Same here, was happening on stock and it's the same issue on Mahdi rom now.
Sent from my N5
Mine is the same, did you ever resolve this issue?
phillev said:
Mine is the same, did you ever resolve this issue?
Click to expand...
Click to collapse
Unfortunately not! I've got rid of the G Pad now (barely used it after a time. ) but after getting a IVSO cover for it which locked/unlocked the tab for me, I rarely saw it! I turned the pin/swipe lock screen off too as it was a faff to open the case and then unlock the tab, so maybe turning security off did it.
Thanks for the reply I have a feeling its a ROM issue. Mine did it yesterday so I tried an experiment and stuck it on charge and it instantly went to normal brightness. If it was a hardware fault I would have thought it wouldn't alter no matter what.
Related
Anyone else having this problem?
The phone won't turn back on from what I think is locked because the screen is black, but none of the buttons do anything, I have to re-insert the battery and the phone will boot up with the power button. This happens almost every day.
Sounds like a problem with the digitiser/screen, and a candidate for a warranty return ?
Have you tried to switch it off (the screen with short press, not the power) and then on again with the power button? Sometimes it happens on my z too but its just a sw bug. Switch off and on helps here.
-- sent from htc z using xda app
I am able to lock and unlock with the power button normally.
tbalden said:
Have you tried to switch it off (the screen with short press, not the power) and then on again with the power button? Sometimes it happens on my z too but its just a sw bug. Switch off and on helps here.
-- sent from htc z using xda app
Click to expand...
Click to collapse
akira112 said:
Anyone else having this problem?
The phone won't turn back on from what I think is locked because the screen is black, but none of the buttons do anything, I have to re-insert the battery and the phone will boot up with the power button. This happens almost every day.
Click to expand...
Click to collapse
Could be a problem with the contacts on the battery -- perhaps the contact is loose, so when you bump the phone just right it loses power and shuts down.
I had this once last week. I left it sitting on the workbench in the garage for about an hour while I was out there and it became unresponsive to all buttons/keypresses.
A battery pull and it fired right up again.
It was -10C in the garage and the bench is metal. I chalked it up to getting too cold.
It hasn't done it again since I keep it in my back pocket (front pocket has claimed a few digitizers/LCDs in the past!).
akira112 said:
Anyone else having this problem?
The phone won't turn back on from what I think is locked because the screen is black, but none of the buttons do anything, I have to re-insert the battery and the phone will boot up with the power button. This happens almost every day.
Click to expand...
Click to collapse
This is definitely not an individual case as I saw so many DesireZ or G2 users in HK or China raised the same issues on the gfan forum (one of the China HTC forum).
My DesireZ is a genuine one with stock ROM. It happened 2-3 times already of what we called the "sleep dead" in China here.
I locked the phone then after a while when I tried to turn it on, all buttons became dead. Finally I have to pull out and insert the battery again to make the phone alive.
Some of the gfan forum members also encountered the same situation. Some of their phone are Euro version and some Asia Pac version but the cases are the same that means this problem are not only for a specific version. Some say it is becoz of temperature but I really don't think so. I am sure this is a bug......
Bring back to HTC is not a solution as this "sleep dead" phenomenon don't appear every minute. Mine has happened 3 times and I bought this DZ only about 2 weeks.
happened 2-3 times to me too, each time it was sitting in my pocket.
it's summer in Australia so i doubt its anything to do with being too cold.
hasn't happened for about a week now, so i kind of ignored the problem.
That is definitely not good news.
Mind is still stock from Bell, unlocked for use on Rogers.
I guess I may have to find a replacement phone soon.
manleyfu said:
This is definitely not an individual case as I saw so many DesireZ or G2 users in HK or China raised the same issues on the gfan forum (one of the China HTC forum).
My DesireZ is a genuine one with stock ROM. It happened 2-3 times already of what we called the "sleep dead" in China here.
I locked the phone then after a while when I tried to turn it on, all buttons became dead. Finally I have to pull out and insert the battery again to make the phone alive.
Some of the gfan forum members also encountered the same situation. Some of their phone are Euro version and some Asia Pac version but the cases are the same that means this problem are not only for a specific version. Some say it is becoz of temperature but I really don't think so. I am sure this is a bug......
Bring back to HTC is not a solution as this "sleep dead" phenomenon don't appear every minute. Mine has happened 3 times and I bought this DZ only about 2 weeks.
Click to expand...
Click to collapse
I encountered the same problem, so do my friends. Google maps causes the problem in 3 different phones.
Sent from my Desire Z
Anyone found a solution to this? Is it a s/w bug or a hardware issue? Thanks.
As far as I can tell, it's a hardware issue. Happened to me four times randomly before I took it in and exchanged at Bell. My new phone and the phone my friend got (at the same time as my first), has zero issues.
At the time, it didn't matter if it was cold, warm, fully charged, plugged-in, etc. It would do it randomly once every 1-4 days. It didn't even matter after I did factory reset (so software would not be an issue).
I have no idea what causes it but if you're getting the sleep-dead issue, I'd really recommend exchanging it if you can. Better to be safe than wait and find it's not an issue you can fix yourself.
I have a Bell stock Desire Z that has done this twice. First time it happened was when I tried wake it up in the morning after sleeping all night. The second time it was at a Christmas party. Just finished taking a picture. Went to take another shot, bang it was dead. Both times, pulled the battery and it came back to life.
Bought mine from Bell as well less than 2 weeks ago. Do they give any trouble to exchange it? Do they actually need me to factory reset it before returning/exchanging it?
sekhar_777 said:
Bought mine from Bell as well less than 2 weeks ago. Do they give any trouble to exchange it? Do they actually need me to factory reset it before returning/exchanging it?
Click to expand...
Click to collapse
I didn't have any troubles. I did a wipe and factory reset, then wipe again for security though. As long as you're only doing EXCHANGE (not refund), you have 30 days.
I must report that this issue happened on mine as well.
In JuicePlotter, the period where the unresponsiveness happened, juice plotter recorded no power.
(Either that or juice plotter only refreshes the graph when you open the app).
Happened twice within the first 48 hours of getting this phone. In day 3 now.
I have the same problem. It happend to me twice (in two weeks).
I would like to know if this is a software issue.
I still have the stock unmodified rom but am planning to install custom roms.
If this appears to be a hardware error, I should return my phone and get a new one. If it's a software thing, there will be a fix eventually, or I can just install a custom rom and be done with it...
anyone any idea?
Is there anyone with a custom rom who has the same problem?
Like I've said, I doubt it's a software issue (especially when it happens AFTER factory reset). But again, why take the chance? Better to be safe than sorry than be out $600.
happend to me today for the first time too... fully loaded, not pretty cold and stock rom on european version. it seems to simply being switched off. kind of sucks, as i'm having hardcase around which needs to removed everytime first.
mine too
it happened to me too. just after i started using maps and locations. i have it for a month now and this issue just started to surface the past 3 days...ohwell..hope we get a fix soon..or at least a "how to stop this issue" sometime real soon....:|
Sometimes the screen of my Galaxy Nexus freaks out; it behaves as if I'm touching the screen repeatedly while I'm not. It does not happen a lot, but I think it mostly occurs after pulling down the notification menu and touching a notification message there.
I have tried to reproduce this behavior (camera ready so I can video the screen of my GN), so far no luck. Anybody else experienced this?
Of course, as soon as I'm in bed and have put my camera away I experienced the issue again.
Will try again this evening.
That really sounds like a faulty screen I'm sorry to say. I had a similar issue with my HD2 two years ago, had to send it for replacement.
Hmmm I hope not. Since it's very hard to reproduce I doubt I can prove it in order to get a replacement.
It happens to me only when I'm charging the device. Do you use custom ROM? I'm suspecting that right now.
Nope, stock rom. I haven't even rooted it yet.
Finally caught it on video! It's not very focused but it clearly shows my problem.
http://www.youtube.com/watch?v=Z5_tUcosrtQ&feature=youtu.be
I don't think its a hardware problem because I'm mostly experiencing this problem at home. Today at work I used the phone the whole day without encountering this behavior. I'm 15 minutes home and the problem pops up again. Difference? At home the phone is connected to my WiFi. Any thoughts?
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
@rbiter said:
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, it does not happen spontaneously. I happens when I'm using the phone.
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
stopdogs said:
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
Click to expand...
Click to collapse
Sounds like a longshot, but I will try it anyway. Thanks!
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
noobdeagle said:
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
The phone has a stock image. Also it's not rooted and I haven't touched the bootloader either.
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Any takers? If it is a hardware issue i want to fix it ASAP before my warranty is up!
I have it too, wipe doesn't help. I will try flash a stock rom..
dymex said:
I have it too, wipe doesn't help. I will try flash a stock rom..
Click to expand...
Click to collapse
i've found myself at 99% when it's plugged in and it won't charge anymore. not sure if it's a hardware thing or a rom thing. it's intermittent though... haven't found a fix yet...
Please share what you find out after you revert back!
Sent from my Galaxy Nexus using XDA
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
tokuzumi said:
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
Click to expand...
Click to collapse
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Hydera5 said:
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I've seen a similar issue where the device will not charge while connected to power. A reboot will resolve the issue but, for obvious reasons, this is less than optimal.
Is there any way to identify what application (since this only changed recently) might be causing the issue?
Thanks!
M
Oh come on!! Don't people use the search function anymore!?!? See http://forum.xda-developers.com/showthread.php?t=1676711 or the other 20-30 threads regarding this issue.
Basically, you need to replace your USB charging board, and Samsung will claim water damage and make you pay for the whole repair...
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Sorry, I'm not targeting you. I'm just not okay with people creating new threads instead of contributing in existing threads regarding the exact same issues.
MJMcMahon said:
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Click to expand...
Click to collapse
Problem solved (sorta) i called customer care and they said that it was a "common problem" and usually was a result of using a charger other than the one that came with the phone... Long story short they are sending me a new one, new post here if you are still in the helping mood (;
http://forum.xda-developers.com/showthread.php?p=26729008#post26729008
This issue just started happening on my Galaxy Nexus last week. I just called Verizon and explained what was going. I told the rep I hard reset the phone and it still occurs. He said it was a known issue and overnight ed a replacement. If you're having this issue Verizon seems very aware of it.
I had the same issue .... for me it went away with the newer CM builds [VZW].
Hydera5 said:
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Click to expand...
Click to collapse
Mine just started doing this yesterday. Tried a couple of battery pulls but it still seems to think it's constantly charging. When it starts flopping back and forth between charging and discharging the phone becomes unusable. I'm just wondering if the battery pull was a permanent fix for you or did you have to send it in eventually?
My phone has developed a problem with vibrate.
I get no vibration from it at all. However, if I install an app that produces a constant vibration and set it off, nothing happens unless I smack the phone into my hand, at which point it will vibrate very weakly and gradually decrease in intensity over the course of about 3 seconds at which point it stops entirely again. Feels like how it would if the battery was dying.
Is this a duff motor or is there something else that I can check? The phone is about as hacked as they come so I don't really have a leg to stand on warranty-wise (bootloader was done thru htcdev) so it's looking like I'm gonna have to get the spudger out
dazultra2000 said:
My phone has developed a problem with vibrate.
I get no vibration from it at all. However, if I install an app that produces a constant vibration and set it off, nothing happens unless I smack the phone into my hand, at which point it will vibrate very weakly and gradually decrease in intensity over the course of about 3 seconds at which point it stops entirely again. Feels like how it would if the battery was dying.
Is this a duff motor or is there something else that I can check? The phone is about as hacked as they come so I don't really have a leg to stand on warranty-wise (bootloader was done thru htcdev) so it's looking like I'm gonna have to get the spudger out
Click to expand...
Click to collapse
Run the HTC Function Test and check if it runs in there.
*#*#3424#*#* Vibrator Test should be at the right(bottom of list)
Sorry I probably should have mentioned that I try that. Similar results. If I run it, nothing happens. If I run it and simultaneously smack the phone with my hand, I get a very short, weak burst of vibration.
dazultra2000 said:
Sorry I probably should have mentioned that I try that. Similar results. If I run it, nothing happens. If I run it and simultaneously smack the phone with my hand, I get a very short, weak burst of vibration.
Click to expand...
Click to collapse
Yeah then it's probably a hardware issue Thought that maybe if it ran in there then we could look towards settings etc but if it doesn't run in there either then it must be hardware related.
I just had to send my device to HTC to get it fixed for this exact same reason.
Since I'm S-OFF, I just masked my HBOOT to appear S-ON and they fixed it no problem.
Captain_Throwback said:
I just had to send my device to HTC to get it fixed for this exact same reason.
Since I'm S-OFF, I just masked my HBOOT to appear S-ON and they fixed it no problem.
Click to expand...
Click to collapse
Seems like it might be a common problem. There's even a video on Youtube that shows steps on how to get to the little motor :cyclops:
http://www.youtube.com/watch?v=jPrLOkWmJeU
Quite a few postson this very forum about vibration problems, in fact....
i had the same problem..
my smartphone has been without vibration for 3 weeks.
I installed "vibrate plus" for try the vibration but not working or sometimes vibrated at very very low intensity.
I installed z-test device to test if it was a hardware problem but the engine vibration was ok.
one day, "playing" with no frills cpu control, I changed the processor frequency at start increasing it.
From that day he returned to work perfectly.
Try to do a test by increasing the frequencies of processors, maybe back to work as well for you.
I hope that my was not just luck, and help you.
Let me know.
PS.
changing the frequency of the processor, I also fix the bug sound.
Weirdly, without doing anything whatsoever, it's started working again today. I even bought a new motor and tools to do it myself, but it's working great today! Weird
Sent from my HTC One_M8 using Tapatalk
dazultra2000 said:
Weirdly, without doing anything whatsoever, it's started working again today. I even bought a new motor and tools to do it myself, but it's working great today! Weird
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
oddly mine just died today too after i was texting the vibration felt weaker and than it just kind of went away i don't want to open up my phone either to replace the motor so i guess im SOL.
Mine is still working after the trouble I had. Maybe try what sheva7 suggested as that might kick it into life...otherwise try and sit it out for a bit and maybe it will magically start working again like mine did...
dazultra2000 said:
Mine is still working after the trouble I had. Maybe try what sheva7 suggested as that might kick it into life...otherwise try and sit it out for a bit and maybe it will magically start working again like mine did...
Click to expand...
Click to collapse
about how long did it die than you had to wait for it to magically come back?
Somewhere between 1 and 2 weeks I'd say. I didn't notice it straight away, and then I ordered parts which took a few days to arrive, and then a couple of days later it started working again
Sent from my HTC One_M8 using Tapatalk
Mine stopped working the 25th of November.
Today, just a few minutes ago, it randomly buzzed for the first time since then. I tried making it happen again and it was not repeatable, so I guess it was just a death rattle. I had a brief glimmer of hope, though....
this is very strange isn't it! Mine Is also doing this, seems to be after installing lollipop, even bought a new motor and replaced and still doesnt work! Im hoping it will kick back in to life at some point!
Mines gone and stopped working again. So frustrated. Again, if I whack it it works for a couple of seconds really weakly. I've always had HTC phones but after the camera lens and vibrate issues I honestly can't wait til I can get rid of this thing
Sent from my HTC One_M8 using Tapatalk
Has anybody noticed an intermittently unresponsive touch screen after the latest OTA? I haven't had any problems since they fixed the original problem way back when.
It goes completely unresponsive and I have to reboot several times to get it to work until it stops again. I'm assuming this is a hardware issue on my end since I haven't heard anybody else talking about it but I just wanted to make sure.
I think I will try a different kernel and/or ROM to see what that does.
Hi,
I have the same issue here, it started a few days ago for me. Up till today I just had to reboot but now it seems completely blocked... I will try again later but this is becoming really annoying
.
I had the same happen to me about 2 months ago. Happened around an OTA.
In the process of trying to replace it. Tried flashing recent factor images but no luck
I've had exactly the same issue as described. Hardware buttons work fine, but no response to touch. Started intermittently and got progressively worse until there is no touch response at all.
The first time this happened, I contacted google support, and they arranged a replacement. That was in June.
The replacement device has now developed the same fault, which progressed in the same way as the first device.
Just got off of the phone with Google support, and my second replacement is now on it's way.
Fingers crossed for 3rd time lucky.
Same thing...
This has started to happen to me -_- replacement is on its way. Doesn't seem like the problem is being fixed more or less just addressed...
DG android fanboy said:
This has started to happen to me -_- replacement is on its way. Doesn't seem like the problem is being fixed more or less just addressed...
Click to expand...
Click to collapse
Sadly they don't think the Pixel c is important enough but least the RMA is straight forward.
Sent from my Pixel C using Tapatalk
Hertshammer said:
I've had exactly the same issue as described. Hardware buttons work fine, but no response to touch. Started intermittently and got progressively worse until there is no touch response at all.
The first time this happened, I contacted google support, and they arranged a replacement....
Click to expand...
Click to collapse
Ditto here. Just received "refurbished" (was actually new--factory wrap, unopened) replacement unit two days ago. Had my initial Pixel C about 10 months with zero issues. Then, a couple weeks ago, touch responsive became spotty, typically cured by putting tablet to sleep and waking. Progressively got worse until no touch response whatsoever. Physical buttons worked fine. Factory reset, tried flashing prior OS versions, etc. Nothing worked. Stock / unrooted.
But, Google customer service was very cool about the replacement.
How were everyone able to contact Google Support? I have the same problems with the touch screen, but am not able to find a way to contact Google about it. I had bought mine straight from Google Store.
DukyY said:
How were everyone able to contact Google Support? I have the same problems with the touch screen, but am not able to find a way to contact Google about it. I had bought mine straight from Google Store.
Click to expand...
Click to collapse
Top right hand corner, "contact Google" > https://support.google.com/store/troubleshooter/3070579?hl=en
I had the same problem after an OTA Security update yesterday. Booting into recovery and erasing cache fixed it for some time, then problem reappeared. Can be fixed by repeating the procedure. Seems a software problem to me.
Same problem. I can't even get it unlocked now as nothing registers.
Sent from my ZTE A2017U using XDA-Developers Legacy app
I guess this is just a hardware issue because it happened to me twice and both times Google provided me with a new tablet. The only advice I can give you is to contact the support because in my opinion nothing can be done at our individual level...
Will they still replace out of warranty? Purchased Dec 21, 15. Tablet had been flawless until yesterday.
Sent from my ZTE A2017U using XDA-Developers Legacy app
Hmmm I highly doubt it, but you can give it a try. Did you try to factory reset yet, just in case?
Yes, initiallyit was slightly working as of Wednesday and I factory reset. No change, but it registers no touches now so I can't even unlock it.
Google is getting me a replacement so I thank them greatly for that.
Sent from my ZTE A2017U using XDA-Developers Legacy app
yeah, google did the right thing by shipping a replacement, bill3508. i just hope whatever hit your device is isolated.
2 issues I've come across lately with my Pixel C tablet:
1. Touchscreen unresponsive
The tablet has lost touchscreen responsiveness. When I touch the screen, nothing happens. Buttons pressing ok - it works.
I have connected the device to the PC by Vysor app. Using a mouse from PC I can manage. I tried diagnostics in programming options (I've turned on show touches on touchscreen and localization of the pointer) but no touches detected however mouse moves yes.
Rebooting didn't help - many trials. Safe mode neither.
I haven't done a full recovery to factory settings yet. I am afraid of loosing USB debugging mode. Looking foreward to finding software resolution before warranty replacement.
2. Power button doesn't light up the screen - possibly backlight fault (software?)
After few trials with power button the screen shows up. Sometimes I try reboot but the problem returns. It is randomly, sometimes after one pressing power buton, sometimes lastlky after few trials withe few rebooting.
When I put the tablet on light (a lamp or sunshine throug window) I can see the view of the screen darkly. So there is the view but without brightness.
Android 7.1.2, N2G47D
I have the same problem now.. However I've noticed the following: When the device is in the case which covers the screen and has a magnet, the problem will persist. If removed from the case and left for a day outside, the problem is gone (so far at least). I will return the device for a replacement and hope google can replicate the issue. Anyone else using a case with a magnet?
Yes I have the same problem and also a magnet case. But for me the problem is not gone, after removed from the case and left for a day outside .
Now I get a replacement from google.
Should I now no longer use a case with magnet? Is the case the reason for a broken pixel c?