Google Pixel 7 pro: after update to Android 14, ringtone changing no longer works

[Saito Benkei]

Hi, I have a flow that, when a call arrives, depending on the sim on which the call arrives sets one ringtone rather than another.
Until the version of android 13 everything worked correctly.
Since the update to android 14 the ringtone change works only if I have "Automate" fully open on the screen.
If I go to see the log, the sim intercept and subsequent ringtone change happens correctly with both "Automate" open and closed, but the ringtone is no longer changed.

[Henrik "The Developer" Lindqvist]

Works as expected on standard Android 14 emulator. Tested with:

1. Flow beginning
2. Delay: 10s
3. Ringtone set: Sound URI=<choose any>
   
4. Notification show: Title=First, Icon=<choose any>
5. Delay: 10s
   
6. Ringtone set: Sound URI=<choose another>
   
7. Notification show: Title=Second, Icon=<choose another>
8. (loop back to #2)
   

Then call within any of the 10s delays and the ringtone will indeed differ.

[Saito Benkei]

Thank you, but in my smartphone the flow changes the ringtone only if "automate" is open (I'm inside the flow screen and I watch the log while I receive the call). 

Il "automate" is in background the ringtone isn't changed. But if I watch the log after the call, it seems all works correctly. 

Thank you

[Henrik "The Developer" Lindqvist]

Pixel device shouldn't include any non-standard "power save" feature which could interfere,  please ensure there's none, see also:

https://llamalab.com/automate/doc/faq.html#automate_not_running

Since i can't reproduce the issue, it's difficult to figure out the cause without seeing the flow, if there's a problem with it's design.

[Saito Benkei]

This is the flow (blocks 3 and 7 play different ringtone).

When in background it's okay always ringgtone in block 3 that's the same ringtone configured in system settings.

[Saito Benkei]

Saito Benkei

6 nov 2023, 21:53:46 (3 ore fa) 

a Automate for Android

* When in background it's play always ringtone in block 3 that's the same ringtone configured in system settings.

[Henrik "The Developer" Lindqvist]

You can't expect that changing the ringtone when its already begun ringing to work, i.e. the Ringtone set block is executed just after Call incoming block.

It working on earlier Android versions may have been just luck, maybe due to the Call incoming block be triggered by the system in a few milliseconds earlier.

[Saito Benkei]

Ok, thank you anyway!

[Henrik "The Developer" Lindqvist]

You might try using the Call screening and Call screening result blocks instead, since those should be executed before the call has begun ringing.

[Saito Benkei]

"Call screening" overrides antispam app settings (Only one app connected to "Call screning" is allowed).
Unfortunately, this is not a viable solution....

[Dmitriy F.]

I would like to raise the topic as I have the same problem with call screening. Android 14 Pixel 7a. If the Automate app is open the call screening works as expected. If the application is in background, the call passes by and is not handled in fiber.

Is there a solution to the problem?

[Henrik "The Developer" Lindqvist]

Very odd. Such behavior is usually caused by non-standard "power save" features killing the app, but Pixel shouldn't include such.

If your flow is showing some dialog then ensure the "draw over other apps or parts the screen" privilege is granted, otherwise they wont show up.

As a test, try a simple test flow:

1. Flow beginning
   
2. Call screening
3. Call screening response: Action=Block
4. (loop back to #2)

Does that test flow block all calls even while Automate is in the background?

[Dmitriy F.]

Thanks for the great advice. I have tried to look into the problem deeper and so far I conclude that the Call screening block itself is working fine.

However, my flow before the "Call screening" block contains "Call Incoming" and it seems to be the one that affects the problem I described.

My flow consists of:
- Call incoming "When ringing"
- Log " Log call from {Number} on {Line}"
- Call screening
- Log "Screen call from {Number} with {Status}"
- Other routins... 

The app in foreground: 
04-19 14:09:51.046 I 40@1: Flow beginning
04-19 14:09:51.048 I 40@55: Call incoming
04-19 14:10:59.908 U 40@72: Log call from +48XXXXXXXXX on 2
04-19 14:10:59.909 I 40@53: Call screening
04-19 14:11:00.064 U 40@73: Screen call from +48XXXXXXXXX with 1
04-19 14:11:00.065 I 40@5: Contact query?
04-19 14:11:00.079 I 40@64: Database query
04-19 14:11:00.118 I 40@68: Expression true?

The app not in foreground:
04-19 14:00:04.959 I 39@1: Flow beginning
04-19 14:00:04.959 I 39@55: Call incoming
04-19 14:00:14.632 U 39@72: Log call from +48XXXXXXXX on 2
04-19 14:00:14.632 I 39@53: Call screening
04-19 14:03:19.820 I 39@53: Stopped by user

The author of this thread also has a flow starting from this block. It is interesting to understand their impact on each other.
This flow has been with me for a long time and worked properly on 11 and 12 versions of Android, it stopped working only after I changed my phone and moved to Android 14.

--
You received this message because you are subscribed to a topic in the Google Groups "Automate for Android" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/M_JO4NczvjQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/bfc52a26-e0e5-459b-8426-63269ce5e2afn%40googlegroups.com.

--

Всего хорошего!

[Henrik "The Developer" Lindqvist]

There should be no need for an Call incoming block when using the Call screening block.

[Dmitriy F.]

Yes but my case is to run the flow only for calls coming from one of the SIM cards. Is there any other way to do it without Call Incoming?

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/7087ad6a-e7a2-4cac-8605-04a800477bccn%40googlegroups.com.

--

Всего хорошего!

[Henrik "The Developer" Lindqvist]

No. Please star: https://issuetracker.google.com/issues/278800519