There is a known issue in the kernel uidcputime module that triggers
the WTF, which has a cost to the system. Convert to a regular log
instead.
Bug:28950306
Change-Id: I7cbb3138f644075f0d9d65ce8b52bd835eb270fd
Use PowerProfile to calculate mAh (MemoryPowerCalculator), and
involve this calculation in the overall accounting of battery
for when the phone is unplugged from a charger.
Note: Depends on ag/1196281
Change-Id: Id02bef19c9b250c614df0a6c88711b486faaef46
Initial implementation of some classes that pipe memory power use
information from the kernel to BatteryStats framework. Reads how much
time has been spent in distinct bandwidth buckets.
Change-Id: Iefb4b4c0a4e0d0f8d7a773075324ebd38ed154f2
Happens because CascadingMenuPopup calls setWidth() rather
than setContentWidth() like StandardMenuPopup does.
BUG: 30365568
Change-Id: Id850baaf1d9c5664220766e5e37869e2ec361a2d
Happens because CascadingMenuPopup calls setWidth() rather
than setContentWidth() like StandardMenuPopup does.
BUG: 30365568
Change-Id: I349b5cf81982d7efc85342ab672f2b4e65bafd70
DecorCaptionView is used in app view hierarchy in freeform mode
and it inherits default ViewGroup#shouldDelayChildPressedState
implementation, which returns true by default for compatibility
reasons.
This results in touch not delivered to child views in some cases
until there is movement or up action. E.g. touch on SeekBar will
not change the position of control instantly in freeform, while
it does in other modes.
This CL disables delaying child pressed state for DecorCaptionView.
Bug: 30037893
Change-Id: I4917143610b6c0d404d2395670de9525c10f2a6c
The platform currently supports the notion of default carrier apps.
These apps are set to DISABLED_UNTIL_USED until a SIM is inserted
which grants them carrier privileges, at which point they are enabled.
Apps are not touched if they have been updated from the version on
/system or if their state has been modified externally (e.g. by the
user).
This CL extends this notion to associated apps, which may not have
carrier privileges themselves, but should be enabled/disabled
alongside a particular carrier app. This should include helper apps
that should not be visible to users who don't use the given carrier
unless the user explicitly enables the app.
As additional protection, we add a check to ensure that we never
disable apps after the first time we've run. Since we need to store
this information in secure settings, we also move the call site from
PackageManagerService#main() to PackageManagerService#systemReady(),
which enables use of secure settings but still occurs before
third-party apps can be started.
Bug: 30141427
Change-Id: Iee72ba4e70e5ca97999c9147a65af82c670a23e8
Preferences lack a title on watch type devices due to lack of ActionBar
support. A custom ListView was added to use a custom wrapper adapter to
add a persistent header view at the top of the ListView that developers
would not be able to remove via the ListView API.
Bug: 27962897
Change-Id: I6bccecf85592d9507e0c7a04c9a035617001e9ef
For watch devices, AlertDialogs added the title and button bar as header and
footer views in the ListView. This broke compatibility, hence a solution to
overlay the panels instead with a wrapper layout.
Bug: 27482353
Bug: 30075032
Bug: 29833395
Bug: 29277843
Change-Id: I2ecbe56ae8f7d7e99c7ca2dad2a2092499212199
These appear as a new event in the battery stats history,
"longwake" in the long version and "Elw" in the checkin.
The power manager keeps track of which wake locks are held
for a long time and reports them to battery stats. Long
is currently considered 1 minute or more. Once it is long,
the start event will appear, and once if is released the
event will end.
In the case of a wake lock changing (typically its work
source changing), for purposes of this accounting this is
considering a pure release of the old state and start of
the new state... so the timer will reset back to one
minute until the wake lock is considered long. This is done
to prevent things that make lots of changes to wake lock
work sources from spamming the log.
Bug: 28753137
Change-Id: I33b6168c57a7ea6ea558273dec731704123124a5
Symptom:
When sharing an image from Album, ChooserActivity can be shown.
But then the app to be located to the bottom part of the list may not
be started even if user tap it.
Root cause:
ChooserActivity uses ResolverDrawerLayout. And ResolverDrawerLayout
can display only some items on the list (known as "Collapse mode").
When the item clipping along the bottom edge is tapped by the user,
ResolverDrawerLayout tries to expand the list and scroll it to a
better position, instead of starting an application.
In this problem case, ResolverDrawerLayout continues to try to expand
the list whenever tapping, so an application will never start.
Solution:
Change a condition so that mOpenOnClick becomes true only when the list
has been collapsed (mCollapseOffset > 0).
Bug: 30153542
Change-Id: I576fb6c8b6a91d79c1e0d46d069146779f4dbd17
