Obsolete
Status Update
Comments
f....@gmail.com <f....@gmail.com>
go...@gmail.com <go...@gmail.com> #2
I am having the same issue on 7 pro.
mr...@gmail.com <mr...@gmail.com> #3
Same issue when asked to select a prompt on 6a. I did manage to get it to work by long pressing the entry. It was the number 2.
jp...@gmail.com <jp...@gmail.com> #4
Same issue, pixel 6a. I was given the options of 1-3 for one phone call, but all 0-9 came up as invalid selections. Called my bank as well, and it wouldn't take my acct number after entering.
he...@gmail.com <he...@gmail.com> #5
I am also affected
I believe each key press registered twice. I tried to press 9, and the message said "99" is not a valid option.
I believe each key press registered twice. I tried to press 9, and the message said "99" is not a valid option.
he...@gmail.com <he...@gmail.com> #6
To add to my previous comment, it's a p6a.
ro...@fisher.net.nz <ro...@fisher.net.nz> #7
I have the same issue
jp...@gmail.com <jp...@gmail.com> #8
Same issue on a P7Pro
bl...@gmail.com <bl...@gmail.com> #9
Same issue (sort of) on Pixel 6. When checking voicemail the system doesn't recognize that I entered my pin. It's like I'm not entering keys when in fact I am.
mi...@gmail.com <mi...@gmail.com> #10
Same issue can't even put my voicemail password in!!!!
ad...@google.com <ad...@google.com> #11
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
ad...@google.com <ad...@google.com> #13
We have passed this to the development team and will update this issue with more information as it becomes available.
he...@gmail.com <he...@gmail.com> #14
Comment has been deleted.
ju...@gmail.com <ju...@gmail.com> #16
Having this issue on Pixel 6 pro
ju...@gmail.com <ju...@gmail.com> #17
I am also having the same issue with the phone dialer. It won't allow me to go through menus.
ad...@google.com <ad...@google.com> #18
For the video & bug report in comment #12 : the number you dialed in the video is not supported, so that is working as intended.
ad...@google.com <ad...@google.com> #19
For others who are facing this issue (of pressing the number did not progress through the IVR tree) :
It would be helpful to have a test phone number, a video and a bug report that reflects that scenario.
1. Test phone number used
2. Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
3. Bug report
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
It would be helpful to have a test phone number, a video and a bug report that reflects that scenario.
1. Test phone number used
2. Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
3. Bug report
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
ri...@gmail.com <ri...@gmail.com> #20
I found this bug report too:
https://issuetracker.google.com/issues/278275498
for me, I found that any keypad issue I hit during a call is sent twice, which would help explain this
for me, I found that any keypad issue I hit during a call is sent twice, which would help explain this
ad...@google.com <ad...@google.com> #21
Please provide the information requested in
st...@google.com <st...@google.com>
f....@gmail.com <f....@gmail.com> #22
Can you please clarify why the number used in Comment #12 is unsupported and therefore "working as intended"? It is a USA-based phone number that I pulled up via Phone Dialer search, and previously made this call on prior versions of Android without dialer tree issues. The number and dialer tree works properly when using my wife's Pixel 7 Pro running the latest stable Android 13.
ad...@google.com <ad...@google.com> #23
Others who are facing this issue (of pressing the number did not progress through the IVR tree) :
Please provide all info requested in comment #19 to investigate further.
Please provide all info requested in
aj...@gmail.com <aj...@gmail.com> #24
I have the same problem with my Pixel 7 Pro, with Android Beta 14.1 when you made calls to an automated support number that requires numerical choice for options, the system does not recognize keystrokes and returns error or repeat the initial instructions, over and over again.
ad...@google.com <ad...@google.com> #25
ad...@google.com <ad...@google.com> #26
Please provide all info requested in comment #19 to investigate further.
xr...@gmail.com <xr...@gmail.com> #27
Same issue Pixel 7 Pro
fr...@gmail.com <fr...@gmail.com> #28
I'm also having this issue. Google Pixel 6 Pro. Happens to any system that uses a dialer menu to access extensions/lines.
ad...@google.com <ad...@google.com> #29
If you are facing this issue then please provide all info requested in
je...@gmail.com <je...@gmail.com> #30
This has been fixed for me in beta 2. I can now enter my voicemail password successfully.
ad...@google.com <ad...@google.com> #31
Others who are still facing this issue on the latest build - please provide all info requested in
ad...@google.com <ad...@google.com> #32
Please provide the requested information to proceed further.
he...@gmail.com <he...@gmail.com> #33
Also fixed for me on p6a.
ad...@google.com <ad...@google.com> #34
Others who are still facing this issue on the latest build - please provide all info requested in comment #19 to investigate further.
ad...@google.com <ad...@google.com> #35
Please provide the requested information to proceed further.
sh...@gmail.com <sh...@gmail.com> #36
Proximity sensor not working in google pixel 6 pro. Please resolve it.
vi...@google.com <vi...@google.com> #37
We’ll be closing this issue due to not having enough actionable information. If you continue to have this issue, please open a new issue and add the relevant information along with a reference link to the earlier issue.
al...@gmail.com <al...@gmail.com> #38
This is happening to me for incoming calls, but not outgoing calls.
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Calls / Voice / Mobile Network
When did this happen?
Apr 14, 2023 8:35 AM GMT-07:00
What steps would let us observe this issue?
1. Place a phone call to a number that has a dialer tree.
2. Press any number as prompted to progress through dialer tree
What did you expect to happen?
Progress through dialer tree
What actually happened?
Restarts initial greeting message or returns a "that's an invalid entry/extension" error.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
High
Additional comments
Does not seem to be fixed by toggling SIM on/off, or the VO5G toggle.
Debugging information
Google Play services
com.google.android.gms
Version 231354044 (23.13.54 (190400-520938292))
System App (Updated)
Android System WebView
com.google.android.webview
Version 556311634 (111.0.5563.116)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit