Database Develop

[GUIDE] How to build CM from source

Hello Guys,
In this guide i will quickly show you how to build CyanogenMod from source.
Step 1)
You will need to install Java6 (Not Java 7 or Java 5 there are not compitable)
Do the following:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
Step 2)
For faster building settup your ccache by editing bashrc:
Make a folder in your home directory callled ccache
gedit ~/.bashrc
Add these 2 lines at the end of the file:
export USE_CCACHE=1
export CCACHE_DIR=ccache
Click to expand...
Click to collapse
Step 3)
Getting the repo tool (if this is not working for the first time try this step again!)
mkdir ~/bin
PATH=~/bin:$PATH
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Click to expand...
Click to collapse
Step 4)
Make a working directory for your build!
mkdir -p ~/android/system
cd ~/android/system
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
If you are building CM10.1 use this source ~/bin/repo init -u git: https://github.com/CyanogenMod/android.git -b cm-10.1
Click to expand...
Click to collapse
Step 5)
Local manifest setup:
mkdir .repo/local_manifests
touch .repo/local_manifests/local_manifest.xml
gedit .repo/local_manifests/local_manifest.xml
then a window will open paste this in the window and save it then close the window
Click to expand...
Click to collapse
CYANOGENMOD 10.2 LOACAL MANIFEST
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.2" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
</manifest>
CYANOGENMOD 10.1 LOACAL MANIFEST
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.1" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
</manifest>
Step 6)
Syncing the repo:
cd ~/android/system
~/bin/repo sync
This can take a long long long time (depends on your pc specs)
Click to expand...
Click to collapse
Step 7)
When syncing is done do the following:
You need to do this otherwise you will get errors when building.
cd ~/android/system/vendor/cm
./get-prebuilts
Click to expand...
Click to collapse
Step 8)
Building CyanogenMod:
cd ~/android/system
source build/envsetup.sh
lunch
brunch p5wifi (For P5 use the following: brunch p5)
Click to expand...
Click to collapse
Credits:
Android open source page
Cyanogenmod WIKI
C-o-M
Kingbabasula
Good luck with building if you have any questions errors post them here and we will help you out!

safariking said:
You will need to install Java6 (Not Java 7 or Java 5 there are not compitable)
Do the following:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
Quick question: The CM build site recommends openjdk whereas the build process seems to complain about using non-oracle/sun jdk.
What's the actual jdk we should be using to build?

I always use java 6 no problems here
Sent from my GT-P7310 using xda app-developers app

safariking said:
I always use java 6 no problems here
Click to expand...
Click to collapse
I guess the question is: which one is the 'right' one to use?

I say java 6 i have seen that a lot of users here on xda are using it
Sent from my GT-I9105P using xda app-developers app

hdd space
Hi,
what's the hdd space needed for syncing the 10.2 repo?
Thanks.

Almost 10GB i recommend you to have a total disk space of 100 GB
Sent from my GT-I9105P using xda app-developers app

safariking said:
Almost 10GB i recommend you to have a total disk space of 100 GB
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
damn, so my 12 GB vmware allocated hdd is not enough
Thanks.

No
Sent from my GT-I9105P using xda app-developers app

combat2k said:
Hi,
what's the hdd space needed for syncing the 10.2 repo?
Thanks.
Click to expand...
Click to collapse
Empty tree: 8GB
Populated tree: 16GB
Post build: 34GB

question
why do I get something like below:
object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <[email protected]> 1380645867 -0700
repo 1.12.4
gpg: Signature made Ma 01 oct 2013 19:44:27 +0300 EEST using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'
when calling ~/bin/repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
There is something wrong with tag 1.12.4? Or something to add to configuration?
Thanks...

combat2k said:
why do I get something like below:
object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <[email protected]> 1380645867 -0700
repo 1.12.4
gpg: Signature made Ma 01 oct 2013 19:44:27 +0300 EEST using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'
when calling ~/bin/repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
There is something wrong with tag 1.12.4? Or something to add to configuration?
Thanks...
Click to expand...
Click to collapse
i found a solution here for the error that you are seeing : http://www.marshut.com/wrrts/repo-release-1-12-4.html
use the below command, this worked for me today.
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

Try noparse-tags and code:
Code:
[PLAIN]curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo[/PLAIN]

Hmm I had the same issue, but the above fixes didnt work for me. Finally used
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2 --no-repo-verify
and it worked.

what should I choose for lunch - step 8? it displays a list with 105 options, and... no hint about my p7300..
Thanks.

What I still don't unterstand at all is, how I can get the sources of e.g. C-o-M'S CM10.1.2 and CM10.1 nightly 2013-Aug-06 to compare it?
In Windows I used to use Total Commander to compare two folders, is there also a similar tool in Linux?

Galaxy Mini S3 "sleeps" and cannot recieve msgs/calls

I have a Samsung S3 mini, which I flashed with Kit Kat Cyanogenmod 11.0 from novafusion.pl
Everything in the installation was OK.
However my phone randomly falls "sleep" and cannot recieve msgs or calls. I have to turned Airplane mode on and off, to give it a "shake" and "wake" it up.
These is a report from Logcat, plus the log from yesterday,
Code:
build.board: montblanc
build.bootloader: unknown
build.brand: samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: golden
build.display: cm_golden-userdebug 4.4.4 KTU84Q d39c1e8ca0 test-keys
build.fingerprint: samsung/cm_golden/golden:4.4.4/KTU84Q/d39c1e8ca0:userdebug/test-keys
build.hardware: samsunggolden
build.host: novafusion.pl
build.id: KTU84Q
build.manufacturer: samsung
build.model: GT-I8190
build.product: cm_golden
build.radio: unknown
build.serial: 47900592d6cb30c0
build.tags: test-keys
build.time: 1436279173000
build.type: userdebug
build.user: root
version.codename: REL
version.incremental: d39c1e8ca0
version.release: 4.4.4
version.sdk_int: 19
I can't attach my full log because I'm new on the forum.
This is the top 30 unique lines processed by me in Bash,
Code:
[email protected]:~/Dropbox# cat 2015-07-28-10-25-50.txt | grep " E/" | cut -d "/" -f 2- | sort | uniq -c | sort -rn | head -n 30
166 Drm ( 1669): Failed to open plugin directory /vendor/lib/mediadrm
144 SpannableStringBuilder( 4288): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
118 ActivityThread( 2565): Failed to find provider info for com.google.android.wearable.settings
87 AuthorizationBluetoothService( 2483): Proximity feature is not enabled.
85 ConnectivityService( 2088): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
85 ConnectivityService( 2088): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
70 audio_a2dp_hw( 1669): adev_set_parameters: ERROR: set param called even when stream out is null
59 WifiNative-wlan0( 2088): doBoolean: disable
57 WifiNative-wlan0( 2088): doBoolean: enable
49 CallDetails( 2409): list is null in setConfUriList
48 ActivityThread(14438): Failed to find provider info for com.google.android.wearable.settings
31 MDM ( 2388): [64] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
31 BluetoothPhoneService( 2409): Could not get a handle on Connection object for the call
30 MDM ( 2388): [89] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
26 MDM ( 2388): [67] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
25 LocationReceiver( 6879): Received bad location: null
17 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x414b3f80 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
16 SpannableStringBuilder(25691): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
15 YSNP_TAG( 5072): [NetworkHelper] : [thread:1]checkNetworkChange() - no active network!
14 bp ( 2374): onStartInput event aborted: com.touchtype.keyboard.c.ag: could not obtain extracted text (class com.touchtype.keyboard.c.ag)
13 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x411acd98 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
11 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x4161b3a0 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x419f8f40
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x416a0f08
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x41490f68
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x412c9f58
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x412c8f48
8 VFM ( 1669): ! getSupportedVideoSettings RETURN_XXX_IF_WRONG, condition=(index<mNbVideoSettingsSupported[nPortIndex]), error=-2147479538(0x8000100e)(OMX_ErrorNoMore) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:407
8 VFM ( 1669): ! getSupportedProfileLevel RETURN_XXX_IF_WRONG, condition=(index<mNbProfileLevelSupported), error=-2147479538(0x8000100e)(OMX_ErrorNoMore) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:379
8 VFM ( 1669): ! getParameter RETURN_OMX_ERROR_IF_ERROR, condition=pParam->getIndexParamVideoProfileLevelQuerySupported(pt), error=-2147479538(0x8000100e)(_error) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:140

any guess?

Where are the jars in XposedInstaller from?

I started digging a little inside https://github.com/rovo89/XposedInstaller source code and would like to know where they are from.
Code:
286987 48 -rw-r--r-- 1 47645 Jan 25 13:46 ./libs/libsuperuser-185868.jar
286985 32 -rw-r--r-- 1 30181 Jan 25 13:46 ./libs/StickyListHeaders-d7f6fc.jar
286986 632 -rw-r--r-- 1 644520 Jan 25 13:46 ./libs/android-support-v13.jar
287177 1160 -rw-r--r-- 1 1184741 Jan 25 13:46 ./tools/signapk.jar
286973 100 -rw-r--r-- 1 98482 Jan 25 13:46 ./assets/XposedBridge.jar
286983 4 -rw-r--r-- 1 3191 Jan 25 13:46 ./lib/AndroidHiddenAPI.jar
Are some jar official google ones and from AOSP? From other rovo89 repositories?

Pixel 4 xl build prop and code name

Can anyone post pixel 4 XL code name and buildprop?

agstn.tanmay said:
Can anyone post pixel 4 XL code name and buildprop?
Click to expand...
Click to collapse
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Tue Aug 27 02:10:09 UTC 2019
ro.system.build.date.utc=1566871809
ro.system.build.fingerprint=google/coral/coral:10/QD1A.190821.007/5831595:user/release-keys
ro.system.build.id=QD1A.190821.007
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=5831595
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=google
ro.product.system.device=generic
ro.product.system.manufacturer=Google
ro.product.system.model=mainline
ro.product.system.name=mainline
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QD1A.190821.007
ro.build.display.id=QD1A.190821.007
ro.build.version.incremental=5831595
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2019-10-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Tue Aug 27 02:10:09 UTC 2019
ro.build.date.utc=1566871809
ro.build.type=user
ro.build.user=android-build
ro.build.host=abfarm836
ro.build.tags=release-keys
ro.build.flavor=coral-user
ro.build.ab_update=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=coral
# Do not try to parse description or thumbprint
ro.build.description=coral-user 10 QD1A.190821.007 5831595 release-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
net.bt.name=Android

Thank you ?

There is more than 1 prop file in pixel 4 xl. Can you give me "getprop" command with terminal emulator to show all of the props?
---------- Post added at 03:23 PM ---------- Previous post was at 03:20 PM ----------
ilal2ielli said:
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Tue Aug 27 02:10:09 UTC 2019
ro.system.build.date.utc=1566871809
ro.system.build.fingerprint=google/coral/coral:10/QD1A.190821.007/5831595:user/release-keys
ro.system.build.id=QD1A.190821.007
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=5831595
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=google
ro.product.system.device=generic
ro.product.system.manufacturer=Google
ro.product.system.model=mainline
ro.product.system.name=mainline
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QD1A.190821.007
ro.build.display.id=QD1A.190821.007
ro.build.version.incremental=5831595
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2019-10-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Tue Aug 27 02:10:09 UTC 2019
ro.build.date.utc=1566871809
ro.build.type=user
ro.build.user=android-build
ro.build.host=abfarm836
ro.build.tags=release-keys
ro.build.flavor=coral-user
ro.build.ab_update=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=coral
# Do not try to parse description or thumbprint
ro.build.description=coral-user 10 QD1A.190821.007 5831595 release-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
net.bt.name=Android
Click to expand...
Click to collapse
There is more than 1 prop file in pixel 4 xl. Can you give me "getprop" command with terminal emulator to show all of the props?

Trying to compile LineageOS 18.1 for discontinued SM-T713

I've been following the instrucsions from here:
[GUIDE/HOW-TO] Building LineageOS for an Unsupported Device
Foreword: This is my own notes I created to build LOS for my device (SM-T713 or gts28vewifi). After reading this, I encourage you to create your own notes as it will help you better understand the build process. I followed the official guide...
forum.xda-developers.com
To try and compile LOS 18.1, and I am using this manifest:
local_manifests/gts28vewifi.xml at lineage-17.1 · team-infusion-developers/local_manifests
Contribute to team-infusion-developers/local_manifests development by creating an account on GitHub.
github.com
And i am getting this error. Wondering if anyone has any insight into how to get past this. Thanks in advance:
[100% 182/182] out/soong/.bootstrap/bin/soong_build out/soong/build.
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android
.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile ou
t/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Androi
d.bp
error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "andr
[email protected]" depends on undefi
ned module "libperfmgr"
Module "[email protected]" is de
fined in namespace "." which can read these 1 namespaces: ["."]
Module "libperfmgr" can be found in these namespaces: ["hardware/goo
gle/pixel"]
17:31:32 soong bootstrap failed with: exit status 1

@thefanum,
While it's nice to follow the provided instructions, one of the main problems with them is that they get out of date if not updated periodically.
Specifically these commits made March 14, 2023.
https://review.lineageos.org/q/git-lfs
require that git-lfs be installed on the host computer now otherwise the compiler will stop and webview.apk won't get installed properly in the rom.
So if you are running a Debian style distro, then you need
Bash:
# install git-lfs
sudo apt install git-lfs
# cd into LineageOS code directory
cd ~/18.1
# tell build system we have git-lfs
repo init --git-lfs
# get rid of old webview
rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*.git
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*.git
# sync everything
repo sync --force-sync
Compiling the next version of Android always requires some code changes. That is, using 17.1 code and trying to build 18.1 will never work.
I've already done 99.9% of the work for T713 because the T813 and T713 share the same common code trees. Since there were no code changes from 17.1 to 18.1 for the device specific tree
https://github.com/retiredtab/android_device_samsung_gts210vewifi
and assuming none are needed for the gts28vewifi tree, then you can use the 17.1 existing tree with MY manifest from
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
That is, your version of my 181-gts210vewifi.xml should look like
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Samsung Device Trees -->
<project name="team-infusion-developers/android_device_samsung_gts28vewifi" path="device/samsung/gts28vewifi" remote="github" revision="lineage-17.1" />
<project name="retiredtab/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-18.1" />
<project name="retiredtab/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-18.1" />
<!-- Samsung MSM8976 Kernel -->
<project name="syphyr/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-16.0" />
<!-- Vendor Trees (for all devices) -->
<project name="retiredtab/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<!-- Samsung Hardware Repo -->
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-18.1"/>
<!-- Dependencies -->
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" remote="github" revision="lineage-18.1"/>
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
</manifest>
In theory, this should yield an equivalent 18.1 T713 build with the same functionality as my 18.1 T813 build.
I suggest you follow my 18.1 build specific instructions at
https://github.com/retiredtab/Linea...ob/main/18.1/181-gts210vewifi-build-guide.txt
One person on xda has followed them and created their own 18.1 T813 private builds.
I'll also make 3 suggestions during your build phase.
1. Make an "eng" build so that adb logcat starts right away so you can see log messages on your console. Once everything works, you can then build the "userdebug".
Bash:
# j4 means 4 threads. If you have 6 core, 12 thread CPU, then change this to 12.
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j4 bacon
2. My publicly released 18.1 T813 is selinux enforcing. There's no guarantee that the rules I wrote will work 100% with the T713 so you should revert/undo this commit
https://github.com/retiredtab/andro...mmit/687691a81e028d002919f9f1d069b5b0c9d72512
so that the build is permissive. Once everything works, then you can enforce the build.
3. You will need at least 16GB DRAM to make this 18.1 64 bit build. The more the better.

thefanum said:
Code:
[100% 182/182] out/soong/.bootstrap/bin/soong_build out/soong/build.
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android
.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile ou
t/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Androi
d.bp
error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "andr
[email protected]" depends on undefi
ned module "libperfmgr"
Module "[email protected]" is de
fined in namespace "." which can read these 1 namespaces: ["."]
Module "libperfmgr" can be found in these namespaces: ["hardware/goo
gle/pixel"]
17:31:32 soong bootstrap failed with: exit status 1
Click to expand...
Click to collapse
The above error is because you are trying to use the 17.1 tree and compiling 18.1 and you are not picking up the 18.1 tree at
https://github.com/LineageOS/android_hardware_samsung/commits/lineage-18.1
If you look at the March 18, 20 and 21, 2021 changes, that's where they added libperfmgr.

retiredtab said:
@thefanum,
While it's nice to follow the provided instructions, one of the main problems with them is that they get out of date if not updated periodically.
Specifically these commits made March 14, 2023.
https://review.lineageos.org/q/git-lfs
require that git-lfs be installed on the host computer now otherwise the compiler will stop and webview.apk won't get installed properly in the rom.
So if you are running a Debian style distro, then you need
Bash:
# install git-lfs
sudo apt install git-lfs
# cd into LineageOS code directory
cd ~/18.1
# tell build system we have git-lfs
repo init --git-lfs
# get rid of old webview
rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*.git
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*.git
# sync everything
repo sync --force-sync
Compiling the next version of Android always requires some code changes. That is, using 17.1 code and trying to build 18.1 will never work.
I've already done 99.9% of the work for T713 because the T813 and T713 share the same common code trees. Since there were no code changes from 17.1 to 18.1 for the device specific tree
https://github.com/retiredtab/android_device_samsung_gts210vewifi
and assuming none are needed for the gts28vewifi tree, then you can use the 17.1 existing tree with MY manifest from
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
That is, your version of my 181-gts210vewifi.xml should look like
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Samsung Device Trees -->
<project name="team-infusion-developers/android_device_samsung_gts28vewifi" path="device/samsung/gts28vewifi" remote="github" revision="lineage-17.1" />
<project name="retiredtab/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-18.1" />
<project name="retiredtab/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-18.1" />
<!-- Samsung MSM8976 Kernel -->
<project name="syphyr/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-16.0" />
<!-- Vendor Trees (for all devices) -->
<project name="retiredtab/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<!-- Samsung Hardware Repo -->
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-18.1"/>
<!-- Dependencies -->
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" remote="github" revision="lineage-18.1"/>
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
</manifest>
In theory, this should yield an equivalent 18.1 T713 build with the same functionality as my 18.1 T813 build.
I suggest you follow my 18.1 build specific instructions at
https://github.com/retiredtab/Linea...ob/main/18.1/181-gts210vewifi-build-guide.txt
One person on xda has followed them and created their own 18.1 T813 private builds.
I'll also make 3 suggestions during your build phase.
1. Make an "eng" build so that adb logcat starts right away so you can see log messages on your console. Once everything works, you can then build the "userdebug".
Bash:
# j4 means 4 threads. If you have 6 core, 12 thread CPU, then change this to 12.
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j4 bacon
2. My publicly released 18.1 T813 is selinux enforcing. There's no guarantee that the rules I wrote will work 100% with the T713 so you should revert/undo this commit
https://github.com/retiredtab/andro...mmit/687691a81e028d002919f9f1d069b5b0c9d72512
so that the build is permissive. Once everything works, then you can enforce the build.
3. You will need at least 16GB DRAM to make this 18.1 64 bit build. The more the better.
Click to expand...
Click to collapse
You're the man! Thanks so much for your help here.
I'm on it!