Quote:
Originally Posted by NiLuJe
If it's stored as a "Saved network" in Nickel, you shouldn't have to click on anything, it should auto-connect to it. (At least for classic APs ^^)
|
So I told both Nickel and KOReader to "forget" the network and started again. I started in Nickel, it discovered a single SSID for my network, I entered the password, and it connected no problem. Then I turned off the WiFi and started KOReader.
In KOReader, I chose Network, WiFi Connection and it asked me if I wanted to turn on WiFi. I said yes and it presented me a list with 3 entries for my home network's SSID in it
and just sits there, doesn't automatically connect. I tried choosing each of these SSIDs and it prompts me for my password for each one (I didn't type it in, just backed out). So after I'd tried them all, KOReader still has WiFi turned off and hasn't automatically connect to my home network.
BUT, and here's the weird thing... if I try to do something that needs the network, say Check for update or look at my DropBox in Cloud Storage, it asks me if I want to connect to WiFi. If I choose yes, it briefly pops up the list of networks (and again I see three of my SSID in it) and then
does automatically connect to my network (without prompting for password), does whatever action prompted the connection, and stays connected.
So is it possible that enabling WiFi via the Wi-Fi connection menu item gets confused when it sees multiple SSIDs?
Quote:
In any case, syslog & crash.log output would be helpful  .
|
I had a look in there but couldn't see anything but will collect and post them later.