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." :-|
Well, I'm not sure what happened but my Phone, Contacts, and Calender are not opening at all. I have been trying to get the gps working reliably for a few days. Yesterday all day I could barley get my location but a couple of times. The phone restarted a couple of times when i would open and try to use Google maps. Also, all day the screen would go blank and would be totally unresponsive except for a soft reset.
Last night I installed this iphone ui here: http://forum.xda-developers.com/showthread.php?t=508429
(figures, i know) j/k-lol. No particular reason but, I don't think the program was the cause.
I tried it for a couple of hours then uninstalled it.
It wasn't till this morning when I woke up that my Today clock said "no service". Usually says "US Cellular". The Touch pro will light up for a call but I cannot answer. (talk button doesn't respond at all) I CAN connect to the internet so I have a data signal (EV on taskbar). GPS did not find any satellites but thats been a problem.
UM..
Touch pro (USCC)
wm 6.1 (stock)
Radio: 1.07.06F (stock)
Chi/Milw area
Haven't hard reset yet. Figured I'd check here first!
You have several underlying issues here. Doesn't sound like they will be resolved without a hard reset.
Well, at least the hard reset went good!
I'm just not sure why it started acting up! Guess I just wanted to see if I could find out what it was. I'm pretty baffled about what could have caused it.
Oh well.
and thanks!
Ugg!
Still can't get the GPS to work!! What is the trick with getting the GPS to work on these touch pro's??
Hello,
I habe a standard, unrooted S6, the only thing I've done is disable some of the Google apps and other apps that came with phone. I don't think this could cause the following issues?
I've noticed a rather annoying problem. Sometimes, and more often than not, when my phone screen is off and locked, I receive no notifications. Only when waking my phone does the notifications flood in. I've tried everything to fix, like the wifi sleep policy, cache clean, factory reset etc. Samsung support said they would repair the phone, but it feels like a software issue rather than a hardware one. I know I'm not alone with this issue, anyone have any advice?
Thanks for your help.
BryterMoon said:
Hello,
I habe a standard, unrooted S6, the only thing I've done is disable some of the Google apps and other apps that came with phone. I don't think this could cause the following issues?
I've noticed a rather annoying problem. Sometimes, and more often than not, when my phone screen is off and locked, I receive no notifications. Only when waking my phone does the notifications flood in. I've tried everything to fix, like the wifi sleep policy, cache clean, factory reset etc. Samsung support said they would repair the phone, but it feels like a software issue rather than a hardware one. I know I'm not alone with this issue, anyone have any advice?
Thanks for your help.
Click to expand...
Click to collapse
I am on T-mo and have the same problem.
Dont know what else to do myself.
We have been discussing this problem in this link if you are interested.
http://forum.xda-developers.com/tmo...otifications-wifi-t3095156/page2#post60632598
http://forum.xda-developers.com/galaxy-s6-edge/help/push-notifications-stop-screen-off-t3071248
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!