QMI, EC25-V, Verizon problems

For Developers
1

Having ongoing issues, I inserted set -x into qmi.sh, and got following error:

Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --stop-network 0xffffffff --autoconnect
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --set-device-operating-mode online
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --set-data-format 802.3
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --wda-set-data-format 802.3
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --wda-get-data-format
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + dataformat='"raw-ip"'
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + '[' '"raw-ip"' '=' '"raw-ip"' ]
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + '[' -f /sys/class/net/wwan0/qmi/raw_ip ]
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + echo 'Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..'
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + echo Y
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --sync
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --network-register
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + echo 'Waiting for network registration'
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): Waiting for network registration
Fri Dec 16 15:58:51 2022 daemon.notice netifd: wwan (4272): + sleep 1
Fri Dec 16 15:58:52 2022 user.notice root: No RS485-USB converter detected
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + local 'registration_timeout=0'
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + local 'registration_state='
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + true
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + + uqmi -s -d /dev/cdc-wdm0 --get-serving-system
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): jsonfilter -e @.registration
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + registration_state=registered
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' registered '=' registered ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + break
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' -n  ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + echo 'Starting network wwan'
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): Starting network wwan
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + + echo
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): awk '{print tolower($0)}'
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + pdptype=
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '['  '=' ip -o  '=' ipv6 -o  '=' ipv4v6 ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + pdptype=ip
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' ip '=' ip ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' -z 0 ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' 0 '=' 0 ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + autoconnect=
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' ip '=' ip -o ip '=' ipv4v6 ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --get-client-id wds
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + cid_4=20
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + '[' 20 -eq 20 ]
Fri Dec 16 15:58:52 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --set-client-id wds,20 --set-ip-family ipv4
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --set-client-id wds,20 --start-network --apn vzwinternet
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): + pdh_4='"Call failed"'
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): + '[' '"Call failed"' -eq '"Call failed"' ]
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): + echo 'Unable to connect IPv4'
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): Unable to connect IPv4
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): + uqmi -s -d /dev/cdc-wdm0 --set-client-id wds,20 --release-client-id wds
Fri Dec 16 15:58:53 2022 daemon.notice netifd: wwan (4272): + proto_notify_error wwan CALL_FAILED

Any ideas ?
This is on 22.03.2.

Much more complete log available, upon request. This behaviour is reproducable.

2

Hi

You can do some manual testing.
Run

uqmi -d /dev/cdc-wdm0 --get-serving-system

to see if your device is registered and

uqmi -d /dev/cdc-wdm0 --get-signal-info

to see what technology your device is registered to.
If your device is register to LTE then you have a valid default APN or your defaut APN is empty and Verzion has assigned one.
Try to start the network connection without APN:

uqmi -d /dev/cdc-wdm0 --get-client-id wds
uqmi -d /dev/cdc-wdm0 --set-client-id wds,<wds-client-id> --start-network
3

I did that already, before posting here: Same result. (Successfully registered)
However, after checking Quectel user forum, I found another user, having EC25-A(F?), facing the same error when using latest Quectel firmware, like me. So it looks like a firmware issue of the modem.

4

Since it is successfully registered, to LTE I assume, what APN is used?

5

vzwinternet