1.23 Quick suspend/resume updates break phone use case

For 1.23 quick suspend/resume is updated with the following commit: c592cde3

This will break the phone use case, as it will take a significant amount of seconds to resume the modem when a call comes in, resulting in lost calls.

Tagging @dylanvanassche from original quick suspend/resume implementation

The updates are probably not bad by itself, but the original purpose of quick suspend/resume should definitely be retained in my opinion.

This is also blocking a patch I made on top of 1.22 where the unsolicited events are disabled during quick sleep, allowing phones to suspend but still wake up for calls/sms.

@aleksm Can we put this feature behind another CLI flag? I did not put things in low power as the modem needs to fully be awake for calls & texts.

Please note, the change referenced to use low-power mode during suspend in addition to the quick suspend/resume logic is already behind its own flag.

The original quick suspend/resume logic is triggered with the --test-quick-suspend-resume option.

The new low-power and quick suspend/resume logic is triggered with the --test-low-power-suspend-resume option.

These options are mutually exclusive.

Please let me know if this is not working as intended. postmarketOS and other phone OS should still use --test-quick-suspend-resume.

closed