At some point recently, my WM6 phone stopped playing its ringtone (normal WM6 ringtone sound, haven't changed it). If I go into Settings->Sounds & Notifications and check the Phone: Incoming Call sound, it is correct and plays. If I check in Settings->Phone and check the sound, it is correct and plays. But it doesn't play when I actually get a call. Changing the ring tone to something else doesn't help either. Anyone have any idea how this can be fixed, other than a hard reset (soft reset doesn't work)?
hi
this happened to me wayyyy back when i still had my xda2. although i'm pretty sure wm se2003 and wm2006 are completely different =)...what happened was i installed an app that's causing the conflict. i forgot which app was causing this problem but after i uninstalled it, did a soft reset and the ringtones came back. for your case, you might want to check if you installed recent apps. if yes, perhaps one of them is causing this. i think it's mostly the old applications that affect the system. example, installing an app made for se2003 devices.
or, is your bluetooth on? it's possible that all sound is being rerouted to the headset. i think it's a bug for a lot of devices.
hope that helps.
cheers
Robson said:
what happened was i installed an app that's causing the conflict. i forgot which app was causing this problem but after i uninstalled it, did a soft reset and the ringtones came back.
Click to expand...
Click to collapse
Thanks for the reply.
Fring is the application in this instance (I wanted to use Skype over my 3G connection, but the Skype client itself is a no-go, unless you go back to an old version that only outputs via the speakerphone). As far as I can tell this happened after installing it.
Problem is, after uninstalling Fring and doing a soft reset, the problem remains. I figured maybe the issue is a registry setting or the like, but have no idea where. So I turn to all you knowledgeable people in the hope that the answer isn't "do a hard reset." :-|
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
Okay, this problem has been bugging me for a while. The ringtones that came with my SGS4G play when I select them, but my others (ringtones, mp3's, stuff created in RingDroid) will not play. This also affects music playback. I get an error that the file is corrupted.
Now the interesting part: if I reset my phone, I can play the sounds again, no problem. After a few days though, it starts happening again. As for the Youtube videos, they play fine, then after a couple of days they stop playing. If I reset the phone, they play again.
My phone is rooted.
Firmware: 2.2.1
Kernel: 2.6.32.9
Stock Froyo Build
I have CacheMate and Super Manager cleaning out my caches whenever they can.
I checked all possible sound stuff (Airplane Mode, no ringtones on silent, etc..) and still have the problem.
This problem started before I ever rooted my phone. Any help you guys could give would be appreciated. Thanks.
You said it is affecting music playback as well have you tried a different SD card? I had one go bad on me and I was having similar issues before it completely died. The Youtube videos however are playing from the internet right?
Nilmandir said:
Okay, this problem has been bugging me for a while. The ringtones that came with my SGS4G play when I select them, but my others (ringtones, mp3's, stuff created in RingDroid) will not play. This also affects music playback. I get an error that the file is corrupted.
Now the interesting part: if I reset my phone, I can play the sounds again, no problem. After a few days though, it starts happening again. As for the Youtube videos, they play fine, then after a couple of days they stop playing. If I reset the phone, they play again.
My phone is rooted.
Firmware: 2.2.1
Kernel: 2.6.32.9
Stock Froyo Build
I have CacheMate and Super Manager cleaning out my caches whenever they can.
I checked all possible sound stuff (Airplane Mode, no ringtones on silent, etc..) and still have the problem.
This problem started before I ever rooted my phone. Any help you guys could give would be appreciated. Thanks.
Click to expand...
Click to collapse
This is intriguing.... you can either:
1) Since your rooted, you can get CWM and install a custom rom. Might fix your problem since it's most likely a software problem i think.
2) Since your still stock and just rooted, and also it started before you were rooted, try sending it in to tmobile.
I suggest try #2 first and if they don't do anything about, try #1.
Sent from my SGH-T959V using XDA Premium App
Thanks guys. I'll try something and post back.
Hi all,
First excuse me if this is not the good forum for this thread, I'm new to this website.
I have a big problem with my Samsung Galaxy Note 2.
It doesn't play any video or music. Not only in a specific app but in every app I tried.
I tried the youtube app, the stock music app, shuttle music player which I usually use, but it also doesn't work when I go to youtube, dailymotion or any video site with the chrome browser. Videos in my facebook news feed won't play too.
When I try to watch a video or listen to music or simply launch an app like youtube for example, the phone becomes so slow that I must close the app. If I manage to click on a video, it just won't start. Generaly the app crash or the phone shut down or restart.
With the vlc app I can see the video but there is no sound.
It really starts to piss me off, I don't understand what's the problem.
Maybe it a software problem, I thought I could do a hard reset.
But it could also be a hardware problem, specifically something in relation with the speaker or the sound system, because yesterday my phone made strange noises and three days ago it fell on the ground.
Any help is welcome. Thank you for everything in advance.
Hi!
The easiest way to solve the following:
1. hard reset.
2. It did not help, then reflash the firmware on the stock, or better service firmware.
3. It did not help, then contact the service, as it is likely unfortunately hard problem.
Sorry for my english, good luck!
Hello, thanks for your help.
I reset the phone and the problem is still here.
But I noticed something interesting.
When I reboot the phone, it works for a while before the problem come back.
But maybe it's just a coincidence, because this morning the speaker made strange noises right before the problem came back. So I'm more and more covinced that it's a hardware issue.
So I think i will take the phone to a repair storé if thé problem doesn't go away by itself.
It's my pleasure.
But if you reflash the device previously, you would advise to try to flash ... Although, if you can carry in service, it is better there.
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!