- 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)
With noop scheduler, I see dramatic jank with an irritant i/o thread;
going back to cfq, which doesn't have nearly the same negative impact
on UX.
Bug: 62375787
Test: boot, scroll a lot
Change-Id: I6a544075a7ae71830e8ea9cb6a594dd062941f35
Bug: 62249703
Test: audio sanity test
Change-Id: If5221697fd06ebdea310324434d8f063275dc259
Signed-off-by: taeho.youn <taeho.youn@lge.com>
Signed-off-by: David Lin <dtwlin@google.com>
This change enables the Information Element in QCMs driver, only
allowing the following IE in probe requests while the device is
scanning in an unassociated state:
- SSID Parameter Set
- DS Parameter Set
- Basic Rates
This improves privacy of the device, by reducing the fingerprint of its
probe requests, and removing IEs which contain uniquely identifiable
information.
Test: Verified via wireshark
Bug: 37281277
Change-Id: Icc0151c214723a3af7c112b8ea8de50d799450a1
