You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably the F5, F6 workflow was planned at its current implementation (force to scan and later refresh the network list manually), but in my opinion the F6 action (force to scan) should do both, scan and refresh the network list.
Testcase
Disconnect from all wireless networks
Launch connman_curses
Select the wifi technology
Press F6 (force scan)
An Scanning WiFi... message is display at the bottom INFO section but the network list is not updated
Press F5 (refresh network list)
Now the network list is updated
The text was updated successfully, but these errors were encountered:
Yes the workflow for a re-scan is as we wanted it to be. I reckon that it might feel counter-intuitive but it's a trade-off. This particular behavior allows a static listing of networks. Without it you might experience AP reordering in areas were there is a lot of network signals, making it painful to select a wifi network among dozens of "moving" items.
At its current stage it looks possible, when connman_curses starts, it shows a list of wireless networks but don't keep updating them, I think the same behavior could be used in the Scan action, giving some timeout for getting networks and displaying them when done?
Hello,
Probably the
F5
,F6
workflow was planned at its current implementation (force to scan and later refresh the network list manually), but in my opinion theF6
action (force to scan) should do both, scan and refresh the network list.Testcase
connman_curses
wifi technology
F6
(force scan)Scanning WiFi...
message is display at the bottom INFO section but the network list is not updatedF5
(refresh network list)The text was updated successfully, but these errors were encountered: