[craftkiller]

> Looks like you didn't enable the suspend

This was with the default settings after flashing Crimson (which I did to recover from the infinite boot loop), so if there is some active step that needs to be taken to enable suspend, then I had not done it.

> When was it?

This was within the past month. I see two possible reasons you didn't run into it:

1) You have been applying the updates as they come out, whereas I took a dusty phone that hadn't been turned on in years and ran the update.

2) You were already on crimson, so maybe they only broke byzantium (or whatever version it was on from years of sitting unused and then hitting update in the software center).

[fsflover]

> This was with the default settings after flashing Crimson

This is strange. See this post concerning the battery life: https://puri.sm/posts/librem-5-battery-life-improved-by-100/. Have you updated the modem firmware?

You are right, I have case 1). It is quite likely that Byzantium is (was) much less stable, as it required a lot of hacks and relied on a very old Debian version.

[craftkiller]

I had some time to check today, and it seems the suspend feature is disabled by default. I just enabled it so I'll see how that goes. Thanks!

> Have you updated the modem firmware?

Nope, but I just looked it up and Purism's site states:

"These files are controlled by a third-party and are not publicly accessible. Contact Purism Support to request these files for a firmware update"

Yikes....