Database Users

[DEV] To Ubuntu Phone and Beyond

DEVS ONLY THAT EXCLUDES ROM MAKERS / USERS
Previous Info
so most of you must have heard about ubuntu touch. And a preview source of which was released. I got somr requests to build if for the 2011 line, but due to the numerous projects I have already I cant do it yet. Canconial did provide a guide to build which I sent to them, but they said it was too confusing etc. If a dev wants to build it, ill provide a simple enough guide where you have to do almost nothing except wait. If requested. *A user can too build it, but I cant solve everything so remember that.
Thank you for reading now onto the development
~emwno
It begins here.... To Ubuntu And Beyond!​
Currently got Ubuntu Touch Developer Preview on my Note II built. So far Ubuntu touch based on cm-10.1
-- NOTE these git changes are only for IYOKAN and ANZU not for any other 2011 DEVICE. Ill push those changes later
Before you begin make sure you have:
Code:
64 bit build machine (pc/laptop)
64 bit Ubuntu
Brain
Basic knowledge about source code / directories
30 gigs of free space for source code / build
Patience for source code download / build
Now if you have those, we can continue. Firstly set up the build environment
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \ zip bzr curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \ libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \ libgl1-mesa-dev g++-multilib mingw32 tofrodos \ python-markdown libxml2-utils xsltproc zlib1g-dev:i386 schedtool
Then install the tools
Code:
sudo apt-add-repository ppa:phablet-team/tools
sudo apt-get update sudo apt-get install phablet-tools
Time to get the source code. It needs patience (around 15-18 gigs)
Code:
phablet-dev-bootstrap -j 4 ubuntu-touch
Code:
cd ubuntu-touch
Now choose your Device and continue...​
Xperia Pro Specific
Time to grab the device specific repositories. Navigate to .repo/local_manifest.xml and add this.
(CTRL + H at home if not present)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="emwno/android_device_semc_iyokan" path="device/semc/iyokan" remote="github" revision="ubuntu-10.1" />
<project name="emwno/android_device_semc_msm7x30-common" path="device/semc/msm7x30-common" remote="github" revision="ubuntu-10.1" />
<project name="emwno/semc_kernel_msm7x30" path="kernel/semc/msm7x30" remote="github" revision="ubuntu-10.1" />
<project name="emwno/android_device_semc_mogami-common" path="device/semc/mogami-common" remote="github" revision="ubuntu-10.1" />
</manifest>
Code:
repo sync -j4
Now extract the proprietary blobs from your phone. For this you need cm-10.1 flashed on your phone. Connect phone to laptop and run
Code:
cd device/semc/iyokan ./extract-files.sh
And build it
Code:
. build/envsetup.sh
brunch iyokan[/list]
Xperia Arc/S Specific
Time to grab the device specific repositories. Navigate to .repo/local_manifest.xml and add this.
(CTRL + H at home if not present)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="emwno/android_device_semc_anzu" path="device/semc/anzu" remote="github" revision="ubuntu-10.1" />
<project name="emwno/android_device_semc_msm7x30-common" path="device/semc/msm7x30-common" remote="github" revision="ubuntu-10.1" />
<project name="emwno/semc_kernel_msm7x30" path="kernel/semc/msm7x30" remote="github" revision="ubuntu-10.1" />
<project name="emwno/android_device_semc_mogami-common" path="device/semc/mogami-common" remote="github" revision="ubuntu-10.1" />
</manifest>
Code:
repo sync -j4
Now extract the proprietary blobs from your phone. For this you need cm-10.1 flashed on your phone. Connect phone to laptop and run
Code:
cd device/semc/anzu ./extract-files.sh
And build it
Code:
. build/envsetup.sh
brunch anzu[/list]
If successful, your zip will be placed at out/target/product/{device code}. But just by flashing that you wont gain Ubuntu Touch. Additionally you will have to download the quantal-preinstalled-phablet-armhf.zip as well. Its the daily build of Ubuntu Touch directly from Canonical (Currently 12.10)
Instructions to flashing​
Code:
Flash kernel
Reboot in recovery
WIpe EVERYTHING (Data/System/Cache/Dalvik)
Install the zip you gained from [B]out/target/product/{device code}[/B]
Install the [B]quantal-preinstalled-phablet-armhf.zip[/B]
Reboot
------------------------------------If it doesn’t boot up then------------------------------------
Code:
Connect phone to PC and in terminal:
adb root
adb shell (then the following commands)
ubuntu_chroot shell
ubuntu-session
Sources
My Github
Ubuntu Touch

Re: [DEV](Q) Easy guide to Ubuntu touch
I recently got myself a new PC, I'll try it out and see what happens, should be a fun little thingy to do this afternoon
Dympy.
Sent from my Nexus 7 using xda premium

Re: [DEV](Q) Easy guide to Ubuntu touch
Would you still mind to post that guide incase you've some time?
Sent from my Xperia Neo V using xda premium

posted... anzu / iyokan changes pushed

Did you make anything flashable?

replicant101 said:
Did you make anything flashable?
Click to expand...
Click to collapse
please read op. or rather the first line.

emwno said:
please read op. or rather the first line.
Click to expand...
Click to collapse
Whoops, I beg your pardon.
Although, after reading it back.. I still don't get it.
Have you or, have you not, got Ubuntu Touch running on the Anzu?

I cant. i dont have the time nor the space to build it. so i posted this simplified guide. so other devs still existent on the 2011 line can build it.t

emwno said:
other devs still existent on the 2011 line can build it.
Click to expand...
Click to collapse
This made my Arc feel really old.. :/
*thanks for the guide though

replicant101 said:
This made my Arc feel really old.. :/
*thanks for the guide though
Click to expand...
Click to collapse
don't worry dude Ubuntu developers has explained, their market strategy is create roms for old phones which are don't have official android update from their producers.

Okay, finally had the sources synced, so gave it my best shot while still following your guide for Iyokan.
I ran into an error while compiling, just thought I'd share it here:
make: *** No rule to make target `/home/dympy/ubuntu-touch/out/target/product/iyokan/obj/SHARED_LIBRARIES/libgenlock_intermediates/export_includes', needed by `/home/dympy/ubuntu-touch/out/target/product/iyokan/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
[email protected]:~/ubuntu-touch$
Click to expand...
Click to collapse
Dympy.

dympy said:
Okay, finally had the sources synced, so gave it my best shot while still following your guide for Iyokan.
I ran into an error while compiling, just thought I'd share it here:
Dympy.
Click to expand...
Click to collapse
libgenlock_intermediates/export_includes
Click to expand...
Click to collapse
Some needed files are missing here. (Did you run config )

emwno said:
Some needed files are missing here. (Did you run config )
Click to expand...
Click to collapse
You mean retrieving stuff from the phone itself? Because I did that..
Dympy.
Sent from my Nexus 7 using xda premium

dympy said:
You mean retrieving stuff from the phone itself? Because I did that..
Dympy.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
try 'make clean' and 'make clobber' and try again

emwno said:
try 'make clean' and 'make clobber' and try again
Click to expand...
Click to collapse
Still nothing, going to walk my dog for a while, think out loud, and then retry some stuff..
Sent from my Nexus 7 using xda premium

do this, manually create a 'export_includes' file at the given directory. that should get you past that for sure. (if not work after build, can always use the lib from my cm10.1 build as ubuntu phone is based upon CM stripped off most of android)

emwno said:
do this, manually create a 'export_includes' file at the given directory. that should get you past that for sure. (if not work after build, can always use the lib from my cm10.1 build as ubuntu phone is based upon CM stripped off most of android)
Click to expand...
Click to collapse
I just got an email from my ISP telling me they had major connection loss from our home, apparently my dog gnawed on some of the cables..
I've replaced the cables and am now syncing the sources again, my guess is that I missed some sources..
Dympy.

emwno said:
do this, manually create a 'export_includes' file at the given directory. that should get you past that for sure. (if not work after build, can always use the lib from my cm10.1 build as ubuntu phone is based upon CM stripped off most of android)
Click to expand...
Click to collapse
Still nothing, same error as before..
Dympy.

dympy said:
Still nothing, same error as before..
Dympy.
Click to expand...
Click to collapse
Resync the iyokan device tree, make clean, copy files from phone again and compile. Made changes to the files pulled from phone, included thst lib to avoid compiling errors

emwno said:
Resync the iyokan device tree, make clean, copy files from phone again and compile. Made changes to the files pulled from phone, included thst lib to avoid compiling errors
Click to expand...
Click to collapse
Well, I still got the error..
The last lines of my terminal:
make: *** No rule to make target `/home/dympy/ubuntu-touch/out/target/product/iyokan/obj/SHARED_LIBRARIES/libgenlock_intermediates/export_includes', needed by `/home/dympy/ubuntu-touch/out/target/product/iyokan/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/dympy/ubuntu-touch/out/target/product/iyokan/obj/SHARED_LIBRARIES/libOmxCore_intermediates/import_includes
Export includes file: hardware/qcom/media/mm-core/Android.mk -- /home/dympy/ubuntu-touch/out/target/product/iyokan/obj/SHARED_LIBRARIES/libOmxCore_intermediates/export_includes
[email protected]:~/ubuntu-touch$
Click to expand...
Click to collapse
Shall I try to create the file it's looking for, like you suggested before?
Dympy.

[GUIDE][CM12] Compiling CM12 for Moto G and cherry picking features.

Here's a little something for the guys (and flashaholics) who don't like to wait for devs to release new CM12 builds.
AFAIK ROMS CAN'T BE COMPILED ON 32 BIT SYSTEMS. ONLY 64 BIT.
YOU CAN USE ANY DISTRO YOU WANT. I USE UBUNTU 14.10 DUAL BOOTED, BUT THAT'S JUST A PERSONAL PREFERENCE.
We start with setting up the build environment:
First, start with installing this:
Code:
sudo apt-get install bison build-essential curl flex git 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
Once that is done, we go about installing JDK-7 since that's the one that works for lollipop
Code:
sudo apt-get install openjdk-7-jdk
Then we install the Android SDK for some useful stuff:
Code:
sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers android-tools-adbd androidsdk-ddms android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview
Once all that is dealt with, we can move on to the repo tool. That's what will get your CM repos syncing:
Code:
mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
and then, reboot to apply the changes.
Now for the interesting part
Not really, actually.
Time to yank the CM source code.
Create a working directory where you're going to sync all the sources and do the dirty stuff.
For this guide, we'll call the working directory "cm12"
Create the directory by running
Code:
mkdir cm12
enter your working directory by typing
Code:
cd cm12
Inititialize the repo by throwing in:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
Wait for all the activity in the terminal to cease. And then type in:
Code:
repo sync
while the stuff is downloading, grab a ginger ale, or a cup of coffee and admire your handiwork. If you're the impatient type, find a generous dose of your favourite sedative, and knock yourself out for a few hours. When you're up again, you'll be faced with one of two things. Either your repos have synced successfully (yay!), or you get some nasty fetch errors. If it's the latter, then, Voila! You've just faced your first ever compiling frustration. Take some time out and break a few things, drive the neighbours crazy and then return to the PC and knock in:
Code:
repo sync -j1
This should (hopefully) work perfectly as long as you have an internet connection worth paying for. If not, then compiling probably isn't for you anyway.
Once all that stuff's over, create a folder called
Code:
local_manifests
in the .repo folder, and then make a new file in that folder called
Code:
roomservice.xml
open roomservice.xml using gedit, and add the following:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-12.0"/>
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" />
</manifest>
Then cd back to your working directory
Code:
cd ~/cm12
YOU'RE READY TO ROLL!
Finally, to build, type in:
Code:
. build/envsetup.sh && brunch falcon
If you have a really powerful PC, then use:
Code:
. build/envsetup.sh && brunch cm_falcon-userdebug -j8
And if you have a really really powerful PC, then use:
Code:
. build/envsetup.sh && brunch cm_falcon-userdebug -j16
Wait for the build to compile. Usually takes about 2-3 hours on an okay PC. You'll find your completed build in cm12/out/target/product/falcon.
The next time you want to build, run:
Code:
make clean
repo sync
. build/envsetup.sh
brunch falcon
.. and so on.
Happy Building!

What're you looking at? This is mine!

One more. Just in case.

Thought I'd add to this
Instead of breakfast and editing room service
U can manually create a folder in .repo folder name it local_manifests make a file say falcon.xml
Add contents required Im on phone now will share the code in a while
Oh and brunch falcon is enough no need adding cm_falcon-userdebug part

Thank you for the guide! (I am limited to 8 thanks per day so ill hit the thanls button tomorrow xD ) You might want to add a few more details on why we use linux distros as our compiling OSes and what toolchains, etc. are. After all those 2 reserved posts do need to be put to use.

bharat_goku said:
Thought I'd add to this
Instead of breakfast and editing room service
U can manually create a folder in .repo folder name it local_manifests make a file say falcon.xml
Add contents required Im on phone now will share the code in a while
Oh and brunch falcon is enough no need adding cm_falcon-userdebug part
Click to expand...
Click to collapse
I know. But for the time being, brunch falcon -j8 doesn't work. It requires cm_falcon..... And, yeah. I was going to add that when I logged on to Ubuntu next.

Where is cherrypicking?

fabus said:
Where is cherrypicking?
Click to expand...
Click to collapse
I'll be typing out a guide for that once my hands get over this long post.

rudi_j7 said:
I know. But for the time being, brunch falcon -j8 doesn't work. It requires cm_falcon..... And, yeah. I was going to add that when I logged on to Ubuntu next.
Click to expand...
Click to collapse
I don't normally use -j8 so not sure
Add the ccache step for users I get my build ready within about 50minutes roughly by assigning 25gb find it more efficient this way,gimme a bit I'm making a new build I'll test the -j8 part then

bharat_goku said:
I don't normally use -j8 so not sure
Add the ccache step for users I get my build ready within about 50minutes roughly by assigning 25gb find it more efficient this way,gimme a bit I'm making a new build I'll test the -j8 part then
Click to expand...
Click to collapse
I use -j8 and -j16 when I'm in a hurry... and it does work. And, right now i was just focusing on adding the most basic stuff. It takes some time and effort to type out so much.

First of all,thanks for the tutorial.
But i have a question,wich distro you use? Linux? Ubuntu? And wich number? And do you use dualboot or native? Or you have an Virtual Machine? Please,i want to know wich should i use

DeHuMaNiZeD said:
First of all,thanks for the tutorial.
But i have a question,wich distro you use? Linux? Ubuntu? And wich number? And do you use dualboot or native? Or you have an Virtual Machine? Please,i want to know wich should i use
Click to expand...
Click to collapse
Personally, I dualboot Ubuntu 14.10 on a 1TB HDD and 128 GB SSD. Virtual machines are usually much much slower, but more convenient. It all depends on whether you want to take the trouble to set up a dual boot or not.

rudi_j7 said:
Personally, I dualboot Ubuntu 14.10 on a 1TB HDD and 128 GB SSD. Virtual machines are usually much much slower, but more convenient. It all depends on whether you want to take the trouble to set up a dual boot or not.
Click to expand...
Click to collapse
Well,i'll try to configure it,but i did this a long time ago and i'm not shure do i remember. Thanks man

I built this for a friend of mine, but he says CDMA doesn't work. Any fix?

topias123 said:
I built this for a friend of mine, but he says CDMA doesn't work. Any fix?
Click to expand...
Click to collapse
So far CDMA isn't working on CM12, but there's another thread in the general section where I think CDMA works.
Sent from my OnePlus One using XDA Premium 4 mobile app

Nice tutorial,and will it be same for if we compile paranoid 5.0 ? and i learned somewhere that there are patches also to fix some basic things ?

Bhavy123 said:
Nice tutorial,and will it be same for if we compile paranoid 5.0 ? and i learned somewhere that there are patches also to fix some basic things ?
Click to expand...
Click to collapse
Generally I suppose it would be the same except for the local_manifest entries. Dunno about the patches. I haven't gone about building PA 5.0.
Sent from my OnePlus One using XDA Premium 4 mobile app

You r such a big developer and even wrote such a wonderful guide but plz write for porting latest multirom for Falcon also ,I didnt understood tassador's guide as i am a newbie,sorry if i went offtopic

Bhavy123 said:
You r such a big developer and even wrote such a wonderful guide but plz write for porting latest multirom for Falcon also ,I didnt understood tassador's guide as i am a newbie,sorry if i went offtopic
Click to expand...
Click to collapse
I'm no big dev. Always learning. About multiROM, my friend is already porting it. If he's stopped work, I'll PM you a guide.
Sent from my OnePlus One using XDA Premium 4 mobile app

Thaaank you man for that guide!
It absolutely worked for me, awesome! So glad to know how to compile my own rom now

[GUIDE] How to compile SlimLP (for d802)

Hello,
as the title says I want to help people who want to compile SlimLP Beta 0.6 for d802 themselves. I am myself a newbie to this, but found somehow out to get it working and want to share my findings. This will likely work for most d8xx versions. I make special notes where I guess you need to do a change for your d8xx version if it's not a d802.
Requirements
you need to know how to use a terminal
64-bit Linux
8GB of memory (swap counts)
at least 100GB of free disk space
recommended is also the lp bootstack and Cloudyfa's Modem
I used a VirtualBox VM with 4GB of memory with 4GB of Swap and 3 CPU Cores. I use Ubuntu 14.04 LTS (x64). If you use a different system, you might want to read the sources of these instructions.
Side Note: If you use a VM,please use "fixed size" hard disk, because dynamic allocation may lead to segmentation faults later, that are hard to track. For exchange of data you can use a shared folder or Airdroid or the likes.
100GB is adviced for compiling a single device source. 150GB is for single device with CCache. 200GB+ is for CCache and multiple devices I'd say. CCache will not be explained here, but is explained in the initializing source. Just you know it exists and it accelerates rebuilds.
Setup tools
ctrl+alt+t (on Ubuntu) to open the terminal and type in:
Code:
$sudo apt-get update
$sudo apt-get install openjdk-7-jdk
$sudo apt-get install phablet-tools
$sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zlib1g-dev:i386 zip
(the last command might be different on different OS versions see Source)
Setup and acquire the source
Code:
$mkdir ~/SlimLP
$cd ~/SlimLP
$repo init -u git://github.com/SlimRoms/platform_manifest.git -b lp5.1
Open or create a file in ~/SlimLP/.repo/local_manifests/slim_manifest.xml (.repo is hidden)
And insert the following text:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lp5.1"/>
<project name="SlimRoms/device_lge_d802" path="device/lge/d802" remote="github" revision="lp5.1" />
<project name="SlimRoms/device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="lp5.1" />
<project name="SlimRoms/kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="lp5.1" />
</manifest>
Now download source and blobs. This takes some time, so get you a beer and wait
Code:
$cd ~/SlimLP
$repo sync
(Source)
Note: You can ignore the error from repo init.
Note2: It downloads ~30GB (compressed, so actual size is way lower) and this process takes some time mostly depending on the download rate.
Note: If you want to compile for another manufacturer's device you might want to check TheLoonyBin. An alternative might be TheMuppets, that is used by CM afaik.
Prepare make
Code:
$cd ~/SlimLP
$. build/envsetup.sh
$lunch slim_d802-userdebug
Note: When you just use $lunch you see all available options
go to ~/SlimLP/kernel/lge/msm8974/arch/arm/configs
copy the name of the file (it's "slim_d802_defconfig" for d802)
open ~/SlimLP/device/lge/d802/BoardConfig.mk with a texteditor
replace "cyanogenmod_d802_defconfig" with "slim_d802_defconfig"
As of 13.09. it is no longer necessary to edit the BoardConfig.mk (see)
Make your own build with blackjack and hookers.
Code:
$cd ~/SlimLP
$make -j4 bacon
Note: -j specifies how many threads are used in the compiling process.
After a few hours depending on the memory, disk speed and CPU power you have your fresh SlimLP build. Have fun.
Credits:
Google
SlimROMs
TheLoonyBin
Josue Rivera (he explained the procedure for SlimKat to someone here)
Kind Regards
NetDwarf
PS: Subsequent (updated) compiles are realized by:
Code:
$cd ~/SlimLP
$make clean
$repo sync
$. build/envsetup.sh
$lunch slim_d802-userdebug
$make -j4 bacon
Don't omit the point in the fourth line and this is the save way to do it, but you can usually omit make clean

Nice, thanks
Nice tutorial, thanks for sharing your hard work.

NetDwarf said:
replace "cyanogenmod_d802_defconfig" with "g2-open_com-perf_defconfig"
Click to expand...
Click to collapse
Simply change to slim_d802_defconfig
https://review.slimroms.eu/#/c/5818/1/BoardConfig.mk
Still not merged lol..
Tapatalk-kal küldve az én LG-D802-el

TaRsY said:
Simply change to slim_d802_defconfig
https://review.slimroms.eu/#/c/5818/1/BoardConfig.mk
Still not merged lol..
Tapatalk-kal küldve az én LG-D802-el
Click to expand...
Click to collapse
Thank you TaRsY, I will change my guide this way. I did not sync for 2 days and they already changed it Just in case you should follow the steps in the hide/spoiler. But it makes way more sense now with the naming.

NetDwarf said:
Thank you TaRsY, I will change my guide this way. I did not sync for 2 days and they already changed it Just in case you should follow the steps in the hide/spoiler. But it makes way more sense now with the naming.
Click to expand...
Click to collapse
As I can say last days arcardinal and gmillz are working on updating the G2 repos. You sould also check the review site: https://review.slimroms.eu/ and do a repo sync.
@arcardinal @gmillz Why are these commits not merged yet to fix kernel defconfig?
for example d802
https://review.slimroms.eu/#/c/4598/
https://review.slimroms.eu/#/c/5818/

TaRsY said:
As I can say last days arcardinal and gmillz are working on updating the G2 repos. You sould also check the review site: https://review.slimroms.eu/ and do a repo sync.
Click to expand...
Click to collapse
Good to hear. I will check reviews and repos and will update the guide accordingly.

One question, why do we do
Code:
make -j4 bacon
instead of
Code:
make -j4 d802
Shouldn't it be the second way?

errikosd said:
One question, why do we do
Code:
make -j4 bacon
instead of
Code:
make -j4 d802
Shouldn't it be the second way?
Click to expand...
Click to collapse
Sry for the late answer. I don't exactly know what "bacon" means in this context, but it's not referring to the OnePlus One. Might be referring to BaCon (Basic Converter), but I'm really only guessing.

Nice guide. But I do have one recommendation. Add the vendor repo to the local_manifest so it is automatically updated when you repo sync to fetch latest sources. Also I'll get those 2 commits merged.
Sent from my LG-D800 using Tapatalk

Thank you for the addition @gmillz. I added it to the guide

[GUIDE][HOW-TO][T819]Build your own LineageOS 15.1 for T819

Hello and welcome to my first try to write an HOW-TO, don't kill me for my epic skillz in that ^^
After a nice chat with @LuK1337 that weekend I was able to build my own LineageOS ROM for our beloved Tablet. It works very nice and thus I think it should be fine to pass my information over to you, but first:
If your tablet eats your cat after that, you are on YOUR OWN! It is NOT my fault and even less the fault of @LuK1337!!
What works:
- Everything the T813 LineageOS can do + working Vibration + LTE
What does not work:
- Phone audio
So, let's start:
First you have this nice howto for the T813: https://wiki.lineageos.org/devices/gts210vewifi/build which you follow down to and including the "Download the source code" step with two lil modifications:
Install the build packages -> I had to "apt-get install python-minimal", too to make it work on Ubuntu 17.10.
Initialize the LineageOS source repository -> Well, we don't want LOS 14.1, so the command we use here is:
Code:
repo init -u https://github.com/LineageOS/android.git -b staging/lineage-15.1
After you finished the repo sync, which takes AGES on slower internet connections, you really should follow two optional steps below:
https://wiki.lineageos.org/devices/gts210vewifi/build#turn-on-caching-to-speed-up-build
https://wiki.lineageos.org/devices/gts210vewifi/build#configure-jack (Especially needed if you have not that much RAM. I did not wanna listen to @LuK1337 telling me that the build EATS RAM for breakfast, but it's true! You NEED more than 12 GB of RAM even with that setting!!)
Next one is the following lines:
Code:
mkdir -p ./.repo/local_manifests
wget https://www.dropbox.com/s/72cb5jix08y9jkv/envsetup.sh?dl=1 -O ./picks
wget https://www.dropbox.com/s/0fknl8w7zl6buz2/roomservice.xml?dl=1 -O ./.repo/local_manifests/roomservice.xml
chmod +x ./picks
repo sync
This loads the device specific stuff you will need now and prepares a step we need later.
Some useful and badly needed pickings from @LuK1337 are added when you next run this command:
Code:
./picks
Now once you are done:
Code:
. build/envsetup.sh
ALLOW_MISSING_DEPENDENCIES=true brunch gts210velte
In theory we now can go to bed and check for a result in $OUT after it finished build after about 6-10 hours. There waits a nice install ZIP for TWRP in there.
Flash on a T819 with FORMATTED and thus useable /data partition. This can and HAS TO be done in TWRP, too. If the file laments about a wrong bootloader, you should update your tablet to most recent official 7.0 firmware first!
Maybe this is a first start for ppl trying to tinker with T819 and add even more things to it, like Phone audio. At least is was a nice odyssey and the result I got was perfect. Have fun with your track down to the crazy self builders ^^
P.S. If you want GAPPS, load em here: https://sourceforge.net/projects/unofficial-opengapps-8-1/
Wanna update? SURE ^^ But be sure your picks are the most recent above.
Code:
repo forall -c 'git am --abort ; git cherry-pick --abort ; git merge --abort ; git clean -fdx ; git reset --hard' ; repo sync -j30 --force-sync -f
./picks
Code:
. build/envsetup.sh
rm -rf out ; ALLOW_MISSING_DEPENDENCIES=true brunch gts210velte
Hello, new version ^^

Updates will be added here:
15.01.18:
If you have funny build problems indicating compiler suite problems... Update the platform tools. Fixes some funny problems with newer LOS builds.
And always be sure you have the most recent picks and roomservice.xml
14.01.18:
Still wanna tinker with your own build? I updated the manual making it waay smaller thx to recent changes.
08.01.18:
https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-15-1-t3732074
https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-15-1-t3732070
Have fun, did go on LuK1337 and others nerves and this is the result. Don't expect a full featured ROM though. Calling is a bit silent when you don't hear ppl and they don't you ^^
25.12.17:
Updated the link to LuK1337's picks to a new one disabling stuff not working on new checkouts anymore. Source is LuK1337 again ^^
Completely removed the after build zip editing by modifying another file and keeping the line uncommented-out in BoardConfig.mk. This way the whole file correctly checks for the CORRECT bootloaders. This way the build.prop file in /system on the device is correct, too.
Added link to unofficial GAPPS for ppl who don't want to tinker inside GAPPS zip files.
Started some tinkering with RIL. Results up to now: ZIP file +30 MB aka LOS has all stuff built needed for telephony. Working? Naaah ^^

and where is the link to test the build

ronald_w. said:
and where is the link to test the build
Click to expand...
Click to collapse
There is none. This is a manual how to make it yourself. If I ever manage to get RIL working... MAYBE I will upload one or two builds.

emuandco said:
There is none. This is a manual how to make it yourself. If I ever manage to get RIL working... MAYBE I will upload one or two builds.
Click to expand...
Click to collapse
this is also my problem

ronald_w. said:
this is also my problem
Click to expand...
Click to collapse
So you made your own build already? Working fine (except RIL)?

emuandco said:
So you made your own build already? Working fine (except RIL)?
Click to expand...
Click to collapse
for now not working, build process without errors but the kernel will not boot the device (lineage 15.0 with other build tree) , new build is 8%

No need to build it at all. It is enough to just edit installer script. Change gts210wifi to gts20lte and delete assert for BL. It works perfect, I tried, I use it. And of courese to use newset twrp 3.2.

ivanox1972 said:
No need to build it at all. It is enough to just edit installer script. Change gts210wifi to gts20lte and delete assert for BL. It works perfect, I tried, I use it. And of courese to use newset twrp 3.2.
Click to expand...
Click to collapse
You know that we are talking about the NON Exynos devices, so you? so it is gts210VEwifi.
And even if it does, lucky you. I don't like the idea to use defconfigs for another device on my tablet.
EDIT: Current status regarding RIL... After hours with LuK1337 and his skills and code source juggling... Daemon runs, SIM detected, IMEI detected, network sorta... runs? This means SMS receiving runs and not much more for now. Still investigating.

Of courese, I forget ve to write, my lapsus. Otherwise it works perfect. They use same board.
But, if you make RIL there, it diffferent story. Every credit to you, if you need someone to test those builds I am here

ivanox1972 said:
Of courese, I forget ve to write, my lapsus. Otherwise it works perfect. They use same board.
But, if you make RIL there, it diffferent story. Every credit to you, if you need someone to test those builds I am here
Click to expand...
Click to collapse
Well, I would prefer someone knowing more of that stuff helping me to fix the remaining bugs. I even went down the pipe to try to disassemble the original libril.so but no big results from that... Right now you have all phone stuff included and thus for example can install WhatsApp again + GAPPS install the DialerFramework and Google Dialer. You get IMEI information, Baseband Information, SIM Phone Number Information and you can receive SMS, but no calling, no SMS sending and no data network works for now.
Current logcat: https://hastebin.com/iguvaxagas.xml

Thanks for hard work, I'll be very happy to have full oreo Los on tab s2!

Well I've been fiddling all day to get it to work, ubuntu 17.* have been removed from the main ubuntu site, and using the the cdimage.ubuntu locations gave me the install iso's but ended in not properly working install repos of the needed apps.
So went for 16.04 after several attempts, every installs fine, setted everything up according the tutorials in the OP and checking my old info for setting up ubuntu VM (or full pc's) what i did in the past, those where the same since my last succesfull setting up build machines.
but in the end I had to use a "repo sync -f --force-sync" instead of repo sync before ./picks, otherwise it ended up with a ton of errors in running ./picks.
After that that being running good, and finally comming to build I end up after 50 to 60 seconds in
Code:
[44/44] bootstrap /home/ragebuilder/android/lineage/out/soong/.minibootstrap/build.ninja.in
[4/4] /home/ragebuilder/android/lineage/out/soong/.bootstrap/bin/minibp /home/ragebuilder/android/lineage/out/soong/.bootstrap/build.ninja
[862/863] glob vendor/qcom/opensource/interfaces/display/config/1.0/Android.bp
[56/56] /home/ragebuilder/android/lineage/out/soong/.bootstrap/bin/soong_build /home/ragebuilder/android/lineage/out/soong/build.ninja
/home/ragebuilder/android/lineage/out/build-lineage_gts210vewifi.ninja is missing, regenerating...
[527/1117] including ./hardware/qcom/media-caf/msm8952/Android.mk ...
./hardware/qcom/media-caf/msm8952/Android.mk:4: warning: target list is : msm8952
[1117/1117] including ./vendor/samsung/zerofltexx/Android.mk ...
build/core/Makefile:34: warning: overriding commands for target `/home/ragebuilder/android/lineage/out/target/product/gts210vewifi/system/lib64/libgps.utils.so'
build/core/base_rules.mk:391: warning: ignoring old commands for target `/home/ragebuilder/android/lineage/out/target/product/gts210vewifi/system/lib64/libgps.utils.so'
build/core/Makefile:34: warning: overriding commands for target `/home/ragebuilder/android/lineage/out/target/product/gts210vewifi/system/lib64/libloc_core.so'
build/core/base_rules.mk:391: warning: ignoring old commands for target `/home/ragebuilder/android/lineage/out/target/product/gts210vewifi/system/lib64/libloc_core.so'
build/core/Makefile:34: warning: overriding commands for target `/home/ragebuilder/android/lineage/out/target/product/gts210vewifi/system/lib64/libloc_eng.so'
build/core/base_rules.mk:391: warning: ignoring old commands for target `/home/ragebuilder/android/lineage/out/target/product/gts210vewifi/system/lib64/libloc_eng.so'
[ 99% 1585/1586] glob vendor/qcom/opensource/interfaces/*/Android.bp
ninja: error: '/home/ragebuilder/android/lineage/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.internal_intermediates/classes.jack', needed by '/home/ragebuilder/android/lineage/out/target/common/obj/APPS/AdvancedDisplay_intermediates/with-local/classes.dex', missing and no known rule to make it
18:57:35 ninja failed with: exit status 1
#### failed to build some targets (54 seconds) ####
Tried resetting up the build VM now 6 times to find anything I could've done wrong, but cant find any, just end up at the same manner with this error.
Also made sure that Jack is setup properly ( https://forum.xda-developers.com/android/software/aosp-cm-los-how-to-fix-jack-server-t3575179 ) and jack starts and stops, shouldn't that also solve the ninja problem? Soz my last home build was nearly 2 years ago and a lot could have been changed, but normally google is my friend to fix it, not this time..
Has anyone some advice what to look at?

I have removed in hardware/samsung/AdvancedDisplay/Android.mk the line org.cyanogenmod.platform.internal and the directory /hardware/samsung/AdvancedDisplay/src/com/cyanogenmod/. (LineageOS 15.0)
Build is complete,
[100% 84744/84744] build bacon
Package Complete: /home/ronald/android/system/out/target/product/gts210velte/lineage-15.0-20180106_214317-UNOFFICIAL-gts210velte.zip
make: Verzeichnis „/home/ronald/android/system“ wird verlassen
#### make completed successfully (03:05:39 (hh:mm:ss)) ####
Click to expand...
Click to collapse
but for me this rom doesn't work properly --> boot stuck with sim card not detected

ronald_w. said:
I have removed in hardware/samsung/AdvancedDisplay/Android.mk the line org.cyanogenmod.platform.internal and the directory /hardware/samsung/AdvancedDisplay/src/com/cyanogenmod/. (LineageOS 15.0)
Build is complete,
but for me this rom doesn't work properly --> boot stuck with sim card not detected
Click to expand...
Click to collapse
That got me just a step furter
14:07:50 Build configuration changed: "" -> "lineage_gts210vewifi-userdebug", forcing installclean
ninja: warning: bad deps log signature or version; starting over
Click to expand...
Click to collapse
now it is waiting time agian....
But thanx for the tip!!!

RagingHarry said:
That got me just a step furter
now it is waiting time agian....
But thanx for the tip!!!
Click to expand...
Click to collapse
I have no clue what you did wrong or why you tinker with LOS 15 with a manual for 15.1, but... check post #2 and load your ROM from there.

emuandco said:
I have no clue what you did wrong or why you tinker with LOS 15 with a manual for 15.1, but... check post #2 and load your ROM from there.
Click to expand...
Click to collapse
That 15.0 was the person I quoted but that step was a test to see if it would hold further, but also then it ended up in errors and a crash of the build.
I did everything with copy pasting from the guide in OP and the linked pages, why it went wrong for me I still don't understand, have been making homebuilds since my Galaxy S2 and always got it to work.
But now you made the new LOS threads I will stick to that for now, and maybe try later again.
Thnx for your efforts and now the Unofficial support start for the T819!

RagingHarry said:
That 15.0 was the person I quoted but that step was a test to see if it would hold further, but also then it ended up in errors and a crash of the build.
I did everything with copy pasting from the guide in OP and the linked pages, why it went wrong for me I still don't understand, have been making homebuilds since my Galaxy S2 and always got it to work.
But now you made the new LOS threads I will stick to that for now, and maybe try later again.
Thnx for your efforts and now the Unofficial support start for the T819!
Click to expand...
Click to collapse
Sure, but beware, we have now device repos for gts210velte and gts28velte ^^
So roomservicexml more should look like this now:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="gts210vewifi-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="staging/lineage-15.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="staging/lineage-15.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-15.0" />
<project name="gts210vewifi-dev/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-15.1" />
<project name="gts210vewifi-dev/android_device_samsung_gts210velte" path="device/samsung/gts210velte" remote="github" revision="lineage-15.1" />
<project name="gts210vewifi-dev/android_device_samsung_gts28velte" path="device/samsung/gts28velte" remote="github" revision="lineage-15.1" />
<project name="gts210vewifi-dev/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_packages_apps_Updater" path="packages/apps/Updater" remote="github" />
</manifest>
And brunch has to be started with that hw id, too:
Code:
ALLOW_MISSING_DEPENDENCIES=true brunch gts210velte
Code:
ALLOW_MISSING_DEPENDENCIES=true brunch gts28velte
Feel free to try it, if it works, tell me. Not much time these days.

Thnx!
Gonna give it a try in a few days when I have some free time.

Feel free to try it, if it works, tell me. Not much time these days.
Click to expand...
Click to collapse
[ 90% 83198/92320] Building with Jack: /home/ronald/android/syst...mmon/obj/JAVA_LIBRARIES/services.core_intermediates/classes.jack
FAILED: /home/ronald/android/system/out/target/common/obj/JAVA_LIBRARIES/services.core_intermediates/classes.jack
ERROR: /home/ronald/android/system/frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java:260.8: The import org.lineageos.internal.util.ActionUtils cannot be resolved
ERROR: /home/ronald/android/system/frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java:2017.17: ActionUtils cannot be resolved
[ 91% 84356/92348] Building with Jack: /home/ronald/android/syst...get/common/obj/APPS/Updater_intermediates/with-local/classes.dex
ninja: build stopped: subcommand failed.
19:24:06 ninja failed with: exit status 1
#### failed to build some targets (02:35:28 (hh:mm:ss)) ####

How to build LineageOS 17.1 for the Lenovo Tab4 10 Plus

Introduction
After being a user of LineageOS for some years, I wanted to do the next step and also be able to create my own build of LOS. After some futile attempts I finally succeeded in building LOS 17.1 for the Lenovo Tab 4 10 Plus. Meanwhile even the fingerprint sensor is working, so that I think it's time to upload my builds somewhere and share them with others. In the meantime I thought it might be interesting for some out there to get a step by step instruction on how to build LOS for the Tab 4 10 Plus.
Part 1: Setting up Ubuntu 20.04 as build system
I'm a Windows user myself. Since building LOS (AFAIK) is requiring a Linux system for building (I tried with Windows Subsystem for Linux once but failed), I went for installing Ubuntu 20.04 inside a VM. VMWare Player is IMO a good choice because it's free and it allows routing USB devices to the guest system, so that it's even possible to use adb commands from within the Linux guest system and access an Android device attached via USB to the host. For this build of LOS this is not necessary, but it can be nice. But probably any VM software or, of course, a native Ubuntu 20.04 will do.
I used the following settings for the Ubuntu VM:
- 16 GB RAM
- 250 GB HDD (8 GB I used as swap space, the rest I gave to the mount point "/")
- USB compatibility I set to 3.1 and set the checkboxes for showing all USB devices and for sharing them with the VM
The above USB settings don't matter for the build. But with less RAM (inkl. swap) or less HDD space I had problems during my first attempts, even though I suspect that a bit less or RAM and HDD space might be possible. But with these settings you should be on the safe side. I opted for the full Ubuntu installation, because I did not want any tools missing that might be needed for the build. Perhaps the minimal installation would also do.
Part 2: Building LOS
There is an official documentation on how to build LOS (in this case for the device "bacon") which can be found here: https://wiki.lineageos.org/devices/bacon/build
During my first attempts of building LOS some of the commands, e.g. "repo sync" would initially fail. As far as I understood this is due to the "python" command missing in Ubuntu 20.04 after the initial setup. "python3" is available. So the first thing I did is adding a symlink "python" that points to python3:
sudo ln -s /usr/bin/python3 /usr/bin/python
After this we can follow the official LOS build documentation for some steps. So first download the Android platform tools from Google and then move to the directory where you downloaded the zip file to, e.g. via
cd Downloads
Next unzip the file (mind that the version no. inside the zip might need to get adjusted):
unzip platform-tools_r31.0.2-linux.zip -d ~
Like the build docs say we now need to add some lines to the file ~/.profile. So type
nano ~/.profile
This will start the nano editor. There right-click and paste the following lines and the end of the file:
# add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
PATH="$HOME/platform-tools:$PATH"
fi
Then press Ctrl O, Enter and Ctrl X to save and exit and then make sure that the changes get used:
source ~/.profile
Next the documentation says that a couple of software packages need to get installed. As of writing this guide, this can be done via
sudo apt-get install bc bison build-essential ccache curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5 libncurses5-dev libsdl1.2-dev libssl-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev
Afterwards some folders need to get created:
mkdir -p ~/bin
mkdir -p ~/android/lineage
Next the repo command needs to get downloaded and made executable:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
After this we again need to source the .profile file:
source ~/.profile
The ~/bin directory is already added to the path in the .profile of Ubuntu 20.04, so that there is no need to add it.
Next we need to setup the user email and name for the git commands. So replace the email address and name in the following commands:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
Now we can change to the LineageOS directory we created above and check out the code:
cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
repo sync
Next I set up the build environment via
source build/envsetup.sh
At this point we need to deviate from the official build documentation and create a file .repo/local_manifests/TBX704.xml with the specific configuration for the Tab 4 10 Plus:
mkdir .repo/local_manifests
nano .repo/local_manifests/TBX704.xml
Then paste the following XML code into this file, then use Ctrl O, Enter and Ctrl X to save and exit:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_lenovo_TB8703" path="device/lenovo/TB8703" remote="github" />
<project name="LineageOS/android_device_lenovo_TB8704" path="device/lenovo/TB8704" remote="github" />
<project name="LineageOS/android_device_lenovo_TBX704" path="device/lenovo/TBX704" remote="github" />
<project name="LineageOS/android_device_lenovo_tb-common" path="device/lenovo/tb-common" remote="github" />
<project name="lenovo-devs/android_kernel_lenovo_msm8953" path="kernel/lenovo/msm8953" remote="github" />
<!-- Vendor -->
<project name="lenovo-devs/proprietary_vendor_lenovo" path="vendor/lenovo" remote="github" revision="lineage-17.1-gxfp" />
</manifest>
Afterwards I again executed
source build/envsetup.sh
Not sure if the last one is needed, but it won't hurt. In the same way I'm not sure whether the following repo sync -c is necessary or whether we might have skipped the repo sync above and only use the following command, but I did
repo sync -c
Now we are ready to prepare the build for the Lenovo Tab 4 10 Plus and then start the build.
lunch lineage_TBX704-userdebug
mka bacon
This will take some hours. You might have noticed that I skipped setting up ccache, which is done in the official documentation. This is not a necessary but an optional step. For the first build this won't matter. For subsequent builds activating ccache might speed up the build. But it also uses up some space on the hard drive (the recommendation in the build docs is 50GB, or 20GB when activating compression). Once the build was finished successfully, you should find the zip file with the LOS image in out/target/product/TBX704/.

Thanks for sharing @Ecthelion4
A quick couple of questions.
1. Can you share details of the machine (RAM, HDD/SSD, OS, OEM) on which you build this !
2. Any details on if this would work with 8Gigs of RAM?
3. Any ideas on if this can work on MacBook Air M1 with 16Gigs of RAM + 256 Gigs of SSD?
Thanks

VGisHere said:
Thanks for sharing @Ecthelion4
A quick couple of questions.
1. Can you share details of the machine (RAM, HDD/SSD, OS, OEM) on which you build this !
2. Any details on if this would work with 8Gigs of RAM?
3. Any ideas on if this can work on MacBook Air M1 with 16Gigs of RAM + 256 Gigs of SSD?
Thanks
Click to expand...
Click to collapse
Re 1: I'm working on a Windows 10 machine with an AMD Ryzen CPU. But the exact machine specs aren't that important, as long as you fulfill the minimum specs I listed in Part 1 above. More CPU cores of course help for getting the build done more quickly.
Re 2: If you can't affort to add more than 8 GB of physical RAM, then I would assume that the build will still work, as long as you assign 16 GB or more of swap space.
Re 3: The limiting factor in this setup could be the harddisk space. Would it be possible to add an external harddisk and then build on that device? An additional question will be whether to use a VM or not. I don't know whether there is VMWare or another VM solution that would allow you to create an Ubuntu 20.04 image on one of the latest M1 BacBooks. If that is the case, then you could try using my above build instructions on such a VM. I am not sure, though, whether everything will work the same way on the ARM-based M1 CPU, but it should do. For a native MacOS M1 build I cannot help. A search on the internet might reveal better instructions for this than mine.

How's the OS working on your tablet? I have a TB-X704F and am pretty fed up with the lack of official updates.

bryangb said:
How's the OS working on your tablet? I have a TB-X704F and am pretty fed up with the lack of official updates.
Click to expand...
Click to collapse
It's working fine, just like the LOS 17.1 version from codeworkx. There is a separate thread for the 17.1 version for the Tab 4 10 Plus where I posted the latest builds.

Hey, thanks for this!
Funny I find this thread when looking for a guide on "how to build android" and it points to exactly my device!
I am interested in building LOS for lenovo TB8704 myself and I have a pretty good understanding of how it works based on your tutorial.
One thing I don't fully understand is. You pull the sources from LineageOS/android_device_lenovo_tb-common but lenovo-devs/android_device_lenovo_tb-common is used in the other TB8704 thread ( [ROM][UNOFFICIAL][10.0][tb8704f/x/v] LineageOS 17.1 for Lenovo TAB 4 8 plus) which is a fork of the first repo. Is there any reason for that? Especially because there is not difference for the branch 17.1. Same for lenovo-devs/android_device_lenovo_TB8704.
Besides that. When you build a new rom, with the latest security fixes, how do you do that? I assume you merge an other repo first? Do you have any idea how that works?
That would be great. I want to get my understanding straight before I jump into hours of compiling.
Thanks again, really appreciate your time writing this guide.
Greeting

sxe said:
Hey, thanks for this!
Funny I find this thread when looking for a guide on "how to build android" and it points to exactly my device!
I am interested in building LOS for lenovo TB8704 myself and I have a pretty good understanding of how it works based on your tutorial.
One thing I don't fully understand is. You pull the sources from LineageOS/android_device_lenovo_tb-common but lenovo-devs/android_device_lenovo_tb-common is used in the other TB8704 thread ( [ROM][UNOFFICIAL][10.0][tb8704f/x/v] LineageOS 17.1 for Lenovo TAB 4 8 plus) which is a fork of the first repo. Is there any reason for that? Especially because there is not difference for the branch 17.1. Same for lenovo-devs/android_device_lenovo_TB8704.
Besides that. When you build a new rom, with the latest security fixes, how do you do that? I assume you merge an other repo first? Do you have any idea how that works?
That would be great. I want to get my understanding straight before I jump into hours of compiling.
Thanks again, really appreciate your time writing this guide.
Greeting
Click to expand...
Click to collapse
Regarding the fork of the Lenovo common device code I can't tell you why this was done. I only took the existing repos I found in the first posting, got some help from codeworkx with some details about building the code and then setup a build. Maybe codeworkx can answer this question, but I cannot. If there are no changes in the forked repo, then it might be possible to simply use the original repo. Perhaps you can try it out?
When starting a new build I usually do cd ~/android/lineage in my existing VMWare image, then source build/envsetup.sh, then repo sync -c (perhaps adding switches for forcing the sync, if the simple sync should fail), then lunch lineage_TBX704-userdebug, followed by mka bacon.

Ah that was fast. Thanks
Yeah I might do that. Problem is, I am not in any position to judge the outcome. So I wouldn't know what differences to looks for, especially cause I installed the rom for the first time yesterday. I am running Linux anyway tho, so I don't use a VM and building shoudl be much faster.
CHeers

Hey mate, I am running my own rom now, so it was successful.
Now teh fun begis figuring out if there is other stuff to tweak. A different kernel maybe or who knows what.
Thanks again!

Hi, I am trying to use this guide to build with lineage 19.0 source, let me know if this guide works just by replacing 17.1 with 19.0. TIA

I never tried, but I would expect it's not so easy as to just exchange the version.

2 years ago I made a docker-compose for the lenovo. I have *not* been using it ever since however the good news is that in those days I was able to run it from Docker-desktop (so on windows). Have a look if you are interested its using the 18.1 version of lineage. as my docker-desktop is now 'broken' I cannot see if it works It still works after today's changes even on WSL, my 32 GB laptop is struggling though. https://github.com/rutgerellen/lenovo_tab4plus_build_docker <-- look at this