This reverts commit 93e164726f.
Reason for revert: This is causing wake lock to remain held
while screen is off
Bug: 139875245
Change-Id: I0ff714a0cf2496d141d355de68761ab720a09539
When transitioning to DOZE, there is a race condition between the
release of the display suspend blocker and calling startDream. This
creates a gap where the device can suspend before the dream actually
starts. In practice, this can cause gestures, which are nitialized
from the Dream Service, to not function until something else
temporarily wakes up the device enough for the CPU to run a few
cycles.
This change delays the release of the display suspend blocker if
there is a pending recalculation of the sleep/doze state.
Bug: 138828701
Test: Manual testing - was 1 in 5 chance of reproing. Tested up to
0 out of 50 after the fix.
Test: atest PowerManagerServiceTest
Change-Id: Ic6df469972dc5765a8c4507404d1dc33f13ec0c3
* changes:
DO NOT MERGE Move device config key high_refresh_rate_blacklist to display_manager
DO NOT MERGE Allow DeviceConfig to change display settings
DO NOT MERGE DeviceConfig: Add Name space and keys for Display Manager
am: cceea08cc7 -s ours
am skip reason: change_id I8f7bd7a6a0562942ed3e12f28705043722d177e8 with SHA1 65c96f2fd4 is in history
Change-Id: I5451e6467e8ffebd08360abfab9f86a429ed0721
Since we're using the pulsing state for docking, the icons would now
become clipped while pulsing.
Fixes: 139096431
Test: dock, observe notification icons showing
Change-Id: If251e6b18c03b2824b4d3ea4dab82d4a403565f1
Merged-In: I8f7bd7a6a0562942ed3e12f28705043722d177e8
Non-notification background vibrations are ignored. However, we don't
want to ignore notifications that represent various events, such as
reminders.
Test: Create a calendar event with a reminder. Close calendar and wait
for reminder. The device should vibrate when the reminder pops up.
Bug: 139523314
Change-Id: I231239daf7cc85bf69aaeef1da31218a23fcf311
Fixed the vendor data/network service non-responsive
issue. The callback binder passed from frameworks
might be GC'd so that vendor data/network service skipped
calling the callback. This eventually caused data
connection state machine messed up.
Fixed by turning the weak refernce to the callback into
a strong reference. This ensure the binder alive when
vendor service needs to invoke the callback.
Test: Telephony sanity tests
Bug: 139076980
Change-Id: Ica0b7b810ffd5416ffd1b2b61f7ebc4af0dcb8ce
Added debug messages and watchdog to catch
unresponsive data service issue.
Bug: 139076980
Test: Manual
Change-Id: I52dd126fddc1b1e8b18d5388a92aabaa3e2e48d5
The OMS was calling stopIdmapService after OMS initialization finished.
This method was not setting the cached service binder to null and the
service binder was being reused when an overlay is enabled or disabled
within the 10 seconds the connection to the service is still opened.
This change no longer calls stopIdmapService and makes startIdmapService
and stopIdmapService private to IdmapDaemon.
Bug: 139307780
Test: enabled overlay within 10 seconds of OMS startup ending and
observed state STATE_ENABLED.
Change-Id: I46b6a3631278c4dbdf5e5d373e085bac5186ed9a
The resource loading is done based on the last SIM to come up
which is not a deterministic design. Thus, update the way to get
the resource based on the subId.
Test: atest FrameworksNetTests
Test: manually test with avoid bad wifi feature supported sim
Bug: 138956509
Change-Id: Ib5b085d97103889600773d269e03b939c29ca47d
Merged-In: Ib5b085d97103889600773d269e03b939c29ca47d
(cherry picked from commit 5e994ea02c)
