Mobile Data Network Type Block doesn't proceed when changed

50 views
Skip to first unread message

Sand Lee

unread,
Mar 12, 2026, 11:35:46 AMMar 12
to Automate for Android
Hi, 

I'm using Automate version 1.51.0 and having trouble with this block:

I've tested two flows: one which polls the mentioned block every 3 seconds and prints the type and another which pauses the fiber until there's a change in the network type. The first flow shows type changes as expected, but the second never triggers.

The two methods I've used to test type changes are: 1) checking for IWlan and toggling Wifi-calling and 2) checking for LTE+NR and toggling mobile data.

Thanks

Henrik "The Developer" Lindqvist

unread,
Mar 14, 2026, 11:20:10 AMMar 14
to Automate for Android
Seems to work on my Android 16 device, but i can tell if the "Current network type" output variable actually change, since it's always LTE where i'm at.

As a test, try leaving the "Network types" input argument empty, do the block then proceed, and if so what's the  "Current network type" output variable?

Android version?
Message has been deleted

Sand Lee

unread,
Mar 14, 2026, 11:46:13 PMMar 14
to Automate for Android
I'm using Android 16 as well. 

With your suggestion, I can see the polling method change between: LTE, NR, IWLAN, and Unknown (if no radio is on).

The "when changed" method doesn't follow the same behavior. It changes between LTE, NR and Unknown. The IWLAN state is never used, no matter what I try.

BTW, I didn't see way to easily determine the type from the number, but this is what I managed to decode:
* 1 Unknown 
* 8192 LTE
* 262144 IWLAN
* 1048576 NR

Thanks

мJ ZЖУ

unread,
Mar 15, 2026, 3:49:20 AMMar 15
to Automate for Android
Could you try check if disable LTE and it change to 4G or 3G or else? Or does it still connect while network is unknown?

Henrik "The Developer" Lindqvist

unread,
Mar 15, 2026, 12:14:08 PMMar 15
to Automate for Android
So the block works with proceed When changed as longs as it's not including IWLAN as network type input argument?
The output values are the same as the input, use the hexEncode function when logging it.

The Android API used by the block is deprecated, and has been replaced with a newer one, but it didn't seem to work any differently when i tested.
Maybe using it would make IWLAN to be reported as well
 I could compile a nightly build using that's using the new API if you're willing to test it for me, if so email me at in...@llamalab.com

Sand Lee

unread,
Mar 15, 2026, 3:26:53 PMMar 15
to Automate for Android
Just retested the block today. Seems like the block with proceed When changed makes the following mappings:
* NR -> LTE
* !(LTE || NR) -> Unknown
It doesn't seem to be taking IWLAN into account at all. Preferring 3G seems to do nothing where I live.

I'll keep the hexEncode function in mind. Interestingly, it seems like the decimal output value was always a power of two when I tested. 

Henrik "The Developer" Lindqvist

unread,
Mar 15, 2026, 4:02:43 PMMar 15
to Automate for Android
Indeed power of two since they're bitwise flags.
Reply all
Reply to author
Forward
0 new messages