Since I'm apparently not allowed to post this kind of question in the CGM thread due to being a new user, here it goes.
CGM10, Verizon GS3. Latest nightly (although I've had this problem with every CGM since I switched over on the 26th.
If I call any number that has a phone menu, such as voicemail, or anything else that has a "press x to go to xxxxxxxx", it does not recognize that I'm putting in numbers. This means I can't delete voicemail, I can't navigate through other phone systems, etc.
Anyone have this issue, and more importantly, anyone have a fix?
I've tried other dialers such as Dialer One and ExDialer, but they only seem to serve as front-ends for dialing. Once I'm in the call it reverts to the broken JB/CGM one.
By "CGM10" do you mean "CM10" as in "CyanogenMod 10"?
I use the Official CyanogenMod Nightlies (right now I am on 9-02), and I tried using my voicemail. It worked fine when dialing stuff while in a call.
bon courage !
-------------------
Voyage Vietnam-Jonque Ginger Halong-Jonque Cai Be Princess
Yeah, CGM10/CM10. I've seen it listed both ways.
After doing about 4 or 5 factory resets, I've found that it starts happening after I go in to change my voicemail to include my password. But, even when I remove the , the phone functionality remains broken, and requires I reformat the phone to fix it.
Looks like I get to refromat the phone again. Wheeeee. I've wasted almost 5 or 6 hours fighting this stupid thing...but at least this time I know what not to do, but that's going to be a pain in the ass, and I'd like to know why it's happening and get it fixed, as I'm not a fan of losing functionality.
So, this is bit of a new issue, one I've not had before. I wish Hangouts/Messenger still had the Service Center ID in the settings in order to fix this, but, in the long/short run...
I unboxed my pixel and put my SIM in, started the phone. LTE/UMTS work perfect, locked right on, good signal/speeds, can place/receive calls, all is right in the world? I noticed after an hour I hadn't received any texts, and after feeling very unimportant, I sent a SMS to a friend, and got an immediate error. Out of curiosity, I went into the INFO settings (*#*#3646#*#*) and went into the SMSC settings. pressed refresh, which, populated an error. I manually typed mine, hit update, went back to hangouts, and voila!
The next day, I restarted the phone ( I like to do this often. I am also this user who actually turns their phone off from time to time ) and noticed upon restart, the problem resurfaced, like as if I never updated it to begin with.
Is this occurring with anyone else? I've yet to see a phone completely dump it. I'd prefer not to download another SMS application really, but, it's just inconvenient those few times I do restart it that I lose that SMSC number...
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
I'm having this same issue. I've contacted support about it, but haven't gotten a response yet (they said I would have an update yesterday).
If I manually put the SMSC in, and then Update, I can send texts briefly, but eventually I start getting an error 38 instead. A reboot and then manually entering the SMSC again allows me to send texts again.
vagosto said:
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
Click to expand...
Click to collapse
I'm curious if setting your mobile data to always-on would be a functional workaround to help until they can get this fixed for real. Have you tried that?
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!
First this is a rant, and I have seen multiple threads with some of the same problems.
1. Day one (right after unboxing) when I first powered on the device, I could not hear the other person on the phone. I tried calling multiple times, I even called on facebook messenger, they could hear me, but I could not hear them. The only way for me to get around this was to reboot my phone. This went away for a little bit, but has been happening again and again more frequently now.
2. BT will randomly switch from headset/stereo to phone speaker without any warning. Just a simple swap from talking to someone over BT and then thinking they hung up or disconnected, only finding out that it decided to swap from BT to phone. Incredibly annoying, and I have even lost some business calls from it.
3. Stock messaging app does not work. It wont send or receive messages. I have to use another 3rd party app to send and receive my text.
4. I am constantly getting notifications that there is a problem with getting my voicemails. Now I lose calls due to the BT failure, and now I do not get the voicemails when they try to all back.
5. Apps will not install. It will download them but it freezes at the install portion, I have tried clearing everything-cache and what not, and only way to get around this is to reboot the phone again. really annoying when I want to install an app, I have to reboot my phone. Although I have had the same problems with my Note 8, So it is most likely a google issue.
Any one have any ideas on these? I am going to try and talk with TMO but odds are they will tell me to do a system reset.
Thanks.
Have you tried reflashing stock and a factory reset?
I would also suggest the factory reset.
However, I have been having issues with the play store this evening installing apps just as you mentioned. Cleared the cache and rebooted, everything installed fine then.
Basically what happens is I get old texts from previous conversations as if they were new. They will come in randomly but tend to follow the sequence of the conversation, so it basically replays the conversation but slowly over the day. Seems to affect group chats more. It makes following conversations very hard since they are full of old texts that are not relevant but they show up as new. Also annoying to keep getting notifications when I'm actually waiting for a text only to see that it's an old text that I got days ago.
Current phone is Google Pixel 4A with CalyxOS, but I've also tried Graphene OS and had the same issue. I've tried the stock app as well as QKSMS. I did not get the issue with Signal (using as SMS client) but they dropped support for SMS, so this started back again as soon as I switched off Signal. I even tried putting the sim card in my old phone (stock android) and it's still doing it! This part is strange to me because when this problem first surfaced, doing this did fix the problem.
How do I make this stop or begin troubleshooting this? Nobody in my contacts is having this issue so trying to convince them to switch to another messaging system is kind of futile, this is my problem. I am starting to wonder if I should just get an iphone like everyone else because it just works, but I really hate the closed nature of apple ecosystem.
I was thinking of looking into how to do app development and modify an existing open source client so that it ignores texts that have a send date older than 24h, but before I do that, is there already a text client for Android available in the F droid store or as an APK that would have such a feature?
So this is not just group chats like I thought. Starting to get old texts I got from single conversations now. Even pictures get resent. These show up as new texts, though they still have the original send date. This will at least make it easier to filter these out.
Anyone have an ideas how to make this stop? Driving me insane. I really don't want to have to write my own app.
Anyone? This problem is driving me insane. It started happening with a vengeonce again. I am being bombarded by old texts that I already got days ago. It's just playing out the entire conversation over the course of a few days. Have to put the phone in airplane mode to make it stop otherwise the phone is just lit up non stop with old texts coming in.
At very least is there some kind of logging of sorts I can enable that would help me better troubleshoot this?
Inreally dont know but i Remember this happened to me sometime ,maybe Just try a factory reset or change rom , i dont know
I tried several roms, resets etc. While it was happening I even put the sim card in another phone and it started doing it on that phone too. It's also not a carrier issue since I'm the only person having this issue. I've also tried all sorts of text apps. The only one it didn't do it with was Signal but they dropped SMS support, which really sucks.