| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
ephemeral flag in WifiInfo.
Add this private field to WifiInfo.
Change-Id: Ic815b87a24e8272faa6e9e820b8fa55224af882a
|
|
|
|
|
| |
Change-Id: I8687594eccea1e3d8b99450da5230442cdbd1a86
(cherry picked from commit 5fc9e14077c3bec51d0a93a5edeeade396d77d15)
|
|
|
|
|
|
|
|
|
|
|
|
| |
As a part of the new runtime permissions work we are limiting
the PII apps can access. BT and WiFi MAC addresses are PII and
based on our research there is no valid use case for app dev
to get these addresses aside of user tracking which we are
trying to limit.
bug:21078858
Change-Id: Ib48223b272c0fd4f5c36acc889d4f44df204b309
|
|
|
|
|
|
|
| |
This method will never return null. It may return "<unknown ssid>" if
no network is currently connected.
Change-Id: Iae09a6b2376e47c2d010f8d05750a16361510cca
|
|
|
|
| |
Change-Id: I9d417c20c6b6721933a4eb943c1305845005facf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Valid dBm ranges should *not* be mentioned in the documentation.
Manufacturers should be able to produce devices which can detect
signal strengths with arbitrary sensitivity rather than being forced
to restrict strengths to a certain range.
Adds a reference to WifiManager.calculateSignalLevel(), an
often-useful method to convert these RSSI values into an absolute
signal level that can be displayed to a user as the signal strength.
Bug: 13731529
Change-Id: I0aae85a6d8bc48ffddd1927d816a1dfbf5230f7e
|
|
|
|
|
| |
This CL is dependent on I10584a447fecd977df3eefd8e2cc028bd26ec0e3
Change-Id: I51fbbf062feb22c5f16b438675519064cc43e160
|
|
|
|
| |
Change-Id: Iffe899225899e7805478a507ce270d537dc84abd
|
|
|
|
|
|
| |
Bug: 15575229
Bug: 15577651
Change-Id: Ia8914a90d803fd9e6ba9fa51efce50c7b7f1c692
|
|
|
|
| |
Change-Id: If19d97d481a93343cf9792ff77bf9926ae5c26a7
|
|
|
|
| |
Change-Id: Iad207974b2fea97420cc6131c5fa0a1f17bf2aac
|
|
|
|
| |
Change-Id: Iccb2ec603bc9c0d3cf1976d0cc3f343cb1096494
|
|
|
|
|
|
| |
Remove references to TI drivers, and unnecessary uncertainty.
Change-Id: I74a01357264338df7c513684c6c752d1edb4ea4d
|
|
|
|
|
|
|
|
| |
constant).
Bug: 12767819
Change-Id: Ib4a03919d9100861e993c733b7e478dc93dffaae
|
|
|
|
|
|
|
|
|
|
| |
Some methods need to be public, since frameworks/base complies before
frameworks/base/services; and services takes build dependency on base.
Similar issue exists with WifiEnterpriseConfig constants.
Bug: 9907308
Change-Id: Ied0e3dee0b25c939067dbc66867a9814b3b3b68e
|
|
|
|
|
|
|
|
|
|
|
|
| |
The method would previously always return false.
Note that this is the simplest fix, and not the most
optimal fix. That said, in this change, a call to
WifiInfo#getHiddenSSID costs the same as a call to
WifiInfo#getSSID, so it isn't that bad.
bug: 10705138
Change-Id: I980563fd8a5bafe8c58c586449e778a0aa8b58a4
|
|
|
|
|
|
|
| |
http://elliotth.blogspot.com/2012/01/beware-convenience-methods.html
Bug: https://code.google.com/p/android/issues/detail?id=58359
Change-Id: Ibf25d0bbc76015cf8353ec01ab2b743cbc2bde67
|
|
|
|
|
|
|
| |
First step in accepting a set of patches.
bug:6799630
Change-Id: I6c894c60aeb3022960c2aaa45451bb1dde2b493b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Supplicant now passes as an ascii encoded string that allows it to
pass any sequence of bytes for a SSID. see src/utils/common.c in supplicant
for details of the implementation.
We create a SSID structure WifiSsid in framework to store the ssid and handle
the conversion appropriately when required for printing and for an application.
At this point, we still do not handle non-printable octets from an application perspective
for connectivity
Bug: 7110903
Change-Id: I520e5ee23baed4867b8b408bbb3eda5c9e92b6bf
|
|
|
|
|
| |
Bug: 6411912
Change-Id: I12f9df403c9633d928d898ae675ce36303dda1a8
|
|
|
|
|
|
|
|
|
|
|
|
| |
When DHCP lease includes vendor info indicating that remote Wi-Fi
network is metered, advise NetworkPolicy. Users can still manually
change the metered flag in Settings.
Also remove any policies belonging to removed Wi-Fi networks, and
teach isNetworkMetered() about ethernet networks.
Bug: 6344821, 6369307, 6365872
Change-Id: I108606c6fddf2d02828fcab011f3a1501415f1bc
|
|
|
|
|
|
|
| |
We are going to always disable the notification
Bug: 5556629
Change-Id: I981eb55a1bb6f44defd674e3a86d9c6f3805f4fc
|
|
|
|
|
|
| |
Notifies when user explicitly clicks on wifi dialog.
Change-Id: I5eee37d68b422d748d41e9384d5006482a223dc5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding a parsable wifiinfo object in Connected broadcast, public api.
The connected broadcast only occurs on successful setup on the wifi
interface, so in normal use is very infrequent (once if the wifi
sleeps, or once at new hotspots, etc...)
WifiInfo objects are small, <10 ints, <5 short strings, and contain info
that could be useful to listeners, such as SSID.
The alternative is to the poll the Wifi Manager, using getConnectionInfo.
Because the Wifi Manager can update state in its own thread, polling the
Wifi Manager might result in an info object that's out of sync from the
received broadcast.
Change-Id: Iafcec77f45dd094ea84e6022b7a40e8952ae8137
|
|
|
|
|
|
|
|
|
|
|
| |
Latest supplicant introduces the INTERFACE_DISABLED state. This
is entered when the interface is brought down (which is effectively
done by us and tracked already through the driver stop operation)
Also, added is a state for tracking authentication when supplicant acts as
the SME
Change-Id: I76090068d0ebba6df76f16707da559fcbd7512c5
|
|
|
|
| |
Change-Id: Ib27824cd0722099e157024ee2a9797236157bc8e
|
| |
|
| |
|
|
|