Today i’ve tested suspend automatic while on battery power.
That is not working for me.
I waited to let suspend mode activate, next I called the L5 from another phone. The phone did not wake up (voicebox answered the call) and after manually waking up the phone the connection was gone.
Ok and thank you for reporting back on the issue.
Okay. I consider that one satisfactorily explained. 
Another firmware updated here. I’ve noticed that the “automatic suspend” (on settings) and the “suspend now” (on the mobile settings app) behave differently: when automatically suspended a call wakes up the phone but it doesn’t ring, and I have to cycle the modem in order to make it work again, while when manually suspended it wakes up and rings. So apparently they are not the same. Anyway, another step ahead.
3 Likes
I’m facing the same: more crashes of the modem. I produced months before the following script:
#!/bin/sh
# from https://source.puri.sm/Librem5/linux-next/-/issues/303
#
# Clayton Craft @craftyguy
# Contributor
#
# I've been using the following script to "recover" the modem when it
# disappears, it seems to work every time for me:
set -x
sudo rmmod xhci_plat_hcd xhci_hcd
echo 0 | sudo tee /sys/class/leds/wwan_en/brightness
sleep 2
sudo modprobe xhci_plat_hcd
sleep 5
echo 1 | sudo tee /sys/class/leds/wwan_en/brightness
# added by guru@unixarea.de
#
sleep 5
sudo systemctl restart ModemManager
@tomoqv, et all: due to the fact that this is perhaps not caused by the now working suspend, but at least happens now more often to me, I will creat a new threat for this problem of crashing modem firmware.
Can the Purism team remove this notification, or provide a way to disable it via Gnome Settings please? It makes the notification LED completely useless, as it blinks after it goes into suspend that there is a notification, and it also forwards notifications to connected devices that are not relevant to notify the owner of (e.g. PineTime, Kodi, KDE Connect, etc…)
Today I got the upgrade to kernel 6.2.0-1-librem5. This is not the kernel with the additions of @dos that make suspend work, right? What version is to be expected that has this work for suspend?
I can add that since the upgraded modem firmware, my mobile data (while wifi off with HKS) no longer comes back after suspend unless I reset the modem or power cycle it. It doesn’t seem to matter if I wait a few minutes, data connection refuses to reestablish.
EDIT: It turns out that when the modem reappears after suspend, I also quite often need to power cycle the modem in order to make a phone call. Otherwise, the Calls app is stuck at “Ringing…” and nothing happens even though indicator shows “connected” and 4G/3G etc.
Please always specify what version of modem firmware it is…to track the bug.
M100E_YCSN0_1.0.0_220926
YCSN0_M100E_1BAD_3117_V1.0.0.2_20220930
M100E_1.0.4_200715
2 Likes
guru/modemFirmwareVersion.sh
+BMSWVER: M100E_YCSN0_1.0.0_220926,YCSN0_M100E_1BAD_3117_V1.0.0.2_20220930,M100E_1.0.4_200715
There are several components needed for it to work that haven’t arrived yet, it’s not just the kernel.
Modem firmware version is irrelevant (except for the wake signal itself, as I mentioned above multiple times).
1 Like
OK. My L5 wakes up always from suspend on incoming calls and satisfies the firmware version you have suggested above. So I wait for the components needed.
Is it possible to have a crude estimate of when all the missing pieces will be available? Maybe in May 2023?
Purism tracked your wish, it already out, just apt upgrade. Enjoy.
2 Likes
New phosh 0.27.0 isn’t on the appstore yet
1 Like
The change mentioned above is not related to phosh.
1 Like
I keep checking suspend after every update. Recently I have noticed this behavior: my L5 always wakes up from suspend when there is an incoming call. Most of the time it does nothing else (no clue there is an incoming call). But there are sometimes that the calls appear systematically correct and works fine until a new reboot will put it again in the state of doing nothing more than waking up.
An orange exclamation mark on the 4G signal strength is always there when it recovers from the suspend state.
One more thing. When it comes up from suspend it often displays a notification about the memory card I have (being mounted I guess).
Set up to “4G only” from mobile setting… try again.
HowTO:
Turn off GSM HKS, turn ON GSM HKS, after 10 sec, set up to 4G-only.