*) Eliminates visibility of the pref removal. You could previously
see vertical movement of text during initial display of replaced
prefs.
*) In addition, when reaping, use setVisible(false) instead of
removePreference. Otherwise, array out of bounds index exceptions
occur in frameworks pref support libraries (as a result of moving
from onBindViewHolder to onAttached).
Change-Id: I1a0045552572a590f89715f8d94156eddaaec469
*) Add support for integer requiresConfig resources (previously supported
only strings and bools). Preference is removed if the int is 0.
*) Add a new attribute requiresConfigMask that takes a string decimal int.
If requiresConfig is an integer then the pref is removed if
(requiresConfig resource value & requiresConfigMask value) == 0.
If requiresConfig is not an integer type then requiresConfigMask
is ignored.
*) Code clean-up for the rest of checking requiresConfig.
Change-Id: Ic2622809c02a94d9cecf6f59ed6e689fdb835458
This got removed unintentionally by:
Author: Sam Mortimer <sam@mortimer.me.uk>
Date: Wed Oct 11 23:00:18 2017 -0700
Remove ThirdPartyKeyguard
Change-Id: Ie3717b9ea7a23988ebd646ed7e2fe8f105a4a693
Add back the lock util methods from the original commit:
Author: Danesh M <daneshm90@gmail.com>
Date: Mon Feb 8 14:57:31 2016 -0800
CMSettings : Add option to pass swipe-up-to-unlock (3/3)
CYNGNOS-1873
Change-Id: Icdd2505dbc56a77f49a76ea61daf75c5d8a24fd6
Change-Id: I6177700be955f42505dbd5fbb23461f8e151e1b4
* The feature was used only on Huashan since 2015
* It serves only for a small part of the users
who wanted to restrict to one light instead
of three lights from the LEDs bar
* Due to Oreo's new HIDL interfaces stack,
the additional data holder would need
a custom lights interface which is useless
for a single device and a rare use case
Change-Id: Ie08a1d625c7ce00fefff5bc1159522207be69dbc
Signed-off-by: Adrian DC <radian.dc@gmail.com>
It's no longer used anywhere and has a dependency
on frameworks code that we don't want to add to
lineage-15.0.
Change-Id: Ib25bc214df658e7576e63c73a9c23b7e87ea71d8
*) Move it here so that external/uicommon can be
deprecated.
Origial uicommon StopMotionVectorDrawable.java history:
Author: Adrian DC <radian.dc@gmail.com>
Date: Fri Oct 28 10:55:25 2016 +0200
uicommon: Fix getAnimatorSetViaReflection UI usage
* The receiver can be an instance of VectorDrawableAnimatorRT
instead of VectorDrawableAnimatorUI since AOSP 7.x,
therefore call the forceAnimationOnUI method to ensure
mAnimatorSet is an instance of VectorDrawableAnimatorUI
* Change introduced in "Support running AVD on UI thread",
frameworks_base: I372ecd3dc52e3fa0bdce3a1e9c19443f9b199027
Change-Id: Ie00c86474f38600b4f10889e292b20a8f7e6531e
Signed-off-by: Adrian DC <radian.dc@gmail.com>
Author: Steve Kondik <steve@cyngn.com>
Date: Wed Oct 12 17:02:17 2016 -0700
uicommon: Fix StopMotionVectorDrawable for N
* The guts of AVD have changed in N, adjust hacks accordingly.
Change-Id: Ia28c3099389252a3fd57373e02800fee9d467f64
Author: d34d <clark@cyngn.com>
Date: Wed May 4 08:59:27 2016 -0700
Add StopMotionVectorDrawable to uicommon
The StopMotionVectorDrawable provides control over the position
within an animation set of the warpped AnimatedVectorDrawable.
Change-Id: I586c54c7dbd5c9f6f373a87e544bc0669f4ba8f1
Change-Id: I868a852e6c5f6f1ab7926deeb109fc68ad4449da
As per similar changes made in
frameworks/base/core/java/android/provider/Settings.java
Whilst not strictly necessary, also renamed
SELECT_VALUE to SELECT_VALUE_PROJECTION
as it is now named in frameworks.
Original AOSP change here:
ea93fe7539
Change-Id: Ib79bdc9a9c1f45d5f8405c7ecea30f68652f2839
This was in frameworks/base on lineage 14.1 and
earlier (https://review.lineageos.org/#/c/65797/).
Update api/lineage_current.txt to match the new location.
Change-Id: Ib852ab1bc04936828ef00e24f71783e6a41de33c
Use the same base theme used for Settings so that our preference
tiles look like the default ones (e.g. add ripple effect).
Change-Id: I27a5569535d8d614a0c0d26dd5b9fcd12f2af1e4
AOSP recently introduced a new power hint, POWER_HINT_LAUNCH,
to indicate the start-up of an activity.
We now use that instead of using our own.
Change-Id: I3ed1ae52a67da37e87a46ca5cc5411de95f00926
Issue-Id: LINN-6
- We might get see attach() calls from multiple prefs, so stop assuming
there's only one per key. Namely, a new activity might be created and
attached before the previous one is destroyed
- The passed-in context is likely to be an activity one. As the manager
instance is static, this can cause leaks and the receiver might be
attached to a destroyed activity. Just hold onto the application
context instead, which is a singleton anyway.
Change-Id: Ica17c19ab6e1cdfd402968ce2594d3ed362e23ee
JIRA:LINN-3
This is used to decide whether a user wants
to long-press the power button while the display
is off to activate the torchlight.
Change-Id: I3bfaa4bf5a5452b9af2c412596c6713a151e0ec8
Many new devices have available flip cover cases with some form
of view window or notification options. Currently we support a
dotcase app for HTC and a View window app is under development.
Provide a new Intent to allow a common way to launch a variety
of device specific cover apps.
Change-Id: Ic986b239b75bfc6d76142451826b3f996e242a29
* Hiding the clock is now possible using the icon blacklist.
* Since the the hide option in the clock position tunable
isn't currently implemented let's remove it
Change-Id: I2412051289a922dfc72cdf266b47f32cf7aaa31a
* Hotspot is not assigning DHCP addresses correctly if enabled
through the profiles codepath using WifiManager.
Change-Id: I9b67748d1b51c873864cf11f9240372e367a0c53
* The preferences constraints system uses reflection to look up
fields via strings, we need to ensure they are not optimized
out by Proguard. Alternatively we can manually enumerate them,
but it's yet another list of constants to maintain. We should
have used a proper enumeration to begin with, but so it goes.
* The @VisibleForTesting annotation is honored by the platform for
ensuring that Proguard doesn't stomp fields. The support library
has an @Keep annotation, but it's only supported by Gradle. If
it becomes supported by the platform in the future, switch to
it instead.
* Also add tests for all of this.
Change-Id: I9f324e003e2a9de5604085b978d5f95bdd098d32
* Factoring out the work done for CMParts into an actual API that can
be used for all of the various device settings apps.
Change-Id: Ie1b47c900c2b37457b90f1b0af0634d5fe12fd9a
* Add a bunch of helpers for dealing with settings URIs in
a transparent way.
* This also includes the "Observatory" which is an aggregator
of ContentObservers. Inspired by TunerService.
Change-Id: Ie30c3f712d3c6536af559d93f7debe2dcc5ead06
* Add support for negation- prefix with !
* Add requiresAction constraint, which checks if an application is
available to resolve the given action
* Fix issues with operations order
* Add flag to remove a preference if it's intent can't be resolved
* Add helper to allow setting minLines of a preference, since it's
common for things to get weird with the kinds of behavior we
are introducing everywhere
* Add support for nuking *other* preferences. For example with
Doze, many devices have custom features and a extra_settings
panel which is redundant with the switch. Now we can trivially
override the one we don't want.
Change-Id: Ibb14b05add56b403013e908db1105dce9d34faad
* Added a proper API for this thing
* Pass objects around with necessary metadata, pre-filtered and sorted
* Added event log and service dump
* Simplified locking and adjusted for performance / correctness
* Clarified/beautified code where possible
* TODO:
- Write profile descriptions
- Finish the UI
- Clean up javadocs
- Do something with per-app profiles, maybe
Change-Id: Ie2ef84031e81a18e95dcd62392c7e6939860d933
* Allow CMParts to update the summary (or any detail) of a preference
so it can be shown correctly in the UI.
* Also some cleanup and refactoring around the parts list.
Change-Id: Idc16a7eb1a1e4170671fd068bd240b88fadfb577
