In reading the release notes on Github (Rev. EG25-G-GB_Firmware_Release_Notes_V0708_01.003.01.003), it seems like it has enough "Solved the problem..." entries (bug fixes) to make flashing it a worthwhile wager. I'm not so much worried about the actual flashing of the device as I am worried about maintaining all the modem settings or resetting them all correctly afterwards.
I did some mmcli tests and it looks like I can use mmcli to sent AT commands to archive current setting values and restore them afterwards, if necessary.
I do have some questions though.
1. Why all the howto elsewhere about shorting the test points or using ADB? From this thread, it seems that many Pinephone users have successfully updated modem firmware without using the test points or ADB.
2. Why is 01.002.01.002 the "default" branch on Github when 01.003.01.003 is available?
3. I'm running Mobian stable. Does it have Megi's kernel / driver code?
Any suggestions, warnings or final advice would be most appreciated!
-Cal
I did some mmcli tests and it looks like I can use mmcli to sent AT commands to archive current setting values and restore them afterwards, if necessary.
I do have some questions though.
1. Why all the howto elsewhere about shorting the test points or using ADB? From this thread, it seems that many Pinephone users have successfully updated modem firmware without using the test points or ADB.
2. Why is 01.002.01.002 the "default" branch on Github when 01.003.01.003 is available?
3. I'm running Mobian stable. Does it have Megi's kernel / driver code?
Any suggestions, warnings or final advice would be most appreciated!
-Cal