|
Hi sladflob!
KOReader uses the same daemon to connect to wifi that nickel uses: that's wpa_supplicant. Internally wpa_supplicant see three different APs. Nickel (and most other gui programs) just displays the AP with more tx power (usually the nearest) while KOReader is reporting the three. That shouldn't affect the behaviour of wpa_supplicant (ie: once connected it should roam fine between aps on both programs)
The code paths you mentioned are somehow platform specific and I don't have a kobo since a few years ago, so bear with me if I miss the point:
As far as I can remember, we will try to repurpose wpa_supplicant configuration from nickel. That's the original implementation. Years after that a proper discovery prompt was addded.
I'm afraid that your two code paths are triggering these two different behaviours and I *think* that you can try to remove "network.lua" in /mnt/onboard/.adds/koreader/settings. This way the second codepath shouldn't apply and, IIRC, nickel wpa_supplicant will be used.
Please keep us informed.
|