✦✦✦ [GUIDE] Build LineageOS ✦ How To use Github ✦✦✦

Search This thread
By:
Advanced…
albertoduqe

albertoduqe

Senior Member
May 4, 2017
1,085
526
FSadino said:
Missing Nfc on PRODUCT_PACKAGES
Click to expand...
Click to collapse

:silly:

You must be kidding XD

Now seriously... Ok!

I haven't seen that in any device_xiaomi_lithium or msm8996-common, and I've looked at most of them...

Anyway... If I put that reference in rom-working-folder/device/xiaomi/lithium it should be ok? Or better in device/xiaomi/msm8996-common? I don't even know why ones are there and others not...

Thanks!!!
 
albertoduqe

albertoduqe

Senior Member
May 4, 2017
1,085
526
OK I specified
PRODUCT_PACKAGES
Nfc

on top of what there already was in /build/target/product/generic_no_telephony.mk, /device/xiaomi/lithium/device.mk and device/xiaomi/msm8996-common/msm8996.mk ... to no avail. There is no nfc.apk or any different or added folder or file respect previous builds...

Could you please elaborate a bit more?

Maybe I am missing something essential like making a clean build? I haven't cleared the out folder in some days...

Thanks!
 
O

OnePlusBenefits

Member
Feb 21, 2017
17
0
Hi, as in the title I built LineageOS 14.1 from Scratch without adding any other repositories,
it wont boot, it shows the boot animation for some time but its not a bootloop. The bootanimation starts to end (shows the lineage os text) but not even a second after that it crashes.
that's not happening with the official build.
what could be wrong?
also of course when building the rom it gives me 0 errors.
Im pretty sure this is easy to solve since im oretty new at this
any help is appreciated, thanks
 
M

Mcenzie

Senior Member
Apr 7, 2012
73
16
When i repo los 15.1 i become this Message:

fatal: remote error: upload-pack Not permitted in this server

Any ideas whats wrong?

Many Thanks
 
T

tripLr

Senior Member
Dec 23, 2013
1,498
832
Castle Rock, Wa
Samsung Galaxy Note 4
Verizon Samsung Galaxy Note 4
Number 9,

What command do I use to adb in a Linux shell? To get to the directory?

Just type adb devices to see if it's connected?

where is the extract files script? On the device?

Working on my first build currently, from @ _mone his build guide and @ripee poststhere

So say I have a device galaxy tab S2

And someone has posted a deodexed rooted stock Samsung ROM ( Posiedon )

Can adb pull all the drivers and programs and whatever I need to build lineageos14 ( posiedon is a android 7 build)

To use in my build?

Thanks.

Haven't got to the kitchen threads yet

---------- Post added at 02:49 AM ---------- Previous post was at 02:19 AM ----------
dev.kasibhatla said:
Thank you for the response. could you please elaborate?
Click to expand...
Click to collapse

If you have a dual boot system on one drive,

Install the second drive

Boot to Linux

Partition the drive to ext4, and mount it as /home/your user name/android

You will now see a folder in your home named android

---------- Post added at 03:02 AM ---------- Previous post was at 02:49 AM ----------

My expierence .

Installed lxle Linux on my 8 year old laptop. It's an Ubuntu derived install
I have dual 750 GB hard drives with Windows 10. So it's gonna be slow cooking.

Only 4 GB memory. How to solve the large cache needed?

Shrunk my windows partition to 400 GB
Install Linux on 2nd hard drive with
/ 50 GB root
/ 100 GB swap partition
/ 500 GB home partition

The second drive will be to try other Linux distributions

Which Debian is probably to be my second choice

Doing this to learn a new trade.

Thanks to all

After an hour, I have 100 percent CPU, 10 percent progress, and 20 percent memory usage, and no hiccups
 
J

johnaaronrose

Member
Nov 4, 2011
43
5
Wolverhampton
I'm trying to build this for my Wileyfox Spark X (codename porridgek3)under Ubuntu 16.04. All Ok until "repo sync" which finishes after over an hour's downloading with "error: Exited sync due to fetch errors".
When I try "source build/envsetup.sh", I get bash: build/envsetup.sh: No such file or directory.
What should I do?
 
FSadino

FSadino

Retired Forum Moderator
Oct 27, 2011
3,802
5,228
Blue River City
OnePlus One
OnePlus 3
johnaaronrose said:
I'm trying to build this for my Wileyfox Spark X (codename porridgek3)under Ubuntu 16.04. All Ok until "repo sync" which finishes after over an hour's downloading with "error: Exited sync due to fetch errors".
When I try "source build/envsetup.sh", I get bash: build/envsetup.sh: No such file or directory.
What should I do?
Click to expand...
Click to collapse

If you can't repo sync you don't have "envsetup.sh" under build directory. Repo sync is failing because you have wrong repos on your manifest. Search for that wrong repo and delete it
 
J

johnaaronrose

Member
Nov 4, 2011
43
5
Wolverhampton
Whilst waiting for a reply on a very rainy day yesterday and because I couldn't find any file having manifest as the first part of its filename, I thought that I would try repo for cm13.0. using openjdk1.7. That went Ok until "breakfast porridgek3" when I got:

Checking out files: 100% (54503/54503), done.

Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:257: *** No matches for product "lineage_porridgek3". Stop.

** Don't have a product spec for: 'lineage_porridgek3'
** Do you have the right repo manifest?

** Warning: 'porridgek3' is using CM-based makefiles. This will be deprecated in the next major release.
Looking for dependencies

Do the above problems matter?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
LINEAGE_VERSION=13.0-20180121-UNOFFICIAL-porridgek3
TARGET_PRODUCT=cm_porridgek3
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-109-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_BUILD_TYPE=release
BUILD_ID=MOI10E
OUT_DIR=/home/john/android/system/out
============================================
 
FSadino

FSadino

Retired Forum Moderator
Oct 27, 2011
3,802
5,228
Blue River City
OnePlus One
OnePlus 3
johnaaronrose said:
Whilst waiting for a reply on a very rainy day yesterday and because I couldn't find any file having manifest as the first part of its filename, I thought that I would try repo for cm13.0. using openjdk1.7. That went Ok until "breakfast porridgek3" when I got:

Checking out files: 100% (54503/54503), done.

Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:257: *** No matches for product "lineage_porridgek3". Stop.

** Don't have a product spec for: 'lineage_porridgek3'
** Do you have the right repo manifest?

** Warning: 'porridgek3' is using CM-based makefiles. This will be deprecated in the next major release.
Looking for dependencies

Do the above problems matter?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
LINEAGE_VERSION=13.0-20180121-UNOFFICIAL-porridgek3
TARGET_PRODUCT=cm_porridgek3
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-109-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_BUILD_TYPE=release
BUILD_ID=MOI10E
OUT_DIR=/home/john/android/system/out
============================================
Click to expand...
Click to collapse

It's seems that your device is not officially supported by lineageos
 
salehin4070

salehin4070

Senior Member
Feb 26, 2013
162
37
Dhaka
Could you please tell me how to add dual sim support in an official build? I have the Galaxy S6 Duos and recently Lineage has started supporting the Galaxy S6. I have flashed the official build and everything is working great except the second sim. It doesn't even detect that sim card. Is there anything I can do to the official build to enable support for my other sim? Thanks!
 
  • Like
Reactions: tripLr
T

tripLr

Senior Member
Dec 23, 2013
1,498
832
Castle Rock, Wa
Samsung Galaxy Note 4
Verizon Samsung Galaxy Note 4
salehin4070 said:
Could you please tell me how to add dual sim support in an official build? I have the Galaxy S6 Duos and recently Lineage has started supporting the Galaxy S6. I have flashed the official build and everything is working great except the second sim. It doesn't even detect that sim card. Is there anything I can do to the official build to enable support for my other sim? Thanks!
Click to expand...
Click to collapse

This problem is affecting another thread as well. @ripee I mentioned you because of the note 4 duos problems you had . Any ideas or what u checked .?

I would try to complile just the kernel but add the kernel compile options
And see if there is a check for your second sim to enable.


Sent from my SM-N910V using XDA Labs
 
M

Mcenzie

Senior Member
Apr 7, 2012
73
16
[1055/1055] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
build/core/Makefile:34: warning: overriding commands for target `/home/mcenzie/android/lineage/out/target/product/oneplus3/system/vendor/lib64/vendor.qti.hardware.wifi.supplicant@1.0_vendor.so'
build/core/base_rules.mk:391: warning: ignoring old commands for target `/home/mcenzie/android/lineage/out/target/product/oneplus3/system/vendor/lib64/vendor.qti.hardware.wifi.supplicant@1.0_vendor.so'
ninja: error: 'kernel/arch/arm64/configs/lineageos_oneplus3_defconfig', needed by '/home/mcenzie/android/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ/.config', missing and no known rule to make it
17:58:29 ninja failed with: exit status 1

#### failed to build some targets (01:12 (mm:ss)) ####


whats are mising?!

thanks
 
FSadino

FSadino

Retired Forum Moderator
Oct 27, 2011
3,802
5,228
Blue River City
OnePlus One
OnePlus 3
Mcenzie said:
[1055/1055] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
build/core/Makefile:34: warning: overriding commands for target `/home/mcenzie/android/lineage/out/target/product/oneplus3/system/vendor/lib64/vendor.qti.hardware.wifi.supplicant@1.0_vendor.so'
build/core/base_rules.mk:391: warning: ignoring old commands for target `/home/mcenzie/android/lineage/out/target/product/oneplus3/system/vendor/lib64/vendor.qti.hardware.wifi.supplicant@1.0_vendor.so'
ninja: error: 'kernel/arch/arm64/configs/lineageos_oneplus3_defconfig', needed by '/home/mcenzie/android/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ/.config', missing and no known rule to make it
17:58:29 ninja failed with: exit status 1

#### failed to build some targets (01:12 (mm:ss)) ####


whats are mising?!

thanks
Click to expand...
Click to collapse

Blobs?
 
You must log in or register to reply here.

Similar threads

jackeagle
  • Sticky
[GUIDE][COMPLETE] Android ROM Development From Source To End
Replies
10K
Views
2M
D
DiamondJohn
isidromxz
  • Sticky
[HOW TO] Beginners Guide to Android ROM Development
Replies
744
Views
487K
R
rr4e
dsixda
  • Locked
[KITCHEN] Android Kitchen, v0.224 [Linux / Mac / Windows]
Replies
6K
Views
3M
dsixda
dsixda
GalaxyUser
[GUIDE] How to extract Huawei firmware (update.app)
Replies
111
Views
327K
B
bugrevealingbme
nitin.chobhe
[GUIDE][COMPLETE]How to build ROM with Google Cloud
Replies
546
Views
159K
icantlogin
icantlogin

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 66
    FSadino
    FSadino
    https%3A%2F%2Fs25.postimg.org%2Fk4tz2dr2n%2Flineageos_logo.jpg

    How-to Build LineageOS​


    Introduction​

    These instructions will hopefully assist you to start with a stock device, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for LineageOS (based on Google’s Android operating system) for your device. Using these, you can build both LineageOS and LineageOS Recovery image from source code, and then install them both to your device.

    It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

    Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :). And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.





    What you’ll need

    * A device (supported by LineageOS)
    * A relatively recent 64-bit computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
    * A USB cable compatible with the OnePlus One (typically micro USB)
    * A decent internet connection & reliable electricity :)
    * Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /. etc.​
    ​



    Summary

    1. Install SDK
    2. Install build packages
    3. Java
    4. Create the directories
    5. Install the repo command
    6. Initialize the LineageOS source repository
    7. Download the source code
    8.Prepare the device-specific code
    9. Extract proprietary blobs
    10. Turn on caching to speed up build
    11. Configure jack
    12. Start the build
    13. Install the build




    Build LineageOS and LineageOS Recovery​



    1. Install SDK

    If you haven’t previously installed adb and fastboot, you can download them from Google. Extract it using:
    Code: 
    unzip platform-tools-latest-linux.zip -d ~

    Now we have to add adb and fastboot to our path. Open ~/.profile and add the following:

    Code: 
    # add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
    PATH="$HOME/platform-tools:$PATH"
fi

    Then, run this to update your environment.
    Code: 
    source ~/.profile



    2. Install build packages

    Several packages are needed to build LineageOS. You can install these using your distribution’s package manager.

    You’ll need:

    Code: 
    bc bison build-essential ccache curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev

    For Ubuntu versions older than 16.04 (xenial), substitute:

    libwxgtk3.0-dev → libwxgtk2.8-dev




    3. Java

    Different versions of LineageOS require different JDK (Java Development Kit) versions.

    LineageOS 11.0-13.0: OpenJDK 1.7 (install openjdk-7-jdk)*
    LineageOS 14.1: OpenJDK 1.8 (install openjdk-8-jdk)

    * Ubuntu 16.04 and newer do not have OpenJDK 1.7 in the standard package repositories. See Ask Ubuntu question How do I install openjdk 7 on Ubuntu 16.04 or higher Note that the suggestion to use PPA openjdk-r is outdated (the PPA has never updated their offering of openjdk-7-jdk, so it lacks security fixes); skip that answer even if it is the most upvoted.



    4. Create the directories

    You’ll need to set up some directories in your build environment.

    To create them:

    Code: 
    $ mkdir -p ~/bin
$ mkdir -p ~/android/system



    5. Install the repo command

    Enter the following to download the repo binary and make it executable (runnable):

    Code: 
    $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

    Put the ~/bin directory in your path of execution

    In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

    Code: 
    # set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

    Then, use this to update your environment.

    Code: 
    source ~/.profile



    6. Initialise the LineageOS source repository

    Enter the following to initialize the repository:

    Code: 
    $ cd ~/android/system
$ repo init -u https://github.com/LineageOS/android.git -b lineage-16.0



    7. Download the source code

    To start the download of the source code to your computer:

    Code: 
    $ repo sync

    The Lineage manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire LineageOS history.



    8. Prepare the device-specific code

    After the source downloads, ensure you’re in the root of the source code (cd ~/android/system), then type:
    You have to change DEVICE with the codename of your device (for example: Oneplus ONE codename is bacon)

    Code: 
    $ source build/envsetup.sh
$ breakfast "DEVICE"

    This will download your device’s device specific configuration and kernel.

    Important: Some maintainers require a vendor directory to be populated before breakfast will succeed. If you receive an error here about vendor makefiles, jump down to Extract proprietary blobs. The first portion of breakfast should have succeded, and after completing you can rerun breakfast​



    9. Extract proprietary blobs

    Method 1
    Now ensure your device is connected to your computer via the USB cable, with ADB and root enabled, and that you are in the ~/android/system/device/your_device/codename folder. Then run the extract-files.sh script:

    Code: 
    $ ./extract-files.sh

    The blobs should be pulled into the ~/android/system/vendor/your_device folder. If you see “command not found” errors, adb may need to be placed in ~/bin.


    Method 2 (Recomended)
    Search for your device blobs on TheMuppets or Donkeycoiote and add them to local manifest



    10. Turn on caching to speed up build


    You can speed up subsequent builds by running:

    Code: 
    $ export USE_CCACHE=1

    And adding that line to your ~/.bashrc file. Then, specify the maximum amount of disk space you want cache to use by typing this from the top of your Android tree:

    Code: 
    $ prebuilts/misc/linux-x86/ccache/ccache -M 50.0G

    Where 50G corresponds to 50GB of cache. This needs to be run once. Anywhere from 25GB-100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s Android build environment initialization page.



    11. Configure jack

    Jack is the new Java compiler used from Lineage 14. It is known to run out of memory

    Simple fix is to run this command:

    Code: 
    $ export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4096m"

    Adding that command to your ~/.bashrc file will automatically configure Jack to allocate a sufficient amount of memory.
    If this doesn't help, you can reduce the number of Jacks to 1 in config.properties

    $HOME/.jack-server/config.properties
    jack.server.max-service=1



    12. Start the build

    Time to start building! Now, type:

    Code: 
    $ croot
$ brunch [COLOR="red"]device[/COLOR]

    Remember, device is the codename for your device

    The build should begin.



    13. Install the build

    Assuming the build completed without errors (it will be obvious when it finishes), type the following in the terminal window the build ran in:

    Code: 
    $ cd $OUT

    There you’ll find all the files that were created. The two files we’re interested in are:

    recovery.img, which is the LineageOS recovery image.
    lineage-14.1-build_date-UNOFFICIAL-device.zip, which is the LineageOS installer package.





    Success! So… what’s next?​

    You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.
    Now, what to do next? You can jump to next section of this guide to understand how Github works and how to pick some commits from other developers/teams to improve your custom ROM​


    This guide was taken from Official LineageOS wiki and all credits goes to LineageOS Maintainers :D​
    View
    23
    FSadino
    FSadino


    What is Github and how to use it



    GitHub is a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere. It is a powerful tool with many features available and here i´m going to talk about how you can use it to help you build and customize your "Custom ROM"
    ​




    Summary

    1. Repositories
    2. How to add/remove repositories
    3. How to add/remove remotes
    4. Repository Fork





    1. Repositories


    Now that you have built custom lineage from source to your device, you can explore deeper and see how things work and change them according to your needs.
    First we are going to se what is inside .repo folder

    Code: 
    cd ~/working_dir/.repo
ls

    It will show you something similar to this:

    Captura_de_ecr_2017-09-07_22-39-15.png


    Inside the .repo folder are the necessary "manifest files" that tell the repo sync command what to include or remove from our project when synchronizing with the source

    Open manifest.xml

    Code: 
     gedit ~/working_dir/.repo/manifest.xml

    Inside that file you have all information about which repositories belongs to source. These are the base repositories to build LineageOS.
    Inside ~/working_dir/.repo/local_manifests/roomservice.xml you can see the repositories needed to build for your specific device. This file is created after breakfast device step and includes, besides others, device tree and kernel.





    2. How to add/remove repositories


    Lets take a look at how we use roomservice.xml to add/remove repo's from our project, i will use Oneplus ONE device tree for example

    Code: 
     <project name="LineageOS/android_device_oneplus_bacon" path="device/oneplus/bacon" remote="github" revision="cm-14.1" />

    * project name="LineageOS/android_device_oneplus_bacon Name of repository (without https://github.com)
    * path="device/oneplus/bacon" Here is where the files will reside in our working directory
    * remote="github" Is the for remote we are using, in this case is github (see below how to add/remove remotes to your project)
    * revision="cm-14.1" Revision is the branch we want to sync

    Image:
    Captura_de_ecr_2017-09-08_20-03-54.png






    3. How to add/remove remotes


    Code: 
    <remote fetch="https://github.com" name="github" />

    * remote fetch="https://github.com Url for remote you want to add to your project (in this case, we are working with github)

    * name="github" This is the name for remote





    Now that you understand the concept of repository, you can "fork" one and start making your
    changes and keep it up to date with LineageOS source. For that, you need a Github Account.​




    4. Repository Fork


    In this example, i will fork Oneplus ONE device tree

    1. Create Github Account

    2. Go to https://github.com/LineageOS/android_device_oneplus_bacon and tap on Fork button. After that you can see that repository on you Github account

    Image:

    Captura_de_ecr_2017-09-08_21-23-01.png


    3. Now that you have "forked" one repository, you need to edit ~/working_dir/.repo/local_manifests/roomservice.xml and change the default location to your location on your github.[/SIZE]

    Image:

    Captura_de_ecr_2017-09-08_21-31-19.png




    This is the basic steps you need to understand how to use Github to keep your code saved and updated. On next section, i will tell you how use Git so you can work on your project and start to pick some cool commits from others projects.​
    View
    4
    FSadino
    FSadino
    Reserved
    View
    3
    FSadino
    FSadino
    Ninnix96 said:
    if I have a unsopported device (zuk z2 pro) how can sobstitute the breakfast and brunch command?
    Click to expand...
    Click to collapse

    This thread is for supported devices, that will be my next guide
    View
    2
    R
    roman01110
    A3 2017

    Hi , I have Galaxy A3 2017 I got to point of breakfast and I cound download files for my phone. What I have to do if I want to have Lineage OS Nuggat in my phone. I hate original rom :-{

    breakfast a3y17lte
    including vendor/cm/vendorsetup.sh
    build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a3y17lte". Stop.
    build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_a3y17lte". Stop.
    build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a3y17lte". Stop.
    Device a3y17lte not found. Attempting to retrieve device repository from LineageOS Github
    Repository for a3y17lte not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
    build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a3y17lte". Stop.
    build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_a3y17lte". Stop.

    ** Don't have a product spec for: 'lineage_a3y17lte'
    ** Do you have the right repo manifest?

    Is that mean that I have to wait for support from LineageOS dvlpr team <?
    Roman
    View

New posts