After installing the July Security update our pixels have stopped recording audio. Google now, calls, videos, etc. After uninstalling an app or two it works again, then later it's gone again. We have tried factory resets which work for a while. Our family has 3 pixels and we can't find the common denominator.
Any tips?
Joshuaboyzn said:
After installing the July Security update our pixels have stopped recording audio. Google now, calls, videos, etc. After uninstalling an app or two it works again, then later it's gone again. We have tried factory resets which work for a while. Our family has 3 pixels and we can't find the common denominator.
Any tips?
Click to expand...
Click to collapse
Did you solve the issue I have the same issue too.
Not really. Ended up getting replacements through Verizon.
Related
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.
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.
Just yesterday my mic has stopped working. When taking videos earlier in the day it seemed to be working fine then maybe a few minutes later nothing. I have taken phone calls since and those are fine, but not sure what I need to do. I've done a hard reset, but haven't wiped the device yet. Can't tell if it's hardware or software. I'm on Android 11 with latest security patch. Any help would be appreciated.
Hello all
I have the (e)xperience, that I always need to restard the phone, before the Netflix app starts without failure. Anyone else this behavior?
BR
Sopur
Sopur said:
Hello all
I have the (e)xperience, that I always need to restard the phone, before the Netflix app starts without failure. Anyone else this behavior?
BR
Sopur
Click to expand...
Click to collapse
No problem with Netflix on my phone.
Delete data and cache and try again.
I'm facing the same issue. Haven't found what's causing it or any workaround to avoid restarting the phone. Deleting data & cache haven't helped. Even reinstalled the app.
I have the same issue not only with Netflix but also with Disney Plus. I think something is messed up with how the phone manages DRM.
I have the exact same issue, and it concerns Netflix, Disney+ and HBO.
same problem here also with p.v and d+, only restart fix the problem temporarily, i noticed also that the cromecast works , so its a minor problem for me because rarely i watch netflix on phone, i hope sony fix this with the next update, its absurde that the app come preinstalled in the phone and works bad ?
Just found the same issue on the first week I was using this phone on early October. I told with the Sony CS and reported this bug to them but they didn't think it's a bug as they told me not so many users reported to them. They won't try to fix this problem....
I had this with the old firmware, with the security patches of August. With the latest firmware, patches of November, I don't have it.
Same annoying problem here with Netflix and Prime Video, even after the firmware update including December patch.
Same problem here. I wasn't even aware of it until reading this thread as I always use a Chromecast.
Same problem here. First time Netflix after restart no problems. After having used the phone for a while and going back to Netflix, videos refuse to start. Red circle keeps spinning, eventually resulting in Netflix error 5.7.
Only a phone restart will fix this. Very annoying.
Any solutions?
I'm having this issue with Netflix as well. Just got the phone, it's on the latest software version. I haven't tried Prime video yet. Not a huge deal, since I only watch videos on my phone when I travel, and well...yeah, that won't be happening for a while. Agree it needs to be fixed.
Dear all - so I am not alone with this problem. (I didn't receive any updates on that threat). Especially, as it is a preinstalled app, Sony should get this work. How can we contact them?
KR
Sopur
It really is pretty poor having a pre instilled app not working properly.
It looks like I no longer have the issue with Prime, only with Netflix. So it could be an issue with the app itself. Has anyone tried to contact Netlfix support?
For me this is solved since my Xperia 5ii was updated to Android 11.
For me, too, with the update, it is gone!