I bought two Charges last week, one for me and one for the wife. Both of us have been having similar issues with music and/or ringtones randomly not playing on our phones. My wife has missed several calls because the ringtone that she downloaded from Zedge mysteriously stopped working, so the phone acted as if it were on silent mode. I noticed several instances where I can't listen to music on my phone due to a "Error playing the requested track" error within the Google Music app. At first, I thought my problem was due to the fact that I was trying to stream music that I've uploaded, but I was given the same error when I attempted to listen to music stored directly on the SD card.
Thinking that my problem was due to some weird issue with the Google Music app, I tried to play the music on my SD card from the built-in Music Player app and I was quickly prompted with an unsupported file type error. Rebooting both our phones seems to fix the problem, but I've had to do this at least two to three times on my phone, and once on my wife's. It seems that the problem always comes creeping back without warning.
Neither of our phones are rooted, and nothing else has been done to the phone that I can think of that would cause this issue.
In short, music/ringtones/etc. will randomly stop playing regardless of their source (SD card, downloaded, stream). Since the problem is on both of our phones, I'm guessing that this is a common issue on all Droid Charges.
Has anybody else experienced this issue? What are your recommendations on fixing it? Should I just take the phones back to Best Buy and get replacements?
=Edit=
Okay...something is definitely up. I just went to watch a video on the YouTube app, and saw no video. I tried other videos and got the same result. Sure enough, I tried to listen to some music and was given the above mentioned error. What the hell?
I would take them back to Best Buy. Ive never heard of this problem. And if youtube is not playing then there seems to be and underlying problem.
I was having this same problem every so often, typically after having the phone on for a few days without turning it off. I am rooted an running a custom ROM so I thought it might have something to do with that, but obviously that is not the case. I turn my phone off whenever I charge it at night and have not had the problem since doing that. Long story short, I would return the phone if you can, but just turning the phone off and then back on (not rebooting) has fixed the problem for me every time.
Try uninstalling the official twitter app if you have it, reboot, and try again. That usually solves that.
Yankees368 said:
Try uninstalling the official twitter app if you have it, reboot, and try again. That usually solves that.
Click to expand...
Click to collapse
Where did you hear about this?
Karma Elite said:
Where did you hear about this?
Click to expand...
Click to collapse
Did that solve the issue for you?
http://www.google.com/support/forum/p/youtube/thread?tid=3ef52f711434ba6d&hl=en
Every time I receive a call my Speakerphone turns on by itself. Same when I make a call, it says that Speakerphone is on but it is not and work normally through the ear speaker.
Did clear data on Google dialer and same thing but at least the Speakerphone icon shows me that it is on when before it didn't.
I'm rooted but still everything else is stock. I had some apps disabled but re enabled them and updated and still the same problem.
On my first attempt to root I managed to stop it from booting the OS so I flashed the factory image and on my second attempt to root everything went fine. So maybe something went wrong there.
Does anyone have any idea beside factory reset or using the flash the factory image?
nitramus said:
Every time I receive a call my Speakerphone turns on by itself. Same when I make a call, it says that Speakerphone is on but it is not and work normally through the ear speaker.
Did clear data on Google dialer and same thing but at least the Speakerphone icon shows me that it is on when before it didn't.
I'm rooted but still everything else is stock. I had some apps disabled but re enabled them and updated and still the same problem.
On my first attempt to root I managed to stop it from booting the OS so I flashed the factory image and on my second attempt to root everything went fine. So maybe something went wrong there.
Does anyone have any idea beside factory reset or using the flash the factory image?
Click to expand...
Click to collapse
try answering or dialing a call with headset(handsfree) plugged in!
Lets see what it does!
When I plug in something like a wired headset the Speakerphone doesn't auto on. But it does the same thing again when I unplug it.
Sent from my Nexus 5 using xda app-developers app
Well I ended up doing a factory reset and it all works fine now. I will personalize my N5 again and monitor it.If it comes back I will let you know what I did to get that problem.
I found what is causing the problem.
It is the app Elixir 2. It must have a but somewhere because of Kitkat.
I absolutely love this app because of its versatility so I already contacted the developer.
Hope he gets back to me soon.
My Pixel suddenly stopped being able to make and receive phone calls a few days ago. The Phone app is extremely sluggish trying to make a call, will usually finally "connect" and look like the call is open, but I hear nothing but silence on the other side, and the other person can't hear me. It's slow to try and hang up, too. I see calls coming in, and can try and answer, but with the same result. Missed calls are registered. Voicemail also does not work. I can see there is a message, but can't play it.
Running 8.1 with February 5 security patch. Carrier is Verizon. I've gone in the store, and they switched out the SIM card. I've also tried a hard factory reset, all with no difference to the problem. The phone is over a year old, so I think a replacement is not possible...
If anyone can help me or has any ideas, I would greatly appreciate it! Thanks!
It's a hardware problem, Google is aware of the problem, they should replace your device. Contact Google, even if you are out of warranty they will replace the device for you!
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPOPRT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH, is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issue. I really DOUBT its a 3rd party app.
Thanks for your replies. I've contacted Google, and they didn't seem to think it was justification for replacing the phone out of warranty. They said I could either take it to a repair place to fix it or trade it in for the new Pixel 2 and get some money for it.
The workaround for answering calls works to connect the call and start the timer, but I still can't hear the caller and they can't hear me...
I still after much troubleshooting have found no way in which calls are functional. In addition to the attempts made above, I've since tried to uninstall and reinstall the phone app, and also to install a different phone app. No change to the problem. Even more curious, the problem still persists in Safe Mode.
If anyone has any more ideas, I'm all ears! Thanks!
So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou
It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.
Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon
I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.
The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.
Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.
Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!
Hi,
I've got a problem. Suddenly a couple of apps won't recognize any sound when using the microphone, e.g. WhatsApp. When I want to record a WhatsApp voice message the app does not record any sound. The sent message is completely silent. Strangely it does work when the screen recorder is running, presumably because the microphone is activated by the recorder. Has anybody an idea why that could happen? It worked till a couple of days ago.
I am on the current Android 12 Version on the latest patch (01.05.).
Thanks!
This is a guess. WhatsApp may have lost the "Allow Use Microphone" permission.
Newer versions of Android can revoke permissions if it wants.
Usually in Settings there is an App Permissions option. Or, long-click the icon and press the "I" for information. You may be able to view/set permissions from there.
This is only a guess - where I would look first.
Sorry, I forgot to mention, that it does have the permission to use the microphone.
WhatsApp Calls, Video recording, ... do work. The problem only occures with voice messages.
As I said, WhatsApp isn't the only App that does not work, there are a couple more, that all the sudden so not recognize the microphone anymore.
I had similar problem with my zflip 3 . I sugest you to make a diagnostic with the samsung members aplication. My secundary microphone was broken , so I had to replace the charging port card (sub pba) .
I don't have a solution but this exact thing, has just happened to me today too! You are the first person I've found with the same problem! Have you heard anything yet? Or had any luck? I've gone as far as to do a full factory reset and still nothing.
Were you able to fix it?
I'm also on Android 12.
Rayrsn said:
Were you able to fix it?
I'm also on Android 12.
Click to expand...
Click to collapse
Nope still broken. Samsung have offered to look at it under warranty but would need it for 2 weeks so I'm waiting until that's viable!