7 Commits (5dbeddd2a145320b9cc630908a1d89ebb0c24b44)

Author	SHA1	Message	Date
yparitcher	5dbeddd2a1	Wifi: toggle when connected even if offline (#8468)	3 years ago
NiLuJe	dffe86dfe9	Cleanup eye-gouging madness around io.read calls (#7149) ... * Don't reinvent the wheel when reading a one-line int or string from sysfs * Simplify a whole other bunch of read calls	3 years ago
NiLuJe	b119e29218	NetworkActivity: Fix an exceedingly unlikely crash. ... If you're *extremely* unlucky, the scheduled check might run *right* after a wakeup, before the network interface is up. So, you have a previously stored packet count, but the new one is nil. Boom.	3 years ago
NiLuJe	2ad976387d	More #6424 cleanups (#6442) ... * Simplify logic, and more detailed debug logging * Kill Nickel's FIFO on startup Avoids udev/udhcpc scripts hanging when trying to open() it.	4 years ago
NiLuJe	744e933036	Minor cleanups after #6424 (#6438) ... * Minor cosmetic code cleanup * String tweak	4 years ago
NiLuJe	37a01100b7	Various Wi-Fi QoL improvements (#6424) ... * Revamped most actions that require an internet connection to a new/fixed backend that allows forwarding the initial action and running it automatically once connected. (i.e., it'll allow you to set "Action when Wi-Fi is off" to "turn_on", and whatch stuff connect and do what you wanted automatically without having to re-click anywhere instead of showing you a Wi-Fi prompt and then not doing anything without any other feedback). * Speaking of, fixed the "turn_on" beforeWifi action to, well, actually work. It's no longer marked as experimental. * Consistently use "Wi-Fi" everywhere. * On Kobo/Cervantes/Sony, implemented a "Kill Wi-Fi connection when inactive" system that will automatically disconnect from Wi-Fi after sustained *network* inactivity (i.e., you can keep reading, it'll eventually turn off on its own). This should be smart and flexible enough not to murder Wi-Fi while you need it, while still not keeping it uselessly on and murdering your battery. (i.e., enable that + turn Wi-Fi on when off and enjoy never having to bother about Wi-Fi ever again). * Made sending `NetworkConnected` / `NetworkDisconnected` events consistent (they were only being sent... sometimes, which made relying on 'em somewhat problematic). * restoreWifiAsync is now only run when really needed (i.e., we no longer stomp on an existing working connection just for the hell of it). * We no longer attempt to kill a bogus non-existent Wi-Fi connection when going to suspend, we only do it when it's actually needed. * Every method of enabling Wi-Fi will now properly tear down Wi-Fi on failure, instead of leaving it in an undefined state. * Fixed an issue in the fancy crash screen on Kobo/reMarkable that could sometime lead to the log excerpt being missing. * Worked-around a number of sneaky issues related to low-level Wi-Fi/DHCP/DNS handling on Kobo (see the lengthy comments [below](https://github.com/koreader/koreader/pull/6424#issuecomment-663881059) for details). Fix #6421 Incidentally, this should also fix the inconsistencies experienced re: Wi-Fi behavior in Nickel when toggling between KOReader and Nickel (use NM/KFMon, and run a current FW for best results). * For developers, this involves various cleanups around NetworkMgr and NetworkListener. Documentation is in-line, above the concerned functions.	4 years ago
yparitcher	70f89c4df1	ReaderGesture: cleanup (#6292) ... convert all gesture actions to use events for better modularity add network event handlers and device event handlers	4 years ago