[Q] Colored pixel noise issue - Nexus 7 (2013) Q&A

Hello everybody,
I recently bought a Nexus 7 LTE. I decided to unlock and root it with WugFresh's Toolkit. The process worked out fine and I didn't have any problems.
But one day later I got some trouble with it. Sometimes when I unlocked the device there was a kind of colored pixel noise. The Nexus then didn't react to the touchscreen and I was only able to deactivate the screen with the power button. The pixel noise stayed for around 5 min and then disappeared. This issue happened multiple times, so I sent back the device to the manufacturer and got a new one.
My question is, was the reason for this problem the unlocking and rooting or is it a hardware issue? Could it happen again when I root my new device?
If you need pictures, device or software information, just tell me,
Thanks for any help

Hardware is my guess
chaoskoch said:
Hello everybody,
I recently bought a Nexus 7 LTE. I decided to unlock and root it with WugFresh's Toolkit. The process worked out fine and I didn't have any problems.
But one day later I got some trouble with it. Sometimes when I unlocked the device there was a kind of colored pixel noise. The Nexus then didn't react to the touchscreen and I was only able to deactivate the screen with the power button. The pixel noise stayed for around 5 min and then disappeared. This issue happened multiple times, so I sent back the device to the manufacturer and got a new one.
My question is, was the reason for this problem the unlocking and rooting or is it a hardware issue? Could it happen again when I root my new device?
If you need pictures, device or software information, just tell me,
Thanks for any help
Click to expand...
Click to collapse
My guess is it is hardware. I have seen something like this with a bad video cable connection. Just a guess, though.
Any time you suspect it is a different ROM and you are about to send it back, try to return your Nexus to stock and see if it goes away.

mmarquis said:
Any time you suspect it is a different ROM and you are about to send it back, try to return your Nexus to stock and see if it goes away.
Click to expand...
Click to collapse
I did that, otherwise they wouldn't have taken it back. Interesting is that the issue occurred on the stock ROM as well after I flashed it.

Related

[Q] Strange screen behavior

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.

[Q] galaxy nexus power button problem

Ok so iv had my GN for four days now and its developed a problem with the power button.
Sometimes when i try to turn the screen on via the power button it wont respond, at first. It happend last night for the first time, i tried to unlock it and nothing happend, then after trying about 5_6 times it rebooted. Same thing happend this morning.
Has anyone else had this problem?
Does anyone think this could be software or hardware issue?
The phone is completely stock running 4.0.1 on tmoble uk.
Anyones help or opinion would be appreciated.
Try updating to 4.0.2 before you write it off as hardware problem.
Sent from my Galaxy Nexus using xda premium
Thought about that but it would mean rooting , my fear is that it becomes permenant , then my warrenty would be void , i did have it on face unlock when this was happening i have now changed to slide and as yet ive had no problem , i will post here if the problem is fixed for anyone who is interested
I thought the stock build is 4.0.2?
Have you tried pinging for an update in the settings menu?
Sent from my LTE Galaxy Nexus using xda premium
Rooting is not permanent. You can remove it by delete the SuperUser apk and binary; that's what root is. Or if you're paranoid, flash a stock image.
Then lock the bootloader. Hooray, your device is stock.
mwestendorf said:
I thought the stock build is 4.0.2?
Have you tried pinging for an update in the settings menu?
Sent from my LTE Galaxy Nexus using xda premium
Click to expand...
Click to collapse
yeah several times, and its defo 4.0.1
chirea.mircea said:
Rooting is not permanent. You can remove it by delete the SuperUser apk and binary; that's what root is. Or if you're paranoid, flash a stock image.
Then lock the bootloader. Hooray, your device is stock.
Click to expand...
Click to collapse
Yeah i do understand that, my fear is while rooted that the problem becomes permanent (at least for me) then while off for repairs they see that its rooted and tell me to get lost!
Iv had a few problems with this phone like locking up while adding widgets to home screen, locking up half way though a phone call, browser hanging all the time and of course the power button all of which resulting in a battery pull.
Id come to expect this kind of behavior over the last year & 1/2 from my hd2 as it wasnt ment to run android in the first place, but this is a google flagship.
Maybe i just got a dud or maybe its the stock 4.0.1 has anyone on custom rom had any of the above problems?
i think the point is that you can unroot it and they cannot tell the difference that it was ever rooted in the first place. and get your warranty fix.
RogerPodacter said:
i think the point is that you can unroot it and they cannot tell the difference that it was ever rooted in the first place. and get your warranty fix.
Click to expand...
Click to collapse
Yes, but his point is if the power button becomes unresponsive while he is attempting to root/unroot the phone then he wont be able to complete the process.
I haven't experienced anything like what you're describing on my Galaxy Nexus, even while I was running 4.0.1. Does the power button only become unresponsive when you're turning the phone on/off? Or does this happen while trying to lock/unlock the phone as well? If it only happens while you're using the face-unlock feature then it could be a software bug and flashing could fix it...
I would call either Samsung or your carrier about it before deciding to root/flash it myself. Perhaps your carrier will just switch it out for another one they have in stock.
I have experienced this problem as well with the power button. I have the GSM version and I haven't received the 4.0.2 update but I did receive the ITL41F update. After about three or four presses of the power button it becomes responsive again. I think you might be getting the resets if you press the power button repeatedly without waiting a few seconds I'm between presses to get it responsive again. I also do not think it is hardware related and may be some kind of software bug. I am waiting patiently for the updates.
Sent from my Galaxy Nexus using XDA App
Kinbote said:
Yes, but his point is if the power button becomes unresponsive while he is attempting to root/unroot the phone then he wont be able to complete the process.
Click to expand...
Click to collapse
yes thats exatly my point, although i really am leaning toward software as tk123456789 pointed out if i wait a few seconds it will come on though only after i got rid of the face unlock, using face unlock it was a lot worse. Im thinking if it were hadware it would either work or not,
BTW this problem is when i unlock the phone and not when turning it on, i dont think i made that clear.
my power button has stopped working....it only works sometimes but it usually acts like im holding it down....if i pull the battery and put it back in, it boots up by itself and i dont even press anything...idk what to do and im freaking out
I wonder if this is becoming a known problem with Samsung devices. Do me a favor and shake your phone a few times. Try it every now and then until it wakes your phone or the power menu pops up. Means the switch is busted and the contact is floating around. This is what was going on with my Captivate and I haven't found a fix, nor do I want to solder on a new power button.
I left it in rice overnight and now everything is working perfectly! Hopefully it stays that way! It may have gotten wet from my XO skin application! Never ever ever again with a wet apply! NEVER!
Edit: its still doing the same thing again...spoke too soon
sent from my Nexus Prime
I got my GSM Unlocked Galaxy Nexus from the Play Store two days ago and am experiencing the same issues with the power button. It worked fine for the first 24 hours.
I'm on the phone with Google right now to get a replacement phone which is nice because they're contacting Samsung on my behalf.
(I'm within the 14-day replacement policy for new devices)
Flash manually the official 4.0.4 IMM76I.. And relock your bootloader after that and try.. Thats it
Sent from my Galaxy Nexus using xda premium
similar Issue:
I bought a used, rooted Galaxy Nexus. Due to my own (drunken) stupidity not long after my purchase I caused a scratch on the glass covering the display. As I did not want to pay for a out-of-warrenty repair, I left the device as it was.
Some time after, my power button became unresponsive. As it took 3-5 presses to activate the screen I installed the app "PGM Galaxy Nexus" that allows to wake the device with a swipe gesture. Not to long after, the power button stopped responding all together. While researching a permanent solution, my battery died.
In order to be able to use my phone as soon as possible, I brought it to a local (and unfortunately, unauthorized) repair shop. The repair shop tested quicky for any further defects (by plugging the phone into a wall charger - I had done the same at home) and quoted me 50€ for the repair. Some time after, they emailed me that the replacement of the power button did not repair the device. They said however, that the "main power supply IC" is most likely at fault and that a replacement would cost about 120€. As I could not find this chip in the teardown pictures at ifixit, I am not sure if I should invest further trust in the repairshop. In addition and as writen above, charging the device was no problem at all. In fact, I charged the battery that was in my Galaxy Nexus to 100% before bringing it in.
This is where my questions start:
1.: Is a defect of the "main power supply IC" a known defect at all? If there are known defects of the "main power supply IC" are those defects linked to a faulty power button?
2.: Currently, my plan of action is to collect the device and contact Samsung to have it repaired by Samsung itself. Does this mean sending it in? Do they have authorized repair centers like Nokia used to have (NSC) where I could just bring it in?
3.: What might the cost of the repair be? Can it be noticed that the device was opened before? Is root a problem when sending it in for repair?
I would be greatly thankfull for any device and in case I forgot to provide any details, please feel free to ask.
Related Information:
Galaxy Nexus GSM unlocked, bought in Germany
Android 4.2, running no custom firmware but rooted
Purchased by the first owner on 24th March 2012
Running on E+ (simyo) and o2 networks

Galaxy Nexus thinks it's charging when not?

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?

After motherboard replacement, constant signal drops

Hey guys,
I have a 5X that recently had a bootloop. The motherboard was swapped out using a donor phone. The phone is happy now with the exception of constant signal drops. I'm currently running 7.1.2 Pure Nexus rom however this issue was happening on stock 7.1.1 and after a 8.0 update (I reverted back to 7.1.2). The phone will behave normally then out of the blue the single strength indicator triangle is displays empty with an outlined triangle vs the traditional filled. I have no data and no cellular service. The only way I can get service back is after a reboot. Sometimes service will last 10 min, other times 4 hours. When I do have service its significantly weaker than typical, ~ -110. Is there some sort of hardware handshake that needs fixing? Would flashing a different radio be worthwhile? Wifi works fine and never cuts out. Any help would be most appreciated as this is very frustrating! Thanks in advance.
-Jesse
you can flash any roms with your repaired phone?
how did you that??
does your bootloader the "no RPMB" message?
jstein84 said:
Hey guys,
I have a 5X that recently had a bootloop. The motherboard was swapped out using a donor phone. The phone is happy now with the exception of constant signal drops. I'm currently running 7.1.2 Pure Nexus rom however this issue was happening on stock 7.1.1 and after a 8.0 update (I reverted back to 7.1.2). The phone will behave normally then out of the blue the single strength indicator triangle is displays empty with an outlined triangle vs the traditional filled. I have no data and no cellular service. The only way I can get service back is after a reboot. Sometimes service will last 10 min, other times 4 hours. When I do have service its significantly weaker than typical, ~ -110. Is there some sort of hardware handshake that needs fixing? Would flashing a different radio be worthwhile? Wifi works fine and never cuts out. Any help would be most appreciated as this is very frustrating! Thanks in advance.
-Jesse
Click to expand...
Click to collapse
openyourmind said:
you can flash any roms with your repaired phone?
how did you that??
does your bootloader the "no RPMB" message?
Click to expand...
Click to collapse
I'm not sure I understand the question. After swapping, the device behaves like a new phone. I was able to install TWRP, unlock bootloader, root etc. I do not receive any error about "no RPMB".
weird... I'm a little confused.
I read in many different forums that the repaired Nexus5x can no longer be rooted.
I have tried it with mine several times already unsuccessfully.
When you start the bootloader you see the message (no RPMB)
Maybe somebody has a solution for this?
openyourmind said:
I read in many different forums that the repaired Nexus5x can no longer be rooted.
Click to expand...
Click to collapse
Depends on who does it. LG UK replaced my motherboard last month. After repair, I was able to root it as easily as I did when I first got the phone.
my phone was at lg german
for over 2 weeks I am looking for a solution
Mine was not sent to a repair facility, I was fortunate to have a donor. Thread has slightly gotten off topic. Any thoughts to flashing another radio? Are some OS better suited for specific radios? Is there a way to verify which radio is most compatible with my OS / rom?
When I got my 5x repaired (motherboard replacement with brand new manufactured at 7/8/17) I can root my phone, unlocking bootloader etc.
Hi jstein84, I've the same identical problem (motherboard replacement after bootloop, and now intermittent signal and very poor reception, often -110dB)... Did you find any solution?
sebastian90 said:
Hi jstein84, I've the same identical problem (motherboard replacement after bootloop, and now intermittent signal and very poor reception, often -110dB)... Did you find any solution?
Click to expand...
Click to collapse
Could it be that something wasn't reattached correctly by the repairer?
In my case, the phone was perfect for 2-3 months after the replacement (never dropped, never got water in this period). Now, since one week, it started issuing this new problem, which seems to be very common after screen or mb replacement in the 5X. Very poor signal, with every SIM card I tried (it happened after I used the wifi hotspot, but no sure it matters). I've tried resetting network settings and hard resetting the phone, nothing changed. I've also tried to check the speaker component inside the rear case (where there are the antennas). It seems ok, I just noticed that if I cover the bottom left right corner of the phone, the signal totally disappears immediately. I'm getting crazy with this problem...
sebastian90 said:
In my case, the phone was perfect for 2-3 months after the replacement (never dropped, never got water in this period). Now, since one week, it started issuing this new problem, which seems to be very common after screen or mb replacement in the 5X. Very poor signal, with every SIM card I tried (it happened after I used the wifi hotspot, but no sure it matters). I've tried resetting network settings and hard resetting the phone, nothing changed. I've also tried to check the speaker component inside the rear case (where there are the antennas). It seems ok, I just noticed that if I cover the bottom left corner of the phone, the signal totally disappear instantly. I'm getting crazy with this problem...
Click to expand...
Click to collapse
You might try flashing the stock firmware with fastboot. I had a similar issue with bluetooth randomly cutting out. After flashing the stock firmware bluetooth now works without issue. I can't tell you why it fixed it because it shouldn't have made a difference, but maybe something got corrupted. Worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for your suggestion! I'll try and then I'll let you know if it works!
jd1639 said:
You might try flashing the stock firmware with fastboot. I had a similar issue with bluetooth randomly cutting out. After flashing the stock firmware bluetooth now works without issue. I can't tell you why it fixed it because it shouldn't have made a difference, but maybe something got corrupted. Worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've flashed the stock firmware with fastboot, but nothing changed. It seems to be an hardware problem: when covering the right side of the phone, in particular the bottom right corner (and not the left one, as I wrongly said before), the signal immediately drops...
sebastian90 said:
I've flashed the stock firmware with fastboot, but nothing changed. It seems to be an hardware problem: when covering the right side of the phone, in particular the bottom right corner (and not the left one, as I wrongly said before), the signal immediately drops...
Click to expand...
Click to collapse
I'm glad to see this post is getting some new activity. To answer Sebastian's question, my phone seems better but still not great. I seem to have better coverage but I noticed that if I enter a complete dead zone, I get the hollow triangle, and the phone is not able to get service again until a reboot. This is after returning to a known service area. I have received numerous ota updates since my original post so I'm not sure if that's the cause. I had also tried flashing new radios a few months ago but to no avail. I personally believe that its a hardware issue but I have no way to verify that. I'm glad Im not the only one and I hope this helps out somebody. If nothing else its validation that you're not alone.

Question Samsung Galaxy A 32 4 G has a blank/black screen after Android 13 update. Any ideas?

Hi everyone, the phone was working fine, it was left to do an update for 3:00 in the morning. Couple hours later realized phone was blank/ black screen. Followed steps to do power and volume down and all it did was vibrate. It vibrates when plugged in. Two technicians looked at it and said it was a screen problem but a new screen was tried and it only showed a charging sign and after that it went blank again. I am wondering if it was android update that breaked the phone or is it something else. What specific hardware failure or is this software failure?
Any help would be greatly appreciated. Thank you.
My cousin had a similar issue with a black screen when they woke up - however their phone automatically reset itself and lost all data while updated to Android 13 overnight.
KineSight said:
My cousin had a similar issue with a black screen when they woke up - however their phone automatically reset itself and lost all data while updated to Android 13 overnight.
Click to expand...
Click to collapse
Hi, Thanks for reaching out. Definitely seems to be a Samsung problem. This problem however cost me a phone. That's life. Thanks again.
darklord17 said:
Hi, Thanks for reaching out. Definitely seems to be a Samsung problem. This problem however cost me a phone. That's life. Thanks again.
Click to expand...
Click to collapse
tried a firmware reflash?
anyways yes. samsung is a **** and has given me terrible experience with my a32. they dont pay attention to midrangers at all pushing out broken ota updates. My fingerprint sensor is now bricked permanently (no like actually. downgrading firmware doesnt help. its just gone. its fine physically. according to logs but something else broke ig). Then that stupid mobile data bug. where if i was using mobile data jt would disconnect from the cell towers and reconnect. as if there was no service. i saw many people have this issue. I was forced to use a gsi. One ui 5.0 is still pretty terrible for this thing. its not optimized at all. I am waiting for one ui 5.1. the final big update for this phone. Samsung seems to be pushing it out for all the phones. even cheaper than this phone. but looks like they forgot abt it.

Categories

Resources