If WPS is already active, we drop user's request
and convey an in progress message
If WPS fails to start, a failure indication is conveyed
to the user
Bug: 3316078
Change-Id: I238c55973cb29cf5c1be66197ffcb4978316cb89
Use the bluetooth adapter broadcast so that we capture
various bluetooth profiles for both scan coex settings
and coex settings during DHCP
Change-Id: Idec41940514efe7ea9927f67b6199b4893794e2a
We now all configured networks on screen on.
Also, removed event logging for scanning and rssi polling
Bug: 2129037
Change-Id: I995893d77f8575a8d987d9d8604c8272f636d12d
Add the missing wifi disable broadcast and also send out
supplicant disconnect on shutdown.
Added unit test cases.
Bug: 3294055
Change-Id: Ia56a8ec9d17784c5aac5b8b369c04837f9057c54
- Use a clean terminate for a regular stop and on failure kill supplicant. This prevents
WifiMonitor from getting hung permanently on a socket in case of a kill
- When WifiMonitor exits, kill supplicant and cleanup sockets
Change-Id: I87c32e03d945433f33eed8c326d7f0368925bf55
- Allow IP and proxy set up for WPS
- Use string for WPS pin to avoid losing leading zeros
- Add a seperate WPS state machine and WpsConfiguration class
Change-Id: I87f43fff8bba0ae8ff02e5fc495a8bc628a8c8cf
Added CMD_SET_DATA_ENABLE which is sent when data is enabled/disabled
via the ConnectivityService. It is anticipated that the communication
channel will be used for additional commands and to receive unsoliciated
commands from DataConnectionTracker back to MobileDataStateTracker.
Change-Id: I3863e7385155d503f069b1dcb7e4f766ec78b5f8
When IP or proxy config changes, we now reconfigure
the network and inform connectivityservice.
Also, fixed the naming for changes on configured
networks.
Bug: 3237735
Change-Id: I2a94b3158b6b0e0d27442d7fd525a8a23f0497f8
- Move SupplicantStateTracker into a seperate file. In the
process clean up code that needs to be present only in SupplicantStateTracker
- Retry twice for password failures
- Clean up supplicant state handling. Dont treat supplicant states
as HSM what values. Instead, just retain SUPPLICANT_STATE_CHANGE
- Add event logging in SupplicantStateTracker
- Move scan handling out SupplicantStateTracker
Change-Id: I083e1c40ef5a858164493b1440b82c5751b3bfb5
also cleaned up some unnecessary synchronous commands from state machine,
and fixed an issue with a synchronous WPS command
Change-Id: I55bf4379d9810e11f2ba2e03e2e703b132d1488f
Add extension to WifiLock to allow apps to operate
in high performance mode (high power & disable suspend
optimizations for battery consumption).
Bug: 2834260
Change-Id: Id394d265b9876bf0230efb3d222056e9b80b44fd
- Add wakelock for driver start/stop to ensure a wifilock
acquisition kick starts driver. Also cleaned up state machine
driver start/stop behavior.
- Add periodic scans when driver is started to ensure wifi
reconnections when wifilock exists or when user chooses
never to sleep
- some minor clean up
Change-Id: I844eb70491d5aa2f8c8933b3d8dd01ba237ee534
- When supplicant dies, restart it
- When wifimonitor fails to connect in time, restart
supplicant
- fix dhcp counter reset
- defer all load/unload actions when waiting for supplicant
control connection
- we dont need to disconnect & reconnect at start with the
faster monitor connection and handling of failures
Bug: 2973023
Bug: 3090725
Change-Id: I5c834ddd08e6300e2b29da0941a24633825b4d3b
Provide per network proxy settings configuration
for wifi. This is stored along with the ip configuration
in ipconfig.txt
bug: 3039302
Change-Id: Ic8bc14493583be19fde3d7c463d1e5a77e6df25f
Merge commit '58e0eefeb5e2e270e2b04369bbf29fc22abda8d5' into gingerbread-plus-aosp
* commit '58e0eefeb5e2e270e2b04369bbf29fc22abda8d5':
Improve power tracking of WIFI use.
We now distribute "wifi started" time across all apps that are
holding WIFI locks that cause it to be started. But only when
WIFI would not normally be running. Also have a mechanism to
distribute other WIFI work that has happened across those processes
based on their use.
Also fixed a bug where we were not retaining the CPU speed step
stats across boots...!
Change-Id: I00e3153b98429166273750512cc37e7975211ab9
This fixes a problem where applications could ask the location
manager to do very heavy-weight things (like... say... update
location every minute), which would get accounted against the
system instead of the application because ultimately it is the
system making the heavy calls (wake locks, etc).
To solve this, we introduce a new class WorkSource representing
the source of some work. Wake locks and Wifi locks allow you
to set the source to use (but only if you are system code and thus
can get the permission to do so), which is what will be reported
to the battery stats until the actual caller.
For the initial implementation, the location manager keeps track
of all clients requesting periodic updates, and tells its providers
about them as a WorkSource param when setting their min update time.
The network location provider uses this to set the source on the
wake and wifi locks it acquires, when doing work because of the
update period.
This should also be used elsewhere, such as in the GPS provider,
but this is a good start.
Change-Id: I2b6ffafad9e90ecf15d7c502e2db675fd52ae3cf
Add support for set and get band and set the default
to 2GHz for now till we get a fix on issues
with 11A
Change-Id: Icb9bddc353e4bf013bdb8a08d9b4ee3451c282f4
