Since config_roundedCornerMultipleRadius was phased out from T,
frameworks read the rounded corner dimensions from rounded.xml.
This resulted in bonito & sargo not rendering the rounded corners
properly.
Change-Id: I5cbdcd959fd7943c74ded9d209e06755b1120670
Test: manual testing - ensure that the brightness value in
Settings>Display>Brightness Level can go the full range from 0% to 100%.
Change-Id: Ife1f2796bb3b8ec5f508903afd30a31556b49cbe
These are replaced by formal mainline module overlays.
Bug: 143464763
Test: Send for Wifi regression tests
Change-Id: Ifa1250a58cc305bc96135dd2c315dc5a96fd0506
Updated power profile wifi controller idle current (ma) to new
calculated results.
70ma reported at 4.2V. The controller runs at 3.7V so the inputted value
is 79ma.
BUG: 123521767
Test: N\A
Change-Id: I689ff3ce47ae611c5b175310e8940cd13ffe873c
"ambient.on" is used to estimate the power consumption
by always on display.
BUG: 112538888
Test: Compile, flash, check Advanced battery usage.
Change-Id: Ieaec0b0bc05939868ce602262325c9665151639f
Cellular, Wifi and GPS power profile for Taimen is updated to values
based on device power measurements.
BUG:79879615
Change-Id: I846b05277b264375d18d5a4451e14a1060743553
Power profiles now support ambient and video.
Remove power.none because it is never used by batterystats.
Remove the radio values that are never used because
modem.controller.* are present. Update audio.
Fixes: 63738468
b/70531798
b/74125473
Test: Boot phone and dump BatteryStats
Change-Id: I4be783bc3c075ac4a94ff8a2e82e144b43d7d331
This should always match the documentation in frameworks/base, since
that's the canonical document.
Bug: 74328541
Test: N/A
Change-Id: I7b3266bb3c07631f13fe295ee883909ce24aff79
Power profiles will now support active and cluster costs.
Some power profile values have been renamed per b/67752294.
Test: dump battery stats
Change-Id: Id479c233dc7456420dc3da5a80dfe03c51caa906
config_displayBlanksAfterDoze was removed from wahoo and needs
to be set on the device overlay
Bug: 71897888
Test: flash taimen, press power button when in AoD
Change-Id: Ic54a0bd2f951b62726ae5451bfe83132f619af6d
Also, move to a nits-based autobrightness curve.
Bug: 71706239
Test: Boot Taimen device, see we get a PhysicalBrightnessMapper in
dumpsys display
Change-Id: I01c6cc1d3abe1c3e547556fc04a41225719cd94f
Right now, the dim brightness is way too dim to the point where most
things aren't visible even in low indoor lighting situations. Upping
this a bit makes it still noticeably dimmer but a lot more visible in
normal usage. It may be worth increasing further, but this is a good
place to start.
Bug: 65346115
Test: wait for the device to dim, see that's actually visible under 4k+
lux ambient light.
Change-Id: Idf89f1309d7eae8d5ce4d617e6117c0f6cc76562
This was erroneously removed when updating the autobrightness curve
under the assumption that the default value was 1 but it's actually 10,
which is way too high.
Change-Id: Ie5b81c23d9d30560f5a686d40bc090d3cbdf3c4d
Fixes: 64708230
Test: manual
Updating all power profiles using the same scripts. Previously,
every power profile was generated using different algorithims.
b/62389228
Test: Run a normal android workload and verify the app blame
is reasonable
Change-Id: Idff05eb0fa776a3dae7bde2952ec80b031834d54
New hardware units have a mapping that's actually linear, so we assume
that the curve is linear here and have the kernel fix it up for us if it
needs to.
Bug: 63606090
Test: manual
Change-Id: I05c98115b20e0328654ca42ac58244ea81e19940
This reduces the minimum brightness to 0.009 nits from 0.09 nits
(on EVT1 and 2).
Bug: 63834045
Test: manual
Change-Id: I7d76eae6e76de5ed3a125f8f4b42d1bba2f57ac7
The control points from another device were directly copied over to
Taimen, but Taimen's display's display has a very different mapping
between backlight value and actual produced brightness. These new values
bring it inline without our ML learned curve compensating for this fact.
The one difference here is that Taimen can go brighter than the devices
the model was trained on so an additional point was introduced. Based on
visual inspection the curve looks almost exactly linear in the last few
points before it hits the ceiling, so the final point is just a linear
extrapolation from Marlin's final two control points to Taimen's maximum
brightness.
Note also that Taimen's display can't be set above 223 in normal use.
Every value about this is an "overdrive" setting and greatly increases
the risk of burn-in not to mention using significantly more power.
Bug: 62027049
Test: manual
Change-Id: Iad725edd7adbe4505fd13237a6cb3aa2efd9bbcf
Make EFFECT_CLICK 10ms and LONG_PRESS 12ms.
Bug: 62176703
Change-Id: Id676a6581e8beff9ad2d951b2d9f405d38d374b9
Signed-off-by: David Lin <dtwlin@google.com>
