I flashed 01.003.01.003. After completion and the programmed modem reset I restarted the phone and made one outgoing test call and one inbound test call successfully. Then I let the phone go to sleep and tried another inbound call. The phone never rang or came out of sleep. When I pushed the power button to wake up the phone, the modem had crashed (no mobile annunciation on the top status strip and no modem in the Setting ap, etc.
As usually a phone reset brought the modem back to life and I restored the following settings that had changed after flashing the new firmware to match their values before I had flashed 01.003.01.003.
< lines are original settings
> lines are post flash settings, which I wrote over to match original settings.
Next I tried another inbound call to my sleeping pinephone. It rang on the third outbound phone ring tone and the call was completed successfully.
However, I've now had a second crash of the modem while testing to see if the GPS would function (it usually doesn't function), resulting in a loss of the modem from the system again and another phone reset was required to restore modem functionality. This is a problem that has always plagued my phone, but these two failures were within only about 20 minutes of use, which is an exceptionally poor failure rate. It usually only happens every few days or even only after a week or two.
I'll use 01.003.01.003. for a while and then I'll try 01.002.01.002.
Finally, though certainly convenient, the lack of enforcement of the requirement to use the test points or ADB is strange. Perhaps it's some kind of security feature bug?
As usually a phone reset brought the modem back to life and I restored the following settings that had changed after flashing the new firmware to match their values before I had flashed 01.003.01.003.
< lines are original settings
> lines are post flash settings, which I wrote over to match original settings.
Code:
< response: '+QCFG: "wakeupin/level",0'
---
> response: '+QCFG: "wakeupin/level",0,0'
11c11
< response: '+QCFG: "ModemRstLevel",0'
---
> response: '+QCFG: "ModemRstLevel",1'
13c13
< response: '+QCFG: "airplanecontrol",1,0'
---
> response: '+QCFG: "airplanecontrol",0,0'Next I tried another inbound call to my sleeping pinephone. It rang on the third outbound phone ring tone and the call was completed successfully.
However, I've now had a second crash of the modem while testing to see if the GPS would function (it usually doesn't function), resulting in a loss of the modem from the system again and another phone reset was required to restore modem functionality. This is a problem that has always plagued my phone, but these two failures were within only about 20 minutes of use, which is an exceptionally poor failure rate. It usually only happens every few days or even only after a week or two.
I'll use 01.003.01.003. for a while and then I'll try 01.002.01.002.
Finally, though certainly convenient, the lack of enforcement of the requirement to use the test points or ADB is strange. Perhaps it's some kind of security feature bug?
