LinkProperties can represent way more complicated configurations
than what we can actually apply to interfaces. This makes it
error-prone to use it to represent static configuration, both
when trying to apply configuration coming from LinkProperties
and when trying to save configuration from current
LinkProperties.
Instead, move static configuration (IPv4 only, since we don't
support static IPv6 configuration) into a separate
StaticIpConfiguration class.
Bug: 16114392
Bug: 16893413
Change-Id: Ib33f35c004e30b6067bb20235ffa43c247d174df
This reverts commit 87efe74e092236c372d3b6909009641123aa416a.
This should be fine now with all the dependency CLs +2-ed
Change-Id: I96ad14ad5ff81e6b5391035cb6c5a62339c6cc40
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 change un-hides constants for these two methods and
also un-hides RADIUS/AAA FQDN field to allow creating
Passpoint release 1 credentials.
Change-Id: Ia3501017dc1f5c0b4932bb45e1e9c5bf7262d7fe
This change will fulfill the same role as ag/487624, which unhid other broadcast
constants (and is being rolled back). We can leverage the existing broadcasts
in this CL rather than introducing new ones. They just need to be exposed.
Bug: 16871063
Change-Id: I91462851c8016ed962cdafa54e9ec938d52c84b6
Setting the value has no effect because it was lost in marshalling
across binder interface.
Bug: 16826305
Change-Id: I5b308441608e0b7fc159fc249a16aec3728bac82
Trusted credentials for both the primary user and its managed profiles are shown
on the Trusted Credentials fragment. All functionalities (e.g. disabling/enabling
of certificates) remain available.
Bug: 16029580
Change-Id: Ia92ae02d8c572bf4a3be172f6c255726cefc0fa1
And other usage of term Hotspot. This is to be technically correct
with the name usage, should the API become public later.
This change also fixes few outstanding requests from GScan API.These
include
a. An event with scan results when REPORT_AFTER_EACH_SCAN is set.
b. ScanSettings now takes in number of APs as an argument.
c. Removed single shot scan API (since it is not implemented anyway)
Change-Id: Id160f9f14193a37cce5f3ab8d6ea528344b788a0
Change-Id: I82ef09ec46d7ac7cc8bbe2939873a5f966ee0df7
On branch scorer-logs
Changes to be committed:
modified: java/android/net/wifi/WifiConnectionStatistics.java
On branch scorer-logs
Changes to be committed:
modified: java/android/net/wifi/WifiConnectionStatistics.java
This change includes various fixes to first RTT implementation and
enables RTT APIs end-to-end. Fixes include proper marshalling of
objects across API and service and JNI fixes.
Change-Id: Ie4ba1ffc6c5b42593e931438b3f03e201ff6be71
This is very similar to the existing
WifiManger.getConfiguredNetworks(), but it returns real preSharedKey.
This API is only used by system application.
Bug: 15703353
Change-Id: If3eaca3286e77b780272f42a28772d1d8d39db65
(cherry picked from commit 775bf6ae5d052948bcb60eaf89defa9105d7077c)
* Only allow system app to send/receive
WIFI_CREDENTIAL_CHANGE.
* Define constants in WifiManager.
Bug: 15703353
Change-Id: I4bcc6bc82ec01952500eef3965cf81116bba693d
(cherry picked from commit f4a43f196e1132968a8add60efa4ae4558f8b010)
