Re: [android-building] How to use build vars like PRODUCT_XXX in genrule cmd?

[Chih-Wei Huang]

I have the same question.
I'd like to use product variables like TARGET_PRODUCT in Android.bp.
I searched the whole AOSP tree but still can't find a way to do that.
Sigh,,, Is it possible?

DavidRobin於 2019年7月16日星期二 UTC+8下午11時13分22秒寫道：
>
> Thanks for your reply.
> Our purpose is to generate "License checking code" for specific product 
> build.
> So we have a shell script to generate the code based on the PRODUCT_XXX 
> properties.
>
> Are you implying that Android.bp should only be used in generic (product 
> independent) modules?
> And this kind of code should be put in device/product specific stuff and 
> use Android.mk to achieve the goal?
> (P.S. will Android.mk be kept or will Android.bp take over the whole 
> build?)
>
> On Tuesday, July 16, 2019 at 2:13:13 AM UTC+8, Dan Willemsen wrote:
>>
>> Those variables aren't exposed, partially because it becomes very 
>> difficult to understand which pieces of the system are then 
>> product-specific vs generic. Is there a reason why you wouldn't just read 
>> the runtime properties rather than trying to embed those values in code?
>>
>> - Dan
>>
>> On Mon, Jul 15, 2019 at 9:31 AM DavidRobin  wrote:
>>
>>> I saw that in external/libmojo/Android.bp there is an example to 
>>> generate header files for later build process.
>>>
>>> genrule {
>>> name: "libmojo_mojom_headers",
>>> cmd: "$(location mojom_source_generator_sh)" +
>>> "--mojom_bindings_generator=$(location 
>>> mojom_bindings_generator)" +
>>> "--package=external/libmojo" +
>>> "--output_dir=$(genDir)" +
>>> "--bytecode_path=$(genDir)" +
>>> "--typemap=$(location 
>>> gen/mojo/common/common_custom_types__type_mappings)" +
>>> "--generators=c++" +
>>> "--use_new_wrapper_types" +
>>> "$(in)",
>>>
>>> However, I cannot find how to use vars like $(PRODUCT_BRAND) 
>>> $(PRODUCT_MANUFACTURER) etc in this cmd line.
>>> Please help.
>>> 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/6a64020b-1413-4723-aabe-3d6ce27f3ae9%40googlegroups.com.

Re: [android-building] Re: Android Security Backport Released

[Chih-Wei Huang]

James Muir於 2019年11月18日星期一 UTC+8下午4時04分45秒寫道：
>
> > Please manage the thing right, Google! 
>
> I'm not sure if comments like that are helpful. 
>
> Maybe there is a valid  reason not to touch the SPL when google has not 
> published a device release from a given tag, or maybe it is just a 
> process issue (e.g. may be the release manager is in charge of changing 
> the SPL). 
>

What's the valid reason to keep it to a very old date?
That's inconceivable.

-- 
-- 
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/2854a15b-ef9d-4f20-971e-414a9123fc4f%40googlegroups.com.

Re: [android-building] Re: Android Security Backport Released

[Chih-Wei Huang]

James Muir於 2019年11月14日星期四 UTC+8下午4時56分59秒寫道：
>
> maybe I am missing something. 
>
> even if a tag is not device-specific, doesn't it make sense to update 
> the SPL? 
>
> e.g. if android-8.1.0_r70 has all the security patches applied from the 
> November 2019 (and earlier) security bulletin, why not update the 
> variable PLATFORM_SECURITY_PATCH? 
>
> Leaving it set to 2017-12-05 seems unnecessarily confusing. 
>


Yes. Totally agree.

If I update to android-8.1.0_r70, the users would think
this is a VERY OLD release which is not updated for
almost two years!

Even android-8.1.0_r65 has update to 2019-06-05,
why android-8.1.0_r70 became even older?

Please manage the thing right, Google!

-- 
-- 
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/043868b6-de10-49f5-aaf7-3b8ccfa00edd%40googlegroups.com.

[android-building] Re: Android Security Backport Released

[Chih-Wei Huang]

Could you explain why the PLATFORM_SECURITY_PATCH of android-8.1.0_r70 is 
still 2017-12-05?
That's very confusing!

lh@server2:~/cwhuang/oreo/build/make$ git diff android-8.1.0_r65 
android-8.1.0_r70 core/version_defaults.mk
diff --git a/core/version_defaults.mk b/core/version_defaults.mk
index 5f45946..5758d22 100644
--- a/core/version_defaults.mk
+++ b/core/version_defaults.mk
@@ -181,7 +181,7 @@ ifndef PLATFORM_SECURITY_PATCH
 #  It must be of the form "-MM-DD" on production devices.
 #  It must match one of the Android Security Patch Level strings of 
the Public Security Bulletins.
 #  If there is no $PLATFORM_SECURITY_PATCH set, keep it empty.
-  PLATFORM_SECURITY_PATCH := 2019-06-05
+  PLATFORM_SECURITY_PATCH := 2017-12-05
 endif
 
 ifndef PLATFORM_BASE_OS


Bill Yi於 2019年11月5日星期二 UTC+8上午1時34分28秒寫道：
>
> Android security backport source code is now available. The following 
> builds and tags are supported:
>
> 5887206, android-8.0.0_r40
> 5887208, android-8.1.0_r70
> 5887210, android-9.0.0_r50
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/a1cd8431-339b-4a4e-855c-db553bb22e49%40googlegroups.com.

[android-building] Re: Android 8.1.0 Oreo MR1 Released

[Chih-Wei Huang]

Xin Li於 2019年10月8日星期二 UTC+8上午6時56分18秒寫道：
>
> Android 8.1.0 Oreo MR1 source code is now available on the 
> oreo-mr1-security-release branch.
>
> This release contains all recent Oreo MR1 platform security updates up to 
> October 2019 Security Release corresponding to the following build and tag:
>
>  - 5794017, android-8.1.0_r69
>


The security patch of r65 is 2019-06-05, but r69 is 2017-12-05?
This is a very very confusing thing. Do you really have security updates in 
r69?

$ git diff android-8.1.0_r65 android-8.1.0_r69 core/version_defaults.mk
diff --git a/core/version_defaults.mk b/core/version_defaults.mk
index 5f45946d5..5758d2275 100644
--- a/core/version_defaults.mk
+++ b/core/version_defaults.mk
@@ -181,7 +181,7 @@ ifndef PLATFORM_SECURITY_PATCH
 #  It must be of the form "-MM-DD" on production devices.
 #  It must match one of the Android Security Patch Level strings of 
the Public Security Bulletins.
 #  If there is no $PLATFORM_SECURITY_PATCH set, keep it empty.
-  PLATFORM_SECURITY_PATCH := 2019-06-05
+  PLATFORM_SECURITY_PATCH := 2017-12-05
 endif
 
 ifndef PLATFORM_BASE_OS

-- 
-- 
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/91a54b8f-30f4-48da-a476-3d780514b84a%40googlegroups.com.

[android-building] Re: Deleting an entire repo sync

[Chih-Wei Huang]

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

[Chih-Wei Huang]

Thank you for the update.

However, I always feel uneasy why the updated tag is not a fast-forward 
commit of previous release.
Worse, usually there are explicitly conflicts between them.

For example, in frameworks/av, merging android-8.1.0_r22 to 
android-8.1.0_r25 (or r29)
results in the conflicts:

git merge android-8.1.0_r25
Auto-merging media/libmediaplayerservice/include/MediaPlayerInterface.h
CONFLICT (content): Merge conflict in 
media/libmediaplayerservice/include/MediaPlayerInterface.h
Auto-merging media/libmediaplayerservice/MediaPlayerService.h
CONFLICT (content): Merge conflict in 
media/libmediaplayerservice/MediaPlayerService.h
Auto-merging media/libmediaplayerservice/MediaPlayerService.cpp
CONFLICT (content): Merge conflict in 
media/libmediaplayerservice/MediaPlayerService.cpp
Auto-merging media/libmediaplayerservice/MediaPlayerFactory.h
CONFLICT (content): Merge conflict in 
media/libmediaplayerservice/MediaPlayerFactory.h
Auto-merging media/libmediaplayerservice/MediaPlayerFactory.cpp
CONFLICT (content): Merge conflict in 
media/libmediaplayerservice/MediaPlayerFactory.cpp
Recorded preimage for 'media/libmediaplayerservice/MediaPlayerFactory.cpp'
Recorded preimage for 'media/libmediaplayerservice/MediaPlayerFactory.h'
Recorded preimage for 'media/libmediaplayerservice/MediaPlayerService.cpp'
Recorded preimage for 'media/libmediaplayerservice/MediaPlayerService.h'
Recorded preimage for 
'media/libmediaplayerservice/include/MediaPlayerInterface.h'
Automatic merge failed; fix conflicts and then commit the result.

After checking the git history, I was surprised to find the conflicts 
result from the two commits:

commit 8a54af87b632c03ff2ae15a4a08880
1bb39fdae7
Author: Pawin Vongmasa
Date: Sun Dec 17 02:31:18 2017 -0800

Refactor MediaPlayerBase's notify

and

commit 5ffa7ea0dfa9ba3eba8ded0878c5293dc35e74a9
Author: Pawin Vongmasa
Date: Tue Dec 12 01:56:40 2017 -0800

Prevent MediaPlayerService::Client's use-after-free

More precisely, android-8.1.0_r22 contains the patch
"Refactor MediaPlayerBase's notify" but android-8.1.0_r29 doesn't.

Digging deeper, I found git log of android-8.1.0_r29
still contains "Refactor MediaPlayerBase's notify"
(commit d12c3600c8), but it was silently removed by
commit dd6cda64 (Snap for 4657601 from 
18cd9b58775e53b2ec1ffe571d165ad8fddfeff4 to oc-m4-release).

This doesn't look right to me.
If "Refactor MediaPlayerBase's notify" is unnecessary, shouldn't it be 
reverted explicitly?

Could anyone explain what happened?


Xin Li於 2018年5月15日星期二 UTC+8上午4時58分39秒寫道：
>
> Hi all,
>
> Android 8.1.0 Oreo MR1 source code is now available.  The following build, 
> tag, and device is supported:
>
>  - OPM2.171019.029.A1, android-8.1.0_r25, Nexus 6P (angler)
>
> 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 also pushed the corresponding kernel projects for the following 
> device:
>
> Tag | Project| Branch  | Device
> android-8.1.0_r0.50 | kernel/msm | android-msm-angler-3.10-oreo-m2 | Nexus 
> 6P (OPM2.171019.029.A1)
>

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

[Chih-Wei Huang]

Where is the update of Nexus 6P (angler)?

Xin Li於 2018年5月8日星期二 UTC+8上午7時11分39秒寫道：
>
> Hi all,
>
> Android 8.1.0 Oreo MR1 source code is now available.  The following 
> builds, tags, and devices are supported:
>
>  - OPM2.171019.029.B1, android-8.1.0_r26, Pixel 2 XL (taimen), Pixel 2 
> (walleye)
>  - OPM4.171019.016.A1, android-8.1.0_r27, Nexus 5X
>  - OPM4.171019.016.B1, android-8.1.0_r28, Pixel XL (marlin), Pixel 
> (sailfish), Pixel 2 XL (taimen), Pixel 2 (walleye)
>  - OPM4.171019.016.C1, android-8.1.0_r29, Pixel C (dragon)
>
> 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 also pushed the corresponding kernel projects for the following 
> devices:
>
> Tag | Project  | Branch
> | Device
> android-8.1.0_r0.51 | kernel/msm   | android-msm-wahoo-4.4-oreo-m2
>  | Pixel 2 and Pixel 2 XL OPM2.171019.029.B1
> android-8.1.0_r0.52 | kernel/arm64 | android-easel-intel-linux-4.7-oreo-m2 
> | Pixel 2 and Pixel 2 XL OPM2.171019.029.B1
> android-8.1.0_r0.53 | kernel/msm   | android-msm-bullhead-3.10-oreo-m4
>  | Nexus 5X OPM4.171019.016.A1
> android-8.1.0_r0.54 | kernel/msm   | android-msm-marlin-3.18-oreo-m4  
>  | Pixel and Pixel XL OPM4.171019.016.B1
> android-8.1.0_r0.55 | kernel/msm   | android-msm-wahoo-4.4-oreo-m4
>  | Pixel 2 and Pixel 2 XL OPM4.171019.016.B1
> android-8.1.0_r0.56 | kernel/arm64 | android-easel-intel-linux-4.7-oreo-m4 
> | Pixel 2 and Pixel 2 XL OPM4.171019.016.B1
> android-8.1.0_r0.57 | kernel/tegra | android-tegra-dragon-3.18-oreo-m4
>  | Pixel C OPM4.171019.016.C1
>
>

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

[Chih-Wei Huang]

Simao Gomes Viana於 2018年1月7日星期日 UTC+8上午9時06分40秒寫道：
>
> I think the main difference between those tags is the base framework.
> For example, the Pixel 2 ones have the power menu you see on the Pixel 2 
> stock images, the other ones have the traditional power menu like on Nougat
>

I don't think that's a good reason.
One release should have a fixed features set.
(of course features could be configured at build time or runtime, but all 
should be in one codebase)
Otherwise, how could you describe the features of one release?
How could you explain different user experiences to people even they use 
the same Android version?

"This is the Oreo-MR1 release, but there are two variants of this release, 
Pixel 2-like and non-Pixel 2 like, ..."

Did Google say so to the vendors?
No, I never heard.
It's ridiculous if Google does so.
Actually fragmentation is a long-standing issue of Android.
Google has spent a lot of effort to improve it -- Treble project is one of 
the effort.
I can't believe Google will release several Android variants that makes 
fragmentation much worse.

Refer: 
https://www.pastemagazine.com/articles/2017/05/can-google-solve-android-fragmentation-for-good.html

I am running android-8.1.0_r5 on a OnePlus 5 at the moment and it works 
> well, and has the Pixel 2 power menu and some other additional features 
> that Pixel 2 has.
>

About the new power menu, it's already in android-8.1.0_r1.
All image built since android-8.1.0_r1 should have the new power menu.
I don't believe it's a Pixel 2 only feature.

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

[Chih-Wei Huang]

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.

[android-building] Re: GPL Projects for Android O MR1 Preview 2

[Chih-Wei Huang]

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.0 Oreo MR1 Released

[Chih-Wei Huang]

Xin Li於 2017年12月6日星期三 UTC+8下午1時28分30秒寫道：
>
> Hi all,
>
> Android 8.1.0 Oreo MR1 source code is now available.  The following 
> builds, tags, and devices are supported:
>
>  - OPM1.171019.011, android-8.1.0_r1, Pixel 2 XL (taimen), Pixel 2 
> (walleye), Pixel XL (marlin), Pixel (sailfish), Nexus 5X (bullhead), Nexus 
> 6P (angler), Pixel C (dragon)
>

Oh! This seems the first time you released ONE branch
for all your devices. Great!
Hope you keep the right direction in the future.

(but where is Nexus Player - fugu?)

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 oreo-mr1-dev branch as well as oreo-mr1-release 
> branch.
>
> We have also pushed the corresponding kernel projects for the following 
> devices:
>
> Tag| Project  | Branch
>  | Device
> android-8.1.0_r0.1 | kernel/msm   | android-msm-angler-3.10-oreo-mr1  
>  | Nexus 6P
> android-8.1.0_r0.2 | kernel/msm   | android-msm-bullhead-3.10-oreo-mr1
>  | Nexus 5X
> android-8.1.0_r0.3 | kernel/tegra | android-tegra-dragon-3.18-oreo-mr1
>  | Pixel C
> android-8.1.0_r0.4 | kernel/msm   | android-msm-marlin-3.18-oreo-mr1  
>  | Pixel and Pixel XL
> android-8.1.0_r0.5 | kernel/msm   | android-msm-wahoo-4.4-oreo-mr1
>  | Pixel 2 and Pixel 2 XL
> android-8.1.0_r0.6 | kernel/msm   | android-easel-intel-linux-4.7-oreo-mr1 
> | Pixel 2 and Pixel 2 XL
>
> We'll also merge Oreo MR1 into AOSP master.  I'll update this post when 
> each of these become available.
>

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

[Chih-Wei Huang]

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: Emulator black screen after make -j16

[Chih-Wei Huang]

aadi於 2017年10月30日星期一 UTC+8上午2時38分23秒寫道：
>
> I;m using android Oreo
>


A known issue.
The emulator in Android O is totally broken.
See this for how to fix it:

https://issuetracker.google.com/issues/66066209

-- 
-- 
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.1.2 Nougat MR2 Released

[Chih-Wei Huang]

I saw all 6.0.1, 7.0.0, 7.1.1, and 8.0.0 got updated.
But 7.1.2 is not. Why?
Any plan to update it?

Xin Li於 2017年8月8日星期二 UTC+8上午7時06分48秒寫道：
>
> Android 7.1.2 Nougat MR2 source code is now available. The following 
> builds, tags, and devices are supported:
>
>  - N2G48C, android-7.1.2_r28, Nexus 5X, Nexus 6P, Nexus Player, Pixel C
>  - NJH47F, android-7.1.2_r29, Pixel XL, Pixel
>  - NHG47Q, android-7.1.2_r30, Pixel XL, Pixel
>  - NKG47S, android-7.1.2_r32, Pixel XL, Pixel
>  - NZH54D, android-7.1.2_r33, Pixel XL, Pixel
>

-- 
-- 
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: Black emulator on Building Android OREO on Linux 14.04 LTS

[Chih-Wei Huang]

You are not alone.
The emulator image built from 8.0.0 release
is totally broken. The issue is tracked in

https://issuetracker.google.com/issues/66066209

You can follow the instructions to build a bootable
emulator image for 8.0. But it's far from stable
than SDK image download from Google.

There must be more patches to fix that.

J Lee於 2017年9月20日星期三 UTC+8下午11時34分39秒寫道：
>
> I need help too.
> I have the exact same problem. I built android-8.0.0_r1 and 
> android-8.0.0_r11 x86-eng on Ubuntu 14.04 and the both of them have same 
> black emulator problem though the builds are sucessful.
> If emulator source is still not stable, is there any way to run the built 
> image on the emulator from standard Android SDK?
>
>
> On Wednesday, September 20, 2017 at 8:53:58 AM UTC-5, pranker wrote:
>>
>> Hi All,
>>
>> I have downloaded Android OREO code. (Branch - android-8.0.0_r4).
>>
>> The code builds successfully but on opening the emulator the emulator 
>> shows with a black screen and never opens.
>>
>> I get below messages while building.
>>
>> cts/apps/CtsVerifier/Android.mk:72: warning: FindEmulator: find: 
>> `cts/apps/CtsVerifier/src/com/android/cts/verifier/backup': No such file or 
>> directory
>> build/core/java_common.mk:88: warning: FindEmulator: cd: 
>> cts/hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/cts/hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/res:
>>  
>> No such file or directory
>> build/core/java_common.mk:88: warning: FindEmulator: cd: 
>> cts/hostsidetests/backup/assets: No such file or directory
>> cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider/Android.mk:23: 
>> warning: FindEmulator: find: 
>> `cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider/src': No such 
>> file or directory
>> cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider1/Android.mk:23: 
>> warning: FindEmulator: find: 
>> `cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider1/src': No 
>> such file or directory
>> cts/tests/tests/contactsproviderwipe/Android.mk:33: warning: 
>> FindEmulator: find: `cts/tests/tests/contactsproviderwipe/common/src': No 
>> such file or directory
>>
>>
>> And the below on running command emulator
>>
>> Your emulator is out of date, please update by launching Android Studio:
>>  - Start Android Studio
>>  - Select menu "Tools > Android > SDK Manager"
>>  - Click "SDK Tools" tab
>>  - Check "Android SDK Tools" checkbox
>>  - Click "OK"
>>
>> My Lunch option is aosp_arm64-eng
>>
>> Thanks for the 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] How to export $(call local-generated-sources-dir) in Android.bp?

[Chih-Wei Huang]

Hi,
I'd like to export the include path $(call local-generated-sources-dir) in 
Android.bp.
In Android.mk I can do like

LOCAL_EXPORT_C_INCLUDE_DIRS := $(call local-generated-sources-dir)

However, seems there is no counterpart in Android.bp.
I tried everything but none work.
Isn't it possible?

-- 
-- 
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] Ninja is unable to find new added Android.mk?

[Chih-Wei Huang]

Colin Cross於 2017年8月23日星期三 UTC+8下午11時45分56秒寫道：
>
> Kati is supposed to detect the new Android.mk, but if you put it back 
> in a way that left it with an old timestamp it may not notice.  Touch 
> any makefile that is read and it should reread everything: 
> touch Makefile 
>

I used repo sync to re-create it so I believe
the timestamp is correct.
However, I'm unable to reproduce the issue
after a clean build.
Don't know what happened yesterday...
Anyway, thank you for the explanation!
 

> On Tue, Aug 22, 2017 at 10:50 PM, Chih-Wei Huang 
> > wrote: 
> > Hi, 
> > I'm building Android O with my device tree but 
> > I got the error 
> > 
> > [1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja 
> > No need to regenerate ninja file 
> > ninja: error: 
> > 'out/host/common/obj/JAVA_LIBRARIES/apksig_intermediates/classes.jar', 
> > needed by 
> > 
> 'out/host/common/obj/JAVA_LIBRARIES/signapk_intermediates/classes-full-debug.jar',
>  
>
> > missing and no known rule to make it 
> > 13:28:20 ninja failed with: exit status 1 
> > make: *** [run_soong_ui] Error 1 
> > make: Leaving directory `/home/cwhuang/git/oreo-x86' 
> > 
> >  make failed to build some targets (13 seconds)  
> > 
> > After checking my codebase, I accidentally deleted tools/apksig/ dir. 
> > Then I added it back. However, I still got the error as before. 
> > It seems Ninja won't parse the new added Android.mk. 
> > How could I force it to do a full parsing? 
> > Do I need to do a clean build? (I don't think/hope so) 
>
>

-- 
-- 
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] Ninja is unable to find new added Android.mk?

[Chih-Wei Huang]

Hi,
I'm building Android O with my device tree but
I got the error

[1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
No need to regenerate ninja file
ninja: error: 
'out/host/common/obj/JAVA_LIBRARIES/apksig_intermediates/classes.jar', 
needed by 
'out/host/common/obj/JAVA_LIBRARIES/signapk_intermediates/classes-full-debug.jar',
 
missing and no known rule to make it
13:28:20 ninja failed with: exit status 1
make: *** [run_soong_ui] Error 1
make: Leaving directory `/home/cwhuang/git/oreo-x86'

 make failed to build some targets (13 seconds) 

After checking my codebase, I accidentally deleted tools/apksig/ dir.
Then I added it back. However, I still got the error as before.
It seems Ninja won't parse the new added Android.mk.
How could I force it to do a full parsing?
Do I need to do a clean build? (I don't think/hope so)

-- 
-- 
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: Emulator Out of Date and x86 based android virtual device error on AOSP.

[Chih-Wei Huang]

Imran Khushwaqt於 2017年4月26日星期三 UTC+8上午11時15分03秒寫道：
>
> HI, 
> I have synced AOSP master and build successfully. Using these commands. 
> Make clobber
>
> lunch aosp_arm-eng
>
> emulator.
>
>
> Emulator starts up with message "*Running an x86 based android virtual device 
> (AVD) is 10x Faseter. We strongly recommend creating a new AVD*". 
>
> and On console it says* AVD is out dated. Please update using android 
> studio*. An other message with emulator commands pops up is "*Could not 
> detect *
>
> *an ADB binary. Some emulator functionality will not work until a custom path 
> to ADB is added in the extended settings page.*"
>
>

As it said, use the x86 emulator instead of arm.


lunch aosp_x86-eng


or if you prefer the 64-bit OS:

lunch aosp_x86_64-eng



 

> My Question is how can I create new AVD and add it to build path during lunch 
> or make command or add custom path in extended settings
>
> page to avoid these error and make AVD faster. 
>
>
> What I have tried is
>
> Open android studio and updated all AVD in android studio sdk directory. This 
> doesn`t worked and then I changed sdk path in android studio 
>
> to AOSP WORKING_DIRECTORY/sdk and updated the installed packages. But still 
> its not working and emulator takes around one and half hour 
>
> or two to start. 
>
> What can I do to make it fast. I am using Mac OS 10.12 with 1.5 GHZ core i5 
> with 8 GB of RAM. 
>
>

-- 
-- 
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: pls help`vbox_x86 stuck at grub _ (virtualbox)

[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: Flashing boot.img

[Chih-Wei Huang]

Christopher Chen於 2017年2月7日星期二 UTC+8上午1時15分47秒寫道：
>
> Hi, everyone! I'm getting into Android/Linux kernel development for the 
> first time and have been trying to flash a freshly built kernel to a Nexus 
> 5X (build number N4F26I, rooted, bootloader unlocked, custom recovery). I 
> checked out branch android-7.1.1_r10 with the repo tool and also cloned 
> the android-msm-bullhead-3.10-nougat-mr1.1 
> 
>  
> branch of the kernel source.
>
> I can successfully compile the kernel from source and run make bootimage 
> in the Android source repository to produce a boot.img using my newly built 
> kernel. However, after running "fastboot flash boot boot.img" the device 
> gets stuck at the Google logo upon reboot. As far as I know, I'm building 
> the exact same kernel that is included in the factory image (I'm not 
> changing the kernel source at all and I'm pretty sure I'm on the right 
> branch for the build number).
>
> Also, adb doesn't show any connected devices at that point so I don't 
> think I can check the logcat.
>
> What might be going wrong? Any thoughts or ideas would be much 
> appreciated!
>

Did you use the correct kernel config?

Is your cmdline correct?

-- 
-- 
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.1.1 Nougat MR1 Released

[Chih-Wei Huang]

Hi Google,

I am checking the changes from
android-7.1.1_r4 to android-7.1.1_r6
in the frameworks/base repo.
Surprisingly it's the same:

$ git diff android-7.1.1_r4 android-7.1.1_r6
(nothing)

However, there is one significant commit
between them according to

$ git rev-list android-7.1.1_r4..android-7.1.1_r6
b88e9f2e121a46dbb85b9aeeb221971f56632cd6
ad760e111ca844c84d3be5eb5a2e51124320f151

$ git show ad760e111

commit ad760e111ca844c84d3be5eb5a2e51124320f151
Author: Rubin Xu 
Date:   Tue Nov 22 15:18:32 2016 +

Fix boot loop when upgrading direclty from L to N

A second attempt to fix the upgrade problem due to SID == 0
in the above upgrade path. The previous fix contains a bug
where it would cause future attempts to unify work challenge
to silently fail, and crash SystemUi when unlocking.

This fix adds a check for non-zero SID before doing the initial work
profile unification (which caused the upgrade crash when SID == 0).
This means the initial work profile unification would only happen when
the user has unlocked the lockscreen and SID is generated.

Bug: 32490092
Bug: 33050562
Change-Id: Ib28951b2ec26b4f091df7763d9902f55616fcb5c
(cherry picked from commit bfc7faaf353ea75ab04e986edbc79478679d40f6)

It seems this commit was reverted quietly:

$ git diff ad760e11 android-7.1.1_r6
diff --git a/services/core/java/com/android/server/LockSettingsService.java
b/services/core/java/com/android/server/LockSettingsService.java
index 03744f8..a91e205 100644
--- a/services/core/java/com/android/server/LockSettingsService.java
+++ b/services/core/java/com/android/server/LockSettingsService.java
@@ -240,17 +240,6 @@ public class LockSettingsService extends
ILockSettings.Stub {
 if (DEBUG) Slog.v(TAG, "Parent does not have a screen lock");
 return;
 }
-// Do not tie when the parent has no SID (but does have a screen 
lock).
-// This can only happen during an upgrade path where SID is yet to 
be
-// generated when the user unlocks for the first time.
-try {
-if (getGateKeeperService().getSecureUserId(parentId) == 0) {
-return;
-}
-} catch (RemoteException e) {
-Slog.e(TAG, "Failed to talk to GateKeeper service", e);
-return;
-}
 if (DEBUG) Slog.v(TAG, "Tie managed profile to parent now!");
 byte[] randomLockSeed = new byte[] {};
 try {


I'm curious why.
If this commit should be reverted, there should be
a commit which explicitly reverted it. Shouldn't it?

Or is this commit was incorrectly reverted
due to wrong merge reset?



Bill Yi於 2016年12月13日星期二 UTC+8上午5時57分45秒寫道：
>
> New nougat builds are now available. The following builds, tags, and 
> devices are supported:
> - NMF26Q, android-7.1.1_r6, Pixel XL (marlin) and Pixel (sailfish)
>
> 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
>
> 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: Try to build Android 7 on ArchLinux - needs help

[Chih-Wei Huang]

Just run the fail commands to see what error it is exactly.
I suspect you didn't install mcopy?

Denis Ciocca於 2016年10月25日星期二 UTC+8上午12時50分11秒寫道：
>
> Hi guys,
>
> I know. It is not supported. But...I like to use my arch linux and I don't 
> want to switch every time to use ubuntu just to build android.
> I'm trying to compile Android 7. I installed virtualenv2 and all libraries 
> needed. As soon as I try to compile for hikey I get:
>
> [  0% 12/43703] build out/target/product/hikey/boot_fat.uefi.img 
> FAILED: /bin/bash -c "(dd if=/dev/zero 
> of=out/target/product/hikey/boot_fat.uefi.img bs=512 count=98304 ) && 
> (mkfs.fat -n \"boot\" out/target/product/hikey/boot_fat.uefi.img ) && 
> (mcopy -i 
> out/target/product/hikey/boot_fat.uefi.img out/target/product/hikey/kernel 
> ::Image ) && (mcopy -i out/target/product/hikey/boot_fat.uefi.img 
> out/target/product/hikey/hi6220-hikey.dtb ::hi62
> 20-hikey.dtb ) && (mcopy -s -i out/target/product/hikey/boot_fat.uefi.img 
> device/linaro/hikey/bootloader/* :: ) && (mcopy -i 
> out/target/product/hikey/boot_fat.uefi.img out/target/product/hi
> key/ramdisk.img ::ramdisk.img )" 
> 98304+0 records in 
> 98304+0 records out 
> 50331648 bytes (50 MB, 48 MiB) copied, 0.274155 s, 184 MB/s 
> mkfs.fat: warning - lowercase labels might not work properly with DOS or 
> Windows 
> mkfs.fat 4.0 (2016-05-06) 
> Total number of sectors (98304) not a multiple of sectors per track (63)! 
> Add mtools_skip_check=1 to your .mtoolsrc file to skip this test 
> [  0% 12/43703] host C++: libadb <= system/core/adb/transport.cpp 
>
> [  0% 12/43703] Docs droiddoc: out/target/common/docs/api-stubs 
> DroidDoc took 41 sec. to write docs to out/target/common/docs/api-stubs 
> ninja: build stopped: subcommand failed. 
> make: *** [build/core/ninja.mk:149: ninja_wrapper] Error 
>
>
> Anyone have experience building on arch? Anyone can help me how to check 
> and read ninja log output?
>
> Thanks a lot,
> Denis
>
>

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

[Chih-Wei Huang]

Bill Yi於 2016年9月9日星期五 UTC+8上午1時29分04秒寫道：
>
>
> On Wednesday, September 7, 2016 at 8:24:36 AM UTC-7, Igor Kalkov wrote:
>>
>> Hi Bill,
>>
>> thanks for publishing the progress. I'm really glad I found this group.
>> One question though:
>>
>> Until now I assumed, that "_rX" tags are created subsequently and mark 
>> different development stages of the whole Android platform. But according 
>> to your message "7.0.0_r3" and "7.0.0_r4" are basically the same thing, 
>> tailored to different devices.
>> So if I develop a new device and always want to be up-to-date, which tag 
>> should I merge: all of them in the ascending order, only one specific of 
>> them or only the latest?
>>
> The latest
>

Then why not all Nexus devices are built from the latest tag?

What's the latest tag? When we thought 7.0.0_r4 is the latest,
but now you released 7.0.0_r6. So...

What's the different between 7.0.0_r3, 7.0.0_r4, and 7.0.0_r6?
If they are the same, why don't you build all Nexus images
from the same tag?
If they are different, why?

The real problem is, why did you (Google) make the thing so confused?

-- 
-- 
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 6.0.1 Marshmallow MR2 Released

[Chih-Wei Huang]

Bill Yi於 2016年9月9日星期五 UTC+8上午1時24分50秒寫道：
>
> Those manifests do not contain the packages/apps/Exchange project.
>


android-6.0.1_r61 still has packages/apps/Exchange
but android-6.0.1_r66 removed it?
So it's officially removed?

 

>
> On Thursday, September 8, 2016 at 7:42:28 AM UTC-7, Chih-Wei Huang wrote:
>>
>> Hi Bill,
>> packages/apps/Exchange missed the new tags again.
>> Please correct it.
>>
>> cwhuang@icm05:~/git/aosp/packages/apps/Exchange$ git fetch aosp 
>> android-6.0.1_r65
>> fatal: Couldn't find remote ref android-6.0.1_r65
>> Unexpected end of command stream
>> cwhuang@icm05:~/git/aosp/packages/apps/Exchange$ git fetch aosp 
>> android-6.0.1_r66
>> fatal: Couldn't find remote ref android-6.0.1_r66
>> Unexpected end of command stream
>> cwhuang@icm05:~/git/aosp/packages/apps/Exchange$ git fetch aosp 
>> android-6.0.1_r67
>> fatal: Couldn't find remote ref android-6.0.1_r67
>> Unexpected end of command stream
>>
>>

-- 
-- 
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 6.0.1 Marshmallow MR2 Released

[Chih-Wei Huang]

Chih-Wei Huang於 2016年9月7日星期三 UTC+8下午11時24分36秒寫道：
>
>
>
> Bill Yi於 2016年9月7日星期三 UTC+8上午5時53分09秒寫道：
>>
>> Android 6.0.1 Marshmallow MR2 source code is now available on the 
>> marshmallow-mr2-release branch. The following builds, tags, and devices are 
>> supported:
>>
>> - MOB31E, android-6.0.1_r66, Nexus 5, Nexus 6, Nexus 9 (volantisg)
>>
>
> Why the manifest android-6.0.1_r66 shows
> android-6.0.1_r62? Is it intentional?
>

Any comment?

 

> $ git fetch aosp android-6.0.1_r66
> remote: Finding sources: 100% (9/9)
> Unpacking objects: 100% (9/9), done.
> remote: Total 9 (delta 3), reused 9 (delta 3)
> From https://android.googlesource.com/platform/manifest
>  * branchandroid-6.0.1_r66 -> FETCH_HEAD
>  * [new branch]  android-6.0.1_r66 -> aosp/android-6.0.1_r66
>
> $ git show aosp/android-6.0.1_r66
> commit c4bfbff81f9493e1aeaf50d0cde5052493f76a8a
> Author: The Android Open Source Project 
> Date:   Mon Aug 1 15:22:04 2016 -0700
>
> Manifest for Android 6.0.1 Release 62 (MTC20F)  <== ???
>
> diff --git a/default.xml b/default.xml
> index fdcce66..f40a163 100644
> --- a/default.xml
> +++ b/default.xml
> @@ -3,7 +3,7 @@
>  
> fetch=".." />
> -   +   remote="aosp"
> sync-j="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.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: Android 6.0.1 Marshmallow MR2 Released

[Chih-Wei Huang]

Hi Bill,
packages/apps/Exchange missed the new tags again.
Please correct it.

cwhuang@icm05:~/git/aosp/packages/apps/Exchange$ git fetch aosp 
android-6.0.1_r65
fatal: Couldn't find remote ref android-6.0.1_r65
Unexpected end of command stream
cwhuang@icm05:~/git/aosp/packages/apps/Exchange$ git fetch aosp 
android-6.0.1_r66
fatal: Couldn't find remote ref android-6.0.1_r66
Unexpected end of command stream
cwhuang@icm05:~/git/aosp/packages/apps/Exchange$ git fetch aosp 
android-6.0.1_r67
fatal: Couldn't find remote ref android-6.0.1_r67
Unexpected end of command stream

-- 
-- 
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 6.0.1 Marshmallow MR2 Released

[Chih-Wei Huang]

Bill Yi於 2016年9月7日星期三 UTC+8上午5時53分09秒寫道：
>
> Android 6.0.1 Marshmallow MR2 source code is now available on the 
> marshmallow-mr2-release branch. The following builds, tags, and devices are 
> supported:
>
> - MOB31E, android-6.0.1_r66, Nexus 5, Nexus 6, Nexus 9 (volantisg)
>

Why the manifest android-6.0.1_r66 shows
android-6.0.1_r62? Is it intentional?

$ git fetch aosp android-6.0.1_r66
remote: Finding sources: 100% (9/9)
Unpacking objects: 100% (9/9), done.
remote: Total 9 (delta 3), reused 9 (delta 3)
>From https://android.googlesource.com/platform/manifest
 * branchandroid-6.0.1_r66 -> FETCH_HEAD
 * [new branch]  android-6.0.1_r66 -> aosp/android-6.0.1_r66

$ git show aosp/android-6.0.1_r66
commit c4bfbff81f9493e1aeaf50d0cde5052493f76a8a
Author: The Android Open Source Project 
Date:   Mon Aug 1 15:22:04 2016 -0700

Manifest for Android 6.0.1 Release 62 (MTC20F)  <== ???

diff --git a/default.xml b/default.xml
index fdcce66..f40a163 100644
--- a/default.xml
+++ b/default.xml
@@ -3,7 +3,7 @@
 
   
-  
 

-- 
-- 
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] Android 7.0 build system doesn't generate .P ?

[Chih-Wei Huang]

It's very helpful.
Thank you very much!

Dan Willemsen於 2016年9月1日星期四 UTC+8下午10時30分18秒寫道：
>
> We've switched to using ninja to do our builds, which defaults to reading 
> the depfile into it's database, then deleting it. You can either keep the 
> depfile:
>
>   NINJA_ARGS="-d keepdepfile" m ...
>
> Or just ask ninja what the deps are for a specific file: (NINJA_EXTRA_ARGS 
> has to be empty as a workaround in this case)
>
>   NINJA_ARGS= "-t deps out/...o" m NINJA_EXTRA_ARGS=
>
> You can also see some of the other ninja tools and debug modes that are 
> useful with -d/-t list:
>
> ninja subtools:
> browse  browse dependency graph in a web browser
>  clean  clean built files
>   commands  list all commands required to rebuild given targets
>   deps  show dependencies stored in the deps log
>  graph  output graphviz dot file for targets
>  query  show inputs/outputs for a path
>targets  list targets by their rule or depth in the DAG
> compdb  dump JSON compilation database to stdout
>  recompact  recompacts ninja-internal data structures
>
> debugging modes:
>   statsprint operation counts/timing info
>   explain  explain what caused a command to execute
>   keepdepfile  don't delete depfiles after they're read by ninja
>   keeprsp      don't delete @response files on success
> multiple modes can be enabled via -d FOO -d BAR
>
>
> On Thu, Sep 1, 2016 at 7:05 AM Chih-Wei Huang  > wrote:
>
>> Hi,
>> Anyone knows why Android 7.0 build system doesn't generate
>> the .P file, the dependency file of the .o to be included?
>> Without the .P file it's hard to debug the dependency issue.
>> Or any alternative way to check the dependency of the .o in Android 7.0?
>>
>> -- 
>>
>

-- 
-- 
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] Android 7.0 build system doesn't generate .P ?

[Chih-Wei Huang]

Hi,
Anyone knows why Android 7.0 build system doesn't generate
the .P file, the dependency file of the .o to be included?
Without the .P file it's hard to debug the dependency issue.
Or any alternative way to check the dependency of the .o in Android 7.0?

-- 
-- 
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] New build system always re-scan makefiles?

[Chih-Wei Huang]

Dan Willemsen於 2016年8月27日星期六 UTC+8上午12時51分26秒寫道：
>
> If you run:
>
> $ (cd bootable/recovery/tests ; find -L  testdata/*)
>
> multiple times, does it give you the results in different orders? Does it 
> return different results before and after a build?
>

It always gives the same results.
If not, I'm surprised since nobody change
any file in bootable/recovery/tests.

find does return results in filesystem order, which is not defined. This 
> hasn't been a problem with any filesystem that I've seen -- you always get 
> the same order until something changes in that directory, then the order 
> may change.
>
>
There is nothing changed in that directory.
In fact I didn't change anything under
the bootable/recovery/ dir. It's exactly
the same as AOSP.

Am I the only one see this issue?

Actually the problem is not at bootable/recovery/tests.
The problem is the new build system always thinks
something is changed. If I removed this line in 
bootable/recovery/tests/Android.mk

testdata_files := $(call find-subdir-files, testdata/*)

and make again, it said
bootable/recovery/tests/Android.mk was modified, regenerating...

This is OK since I did change the makefile.
However make again it said:

$(shell cd libcore && ls -d */src/test/{java,resources} 2> /dev/null) was 
changed, regenerating...

(what? I didn't change libcore)

-- 
-- 
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] New build system always re-scan makefiles?

[Chih-Wei Huang]

Try to build Android 7.0, the new build system is much faster.
Looks great! However, I noticed it always
re-scan all Android.mk since it detects something
is changed. Actually it's not.
I just do another make after the previous successful make.
I expect it should show "Nothing to be done".

How to avoid that?

$ make -j32

PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.0
TARGET_PRODUCT=android_x86_64
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86_64
TARGET_ARCH_VARIANT=x86_64
TARGET_CPU_VARIANT=
TARGET_2ND_ARCH=x86
TARGET_2ND_ARCH_VARIANT=x86
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-40-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=NRD90M
OUT_DIR=out

make: Entering directory `/home/cwhuang/git/android-x86-7.0'
Running kati to generate build-android_x86_64.ninja...
$(shell cd bootable/recovery/tests ; find -L  testdata/*) was changed, 
regenerating...
   ^^^ WHAT? I 
didn't change that
 

PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.0
TARGET_PRODUCT=android_x86_64
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86_64
TARGET_ARCH_VARIANT=x86_64
TARGET_CPU_VARIANT=
TARGET_2ND_ARCH=x86
TARGET_2ND_ARCH_VARIANT=x86
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-40-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=NRD90M
OUT_DIR=out

including ./abi/cpp/Android.mk ...
including ./art/Android.mk ...
including ./bionic/Android.mk ...
including ./bootable/newinstaller/Android.mk ...
including ./bootable/recovery/Android.mk ...
including ./build/libs/host/Android.mk ...
including ./build/target/board/Android.mk ...
including ./build/target/product/security/Android.mk ...
...

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