* AOSP "Smooth display" setting is just a toggle,
some devices support multiple refresh rates so
add support for it with a ListPreference.
Change-Id: I3da3d2b86e61ed3caf9af5770d8bdb4485817b97
Not sure why Google assumed that showing this setting is only useful
for devices with FP sensor built into a side-mounted power button.
Change logic to preserve check for side mounted (really, power-button
mounted) FP sensors, but allow any device which has a a rear or front
mounted sensor to show the relevant setting; so users can toggle it.
Bug: Enchilada (Oneplus 6, capacitive FP sensor on the back) no longer
wakes & unlocks from screen-off with FP sensor touch after QPR3 merge.
Test: Apply commit. "Touch to unlock anytime" setting is now visible;
enabling once again allows one-touch wakeup-and-unlock-on-successful-
FP-auth, does nothing with failed FP auth, while disabling toggle
requires pressing power button to wake screen first before FP auth
will unlock.
Change-Id: I4d8204b5fed7d43baa93d6793e7280260ae404d6
This is based on the following changes, adapted to Android 12
considering the fact that AOSP now supports FOD as well as
fingerprint sensors embedded in the power button:
Author: d34d <clark@cyngn.com>
Date: 2016-06-23 11:21:45 -0700
fingerprint: Allow devices to configure sensor location
The text for enrolling a fingerprint always assumes the sensor is
located on the back. This patch adds a config integer that defines
where the sensor is located on the device.
0 = back
1 = front
2 = left side
3 = right side
This patch also adds a new drawable that shows the front of the device
when applicable.
Change-Id: Ia8f5f8ff4ba4d13d35aed3052f60ff665dd4f294
TICKET: CYNGNOS-3089
Author: Paul Keith <javelinanddart@gmail.com>
Date: 2018-01-26 22:23:03 +0100
FingerprintEnrollFindSensor: Don't overlay front for side sensors
* Both the base image and the base image + overlay are equally nonsense
for devices with a side fingerprint scanner, but for those that overlay
a custom fingerprint enrollment graphic, this image overlay wreaks havoc
* Only set this overlay to be visible if the sensor is on the front, to
allow devices with side sensors to only overlay the base image
Change-Id: I7cbcea4830d4526cf9f7d139e7f84f21117fa9c4
Author: Michael W <baddaemon87@gmail.com>
Date: Thu Jan 17 21:44:28 2019 +0100
Settings: Make find fingerprint look great again
* The current logic places the animation based on the size of
the whole overlay instead of the image, which is a fixed-size png
* Get the size of the image instead and place the dot relative to it
* Also use "wrap_content" and add a padding to the top so the
distance to the text is a fixed thing, not depending on how
much space relative to the wanted space it actually takes
* Preview: https://imgur.com/a/XanJ2aP
Change-Id: I2bd08cee1abd1c6bad78ca1efc2189e573ded3cc
Author: LuK1337 <priv.luk@gmail.com>
Date: Sat Dec 15 17:11:41 2018 +0100
fingerprint: Remove unnecessary spacing in enroll layout
* This makes it look ugly on 480 dpi devices.
Change-Id: Ia1bbd443063a125878dddd12e5c6a816d289fb82
Author: Bruno Martins <bgcngm@gmail.com>
Date: Thu Mar 17 10:30:41 2022 +0000
FingerprintEnrollEnrolling: Set proper dialog message when user touches fp icon
Change-Id: Iafd86e636b0c54bbddcf26d153cc671259391259
Author: Michael Bestas <mkbestas@lineageos.org>
Date: Tue Dec 6 20:40:45 2022 +0200
Use AOSP string for side fps enrollment
Change-Id: I9267b6a75716f45044f4d7a51650ca4f928b104e
Author: Bruno Martins <bgcngm@gmail.com>
Date: Tue Apr 18 16:16:34 2023 +0100
FingerprintEnroll: Add config for dedicated side mounted fps
Google likes to assume that there only exists devices with
fingerprint sensor embedded in the power button, but that's
not always true. Since specific enrollment messages were added
just for those devices, we need to address our own usecase.
Change-Id: I56a7d7fe0374fe5a1fce5e24bdbb265cb5edc246
Change-Id: If372ef50c4a719e89a4e80cc20e3eb445af61bc6
When an app target pre-O releases, the default max aspect ratio
is 1.86:1 which leads to ugly black areas on devices that have
screens with higher aspect ratio (for example Galaxy S8/S9).
This change adds an option to allow users to change aspect ratio
for pre-O apps to full screen aspect ratio.
Change-Id: I0fb73511cf654ee22a4cfb7aef252008f8db8855
Splitted from commit 5aa2f34, adapted to the Lineage SDK
and squashed with commits c6dc688 and 19105ab.
Change-Id: I7516c833ff39de6bdb36c815a5292606cbaa0533
Read and write POLICY_REJECT_ALL instead of manipulating the setting
designated for the restricted mode allowlist.
Requires: I74407c21cd4ed2cdd932d634577ae07d0bad67b1
Change-Id: I354fae215dcb15e1bf3a67ff4c94803eb60fcac1
When Google introduced commit d3b35f2, all the custom addons for
per-app network isolation became hidden on devices that set the
overlay config_show_sim_info to "false".
Expose only the toggles that really make sense, i.e. for the mentioned
usecase, leave the main toggle (restrict all), WiFi and VPN data
toggles.
Change-Id: I4720483d98ae69fbb6eec8fa749e8d071e91c629
*) Add options to disable all cellular, vpn and wifi data
in app data usage settings.
*) Disable the existing background data and unrestricted
data usage options when all cellular data access is
disabled.
*) The vpn data option can be selected independently from
the Wi-Fi and cellular options.
*) Prevent DataSaverBackend from overwriting uid policies
This is a replacement for the appops menu based cell/wifi data
restriction settings in cm-13.0:
Author: Danesh M <daneshm90@gmail.com>
Date: Mon Mar 7 15:17:59 2016 -0800
Settings : Add per app internet/data control
CYAN-3976
CRACKLING-834
Change-Id: I13192df837c057b5cadde8f31532e12daaf3c1b0
Change-Id: Ic087c27a5ed0bdb84bb8f297c425c6bcbffec848
(cherry picked from commit d4a2eea698cbc4636a635d60f2a52ec1bbc36ba2)
*) Add option to disable all network traffic
in app data usage settings.
*) Disable the existing background data and unrestricted
data usage options when all network traffic is
disabled.
Change-Id: I0aaf5703d6dd5d6e6ec3cda3940f28833fe052ea
We already make sure to use a copy of the Intent, but now we do so
earlier. See bug.
Bug: 353680402
Flag: EXEMPT bugfix
Test: manual
Test: atest com.android.settings.users.UserSettingsTest
com.android.settings.users.UserDetailsSettingsTest
(cherry picked from commit b7240e2f0c50455a1c8f3ae1fc4f27d55b86e89b)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:d8166274a030372f9b1184137fceef9d4dac83e1)
Merged-In: I860e9e606de6b8d3c99fa52a63b72ba7a99ce179
Change-Id: I860e9e606de6b8d3c99fa52a63b72ba7a99ce179
- if the user is locked
- and the user has chosen to hide sensistive content when locked
Test: manual with a work profile with a different pin
Bug: 378088320
Flag: EXEMPT bug fix
(cherry picked from commit 9df37c3f8be2dedd2e44e52da4de45fba33c6a6e)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ac4d72060aeb282d5c1c024438ed9e0689b50031)
Merged-In: Ia70454d9859fb788ffa1f48f88760f88c354cdff
Change-Id: Ia70454d9859fb788ffa1f48f88760f88c354cdff
Activity.getCallingPackage() does not always return the package
name of the actual calling app. getLaunchedFromPackage() should
be used instead.
Bug: 389681530
Test: manual
Flag: EXEMPT bugfix
(cherry picked from commit 70bd3efe0674bccb0d454845d86fb2402779a7bf)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:48e4b5e1af2156dc0db1546df1c14030e77e542e)
Merged-In: Ibdbc45e53f4aa46fae79fa234705b3735bfda4cd
Change-Id: Ibdbc45e53f4aa46fae79fa234705b3735bfda4cd
After vetting the intent, use the component we used for the vetting.
Bug: 353680402
Bug: 365739560
Test: manual
Flag: EXEMPT bugfix
(cherry picked from commit d3e34060803c97ae05719fe9301026e5c54892c8)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:586422578de58f1da68fd9becf89a08ea2ae0058)
Merged-In: Iff0d820c1261c29eb6703bf89194339cba700688
Change-Id: Iff0d820c1261c29eb6703bf89194339cba700688
We'll allow devices to add touchscreen gesture settings
using the LineageHW TouchscreenGesture API.
Change-Id: I569b91ed66d34097a2bd96fb56af660a2702224b
* This causes the options to go off screen and almost always
require scrolling in order to reach all the options.
Change-Id: I3880982978aa50f11bf24b4da6e91a0917181811
The NFC preference in Settings -> Connected devices -> Connection
preferences doesn't listen to changes from the NFC tile. (This wasn't an
issue in Android 10, because there used to be a SwitchPreference that
listened there.)
Change-Id: I85842db3faa558ea61bc878ca76ff6d8ce1a4b02
The title of the USB preference screen ("USB Preferences") is
inconsistent in several ways:
1. It doesn't match the title of the preference that launches it
2. No other preference screens say "preferences" in their title, since
it's redundant
3. It violates the Material text conventions, which prefer to not
capitalize titles in the UI
This commit changes it to "USB", which fixes all of the inconsistencies
listed above.
Change-Id: I7330a9e4e121d57ee2140ef60aefb4412b1fe728
* If a device has its own panel, we should replace the item under
display settings instead of having to clutter up the dashboard.
* Devices that provide Doze settings typically implement own AOD pref,
so hide AOSP one.
* This uses the new RemotePreference API to allow the external
app to update the view.
* The action for this is "org.lineageos.settings.device.DOZE_SETTINGS".
Co-authored-by: Bruno Martins <bgcngm@gmail.com>
Change-Id: I22fd7e6307b370807415ce2132bed4808b2befe1
Having double quotes around the strings causes crowdin
to export translations with unescaped quotes.
Removing them has no side effect and fixes crowdin export.
Change-Id: I93865d793eef711f8738e00e843e9d4670724c66
* We need to disable A2DP HW offload on FP4 for now, however
disabling developer settings would enable offload again and
break SBC and AAC audio. Just remove this section and allow
this setting to persist after disabling developer settings.
Change-Id: I5b65b3887d68ac684d7ea78de0ee89fb7db9bb0f
Open up the LineageOS legal info in the browser.
Change-Id: I263ccc0509e275d17512528deb606341d58e7a0d
Ticket-Id: CYNGNOS-1895
Signed-off-by: Roman Birg <roman@cyngn.com>
