[android-building] Re: PPR2.181005.003 Sailfish Vendor Blobs require Marlin QCOM blob to build AOSP
Yes, I downloaded Friday after seeing the bug I logged was fixed. Everything works for Sailfish now. Thanks. On Friday, November 9, 2018 at 11:53:10 AM UTC-8, Bill Yi wrote: > > The blobs should be updated now. Can you please download again and retry? > > bill > > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com 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 android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] PPR2.181005.003 Sailfish Vendor Blobs require Marlin QCOM blob to build AOSP
Similar to the issue I reported a couple of weeks ago regarding the Blueline blobs, which was fixed (thanks), new Vendor blobs for Sailfish were posted for PPR2.181005.003...apparently to fix the Phone Sim not getting detected issue...but I cannot build AOSP R10 for Sailfish using just these Sailfish blobs. Here's the error... dswalen@mtl-linux-build:~/Android9_TS_Merge$ make -j24 PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=9 TARGET_PRODUCT=aosp_sailfish TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_ARCH=arm64 TARGET_ARCH_VARIANT=armv8-a TARGET_CPU_VARIANT=kryo TARGET_2ND_ARCH=arm TARGET_2ND_ARCH_VARIANT=armv8-a TARGET_2ND_CPU_VARIANT=kryo HOST_ARCH=x86_64 HOST_2ND_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-3.13.0-96-generic-x86_64-Ubuntu-14.04.5-LTS HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 HOST_BUILD_TYPE=release BUILD_ID=PPR2.181005.003 OUT_DIR=out [1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja [55/56] glob external/pdfium/third_party/pdfiumbigint.bp [77/77] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja out/build-aosp_sailfish-cleanspec.ninja is missing, regenerating... out/build-aosp_sailfish.ninja is missing, regenerating... [564/934] including system/sepolicy/Android.mk ... system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version [934/934] including tools/tradefederation/core/Android.mk ... [ 99% 722/723] glob frameworks/base/core/res/res/**/* ninja: error: 'vendor/qcom/marlin/proprietary/lib64/vendor.qti.atcmd...@1.0.so', needed by 'out/target/product/sailfish/system/lib64/vendor.qti.atcmd...@1.0.so', missing and no known rule to make it 17:53:04 ninja failed with: exit status 1 This rang recent bells so I immediately downloaded the Marlin Qcom blob for PPR2.181005.003 and stuck it in the Vendor folder in the AOSP repo. Now the Sailfish build is off and running. So it seems these Sailfish blobs are no good. -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com 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 android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Re: Clean Android 9 AOSP builds not finding Phone Sim on Pixel
Oh nice research there. I was giving up hope on finding an answer for this. On Saturday, October 27, 2018 at 9:28:03 AM UTC-7, Brian Moore wrote: > > Update: > Take a look at the project below. It's essentially a set of scripts that > will download an android image and extract a working /vendor/google_devices > tree to include with your AOSP build. Using this I was able to easily build > a working AOSP 9.0 image that found the SIM card. Apparently the vendor > tree provided by Google is not complete. > > https://github.com/anestisb/android-prepare-vendor -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com 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 android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Flashing AOSP on Pixel3/Blueline
I'm not entirely sure this is the right forum for this question but I don't see any other forum that is a better fit either... So previously with Pixel/Sailfish when I would build and flash AOSP it was straightforward. I'd do the build and then flash four files copied from the out/target/product/sailfish directory... fastboot flash boot boot.img fastboot flash system system.img fastboot flash userdata userdata.img fastboot flash vendor vendor.img This procedure would work on Pixel...as it had worked for my Nexus devices previously as well. But with Pixel 3 the steps outlined above do not work. After flashing the aforementioned files, I do fastboot reboot and a splash screen appears for a second like the boot is going to go through but then I'm taken back to the bootloader. I can still put the Factory back on but whenever I try to put AOSP on the way I'd been doing it, it doesn't work. I don't think this is a build issue because I'm doing an unmodified AOSP build with no code changes so the build should be good. I went looking for instructions to see if there's been any change in flashing procedure or a listing of what needs to be flashed but the only document I found was located here... https://source.android.com/setup/build/running ...and it's not current (doesn't mention either the Pixel 2 or 3 line of devices when doing builds) I did notice that it recommended using fastboot flashall but it wasn't clear on what was to be flashed. Am I to just grab every .img file out of my out/target/product/blueline directory and run flashall? Or some subset of those files? If anyone can clue me in on the best method for flashing AOSP on the Pixel 3, given that my old method is apparently no longer operative, I would be very grateful. -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com 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 android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Crosshatch qualcomm binaries required for Blueline builds?
I am attempting my first Blueline build. Just a straight build of r11 for Blueline (no modifications). I got the r11 repo. I got the r11 binaries for Blueline. I did lunch aosp_blueline-userdebug after calling source build/envsetup.sh. But when I did make the build threw an error in the first three minutes. I've never run into this before when building for sailfish on 9 or 8 or 8.1...getting an error for doing a straight build. Here's the error... ninja: error: 'vendor/qcom/crosshatch/proprietary/lib64/libOpenCL_system.so', needed by 'out/target/product/blueline/system/lib64/libOpenCL_system.so', missing and no known rule to make it 15:07:45 ninja failed with: exit status 1 failed to build some targets (03:43 (mm:ss)) Why is a blueline build asking for crosshatch Qualcomm binaries? I never had to include marlin Qualcomm binaries when building for sailfish and I never had to include muskie Qualcomm binaries when building for walleye. And yet, to get around this error, I had to download and add the crosshatch Qualcomm binaries to my vendor folder so that the build for sailfish could continue. This little detail isn't spelled out anywhere as far as I can tell. Either this is now the new normal for AOSP builds for blueline, in which case this really should be documented somewhere, or something in the build scripts is making an erroneous crosshatch binary request, in which case this is a build bug in the AOSP branch for r11. I have no idea which is the case. Can someone please clear this up? -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com 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 android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Clean Android 9 AOSP builds not finding Phone Sim on Pixel
I'm assuming this isn't actually a bug but something I need to address with the build process... I've been doing some tests with clean unmodified AOSP builds on the Pixel. I had been working with Android 8 and 8.1 and my build process was as follows: 1. Clone the AOSP branch I want to build. 2. Download the corresponding Vendor and drivers files for that branch and copy them to the folder containing that branch. 3. source build/envsetup.sh 4. lunch (select the Sailfish option) 5. make I would then flash the binaries to the Pixel. The Pixel, which was not an OEM locked Pixel, had a phone sim in it and it worked. But when I switched to Android 9, the sim was no longer being detected. I first noticed this with the 9.0.0_r2 branch. Yesterday I checked out and build the r10 branch and it's still an issue. AOSP isn't finding the Sim on the Pixel with Android 9. Nothing changed in the build process. I'm following the same steps I did with 8.0 and 8.1 but now with 9.0 instead of a working Sim I get no Sim. Can anyone offer any guidance on what I can do from the build side to address this. I hope this isn't actually a bug but something I'm failing to address...(though I can't see why things would need to change between 8.0/8.1 and 9.0). Thanks in advance... -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com 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 android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
