Status Update
Comments
vi...@google.com <vi...@google.com> #2
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
he...@gmail.com <he...@gmail.com> #3
Here you go.
vi...@google.com <vi...@google.com> #4
he...@gmail.com <he...@gmail.com> #5
Here you go.
vi...@google.com <vi...@google.com> #6 Restricted+
he...@gmail.com <he...@gmail.com> #7
As said, i myself have reproduced it on the latest Android 14 emulator image, revision 9, sdk_gphone64_x86_64-userdebug 14 UE1A.230829.019 10866155 dev-keys
. But a user of my app have reported it affecting Pixel 7a with standard phone app version 115.0.570746104, i.e. the reason of this issue report.
vi...@google.com <vi...@google.com> #8
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
vi...@google.com <vi...@google.com> #9
Thanks for reporting this issue!
This was an intentional change related to a fix for a security vulnerability CVE-2023-21313. Starting with Android 14, only system or user configured default dialer can use ACTION_CALL to configure call forwarding using MMI codes. Otherwise, the user must confirm to dial the MMI code.
he...@gmail.com <he...@gmail.com> #10
Does it only affect call forwarding?
Please update the documentation accordingly.
ar...@gmail.com <ar...@gmail.com> #11
Since there are legitimate cases for apps to manage call forwarding settings, can you add a new permission which apps can explicitly request?
cl...@gmail.com <cl...@gmail.com> #12
Surrond the MMI-Code with (), f. e. (##21#)
Description
On Android 14 using ACTION_CALL with MMI code, e.g. ##21# (call forward), no longer works without user intervention as the code is only inputted but never actually called/sent. On Android 13 and lower the code is actually called so the "success" dialog is shown immediately.
This is either an undocumented change or a bug, making ACTION_CALL behave like ACTION_DIAL for MMI codes.
I've only reproduced this on Android 14 emulator, but got reports of it affecting Pixel 7a with standard phone app version 115.0.570746104.