Latest firmware for PinePhone modem!

[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)