yashsingh1/xdaforums huggingface dataset:
[Android] nitin.chobhe:
What device tree are you using?

I compared commits of system/sepolicy/public/domain.te of Havoc with those of CarbonROM and found that:

Reverting following 2 commits would fix your error:

https://github.com/Havoc-OS/android...14d0e9b#diff-fd2030c6aab2ec3822840982b0c71545

https://github.com/Havoc-OS/android_system_sepolicy/commit/33fe8ff386dee1c053785d1eaaa07b56414d0e9b#diff-fd2030c6aab2ec3822840982b0c71545

https://github.com/Havoc-OS/android...7927aee#diff-fd2030c6aab2ec3822840982b0c71545

https://github.com/Havoc-OS/android_system_sepolicy/commit/d4a8dad3b1d897d422a781fd8377d4bad7927aee#diff-fd2030c6aab2ec3822840982b0c71545

Nitin
[Android] tweetingdinosure:
maybe try adding this PRODUCT_FULL_TREBLE_OVERRIDE = false

in the boardconfig.mk
[Android] alphamale:
Thank you. I'm using colt dt
[Android] nitin.chobhe:
Ok :)

Above steps should solve your issue then. Keep us posted :fingers-crossed:

Nitin
[Android] alphamale:
I got it to build, but stuck on boot animation. Tried logcat got waiting for device
[Android] DiamondJohn:
last_kmsg?
[Android] nitin.chobhe:
Are you sure you used wahoo from ColtOS-Devices github? Because it has this commit, which allows to connect to adb.

Nitin
[Android] alphamale:
Yes I see it in device.mk.
[Android] nitin.chobhe:
That's strange... Can you link me your device and vendor trees? Are you building with gapps? What is the size of your build?

Nitin
[Android] alphamale:
https://gitlab.com/DirtyUnicorns/android_vendor_pixelgapps

https://github.com/ColtOS-Devices/android_device_google_taimen

https://github.com/ColtOS-Devices/android_device_google_wahoo/tree/c10

https://github.com/ColtOS-Devices/android_kernel_google_wahoo/tree/c10

https://github.com/ColtOS-Devices/android_vendor_google

Building with pixelgapps. Build is 770 mb.
[Android] nitin.chobhe:
Not my device tree links (I've them as I work on then :cyclops:). I wanted to see what your changes look like for Havoc OS.

The build size looks ok. If I were you, I would build without gapps till the build boots (makes life easier).

Nitin
[Android] alphamale:
Sorry

https://github.com/alphamalee/android_device_google_taimen/tree/havoc

https://github.com/alphamalee/android_device_google_wahoo/tree/havoc
[Android] ParanoidNemo:
Getting this:

fatal: remove-project element specifies non-existent project: platform/hardware/qcom/gps

when trying to sync Sony AOSP local_manifest over POSP source code.

The think that I don't understand is that the POSP manifest.xml contains the platform/hardware/qcom/gps, and infact if I try to repo sync without the <remove-project> tag it says that the project already exists and so cannot be synced.

Any advise?
[Android] ismael47:
FAILED:

build/make/core/base_rules.mk:325: error: hardware/qcom/display/msm8998/include: MODULE.TARGET.HEADER_LIBRARIES.display_headers already defined by hardware/qcom-caf/msm8996/display.

23:23:35 ckati failed with: exit status 1

can someone help me with that mistake I try to compile for taimen I have everything but meda that error
[Android] NepoRood:
I've been building for Crosshatch for over a year and never seen that error, sorry I can't help with it.
[Android] NepoRood:
Drop the CAF repo(s) you don't need them for Pixel devices :good:
[Android] Hb20032003:
Hi I compiled AEX 6.7 for falcon. Everything works fine except when I make a call I get "No sim or sim error" but I am able to SMS and use data. I have attached the log. Please help.

Device tree:https://github.com/hbarsaiyan/android_device_motorola_falcon/tree/aex-new

Common Device Tree:https://github.com/hbarsaiyan/android_device_motorola_msm8226-common/tree/aex-new

Vendor tree:=https://github.com/RenanQueiroz/proprietary_vendor_motorola/tree/lineage-16.0

Kernel Source:=https://github.com/RenanQueiroz/android_kernel_motorola_msm8226/tree/lineage-16.0
[Android] gipsy.danger:
let me know if you find the solution.
[Android] ParanoidNemo:
Getting this right at the start from porting POSP for suzu (Xperia X). I'm following the instruction founded in their github repo so I really am at a loss.

ROM source and instruction:= https://github.com/PotatoProject/manifest

device tree:=https://github.com/sonyxperiadev/local_manifests

Error I get:=https://hastebin.com/okeyaveziv.coffeescript

Any help is much appreciated.
[Android] DiamondJohn:
re-check that you have performed all the device changes specified in their instructions. ie
[Android] ParanoidNemo:
Checked at least a couple of times before posting here. I don't know if I'd done it wrong but I have copied my file.mk then rename it potato.mk and made the changes. Also tried not renaming it and maintain that AND the original potato.mk. same outcome and same identical error.
[Android] DiamondJohn:
Check the device setup of an official device for the ROM. Historically, most of the ROMs I have compiled have had the pattern of make files; with changes to the product name within the make files and the vendor include etc etc:

Android.mk
AndroidProducts.mk
BoardConfig.mk
device.mk
[B]full_ks01ltexx.mk[/B]
[B][COLOR="Red"]havoc_ks01ltexx.mk[/COLOR][/B]

The above is for a Havoc-OS ROM, but you can see how the make file aligns to the ROM name and the device name. Yours may be different, and their instructions actually explicitly tell you such. But I repeat, the way I normally check the above when converting to another ROM is to check an official device. Also check the change log on official devices, you may find an actual example where a dev has explicitly gone through the steps to convert say a los device tree to an official device for your ROM.
[Android] NepoRood:
Did you add the lunch combo? It's not listed in your pasted error, you could also try this:

brunch potato_f5121-userdebug
[Android] roshan2989:
HI guys..im buidling Lineage Os for my device..how to replace trebuchet with Lawnchair?

i need to add prebuilt in vendor then how about the Quickstep..?any suggestion,help would be appreciated
[Android] ParanoidNemo:
Yes I'd added it to lunch combo. Tried your suggestion but same error.
[Android] NepoRood:
Then you need to push your current working trees to Github, so we can see exactly what you're working with
[Android] ParanoidNemo:
Will do as soon as I can (tonight/tomorrow) and then link it here. Thanks

--EDIT--

[MENTION=7237874]NepoRood[/MENTION] I've a little doubt regarding what you need. I'd only made the change descripted above, the tree is the POSP backed tree with sony xperia aosp local manifest on top of that as linked before. Please give me more info in what to post if that's not enough.
[Android] NepoRood:
Just your device tree (from your local manifest, but with your changes), and common tree, if you have one. No need for vendor or kernel trees. If the env can't find a config for your device, then something is wrong somewhere.
[Android] ParanoidNemo:
Ok thanks. Will do and link this evening.

--EDIT--

[MENTION=7237874]NepoRood[/MENTION]

here the device tree and common tree. I'm linking the one from sony aosp local manifest because I didn't have done any change to those. Following the POSP guide linked earlier it didn't mention anything like that in the device tree but only in their potato tree. (as mentioned before). Sorry if I'm missing something but really I'm trying to understand how to move into this kind of things but haven't really found a good guide/manual to start with.

Thanks for your time.
[Android] NepoRood:
Ok, now we are getting somewhere, not far, but somewhere. Those are the trees that the POSP guide are referring to making changes to. You need to fork those trees to your own github account, when you've done that, I can show you better what you need to do :good:
[Android] ParanoidNemo:
Thanks a lot, really.

Ok so I've forked those on my github account. Also forked device-sony-loire (the platform for my device), I don't know if is needed but anyway.

common tree:= https://github.com/ParanoidNemo/device-sony-common

device tree:= https://github.com/ParanoidNemo/device-sony-suzu

platform tree:= https://github.com/ParanoidNemo/device-sony-loire
[Android] DiamondJohn:
I dont know if the following is your issue, however, the file https://github.com/ParanoidNemo/device-sony-suzu/blob/master/aosp_f5122.mk has an include to https://github.com/ParanoidNemo/device-sony-suzu/blob/master/aosp_f5121.mk

Within aosp_f5122.mk you are setting "PRODUCT_NAME := aosp_f5122" and in aosp_f5121.mk you have "PRODUCT_NAME := aosp_f5121". I wou;ld also expect that to be more like aosp_potato or you need to build aosp_f5121 or aosp_f5122

also look at the following to see what others have done to change a device tree

https://github.com/AOSPA/android_device_asus_tilapia/commit/9a8c10ad31d333918b80b3939f285f9bbc4df6a6

https://github.com/AOSPA/android_device_asus_grouper/commit/9ba01baaa5746cedc2732f35355491317100ccc7
[Android] savsir:
Hi guys. I tried build havoc 3.0 on mi 9. Phone boots up but no sim and power off immediately.

Source codes

https://github.com/Demon000/device_xiaomi_cepheus

https://github.com/markakash/vendor_xiaomi_cepheus

https://github.com/markakash/device_xiaomi_sm8150-common

https://github.com/markakash/kernel_xiaomi_sm8150
[Android] ParanoidNemo:
Thanks for the reply, but that shouldn't be the issue because f5122 is the dual sim variation of the same phone and generally aosp_f5122 add only the dual sim support so right now is not my case because I would start to build for f5121. Also AndroidProducts.mk in POSP tree seems to contain only the code for building unbundled apps and nothing more and my device tree AndroidProducts.mk already contains the right targets.
[Android] AndDiSa:
I have a question to the experts here in XDA: Currently I am trying to port Lineage-15.1 onto the BQ Aquaris X5+ it's building fine but unfortunately it's in a bootloop when starting, i.e. there is the boot animation, but it never ends. It does also not ask for the decryption pattern :(

But the biggest issue for me: I cannot get any information what might be the issue. ADB is not started yet so I don't get a logcat, rebooting afterwards into recovery does not provide last_kmsg nor pstore info ...

Would be great if anyone here could help me to get some light into the dark?
[Android] gipsy.danger:
you can get logcat when its bootlooping.
[Android] AndDiSa:
as I already wrote: adbd is not yet started, i.e. it's in a very early starting phase.
[Android] gipsy.danger:
when bootlooping just connect your device and run adb logcat.
[Android] AndDiSa:
... would be great if you could explain me how ADB logcat works without adbd started on the device ?
[Android] quake73:
Search for 'ramoops' and how to set it up
[Android] alphamale:
Trying to build crdroid for taimen. Getting following error

https://del.dog/aqumopeguh
[Android] quake73:
I was getting similar errors if I tried commenting the lines that inlcude sepolicy in the device tree.
[Android] DualJoe:
nvm
[Android] ParanoidNemo:
Tried to create the potato.mk file into my device tree but always getting the same error:

[url]https://hastebin.com/okeyaveziv.coffeescript
[Android] NepoRood:
I've been swamped at work, push your changes and I'll look at your trees again. Did you try adding potato.mk to AndroidProducts?
[Android] ParanoidNemo:
No problem, I was just asking generally it's really not a problem if you couldn't. I haven't tried yet but I will and report other then pushing my changes. Thanks a lot to help me in your free time.

--EDIT--

Ok [MENTION=7237874]NepoRood[/MENTION] I've added it to AndroidProducts.mk but I've the same error again.

Pushed my changes in the android-device-suzu, p-mr1 branch (HEAD for the specific repo was detached so I've pushed on the one I was pulling from, hope is right).

https://github.com/ParanoidNemo/device-sony-suzu/tree/p-mr1
[Android] zDemoox:
Hello! I'm getting lots of errors while installing all the building tools, just after installing java. Every package seems to be unable to be located

Is there a fix?
[Android] NepoRood:
If you're head is detached, checkout a branch:

git checkout p-mr1

That will put you on track with Github.

That aside, looks like you have done everything right. After your changes, did your source your environment again?

source build/envsetup.sh

And remember to add the lunch combo before brunch:

add_lunch_combo potato_f5121-userdebug
[Android] ParanoidNemo:
Yes, after the changes I've redone everything again (source build/envsetup, add_lunch_combo) and only then brunch, but nothing changed. Always the same error. I'll try to reach for the developer of POSP if you have no other advice and see if they can help me.
[Android] NepoRood:
Only other thing I can think of is to rename "potato.mk" to "potato_f5121.mk" and be sure to change it in AndroidProducts.mk

This is easy enough with GUI, just right click and rename. If you're using CLI (terminal) do this:

mv potato.mk potato_f5121.mk

I'd also recommend creating a "vendorsetup.sh" file in you device tree that has your lunch combo in it already, that way you don't have to type it every time.
[Android] NepoRood:
Trim some fat, you're overcrowding the system partition....
[Android] dungphp:
Please help me this errors ?

Thanks
[Android] NepoRood:
If you're using the packages from the OP of this thread, they're outdated, just get them from Google:

https://source.android.com/setup/build/initializing#setting-up-a-linux-build-environment
[Android] ParanoidNemo:
Will try that. Is the same think I was wondering about. Maybe the guide is outdated or imprecise. Thanks again.

--EDIT--
[MENTION=7237874]NepoRood[/MENTION] It worked! Now I've a new error right at the start of the build but before posting it here I'll try to solve it on my own and learn something. Thanks a lot.
[Android] alphamale:
Trying to build msm xtended 10 for taimen. I get bootloop. https://del.dog/oxuqafulaf
[Android] nitin.chobhe:
See lines 1002 to 1014... Some permissions are missing. Refer colt OS device tree and see how you can allow those permissions.

Nitin
[Android] zDemoox:
I tried to build RevengeOS for sagit, but the build fails after a bit, no error displayed

https://del.dog/afatehoteb

I think it is related to the kernel, since it spews out warnings about, but i do not know how to solve the issue
[Android] NepoRood:
Looks like your pre-built kernel binary is missing, either fix it up to build in-line or add the pre-built
[Android] zDemoox:
Thanks for the reply, can you help me out in doing that (maybe in DMs so we don't spam here)? This is my first build and I'm not very familiar with commands and I do not want to mess the project up :) Thank you again
[Android] zDemoox:
I managed to get rid of that error and now i'm left with this, anyone can help? error here

This is my device tree: https://github.com/Clashkid155/lineage_device_xiaomi_sagit

This is my vendor: https://github.com/xiaomi-msm8998/vendor_xiaomi

and this is my kernel: https://github.com/xiaomi-msm8998/kernel_xiaomi_msm9889
[Android] alphamale:
Not sure I follow. Only thing I added was gapps. Any thing you know of that can be safely removed
[Android] andybones:
I am not 100% sure but it's saying that it found:

Branches found:

cm-13.0

cm-14.1

It's almost as if lineage16 isn't synced, but confused about the errors.

also maybe try renaming from local_manifest to roomservice.xml

another thing which isn't the cause of error, but refer here for the full roomservice.xml

https://github.com/Fagyi/local_manifest/blob/lineage-16.0/local_manifest.xml

you shouldn't have to edit anything IIRC with fagyis sources on lin16, should be a repo sync, then I believe it builds without error, or should.

I would possibly redownload the source?

you can also try this to save a little space:

repo sync --no-tags --no-clone-bundle

and I find it easier to just combine to one line to build:

. build/envsetup.sh && brunch pme

Wish I had more answers.

not sure why this is getting denied either

fork/exec /tmp/go-build619979590/b001/exe/microfactory: permission denied

google has a few pages referring to it however. could be the distro, but idk
[Android] NepoRood:
Which GApps are you using? I had this issue not too long ago on Marlin/Sailfish, which has smallest of system partitions. Built fine without the GApps, so had to trim down some of the packages.
[Android] alphamale:
Yes same issues builds without. Tried two different pixel gapps pixeldust and dirty unicornns and I get the error. I increase system img size and it builds, but I got error in twrp.

---------- Post added at 03:07 PM ---------- Previous post was at 02:40 PM ----------

Can you advise what's safe to remove?
[Android] DiamondJohn:
I didnt read your history of what ROM, but apps are a good place to start.Things like Music Players, AudioFX, File Managers (outside of "files" that is), Calendar, Email App, Browser etc etc ie things sitting in /system/apps and that can be replaced with non system apps and/or apps from the google store or F-Droid etc. Also check you are not building an ODEX'd ROM (ie ODEX files on system instead of on cache when first booted, I always get confused between odexed/deodexed :silly:). Just a few of ideas. HTH
[Android] NepoRood:
Pretty sure Taimen uses "system/product" too, so you can check to see what's being built into the product folder of system. [MENTION=5417899]DiamondJohn[/MENTION] gave a great list to start with
[Android] DiamondJohn:
Actually, I just realised, you do not appear to have fully answered [MENTION=7237874]NepoRood[/MENTION] 's original question. Try cutting back to the min GApps in your build.

Another question, if you build without GApps, does it work if you flash min GApps?
[Android] alphamale:
I've tried removing packages from gapps still got error using pixel gapps from du and pixeldust. Yes flashed without gapps in line. When I flashed open gappspico in twrp I get an error 20 code and my data gets wiped
[Android] NepoRood:
This is the smallest, most up-to-date GApps repo I know of: Link

Very minimal (based off Lineage Mind the GApps)

Have you tried sideloading, instead of using TWRP? I've got the Pixel 3 XL and TWRP doesn't work at all, we've been sideloading our ROM builds with the stock recovery. You can't use the recovery from Factory images, has to be the one compiled in your build. So, like this:

# I open a terminal in my out directory:

1) Reboot to bootloader

2) fastboot boot boot.img (this is the one you compiled, to make sure it boots)

# IF it does boot, continue, if it doesn't, you can stop here

3) fastboot reboot bootloader

4) fastboot flash boot boot.img --slot all

5) fastboot reboot-bootloader

6) select Recovery from the menu and press power

7) sideload update from ADB

8) adb sideload name_of_the_package.zip

9) reboot

You should be able to flash all the zips you want, including GApps...
[Android] Himan99:
Please help developers i have recently purchased Rog phone 2. what a wonderful device and i want to develop coustom Roms and Custom kernel for my device.

Asus release the kernel source code of Device.

How can i build the custom kernel which is overclock CPU and GPU for more intense performance.

Also i want to port oxygen os of 7t pro which has same chipset for my Rog phone 2

Developers please help me
[Android] DiamondJohn:
I am building Havoc-OS Q. I can get it to build, but there is one small step I do which I would guess there is a better way to resolve. Near the end (>95%) I get the error

FAILED: /home/diamondjohndroid/android/havoc_os_q/out/target/product/ks01ltexx/ramdisk-recovery.img
/bin/bash -c "lzma -f -c < /home/diamondjohndroid/android/havoc_os_q/out/target/product/ks01ltexx/ramdisk-recovery.cpio > /home/diamondjohndroid/android/havoc_os_q/out/target/product/ks01ltexx/ramdisk-recovery.img"
"lzma" is not allowed to be used. See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
14:50:12 Disallowed PATH tool "lzma" used: []string{"lzma", "-f", "-c"}

After searching for the resolution I found https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools which gives the temporary fix of

Which works.

However, what is the actual fix? I am guessing it has something to do with the file mentioned in the above link.

Is it a simple

sudo apt-get install lzma

or liblzma-dev?
[Android] AJ:
is there a flag to get it to build for android 10 aosp , or is it 9 only ?
[Android] NepoRood:
This commit from Lineage was just added today, probable fixes the issue, Link

Give Havoc a minute, or pick it yourself to see :D
[Android] NepoRood:
Yes, you can use it for 10, just add it to your device makefile, like the example below:

$(call inherit-product-if-exists, vendor/gapps/arm64/arm64-vendor.mk)
[Android] quake73:
Adding "lzma" in the allowed list here:

build/soong/ui/build/paths/config.go

should fix it.
[Android] lennon86:
[SOLVED] Cannot get Fagyi's LOS16 on HTC10 to make it thru lunch!

https://xdaforums.com/showpost.php?p=80854181&postcount=9751
[Android] DiamondJohn:
Yep, thats the change that fixed it. ie added at line 96 of build/soong/ui/build/paths/config.go

"lzma": Allowed,

FYI [MENTION=7237874]NepoRood[/MENTION] , the change you suggested already appeared to be in the Havoc-OS source.
[Android] tribual:
Hi!

Have a question, hope it also belongs here, or anyone knows a better community to ask:

Have 2 build PC

1. Server with dual xeon 8x2 GHZ

2. PC with i9 9900k 16x5,2 ghz

On both i build same rom for same device with same trees and same commands

No.1 has 100% usage for all cores

No.2 only uses one core at a time, and switches the core all few seconds

Why No. 2 not uses all cores at the same time like no. 1?

Already changes distro withou luck, and also searched all bios setups, no luck also...
[Android] DiamondJohn:
My vague understanding is that its ninja that controls how many threads are run in parallel. I would guess that either the single threaded one is running without ninja or it is somehow configured to only run a single thread.
[Android] Louis1977:
help please,...

https://del.dog/ugusejifaz
[Android] ArcherTanu:
Im using ruzen 2700x some times ninja uses single thread but most of the time it alaways 100%.. Btw how much time takes to compile while ur using 32gb ram.
[Android] adinechin:
Hi to all, I have 3 bugs on 2 different ROMs I'd like to share with you for some help and pointers:

First ROM is LineageOS 14.1 (Nougat)

First bug is a problem with the notification led color, it is not changing according to the configuration in parameters when charging the battery, can you tell me where to look ?

Second bug is quite specific but I don't know how to get proper logs or to solve it : when the battery is low, the GPS is on and the screen is unlocked, if I plug the charger the phone switches off immediatly. The logcat does not give anything...

Second ROM is Lineage 15.1 (Oreo) : I have a stereo sound that is not centered. Some testers said to me that the bug did not occur with another ROM I made with the same device source, so perhaps a ROM problem but I don't know where to look...

Thanks for your help !
[Android] DiamondJohn:
On a "random" reboot, the place to check is in your last_kmsg.
[Android] DiamondJohn:
A lot of people (including myself) have been experiencing poor GPS on a lot of ROMs. I even tried flashing a stock ROM onto my device, and it too had poor GPS.:silly:

I recently received a PM regarding an old device I used to build ROMs for, and the user mentioned something I have never heard of before. He talked of a "GPS Week Number Rollover". When I searched on it, I came across the following WiKi entry.

https://en.wikipedia.org/wiki/GPS_Week_Number_Rollover

Although it does appear to be specific to Time (ie not positioning) I do wonder if it has any effect on our positioning issues? I do note there is an ms since 1970 parameter, in one of the gps code files in my ROM.

The thing that really stands out is that my phone will connect to 10+ satellites, but still not manage to get a fix.:mad:

I did a search on github to see if there were any commits regarding the issue, but did not find any.