| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
|
|
|
|
| |
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
|
|
|
|
| |
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
|
|
|
|
|
|
| |
This reverts commit bdd491a7286fd023a608daf88ae7a868a11dd9a0.
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
|
|
|
|
| |
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a squash of the following commits:
1. Optimise dex flags for a faster boot
* Used multiple threads and speed profile to hasten the first boot
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Change-Id: I2cce5ddf7d50308511e81436fcac613b2c6537bf
2. Rework dex flags again
When I went through https://source.android.com/devices/tech/dalvik/configure my previous configs felt wrong, this one should be perfect (I hope).
Even though there is a slight trade-off for boot time by using the speed profile, we do make up for it by using 8 threads.
PRODUCT_DEX_PREOPT_DEFAULT_COMPILER_FILTER attempts to compile all prebuilts fully optimised to speed level, thus the phone doesnt need to deal with it.
I also do know that this might be a trade-off on size, but I do see the first boot time is more worthy to trade-off.
The speed level mentioned here runs dex verification and compiles all AOT methods.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Change-Id: Ic0156ff8956a7c5f53820be6db438f6f6399d3c0
3. Switch certain dexopt profiles to verify
Prebuilt apps like Gmail/Google App, will be updated by google play, and there is no need spend time and space optimising what is going to be replaced.
Switch to Google's recommendation of using verify for an OTA package.
Applications still stay on speed.
Instead, replace the install profile with speed-profile making apps perform better.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Change-Id: I2cce5ddf7d50308511e81436fcac613b2c6537bf
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Credits:
https://github.com/xiaomi-sm8250-devs/android_device_xiaomi_sm8250-common
- Adapte to pixelexperiece
- Drop doze
- Drop fod and pop camera
- Add Clear speaker
- Adapte SEPolicy credis: [Sebastiano Barezzi, Chenyang Zhong]
Co-authored-by: Sebastiano Barezzi <barezzisebastiano@gmail.com>
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Co-authored-by: kubersharma001 <kubersharma001@gmail.com>
Co-authored-by: TheScarastic <warabhishek@gmail.com>
Co-authored-by: Joey <joey@lineageos.org>
Signed-off-by: kleidione <kleidione@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
| |
According to AOSP docs [1] apps should use xxhdpi resources
for 440 dpi density.
[1] https://developer.android.com/reference/android/util/DisplayMetrics#DENSITY_440
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Signed-off-by: daniml3 <daniel@danielml.dev>
|
|
|
|
|
|
| |
error: build/make/target/product/gsi_keys.mk does not exist..
Change-Id: I7ac37f3e104f1bc6dce504ca29fcbf078127b399
|
|
|
|
|
|
|
| |
Bug: 220306859
Test: atest
Tag: #feature
Change-Id: I300369d36399ffb558b98bafc2478b872d09faba
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
| |
Change-Id: I1ae32e41ea3cdb1f3b5d7f81a57f548fa211c9ca
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
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>
|
|
|
|
| |
Change-Id: I2aaa0c06b23b40aac120c325ce15fb0992463520
|
|
|
|
|
|
| |
* From veux-user 11 RKQ1.211001.001 V13.0.10.0.RKCMIXM release-keys
Change-Id: I0ec4b4487bd41be4d1e60a33b48e24126790898f
|
|
Change-Id: I7c2239425ded71fa967d983a637564aaaef3b8a9
|