Not sure why we aren't getting warnings but these casts are to the wrong
type.
Bug: 34758075
Test: Manual
Change-Id: I6b9fc0500762c34379f4de56e0b5a66e6f17d87d
CaptureResult.JPEG_GPS_TIMESTAMP' queries can
return null Long objects. The conversion to
seconds should happen only in cases where we have
non-null objects.
BUG: 34835263
Change-Id: I1251fad55b2a671928839725123adedfb12fe53a
It's unclear if we need this check; esp if we want to support
running legacy instant apps [i.e. instant apps that run pre-O
under the supervisor].
Test: Build and install instant app
Change-Id: I241f97e7960635af933e8fe1ddd86675789ec26c
The wrong TypedArray was being used to retrieve the value.
Bug: 34818260
Test: run cts -m CtsWidgetTestCases -t
android.widget.cts.TextViewTest#testFontResources_setInXmlStyle
Change-Id: I09334710b9b21f1397bc02d92d14b41fbc96178f
With this change, data flows strictly like so:
AFManagerService -> AFManagerServiceImpl -> Session -> ViewSession
A ViewSession is introduced to 1) know when we can show the fill UI,
and 2) know when we need to create or update the current fill UI.
Each class has its own responsibilities:
* AFManagerService - interface to app process
* AFManagerServiceImpl - per user id
* Session - per activity
** AutoFillUI - per activity (can consider moving to ViewSession)
* ViewSession - per view
Bug: 34633695
Change-Id: Ia197a5c40219379ab6a95d0cf5c39ac4f5470d0e
Test: CTS, Manual with GMS Core
All the tests are now asynchronous. The only remaining uses of
Thread.sleep() are in the tests that check for NetworkRequest
timeouts.
Test: ConnectivityServiceTest passes 100 times in a row
Bug: 32561414
Change-Id: If420bd66c692a90d5031ee06a888a8cc3b4398a8
The calls in testAvoidBadWifi are no longer necessary now that
waitForIdle is reliable, and the calls in testPacketKeepalives
are replaced with a wait for the NetworkAgent to disconnect.
Test: ConnectivityServiceTest passes 100 times in a row.
Bug: 32561414
Change-Id: Icbb161ca6e343bd14764a1c9ccfdd14b6cd6803f
Rename the class and ensure that all code related to bad wifi
avoidance has names that reflect its purpose. This will allow us
to reuse most of the the code for other purposes in future CLs.
Test: runtest frameworks-net passes
Bug: 34630278
Change-Id: Ida190e5a79e7a12f4eec07e1a3e4d9d138e83bcd
The current implementation of IdleableHandlerThread is based on
the assumption that MessageQueue#isIdle will return true iff the
message loop has finished processing its messages.
Unfortunately, this is incorrect: isIdle returns true iff are no
more messages waiting in the queue; thus, it will also return
true while it is processing the last message before going idle.
Instead of using idle handlers, take the simpler approach of
posting a runnable to the message loop and waiting for it to
be processed.
Test: see other CLs in this patch series
Bug: 31479480
Change-Id: Iae75781f067b762c8653a488a5e4d5ee0c789e01
Note DPM.wipeData() on a secondary user is now blocking, just like
it's been always blocking on the primary user.
Bug 30681079
Change-Id: Ia832bed0f22396998d6307ab46e262dae9463838
Merged-In: Ia832bed0f22396998d6307ab46e262dae9463838
Note DPM.wipeData() on a secondary user is now blocking, just like
it's been always blocking on the primary user.
Bug 30681079
Change-Id: Ia832bed0f22396998d6307ab46e262dae9463838
VolumeDialogController(System UI) only manages active sessions,
but MediaSessionService always notifies the System UI of remote
volume change regardless of whether the session is active or not.
This CL makes MediaSessionService notify of remote volume change
only when the session is active.
Bug: 34033926
Test: Flashed new master build on angler and tested.
Change-Id: Id363c078f75d49732aa7af9578ee44a24649df63
