Many thanks for your response. But since I am new to this, I am not sure I understand what that means. Could you please explain a little more? Thanks
✦✦✦ [GUIDE] Build LineageOS ✦ How To use Github ✦✦✦
- Thread starter FSadino
- Start date
Many thanks for your response. But since I am new to this, I am not sure I understand what that means. Could you please explain a little more? Thanks
Example if you've a Samsung device have a look at device tree of a Samsung device and copy files 1 per 1 (exp bin files for WiFi) then build and try
Gesendet von meinem Pixel 2 XL mit Tapatalk
Is generic build for emulator supported and runnable?
I am trying to build LOS 16.0 for emulator. Build is successful but booting fails because it can not find root device /dev/vda1. Here is what I did:
After trying it to run in emulator it does not boot:
Partition /dev/vda1 does not exists only /dev/vda exists. Kernel however is started with parameter root=/dev/vda1. Why this misalignment? Am I missing something?
Is running LOS in emulator officially supported? Has anyone tried it? Am I using correct combo? If not, what is the right one and what is the purpose of lineage_{x86,x86_64,arm,arm64}-userdebug combos?
Thanks for any hint.
I am trying to build LOS 16.0 for emulator. Build is successful but booting fails because it can not find root device /dev/vda1. Here is what I did:
Code:
$ repo init -u https://github.com/LineageOS/android.git -b lineage-16.0
$ repo sync
$ source build/envsetup.sh
# also tried lineage_x86-userdebug and lineage_arm-userdebug on next lines with the same result
$ breakfast lineage_x86_64-userdebug
$ brunch lineage_x86_64-userdebugAfter trying it to run in emulator it does not boot:
Code:
$ emulator -show-kernel
...
[ 0.000000] Linux version 4.4.124+ (android-build@wprf1.hot.corp.google.com) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Aug 16 04:59:43 UTC 2018
[ 0.000000] Command line: qemu=1 no_timer_check androidboot.hardware=ranchu clocksource=pit no-kvmclock console=ttyS0,38400 android.qemud=1 android.checkjni=1 qemu.gles=1 qemu.encrypt=1 qemu.opengles.version=131072 cma=262M@0-4G qemu.wifi=1 mac80211_hwsim.channels=2 androidboot.android_dt_dir=/sys/bus/platform/devices/ANDR0001:00/properties/android/ skip_initramfs rootwait ro init=/init root=/dev/vda1 loop.max_part=7 ramoops.mem_address=0xff018000 ramoops.mem_size=0x10000 memmap=0x10000$0xff018000 qemu.dalvik.vm.heapsize=192m
...
[ 0.984823] VFS: Cannot open root device "vda1" or unknown-block(253,1): error -6
[ 0.985395] Please append a correct "root=" boot option; here are the available partitions:
[ 0.986019] 0100 16384 ram0 (driver?)
[ 0.986385] 0101 16384 ram1 (driver?)
[ 0.986760] 0102 16384 ram2 (driver?)
[ 0.987134] 0103 16384 ram3 (driver?)
[ 0.987496] 0104 16384 ram4 (driver?)
[ 0.987855] 0105 16384 ram5 (driver?)
[ 0.988224] 0106 16384 ram6 (driver?)
[ 0.988586] 0107 16384 ram7 (driver?)
[ 0.988950] 0108 16384 ram8 (driver?)
[ 0.989311] 0109 16384 ram9 (driver?)
[ 0.989682] 010a 16384 ram10 (driver?)
[ 0.990098] 010b 16384 ram11 (driver?)
[ 0.990475] 010c 16384 ram12 (driver?)
[ 0.990843] 010d 16384 ram13 (driver?)
[ 0.991215] 010e 16384 ram14 (driver?)
[ 0.991587] 010f 16384 ram15 (driver?)
[ 0.991957] fd00 1338980 vda driver: virtio_blk
[ 0.992395] fd10 56 vdb driver: virtio_blk
[ 0.992809] fd20 2097152 vdc driver: virtio_blk
[ 0.993229] fd30 1024 vdd driver: virtio_blk
[ 0.993643] fd40 63092 vde driver: virtio_blk
[ 0.994060] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(253,1)
...Partition /dev/vda1 does not exists only /dev/vda exists. Kernel however is started with parameter root=/dev/vda1. Why this misalignment? Am I missing something?
Is running LOS in emulator officially supported? Has anyone tried it? Am I using correct combo? If not, what is the right one and what is the purpose of lineage_{x86,x86_64,arm,arm64}-userdebug combos?
Thanks for any hint.
hi
i see this error after brunch command :
error: vendor/xiaomi/msm8953-common/Android.bp:22:1: module "vendor.display.color@1.0" variant "android_arm64_armv8-a_core_shared": module source path "vendor/xiaomi/msm8953-common/proprietary/lib64/vendor.display.color@1.0.so" does not exist
and i dont know what should i do!!!
i see this error after brunch command :
error: vendor/xiaomi/msm8953-common/Android.bp:22:1: module "vendor.display.color@1.0" variant "android_arm64_armv8-a_core_shared": module source path "vendor/xiaomi/msm8953-common/proprietary/lib64/vendor.display.color@1.0.so" does not exist
and i dont know what should i do!!!
yes , exactlly
but i could not find that filles in any where
i extract proprietary filles from tissot phone and dont know why sme files missing !!!
thanks for attention
Hi, I think it's time to ask for help.
I'm trying to build Lineage for my device, I got the kernel sources, device tree and vendor files, and now trying to compile following the instructions.
Steps I'm doing:
. build/envsetup
lunch lineage_vtr-eng
brunch lineage_vtr-eng
First time I compiled some errors appeared due to device tree issues which were fixed, but now I have an error which I think is related to the build commands (lunch/breakfast/brunch)
Any help is welcomed. Thanks
I'm trying to build Lineage for my device, I got the kernel sources, device tree and vendor files, and now trying to compile following the instructions.
Steps I'm doing:
. build/envsetup
lunch lineage_vtr-eng
brunch lineage_vtr-eng
First time I compiled some errors appeared due to device tree issues which were fixed, but now I have an error which I think is related to the build commands (lunch/breakfast/brunch)
Code:
============================================
[1/1] /home/sirkifixo/LineageOS/out/soong/.minibootstrap/minibp /home/sirkifixo/LineageOS/out/soong/.bootstrap/build.ninja
[55/56] glob prebuilts/ndk/cpufeatures.bp
[80/80] /home/sirkifixo/LineageOS/out/soong/.bootstrap/bin/soong_build /home/sirkifixo/LineageOS/out/soong/build.ninja
/home/sirkifixo/LineageOS/out/build-lineage_vtr-cleanspec.ninja is missing, regenerating...
build/make/core/combo/TARGET_linux-arm.mk:43: warning: cortex-a53 is armv8-a.
build/make/core/combo/TARGET_linux-arm.mk:45: warning: TARGET_2ND_ARCH_VARIANT, armv7-a-neon, ignored! Use armv8-a instead.
/home/sirkifixo/LineageOS/out/build-lineage_vtr.ninja is missing, regenerating...
build/make/core/combo/TARGET_linux-arm.mk:43: warning: cortex-a53 is armv8-a.
build/make/core/combo/TARGET_linux-arm.mk:45: warning: TARGET_2ND_ARCH_VARIANT, armv7-a-neon, ignored! Use armv8-a instead.
[1039/1039] including vendor/qcom/opensource/dataservices/Android.mk ...
build/make/core/Makefile:28: warning: overriding commands for target `/home/sirkifixo/LineageOS/out/target/product/vtr/system/etc/apns-conf.xml'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/sirkifixo/LineageOS/out/target/product/vtr/system/etc/apns-conf.xml'
build/make/core/Makefile:28: warning: overriding commands for target `/home/sirkifixo/LineageOS/out/target/product/vtr/system/compatibility_matrix.xml'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/sirkifixo/LineageOS/out/target/product/vtr/system/compatibility_matrix.xml'
build/make/core/Makefile:28: warning: overriding commands for target `/home/sirkifixo/LineageOS/out/target/product/vtr/system/media/bootanimation.zip'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/sirkifixo/LineageOS/out/target/product/vtr/system/media/bootanimation.zip'
[ 99% 1243/1244] glob vendor/qcom/opensource/interfaces/wifi/supplicant/2.0/src
[100% 1/1] build bacon
FAILED: bacon
/bin/bash -c "(ln -f /home/sirkifixo/LineageOS/out/target/product/vtr/lineage-16.0-20200407-UNOFFICIAL-vtr.zip ) && (md5sum /home/sirkifixo/LineageOS/out/target/product/vtr/lineage-16.0-20200407-UNOFFICIAL-vtr.zip | sed "s|/home/sirkifixo/LineageOS/out/target/product/vtr/||" > /home/sirkifixo/LineageOS/out/target/product/vtr/lineage-16.0-20200407-UNOFFICIAL-vtr.zip.md5sum ) && (echo "Package Complete: /home/sirkifixo/LineageOS/out/target/product/vtr/lineage-16.0-20200407-UNOFFICIAL-vtr.zip" >&2 )"
ln: failed to access '/home/sirkifixo/LineageOS/out/target/product/vtr/lineage-16.0-20200407-UNOFFICIAL-vtr.zip': No such file or directory
ninja: build stopped: subcommand failed.
17:44:31 ninja failed with: exit status 1
#### failed to build some targets (01:53 (mm:ss)) ####Any help is welcomed. Thanks
For those who struggling why ccache not working when compiling 17.1, read this: stackoverflow.com/questions/59811821/how-to-use-ccache-to-speed-up-compiling-of-aosp
In gist, you need an extra environment variable compare with previous versions.
In gist, you need an extra environment variable compare with previous versions.
Hello,
I'm trying to build LOS 17.1 for a OP6 and have several questions.
I tried to remove some stock apps but the resulting build powers off the phone at first boot. Apparently it's not as simple as removing the apps from packages/apps. I see there are some tests while building, looking for the preinstalled apps files. Is that necessary? Why can't I build without "Calendar" for example?
Can I replace the captive portal server before build? Or make the build with it turned off?
How exactly would I turn on avb for a user build?
It's pretty nice that you put the tutorial for people to be able to build themselves, but it's kind of a moot point since the whole power of building yourself is to be able to modify different aspects of the build. Without info on how to modify it you might just as well install the official downloads version.
Also, how would I go about locking the bootloader, if I sign my own build? I understand it's not that simple, but maybe some pointers in the right direction?
Thank you.
I'm trying to build LOS 17.1 for a OP6 and have several questions.
I tried to remove some stock apps but the resulting build powers off the phone at first boot. Apparently it's not as simple as removing the apps from packages/apps. I see there are some tests while building, looking for the preinstalled apps files. Is that necessary? Why can't I build without "Calendar" for example?
Can I replace the captive portal server before build? Or make the build with it turned off?
How exactly would I turn on avb for a user build?
It's pretty nice that you put the tutorial for people to be able to build themselves, but it's kind of a moot point since the whole power of building yourself is to be able to modify different aspects of the build. Without info on how to modify it you might just as well install the official downloads version.
Also, how would I go about locking the bootloader, if I sign my own build? I understand it's not that simple, but maybe some pointers in the right direction?
Thank you.
Build different Lineage versions on the same machine or not?
I am currently building LineageOS 15.1 for Samsung S6, S6 Edge and HTC One M8. I am using an Ubuntu 20.04 VM with 300GB of storage. I created the build environment in /home/user/android/lineage/. I forked the S6/S6 edge sources and made some changes to fix a couple of issues and I am building with my own keys and everything is working well for 15.1 (obviously excluding the inherent camera issues with the S6).
I want to start building LineageOS 16 and/or 17.1 and am not sure if I can use the same build environment or should I create a new one - i.e. new Ubuntu VM, memory, storage etc. I am not sure whether there are downsides or limits with either?
Cheers
Andy
I am currently building LineageOS 15.1 for Samsung S6, S6 Edge and HTC One M8. I am using an Ubuntu 20.04 VM with 300GB of storage. I created the build environment in /home/user/android/lineage/. I forked the S6/S6 edge sources and made some changes to fix a couple of issues and I am building with my own keys and everything is working well for 15.1 (obviously excluding the inherent camera issues with the S6).
I want to start building LineageOS 16 and/or 17.1 and am not sure if I can use the same build environment or should I create a new one - i.e. new Ubuntu VM, memory, storage etc. I am not sure whether there are downsides or limits with either?
Cheers
Andy
If you're on a Debian distro try
sudo apt-get install libffi-dev
pyenv uninstall 3.7.6
pyenv install 3.7.6
Can someone help me I try to compile rom more of this error
find: '/home/viperx/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates': No such file or directory
build/core/base_rules.mk:183: *** vendor/samsung/galaxys2-common/proprietary: MODULE.TARGET.SHARED_LIBRARIES.libUMP already defined by hardware/samsung/exynos4/hal/libUMP.
make: *** [build/core/ninja.mk:167: /home/viperx/android/lineage/out/build-lineage_i9100.ninja] Error 1
make: Leaving directory '/home/viperx/android/lineage'
#### make failed to build some targets (01:53 (mm:ss)) ####
find: '/home/viperx/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates': No such file or directory
build/core/base_rules.mk:183: *** vendor/samsung/galaxys2-common/proprietary: MODULE.TARGET.SHARED_LIBRARIES.libUMP already defined by hardware/samsung/exynos4/hal/libUMP.
make: *** [build/core/ninja.mk:167: /home/viperx/android/lineage/out/build-lineage_i9100.ninja] Error 1
make: Leaving directory '/home/viperx/android/lineage'
#### make failed to build some targets (01:53 (mm:ss)) ####
Attachments
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
66
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 Maintainers23
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:
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:
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:
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:
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.32A3 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
