If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
Related
So I land in Orlando on vacation, get my rental car, and enter the hotel address into Maps ready to push the navigation button as soon as I'm out of the garage. I do this and gps can't get a fix. I start driving in a random direction assuming it'll get a fix soon. Long story short, it never does!
I've been using gps, maps, navigation all with no issues until now. Had my phone since mid July. Tried restarting, tried battery pull, of course gps on/off a million times. Downloaded a free gps test app - if I was reading it right it seemed to show about 8-12 satellites it was picking up but 0 fixes. It's like the gps hardware is working fine but it won't get a fix on my location.
I'm on stock ROM. Haven't done anything weird or installed any new apps other than a fee games.
Any suggestions? I was counting on having maps/navigation while on vacation.
hollywoodfrodo said:
So I land in Orlando on vacation, get my rental car, and enter the hotel address into Maps ready to push the navigation button as soon as I'm out of the garage. I do this and gps can't get a fix. I start driving in a random direction assuming it'll get a fix soon. Long story short, it never does!
I've been using gps, maps, navigation all with no issues until now. Had my phone since mid July. Tried restarting, tried battery pull, of course gps on/off a million times. Downloaded a free gps test app - if I was reading it right it seemed to show about 8-12 satellites it was picking up but 0 fixes. It's like the gps hardware is working fine but it won't get a fix on my location.
I'm on stock ROM. Haven't done anything weird or installed any new apps other than a fee games.
Any suggestions? I was counting on having maps/navigation while on vacation.
Click to expand...
Click to collapse
The only thing I can think of is reprovision/factory reset. *2767*3855#. You'll lose EVERYTHING on your phone though. Make a backup first. If that doesn't work I don't know of any other way to fix GPS.
It sounds like the GPS receiver is working if it shows satelites, it just needs to download the catalog. You might try going outside and running some GPS software for an hour and getting a good download. Or you should be able to download a program like GPSstatus. then go to menu, tools, manage a-gps. From there do a RESET, then a DOWNLOAD. Then go outside for a while and you should start seeing fixes on satellites.
I like worwig's suggestion. I'm not familiar with GPS fixes, so it's great if what he said will work. Reprovisioning tends to fix anything related to radio problems (if IMEI was never lost)
GPS Woes Continue
Zalithian said:
The only thing I can think of is reprovision/factory reset. *2767*3855#. You'll lose EVERYTHING on your phone though. Make a backup first. If that doesn't work I don't know of any other way to fix GPS.
Click to expand...
Click to collapse
Tried this. Problem still persists. Can't get lock in Maps unless I let it go for over a minute. If I use GPS Test or GPS Status, it IMMEDIATELY reports 27 satellites in view, but shows connected to 0 for a good 20~30 seconds, then slowly starts to connect to one at a time.
Again, fully stock, non-rooted, locked bootloader.
try this in the Market:
https://play.google.com/store/apps/details?id=com.androidlab.gpsfix&feature=search_result#?t=W10.
its been listed in other forums that it works, and as i haven't used it myself, will go by what others say that works.
if nothing else, its free
goldsmitht said:
try this in the Market:
https://play.google.com/store/apps/details?id=com.androidlab.gpsfix&feature=search_result#?t=W10.
its been listed in other forums that it works, and as i haven't used it myself, will go by what others say that works.
if nothing else, its free
Click to expand...
Click to collapse
This is the ONLY app I have not tried on the market and I finally got a working gps on my S3 with Synergy Rom & Unlocked bootloader (of course) ... So thank you for the mention of the app!
Thanks to everyone who's tried to help. I've tried everything here except for a factory reset which was my last resort. So far nothing has worked. The first time I did the GPS Test thing, it worked, but then 5 minutes later when I went to use maps, it wasn't working again. I tried the other app - GPSfix as well - nothing. Also spent an hour on the phone with a Verizon Tech trouble shooting - not that I thought they'd know more than I could find on my own here, but figured it was worth a try.
I'll be factory resetting in a week or so (don't wanna do it now cause I don't have time to reset up everything on my phone right now). When I do I'll report back. Also I did find over on droidforums that there are several people who've had this exact same issue with their S3 - GPS worked fine then suddenly didn't work at all. So it may be a bigger glitch that's triggered somehow in some phones. All I know is I need my gps working and reliable on my phone...
If anyone else has had this issue and figured it out, let us know. Otherwise, I'll report back after the factory reset...
GPS Issue
hollywoodfrodo said:
Thanks to everyone who's tried to help. I've tried everything here except for a factory reset which was my last resort. So far nothing has worked. The first time I did the GPS Test thing, it worked, but then 5 minutes later when I went to use maps, it wasn't working again. I tried the other app - GPSfix as well - nothing. Also spent an hour on the phone with a Verizon Tech trouble shooting - not that I thought they'd know more than I could find on my own here, but figured it was worth a try.
I'll be factory resetting in a week or so (don't wanna do it now cause I don't have time to reset up everything on my phone right now). When I do I'll report back. Also I did find over on droidforums that there are several people who've had this exact same issue with their S3 - GPS worked fine then suddenly didn't work at all. So it may be a bigger glitch that's triggered somehow in some phones. All I know is I need my gps working and reliable on my phone...
If anyone else has had this issue and figured it out, let us know. Otherwise, I'll report back after the factory reset...
Click to expand...
Click to collapse
Hollywood,
Just out of curiosity, were you ever running Synergy?
With my situation, it took three calls to VZW, and an hour-long phone call to Samsung (which resolved nothing) to get a new phone shipped to me. The only good thing that came from the Samsung phone call was that I used it as ammunition when calling VZW the last time ("Look, I was even on the phone with Samsung tech support for an hour today, and they couldn't help me."). The Samsung rep had never even heard of the term "GPS Lock" and didn't understand the concept. She was totally convinced that if the blue arrow came up in Google Maps, that my GPS was working as it should, despite the still-flashing GPS icon and the "Searching for GPS" message in the pull-down screen. Also, she didn't think it was a problem that my positional accuracy never got closer than 3,400 meters.
A complete factory reset didn't help me; I even used Odin to reload stock, non-rooted, locked bootloader OTA ROM with original kernels, recovery, radios, etc.
I also tried the re provisioning dialer code, which didn't help.
I tried the GPS Fix program, GPS Test, GPS Status, and everything else I thought looked promising. Nothing helped.
GPS Fix helped after initial lock, but only while it kept GPS control. Once it released "fix", Maps would go back to having the same problem getting a lock after a while.
Good luck!
Search for the agps patch. Any forum will work. It works on all android. I just flashed it and I'm running beans. It also works for like cm. I used the 3.1 cwm flashable patch. It locks gos on instantly.
Sent from my SCH-I535 using Tapatalk 2
GPS Issues
So now that I have my new SGS3 on the way (should be here in two days) my GPS starts working again out of the blue. No changes to my phone, no new apps. Too weird that after three weeks of it not working right, it suddenly works perfectly again.
At least the issue shouldn't repeat once the completely new phone arrives.
check this link out
http://forum.xda-developers.com/private.php?do=showpm&pmid=8541888
Ryezen said:
So now that I have my new SGS3 on the way (should be here in two days) my GPS starts working again out of the blue. No changes to my phone, no new apps. Too weird that after three weeks of it not working right, it suddenly works perfectly again.
At least the issue shouldn't repeat once the completely new phone arrives.
Click to expand...
Click to collapse
My phone is doing something very similar, it's finding various satellites and finding a fix on 3 of them. Although, in Google Maps and Navigation, it will stay stuck on searching for GPS. This phone has been great since day 1 including GPS, strange that it will stop working just like that. I tried clearing data for Maps, running other GPS utilities, and a factory reset to no avail.
Decided to phone Verizion, and they will send me another S3 (refurb).. Hoping the new one works as it should.
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Since I got my phone on release day and I haven't been able to use it to make calls in my 2012 mazdaspeed3. My other phones have worked fine so I thought I needed a software update on my radio. Well everything is up to date and that didn't fix it.
The problem is when I make or receive a phone call the Bluetooth will connect and disconnect every 5-10 seconds. This makes it impossible to talk on the phone.
So I have tried stock roms, sense based roms, and all the CM based roms and they all did the same thing. Yesterday I was trying to figure it out so I sat in my car in the garage and the phone was in a constant connect disconnect loop. During this time I was disabling apps and services hoping to stop it when all of a sudden I turned off WiFi and it stopped. I then called my wife and had a 10 min conversation with no problems. So I now run a tasker profile that when Bluetooth connects it turns off WiFi so I can make calls. The problem is I have a nexus 7 dash mounted and I use the WiFi hotspot to run apps.
So after all that, does this sound like a hardware issue or a software issue? Should I return my phone for an exchange? Thanks for the help
Sent from my HTC6525LVW using Tapatalk
smalltownbird said:
Since I got my phone on release day and I haven't been able to use it to make calls in my 2012 mazdaspeed3. My other phones have worked fine so I thought I needed a software update on my radio. Well everything is up to date and that didn't fix it.
The problem is when I make or receive a phone call the Bluetooth will connect and disconnect every 5-10 seconds. This makes it impossible to talk on the phone.
So I have tried stock roms, sense based roms, and all the CM based roms and they all did the same thing. Yesterday I was trying to figure it out so I sat in my car in the garage and the phone was in a constant connect disconnect loop. During this time I was disabling apps and services hoping to stop it when all of a sudden I turned off WiFi and it stopped. I then called my wife and had a 10 min conversation with no problems. So I now run a tasker profile that when Bluetooth connects it turns off WiFi so I can make calls. The problem is I have a nexus 7 dash mounted and I use the WiFi hotspot to run apps.
So after all that, does this sound like a hardware issue or a software issue? Should I return my phone for an exchange? Thanks for the help
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Borrow the ole ball and chain's phone and see if it acts the same way.
Tried it. It works fine in my car, she has an S4. My phone also does the same in her car...
Sent from my HTC6525LVW using Tapatalk
Sounds like u need to swap it out for a replacement. Never had an issue unless using custom kernals.
deeznuts said:
Sounds like u need to swap it out for a replacement.
Click to expand...
Click to collapse
^ ^ What he said^ ^
Weird...
My M8 should be here today and I have a 2010 Mazdaspeed3. I hope this isn't an issue with all of them. Although, my MS3 has a long history of it's bluetooth not getting along with HTC phones.
Did you have any issues?
Sent from my HTC6525LVW using Tapatalk
smalltownbird said:
Did you have any issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So far, no. It took me like 20 minutes to get the phone to pair but once that was done it hasn't disconnected at all. I have music constantly streaming through Bluetooth to the car and I've taken a couple calls with no issue.
having the same issue here. My vehicle is a 2013 Ford F150 with Sync.
Worked up until about a day ago .. Now i can't get stock or aosp roms to lock in bluetooth
jdebutts said:
having the same issue here. My vehicle is a 2013 Ford F150 with Sync.
Worked up until about a day ago .. Now i can't get stock or aosp roms to lock in bluetooth
Click to expand...
Click to collapse
Have you tried clearing data and cache in settings?
the Red Viper ROM
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
jonkunke said:
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
Click to expand...
Click to collapse
Sounds like the common theme may be root for whatever reason. I assume when you first had the phone and it worked that you were not rooted? Possible issue?
Sent from my SM-N900V using Tapatalk
jonkunke said:
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
Click to expand...
Click to collapse
you need to let HTC backup app take care of backing up your texts etc...what if you dropped the phone in the toilet tonight or got pushed into a pool?
this app is free...will backup your stuff daily or on demand and will restore email accounts/texts/desktop/apps/blinkfeed settings etc.
http://www.androidfilehost.com/?fid=23329332407589902
install that, backup to the cloud (uses Google drive) and then continue troubleshooting without fear of losing stuff.
Sent from my SM-T320 using Tapatalk
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse
LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.
since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.
I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.
toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...
I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?
I installed lineageos 16 without gapps and is working good for hours until installed gapps.
ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.