DB410c AOSP Latest Build (1-17-19) New Warning on Lunch [ Builds Successful but won't Boot ]


#1

I have compiled the AOSP Master Branch every day for the last week or two.
Prior to 1-15-2019 the code compiled correctly and would produce binary’s that booted.

The problem i ran into was that AOSP would boot but the USB Gadget was not working correctly and adb access was not able.

Trying to debug this issue became slightly confusing due to the system as root feature now utilized in newer builds. The files in ~/AOSP/out/target/product/db410c32_only/root previously were a part of the boot.img. Now the ~/AOSP/out/target/product/db410c32_only/root ( root filesystem ) is a part of the system image.

The errors i was seeing were related to the system not finding files that are a part of ~/AOSP/out/target/product/db410c32_only/root.

I re-installed ubuntu 18.04 Lts server on my server and downloaded a fresh clone of AOSP.
The Warning i see during lunch and during the build in a couple spots only started occurring after sync the source after 1-15-2019. A recent change must be responsible for the new waning.

Upon executing lunch I get.

[W][2019-01-17T17:51:34-0500][28277] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2019-01-17T17:51:34-0500][28277] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files

During the build i also see the same warning in a few other spots.

verbose: kati: 4921 symbols
[W][2019-01-17T17:51:35-0500][28345] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2019-01-17T17:51:35-0500][28345] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files

[1/1] out/soong/.minibootstrap/minibp -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/.bootstrap/build.ninja.d -globFile out/soong/.minibootstrap/build-globs.ninja -o out/soong/.bootstrap/build.ninja Android.bp
[W][2019-01-17T17:51:37-0500][28630] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2019-01-17T17:51:37-0500][28630] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files

[2/122] GOROOT=‘prebuilts/go/linux-x86’ prebuilts/go/linux-x86/pkg/tool/linux_amd64/compile -c 8 -o out/soong/.bootstrap/blueprint-deptools/pkg/github.com/google/blueprint/deptools.a.tmp -p github.com/google/blueprint/deptools -complete -pack build/blueprint/deptools/depfile.go && if cmp --quiet out/soong/.bootstrap/blueprint-deptools/pkg/github.com/google/blueprint/deptools.a.tmp out/soong/.bootstrap/blueprint-deptools/pkg/github.com/google/blueprint/deptools.a; then rm out/soong/.bootstrap/blueprint-deptools/pkg/github.com/google/blueprint/deptools.a.tmp; else mv -f out/soong/.bootstrap/blueprint-deptools/pkg/github.com/google/blueprint/deptools.a.tmp out/soong/.bootstrap/blueprint-deptools/pkg/github.com/google/blueprint/deptools.a; fi

[122/122] 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
[W][2019-01-17T17:51:50-0500][28866] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2019-01-17T17:51:50-0500][28866] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files

[W][2019-01-17T17:52:29-0500][31548] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2019-01-17T17:52:29-0500][31548] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files
status: out/build-db410c32_only-cleanspec.ninja is missing, regenerating…
verbose: kati: regen check time: 0.000041
verbose: kati: Stack size: 8384512 bytes
verbose: kati: 840513 find nodes
verbose: kati: init find emulator time: 1.799849
verbose: kati: eval time: 3.221838
verbose: kati: 5 explicit rules

verbose: kati: func wildcard time: 0.910112 / 172178
verbose: kati: func sort time: 0.442301 / 349858
verbose: kati: 944951 symbols
[856/856] writing build rules …
[W][2019-01-17T17:53:26-0500][667] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2019-01-17T17:53:26-0500][667] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files
status: out/build-db410c32_only-package.ninja is missing, regenerating…
verbose: kati: regen check time: 0.000044
verbose: kati: Stack size: 8388608 bytes
[857/859] initializing packaging system …
[858/859] including distdir.mk …

Here is the Verbose.log file.
https://mega.nz/#!9SZAlABS!ZuF1TBzyUWx3Sckaa1PnFLuEP_spBTHToe5Vee0kB6c

I am not sure what to change or if this warning is the main issue.
But as i said the builds were booting prior to this.


#2

HI @BigCountry907, I’m sorry I can not help you with the question …:wink: but you could help me, I’m trying to update my D410C to Andriod> = 6 months ago, but I can not compile OASP, I’m a beginner, I do not even have the necessary disk space to do it.
Would you be so kind to upload or share the latest build that you have successfully compiled and booted on the D410C?

That will be very useful, not only for me, but for all those who want to update the D410C and we do not know how to do it …

Thanks in advanced!


#3

Even though I had successfully compiled and booted AOSP there were many problems with the build. It was actually Android Q that I compiled. The problem appeared to be that the new System as Root was not properly configured so things like ADB was not working correctly.

When i find time in the next few days I will set up a new build and see if i can get it cleaned up a bit.
I do have copies of some of my earlier builds but like i said things are broken. It will boot but is difficult to work with not having ADB.


#4

Ok Thanks, I’m going to wait you… don’t forget me… :slight_smile:


#5

I posted a build at the end of this thread.

I think it’s one that boots but it does have some issues.
Test it and let me know.


#6

Hi! I wil back. Any news? Finally did you build a Android >6 image for D410C fully working?


#7

No i have not revisited the DB. If i get some time i will see if it will build again.


#8

Ok, thank in advanced. It’s really hard to build a get fully working andriod image…