* Since we removed onehand from settings
we need to make sure user doesn't have them
set in settings otherwise we will hit
ArrayIndexOutOfBoundsException exception.
* Fixes : BUGBASH-1525
Change-Id: I7a5737ecfe5e70c3f0108c03b3e8745eade80433
(cherry picked from commit eb8fc0648f645a265ce8d1b6daf575795eb69510)
*) This was initialized from Settings.Global.DEVICE_PROVISIONED and it is no
longer possible to access system settings during provider startup since:
235272a216
*) LINEAGE_SETUP_WIZARD_COMPLETED has been deprecated since 14.1:
797a45aa69
*) We will later cleanup the unused setting during topic:pie-db-upgrade
Change-Id: I185648ca25995fae80362642d297573795d04bfa
*) Migrate database from cmsettings.db to lineagesettings.db
*) Remove old CMSettingsProvider.xml shared_prefs.
*) Remove the code to disable the PreBootReceiver component.
PackageManager is not yet ready for component lookups when
LineageSettings is called during fw/b service startups.
However, the preboot intent is only sent when the build
fingerprint changes so disabling it doesn't really buy us
anything. We also track and check migration state in
sharedPrefs anyway.
Change-Id: I636f8315ce8a36f6d223d6a5accfe11c40ef9570
*) Support separate normal and dnd led brightness levels for battery
and notifications.
*) Move lineage-specific notification bundle extras definitions from fw/b
to LineageNotification here in the sdk.
*) In addition to the existing bundle extra EXTRA_FORCE_SHOW_LIGHTS, add
a new extra EXTRA_FORCE_LIGHT_BRIGHTNESS that can be used to override
the brightness level set by a Lineage system setting brightness level
on a per notification basis. This is used by the brightness sliders
in LineageParts that otherwise would have to juggle changing / restoring
the system led brightness setting whenever the a slider is on display.
*) Disable all lights in dnd mode when lineage setting ZEN_ALLOW_LIGHTS
is set to 0.
Change-Id: I917f402a291682b582f68c8324a33c461357dad9
* 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>
The *DelimitedString* settings methods that we patched into
frameworks/base in <= 14.1 aren't used by anything else so move
the minimum code needed here thereby allowing us not to have to
add the frameworks commit to 15.0.
Link to previous code that was in 14.1:
https://review.lineageos.org/#/c/65703/
Change-Id: I3ec10e406e642ee90f5c2dbd89e598ea97682f67
This allows to start protected application from the "Protected apps"
activity without re-inserting the secret code.
Change-Id: Iaf727d741ef8e302b76a566ae9cd6a5031c85079
We don't need it because we don't support using the returned cursor
directly, and it can cause deadlocks when being called from platform
code.
Change-Id: I2f85be1152569ba27e4622d310d867e20965faa3
* Do not break boot if clock position tunable is unset
* Fixes I2412051289a922dfc72cdf266b47f32cf7aaa31a
Change-Id: I8d841f324f5bf8499365ca48cdf6aa4710ccd957
* 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
If the database needs to be created, it will not be upgraded. So, if the
device was provisioned and the table wasn't created, we don't upgrade
and so we cannot bring the old flag to the new location.
Fix this by setting the new cm provisioned flag on database creation.
Ticket: CYNGNOS-3017
Change-Id: I1e961f1cb2d06c55c1e92ef63c6dbaee17dbc304
Signed-off-by: Roman Birg <roman@cyngn.com>
Since DEV_FORCE_SHOW_NAVBAR was moved to global, the test needs
to query its value there.
TICKET: CYNGNOS-3016
Change-Id: Ided274ec065ec989b4ca4f172ec569adb74cbfd5
