Database Info

Headphone adapter - no audio

Has anyone found that their headphone adapter has stopped working for some reason?
Was working fine, and now seems that the phone no longer recognizes the adapter. Power passes through just fine - however, can't get audio out.
Please let me know if you have any suggestions? I don't have a spare adapter to test.
Thanks,
Chip

I'm afraid that is the test. Either use your headset on a different phone, or a different headset on your phone.
You should be able to test a headset at your local phone retailler (just tell them you want to check it works before you buy it)

I'm having the same problem, just not at your stage yet.
I have audio but it's obvious there are some connections that aren't quite lining up since I get mono out of both speakers now instead of stereo and moving the connector at all gives me the typical "short out" garble you hear when you've disrupted a short in an audio cable.
The only time anything is plugged into my phone is when it's laying flat on a desk (I even make sure the wire comes out straight with NO pressure on it at all). I've never forced the cable, had it in my pocket where it could have put pressure on the connection, or anything else that might have caused the problem...
I think it's just wear. I can still charge the phone just fine, it's just audio that is screwed up now. I'm just waiting for the day when I don't hear anything...
...and I'll probably never buy HTC again... since this happened with my Star Trek too.

Beeble said:
I'm afraid that is the test. Either use your headset on a different phone, or a different headset on your phone.
You should be able to test a headset at your local phone retailler (just tell them you want to check it works before you buy it)
Click to expand...
Click to collapse
So I went to the AT&T store - a headset worked fine.
I went out and bought a new headphone adapter - same thing, doesn't get recognized by the Phone, so still SOL.
Question - any idea of this could be software related? I had installed skype (uninstalled to see if this was the cause) and wondering if that did something to the headset settings.
Any value in reimaging with a new ROM to see if this fixes it before calling AT&T warranty?
Thanks,
chip

igolfchip said:
So I went to the AT&T store - a headset worked fine.
I went out and bought a new headphone adapter - same thing, doesn't get recognized by the Phone, so still SOL.
Question - any idea of this could be software related? I had installed skype (uninstalled to see if this was the cause) and wondering if that did something to the headset settings.
Any value in reimaging with a new ROM to see if this fixes it before calling AT&T warranty?
Thanks,
chip
Click to expand...
Click to collapse
If you have flashed cooked ROMs then you will have to flash back to stock for warranty reutrn anyway, so this could likely be your issue.
If you're on the stock ROM, then I would suspect hardware.

Bruce Inman said:
If you have flashed cooked ROMs then you will have to flash back to stock for warranty reutrn anyway, so this could likely be your issue.
If you're on the stock ROM, then I would suspect hardware.
Click to expand...
Click to collapse
Thanks Bruce - about to call AT&T warranty to get relief (within 1 year).

Audio Stuttering

Hello everyone,
I recently obtained an S3 i535. At first, it was working very well. Suddenly the audio became wonky. Now, all audio that emanates from the phone speaker "stutters". This includes ringtones, notifications, music...even the boot audio on startup cuts in and out. Audio through the headphones works perfectly.
I am not completely sure when it started, but it seems that it was right around the time that I rooted.
I HAVE Odin'd back to 4.1.2, with no luck. The stuttering persists.
Also, FYI - at one point, this phone had shattered glass. . I had the glass replaced just before rooting....
Any ideas out there? Thanks in advance...
Mac

ripdoozer said:
Hello everyone,
I recently obtained an S3 i535. At first, it was working very well. Suddenly the audio became wonky. Now, all audio that emanates from the phone speaker "stutters". This includes ringtones, notifications, music...even the boot audio on startup cuts in and out. Audio through the headphones works perfectly.
I am not completely sure when it started, but it seems that it was right around the time that I rooted.
I HAVE Odin'd back to 4.1.2, with no luck. The stuttering persists.
Any ideas out there? Thanks in advance...
Mac
Click to expand...
Click to collapse
Can you provide us a little more detail? Stuff like:
Software:
What ROM are you running?
Are you running any audio mods?
Have you tried re-rooting?
What root method did you use?
Hardware:
Have you recently dropped the phone?
Have you tried to clean the phone's speaker with canned air?
Etc.
Thanks!

Sorry, I left out some info.
Running stock 4.1.2... just flashed back to stock. (problem has ocurred on multiple roms)
First time around used Casual root method.
I have not rerooted.
I have not dropped the phone recently and have not tried to clean the speaker with compressed air.
Thanks for helping.
Sent from my SCH-I535 using xda app-developers app

Kelter said:
Can you provide us a little more detail? Stuff like:
Software:
What ROM are you running?
Are you running any audio mods?
Have you tried re-rooting?
What root method did you use?
Hardware:
Have you recently dropped the phone?
Have you tried to clean the phone's speaker with canned air?
Etc.
Thanks!
Click to expand...
Click to collapse
Also, I just discovered that the sound works MUCH better when the phone is plugged in and charging. Not perfectly...but very nearly perfect.
If I unplug the charging cable. The audio barely works, if at all.
Though maybe this info might help with the mystery...
Thanks again
Mac

ripdoozer said:
Also, I just discovered that the sound works MUCH better when the phone is plugged in and charging. Not perfectly...but very nearly perfect.
If I unplug the charging cable. The audio barely works, if at all.
Though maybe this info might help with the mystery...
Thanks again
Mac
Click to expand...
Click to collapse
SOunds like maybe you broke something internally when you dropped it.

DigitalMD said:
SOunds like maybe you broke something internally when you dropped it.
Click to expand...
Click to collapse
If its charging and sitting on my night stand like it is right now, it works well. If I touch the screen, even without picking it up, it starts to cut out. Do you think it sounds like a hardware problem?
Could installing TWRP have anything to do with it? I installed it right after rooting/unlocking.
I am going to try to flash back to the first 4.1.2 ota. If that doesn't work, I will try to flash to 4.1.1. Personally, i think something got messed up during the root process because it didn't go smoothly the first time....I had to try a second time to get it to work, then the problem started.
Btw, this was my friend's phone. She dropped it, shattered the glass and wanted to get an iPhone. I convinced her to give me the phone, then I had the glass repaired. The speaker was working perfectly until around the time I rooted.

ripdoozer said:
If its charging and sitting on my night stand like it is right now, it works well. If I touch the screen, even without picking it up, it starts to cut out. Do you think it sounds like a hardware problem?
Could installing TWRP have anything to do with it? I installed it right after rooting/unlocking.
I am going to try to flash back to the first 4.1.2 ota. If that doesn't work, I will try to flash to 4.1.1. Personally, i think something got messed up during the root process because it didn't go smoothly the first time....I had to try a second time to get it to work, then the problem started.
Btw, this was my friend's phone. She dropped it, shattered the glass and wanted to get an iPhone. I convinced her to give me the phone, then I had the glass repaired. The speaker was working perfectly until around the time I rooted.
Click to expand...
Click to collapse
Software is never intermittent , hardware is. I suspect you have a lose connector to the speaker inside, I can;t tell you how to fix it, but I'm sure you can find some disassemble instructions that will show you the connectors.

DigitalMD said:
Software is never intermittent , hardware is. I suspect you have a lose connector to the speaker inside, I can;t tell you how to fix it, but I'm sure you can find some disassemble instructions that will show you the connectors.
Click to expand...
Click to collapse
Thanks MD. I pulled the back off the phone and reseated the speaker connection. All is working well...for now at least.
Thanks again.
Mac

And now....the stutter is back....great!
Sent from my SCH-I535 using xda app-developers app

ripdoozer said:
Thanks MD. I pulled the back off the phone and reseated the speaker connection. All is working well...for now at least.
Thanks again.
Mac
Click to expand...
Click to collapse
I have discovered that, after a battery pull, the speaker works much better, then deteriorates over time. I am confused.

No phone audio after rooting and new ROM

So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!

Edit, sounds like a hardware problem.
Have you tried to odin back to stock?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.

dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.

dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4

And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.

I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.

Audio Issue Questions?

I'm having a few Issues with audio on my pixel that I'm having a hard time finding answers to.
1. The biggest issue that I'm having the hardest time finding info about is this; when listening to music through my headphones after about 5 seconds there will be a pop, the all the audio on my phone will stop working completely. no, mic, no assistant, no headset, bluetooth, speakerphone, or speaker in general.
2. Often, my pixel will just not detect headphones at all. or detect them, then play no sound.
3 Sometime only the mic stops working. I know this one is common in android in general.
A reboot fixes all these things, but the headphone pop happens every single time. I'm talking with support now and they want me to factory reset the phone, so we'll see what happens after that. My questions are if any of you have found fixes, and if the problems happen on custom ROMs. And Does ROMing void the warranty on this phone?

Did you buy your phone from Verizon or Google? The pop and audio dying compare results of a poorly made headphone plug. Check with another pair of headphones and see if you get the same results unless you already have. If the alignment is slightly off it could be shorting across contacts although I don't understand why would work for a short period of time and then stop.

I had the issue with several pairs of headphones and auxillary cables. I talked with Google support and they had me factory reset the phone, and that seems to have fixed the headphone jack issue. The other issues still persist with the mic and call problems though.
The guy from Google support doesn't seem to be getting it. I told him that I'm still having issues the other stuff, but he keeps asking if I tried other headphones. This is the 5th time he's asked.

Yeah, the mic only works about %20 of the time. I've had to restart my phone just to make phone calls for about a week now. I'm going to try and get a replacement.

I'm having an issue from time to time where the phone speaker at the top stops working when taking a call. Only happened twice in 3-4 months. reboot fixed it... ugh..

That's how mine started. Now, o times out of ten I have to restart my phone and pray that my phone likes me that day to make a phone call.

Figured I would pop in here guys. Had a Pixel since launch and have had myriad problems, mic stopped working and couldn't make calls, headphones not being recognized. Factory reset didnt help, safe mode no help, etc. Scoured the net and found on google product forums a possible solution, tried it and so far it has worked.
https://productforums.google.com/forum/#!topic/phone-by-google/4kyIdArEve8
basically go to clock app, find alarms and delete them, then delete data and cache from clock app and reboot. worked a charm for me, try it out.

I'll give this a shot. How long has this been working for you?

Anyone having issue with music "skipping" when connected to a 3rd party bluetooth for cars?

chadhoard said:
Anyone having issue with music "skipping" when connected to a 3rd party bluetooth for cars?
Click to expand...
Click to collapse
Occasionally. Typically a reboot fixes it for me.

magicCrazyThing said:
I'll give this a shot. How long has this been working for you?
Click to expand...
Click to collapse
meant to post earlier but got tied up, this worked for a few hours then back to the same thing. I RMA'd the phone and have a new one now. Hope this one is better
also fyi, my verizon new/possibly refurb phone was received today running 7.1 , not 7.1.1 , i thought some had questions about that.

CaddymanLNL said:
meant to post earlier but got tied up, this worked for a few hours then back to the same thing. I RMA'd the phone and have a new one now. Hope this one is better
also fyi, my verizon new/possibly refurb phone was received today running 7.1 , not 7.1.1 , i thought some had questions about that.
Click to expand...
Click to collapse
I'm just waiting until I get another screen ordered for my MXPE to swap my pixel. If that one has issues too I'll probably just try to get my money back. I love this phone, but that's not an issue I can handle.

magicCrazyThing said:
Yeah, the mic only works about %20 of the time. I've had to restart my phone just to make phone calls for about a week now. I'm going to try and get a replacement.
Click to expand...
Click to collapse
I have the exact same issue Are we sure it's a hardware problem?

d3sm0nd said:
I have the exact same issue Are we sure it's a hardware problem?
Click to expand...
Click to collapse
If it's not, then it has to be a really deep seated software issue. I flashed pure Nexus to see if it still did it and had no luck at all. Lol

magicCrazyThing said:
If it's not, then it has to be a really deep seated software issue. I flashed pure Nexus to see if it still did it and had no luck at all. Lol
Click to expand...
Click to collapse
Then i'm ****ed because I bought off ebay and I nobody can exchange my phone. I have to send it to Google and wait probably weeks until I get a new one. :crying:

Microphone and speaker no longer working

I have run into the dreaded headphone jack problem. The phone won't play audio through the speakers and doesn't use the microphone because it thinks that headphones are connected. I've tried resetting it to factory settings and it didn't fix anything which is why I think it's not a software problem.
After some Googling I found that I'm not the only one to have this problem and that Google is replacing the units with this hardware fault. Unfortunately I didn't buy the phone via play store so I can't return it directly to google.
I'd like to try and fix it myself. If anyone knows where I could buy a headphone jack for the 5" pixel I'd be very grateful. Before I buy the replacement part I was thinking of removing the headphone jack and trying to start the phone like without it. My reasoning is that the phone would then default to playing the sound through speakers and I would be sure that it's a headphone jack problem. Would that work at all or the phone won't even start?
I need your advice and opinions, thanks

Please keep us updated as I'm facing the same issue:/

Alaadragonfire said:
Please keep us updated as I'm facing the same issue:/
Click to expand...
Click to collapse
I ordered a replacement headphone jack and as soon as it arrives, within the next 2 weeks I hope, I'll replace it and see if that gets it fixed.
A couple of more details:
-problems started about 3 days after updating to Oreo
-at the beginning the volume would first turn itself gradually down to zero and I had to fight it with the volume up (I would always lose eventually xD)
-there was usually a loud pop heard through the headphones after that 'battle' and then the audio and mic would completely cut off
-restarting the phone would enable the audio and mic again but the problems returned as soon as I plugged in the headphones again (tried with several different headphones)
-factory reset didn't fix it and after a couple of days of problems I'm now stuck with no audio at all and no mic input
-my phone can't recognize the headphones anymore

I have the exact struggle, restart will work for a while and then problem return, when I contacted google they offered a replacement but since I'm not in Canada at the moment, they will not be able to process my replacement request, but google representative told me that I can try and replace the mic with the charging port(as it all comes together) and it should fix the issue, but I also think that it might be the headphones jack, also this happened after I tried Android O beta.

FooFighter312 said:
I ordered a replacement headphone jack and as soon as it arrives, within the next 2 weeks I hope, I'll replace it and see if that gets it fixed.
A couple of more details:
-problems started about 3 days after updating to Oreo
-at the beginning the volume would first turn itself gradually down to zero and I had to fight it with the volume up (I would always lose eventually xD)
-there was usually a loud pop heard through the headphones after that 'battle' and then the audio and mic would completely cut off
-restarting the phone would enable the audio and mic again but the problems returned as soon as I plugged in the headphones again (tried with several different headphones)
-factory reset didn't fix it and after a couple of days of problems I'm now stuck with no audio at all and no mic input
-my phone can't recognize the headphones anymore
Click to expand...
Click to collapse
please update the progress, i'm having the same problem. I hope it get fixed after you replace the headphone jack

malstroms said:
please update the progress, i'm having the same problem. I hope it get fixed after you replace the headphone jack
Click to expand...
Click to collapse
I'm still waiting on the part to arrive. I'm expecting it within the next two weeks. I'll try to document the replacement with photos and/or video so others can do it if it turns out successful

Okay guys, here's the update with some good news and some bad news.
The replacement headphone jack arrived yesterday and the good news is that I replaced it and it seems to have fixed the problem! Yay!
But the bad news is that in the process I damaged the LCD screen so now I'm waiting on a replacement LCD. I guess I should've expected that because the screen and LCD itself are extremely sensitive and the damage is not even visible, but it's simply not working anymore.
So how do I know it actually works? Well since the phone used to be paired to my PC via bluetooth, whenever I turn on my PC a notification sounds on my phone if I want to pair or not.
Minor bad news - I tried to record the whole process as a tutorial for anyone who'll try to fix this themselves but my camera's battery died halfway and I lost everything I recorded.
Here are the 2 teardown videos I used for guidance: First and Second. I highly recommend you watch them entirely before attempting anything.
I got the headphone jack on eBay from here. It is totally overpriced but it's the only place I was able to find it.
I'm getting my replacement LCD and adhesive for it from Replace Base

FooFighter312 said:
Okay guys, here's the update with some good news and some bad news.
The replacement headphone jack arrived yesterday and the good news is that I replaced it and it seems to have fixed the problem! Yay!
But the bad news is that in the process I damaged the LCD screen so now I'm waiting on a replacement LCD. I guess I should've expected that because the screen and LCD itself are extremely sensitive and the damage is not even visible, but it's simply not working anymore.
So how do I know it actually works? Well since the phone used to be paired to my PC via bluetooth, whenever I turn on my PC a notification sounds on my phone if I want to pair or not.
Minor bad news - I tried to record the whole process as a tutorial for anyone who'll try to fix this themselves but my camera's battery died halfway and I lost everything I recorded.
Here are the 2 teardown videos I used for guidance: First and Second. I highly recommend you watch them entirely before attempting anything.
I got the headphone jack on eBay from here. It is totally overpriced but it's the only place I was able to find it.
I'm getting my replacement LCD and adhesive for it from Replace Base
Click to expand...
Click to collapse
Thanks for the updated! Are you sure problem is fixed by changing the headphone jack ? It's not temporary fixed like before ? BTW the link for eBay headphone jack is already sold out

Alaadragonfire said:
Thanks for the updated! Are you sure problem is fixed by changing the headphone jack ? It's not temporary fixed like before ? BTW the link for eBay headphone jack is already sold out
Click to expand...
Click to collapse
Well I'll know for sure as soon as I replace the LCD. I'm hoping it will arrive during the next week and then I'll update this thread again

Alaadragonfire said:
I have the exact struggle, restart will work for a while and then problem return, when I contacted google they offered a replacement but since I'm not in Canada at the moment, they will not be able to process my replacement request, but google representative told me that I can try and replace the mic with the charging port(as it all comes together) and it should fix the issue, but I also think that it might be the headphones jack, also this happened after I tried Android O beta.
Click to expand...
Click to collapse
I definitely recommend others try to get Google to replace it. I got mine from Swappa second hand and they still respected the warranty. Much easier and cheaper than replacing it yourself.

wow its nice to hear that it work, but some say that its the charging port board that has a problem(the location of the microphone). should i buy headphone jack replacement or charging port board?
yesterday i put i my pixel into freezer for 2 hour(i tried this because it help my previous phone which is nexus 5x come back to life for a while haha) and rebooted to safe mode and tried to record and microphone work, rebooted to normal and until now it still work, but im hoping that your replace method would be a permanent fix and i will do that too.
please update this thread again as soon as you replace your lcd
thank you

Another update. I got the replacement screen today but the problem hasn't been fixed. Well, partly it has been. The speaker now finally works when nothing is plugged in but the phone can't recognize any headphones. So, like Mattish13, if you can get it replaced by Google do so. Fixing things on my own is my hobby and was logical since I couldn't get mine replaced by Google, but this fix is not worth your time or money, trust me. I'm guessing the next thing to get replaced would be the daughterboard, maybe that would fix the problem finally, but in my opinion it's not worth it.
Ironic how so many problems with the headphone jack appeared for so many people and at the same time Google decided to ditch the jack for Pixel 2 :laugh:
Edit: just to be clear, since I already invested in a new screen and new jack, I will drop in another 25$ for the new daughterboard. If that doesn't fix it, nothing can

malstroms said:
wow its nice to hear that it work, but some say that its the charging port board that has a problem(the location of the microphone). should i buy headphone jack replacement or charging port board?
yesterday i put i my pixel into freezer for 2 hour(i tried this because it help my previous phone which is nexus 5x come back to life for a while haha) and rebooted to safe mode and tried to record and microphone work, rebooted to normal and until now it still work, but im hoping that your replace method would be a permanent fix and i will do that too.
please update this thread again as soon as you replace your lcd
thank you
Click to expand...
Click to collapse
As strange as it sounds the freezer trick works! I think the issue appears when the phone heats or it's heat related

FooFighter312 said:
Another update. I got the replacement screen today but the problem hasn't been fixed. Well, partly it has been. The speaker now finally works when nothing is plugged in but the phone can't recognize any headphones. So, like Mattish13, if you can get it replaced by Google do so. Fixing things on my own is my hobby and was logical since I couldn't get mine replaced by Google, but this fix is not worth your time or money, trust me. I'm guessing the next thing to get replaced would be the daughterboard, maybe that would fix the problem finally, but in my opinion it's not worth it.
Ironic how so many problems with the headphone jack appeared for so many people and at the same time Google decided to ditch the jack for Pixel 2 :laugh:
Edit: just to be clear, since I already invested in a new screen and new jack, I will drop in another 25$ for the new daughterboard. If that doesn't fix it, nothing can
Click to expand...
Click to collapse
Any updates ?

Alaadragonfire said:
Any updates ?
Click to expand...
Click to collapse
Yes, sorry for forgetting to post earlier. I changed the daughterboard and it appeared to be working perfectly. But about 30 minutes later the microphone again wasn't working and there was no audio. I was back at the beginning.
Then I did a factory reset and again it worked. But every time, after about 30 minutes it stops working. At this point I have no idea what the exact problem is.
I've definitely fixed it partly somehow because before I couldn't get the microphone and speaker to work at all. Now I can, but it fails after some time eventually. The headphones jack works normally until the failure happens.
I've tried the freezer trick after that and had no noticeable improvement. My theory now is that the problem probably was on the daughterboard but the replacement one I got (which is actually a refurbished part) might have had the same problem but not as serious as my original part.

FooFighter312 said:
Yes, sorry for forgetting to post earlier. I changed the daughterboard and it appeared to be working perfectly. But about 30 minutes later the microphone again wasn't working and there was no audio. I was back at the beginning.
Then I did a factory reset and again it worked. But every time, after about 30 minutes it stops working. At this point I have no idea what the exact problem is.
I've definitely fixed it partly somehow because before I couldn't get the microphone and speaker to work at all. Now I can, but it fails after some time eventually. The headphones jack works normally until the failure happens.
I've tried the freezer trick after that and had no noticeable improvement. My theory now is that the problem probably was on the daughterboard but the replacement one I got (which is actually a refurbished part) might have had the same problem but not as serious as my original part.
Click to expand...
Click to collapse
Thanks for the update, interesting... Maybe the daughterboard is faulty as well, but didn't Google response was that there is a crack line in the audio codec, as far as I know the audio codec is on the motherboard, I guess this problem won't be fixed after all, it is really annoying!! I wanted to get another pixel maybe XL this time, I found some offers with used ones, but now I am really afraid to buy one and this problem appears with the second phone.

Yes, found that response but unfortunately changing the motherboard is not possible because I couldn't find any place that sells them and I guess it's the same as getting a new phone in the end ?
I ended up getting a pixel XL but Google said this problem appears on devices manufacturered before March 2017,so I made sure when I was buying that I got a device manufactured after that and I did. So far so good ?

FooFighter312 said:
Yes, sorry for forgetting to post earlier. I changed the daughterboard and it appeared to be working perfectly. But about 30 minutes later the microphone again wasn't working and there was no audio. I was back at the beginning.
Then I did a factory reset and again it worked. But every time, after about 30 minutes it stops working. At this point I have no idea what the exact problem is.
I've definitely fixed it partly somehow because before I couldn't get the microphone and speaker to work at all. Now I can, but it fails after some time eventually. The headphones jack works normally until the failure happens.
I've tried the freezer trick after that and had no noticeable improvement. My theory now is that the problem probably was on the daughterboard but the replacement one I got (which is actually a refurbished part) might have had the same problem but not as serious as my original part.
Click to expand...
Click to collapse
I had this problem and Google said pixel has warranty till 2019 and sent me a new one... However they sent me the wrong color and I have no choice in the manner

knowitall72 said:
I had this problem and Google said pixel has warranty till 2019 and sent me a new one... However they sent me the wrong color and I have no choice in the manner
Click to expand...
Click to collapse
Do you mean your phone had warranty till 2019 or all pixel devices, because when I contacted Google the guy on the phone told me my phone has warranty till Jan 2018, which sucks in my case as I'm at the moment outside of Canada and won't be returning till summer 2018

Alaadragonfire said:
Do you mean your phone had warranty till 2019 or all pixel devices, because when I contacted Google the guy on the phone told me my phone has warranty till Jan 2018, which sucks in my case as I'm at the moment outside of Canada and won't be returning till summer 2018
Click to expand...
Click to collapse
I believe all pixel devices because I bought mine just after they came out in Australia... Phone screen broke and when I replaced it I had these problems... Told Google it was a hassle contacting my australian provider and would cost alot and they said it had warranty until '19 and that they would replace it here in the states free of charge... It may have been only till '18 but my first pixel was faulty as well and I had it exchanged out there n straya so maybe that's why it is until 2019