| commit | eeb32fbef67dfa2d3a872876844c3004cbe8904d | [log] [tgz] |
|---|---|---|
| author | Bjorn Andersson <bjorn.andersson@linaro.org> | Sun Mar 01 18:02:13 2020 -0800 |
| committer | Amit Pundir <amit.pundir@linaro.org> | Wed Jun 17 16:53:53 2020 +0530 |
| tree | 62befcc551d53ded4b5530b0cb261f67316d9351 | |
| parent | 501bf676a3f976ce72156dfbe5aa9544609a104b [diff] |
qcom: qrtr: ns: Go dormant when exsting name server is found cherry-picked from upstream device/linaro/dragonboard project. With the introduction of the in-kernel nameserver launching the user space qrtr-ns will fail, but typically other services depends on its presence. As such, go dormant instead of failing when noticed that the name service is already present. Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by: Amit Pundir <amit.pundir@linaro.org> Change-Id: I62aa002294e6980bab0b5e1b7282212b8d2c3d57
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 aosp_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/aosp_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
input swipe 20 2000 20 0 input tap 300 600 input tap 200 600 input tap 200 600 # Scanning for devices here. So wait till your BT mouse appears. input tap 400 600 input keyevent 22 input keyevent 22 input keyevent 66
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
Delete all objects in aosp-repo/device/xiaomi/beryllium/prebuilt-kernel/android-mainline/ then copy build artifacts from kernel-repo/out/android-mainline/dist/ to aosp-repo/device/xiaomi/beryllium/prebuilt-kernel/android-mainline/ build AOSP images again.
cd aosp-repo source build/envsetup.sh lunch aosp_beryllium-userdebug make TARGET_KERNEL_USE=mainline -j$nproc
Now flash and boot AOSP images again with your custom kernel.
ToDo -->