Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The force scan action doesn't refresh automatically the network list #10

Open
javier-lopez opened this issue Feb 1, 2015 · 2 comments

Comments

@javier-lopez
Copy link
Contributor

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 the F6 action (force to scan) should do both, scan and refresh the network list.

Testcase

  1. Disconnect from all wireless networks
  2. Launch connman_curses
  3. Select the wifi technology
  4. Press F6 (force scan)
    • An Scanning WiFi... message is display at the bottom INFO section but the network list is not updated
  5. Press F5 (refresh network list)
    • Now the network list is updated
@alan-mushi
Copy link
Contributor

Hi,

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.

@javier-lopez
Copy link
Contributor Author

Hi,

And what about adding a timeout for scanning?

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants