+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Mobian on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=139)
+---- Thread: Pinephone woon't stay registered (/showthread.php?tid=16418)
Pages:
1
2
Pinephone woon't stay registered - jhasler - 04-01-2022
Pinephone beta edition purchased last month. Installed Mobian and a Tracfone sim. Activated it successfully. I can occasionally complete a call but it always gets terminated within a minute or two. A typical log extract is included below.
Apr 01 17:05:03 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:03 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:03 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:05:04 mobian ModemManager[600]: <info> [modem0/call1] call state changed: dialing -> ringing-out (unknown)
Apr 01 17:05:05 mobian ModemManager[600]: <info> [modem0/call1] call state changed: ringing-out -> active (unknown)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:07 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:55 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:05:58 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> idle)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] state changed (registered -> enabled)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:06:00 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
Apr 01 17:06:19 mobian ModemManager[600]: <info> [modem0/call1] call state changed: active -> terminated (unknown)
Apr 01 17:06:29 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (home -> searching)
Apr 01 17:06:29 mobian ModemManager[600]: <info> [modem0] state changed (registered -> searching)
Apr 01 17:06:29 mobian ModemManager[600]: <warn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Apr 01 17:06:29 mobian ModemManager[600]: <warn> [modem0] couldn't load operator name: Current operator id is still unknown
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (searching -> idle)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] state changed (searching -> enabled)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 01 17:07:02 mobian ModemManager[600]: <info> [modem0] state changed (enabled -> registered)
RE: Pinephone woon't stay registered - jhasler - 04-02-2022
Update: Reinstalled the latest weekly and upgraded. Now the log cycles through
Apr 02 15:47:27 mobian ModemManager[578]: <warn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Apr 02 15:47:27 mobian ModemManager[578]: <warn> [modem0] couldn't load operator name: Current operator id is still unknown
Apr 02 15:47:48 mobian ModemManager[578]: <info> [modem0] 3GPP registration state changed (unknown -> idle)
Apr 02 15:47:48 mobian ModemManager[578]: <info> [modem0] 3GPP registration state changed (idle -> registering)
Apr 02 15:47:48 mobian ModemManager[578]: <info> [modem0] 3GPP registration state changed (registering -> home)
Apr 02 15:47:48 mobian ModemManager[578]: <info> [modem0] state changed (enabled -> registered)
Apr 02 15:48:05 mobian ModemManager[578]: <info> [modem0] 3GPP registration state changed (home -> unknown)
Apr 02 15:48:05 mobian ModemManager[578]: <info> [modem0] state changed (registered -> enabled)
I'm no longer ever able to complete or receive a call.
Immediately after rebooting I see:
Apr 02 15:44:27 mobian ModemManager[578]: [/dev/cdc-wdm0] Registered 'pdc' (version 1.0) client with ID '1'
Apr 02 15:44:27 mobian ModemManager[578]: [/dev/cdc-wdm0] Allocating new client ID...
Apr 02 15:44:27 mobian ModemManager[578]: [/dev/cdc-wdm0] Registered 'voice' (version 2.1) client with ID '3'
Apr 02 15:44:29 mobian ModemManager[578]: <warn> [modem0] couldn't query SIM slots: QMI protocol error (94): 'NotSupported'
Apr 02 15:44:29 mobian ModemManager[578]: <warn> [modem0/sim0] couldn't load operator identifier: Couldn't get home network: QMI protocol error (16): 'NotProvisioned'
Apr 02 15:44:29 mobian ModemManager[578]: <warn> [modem0/sim0] couldn't load operator name: Couldn't get home network: QMI protocol error (16): 'NotProvisioned'
RE: Pinephone woon't stay registered - jhasler - 04-02-2022
Upgraded the modem firmware. No change. Incoming calls go to voicemail. Attempting to place a call produces this in the log:
[modem3] state changed (enabled -> registered)
Apr 02 18:42:35 mobian ModemManager[578]: <info> [modem3/call1] user request to start call
Apr 02 18:42:35 mobian ModemManager[578]: <info> [modem3/call1] call state changed: unknown -> dialing (outgoing-started)
Apr 02 18:42:42 mobian ModemManager[578]: <info> [modem3] 3GPP registration state changed (home -> searching)
Apr 02 18:42:42 mobian ModemManager[578]: <info> [modem3] state changed (registered -> searching)
Apr 02 18:42:42 mobian ModemManager[578]: <warn> [modem3] couldn't load operator code: Current operator MCC/MNC is still unknown
Apr 02 18:42:42 mobian ModemManager[578]: <warn> [modem3] couldn't load operator name: Current operator id is still unknown
Apr 02 18:43:07 mobian ModemManager[578]: <warn> [modem3/call1] couldn't start call: Couldn't create call: QMI protocol error (90): 'IncompatibleState'
Apr 02 18:43:07 mobian ModemManager[578]: <info> [modem3/call1] call state changed: dialing -> terminated (unknown)
RE: Pinephone woon't stay registered - Fish - 04-02-2022
I cannot help you with this, but have you tried Biktors firmware?
link: https://github.com/Biktorgj/pinephone_modem_sdk
note: use at your own risk.
RE: Pinephone woon't stay registered - Juergen - 04-03-2022
(04-02-2022, 04:07 PM)Fish Wrote: I cannot help you with this, but have you tried Biktors firmware?
link: https://github.com/Biktorgj/pinephone_modem_sdk
note: use at your own risk.
I'm using Biktor's firmware for several month now, works perfect.
I'm using PMOS (edge) for several month now without modem disconnects, works perfect. The modem wakes up
reliably from suspend and rings at the first dial tone.
I'm using ADSP Version 01.003.01.003
RE: Pinephone woon't stay registered - jhasler - 04-03-2022
(04-03-2022, 01:18 AM)Juergen Wrote:(04-02-2022, 04:07 PM)Fish Wrote: I cannot help you with this, but have you tried Biktors firmware?
link: https://github.com/Biktorgj/pinephone_modem_sdk
note: use at your own risk.
I'm using Biktor's firmware for several month now, works perfect.
I'm using PMOS (edge) for several month now without modem disconnects, works perfect. The modem wakes up
reliably from suspend and rings at the first dial tone.
I'm using ADSP Version 01.003.01.003
I may try that after I have this thing working as well as it does for most other Pinephone users. I've ordered a sim from US Mobile to see if the Tracfone sim is the problem. I think that "couldn't load operator code: Current operator MCC/MNC is still unknown" is at the core.
I've been learning more than I really wanted to know about the insanely complex cellphone APIs, protocols, and interfaces.
RE: Pinephone woon't stay registered - jhasler - 04-06-2022
Same behavior with a US Mobile SIM as with the Tracfone one.
RE: Pinephone woon't stay registered - jhasler - 04-06-2022
I'm getting
mobian@mobian:~$ sudo mmcli --command='AT+CPOL=?' -m 0
error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NotAllowed: Operation not allowed'
I get the same error using minicom to send that AT command. Same result without the "=". It should return the preferred operator list.
I get the same error witha Tracfone simand with a US Mobile sim.
RE: Pinephone woon't stay registered - jhasler - 04-06-2022
Now I sometimes see:
sudo mmcli -m 2 --3gpp-register-in-operator=310240
error: couldn't register the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NetworkNotAllowed: Network not allowed - emergency calls only'
RE: Pinephone woon't stay registered - jhasler - 04-08-2022
Installed Biktorj's modem firmware.
Made a difference: the modem now connects and stays connected for at least an hour. However, I still cannot complete calls. My first try went through but was terminated (reason "unknown") after a few seconds. Subsequent attempts get
couldn't start call: Couldn't create call: QMI protocol error (90): 'IncompatibleState'
followed by
[modem14/call3] call state changed: dialing -> terminated (unknown)
Incoming calls get sent to voicemail. Now, after an attempt to call the phone, the log is filling up with
<warn> [modem14/bearer20] reloading stats failed: Couldn't get packet statistics: QMI protocol error (15): 'OutOfCall'
On a second attempt to call in the phone rang but the ringback continued and the call did not complete. Log:
<info> [modem14/call4] call state changed: unknown -> ringing-in (incoming-new)
<info> [modem14/call4] user request to accept call
<info> [modem14/call4] call is accepted
<info> [modem14/call4] call state changed: ringing-in -> active (accepted)
<info> [modem14/call4] call state changed: active -> terminated (unknown)
<warn> [modem14/bearer20] reloading stats failed: Couldn't get packet statistics: QMI protocol error (15): 'OutOfCall'
<info> [modem14] 3GPP registration state changed (home -> searching)
<warn> [modem14] couldn't load operator code: Current operator MCC/MNC is still unknown
<warn> [modem14] couldn't load operator name: Current operator id is still unknown
<warn> [modem14] couldn't load operator code: Current operator MCC/MNC is still unknown
<warn> [modem14] couldn't load operator name: Current operator id is still unknown
and then back to:
<warn> [modem14/bearer20] reloading stats failed: Couldn't get packet statistics: QMI protocol error (15): 'OutOfCall'
Seems like the modem is working but modemmanager isn't.