| commit | 2ad7722266c9ff11280567fbf5ae3c203893c94e | [log] [tgz] |
|---|---|---|
| author | John Stultz <john.stultz@linaro.org> | Wed Sep 23 02:09:15 2020 +0000 |
| committer | Amit Pundir <amit.pundir@linaro.org> | Thu Oct 08 19:30:44 2020 +0530 |
| tree | 8388dd7eedea5101ddd760559267e7220a895fc9 | |
| parent | b6d45bd2b97e1e9336434d9042f8739b5bcd1c80 [diff] |
db845c: Add missing etc/permissions/android.software.xml Since Android11 merged in, I have been seeing some odd crashes occasionally that was pointing to the fact that the AutoFillManager mService value was null. However, this same issue was not seen on HiKey960, with the same application and AOSP source. I dug around and realized we were not adding the android.software.xml file we add on HiKey960, and copying it over resolves the issue. Signed-off-by: John Stultz <john.stultz@linaro.org> Change-Id: I1bc88c67030b0ed69511acdf348c27367bf7213a Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
IMPORTANT NOTICE --> UNLOCKING AND ROOTING MAY VOID YOUR PHONE WARRANTY AND MAY BRICK YOUR DEVICE AS WELL. I'M NOT RESPONSIBLE FOR EITHER OF THAT.
Here is a reasonable guide to get you started on unlocking and rooting Poco F1 --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Just for the records I downloaded and installed following external packages to unlock and root my device-->
Also Dont forget to take a backup of your images from TWRP and copy them to your Host machine. It will come very handy. Believe me :)
mkdir aosp-repo cd aosp-repo repo init -u https://android.googlesource.com/platform/manifest -b master git clone git@github.com:pundiramit/android-local-manifests.git .repo/local_manifests -b master repo sync -j$nproc source build/envsetup.sh lunch beryllium-userdebug make -j$nproc
NOTE: To get display working on PocoF1, we need supported Adreno firmware binaries, otherwise PocoF1 will not boot to UI.
Adreno binaries are shipped with non-distributable license,
hence I'm not shipping them in my build setup. You can
extract Adreno a630_* firmware binaries from a working
device build. I extracted mine from
lineage-16.0-20190612-nightly-beryllium-signed.zip ;)
Then copy the binaries to out vendor directory
i.e. out/target/product/beryllium/vendor/firmware,
and run "make -j$nproc" to create vendor.img again.
fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash userdata userdata.img fastboot flash boot boot.img fastboot reboot
mkdir kernel-repo cd kernel-repo repo init -u https://android.googlesource.com/kernel/manifest -b common-android-mainline git clone git@github.com:pundiramit/android-local-manifests.git .repo/local_manifests -b kernel repo sync -j$nproc BUILD_CONFIG=beryllium/build.config.beryllium ./build/build.sh
cd aosp-repo source build/envsetup.sh lunch beryllium-userdebug make TARGET_KERNEL_USE=mainline -j$nproc
Now reflash the images as above and boot with your custom kernel.
NOTE:
By default the above instructions will sync/download beryllium-android-mainline branch to kernel-repo/beryllium directory. If you want to reproduce android12-5.4 or GKI build then checkout common-android12-5.4 repo manifest and beryllium-android-5.4 branch instead.