(08-12-2021, 02:53 AM)dukla2000 Wrote: A few days ago I added my experience to the issue on the Pine64-arch git and was "nudged" that the modem-vanishing "trick" was more of a problem with 01.003.01.003. So I flashed 01.002.01.002 about 36 hours ago and since then have been running arch without a hiccup.
I just had a quick check through my journal and it seems the eg25manager code to regularly try recover the modem works as intended with 01.002.01.002 and (my suspicion) does not work with arch & 01.003.01.003?
YMMV
Thank you for your post here and on the Pin64-arch git, dukla2000!
In checking my journal, I'm seeing the same failure. Sometimes eg25manager recovers the modem (even with 01.003.01.003) but sometimes it does not recover it. Strangely, the xgps ap, from the gpsd-clients package, has not worked for me for quite a while (on Mobian). It stopped working with the original 01.001.01.001 firmware weeks or months ago but I don't use it much (because my GPS works so poorly as to be pretty much worthless, even after seeding positional data with the load_agps_data.py "proof of concept" script) and I didn't realize that xgps was bringing the modem down. I now see that it quite reliably removes the modem from my system, requiring a phone reset.
Many months ago, when I first install gpsd-clients, it worked. It was not what caused my 01.003.01.003 firmware modem removal yesterday when I attempted to place an inbound call to a sleeping phone, however.