Related
Is/has anyone experiencing/ed issues with their AT&T HTC One X's Bluetooth A2DP capability when streaming music and/or playing any types of audio?
Mine is a new phone, and it makes a continuous crackling / jitter noise when audio is being streamed to the car's BT stereo. I have also tried this on my computer's BT headset, and it does the same thing. It sounds like the white noise you get from an old TV when you do not get a signal, only the frequency of that noise is less frequent. Using my LG Optimus S right on the side, I do not get any disruptions in my audio stream, so it doesn't seem like it is an environmental interference problem.
Unfortunately I rooted and flashed my phone to Noctural Dirty ROM before I got a chance to try anything out on the stock ROM, so I am not quite sure if this behavior is limited to the ROM (software issue) or if there is actually something wrong with the phone (hardware issue) that I should go get a replacement.
Searching through the forums I am getting mixed feedbacks (some folks are saying that they are getting replacements, while some say that the issue comes and goes).
Any thoughts on this?
Thanks!
Well, for the heck of it I flashed the stock RUU back and lo' and behold, the problem vanished. Crystal clear sound... How can this happen?
As soon as I root the device and flash to a custom ROM, this problem again resurfaces...
Perhaps I am doing this wrong?
From stock:
1) Unlock bootloader
2) Flash recovery
3) Flash boot.img
4) Wipe system, cache, davlik-cache
5) Install rom
6) Reboot
7) Install streaming app + BT pairing
This seemed to happen on all the ROMs I have tried so far - ViperXL, Noctural, CleanROM, Calkulin...
Maybe I also need to flash the radio or something?
Any ideas?
Thanks.
Does anyone have any ideas on this? I tried it on the latest CM10 and it's still having the same issues... The only thing that worked is stock... very disappointing
Sorry, it sounds like possibly hardware.
I'm on Cleanrom, and stream to my truck and use a old Jawbone for voice, both work well enough.
WR
Sent by WR's O/C'd One-XL on CR-V
I guess no one knew anything about this or has this problem.
Anyhow, I exchanged my device for another one and it seemed to have resolved the issue.
What remains curious was, why did the original phone not have any problems on stock ROMs but problems on almost all other rooted ROMs? Perhaps the Bluetooth stack was different or there was some kind of settings difference between these? Ummm...
I have the same issue with my Rogers One X.
However, it does not go away if I revert to stock with the RUU, though it does become much less intense than with AOSP ROMs.
I spoke with HTC tech support on a couple occasions and after several diagnostic steps they concluded it was a hardware problem and issued an RMA. I made it perfectly clear with them that my device's bootloader had been previously unlocked, which did not seem to be a concern since this was hardware-related.
However, after sending my device to their authorized repair center here in Canada, it was returned to me untouched with the mention "Unlocked phone - Return without repair". At the time of sending it in, the bootloader had been relocked and the device was 100% stock.
I called HTC back again, asking why they'd issue an RMA number after I mentioned upfront that I had unlocked the bootloader if the device would just be sent back to me, and they said that there was nothing they could do. They disagreed with this policy but it was that of their service provider called FutureTel here in Canada...
In short: I don't think this issue can be fixed, it is probably a defective motherboard.
I guess I am lucky that AT&T doesn't have the same policy, at least as not as I know of... heh
HTC One X bluetooth problem
I have the same issue with my One X. Bluetooth audio sets static and garbled when the phone is in my left pocket. Tried resetting phone and a replacement, but same problem. I tried several different new headsets with same results. Definitely hardware problem. ATT device support center gave me an S3 replacement, but I dont care for the interface, so I may just live with it or send it in to HTC for repair. S3 is way better hardware, but the interface kills it for me.
For some reason the microphone on my Sensation is no longer working
The microphone is incredibly quiet (shouting sounds like a whisper), but there is obviously still some response. Occasionally I get a "popping" noise from the microphone.
I'm trying to work out what could have caused the issue. I'm using Albionman's CyanogenMod 10.1 Jellybean 4.2.2 Rom and no other users have reported a problem with it. The only thing I can think of that might have caused an issue is flashing a new radio and RCdata.img file. I've tried changing the radio and it's not made a difference, but I'm not sure if there's any way of getting rid of the RCdata? Could the radio even make a difference to the microphone?
Does anyone have any other ideas for fixes or ways to find out if this is a software or hardware isse? Any help people can offer would be great! :good:
Quick update and some extra info:
I've tried flashing different ROMs on there and it's made no difference. I get the same whisper level sound in calls, sound recorder and video.
Does the video use the two microphones separately to record sound? If so, if one was broken then I'd still expect the sound to be a lot louder than it is (though obviously not normal volume). The chances of both microphones breaking simultaneously seems kind of slim...
Replaced microphone... still not working
So today my replacement microphone turned up and I set to work replacing it. I plugged it in and powered up the phone to check it was working and I STILL have no microphone :crying:
This leads me to believe that it must be a software problem, so does anyone know what things can affect the microphone? I've tried different ROMs, different radios, taking the SD card out and seemingly everything else
Any ideas?????
Edit: sound is exactly the same with microphone unplugged completely
I flashed the stock RUU yesterday and the microphone came back
I then foolishly decided to try installing a custom ROM and the microphone stopped working. I thought I'd be able to flash the stock RUU again and fix the issue but this time flashing the stock RUU didn't work :crying: I'm wondering if I've got a bad sector on the ROM or something... :crying:
again install stock RUU then
ganeshp said:
again install stock RUU then
Click to expand...
Click to collapse
Yeah, I did... several times. It hasn't worked this time though for some reason.
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
potato muncher said:
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
Click to expand...
Click to collapse
Well since you said that this started happening after you've updated to 4.2.2 you have 2 options
1. Reflash the 4.2.2 update
2. Downgrade to 4.1.2
I hope that helps
Sent from my C2104 using xda app-developers app
Unfortunately, I can't be sure if it's due to 4.2.2 or just a coincidence, since it didn't start immediately after the update. Like I said, that thread about the Ion mic problem got me thinking that maybe this is what happened, in which case it's only a coincidence that I also updated to 4.2.2 a couple of days prior.
"Reflash the 4.2.2 update" - is this different from repairing it via the PC Companion? Like I said, I already did that and a factory reset later on and it didn't help with this.
In any case, thanks for your help! :good:
potato muncher said:
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
Click to expand...
Click to collapse
The ultimate method for fix this problem is send it to sony service center,,i suggest so,,i think it the best choices
potato muncher said:
"Reflash the 4.2.2 update" - is this different from repairing it via the PC Companion? Like I said, I already did that and a factory reset later on and it didn't help with this.
In any case, thanks for your help! :good:
Click to expand...
Click to collapse
You can either use as you said repairing via PCC or just flash FTF.
I've been digging as much as I can on this issue, and so far I haven't been able to find any official acknowledgement or diagnosis of this issue. Please forgive me if this has been discussed before, but I simply cannot find the thread.
So far, I have had 2 Nexus 5's. Both of them had the exact same issue. When I am on a call, occasionally the volume from the other side will drop to a level where I cannot hear it. This happens most often when I am listening through the earpiece, thought it has happened while using speakerphone and multiple bluetooth headsets (plus my car). There doesn't seem to be a specific thing that triggers the issue, the area or type of phone I am calling doesn't seem to matter.
The phone is stock, I've never messed with the OS and the only apps I've downloaded were basic free ones, too many to list but if an app could be causing it I can post a list.
So far, I've tried the following to resolve the issue.
1. Factory reset both phones
2. Change sim card
3. Contacted my wireless provider (AT&T)
4. Contacted LG
5. Contacted google
Changing phones didn't help, Factory reset seemed to fix the problem for a bit but it came back. Changing sim did nothing. AT&T told me that because the device was third party, it wouldn't work properly. (I don't believe that for a second) LG just wanted me to ship the phone to them. (Not an option as they will take 2 weeks to get it back to me) And google just gave me some basic troubleshooting tips that I had already tried.
I cannot RMA the phone, i bought it used off of Swappa. I do not want to pay LG for a repair as this is a software issue and it should be solvable on my own. (though I will send the phone to them if it comes to that)
Has anyone had this issue, or at least heard about it? The only possible explanation I've found is that there's a problem with the noise cancellation software, but no one seems to have any solutions other than send it to LG, which really isn't an option for me at this point.
Thanks a crap load in advance to anyone who can shed any light onto this.
Bump for help please.
We are in the same boat
detailedvenom said:
I've been digging as much as I can on this issue, and so far I haven't been able to find any official acknowledgement or diagnosis of this issue. Please forgive me if this has been discussed before, but I simply cannot find the thread.
So far, I have had 2 Nexus 5's. Both of them had the exact same issue. When I am on a call, occasionally the volume from the other side will drop to a level where I cannot hear it. This happens most often when I am listening through the earpiece, thought it has happened while using speakerphone and multiple bluetooth headsets (plus my car). There doesn't seem to be a specific thing that triggers the issue, the area or type of phone I am calling doesn't seem to matter.
The phone is stock, I've never messed with the OS and the only apps I've downloaded were basic free ones, too many to list but if an app could be causing it I can post a list.
So far, I've tried the following to resolve the issue.
1. Factory reset both phones
2. Change sim card
3. Contacted my wireless provider (AT&T)
4. Contacted LG
5. Contacted google
Changing phones didn't help, Factory reset seemed to fix the problem for a bit but it came back. Changing sim did nothing. AT&T told me that because the device was third party, it wouldn't work properly. (I don't believe that for a second) LG just wanted me to ship the phone to them. (Not an option as they will take 2 weeks to get it back to me) And google just gave me some basic troubleshooting tips that I had already tried.
I cannot RMA the phone, i bought it used off of Swappa. I do not want to pay LG for a repair as this is a software issue and it should be solvable on my own. (though I will send the phone to them if it comes to that)
Has anyone had this issue, or at least heard about it? The only possible explanation I've found is that there's a problem with the noise cancellation software, but no one seems to have any solutions other than send it to LG, which really isn't an option for me at this point.
Thanks a crap load in advance to anyone who can shed any light onto this.
Click to expand...
Click to collapse
I'm being searching a lot to find a solution to this problem, but no luck.
I am using a Nexus 5 from the past 15 days and have the same problem of low to no volume from the speaker (voice of the other party). I initially though that it happens when I am outdoors, but no, it happens indoors too; and this does not happen always, sometimes it is loud and clear sometimes it is not. So I suspect that this has got something to do with the software rather than the software.
Even I don't have an option to send it back to LG cause I bought this in a different country.
My phone is Stock OS, updated to 4.4.4, rooted has Xposed Framework on it.
I also modified the build.prop and set the persist.audio.fluence.voicecall from true to false, but even this did not help.
Please, please, please, if anyone has found a solution to his please let us know.
If you press the back of the phone slightly, does it lower the sound? when i do not apply pressure to any back part of the phone, the sound is clear. with even slight pressure the sound dims on the other side. just noticed this today after trying to troubleshoot the problem. really bad design
IINexusII said:
If you press the back of the phone slightly, does it lower the sound? when i do not apply pressure to any back part of the phone, the sound is clear. with even slight pressure the sound dims on the other side. just noticed this today after trying to troubleshoot the problem. really bad design
Click to expand...
Click to collapse
So far I haven't been able to try that. For some reason the phone has started behaving, though there are a few issues here and there. I'll try this out next time it happens and report back.
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: