Troubles staying on network?

[2disbetter]

I am happy to see some discussion on this issue that shows they are making progress. Seems the suspending of components and resuming is the issue, ONLY if the suspending process is not successfully completed.

I have a script running automatically to reset the modem when it notices that it drops, but it isn’t super reliable. So I am using the following command to do it manually. This seems to work better anyway.

echo 0 | sudo tee /sys/class/leds/wwan_en/brightness; sleep 5; echo 1 | sudo tee /sys/class/leds/wwan_en/brightness

[rpm]

At this point I wish my issue was connected to power management, but starting up fresh it can’t even get on the LTE network happy and it was running really well for almost 2 months?

The lines that have to be a hint are:

[modem1] 3GPP registration state changed (home -> searching)
[modem1] couldn't load operator code: Current operator MCC/MNC is still unknown
[modem1] couldn't load operator name: Current operator id is still unknown

I guess I’ll write support tomorrow about this.

[tomoqv]

I am reposting this question as I did not get any response earlier.

@tomoqv

I would like to know where most of the challenges with the modem performance lie. Is it

1. In the modem software
2. In the Linux kernel
3. In PureOS
   I guess it is a combination of the above, but are there hurdles that are out of Purism’s control to fix or is it a matter of more devs and time on their/our part in order to sort it?