New aosp/drivers on 2019-11-05 has the same result firstly: touch screen no response.
Finally, I find that changing: + <linkfile src="build.config.bluecross_no-cfi" dest="build.config" /> to: + <linkfile src="build.config.bluecross" dest="build.config" /> in default.xml in .repo can fix my issue. So maybe the root cause is my built kernel. Thanks On Wednesday, November 6, 2019 at 7:22:34 AM UTC+8, clark cui wrote: > > Find asop/factory drivers has new ones on 2019-11-05. > I will try them. > > Thanks > > > On Tuesday, November 5, 2019 at 11:00:59 PM UTC+8, clark cui wrote: >> >> Tried change the default.xml in kernel repo to " >> android-msm-crosshatch-4.9-android10". >> Now the kernel and system can boot, but the touch screen has no response. >> >> >> >> <project path="build" name="kernel/build" revision="master"/> >> >> - <project path="private/msm-google" name="kernel/msm" > >> >> - <linkfile src="build.config" dest="build.config" /> >> >> + <project path="private/msm-google" name="kernel/msm" >> revision="android-msm-crosshatch-4.9-android10"> >> >> + <linkfile src="build.config.bluecross_no-cfi" dest="build.config" /> >> >> </project> >> >> - <project path="private/msm-google/techpack/audio" >> name="kernel/msm-extra" /> >> >> - <project path="private/msm-google-modules/wlan/qca-wifi-host-cmn" >> name="kernel/msm-modules/qca-wfi-host-cmn" /> >> >> - <project path="private/msm-google-modules/wlan/qcacld-3.0" >> name="kernel/msm-modules/qcacld" /> >> >> - <project path="private/msm-google-modules/wlan/fw-api" >> name="kernel/msm-modules/wlan-fw-api" /> >> >> + <project path="private/msm-google/techpack/audio" >> name="kernel/msm-extra" revision="android-msm-crosshatch-4.9-android10" /> >> >> + <project path="private/msm-google-modules/wlan/qca-wifi-host-cmn" >> name="kernel/msm-modules/qca-wfi-host-cmn" >> revision="android-msm-crosshatch-4.9-android10" /> >> >> + <project path="private/msm-google-modules/wlan/qcacld-3.0" >> name="kernel/msm-modules/qcacld" >> revision="android-msm-crosshatch-4.9-android10" /> >> >> + <project path="private/msm-google-modules/wlan/fw-api" >> name="kernel/msm-modules/wlan-fw-api" >> revision="android-msm-crosshatch-4.9-android10" /> >> >> <project >> path="prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9" >> name="platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9" >> revision="pie-release" clone-depth="1" /> >> >> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" >> name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" >> revision="pie-release" clone-depth="1" /> >> >> - <project path="prebuilts-master/clang/host/linux-x86" >> name="platform/prebuilts/clang/host/linux-x86" revision="pie-release" >> clone-depth="1" groups="partner" /> >> >> + <project path="prebuilts-master/clang/host/linux-x86" >> name="platform/prebuilts/clang/host/linux-x86" >> revision="4b1f275e6b3826c86f791ae8c4d5ec3563c2fc11" clone-depth="1" >> groups="partner" /> >> >> <project path="prebuilts-master/misc" name="platform/prebuilts/misc" >> revision="pie-release" clone-depth="1" /> >> >> </manifest> >> >> Is there something wrong? >> >> Thanks >> >> On Tuesday, November 5, 2019 at 7:59:14 AM UTC+8, clark cui wrote: >>> >>> Yes, I downloaded the driver blobs and extracted them into aosp dir. >>> After flashing bootloader image in the google's factory android 10 zip >>> file, I can boot the built aosp now. >>> >>> Left problem is: >>> I cannot found the kernel branch for pixel 3 android 10 in kernel repo. >>> Should I need change the default.xml in the .repo for the branch " >>> android-msm-crosshatch-4.9-android10" ? >>> >>> Thanks >>> >>> On Tuesday, November 5, 2019 at 2:24:09 AM UTC+8, Xin Li wrote: >>>> >>>> >>>> >>>> On Fri, Nov 1, 2019 at 1:26 AM clark cui <[email protected]> wrote: >>>> >>>>> Hi Li, >>>>> >>>>> I download aosp src for pixel 3 with: >>>>> >>>>> repo *init* -u https://android.googlesource.com/platform/manifest -b >>>>> android-10.0.0_r4 >>>>> >>>>> >>>>> And I build it for pixel 3 per google's aosp site (m, lunch 3, make >>>>> dist). >>>>> >>>>> Then flash the built images into a pixel 3 with google's factory >>>>> android 10 images with below command: >>>>> >>>>> fastboot *update* dist_output/aosp_blueline-img-eng.ycui.zip >>>>> >>>>> >>>>> After that, the pixel device cannot boot successfully. It will display >>>>> only "android" characters forever. >>>>> >>>> Have you used the binary blobs at >>>> https://developers.google.com/android/drivers for the same build? You >>>> need the corresponding blobs to build working AOSP images. >>>> >>> -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/d4d3c8d0-c42d-4c07-8e74-819f8d85e520%40googlegroups.com.
