Enable dex2oat64 usage on device
Bug: 153380900
Test: boot and install an application.
Change-Id: Ifff726eb2f8bd315a42c02bdca9ff10cf027a06c
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
* first-boot is set to quicken to reduce first boot times
* we are installing with speed-profile to have balance
between time taken to optimise and runtime performance
* once device is in idle+charging, bg dexopt will compile
for maximum runtime performance
[ghostrider-reborn]
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
* ref: P-404/android_device_qcom_common@87fc9c5
This causes weird inconsistent scrolling behaviors, even on v5.4
Change-Id: I1025014bb31aae15c79579c31cd134c35c2d527f
* Implement a smarter system on whether to connect to the provided 2Ghz or 5Ghz network.
Change-Id: I4f8363c712d07c64b2bad25538474003a56976b3
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
Currently Min, Max and default values of gEnableNUDTracking in
code are:
Min: 0 (Driver will not track the NUD failures, and ignore the same)
Max: 2 (Driver will track the NUD failures and if honoured will roam
away from the connected BSSID to a new BSSID to retain the
data connectivity).
Default: 2
In order to enable NUD tracking after NUD failure by default,
remove entry for gEnableNUDTracking from ini file.
Change-Id: Ie8ed6d12f373891d11727b1f903825a7fc145750
CRs-Fixed: 2559325
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
* This enables Deep Sleep mode, additionally to QPower
* With this configuration, QPower manages the new Deep sleep mode
-> Leads to amazing power savings
Signed-off-by: DarkAngelGR <asavvo01@gmail.com>
Change-Id: Ie7b8bec94da2707e5ae507682169d0ad26b99163
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
QCOM's driver can support a max of 512 scan results. Ensure that
wpa_supplicant is in sync with that number.
Bug: 74724482
Test: Device boots up and connects to wifi networks.
Signed-off-by: xNombre <kartapolska@gmail.com>
Signed-off-by: Marco Zanin <mrczn.bb@gmail.com>
Change-Id: I7cc7f0f604a0a16036080256e672d0b3127840bc
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
Those parameters need to set for Hotspot 2.0 network
interworking=1 : Enable Interworking
hs20=1: Enable Hotspot 2.0
auto_interworking=0 : Do not automatically go through Interworking
network selection in wpa_supplicant
Bug: 118633353
Test: live test with Passpoint AP
Signed-off-by: Ecco Park <eccopark@google.com>
Change-Id: I04e77be3d008d012690d4f4185a4c80d9b660df2
Signed-off-by: PainKiller3 <ninadpatil100@gmail.com>
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
Bug: 73301881
Test: Verify that the connected MAC randomization ~3 seconds delay problem is gone
Change-Id: I73dbeb9e9d0e740883c81384f3fee9b074292cd2
Signed-off-by: PainKiller3 <ninadpatil100@gmail.com>
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
* Redmi Note 12 5G
* This device using Snapdragon 4 Gen 1 aka SM4375 ( holi base platform )
* So.. add that device because use same platform
Change-Id: I77d39cf4954f71e2c238e3ff352b9574747ff92c
* F linker : CANNOT LINK EXECUTABLE /vendor/bin/hw/android.hardware.nfc@1.2-service: library vendor.nxp.nxpnfclegacy@1.0.so not found: needed by main executable
ag/16564596 will change default value to false.
Configure correct overlay configuration.
Bug: 212488775
Test: manual test & build
Change-Id: Iaf1a0a23dae69fde5995e591a757a8ef5374d5b5
Those keys will be embedded into VtsSecurityAvb on host side
instead, to verify the GSI image used on the device.
Bug: 149806769
Test: build and checks those keys are removed from
$OUT/recovery/root/first_stage_ramdisk/avb/
Change-Id: I8a002ba6f1421fb460056ccae6572050bdb0ce3c
As of I3c7aed1bdb45db728d319f7d757400e44d232283 the Bluetooth stack
defaults to reasonable defaults that should work for all devices.
Change-Id: I056d63c4c8a2727e384172e964dc0000b6773504
* These are currently in FrameworksResTarget, but were
moved to sysprops in Android 13.
976d33062b%5E%21/#F0
Change-Id: I5bff67a15c537e8a47a19f30776fca6bf2c9fbe5
