| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Bug: http://b/215753485
This warning is introduced in clang-r445002. In code where the bitwise
operation was used to avoid short-ciruit evaluation, make that explicit
by introducing temporary variables.
Test: build with clang-r445002.
Change-Id: Ia7ccf1d48922d926313f691888d26c3e314c1056
|
|
|
|
|
|
| |
error: build/make/target/product/gsi_keys.mk does not exist..
Change-Id: I7ac37f3e104f1bc6dce504ca29fcbf078127b399
|
|
|
|
|
|
| |
Test: make android.hardware.sensors@aidl-multihal
Fix: 206867060
Change-Id: I9b78a0f25117d11fdf4beb1e0913393c1c14620d
|
|
|
|
|
|
|
| |
Bug: 220306859
Test: atest
Tag: #feature
Change-Id: I300369d36399ffb558b98bafc2478b872d09faba
|
|
|
|
|
|
| |
- Its set in default.prop
Change-Id: I8d94738978b3ef3f146a938a592500437bfc1b00
|
|
|
|
|
|
|
| |
* Size decreased from 148 mb to 12 mb.
Signed-off-by: Jabiyeff <cebiyevanar@gmail.com>
Change-Id: If680f2b0511f9e348973ea2a98f9f832745f6d79
|
|
|
|
|
|
|
| |
* qcom-camera topic hasn't been ported to 19.1
* Keep building vendor.qti.hardware.camera.device@1.0 interface lib, IMS stack and possibly camera HAL still needs it
Change-Id: I87bcd5b54ad986d5844df50de243fc1a18507198
|
|
|
|
|
|
|
|
|
|
| |
Enable display kernel driver idle timer, which allows dropping to lower
refresh rate earlier and without additional overhead.
Bug: 160682800
Test: track idle timer through systrace
Test: zone test, scrolling
Change-Id: I6e82b58026d7b31cf0cabc0db7bb6277f6731d12
|
|
|
|
| |
Change-Id: Ic0fbdc97961808eba939b5785a4e1c2a275bed63
|
|
|
|
|
|
|
|
|
| |
- I need to revist this later, rollback for now.
- Keep prop to set frame rate multiple threshold to 120 because https://github.com/search?q=Ie4d5c8c9a45079306ad51e1607ae72eb9493ee0c&type=commits
This reverts commit 5fece213ba7bf9c4cfd85f3e1873d1e3291bb551.
Change-Id: I95ad1841a2a4206b681a8503c190dc7ddf4b2cf3
|
|
|
|
| |
Change-Id: I591b4ae4bc0adaa5f57e19ccb5d06dd5f1a42fcd
|
|
|
|
|
|
|
| |
- Our device doesn't support doze
- Fixes AOD flickering issues
Change-Id: I44855e85f7d9e26666a8efb79afc202c69770615
|
|
|
|
| |
Change-Id: Ic8ce5064ca3e27432331ac679b7dd3df166089
|
|
|
|
| |
Change-Id: I2f724061fd974cc6f20dc2abd64ee61c0167789a
|
|
|
|
| |
Change-Id: I6b7d0b928e3d368ce3253f6716f3df6fc628ca02
|
|
|
|
|
| |
ref: gs101 - android-12.1.0_r8
Change-Id: Iadd9780769f3f7eda9476d93ecc0817b51d6ba87
|
|
|
|
|
|
|
|
|
| |
Caused incoming caller number not being parsed correctly by Phone app on
VoLTE and VoWiFi. No idea why Xiaomi enabled this ancient prop.
Signed-off-by: Jyotiraditya Panda <jyotiraditya@aospa.co>
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Change-Id: Ie3e3459558be2bad2938aee02e1aa25da47ecd31
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a squash of the following:
1. Set refresh rate idle timeout in SF
* This allows refresh rate to drop to 60Hz when idle,
leading to minor power savings.
* Kanged from redfin with minor modification.
2. Relax automatic refresh rate switching
* In some cases there maybe a slight flickering while
switching refresh rate. Increase the timeout to
reduce the frequent switching and improve UX.
* Move the props to product to override the ones in
vendor which is set by display HAL configuration.
Change-Id: I5fbfd45fb30479db46970214db15a115acb075ef
|
|
|
|
| |
Change-Id: I0a87ff5b2c475769cd75e0fcbd79d230f711c5c1
|
|
|
|
|
|
|
|
|
| |
- ref:
1. ghostrider-reborn/android_device_xiaomi_lisa
2. ArrowOS-Devices/android_device_xiaomi_sm8350-common
- Adjust and cleanup as per veux
Change-Id: I9fc92e55c1af3e3820670523b59f3fb04270bd66
|
|
|
|
| |
Change-Id: Ic070c507aeaeb98ce859fe00b95f3a6e5df26a8c
|
|
|
|
|
|
|
| |
- obsolete on android-12
Ref: I97738435edd07e8b6770372cd935218c1a9cd984
Change-Id: Ibbc8d35961d919ccdc454ef2043824f38191637e
|
|
|
|
| |
Change-Id: I69a14e00cfc3291175351259f2d8cbd6b0dc827a
|
|
|
|
|
|
|
|
|
| |
* It's largely for testing purposes and it consumes
a large amount of memory. If your hardware doesn't
have graphics then it can be useful, which isn't the
case for shipped devices.
Change-Id: I2348718ad3afba846498572161fa7e83dd8b7ce9
|
|
|
|
| |
Change-Id: Iea0976ae3b43312b4b596e004582cbe4440b1aff
|
|
|
|
| |
Change-Id: I5c54643b3d6d6ea4e5f847870a5266bb96342583
|
|
|
|
| |
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
|