[GUIDE][COMPLETE] Android ROM Development From Source To End

[qiurigao]

[34/54] link out/soong/.bootstrap/soong-python/test/test
[35/54] test android/soong/python
[36/54] link out/soong/.bootstrap/soong-cc-config/test/test
[37/54] test android/soong/cc/config
FAILED: out/soong/.bootstrap/soong-cc-config/test/test.passed
out/soong/.bootstrap/bin/gotestrunner -p ./build/soong/cc/config -f out/soong/.bootstrap/soong-cc-config/test/test.passed -- out/soong/.bootstrap/soong-cc-config/test/test -test.short
panic: read /opt/8937: is a directory

goroutine 1 [running]:
android/soong/cc/config.setSdclangVars()
/opt/8937/build/soong/cc/config/global.go:206 +0x17bc
android/soong/cc/config.init.2()
/opt/8937/build/soong/cc/config/global.go:179 +0xcd6
android/soong/cc/config.init()
/opt/8937/build/soong/cc/config/tidy_test.go:42 +0x3cbb
main.init()
/opt/8937/out/soong/.bootstrap/soong-cc-config/test/test.go:64 +0x58
[38/54] link out/soong/.bootstrap/soong-java/test/test
[39/54] compile out/soong/.bootstrap/soong-cc/pkg/android/soong/cc.a
[40/54] compile out/soong/.bootstrap/soong-cc/test/android/soong/cc.a
ninja: build stopped: subcommand failed.
01:31:39 soong failed with: exit status 1

 

[ashwini215]

After reverting it the those are working?[/QUOTE]

No, still the same problem.
Is this problem something to do with the warnings that come at the last during kernel compilation.

I have attached log.

 

[pix106]

Hi,

in this security bulletin, i can see 5.1.1 in "updated AOSP versions" column of some tables.
When i "repo sync" my 5.1.1 AOSP source, i don't seem to get these securtity patches.

I'm syncing android-5.1.1_r38, are these patches merged in some other tag ?
Did i understand it wrong ?

Thanks !

 

[DodoGTA]

Hi,

in this security bulletin, i can see 5.1.1 in "updated AOSP versions" column of some tables.
When i "repo sync" my 5.1.1 AOSP source, i don't seem to get these securtity patches.

I'm syncing android-5.1.1_r38, are these patches merged in some other tag ?
Did i understand it wrong ?

Thanks !

Just because it's applicable to that version doesn't mean that a new tag will be released for that version

Sent from my Samsung Galaxy Trend Plus using XDA Labs

 

[pix106]

Just because it's applicable to that version doesn't mean that a new tag will be released for that version

Thanks.
So, do you know where it has been updated and how to sync it ? Table header on security bulletin says "updated AOSP version" not "applicable to" , there must be somewhere to get this updated source code, isn't it ?

 

[DiamondJohn]

Kanging?

I've successfully build a few ROMs for my device and I share my builds here on XDA.

All my builds are LineageOS based, and as part of my build, I replace a few standard LineageOS apps with ones from other ROMs. For example, in my ResurectionRemix build, I replace LineageOS's music player Eleven, with OmiRom's music player Phonograph.

I do specifically give mention / references to these changes in the threads where I post the builds for my ROMs.

Is this taking from a number of different ROMs (found on GitHub) to piece together my version of a ROM OK? or do I need to attain explicit permissions from someone to "Kang" these repositories on GitHub? ironically, the last ROM I built using this technique was to modify the apps included in AOKP.

 

[DodoGTA]

Thanks.
So, do you know where it has been updated and how to sync it ? Table header on security bulletin says "updated AOSP version" not "applicable to" , there must be somewhere to get this updated source code, isn't it ?

You have to cherry-pick the relevant commits

Sent from my Samsung Galaxy Trend Plus using XDA Labs

 

[xenreon]

I've successfully build a few ROMs for my device and I share my builds here on XDA.

All my builds are LineageOS based, and as part of my build, I replace a few standard LineageOS apps with ones from other ROMs. For example, in my ResurectionRemix build, I replace LineageOS's music player Eleven, with OmiRom's music player Phonograph.

I do specifically give mention / references to these changes in the threads where I post the builds for my ROMs.

Is this taking from a number of different ROMs (found on GitHub) to piece together my version of a ROM OK? or do I need to attain explicit permissions from someone to "Kang" these repositories on GitHub? ironically, the last ROM I built using this technique was to modify the apps included in AOKP.

Keeping the original commit authorship is enough, that's why it's open source.

 

[pix106]

You have to cherry-pick the relevant commits

Ok, if I got it well, I actually have to cherry pick all commits before these ones ? Isn't there a "master" branch somewhere ?

 

[DodoGTA]

Ok, if I got it well, I actually have to cherry pick all commits before these ones ? Isn't there a "master" branch somewhere ?

You have to cherry-pick the relevant security patch-related commits (They can be found in the security bulletins) that are of a newer security patch than the one specified in build/core/version_defaults.mk (Example: If one wants to go from April 2016 to January 2017 security patch, then one has to cherry-pick commits from the May, June, July... 2016 security patch) and bump the security patch level accordingly

And AOSP has a master branch, but it's bleeding-edge (and that's not what you want in this case)

Sent from my Samsung Galaxy Trend Plus using XDA Labs

 

[ichiato]

I am trying to build aicp from source for an unsupported device and I keep getting this error when building

ninja: error: '/Volumes/android/aicp/out/target/product/j3x3g/obj/KERNEL_OBJ/usr', needed by '/Volumes/android/aicp/out/target/product/j3x3g/obj/SHARED_LIBRARIES/libtinyalsa_intermediates/mixer.o', missing and no known rule to make it

. full log attached. Any help would be appreciated

 

[manishvermaa]

I am getting this error while building DU for oneplus 3t. Any help will be appriciated.

ninja: error: '/home/manish/DU/out/target/product/oneplus3/kernel', needed by '/home/manish/DU/out/target/product/oneplus3/boot.img', missing and no known rule to make it
20:00:38 ninja failed with: exit status 1
make: *** [build/core/main.mk:21: run_soong_ui] Error 1

Full log:
https://hastebin.com/aqegiruqur.pl

 

[ichiato]

I am getting this error while building DU for oneplus 3t. Any help will be appriciated.

ninja: error: '/home/manish/DU/out/target/product/oneplus3/kernel', needed by '/home/manish/DU/out/target/product/oneplus3/boot.img', missing and no known rule to make it
20:00:38 ninja failed with: exit status 1
make: *** [build/core/main.mk:21: run_soong_ui] Error 1

Full log:
https://hastebin.com/aqegiruqur.pl

where in your device tree is your recovery.fstab and kernel located ?

 

[virsys]

Good morning
I used this guide to create a ROM for my tablet (gt510wifi). The rom compiles just fine, but it isn't booting on the device. TWRP flashes the rom without any issues. The tablet is stuck on the bootlogo and not rebooting. The rom (rr) is rooted with Magisk. Is knox preventing my phone from booting? I'm new to this..
Can you give me a hint?? Is there a log deep inside of my tablet?
Thanks

 

[pix106]

You have to cherry-pick the relevant security patch-related commits (They can be found in the security bulletins) that are of a newer security patch than the one specified in build/core/version_defaults.mk (Example: If one wants to go from April 2016 to January 2017 security patch, then one has to cherry-pick commits from the May, June, July... 2016 security patch) and bump the security patch level accordingly

And AOSP has a master branch, but it's bleeding-edge (and that's not what you want in this case)

Sent from my Samsung Galaxy Trend Plus using XDA Labs

ok, thanks a lot !
I hoped there was a "5.1.1 master", from which a new tag hadn't been created after the r38...
I'll try to do this, but as i never cherry-picked i'm affraid of the dependencies... and i'll have to cherry-pick dozens of commits... i'll discover if they are easy to deal with

And i didn't mention that, for now, my unpublished AOSP rom for Tab2 A7-10F (MT8127) reboots randomly "after a while", with a device tree that is very close to the one i used for CM12.1 and which works with no reboot.

Thanks again !

 

[albertoduqe]

Hi again you all!!

I sorted out the fatal signals I was getting with LegendRom for Lithium. They were related to NFC.

I solved them temporarily replacing and adding missing NFC files and folders directly yo /out/target/lithium/system, getting them from an RR build.

In the meantime, I added the missing sources to local_manifest (pointing to the three repos I found in LineageOS, LineageOS/android_vendor_nxp-nfc_opensource_XXX), and to lithium's dependencies, but when I run another build the "missing" files are not there.

I do not want to bother you guys with the list of files affected, but my guess is that the main missing thing is the folder NQNfcNci in system/vendor/app and its inner lib folder and apk file.

My question is, what am I missing? I mean, the source for that folder and apk is there in the Android.mk, in my working-tree/vendor/nxp-nfc/opensource/Nfc...

My only guess is that I must make clobber and clear the out folder, run a clean build and maybe then it's all pulled to its place, but I don't know if I am in the right path at all...

Thanks!!!

 

[Infect_Ed]

Hi again you all!!

I sorted out the fatal signals I was getting with LegendRom for Lithium. They were related to NFC.

I solved them temporarily replacing and adding missing NFC files and folders directly yo /out/target/lithium/system, getting them from an RR build.

In the meantime, I added the missing sources to local_manifest (pointing to the three repos I found in LineageOS, LineageOS/android_vendor_nxp-nfc_opensource_XXX), and to lithium's dependencies, but when I run another build the "missing" files are not there.

I do not want to bother you guys with the list of files affected, but my guess is that the main missing thing is the folder NQNfcNci in system/vendor/app and its inner lib folder and apk file.

My question is, what am I missing? I mean, the source for that folder and apk is there in the Android.mk, in my working-tree/vendor/nxp-nfc/opensource/Nfc...

My only guess is that I must make clobber and clear the out folder, run a clean build and maybe then it's all pulled to its place, but I don't know if I am in the right path at all...

Thanks!!!

https://github.com/LineageOS/android_vendor_nxp-nfc_opensource_Nfc/tree/lineage-15.0

https://github.com/LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci/tree/lineage-15.0

https://github.com/LineageOS/android_vendor_nxp-nfc_opensource_frameworks/tree/lineage-15.0

You need all three of these

 

[ZVNexus]

Trying to build Dirty Unicorns v12 for the HTC One (M9) (Verizon).

https://hastebin.com/wobatalelu.vbs

Have looked this up but all I can find is just other people's hastebins pertaining to the same error. From reading it, it looks like its missing a Java library? I have a hard time reading errors.

How would I go about obtaining a Java library?

 

[xenreon]

Trying to build Dirty Unicorns v12 for the HTC One (M9) (Verizon).

https://hastebin.com/wobatalelu.vbs

Have looked this up but all I can find is just other people's hastebins pertaining to the same error. From reading it, it looks like its missing a Java library? I have a hard time reading errors.

How would I go about obtaining a Java library?

Either sync lineagesdk (check los GitHub) or remove whatever is asking for it.

 

[ZVNexus]

Either sync lineagesdk (check los GitHub) or remove whatever is asking for it.

I originally thought to remove GestureHandler, (the thing that was requested the library but couldnt be found), but I need that. Thanks a lot for the lineagesdk thing!