ID resources that get generated on demand with the
notation @+id/name were previously not given the
appropriate type ID offset when being built as feature
splits.
This change declares an ID type ahead of time so that
the type ID offset is applied before IDs can be generated.
Bug:30607637
Change-Id: I122a9133cb01b35e9892103ec52fc228dc65bf1a
- The nav bar now moves to follow a specific edge of the device, so we
should always choose the opposite end of the screen to ensure a valid
drop target is accessible.
Bug: 30548794
Change-Id: Icac8adfb167a4115377d42ddd897ac94e02077a3
- When the cached UID state says a UID is in the background,
check with AM and get the latest state, since the state
might just have been changed.
Bug 30640208
Change-Id: If448f6f21f290fa0fc13550d9c740f56aa8bfce0
There are PackageManager flags we can use to resolve the camera app
for a given user, even while they're still locked.
Bug: 30621101
Change-Id: I0098c9423e2cd453e957d4365cfbcac5ccbb2947
When there's no notification anymore, the background could animate
weirdly as it still factored in the stack translation, which doesn't
make much sense. This lead to weird transitions on the lockscreen.
Change-Id: I0f17dc5f667106dcad54702be1880a689df24764
Fixes: 30341287
This change adds historical operations to the dump state
of the settings provider. The historica operations are
currently appended only on user-debug and eng builds.
These change is needed to help diagnose the referred
bug and improve the settings provider's maintenance.
bug:30561721
Change-Id: I58a1ba0d598c4d28adcb5e654ebb78cf947e94db
When multiple alarm clocks are scheduled at the same time, we would
flap among the alternatives for considering them the 'next upcoming
alarm clock', which in turn would generate [many] spurious broadcasts
about changes to the upcoming alarm situation. This is now fixed;
once we have found the soonest upcoming alarm clock, we stick with
that one until it becomes unavailable, eliminating the spurious
broadcast traffic.
Bug 29501073
Change-Id: Ice1892490bb339e05fa8bd9d324fa1c6718b4942
A lot of calling framework code expects a null value on failure,
and didn't catch the previous exception. There were some strange
corner cases where previously a null value was not checked for
in framework code, allowing the null Resources object to be
returned to the caller. Introducing an exception changed the
semantics and can crash certain apps.
Bug:30422475
Change-Id: I51d34ae43c9ec605a8790989c56cf85b815ff5b8
Corrected the information related to the spanning of multiple columns.
As per the reference documentation, cells can span multiple columns. Added
information about how to span multiple columns and provided a reference
link for more details.
Bug: 24760839
Change-Id: I32d51d27db94f61dfa83f7fe1fe94ca58708a2d0
Bug: 30604178
Fixes a bug where opa would be enabled for non-opa-enabled devices upon
orientation change.
Change-Id: I5f8f913a53f180d783ba1c6d1fab22514986847e
When updating a child of a group, the group would always
animate, because of the suppression logic. This doesn't
happen anymore.
Change-Id: Ie2b09c1e03f37a12ba8f995e5b7d0e3721e3651a
Fixes: 30608517
