The wrong thermal-config was copied for VR mode.
Bug: 37544246
Test: verify that the correct VR thermal config is on-device
Change-Id: I8605336c5fbdac7450036883a68f1f25f111d286
This will allow AAudio to route audio data through a new service
that uses ALSA MMAP/NOIRQ mode.
Bug: 63002656
Test: reboot, then "adb shell getprop aaudio.mmap_policy" should be 2
Change-Id: Id2f692ac9350e4c308f17d86ee8d5cbb858bb565
Keep the original property also, to make it easier to experiment
with old and new libadm.so
Bug: 63810681
Test: round-trip USB latency unchanged with old or new libadm.so
Change-Id: I3ba8a670f6d8498a5899c352c544cbd63d815169
This reduces the minimum brightness to 0.009 nits from 0.09 nits
(on EVT1 and 2).
Bug: 63834045
Test: manual
Change-Id: I7d76eae6e76de5ed3a125f8f4b42d1bba2f57ac7
RESTRICT_VENDOR_FILES cannot be set to also enforce "path" as some vendor
specific modules related to IMS VT still needs to be installed in system.
Bug: 37330627
Change-Id: Ic94a63b4a53c876553a1c48a7d7a986ac11f790e
Signed-off-by: Thierry Strudel <tstrudel@google.com>
fix rx/tx mute when making call with 3-pole headset and USB dongle
Bug: 63680197
Test: manual audio sanity test
Change-Id: Ie8b3b6d0c5666539a794459e425570f4e5d7d447
This also provides tuning for touch size information.
Test: flash and look at touch size with pointer location enabled
Bug: 62871286
Change-Id: I1dafed6b482a74d9baeac162be1dc831370a5ebc
Bug : 62663757
- Change low persistence(LP) mode brightness from 255 to 159
- If panel version is 2-1, Set LP mode brightness to 255
Change-Id: Ie3754ac9ab11347e4f4edf91a607a17fc6b776fc
Newer revisions of hardware have changed the placement
of the bd_therm thermistor. To allow software to work
on both old and new hardware, we've renamed that thermistor
to bd_therm on the new hardware, which requires a new
set of throttling constraints using that thermistor.
Bug: 63344220
Test: booted old and new hardware, checked configs,
and verified that throttling happened at the right
temps according to the thermistors
Change-Id: I9639142551a8fc1dcbe65559045ae40b2ace5537
- VoIP handset spk analog gain 97->93
- enable handset sidetone
Bug: 62826294
Test: audio sanity test
Change-Id: Ie4a0c92a445589f4345f5a902373d21b0f52a14e
Signed-off-by: David Lin <dtwlin@google.com>
The intervals(dB) by Ringtone/Alarm/Notification are too small to be recognized.
the gap between each step 3dB -> 4.3dB.
Bug: 62826294
Test: notification playback at different volume steps
Change-Id: I02180a71878be65d1d2a976b42ba7c768e903a80
For normal mode, make throttling more aggressive on Taimen,
in line with tuning on our other devices.
For VR mode, add an aggressive throttle just before shutdown.
Bug: 36458508
Bug: 37544246
Test: Booted, checked throttling with adjusted temps
Change-Id: Ia192535ed305cd6e8e1fbae4c53a7b4b7e3e8c23
Remove the cad calibration file and use only factory calibration
file.
Test: Tested on Taimen
BUG=63146009
Change-Id: I3cf1a0084723b925eaa358830f76d48da0841b4e
No change in latency for Taimen
Bug: 62375603
Test: Loopback shows reduction and no glitches on Walleye, no change on Taimen
Change-Id: I6dc85ecdc825462acb4e1cda3227fb4d4f93c56e
- VOIP mixer Tx gain
- set app type for VoIP
- set acdb_id for VoIP speaker
- set echo reference for VoIP speaker
Bug: 62826294
Test: audio sanity test
Change-Id: I8c05d666d3b4fe8719419d3dde7954e91201397b
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
Bug: 62732748
Test: Boot into recovery; check that recovery menu and 'View recovery
logs' don't have obscured text.
Change-Id: I03387573a4e474bff7d823f5390acef61a9312e8
(cherry picked from commit 174e936f52)
