Device no longer gets past LG screen, looking for advice before factory reset - AT&T LG G4

So just to preface all this, the phone is probably toast, I got it the day it came out and I've done all the common sense things to get it up and running. I replaced the battery with a fully charged one (complements of LG) and tried to turn it back on. It gets to the LG screen, and sometimes the ATT symbol shows up, but no longer to the home sreen. After I've seen the LG screen, I can no longer do anything. I can however remove and reinsert the battery and begin the cycle anew. So has this happened for anyone else?
After a few minutes of brainlessly attempting to resurrect the device, it now consistently gets to the ATT screen. The problem is that the ATT animation only goes for a few frames and then stops. The blue led flashes slowly, and then nothing (or perhaps another LG screen).

Are you even able to get to the factory reset screen? because I'm having the exact same issue and I can't even get there.
I bought the phone in June and it's been working great until today. I was just using the phone as normal for hangouts when it froze on me. Obviously, I removed the battery and now it's stuck in the same loop that you have described where I have to remove the battery just to get to the LG logo screen upon booting.
Should I contact AT&T support or LG support for this?
---------- Post added at 08:25 PM ---------- Previous post was at 08:08 PM ----------
Seems the only fix is RMA
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734

Same thing happened to me:
http://forum.xda-developers.com/att-g4/general/lg-g4-stuck-bootloop-rma-solution-t3279690

I'm pretty sure you have one of the 1.0 devices. This is a common problem among the first batch of G4s made before October 2015. You can check the hardware revision number by removing the battery. If it says H/R 1.0, your phone is useless now, something to do with the motherboard. Contact LG and demand a replacement, they know about the problem. It has happened to a lot of users.

I had this exact thing happen to me about a month ago. Also a day 1 phone. Took it into ATT to see what's up. They couldn't do anything since I don't have insurance. But they did suggest doing an RMA on the LG site for repair since the phone has a 1 year manufacturer warranty for parts. So I did that and LG fixed the phone and sent it back. Turn around time was like 2 weeks. RMA process was done online. https://www.lg.com/us/support/repair-service/schedule-repair. Best of luck

Today I was in the middle of typing up a Google+ post when my phone started vibrating and wouldn't stop. Realized it was completely frozen so I pulled the battery. At first t wouldn't boot then it booted up fine and I was like "thank god". Went to plug it in and I'm back at the boot screen. Tried my other fully charged battery and Best I could get was to the death star and that's when graphics got distorted then it rebooted and now its hard bricked won't even turn on. Got mine a day before at&ts launch on June 4, really thought by now the motherboard issue was all hype. So why would you have to go through LG and not just get a refurb swap through at&t? As long as there's no visible physical damage shouldn't be an issue I would think
Sent from my SHIELD Tablet K1 using Tapatalk

so yeah AT&T is sending me a replacement, no drama. Not sure what insurance has to do with anything

Related

S6 Pressing Back Button By It's self (Capacitive key)

I'm not sure how this is possible, but about once or twice a day, the back button on my S6 is pressed on it's own. It has happened when the device has been on the desk, I see the soft keys light up, the device vibrates like they've been touched and the app I was on went back, all while I was not even touching the device.
It's happened mostly when I'm holding the phone but not even close to touching the buttons, and once it happened and pressed the back button about 10 times in a row while I watched it.
The phone is completely undamaged, perfect condition, never touched water, not dirty at all, buttons are 100% clean. Happens while it's charging or on battery.
Has anyone else experienced this?
(My device was repaired by Samsung for a different issue, motherboard replaced, this only started happening after the repair)
i have, started like yours random. then it started happening more and more so when i was at the store waiting for someone i decided to factory reset ( factory reset twice while at the store) but it got worse. couldn't even get passed initial setup the phone just kept spamming back button so i just kept going back. luckily i already ordered a replacement s6 from tmobile since i was having some other issue with the phone. sadly the replacement s6 took over 7 days to get here. shipped through UPS and got to hawaii then for some reason UPS gave it to USPS for delivery. kinda sad that i ordered screen protectors 2 days after i ordered replacement phone and the screen protectors got here 4 days later through USPS. but other than that my NEW ( we all know its refurbished) galaxy s6 so far has no issues. even the no audio on calls is fixed.
also if you are going to order a replacement, be sure to let them know you have a GALAXY S6 and the date it was released. i say this because the 2 tmobile reps i talked to kept asking questions they say it was for them to determine if my galaxy s6 that was what 2 almost 3 months old at the time was still under warranty
My s6 was showing the same issue with the stuck back button.
It started randomly but than it went crazy and stuck. I wasn't even able to use it.
But 1 factory reset fixed it.
But yesterday the random stuck back button started again when the phone was on my desk and it was really hot (weather was hot as well as the phone). I turned it off for a while and apparently the issue stopped.
I'm not sure it's temperature, firmware, whatever related but I really don't want to factory reset it again.
No solution here, but it is happening to me as well
Solved
Hi i had the same problem aswell , i bought samsung s6 in Pakistan, after the update the back button kept pressing ghostly, i went to local samsung repair shop and the assistant reset something from the setting and then it was fine, i even asked him what you did and how you did? but he said it is secret lol very stupid. i could have post the solution if i know it, but i think it is very easy and something to do with setting. i am sure it is not hard/soft reset. i will post this on other forums to help other people.
thanks
having this problem with my phone too, i cant even get it to stay on the settings screen long enough to back up my stuff
edit: well i think i solved it. i tried clearing the cache, didnt work. then i did a hard reset, didnt work. then i went back and cleared the cache and did a hard reset at the same time and it seems to have worked.
+1 same problem. It happens mainly when the phone is on the move. Funny thing it happened 3-4 times while taking the metro (go figure) with the data on. Usually when I turn off the data, it reduces the amount of back press.
Normal reset doesn't solve the problem. It stops after a while, probably when the phone cools down. I can't seem to reproduce it, but I believe it has something to do with the data on.
I don't really want to factory reset so I'm going to write to samsung directly as the phone is brand new.
i am having same issue too.
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
Did anyone try loading a custom rom and got it fixed ?
I've had that issue with my first one. Took it back ASAP as it was DOA. Got a brand new one 3 days later as they didn't have any in stock. This one doesn't have any problems. Don't worry to mutch about it. Get it exchanged.
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
I have the exact same problem...did anyone contact the manufacturer and got a response on the matter?
I believe it may be an app setting messing with the system settings. My device did it once and wouldnt allow me to use my device. After factory reset it made it worse so i used twrp and wiped everything but my modem and flashed my stock firmware and it stopped and hasnt done it since
Sent from my SM-G925P using Tapatalk
faiding said:
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Hum that's interesting, thanks for your precious input on this.
I did contact Samsung who asked me to do a factory reset. It didn't change anything.
They redirected me to a Samsung office in Paris, not for repair but for a deeper factory reset... (not sure what they are talking about), but I haven't been there since due to lack of time.
However, I didn't experience the problem since the last update FXXU3QOKN so I'm keeping an eye on it.
Following "faiding's" comment, I'll probably pay them a visit for a replacement.
working "workaround"
workaround:
lower the speaker volume to ~75% in all settings (Media, ringtone, system, notifications, etc...)
Whats going on? why is it working?
some posts ago someone (user called "faiding") mentioned something about EMC leak, or at least he meant to, by mentioning a faulty insulation.
with that in mind i did some testing and found out that the closes radiating component it the speaker... and once you lower its emissions even thought the faulty insulation, the EMC leak is sufficiently low and the 'capacity short' is avoided.
Note: depending on how 'faulty' is your insulation (it varies from one phone to another depending on production line assembly) lower the volume until the issue stops accruing.
not full-proof but working
What worked for me is turn power saving on
possible fix
might be a coincidence, but this worked for me:
(I am a new user so i cant post a link but here is what you should do)
1. enter YOUTUBE
2. find this video: "Samsung Galaxy S6 Touch Screen Sensitivity Fix"
worked like magic for me
Repair tech
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
dslayer83 said:
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
Click to expand...
Click to collapse
Hi dslayer83,
I've the same problem with my S6
Could you solved the problem replacing the charging port?
It would be very important to me knowing how to repair the phone because I buyed it abroad. In my country Samsung does not cover warranty.
Up with this thread!
I had an S6 since January.. initially the problem was very random, maybe 1 or 2 times per day, sometimes would go crazy for a while
Then i had some time with no defect at all (a couple of weeks?) without doing nothing
This past week, the phone was feeling like the MENU button (what menu as in this phone there isn't any?) and that was very weird!
Today, it simply went completely crazy, and now is completely unusable... i can't actually swtich it off as the back key is pressed so quickly i don't have the chance of doing nothing!
EDIT: Managed to reboot and wipe cache... now it is useable, but still hits the button from time to time
Update... went unuseable again today.... factory resetting now...
If it works, shall we suspect is something software related?
Update: Not working... it started giving the phantom touches just after the factory reset then suddenly stopped
Worked fine for few hours, then started craza again
Now i have done a wipe and factory reset again, and still unuseable

Got replacement tablet but will not boot

So, my old tablet had the Y1 battery, and today i got the replacement. Unfortunately it did not respond to power on, screen remained totally black. Tried to hold it for nearly two minutes, but still nothing happened. Left it on charger for 30 minutes or so, and charging light was green. Nothing happened still when trying to turn on.
Contacted Nvidia support and they told me to do the same as i already did. Still did not work....
Was told to fill out RMA form, but since i live in Norway i have to pay 25% customs tax each time a new tablet is sent to me.
Annoying, at least. Any suggestions on what to do?
My replacement received a kill signal it seems. It was working then one day rebooted, went through boot process to a black screen, and then stopped powering on. I tried the recall number they were dumb and told me to file a warranty RMA, eventually they took my info for a manger but I never received a call back. I filled out the customer support form with nvidia and they sent me a canned response about how to reset the tablet. Eventually I escalated and asked some higher ups at nvidia to get me in touch with someone who could look into why a tablet accidentally received a kill signal, before other customers have the same issue. Two days later I have a new tablet in my hands. A RMA is probably all you can hope for at this point.
There have been a few "RMA replacement accidentally killed" reports.
When I get my replacement, I'll be flashing the nomoreota kill switch killer first thing onto the new tablet before letting it onto my the network so it never has a chance to be screwed up.
Marc
rhpot1991 said:
My replacement received a kill signal it seems. It was working then one day rebooted, went through boot process to a black screen, and then stopped powering on. I tried the recall number they were dumb and told me to file a warranty RMA, eventually they took my info for a manger but I never received a call back. I filled out the customer support form with nvidia and they sent me a canned response about how to reset the tablet. Eventually I escalated and asked some higher ups at nvidia to get me in touch with someone who could look into why a tablet accidentally received a kill signal, before other customers have the same issue. Two days later I have a new tablet in my hands. A RMA is probably all you can hope for at this point.
Click to expand...
Click to collapse
Well, my replacement did not receive a kill signal since it did not boot at all. The screen shows no sign of getting power. The tablet was completely dead from the beginning.

LG G5 T-Mobile Won't Turn On

My wife's phone randomly turned off yesterday and we just ignored it. Today, it would randomly restart and/or turn off at least 3 times the whole day. When we have it plugged in to charger, it would randomly turn off and restart. Then we have to pull the battery out to turn the phone on. But now, the phone won't even turn on anymore. I have a G5 (w/ Verizon) and we tried swapping the battery packs and her phone won't turn on. Just to be sure, I plugged her battery to my phone and it started, though it displayed a "Module not compatible with Verizon"
Anyone else running into similar issues?
Yes. Today I had about 30 app updates to do in Google Play. I set it to update all while here at work, put it in my pocket, and went to take care of some tasks here in the building. The next time I pulled it out about an hour after that, I noticed the phone was off. It wasn't hot or overheating, and the power button doesn't respond regardless of how long I hold it in. Recovery mode also doesn't start up. I removed/reinserted the battery multiple times to no avail.
My phone did the same thing! It just froze one day and I had to battery pull to get it working again. Then later on it froze and started resetting over and over again. Finally it froze, shut off, and never worked again no matter what I did. It might be a bad batch of these phones. I am now on my fifth phone. The other three had dead pixels. I hope my fifth phone won't have any of the previous phones issues.
DarkMage619 said:
My phone did the same thing! It just froze one day and I had to battery pull to get it working again. Then later on it froze and started resetting over and over again. Finally it froze, shut off, and never worked again no matter what I did. It might be a bad batch of these phones. I am now on my fifth phone. The other three had dead pixels. I hope my fifth phone won't have any of the previous phones issues.
Click to expand...
Click to collapse
I'm on my second one, but now I'm past the 14 day return window. How do I go about getting this replaced? Can I take it to my local Tmobile store or do I contact LG? Should I be concerned about pictures and data being retrieved off of the phone if I ship it off somewhere in exchange for a replacement device? I know it's pessimistic to say, but if I wanted to return the device due to these defects for a full refund and go with a different phone, is that possible at this point?
I'm in the UK on EE and I've also had this problem with both my original LG G5 and the replacement. The phone display would randomly disappear then it would be impossible to switch it back on using the power button and recovery mode didn't work either. The only way to make it work again was to plug it into the charger.
Luckily I was within the 14 days and have returned them both. The second is awaiting assessment by their engineers but I've lost faith and am going with the Samsung Galaxy S7 instead.
woodie said:
I'm on my second one, but now I'm past the 14 day return window. How do I go about getting this replaced? Can I take it to my local Tmobile store or do I contact LG? Should I be concerned about pictures and data being retrieved off of the phone if I ship it off somewhere in exchange for a replacement device? I know it's pessimistic to say, but if I wanted to return the device due to these defects for a full refund and go with a different phone, is that possible at this point?
Click to expand...
Click to collapse
I called T-Mobile and told them my phone was dead. Saying it was dead allowed me to avoid all the tech support questions and they sent me a new phone with 2 day shipping. I was surprised how quickly they sent the new phone to me. I don't think there is any way they will give you a full refund if you are outside of the 14 day window but you are still well within the warranty period so I would keep bugging them till you get a phone you are fully satisfied with.
In addition you can use the LG backup app to save all apps and the associated data. After everything is backed up wipe the phone that way you keep your data with you on an SD card. I couldn't wipe the data off my dead phone but I doubt it could be retrieved anyway.
woodie said:
I'm on my second one, but now I'm past the 14 day return window. How do I go about getting this replaced? Can I take it to my local Tmobile store or do I contact LG? Should I be concerned about pictures and data being retrieved off of the phone if I ship it off somewhere in exchange for a replacement device? I know it's pessimistic to say, but if I wanted to return the device due to these defects for a full refund and go with a different phone, is that possible at this point?
Click to expand...
Click to collapse
if you call t mobile and tell them about yiur problem they will send you a new one try it
Sent from my SM-G935T using XDA-Developers mobile app

Lg acknowledged bootloop

So today after speaking with a lg rep they told me they are aware of the problem and I was told not to update my phone and that would give me less chance of problems for now as a temporary measure, I called because my phone froze and restarted and it made me nervous lol
Mine restarts randomly or freezes to where I need to pull the battery. This is my favorite phone due to the front camera! I'd hate to have to get a different phone.
Sent from my iPad using Tapatalk
It's my favorite considering how well rounded it is for the price, how long has yours been freezing? Curious if it's the start of a issue or just a flouke
Had the same issue back in july i believe after an update it did go away. I dont know what
The i initial cause was i kept assuming it was a sim or network issue
Sent from my LG-H901 using XDA-Developers mobile app
The v10 is a nice phone, but I'm having so many issues with it, I think I'll be bailing soon. I think my hardware is OK, no random reboots or bootloops, but software-wise something always isn't working. If it's not one thing then It's another. Fixed the issue? Well, great, here's another problem. I'm used to dealing with Android issues, but this phone is pushing my sanity. I'm about ready to throw it in the trash and go buy a new Note 4 on Amazon.
Samsung has it's fair share of problems, and battery life wasn't always so great with the Note 4, but overall it was a much better experience. And it can run AOSP/CM quite nicely while retaining full functionality, the v10 cant, not without sacrificing hardware features like the camera and 2nd screen. I much prefer AOSP(ish) over stock because there is little or no bloat.
The v10 is my first LG and almost certainly my last, they have in all likelihood lost a potentially long term customer. I bought an LG to see what was out there other than Samsung, now I sometimes wish I hadn't left.
Which Driver To Flash From Boot?
Mine froze and upon restart it either gets stuck on the LG splash screen or it shows the splash screen and turns off but never fully booted again.
I tried to use the LG Bridge PC App but because it doesn't fully boot Android, it doesn't detect it. Also if I connect the USB upon booting, I get an "unknown driver" error.
I was hoping there is a way to flash the device from boot via another tool? And which driver would I have to install for it?
Anyone here knows?
Went to update my v10 (I'm not unlocked or rooted) Never turned on again after that. Screen was blank. Swapped it out at Tmobile for 5 bucks.
I moved over to the V10 from a galaxay s5 whihc replaced my HTC m8. THe camera is cool, but the battery management is terrible for this phone. I'm a medium user and am getting 5 hours maybe 6, I can make that work. But the random reboots and freezes are a turn off. I'll put up with it till HTC releases something new or the pixel comes to t-mo. LG did not impress me. And Samsung is only good rooted...maybe i'll see what Huwei is up to.
I got the bootloop last night, just out of the blue. I tried everything to fix it but it seemed bricked. I'm sending it in even tho it might be out of warranty by 1 month. Hopefully they'll just take care of me..
This just happened to me last Thursday. Random freezing then it wouldn't boot. Pulled the battery and was able to get it to boot again. Then I was driving home and it completely died, had to take it in for warranty replacement, just got my new one today. The T-Mobile rep said that they have fixed the issue, so we will see.

My Pixel 2 Randomly shut off

Hi,
Earlier today I was using Google Maps and suddenly the phone went blank and a couple of lines showed up on the screen each a different color for 2-3 seconds and then the phone turned off.
Then I held the power button and it took longer than usual to come back on.
This is the first time this has happened.
And no this is not like what happens when an app hangs/crashes this was completely different and not normal.
Do I have a defective unit?
This is the first time something like this has happened.
Is there a way to check an error log or something?
I've had this happen 3 times so far, twice in the first hour of usage and then once again the next day. Since then (several more days) it hasn't happened at all. Another user reported having this happen 10 times on the first day and support told him to uninstall twitter, I don't have twitter installed myself and hoping that the issue has cleared itself up as it seems to have gone away, though I can not imagine why it would.
I received a new pixel yesterday and haven't had any issues at all out of it. It could be a software bug, but I didn't take any chances and contacted Google.. glad I did. If this new one does it I'll report back here.
Happened during one phone call... I have the next 3 hours in an airport and I'm leaving the laptop off so i think if anything is going to be so problem it will probably happen here.
Mine new pixel has done it twice in the past hour.... IDK what to do.
t2jbird said:
Mine new pixel has done it twice in the past hour.... IDK what to do.
Click to expand...
Click to collapse
Run in safe mode and see what happens?
Call support? RMA?
mine crashed too while on a call using the usb dongle. wth
foosion said:
Run in safe mode and see what happens?
Call support? RMA?
Click to expand...
Click to collapse
Been down that road; this is a replacement, because my original one did the same thing. I'd like to be able to use my phone normally.
This happened to mine about 3-4 times a day and happened once during safe mode. Most of the times I was unaware and found the phone had spontaneously rebooted and I'd be forced to enter my password to get in. Sometimes it would reboot while doing something (send a text or checking something out in settings) and at other times would reboot while just sitting at my desk.
I contacted Google and they asked me to get a new one from my carrier (Rogers), so that's what I did today. I'll try the new one and see what happens.
BTW, I found the Bluetooth really flaky on mine.
Pixel 2 Issues
Yeah. My pixel 2 did the same exact thing yesterday. Two vertical blue lines show up. My phone went black then turned off. Took several minutes to restart. Forget this! I've had so many issues with Google.
This just happened to my phone, on the new update so assumed it was something to do with that as never noticed it on the original firmware. Was on the XDA app, screen went black, completely dead, didn't respond to anything apart from a very long press of the power button, and eventually got the Google boot logo.
What is going on?
---------- Post added at 06:49 PM ---------- Previous post was at 06:40 PM ----------
Just happened again within the space of 15 minutes, again I was in the xda app, screen went unresponsive, then black with two horizontal white bars that faded out. Left it this time and it eventually rebooted itself. What the hell
bloomylicious said:
This just happened to my phone, on the new update so assumed it was something to do with that as never noticed it on the original firmware. Was on the XDA app, screen went black, completely dead, didn't respond to anything apart from a very long press of the power button, and eventually got the Google boot logo.
What is going on?
---------- Post added at 06:49 PM ---------- Previous post was at 06:40 PM ----------
Just happened again within the space of 15 minutes, again I was in the xda app, screen went unresponsive, then black with two horizontal white bars that faded out. Left it this time and it eventually rebooted itself. What the hell
Click to expand...
Click to collapse
Sorry to hear that man! I'm thinking about returning it. I emailed Google a picture I took. Half of it was blue. I haven't heard anything back. This has been so frustrating!
This just happened to me on first full day with the phone, in the middle of typing an email. A shame everything was going perfectly otherwise. Sounds common enough that replacement (at least for now) could have the same issue. Maybe if it's common enough Google will make a statement about it, but seems unlikely. Oh well 14 days left in return window I guess.
Edit: if it's indeed due to the software update at least potential for a software fix is high. Also explains why no reviewers complained although I have a sneaking suspicion they might leave stuff like that out to stay on companies' good side...
i'm done
Google's QC is extremely suspect. I'm on my third Pixel 2. The first one rebooted randomly in safe mode, the second had a bad OLED panel (blotchy, should have never passed QC) and the third one just rebooted itself in safe mode. I'm sending it back until they sort their stuff out, this is ridiculous.
I'm seeing this again on my second Pixel 2 - will contact Google again and see.
I've had this on two devices so far, but after switching to the 8.1 DP I haven't had a single issue. Weird but seems software related.
I've had a few crashes, but they've been so intermittent in the few weeks I've had it that they've never annoyed me enough to think of returning it. If enough of us have had it, I doubt it's down to hardware and so it's likely to be something software based.
Only reason I'm even writing this is because I'm sat on a bus, wasn't even doing anything in particular and the whole phone froze up and I got some weird pink lines across the screen!
Same here. I'm on my 2nd Pixel 2 and am really starting to question the build quality of these devices. The first one had a slight gap between the back glass and the frame which, I'm told, was a manufacturing defect and can compromise water resistance. Well, the 2nd has is too but I don't want to spend another day going to the Verizon store and setting up my phone again.
Now I've had 2 or 3 random shut-downs, with a significant delay before the phone will reboot. Came here to see if others were experiencing it - at least I know I'm not alone with this issue.
I haven't had a shutdown with my Pixel 2. I've been running 8.1 DP since the first week.
Sent from my Pixel 2
I have Pixel 2 , black, and no shut downs or random reboots at all. I've been using it for two weeks. Screen is good, though it is pink hue. I did notice low ear piece volume (especially when I am outside), but im still testing it.

Categories

Resources