[ROM][BULLHEAD][UNOFFICIAL] LineageOS 13.0 for Nexus 5x + Compilation tutorial!!

[ROM][BULLHEAD][UNOFFICIAL] LineageOS 13.0 for Nexus 5x + Compilation tutorial!! - Nexus 5X Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I built this ROM based on LineageOS 13.0 for Nexus 5x, with latest security patches. See below for more details and ENJOY IT!
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM/KERNEL before flashing it! YOU are choosing to make these modifications, and if you point your finger at me for messing up your device, I will laugh at you.
About this build:
• This is the updated build with the latest security patches from Google and bug fixes from LOS Team.
• TWRP recommended: 3.0.2.
• Bootloader recommended: BHZ10R (MTC20K)
• Radio recommended: M8994F-2.6.36.2.20 (MTC20K)
• Vendor: MTC20K
Instructions (clean flash recommended):
1. Make sure you unlocked your bootloader.
2. Install TWRP (version 3.0.2 recommended)
3. Flash LOS 13.0 (DOWNLOAD LineageOS-13.0)
4. Flash Gapps (OpenGapps Pico recommended: http://opengapps.org/)
DOWNLOAD ROM!
Optional packages:
• Root ( https://mirrorbits.lineageos.org/su/13.0/addonsu-arm64-signed.zip )
Bugs:
• You tell me!
XDA: DevDB Information
[ROM][BULLHEAD][UNOFFICIAL] LineageOS 13.0 for Nexus 5x
Contributors
LineageOS whole team.
ROM OS Version: 6.0.X
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Source code: https://github.com/LineageOS/android...e_lge_bullhead & https://github.com/LineageOS/android...l_lge_bullhead
Changelog: https://review.lineageos.org/#/q/sta...branch:cm-13.0
Version Information
Status: Stable
Stable Release Date: Always updated!
Created: Always updated!
Last Updated: Always updated!
Compile your own LineageOS Rom 13.0:
Use Ubuntu 14.04LTS
Simply copy and paste:
Preparing packages to compile:
Code:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk openjdk-7-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev maven maven2 libnss-sss:i386 python-networkx ccache libc6-dev-i386 x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev unzip
Code:
sudo apt-get install g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
Code:
sudo apt-get install android-tools-fastboot android-tools-adb
Code:
sudo apt-get install phablet-tools
Code:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
EXAMPLE:
Code:
git config --global user.email [email protected]
git config --global user.name johan88
Preparing environment:
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
Code:
mkdir ~/source-LineageOS-13.0
Code:
cd ~/source-LineageOS-13.0
Code:
repo init -u git://github.com/LineageOS/android.git -b cm-13.0
Code:
cd ~/source-LineageOS-13.0
This is going to take ...
Code:
repo sync
Prepare code for our device "bullhead"
Code:
source build/envsetup.sh
Code:
breakfast bullhead
Add proprietary files to the code.
Go to route:
Code:
Personal folder/source-LineageOS-13.0/.repo/local_manifests/roomservice.xml
Add in the middle these 2 lines:
Code:
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
Resync:
Code:
cd ~/source-LineageOS-13.0
Code:
repo sync
Now start the compilation:
Code:
cd ~/source-LineageOS-13.0
Code:
. build/envsetup.sh && brunch bullhead
Once finished the compilation the rom will be in:
Code:
Personal Folder//source-LineageOS-13.0/out/target/product/bullhead/
To clean everything and recompile:
Code:
cd ~/source-LineageOS-13.0
Code:
make clobber
Code:
repo sync
Code:
. build/envsetup.sh && brunch bullhead
ATTENTION! I can not support compilation errors since I am not an expert.

This is for users who still do not want to go to Lineage 14.1, have an option to be able to use CyanogenMod / LineageOS 13 in a stable way.

veloz46 said:
This is for users who still do not want to go to Lineage 14.1, have an option to be able to use CyanogenMod / LineageOS 13 in a stable way.
Click to expand...
Click to collapse
How?
Sent from my Nexus 5X using Tapatalk

paul222008 said:
How?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Excuse me, what is your question exactly?
Enviado desde mi Nexus 5X mediante Tapatalk

veloz46 said:
This is for users who still do not want to go to Lineage 14.1, have an option to be able to use CyanogenMod / LineageOS 13 in a stable way.
Click to expand...
Click to collapse
Thanks! Works good!

Hi! Great to see this! I'll try it ASAP. Thanks, @lfuentes for this tip! :highfive: If you need help @veloz46, feel free to PM me. I'm an Spanish-English translator. I think some improvement can be made in the first post.

I am doing a new compilation.
@CLPose siéntate libre de ayudarme en lo que creas conveniente.
Enviado desde mi Nexus 5X mediante Tapatalk

I am doing a new compilation.
@CLPose siéntate libre de ayudarme en lo que creas conveniente.
Enviado desde mi Nexus 5X mediante Tapatalk

Updated with the patches of this month.

Many thanks to @CLPose for your help in complementing the information of the first post!

veloz46 said:
Updated with the patches of this month.
Click to expand...
Click to collapse
OK, Downloading...

Hi! Does anyone try this ROM in MTC20F bootloader, radio, vendor? I don't know why, but I can't flash a permanent TWRP in MTC20K. So I want to know if this could work in MTC20F. Is it risky to try it? Thanks!

CLPose said:
Hi! Does anyone try this ROM in MTC20F bootloader, radio, vendor? I don't know why, but I can't flash a permanent TWRP in MTC20K. So I want to know if this could work in MTC20F. Is it risky to try it? Thanks!
Click to expand...
Click to collapse
I do. It works well. Try to flash a full stock MM. Then flash twrp 3.1

Building May update request
Hey, thank you for this updated lineage 13 for bullhead ! Necessary for Xposed users... This April built is very stable for daily use. Can someone please build an updated version with May security ? Thanks

i-Pericles said:
Hey, thank you for this updated lineage 13 for bullhead ! Necessary for Xposed users... This April built is very stable for daily use. Can someone please build an updated version with May security ? Thanks
Click to expand...
Click to collapse
+1

Okay, a see I can do.

This month's patches have not yet been applied, the compilation is also uploading.
Enviado desde mi Nexus 5X mediante Tapatalk

OK. Waiting...

The ROM has been uploaded. Downloading now...

Official CM13 N5X maintainer review on Lineageos 13 by veloz46
Hey, thank you again veloz46 for your work on Lineageos 13, I asked a review from razorloves (official maintainer) about your ROM on official CM13 thread.
Can you clarify the work made on security patching in your ROM and answer razorloves here please ? Thanks

Related

[ROM][KK][4.4.2][SABERMOD] CyanogenMod 11 [5/3][DEV DISCUSSION]

Download Links and Changelog
CM Commit Changelog
Recommended GApps: CM11 Compatible GApps
If you dont like torrents in the above link use: This
OR Aroma GApps (But PLEASE READ thread to make sure this is for you)
Download Links
Current Build:4/03/2014 Build 9
Comes with the stock CM11 Kernel
Sync'd CM11 Source
Compiled with new Linaro Toolchain (4.7.4) custom made for Cortex A9!!!!
Older Builds
12/07/2013 Build 1
Initial Build
12/08/2013 Build 2
Cherry-picked Exynos Camera Fixes: should fix video recording (Not Tested yet)
12/11/2013 Build 3
Initial Linaro Build (4.7.4)
Updated Mali Drivers
12/12/2013 Build 4
Linaro
(New Governors)
hotplug author: Mike Turquette <[email protected]> &
Santosh Shilimkar <[email protected]>
lulzactiveq author: Mike Chan <[email protected]>
Improved by tegrak <[email protected]>
Tuned by: gokhanmoral-robertobsc"
(New I/O Schedulers)
Updated ROW to V4.
Tweaked SIO a bit.
Added V(R) authored by Aaron Carroll <[email protected]>.
Added BFQ v6r2 authored by:
-Jens Axboe <[email protected]>
-Fabio Checconi <[email protected]>
-Paolo Valente <[email protected]>
and improved by Arianna Avanzini <[email protected]>
12/19/12013 Build 5
Synced latest CM sources
Cherry-Picked Video Recording Fix
Tried to add Low RAM option but it doesnt work . . .for now
12/23/2013 Build 6 WIFI FIXED!
Integrated Kernel build 12/29/2013 For more info about kernel please see: Link
Synced CM sources
Reverted cherry-picks to hopefully resolve minor issues
2/24/2014 Build 8
Comes with the stock CM11 Kernel
Sync'd CM11 Source
This is the smoothest build so far!!
Compiled with new Linaro Toolchain (4.7.4) custom made for Cortex A9!!!!

Screen Shots
courtesy of @@trevor.bman
CM11 Build Instructions
courtesy of @@iXNyNe
most of this is ripped from http://wiki.cyanogenmod.org/w/Build_for_i777 so visit there for extra details and explanations
You will need:
A Galaxy S II running CyanogenMod
A Linux environment; you have multiple options here
A dedicated machine (probably the quickest to make builds)
A "Dual Boot" setup (also fast, but the build can take some time so expect to get familar with linux desktop while it's building)
a Virtual Machine setup such as VirtualBox (if you run just a basic command line setup this may be faster, but if you run the full environment it's likely to be slower because of the resources)
An internet connection (probably not a hotspot... you'll be downloading ~20GB)
A Micro USB cable
*Notes: you'll want to be using the 64-bit version of whatever linux distro you choose
**I'm not going to go into detail on setting up linux here, but there's lots of tutorials
***personally I use Ubuntu linux as my daily desktop environment (I'M FREE FROM WINDOWS!)
Phase 1: Setup that only has to be done once
You'll need to install ADB (and wouldnt hurt to have fastboot)
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
next is udev rules
on ubuntu press alt+f2 and enter
Code:
gksu gedit /etc/udev/rules.d/51-android.rules
you'll be asked for a password for elevated permissions *should have been setup when you setup linux
paste this
Code:
#Samsung
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0660"
There are other rules you can add for other vendors but this one should work for all samsung devices.
Next install the other tools required to build
Code:
sudo apt-get install bison build-essential curl flex git-core gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
*note this will install the 32 and 64 bit tools, if you're on 32 bit you're doing it wrong...
Next create some directories
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
Install repo command
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Allow repo to run outside of it's directory (so you can just type repo insteas of /home/user/bin/repo)
Code:
gedit ~/.bashrc
enter the following in the text editor then save and close
Code:
export PATH=${PATH}:~/bin
Initialize the CyanogenMod source repository
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
Download the source code
Your first sync will take forever! it's just under 20GB, I recommend doing it overnight - in the future your sync will be faster because it just downloads updates.
Code:
repo sync
*Note from Render - by default the repo sync command will download using 4 simultanous connections. If you have a fast internet connection you can add more connections like this:
repo sync -j6 (or -j8 and so on)
Get prebuilt apps
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
notice the dot!
Prepare the device-specific code
Code:
cd ~/android/system
source build/envsetup.sh
breakfast i777
Extract proprietary blobs
Now ensure that your Galaxy S II (AT&T) is connected to your computer via the USB cable and usb debugging is turned ON!
Code:
adb devices
if you see your device listed then proceed, if not come here to this thread and ask for help! you cannot go further! (and won't be able to go further in the future).
Code:
cd ~/android/system/device/samsung/i777
./extract-files.sh
*Note from Render - If you setup your roomservice.xml file like below then you already have the needed device files and the above few steps really are not necessary.
Setup and modify roomservice.xml
Code:
mkdir .repo/local_manifests
gedit .repo/local_manifests/roomservice.xml
Enter this
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_i777" path="device/samsung/i777" remote="github" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Save and quit
Phase 2: Building (finally!)
Let's assume from here that you finished all of the above and got bored and closed the terminal - or that you just finished a build and are starting a new one after opening a fresh terminal (or just continuing from the instructions above) the following commands in order will set up your build environment, sync the latest changes, and pull in the patches we need for the build to work and then initiate the build. All of the commands up until brunch shouldn't take long to run, brunch can take anywhere from 2-10 hours depending on your system specs
Code:
cd ~/android/system/
repo selfupdate
repo sync
cd device/samsung/i777/
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_i777 refs/changes/90/54090/1 && git cherry-pick FETCH_HEAD
croot
cd device/samsung/galaxys2-common/
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_galaxys2-common refs/changes/65/55865/1 && git cherry-pick FETCH_HEAD
croot
export USE_CCACHE=1
. build/envsetup.sh
brunch i777
#done (as long as the build shows the out file)
If your build succeeds and you have a file you can push it to your device over usb using adb like so
Code:
cd $OUT
adb push cm-11-20140107-UNOFFICIAL-i777.zip /sdcard/
*Note that the filename should match whatever your build name (depending on the date usually just change the number)
this takes a minute or two, but once it's done you can reboot into recovery and then flash your build!
Also since you used CCACHE=1 And build from here on will now take a fraction of the time to build.

Awesome
Sent from my LG-D801 using Tapatalk

Excited to try it out!!

Is this also compiled with linaro?
Sent from my SGH-I777 using Tapatalk 2

Not yet, Its just a fully working CM11 Build for now.

Thanks a lot for this man. I am downloading it right now. I will let you know of any bugs.
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
There is a problem. I clicked the link to the ROM but it says I need mega to download the file. I suggest using drop box or mega upload to upload the file. Thanks!

csfile said:
Is this also compiled with linaro?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
azeem40 said:
Thanks a lot for this man. I am downloading it right now. I will let you know of any bugs.
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
There is a problem. I clicked the link to the ROM but it says I need mega to download the file. I suggest using drop box or mega upload to upload the file. Thanks!
Click to expand...
Click to collapse
Damn, I was trying to use Dev Host but it crapped out SO many times. I will fix it. Thanks for the heads up

RenderBroken said:
Damn, I was trying to use Dev Host but it crapped out SO many times. I will fix it. Thanks for the heads up
Click to expand...
Click to collapse
NP. It still downloads just fine, though, and I get free 50gb storage! For others, it might be a problem.

RenderBroken said:
Damn, I was trying to use Dev Host but it crapped out SO many times. I will fix it. Thanks for the heads up
Click to expand...
Click to collapse
Anyone else having issues using Mega? I was able to initiate the download without a prompt to install/download Mega like Azeem says? Apparently Dev Host wants to work for me now :silly:

EDIT: Nvm, I figured out the problem. I forgot to reboot into recovery. It was showing the old recovery.

azeem40 said:
EDIT: Nvm, I figured out the problem. I forgot to reboot into recovery. It was showing the old recovery.
Click to expand...
Click to collapse
So you were able to download the file? What did you end up having to do?

azeem40 said:
EDIT: Nvm, I figured out the problem. I forgot to reboot into recovery. It was showing the old recovery.
Click to expand...
Click to collapse
Can you explain? I can't get it to install either. I was having the same metadata recursive error. The OP says use CWM 6.0.4.4, but the newest i can find is 6.0.1.0

lordmorphous said:
Can you explain? I can't get it to install either. I was having the same metadata recursive error. The OP says use CWM 6.0.4.4, but the newest i can find is 6.0.1.0
Click to expand...
Click to collapse
You have to install the cm10.2 latest nightly, which will have 6.0.4.5.

azeem40 said:
You have to install the cm10.2 latest nightly, which will have 6.0.4.5.
Click to expand...
Click to collapse
Ironically, I'm downloading that now. Thanks.

RenderBroken said:
So you were able to download the file? What did you end up having to do?
Click to expand...
Click to collapse
I still had to do what I explained in the previous page (download MEGA and sign up for an account).

lordmorphous said:
Ironically, I'm downloading that now. Thanks.
Click to expand...
Click to collapse
azeem40 said:
You have to install the cm10.2 latest nightly, which will have 6.0.4.5.
Click to expand...
Click to collapse
lordmorphous said:
Can you explain? I can't get it to install either. I was having the same metadata recursive error. The OP says use CWM 6.0.4.4, but the newest i can find is 6.0.1.0
Click to expand...
Click to collapse
I will make that more clear in the OP. Unfortunately there is not an easier way to install the recent recovery other than flashing the newer CM10.2 nightlies.

how come this is not on the cyanogenmod website for our device?
>> http://download.cyanogenmod.org/?device=i777

ksaul said:
how come this is not on the cyanogenmod website for our device?
>> http://download.cyanogenmod.org/?device=i777
Click to expand...
Click to collapse
That is because this is an unofficial nightly. RenderBroken ported cm11 for us.
---------- Post added at 05:59 PM ---------- Previous post was at 05:38 PM ----------
Render, did you forget to include the launcher in this? Cuz when I click home, the screen goes black. Also, when I restart the phone, it goes into a bootloop. I have tried reflashing it three times and each time, the same thing happens.

{All 2011}[GUIDE][DEV] How to build CyanogenMod 12.1

This thread is intended for devs & advanced users only.
Here you can learn how to build CyanogenMod 12.1 for any of the 2011 xperia devices.
I will use 'smultron' as an example device, you should replace the codename with the device you want to build.
For the first time you try to build CM12.1
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Initialize the CyanogenMod source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
ln -s vendor/extra/updates.sh updates.sh
./updates.sh
Setup the build environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-12.1-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-12.1-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Some suggestions for faster builds:
* Enable ccache
* Use the fastest hdd on your pc to store the source, build output & ccache
* You can also buy an ssd, if it's not large enough to hold everything, just store the build output & ccache
* mount /tmp on tmpfs (RAM).
The above have greatly improved my dirty build times with removed /out/target from 1h30m to 30m.
Mounting /tmp on tmpfs made the biggest improvement for me.
Credits: Thanks to hnl_dk for the initial CM9 & CM10 guides.

Reserved

getting insuficiant storage aviable in pa gappps (pico/micro) packages

Druboo666 said:
getting insuficiant storage aviable in pa gappps (pico/micro) packages
Click to expand...
Click to collapse
yes...same here
from build of 21st...i am getting this error
and even other zips are not getting flashed

TWRP
delete

Other than a fast HDD, does you computer need to be fast to build it? (Running a 2007 Core 2 Duo...)
Theonew said:
More cores are better. Here are the requirements to build it from source:
- 6GB of download.
- 25GB disk space to do a single build.
- 80GB disk space to build all AOSP configs at the same time.
- 16GB RAM recommended, more preferred, anything less will measurably benefit from using an SSD.
- 5+ hours of CPU time for a single build, 25+ minutes of wall time, as measured on a workstation (dual-E5620 i.e. 2x quad-core 2.4GHz HT, with 24GB of RAM, no SSD).
Click to expand...
Click to collapse
And I would say that a fast internet connection is also recommended, since the full source for initial sync is more than 10GBs (on ICS it already was, probably like 20GBs for lollipop).

brunch build error 12.1
Hi,
I am trying to build the image from the sources as per the build instructions to make my own test build.
After repo downloads, while building i am getting error "init/Kconfig:953: can't open file "usr/Kconfig"" in the brunch smultron command.
I am following these commands:
1) repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
2) curl https://raw.githubusercontent.com/Le...-12.1/semc.xml > /tmp/android/system/.repo/local_manifests/semc.xml
3) repo sync
4) ln -s vendor/extra/updates.sh updates.sh
5) ./updates.sh
6) . build/envsetup.sh
7) breakfast smultron
8) brunch smultron
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you tell me whats wrong.
Thanks.

joshipallav said:
Hi,
I am trying to build the image from the sources as per the build instructions to make my own test build.
After repo downloads, while building i am getting error "init/Kconfig:953: can't open file "usr/Kconfig"" in the brunch smultron command.
I am following these commands:
1) repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
2) curl https://raw.githubusercontent.com/Le...-12.1/semc.xml > /tmp/android/system/.repo/local_manifests/semc.xml
3) repo sync
4) ln -s vendor/extra/updates.sh updates.sh
5) ./updates.sh
6) . build/envsetup.sh
7) breakfast smultron
8) brunch smultron
Can you tell me whats wrong.
Thanks.
Click to expand...
Click to collapse
Delete the folder ~/android/system/kernel
repo sync again and make sure you get no errors
run make clean
try to build again

@Langes
hi.. just wanted to know.. any guide to Build for AOSP 5.1.1 Lollipop for Xperia Devices 2011 like cm12.1 here
and silly question time.. lol
is it possible that AOSP Android M source can also be built for Xperia Play (2011 Devices) .. I mean changes made by Mike (the AOSP Mike) + Source of Android M .. will it give us some output or :/

I built this rom today with new 3.10 kernel. It seems to be improved in some points (what isn't neccessary because of kernel), but with new kernel I can't use wifi and mobile data seems to be not working too. To build I fetched the new kernel and cherry-picked following commits:
Code:
#msm7x30-common: Update USB configuration for 3.10
cherries+=(LX_594)
#Use common msm7x30 kernel
#cherries+=(LX_422)
#msm7x30-common: Use common msm7x30 kernel
cherries+=(LX_421)
#mogami-common: wl12xx updates for 3.10
cherries+=(LX_407)
#media/msm7x30: Update for 3.10 support
cherries+=(LX_403)
#display/msm7x30: Update for 3.10 support
cherries+=(LX_402)
#audio/msm7x30: Update for 3.10 support
cherries+=(LX_401)
#kernel
#usb: Import msm charger changes from 6.2.B.0.200
cherries+=(LX_430)
#usb: msm72k_otg: Remove userspace events [REVISIT]
cherries+=(LX_428)
Is there something I missed to get working internet connection? (I didn't really test the rom for other things so far)

Getting this error when building AOSP rest all goes fine..
build also starts but getting this error.. any suggestion ?

Hey Mike, I tried to build CM14 and it fails. After some investigation it seems that imgdiff is missing. This was fixed on CM13: http://review.cyanogenmod.org/#/c/135193, which can't be applied to CM14 (no RECOVERY_PATCH_INSTALL).
I hope this helps.

zweif said:
Hey Mike, I tried to build CM14 and it fails. After some investigation it seems that imgdiff is missing. This was fixed on CM13: http://review.cyanogenmod.org/#/c/135193, which can't be applied to CM14 (no RECOVERY_PATCH_INSTALL).
I hope this helps.
Click to expand...
Click to collapse
I already have a cm14 zip for anzu, just unable to flash it because it's about 330MB and device runs out of memory when attempting to flash. Will try to find a solution/hack on the weekend

I managed to build cm14 zip for mango (installation fails as expected).
I modified build/core/Makefile, I don't fully understand how these dependencies work, but maybe there is a dependency issue.
There are dependencies: imgdiff <- RECOVERY_FROM_BOOT_PATCH <- INSTALLED_SYSTEMIMAGE <- BUILT_TARGET_FILES_PACKAGE (where make_recovery_patch is called, which needs imgdiff)
Now INSTALLED_SYSTEMIMAGE is defined before RECOVERY_FROM_BOOT_PATCH, but dependencies of INSTALLED_SYSTEMIMAGE are defined after that. Could this cause an issue?
After moving
Code:
INSTALLED_SYSTEMIMAGE := $(PRODUCT_OUT)/system.img
SYSTEMIMAGE_SOURCE_DIR := $(TARGET_OUT)
from line 1284 to line 1314 build was successfull.

mikeioannina said:
I already have a cm14 zip for anzu, just unable to flash it because it's about 330MB and device runs out of memory when attempting to flash. Will try to find a solution/hack on the weekend
Click to expand...
Click to collapse
I managed to flash cm14 after disabling dex-preoptimization. Zip size decreases to ~260MB. I didn't do extensive testing - messaging seems to work, dialing a number causes restart (system, not kernel), the only sounds I noticed were dialing sounds, i miss a browser and other apps - but it seems nice for a first impression.
Concerning my problem with imgdiff: After reading some make documentation I have no clue why it isn't built. Maybe these dependencies aren't tracked because RECOVERY_FROM_BOOT_PATCH is set to an empty string when BOARD_CANT_BUILD_RECOVERY_FROM_BOOT_PATCH is defined?
I can manually call 'make imgdiff' as workaround.
I tried some things that could have affected imgdiff before my last post, and I'm not sure if I cleared output directory. Did you try a clean build or could imgdiff come from a previous build on your machine?

bro, How much space does it need to sync the repo??
& if I want to port a ROM based on CM (Like Resurrection Remix or Liquid Smooth), would I have to use the command "repo sync"?

I'm trying to build CM14.0, but jack server is giving me a bad time with out of memory error. I have tried changing jack.server.max-service to 1, heap size to 2g, 3g and 4g, even to build without ninja, but always getting out of memory. In CM13.0 I could build without jack, but now the built is failing without it. I'm using Ubuntu 16.04 on an i3 with 4g RAM and 8g swap, I've seen cases with machines with better specs failing (e.g. i5, 8g RAM). Is it a bug with jack, or my specs is the limiting factor?
Edit: I guess this is the EOL for me :crying:.

azakosath said:
I'm trying to build CM14.0, but jack server is giving me a bad time with out of memory error. I have tried changing jack.server.max-service to 1, heap size to 2g, 3g and 4g, even to build without ninja, but always getting out of memory. In CM13.0 I could build without jack, but now the built is failing without it. I'm using Ubuntu 16.04 on an i3 with 4g RAM and 8g swap, I've seen cases with machines with better specs failing (e.g. i5, 8g RAM). Is it a bug with jack, or my specs is the limiting factor?
Edit: I guess this is the EOL for me :crying:.
Click to expand...
Click to collapse
Jack troubleshooting
If your computer becomes unresponsive during compilation or if you experience Jack compilations failing on “Out of memory error”
You can improve the situation by reducing the number of Jack simultaneous compilations by editing your $HOME/.jack-server/config.properties and changing jack.server.max-service= to a lower value.
Description with default values follows:
jack.server.max-service=<number> Maximum number of simultaneous Jack tasks. Default is 4.
jack.server.max-jars-size=<size-in-bytes> Maximum size for Jars, in bytes. -1 means no limit. Default is 100 MiB.
jack.server.time-out=<time-in-seconds> Time out delay before Jack gets to sleep. When Jack sleeps, its memoryusage is reduced, but it is slower to wake up. -1 means "do not sleep".Default is 2 weeks.
jack.server.service.port=<port-number> Server service TCP port number. Default is 8076. Needs to match theservice port defined in $HOME/.jack-settings on the client host (SeeClient section).
jack.server.admin.port=<port-number> Server admin TCP port number. Default is 8077. Needs to match theservice port defined in $HOME/.jack-settings on the client host (SeeClient section).
jack.server.config.version=<version> Internal, do not modify.

Mardon said:
Jack troubleshooting...
Click to expand...
Click to collapse
Thanks for answering, but I have already read these. I tried several combinations (max services and "-Xmx") without luck. Even:
Code:
export USE_NINJA=false
to build without ninja. The result was always the same, jack server was hanging and failing after 30 or more compilations.
P.S. I did use the changes that are not merged yet, but I don't think this is related.

You also can try
breakfast devicename
And after that
make -j1 bacon
To force 1 job compiling only
Gesendet von meinem GT-I8190 mit Tapatalk

[REFERENCE] ELS - exynos-linux-stable (4.9.193)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Project: Exynos-Linux-Stable- Exynos-Linux-Stable is an organisation on GitLab & GitHub containing upstreamed linux for some of the latest flagship handset from SAMSUNG like the S7, S7E, S8, S8+, Note 8, S9, S9+, Note 9 kernel upstreamed to be inline with respective linux branches.
What does this bring?
- All of the devices mentioned above uses Long Term Support (LTS) releases, they are like old softwares.
- LTS releases are supported through their specified support duration by security updates, bug fixes, backports, and new device drivers, just like a regular release.
So updating or up-streaming your device's kernel brings many improvements talking security, performance wise etc...
How do I use?
If you are a developer, the reference tree is located in the exynos-linux-stable organization: https://github.com/exynos-linux-stable
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, ask your kernel developer KINDLY to use this source for his kernel that has all the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The exynos-linux-stable Telegram channel: https://t.me/exynos_linux_stable
Subscribe to this thread
XDA:DevDB Information
ELS - exynos-linux-stable, Kernel for the Samsung Galaxy Note 9
Contributors
farovitus
Source Code: https://github.com/exynos-linux-stable/crownlte
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2019-05-18
Created 2018-08-24
Last Updated 2019-09-17

Reserved

Reserved

This source appears to be broken (apparently now differently to when I tried a few days ago):
Code:
~$ mkdir note-9
~$ cd note-9
~/note-9$ git clone https://bitbucket.org/UBERTC/aarch64-linux-android-4.9-kernel
~/note-9$ git clone https://github.com/exynos-linux-stable/crownlte
~/note-9$ cd crownlte
~/note-9/crownlte$ export ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- PATH=$PWD/aarch64-linux-android-4.9-kernel/bin:$PATH
~/note-9/crownlte$ make exynos9810-crownlte_defconfig
~/note-9/crownlte$ make -j1
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
LD init/mounts.o
AS init/_uh.o
init/_uh.S: Assembler messages:
init/_uh.S:40: Error: file not found: init/uh.8g.elf
scripts/Makefile.build:393: recipe for target 'init/_uh.o' failed
make[1]: *** [init/_uh.o] Error 1
Makefile:1036: recipe for target 'init' failed
make: *** [init] Error 2
stock source builds in the same environment.

Phoenix09 said:
This source appears to be broken (apparently now differently to when I tried a few days ago):
stock source builds in the same environment.
Click to expand...
Click to collapse
Well i did compile the source before i pushed it to GitHub and it was totally fine... but i will double check tomorrow.

farovitus said:
Well i did compile the source before i pushed it to GitHub and it was totally fine... but i will double check tomorrow.
Click to expand...
Click to collapse
did you manage to check?
Sent from my SM-N960F using Tapatalk

Phoenix09 said:
did you manage to check?
Click to expand...
Click to collapse
No, i am quiet busy these days. Send me a link of your source so i can check it out from my phone.
Again, i am sure the ELS source will compile just fine.

farovitus said:
No, i am quiet busy these days. Send me a link of your source so i can check it out from my phone.
Again, i am sure the ELS source will compile just fine.
Click to expand...
Click to collapse
https://github.com/exynos-linux-stable/crownlte
I made zero changes, what I posted is exactly what I did, it does not compile.
Edit: what OS are you compiling on?
Sent from my SM-N960F using Tapatalk

Phoenix09 said:
This source appears to be broken (apparently now differently to when I tried a few days ago):
stock source builds in the same environment.
Click to expand...
Click to collapse
Source compile just fine. Please do a proper clone to the source to avoid any issue.

4.9.140 has been merged.

farovitus said:
4.9.140 has been merged.
Click to expand...
Click to collapse
that now builds for me.. in the exact same environment, Ubuntu 14.04 in vagrant with a script:
Code:
#!/bin/sh
set -e
sudo apt-get update
sudo apt-get install -y git build-essential bc
cd $HOME
[ -d aarch64-linux-android-4.9-kernel ] || git clone --depth=1 https://bitbucket.org/UBERTC/aarch64-linux-android-4.9-kernel
[ -d crownlte ] || git clone --depth=1 https://github.com/exynos-linux-stable/crownlte
export ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- PATH=$HOME/aarch64-linux-android-4.9-kernel/bin:$PATH
cd crownlte
make exynos9810-crownlte_defconfig
make -j8

4.9.141 has been released.

hi, i need a stock note 9 pie kernel (CSB3), i flashed another kernel and it wont allow me to go past my login, can you please direct me to a stock pie kernel so i can flassh and get in?

mafioso345 said:
hi, i need a stock note 9 pie kernel (CSB3), i flashed another kernel and it wont allow me to go past my login, can you please direct me to a stock pie kernel so i can flassh and get in?
Click to expand...
Click to collapse
Don't ask here.. Just take a Rom like ketan and flash only kernel via aroma. Done
Ketan p06 has CSB3 base so that kernel will work no problem.

- 4.9.177 merged in.
- Merged CSDE OSRC into crownlte exynos-linux-stable tree.
https://github.com/exynos-linux-stable/crownlte
As always, join https://t.me/exynos_linux_stable to get instantly notified of every ELS update.

I know it's a stupid question but how to pack kernel inside IMG? I want to get image for heimdall.
I've honestly googled but it looks like everybody just knows how to do this. And nobody discuss it

-W_O_L_F- said:
I know it's a stupid question but how to pack kernel inside IMG? I want to get image for heimdall.
I've honestly googled but it looks like everybody just knows how to do this. And nobody discuss it
Click to expand...
Click to collapse
You'll want to use Android Image Kitchen to unpack and repack kernels inside images. You can diff the unpacked boot.img provided in devbase with mine to see the basic ramdisk modifications to prevent forced encryption or various other issues. Or you can just unpack my image, it's relatively basic with it's modifications. Hope this helps.
EDIT: You can also look at my make9810.sh script on GitHub to see the various steps I take for repacking my images.

Can someone explain what this is for? Is this purely for use with linux on DEX or are you guys flashing linux direct to your Note9 somehow? Or updating the kernel that android is running on?

bandario said:
Can someone explain what this is for? Is this purely for use with linux on DEX or are you guys flashing linux direct to your Note9 somehow? Or updating the kernel that android is running on?
Click to expand...
Click to collapse
It's a reference kernel source with all recent patches from vanilla kernel applied to Samsung stock one. Some developers use this source as a base for their custom kernels. This is what it's for.
ELS is for Android. But I'm developing a kernel that can boot Linux (GNU/Linux) on Note9. And yes, it's based on ELS sources.

4.9.193 has been merged into the exynos-linux-stable tree.
https://github.com/exynos-linux-stable/crownlte

lineage-14.1-20190302-[Final Build] with microG for i9300

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Wiki
Official LineageOS Wiki: http://wiki.lineageos.org/devices/i9300
Known issues
@curiousrom has a list of known issues/workarounds. You can see them here: https://forum.xda-developers.com/showpost.php?p=76224958&postcount=4419
Installation
(NOTE: if you experience robotic voice during calls: see the FAQ for a fix)
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Unfortunately, now you have to wipe to come from CM - see "First time LineageOS14.1 installation on your Galaxy S III", or if you're brave try the instructions on changing keys.
First time LineageOS 14.1 installation on your Galaxy S III:
Read the official Wiki page
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the Lineage 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the Lineage 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - Lineage Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 or higher to automatically install updates in Lineage 14.1)
Push the new Lineage 14.1 zip to your SD card
Boot into Recovery
Flash the Lineage 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Install packages: https://download.lineage.microg.org/i9300/lineage-14.1-20190302-microG-i9300.zip
Google Apps (arm): https://wiki.lineageos.org/gapps
Root add-on (arm): https://download.lineageos.org/extras
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modified system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
F.A.Q.
Root?
Flashable zips to install/uninstall root can be found here. Download the "arm" variants.
Robotic voice during calls?
Try using the I9300XXUGMK6 modem. Instructions are here.
GPS Issues?
Probably a hardware issue. Try tightening the screws on the back of the device, or see this video for more information (thanks to @baltics for the link)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly

good job
i like what you have done, only there is 1 problem. when i install the rom its in a loop while searching for updates and when i try to put data from another phone to it and i enter my google account i got a message like this: the previous owner need to log in before you can use this phone.
when i use another rom i have no problems. can you please fix this?

Thank you very much for this ROM, works very good. Haven't noticed any big problems yet

Please re-insert the rom because the link has expired

recheck download link please !!!! ??

ataman76 said:
Please re-insert the rom because the link has expired
Click to expand...
Click to collapse
HANA.BICO said:
recheck download link please !!!! ??
Click to expand...
Click to collapse
Use up to date lineageOS 14.1 and nanodroid.
E.foundation also builds a lineageOS based ROM with microG.

kurtn said:
Use up to date lineageOS 14.1 and nanodroid.
E.foundation also builds a lineageOS based ROM with microG.
Click to expand...
Click to collapse
i don't understand !! where i can download this rom ?
download link don't work !!

HANA.BICO said:
i don't understand !! where i can download this rom ?
download link don't work !!
Click to expand...
Click to collapse
https://download.lineage.microg.org/i9300/
It's been deleted from the servers, if you want this particular rom you can build it yourself.

Sly Fox007 said:
https://download.lineage.microg.org/i9300/
It's been deleted from the servers, if you want this particular rom you can build it yourself.
Click to expand...
Click to collapse
how i can build it?

HANA.BICO said:
how i can build it?
Click to expand...
Click to collapse
With dokker
https://lineage.microg.org/#faq

HANA.BICO said:
how i can build it?
Click to expand...
Click to collapse
Easiest way is with docker
I'm assuming you're using windows, here's how to install docker.
Code:
docker run \
--name=i9300_build \
-e "BRANCH_NAME=cm-14.1" \
-e "DEVICE_LIST=i9300" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend FDroid FDroidPrivilegedExtension " \
-v "C:/Users/<user>/lineageBuild/lineage:/srv/src" \
-v "C:/Users/<user>/lineageBuild/zips:/srv/zips" \
-v "C:/Users/<user>/lineageBuild/logs:/srv/logs" \
-v "C:/Users/<user>/lineageBuild/cache:/srv/ccache" \
-v "C:/Users/<user>/lineageBuild/keys:/srv/keys" \
-v "C:/Users/<user>/lineageBuild/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
with microg.xml in manifests
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lineageos4microg/android_prebuilts_prebuiltapks" path="prebuilts/prebuiltapks" remote="github" revision="master" />
</manifest>

I can provide a mirror of the last version if it is ok?
lineage-14.1-20190302-microG-i9300.zip

IceXcube84 said:
I can provide a mirror of the last version if it is ok?
lineage-14.1-20190302-microG-i9300.zip
Click to expand...
Click to collapse
Please provide an alternate link. Or suggest me good microG rom

msb arkon said:
Please provide an alternate link. Or suggest me good microG rom
Click to expand...
Click to collapse
I would take non-microG lineage 14 and apply nanodroid patcher.

OK

Sly Fox007 said:
Easiest way is with docker
I'm assuming you're using windows, here's how to install docker.
Code:
docker run \
--name=i9300_build \
-e "BRANCH_NAME=cm-14.1" \
-e "DEVICE_LIST=i9300" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend FDroid FDroidPrivilegedExtension " \
-v "C:/Users/<user>/lineageBuild/lineage:/srv/src" \
-v "C:/Users/<user>/lineageBuild/zips:/srv/zips" \
-v "C:/Users/<user>/lineageBuild/logs:/srv/logs" \
-v "C:/Users/<user>/lineageBuild/cache:/srv/ccache" \
-v "C:/Users/<user>/lineageBuild/keys:/srv/keys" \
-v "C:/Users/<user>/lineageBuild/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
with microg.xml in manifests
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lineageos4microg/android_prebuilts_prebuiltapks" path="prebuilts/prebuiltapks" remote="github" revision="master" />
</manifest>
Click to expand...
Click to collapse
Where do I have to enter this code? What do I have to do with the xml? Is there a beginner-friendly declaration?

@HANA.BICO & @EVGENIJ88 @msb-arkon
https://web.archive.org/web/20190414130532/https://download.lineage.microg.org/i9300/lineage-14.1-20190302-microG-i9300.zip
This ROM was saved by archive.org (the internet archive).
https://web.archive.org/web/20190414130532/https://download.lineage.microg.org/i9300/lineage-14.1-20190302-microG-i9300.zip

[UNOFFICIAL][RMX218x][R] Havoc-OS v4.12

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI crafted by @SKULSHADY.
Many useful features that provide a smooth premium experience.
Just flash and enjoy...
https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6
Founder & Lead Developer:
SKULSHADY (Anushek Prasal)
DevOPS & Scaling:
Irongfly (Sukeerat Singh Goindi)
Support Team:
theo.j22 (Tushar Jain)

If you like our work and would like to support this project then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
Working
- VoLTE
- WiFi & Bluetooth
- Video in NewPipe and Facebook
- Sounds are fine
- SafetyNet
Bugs
- Permissive
- 'Double Tap To Wake' in some
- If your fingerprint is not working, then see this
Notes
- It is Encrypted and Permissive
- Source compiled 4.9.206 kernel
do keep in mind that a permissive SELinux environment is not at all meant for being a daily driver. Unless you don’t have any problem with running a less secure software, you’re better off not installing it as your primary device.
Click to expand...
Click to collapse
ROM: https://androidfilehost.com/?fid=17825722713688262349 (Only for UI 1)
Mirror link is available here
About Us: https://havoc-os.com
Recovery: https://forum.xda-developers.com/t/unofficial-twrp-v3-5-2-for-realme-c12.4296429/
Code Review: https://review.havoc-os.com
1. Download the ROM, GApps (Optional) from the links above.
2. Flash the ROM, GApps (Optional and FlameGApps are suggested).
3. 'Format Data' and Wipe Cache
4. Reboot and Enjoy.
Irawan's for trees
TechyMinati for initial trees and kernel fixes
Apon77 for server at here
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
https://github.com/HemanthJabalpuri/device_realme_RMX2185/tree/havoc
https://github.com/realme-kernel-opensource/realmeC11_realmeC12_realmeC15_AndroidQ-kernel-source

microG
Havoc-OS supports Signature Spoofing and microG works out of the box without any additional steps.
Use below steps for bare minimal replacement of Play Services i.e, without any Location Services, Maps and Play Store InApp Purchases
- Flash Havoc-OS without flashing GApps
- Download and install GmsCore from https://github.com/microg/GmsCore/r...2.212658/com.google.android.gms-212658044.apk
- Download and install GsfProxy from https://github.com/microg/android_packages_apps_GsfProxy/releases/download/v0.1.0/GsfProxy.apk
- Download and install FakeStore from https://github.com/microg/FakeStore/releases/download/v0.1.0/FakeStore-v0.1.0.apk
- Go to AppInfo of microG Services Core from AppDrawer and grant all the permissions
- Open microG Services Core, go to Self-Check and make sure that all options are checked. If something is not checked, then click on it and allow for asked permission
- Go back and choose Account for adding Google Account
- Also enable Google device registration, Cloud Messaging if not enabled
- Reboot
BUILDING
Below are the instructions that I used to build Havoc-OS in Ubuntu 20.04 LTS.
Setup build environment
It will download and install packages required for building
Bash:
git clone https://github.com/akhilnarang/scripts
cd scripts && bash setup/android_build_env.sh
git config --global user.name "HemanthJabalpuri"
git config --global user.email "[email protected]"
mkdir ~/work && cd ~/work
Sync Havoc-OS ROM sources
It will download sources that have size upto 100GB. So be prepared to have that much internet and time to wait till it downloads
Bash:
repo init -u https://github.com/Havoc-OS/android_manifest.git -b eleven
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
Apply required patches
For fix booting
Bash:
cd external/selinux
curl -sL https://github.com/phhusson/platform_external_selinux/commit/f3d5e2eb212ebd4189428d6adb915880573962f9.patch | patch -p1 -b
cd -
Clone Device and Vendor trees
Our device specific trees to build.
Bash:
git clone --depth=1 https://github.com/HemanthJabalpuri/android_device_realme_RMX2185 -b havoc device/realme/RMX2185
git clone --depth=1 https://github.com/dodyirawan85/vendor_realme_RMX2185 -b lineage-18.1 vendor/realme/RMX2185
git clone --depth=1 https://github.com/dodyirawan85/android_kernel_realme_mt6765 -b lineage-17.1 kernel/realme/mt6765
Build the ROM
It is the crucial step. Its time to build ROM from sources. It may take so much depending on your PC specifications. It may take upto 7 - 15 hours for a decent PC
Bash:
. build/envsetup.sh
lunch havoc_RMX2185-userdebug
m bacon 2>&1 | tee log.txt
Get final flashable ROM zip
Code:
out/target/product/RMX2185/{ROM_NAME}.zip

Reserved

Blotooth not working, please help

Updated to 4.12

Havoc-OS-v4.12-20211221-RMX2185-Unofficial.zipfor the -Android- Generic Device/Other, by HemanthJabalpuri
OOPS!
no mirrors found.
why??

r4mskyy said:
Havoc-OS-v4.12-20211221-RMX2185-Unofficial.zipfor the -Android- Generic Device/Other, by HemanthJabalpuri
OOPS!
no mirrors found.
why??
Click to expand...
Click to collapse
Sorry, you can find mirror at here https://roms.cirrus-ci.workers.dev/0:/RMX2185/Havoc-OS-v4.12-20211221-RMX2185-Unofficial.zip

no erro?

Works okay except for one part -- System UI seems to die and start back up, then die, then start back up again. It gets annoying sometimes.
Using a Realme C12. (It calls my phone an RMX2185 instead of RMX2189)

GPS doesn't work. There's no gps.conf on it.

Better Mobile App

welcome