Quote:
Originally Posted by NiLuJe
@mkozlows: Check the logs, my wild guess would be poor connectivity making the initial connection attempt fail, as there's no retry in these cases.
|
When you say "no retry", do you mean "no retry after fail until Wifi is manually connected"? Because that matches what I see: On 7/6, when I went on a trip, I see a "restore-wifi-async.sh: Failed to connect to preferred AP!" message (which makes sense, there was no Wi-Fi enabled on the airplane), and then it never tries to connect on wake-up from there on out:
Code:
07/13/22-18:00:57 INFO Kobo suspend: ZzZ ZzZ ZzZ... And woke up!
07/13/22-18:00:57 INFO Kobo resume: clean up after wakeup
07/13/22-18:00:57 INFO Kobo resume: successfully asked the kernel to resume subsystems
07/13/22-18:00:57 INFO Restoring user input handling
GET https://sync.koreader.rocks:443/syncs/progress/54255d2149fbf92b1341a73db2265c3c
host or service not provided, or not known
PUT https://sync.koreader.rocks:443/syncs/progress
host or service not provided, or not known
07/13/22-18:04:25 INFO WakeupMgr: scheduling wakeup in 259200
07/13/22-18:04:25 INFO Inhibiting user input
07/13/22-18:04:41 INFO Kobo suspend: going to sleep . . .
... until I manually connect the network, and then it automatically reconnects on wake from then on.
This behavior surprises me. Is there a reason it doesn't try on every wake, regardless of prior failures?