* according to what this file used for and how it comes on aosp(https://source.android.com/docs/core/power/values)
* it should be WRITTEN in model by OEM after doing a current test for all parts and used for battery consumption calculating.
* So just "update it all" to other device's profile is a wrong action
* as we have changed our architecture to 4.19, copy cpu/modem/wifi related values is sensible
* but as we are a tablet, it has a big/old/not power saving LCD screen, and from current monitoring, it really drags about 1A when full brightness
* reset screen profile to 290/950 is correct for battery recording
Signed-off-by: pix106 <sbordenave@gmail.com>
* as c999a1a2b9d975610ffa359ba34cb27d016165cc has unlocked setupwizard rotation, auto rotation default as "on" is not meaningless now
* (pix106) Adapted to RRO
Signed-off-by: pix106 <sbordenave@gmail.com>
* We don't need to manually set this anymore.
Change-Id: I1239ba541636e53f8ea4373d3815024f2cd60824
Signed-off-by: Immanuel Raj <iamimmanuelraj@gmail.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
[@jjpprrrr: camera ids
0: main camera
1: front facing camera
Therefore, block the rest of the aux camera ids.]
Change-Id: I543f078dd4dba30e1b22737d5c22d591e3fb34e6
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* if device is a LTE variant, telephony service will reset the prop
* show "Wi-Fi Only" instead of "Unknown" in settings baseband on wifi only variant
Signed-off-by: pix106 <sbordenave@gmail.com>
* android.hardware.radio keeps in retrying for wifi variant
* it is retrying by com.android.phone(TeleService.apk)
Signed-off-by: pix106 <sbordenave@gmail.com>
* cgroups and task_profiles exists in system/etc/task_profiles, but it does not has API26 ones so we add it
* Schedtune sometimes fail maybe because of this but still unsure
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
With my previous CL [1], we can override
rounded_corner_content_padding
at the Framework resource layer rather than the SysUI resource layer.
No matter whether
persist.sys.ime.can_render_gestural_nav_buttons
is enabled or not, there should be no observable behavior change in
this CL.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: Manually verified as follows.
1. Build aosp_coral-userdebug and flash it
2. adb shell cmd overlay lookup android \
android:dimen/rounded_corner_content_padding
-> 70.0px
3. adb shell cmd overlay lookup com.android.systemui \
com.android.systemui:dimen/rounded_corner_content_padding
-> 70.0px
Change-Id: I391a504482f25c17f9b67f7eb8f56f362da71ae0
Signed-off-by: pix106 <sbordenave@gmail.com>
