(05-03-2022, 06:47 PM)mark1250 Wrote:

(05-03-2022, 05:02 PM)robthebold Wrote:

(04-02-2022, 03:54 AM)Juergen Wrote: I use the open modem firmware from Biktor (0.61) and just tested "mobian-pinephone-phosh-20220327.img.gz".
At incoming calls the phone does not ring reliably.
In PMOS (edge) it works perfectly.
(Braveheart Edition 1.1.)

Not quite as good a result here.   

I've got the Biktor modem firmware and PMOS edge, too, but still don't have reliable incoming call service. Playing around with other distros, too, but so far no luck.  USA, AT&T MVNO. And of course the problem is I don't know if I'm not getting calls because no one's calling or I'm not getting calls because the modem has decided to take a nap.  At least until my wife comes in and demands to know why my nerd phone isn't working and she gets my voicemail. Domestic tranquility may require me to get a flip phone or something.   (Still better than Android, though.)

If anyone's got any good suggestions as to how to periodically poke the modem with a pointy stick so it doesn't doze off, I'm all ears.

Did you follow Biktorgj' recommendation about the udev rule? Here is a link for the OG Pinephone.

Basically you need to edit /usr/lib/udev/rules.d/80-modem-eg25.rules. Change "auto" to "on" in the 1st line and reboot.

(05-04-2022, 12:46 PM)robthebold Wrote:

(05-03-2022, 06:47 PM)mark1250 Wrote:

(05-03-2022, 05:02 PM)robthebold Wrote:

(04-02-2022, 03:54 AM)Juergen Wrote: I use the open modem firmware from Biktor (0.61) and just tested "mobian-pinephone-phosh-20220327.img.gz".
At incoming calls the phone does not ring reliably.
In PMOS (edge) it works perfectly.
(Braveheart Edition 1.1.)

Not quite as good a result here.   

I've got the Biktor modem firmware and PMOS edge, too, but still don't have reliable incoming call service. Playing around with other distros, too, but so far no luck.  USA, AT&T MVNO. And of course the problem is I don't know if I'm not getting calls because no one's calling or I'm not getting calls because the modem has decided to take a nap.  At least until my wife comes in and demands to know why my nerd phone isn't working and she gets my voicemail. Domestic tranquility may require me to get a flip phone or something.   (Still better than Android, though.)

If anyone's got any good suggestions as to how to periodically poke the modem with a pointy stick so it doesn't doze off, I'm all ears.

Did you follow Biktorgj' recommendation about the udev rule? Here is a link for the OG Pinephone.

Basically you need to edit /usr/lib/udev/rules.d/80-modem-eg25.rules. Change "auto" to "on" in the 1st line and reboot.

Nope. I completely missed that (or at least misread it). Good excuse to finally install nano. I've edited and rebooted and will see what happens

Thanks

(12-08-2020, 02:03 AM)dcinoz Wrote: FYI 5 additional VoLTE profiles (in bold):

Edit: $mmcli --list-modems | grep -oP "(?<=Modem/)[0-9]+" to get correct modem 'number'

$mmcli -m 0 --command='AT+QMBNCFG="list"' (modem number may not be '0')

Edit: As per https://forum.pine64.org/showthread.php?tid=11815&pid=85971#pid85971 from fdlamotte above command can be simplified using -m any instead of a number as there is only one modem in the Pinephone:
mmcli -m any --command=.....

Response:
+QMBNCFG: "List",0,0,0,"ROW_Generic_3GPP",0x05010820,201905141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,202004261
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,202004091
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,202004211
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,202003251
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,202004151
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,202004161
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,202001171
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,202001171
+QMBNCFG: "List",14,1,1,"Telstra-Commercial_VoLTE",0x0580079E,202006101
+QMBNCFG: "List",15,0,0,"Commercial-KDDI",0x0501071D,202004041
+QMBNCFG: "List",16,0,0,"Commercial-DCM",0x05010D17,202006101
+QMBNCFG: "List",17,0,0,"Commercial-SKT_VoLTE",0x05012724,201907221
+QMBNCFG: "List",18,0,0,"Commercial-KT",0x05012C0D,202005071

Note 1,1 indicates Telstra for me (though not currently available to Telstra MVNOs so can't test).
The following AT commands could be of interest to you, not sure what defaults are.

# SelectVoLTE profile
AT+QMBNCFG="Select","Telstra-Commercial_VoLTE" (use relevant name for you)

# Deactivate active profile
AT+QMBNCFG="Deactivate"

# Configure MBN Automatic Selection Function
# Return current configuration
AT+QMBNCFG="AutoSel"

response: '+QMBNCFG: "Autosel",1' (enabled)
response: '+QMBNCFG: "Autosel",1' (disabled)

#Set to autosel
AT+QMBNCFG="AutoSel",<enable>
where <enable> 0 disable, 1 enable

# Enable calling over ip (VoLTE)
AT+QCFG="ims",1

# Check ims status
AT+QCFG="ims"

Response:
+QCFG: "ims",<value>,<volte_state>

<value>              IMS function configuration parameter
                0        The NV about IMS can be set by the configuration of the MBN file
                1        Enable IMS function
                2        Disable IMS function

<volte_state>      VoLTE state
                0        VoLTE is not ready
                1        VoLTE is ready

Edit: Don't believe this is needed as it is Set Phone Functionality command (might be needed to enable settings changes)
# Reboot the modem to apply the settings # THIS IS WRONG
AT+CFUN=1,1 # THIS SETS FULL PHONE FUNCTIONALITY AND RESETS THE ME
AT+CFUN=1,0 # this sets full (default) functionality (1) and does not reset the ME (0)

# Set Phone Functionality
AT+CFUN=<fun>[,<rst>]

<fun>          0      Minimum functionality
                   1      Full functionality (Default)
                   4      Disable the ME from both transmitting and receiving RF signals

<rst>          0      Do not reset the ME before setting it to <fun> functionality level.
                          This is the default setting when <rst> is not given.
                   1     Reset the ME. The device is fully functional after the reset.
                          This value is available only for <fun>=1.

Response:
OK
If there is an error related to ME functionality, response:
+CME ERROR: <err>

# Check Phone Functionality
AT+CFUN?

Response:
+CFUN: <fun>

<fun>          0      Minimum functionality
                   1      Full functionality (Default)
                   4      Disable the ME from both transmitting and receiving RF signals

End edit.

Write down your actual configuration values / settings before changing anything and don't blame me - I don't believe you can break anything permanently but things could stop working until you revert back to your current configuration, you have been warned.

Google is your friend for Quectel PDFs though I couldn't find one for the EG25-G.
Be aware of the m modem number increasing as modem sleeps / wakes up.
Be aware that " is used in the commands.
AT commands can also be sent using minicom or screen for example using /dev/ttyUSB2 (Mobian, not sure on other OSes).

I've tried uploading and 'Adding' MBN files (new profiles) from a Xiaomi Android phone but it failed (Optus and Vodafone), presumably due to not being signed correctly. I wonder what will happen in terms of future support / updates from Quectel.

(07-07-2022, 04:24 PM)simcommbn Wrote: Hey, I know this is a long shot since I don't even have a Pinephone. But what I do have is a device that uses the same underlying modem. Is there any chance someone could provide me the Volte-ATT.mbn file so I can add AT&T VoLTE calling support to my device? I tried extracting it from the firmware images myself, but I cannot for the life of me figure out where the carrier configuration files are being stored. If they're in there, they're either in one of the .img files I can't get to extract, or they're named differently once actually flashed somehow. I'm just lost and tired, and figured maybe someone here already has a copy of the file I need anyways. I suppose a dump of all the carrier-specific MBNs might be useful for recovery purposes anyways for someone, so it couldn't hurt to have them uploaded somewhere if someone can get them or already has them. Hope it's not too much trouble. Thanks.