Ticket #1514 (new defect)

Opened 10 years ago

Last modified 10 years ago

wifi policy needed

Reported by: marek Owned by: will
Priority: high Milestone: Om2008.8
Component: Network Manager Version: unspecified
Severity: major Keywords: pm
Cc: will@…, raster@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

We need a defined wifi policy for ASU.
For example:

  • When the phone is turned on - should wifi be an/disabled ?
  • Should the phone scan for wifi networks all the time ?
  • After turning on the wifi should the phone connect to known networks automatically ? Only to crypted ? What if we have more than one known network ?
  • What should the phone do if we loose the connection to our current network ?

Change History

comment:1 Changed 10 years ago by marek

  • Cc will@… added
  • Type changed from task to defect
  • Version changed from current svn head to unspecified
  • Component changed from unknown to Network Manager

comment:2 Changed 10 years ago by will

  • Cc raster@… added
  • When the phone is turned on - should wifi be an/disabled ?

disabled by default during boot, user has to turn it on if they want it.

  • Should the phone scan for wifi networks all the time ?

Yes. If enabled, it keeps scanning.
Important thing is to show a 'Wifi Icon' indicating that Wifi is in fact enabled, scanning, and eating up battery.

  • After turning on the wifi should the phone connect to known networks automatically ?

Yes.
*Only to crypted ?
No. Auto-connect to any known network.
*What if we have more than one known network ?
Strongest encrypted wins.

  • What should the phone do if we loose the connection to our current network ?

Go back to scan state until connection is found.

  • What if we are connected to a network and later we find a better, stronger network?

Keep current connection.

  • How do we store passwords?

Store passwords plain, and keep your Neo somewhere safe..

comment:3 Changed 10 years ago by john_lee

  • HasPatchForReview unset

since will already answered the question , should we close this?

comment:4 Changed 10 years ago by marek

Well, it is defined but not fully implemented yet. But this may take a while as the network manager state is unclear at the moment.

Note: See TracTickets for help on using tickets.