| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Change-Id: I1ae32e41ea3cdb1f3b5d7f81a57f548fa211c9ca
|
|
|
|
|
|
| |
Bug: 175231451
Test: CtsMediaTranscodingTestCases:MediaTranscodeManagerTest
Change-Id: Id25ce60b58ab29a8670695c77be20dd53d63981a
|
|
|
|
|
|
| |
- V13.0.8.0.RKCMIXM
Change-Id: I54c4a00971a42750a4b0809913250f72b0b7c167
|
|
|
|
| |
Change-Id: Ie4f78b6a13cb40cb67ce67f0269c2a94cc900326
|
|
|
|
|
|
| |
- not valid
Change-Id: Ib4fa4e0f878402808ce1ea8340df32eb877ef418
|
|
|
|
| |
Change-Id: Ia29ac831f57bc958b78163090c12e340f3b3b658
|
|
|
|
|
|
|
|
|
|
|
|
| |
Routing primary output before voip_rx output will cause unexpected
RX/TX path suddenly and unmuted voice stream during when system
plays touch sound and switches path between handset and handsfree.
Bug: 154290829
Test: manual test in VoIP
Signed-off-by: Jasmine Cha <chajasmine@google.com>
Change-Id: Ia60802ec887f0dfeaa0f93d151ba2f2c50e0d41d
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Ultra low latency playback is currently broken. Crackling audio
can be well noticed while playing WhatsApp audio messages or even
during some games.
- This patch routes all audio that normally used audio-ull-playback
paths to low-latency-playback paths instead, thus meaning we're
switching from ULL to LL mode.
Change-Id: I8adf8a67a6151843cff5860f430d87727ad8f4c2
|
|
|
|
|
|
| |
- doesnt work and kills alarm audio when vibration is enabled
Change-Id: If8b4de516f60b0a4187b976c8d86b93e58119455
|
| |
|
|
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
Change-Id: Ib9248d9e7101998975567e23dd6092dbef6b7410
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Change-Id: I6fdcda70a5e0498e65e95e29480676dd8f8d7ada
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is because of the following reasons:
- Many build scripts force disable it anyways by settings OVERRIDE_TARGET_FLATTEN_APEX env flag so why bother rendering differences in official and local builds [1][2].
- Compressed apex causes issues with OTA on A only devices [3].
- Compressed apex may cause issues on devices which do not meet kernel requirements [4].
- Highly anticipated mainline modules update aka Play System updates is limited to OEMs/Pixels only [5], we don't do such things on AOSP; shipping Pixel prebuilt apex components feels somewhat unethical.
Ref:
[1]: https://github.com/lineageos-infra/build-config/blob/8e435ce7ff7c74097b3500e143380273e099aefb/android/build.sh#L9
[2]: https://github.com/LineageOS/android_build/blob/lineage-18.1/target/product/updatable_apex.mk#L19
[3]: RecoverySystemService: Failed to reserve space for compressed apex
[4]: https://source.android.com/devices/tech/ota/apex#kernel-requirements
[5]: "pushed to end-user devices, either by Google (using the Google Play Store infrastructure) or by the Android partner (using a partner-provided OTA mechanism)." as stated in https://source.android.com/devices/architecture/modular-system#architecture
test: m, boots and ota.
Change-Id: I5b5c2366398791100fa2222ef779ca4d90842211
|
|
|
|
| |
Change-Id: Ifa174b17f0f11a9c38864dd30e4e00523bc3ac81
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
| |
- Ref: https://github.com/ArrowOS-Devices/android_device_xiaomi_vayu
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
|
| |
- Ref:
https://github.com/xiaomi-sm6375-devs/android_device_xiaomi_sm6375-common
Signed-off-by: kleidione <kleidione@gmail.com>
|
| |
|
|
|
|
| |
* Don't set displayID as it's display-independent
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- ELF prebuilts were banned in PRODUCT_COPY_FILES starting May 11.
- Adding BUILD_BROKEN_ELF_PREBUILT_PRODUCT_COPY_FILES := true to
BoardConfig.mk temoporarily.
- See b/156534160 for long-term fix which should override this change.
Test: Build
Bug: 156534160
Change-Id: I7d80798d3b2d3818bc835fcede21de2e7ab04735
|
|
|
|
| |
Change-Id: I66713222ea83c6ccee39dc49effc36d59546c93f
|
|
|
|
| |
Change-Id: I5447126ffea6a8e8db9ef9d05aa7055f5f050b7b
|
|
|
|
|
|
|
|
| |
* The device's ultrasound proximity sensor is not active
during standby, thus it can't be used as a check before
pulsing. This fixes Ambient Display.
Change-Id: I1fc416247ed13cbfba245f37a4aafeae74ddbff7
|
|
|
|
|
| |
Change-Id: I96f218b55426cb5e04e7bc661fe6179d544e97ad
Signed-off-by: eray orçunus <erayorcunus@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
When the proximity sensor is in use, the smp2p_sleepstate
IRQ is fired multiple times a second, with each one
holding a 200ms wakelock. This is probably a bug in the
DSP firmware. To fix this, avoid using the proximity sensor
in doze mode, because sleep is preferred to turning off the
screen.
Change-Id: I5c54643b3d6d6ea4e5f847870a5266bb96342583
|
|
|
|
| |
Change-Id: I2aaa0c06b23b40aac120c325ce15fb0992463520
|
|
|
|
| |
Change-Id: I76e85e07f5a562b7e2a3683da264ccebff5c3613
|
|
|
|
|
|
|
|
|
| |
Veux supports switching between 60 and 120 Hz refresh rates, so let's
expose it in Settings -> Display -> Smooth Display for users to save
battery if necessary.
Test: visual confirmation after toggling several times
Change-Id: Ie698ec4d4e738afd2a9055dba2369233103a4f13
|
|
|
|
| |
Change-Id: I89280df82431980c40f415ff2e2862f7fe9eb8a6
|
|
|
|
|
|
| |
* to support both variants of the device
Change-Id: Idbf3d58c306a317ff21636c93c34b1420c714cba
|
|
|
|
| |
Change-Id: Icc7f1445a7ef12d1db9c49ddc1800e4476196411
|
|
|
|
|
|
| |
* From veux-user 11 RKQ1.211001.001 V13.0.10.0.RKCMIXM release-keys
Change-Id: Ifd9c2d64cced3ae02554aaf04eb2e2b06d9bb6ff
|
|
|
|
|
|
| |
* From veux-user 11 RKQ1.211001.001 V13.0.10.0.RKCMIXM release-keys
Change-Id: Ib63bbcc86ee346efa2a12cde6ff27221e893a792
|
|
|
|
|
|
| |
* From veux-user 11 RKQ1.211001.001 V13.0.10.0.RKCMIXM release-keys
Change-Id: I0ec4b4487bd41be4d1e60a33b48e24126790898f
|
|
Change-Id: I7c2239425ded71fa967d983a637564aaaef3b8a9
|