Expected as an array in Settings package.
Change-Id: I1e35fe6e2a1a6a18cb3216065dade964c2f405b9
Signed-off-by: Abhay Ruparel <abhayruparel2000@gmail.com>
* remove MIUI imported system.prop & vendor.prop
* Commonize both the system.prop & vendor.prop into one make file
* As it is treble enabled the system.prop is quite useless
Change-Id: I170ba44e6ee53f9bd66679df41062dc3ebb9cb2c
Signed-off-by: Subhaam <derksoul98@gmail.com>
This broke in commit a2fd40ee4a
[ 7.668496] init: cannot find '/vendor/bin/init.goodix.sh', disabling 'goodix_script': No such file or directory
Change-Id: Ie6b09c96be61d7218835286528478195df64d5b9
Signed-off-by: Akhil Narang <akhilnarang.1999@gmail.com>
Cpuset foreground boost is departed since
a712d4058f
Change-Id: Iab1834dbb8cce15480b5e11968bcfff7cc80177e
Signed-off-by: Lennart Wieboldt <lennart.1997@gmx.de>
* In O, the default setting for mobile data always active was
changed from off to on, meaning that when non-WiFi tethering
is being attempted, more than one connection can be active
* Since the first active connection type in this overlay is used,
reorder the values to get WiFi connections first, and then
any type of mobile data connection, instead of vice versa
Change-Id: I41f31ba1a2793e209ff439c9ba28a390fecdeecb
* send_mic_mute_to_AudioManager hasn't been doing anything
since Android 4.4, therefore there's no reason to keep it.
Change-Id: I74ed33265fccd59def5c2f9e67a9e8a28ce4dbc9
* the device doesn't have hardware buttons
* Hence the navbar needs to be enabled by default
Change-Id: I5ec129f0b797f32970483a73502522e155b2059c
Signed-off-by: Subhaam <derksoul98@gmail.com>
Replicate what Google did for SystemUI in this commit.
fabc743bcf
Registering a sensor seems to be an expensive operation,
and we do it on each screen-on event, so moving it to
an asynchronous task looks like a good idea anyway.
By moving all non-essential binder calls of the main thread or to the
next frame, we bring this down to 5ms, such that window animation
and Keyguard animation starts about at the same time.
The interesting part about the ExecutorService:
"Memory consistency effects: Actions in a thread prior to the submission
of a Runnable or Callable task to an ExecutorService happen-before any
actions taken by that task, which in turn happen-before the result is
retrieved via Future.get()."
(from https://developer.android.com/reference/java/util/concurrent/ExecutorService)
Change-Id: I4f37bb9a7dc9d7775d587d4ebd4b6619f3b77e81
