[android-building] Re: Choosing a target device

['Glenn Kasten' via Android Building]

Please see https://source.android.com/setup/build/building#choose-a-target
and https://source.android.com/setup/build/running#selecting-device-build

On Thursday, October 8, 2020 at 10:34:11 AM UTC-7, Mahnoor Malik wrote:
>
> Dear all.
>
>
> I am building android for the first time. I donot have to flash the os on 
> a hardware device and have to work on emulator only ( university project ). 
> I have downloaded the master branch of android repo. Let me know which 
> target should I select for lunch command. Here many devices are listed for 
> android 11. I need suggestions
>
> https://source.android.com/setup/start/build-numbers
>
> Regards,
> Mahnoor
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/2df31138-e944-4664-91e3-709765a0e31fo%40googlegroups.com.

[android-building] Re: Android 11 Released

['Glenn Kasten' via Android Building]

Miguel, thank you for mentioning these problems. Would you mind please 
filing bug report(s) here 

and / or uploading CLs 
 that fix, 
since it sounds like you do have fixes?
The reason is that is difficult to track bugs and CLs here in the 
discussion group,
and so we generally prefer them in the bug tracking system and Gerrit for 
CLs.
Thanks so much!
Glenn

On Thursday, September 17, 2020 at 2:10:52 PM UTC-7, Miguel Martinez wrote:
>
> Few bugs in the android-msm-sunfish-4.14-android11 branch 
>
> The last merge in this repo:
> kernel/msm/data-kernel
> for branch: 
> android-msm-sunfish-4.14-android11
>
> Contains a mismerge in the last merge, commit 
> d88d11796e03f56df05d25333e11767b094b2cae
> Line 2640 of drivers/rmnet/shs/rmnet_shs_wq.c
> +<<< HEAD +=== 
> + jiffies = msecs_to_jiffies(rmnet_shs_wq_interval_ms); 
> + 
> +>>> LA.UM.9.1.R1.10.00.00.604.038  
>
> The kernel/msm-modules/fts_touch repo
> this version of the driver is older than the R-Beta3 branch we had in the 
> beta release.
> Touch does not work with this android11 branch version of the driver. If I 
> revert this repo to the rbeta3 branch version, then touch works fine again.
>
> Final issue is the qcacld driver needs hardcoded to init by default or it 
> does not function, will not turn on. But that's not a big deal and an easy 
> fix.
> On Tuesday, September 8, 2020 at 6:23:49 PM UTC-5 Bill Yi wrote:
>
>>
>> We pushed reference Android Mainline source with the following tags:
>> - android-mainline-11.0.0_r1
>>
>> bill
>>
>>
>> On Tuesday, September 8, 2020 at 5:59:50 PM UTC-4 Bill Yi wrote:
>>
>>> Hi all,
>>>
>>> Android 11 source code is now available. The following builds, tags, and 
>>> devices are supported:
>>>  - RP1A.200720.009, android-11.0.0_r1, Pixel 2, Pixel 2 XL, Pixel 3, 
>>> Pixel 3 XL, Pixel 4, Pixel 4 XL, Pixel 3a XL, Pixel 3
>>>  - RP1A.200720.010, android-11.0.0_r2, Pixel 4a
>>>  - RP1A.200720.011, android-11.0.0_r3, Pixel 4a
>>>
>>> The corresponding factory images, ota images, and proprietary binaries 
>>> are available at
>>>  https://developers.google.com/android/images
>>>  https://developers.google.com/android/ota
>>>  https://developers.google.com/android/drivers
>>>
>>> We pushed a reference "android11-dev" branch.
>>>
>>> We have pushed the corresponding kernel projects for the following 
>>> devices:
>>>
>>> Tag  | Project| Branch  
>>> | Device
>>> android-11.0.0_r0.1 | kernel/msm  | 
>>> android-msm-wahoo-4.4-android11 | Pixel 2 XL, Pixel 2
>>> android-11.0.0_r0.1 | kernel/arm64| 
>>> android-amber-intel-linux-4.7-android11 | Pixel 2 XL, Pixel 2
>>> android-11.0.0_r0.2 | kernel/msm  | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-extra| 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-modules/qca-wfi-host-cmn | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-modules/qcacld   | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-modules/wlan-fw-api  | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.3 | kernel/msm  | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-extra| 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-modules/qca-wfi-host-cmn | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-modules/qcacld   | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-modules/wlan-fw-api  | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.4 | kernel/msm  | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-extra| 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/data-kernel  | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/fts_touch| 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/qca-wfi-host-cmn | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/qcacld   | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm

Re: [android-building] AOSP Resources

['Glenn Kasten' via Android Building]

The classic book 
is 
https://www.amazon.com/Embedded-Android-Porting-Extending-Customizing/dp/1449308295
but it's old and may only be available used.

On Tuesday, September 15, 2020 at 8:16:21 AM UTC-7, Igor Kukushkin wrote:
>
> Duh try narrowing the question down, way too much possibilities there.
>
> Try building the basic targets first (Cuttlefish, emulator image, generic 
> GSI, some Pixel/Nexus targets, Auto if curious). Then start looking into 
> how makefiles (.mk)/Bazel is working. Then try the same thing with any 
> custom fork, and proceed to experimenting (adding some HAL changes, custom 
> system server services), or look into hooking (frida/xposed/magisk) - that 
> alone is a great experience.
> Do try to understand the reasoning behind using Gerrit, that's kinda 
> important - then find a couple projects (forks) using it and see what 
> changes are common these days.
>
> On Mon, Sep 14, 2020 at 6:37 PM Heman Parbhakar  
> wrote:
>
>> Hello Everyone,
>>
>> Can anyone tell me good resources to learn Android ROM Development from 
>> scratch. 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/android-building/6e3aa5df-2457-48e9-81d0-0a7e1fd1fcdbn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/89371d54-709a-4aef-ae4b-89186b47f563o%40googlegroups.com.

[android-building] Re: AOSP Resources

['Glenn Kasten' via Android Building]

I'm not quite sure what you mean by "from scratch", but I recommend 
starting here:
https://source.android.com/
in particular tab "set up" and then the sub-tabs of "set up".

In general it is usually easier to first build for an AOSP-supported target 
device
before attempting to port to another device. Supported devices are listed 
here:
https://source.android.com/setup/build/running#selecting-device-build

On Monday, September 14, 2020 at 9:37:46 AM UTC-7, Heman Parbhakar wrote:
>
> Hello Everyone,
>
> Can anyone tell me good resources to learn Android ROM Development from 
> scratch. 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/33cbcb6d-6d81-4af5-9343-6b9b0c3486cdo%40googlegroups.com.

[android-building] Re: Building Android Automotive for Raspberry Pi [closed]

['Glenn Kasten' via Android Building]

See list of supported build targets here:
https://source.android.com/setup/build/running#selecting-device-build

On Thursday, September 10, 2020 at 8:13:50 AM UTC-7, Salvatore Amodio wrote:
>
> I would like to know how building Android Automotive OS for Raspberry Pi? 
> I downloaded the source through Repo Launcher from
>
> https://source.android.com/setup/build/downloading
>
> Then I initialized the environment:
>
> -- source build/envsetup.sh -- build/envsetup.sh
>
> I chose the target:
>
> -- lunch aosp_car_arm64-userdebug
>
> and I launched the last command:
>
> -- time make -j$(nproc)
>
> The image has been created is only for the emulator or it can be flashed 
> on the Rpi 4?
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/239b7efe-73ed-4b8f-9d6b-d86d3426884eo%40googlegroups.com.

[android-building] Re: Run emulator on Android 11 (R)

['Glenn Kasten' via Android Building]

Preview source code is incomplete and for reference only, and is not 
intended to be buildable or fully executable.

On Friday, August 28, 2020 at 11:49:48 AM UTC-7, Nguyễn Trung Thành wrote:
>
> Dear all,
>
> I am trying to get source code from master from to build. With few 
> adjustment I can build this source code. However, emulator isn't started as 
> well. I check logcat and there are some errors. 
>
> Here is error:
> 08-27 08:04:46.366   718   718 D SystemServerTiming: 
> MakePackageManagerServiceReady took to complete: 205ms
> 08-27 08:04:46.366   718   718 E Zygote  : System zygote died with 
> exception
> 08-27 08:04:46.366   718   718 E Zygote  : 
> java.lang.IllegalStateException: Signature|privileged permissions not in 
> privapp-permissions whitelist: {com.android.car.developeroptions: 
> android.permission.READ_PRIVILEGED_PHONE_STATE}
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2983)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:122)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:3044)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21192)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.SystemServer.startOtherServices(SystemServer.java:2035)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.SystemServer.run(SystemServer.java:536)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.SystemServer.main(SystemServer.java:362)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> java.lang.reflect.Method.invoke(Native Method)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:906)
> 08-27 08:04:46.366   718   718 D AndroidRuntime: Shutting down VM
> 08-27 08:04:46.366   718   718 E AndroidRuntime: *** FATAL EXCEPTION IN 
> SYSTEM PROCESS: main
> 08-27 08:04:46.366   718   718 E AndroidRuntime: 
> java.lang.IllegalStateException: Signature|privileged permissions not in 
> privapp-permissions whitelist: {com.android.car.developeroptions: 
> android.permission.READ_PRIVILEGED_PHONE_STATE}
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2983)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:122)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:3044)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21192)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.SystemServer.startOtherServices(SystemServer.java:2035)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.SystemServer.run(SystemServer.java:536)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.SystemServer.main(SystemServer.java:362)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> java.lang.reflect.Method.invoke(Native Method)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:906)
> 08-27 08:04:46.367   718   718 I DropBoxManagerService: add 
> tag=system_server_crash isTagEnabled=true flags=0x2
>
> I see something relate to READ_PRIVILEGED_PHONE_STATE  but I don't know 
> how to fix it.
> Could you help me to check the problem?
>
> Best regards,
> Thanh
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/6fefca37-85f8-4020-

[android-building] Re: Help! Disk space getting nearly full because of Android's source files

['Glenn Kasten' via Android Building]

I'm not sure what's causing the tmp_pack_ problem.
But you might need to start over with a completely new download, and on a 
machine with a lot more disk space available.
That is:
 - make a backup of any of your important files
 - delete your current download area, including hidden directories and 
hidden files within the download area
 - check your disk space and make sure you have *lots* available, and 
consider adding even more space
 - start a new download

On Wednesday, August 26, 2020 at 6:30:01 AM UTC-7, `mCT wrote:
>
> @Glenn Kasten
>
> Hi,
> I see that one of my two messages, which I posted yesterday, hasn't 
> appeared here yet, while the other has appeared. I am talking about the 
> message, which I posted in response to your reply of 22 Aug to me, in which 
> you are asking me to see an article based on disk space requirements.
> So, I would ask you to kindly check my that message also, as it is quite 
> important in this conversation. It would be very kind of you to share the 
> update regarding that message.
>
> thanks,
> Waiting for your help `n reply.
>
> On Sunday, August 23, 2020 at 8:44:07 PM UTC+5:30 `mCT wrote:
>
>> @ Glenn Kasten
>>
>> In addition to my earlier message, I forgot to say that, I have also 
>> written my problem in one message outside of this conversation. It is 
>> here. 
>> <https://groups.google.com/g/android-building/c/zSzC3WtgPYI/m/rZjoSH_4BgAJ>
>>
>> On Saturday, August 22, 2020 at 11:47:11 PM UTC+5:30 Glenn Kasten wrote:
>>
>>> Please see this article on disk requirements:
>>> https://source.android.com/setup/build/requirements
>>>
>>> Are you finding that it actually needs more free disk space than the 
>>> amount listed?
>>> If so please reply and we'll update the documentation to the correct 
>>> amount.
>>>
>>> On the other hand, if the amount listed is correct and your machine just 
>>> doesn't have that much free space,
>>> really the only solution is to create more free space, for example by 
>>> adding another larger drive.
>>>
>>> On Saturday, August 22, 2020 at 11:11:26 AM UTC-7, `mCT wrote:
>>>>
>>>>
>>>> Hi everyone,
>>>> I would just like to ask for help. While downloading Android's source, 
>>>> my disk's space is getting nearly full because of these 'tmp_pack_...' 
>>>> files which are of many GBs, and I am not able to find a solution.
>>>> It would be very kind of anyone who can guide me what to do of these 
>>>> 'tmp_pack_...' files, as deleting them will not solve my problem 
>>>> completely, as when I have to download Android's source again, these files 
>>>> will start getting accumulated again, but as I have to pause downloading 
>>>> the source because of Internet data getting finished, so I also wanted to 
>>>> know if it's possible to pause downloading the source, then how to do it?
>>>
>>>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/60c13dcf-6813-445f-8089-58a9f9becca7o%40googlegroups.com.

[android-building] Re: Help! Disk space getting nearly full because of Android's source files

['Glenn Kasten' via Android Building]

Please see this article on disk requirements:
https://source.android.com/setup/build/requirements

Are you finding that it actually needs more free disk space than the amount 
listed?
If so please reply and we'll update the documentation to the correct amount.

On the other hand, if the amount listed is correct and your machine just 
doesn't have that much free space,
really the only solution is to create more free space, for example by 
adding another larger drive.

On Saturday, August 22, 2020 at 11:11:26 AM UTC-7, `mCT wrote:
>
>
> Hi everyone,
> I would just like to ask for help. While downloading Android's source, my 
> disk's space is getting nearly full because of these 'tmp_pack_...' files 
> which are of many GBs, and I am not able to find a solution.
> It would be very kind of anyone who can guide me what to do of these 
> 'tmp_pack_...' files, as deleting them will not solve my problem 
> completely, as when I have to download Android's source again, these files 
> will start getting accumulated again, but as I have to pause downloading 
> the source because of Internet data getting finished, so I also wanted to 
> know if it's possible to pause downloading the source, then how to do it?

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/c30771f6-b277-4f98-8c1c-92aa7e325305o%40googlegroups.com.

[android-building] Re: Build android-r-preview-4 on macOS 10.15 failed. Did anyone succeed?

['Glenn Kasten' via Android Building]

Preview source code is incomplete and for reference only, and is not 
intended to be buildable.

On Wednesday, August 5, 2020 at 7:22:56 PM UTC-7, Lee Prime wrote:
>
> After the repo sync was done , I start do the following steps. 
>
> source build/envsetup.sh  # this works fine. 
>
> lunch # there was several problems. Here they are.
>
> ===
> dyld: Library not loaded: @rpath/libcrypto-host.dylib
>   Referenced from: 
> /Volumes/AOSP/android-r-preview-4/prebuilts/build-tools/path/darwin-x86/date
>   Reason: image not found
> dyld: Library not loaded: @rpath/libcrypto-host.dylib
>   Referenced from: 
> /Volumes/AOSP/android-r-preview-4/prebuilts/build-tools/path/darwin-x86/date
>   Reason: image not found
> dyld: Library not loaded: @rpath/libcrypto-host.dylib
>   Referenced from: 
> /Volumes/AOSP/android-r-preview-4/prebuilts/build-tools/path/darwin-x86/date
>   Reason: image not found
> /bin/bash: line 1: 68924 Doneecho a
>  68925 Abort trap: 6   | sed -E -e 's/a/b/' 2> /dev/null
> /bin/bash: line 1: 68927 Doneecho c
>  68928 Abort trap: 6   | sed -r -e 's/c/d/' 2> /dev/null
> ==
>
> I fiexed the dyld problem by using install_name_tool. 
> But there still 2 problem to be solved. 
>
> =
> /bin/bash: line 1: 68924 Doneecho a
>  68925 Abort trap: 6   | sed -E -e 's/a/b/' 2> /dev/null
> /bin/bash: line 1: 68927 Doneecho c
>  68928 Abort trap: 6   | sed -r -e 's/c/d/' 2> /dev/null
> -===
>
> How should I fix it?
>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/66bd3038-b53c-47ff-9c29-80453501cd41o%40googlegroups.com.

[android-building] Re: increase the memory used for building

['Glenn Kasten' via Android Building]

> Does the the build system take the full advantage of the available memory 
in the building machine?
Yes, by default.

> Lets say I have 64Gb RAM does it use all the memory?
Yes, if that much is needed, except for memory used by the host OS/kernel 
and other processes running on same machine.

> If there is a limit how I can change it? is there an option to increase 
it?
There is no overall limit or option for the build, but specific build tools 
may have limits and options.
Generally it is not necessary to configure these.

The host OS may have facilities for limits ...
for example Linux has cgroups, and bash has the ulimit command.
But you will usually not need to use these.


On Tuesday, July 21, 2020 at 7:32:36 AM UTC-7, Kbc K wrote:
>
> Hi all,
>
> I have a question about AOSP build system memory usage.
>
> Does the the build system take the full advantage of the available memory 
> in the building machine? 
> Lets say I have 64Gb RAM does it use all the memory?
>
> If there is a limit how I can change it? is there an option to increase 
> it? 
>
> BR
> K
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/0b28bbee-0858-469c-8430-029cd55a28bao%40googlegroups.com.

[android-building] Re: com.google.doclava.Doclava method start exception

['Glenn Kasten' via Android Building]

Please consider filing a bug report here, that will be the best way to make 
sure the issue is tracked:
https://source.android.com/setup/contribute/report-bugs

On Monday, July 20, 2020 at 2:13:10 PM UTC-7, Dean Wheatley wrote:
>
> AOSP version: master
>
> Stack:
>
> javadoc: error - In doclet class com.google.doclava.Doclava,  method start 
> has thrown an exception java.lang.reflect.InvocationTargetException
> java.lang.NullPointerException
> at 
> jdk.javadoc/com.sun.tools.javadoc.main.ExecutableMemberDocImpl.position(ExecutableMemberDocImpl.java:285)
> at 
> com.google.doclava.Converter.convertParameters(Converter.java:291)
> at com.google.doclava.Converter.access$700(Converter.java:48)
> at com.google.doclava.Converter$2.make(Converter.java:467)
> at com.google.doclava.Converter$Cache.obtain(Converter.java:736)
> at com.google.doclava.Converter.obtainMethod(Converter.java:447)
> at com.google.doclava.Converter.access$500(Converter.java:48)
> at com.google.doclava.Converter$8.make(Converter.java:717)
> at com.google.doclava.Converter$Cache.obtain(Converter.java:736)
> at 
> com.google.doclava.Converter.obtainAnnotationInstance(Converter.java:705)
> at 
> com.google.doclava.Converter.convertAnnotationInstances(Converter.java:698)
> at com.google.doclava.Converter.access$800(Converter.java:48)
> at com.google.doclava.Converter$2.make(Converter.java:498)
> at com.google.doclava.Converter$Cache.obtain(Converter.java:736)
> at com.google.doclava.Converter.obtainMethod(Converter.java:447)
> at com.google.doclava.Converter.convertMethods(Converter.java:424)
> at com.google.doclava.Converter.initClass(Converter.java:138)
> at com.google.doclava.Converter.makeInfo(Converter.java:71)
> at com.google.doclava.Doclava.start(Doclava.java:426)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at 
> jdk.javadoc/com.sun.tools.javadoc.main.DocletInvoker.invoke(DocletInvoker.java:333)
> at 
> jdk.javadoc/com.sun.tools.javadoc.main.DocletInvoker.start(DocletInvoker.java:212)
> at 
> jdk.javadoc/com.sun.tools.javadoc.main.Start.parseAndExecute(Start.java:446)
> at 
> jdk.javadoc/com.sun.tools.javadoc.main.Start.begin(Start.java:238)
> at 
> jdk.javadoc/com.sun.tools.javadoc.main.Start.begin(Start.java:224)
> at jdk.javadoc/com.sun.tools.javadoc.Main.execute(Main.java:174)
> at 
> jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:419)
> at 
> jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:344)
> at jdk.javadoc/jdk.javadoc.internal.tool.Main.execute(Main.java:63)
> at jdk.javadoc/jdk.javadoc.internal.tool.Main.main(Main.java:52)
> 1 error
>
> Steps to reproduce:
>
> $ make 
>
> droiddoc {
> name: "com.vendor.component-api-docs",
> custom_template: vendor_droiddoc_template,
> srcs: [
> ":vendor_component_source_files",
> ],
> libs: [vendor_module],
> args: "-stubpackages com.vendor.component -showAnnotation 
> com.vendor.component.SuppressAutoDoc",
> installable: false,
> }
>
>
> This error did not occur in Android 10.
>
> I have looked into the differences in the Android 10 and Android master 
> commands:
> * Android 10 uses JDK9 and master uses JDK11. Changing JDK11 to JDK9 does 
> not fix problem.
> * I reverted external/doclava to the Android 10 SHA but this did not fix 
> the issue either.
>
> There's been a lot of changes to build/soong/java/droiddoc.go between Q 
> and master.
>
> Thanks,
>
>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/97c13bcd-3c9b-42ec-a9f3-ec513720e291o%40googlegroups.com.

[android-building] Re: acloud fails on Ubuntu 20.04

['Glenn Kasten' via Android Building]

Please file a bug here:

https://source.android.com/setup/contribute/report-bugs

On Thursday, June 18, 2020 at 7:32:05 AM UTC-7, Ismael Vidal wrote:
>
> I have the same problem on Ubuntu 20.04. :(
>
> On Tuesday, June 2, 2020 at 12:35:10 PM UTC-4, Dean Wheatley wrote:
>>
>> Irrespective of running python version (2.7.18rc1 or 3.8.2) on Ubuntu 
>> 20.04, acloud fails as below:
>>
>> $ acloud setup --host
>>
>> Welcome to
>> 
>>___  ___     __  _ 
>>   / _ |/ ___/ /  / __ \/ / / / _ \ 
>>  / __ / /__/ /__/ /_/ / /_/ / // /  
>> /_/ |_\___//\/\// 
>>   
>>
>> Traceback (most recent call last):
>>   File "/tmp/Soong.python_ym5s7lig/acloud/public/acloud_main.py", line 
>> 440, in 
>> EXIT_CODE, EXCEPTION_STACKTRACE = main(sys.argv[1:])
>>   File "/tmp/Soong.python_ym5s7lig/acloud/public/acloud_main.py", line 
>> 419, in main
>> setup.Run(args)
>>   File "/tmp/Soong.python_ym5s7lig/acloud/setup/setup.py", line 73, in Run
>> subtask.Run(force_setup=args.force)
>>   File "/tmp/Soong.python_ym5s7lig/acloud/setup/base_task_runner.py", 
>> line 97, in Run
>> if self.ShouldRun() or force_setup:
>>   File "/tmp/Soong.python_ym5s7lig/acloud/setup/host_setup_runner.py", 
>> line 67, in ShouldRun
>> if not utils.IsSupportedPlatform():
>>   File "/tmp/Soong.python_ym5s7lig/acloud/internal/lib/utils.py", line 
>> 1218, in IsSupportedPlatform
>> dist = platform.linux_distribution()[0]
>>
>>
>>
>> Why does acloud seemingly always use the latest python version on the 
>> system (3.8.2 in my case) rather than the one set to local python? 
>> (platform.linux_distribution API has been removed in Python 3.8)
>>
>> Building and running acloud-dev worked around this issue, but I needed to 
>> ensure that python2 was the active version on my system.
>>
>>
>>
>>
>>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/8d35a288-8be5-4623-8032-637b61851601o%40googlegroups.com.

[android-building] Re: android build take eons

['Glenn Kasten' via Android Building]

The listed build hardware requirements 
 
are the bare minimum.
The more RAM and CPUs you have, the better.
And be sure to use make -k to take advantage of all your CPUs.

On Monday, May 4, 2020 at 12:19:43 PM UTC-7, Imx6dev Kit wrote:
>
> I got my AOSP build to work but it took maybe 8 hours ... i cannot imagine 
> how anyone can develop anything this way .. if i want to include a new 
> library, or write a new driver, or change something minimal, and recompile, 
> isn't there a way to do it quicker?  What is the recommended way to build 
> after making a minor change?
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/5192f89b-c40e-4bba-969c-ec6f012d8324%40googlegroups.com.

[android-building] Re: Finding corresponding pixel kernel in msm repo for a given released android version

['Glenn Kasten' via Android Building]

I don't know the answer to your specific question, but here are some 
general resources that might help:
https://source.android.com/setup/build/building-kernels
https://source.android.com/devices/architecture/kernel/android-common

On Monday, May 4, 2020 at 8:48:53 AM UTC-7, Zheng Zhang wrote:
>
> Hi:
> I'm a student trying to compile Android kernel with kcov. How could I 
> find pixel kernel  (in kernel/msm repo) corresponding to a specific Android 
> version? 
> For example, how could I find a kernel snapshot in the kernel/msm 
> repository that corresponds to QQ2A.200405.005? It seems that tag in 
> Android(android-10.0.0_r33) is different from the tag in MSM repository 
> (android-10.0.0_r0.33, for example). Could you give me any suggestions?
> Thanks very much!
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/e294a2d2-06b6-4e0d-be8b-212bcf8c90eb%40googlegroups.com.

[android-building] Re: Android 10 Released

['Glenn Kasten' via Android Building]

There is another thread on a similar topic.
Please see my reply there:

   Finding corresponding pixel kernel in msm repo for a given released 
android version
  https://groups.google.com/forum/#!topic/android-building/ziIidQ4UcLw


On Monday, May 4, 2020 at 8:48:45 AM UTC-7, Zheng Zhang wrote:
>
> Hi, Dr Xin Li:
>I'm a student trying to compile Android kernel with kcov. How could 
> I find corresponding pixel kernel  (in kernel/msm repo) for a specific 
> Android version? 
>For example, how could I find a kernel snapshot in the kernel/msm 
> repository that corresponds to QQ2A.200405.005? It seems that tag in 
> Android(android-10.0.0_r33) is different from the tag in MSM repository 
> (android-10.0.0_r0.33, for example). Could you give me any suggestions?
>Thanks very much!
>   
>  zheng zhang
>
> On Monday, April 6, 2020 at 7:36:52 PM UTC-7, Xin Li wrote:
>>
>> Hi all,
>>
>> Android 10 source code is now available. The following builds, tags, and 
>> devices are supported:
>>  - QQ2A.200405.005, android-10.0.0_r33, Pixel 2, Pixel 2 XL, Pixel 3, 
>> Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL
>>
>> The corresponding factory images, ota images, and proprietary binaries 
>> are available at
>>
>>   https://developers.google.com/android/images
>>   https://developers.google.com/android/ota
>>   https://developers.google.com/android/drivers
>>
>> We also pushed the corresponding kernel projects for the following 
>> devices:
>>
>> Tag  | Project | Branch  
>> | Device
>> android-10.0.0_r0.50 | kernel/msm  | 
>> android-msm-wahoo-4.4-android10 | Pixel 2 XL, Pixel 2
>> android-10.0.0_r0.51 | kernel/arm64| 
>> android-amber-intel-linux-4.7-android10 | Pixel 2 XL, Pixel 2
>> android-10.0.0_r0.52 | kernel/msm  | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-extra| 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-modules/qcacld   | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.53 | kernel/arm64| 
>> android-blue-intel-linux-4.7-android10  | Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.54 | kernel/msm  | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-extra| 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-modules/qcacld   | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.55 | kernel/arm64| 
>> android-blue-intel-linux-4.7-android10  | Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.56 | kernel/msm  | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-extra| 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/data-kernel  | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/fts_touch| 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/qcacld   | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.57 | kernel/arm64| 
>> android-blue-intel-linux-4.7-android10  | Pixel 4 XL, Pixel 4
>>
>

-- 
-- 
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 me

[android-building] Re: Build processes uses 100% CPU and >4GB RAM all time, crashes frequently during build

['Glenn Kasten' via Android Building]

> Not sure if my hardware meets the requeriments for AOSP builds.
see 
https://source.android.com/setup/build/requirements#hardware-requirements
for minimums but it is better to have much more

On Saturday, March 14, 2020 at 11:58:40 AM UTC-7, Eliane Fonseca wrote:
>
> During the builds, using somewhat underpowered hardware (1 GHz CPU, 8GB 
> RAM, no SSD), the build process uses 100% CPU and a large RAM amount, 
> different AOSP versions tried (7.1, 8.0, 9, 10) , and my CPU stays at 1.00 
> GHz rather than auto overclocking (it can, up to 1.40 GHz). Long running 
> builds frequently crashes as well but simply running make again allows the 
> build to proceed. Not sure if my hardware meets the requeriments for AOSP 
> builds.
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/b8e12230-5df6-4beb-8354-0ffe8fdac6c4%40googlegroups.com.

[android-building] Re: Error during building AOSP for Moto G5s Plus

['Glenn Kasten' via Android Building]

I just noticed that this discussion thread is about a build target that is 
unsupported by AOSP,
therefore this thread is off-topic for the android-building group.  As long 
as only upstream AOSP is involved,
then you can post about unsupported build targets at android-porting group.
However, if other components beyond AOSP are involved, then it would also 
be off-topic for android-porting.
Please see posting guidelines at top of:
https://groups.google.com/forum/?oldui=1#!forum/android-building
https://groups.google.com/forum/?oldui=1#!forum/android-porting

On Thursday, March 12, 2020 at 7:55:51 PM UTC-7, Andrew Wheeler wrote:
>
> Are you adding components from LineageOS?  Maybe you need to port this 
> 
> ?
>
>
> On Thursday, March 12, 2020 at 12:21:46 PM UTC-5, Rajesh Kumbhakar wrote:
>>
>> FAILED: ninja: 
>> 'out/target/product/sanders/obj/HEADER_LIBRARIES/generated_kernel_headers_intermediates/export_includes',
>>  
>> needed by 
>> 'out/target/product/sanders/obj/STATIC_LIBRARIES/libwifi-hal-qcom_intermediates/import_includes',
>>  
>> missing and no known rule to make it
>>
>> can anyone help me with this please...?
>>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/b4d19fab-5ea1-4aff-996c-d79053a50f73%40googlegroups.com.

[android-building] Re: Compile AOSP on Intel Platforms

['Glenn Kasten' via Android Building]

> for an old Tablet with Intel Atom Z2520

Sorry, this post got past moderation and should have been redirected to 
android-porting.
The device mentioned is not an AOSP-supported build target.
See the list of AOSP-supported build targets 
.

Please post follow-ups to android-porting, not here
Thank you

On Thursday, January 30, 2020 at 7:06:27 AM UTC-8, Agostinho Carvalho wrote:
>
> I'm trying to compile AOSP 10 for an old Tablet with Intel Atom Z2520 
> (32-bit architecture).
>
> Question 1: What lunch option should I use, to compile for that Tablet + 
> SoC combination?
>
> Current offered options are:
>  1. aosp_arm-eng
>  2. aosp_arm64-eng
>  3. aosp_blueline-userdebug
>  4. aosp_bonito-userdebug
>  5. aosp_car_arm-userdebug
>  6. aosp_car_arm64-userdebug
>  7. aosp_car_x86-userdebug
>  8. aosp_car_x86_64-userdebug
>  9. aosp_cf_arm64_phone-userdebug
>  10. aosp_cf_x86_64_phone-userdebug
>  11. aosp_cf_x86_auto-userdebug
>  12. aosp_cf_x86_phone-userdebug
>  13. aosp_cf_x86_tv-userdebug
>  14. aosp_coral-userdebug
>  15. aosp_crosshatch-userdebug
>  16. aosp_flame-userdebug
>  17. aosp_marlin-userdebug
>  18. aosp_sailfish-userdebug
>  19. aosp_sargo-userdebug
>  20. aosp_taimen-userdebug
>  21. aosp_walleye-userdebug
>  22. aosp_walleye_test-userdebug
>  23. aosp_x86-eng
>  24. aosp_x86_64-eng
>  25. beagle_x15-userdebug
>  26. fuchsia_arm64-eng
>  27. fuchsia_x86_64-eng
>  28. hikey-userdebug
>  29. hikey64_only-userdebug
>  30. hikey960-userdebug
>  31. hikey960_tv-userdebug
>  32. hikey_tv-userdebug
>  33. m_e_arm-userdebug
>  34. mini_emulator_arm64-userdebug
>  35. mini_emulator_x86-userdebug
>  36. mini_emulator_x86_64-userdebug
>  37. poplar-eng
>  38. poplar-user
>  39. poplar-userdebug
>  40. qemu_trusty_arm64-userdebug
>  41. uml-userdebug
>
>
>
>
>
> Question 2: Although the list provided above offers lots of options, it 
> doesn't list them all.
> Is there a way to list every single option?
>
>
>
>
>
> Question 3: Android on Intel Platform seems to have renamed to "Project 
> Celadon".
> So I tried using the following manifest:
> repo init -u 
> https://github.com/projectceladon/manifest/blob/master/default.xml
> I'm not sure if this Celadon manifest is the one I need for my Intel 
> Tablet.
>
>
> Even if I use the lunch combination "celadon-user" I still get the 
> following error:
>
> ...
> ...
> ...
> ...
>
> Skipped fetching project platform/hardware/qcom/msm8998 (already have 
> persistent ref)
> Skipped fetching project device/google/marlin-kernel (already have 
> persistent ref)
> Skipped fetching project platform/test/vts-testcase/hal (already have 
> persistent ref)
> Skipped fetching project platform/external/f2fs-tools (already have 
> persistent ref)
> Skipped fetching project platform/tools/security (already have persistent 
> ref)
> Skipped fetching project platform/external/python/httplib2 (already have 
> persistent ref)
> Skipped fetching project platform/external/libhevc (already have 
> persistent ref)
> Fetching projects:  99% (796/804) platform/external/python/httplib2Skipped 
> fetching project platform/frameworks/opt/setupwizard (already have 
> persistent ref)
> Skipped fetching project device/generic/car (already have persistent ref)
> Skipped fetching project platform/external/iperf3 (already have 
> persistent ref)
> Skipped fetching project platform/packages/apps/CertInstaller (already 
> have persistent ref)
> Skipped fetching project platform/tools/apkzlib (already have persistent 
> ref)
> Fetching projects: 100% (804/804), done.
> Checking out projects:   4% (33/803) device/generic/x86_64error: Cannot 
> checkout device/google/bonito-kernel: GitError: device/google/bonito-kernel 
> rev-list ('^eebd2aa4f12a59eec71188a59f5b67a1d9418251', 'HEAD', '--'): 
> fatal: bad object HEAD
>
> Traceback (most recent call last):
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 530, in 
> 
> _Main(sys.argv[1:])
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 505, in 
> _Main
> result = run()
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 498, in 
> 
> run = lambda: repo._Run(name, gopts, argv) or 0
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 201, in _Run
> result = cmd.Execute(copts, cargs)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/sync.py", line 994, 
> in Execute
> self._Checkout(all_projects, opt)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/sync.py", line 553, 
> in _Checkout
> self._CheckoutWorker(**kwargs)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/sync.py", line 435, 
> in _CheckoutWorker
> return self._CheckoutOne(opt, project, *args, **kwargs)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/

[android-building] Re: Building android-10.0.0_r15 segmentation fault error

['Glenn Kasten' via Android Building]

This is most likely due to insufficient RAM (8 GB).
I'll request that this page be updated:
https://source.android.com/setup/build/requirements

On Wednesday, January 8, 2020 at 12:01:10 PM UTC-8, Eliane Fonseca wrote:
>
> [ 15% 13954/87886] target  C++: libLLVM_swiftshader <= 
> external/swiftshader/third_party/llvm-7.0/llvm/lib
> FAILED: 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
> /bin/bash -c "PWD=/proc/self/cwd  
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++ -I bionic -I 
> external/swiftshader/third_party/llvm-7.0/llvm/include -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/AArch64 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/ARM -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/configs/android/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/IR -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/AArch64 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/ARM 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/X86 
> -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Transforms/InstCombine
>  
> -I external/swiftshader/third_party/llvm-7.0 -I 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> -I 
> out/target/product/generic_x86/gen/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> \$(cat 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/import_includes)
>
> -isystem out/target/product/generic_x86/obj/include -c  -msse3 
> -mstackrealign -DANDROID -fmessage-length=0 -W -Wall -Wno-unused 
> -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG 
> -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing 
> -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof 
> -faddrsig -Wimplicit-fallthrough -Werror=int-conversion 
> -Wno-reserved-id-macro -Wno-format-pedantic 
> -Wno-unused-command-line-argument -fcolor-diagnostics 
> -Wno-zero-as-null-pointer-constant -Wno-sign-compare 
> -Wno-defaulted-function-deleted -Wno-inconsistent-missing-override 
> -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables 
> -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 
> -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor 
> -Werror=address -Werror=sequence-point -Werror=date-time 
> -Werror=format-security -nostdlibinc -m32 -march=prescott -target 
> i686-linux-android 
> -Bprebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/x86_64-linux-android/bin
>   
> -Wsign-promo -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS 
> -Wno-thread-safety-negative -Wno-gnu-include-next 
> -fvisibility-inlines-hidden  -std=gnu++17   -fno-rtti 
> -DLOG_TAG=\\\"libLLVM_swiftshader\\\" -Wall -Werror 
> -Wno-implicit-exception-spec-mismatch -Wno-overloaded-virtual 
> -Wno-undefined-var-template -Wno-unneeded-internal-declaration 
> -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef 
> -Wno-unused-parameter -Wno-unused-private-field -Wno-unused-variable 
> -Wno-unknown-warning-option -Xclang -fuse-init-array -Os 
> -fomit-frame-pointer -ffunction-sections -fdata-sections 
> -fno-operator-names -msse2 -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
> -DANDROID_PLATFORM_SDK_VERSION=29 -U_FORTIFY_SOURCE -D__ANDROID_API__=29 
> -D__ANDROID_VNDK__ -fPIC -Wno-enum-compare -Wno-enum-compare-switch 
> -Wno-null-pointer-arithmetic -Wno-null-dereference -D_USING_LIBCXX 
> -std=c++11  -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast 
> -Werror=address-of-temporary -Werror=return-type 
> -Wno-tautological-constant-compare -Wno-tautological-type-limit-compare 
> -Wno-tautological-unsigned-enum-zero-compare 
> -Wno-tautological-unsigned-zero-compare -Wno-c++98-compat-extra-semi 
> -Wno-return-std-move-in-c++11  -MD -MF 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.d
>  
> -o 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
>  
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Analysis/SyntheticCountsUtils.cpp"
> Stack dump:
> 0.Program arguments: 
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++.real -cc1 -triple 
> i686-unknown-linux-android -emit-obj -mnoexecstack -disable-free 
> -disable-llvm-verifier -discard-value-names -main-file-name 
> SyntheticCountsUtils.cpp -mrelocation-model pic -pic-level 2 -mthread-model 
> posix -relaxed-aliasing -masm-verbose -mconstructor-aliases -munwind-tables 
> -fuse-init-array -target-cpu prescott -t

[android-building] Re: Building android-10.0.0_r15 segmentation fault error

['Glenn Kasten' via Android Building]

Thank you.  I have filed an internal bug and will plan to get back to you 
if they request additional information.

On Wednesday, January 8, 2020 at 1:06:12 PM UTC-8, Eliane Fonseca wrote:
>
> Below is the hardware/build config
>
> Release branch: android10-qpr1-release, android-10.0.0_r15, Build target: 
> aosp_x86-eng, command: m -j2, Host: Ubuntu 18.04 64 bit, Hardware config: 
> AMD C-60 CPU (2 cores, 1.00 GHz)/8 GB RAM/285 GB storage. This happened 
> today after 2+ hours building. Not sure if it was insufficient RAM or high 
> CPU usage.
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/7ba4884d-904e-4fa3-9384-56a3b9c1558f%40googlegroups.com.

[android-building] Re: Building android-10.0.0_r15 segmentation fault error

['Glenn Kasten' via Android Building]

Thank you for reporting this.
Can you please mention which branch you synced, the lunch command, the 
top-level make command you used, the host OS and hardware configuration, 
and any other information that might help to reproduce or investigate (for 
example, whether this is a new problem and what changed recently, etc.)?

On Wednesday, January 8, 2020 at 12:01:10 PM UTC-8, Eliane Fonseca wrote:
>
> [ 15% 13954/87886] target  C++: libLLVM_swiftshader <= 
> external/swiftshader/third_party/llvm-7.0/llvm/lib
> FAILED: 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
> /bin/bash -c "PWD=/proc/self/cwd  
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++ -I bionic -I 
> external/swiftshader/third_party/llvm-7.0/llvm/include -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/AArch64 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/ARM -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/configs/android/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/IR -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/AArch64 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/ARM 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/X86 
> -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Transforms/InstCombine
>  
> -I external/swiftshader/third_party/llvm-7.0 -I 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> -I 
> out/target/product/generic_x86/gen/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> \$(cat 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/import_includes)
>
> -isystem out/target/product/generic_x86/obj/include -c  -msse3 
> -mstackrealign -DANDROID -fmessage-length=0 -W -Wall -Wno-unused 
> -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG 
> -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing 
> -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof 
> -faddrsig -Wimplicit-fallthrough -Werror=int-conversion 
> -Wno-reserved-id-macro -Wno-format-pedantic 
> -Wno-unused-command-line-argument -fcolor-diagnostics 
> -Wno-zero-as-null-pointer-constant -Wno-sign-compare 
> -Wno-defaulted-function-deleted -Wno-inconsistent-missing-override 
> -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables 
> -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 
> -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor 
> -Werror=address -Werror=sequence-point -Werror=date-time 
> -Werror=format-security -nostdlibinc -m32 -march=prescott -target 
> i686-linux-android 
> -Bprebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/x86_64-linux-android/bin
>   
> -Wsign-promo -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS 
> -Wno-thread-safety-negative -Wno-gnu-include-next 
> -fvisibility-inlines-hidden  -std=gnu++17   -fno-rtti 
> -DLOG_TAG=\\\"libLLVM_swiftshader\\\" -Wall -Werror 
> -Wno-implicit-exception-spec-mismatch -Wno-overloaded-virtual 
> -Wno-undefined-var-template -Wno-unneeded-internal-declaration 
> -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef 
> -Wno-unused-parameter -Wno-unused-private-field -Wno-unused-variable 
> -Wno-unknown-warning-option -Xclang -fuse-init-array -Os 
> -fomit-frame-pointer -ffunction-sections -fdata-sections 
> -fno-operator-names -msse2 -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
> -DANDROID_PLATFORM_SDK_VERSION=29 -U_FORTIFY_SOURCE -D__ANDROID_API__=29 
> -D__ANDROID_VNDK__ -fPIC -Wno-enum-compare -Wno-enum-compare-switch 
> -Wno-null-pointer-arithmetic -Wno-null-dereference -D_USING_LIBCXX 
> -std=c++11  -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast 
> -Werror=address-of-temporary -Werror=return-type 
> -Wno-tautological-constant-compare -Wno-tautological-type-limit-compare 
> -Wno-tautological-unsigned-enum-zero-compare 
> -Wno-tautological-unsigned-zero-compare -Wno-c++98-compat-extra-semi 
> -Wno-return-std-move-in-c++11  -MD -MF 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.d
>  
> -o 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
>  
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Analysis/SyntheticCountsUtils.cpp"
> Stack dump:
> 0.Program arguments: 
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++.real -cc1 -triple 
> i686-unknown-linux-android -emit-obj -mnoexecstack -disable-free 
> -disable-llvm-verifier -discard-value-names -main-file-name 
> SyntheticCountsUt

[android-building] Re: Pixel2 AOSP build No default GApps(playstore, gmail, chrome etc)

['Glenn Kasten' via Android Building]

Sorry proprietary apps and services are off-topic for android-building. 
Please read the guidelines at top of
   https://groups.google.com/forum/#!forum/android-building
in particular:
   "add-on applications and proprietary services not included in the AOSP 
platform distribution"



On Monday, January 6, 2020 at 10:27:24 AM UTC-8, sachin verma wrote:
>
> I have flashed android 10 aosp_walleye-userdebug in my Pixel2 device but I 
> could not find the default applications playstore, gmail, chrome etc(while 
> I had run the google and qualcom driver binaries script before creating 
> build).
>
> Is it disabled in the AOSP build?
>
> How can i enable or install the correct versions on flashed Custom ROM.
>
> Thanks,
> Sachin
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/131367e7-b05d-4a62-ac5c-2d63096f6389%40googlegroups.com.

[android-building] Re: Building Android GSI with Google Apps

['Glenn Kasten' via Android Building]

This topic slipped through moderation and should not have been approved for 
posting;
see guidelines at top of 
https://groups.google.com/forum/#!forum/android-building
in particular item #3 "add-on applications and proprietary services not 
included in the AOSP platform distribution".

On Thursday, December 19, 2019 at 8:31:49 AM UTC-8, Nisarg Ujjainkar wrote:
>
> Hi All, 
>
> I have successfully built and booted Android 9 GSI but it lacks the Google 
> apps. How can I build a GSI with the Google apps included?

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/e87386e0-6865-4b6a-92e1-af5245c4dae2%40googlegroups.com.

[android-building] Re: LineageOS 17.0 build in LXC 2.x - nsjail/sandboxing error

['Glenn Kasten' via Android Building]

Can you reproduce this problem with AOSP distribution?
This discussion group is targeted at AOSP distribution per guidelines here 
.
[I am a volunteer moderator]

On Tuesday, October 22, 2019 at 9:08:28 AM UTC-7, Condor wrote:
>
> Hello,
>
> I've just tried building LineageOS 17.0 for fajita (OnePlus 6T). For 
> efficiency reasons and to maintain isolation from the host I've opted to 
> spin up an LXC container for this.
> The host machine is running Debian 9 and LXC 2.x, while the container is a 
> Debian 10 machine. Apparently this doesn't support nsjail, which caused 
> "breakfast fajita" to fail.
> A screenshot is available at 
> https://www.nixmagic.com/pics/lineage-nsjail-error.png.
> I've followed the build guide at 
> https://wiki.lineageos.org/devices/fajita/build.
> Below is the error log in text form.
>
> Looking for dependencies in kernel/oneplus/sdm845
> kernel/oneplus/sdm845 has no additional dependencies.
> Looking for dependencies in packages/resources/devicesettings 
> packages/resources/devicesettings has no additional dependencies.
> Done
> 15:31:05 Build sandboxing disabled due to nsjail error. This may become 
> fatal in the future.
> 15:31:05 Please let us know why nsjail doesn't work in your environment at:
> 15:31:05 https://groups.google.com/forum/#!forum/android-building
> 15:31:05 https://issuetracker.google.com/issues/new?component=381517
> build/make/target/product/updatable_apex.mk:21: error: 
> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]: 
> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.
> 15:31:11 dumpvars failed with: exit status 1
> 15:31:13 Build sandboxing disabled due to nsjail error. This may become 
> fatal in the future.
> 15:31:13 Please let us know why nsjail doesn't work in your environment at:
> 15:31:13 https://groups.google.com/forum/#!forum/android-building
> 15:31:13 https://issuetracker.google.com/issues/new?component=381517
> build/make/target/product/updatable_apex.mk:21: error: 
> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]: 
> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.
> 15:32:42 dumpvars failed with: exit status 1
>
> ** Don't have a product spec for: 'lineage_fajita'
> ** Do you have the right repo manifest? 
>
> I wish I could explain why nsjail isn't available in LXC but unfortunately 
> I don't know either... I'll retry the build in a VM or on a physical host.
>
> Best regards,
> Michael De Roover (android-building at nixmagic dot com)
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/b8113ccb-73b0-4c6f-8cea-1cd29768f8e4%40googlegroups.com.

[android-building] Re: android Q AOSP available ?

['Glenn Kasten' via Android Building]

Did you try the branch name or tag at
https://groups.google.com/forum/#!topic/android-building/Zj5VVapM8H8


On Wednesday, September 4, 2019 at 9:42:13 PM UTC-7, jw wang wrote:
>
> Hi google
>
> android Q factory is already available for pixel 3a, however, when I try 
> to get android-10.0.0_r1, it fail, any idea which tag/branch name should I 
> take to repo init ??
>
>
> jericho@jericho-System-Product-Name:~/work/agent/_work/android-10.0.0_r1$ 
> repo init -u https://android.googlesource.com/platform/manifest -b 
> android-10.0.0_r1
> Get https://gerrit.googlesource.com/git-repo/clone.bundle
> Get https://gerrit.googlesource.com/git-repo
> remote: Counting objects: 2, done
> remote: Finding sources: 100% (41/41)
> remote: Total 41 (delta 8), reused 41 (delta 8)
> Unpacking objects: 100% (41/41), done.
> From https://gerrit.googlesource.com/git-repo
>3069be2..46702ed  master -> origin/master
>745be2e..46702ed  stable -> origin/stable
>  * [new tag] v1.13.5-> v1.13.5
>  * [new tag] v1.13.5.1  -> v1.13.5.1
> Get https://android.googlesource.com/platform/manifest
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  
> Speed
>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--  
>0
> curl: (22) The requested URL returned error: 404 Not Found
> Server does not provide clone.bundle; ignoring.
> fatal: Couldn't find remote ref refs/heads/android-10.0.0_r1
>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/8af3990d-9ce1-476c-a3b4-9835a934cec1%40googlegroups.com.

Re: [android-building] Re: Error when building Reference TV App

['Glenn Kasten' via Android Building]

Please see the second paragraph of
https://source.android.com/setup/community#for-business-inquiries
that starts "While we read ...". 

On Thursday, August 1, 2019 at 7:23:58 PM UTC-7, jw wang wrote:
>
>
> Hi Nick
>
> what do you mean for "partner engineering source " ?
>
> is it a android Q pre aosp that available for the pixel device, I mean, 
> I'm looking for some way to get a pre-Q AOSP that I'm able to build Q 
> userdebug image for my pixels, 
>
> so I can start some migration of the project inside framework (no source 
> code available in androidsource for general public) on the upcoming OS, 
>
> I've tried to write to android-partnersh...@google.com but end up 
> nothing, can you give me some clue ?
>
>
>
>
>
>
> On Friday, 2 August 2019 03:12:01 UTC+8, Nick Chalko wrote:
>>
>> Sorry about that.  
>>
>>
>> I have verified that my latest internal version build on Q.
>> I am working with my build team to get the source on Q updated and that 
>> will be released to public when Q is released.
>>
>> Meanwhile do you have access to partner engineering source ?
>>
>>
>> On Thu, Aug 1, 2019 at 7:54 AM Haris Zukanović  
>> wrote:
>>
>>> I tried building today... it still does not work...
>>> Any updates to expect soon?
>>>
>>> -- 
>>> -- 
>>> 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-...@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 a topic in the 
>>> Google Groups "Android Building" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/android-building/f6aGR9qo9WI/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> android-...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/android-building/6fea0bfe-0e69-43ad-a4ed-327d74f7a576%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Nick Chalko | Software Engineer | nch...@google.com |   :-) 
>> Generate your java flags for easier testing.
>> go/java-flags-generator
>>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/8b1c51de-e13d-4d2f-9f1b-fa6022052e59%40googlegroups.com.

Re: [android-building] Re: No files in working folder after running repo sync

['Glenn Kasten' via Android Building]

Yes it looks like the DNS lookup failed: Could not resolve host: 
android.googlesource.com
but strange that it succeeded earlier. As you mentioned, perhaps try again.

On Wednesday, July 24, 2019 at 4:02:09 PM UTC-7, Lord Unknown wrote:
>
> Hi Glenn,
>
> Here's all the errors in repo sync: https://hastebin.com/quxuwumexo
> repo init did not output any errors.
>
> Here's the full output: https://hastebin.com/locubibaju 
> <https://hastebin.com/locubibaju.>
>
> The internet connection was a bit slow today. Maybe that's the issue.
>
> Thank you in advance,
> - Michael
>
> On Wed, Jul 24, 2019 at 8:23 PM 'Glenn Kasten' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> Can you please include a short excerpt of just any errors in the output 
>> of the repo init and sync?
>>
>> On Wednesday, July 24, 2019 at 10:20:52 AM UTC-7, Lord Unknown wrote:
>>>
>>> Hi everyone,
>>>
>>> I ran repo init and repo sync in /vagrant/android (I'm running Ubuntu 
>>> 14.04 in Vagrant). I ran ls in /vagrant/android and there were no folders, 
>>> except .repo
>>>
>>> What could happen with folders? And how to solve this problem?
>>>
>>> The commands that I've used: 
>>> repo init -u https://android.googlesource.com/platform/manifest -b 
>>> android-9.0.0_r45 -p linux --depth=1
>>> repo sync -j9
>>>
>>> Regards,
>>> - Michael
>>>
>> -- 
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/android-building/b06387f6-81e5-4d84-a825-f3687ae88979%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/android-building/b06387f6-81e5-4d84-a825-f3687ae88979%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/3b5b5352-a0cd-4ba6-affb-e31dc113c91e%40googlegroups.com.

[android-building] Re: No files in working folder after running repo sync

['Glenn Kasten' via Android Building]

Can you please include a short excerpt of just any errors in the output of 
the repo init and sync?

On Wednesday, July 24, 2019 at 10:20:52 AM UTC-7, Lord Unknown wrote:
>
> Hi everyone,
>
> I ran repo init and repo sync in /vagrant/android (I'm running Ubuntu 
> 14.04 in Vagrant). I ran ls in /vagrant/android and there were no folders, 
> except .repo
>
> What could happen with folders? And how to solve this problem?
>
> The commands that I've used: 
> repo init -u https://android.googlesource.com/platform/manifest -b 
> android-9.0.0_r45 -p linux --depth=1
> repo sync -j9
>
> Regards,
> - Michael
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/b06387f6-81e5-4d84-a825-f3687ae88979%40googlegroups.com.

[android-building] Re: Error when build Android Q Beta5 for Pixel3

['Glenn Kasten' via Android Building]

The previews are not intended to be buildable, they are for reference only.

See this post:
GPL projects for Android Q Beta 5
https://groups.google.com/forum/#!topic/android-building/uXXzjIqvER8

On Wednesday, July 24, 2019 at 6:01:54 AM UTC-7, Phuoc Nguyen wrote:
>
> Dear All,
> I am trying to build Android Q Beta5 for Pixel3 but the error occurred. 
> Could you shed me some light?
> Thanks
> Phuoc
>
>  abc@abc-283:~/Downloads/WORKING_DIRECTORY$ source build/envsetup.sh
> abc@abc-283:~/Downloads/WORKING_DIRECTORY$ lunch
>
> You're building on Linux
>
> Lunch menu... pick a combo:
>  1. aosp_arm-eng
>  2. aosp_arm64-eng
>  3. aosp_blueline-userdebug
>  4. aosp_car_arm-userdebug
>  5. aosp_car_arm64-userdebug
>  6. aosp_car_x86-userdebug
>  7. aosp_car_x86_64-userdebug
>  8. aosp_cf_arm64_phone-userdebug
>  9. aosp_cf_x86_64_phone-userdebug
>  10. aosp_cf_x86_auto-userdebug
>  11. aosp_cf_x86_phone-userdebug
>  12. aosp_cf_x86_tv-userdebug
>  13. aosp_crosshatch-userdebug
>  14. aosp_walleye-userdebug
>  15. aosp_walleye_test-userdebug
>  16. aosp_x86-eng
>  17. aosp_x86_64-eng
>  18. beagle_x15-userdebug
>  19. hikey-userdebug
>  20. hikey64_only-userdebug
>  21. hikey960-userdebug
>  22. hikey960_tv-userdebug
>  23. hikey_tv-userdebug
>  24. m_e_arm-userdebug
>  25. mini_emulator_arm64-userdebug
>  26. mini_emulator_x86-userdebug
>  27. mini_emulator_x86_64-userdebug
>  28. poplar-eng
>  29. poplar-user
>  30. poplar-userdebug
>  31. qemu_trusty_arm64-userdebug
>  32. uml-userdebug
>
> Which would you like? [aosp_arm-eng] aosp_blueline-userdebug
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=10
> TARGET_PRODUCT=aosp_blueline
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=generic
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.8.0-59-generic-x86_64-Ubuntu-16.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=QP1A.190711.002
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av 
> hardware/google/interfaces hardware/google/pixel hardware/qcom/sdm845 
> vendor/google/camera vendor/qcom/sdm845 vendor/google/interfaces
> 
> abc@abc-283:~/Downloads/WORKING_DIRECTORY$ make -j4
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=10
> TARGET_PRODUCT=aosp_blueline
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=generic
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.8.0-59-generic-x86_64-Ubuntu-16.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=QP1A.190711.002
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av 
> hardware/google/interfaces hardware/google/pixel hardware/qcom/sdm845 
> vendor/google/camera vendor/qcom/sdm845 vendor/google/interfaces
> 
> [100% 1/1] 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: device/google/wahoo/Android.bp:1:1: module "soong_namespace": 
> namespace hardware/google/pixel does not exist
> 08:28:15 soong bootstrap failed with: exit status 1
>
>  failed to build some targets (2 seconds) 
>
> abc@abc-283:~/Downloads/WORKING_DIRECTORY$ 
>
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/8be01e34-1ece-4582-8238-c2211d196c27%40googlegroups.com.

[android-building] Re: Q-preview AOSP availability ?

['Glenn Kasten' via Android Building]

The previews are not intended to be buildable, they are for reference only.

On Monday, July 1, 2019 at 8:05:52 AM UTC-7, jw wang wrote:
>
> Hello google
>
> is it possible that we can repo sync Q-preview AOSP, and build the 
> userdebug version into pixel 3a ?
> now the preview are mostly used to test API level, but when it comes to 
> testing the component compatibility under native layer for example
> frameworks/av/service/audioflinger, this obvious need a right aosp and 
> userdebug privilege to do so.
>
> I can see there so far are many Q-preview tags 
>
> https://android.googlesource.com/platform/frameworks/av/+/refs/tags/android-q-preview-4/services/audioflinger/
>
> but according to the experience in past few years, this ends up totally 
> different to the formal release..
>
> which branch in the current aosp git resemble the Q preview most ??
>
> is it the master branch repo init -u 
> https://android.googlesource.com/platform/manifest???
>
> thanks
>
>
>  
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/89377bb6-9d19-4501-82a4-88d3e5e07e95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: GPL projects for Android Q Beta 4

['Glenn Kasten' via Android Building]

This preview is not intended to be buildable, it is for reference only.

On Sunday, June 16, 2019 at 7:47:45 PM UTC-7, Paulo Costa wrote:
>
> I found this problem too, and for once the fix was exactly what the error 
> suggested: 
>
> LPF + F2FS_SLOT_LEN -> &LPF[F2FS_SLOT_LEN] 
>
> However, there are other compilation errors after this one -- I gave up 
> before I could get to the end of a full compilation. 
>
> Also, the tag doesn't have many of the Q's changes -- particularly in 
> framework, most of the new APIs are missing, which makes it kind of useless 
> :/ 
>
> I ended extracting framework.jar from a Q beta 4 device and decompiling it 
> with dex2jar.

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/ebe6d4bf-67c4-4ebd-a375-3ff600b98f79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: AOSP libselinux build error for android-q-preview-1

['Glenn Kasten' via Android Building]

Reminder: see March 14 post. It still applies:

*"This preview is not a full platform update and only for reference."*

On Thursday, June 6, 2019 at 2:41:09 PM UTC-7, Paulo Costa wrote:
>
> Same problem here building Beta 4 (And beta 2.5 before)
>
> Did you ever figure it out?
>
> On Monday, May 20, 2019 at 12:30:07 PM UTC-3, Jean-Marc GRIMAUD wrote:
>>
>> Hi,
>> I now try to build android-q-preview-2.5, and have the following error:
>> error: cts/hostsidetests/jdwptunnel/Android.bp:15:1: 
>> "CtsJdwpTunnelHostTestCases" depends on undefined module "jdi-support"
>>
>> Any idea how to solve it ?
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/c9ebb4de-6bbb-44be-a390-f89b75e8aaa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: Why did you name it Soong, Kati, Ninja ?

['Glenn Kasten' via Android Building]

Kati  and Soong 
 appear to be from 
Star Trek.
I assume that Ninja comes from here 
 
:-)

On Tuesday, May 14, 2019 at 10:13:28 PM UTC-7, CK RYU wrote:
>
> Hi,
>
>  
>
> I have question about the soong build system.
>
>  
>
> I want to know why did you name it Soong, Kati, Ninja?
>
> Is the name meaningful?'
>
>  
>
> Thanks,
>
>  
>
> CK.RYU
>

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/d8d519db-c921-41dc-b353-d92f0fbe1602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: how to fix run stagefright on ubuntu x86_64 built normally?

['Glenn Kasten' via Android Building]

As far as I know, the 'stagefright' shell command located 
in frameworks/av/cmds/stagefright
is intended for unit testing on Android only, and in any case is 
unsupported.

On Thursday, May 2, 2019 at 11:21:02 AM UTC-7, callme@gmail.com wrote:
>
> I'm trying to run stagefright on linux environment `x86_64`.  
> I built android-9.0.0-r35 as `x86_64`, and compiled kernel with binder, 
> ashmem configuration, but it didn't work.
>
> My environment is Ubuntu14.04 64bit, I compiled and install new kernel 
> 4.20.17.
>
> According to https://source.android.com/setup/build/building , I did 
> below first.  I set the build environment as x86_64.
>
>
> $ source build/envsetup.sh
> $ lunch aosp_x86_64-eng
> $ make -j4
>
>
> I Also built stagefright like below.
>
>
> $ cd [AOSP sourcecode]/framework/av
> $ mma -j4
>
>
>
> After that, I made a symbolic link for runtime-environment.
>
>
> $ ln -s [AOSP sourcecode]/out/target/product/generic_x86_64/system /system
>
>
>
> Next, I download newer version kernel, 4.20.17, and copied my original 
> configuration file, and add options, compiled, and install it.
>
>
> $ cp /boot/config-4.4.0-142-generic .config
>
>
> (.config file)
> ...
> CONFIG_ANDROID=y
> CONFIG_ANDROID_BINDER_IPC=y
> CONFIG_ASHMEM=y
> ...
>
>
> $ make menuconfig
> $ make-kpkg --initrd --J 4 kernel_image
> $ dpkg -i linux-image-4.20.17_4.20.17-10.00.Custom_amd64.deb
> $ echo -e "KERNEL==\"binder\", MODE=\"0666\"\nKERNEL==\"ashmem\", 
> MODE=\"0666\"" | tee /etc/udev/rules.d/android.rules
>
>
>
> After that process, I rebooted my VM, and tried to run the stagefright.
>
>
> $ /system/bin/stagefright -s sample.mp4
>
>
> (waiting until ctrl+c)
>
>
>
> But the result is `nothing`. The process didn't stop or finish.
>
> I just want to know how to run stagefright on x86_64 environment.
> (I don't want to ARM cross compile stagefright.)
>
> AOSP version is pie_9.0.0-r35.
> Is anybody know how to fix it and run stagefright on ubuntu x86_64 
> normally?
>

-- 
-- 
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] AOSP libselinux build error for android-q-preview-1

[Glenn Kasten]

The "android-q-preview-1" tag refers to the sources published as part of 
this post:

   GPL projects for Android Q Beta 1

   https://groups.google.com/forum/#!topic/android-building/alh5sZHhEtU

Please note that it is not a complete release, and only includes GPL 
projects.

On Monday, March 18, 2019 at 12:18:59 PM UTC-7, Jacob Abrams wrote:
>
> Google pushed a tag to AOSP named "android-q-preview-1" a few days ago but 
> it is unclear what exactly makes it "Q" since the API level didn't change 
> and it appears to be missing new APIs like 
> Activity#onTopResumedActivityChanged()
>
> Would be nice if someone could explain what exactly the 
> "android-q-preview-1" tag is.
>
> I guess Google won't actually be releasing the source code for Q until 
> after they go through several preview releases? It appears that is what 
> they did last time with Pie.
>
> Jacob
>
> On Thursday, March 14, 2019 at 8:29:47 AM UTC-7, shahul hameed wrote:
>>
>> Hi Jacob,
>>
>> Is Android Q source available? can you share me link to download source.
>>
>> Regards,
>> SkShahul.
>>
>> On Thu, Mar 14, 2019, 11:31 AM Jacob Abrams  wrote:
>>
>>> 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-...@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.

Re: [android-building] AOSP libselinux build error for android-q-preview-1

[Glenn Kasten]

Please read this part of the post:
   

   GPL projects for Android Q Beta 1

   https://groups.google.com/forum/#!topic/android-building/alh5sZHhEtU


   ... *"This preview is not a full platform update and only for 
reference."*


Thank you

On Thursday, March 14, 2019 at 8:29:47 AM UTC-7, shahul hameed wrote:
>
> Hi Jacob,
>
> Is Android Q source available? can you share me link to download source.
>
> Regards,
> SkShahul.
>
> On Thu, Mar 14, 2019, 11:31 AM Jacob Abrams  wrote:
>
>> 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.
>>
>

-- 
-- 
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: Where can I download goldfish 4.20 kernel?

[Glenn Kasten]

I see named branches up to 4.14, but not 4.20:
  https://android.googlesource.com/kernel/goldfish/+refs
Perhaps it has not yet been ported to 4.20, or if it has been ported then 
the port hasn't yet been published?
4.20 is relatively recent, and the latest long-term stable (LTS) after 4.14 
is 4.19,
so it seems more likely that goldfish would be ported to 4.19 rather than 
4.20.

On Wednesday, 20 February 2019 08:03:55 UTC-8, Yuan Zhou wrote:
>
> I want to customize some feature in linux 4.20. Where can I download 
> goldfish 4.20 kernel? It is not on the googlesource.com. Thank you
>

-- 
-- 
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: Optimization level

[Glenn Kasten]

-O2 comes from the default options in build/soong/cc/config/global.go

-Os comes from external/v8/Android.v8common.mk that overrides those defaults

For most options, the last one takes effect.
An exception is options that accumulate such as -I directories.

On Friday, November 9, 2018 at 7:27:47 AM UTC-8, Muhui Jiang wrote:
>
> Hi
>
> I download the source code (PR2.180905.006.A1 android-9.0.0_r8).
>
> I set the compile target as aosp_arm-eng. Then I use make showcommands to 
> try to dig the detail flags used for compiling.
>
> I am curious about the optimization level. For example, Below is one 
> command generated.
>
>   2629 [  0% 619/77386] /bin/bash -c "PWD=/proc/self/cwd  
> prebuilts/clang/host/linux-x86/clang-4691093/bin/clang++ -I 
> external/v8/src -I external/v8 -I 
> out/host/linux-x86/obj/STATIC_LIBRARIES/libv8base_intermediates -I 
> out/host/linux-x86/gen/STATIC_LIBRARIES/libv8base_intermediates -I 
> libnativehelper/include_jni \$(cat 
> out/host/linux-x86/obj/STATIC_LIBRARIES/libv8base_intermediates/import_includes)
>   
> -I system/core/include -I system/media/audio/include -I 
> hardware/libhardware/include -I hardware/libhardware_legacy/include -I 
> hardware/ril/include -I libnativehelper/include -I 
> frameworks/native/include -I frameworks/native/opengl/include -I 
> frameworks/av/include  -c  -Wa,--noexecstack -fPIC -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -fstack-protector -D__STDC_FORMAT_MACROS 
> -D__STDC_CONSTANT_MACROS 
> --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 
> --sysroot prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot 
> -fstack-protector-strong -m64 -DANDROID -fmessage-length=0 -W -Wall 
> -Wno-unused -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG 
> -UDEBUG -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing 
> -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof 
> -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic 
> -Wno-unused-command-line-argument -fcolor-diagnostics 
> -Wno-expansion-to-defined -Wno-zero-as-null-pointer-constant 
> -fdebug-prefix-map=\$PWD/=   -target x86_64-linux-gnu 
> -Bprebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/bin  
> -Wsign-promo -Wno-inconsistent-missing-override -Wno-null-dereference 
> -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS -Wno-thread-safety-negative 
> -Wno-gnu-include-next  -isystem 
> prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8
>  
> -isystem 
> prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/backward
>  
> -isystem 
> prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/x86_64-linux
>  
> -std=gnu++14  -Wall -Werror -Wno-endif-labels -Wno-import -Wno-format 
> -Wno-unused-parameter -Wno-unused-private-field -Wno-sign-compare 
> -Wno-missing-field-initializers -Wno-ignored-qualifiers 
> -Wno-undefined-var-template -fno-exceptions -fvisibility=hidden 
> -DENABLE_DEBUGGER_SUPPORT -DENABLE_LOGGING_AND_PROFILING 
> -DENABLE_VMSTATE_TRACKING -DV8_NATIVE_REGEXP -DV8_I18N_SUPPORT -std=gnu++0x 
> -Os -fPIC -DV8_TARGET_ARCH_X64 -D_USING_LIBCXX -nostdinc++  
> -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast 
> -Werror=address-of-temporary -Werror=return-type 
> -Wno-tautological-constant-compare -Wno-null-pointer-arithmetic 
> -Wno-enum-compare -Wno-enum-compare-switch   -MD -MF 
> out/host/linux-x86/obj/STATIC_LIBRARIES/libv8base_intermediates/src/base/file-utils..d
>  
> -o 
> out/host/linux-x86/obj/STATIC_LIBRARIES/libv8base_intermediates/src/base/file-utils..o
>  
> external/v8/src/base/file-utils.cc"
>
> As you can see, there are two optimization flags. I highlighted it. My 
> question is what is the optimization level. O2 or Os? Or they have 
> different meanings? Many Thanks
>
> Regards
> Muhui
>

-- 
-- 
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: what are the packages required to build pixel experiance android pie

[Glenn Kasten]

Sorry, off-topic for android-building.  android-building is for discussion 
of AOSP only,
not any proprietary software.

On Tuesday, November 6, 2018 at 10:15:55 AM UTC-8, austin pinto wrote:
>
> hi all. 
> i am on Ubuntu 18.10 the latest 9months supported branch. 
> i want to build pixel experience rom and this is my first rom building. 
> i downloaded pie sources and want to know what packages required for a 
> successfull build. 
> i red tutorials on xda but they are very old and talk about building 
> android 4 and 5 
>

-- 
-- 
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: Android 9.0.0 Pie QPR1 Released

[Glenn Kasten]

If only that were true :-)  
No, "QPR" stands for "Quarterly Platform Release". 
Sorry to disappoint !

On Tuesday, November 6, 2018 at 6:34:28 AM UTC-8, SZ Lee wrote:
>
> Hi Xin Li,
>
> Does QPR1 means Q pre-release is coming soon?
>
> Thanks
>
>
> 2018년 11월 6일 화요일 오전 9시 39분 24초 UTC+9, Xin Li 님의 말:
>>
>> Hi all,
>>
>> Android 9.0.0 Pie QPR1 source code is now available. The following 
>> builds, tags, and devices are supported:
>>
>>  - PQ1A.181105.017.A1, android-9.0.0_r16, Pixel 3 XL (crosshatch), Pixel 
>> 3 (blueline), Pixel 2 XL (taimen), Pixel 2 (walleye)
>>
>> The corresponding factory images, ota images, and proprietary binaries 
>> are available at
>>
>>  https://developers.google.com/android/images
>>  https://developers.google.com/android/ota
>>  https://developers.google.com/android/drivers
>>
>> We have pushed the corresponding kernel projects for the following 
>> devices:
>>
>> Tag | Project | Branch
>>  | Device
>> android-9.0.0_r0.35 | kernel/msm  | 
>> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
>> android-9.0.0_r0.35 | kernel/msm-extra| 
>> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
>> android-9.0.0_r0.35 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
>> android-9.0.0_r0.35 | kernel/msm-modules/qcacld   | 
>> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
>> android-9.0.0_r0.35 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-crosshatch-4.9-pie-qpr1| Pixel 3 XL, Pixel 3
>> android-9.0.0_r0.36 | kernel/arm64| 
>> android-blue-intel-linux-4.7-pie-qpr1  | Pixel 3 XL, Pixel 3
>> android-9.0.0_r0.37 | kernel/msm  | 
>> android-msm-wahoo-4.4-pie-qpr1 | Pixel 2 XL, Pixel 2
>> android-9.0.0_r0.38 | kernel/arm64| 
>> android-amber-intel-linux-4.7-pie-qpr1 | Pixel 2 XL, Pixel 2
>>
>

-- 
-- 
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] Clean Android 9 AOSP builds not finding Phone Sim on Pixel

[Glenn Kasten]

See https://source.android.com/source/report-bugs

On Monday, October 29, 2018 at 7:34:08 AM UTC-7, Brian Moore wrote:
>
> Sure. How and where do I file? 
> (I'm not really much of a developer, I just like to build my own AOSP for 
> my phone) 

-- 
-- 
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] Re: Android full mirror download size

[Glenn Kasten]

Documentation has been updated, see the blue note:
https://source.android.com/setup/build/requirements#hardware-requirements

It still does not give the exact requirement, but at least it now warns you 
that you need more.

Thanks again for reporting this!

On Wednesday, October 24, 2018 at 7:49:50 AM UTC-7, Vincent Victor wrote:
>
> Hi Colin, 
>
> So instead of "mirror" in path "platform" needs to be used, right?
>
> Further, what is use of "-b master" flag. Official website says, "To check 
> out a branch other than "master", specify it with -b." This means "-b 
> master" should not be required for master branch.
>
> Please help me with these two confusions! Thanks!
>
> On Wednesday, 24 October 2018 00:21:53 UTC+5:30, Colin Cross wrote:
>>
>> Use repo init -u https://android.googlesource.com/platform/manifest -b 
>> master --mirror to only sync projects that are in the master manifest.
>>
>> On Tue, Oct 23, 2018 at 10:10 AM Vincent Victor  
>> wrote:
>>
>>> Do we have any way using which only mirror for master branch could be 
>>> maintained and used for syncing clients?
>>>
>>> On Tuesday, 23 October 2018 02:08:24 UTC+5:30, andrew_esh wrote:

 I maintain a full mirror on a volume that I recently had to upsize to 
 250G, and I just found out that that size is not enough. I'll have to 
 upsize it again to finish my sync.

 On Friday, October 19, 2018 at 10:18:59 AM UTC-5, Vincent Victor wrote:
>
> I am creating a local Android full mirror using commands mentioned on 
> official Android website as follows:
>
> mkdir -p /usr/local/aosp/mirror
> cd /usr/local/aosp/mirror
> repo init -u https://android.googlesource.com/mirror/manifest --mirror
> repo sync
>
> It already downloaded 173GB and still going on. Do we have any idea 
> that how much will be the final size? Am I doing anything wrong here?
>
 -- 
>>> -- 
>>> 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.

Re: [android-building] Re: Android full mirror download size

[Glenn Kasten]

Thanks, I'll let our doc team know so they can mention it.

On Monday, October 22, 2018 at 11:37:22 AM UTC-7, Colin Cross wrote:
>
> Mirrors are much bigger than a normal checkout, at least a few hundred GB.
>
> On Mon, Oct 22, 2018 at 7:17 AM Vincent Victor  
> wrote:
>
>> Download was ongoing till 238 GB and then I killed it. Could not afford 
>> to keep it continue. One more thing, I was downloading in home folder 
>> instead of /usr/local/, could this be the problem? 
>>
>> On Saturday, 20 October 2018 08:12:27 UTC+5:30, Glenn Kasten wrote:
>>>
>>> According to section Hardware Requirements of
>>> https://source.android.com/setup/build/requirements
>>> only 100 gig is needed.  So either that doc is wrong,
>>> or your download has gone wild.  Please post here if it finishes,
>>> and if so what the actual size is. 
>>>
>>> On Friday, October 19, 2018 at 8:18:59 AM UTC-7, Vincent Victor wrote:
>>>>
>>>> I am creating a local Android full mirror using commands mentioned on 
>>>> official Android website as follows:
>>>>
>>>> mkdir -p /usr/local/aosp/mirror
>>>> cd /usr/local/aosp/mirror
>>>> repo init -u https://android.googlesource.com/mirror/manifest --mirror
>>>> repo sync
>>>>
>>>> It already downloaded 173GB and still going on. Do we have any idea 
>>>> that how much will be the final size? Am I doing anything wrong here?
>>>>
>>> -- 
>> -- 
>> 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] Re: Android full mirror download size

[Glenn Kasten]

According to section Hardware Requirements of
https://source.android.com/setup/build/requirements
only 100 gig is needed.  So either that doc is wrong,
or your download has gone wild.  Please post here if it finishes,
and if so what the actual size is. 

On Friday, October 19, 2018 at 8:18:59 AM UTC-7, Vincent Victor wrote:
>
> I am creating a local Android full mirror using commands mentioned on 
> official Android website as follows:
>
> mkdir -p /usr/local/aosp/mirror
> cd /usr/local/aosp/mirror
> repo init -u https://android.googlesource.com/mirror/manifest --mirror
> repo sync
>
> It already downloaded 173GB and still going on. Do we have any idea that 
> how much will be the final size? Am I doing anything wrong here?
>

-- 
-- 
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: Deleting an entire repo sync

[Glenn Kasten]

If I understood the original question correctly, I believe that the problem 
was that the directory contained a mix of repo files and unrelated files 
that are important.
So in that case, rm -rf on the whole folder could delete the important 
files also.
Until repo has an uninit/destroy command, here is a workaround:
   cd directory
   ls -alt directory
The repo synced files should mostly be near the top, so you can just rm -rf 
on those directories.
The -t option sorts by time, and -a allows you to the see the . files such 
as .repo/

On Monday, October 15, 2018 at 9:21:47 AM UTC-7, Chih-Wei Huang wrote:
>
>
>
> Ad!thya於 2018年10月13日星期六 UTC+8下午11時40分03秒寫道：
>>
>> So I made a new folder in my server, cd'ed into it and synced a project, 
>> but unfortunately I realized that due to some reason it was synced in my 
>> home folder which has subdirs containing other roms and some other files 
>> which I'd like to keep. So how can I delete the entire synced project or 
>> move it to the subdir? Thanks in advance.
>> P.S: Wish there was a 'repo delete' feature which could do this :D
>>
>
> rm -rf (dir_name) 
>

-- 
-- 
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: Build android Oreo Code

[Glenn Kasten]

On Linux, build/envsetup.sh is a symlink to make/envsetup.sh so you can 
still use:
   . build/envsetup.sh

Are you sure you are in the top directory of your sandbox when you issued 
the ". build/envsetup.sh" ?

"lunch 39" might not be a valid lunch target.  Try using another lunch 
target name such as
"lunch aosp_arm-eng" etc.


On Wednesday, September 19, 2018 at 8:21:53 AM UTC-7, ashok reddy reddy 
wrote:
>
> I am trying to build android O code. Looks like in O some folder structure 
> is modified ie envsetup.sh is moved form build/envsetup.sh to 
> build/make/envsetup.sh.
>
> Lunch command is failing for me.
>
>
> *. build/make/envsetup.sh *
> including device/generic/car/vendorsetup.sh
> including device/generic/mini-emulator-arm64/vendorsetup.sh
> including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
> including device/generic/mini-emulator-x86_64/vendorsetup.sh
> including device/generic/mini-emulator-x86/vendorsetup.sh
> including device/generic/uml/vendorsetup.sh
> including device/qcom/common/vendorsetup.sh
> including sdk/bash_completion/adb.bash
>
>
> *lunch 39*
> cat: /build/envsetup.sh: No such file or directory
> cat: /build/envsetup.sh: No such file or directory
> make: build/core/config.mk: No such file or directory
> make: *** No rule to make target `build/core/config.mk'.  Stop.
>
> anyone build android O code?...
>
>
> Please let me know the steps to build.
>
>
>

-- 
-- 
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: Can I build android with GCC?

[Glenn Kasten]

See https://source.android.com/setup/build/requirements#toolchain

On Thursday, September 13, 2018 at 8:54:40 PM UTC-7, bx L wrote:
>
> Hello everyone,
>  I'm building Android 8.0. By default, it uses the clang toolchain. 
> Can I switch it to gcc toolchain, or use my own toolchain instead of the 
> prebuilt one?
>  Thanks!
>

-- 
-- 
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: Newbies android kernel development

[Glenn Kasten]

Start here, and the other tabs on same page:
https://source.android.com/setup/

On Thursday, August 16, 2018 at 7:53:04 AM UTC-7, yash omer wrote:
>
> Hello everyone,
>
> I have been doing linux kernel development for a while ago.
>
> And I am new to Android Kernel development . Can anyone help me guide how 
> to get started after setting up development environment from Google AOSP 
> website.
>
> My host platform is MacOS High Sierra and and how to compile and build 
> kernel on qemu.
> If anyonee can help me will be great 
>
> Thanks.
>

-- 
-- 
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: jack server out of memory error

[Glenn Kasten]

See https://source.android.com/setup/build/requirements#hardware-requirements
The RAM/swap listed there is the bare minimum.  I recommend even more.

On Tuesday, May 15, 2018 at 8:23:55 AM UTC-7, Yogi nit wrote:
>
> Well I have been compiling roms on 4gb system with 8gb swap. 
> I also had problem with jack. 
> So before compiling do this 
> As you said you have decreased service to 1, so it's fine. 
> then 
> # Stop the jack server if running 
> jack-admin stop-server 
> # If you are starting jack manually then 
>
> JACK_SERVER_VM_ARGUMENTS="-Xmx2g -Dfile.encoding=UTF-8 
> -XX:+TieredCompilation" /path/to/jack-admin start-server 
>
>
> #If you use the jack server in the android tree then 
>
> export ANDROID_JACK_VM_ARGS="-Xmx2g -Dfile.encoding=UTF-8 
> -XX:+TieredCompilation 
>
> If this doesn't work change the -Xmx2g to -Xmx4g, increase it if it 
> doesn't work

-- 
-- 
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: How To Get The Logs Of ROM Building Process To Get Help From Community

[Glenn Kasten]

When you do the repo sync, redirect stdout and stderr and then grep for 
errors to make sure you got the full source code:
   repo sync [other options] >& sync.log
Likewise when you do the build:
   make [other options] >& build.log
Examine the build log for errors. Don't share the full logs
by either attaching them or including inline,
they are usually far too long.  Just include the relevant
error lines and enough context to be able to understand.

On Sunday, April 8, 2018 at 12:43:21 PM UTC-7, Srinivasa Raju Mudunuri 
wrote:
>
> Hello,
>
> I'm new to Android ROM development, after going through few tutorials over 
> XDA & other sites and after watching some YouTube videos on how to build 
> Android ROM from source, I tried building a ROM from its sources. But I 
> encountered errors & my attempts were failed in building the ROM from its 
> sources. I tried to get help from some online groups about the error by 
> showing them the last few lines that I could copy from the SSH session, but 
> they said they need more logs(build logs & source logs), but being a 
> completely new to Android ROM development I don't know where do those logs 
> get saved when building Android ROMs from sources. Do the logs(output) of 
> Android ROM building process get saved by default? or Do we need to pass 
> some special parameters to the build process starting commands?. Can any 
> one shed some light for me on this??.
>
> Regards. 
>

-- 
-- 
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: lunch aosp_car_emu_x86

[Glenn Kasten]

According to https://source.android.com/setup/building#choose-a-target
you can use the command "lunch" with no parameters to see a list of 
AOSP-supported targets.
Can you confirm that your target is supported by AOSP?



On Wednesday, January 31, 2018 at 8:25:14 AM UTC-8, Henri Hildebrand wrote:
>
> Hello,
>
> I try to build the Android Automotive emulator *aosp_car_emu_x86*, but 
> when I enter lunch combo I get the message:
>
> *build/core/product_config.mk:227 : *** Can 
> not locate config makefile for product "aosp_car_emu_x86".  Stop.*
>
> I use the branch 'android-8.1.0_r9'. 
> Is the emulator not available or what can I do to build this?
>
> Thanks!
>

-- 
-- 
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: Android 8.1.0 Oreo MR1 Released

[Glenn Kasten]

Thank you for your criticism. I'm looking for someone from Treble team to 
respond,
however it may be a few days due to the holidays.

On Thursday, January 4, 2018 at 9:22:39 AM UTC-8, Chih-Wei Huang wrote:
>
>
>
> Xin Li於 2018年1月3日星期三 UTC+8上午10時15分54秒寫道：
>>
>> Hi all,
>>
>> Android 8.1.0 Oreo MR1 source code is now available.  The following 
>> builds, tags, and devices are supported:
>>
>>  - OPM1.171019.012, android-8.1.0_r3, Pixel XL (marlin), Pixel (sailfish)
>>  - OPM1.171019.013, android-8.1.0_r4, Pixel 2 XL (taimen), Pixel 2 
>> (walleye)
>>  - OPM1.171019.014, android-8.1.0_r5, Pixel 2 XL (taimen), Pixel 2 
>> (walleye), Pixel XL (marlin), Pixel (sailfish)
>>  - OPM1.171019.015, android-8.1.0_r6, Pixel C (dragon)
>>  - OPM3.171019.013, android-8.1.0_r7, Nexus 5X (bullhead), Nexus 6P 
>> (angler)
>>
>
>
> OOPS!
> I just praised you released ONE branch for all your devices in 8.1.
> But now you broke it again. What happened?
>
> If you can't build all your devices images from one branch,
> that means your Treble Project would finally failed.
> The Treble Project requires all compatible devices could be updated the 
> Android OS framework only.
> That implies one OS framework image (built from one branch of course) 
> could be used for all Treble compatible devices.
> So if even Google can't build one image (from one branch) for all of your 
> devices,
> how could you expect Treble Project to work?
>
>

-- 
-- 
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] No response after “lunch" command

[Glenn Kasten]

Sorry to hear about that.  4G is not nearly enough RAM to be able to build 
successfully.  You need much much more, as much as you can possibly get.

On Thursday, December 21, 2017 at 3:55:27 PM UTC-8, Peter Warrington wrote:
>
> Thank you for all your help and good luck with improving finder! With 
> regards to memory, I have a measly 4GB of ram so that is probally slowing 
> finder down and I do expect it to be slow (I do plan on upgrading in case 
> you are wondering). However, I do not believe what I am experiencing is the 
> same as what Alessandro is experiencing. Again, Thanks for all your help!
>
> On Thursday, December 21, 2017 at 8:14:39 PM UTC, Colin Cross wrote:
>>
>> Yeah, this is showing very slow lstat calls:
>> [pid  4007] <... lstat resumed> {st_mode=S_IFDIR|0777, st_size=4096, 
>> ...}) = 0 <0.020417>
>> vs. mine:
>> [pid 219359] <... lstat resumed> {st_mode=S_IFREG|0640, st_size=323161, 
>> ...}) = 0 <0.46>
>>
>> I don't know why yours would be so much slower, maybe just round trip 
>> latency to the external drive and not enough memory to keep them all in 
>> the inode cache?
>>
>> We can improve finder to drastically reduce the number of lstat calls, 
>> but ninja is going to have to stat most of the files to determine what 
>> needs building so I don't know how much improvement you will see.
>>
>>
>> On Thu, Dec 21, 2017 at 11:56 AM, Peter Warrington  
>> wrote:
>>
>>> Sorry about that. Is this attached strace any better?
>>>
>>> On Thursday, December 21, 2017 at 7:36:22 PM UTC, Colin Cross wrote:

 I don't see the data I'd expect with -T, it should have a time in angle 
 brackets after each finished syscall:
 [pid 219359] <... lstat resumed> {st_mode=S_IFREG|0640, st_size=323161, 
 ...}) = 0 <0.46>


 On Thu, Dec 21, 2017 at 3:05 AM, Peter Warrington  
 wrote:

> Attached is a much longer strace with the -T option used.
>
> On Wednesday, December 20, 2017 at 11:16:53 PM UTC, Colin Cross wrote:
>>
>> The results of the finder are cached in out/.module_paths/files.db, 
>> so once the command has completed successfully once the next runs will 
>> be 
>> much faster.  You could try wiping that file to reproduce it again, or 
>> run 
>> with a different value for OUT_DIR (OUT_DIR=out2 lunch ...).
>>
>> On Wed, Dec 20, 2017 at 1:58 PM, Peter Warrington <
>> sothis...@gmail.com> wrote:
>>
>>> Hello, the command has now started to work like normal after leaving 
>>> it for a while, so my problem might not be the same as Alessandro's. 
>>> Unfortunately, I cannot upload a bigger stack trace until tomorrow 
>>> because 
>>> of the time in my timezone. Sorry!
>>>
>>> On Wednesday, December 20, 2017 at 9:48:34 PM UTC, Colin Cross wrote:

 Can you attach a longer strace with -T ?

 On Wed, Dec 20, 2017 at 1:28 PM, Peter Warrington <
 sothis...@gmail.com> wrote:

> Thank you! That is very interesting. In case it helps, I 
> benchmarked my external HDD and it has an average read rate of 92.0 
> MB/s 
> and an average access time of 16.37 msec. However, I didn't have any 
> trouble with this previously.
>
> On Wednesday, December 20, 2017 at 9:06:16 PM UTC, Colin Cross 
> wrote:
>>
>> Nothing looks wrong in that strace, it is making forward 
>> progress.  It needs to read every directory and stat every file in 
>> the 
>> tree, is your filesystem very slow for some reason?
>>
>> One difference I see between the old implementation using the 
>> find tool and the new implementation is that find seems to be able 
>> to 
>> avoiding calling stat on every directory entry, because the relevant 
>> information (whether the entry is a subdirectory or a file) is 
>> contained in 
>> the return from the getdents64 syscall.  The Go implementation is 
>> ignoring 
>> that information and has to call lstat to get it.
>>
>> On Wed, Dec 20, 2017 at 11:32 AM, Peter Warrington <
>> sothis...@gmail.com> wrote:
>>
>>> Attached is a partial strace.
>>>
>>> On Wednesday, December 20, 2017 at 7:06:31 PM UTC, Colin Cross 
>>> wrote:

 From the stack trace after ctrl-c, lunch will be waiting for 
 the child soong_ui process to complete.  An strace of that process 
 would be 
 interesting.

 On Mon, Dec 18, 2017 at 4:12 PM, Alessandro Brucato <
 ale13...@gmail.com> wrote:

> This is the output of strace attached to the process in which 
> I execute "lunch".
>
>
>
> 

[android-building] Re: Android building questions problems

[Glenn Kasten]

For the tablet porting questions, please ask at android-porting group 
instead of android-building.

For the minimum host configuration question, I suspect that 8 GB of RAM is 
insufficient.
https://source.android.com/setup/requirements
says minimum of 16 GB RAM for VMs, but I think that is also true for 
non-VMs.
I would recommend much more than 16 GB if you can get it. For example 64 GB 
is better.

On Wednesday, December 20, 2017 at 8:43:03 AM UTC-8, Louis Paquet wrote:
>
> Hi,
>
> I'm posting here because I have a few questions and some problems.
>
> Me and some friends a trying to create are own tablet and our android rom.
>
> So we wanted to try and play a bit with AOSP 7.1.1 to see what we can do 
> and start working on it, but we can't seem to build it, at first we got RAM 
> issues with a java error, we seem to have resolved this error but now when 
> we try to build we get subcommand failed. It sometimes fails at 1% or it 
> can also fail at 60%. I seem to have install all the necessary dependencies.
>
> We are working on linux mint, we are trying to build AOSP 7.1 with a Intel 
> Core i7-5600U 2.60GHz and 8GB of ram. We put AOSP on a external 1To drive 
> because we want to build a server to access it in remote.
>
> Here are some additional questions if someone can help
>
>
>- We will need a kernel for our tablet, what can we use do we have to 
>compile it with AOSP,  i've read a bit about kernels but didn't get to it.
>- Are there things we must do or mustn't do
>
> If you have any tips i'll take everything
>
> Thanks
>

-- 
-- 
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: Soong confusion

[Glenn Kasten]

Thank you for feedback and request for improving the documentation.

As I understand, the primary goals of the new build system were:
 - reliable incremental builds
 - module definitions less error-prone
 - build output more predictable across devices

Obviously these goals may result in an initial learning curve for porting,
but hopefully we can improve the documentation to overcome that hurdle. 

On Monday, December 11, 2017 at 12:13:43 PM UTC-8, Jeffrey Blattman wrote:
>
> I'm wondering if there's a guide, or something that describes the 8.0 
> build setup ... targeted at someone coming from a pre-8.0 source base. The 
> Soong FAQ here: 
> https://android.googlesource.com/platform/build/soong/
>
> has ONE question.
>
> As a side note ... if you are interested in making it easier for vendors 
> to get running with and upgrade their Android dists faster, introducing a 
> new, proprietary build system does not further that end.
>

-- 
-- 
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: GPL Projects for Android O MR1 Preview 2

[Glenn Kasten]

In order of stability: O MR1 Preview 1, O MR1 Preview 2, O MR1 8.1.0 
(final).
O MR1 Preview 1 and O MR1 Preview 2 have GPL sources only.
O MR1 8.1.0 (final) has full sources and is intended to be buildable.

On Saturday, December 9, 2017 at 9:19:04 AM UTC-8, Chih-Wei Huang wrote:
>
>
> Yesterday you released "Android 8.1.0 Oreo MR1" while 
> 
> now you released "Android O MR1 Preview 2" which
> is not a full platform? I'm confused.
>
> What's the different between "Android 8.1.0 Oreo MR1" 
> 
> and "Android O MR1 Preview 2"?
> Is this a preview of Android 8.2?
>
> Xin Li於 2017年12月7日星期四 UTC+8上午9時29分36秒寫道：
>>
>> Hi, all,
>>
>> Today, we pushed a small number of GPL projects for the O MR1 Preview 2. 
>> The tag is android-o-mr1-preview-2. This preview is not a full platform 
>> update and only for reference.
>>
>> We also pushed the kernel source for the following devices:
>>
>> Tag  | Branch
>>   | Project  | Device
>> android-o-mr1-preview-2_r0.1 | android-msm-angler-3.10-o-mr1-preview2
>>   | kernel/msm   | Nexus 6P
>> android-o-mr1-preview-2_r0.2 | android-msm-bullhead-3.10-o-mr1-preview2  
>>   | kernel/msm   | Nexus 5X
>> android-o-mr1-preview-2_r0.3 | android-tegra-dragon-3.18-o-mr1-preview2  
>>   | kernel/tegra | Pixel C
>> android-o-mr1-preview-2_r0.4 | android-msm-marlin-3.18-o-mr1-preview2
>>   | kernel/msm   | Pixel and Pixel XL
>> android-o-mr1-preview-2_r0.5 | android-msm-wahoo-4.4-o-mr1-preview2  
>>   | kernel/msm   | Pixel 2 and Pixel 2 XL
>> android-o-mr1-preview-2_r0.6 | 
>> android-easel-intel-linux-4.7-oreo-mr1-preview2 | kernel/arm64 | Pixel 2 
>> and Pixel 2 XL
>>
>>

-- 
-- 
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: Android 8.1 Developer Preview Source

[Glenn Kasten]

Thank you for calling this delay to our attention. 
I see that the sources for GPL projects in O MR1 Developer Preview 1 were 
recently pushed:
https://groups.google.com/forum/#!topic/android-building/vSybPC-T_3Q
I would expect a similar push is coming soon for O MR1 Developer Preview 2, 
but I don't have the schedule.
Note that the full sources (including non-GPL projects)
are typically pushed around the time of, or shortly after, the OTA for the 
final release.
Again I don't have the schedule for this.

On Saturday, December 2, 2017 at 12:15:12 PM UTC-8, Matthew Alex wrote:
>
> Hello,
>
> As of lately Google is not pushing Developer Preview source code, does 
> anyone have any insight why? Can we please have these published as per GPL 
> since they are being distributed as an actual release.
>
> Thanks,
>

-- 
-- 
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: Android 8.0.0 Oreo DR Released

[Glenn Kasten]

Sorry, but I am confused about what you are asking for.

Note that this thread is about DR which is not for Pixel. It is only for 
Pixel 2 and Pixel 2 XL.

Which part of the build-numbers page do you think is incorrect or 
incomplete?

On Friday, November 17, 2017 at 5:28:40 AM UTC-8, 薛秋实 wrote:
>
> What about Pixel? Could you please update the tags at
> https://source.android.com/source/build-numbers
>
> 在 2017年11月8日星期三 UTC+8上午3:36:14，Bill Yi写道：
>>
>> Android 8.0.0 Oreo DR EMR source code is now available. The following 
>> builds, tags, and devices are supported:
>> - OPD1.170816.025, android-8.0.0_r33, Pixel 2 XL, Pixel 2
>> - OPD3.170816.023, android-8.0.0_r34, Pixel 2 XL, Pixel 2
>>
>> The corresponding factory images, ota images, and proprietary binaries 
>> are available at
>> https://developers.google.com/android/images
>> https://developers.google.com/android/ota
>> https://developers.google.com/android/drivers
>>
>> We have pushed the corresponding kernel projects for the following 
>> devices:
>> tag project branch
>>device
>> android-8.0.0_r0.28 kernel/msm android-msm-wahoo-4.4-oreo-dr1 Pixel 2 XL, 
>> Pixel 2
>>
>> 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] Re: Android 8.0.0 Oreo DR Released

[Glenn Kasten]

The DR variant is targeted to Pixel 2 XL (taimen) and Pixel 2 (walleye) 
only;
for all other devices you can use the non-DR variant.
The only reliable way I know of to get an exact list of differences is to 
do diff for each project.
For the first release of a new device, it is not always possible to align 
the release dates
of new devices and updates to existing device, thus there are differences.
Usually for subsequent update releases, the same branch is used.
This is not a new thing in O; see for example my 11/7/15 answer to 
vishalm's question at 
https://groups.google.com/forum/#!topic/android-building/KuVIYWOcXMo

On Thursday, November 9, 2017 at 7:03:29 AM UTC-8, Chih-Wei Huang wrote:
>
>
> Glenn Kasten於 2017年11月7日星期二 UTC+8下午11時59分39秒寫道：
>>
>> A release targeted to Pixel 2 XL (taimen) and Pixel 2 (walleye) 
>>
>
> What are the exact differences between DR and non-DR branches?
> It's very confusing.
>
> More precisely, why couldn't you build all images
> from the same branch?
> Shouldn't there just one release for Oreo?
>
> Since you released so many branches,
> for vendors who want to ship Oreo,
> which branch should they choose?
> Why?
>
>  
>
>> On Tuesday, November 7, 2017 at 7:57:48 AM UTC-8, Guoyin Chen wrote:
>>>
>>> What the DR means here?
>>>
>>> On Tuesday, November 7, 2017 at 9:00:52 AM UTC+8, Bill Yi wrote:
>>>>
>>>> Android 8.0.0 Oreo DR source code is now available. The following 
>>>> builds, tags, and devices are supported:
>>>> - OPD1.170816.018, android-8.0.0_r25, Pixel 2
>>>> - OPD2.170816.015, android-8.0.0_r26, Pixel 2
>>>> - OPD3.170816.016, android-8.0.0_r27, Pixel 2
>>>>
>>>> The corresponding factory images, ota images, and proprietary binaries 
>>>> are available at
>>>> https://developers.google.com/android/images
>>>> https://developers.google.com/android/ota
>>>> https://developers.google.com/android/drivers
>>>>
>>>> We have pushed the corresponding kernel projects for the following 
>>>> devices:
>>>> tag project branch 
>>>>   device
>>>> android-8.0.0_r0.22 kernel/msm android-msm-wahoo-4.4-oreo-dr1 Pixel 2
>>>>
>>>> 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] Re: Android 8.0.0 Oreo DR Released

[Glenn Kasten]

A release targeted to Pixel 2 XL (taimen) and Pixel 2 (walleye) 

On Tuesday, November 7, 2017 at 7:57:48 AM UTC-8, Guoyin Chen wrote:
>
> What the DR means here?
>
> On Tuesday, November 7, 2017 at 9:00:52 AM UTC+8, Bill Yi wrote:
>>
>> Android 8.0.0 Oreo DR source code is now available. The following builds, 
>> tags, and devices are supported:
>> - OPD1.170816.018, android-8.0.0_r25, Pixel 2
>> - OPD2.170816.015, android-8.0.0_r26, Pixel 2
>> - OPD3.170816.016, android-8.0.0_r27, Pixel 2
>>
>> The corresponding factory images, ota images, and proprietary binaries 
>> are available at
>> https://developers.google.com/android/images
>> https://developers.google.com/android/ota
>> https://developers.google.com/android/drivers
>>
>> We have pushed the corresponding kernel projects for the following 
>> devices:
>> tag project branch   
>> device
>> android-8.0.0_r0.22 kernel/msm android-msm-wahoo-4.4-oreo-dr1 Pixel 2
>>
>> 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] Re: porting Android TV on our own hardware

[Glenn Kasten]

Sorry this thread slipped through moderation. It is off-topic for 
android-building, and should have been posted at android-porting.
Please post follow-ups at android-porting instead of here. Thank you

On Tuesday, October 17, 2017 at 8:57:25 AM UTC-7, Tomasz Witke wrote:
>
> This is my repo: https://github.com/kyvaith/AndroidTV-AOSP
>
> W dniu wtorek, 17 października 2017 01:07:21 UTC+2 użytkownik Nagendra Rao 
> Jogi napisał:
>>
>> Hi Team,
>> we are developing a device in which we are planning to implement Android 
>> TV as operating systems for it with our own ARM hardware/processor.
>> we were able to find details about Android, however since we are looking 
>> for Android TV, we are wondering how and where to get more information on 
>> build and deployment process, licensing. 
>>
>> Appreciate it.
>>
>> Regards
>> Nagen
>>
>

-- 
-- 
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] service announcement for android-building

[Glenn Kasten]

android-building is a moderated discussion group.
Too often posts are rejected because they are off-topic.
Please take a moment to review the posting guidelines in the welcome 
message at top of group 
.
This will save grief for both you and the volunteer moderators.
Thank you!

-- 
-- 
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: Android 8.0.0 Oreo Released

[Glenn Kasten]

See https://developer.android.com/about/versions/o/download.html

On Monday, August 21, 2017 at 7:30:38 PM UTC-7, PeterK wrote:
>
> Hi,
>
> Will device binaries be released for these builds?
>
> Thanks, Pete.
>
> On Tuesday, 22 August 2017 11:09:11 UTC+10, Bill Yi wrote:
>>
>> Hi all,
>>
>> Android 8.0.0 Oreo source code is now available on the oreo-release 
>> branch. The following builds, tags, and devices are supported:
>> - OPR6.170623.010, android-8.0.0_r1, Pixel C (ryu)
>> - OPR6.170623.011, android-8.0.0_r2, Pixel XL (marlin) and Pixel 
>> (sailfish)
>> - OPR6.170623.012, android-8.0.0_r3, Pixel XL (marlin) and Pixel 
>> (sailfish)
>> - OPR6.170623.013, android-8.0.0_r4, Nexus 5X (bullhead), Nexus 6P 
>> (angler)
>>
>> We will push a reference oreo-dev branch. We'll also merge Oreo into AOSP 
>> master. I'll update this post when each of these become available.
>>
>> Thanks! Enj*O*y!
>>
>> 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] Re: Problem when building Android O Preview 3

[Glenn Kasten]

As mentioned by PeterK on July 11, android-o-preview-3 is not a full 
release and is not buildable. 
>From the announcement "This preview is not a full platform update and only 
for reference." 
GPL projects for Android O Preview 3 
https://groups.google.com/forum/#!msg/android-building/SIFVGg5z9BQ/U0PuOknZBQAJ



On Saturday, August 5, 2017 at 12:40:02 PM UTC-7, Ryan Hu wrote:
>
> Did U fix this issue?
> I meet same problem...
>
> 在 2017年7月12日星期三 UTC+8上午2:41:06，Larry Tsai写道：
>>
>> Hi,
>>
>> I am trying to build android-o-preview-3 for Nexus Player, but it fails 
>> at the very beginning while loading Android.bp of each module.
>>
>> The building log shows two errors:
>> error: frameworks/rs/cpu_ref/Android.bp:1:1: "libRSCpuRef" depends on 
>> undefined module "libblas"
>> error: frameworks/base/media/jni/Android.bp:1:1: "libmedia_jni" depends 
>> on undefined module "libexif"
>>
>> My building sequences follows the instruction at:
>> https://source.android.com/source/building
>>
>> It works on AOSP KK/L/M/N, but now it fails at O preview. Here is the 
>> whole log:
>>
>> 
>> PLATFORM_VERSION_CODENAME=O
>> PLATFORM_VERSION=O
>> TARGET_PRODUCT=aosp_fugu
>> TARGET_BUILD_VARIANT=userdebug
>> TARGET_BUILD_TYPE=release
>> TARGET_ARCH=x86
>> TARGET_ARCH_VARIANT=silvermont
>> HOST_ARCH=x86_64
>> HOST_2ND_ARCH=x86
>> HOST_OS=linux
>> HOST_OS_EXTRA=Linux-4.1.4-040104-generic-x86_64-with-Ubuntu-14.04-trusty
>> HOST_CROSS_OS=windows
>> HOST_CROSS_ARCH=x86
>> HOST_CROSS_2ND_ARCH=x86_64
>> HOST_BUILD_TYPE=release
>> BUILD_ID=NYC
>> OUT_DIR=out
>> 
>> [38/38] bootstrap out/soong/.minibootstrap/build.ninja.in
>> [1/2] out/soong/.bootstrap/bin/minibp out/soong/.minibootstrap/
>> build.ninja.in
>> [4/4] cp out/soong/.bootstrap/bin/bpglob
>> [496/497] glob vendor/*/*/Android.bp
>> [45/46] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
>> FAILED: out/soong/build.ninja
>> out/soong/.bootstrap/bin/soong_build  -t -b out/soong -d 
>> out/soong/build.ninja.d -o out/soong/build.ninja Android.bp
>> error: frameworks/base/media/jni/Android.bp:1:1: "libmedia_jni" depends 
>> on undefined module "libexif"
>> [46/46] soong_build docs out/soong/.bootstrap/docs/soong_build.html
>> FAILED: out/soong/.bootstrap/docs/soong_build.html
>> out/soong/.bootstrap/bin/soong_build  -t -b out/soong --docs 
>> out/soong/.bootstrap/docs/soong_build.html ./Android.bp
>> error: frameworks/rs/cpu_ref/Android.bp:1:1: "libRSCpuRef" depends on 
>> undefined module "libblas"
>> error: frameworks/base/media/jni/Android.bp:1:1: "libmedia_jni" depends 
>> on undefined module "libexif"
>> ninja: build stopped: subcommand failed.
>> 00:15:47 soong failed with: exit status 1
>> make: *** [run_soong_ui] Error 1
>>
>>
>> Am I missed some new sequence introduced by new build system blueprint?
>>
>>
>> Best Regards,
>> Larry
>>
>

-- 
-- 
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: Nexus 5X Paranoid Android "make otapackage -j6" Fails - Ninja Error

[Glenn Kasten]

Sorry, but this post is off-topic for the android-building discussion group.
It accidentally slipped through moderation and so no further replies will 
be permitted.
android-building is for technical discussion of building the AOSP upstream 
distribution
for AOSP-supported build targets from the AOSP source code without any 
modifications.

On Saturday, July 29, 2017 at 4:38:12 PM UTC-7, Nate Robbins wrote:
>
> Hi! So I'm trying to build Paranoid Android from source on my Linux PC. I 
> had ran the rom-build.sh or whatever that script was called, which is a 
> script made by the PA team to easily run all the lunch, make commands etc 
> and it completed succesfully. I flashed the images but they did not boot 
> properly, which might have been my USBs error. I then wanted to try a .zip 
> file, so I ran make otapackage -j6 and I got this error: (It's not full log 
> just last 50 or so lines before it crashed)
>
>  system 
>
>
> creating system.img...
> BuildImage: in_dir = /tmp/targetfiles-dUtsy7/system, out_file = /tmp/
> system-zSAxhf.img
> fs type is not ext4
> Running:  mkuserimg.sh -s /tmp/targetfiles-dUtsy7/system /tmp/system-
> zSAxhf.img ext4 system 3170938880 -T 1230786000 -C /tmp/targetfiles-dUtsy7
> /META/filesystem_config.txt -B /tmp/system-blocklist-WBNwik.map -L system 
> /tmp/targetfiles-dUtsy7/META/file_contexts.bin
> make_ext4fs -s -T 1230786000 -S /tmp/targetfiles-dUtsy7/META/file_contexts
> .bin -C /tmp/targetfiles-dUtsy7/META/filesystem_config.txt -B /tmp/system-
> blocklist-WBNwik.map -L system -l 3170938880 -a system /tmp/system-zSAxhf.img 
> /tmp/targetfiles-dUtsy7/system
> error: file_write: incomplete write
> loaded 2283 fs_config entries
> Creating filesystem with parameters:
>Size: 3170938880
>Block size: 4096
>Blocks per group: 32768
>Inodes per group: 8080
>Inode size: 256
>Journal blocks: 12096
>Label: system
>Blocks: 774155
>Block groups: 24
>Reserved block group size: 191
> Created filesystem with 2293/193920 inodes and 307286/774155 blocks
> Running ['mkuserimg.sh', '-s', '/tmp/targetfiles-dUtsy7/system', 
> '/tmp/system-zSAxhf.img', 'ext4', 'system', '3170938880', '-T', 
> '1230786000', '-C', '/tmp/targetfiles-dUtsy7/META/filesystem_config.txt', 
> '-B', '/tmp/system-blocklist-WBNwik.map', '-L', 'system', 
> '/tmp/targetfiles-dUtsy7/META/file_contexts.bin'] command, exit code = 0
> build_verity_tree -A 
> aee087a5be3b982978c923f566a94613496b417f2af592639bc80d141e34dfe7 /tmp/
> system-zSAxhf.img /tmp/tmpIyC9ty_verity_images/verity.img
> Could not build verity tree! Error: failed to write 
> '/tmp/tmpIyC9ty_verity_images/verity.img'
> a39ced07ca3acc2fb957f44b62a0bfa80895336bbe3fa59d2f3ed3b668c6a40c 
> aee087a5be3b982978c923f566a94613496b417f2af592639bc80d141e34dfe7
> Error: making verity enabled image failed
> Traceback (most recent call last):
>  File "./build/tools/releasetools/add_img_to_target_files", line 471, in 
> 
>main(sys.argv[1:])
>  File "./build/tools/releasetools/add_img_to_target_files", line 465, in 
> main
>AddImagesToTargetFiles(args[0])
>  File "./build/tools/releasetools/add_img_to_target_files", line 384, in 
> AddImagesToTargetFiles
>boot_img=boot_image)
>  File "./build/tools/releasetools/add_img_to_target_files", line 109, in 
> AddSystem
>block_list=block_list)
>  File "./build/tools/releasetools/add_img_to_target_files", line 118, in 
> BuildSystem
>return CreateImage(input_dir, info_dict, "system", block_list=
> block_list)
>  File "./build/tools/releasetools/add_img_to_target_files", line 211, in 
> CreateImage
>assert succ, "build " + what + ".img image failed"
> AssertionError: build system.img image failed
> ninja: build stopped: subcommand failed.
> build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
> make: *** [ninja_wrapper] Error 1
>
>  make failed to build some targets (18:39 (mm:ss)) 
>
>
> Does anybody know how to fix this? Thanks :)
>

-- 
-- 
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: Android 8.0 source code build error “xxx” depends on undefined module “libxxx”

[Glenn Kasten]

android-o-preview-2 is not a full release and is not buildable. 
>From the announcement "This preview is not a full platform update and only 
for reference."
See https://groups.google.com/forum/#!topic/android-building/V-1RR6QAYMs

On Thursday, July 20, 2017 at 1:53:52 AM UTC-7, tang jie wrote:
>
> I have downloaded the Android O preview version with the following steps:
>
>1. 
>
>repo init -u https://android.googlesource.com/platform/manifest -b 
>refs/heads/android-o-preview-2
>2. 
>
>repo sync 
>
> And then,start to build the source code:
>
> source build/envsetup.sh 
>
>1. lunch 1
>2. make -j8
>
> When the building is running ,after some seconds, this build error 
> happened:
>
>
> $make
> 
> PLATFORM_VERSION_CODENAME=O
> PLATFORM_VERSION=O
> TARGET_PRODUCT=aosp_arm
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a
> TARGET_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.4.0-77-generic-x86_64-with-Ubuntu-16.04-xenial
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=NYC
> OUT_DIR=out
> 
> [2/2] bootstrap out/soong/.minibootstrap/build.ninja.in
> [1/2] out/soong/.bootstrap/bin/minibp out/soong/.minibootstrap/
> build.ninja.in
> ninja: no work to do.
> [1/2] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> FAILED: out/soong/build.ninja 
> out/soong/.bootstrap/bin/soong_build  -t -b out/soong -d 
> out/soong/build.ninja.d -o out/soong/build.ninja Android.bp
> error: frameworks/rs/cpu_ref/Android.bp:1:1: "libRSCpuRef" depends on 
> undefined module "libblas"
> error: frameworks/base/media/jni/Android.bp:1:1: "libmedia_jni" depends on 
> undefined module "libexif"
> [2/2] soong_build docs out/soong/.bootstrap/docs/soong_build.html
> FAILED: out/soong/.bootstrap/docs/soong_build.html 
> out/soong/.bootstrap/bin/soong_build  -t -b out/soong --docs 
> out/soong/.bootstrap/docs/soong_build.html ./Android.bp
> error: frameworks/base/media/jni/Android.bp:1:1: "libmedia_jni" depends on 
> undefined module "libexif"
> error: frameworks/rs/cpu_ref/Android.bp:1:1: "libRSCpuRef" depends on 
> undefined module "libblas"
> ninja: build stopped: subcommand failed.
> 14:57:38 soong failed with: exit status 1
> build/core/main.mk:21: recipe for target 'run_soong_ui' failed
> make: *** [run_soong_ui] Error 1
>
>  make failed to build some targets (19 seconds) 
>
>
> I don't know why, I tried to fix the dependency for system libs, but it 
> does not work yet.
>

-- 
-- 
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: Build targets

[Glenn Kasten]

For phones and tablets see
https://source.android.com/source/build-numbers#source-code-tags-and-builds

For reference boards, see
https://source.android.com/source/devices

For kernels, see
https://source.android.com/source/building-kernels

On Monday, July 17, 2017 at 7:33:11 AM UTC-7, Yile Ku wrote:
>
> What build targets are supported by the AOSP upstream distribution?  Which 
> is the most recently released phone that is supported by the AOSP upstream 
> distribution? 
>
> y-
>

-- 
-- 
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 7.1.1 Speech Recognizer Availability

[Glenn Kasten]

The closest thing to "official" documentation for AOSP 
is https://source.android.com/
But that only documents what is in AOSP, not what is not in AOSP. :-)

There is also the AOSP API documentation:
https://developer.android.com/reference/android/speech/SpeechRecognizer.html

And the source code for the AOSP API:
https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/speech/SpeechRecognizer.java

Note that the AOSP API is not the same as a service that implements the 
guts behind the API.

There are also proprietary (non-AOSP) APIs for speech recognition
available from Google and other parties, but I will not describe those here
since proprietary services are off-topic for the android-building 
discussion group.
A web search should locate those.

On Wednesday, June 14, 2017 at 7:23:32 AM UTC-7, aosp.build...@gmail.com 
wrote:
>
> Hi all,  
>
>
> I've built the AOSP 7.1.1 and I've noticed in the emulator that in the 
> Language and Input menu, on the Speech part only the Text to Speech item is 
> available. 
>
>
> This makes me think that the speech recognizer is not present in AOSP. 
>
>
> Can anyone confirm my hypothesis ? 
>
>
> Is there an official Google documentation related to this topic ? (I would 
> prefer the official documentation or an official answer as it is easier to 
> refer to)
>
>
> Thank you
>
>
> Florin
>

-- 
-- 
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: Building AOSP 6.0.0 on Ubuntu 16.04 LTS keeps failing

[Glenn Kasten]

As you mentioned the minimum requirements at 
https://source.android.com/source/requirements#hardware-requirements
do recommend at least 16 6GB of RAM/swap.
That said, the more real RAM you have the better,
so using 1GB RAM and the rest swap is unlikely to be productive.

Also your 100 GB HDD is small.

Overall, I think your machine is underpowered for this.


On Wednesday, May 10, 2017 at 10:53:08 AM UTC-7, Ali Reza Barkhordari wrote:
>
> I'm using a copy of Ubuntu 16.04 LTS on a VPS having the following spec. 
> 1GB RAM / 100GB HDD. Official docs say it's recommended for the machine to 
> have 16GB RAM. I worked around this issue by creating a 15GB swap file.
>
> I tried many times to build, but every time it failed. Seems it have 
> trouble with Jack. The most recent log file (i.e. stdout) follows.
>
> including ./system/security/softkeymaster/Android.mk ...
>>
>> including ./system/vold/Android.mk ...
>>
>> including ./tools/external/fat32lib/Android.mk ...
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/with-local/classes.dex
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/libphonenumber-platform_intermediates/classes.jack
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/with-local/classes.dex
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/conscrypt_intermediates/with-local/classes.dex
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/with-local/classes.dex
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/with-local/classes.dex
>>
>> Building with Jack: 
>>> out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex
>>
>>
>>> May 08, 2017 8:10:53 PM 
>>> com.android.sched.scheduler.MultiWorkersScheduleInstance$LongRunning dump
>>
>> SEVERE: Timeout detected during run:
>>
>> May 08, 2017 8:11:49 PM 
>>> com.android.sched.scheduler.MultiWorkersScheduleInstance$LongRunning dump
>>
>> SEVERE:   No thread. Wrong detection. Try to increase timeout with 
>>> 'sched.runner.thread.detector.long-running.timeout' property
>>
>> May 08, 2017 8:12:54 PM com.android.jack.CommandLine runJack
>>
>> SEVERE: Internal compiler error (version 1.1-mr2 'Brest' (175100 
>>> 000a2f91edbe638090dc577801ba49592229fd8b)):
>>
>> java.lang.AssertionError
>>
>> at 
>>> com.android.sched.scheduler.MultiWorkersScheduleInstance.process(MultiWorkersScheduleInstance.java:490)
>>
>> at com.android.jack.Jack.run(Jack.java:597)
>>
>> at com.android.jack.Jack.checkAndRun(Jack.java:367)
>>
>> at com.android.jack.CommandLine.runJack(CommandLine.java:66)
>>
>> at com.android.jack.Main.main(Main.java:73)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:606)
>>
>> at com.android.jack.launcher.Main.main(Main.java:94)
>>
>>
>>> java.lang.AssertionError
>>
>> at 
>>> com.android.sched.scheduler.MultiWorkersScheduleInstance.process(MultiWorkersScheduleInstance.java:490)
>>
>> at com.android.jack.Jack.run(Jack.java:597)
>>
>> at com.android.jack.Jack.checkAndRun(Jack.java:367)
>>
>> at com.android.jack.CommandLine.runJack(CommandLine.java:66)
>>
>> at com.android.jack.Main.main(Main.java:73)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:606)
>>
>> at com.android.jack.launcher.Main.main(Main.java:94)
>>
>>
>>> Internal compiler error (version 1.1-mr2 'Brest' (175100 
>>> 000a2f91edbe638090dc577801ba49592229fd8b)).
>>
>> Warning: This may have produced partial or corrupted output.
>>
>> build/core/java.mk:643: recipe for target 
>>> 'out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex'
>>>  
>>> failed
>>
>> make: *** 
>>> [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex]
>>>  
>>> Error 41
>>
>>
> How can I get the Jack to work or completely disable it?
>
> 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-buildin

[android-building] Re: pls help`vbox_x86 stuck at grub _ (virtualbox)

[Glenn Kasten]

Sorry, in that case this thread is off-topic for android-building.
android-building is for discussion of AOSP distribution for AOSP-supported 
build targets.

On Wednesday, April 19, 2017 at 3:02:33 PM UTC-7, alin silen wrote:
>
> thanks for your answer``
> but i m building androvm... and it doesn't support android x86`
>
>
>
> 在 2017年4月20日星期四 UTC+8上午1:38:27，Chih-Wei Huang写道：
>>
>>
>>
>> alin silen於 2017年4月15日星期六 UTC+8上午8時45分22秒寫道：
>>>
>>>
>>> here is how i built
>>>
>>> lunch vbox_x86-eng
>>> make -j8
>>> make android_disk_vdi
>>>
>>>
>>
>> I don't think anyone is maintaining the
>> vbox_x86 target of AOSP.
>>
>> If you want to run android on virtualbox,
>> see www.android-x86.org. 
>>
>

-- 
-- 
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: Android development tools

[Glenn Kasten]

There is goldfish kernel for emulation, see
https://source.android.com/source/building-kernels
and search for "goldfish".

On Thursday, April 13, 2017 at 10:51:43 AM UTC-7, Wiktoria Lewicka wrote:
>
> Hello! 
> I write simple Linux kernel modules and I want to test my modules in 
> Android. But I can't test it on physical hardware. Is impossible to build 
> virtual environment to test changed in Android system or kernel? 
> I will be very thankful for any answers.

-- 
-- 
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: syncing the source tree

[Glenn Kasten]

Can you please add the command you use to repo init and sync,
and a short excerpt of the most important part of the log of error messages.

On Friday, November 18, 2016 at 2:47:21 PM UTC-8, Daniel Carr wrote:
>
> Hi all,
>
> I have a local mirror of asop,
>
> trying re sync it: repo sync
> using https, http, or git timeout errors
> this has work before with no problems.
> no change to software or hardware
> opensuse 13.2  64 bit with no firewall  or proxy
>
> tried  other repos no problem except when they download from google source 
> site.
>
> 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.

[android-building] Re: Android 7.0 Nougat MR 0.5 released

[Glenn Kasten]

PeterK, thank you for reporting this problem. We are in process of fixing 
now.

On Wednesday, October 5, 2016 at 1:38:31 PM UTC-7, Xin Li wrote:
>
> Nougat MR 0.5 release source code is now available on the 
> nougat-mr0.5-release branch. The following builds, tags, and devices are 
> supported:
> - NBD90W, android-7.0.0_r12, Nexus 5X
> - NBD90X, android-7.0.0_r13, Nexus 6P
> - NBD90Z, android-7.0.0_r14, Nexus 6
>
> The corresponding factory images, OTA images and driver blobs are 
> available at:
>
>  https://developers.google.com/android/nexus/images
>  https://developers.google.com/android/nexus/ota
>  https://developers.google.com/android/nexus/drivers
>
> We have also pushed the corresponding kernel projects for the following 
> devices:
> tag  project   branch 
> device
> android-7.0.0_r0.22 kernel/msm android-msm-angler-3.10-nougat-mr0.5   
> Nexus 6P
> android-7.0.0_r0.23 kernel/msm android-msm-bullhead-3.10-nougat-mr0.5 
> Nexus 5X
> android-7.0.0_r0.24 kernel/msm android-msm-shamu-3.10-nougat-mr0.5   
>  Nexus 6
>

-- 
-- 
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: Which lunch combo should Nexus 5 config to assure it get the latest version from master branch?

[Glenn Kasten]

The most recent build of Nexus 5 according to 
https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
 
is:

M4B30X android-6.0.1_r72 Marshmallow Nexus 5
And see Bill Yi's post on Aug 25 "We have merged nougat into AOSP master."
at 
thread https://groups.google.com/forum/#!topic/android-building/qtO8b1efRjA

Thus, Nexus 5 is not supported on AOSP master. For Nexus 5, please use an 
earlier branch.


On Friday, October 28, 2016 at 7:43:31 PM UTC-7, 龚泽龙 wrote:
>
> I am working on Ubuntu 16.04 LTS and have a Nexus 5 with me.
>
> I followed the steps from the official android website.
>
> As for Nexus 5 I refer to https://developers.google.com/android/drivers.
>
> I wanna get the latest android version, so I chose the  Nexus 5 (GSM/LTE) 
> binaries for Android 6.0.1 (M4B30X).
>
> and when I lunch 
>
> ```
> gongzelong@gongzelong:~/OpenSource/Android$ lunch
>
> You're building on Linux
>
> Lunch menu... pick a combo:
>  1. aosp_arm-eng
>  2. aosp_arm64-eng
>  3. aosp_mips-eng
>  4. aosp_mips64-eng
>  5. aosp_x86-eng
>  6. aosp_x86_64-eng
>  7. full_fugu-userdebug
>  8. aosp_fugu-userdebug
>  9. mini_emulator_arm64-userdebug
>  10. m_e_arm-userdebug
>  11. m_e_mips64-eng
>  12. m_e_mips-userdebug
>  13. mini_emulator_x86_64-userdebug
>  14. mini_emulator_x86-userdebug
>  15. aosp_dragon-userdebug
>  16. aosp_dragon-eng
>  17. aosp_flounder-userdebug
>  18. aosp_angler-userdebug
>  19. aosp_bullhead-userdebug
>  20. hikey-userdebug
>  21. aosp_shamu-userdebug
>
> Which would you like? [aosp_arm-eng] aosp_hammerhead-userdebug
> build/core/product_config.mk:238: *** Can not locate config makefile for 
> product "aosp_hammerhead".  Stop.
>
> ** Don't have a product spec for: 'aosp_hammerhead'
> ** Do you have the right repo manifest?
>
> gongzelong@gongzelong:~/OpenSource/Android$ vi build/core/
> product_config.mk
> gongzelong@gongzelong:~/OpenSource/Android$ git branch
> fatal: Not a git repository (or any of the parent directories): .git
> gongzelong@gongzelong:~/OpenSource/Android$ lunch aosp_hammerhead-userdebug
> build/core/product_config.mk:238: *** Can not locate config makefile for 
> product "aosp_hammerhead".  Stop.
>
> ** Don't have a product spec for: 'aosp_hammerhead'
> ** Do you have the right repo manifest?
>
> ```
>
> So, which lunch combo is suitable for me to work on Nexus 5 and can get 
> the latest version?
>
> Or, am I got the wrong repo manifest? If yes, how to change it.
>
> Before I follow the steps shown below.
> https://source.android.com/source/building.html
>
 

-- 
-- 
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: Android Wear 6.0.1 Marshmallow MR1 Released

[Glenn Kasten]

This group android-building is for discussion of the AOSP open source 
distribution.
For other components, see the last section 
of https://source.android.com/compatibility/contact-us.html

On Saturday, September 17, 2016 at 12:14:04 PM UTC-7, appincloud hk wrote:
>
> Hi Bill,
> where is the android wear source code ? What is the latest release? How 
> can we download it? (not only the kernel, but the whole source code, like 
> 4.4w)
>
> On Thursday, September 1, 2016 at 2:44:59 AM UTC+8, Bill Yi wrote:
>>
>> We pushed the kernel project for the following devices:
>> tag projectbranch   
>>  device
>> android-wear-6.0.1_r0.41 kernel/msm 
>>  android-msm-anthias-3.10-marshmallow-mr1-wear-release anthias
>> android-wear-6.0.1_r0.42 kernel/msm 
>>  android-msm-wren-3.10-marshmallow-mr1-wear-release wren
>> android-wear-6.0.1_r0.44 kernel/x86 
>>  android-x86-glacier-3.10-marshmallow-mr1-wear-release glacier
>> android-wear-6.0.1_r0.47 kernel/msm 
>>  android-msm-sprat-3.10-marshmallow-mr1-wear-release sprat
>>
>> 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] Re: Baseband error when compiling Nougat for Shamu

[Glenn Kasten]

Which branch are you syncing? Sometimes master has temporary failures.
Also, search this group for previous postings about it.  Often to get radio 
working you need to also flash some proprietary vendor images,
and the earlier postings may explain what you need to do.

On Thursday, September 1, 2016 at 8:15:10 AM UTC-7, Robb B. wrote:
>
> If this has already been covered, apologies.  I am compiling from source, 
> and having 0 issues other than no baseband. I am not able to even flash a 
> supported radio.  It completely hoses, and will not allow any baseband to 
> be detected.  Is this why there are no OTAs being posted for Shamu?
>

-- 
-- 
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: Android 7.0 Nougat Released

[Glenn Kasten]

Oops, I just shot myself in the foot, I mean additional predictions beyond 
those above :-)

On Tuesday, August 23, 2016 at 6:01:06 PM UTC-7, Glenn Kasten wrote:
>
> Regarding the questions about other devices ... I don't speak for the AOSP 
> build and release team
> (I'm just one of the volunteer moderators of this group).
> But in my experience, the build and release team typically posts here only 
> when something is available,
> and does not usually make predictions or commitments about the future.
> Glenn
>
>
> On Tuesday, August 23, 2016 at 5:55:26 PM UTC-7, Sachin Sachi wrote:
>>
>> On Tuesday, August 23, 2016 at 9:46:52 PM UTC+5:30, Bill Yi wrote: 
>> > Hi all, 
>> > 
>> > I 
>> > Android 7.0 nougat source code is now available on the nougat-release 
>> branch.  The following builds, tags, and devices are supported: 
>> > - NRD90M, android-7.0.0_r1, Nexus 9 (volantis), Nexus Player (fugu), 
>> and Pixel C (ryu) 
>> > 
>> > 
>> > The corresponding factory images, ota images, and proprietary binaries 
>> are available at 
>> > https://developers.google.com/android/nexus/images 
>> > https://developers.google.com/android/nexus/ota 
>> > https://developers.google.com/android/nexus/drivers 
>> > 
>> > 
>> > Over the next few days, we'll merge nougat into AOSP master and push a 
>> reference nougat-dev branch. Corresponding kernel updates will also be 
>> posted within the next week.  I'll update this post when each of these 
>> become available. 
>> > 
>> > 
>> > Thanks! 
>> > 
>> > 
>> > bill 
>>
>>
>>
>> What about Android one [SPROUT] 
>> Thanks.
>
>

-- 
-- 
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: Android 7.0 Nougat Released

[Glenn Kasten]

Regarding the questions about other devices ... I don't speak for the AOSP 
build and release team
(I'm just one of the volunteer moderators of this group).
But in my experience, the build and release team typically posts here only 
when something is available,
and does not usually make predictions or commitments about the future.
Glenn


On Tuesday, August 23, 2016 at 5:55:26 PM UTC-7, Sachin Sachi wrote:
>
> On Tuesday, August 23, 2016 at 9:46:52 PM UTC+5:30, Bill Yi wrote: 
> > Hi all, 
> > 
> > I 
> > Android 7.0 nougat source code is now available on the nougat-release 
> branch.  The following builds, tags, and devices are supported: 
> > - NRD90M, android-7.0.0_r1, Nexus 9 (volantis), Nexus Player (fugu), and 
> Pixel C (ryu) 
> > 
> > 
> > The corresponding factory images, ota images, and proprietary binaries 
> are available at 
> > https://developers.google.com/android/nexus/images 
> > https://developers.google.com/android/nexus/ota 
> > https://developers.google.com/android/nexus/drivers 
> > 
> > 
> > Over the next few days, we'll merge nougat into AOSP master and push a 
> reference nougat-dev branch. Corresponding kernel updates will also be 
> posted within the next week.  I'll update this post when each of these 
> become available. 
> > 
> > 
> > Thanks! 
> > 
> > 
> > bill 
>
>
>
> What about Android one [SPROUT] 
> Thanks.

-- 
-- 
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: help with android N preview 3 wont boot on oneplus2

[Glenn Kasten]

 

Please see the second paragraph of

https://groups.google.com/forum/#!topic/android-building/cul3-5jfS9w

that starts "This preview is not ..."

On Sunday, June 19, 2016 at 11:59:14 AM UTC-7, Kar L wrote:
>
> i have compiled successfully android preview N 3 for oneplus2 device. The 
> rom boots but loops at "android" boot animation. 
> there is also no logcat available. 
> i tried building "eng" builds. 
> how can i get logs. 
> please help.

-- 
-- 
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: Small or corrupted system.img

[Glenn Kasten]

The smaller size could be partly explained by the lack of proprietary apps.
But since it didn't boot up, maybe there is a build problem that also 
contributse to the smaller size.

On Thursday, June 9, 2016 at 7:01:23 AM UTC-7, Pawel wrote:
>
> Hi,
>
> I've tried to build android-6.0.1_r45 for my Nexus 5X on Ubuntu 16.04. I 
> followed the instruction https://source.android.com/source/building.html 
> and also extracted both lge and qcom images into my source tree. It 
> successfully created bullhead image, however when I flash it device gets 
> stack on google screen. 
> I've realized that size of system.img is much smaller (792M) then original 
> one (1.8G). Is there any way to investigate it to check what when wrong?
>
>
>
>

-- 
-- 
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: Android N source code building error

[Glenn Kasten]

 

Please see the second paragraph of

https://groups.google.com/forum/#!topic/android-building/cul3-5jfS9w

that starts "This preview is not ..."

On Tuesday, June 7, 2016 at 7:50:32 AM UTC-7, tamil wrote:
>
> Hi all, 
>
> I am building the android N source code and getting this following 
> error. Please help to identify the issue and to resolve it. 
>
> [ 88% 40323/45738] Target system fs image: 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em.img 
> FAILED: /bin/bash -c "(mkdir -p 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/ 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates && 
> rm -rf 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"fs_type=ext4\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"system_size=2782920704\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"userdata_fs_type=f2fs\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"cache_fs_type=ext4\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"cache_size=268435456\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"extfs_sparse_flag=-s\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"squashfs_sparse_flag=-s\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo 
> \"selinux_fc=out/target/product/flounder/root/file_contexts.bin\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"boot_signer=false\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"verity=true\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo 
> \"verity_key=build/target/product/security/verity\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"verity_signer_cmd=verity_signer\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"verity_fec=true\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo 
> \"system_verity_block_device=/dev/block/platform/sdhci-tegra.3/by- 
> name/APP\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo 
> \"vendor_verity_block_device=/dev/block/platform/sdhci-tegra.3/by- 
> name/VNR\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (echo \"skip_fsck=true\" >>   
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt ) && (PATH=out/host/linux-x86/bin/:\$PATH 
> ./build/tools/releasetools/build_image.py 
> out/target/product/flounder/system 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em_image_info.txt 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em.img out/target/product/flounder/system || ( echo \"Out of space? the 
> tree size of out/target/product/flounder/system is (MB): \" 1>&2 ; du - 
> sm out/target/product/flounder/system 1>&2; if [ \"ext4\" == \"ext4\" ]; 
> then maxsize=2782920704; if [ \"\" == \"true\" ]; then 
> maxsize=\$((maxsize - 4096 * 4096)); fi; echo \"The max is \$(( maxsize 
> / 1048576 )) MB.\" 1>&2 ; else echo \"The max is \$(( 2782920704 / 
> 1048576 )) MB.\" 1>&2 ; fi; mkdir -p out/dist; cp 
> out/target/product/flounder/installed-files.txt out/dist/installed- 
> files-rescued.txt; exit 1 ) )" 
>
> error: failed to build 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em.img from out/target/product/flounder/system 
> Running:  mkuserimg.sh -s out/target/product/flounder/system 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em.img ext4 system 2739474432 -D out/target/product/flounder/system -L 
> system out/target/product/flounder/root/file_contexts.bin 
> make_ext4fs -s -T -1 -S 
> out/target/product/flounder/root/file_contexts.bin -L system -l 
> 2739474432 -a system 
> out/target/product/flounder/obj/PACKAGING/systemimage_intermediates/syst 
> em.img out/target/product/flounder/system 
> out/target/product/flounder/system 
> Creating filesystem with parameters: 
> Size: 2739474432 
> Block size: 4096 
> Blocks per group: 32768 
> Inodes per group: 7968 
> Inode size: 256 
> Journal blocks: 10450 
> Label: system 
> Blocks: 668817 
>  

[android-building] Re: Android build fail

[Glenn Kasten]

Please see the second paragraph of
https://groups.google.com/forum/#!topic/android-building/cul3-5jfS9w
that starts "This preview is not ..."

On Tuesday, June 7, 2016 at 7:50:04 AM UTC-7, Balder wrote:
>
> I try to build the N preview 2 master branch on Ubuntu 16.04.
> But I got error.
>
> my step:
> source ./build/envsetup.sh
> lunch aosp_arm-eng
> make -j8
>
> build/core/ninja.mk:159:recipe for target 'out/build-aosp_arm.ninja' failed
> make :***[out/build-aosp_arm.ninja] killed
>
> I don't understand why does not the 'out/build-aosp_arm.ninja' generate?
> Or I lost something for build.
>
>  
>

-- 
-- 
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: Eigen - Android iMX6 Boundary Devices unable to download

[Glenn Kasten]

If this is a generic fetch problem for all devices, android-building is the 
right group.
But if it is specific to iMX6, android-porting would be a better group to 
discuss it.

On Tuesday, May 31, 2016 at 7:42:37 AM UTC-7, Deepak Rao wrote:
>
> Hi All,
>
>
> I am trying to download "Eigen" for Android iMX6 Board (from Boundary 
> Devices). But, downloading is hanging even after 12 hours. This is third 
> time unsuccessful. 
>
>
> "Fetching projects:  98% (493/503)  Fetching project 
> platform/external/eigen" 
>
> Kindly, suggest, if you any idea how to resolve "eigen" downloading
>
> In Android.manifest.xml file :  
>
>
> https://github.com/boundarydevices/android-manifest/blob/boundary-imx-l5.1.1_2.1.0-ga/default.xml#L200
>
> https://github.com/boundarydevices/android-manifest/blob/boundary-imx-l5.1.1_2.1.0-ga/default.xml#L4
>
>
> Thanks in advance,
>
> Regards
> Deepak
>

-- 
-- 
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.