Related
This is a guide to build CyanogenMOD 10.2 (Android 4.3) for Google Nexus 4. This guide is for OS X Mountain Lion (10.8).
[size=+1]Pre Requirements:[/size]
1) go to App Store on your OS X and Download Xcode 4. Once that is installed, open Xcode and go to preferences. There you find a tab “DOWNLOADS”, open it and there you can find “Command line tools” and next to it click INSTALL. It will take a few minutes to download and install
2) Make sure you have the android-sdk downloaded and setup adb and fastboot, so they work. It is recommended to place the android-sdk to /usr/local/
[size=+1]Initializing the build environment[/size]
First we need to set up our OS X to be able to build Android. This needs some extra things compared to for example, building in Linux, but the main stuff is pretty much the same. So let’s get started then, shall we?
Open up Terminal and type
Code:
java
If you don’t have java installed you will get a prompt to install it.
Next we will install homebrew (you can also use macports if you like)
Code:
ruby <(curl -fsSk https://raw.github.com/mxcl/homebrew/go)
Now make sure android-sdk and homebrew are in $PATH
Code:
touch ~/.bash_profile && echo "PATH=/usr/local/bin:/usr/local/sbin:$PATH:/usr/local/android-sdk/tools:/usr/local/android-sdk/platform-tools" >> ~/.bash_profile
I also recommend to add this edit to the .bash_profile file:
Code:
nano –w ~/.bash_profile
Code:
export BUILD_MAC_SDK_EXPERIMENTAL=1
Now run this and see if you need to update anything.
Code:
brew doctor
If you do (and you probably will once a day) type:
Code:
brew update
Now we need to get our dev packages
Code:
brew install git coreutils findutils gnu-sed gnupg pngcrush repo
Once that is done, run
Code:
brew outdated
if it shows anything, run
Code:
brew upgrade
Now run this the correct a few symlinks [Not sure if these are needed anymore]:
Code:
ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed
Now to create our case sensitive image for our CM work [NOTE: the 60g can be changed to anything. It only takes up what it needs but I used 60GB]:
Code:
hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 60g -volname "android" -attach ~/Desktop/Android
Now to create our working directory
Code:
cd /Volumes/Android && mkdir cm10.2 && cd cm10.2
[size=+1]Getting the source[/size]
Now to initialize the git and to download it
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Download the sources:
Code:
repo sync
Wait until it is finished. It will take a long time, depending on your internet connection.
[size=+1]Obtain the device build files and proprietary files:[/size]
To do this we will use CyanogenMods "tool" called roomservice. Roomservice is replacing the old local_manifest.xml file. Just run the code below to create the file directly into the folder.
Code:
nano -w /Volumes/android/cm10.2/.repo/local_manifests/roomservice.xml
Paste the following lines into the file:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>
</manifest>
It seems that nowadays you only need to have the TheMuppets repo there, the roomservice process takes care of the rest and downloads the needed mako bits automatically. And actually it doesn't matter what you name the xml file under the local_manifests directory. The process loads every xml file from there in a alphabetical order. If you still have that local_manifest.xml file in your .repo directory, i suggest you remove that, because at that case that file will be read first and after that all the other from the local_manifests folder
Save the file. And rerun the code:
Code:
repo sync
Download the necessary pre-builts:
Code:
/Volumes/android/cm10.2/vendor/cm/get-prebuilts
That is all. The sources are now ready.
[size=+1]Building CyanogenMOD[/size]
If you build now, you're probably gonna get kernel build errors regarding the missing elf.h header (this error might be device specific). Fortunately, we already have this file downloaded, so we only need to copy it to /usr/local/include:
Code:
cp /Volumes/android/cm10.2/external/elfutils/libelf/elf.h /usr/local/include
FINALLY, we are ready to build:
Code:
cd /Volumes/android/cm10.2 && source build/envsetup.sh && brunch mako
Change “mako” to something else if you want to build for another device (of course needs to be supported by CM)
Then we just let the Mac do the rest. Remember that it will take a while to do the build, and meantime you Macs fans will scream for mercy while CM punishes your system ☺
After the build is finished successfully you can find your newly created flashable zip by typing:
Code:
cd $out
Look for .zip file with a tag UNOFFICIAL
Happy building!
[size=+2]Credits:Imperticus (borrowed some stuff from his guide
ArmanUV (borrowed some stuff from his guide[/size]
Build errors
jeroenqui said:
if you get a similar error like this when building, here is the solution:
Zcat: /volumes/android/cm10.1/out/target/product/mako/ramdisk.img.z: No such file or directory
then it's because zcat is old and broken. Do this to fix it and use the newer version: Gzcat
sudo mv /usr/bin/zcat /usr/bin/broken-zcat
sudo ln -s /usr/bin/gzcat /usr/bin/zcat
Click to expand...
Click to collapse
And this too
Is it possibile to build on osx leopard 10.5?
Inviato dal mio Nexus 4
Excellent write up
Cice96 said:
Is it possibile to build on osx leopard 10.5?
Inviato dal mio Nexus 4
Click to expand...
Click to collapse
Not totally sure but it should be possible.
kennyp987 said:
Excellent write up
Click to expand...
Click to collapse
Thanks!
Can you do same things for aokp
Awesome work !
Envoyé depuis mon Nexus 4 avec Tapatalk
Excellent! Will give it a try and let you know how it goes! Can you maybe add instructions for cherry picks?
Thanks!!!
Sent from my Nexus 4 using xda premium
+1
Sent from my Nexus 4 using Tapatalk 2
This worked for me. Thanks OP!
how much time takes to build ?
Zasuk said:
how much time takes to build ?
Click to expand...
Click to collapse
Build times will depend on what Cpu, memory and hardrive you have.
My Macbook pro is a little older (2009) and is running a core 2 duo, with 8gigs of ram and a Momentus hybrid XT hardrive.
My build times are about 2.5 hours. Using ccache, and not doing a make clobber before the build, build times will drop down to about 30 minutes or less for me.
Just wanted to say thanks to the OP for the guide. Everything worked like a charm.
One thing I did, just to avoid any unknown problems was to download the 10.6 sdk and add it to the Xcode sdk folder just for a little extra insurance being new to building with my Mac.
i have this error any idea ? thank you for this excellent thread !
hdiutil: create failed - Ressource occupée
hey man,
what would the local_manifest.xml look like for the AT&T Galaxy S3 (d2att) ?
[GUIDE] Building CM10.1 for Nexus 4 with Mac OS X Mountain Lion (aka OS X 10.8)
jakew02 said:
hey man,
what would the local_manifest.xml look like for the AT&T Galaxy S3 (d2att) ?
Click to expand...
Click to collapse
No idea
jakew02 said:
hey man,
what would the local_manifest.xml look like for the AT&T Galaxy S3 (d2att) ?
Click to expand...
Click to collapse
This is what mine looks like for d2vzw. I'd imagine you just replace the vzw with att:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung/" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
</manifest>
Re: [GUIDE] Building CM10.1 for Nexus 4 with Mac OS X Mountain Lion (aka OS X 10.8)
How big is the sparseimage you guys made? I tried with 5gb and it filled up without finishing. My Mac partition only got 10gb of free space.
Sent from my Nexus 4 using Tapatalk 2
[GUIDE] Building CM10.1 for Nexus 4 with Mac OS X Mountain Lion (aka OS X 10.8)
sh0td0wn said:
How big is the sparseimage you guys made? I tried with 5gb and it filled up without finishing. My Mac partition only got 10gb of free space.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
5gigs isä way too small.
The source hogs at least 15gb (about) and building takes at least the same. So I made a 70gb image so it wouldn't fill up
Awesome guide! Any chance you can tell us how to build it with the Linaro toolchain and Bionic stuff everyone says makes android faster?
---------- Post added at 01:27 PM ---------- Previous post was at 12:34 PM ----------
FYI this command is failing:
/usr/bin/ruby -e "$(/usr/bin/curl –fsSL https://raw.github.com/mxcl/homebrew/master/Library/Contributions/install_homebrew.rb)"
Looks like the URL is no good any more.
EDIT: This is the new command for downloading homebrew:
ruby <(curl -fsSk https://raw.github.com/mxcl/homebrew/go)
Hey guys, i am interested in making my own ROMO for this device. I know that it will probably be difficult to do so i just wanted to know the basics, as in, what do i need to know (skills) before i fully get into making a ROM. the difficulty is not a factor, i will get it eventually
Linux based operating system and effort
start by compiling cm from the instructions on there site
chococomaxim said:
Hey guys, i am interested in making my own ROMO for this device. I know that it will probably be difficult to do so i just wanted to know the basics, as in, what do i need to know (skills) before i fully get into making a ROM. the difficulty is not a factor, i will get it eventually
Click to expand...
Click to collapse
Set up cygwin kitchen with a Linux virtual machine and learn the structure and functions of rom folders and files.. That's all you need...
Sent from my MB886 using xda app-developers app
What you need really depends on what kind of rom you want to do. For Stock Based Roms, all you need is 7-zip, Notepad++, apktool and a wrapper for it (android kitchen, etc).
You don't need Linux unless you want to compile from source. Ignore the Cygwin suggestion -- Cygwin will eat the cpu/ram up and that's whats needed the most when compiling (well, disk IO is, but....). Once you have Linux installed, do a PAC or CM10.2 build since they both fully compile and ya need to test out your build environment.
Cygwin is fine if you just need to use some Linux apps\commands every once and a while and ya don't wanna boot into Linux. Unless you have a really, really bad ass PC (8 core AMD @ 3.8ghz, 16GB+ ram, SSD) Cygwin/virtual environments won't be worth using for things like compiling.
skeevydude said:
What you need really depends on what kind of rom you want to do. For Stock Based Roms, all you need is 7-zip, Notepad++, apktool and a wrapper for it (android kitchen, etc).
You don't need Linux unless you want to compile from source. Ignore the Cygwin suggestion -- Cygwin will eat the cpu/ram up and that's whats needed the most when compiling (well, disk IO is, but....). Once you have Linux installed, do a PAC or CM10.2 build since they both fully compile and ya need to test out your build environment.
Cygwin is fine if you just need to use some Linux apps\commands every once and a while and ya don't wanna boot into Linux. Unless you have a really, really bad ass PC (8 core AMD @ 3.8ghz, 16GB+ ram, SSD) Cygwin/virtual environments won't be worth using for things like compiling.
Click to expand...
Click to collapse
Thanks for the info, I do have Linux and I want to compile from the source.
Sent from my Atrix HD using Tapatalk 4
chococomaxim said:
Thanks for the info, I do have Linux and I want to compile from the source.
Sent from my Atrix HD using Tapatalk 4
Click to expand...
Click to collapse
Which distro & what rom?
I use Manjaro Linux and schroot into Ubuntu 12.04 for compiling -- its the best of both worlds -- a fully up-to-date modern Linux distro with an environment recommended for building android. Using just Ubuntu 12.04/Mint 13 kinda sucks cause its a bit outdated -- Old versions of apps, desktop environments (Gnome, XFCE, KDE, etc). Since I've been doing it for a while now, I gotta recommend the modern Linux/schroot for android way. So far the only downside is a 20 minute increase in compile time (probably due to my 3GB ram more than anything), but the benefit of having an up to date desktop for everything else is worth it.
I'll admit that I cheated a bit. I was dual booting Manjaro and Ubuntu 12.04 until I just said screw it and setup the schroot. Normally with an schroot setup, the other environment is setup from a basic command line environment and if you copy/paste the apt-get commands from the various guides around you'll be missing necessary files (those guides are written assuming you're doing it from an actual desktop install which includes a lot more files than the bare minimum command line only install). I've done schroot environments both ways and using my dual boot OS as my schroot has worked better (only problem is the GUI is broke if I try to boot into Ubuntu now, but apt-get update and upgrade work, from boot and schroot, and that's the only reason I'd actually boot into now anyways).
skeevydude said:
Which distro & what rom?
I use Manjaro Linux and schroot into Ubuntu 12.04 for compiling -- its the best of both worlds -- a fully up-to-date modern Linux distro with an environment recommended for building android. Using just Ubuntu 12.04/Mint 13 kinda sucks cause its a bit outdated -- Old versions of apps, desktop environments (Gnome, XFCE, KDE, etc). Since I've been doing it for a while now, I gotta recommend the modern Linux/schroot for android way. So far the only downside is a 20 minute increase in compile time (probably due to my 3GB ram more than anything), but the benefit of having an up to date desktop for everything else is worth it.
I'll admit that I cheated a bit. I was dual booting Manjaro and Ubuntu 12.04 until I just said screw it and setup the schroot. Normally with an schroot setup, the other environment is setup from a basic command line environment and if you copy/paste the apt-get commands from the various guides around you'll be missing necessary files (those guides are written assuming you're doing it from an actual desktop install which includes a lot more files than the bare minimum command line only install). I've done schroot environments both ways and using my dual boot OS as my schroot has worked better (only problem is the GUI is broke if I try to boot into Ubuntu now, but apt-get update and upgrade work, from boot and schroot, and that's the only reason I'd actually boot into now anyways).
Click to expand...
Click to collapse
I have Linux mint 15 and going to use a cm build
Sent from my Atrix HD using Tapatalk 4
Should I stay where I'm at or do something similar to what you are doing
Sent from my Atrix HD using Tapatalk 4
chococomaxim said:
I have Linux mint 15 and going to use a cm build
Sent from my Atrix HD using Tapatalk 4
Click to expand...
Click to collapse
You shouldn't have to do much more than search xda for an Ubuntu 13.04 guide (I think Mint 15 is Ubuntu 13.04). From there its pretty much
make a directory for the source, open a terminal, cd to the created directory
repo init -u https://github.com/CyanogenMod/android.git -b cm-10.2
add the codebox below to a new file named roomservice.xml
repo sync
-. vendor/cm/get-prebuilts
. build/env-setup.sh
brunch mb886
To update and build a new rom
make a copy of the last compiled rom if necessary (located at out/product/mb886)
open terminal at source directory
make clean
do everything from repo sync to brunch
Everything in italics is terminal commands
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_motorola_mb886" path="device/motorola/mb886" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_motorola_msm8960-common" path="device/motorola/msm8960-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_motorola_msm8960-common" path="kernel/motorola/msm8960-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-10.2" />
</manifest>
Lots of the guides suggest using CCACHE, but I gotta recommend NOT using it. In the past I did use it, but sometimes builds would have random errors, FC's, and whatnot, and builds using the same sources (no repo sync) with CCACHE disabled didn't have the random bugs. Ccache might speed up the 2nd build and on, but risking random bugs isn't worth the small speed up IMHO.
---------- Post added at 01:00 PM ---------- Previous post was at 12:47 PM ----------
chococomaxim said:
Should I stay where I'm at or do something similar to what you are doing
Sent from my Atrix HD using Tapatalk 4
Click to expand...
Click to collapse
If you're happy with Mint 15, then stay with it. You might run into some Python2/3 issues, but the rest of it should work fine. "repo" doesn't like Python 3 and doesn't like being initialized with 3 and syncing with 2 and vice-a-versa. Luckily, the OpenJDK/Java7 patches are included in the CM repos now, so the BS of installing Java6 isn't here anymore (be glad you don't have to deal with it).
If you're having a difficult time using an updated Linux as an android build environment, then consider using the schroot way. IMO, its worth at least to try to compile on your current system -- only go the schroot or dual boot if your current system doesn't like android compiling.
skeevydude said:
If you're having a difficult time using an updated Linux as an android build environment, then consider using the schroot way. IMO, its worth at least to try to compile on your current system -- only go the schroot or dual boot if your current system doesn't like android compiling.
Click to expand...
Click to collapse
I'm also going to get a Linux install up (Debian 7.10), and probably going to start building/compiling, and will very likely run into issues. Would there be any extra packages I would need besides that giant list in every build guide to get it working right? Would there be issues like there would be trying to build with 13.04? I know Ubuntu is what everyone uses for compiling, but I'd rather be at the base of everything.
Also, incase there are big issues, how would we go about setting up a schroot?
skeevydude said:
You shouldn't have to do much more than search xda for an Ubuntu 13.04 guide (I think Mint 15 is Ubuntu 13.04). From there its pretty much
make a directory for the source, open a terminal, cd to the created directory
repo init -u https://github.com/CyanogenMod/android.git -b cm-10.2
add the codebox below to a new file named roomservice.xml
repo sync
-. vendor/cm/get-prebuilts
. build/env-setup.sh
brunch mb886
To update and build a new rom
make a copy of the last compiled rom if necessary (located at out/product/mb886)
open terminal at source directory
make clean
do everything from repo sync to brunch
Everything in italics is terminal commands
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_motorola_mb886" path="device/motorola/mb886" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_motorola_msm8960-common" path="device/motorola/msm8960-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_motorola_msm8960-common" path="kernel/motorola/msm8960-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-10.2" />
</manifest>
Lots of the guides suggest using CCACHE, but I gotta recommend NOT using it. In the past I did use it, but sometimes builds would have random errors, FC's, and whatnot, and builds using the same sources (no repo sync) with CCACHE disabled didn't have the random bugs. Ccache might speed up the 2nd build and on, but risking random bugs isn't worth the small speed up IMHO.
---------- Post added at 01:00 PM ---------- Previous post was at 12:47 PM ----------
If you're happy with Mint 15, then stay with it. You might run into some Python2/3 issues, but the rest of it should work fine. "repo" doesn't like Python 3 and doesn't like being initialized with 3 and syncing with 2 and vice-a-versa. Luckily, the OpenJDK/Java7 patches are included in the CM repos now, so the BS of installing Java6 isn't here anymore (be glad you don't have to deal with it).
If you're having a difficult time using an updated Linux as an android build environment, then consider using the schroot way. IMO, its worth at least to try to compile on your current system -- only go the schroot or dual boot if your current system doesn't like android compiling.
Click to expand...
Click to collapse
i found this link from the CM wiki http://wiki.cyanogenmod.org/w/Build_for_mb886 and i was wondering what would be the different because it has totally different commands than what you provided. is it because this the wiki guide is 10.1 and the one you had was 10.2?
chococomaxim said:
i found this link from the CM wiki http://wiki.cyanogenmod.org/w/Build_for_mb886 and i was wondering what would be the different because it has totally different commands than what you provided. is it because this the wiki guide is 10.1 and the one you had was 10.2?
Click to expand...
Click to collapse
I believe it's all the same, except when you get to the repo init, change cm-10.1 to cm-10.2.
Sent from my MB886 using xda app-developers app
Hey guys
I guess you already know the drill It's more-less the same as we did on CM11, but Adam77Root isn't actively developing for the device anymore and also Demetris isn't working on this project anymore. I am pretty busy lately myself, which is why you shouldn't expect any miracles soon.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, and we will most likely merge it happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let us know about it before you release it and give credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
You tell me
Possibly more
Working:
Everything else
Now, the most important part:
Download
All builds can be found on my goo.im account:
CM12
CM12.1
Please note that goo.im is currently having issues, which is why the latest builds are available from the devDB downloads tab.
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[ROM] [WIP] Unofficial CM12.1 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf, Adam77Root, sunsettrack4
Source Code: https://github.com/P880-dev/android_kernel_lge_x3/tree/cm-12.0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-11-09
Last Updated 2015-04-06
Reserved
I have used the following local_manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- p880 specific stuff -->
<project name="P880-dev/android_device_lge_p880" path="device/lge/p880" remote="github" revision="cm-12.0" />
<project name="P880-dev/android_kernel_lge_x3" path="kernel/lge/x3" remote="github" revision="cm-12.0" />
<project path="vendor/lge" name="P880-dev/proprietary_vendor_lge" revision="cm-12.0" />
<remove-project path="device/asus/fugu" name="device/asus/fugu" groups="device,fugu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/fugu-kernel" name="device/asus/fugu-kernel" groups="device,fugu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/grouper" name="device/asus/grouper" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/tilapia" name="device/asus/tilapia" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder" name="device/htc/flounder" groups="device,flounder" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder-kernel" name="device/htc/flounder-kernel" groups="device,flounder" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu" name="device/moto/shamu" groups="device,shamu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu-kernel" name="device/moto/shamu-kernel" groups="device,shamu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/samsung/manta" name="device/samsung/manta" groups="device,manta" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
</manifest>
if you run into some errors, just remove the according "remove-project" line and you should be fine
Thank you!
Thank you @laufersteppenwolf, @Demetris for all your efforts! I'll build it later, and try to help you with logs and anything else i can do, as much as i can! Keep up, mates, brilliant job!
Thanks man! I will go download sources now!
SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
Tim_Pan said:
SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
Click to expand...
Click to collapse
SF issues should be gone, is you've got the latest sources. It was related to SELinux, which is why I completely killed it via kernel for now
Also, I highly doubt that you're gonna have much success using the stock blobs (which is why I'm not even gonna try)
I wil try building when I get home
Any News?
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
Yeah good idea.
fritzcola said:
Any News?
Click to expand...
Click to collapse
Not really haven't got much free time lately to test...
iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
laufersteppenwolf said:
Not really haven't got much free time lately to test...
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
No Problem
Keep up the great work.
Im sure you are going to fix it soon.:good:
laufersteppenwolf said:
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.
If anyone get a bootable Build, can he upload it!!
Thx
fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
Help us to achieve that
If i could of course i would but im sure i cant help you. My skills are very little
iSWORD14 said:
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.
Click to expand...
Click to collapse
Well, some may do that, but I am not like that I have seen just too many things happen to phones just because people didn't read and just downloaded something with the name of their device on it.
fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
The same thing as last time is going to happen: As soon as we've got a halfway working build, it will be released. Until then, there won't be a public release.
And I also ask anyone to please not publically post a build until it doesn't properly work (and by properly I mean the important things like network, audio, ... )
Alright, a general update on the situation:
SF issues are gone and we've got a boonanimation. But ATM, we are bootlooping due to audio issues.
The problem is, I have no idea what exactly is causing the issues, as the logs do not specify it (it's literally being shown as <unknown>). I was hoping that fixing the AudioWrappers would at least resolve the bootloop, but no dice.
If you want to look into it yourself, logcat and a strace from mediaserver is located HERE
Thanks to @LGaljo for the logs
News?
Busaton said:
News?
Click to expand...
Click to collapse
Dont think so
There are no news, because we keep everything private and deliberately not telling anything about the progress that have been made. :beer:
Any news about LOS 15 for Xiaomi Mi Mix2?
https://drive.google.com/file/d/1Xf-ULJcr0UptEutLxUFPDrcoTGVzUm3G/view?usp=sharing
I'm confused, what is that link?
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
Its Arasthels lineage 15.1 build, does this guy have permission to issue it?
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
I wanned to ask as well. Who merged that and who has given the shout of the link. Getting LOS15 indtalled would blow up my f...en brain right on to the ceiling for sure
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
fbousk said:
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
Click to expand...
Click to collapse
Aaaah now I get it. Thank you. We'd better wait on him to say something when he feels it's ready enough.
armsar1978 said:
Any news about LOS 15 for Xiaomi Mi Mix2?
https://drive.google.com/file/d/1Xf-ULJcr0UptEutLxUFPDrcoTGVzUm3G/view?usp=sharing
Click to expand...
Click to collapse
Seriously, what's that thread ?
Is your link coming from a reliable source (in that case, make a proper OP with bugs, issues, credits, sources) ? Or did you just download a zip from github branch wich means it's a "[email protected]#!*!!#€upyourphone" ?
If it's the second case, this is really a bad joke considering people awaiting here.
If it's just a question, it's also a bad joke and not the right place to post.
Envoyé de mon MI Mix 2 en utilisant Tapatalk
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
fbousk said:
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
Click to expand...
Click to collapse
Aaaah now I get it. Thank you. We'd better wait on him to say something when he feels it's ready enough.
I almost got an heart attack
So, I tried and I can confirm it's legit.
Benjimaestro said:
So, I tried and I can confirm it's legit.
Click to expand...
Click to collapse
So, it boots ? No real major issue for the moment ?
Thx
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="vendor/xiaomi/chiron" name="LineageOS-chiron/android_vendor_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="device/xiaomi/chiron" name="LineageOS-chiron/android_device_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="kernel/xiaomi/msm8998" name="LineageOS-chiron/android_kernel_xiaomi_msm8998" remote="github" revision="chiron-oreo-8.1" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" />
<project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" remote="github" />
<project path="packages/lineage/livedisplay" name="LineageOS/android_hardware_lineage_livedisplay" remote="github" />
</manifest>
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Arasthel said:
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="vendor/xiaomi/chiron" name="LineageOS-chiron/android_vendor_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="device/xiaomi/chiron" name="LineageOS-chiron/android_device_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="kernel/xiaomi/msm8998" name="LineageOS-chiron/android_kernel_xiaomi_msm8998" remote="github" revision="chiron-oreo-8.1" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" />
<project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" remote="github" />
<project path="packages/lineage/livedisplay" name="LineageOS/android_hardware_lineage_livedisplay" remote="github" />
</manifest>
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Click to expand...
Click to collapse
Thank you so much !
Wahoux said:
Thank you so much !
Click to expand...
Click to collapse
Absolutely terrific. Do I need to get thru Xiaomi 7.1 firmware or can I just switch from MIUI Oreo beta. That Is my major concern. Thanks for this beauty
enzo_cz said:
Absolutely terrific. Do I need to get thru Xiaomi 7.1 firmware or can I just switch from MIUI Oreo beta. That Is my major concern. Thanks for this beauty
Click to expand...
Click to collapse
I came from Miui Oreo, and just formated data before flashing LOS, and works fine
Wahoux said:
Thank you so much !
Click to expand...
Click to collapse
Wahoux said:
I came from Miui Oreo, and just formated data before flashing LOS, and works fine
Click to expand...
Click to collapse
Thanks man, I appreciate that
Amazing timing, my Mi Mix 2 is being delivered tomorrow, i cannot wait to play!
Thank you!
Arasthel said:
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Click to expand...
Click to collapse
@Arasthel
Well, this is pretty good news ! But in an unconventional way. This thread is going to be spammed with questions about how to flash, which twrp, from what firmware do we need to come, dirty flash over LOS14, what's working, what's not and so on ...
Couldn't it be better that you start an official new thread and ask mods to merge this one as replies ?
Anyway, I was waiting for this. Great job Man ! Waiting for some more infos / procedure before flashing.
Envoyé de mon MI Mix 2 en utilisant Tapatalk
For flash, I'm coming from Oreo bêta Miui and have juste full wipe.
For me, the Best custom rom (Aosp) so far !!! No bug for the moment and buttery smooth !!!
Wahoux said:
So, it boots ? No real major issue for the moment ?
Thx
Click to expand...
Click to collapse
Boots very quickly. No major issues so far. Calls, SMS, mobile data, BT, camera, audio, performance are all good.
Input lag seems to be better than nougat.
For a sketchy looking alpha release it's VERY good.
Only issue is that the FP scanner vibrates if touched at any time, which causes the phone to vibrate. Just a minor annoyance.
Shuyin10 said:
For flash, I'm coming from Oreo bêta Miui and have juste full wipe.
For me, the Best custom rom (Aosp) so far !!! No bug for the moment and buttery smooth !!!
Click to expand...
Click to collapse
wow, thats encouraging! Great work to all involved. :good:
I've applied for unlock, just waiting for the sms, so by the time all that comes through this (or a proper thread) will have expanded a little.
I've missed tinkering with my phones, not done it since my htc one
Hello, ladies, gentlemen and non-booleans!
Since I prefer building my own ROMs for various reasons, especially when the device tree source isn't made public, I have now finally gotten a LineageOS 18.0 build together.
"But there's already a build there!"
Fair point, but the sources of the device tree and kernel aren't public anywhere, to my knowleadge.
While I'm nowhere near as much of an open source fanatic as to demand all the source everywhere, it doesn't feel right either.
So since I've got a habit of having my own builds so I myself decide when I get an update, I decided to spin one up and at the same time provide a workaround for others who want to build their own versions.
So, what did I do? Voodoo? Other black magic? No!
I looked at crDroid's Github and the source tree seemed to be largely compatible with the LOS build system customisations.
They seem to often be working pretty closely with LOS build conventions.
They even specifically host a kernel there that has got an Android 11 branch!
And with that, we come to the sources used section:
Sources used:
Xiaomi-common
device
Kernel
So, how would you get your own private builds?
Do a repo sync as normal, then put into
.repo/local_manifests/roomservice.xml the following:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/tissot" name="crdroidandroid/android_device_xiaomi_xiaomi" remote="github" revision="11.0" />
<project path="kernel/xiaomi/msm8953" name="crdroidandroid/android_kernel_xiaomi_tissot" remote="github" revision="11.0" />
<project path="vendor/xiaomi/" name="crdroidandroid/proprietary_vendor_xiaomi" remote="github" revision="11.0-tissot" />
<project path="device/xiaomi/msm8953-common" name="crdroidandroid/android_device_xiaomi_msm8953-common-tissot" remote="github" revision="11.0" />
</manifest>
Do another sync and you're going to have everything you need downloaded. From there it's the usual procedure for builds.
"So, Lilly, that's all well and good, but why upload yet another LOS build?"
Because I've got itchy fingers and while I'm definetely not qualified myself to improve the device tree myself, you could profit from my addiction to doing builds quite frequently and get the latest feature changes pretty quickly.
Aside from that, I also plan on integrating Opengapps into the builds using their build system plugin. I didn't do it right away because last time there were some errors I couldn't figure out and I wanted a build right now.
Another thing I want to get working is having LuciferKernel preinstalled in the overclocked variant, because that overclock is definitely helping performance in my experience. Keep that in mind before installing. If you've got gripes about overclocking and I get the kernel to work (last in tree compilation resulted in an unbootable kernel) you're going to be stuck on the first vanilla version.
All in all, it's just sharing something what I use and trying to fill a tiny niche.
Do keep in mind that I'm definetely not a complete wizard and not an Android ROM developer. I just about know how to build a ROM and how to manipulate it here and there. I provide no support aside from "this build is borked, could you try again?".
That said, here's the download link:
ROM Downloads - Google Drive
drive.google.com
The first build hasn't been tested yet so do not expect to plug and play. I'm in the process of flashing it as I type this. MAKE BACKUPS!
Right, that should just about cover everything. Cheers!
Update: So far it's not booting and throwing up a couple of errors in the logcat. Hm.
I'll examine it a bit tomorrow.
Another update: Flashed crDroid and the same opengapps I used for my LOS build and now it's failing to boot in a similar manner... Weird.
Another update: It boots without that borked opengapps package.
Here's some proof that it boots successfully!
_I did a derp_
I noticed I had synced LOS 18 instead of 18.1
I just finished syncing the other branch and a new build will follow. Should be directly upgradable.
crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards
murtaza1326 said:
crdroid is based on Lineage os & since it's identical in many ways it shares many stuff well lineage os maintainer(aka maintainer of Pixel experience) abhinav gupta is handling it there are some stuffs & some (he preferes to open sources after he goes official for his device) that's how it works on last update he did it with pixel experience but since it's likely near dead his primary focus is on Lineage os thus until tissot doesn't recieve official Lineage os 18.1 he won't release his stuff publically
since you are using my stuff i still suggest to wait for him to do release it
Regards
Click to expand...
Click to collapse
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?
lillywho said:
I don't quite see why I shouldn't make my own builds. It's not like I'm not being transparent about my intentions or to what extent I can work on a ROM.
It's just that I want to build my own builds and I can't do that when people don't do upload their sources. May I ask what you're getting at?
Click to expand...
Click to collapse
i never said that you should not make your own builds but it device side source stuff take reasonable amount of time & hardwork they put about it
imagine you are one of dt maintainers & you publically share your work & people will use it before even waiting for you & giving you first chance (happens alot here)
thus he does this until they get green flag to do so from source side he won't do it
also if i decided to keep my stuff private literally no rom execept abhinav's & sooti (aosp gsi)
would exist for this device (i bet)
you are free to use any of my trees & stuff & make builds but please don't hop over multiple roms (like a mad person) (happens in our community alot)
there are more rom on telegram built by BBots (but they don't regularly update those)
if this is just a personal build & you are not going to update it in feature just don't share it
thanks & regards
What is the current situation?