This reverts commit e0237fa50b. Reverting
based on the feedback from Permissions and privacy team.
Bug: 158705914
Test: atest --test-mapping apex/blobstore
Change-Id: Id057e8c61dcf9d3d111ab20530a2074083052392
Included changes:
* b692f37: Rename `Int64` in annotation processor to `Long`.
* 05fe08c: Get QueryLength from Native
* 8f46606: Logging stats for remove (1)
* 237c134: Alter inheritance of LongProperty for backwards compatibility.
Bug: 187820569
Bug: 173532925
Bug: 173532925
Bug: 187820569
Test: Presubmit
Change-Id: Ia27e00250e7aa7c7a1acc974f24c63cc456739be
The internal api ShortcutService#postValue isn't protected by mLock and
thus causing concurrent modification exception.
This CL temprorary fixes the issue by protecting above api with existing
lock. In the long run we should be moving the lock to package level,
which will be implemented in b/186011943
Bug: 187062117, 188397473, 188277633
Test: manual
Change-Id: I93537f8abe7a2ec2787949d109c6b3045664d8dd
This avoid the race condition when we are about to seal the session, but
another notification goes through and fails the commit.
Also saves some resources - we almost never need a dataLoader for e.g.
Incremental installations.
Bug: 188079906
Bug: 187967058
Fixes: 188079906
Fixes: 187967058
Test: atest PackageManagerShellCommandIncrementalTest
Change-Id: Id931b40362f603ccd45b64ff5f8636d8c32e849e
This helps to avoid the problem where the auto-generated
IMS or EMERGENCY APN being used for initial-attach due to
racing conditions.
Some carriers may require IMS APN for initial-attach. That case,
the IA type should have been added to the APN explicitly to prevent
the DEFAULT APN from being used.
Bug: 186120396
Change-Id: Ic5e449e514a996f90b815e56fe136ac1f453496e
Test: manual
This is needed so that calendar and other time based updates are still received when in doze mode.
Bug: 187186900
Test: KeyguardClockSwitchControllerTest, manually on device
Change-Id: I2667b722fbde219063c719296de35946f536473b
* changes:
Adjust split layout with IME animation in split (5/N)
Adjust split layout with IME animation in split (4/N)
Adjust split layout with IME animation in split (3/N)
Adjust split layout with IME animation in split (2/N)
Adjust split layout with IME animation in split (1/N)
This seems to interfere with cross profile remote views otherwise. This
will also avoid changing the stored RemoteViews, or not providing an ID
if the RemoteViews is constructed by the host.
Fix: 187837525
Fix: 187867661
Test: atest ManagedProfileCrossProfileTest#testCrossProfileWidgets
Test: Manually with other apps, checking the colors do no flickr
Test: Check that uninstalling an app with a widget doesn't crash anymore
Change-Id: I7caa3f58d9b554e36f54e6b9d3b793c3ae5023ef
Root cause was that `this` on lines 353 and 354 was referring to the
ValueAnimator, not the clipLayer.getDrawable().apply{} that was started
on line 330. I refactored the code a bit so it uses fewer Kotlin idioms
but should be less error-prone, but let me know if you'd rather I just
update lines 353 and 354 to specify which `this` it's referring to.
Test: manual
Fixes: 187903455
Change-Id: I3505c1fc80f7dda6d6cc318b0dfa2754171b8a2b
