In the context of software development methodology, yes, rapid.
1 Like
Exactly, there is actually quite a bit or development going on by a couple of people working for Purism. I see updates quite frequently. IN fact, the recent Phosh update fixed the only resuming from suspend bug I was experiencing. For my purposes this makes suspend completely useful to me. I would prefer my cellular modem off when the phone in standby mode, but I understand why everyone else wants it on.
With the work Purism is doing, the concept of a phone that is your main computer is becoming more and more real each day. I am truly astounded that Purism, with so little experience in developing such a thing, has learned so much, and is doing the darn thing.
4 Likes
Here is a new one: trying to unlock my sim card after a suspend now results in a time out. Restarting the phone didnāt work at first. Only after I switched off the suspend mode, restarting the phone resulted in being able to unlock the sim card. That firmware update might not have done the job.
1 Like
Iāve disabled suspend. Telegram and signal stop responding after waking.
EDIT: unrelated to suspend but something else post latest updates.
Itās too subjective for the meaning of ārightā when you say āget the android rightā. Letās assume they got it ārightā by the time it was the best selling smartphone OS.
While there was a previous Open Handset Alliance associated with Android, Google didnāt get involved until later. Googleās efforts were unveiled in November 2007 ā¦ with its first phone released/sold to the public in September 2008. There was basically a one year wait. By 2011, Android was the best selling OS on smartphones. So ā¦ 3 years after first release and 4 years after announcement.
Right, but for example it wasnāt until 2015 when they got Doze introduced.
I will grant that itās sort of apples & oranges because the perspective for āoperationalā that exists today didnāt exist back then, so battery life wasnāt the concern back then that it is today. Further, one doesnāt know what is capable until itās been achieved. But the point is that it took a long time for all-powerful google to get Android to where it is today. Using the same timeline, the L5 is cooking right along.
But, I mean, the whole discussion is subjective. āLong timeā is subjective. So is ārapid.ā 
Battery life on Android was fine even before Doze. My wife and kids had Nexus 5ās which were in 2013 and the battery life was 1.5 days under light use.
I disagree. Frankly your āit took a long timeā is a specious argument that could be applied to anything where there are constant improvements.
Again, I will point out that it took Android only 3 years from āfirst releaseā to become the best selling OS on smartphones. Compared to that pace the L5 is not ācooking right alongā.
I canāt argue with that. 
Sure, out of context.
ā¦which is important here because your argument is a non-sequitur. Itās like saying ājet fighter development is slow because biplanes were able to fly in a fraction of the time.ā
1 Like
I tested manual suspend yesterday (using the āmobile settingsā app).
Today I tested the automatic suspend, and it did not run so well. Power settings are : black screen after 1 minute, auto suspend on battery only after 2 minutes. Wifi off by HKS.
On wake up, I add a lot of āorange exclamation mark on signal strength iconā situations.
Sometimes, it works again after toggling the mobile data, but often it did not recover until I toggle the modem HKS.
Sometimes, the exclamation mark disappears, but I do not have connectivity. In this situation, wwan is in an UNKNOWN state, and setting the interface up or down do not change anything:
In this situation :
- SMS are received, but did not fire any ring/alert (I found them after reboot)
- Call trigger a ringā¦ but aborting the call after a few ring leads to endless ring on the librem5. It ends up after a long timeout, but cannot receive any call after. It shows cellular OFF in the top drop menu, and I cannot click the icon anymore. dmesg shows nothing.
journalctl show that the modem was marked as invalid after the timeoutā¦
Mar 08 22:44:40 pureos ModemManager[888]: <warn> [modem1] couldn't load call list: Serial command timed out
Mar 08 22:44:40 pureos ModemManager[888]: <warn> [modem1] port ttyUSB1 timed out 8 consecutive times
Mar 08 22:44:45 pureos ModemManager[888]: <warn> [modem1] port ttyUSB1 timed out 9 consecutive times
Mar 08 22:44:48 pureos ModemManager[888]: <error> [modem1] port ttyUSB1 timed out 10 consecutive times, marking modem avalid
Mar 08 22:44:48 pureos NetworkManager[634]: <info> [1678311888.3476] device (ttyUSB1): state change: prepare -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Mar 08 22:44:48 pureos mmsdtng[938]: ../plugins/modemmanager.c:mmsd_modem_unavailable() Disabling Bearer Handler
Mar 08 22:44:48 pureos mmsdtng[938]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaab084edd40 handler (nil)
Mar 08 22:44:48 pureos mmsdtng[938]: ../plugins/modemmanager.c:mmsd_disconnect_from_sms_wap() Stopping watching SMS WAPs
Mar 08 22:44:48 pureos mmsdtng[938]: ../plugins/modemmanager.c:mmsd_mm_state() Modem vanished, Disabling plugin
Mar 08 22:44:48 pureos mmsdtng[938]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MODEM
Mar 08 22:44:48 pureos mmsdtng[938]: ../plugins/modemmanager.c:cb_object_removed() Modem removed: /org/freedesktop/ModemManager1/Modem/1
Mar 08 22:44:48 pureos NetworkManager[634]: <info> [1678311888.3553] manager: NetworkManager state is now DISCONNECTED
After another sleep/resume, modem did reattach, but as Modem 2:
Mar 08 22:59:02 pureos mmsdtng[938]: ../plugins/modemmanager.c:mmsd_mm_add_object() Added device at: /org/freedesktop/ModemManager1/Modem/2
When exclamation mark is present, interface is DOWN, and it goes to UNKNOWN if I try to set it up:
- What is the best way to contribute to solve / document / help this issue ?
- Is there an automated ābug reportā process, maybe a script or an application to collect all usefull logs ? (I saved the full journalctl, the most relevant)
- What are all the related projects in puri.sm gitlab ? (I can fill an issue with as much debug information as needed)
Purism already know pretty much everything on modem issues, the problem is that any modem it is propietary blackbox hardcoded things, this modem come with obsolete linux version inside, so this blackbox modems complaints everything making a lot troubles in gnu+lnx ecosystems. that is why gnu fsf it recommend do not gaming with firmware blobs
I recommend keeping an updated das-uboot in ur Purism Librem 5 to kill some bugs.
At the moment suspend is still considered experimental and thereās little point in documenting all these issues as a lot still needs to be done for it to even have a chance to work reliably.
3 Likes
I pretty much have abandoned using it until itās further along. Iām just being more cognizant of the battery state and managing it accordingly.
2 Likes
@dos Could you give us a rough outline of what there is still to be done for suspend to work properly?
I follow the suspend related issues on gitlab, but Iām positive that Iām not aware of all the missing pieces.
1 Like
Fixing modemās USB resets, preventing QMI CID reset on suspend, adding more steps to MMās quick sync (call and message list), solving caam_jr issue, getting modemās USB device suspended with remote wakeup enabled to not reset upon resume, reducing MMC post-power up delay without breaking Redpine cards, letting Redpine cards shut down during suspend, having MM correctly handle modem enumeration with PDP context active, fixing NM autoconnect of WWAN profile after connection failureā¦
Some of them already have possible solutions, but theyāre very very fresh (literally a product of last days) 
12 Likes
If it were easy everyone would be doing itā¦lol.
2 Likes
Thank you!
So many things to do, yet not much manpower. I hope that you will be able to find adequaquate solutions in reasonable time without stressing yourself 
2 Likes
Any news on the suspend function? It still says that it is experimental. But I am just curious how things are coming alongā¦
1 Like
I have been using the suspend function for several month continuously (~6MO) and more recently (last month maybe) the cellular modem dropping out issues, or not being able to bring the modem back up have improved a lot. Occasionally the modem does not come back up, but when toggling the wwan modem switch it does. That said i am also running the watch modem script that will re-initiate the modem if it detects it disappearing and generate a warning audio notification, but i havenāt received as many notifications of the modem doing so lately, with phone suspended, or not suspended and just sitting there on a charger (where my suspend delay is much longer, than for battery suspend delay).
Getting SMS messages and message notifications while suspended i think almost works, not sure about calls.
3 Likes
Thanks, Captain. Maybe I will give it another try one of these days. It would be nice if it was totally reliable. Meanwhile battery life of the L5 is pretty decent by now as well. So I can live without suspend most of the time.
I have found it works but most people do not have the patience to wait until you answer your phone while it wakes from slumber so thatās an issue. I have found that SMS is mostly reliable but not sure about other things like Signal messages for example.
1 Like