Latest firmware for PinePhone modem!
#31
Thanks, went smoothly!
  Reply
#32
Worked great on mobian with Megi's multi_boot img. I had to reboot the phone before the dmesg gave the updated information.
  Reply
#33
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?...1#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.
Pinephone v1.2 UBports CE. Adelaide, Australia using Amaysim SIM (Optus network, VoLTE enabled) with Mobian SD card. VoLTE working also with Felix / Vodafone AU and Aldimobile / Telstra AU.
Manjaro Plasma Mobile on EMMC.
  Reply
#34
For those that have installed and are USA based, any quality of life improvements that are noticeable post update? I see that my carrier is listed with a VoLTE profile on the shipped modem version, and as I don't call often didn't know if it would be worth attempting or better left alone for now.

I'm leaning more towards leaving it to test initially but wanted to see if anyone else could chime in.
  Reply
#35
Did the update on current pmOS just today (5.9.1), here's  the list of needed (additional) tasks for pmOS:

1) it's not possible to uncompress zstd by default :
Code:
pitrpp:~/Downloads/modem_fw$ tar xvf newfw.tar.zst
tar: invalid tar magic

pitrpp:~/Downloads/modem_fw$  tar -I zstd -xvf newfw.tar.zst
tar: unrecognized option: I
so install zstd
Code:
pitrpp:~/Downloads/modem_fw$ sudo apk add zstd
[sudo] password for p1trson:
(1/1) Installing zstd (1.4.5-r0)
Executing busybox-1.31.1-r19.trigger
OK: 1105 MiB in 499 packages


pitrpp:~/Downloads/modem_fw$ unzstd newfw.tar.zst
Code:
newfw.tar.zst       : 118108160 bytes
Code:
pitrpp:~/Downloads/modem_fw$ unzstd qfirehose_good.tar.zst
Code:
qfirehose_good.tar.zst: 409600 bytes

then untaring works

Code:
pitrpp:~/Downloads/modem_fw$ tar xvf newfw.tar
...
pitrpp:~/Downloads/modem_fw$ tar xvf qfirehose_good.tar
...

on pmOS you won't be able to just
Code:
pitrpp:~/Downloads/modem_fw/qfirehose_good$ sudo ./QFirehose -f ../newfw
sudo: unable to execute ./QFirehose: No such file or directory

install following:
Code:
apk add make
apk add gcc
apk add musl-dev
apk add linux-headers

then
Code:
pitrpp:/home/p1trson/Downloads/modem_fw/qfirehose_good# ./QFirehose -f ../newfw


verify the output
Code:
...
[034.935]: upgrade progress 100% 122659832/122437088
[034.936]: send finished
[034.936]: <log value="Finished sector address 0"/>
[034.936]: <response value="ACK" rawmode="false" />
[034.936]: <power value="reset" />
[034.937]: <log value="Inside handlePower() - Requested POWER_RESET"/>
[034.937]: <response value="ACK" />
[035.939]: inf[0] ep_in -1/1024, errno = 108 (Cannot send after socket shutdown)
[035.939]: qusb_noblock_read read=-1, errno: 108 (Cannot send after socket shutdown)
[035.939]: qusb_noblock_read cur=0, min_size=1
[035.939]: firehose_protocol.c fh_recv_cmd 327 fail
[035.939]: THE TOTAL DOWNLOAD TIME IS 30.430 s
[035.939]: Upgrade module successfully.

and reboot. verify the version via dmesg
Code:
pitrpp:~# dmesg | grep -i modem
...
[   27.938244] modem-power serial1-0: Project Rev : EG25GGBR07A08M2G_01.002.07
...
  Reply
#36
after the updates, calls did not work as good as before ...

I tried disabling VoLTE usiing dcinoz commands, it now works as a charm (maybe we don't have the good profile or I couldn't find it ...)

also fyi you can use "mmcli -m any" if you don't want to search for your modem number (assuming you only have one modem Wink but it should be the case)
  Reply
#37
Perhaps interesting:

https://github.com/Biktorgj/quectel_eg25_recovery

https://github.com/Biktorgj/pinephone_modem_sdk
  Reply
#38
Hi,

I'm getting:
[035.180]: upgrade progress 100% 122659832/122437088
[035.180]: send finished
[035.180]: <log value="Finished sector address 0"/>
[035.181]: <response value="ACK" rawmode="false" />
[035.181]: <power value="reset" />
[035.181]: <log value="Inside handlePower() - Requested POWER_RESET"/>
[035.181]: <response value="ACK" />
[036.188]: inf[0] ep_in -1/1024, errno = 108 (Cannot send after transport endpoint shutdown)
[036.188]: qusb_noblock_read read=-1, errno: 108 (Cannot send after transport endpoint shutdown)
[036.188]: qusb_noblock_read cur=0, min_size=1
[036.188]: firehose_protocol.c fh_recv_cmd 327 fail
[036.188]: THE TOTAL DOWNLOAD TIME IS 30.851 s
[036.188]: Upgrade module successfully.

When I do 'dmesg | grep -i modem' it doesn't show me the new firmware version before or after reboot. Is there another way to check this? @as400 mentioned having to change the log level?
I'm just worried about the '[036.188]: firehose_protocol.c fh_recv_cmd 327 fail' even though it says 'Upgrade module successfully'.

Thanks
  Reply
#39
(12-19-2020, 09:41 AM)moodroid Wrote: When I do 'dmesg | grep -i modem' it doesn't show me the new firmware version before or after reboot. Is there another way to check this? @as400 mentioned having to change the log level?
I'm just worried about the '[036.188]: firehose_protocol.c fh_recv_cmd 327 fail' even though it says 'Upgrade module successfully'.

Thanks

Try:

Code:
$ mmcli -m any --command='AT+GMR'
response: 'EG25GGBR07A08M2G'

According to AT commands this is the AT+GMR Request Firmware Revision Identification command.

Mobian also has the revision in Settings -> Mobile -> Advanced (Modem Details) -> Firmware Version

You can also check the VoLTE profiles list, there should be 18:
Code:
$ mmcli -m any --command='AT+QMBNCFG="list"'
Pinephone v1.2 UBports CE. Adelaide, Australia using Amaysim SIM (Optus network, VoLTE enabled) with Mobian SD card. VoLTE working also with Felix / Vodafone AU and Aldimobile / Telstra AU.
Manjaro Plasma Mobile on EMMC.
  Reply
#40
Perfect thank you @dcinoz - looks like it all went well
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Which word processor to choose for the Pinephone? Peter Gamma 16 2,909 06-22-2024, 07:28 AM
Last Post: Peter Gamma
  Samba share on the Pinephone? Peter Gamma 0 381 06-16-2024, 10:26 PM
Last Post: Peter Gamma
  Struggle to install LibreOffice on the PinePhone Peter Gamma 49 28,495 06-13-2024, 05:50 PM
Last Post: Peter Gamma
  Possible Free Backup Carrier for PinePhone PineFone 0 78 06-13-2024, 03:45 PM
Last Post: PineFone
  Using Signal on PinePhone in mid-2023? dante404 47 16,714 05-03-2024, 02:19 AM
Last Post: dragonhospital
  Slarm64 on PinePhone [Unofficial Slackware ARM - 64 bit] acid andy 38 27,144 04-23-2024, 10:29 AM
Last Post: donchurch
  PinePhone app development WhiteHexagon 15 4,946 04-23-2024, 05:19 AM
Last Post: Jonnyc
Wink PINEPHONE not booting Touchwood 2 730 02-23-2024, 07:27 AM
Last Post: Touchwood
  Slack on PinePhone Adam Seline 5 5,758 12-20-2023, 07:20 AM
Last Post: nickolas
  openSUSE for Pinephone Alefnode 75 105,849 11-17-2023, 08:37 AM
Last Post: Uturn

Forum Jump:


Users browsing this thread: 3 Guest(s)