Dialer not working on calls with automated systems - OnePlus 7 Pro Questions & Answers

I have OxygenOS 10.3 installed on my OnePlus 7 Pro. My carrier is TMobile. When I'm on a call with an automated system, where they prompt you to press a number on the dialer keypad to proceed to some department, it doesn't respond when I push a number. This has happened to 2 separate companies. Is this a bug with OxygenOS? I haven't had much luck googling to see if others have this issue.
I tried clearing cache in the Phone app, I also tried installing the patched Google Dialer (and setting it as the default) but that didn't change the behavior.
Any help is greatly appreciated.

Related

[Q] SMS Issues

Hey guys,
I just got my OPO today and have been loving every bit of it, but it seems that my SMS isn't working correctly. I checked the APN settings multiple times and even tried some of the preset ones with no luck. My issue is that I can both receive SMS messages as well as send and receive MMS messages, but when it comes to sending an SMS, I get a "Message note sent. Touch to retry" message. I've tried both the default app AND Google Hangouts with no luck from either. It's not a huge issue because I use mostly group chats and my gf can use hangouts, but it's still incredibly frustrating. Do you guys have any hints or tricks I should try out? I seriously love this device, but I am going crazy over the SMS issue.
I'm running the stock CM11S rooted with TWRP 64GB model on AT&T. Mobile data, LTE, everything else works. Just not actually sending SMS. I thank you for the responses ahead of time.
Hey @Bliznade.. .i see you posted about this sms issue. I am also having exact same issue now with my oneplus. Did you manage to find a solution of your issue? If yes, then can you share it with me? It is driving me crazy.
OR if anyone else can help me here?
Guys, basically you have to get the apn that is used by AT&T. Idk if you already have that apn, but the preset ones are made for the T-Mobile bands not really AT&T as I know it.
Parvinder25 said:
Hey @Bliznade.. .i see you posted about this sms issue. I am also having exact same issue now with my oneplus. Did you manage to find a solution of your issue? If yes, then can you share it with me? It is driving me crazy.
OR if anyone else can help me here?
Click to expand...
Click to collapse
Yes, I was! It was actually Google Voice setting itself up wrong or something and after I factory reset my SMS/MMS was working fine. I turned off Google's auto-app-restore and installed only the apps I needed and one at a time, trying SMS inbetween, since I knew it HAD to be an app if it worked after a factory reset but didn't after setting up my phone. I'd say if you have Google Voice to uninstall it completely. Some setting in there messed up my phone. If you don't have Voice installed, honestly the best thing to do is factory reset and makes sure SMS is working, then install each app one at a time. I know it sounds like a lot but that's what worked for me.
If that doesn't work, this is what OnePlus's customer service had to say. It was seriously a lot of back and forth, and they were incredibly helpful, even if it didn't fix my issue, it might fix yours, so I'll post out conversation below:
Email with R (OnePlus) said:
Jacob K
Jul 20 09:34
I got my device today, the 64GB sandstone black, and put in my AT&T sim card. The phone worked as usual-or so I thought. My data works. 4g LTE on the wireless network, group MMS works, and I even receive SMS fine. But I'm not able to send out any SMS for some reason. I get left with a "Message not sent" notification. I tried this first with the stock app then tried Hangouts and neither worked. I checked my APN and everything seems to be correct. I'm just at a loss, as it's odd that I can receive both SMS and MMS and even send MMS but I can't send out SMS. Is there something I can do to resolve this?
R (OnePlus)
Jul 22 13:27
Hi Jacob,
Let's try a few things to help you solve your SMS problem.
First, turn off your OnePlus One, carefully remove the SIM tray, and then power on your OnePlus One. Let it finish booting up. Obviously it will say there is no SIM inserted, cause there isn't!
Next, turn off your OnePlus One again. Carefully put the SIM tray/card back in the same way you took it out and power on again. Give your phone a few minutes to register on the network and get settled. Now, try to send an SMS, see if it works.
If we are back to square one, I'm going to have to gather a bit more info. As you probably already know, this problem is typically APN related. Are you using the PTA APN on At&t?
Would you mind downloading an SMS app called Textra (free) to see if you can send an SMS using this app please? Let me know if any of this stuff works, or not. Thanks.
Jacob K
Jul 22
to OnePlus
Alright, I tried all of the steps you gave me and it didn't work, so I tried again waiting longer in between each step and no luck. I also tried Textra and upon hitting the send button got an immediate notification that the message failed. I realize this seems to be a very specific problem because I've searched all over the internet and I've come up with no solutions. I posted in multiple forums with just one reply from someone else with the same issue. But since putting the ticket in I've also tried inputting the correct AT&T SMSC in all 4 formats to no avail. Every time I press update and re-enter it goes back to the old, which is in fact one of the correct SMSC's for AT&T (the one in quotes) with a ,145 tailing it (not sure what that's for). But any information you need I'll be glad to provide, and I greatly appreciate your response. I've been living off of Facebook messages and group chats the last few days, haha.
R (OnePlus)
Jul 22 14:46
Hey Jacob,
Cool, thanks for enduring a little troubleshooting and glad you understand the language of tech. Just to remove another obvious layer of doubt, please make sure you have updated to the latest version of CM via OTA. The fact that you can receive SMS messages makes this an interesting puzzle to solve.
For our next attempt, we will try something a little more drastic before I ultimately suggest a factory reset, but lets put that on the back burner for now.
Go to settings/apps and then swipe right 2 times to reach the 'All' category
For each of these apps: Phone/Messaging Storage , Messaging , Hangouts , and com.android.smspush
Perform this process: Force stop, Clear cache, Clear data
Do a restart when you are done and fire off an SMS when you are rebooted to a stable state. Any luck?
Jacob K
Jul 22
to OnePlus
Alright, no luck with that either, so I just sucked it up and did a factory reset. I tried sending an SMS immediately after and it worked, so I thought I was good. But then after I allowed Google to install all of my old apps, I tried it again and no luck. But I did notice when Google Voice installed, CM asked me if I wanted to use Voice+ (or something along those lines) and I said yes, chose my Gmail and allowed it to access my G+ info, but after that it asked me which email to use again and wouldn't go away until I clicked out of it. Then I had to swipe the notification away, so I figured Voice might be the culprit, uninstalled and voila, working SMS.
So maybe something in the Voice settings was messing things up, or maybe the CM Voice+ thing messed it up since it worked fine on my old phone. Not sure, but I'm happy to have fixed it. Everything works great now! And even though we weren't able to fix the problem through the troubleshooting steps you provided, I realize this was a difficult and very specific and local issue.
[insert nerdy thank you note here]
Click to expand...
Click to collapse
Bliznade said:
Yes, I was! It was actually Google Voice setting itself up wrong or something and after I factory reset my SMS/MMS was working fine. I turned off Google's auto-app-restore and installed only the apps I needed and one at a time, trying SMS inbetween, since I knew it HAD to be an app if it worked after a factory reset but didn't after setting up my phone. I'd say if you have Google Voice to uninstall it completely. Some setting in there messed up my phone. If you don't have Voice installed, honestly the best thing to do is factory reset and makes sure SMS is working, then install each app one at a time. I know it sounds like a lot but that's what worked for me.
If that doesn't work, this is what OnePlus's customer service had to say. It was seriously a lot of back and forth, and they were incredibly helpful, even if it didn't fix my issue, it might fix yours, so I'll post out conversation below:
Click to expand...
Click to collapse
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Parvinder25 said:
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks.. Didn't find that setting but uninstall works perfect.
Sent from my A0001 using XDA Free mobile app
Parvinder25 said:
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Parvinder25: Could you perhaps elaborate on exactly where these "connection settings" are located? I could not find them anywhere within the Google Voice app. I'd like to keep using GV for its visual voicemail feature, however it seems to completely disable my ability to send MMS messages (although they do send after GV is uninstalled). I've located a toggle to receive text messages either within google or through the messaging app, however the messaging app was already selected. That would be the only toggle I could locate within GV that remotely relates to messaging. Thanks in advance.
Hello Parvinder,
It was glad that you have resolved this issue, i am also facing similar issue with my One Plus One mobile - MESSAGING. I am using AT&T network. I couldn't fine Google Voice+ in the apps or settings. I can just see Google Voice but, i am not able to find which setting needs to be disabled or Uninstalled? Could you please provide exact navigation for the same would be great help for me and other users on this blog.
Appreciate your help.
Thanks,
Venki

Google Voice Calling

I use Google Voice as my main phone number and I never had a problem just installing the Google app and having my calls routed through it, but on this phone a get a "Call Not Sent" error. I searched and it seems this is an issue with other Huawei phones, but didn't find any solution. Any ideas?
Can anyone test to confirm it's an issue? Would flashing a Gapps package help?
maybe, cuz flashing gapps package would make them system apps. just make sure u have enough space left on your system partition...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
I deleted some system apps and installed open gapps mini. No luck, still getting the same error. Is it possible to replace the phone apk (not dialer), or is that too tied to the hardware?
I've been using the phone for a couple days now, and I'd hate to give it for such a small (but fundamental) bug...
I found a solution: make Google voice a system app
adriangb said:
I found a solution: make Google voice a system app
Click to expand...
Click to collapse
please explain
i still can't figure it out
Actually it may have been a fluke... I placed one single call and confirmed with the other party it was my Google voice number. Now it isn't working again.
I think I may have fixed it. I copied in some telecom files from AOSP. So far I'm like 5 calls and 2 reboots in and it's holding. I'm going to try to update to the new L-29 OTA, root and then follow the same process. If it works, I'll post the ROM. If it's like what I'm on right now, it's a very nice mix of EMUI and AOSP since most of the Huawei stuff is gone, except some of the handy features, and all the Google stuff is loaded and working.
maybe you could also include a howto, which files to add where so that others may cook up their own emui/aosp mix
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
To be honest, I'm really not 100% sure, I kind of brute forced through the testing. What I do know: replacing a couple telecom framework and binaries from the 6P factory image (figured might as well use this), and installing Google voice as a system app, I have gotten it to work every time (for me) as long as it is set to prompt for every call. If set to "use Google voice for all calls", it breaks. My guess is it's a timing issue (emui telecom not giving Google voice the time it needs to make the connection).
I'll attach the ZIP file with all of the telecom components I used (NOTE THAT USING PRIV-APP COMPONENTS -IE TELECOM.APK, SEEMS TO CAUSE A BOOTLOOP).
Also, here is a link to my TWRP backup of my current system. It is 152 with a full Gapps package, Google voice as a system app and the telecom components Frankensteined in. Hopefully it will work on your devices, but just in case it bricks it I won't be giving out my address, least I get picketed
https://drive.google.com/a/adriangb.com/file/d/0B8hgJSh5NMsLVGpicmEwdWpDb00/view?usp=docslist_api
Still no real solution. The ask every time trick works without having to do anything with making Google Voice a system app and it only works 90% of the time.
Can anyone else confirm this issue? I'm discussing it with the vendor I purchased from, they're claiming it works perfectly
adriangb said:
I use Google Voice as my main phone number and I never had a problem just installing the Google app and having my calls routed through it, but on this phone a get a "Call Not Sent" error. I searched and it seems this is an issue with other Huawei phones, but didn't find any solution. Any ideas?
Click to expand...
Click to collapse
This is an old post with little activity, and yet I have this same problem. I have tried all the app setting and permissions, the battery setting etc, but the Mate 8 seems incompatible with Google Voice. The app install fine, sets up normally, and incoming calls to my Google Voice number work. It is just dialing out. All dials get the message "call not sent" and the dialer screen returns to befor the call was placed. The log also does not show an attempted call. I have tried alternative dialers from the play store, but none work. Has anyone solved this, or are there just very few people using Google Voice with this particular phone.
I've been having this same issue and have had the best results just setting it to "ask every time", no other tricks needed.
joburgslim said:
This is an old post with little activity, and yet I have this same problem. I have tried all the app setting and permissions, the battery setting etc, but the Mate 8 seems incompatible with Google Voice. The app install fine, sets up normally, and incoming calls to my Google Voice number work. It is just dialing out. All dials get the message "call not sent" and the dialer screen returns to befor the call was placed. The log also does not show an attempted call. I have tried alternative dialers from the play store, but none work. Has anyone solved this, or are there just very few people using Google Voice with this particular phone.
Click to expand...
Click to collapse
This is broken on the mate 9 as well
Anything on this? i just got a mate 8 and am having the same damned issue.

Unkown Caller - But is in contacts

I am on the 3 network here in the UK ,I have owned a Oneplus 1 2 and 3 and had no problems. However on my OnePlus 6 when I receive a call from someone in my Google contacts I get the message unknown caller
Oxygen 5.1.11
patch July 2018
Build ONEPLUS A6003_22_180810
Have you checked the settings in the contact manager? Check if "contacts to display" is set to all
Hi thanks, just tried that, and even switched it off and on again but it's still the same.
You're going to have file a feedback/bug report with OP, I've seen many postings with the same exact problem. I think it goes back to all the problems with the dialer itself.
You could also download a different dialer and see if the problem persist. Keep in mind because of the way they've done the call settings the new dialer may not be able to see all the settings. Don't use Truecaller, that has its own issues and I'm not a fan of their what info they collect.
Make sure in settings under apps the permissions are all checked.

[Working] Google Call Screening on Android 10 Beta [WIP] Google Visual Voicemail

Call Screening is working on the OOS Android 10 Open Beta 1 with the following instructions (ignore the first 3 steps if you're already on Android 10 open beta and rooted):
Requirements:
Android 10 Open Beta 1 (prior to OB1, there’s an issue with the caller not being able to hear the Assistant voice properly)
Root is necessary to make Google Phone a system app and to make the required mods to the XML file
Either the Pix3lify Magisk module or the Google Dialer Framework module (much lighter) to install the Google Phone app from the Play Store (might have to clear Play Store data/cache), or a patched Google Phone APK
App Systemizer and Busybox Magisk modules and Terminal Emulator
Preferences Manager Attached Google Call Screening Magisk module (all credit to thehappydinoa, I just updated it for the Call Screening flags on the latest Google Phone app)
Instructions:
install the beta
fastboot flash the patch root boot image from here (fastboot flash boot magisk_patched.img)
install TWRP and re-install Magisk both from Magisk, reboot
install Busybox and App Systemizer in Magisk
install Google Phone app using one of the above methods, enable all permissions and set as default Phone app, disable OOS Phone app, Systemize using Terminal Emulator (type su, then systemize, then choose the Phone app and systemize it to /system/priv-app), reboot
in Preferences Manager, enable system apps, scroll down to Phone, go to dialer_phenotype_flags.xml, search for ‘screen’ and set all the call_screen and callscreen flags to true, and search for ‘speak’ and set all the speakeasy and speak_easy flags to true. Install Call Screening Magisk Module, reboot
It seems Google Visual Voicemail seems to work only on certain phones with certain carriers, but not on the GM1917 with T-Mobile. I’ve tried putting the GM1915 software on my GM1917 but still can’t get it to work. It seems to work with GM1915s that have been converted to international firmware and rooted when Google Phone is installed as a system app as above.
Finally!!! I thought I was alone! Hope to see where this goes I really miss Google visual voicemail
Doesn't the "pixelfy" magisk module warn about bootloops on oxygen OS? Otherwise, wow, you got the screening to work, awesome! Unfortunately, I have nothing to offer on why the volume would be too low.
Cm4nXD said:
Finally!!! I thought I was alone! Hope to see where this goes I really miss Google visual voicemail
Click to expand...
Click to collapse
You're not alone! I really want the Google visual voicemail and transcription. I feel like it's an issue with my phone/account because there was someone with a OnePlus 6T with a very similar mod that got it working on T-Mobile. I might just need to wipe and try again.
jetfire245 said:
Doesn't the "pixelfy" magisk module warn about bootloops on oxygen OS? Otherwise, wow, you got the screening to work, awesome! Unfortunately, I have nothing to offer on why the volume would be too low.
Click to expand...
Click to collapse
It does give that warning, but I've had no issues with it. I've been using it since this phone first got Magisk. YMMV, of course.
Attempted everything included in the tutorial but I used dialer framework. Sadly, I could not get anything to appear. What was used in the guide?
Edit: I noticed the modified xml is about 28kb. Before I replace the xml in my root, it's about 14kb. I'll replace the file, and restart, only to see, I have a 14kb file again. Is this the issue?
It worked for me. Google Visual Voicemail and Transcriptions! I got the Call Screen options but did not receive any calls to test out out. Here is the rub... Google Phone went to sleep last night with everything set. This morning it had reverted to the standard set of options. Visual Voicemail, (no Transcriptions), and no Call Screen.
ozfive said:
It worked for me. Google Visual Voicemail and Transcriptions! I got the Call Screen options but did not receive any calls to test out out. Here is the rub... Google Phone went to sleep last night with everything set. This morning it had reverted to the standard set of options. Visual Voicemail, (no Transcriptions), and no Call Screen.
Click to expand...
Click to collapse
I'm noticing a consistency on the app resetting itself.
I would love to see if there was a way to keep the OOS Native call recording and get this as well...... any ideas?
jetfire245 said:
I'm noticing a consistency on the app resetting itself.
Click to expand...
Click to collapse
Can't seem to get it to re-enable after this morning either.
It's very obvious we need dedicated development for this project to work. Perhaps making a bounty for the successful and repeatable modification to get call screening and maybe voicemail.
We can just make a Tasker profile guys. I made one back in the day to constantly keep material design 2 enabled. I'm working on one rn that will Auto enable dark mode for the Google apps at sundown and whatever other phenotypes or bugle changes i need to make. Including VVM and CS
If you ever managed to solve problems , please update the post. Somehow , I did the exact same stuff before I saw your post and have exact same problems , low call screen volume , Voicemail can't activate
So I have had success using Preference Manger from the Google Play Store to kick in transcription visual voicemail. The settings stuck overnight too! I can't get Call Screen working yet though.
In Preference Manger I scrolled I enabled system apps from the three dot menu.
I scrolled down to phone (searching crashed the app)
I side scrolled to dialer.phenotype.xml
I searched "transcription" in the xml file
I turned every one from false to true
I force stopped the phone app
It works.
stealth658 said:
I'm trying to get Pixel Call Screening and Native Visual Voicemail working on my GM1917. I'm on T-Mobile US, and my phone is rooted with Magisk on OOS 9.5.8. From the settings I changed, it seems like the Call Screening should work in the US and Canada, and maybe elsewhere also. And it seems like VVM should work on Verizon, T-Mobile, AT&T, Tracfone, Freedom (CA), O2 (UK), and Swisscom.
So far, I've gotten the Voicemail tab to show up in the Google Phone app, but VVM won't activate on T-Mobile. And I've gotten Call Screening enabled with working transcription, but the Google Assistant voice is too quiet for the caller to hear. I'm hoping someone here can help me get these things working fully.
Requirements:
Root is necessary to make Google Phone a system app and to make the required mods to the XML file
Either the Pix3lify Magisk module, the Google Dialer Framework module (much lighter), or a modded Google Phone APK to install Google Phone
App Systemizer Magisk module
A root file explorer (I'm using Root Explorer)
Instructions:
Install Google Phone (I used Google Phone 34.0.253691707 from APKMirror)
Use App Systemizer Magisk module and Terminal Emulator to move Google Phone app to /system/priv-app/
Reboot Phone (You may also have to freeze/disable the OOS native phone app)
Force Stop Google Phone app
Using a root file explorer, unzip and copy attached dialer_phenotype_flags.xml to /data/data/com.google.android/dialer/shared_prefs/ (You may have to set permissions to 0660 rw-rw----).
Reboot your device (I've found that if you wait too long between Force Stopping, replacing the file, and rebooting, the Google Phone app will restart and override the changes)
When you re-open Google Phone app, you should have Call Screen in the menu ( It won't show up unless you enable the Microphone permission) and the Voicemail tab accessible (You may have to delete the Carrier VVM app for it to show up)
Screenshots of Call Screen and VVM tab on OP7Pro
Click to expand...
Click to collapse
What flags did you switch from false to true to enable call screen?
ozfive said:
What flags did you switch from false to true to enable call screen?
Click to expand...
Click to collapse
Anything with speakeasy, speak_easy, call_screen. For visual voicemail, change anything with vvm and voicemail (except a few flags that end in disable — they should be false). There are also a bunch of Duo related flags that I changed to integrate Duo more in the dialer.
I can give you a full list tonight when I’m home
A full list with be great!
I got Call Screen working and working transcriptions in visual voicemail as well.
The Call Screen assistant voice is too quiet to be useful at this time. Hopefully there will be a solution found for this too!
jetfire245 said:
Attempted everything included in the tutorial but I used dialer framework. Sadly, I could not get anything to appear. What was used in the guide?
Edit: I noticed the modified xml is about 28kb. Before I replace the xml in my root, it's about 14kb. I'll replace the file, and restart, only to see, I have a 14kb file again. Is this the issue?
Click to expand...
Click to collapse
ozfive said:
A full list with be great!
I got Call Screen working and working transcriptions in visual voicemail as well.
The Call Screen assistant voice is too quiet to be useful at this time. Hopefully there will be a solution found for this too!
Click to expand...
Click to collapse
Which carrier and phone model do you have?
I am using a t-mo converted to international
ozfive said:
I am using a t-mo converted to international
Click to expand...
Click to collapse
I'm not sure why my international on T-Mobile stays stuck on activating for VVM. Are you using Pix3lify or any other relevant mods?
I am using Google dialer framework vs pixelfy, maybe that is the issue?

Question Dialer issue since December update

Hi all, anybody else notices this?
Since the December 5 update I don't seem to be able to pick up when I'm called. There's no dialer / phone (image) popping up to pick up the phone. I have to call back people instead. Total bummer, very inconvenient.
Any suggestions other than installing another dialer of course (although, if you have a great tip...) appreciated!
Not having that issue
Wiped cache and data to be sure. But happened again
For me dialer is working fine but having issue in whatsapp call notification. Phone just rings and vibrates without any information. When whatsapp os opnened the it will show the call on top bar.
Update: my issue is resolved by installing a newer version which is not available in play store currently.

Categories

Resources