Latest firmware for PinePhone modem!

[dukla2000]

I decided to try installing this in hopes of fixing modem issues (in fact i did it couple of weeks ago), but it did not. I cannot tell if it helps for that thing many others say, missing calls, because i never tried calls so much, but the issue of losing mobile data after waking up from sleep is still present.

Yepp,

absolutely no change on the problem of

- not receiving incoming calls
- losing mobile connection after wakeup
- modem completely without function after wakeup

Since weeks NO reliable incoming calls :-(

I have far less problem than you, I think, after wakeup. For sure occasionally things need a reboot. But for whatever reason I learned a long time ago that my wakeup routine must be

1. push powerbutton
   
2. wait till phone signal strength (and wifi if enabled) icons appear and get status on lock screen
   
3. then scroll up phosh unlock screen and unlock
   

Otherwise I get the "dreaded" no data icon in the status bar and have yet to find a reliable cure for it except reboot. (It will also cure if WiFi was off, you enable it and it connects but that depends on being in a WiFi area.)

Similarly I receive all the incoming calls I expect and have had no moans from any contacts. I do receive few calls though - less than 1/day. But I do have a ritual after every reboot to go to Settings, Sound, and test both channels, then flick the bottom of the phone and check the mic signal meter moves. About half of the time the settings application crashes before completing all 3 steps - retry the Settings application as necessary. Often times it auto swaps to a Ping rather than "Front left" - in which case playing with the Phone/default option may recover things, or a reboot or a ...

[puffchumpy]

Updating my Braveheart board did increase the list of supported LTE networks, so something changed. I updated to the Mobian 5.8 kernel to do the upgrade. So I don't know if the Mobian update or modem update reduced the running temperature. Before the board and modem were getting very hot, the temperature is much less now.

[firefox-58]

I decided to try installing this in hopes of fixing modem issues (in fact i did it couple of weeks ago), but it did not. I cannot tell if it helps for that thing many others say, missing calls, because i never tried calls so much, but the issue of losing mobile data after waking up from sleep is still present.

Yepp,

absolutely no change on the problem of

- not receiving incoming calls
- losing mobile connection after wakeup
- modem completely without function after wakeup

Since weeks NO reliable incoming calls :-(

I have far less problem than you, I think, after wakeup. For sure occasionally things need a reboot. But for whatever reason I learned a long time ago that my wakeup routine must be

1. push powerbutton
   
2. wait till phone signal strength (and wifi if enabled) icons appear and get status on lock screen
   
3. then scroll up phosh unlock screen and unlock
   

Otherwise I get the "dreaded" no data icon in the status bar and have yet to find a reliable cure for it except reboot. (It will also cure if WiFi was off, you enable it and it connects but that depends on being in a WiFi area.)

Similarly I receive all the incoming calls I expect and have had no moans from any contacts. I do receive few calls though - less than 1/day. But I do have a ritual after every reboot to go to Settings, Sound, and test both channels, then flick the bottom of the phone and check the mic signal meter moves. About half of the time the settings application crashes before completing all 3 steps - retry the Settings application as necessary. Often times it auto swaps to a Ping rather than "Front left" - in which case playing with the Phone/default option may recover things, or a reboot or a ...

The problem is grave if:

- phone is more than 30 minutes in sleep state. Then incoming calls often cannot received and would not be signalled. It does not help to check mobile connection after boot. The problem comes up after deep sleep of the phone.

You can easily check this:
Take Your phone for one hour aside. Call from another phone to the Pinephone. Check if modem comes up before the call is lost.

My 2 cents......

[dukla2000]

...

You can easily check this:
Take Your phone for one hour aside. Call from another phone to the Pinephone. Check if modem comes up before the call is lost.

...

Works fine for me - could test this afternoon.

• Dialled my PinePhone using another phone
  
• PinePhone woke up, slowly screen appeared, wireless and network icons came back on home screen
  
• PinePhone started ringing
  
• Could log in and answer call
  

I am on 3 UK - seems YMMV!

Sadly have worked out it is beyond my skills to give watertight proof that this happened as the systemlog/dmesg times also stop when PinePhone is asleep - see man dmesg! What I do have is a picture of screen showing a call at 16:31 today:
   

Then I have some contiguous dmesg dump showing the phone was going into deep sleep (but as above my skills are unable to get a meaningful time from dmesg:

Code:

[ 1910.703707 <  580.972209>] PM: suspend entry (deep)
[ 1911.188699 <    0.484992>] Filesystems sync: 0.481 seconds
[ 1911.194322 <    0.005623>] Freezing user space processes ... (elapsed 0.009 seconds) done.
[ 1911.211770 <    0.017448>] OOM killer disabled.
[ 1911.215070 <    0.003300>] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1911.224126 <    0.009056>] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1911.495093 <    0.270967>] Disabling non-boot CPUs ...
[ 1911.496039 <    0.000946>] CPU1: shutdown
[ 1911.497534 <    0.001495>] psci: CPU1 killed (polled 4 ms)
[ 1911.501109 <    0.003575>] CPU2: shutdown
[ 1911.502324 <    0.001215>] psci: CPU2 killed (polled 0 ms)
[ 1911.505654 <    0.003330>] CPU3: shutdown
[ 1911.506783 <    0.001129>] psci: CPU3 killed (polled 0 ms)
[ 1911.509741 <    0.002958>] Enabling non-boot CPUs ...
[ 1911.511213 <    0.001472>] Detected VIPT I-cache on CPU1
[ 1911.511285 <    0.000072>] arch_timer: CPU1: Trapping CNTVCT access
[ 1911.511309 <    0.000024>] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 1911.512398 <    0.001089>] CPU1 is up
[ 1911.513227 <    0.000829>] Detected VIPT I-cache on CPU2
[ 1911.513269 <    0.000042>] arch_timer: CPU2: Trapping CNTVCT access
[ 1911.513285 <    0.000016>] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 1911.514071 <    0.000786>] CPU2 is up
[ 1911.514863 <    0.000792>] Detected VIPT I-cache on CPU3
[ 1911.514903 <    0.000040>] arch_timer: CPU3: Trapping CNTVCT access
[ 1911.514919 <    0.000016>] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 1911.515743 <    0.000824>] CPU3 is up

Last I have some contiguous journal output showing nothing between 15:54 and 16:30 when the call came in (my automatic suspend is 5 mins BTW). For sure really messy and not sure it sows much other than silence between 15:54:55 and 16:30:58 when the call started.

Code:

Nov 05 15:54:55 mobian phosh[2134]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Nov 05 15:54:55 mobian phosh[2134]: > Warning:          Unsupported maximum keycode 569, clipping.
Nov 05 15:54:55 mobian phosh[2134]: >                   X11 cannot support keycodes above 255.
Nov 05 15:54:55 mobian phosh[2134]: > Internal error:   Could not resolve keysym Invalid
Nov 05 15:54:55 mobian phosh[2134]: Errors from xkbcomp are not fatal to the X server
Nov 05 16:30:58 mobian pipewire[584]: [W][000000978.200766][main-loop.c:157 pw_main_loop_run()] main-loop 0x557f017d70: iterate error -4 (Interrupted system call)
Nov 05 16:30:58 mobian phoc[500]: event0  - gpio-keys: client bug: event processing lagging behind by 804ms, your system is too slow
Nov 05 16:30:58 mobian pipewire[570]: [W][000000978.208736][main-loop.c:157 pw_main_loop_run()] main-loop 0x559fc59c40: iterate error -4 (Interrupted system call)
Nov 05 16:30:58 mobian systemd[526]: Stopped target Bluetooth.
Nov 05 16:30:58 mobian phosh[2272]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Nov 05 16:30:58 mobian gnome-session[696]: gnome-session-binary[696]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at>
Nov 05 16:30:58 mobian gnome-session-binary[696]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Nov 05 16:30:58 mobian phosh[2272]: > Warning:          Unsupported maximum keycode 569, clipping.
Nov 05 16:30:58 mobian phosh[2272]: >                   X11 cannot support keycodes above 255.
Nov 05 16:30:58 mobian phosh[2272]: > Internal error:   Could not resolve keysym Invalid
Nov 05 16:30:58 mobian phosh[2272]: Errors from xkbcomp are not fatal to the X server
Nov 05 16:30:59 mobian systemd[526]: Reached target Bluetooth.
Nov 05 16:30:59 mobian phoc[500]: [backend/drm/drm.c:364] Failed to page-flip output 'DSI-1': a page-flip is already pending
Nov 05 16:31:09 mobian gnome-calls[1056]: g_string_assign: assertion 'rval != NULL' failed
Nov 05 16:31:10 mobian gsd-color[848]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Nov 05 16:31:12 mobian gsd-media-keys[873]: Unable to get default sink
Nov 05 16:31:12 mobian gsd-media-keys[873]: Unable to get default source
Nov 05 16:31:12 mobian phosh[737]: instance with invalid (NULL) class pointer
Nov 05 16:31:12 mobian phosh[737]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 05 16:31:24 mobian gsd-media-keys[873]: Unable to get default sink
Nov 05 16:31:24 mobian gsd-media-keys[873]: Unable to get default source
Nov 05 16:31:24 mobian phosh[737]: instance with invalid (NULL) class pointer
Nov 05 16:31:24 mobian phosh[737]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov 05 16:31:30 mobian gnome-calls[1056]: gtk_application_uninhibit: assertion 'cookie > 0' failed
Nov 05 16:31:30 mobian gsd-usb-protect[849]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.>
Nov 05 16:31:42 mobian gnome-calls[1056]: gtk_application_uninhibit: assertion 'cookie > 0' failed
Nov 05 16:31:42 mobian gnome-session[696]: gnome-session-binary[696]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at>
Nov 05 16:31:42 mobian gnome-session-binary[696]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Nov 05 16:31:42 mobian gsd-usb-protect[849]: Error calling USBGuard DBus to change the protection after a screensaver event: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.>
Nov 05 16:31:43 mobian phosh[2429]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Nov 05 16:31:43 mobian phosh[2429]: > Warning:          Unsupported maximum keycode 569, clipping.
Nov 05 16:31:43 mobian phosh[2429]: >                   X11 cannot support keycodes above 255.
Nov 05 16:31:43 mobian phosh[2429]: > Internal error:   Could not resolve keysym Invalid
Nov 05 16:31:43 mobian phosh[2429]: Errors from xkbcomp are not fatal to the X server
Nov 05 18:07:30 mobian pipewire[570]: [W][000001325.878730][main-loop.c:157 pw_main_loop_run()] main-loop 0x559fc59c40: iterate error -4 (Interrupted system call)

[as400]

Can someone give me the firmware version after the update ?

[Subsentient]

Can someone give me the firmware version after the update ?

It's "EG25GGBR07A08M2G_01.002.07".

Code:

[   47.103128] modem-power serial1-0: ===================================================
[   47.111081] modem-power serial1-0: Project Name: EG25G
[   47.116310] modem-power serial1-0: Project Rev : EG25GGBR07A08M2G_01.002.07
[   47.123295] modem-power serial1-0: Branch  Name: 9x07_R07_NEW
[   47.129716] modem-power serial1-0: Custom Name : STD
[   47.135415] modem-power serial1-0: Build   Date: 2020-06-13,09:14
[   47.141673] modem-power serial1-0: Version:    SBLR07EG25G01_1:37500: May 30 2
[   47.148673] modem-power serial1-0: Version:    TZR07A03: Dec  2 2019
[   47.154786] modem-power serial1-0: Version:    RPMR07A03_1:37500: Dec  2 2019
[   47.161666] modem-power serial1-0: ===================================================
[   47.180505] modem-power serial1-0: ADB KEY is '74836969' (you can use it to unlock ADB access to the modem, see https://xnux.eu/devices/feature/modem-pp.html)
[   48.240483] modem-power serial1-0: QDAI is '1,1,0,1,0,0,1,1'
[   48.256432] modem-power serial1-0: QCFG 'risignaltype' is '"physical"'
[   48.276508] modem-power serial1-0: QCFG 'urc/ri/ring' is '"pulse",1,1000,5000,"off",1'
[   48.296452] modem-power serial1-0: QCFG 'urc/ri/smsincoming' is '"pulse",1,1'
[   48.316442] modem-power serial1-0: QCFG 'urc/ri/other' is '"off",1,1'
[   48.332436] modem-power serial1-0: QCFG 'urc/ri/pin' is 'uart_ri'
[   48.348475] modem-power serial1-0: QCFG 'urc/delay' is '0'
[   48.364474] modem-power serial1-0: QCFG 'sleepind/level' is '0'
[   48.384492] modem-power serial1-0: QCFG 'wakeupin/level' is '0,0' (changing to '0')
[   48.424734] modem-power serial1-0: QCFG 'ApRstLevel' is '0'
[   48.440450] modem-power serial1-0: QCFG 'ModemRstLevel' is '0'
[   48.456482] modem-power serial1-0: QCFG 'apready' is '0,0,500'
[   48.476460] modem-power serial1-0: QCFG 'airplanecontrol' is '1,0'
[   48.493228] modem-power serial1-0: QCFG 'fast/poweroff' is '1'

[dukla2000]

Can someone give me the firmware version after the update ?

The version on the documentation that is downloaded from OP is V0708_01.002.01.002 dated 2020-06-18. In section 1 of the Release Notes it says EG25GGBR07A08M2G_01.002.01.002 being an upgrade from EG25GGBR07A08M2G_01.001.01.001

Not sure if the s/w has enough oomph to admit what it is - happy to ask mine if you say how.

[as400]

@Subsentient what tool are you using to get that info ?

[Subsentient]

@Subsentient what tool are you using to get that info ?

It's the output from dmesg, on a 5.9.6 Megous kernel.

[as400]

THX. I had to increase loglevel to get these messages.

And it says that latest known firmware is 01.002.07 - "Consider updating "



EDIT:

Upgrade went smoothly - thanks for this.