Call phonenumber directly - issue after update to Android 14

[CL]

I use a flow since many years: When the phone connects to WIFI it dials directly a MMI-Code to set or reset call forwarding.
After updating my Pixel 7a to Android 14, the flow is still active, but it doesn't dial in background. It opens the phone-app on the locked phone and pastes the MMI-Code. You can't see this, because it's locked. After unlocking the phone app is in foreground, with pasted MMI-Code. Dialing is not possble, it occurs an error "false code".

Has anyone else such an issue and possibly a workaround?

[Henrik "The Developer" Lindqvist]

The Call number block do still seem to work as expected.

What do you mean by "paste the MMI-Code", is it using the Interact block?

[CL]

Sry for my misslieading post.
The Call number block works as expected.
The android's phone-app gets the phone number (in my case MMI-Code) but doesn't dial allthough phone number dial directly is activated.
Manual dialing leads to an error.
When the phone is unlocked and the flow runs, the phone-app comes in foreground and the phone-number-field is filled from the number block. In this case (phone unlocked) a manual dialing is succesful.

[Henrik "The Developer" Lindqvist]

Tested again, the standard Android phone app opens and dials the number even when the device is locked, so this must be a device issue or a bug in your (MMI-Code?) phone app.

Device brand & model?

[CL]

It's a Pixel 7a with standard phone app, version 115.0.570746104.

I've tested it now with a normal phone-number, and you are right, automate dials in the background.
The behavior occurs with a MMI-Code, f.e ##21# (delete all forwards).

I will look somewhere else (Pixel forum) for a solution. Or do you know a workaround to set a forward with automate?

[Henrik "The Developer" Lindqvist]

Finally able to reproduce, calling ##21# on Android 13 works without user interaction, showing a saying call forward is enabled.

But on Android 14 the phone app only inputs the code but never actually "calls" it.

This is probably an Android 14 regression/bug since it's not a documentation change, see:

https://developer.android.com/reference/android/content/Intent#ACTION_CALL

https://developer.android.com/about/versions/14/behavior-changes-all

This could also be a bug in the Phone app.

I'll report the bug to Google, you should report it on the Pixel forum as well, then i'll check if there's any workaround, and implement it there is.

[Henrik "The Developer" Lindqvist]

Reported: https://issuetracker.google.com/issues/305466094

On Friday, October 13, 2023 at 6:46:49 AM UTC+2 CL wrote:

[Henrik "The Developer" Lindqvist]

So it's an undocumented Android 14 change, fixing a security issue, not a bug, see:

https://issuetracker.google.com/issues/305466094#comment9

I'll investigate if root/ADB access is able to work around it.

On Friday, October 13, 2023 at 6:46:49 AM UTC+2 CL wrote:

[CL]

Hallo Henrik,
after several weeks of unperfect  😉 manual setting of call forwarding, I found a solution to send a mmi-code in background under android 14:
The number has to surronded by (), f. e.  (##21#).

Happy new year
Christian

[Henrik "The Developer" Lindqvist]

LOL, probably not what Google intended, we'll let them discover this "bug" themselves. How did you find this workaround?