Kindle: Add wifi selector#12056
Conversation
…#12038) This prevents the current directory from appearing in the listing.
|
Found a bug where my lipc handle commits suicide 😅 probably a bug in my underlying library |
Screenshot dialog could not be interacted with in Text editor. Closes koreader#12066.
We can't actually tell whether anything happened, good or bad, so don't let it kill the potentially in-progress attempt. We lose the notifications if you force the scan list via a long-press, but that's another kettle of fish... None of this was really designed for an async backend ;).
It gets a biiit clunkier ;).
|
Whatever magic you did @NiLuJe seems to have fixed it, i assume it has to do with not letting enableWifi abort the connection since that's the only thing i didn't try, thanks! |
|
I have a bunch of other changes to test, FWIW, because there's some stupidity left-over from #10669 that ties into that very change ;). (It's also not really Kindle-specific, I'm pretty sure that scan window leads to funky stuff pretty much everywhere...). |
|
Oh btw for |
I think you're supposed to, yeah. I'm pretty sure we only use that to pre-fill the password input field; and we will save that in plaintext, FWIW. |
This comment was marked as outdated.
This comment was marked as outdated.
Long time no update. A lot of changes.
Co-authored-by: Frans de Jonge <fransdejonge@gmail.com>
|
(Commit history archived in the kindle-wifi-ui-openlipc branch ;). |
|
@notmarek Also, this one is a simple username/password UI? |
|
It's the standard UI, and behaves roughly like the stock ones, i.e., unless it can connect to a previously setup preferred netwokr, you get shown a network list. And, indeed, eduroam would require manual labor to setup ;). (My only experience with eduroam was quite a few years ago on macOS, so things may be slightly less ridiculous nowadays. But, FWIW, I'd never done that on an eReader, it was usually faster to setup a Wi-Fi hotspot on my phone). |
Can I see network list even with existing network? I noticed I have a very weird thing. Kindle connects to a different network that I probably accidentally hit one day. While in KOReader, I turn on Wi-Fi, then it connects to this stupid network and I need to quit and setup eduroam all over again :D This PR could have helped me save a few steps. I vaguely remember something about /var/local/ folder and wpa-supplicant files I needed to wipe to forget all networks. Are there any gentler ways to forget networks on Kindle? :D |
|
A long-press on the Wi-Fi menu entry will force the scan list to display (it won't prevent the connection attempt to go through, though, so you'll see the preferred network as "connected". Even though, on Kindle, it's sort of not actually entirely connected yet ^^). I imagine you can forget about networks in the stock WiFi setting, though. |
|
|
Lol, I figured out how to forget networks in Kindle. After it is connected, hit it again, and it will ask to forget the network xD |
|
I found a cosmetic bug. |
|
probably a kindle bug since the info is grabbed straight from lipc
…On Tue 2. 7. 2024 at 16:27, mergen3107 ***@***.***> wrote:
I found a cosmetic bug.
I was at home, connected to home network OK.
Then went to school with eduroam, and it said that it is connecting to
home network, but actually connected to eduroam OK.
—
Reply to this email directly, view it on GitHub
<#12056 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANZQHJWL4EPIZ7YJ46FIVXDZKK2FLAVCNFSM6AAAAABJUF7V3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBTGM3DSMZWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I still can't find a way to bring up a list of networks (Kindle Scribe).
|
|
I don't think there's a forget button in koreader, otherwise I would've
implemented it too
…On Fri 28. 6. 2024 at 19:05, mergen3107 ***@***.***> wrote:
Lol, I figured out how to forget networks in Kindle. After it is
connected, hit it again, and it will ask to forget the network xD
—
Reply to this email directly, view it on GitHub
<#12056 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANZQHJUBKBUW2JGPW3JFBK3ZJWJXFAVCNFSM6AAAAABJUF7V3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGMZTOMBYGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@notmarek |
Oops, it seems network actually did not connect the second time :D |
|
OK, so some mysteries. I don't remember if that starting happening with this PR though.
|
|
We don't do anything, it's all wifid. |
* Kindle: Implement a NetworkMgr backend loosely based on WpaClient in order to allow feature-parity with hasWifiManager platforms. This involves dealing with the native wifid over lipc (the native IPC system, based on DBus), through custom Lua bindings (https://github.com/notmarek/openlipclua), since the stock ones lack support for the needed hasharray data type. * NetworkMgr: Clear up leftover hallucinations from koreader#10669, making `enableWifi` much simpler (and much more similar to `turnOnWifiAndWaitForConnection`). * NetworkMgr: Made it clearer that `turnOnWifi` implementations *must* deal with `complete_callback`, as part of the aforementioned changes mean that it's *always* wrapped in a connectivity check, and we need that for proper event signaling. * Android, Emu: Run `complete_callback` properly in `turnOnWifi`. * Kindle: Support `powerd:isCharged()` on the PW2 (yes, this is random, it just happened to be my test device :D). * NetworkMgr:disableWifi: Properly tear down any potential ongoing connection attempt (e.g., connectivity check). * NetworkMgr:promptWifi: Make the "wifi enabled but not connected" popup clearer if there's an ongoing connection attempt, and gray out the "Connect" button in this case (as it would only lead to another "connection already in progress" popup anyway). * NetworkMgr:reconnectOrShowNetworkMenu: Make *total* scanning failures fatal (they will lead to an immediate wifi teardown). * NetworkMgr:reconnectOrShowNetworkMenu: Clear up the long-press behavior (which *always* shows the network list popup) so that it doesn't weirdly break all the things (technical term!). * NetworkMgr:reconnectOrShowNetworkMenu: When we manage to connect to a preferred network on our own *before* showing the network list, make sure it is flagged as "connected" in said list. * NetworkMgr:reconnectOrShowNetworkMenu: Make connection failures fatal in non-interactive workflows (they'll lead to a wifi teardown). * NetworkSetting (the aforementioned network list widget): Clear NetworkMgr's "connection pending" flag on dismiss when nothing else will (i.e., when there's no connectivity check ticking).
* Kindle: Implement a NetworkMgr backend loosely based on WpaClient in order to allow feature-parity with hasWifiManager platforms. This involves dealing with the native wifid over lipc (the native IPC system, based on DBus), through custom Lua bindings (https://github.com/notmarek/openlipclua), since the stock ones lack support for the needed hasharray data type. * NetworkMgr: Clear up leftover hallucinations from koreader#10669, making `enableWifi` much simpler (and much more similar to `turnOnWifiAndWaitForConnection`). * NetworkMgr: Made it clearer that `turnOnWifi` implementations *must* deal with `complete_callback`, as part of the aforementioned changes mean that it's *always* wrapped in a connectivity check, and we need that for proper event signaling. * Android, Emu: Run `complete_callback` properly in `turnOnWifi`. * Kindle: Support `powerd:isCharged()` on the PW2 (yes, this is random, it just happened to be my test device :D). * NetworkMgr:disableWifi: Properly tear down any potential ongoing connection attempt (e.g., connectivity check). * NetworkMgr:promptWifi: Make the "wifi enabled but not connected" popup clearer if there's an ongoing connection attempt, and gray out the "Connect" button in this case (as it would only lead to another "connection already in progress" popup anyway). * NetworkMgr:reconnectOrShowNetworkMenu: Make *total* scanning failures fatal (they will lead to an immediate wifi teardown). * NetworkMgr:reconnectOrShowNetworkMenu: Clear up the long-press behavior (which *always* shows the network list popup) so that it doesn't weirdly break all the things (technical term!). * NetworkMgr:reconnectOrShowNetworkMenu: When we manage to connect to a preferred network on our own *before* showing the network list, make sure it is flagged as "connected" in said list. * NetworkMgr:reconnectOrShowNetworkMenu: Make connection failures fatal in non-interactive workflows (they'll lead to a wifi teardown). * NetworkSetting (the aforementioned network list widget): Clear NetworkMgr's "connection pending" flag on dismiss when nothing else will (i.e., when there's no connectivity check ticking).
#12040, this is not final, i still need to add https://github.com/notmarek/openlipclua to the base, and i have no idea how to go about it
This change is