* The anti-falsing implementation from HumanInteractionClassifier
regularly prevents easy swipe to unlock or to pattern / pin
on the keyguard lockscreen, requiring multiple attempts
until accepted due to a hardcoded evaluation (5.0f)
while normal usage shows better results without it
* Another solved situation is remote device access like
Vysor or TeamViewer where the device is almost impossible
to swipe properly from a computer client
Change-Id: I1caf603bc6a3bf7794af724b8e48a9ebb96da971
* We shouldn't be changing the default behaviour anyway, plus
Airplane Mode toggle is horrid on 8.1 right now
Change-Id: Ie795443f840e023f0c67f2a6729a7d702bc37cd5
* Change Ibf1370ff3cb539a9a54002a8704922744a3ca5d7 on fw/base
added support for a security feature. This feature listens
for multiple back button presses in succession and then
returns the user to their home screen.
Change-Id: I5a386782ae2dcb0898491e1af48a73d6fb74a181
Globally enable full alarm info in quick settings drawer.
Screenshots: https://goo.gl/photos/ycuvZZFD1ssyWu8B6
This detailed info is pretty useful why not enable it for all devices.
Change-Id: I46ccc3547922b6ab5fdcf8798bd5269b7465a92d
Signed-off-by: Sebastian Haderecker <sebastian.haderecker@gmail.com>
With Android N this feature became less relevant since a subset of
the toggles is available without fully expanding the notification
panel. This gives better access to the notifications with almost no
functionality loss.
Change-Id: Idb66472b77e60f4ae753c5dd00f6588566cc3c63
As of fw/b change I14365389990eb06daaa127f5db66df45abf6c064,
we now have an option to long-press on power to enable torch.
To support this feature, we need to enable long-press on power
while the device is still non-interactive.
Change-Id: I4e2b4af86d397f68e119963054c33fd890c77cc5
Chrome Stable and Google Webview had incorrect
signatures. That was due to an incorrect method
of determining the right signature.
That mistake wasn't noticed because Android
disables the signature check on "userdebug" and
"eng" builds. It is only enabled on "user" builds.
So this commit replaces the wrong signatures
of Chrome Stable and Google Webview by the
correct ones and thus makes them avaliable
webview providers on "user" builds.
Main credits go to @KreAch3R for his
extensive research on the issue.
Change-Id: I081783b59254bfed0b2e3568ba8ae2801d86efea
Signed-off-by: Alex Naidis <alex.naidis@linux.com>
The framework disables aggressive power-save modes when appropriate,
such as when the device lacks a significant motion detector.
Thus, instead of enabling it in each device tree,
enable it by default for all devices.
Change-Id: I1999b04876f1ddce1574c050b6bc582e9a9a96da
If Gapps are installed, better webview providers
become avaliable.
This commit adds support for those and makes the system
choose the best provider: Chrome Stable>Google Webview>AOSP Webview
It also allows the user to choose between additional
providers from Play Store: Chrome Beta, Chrome Dev and Chrome Canary.
This patch is a collobarative work of:
mfonville <maarten.fonville@gmail.com> @mfonville
rapperskull <rapper.skull@hotmail.it> @rapperskull
Arne-Christian Blystad <arne.christian.blystad@bartec-pixavi.com> @Blystad
Alex Naidis <alex.naidis@linux.com> @TheCrazyLex
Bugfixes and move to an overlay by blunden <blunden2@gmail.com>
You can find more information on this topic here: opengapps/aosp_build#76
Change-Id: I006d814b7c12ffe4f29cd865c9d4cc6a60bc7783
