yashsingh1/xdaforums huggingface dataset:
[Android] tech mashido:
Got error while compiling rom using ScriBt guide

Hi i am trying to build xenonHD rom for my phone zuk z1(ham) with the help of your Projekt ScriBt guide..

after entering ROM's id and branch n other stuffs it says "TeamHorizon repo initialized/initiated (don't remember exact word ) in /xenon " then autobot says local_manifests folder has been created" then it asks for create local_manifest.xml file" but i did not find above folder

and as you suggested (in one of the user's reply) to take help from jackeagle's guide to create this file... so i created local_manifest.xml file in /xenon/.repo (as that guide suggest) ..then synced sources again then hit on "pre-built" ..after giving device codename,vendor name and build name (as bot suggested to give).....i get this

[?] Choose your Device type among these. Explainations of each file given in README.md

[!] For Phones : If you don't find common_full_phone / common_mini_phone then leave this field blank

BuildSystem would consider the Device as a Phone.

[>]

================================================== =======

[!] xenonhd-fying Device Tree...

===========================================

[!] Initializing Build Environment

including vendor/xenonhd/vendorsetup.sh

including sdk/bash_completion/adb.bash

including vendor/xenonhd/bash_completion/git.bash

including vendor/xenonhd/bash_completion/repo.bash

===========================================

[!] Done

[!] Creating Interactive Makefile for getting Identified by the ROM's BuildSystem...

ROM.sh: line 473: cd: device/zuk/ham: No such file or directory

stuck at above line ...

so what should i do now?

do i need to manually create "local manifests" folder in /xenon then move that local_manifest.xml file to this folder then i need to sync sources again then hit pre-built ???

because when i look at /xenon/device and /xenon/vendor folder then i don't see my phone related files/folders /device/zuk/ham and vendor/zuk ....also i don't see kernel folder
[Android] Arvind7352:
If you haven't done what you've said in the last line, then do that.

And the folder's name is 'local_manifests', not 'local manifests'

From what you have said, looks like the local_manifest.xml has been placed inside .repo and not inside the folder i said, so the Repositories mentioned in that XML weren't synced, and you've got this Error.
[Android] jogai:
But if CM-based roms are available? Can we use ScriBt to port to other cm-based roms? For example: https://github.com/search?utf8=✓&q=zte_nx510j&type=Repositories&ref=searchresults / https://wiki.cyanogenmod.org/w/Nx510j_Info
[Android] Arvind7352:
You mean if you have the Device Sources, and want to build among these ROMs with the help of ScriBt, then Why Not ?

It's Possible. Do it. ;)
[Android] tech mashido:
i have synced the sources and it says

"

[?] Provide me the Synced Source's Location from /

[>]

"

so i have to enter just below mentioned url as it is or is there any format for that ?? in my case url is

https://github.com/TeamHorizon/platform_manifest.git -b n

---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------

sorry that was just a typo...i meant for local_manifests only instead of local manifests
[Android] Arvind7352:
Initializing a ROM Repo is just one-time step.

You can directly start off with sync next time.

The Prompt you answered incorrectly can be explained by this scenario

You have a ROM's source completely synced, suppose the name is R1. Now, you want to sync another ROM 'R2', but you don't want to waste your Internet Bandwidth on syncing 'R2'. Here, repo's great function, the --reference comes into the picture

Now, In ScriBt,

First prompt asked is Whether you have a Reference ROM Source already synced -> You'd answer y

Second prompt asked is to Enter the location of the Reference ROM R1 -> You'd enter the location of the ROM R1's Source in your PC (Not the GitHub URL)

Doing this would search for matching repositories on R2 with R1, and use the R1's sources instead of re-syncing a new one.

This SAVES Bandwidth considerably.
[Android] tech mashido:
ohk..thanks....as you suggested in previous post so i moved that local_manifest.xml to /xenon/local_manifests folder but it says

[!] Initializing the ROM Repo fatal: manifest 'default.xml' not available fatal: remote github not defined in /home/rajveersandhu171/xenon/.repo/manifests/default.xml [!] TeamHorizon Repo Initialized ========================================================= mkdir: cannot create directory ‘.repo/local_manifests’: No such file or directory [!] A folder "local_manifests" has been created for you. [!] Create a Device Specific manifest and Press ENTER to start sync

i sent you a PM please reply there also ...
[Android] EatBeans:
Thanks for this! Could you maybe add CypherOS?
[Android] felipeiank:
Hey congratulations for your work! Will it has Miui 8 support? I'd really appreciate if you support this rom because it's unique and not only a Cyanogen-ish rom
[Android] Miustone:
Do i need the Key packages from the Google Link to get ScriBt working? (Python, GNU Make, GIT?)

Would be great if ScriBt could check for the given requirements and to leave a hint if something is missing...

I can't get it to working correctly :/
[Android] minz1:
I keep getting this error whenever I try building. MSM8929 isn't even used in this.. my device is MSM8939. [IMG="Bug"]http://imgur.com/a/21Brb[/IMG]
[Android] Arvind7352:
Yes. Just run ScriBt and Go to Tools -> Install Build Dependencies

It'd install all these packages.

ScriBt requires a Bash shell, that's all. If you had any problems, share it here. :)
[Android] kenymccornick:
Hey there! This is awesome! I saw in the readme you mentioned that it's possible to build Nougat without jack, but I've having issues with jack and disabling it just ends up in a failed build as soon as it hits the first Java file. would you mind telling me how to get it to compile Nougat without jack (with scribt and without it)? in my case I'm trying to compile GZR Tesla. Thanks a lot in advance.
[Android] minz1:
Whenever I try to build the rom, I get an error here:

define print-vars
$(foreach var,$(1), \
$(info $(var):) \
$(foreach word,$($(var)), \
$(info $(space)$(space)$(word)) \
) \
) \
endef

The error is:

build/core/definitions.mk:115: *** missing 'endef', unterminated 'define'. Stop.

Any help?
[Android] Arvind7352:
I've put that up as a theoretical way of Building Android (Didn't check it's feasibility). People have suggested that Nougat doesn't get built without Jack.

I'd update the Documentation after i get a confirmation from other Developers...

From the code you've shown...

There's an extra backslash on the second last line of your code (I've highlighted it in your quote, in this same post). On Comparison with CyanogenMod's Build repo

Remove it.

One more thing. Build Errors cannot be solved here, there are other threads in Chef-Central, a request.
[Android] minz1:
Okay. My bad, I didn't know where to post this. Thanks for helping anyway!
[Android] Arvind7352:
ScriBt updated to v1.35

Changelogs updated in Post #3

Thanks [MENTION=5782468]tech mashido[/MENTION] for repeatedly reporting about an issue with Pre-Build. His issue has been fixed with this update.

The Issue is mentioned in Changelog of ScriBt v1.35

v1.35 onwards, ScriBt will update itself with a prompt from user.

But, you need to clone (re-clone) ScriBt v1.35 for the first time. OR perform these commands inside the Script directory

git reset --hard; git pull origin master

This would pull the latest changes, you'd be on version 1.35

A Good News!

Thanks for the overwhelming response on this Project.

Under a week, I've observed over 100 unique cloners (users)under it's First week of Release. Number of clones went above 170.

I'd share the pictorial chart ASAP.

#HappyScriBting
[Android] NZnewbie:
HI,

Is there a slightly more noob friendly instruction page ?.

Thanks
[Android] Arvind7352:
This is the best I could do. Now it totally depends on your interest to read it. :)

Thread is still in the Editing stage, but contents won't be changed by much, and people using this didn't report an issue in understanding. So I assume it to be alright.
[Android] NZnewbie:
Mmm, i dont think my hangovers helping me out.

Will look another day :good:
[Android] jogai:
Is it okay to request extra roms here? Or do we have to contribute via github on the ROM.rc file? How do we know what roms are possible to build with this toolkit?
[Android] canteo:
device's codename? what should i answer? i got an angler and synced candy...

i answered common_full_phone, common_mini_phone

but at Company/vendor had tried with angler, huawei_angler, nexus 6p.....

before i had build some roms, iḿ a noob with a little experience, but i can pass the prebuild

[?] What's your Device's CodeName

[!] Refer Device Tree - All Lowercases

[>] common_full_phone, common_mini_phone

[?] Your Device's Company/Vendor

[!] All Lowercases

[>] angler

[?] Build type

[!] [userdebug/user/eng]

[>] user

[?] Choose your Device type among these. Explainations of each file given in README.md

[!] For Phones : If you don't find common_full_phone / common_mini_phone then leave this field blank

BuildSystem would consider the Device as a Phone.

0. common_full_phone

1. common_full_tablet_wifionly

[>] 0

=========================================================

[!] candy-fying Device Tree...

ROM.sh: línea 526: [: /home/canteo/script/device/angler/common_full_phone,: se esperaba un operador binario

===========================================

[!] Initializing Build Environment

including device/generic/mini-emulator-arm64/vendorsetup.sh

including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh

including device/generic/mini-emulator-mips64/vendorsetup.sh

including device/generic/mini-emulator-mips/vendorsetup.sh

including device/generic/mini-emulator-x86_64/vendorsetup.sh

including device/generic/mini-emulator-x86/vendorsetup.sh

including vendor/candy/vendorsetup.sh

including sdk/bash_completion/adb.bash

===========================================

[!] Done

[!] Creating Interactive Makefile for getting Identified by the ROM's BuildSystem...

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binari

ROM.sh: línea 445: [: device/angler/common_full_phone,: se esperaba un operador binario

ROM.sh: línea 473: cd: device/angler/common_full_phone,: No existe el archivo o el directorio

any help? thanks in advance...
[Android] Arvind7352:
Empty post.
[Android] Arvind7352:
No issues.

Device Codename is more of a Nickname, it is easier to Implement and make use of in it's Source code by the Developers. It's a Single word.

Huawei Nexus 6P has the Codename angler and is manufactured by the company/vendor huawei

Build-Type describes the extent of availability of Developer-Specific Tools and Configurations.

According to source.android.com

user - limited access; suited for production

userdebug - like "user" but with root access and debuggability; preferred for debugging

eng - development configuration with additional debugging tools

Among these types, userdebug is the most used build-type by Custom ROMs. eng is mostly a alpha version of Android, and is used for Initial Source bring-up (Getting the source ready).

For Device Type, you've entered the correct response, although give it a read HERE If you haven't.

A Secondary note, just in case if your post becomes too long by ScriBt's suspected erroneous output, then paste those contents to a paste service like pastebin.com or hastebin.com
[Android] S3-747m:
Will it run on a Raspberry Pi 3? I am willing to sacrifice a couple microSD cards...
[Android] jogai:
Dont quote whole start post, but read it. There is a link to the requirements: https://source.android.com/source/requirements.html
[Android] chintu1234:
I.m getting an error in prebuild after i put up my device name

here is the log

http://pastebin.com/TTN6Mwch

and this is my device tree for oneplus2 in slimroms

https://github.com/SlimRoms/device_oneplus_oneplus2

please can you check what i have done wrong???
[Android] Arvind7352:
You've entered an incorrect answer for 'Codename' prompt...

I've explained the meaning of Codename, Two posts above.

Codename for OnePlus 2 is oneplus2
[Android] chintu1234:
yeah i tried that too and it gives the same error

here check this out same error: http://pastebin.com/jUMj4XwF
[Android] Arvind7352:
Check if the Device Tree exists. Most Probably you have incompletely synced the tree, sync it again.
[Android] chintu1234:
Ok i checked.

For my oneplus 2 there is two branches mm6.0 and ng7.0

But i have synced slimroms to only include ng7.1

Should i have synced other branches too? But i only need a 7.1 rom.
[Android] AndroidBeginNinja:
I get this error a lotmkdir: cannot create directory â€˜.repo/local_manifestsâ€™: No such file or directory

[!] A folder "local_manifests" has been created for you.

[!] Create a Device Specific manifest and Press ENTER to start sync
[Android] Arvind7352:
That can be ignored, that happens when the command tries to create a directory which has been already created
[Android] Arvind7352:
[!] Update - ScriBt v1.38

[!] Changelogs

* 1.38 - https://github.com/a7r3/ScriBt/commit/2d627e0a331942f964dc52722e56d8624970f3d9

* 1.37 - https://github.com/a7r3/ScriBt/commit/85d6a158002c8f128608ae6b613aaf3d9f835c13 - by GitHub user systemcrash

* 1.36 - https://github.com/a7r3/ScriBt/commit/c33b581bc84c3d1af73773e8f063aa69655f7514 - by [MENTION=7693041]CubeDev[/MENTION]

Thanks GitHub user Rahh1112 for Reporting an Issue with Distro Detection, and systemcrash for correcting my Grammer Grammar in README.md

[!] Notes:

1. New Implementation of Distro Detection. ScriBt will detect Distros with their name and version, and download the packages according to their Year of Release.

OSes supported are : Ubuntu, Ubuntu Flavors, Linux Mint, Elementary OS, and Zorin OS.

2. Fixed a minor issue in Init -> Code which adds ~/bin to PATH was incompletely echoing the statements.

#HappyScriBting

EDIT:

[!] Update - ScriBt v1.39

[!] Changelog for v1.39 : 312f19
[Android] chintu1234:
Ok i passed the pre-build but now i get this error about some syntax when using non ninja build: http://pastebin.com/FCSQeNBD

i also got an error with ninja build but i did not save the error logs for it.

this is my local manifest

i used

0 no of makefile calls

use make instead of mka

1 job

y for jack toolchain

n for ninja
[Android] -->:
Is arch linux supported?
[Android] kirito9:
Yes, clearly says so on the first post.
[Android] jogai:
Yes, but here: http://xdaforums.com/showpost.php?p=69874305&postcount=62 its not included in the list

However, when I tried v1.34 on bbq linux (arch based android building distro) it seemed to work.
[Android] kirito9:
Should've tried first then report after ;).
[Android] Arvind7352:
Supported OSes are for Distro Detection (the new and current method which I implemented), not ScriBt's compatible OSes.

Please read the OP before asking.

ArchLinux has a different way of installing Packages, so it wasn't involved in this Problem.

To make it clear, ArchLinux is supported. (It's mentioned in the OP too)
[Android] -->:
Sorry, looks like i didn't read everything carefully :p
[Android] Arvind7352:
That error is related to build time, I don't think it should come up, but I'll look into it.
[Android] S3-747m:
Ah... Let's see... (I don't have 15 minutes to read it all, but interesting...) AAAGH! NO ARM SUPPORT!

...Great. Back to my Windows XP 1280x800 single-core laptop with VirtualBox 5.1.11.0.

:(

No Windows XP or Vista, can't run 7, or anything higher, is Ubuntu good for 2.5GB of DDR2, 1.86GHz Pentium M 750, and a Intel 915GM without shaders?
[Android] Arvind7352:
Ubuntu can run (there are some Low-End Alternatives), but building Android couldn't be feasible.

You can go for a Google Cloud Trial, tutorial to set it up is HERE

[MENTION=4406061]chintu1234[/MENTION] The Build time problem has been fixed, misplaced a line (maybe in previous commits), would be up on ScriBt v1.40

The Build Error is irrelevant to ScriBt though.
[Android] chintu1234:
Ohh ok thanks, and i figured the error must also be because i synced my device, vendor and kernel tree from local_manifest from other github links so i think i need them to link it to the make files to make it work.
[Android] Arvind7352:
[!] Update - ScriBt v1.40

[!] Changelogs

v1.40 :

cbee47

Added Nexus-Only ROMs - PureNexus, Krexus, and Nitrogen OS

These ROMs can only be built for Nexus ( or Non-CAF ) devices, so please choose among these only if you have a Nexus Device. Information about the same is mentioned in ScriBt

Fixed some minor issues, read commit message.

Another Good News, the number of Daily cloners are 8-13, which is the great usage response I could get!
[Android] Miustone:
Thanks for the Updates Mate!

I want to try it again now after reading the Changelog. But idk. how to run ScriBt from My HDD instead of running it from My small SSD (About 30Gb free). Is there a easy Way to do so? If not, can i reduce the Size of the Downloaded Sources to a minimum that i can use My SSD? Thanks in advance and sorry for this Noob Question!

BR :)
[Android] Arvind7352:
Describe your System

> Operating System

> Space Available

> Partitions in which you can place the Source

Below is the Pic showing the Size of various parts of the Source

From left to right

Size of .repo -> Size of Checked out Source -> Size of Temporary directory (/out)

This was for Marshmallow source (TipsyOs)
[Android] Miustone:
Oh right, I'm using Ubuntu 16.04 LTS installed on the SSD and My HDD is empty. SDA (SSD) has 58615704 Blocks at all, and SDB (HDD) has 244198584 Blocks ($ cat /proc/partitions). Hope that's what You wanted to know... :fingers-crossed:

My HDD is empty and My SSD has about the half of the Blocks free. Would be cool to use the SSD but i have Time so i'm fine with the HDD speeds. Just need to know how i can use the HDD..
[Android] Arvind7352:
Run ScriBt wherever you want to start with ROM building. Looking at your Laptop specs in your Signature (Your mentions match those of the laptop), you can run ScriBt and get the ROM built.

ScriBt just requires a Linux PC with Bash shell, and the minimum specifications required to build as mentioned in source.android.com, the Specs mentioned are good enough.
[Android] Miustone:
Ah, now i understand. Great that it is that easy. I had just to "Right-Click" on a HDD Folder Window and opened the Terminal from there, used the Commands from the first Post, and that's it for now...

Is it normal that the CCACHE Options takes a bit long!? I've set it to 50Gb...
[Android] Arvind7352:
Oh, okay. I've reproduced the same issue.

Would be fixed on ScriBt v1.41, thanks for reporting!
[Android] Arvind7352:
[!] Update - ScriBt v1.41

[!] Changelogs

v1.41 : 013c87

*NEW* Guide to make a Custom Manifest has been made in the ScriBt wiki, which is here. Take a look!

Issue with setting up CCache fixed.

Added prompt to assign /out directory to another directory (or drive)

Read commit message for more fixes.

[!] Introducing ScriBt wiki

A new central place for all things ScriBt!

Available here : https://github.com/a7r3/ScriBt/wiki

(Wiki Tab in ScriBt repo)

Every function is explained in detail over there, README.md is now deprecated and is minimal.

Take a note of it.

#HappyScriBting
[Android] HaoZeke:
Hey, I've suddenly been getting this error.... Any ideas?

/run/media/haozeke/Storage/AndBuild/aosp_n/kernel/sony/msm/kernel/Makefile:144: *** No X.509 certificates found ***
AS kernel/system_certificates.o
/run/media/haozeke/Storage/AndBuild/aosp_n/kernel/sony/msm/kernel/system_certificates.S: Assembler messages:
/run/media/haozeke/Storage/AndBuild/aosp_n/kernel/sony/msm/kernel/system_certificates.S:11: Error: file not found: kernel/$
509_certificate_list
make[2]: *** [/run/media/haozeke/Storage/AndBuild/aosp_n/kernel/sony/msm/scripts/Makefile.build:344: kernel/system_certifi$
ates.o] Error 1
make[1]: *** [/run/media/haozeke/Storage/AndBuild/aosp_n/kernel/sony/msm/Makefile:842: kernel] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:130: sub-make] Error 2
[Android] Arvind7352:
Please ask this question in other threads on Chef Central.

This thread is only for my Script. I'd help there if possible.
[Android] HaoZeke:
Oh sure, I'm sorry...

Love the script though, it's great work.. :)
[Android] shubham540:
Sorry for the Offtopic

I want to port CyanogenMod to Samsung Galaxy A8 (SM-A800F), which is based on Exynos 5430 Chipset! Can you help in setting up my build environment and device tree, kernel and vendor files etc etc with the help of your Projekt ScriBT, i am new to all these things, not a developer but i just want to make a effort to port CM to my device by myself!!

Thanks
[Android] Arvind7352:
Porting/Building a Custom ROM for a Device which doesn't have it's Sources isn't that Easy. You need some experience in Device Development Stuff.

If you need a head-start, then start developing a Custom ROM for a Device which has the Sources ready, understand things from these experiences (looong way ahead), and then start Development for a New Device (Or a device whose sources aren't available).

This may take time, but if it is your interest, it would be very useful in Developing it.

ScriBt helps the user by providing it that head-start
[Android] shubham540:
Sources are already available (partially), actually, Samsung Galaxy Alpha (SM-G850F) which is also based on Exynos 5430 Chipset, with almost same hardware specs (except camera's, display resolution and fingerprint sensor) has already got CM13 support (unofficially)! But its developer, is not that of helpful nature, thats why i want to start my own build environment for my own device through ScriBT! :)

Sources= https://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/?h=cm-14.1

Official Sources= http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-a800f
[Android] Arvind7352:
[!] Update - ScriBt v1.42

[!] Changelogs

v1.42 : 4e8055

Rewritten Automation Code. A new way of Automation has been Implemented, take a Look at Features Section of ScriBt Wiki to know more about it.

Simplified Cherry pick, usage again described in Features Section of ScriBt Wiki

Some moar Comments and Enhancements, read the commit message if you're interested to know all the changes

#HappyScriBting
[Android] bigsupersquid:
This.

Appreciate the code. I detest looking up java installation over and over, because the technicalities aren't sticking yet, and the real key is swapping between versions. cm11 won't build with the java cm14 wants, but I have a device stuck on KitKat (ART, whyfor art thou such a **** about running on armv6?).

My optimus V wants maintenance, but I've been concentrating on Marshmallow and Nougat for the last year; trying to hack Lollipop onto the V was a pointless exercise in futility for much of the previous time after KitKat started getting stale.

Now that I'm past the long-winded explanation, thanks for the java version switcher.