[android-building] Re: Android Wear 9.0 released
Hi, all, Today, we pushed kernel projects for the following devices: Tag | Project| Branch | Device android-wear-9.0.0_r0.13 | kernel/msm | android-msm-skipjack-3.18-pie-wear-dr | skipjack PWDS.190212.004 android-wear-9.0.0_r0.14 | kernel/msm | android-msm-skipjack-3.18-pie-wear-dr | skipjack LE PWDS.190212.008 -- -- 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.
Re: [android-building] sdk 23 bytecode does not match source
Studio is decompiling the android.jar shipped with the SDK, which only contains the public API of each class with the implementation replaced with an exception. On Mon, Mar 25, 2019 at 7:34 AM Robert Durkacz wrote: > I have built ApiDemos sample code with sdk 23 and get wrong behaviour with > InstallPackage demo. I trace problem into SDK code with debugger. Android > Studio decompiles sdk code for me showing frequent throws of Runtime Error > ("Stub!"). I download source code for SDK level 23 and the source code is a > gross mismatch to what debugger sees. Source code likewise is different to > decompiled code, with none of those exception throws. Can someone tell me > what is going on? > > -- > -- > 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. > -- -- 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] Best way to create custom emulator-only lunch
Hi, I haven't paid much attention to the emulator in the last 5-10 years because we almost always had a matching hardware at hand. Now I am in need of creating a custom lunch that is emulator-only, running on x86. I tried to clone some of the existing x86 lunches and added my modifications, but always ended up with something that did not boot. The kernel did, but it didn't proceed to the system partition. I also did not see a system-qemu.img in my output folder. Funny thing is, if I use the original lunches they boot properly, but I don't want to change those. Is there anything hard-wired in the build system that does not like my cloned target? Best regards Joerg -- -- 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: AOSP libselinux build error for android-q-preview-1
https://android-review.googlesource.com/c/platform/external/selinux/+/897339 在 2019年3月14日星期四 UTC+8下午2:01:56,Jacob Abrams写道: > > Getting the following error when trying to build Q preview aosp generic > aosp_arm: > > > PLATFORM_VERSION_CODENAME=Q > PLATFORM_VERSION=Q > TARGET_PRODUCT=aosp_arm > TARGET_BUILD_VARIANT=eng > TARGET_BUILD_TYPE=release > TARGET_ARCH=arm > TARGET_ARCH_VARIANT=armv7-a-neon > TARGET_CPU_VARIANT=generic > HOST_ARCH=x86_64 > HOST_2ND_ARCH=x86 > HOST_OS=linux > HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-Ubuntu-16.04.6-LTS > HOST_CROSS_OS=windows > HOST_CROSS_ARCH=x86 > HOST_CROSS_2ND_ARCH=x86_64 > HOST_BUILD_TYPE=release > BUILD_ID=PI > OUT_DIR=out > > [100% 134/134] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja > FAILED: out/soong/build.ninja > out/soong/.bootstrap/bin/soong_build -t -l > out/.module_paths/Android.bp.list -b out/soong -n out -d > out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o > out/soong/build.ninja Android.bp > error: frameworks/native/libs/gui/Android.bp:20:1: module "libgui" variant > "android_arm_armv7-a-neon_core_shared_asan": links a library "libselinux" > which is not LL-NDK, VNDK-SP, or explicitly marked as > 'double_loadable:true'. (dependency: libgui -> libbufferhubqueue -> > libpdx_default_transport -> libselinux) > > I went to external/selinux/libselinux/Android.bp and added > "double_loadable: true" to that particular module and the build is > continuing now. Not sure what effect that has, but likely needs a fix? > > Best, > Jacob > -- -- 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: Flashing AOSP master on Pixel failed (Android Q)
I would not expect the AOSP source code base to be fully runnable at this stage. Anything on there is probably going to be previews of bits and pieces of what will eventually become the full release. The only way to get Android Q running on a device at this stage is to install one of the binary preview blobs. I don't expect the full source for Q to drop until late September. https://www.techradar.com/news/android-q -- -- 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.
Re: [android-building] Flashing AOSP master on Pixel failed (Android Q)
Hello dan, I have downloaded, and it works a charm! It is so hard to get a correct vendor.img. Thank you so much! Yuan 在 2019年3月25日星期一 UTC+8上午12:25:08,Dan Willemsen写道: > > Had you downloaded the appropriate device blobs from here: > https://developers.google.com/android/blobs-preview ? > > - Dan > > On Sun, Mar 24, 2019 at 9:21 AM Yuan Zhou > wrote: > >> I am flashing the original AOSP master to my Pixel. I used many methods >> but still failed. >> >> I make AOSP used following command: >> lunch aosp_sailfish-userdebug >> make -j48 (make updatepackage after that) >> >> *Method one:* >> WIPE system/cache/dalvik from twrp. >> fastboot flash boot boot.img >> fastboot flash system system.img >> fastboot flash userdata userdata.img >> fastboot flash vendor vendor.img (from factory image, because there is no >> vendor.img after make -j48 in the out/target/product/saifish directory) >> When it boot, it stuck at android Logo forever. >> >> *Mehthod two:* >> WIPE system/cache/dalvik from twrp. >> fastboot flashall -w (from the out/target/product/sailfish directory I >> made.) >> When it boot, it stuck at android Logo forever. >> >> *Method three:* >> WIPE system/cache/dalvik from twrp. >> fastboot update aosp_sailfish-img-eng.zip (from make >> updatepackage command) >> When it boot, it stuck at android Logo forever. >> >> *Method four:* >> Install the aosp_sailfish-img-eng.zip from twrp, i got the log: >> Installing zip file '/sdcard/aosp_sailfish-img-eng.zip' >> Checking for Digest file... >> Skipping Digest check: no Digest file found >> Invalid zip file format! >> Error installing zip file '/sdcard/aosp_sailfish-img-eng.zip' >> updating partition details... >> done >> >> Anyone can help, PLZ. Thank you 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-...@googlegroups.com >> >> To unsubscribe from this group, send email to >> android-buildi...@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-buildi...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > -- -- 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] What's the correct way to make pm module ?
Hi, I try to build `pm` module in emulator Marshmallow. My platform is Ubuntu 18.04. I choose aosp x86_64, and emulator Android 6 x86_64 (without play) created in AVD. I did success make both framework and then pm module with `LANG=C make framework -j4 VERBOSE=1` and `LANG=C make pm -j4 VERBOSE=1` respectively. I also try a push only simple framework.jar -> reboot seems no crash. Now I try pm: $ adb push out/target/product/generic_x86_64/system/framework/oat/x86/pm.odex /system/framework/oat/x86/ $ adb push out/target/product/generic_x86_64/system/framework/oat/x86_64/pm.odex /system/framework/oat/x86_64/ After reboot emulator, run `pm` command only shows "Abort" and do nothing, how do I debug it ? I think I probably missing some critical steps but I'm new t build Android source. Any help would be appreciate. -- -- 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] sdk 23 bytecode does not match source
I have built ApiDemos sample code with sdk 23 and get wrong behaviour with InstallPackage demo. I trace problem into SDK code with debugger. Android Studio decompiles sdk code for me showing frequent throws of Runtime Error ("Stub!"). I download source code for SDK level 23 and the source code is a gross mismatch to what debugger sees. Source code likewise is different to decompiled code, with none of those exception throws. Can someone tell me what is going on? -- -- 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.