am: 5b25aba19f -s ours
am skip reason: change_id I54fc4ca104cb451af847d7973fbffc7f0ed97c10 with SHA1 04be9d1972 is in history
Change-Id: I58f8529e4efcd2e7586991a250d7a76160340e0d
am: 05a10d2f89 -s ours
am skip reason: change_id I6a5ba2439713105b25913ba8eb081abfaafd1a2e with SHA1 9c7fad9235 is in history
Change-Id: Iea5ea3522f36eb0f4c18ddb7e9b25b25d1837422
This reverts commit be71ed8a8e.
Causes various issues. Out of time for Q to investigate and fix.
Fixes: 135706138
Fixes: 135661232
Fixes: 135976008
Fixes: 135921478
Fixes: 135780312
Bug: 134561008
Change-Id: Ifb7b1fe2b189649d320516e70368625c903debea
am: c0fd05cf73 -s ours
am skip reason: change_id Ie73481e8d91ce43e4939f8c31a9ce431e382c6d9 with SHA1 fe1ad3d0b8 is in history
Change-Id: Ib41b3e4d93fa4ade8c5dd573c843dcd6c3b0c2a5
The "Connected" notification would be shown every time a network
validates after being identified as a captive portal. This causes issues
on networks that have auto-login mechanisms, as a high priority
notification would be shown even though the user was not interacting
with the phone.
The "Connected" notification is intended to confirm to the user that
they successfuly logged in (manually), so only show it after the user
opens the portal on the network.
Bug: 134124044
Test: Flashed, connected to portal: notification shown
Opened portal from command line + revalidate: no notification
Tests passing with change, failing without
Change-Id: I89e7a7f49019bd7e4686712c56e00bd786eb3ef3
Tactical, minimal fix to make sure the DhcpServer is stopped when
disabling tethering. The current code may throw if the interface is gone
when calling mNMService.setInterfaceConfig() on teardown. Make sure DHCP
is stopped regardless of what happens.
A longer term fix will be to figure out the right flow to teardown the
interface and avoid errors on setInterfaceConfig().
Bug: 124520692
Test: Manual: no more socket leaked when stopping USB tethering
Merged-In: Ie73481e8d91ce43e4939f8c31a9ce431e382c6d9
(cherry picked from commit fe1ad3d0b8)
Change-Id: Ia80761cb42dc62b14128fc60009be82ae9a008da
NetworkStatsService uses an internal boolean to know when it has
started for the purpose of preventing access to other internal
variables before they are initialized.
However that boolean is set to true in systemReady() non-atomically
with respect to the initialization of the other variables it guards,
which can cause the system server to crash.
This patch fixes this concurrency bug by moving setting the internal
boolean flag and the variable it guards in one atomic synchronized
block.
This patch also removes code checking if bandwidth control is enabled,
because this is now always true.
Bug: 132767673
Test: Compiled.
Change-Id: Ia089b5767ce271d669879c975508654d4dd03429
The GnssLocationProvider requests a LOW_POWER fix from fused
location provider for DBH requests and uses a short request
duration of 10 secs. Change it to request a high accuracy fix
and use a larger request duration for emergency requests.
Fixes: 135458882
Test: Simulated E911 DBH request from HAL and verified that
a location is injected to HAL when location settings
are OFF/ON. Tested with and without GPS signal.
Change-Id: Ia40bff4cbf8574b30dfe65704d33c716a317c66d
