No .zip file after successful LinegaeOS 14 gtaxlwifi build - LineageOS Questions & Answers

Hello Friends,
I am new to build LineageOS. Today I have successfully built a gtaxlwifi build but got no .ZIP file that I can use with TWRP in the 'OUT'.
Used Valera1978's "guidelines" of how to build it, can find it here at the bottom of the page.
Sorry but cannot link the page as I am too new to this forum...
Here is the guideline from his page:
Device configuration for the Samsung Galaxy Tab A
Copyright (C) 2017 The LineageOS Project Copyright (C) 2017 Valera Chigir [email protected]
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Description
This repository is for LineageOS on Samsung Galaxy Tab A (gtaxlwifi)
How To Build LineageOS for Samsung Galaxy Tab A
Make a workspace
mkdir cm14 cd cm14
Do repo init & sync
repo init -u git://github.com/LineageOS/android.git -b cm-14.1
Create .repo/local_manifests/roomservice.xml with the following content:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Valera1978/android_device_samsung_gtaxlwifi" path="device/samsung/gtaxlwifi" remote="github" />
<project name="Valera1978/android_kernel_samsung_exynos7870" path="kernel/samsung/exynos7870" remote="github" revision="cm-14.1_perm" />
<project name="Valera1978/android_vendor_samsung_gtaxlwifi" path="vendor/samsung/gtaxlwifi" remote="github" />
<project name="Valera1978/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="Valera1978/android_hardware_samsung_slsi-cm_exynos7870" path="hardware/samsung_slsi-cm/exynos7870" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="LineageOS/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="LineageOS/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
</manifest>
repo sync
Copy proprietary vendor files
There are two options to to that. Connect your device with adb enabled and run:
./extract-files.sh
Or if you have the system image unpacked on your disk, then simply run:
STOCK_ROM_DIR=/path/to/system ./extract-files.sh
Setup environment
. build/envsetup.sh
Build cm14
brunch gtaxlwifi
Can someone tell me what can I be possibly doing wrong?
Many thanks!
D4

_d4Mn_ said:
Hello Friends, I am new to build LineageOS. Today I have successfully built a gtaxlwifi build but got no .ZIP file that I can use with TWRP in the 'OUT'.......
Click to expand...
Click to collapse
I've never built a ROM before but, I believe that the following thread is one of the best places to obtain some member guidance with this.
https://forum.xda-developers.com/showthread.php?t=3551484
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Ibuprophen said:
I've never built a ROM before but, I believe that the following thread is one of the best places to obtain some member guidance with this.
https://forum.xda-developers.com/showthread.php?t=3551484
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the answer, I never found out what the problem is, but managed to work it around.
1.: build with $ make -j4
2.: $ make clobber
3.: $ breakfast gtaxlwifi
4.: rebuild again with $ brunch gtaxlwifi
and voila the zip is going to be there. If I don't do the $ make clobber thing the $ brunch build will never produce the zip.
This is probably due to the lack of my knowledge in this topic, but anyway, it works now.

I faced the same issue.
Compiling using "m" or "brunch" didn't output zip, but mka bacon made it...

Related

[GUIDE][Step-by-Step] Build ROM from source

I put this tutorial together in an attempt to create the most complete and easy to follow guide for building a ROM from source. Including steps for adding apps to your build, changing toolchains and more... The entire guide uses a single Linux terminal window from start to finish in an attempt to keep everything as user friendly as possible. Please feel free to PM me suggestions on where changes need be made.
If you find this guide helpful please press the Thanks button on my posts and rate the thread a 5.​
Prerequisites​1. This guide is for Ubuntu 12+ based machine, I run Linux Mint 15. Follow links at end of OP for alternate directions
Windows Users: Setup Ubuntu in Virtualbox Instructions
2. You need to know the location for your device, vendor, and kernel repos. This can be found fairly easily in the forum for your phone. Also take note of your phones codename.
For example the Optimus G is the gee and its repos can be found here https://github.com/TeamPlaceholder
Note*All terminal commands will be in Code boxes*
Part 1 - Setting Up The Build Environment​
Install Java JDK
Code:
sudo add-apt-repository ppa:webupd8team/java
Code:
sudo apt-get update
Code:
sudo apt-get install oracle-java6-installer
Installing required packages
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Set-up ccache This Is Optional
Code:
nano ~/.bashrc
Add these two lines
export USE_CCACHE=1
export CCACHE_DIR=<path-to-your-cache-directory>
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Install ADB & Fastboot This is optional, as you may already have them working. If not, they're a good thing to have.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Setup Repo
Code:
mkdir ~/bin
Code:
PATH=~/bin:$PATH
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Create working directory
Code:
mkdir [I][B]working-dir[/B][/I]
(Replace working-dir with whatever you'd like to call it, ie. aokp)
Code:
cd working-dir
Part 2 - Get Source​ROM Source
Choose which custom rom you are going to build and initialize the repo for it
Code:
repo init -u [I][B]chosen-manifest[/B][/I]
(Replace chosen-manifest appropriately from the list below)
AOKP: https://github.com/AOKP/platform_manifest.git -b Branch
Cyanogenmod: https://github.com/CyanogenMod/android.git -b Branch
CarbonDev: https://github.com/CarbonDev/android.git -b Branch
Liquid Smooth: https://github.com/LiquidSmooth/android.git -b Branch
Replace Branch with appropriate branch from github repo ie cm-10.2 or jb3
If unsure which branch click the link above to locate appropriate branch
Click to expand...
Click to collapse
Device Source
Go HERE and follow instructions on obtaining your device specific repos.
Sync the repo
Code:
repo sync
This will take a while as it downloads all the required source
Part 3 - Preparing Source​Before you're ready to build your source needs to be configured to include your device. This preparation varies slightly for different custom Roms.
Go HERE and follow instructions for your ROM choice
Part 4 - Edit Source​This Is Optional​This is where you can make edits to the source before building to suit your needs.
Go HERE and follow the instructions to tweak source
Part 5 - Building ROM​
Code:
. build/envsetup.sh
Code:
lunch
Locate your device on the list and enter appropriate number
Code:
make -j[B][I]# [/I][/B]otapackage
Replace # with the number of cores in your system (Is the number of jobs that will be done at once, more cores means more jobs)
Build Errors​
This can be hard, especially if you're new to programming languages and building. Meet Google your new best friend.
Here is a basic overview to get you started, and if no more at least googling in the right direction.
Finished​When it's done you're rom will be in working-dir/out/target/product/codename/
Enjoy.
I used these sites while making this guide
http://source.android.com/source/initializing.html
http://www.webupd8.org/2012/11/oracle-sun-java-6-installer-available.html
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
Device Source​ As stated in the prerequisites you will need a device specific Device repo, Vendor repo, and Kernel repo. You can find links to them in the threads for your devices. Also take note of your device codename ie Nexus 4 is mako, Optimus G is gee.
There are two options for adding in device specific source, local manifest and git clone.
Note: The local path for your phone's repos should be device/manufacturer/codename, vendor/manufacturer/codename, kernel/manufacturer/codename regardless of method chosen.
Git Clone
Git clone is a one time download of a specific repo to the directory indicated and is not affected when a repo sync is run. This is probably the better choice if you make edits to the device source as they won't be over written or cause conflicts when syncing.
This method is used AFTER the inital rom source sync. Preform a repo sync before cloning repos
Code:
git clone [B][COLOR=DarkOrange]repo[/COLOR][/B] -b [B][COLOR=Red]branch[/COLOR][/B] [B][COLOR=Lime]destination-path[/COLOR][/B]
here is and example for the vendor repo for the E973 from TeamPlaceHolder
git clone https://github.com/TeamPlaceholder/proprietary_vendor_lge_gee -b cm-10.2 vendor/lge/gee
Click to expand...
Click to collapse
Local Manifest
Local manifest syncs the device repos each time a repo sync is run. This is probably the better choice if you don't make edits and rely on the repo's maintainer for changes. Be wary making edits locally to the repos you list as a repo sync may overwrite your changes.
This method is used BEFORE the initial rom sync. This gets your device source during the first repo sync
Code:
mkdir .repo/local_manifests
Code:
touch .repo/local_manifests/local_manifest.xml
Code:
nano .repo/local_manifests/local_manifest.xml
Add these lines:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="name-for-remote" fetch="remote-url" />
<project path="destination-folder-path" name="repo-location" remote="name-for-remote" revision="branch" />
</manifest>
Click to expand...
Click to collapse
name-for-remote - Any name you want to give to identify the url where your repos are stored
remote-url - The url for the remote location your repos are stored
destination-folder-path - Where do you want this repo stored locally
repo-location - Where on the remote url is your repo stored
branch - The branch of the remote repo you are using
**You will need a project line for each repo you wish to add to the source. **
Here is an example for E973 using TeamPlaceHolder repos, adding all device/vendor/kernel repos.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gh"
fetch="git://github.com/" />
<project path="kernel/lge/gee" name="TeamPlaceholder/android_kernel_lge_gee" remote="gh" revision="cm-10.2-update" />
<project path="device/lge/geeb" name="TeamPlaceholder/android_device_lge_geeb" remote="gh" revision="cm-10.2" />
<project path="device/lge/gee-common" name="TeamPlaceholder/android_device_lge_gee-common" remote="gh" revision="cm-10.2" />
<project path="vendor/lge/gee" name="TeamPlaceholder/proprietary_vendor_lge_gee" remote="gh" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
Preparing Source
Preparing Source​ROM specific setup instructions prior to building. All source should be downloaded already.
All ROM setup is fairly similar,
1. You must add your device to the ROM's vendor repo(vendor/cm or vendor/aokp) This process is slightly different per rom. Look at how other devices are added in the vendor repo and emulate those.
2. A ROM specific makefile, again look at how other devices are added.
3. If building AOSP based ROMs, a pre-built kernel is generally required. Look here for instructions on how to compile a kernel separately.
Here are examples of how to set up AOKP or Carbon to build. Device used in example is Optimus G.
Manufacturer and codename MUST be updated to reflect your device.
AOKP
Code:
nano vendor/aokp/vendorsetup.sh
Add this line
add_lunch_combo aokp_geeb-userdebug
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Code:
touch vendor/aokp/products/geeb.mk
Code:
nano vendor/aokp/products/geeb.mk
Add these lines
If building for CDMA network change gsm.mk to cdma.mk
# Inherit AOSP device configuration for geeb
$(call inherit-product, device/lge/geeb/full_geeb.mk)
# Inherit AOKP common bits
$(call inherit-product, vendor/aokp/configs/common.mk)
# Inherit GSM common stuff
$(call inherit-product, vendor/aokp/configs/gsm.mk)
# Setup device specific product configuration
PRODUCT_NAME := aokp_geeb
PRODUCT_BRAND := google
PRODUCT_DEVICE := geeb
PRODUCT_MODEL := Optimus G
PRODUCT_MANUFACTURER := LGE
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Code:
nano vendor/aokp/products/AndroidProducts.mk
Add this line
$(LOCAL_DIR)/geeb.mk \
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
CarbonDev
Code:
nano vendor/carbon/vendorsetup.sh
Add this line
add_lunch_combo carbon_geeb-userdebug
Click to expand...
Click to collapse
Once your device has been added you're ready to build! Go back to the OP and complete the guide from where you left off.
good stuff haze
AGREED!!
What bout building ROMs based on LG source? I'd rather see more LG based ROMs because the camera quality is higher, and a lot of AOSP/AOKP ROMs feel more or less the same.
geokilla said:
What bout building ROMs based on LG source? I'd rather see more LG based ROMs because the camera quality is higher, and a lot of AOSP/AOKP ROMs feel more or less the same.
Click to expand...
Click to collapse
Seriously ? Find me LG source to build a rom and I'll make you one.
@moderator.
Btw, This post and the previous should be removed, that thread locked to prevent post like these and pinned. thanks.
Haze028 said:
Well I had put up build instructions for AOKP but thought I would generalize them so people could use them for other ROM bases. My therory is the more people that are trying to build, the more improvments/enhancements can be put forth to the OG community.
As I've stated before I do not consider myself a dev. So don't be afraid of giving this a try, even if you have little to no android building experience. The instructions are as step by step as I could make them, and I'll always try to help where I can.
When it's done you're rom will be in out/target/product/geeb/
I'm writing this now from memory, so if it doesn't work let me know so I may update accordingly
Enjoy.
Click to expand...
Click to collapse
It was what I'm looking for...
Thanks a lot..
Definitely I'll give a try!
chadouming said:
Seriously ? Find me LG source to build a rom and I'll make you one.
@moderator.
Btw, This post and the previous should be removed, that thread locked to prevent post like these and pinned. thanks.
Click to expand...
Click to collapse
Why would want to lock the thread? How do we suppose to learning? I think @Haze purpose was opposite that you suggest, if we do not learn, we'll keeping ask you to change this, or do that instead to help you and even do some nice stuff.
Don't be like that be patience and share your great knowledge. I'm your fan. :good:
d.terenzzo said:
Why would want to lock the thread? How do we suppose to learning? I think @Haze purpose was opposite that you suggest, if we do not learn, we'll keeping ask you to change this, or do that instead to help you and even do some nice stuff.
Click to expand...
Click to collapse
Yeah, I don't think it should get locked, I started it to try to help people out, so they can get assistance through this thread with their builds. Being new to building myself, I have found that the issues, and resolutions to them, in similar threads to this to be a wealth of knowledge.
getting error
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[vendor/aokp/products/geeb.mk]]: "device/lge/geeb/full_geeb.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_geeb'
** Do you have the right repo manifest?
Any idea what i missed?
Recon Freak said:
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[vendor/aokp/products/geeb.mk]]: "device/lge/geeb/full_geeb.mk" does not exist. Stop.
** Don't have a product spec for: 'aokp_geeb'
** Do you have the right repo manifest?
Any idea what i missed?
Click to expand...
Click to collapse
have you cloned the geeb device tree into device/lge/geeb? seems the error is saying that full_geeb.mk doesn't exist, so either you've not yet cloned the device tree, or you have it in a differnt folder name, I'm assuming currently.
let me know if that's not the case.
I know most people want to run latest and greatest but I'm curious if we could build a cm10 (4.1.2) using LG's released kernel sources?
Any thoughts??
Would be cool to get a 4.1.2 build without LG's proprietary software...
Hopefully you see my point in posting this here as building from lg's sources and either aosp or cm10 isn't the most straightforward.
I'm attempting but I don't expect to have much success...
Mate, how long does repo sync takes? I saw something to download about 10gb?
cheers
d.terenzzo said:
Mate, how long does repo sync takes? I saw something to download about 10gb?
cheers
Click to expand...
Click to collapse
It all depends on your internet connection, looking at around 10-20gb. I think my AOKP repo is 12gb...give or take
Haze028 said:
It all depends on your internet connection, looking at around 10-20gb. I think my AOKP repo is 12gb...give or take
Click to expand...
Click to collapse
"Once you know the truth, there is no going back"
for learning purpose:
Why should we have to download all projects in AOKP, if I wont use it.
There is a way to choice between what to download and what to not download?
cheers
d.terenzzo said:
"Once you know the truth, there is no going back"
for learning purpose:
Why should we have to download all projects in AOKP, if I wont use it.
There is a way to choice between what to download and what to not download?
cheers
Click to expand...
Click to collapse
In the third post i show you how to use a local manifest to remove projects you don't want/need from the repo before you sync, linked to in the build instructions. I always remove the device tree and vendor for other devices before my initial sync.
Yeah, I tried that, but I got weird error. Something about manifest, once I removed the example line about Samsung groups, it worked.
Would you mind to share your local_manifest.
Cheers
Sent from my LG-E971 using xda app-developers app
d.terenzzo said:
Yeah, I tried that, but I got weird error. Something about manifest, once I removed the example line about Samsung groups, it worked.
Would you mind to share your local_manifest.
Cheers
Sent from my LG-E971 using xda app-developers app
Click to expand...
Click to collapse
Sorry for the delay, didn't notice your post, anyways here is my current local manifest file for aokp
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/geeb" name="Haze028/android_device_lge_geebca" remote="aokp" revision="aokp"/>
<project path="vendor/lge/geeb" name="Haze028/android_vendor_lge_geeb" remote="aokp" revision="cm-10.1"/>
<project path="kernel/lge/geeb" name="Haze028/geeb" remote="aokp" revision="geeb"/>
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="linux,arm" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" revision="master" groups="linux,arm" />
<remove-project name="AOKP/packages_apps_Launcher2" />
<remove-project name="AOKP/device_acer_a510" />
<remove-project name="AOKP/device_asus_grouper" />
<remove-project name="AOKP/device_asus_tilapia" />
<remove-project name="CyanogenMod/android_device_common" />
<remove-project name="device/generic/armv7-a-neon" />
<remove-project name="device/generic/armv7-a" />
<remove-project name="device/generic/common" />
<remove-project name="device/generic/goldfish" />
<remove-project name="device/generic/mips" />
<remove-project name="device/generic/x86" />
<remove-project name="device/google/accessory/arduino" />
<remove-project name="device/google/accessory/demokit" />
<remove-project name="AOKP/device_htc_evita" />
<remove-project name="AOKP/device_htc_msm8960-common" />
<remove-project name="AOKP/device_lge_iprj-common" />
<remove-project name="AOKP/device_lge_mako" />
<remove-project name="AOKP/device_lge_p930" />
<remove-project name="AOKP/device_lge_su640" />
<remove-project name="AOKP/device_lge_vs920" />
<remove-project name="AOKP/device_motorola_maserati" />
<remove-project name="AOKP/device_motorola_omap4-common" />
<remove-project name="AOKP/device_motorola_solana" />
<remove-project name="AOKP/device_motorola_spyder" />
<remove-project name="AOKP/device_motorola_targa" />
<remove-project name="AOKP/device_motorola_umts_spyder" />
<remove-project name="device/sample" />
<remove-project name="AOKP/device_samsung_aries-common" />
<remove-project name="AOKP/device_samsung_celox-common" />
<remove-project name="AOKP/device_samsung_d2-common" />
<remove-project name="AOKP/device_samsung_d2att" />
<remove-project name="AOKP/device_samsung_d2tmo" />
<remove-project name="AOKP/device_samsung_d2usc" />
<remove-project name="AOKP/device_samsung_d2vzw" />
<remove-project name="AOKP/device_samsung_galaxys2-common" />
<remove-project name="AOKP/device_samsung_hercules" />
<remove-project name="AOKP/device_samsung_i605" />
<remove-project name="AOKP/device_samsung_i9100" />
<remove-project name="AOKP/device_samsung_i9100g" />
<remove-project name="AOKP/device_samsung_i9300" />
<remove-project name="AOKP/device_samsung_l900" />
<remove-project name="AOKP/device_samsung_maguro" />
<remove-project name="AOKP/device_samsung_manta" />
<remove-project name="AOKP/device_samsung_msm8660-common" />
<remove-project name="AOKP/device_samsung_msm8960-common" />
<remove-project name="CyanogenMod/android_device_samsung_omap4-common" />
<remove-project name="AOKP/device_samsung_qcom-common" />
<remove-project name="AOKP/device_samsung_smdk4412-common" />
<remove-project name="CyanogenMod/android_device_samsung_smdk4412-qcom-common" />
<remove-project name="AOKP/device_samsung_t0lte" />
<remove-project name="AOKP/device_samsung_t0ltecdma" />
<remove-project name="AOKP/device_samsung_toro" />
<remove-project name="AOKP/device_samsung_toroplus" />
<remove-project name="AOKP/device_samsung_tuna" />
<remove-project name="AOKP/device_samsung_vibrantmtd" />
<remove-project name="device/ti/panda" />
<remove-project name="AOKP/vendor_htc" />
<remove-project name="AOKP/vendor_lge" />
<remove-project name="AOKP/vendor_motorola" />
<remove-project name="AOKP/vendor_samsung" />
<remove-project name="AOKP/vendor_acer_a510" />
<remove-project name="AOKP/vendor_asus" />
</manifest>
Click to expand...
Click to collapse
Haze028 said:
Sorry for the delay, didn't notice your post, anyways here is my current local manifest file for aokp
Click to expand...
Click to collapse
Hey Haze028, thanks for this great write up!
Anyways, im trying to build this for the Sprint LG OG. Do i need to sync with different device trees then this? Im very new at building from source, so, sorry if this is a stupid question.
Thanks!
eletendre84 said:
Hey Haze028, thanks for this great write up!
Anyways, im trying to build this for the Sprint LG OG. Do i need to sync with different device trees then this? Im very new at building from source, so, sorry if this is a stupid question.
Thanks!
Click to expand...
Click to collapse
I believe you will need different repo's, check out Team LGOG's github(https://github.com/TeamLGOG) They have device tree's for all variants, Chadouming is a member of that team and as such his CM10.1 uses those repo's. The local_manifest for Cyanogenmod in the OP should show you which repo's to use.... then depending on what rom you're looking to build some minor changes might be required.
I've not built using their repo's, but I'll help you in getting it all set up.

HELP on making S4 build for AOSPA

http://forum.xda-developers.com/showthread.php?t=1863547&highlight=signal
Im trying to compile my own AOSPA for the S4
i got a noob question. When I try to # Initialize the ParanoidAndroid Repo i get a error on the terminal that states
/home/joel/bin/repo: line 1: syntax error near unexpected token `newline'
/home/joel/bin/repo: line 1: `<!DOCTYPE html>'
can somebody help me on what extactly im doing wrong. Ive googled it and found nothing that helped out.
jm492705 said:
http://forum.xda-developers.com/showthread.php?t=1863547&highlight=signal
Im trying to compile my own AOSPA for the S4
i got a noob question. When I try to # Initialize the ParanoidAndroid Repo i get a error on the terminal that states
/home/joel/bin/repo: line 1: syntax error near unexpected token `newline'
/home/joel/bin/repo: line 1: `<!DOCTYPE html>'
can somebody help me on what extactly im doing wrong. Ive googled it and found nothing that helped out.
Click to expand...
Click to collapse
I will assume you followed the preceding instructions about installing Python and that it was configured correctly. I would say to "rm -rf ~/bin/repo", which will remove the folder /repo and all its contents... then to start back at #Install the Repo.
lordcheeto03 said:
I will assume you followed the preceding instructions about installing Python and that it was configured correctly. I would say to "rm -rf ~/bin/repo", which will remove the folder /repo and all its contents... then to start back at #Install the Repo.
Click to expand...
Click to collapse
i did what you told me to attempt and still got the same error when try to #Install the Repo. Is there anything else that i can do. i just don't get what im doing wrong because i did it right when i did my own CM build, just attempiting now to make my own AOSPA ROM for the S4.
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where? im confused
jm492705 said:
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where for my specific device? im confused on what to do next. plz help
Click to expand...
Click to collapse
jm492705 said:
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where? im confused
Click to expand...
Click to collapse
I assume there's a better way than mine, but I always go into <your source location>/.repo and edit manifest.xml to include CM's android_device_samsung_jf-common, android_device_samsung_jfltetmo, and android_kernel_samsung_jf. After adding them to your manifest, just do another repo sync and you should have everything you need to start cranking out a build...
lordcheeto03 said:
I assume there's a better way than mine, but I always go into <your source location>/.repo and edit manifest.xml to include CM's android_device_samsung_jf-common, android_device_samsung_jfltetmo, and android_kernel_samsung_jf. After adding them to your manifest, just do another repo sync and you should have everything you need to start cranking out a build...
Click to expand...
Click to collapse
is this the right informartion that i need to add to the manifest?
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jfltetmo" path="device/samsung/jfltetmo" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
jm492705 said:
is this the right informartion that i need to add to the manifest?
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jfltetmo" path="device/samsung/jfltetmo" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
Click to expand...
Click to collapse
That looks good, but I didn't even think that @ayysir has his PA tree on his github.
I've never built PA but I would assume you could use CM's tree with a few modifications here and there.
lordcheeto03 said:
That looks good, but I didn't even think that @ayysir has his PA tree on his github.
I've never built PA but I would assume you could use CM's tree with a few modifications here and there.
Click to expand...
Click to collapse
So would it be okay for me to put the CM trees that it in the local manifest? just making sure, and then do the repo sync sorry for the noobness just getting the hang of things and really intrested on building PA
jm492705 said:
So would it be okay for me to put the CM trees that it in the local manifest? just making sure, and then do the repo sync sorry for the noobness just getting the hang of things and really intrested on building PA
Click to expand...
Click to collapse
http://www.github.com/aospa-legacy

Attempting to build Liquid Smooth ROM for captivate glide

First off i'm going to say, I know SOME BASIC CODING (I developed some for windows and a little bit on android)
I decided to TRY to build our Captivate glide users more KitKat roms!
So basically I have the source for liquid smooth but I don't know what to do from there (Remember I'm new so don't blow up on me,I'm trying!)
If there is a guide on how to build or you guys can help me on this that would be great!
I was following this guide:
[GUIDE][AOSPA:v3.+] How to Compile AOSPA from Source : + Support and Maintenance
Instead of compiling PA, I decided to use Liquid Smooth (for the life of me couldn't find PA android 4.4.2 REPO!)
did what the guide said and now i'm stuck here:
VERY IMPORTANT: Now, before the final stage sync, make sure there's no code referring to 'ParanoidPreferences' in manifest.
To check that
1) Open your File Browser,
2) Press Ctrl+H (to show hidden files/directories)
3) Navigate to android/system/.repo/manifest.xml
(Right Click & open the XML file in text editor)
*REMOVE ANY 'PARANOIDPREFERENCES' CODE FROM MANIFEST*
*REMOVE GROUPER DEVICE TREE FROM MANIFEST* (This'll be useless, unless you're compiling for Grouper: Nexus 7)
-> Now, Lets add the device specific trees:
Add your own device tree, kernel tree, hardware source tree, & vendor proprietaries tree in the local manifest.
For this, create a new file .repo/local_manifest.xml, & use something in similar terms:
For example, I'm using all corresponding trees for Samsung Galaxy S3 i9300 - International
Following is just an example, not what you should copy/paste. SEARCH & USE YOUR OWN DEVICE SPECIFIC TREES
(codes)Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-10.2" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
I also didn't download the repo into /android/system like it says, I put it into /liquid (followed this) How to compile liquid smooth
Any help would be greatly appreciated! I'm eager to learn how to do this!
My setup
Ubuntu 13.10 x64
did you read that?
Any error message?
wget http://commondatastorage.googleapis.com/git-repo-downloads/repo
chmod 777 repo
./repo init -u git://github.com/LiquidSmooth/android.git -b kitkat
./repo sync
Than you should have source.
Well this attempt to develop is on stand still until I go off on my ISP for shutting off my services because we "apparently" did't pay enough when we did!
Sent from my Kitkatified I927 running CM 11
Here is the paranoid android 4.4 repo:
https://github.com/AOSPA-legacy/manifest

Is Anyone Building Other ROMs Not Posted?

The choice of ROMs has slowly been dipping since Lollipop as more and more ROMs no longer have Official support for Galaxy Nexus.
At the same time, newer ROMs are popping up for other devices and they look quite interesting.
Ones I have been looking at are Dirty Unicorns, Screw'd, AICP and OctOS.
However, building an unofficial ROM has been troublesome for me.
I have been focusing on Marshmallow since there are still some bugs with AOSP/Unlegacy nougat.
My main issue is that it isn't clear which gnex repos I should be adding after I have sync'd the main ROM source.
There are lots of different forks around and it isn't clear which one to choose.
Which repos do I need to add for AOSP based ROMs?
What is the recommended way to add them?
Does it make any difference if the ROM uses Cyanogenmod or Omnirom as a base instead of AOSP?
Has anyone built these (or any other ROMs) privately and would like to share all the commands necessary for a successful build?
Take a look at this backstage development
https://www.androidfilehost.com/?a=show&w=files&flid=18435
SAOSP has more nougat builds,
Then Dirty Unicorn and Pure Nexus.....
Thank him -> @voidz777
My present time is 5 o'clock in the morning.
In other words, it is before going to work.
So I can not write much.lol
Hi, opticyclic
I did not ignore you.
I have been working forever since I got your email.
Because I can not tell the right way unless I port it before telling you.
I was doing screwed work for a while.
https://github.com/voidz777-crewd
But I can not boot it.
Probably, I think it is due to more optimizing.
I got tired because I got tired.lol
After a while, delete https: //github.com/voidz777-crewd.
It is another addition.
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="pdk,linux,arm" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" revision="aosp-6.0" />
<project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="unlegacy" revision="stable" groups="omap4" />
<project path="vendor/ti" name="proprietary_vendor_ti" remote="unlegacy" revision="stable" />
<project path="vendor/widevine" name="proprietary_vendor_widevine" remote="unlegacy" revision="aosp-6.0" />
I'm sorry, my English is not good.
If I could write in Japanese here, I can tell you a little more about the way of port.
There is no time now.
PS.Ah, oct could be pored immediately.
@voidz777 No apologies necessary!
Your posts about different ROMs on Google plus are actually what prompted me to try to build some myself!
Thanks for the info.
I'll post back after trying out a few different ROMs and give an update in the OP on any successes.
I tried to build octos with
Code:
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm
and this in .repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<project remote="unlegacy" path="device/samsung/tuna" name="android_device_samsung_tuna" />
<project remote="unlegacy" path="hardware/ti/omap4" name="android_hardware_ti_omap4" revision="stable" groups="omap4" />
<project remote="unlegacy" path="vendor/samsung" name="proprietary_vendor_samsung" />
<project remote="unlegacy" path="vendor/ti" name="proprietary_vendor_ti" revision="stable" />
<project remote="unlegacy" path="vendor/widevine" name="proprietary_vendor_widevine" />
</manifest>
However, they are doing something funny with the build/envsetup.sh and it isn't picking up the vendorsetup.sh so the device isn't picked up by brunch/breakfast etc.
As far as I can tell, there is no specific info on GitHub, GooglePlus or any posts on xda on how to add a new device for their ROM.
On to AICP....
Check vendor / rom - name or device / other - device /.
If oct it will be platform_vendor_to.
Let's see the commit log.
Is there any device added?
For example, let's look for mako.
https://github.com/Team-OctOS/platform_vendor_to/commit/d30dd90c018ca521d458c939a2c56ffc5a97741d
Mako has been added by this commitment.
Create the tuna file in the same way.
Well, will you continue your way of thinking? Or do you want to know the answer quickly?
Thanks for the tip.
If they are going to use a different build structure, it should really be on the README or a FAQ somewhere.
It's bad programming practice in general to expect people to search through commit logs just to try to work out how a project works.
So instead of just adding a local manifest, OctOs requires the following:
to.dependencies (same as local manifest but in JSON instead of XML)
to.mk - same as the device board (aosp_tuna.mk)
extra line in vendorsetup_community.sh - it ignores your vendorsetup.sh
Then do lunch aosp_tuna-userdebug.
Then do mka bacon
However, the first time I did this, it overwrote my .repo/local_manifest/roomsevice.xml with a generated version that contained octos revisions instead of the aosp revisions, which obviously failed as there is no octos revision in unlegacy!
Weirdly, after reverting the roomservice.xml and running lunch again didn't overwrite it.
AICP was more straightforward.
I just added the roomservice.xml and ran lunch aosp_tuna-userdebug and mka bacon.
However, both failed with the following error:
Code:
build/core/base_rules.mk:157: *** packages/apps/Nfc//nxp/jni: MODULE.TARGET.SHARED_LIBRARIES.libnfc_jni already defined by packages/apps/Nfc/nxp/jni/. Stop.
What is weird about this is that it is the same module defining the library, however, the first one has a double slash in the path!
Probably revert this commit
https://github.com/Team-OctOS/platf...mmit/1b8ed2250fc89adce8e0b0dbb6c5ca4d82705ccb
Sent from my Nexus 5
Good catch.
I wonder how that didn't cause a build failure on the build servers.
The next failure in both was:
Code:
build/core/base_rules.mk:157: *** hardware/invensense/60xx/mlsdk: MODULE.TARGET.SHARED_LIBRARIES.libmlplatform already defined by device/samsung/tuna/libsensors. Stop.
That was resolved by removing the Cyanaogenmod project and using the unlegacy one instead, so the local manifest now looks like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<remove-project name="CyanogenMod/android_hardware_invensense" />
<project name="android_device_samsung_tuna" path="device/samsung/tuna" remote="unlegacy" />
<project name="android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="unlegacy" revision="stable"/>
<project groups="omap4" name="android_hardware_ti_omap4" path="hardware/ti/omap4" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" />
<project name="proprietary_vendor_ti" path="vendor/ti" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="unlegacy" />
</manifest>
I chose revision="stable" for android_kernel_samsung_tuna", although there is also "aosp-6.0-sound" but I just wanted any kernel to allow me to compile at this point.
The next error (both ROMs) is this (maven 3 is installed)
Code:
make: *** No rule to make target '/home/buildbot/android/aicp/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/aar/classes.jar', needed by '/home/buildbot/android/aicp/out/target/common/obj/APPS/messaging_intermediates/AndroidManifest.xml'. Stop.
This relates to this dir https://github.com/AICP/vendor_aicp/
Interestingly, ambientsdk dir existed all thoughout the n7.0 branch and only got removed recently in the n7.1 branch
https://github.com/AICP/vendor_aicp/commit/8f150895f8b361480ac91ef0ace941e06e9f548e
I also don't see any maven messages in the build log and com.cyngn.ambient/ambientsdk/ is not in my ~/.m2/repository which makes me wonder if I am missing a project.
The only similar errors I see online are if people don't have maven installed.
I tried removing the files like the 7.1 branch even though it felt wrong,
Code:
rm vendor/aicp/overlay/common/frameworks/base/core/res/res/values/cm_arrays.xml
rm -rf vendor/aicp/ambientsdk
Not surprisingly, it seems like something else is calling it as the same error pops up 25 mins into build.
repo grep ambientsdk shows ContactsCommon, Trebuchet and ContactsProvider using it in the Android.mk files and grepping for ambient shows lot of java imports.
So now I am stuck again.
To be honest, I wasn't expecting to have to deal with errors like this as they don't seem to be device specific.
i.e. there are builds for other devices so how did they compile?
i have posted nethunter rom here: https://forum.xda-developers.com/galaxy-nexus/development/rom-kali-linux-net-hunter-t3676472

Help building LineageOS 16.0

Hi, I'm trying to build LOS 16.0 for the kltedv but it keeps crashing (error message at the end of post).
These are the steps I'm taking on Ubuntu.
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
Code:
repo sync --force-sync --no-clone-bundle --no-tags
Code:
cd .repo && mkdir local_manifests && cd local* && subl roomservice.xml
In roomservice.xml, I have
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="platform/prebuilts/qemu-kernel" />
<project name="knaik95/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_kltedv" path="device/samsung/kltevzw" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" revision="lineage-16.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-16.0"/>
</manifest>
Code:
repo sync
Code:
source build/envsetup.sh
Code:
add_lunch_combo lineage_kltedv-userdebug
Code:
breakfast kltedv
And this is where it says
Code:
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kltedv".
Has something changed in the build process from the upgrade from 15.1 to 16.0?
Same here. I am trying to build LOS16 for my moto device. Device tree builds fine with LOS 15.1. But fails for LOS 16. Error is same "build/make/core/product_config.mk:234: error: Can not locate config makefile for product". @knaik95, were you able to get pass this situation? Please update.
Thanks
KS
kalyansundhar said:
Same here. I am trying to build LOS16 for my moto device. Device tree builds fine with LOS 15.1. But fails for LOS 16. Error is same "build/make/core/product_config.mk:234: error: Can not locate config makefile for product". @knaik95, were you able to get pass this situation? Please update.
Thanks
KS
Click to expand...
Click to collapse
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
kalyansundhar said:
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
Click to expand...
Click to collapse
Yep. I also renamed lineage.mk to lineage_[device name].mk just to be safe. Did you get any farther? I was met with a bunch of missing dependencies after that. The first one was gradle-plugin, which I fixed by git cloning from the official aosp site, but the others I'm not sure how to get past.
knaik95 said:
Yep. I also renamed lineage.mk to lineage_[device name].mk just to be safe. Did you get any farther? I was met with a bunch of missing dependencies after that. The first one was gradle-plugin, which I fixed by git cloning from the official aosp site, but the others I'm not sure how to get past.
Click to expand...
Click to collapse
I didn't face any further issues so far. But I have to wait and watch.
Thanks
KS
Sent from my Moto G5s using Tapatalk
Can you explain that.. in that detail please
kalyansundhar said:
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
Click to expand...
Click to collapse
there is a file exist in device tree AndroidProduct.mk
I wish you success @knaik95 with your build.
I do recall flashing your RR Oreo builds and they were awesome!!
pmduper said:
I wish you success @knaik95 with your build.
I do recall flashing your RR Oreo builds and they were awesome!!
Click to expand...
Click to collapse
Oh, uh.... yeah I figured out what I was doing a while ago. I've built and tested LiquidRemix based on Android Pie a couple times; I was satisfied with the result. Not a daily driver yet because we're atm without Xposed SDK28 so still on RR Oreo :silly:
knaik95 said:
Oh, uh.... yeah I figured out what I was doing a while ago. I've built and tested LiquidRemix based on Android Pie a couple times; I was satisfied with the result. Not a daily driver yet because we're atm without Xposed SDK28 so still on RR Oreo :silly:
Click to expand...
Click to collapse
Best of luck with your project.
I've been using a variety of Pie builds for the past couple of months. :good:
pmduper said:
Best of luck with your project.
I've been using a variety of Pie builds for the past couple of months. :good:
Click to expand...
Click to collapse
If you wanna give LiquidRemix a try, I can try to post a link. It was daily driver back when the Galaxy S3 was still relevant and the ROM was called LiquidSmooth. I haven't done a thorough examination of features and what not, but I'd say Liquid rivals the customizability of RR.
redacted

Categories

Resources