Database Info

Sooooooo many problems since nougat update!

Well this really sucks. I've been telling people for a long time that my G5 has been the best phone I've ever had...a true powerhouse. Then came the Nougat update. Since then it's been nothing but problems. I called Verizon, LG (useless), and Google. All said 'try a factory data reset, that should fix everything'. Yeah, right. So after the Ohhhhhhh-so-painful FDR, I still have all the same problems. When plugging in the oem or third party fast chargers (I have two of each), the notifications will simultaneously say "slow charging" and either "charging" or "fast charging" at the same time. Unplugging and reconnecting will fix it every time. Also, I'm getting ghost images when changing screens...I can still see a shadow of the previous screen which eventually fades away. These are both just minor annoyances, but still weren't there before. But also, my NAV appears to have a hard time keeping track of where I am. More annoying. But the biggie is that I can no longer use any of my many Bluetooth headsets for phone calls. You just can't have a Bluetooth conversation anymore. Streaming audio is fine. But calls aren't doable. That's a problem. Since I already tried an FDR to no avail, Verizon is going to send me a new phone. All I can say is if it comes with Marshmallow, I'm leaving it that way. Any benefits that Nougat brought are far outweighed by the problems. I'll wait until they fix it, maybe then. Anybody else been so plagued by this update?
D Dave

I have the same problem.. I have to charge and re-start the phone to make the phone "charging" otherwise it is intermittently connected and disconnected.. I've done factory reset and didn't work out also.. I guess getting a new replacement from T-mobile is the option here.

I got the new phone that Verizon overnighted to me and got it all set up. It thankfully came loaded with marshmallow and is working fine, but keeps prompting me to install Nougat. I'm going to keep postponing the update for now to give them a chance to work the bugs out. Is there anybody out there who has installed the update on their Verizon G5 without any problems after?

I have the charging issue as well and it started with 7.0.

You should report it. They won't fix something if only a couple people report the problem. They sent me a new phone and I've managed to defer the 7.0 update for over a week now. It prompts me everyday, but I just say later! I'll wait awhile to see if they fix it. The unbearable Bluetooth call quality was just totally unacceptable.

Nougat?
My G5 is still on Marshmallow, and does not see that there is any update to Nougat available. So what are you all talking about?

What carrier are you with? I'm on Verizon, so maybe not all carriers have it yet. Or maybe you're one of the lucky ones who wasn't randomly chosen to be a guinea pig and find all the bugs and glitches. ☺

I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?

Dangerous Dave said:
Is there anybody out there who has installed the update on their Verizon G5 without any problems after?
Click to expand...
Click to collapse
Me, totally problem free. No problems of any kind but it did fix one bug, I had an app that wouldn't run in Marshmallow and it's back working normally again with Nougat, who knows why?

jpradley said:
I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?
Click to expand...
Click to collapse
Try to keep up.

I have the G5 on Verizon and am fully updated. The only problem I've had is with storage space. 85% full and I'm lagging frequently. I've deleted as much as I can, to no avail. I can't seem to get anything successfully moved to the SD card, so I'm not sure of its purpose.

I´ve got exactly the same problems and more.... What did you do to fix them in the meantime?
To add another problem, my fingerscanner isn't working 9 out of 10 times.
It became an annoying piece of ****! Please help to get my awesome phone back.
Greetz from the Netherlands

I've had other bluetooth issues... I have to restart bluetooth nearly every day to get it to connect to my devices, it's as if the bluetooth apk is hanging up in the background.
That said... My phone updated to 27A this morning, so I guess I'll find out in the next few days if I have the same problem, lol

Well the 27A update must literally be ONLY the security patch. It didn't fix the bluetooth issues...

Seriously this update has been the worst. I too am experiencing the power cable issue. I'd say 7 out of 10 times it tells me it's slow charging. Simply reseating the cable fixes it every time. The most frustrating part for me is Facebook and Twitter. With the first Nougat update the Facebook app began to bug out. At least once a day it randomly crashes, even when i'm not actively on it, and begins a crash loop that won't stop until I restart the phone. that usually fixes it. I'd say every other week I've had to straight up re-install the FB app to fix the crash loop. and now after the recent update that was pushed the twitter app keeps failing to load some images. Most tweeted images show up fine but profile/banner images will not. Again fixed with a restart. This is really quite frustrating. I don't understand what they did to break Nougat so badly. My friends Pixel hasn't had any of these issues. I'm getting so fed up with my G5. I love it but it just so damn locked down and now this. It really makes me wary of getting another LG phone

Well, it's been over three months since I started this thread. The problems after the Nougat update were just unacceptable, so Verizon sent me a new phone loaded with Marshmallow. I've been deferring the update every day for three months. Last night I accidentally tapped the wrong spot on my screen and it installed the damn Nougat update. I've had the update less than 24 hours now, so haven't tried everything. But I can tell you they haven't fixed the problem with the slow charge/fast charge, as it came back IMMEDIATELY after the update. I called Verizon today to ask why the hell LG couldn't fix that issue in three months time! Verizon called LG for me and inquired if there was a fix. LG said if I send the phone back to them, they'll fix the corrupted files and send it back to me. Really?!? Both my G5s experienced the same problem immediately after the update and they couldn't fix the issue in the download in three months time? Douchebags. Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!

Dangerous Dave said:
Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!
Click to expand...
Click to collapse
Unfortunately don't have anything helpful for you, other than to say, you're not alone, and I similarly got sufficiently pissed with this bug today to see if there was a solution yet.
Pretty sure you answered your own question though: they don't actually have a fix because LG has likely stopped developing new releases for the G5 in anticipation of the G6 release. They want you to send it back to them for the "fix" because it's a pain in the ass and transfers the opportunity cost onto you, which hopefully (in their eyes) means they can do absolutely nothing.
I'm just.... beyond frustrated with this ****ing phone. I really wish that I would have limped by on my old HTC M8 until the V20 came out, even with its barely-chargeable battery. At this rate, I would have been better off with a pixel or internal-battery phone for that matter. There is just seemingly no end of software and hardware issues with this phone, and LG's piss-poor customer service gives you almost no recourse for any of them

Hi. G5 VS987 Owner here with a build date of 10/2016 so I've managed to survive the bootloop issues that plagued a great number of us thus far.
My theory is: LG has no clue on how to push an OTA update.
My question(s) are: How many of you updated with the OTA?
And how many updated via LG Bridge or some other flashable method?
I'm wondering what if any difference knowing this makes because while this phone has honestly been the best/fastest/bug free phone I've ever used...the update nagscreen has me wanting to choke the [email protected]!%# out of it. It just won't go away.
I really wanted the Note 7 before they blew up...What to do guys?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Another thing...is there a way to flash back to MM if this update really goes south?

I updated to Nougat OTA with no problems except the power cord which I fixed.
Here's how I did it:
DISCLAIMER! I KNOW this has nothing to do with the problem and cannot possibly fix it but... it did fix it for me so give it a try, OK?
1. When you get the slow charging message look at the power cord, turn it around and plug it in the other way, see if that helps. Once you've determined that plugging the power cord in one way reduces the frequency of the error just keep on doing it that way and in a couple of days the problem will be gone!
I know, I know, but try it, what can it hurt?

Well, interesting update here. Verizon said I could send it back to LG to have corrupt files replaced. I decided that neither option, living with the problem or shipping the phone back to LG, was acceptable. I called Verizon back and told them so, asking for a replacement and hoping it would come with MM. They just sent me a replacement, and it came with Nougat already on board. But would you believe this phone works perfectly! I mean, it rocks! I have NONE Of the problems I had with the last two phones after the OTA update. So maybe the OTA really is a piece of crap. But I gotta say, it's nice to love my phone again.

Intermittent freeze and no sound when making calls: hardware or software issue?

For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.

davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.

reyscott said:
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
Click to expand...
Click to collapse
It has to be at a point now to contact the OEM. On countless occassions I've factory reset and gone to different ROMs from scratch with the issue returning. Thanks.

Hats off to Verizon! I had purchased their total protection plan awhile back where you warrant your phone for 11 bucks a month. If it's lost or stolen you pay a deductible. With this issue I was hesitant but went in anyways.
For one, I didn't have to pay anything because I brought it in on the premise that it's a manufacturer defect (microphone hardware issue). Now if they determine my phone is damaged, the warranty company charges you 299. Mine won't be.
I go in yesterday and they told me I'll be receiving the replacement at my house TODAY. I even got the FedEx shipping memo for it being delivered tonight. Then I can just sent my old one in the same box that's a prepaid label.
Super happy about this!

No Sound
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC

cc999 said:
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
Click to expand...
Click to collapse
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.

New Pixel
davidisflash said:
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
Click to expand...
Click to collapse
What's the manufacture date of the new phone?
CC

cc999 said:
What's the manufacture date of the new phone?
CC
Click to expand...
Click to collapse
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.

davidisflash said:
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
Click to expand...
Click to collapse
better than having a broken phone. I was under the impression that the newer replacements came from google and were unlockable, but I guess only a lucky few,

Battery Issue?

Hey friends. I posted here a few weeks back saying I was having issues with my Pixel freezing and restarting itself. I've already factory reset and reflashed. No dice. My warranty is out by a month so I can't get it replaced.
I have a friend who said he could replace the battery for $35 USD. It's a great price but I don't know that it's 100% the battery. I was hoping you all could maybe chime in and let me know what you guys think. It's very intermittent. It can happen when I'm watching a YouTube video or during a phone call. I've seen a lot of other people having this issue and I think it's crazy Google won't back there problem when it's a known issue. Any advice is appreciated.
Also, an unrelated question. I never seem to get the current security patches until the end of the month. I still don't have Feb. patch and my wife and a friend of mine have had it for a while.
Thanks!
Edit: More information

If the battery is charging and discharging properly, I don't know that I would attribute the freezing/restarting to the battery at all. The Pixel microphone defect could be one possible cause. It's a small crack in a solder joint that can intermittently cause the phone to freeze or reboot when it attempts to use audio. Just do a search for the issue and you should see some articles about the issue.

ForeverZ3RO said:
Hey friends. I posted here a few weeks back saying I was having issues with my Pixel freezing and restarting itself. I've already factory reset and reflashed. No dice. My warranty is out by a month so I can't get it replaced.
I have a friend who said he could replace the battery for $35 USD. It's a great price but I don't know that it's 100% the battery. I was hoping you all could maybe chime in and let me know what you guys think. It's very intermittent. It can happen when I'm watching a YouTube video or during a phone call. I've seen a lot of other people having this issue and I think it's crazy Google won't back there problem when it's a known issue. Any advice is appreciated.
Also, an unrelated question. I never seem to get the current security patches until the end of the month. I still don't have Feb. patch and my wife and a friend of mine have had it for a while.
Thanks!
Edit: More information
Click to expand...
Click to collapse
This has happened to me on a few sparse occasions, I've not found any particular trigger, but can confirm it is not the battery. I also highly recommend against doing a third party battery replacement on any phone that lacks a removable back honestly. I would recommend fully reflashing using the flash all file with the -w intact (back everything up obviously) a couple times. As far as the security patches they are released on the 5th of every month I believe. Manually checking for system updates may resolve your problem as the ota signal might just not be pushing to your device properly. If this doesn't work then you can always grab the factory image on the day of release and manually flash it (without the -w obviously).

What Custom ROM that fixes Microphone Issue?

As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1

chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once

jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?

chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems

If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software

That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.

I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.

UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.

UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2

I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.

chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.

jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)

zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........

Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?

mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse

abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.

Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.

mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:

Recent problems with wifi, bluetooth, over heating

right now I have been using G4 for a long time.
And many problems start to appear on my phone.
I have got Bluetooth lagging, so sometimes disconnected with my earbud.
I have got no internet on 5G wifi, but 2.4G wifi works fine.
I have overheating problem and battery draining problem.
I want to know what I can do to fix or reduce the problem. Please don't tell me to buy a new one. I know it can be a solution.
Another problem is it only get Android 6.0 and I have att version but I am on Tmobile network.
I also want to know if any 3rd party Rom provides have a 7.0 or 8.0 for that?
Any suggestion can help.
If no way to fix or improve, I will look for a new one.

kevinzhang0528 said:
right now I have been using G4 for a long time.
And many problems start to appear on my phone.
I have got Bluetooth lagging, so sometimes disconnected with my earbud.
I have got no internet on 5G wifi, but 2.4G wifi works fine.
I have overheating problem and battery draining problem.
I want to know what I can do to fix or reduce the problem. Please don't tell me to buy a new one. I know it can be a solution.
Another problem is it only get Android 6.0 and I have att version but I am on Tmobile network.
I also want to know if any 3rd party Rom provides have a 7.0 or 8.0 for that?
Any suggestion can help.
If no way to fix or improve, I will look for a new one.
Click to expand...
Click to collapse
If you google LG g4 boot loops it’s all a common issue. There are fixes like baking it in the oven, taking it apart and redoing to heat sink or whatever. But only actual fix is replace the phone. The G4 is common for hardware failure. Just make sure you backup everything as it wouldn’t be a surprise when it bootloops, usually there’s no bad signs before bootloop but can still happen especially since your having hardware problems.
You’ll need an AT&T sim to update the device. Sorry can’t answer on custom Roms though.
Sent from my iPhone using Tapatalk