|
|
|
|
|
by ylj
455 days ago
|
|
I understand your point and initially wanted to avoid the overhead of generating and scanning a QR code just to connect to WiFi. The reason for this approach is that the Android API doesn’t allow non-system or non-rooted apps to directly manage WiFi connections. In other words, it’s not possible to create a simple app that directly connects to WiFi with known network name and password. Generating and scanning a QR code is a workaround to minimize steps—avoiding the need to manually select the network from a long list and type the password. Android does provide a WiFi suggestion API [1], but it has several limitations and doesn’t behave quite as expected. I initially tried using that, but eventually settled on the QR code solution. Hope this clarifies things! [1] https://developer.android.com/develop/connectivity/wifi/wifi... |
|
Can you expand on this? I read the linked doc, and it looked like a separate API should be used to used to "persist a network connection" (my words), but as someone with no Android dev experience there don't seem to be any obvious limitations.
You did mention in another reply that only certain root apps can do [what we expect]. Is there a link where I can learn more about that?