• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

where to begin to port to a newer Lineage Release?

Search This thread

AndyYan

Recognized Contributor
Jan 30, 2012
4,290
3,570
Beijing
Anyone want to take this up? apparently this developer has been making Lineage versions up to 17.1 for the Docomo version of the Tab S 8.4 cellular version (like the SM-T705)


klimtdcm uses SD800, unlike most other klimt variants with E5420. The only other similar variant is Verizon's but that one is non-unlockable to begin with.
 
  • Like
Reactions: extended84

cixelsyddyslexic

Senior Member
Sep 14, 2011
77
9
I now have SM-T700 with p-multihal merged and sensors working. I suspect the problem with the above where I had to remove the [email protected] was because I was using an old KitKat blob which I didn't know at the time.

I updated the sensors blob to Android 6 stock and now SM-T700 works with sensors and [email protected] as per

What are the chances of getting a copy of this build? I am sitting on this great device, too, but stuck way back. I understand you guys are trying to get it going, I am happy to help test things as well.
 

cixelsyddyslexic

Senior Member
Sep 14, 2011
77
9
What are the chances of getting a copy of this build? I am sitting on this great device, too, but stuck way back. I understand you guys are trying to get it going, I am happy to help test things as well.
Additionally, I would be happy to provide compute power if needed, I saw some discussion earlier about compiling on an original Core CPU. My development experience is nonexistent beyond CS courses some 20 years ago, but given instruction I can do most anything. 5900X CPU, 32GB RAM.
 
Additionally, I would be happy to provide compute power if needed, I saw some discussion earlier about compiling on an original Core CPU. My development experience is nonexistent beyond CS courses some 20 years ago, but given instruction I can do most anything. 5900X CPU, 32GB RAM.
I'm a bit worried at how desolate this thread is becoming. I bought my tablet hoping this would come to fruition 🤷🏼‍♂️.
 
  • Like
Reactions: cixelsyddyslexic

garak elim

Senior Member
Mar 18, 2014
103
45
something to encourage others
 

Attachments

  • Screenshot_20210510-070823_Settings.png
    Screenshot_20210510-070823_Settings.png
    70.5 KB · Views: 68

garak elim

Senior Member
Mar 18, 2014
103
45
This is for chagallwifi.
1. create folder "lineage-18.1" for example
2. copy roomservice.xml from here https://github.com/exynos5420/manifests/blob/lineage-17.1/roomservice.xml
3. Delete repos for other devices except for your device.
4. place the updated roomservice.xml to the folder ".repo/local_manifests/"
5. install necessary programs to build. (look here https://wiki.lineageos.org/devices/chagallwifi/build)
6. in console run these commands from lineage-18.1 folder
repo init -u git://github.com/LineageOS/android.git -b lineage-18.1
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
. build/envsetup.sh
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t universal5420-R
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t chagall-R
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7723 7724 7725 7823 7824 7826
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t R-tcpinfo-parsing-error
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7864 7825
brunch chagallwifi
7. some repopicks will need to be updated over time
8. repo sync command takes a several hours to finish (depends on internet speed) and approx 150Gb space
9. brunch chagallwifi takes a several hours to finish too (depends on computer speed)
10.finished rom is located in folder .out/target/product/chagallwifi/
 
Last edited:

garak elim

Senior Member
Mar 18, 2014
103
45
Important info for potential rom builders - many things will not work on lineage 18.1 rom. Lineage 17.1 rom is better but also doesn't work 100%.
Use it only for testing and learning purposes.
 

chrisn812

Senior Member
Dec 15, 2008
63
17
Louisville
This is for chagallwifi.
1. create folder "lineage-18.1" for example
2. copy roomservice.xml from here https://github.com/exynos5420/manifests/blob/lineage-17.1/roomservice.xml
3. Delete repos for other devices except for your device.
4. place the updated roomservice.xml to the folder ".repo/local_manifests/"
5. install necessary programs to build. (look here https://wiki.lineageos.org/devices/chagallwifi/build)
6. in console run these commands from lineage-18.1 folder
repo init -u git://github.com/LineageOS/android.git -b lineage-18.1
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
. build/envsetup.sh
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t universal5420-R
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t chagall-R
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7723 7724 7725 7823 7824 7826
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t R-tcpinfo-parsing-error
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7864 7825
brunch chagallwifi
7. some repopicks will need to be updated over time
8. repo sync command takes a several hours to finish (depends on internet speed) and approx 150Gb space
9. brunch chagallwifi takes a several hours to finish too (depends on computer speed)
10.finished rom is located in folder .out/target/product/chagallwifi/

Thanks for this. I have a spare Dell R720 i can put to work compiling tomorrow.
 

Skyh

Member
Nov 30, 2010
45
16
This is for chagallwifi.
1. create folder "lineage-18.1" for example
2. copy roomservice.xml from here https://github.com/exynos5420/manifests/blob/lineage-17.1/roomservice.xml
3. Delete repos for other devices except for your device.
4. place the updated roomservice.xml to the folder ".repo/local_manifests/"
5. install necessary programs to build. (look here https://wiki.lineageos.org/devices/chagallwifi/build)
6. in console run these commands from lineage-18.1 folder
repo init -u git://github.com/LineageOS/android.git -b lineage-18.1
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
. build/envsetup.sh
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t universal5420-R
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t chagall-R
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7723 7724 7725 7823 7824 7826
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t R-tcpinfo-parsing-error
./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7864 7825
brunch chagallwifi
7. some repopicks will need to be updated over time
8. repo sync command takes a several hours to finish (depends on internet speed) and approx 150Gb space
9. brunch chagallwifi takes a several hours to finish too (depends on computer speed)
10.finished rom is located in folder .out/target/product/chagallwifi/

Hi garak,

Thanks for posting this. I'm trying to build 17.1 for my chagallwifi, and when I get to the compilation step (brunch chagallwifi), I run into this error and it dies fairly quickly into it:


14:29:35 Build sandboxing disabled due to nsjail error.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
LINEAGE_VERSION=17.1-20210723-UNOFFICIAL-chagallwifi
TARGET_PRODUCT=lineage_chagallwifi
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-19041-Microsoft-x86_64-Ubuntu-20.04.2-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/samsung/universal5420-common vendor/samsung/chagall-common vendor/samsung/chagallwifi
============================================
FAILED: ninja: ./build/blueprint/bootstrap/build.ninja:11: loading 'out/soong/.minibootstrap/build-globs.ninja': Exec format error
subninja ${myGlobs}
^ near here
14:29:37 soong minibootstrap failed with: exit status 1


Any idea what needs to be done to get this going? Or what is happening at that "subninja ${myGlobs}" line?

EDIT: It appears this might be a WSL version 1 issue, and I guess I need to update to WSL 2 (not sure why it just didn't install version 2 in the first place... anyways, I'll update if this fixes it.
 
Last edited:

garak elim

Senior Member
Mar 18, 2014
103
45
Hi garak,

Thanks for posting this. I'm trying to build 17.1 for my chagallwifi, and when I get to the compilation step (brunch chagallwifi), I run into this error and it dies fairly quickly into it:


14:29:35 Build sandboxing disabled due to nsjail error.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
LINEAGE_VERSION=17.1-20210723-UNOFFICIAL-chagallwifi
TARGET_PRODUCT=lineage_chagallwifi
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-19041-Microsoft-x86_64-Ubuntu-20.04.2-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/samsung/universal5420-common vendor/samsung/chagall-common vendor/samsung/chagallwifi
============================================
FAILED: ninja: ./build/blueprint/bootstrap/build.ninja:11: loading 'out/soong/.minibootstrap/build-globs.ninja': Exec format error
subninja ${myGlobs}
^ near here
14:29:37 soong minibootstrap failed with: exit status 1


Any idea what needs to be done to get this going? Or what is happening at that "subninja ${myGlobs}" line?

EDIT: It appears this might be a WSL version 1 issue, and I guess I need to update to WSL 2 (not sure why it just didn't install version 2 in the first place... anyways, I'll update if this fixes it.

Here is solutions, but it's in Chinese. it looks like this error is related to wsl. You need to change something in wsl settings.
 

Skyh

Member
Nov 30, 2010
45
16
Here is solutions, but it's in Chinese. it looks like this error is related to wsl. You need to change something in wsl settings.

Thanks garak. Indeed, the issue is a WSL Version 1 thing. I removed the distro, installed WSL Version 2, and after getting everything set up again, it worked. I'm now running Lineage 18.1 on my SM-T800, and except for a couple quirks, I feel like it works pretty well. Certainly does what I use it for, generally, which is watching Twitch, and now browsing the internet on it doesn't 100% suck.
 

garak elim

Senior Member
Mar 18, 2014
103
45
Thanks garak. Indeed, the issue is a WSL Version 1 thing. I removed the distro, installed WSL Version 2, and after getting everything set up again, it worked. I'm now running Lineage 18.1 on my SM-T800, and except for a couple quirks, I feel like it works pretty well. Certainly does what I use it for, generally, which is watching Twitch, and now browsing the internet on it doesn't 100% suck.
I'm glad I helped you
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    something to encourage others
    3
    Hey Guys,

    i wanted to check what to do, for trying to port a newer Lineage release to this device.
    Any hints where to begin?

    I luckily compiled the 14.1 branch yesterday.
    But what to do next?

    Regards for the hints
    2
    I tried compiling 16.0 for chagallwifi (T800) over the fall and ran into a number of compiler problems, but when I finally got it to compile, the resulting image wouldn't boot. A lot of those problems have now been fixed in gerrit.

    I also tried 15.1 last week, but ran into a number of compile problems. Then I noticed a lot of activity on https://github.com/exynos5420 and https://review.exynos5420.com/ wrt to 16.0 so I tried again yesterday and today and I had to make 2 modifications for it to compile, but the result is an image that won't boot. The recovery image won't boot meaning somethings wrong with the boot/kernel stage.

    Hopefully the team will make more modifications over the holidays and I will have a bootable 16.0 image?
    2
    I have a 16.0 SM-T800 build booting now. Now I have to go through and see what works and doesn't work. This will take a couple of days.

    I will also document what patches I needed to make this work not only for myself, but for other future builders.
    2
    This is for chagallwifi.
    1. create folder "lineage-18.1" for example
    2. copy roomservice.xml from here https://github.com/exynos5420/manifests/blob/lineage-17.1/roomservice.xml
    3. Delete repos for other devices except for your device.
    4. place the updated roomservice.xml to the folder ".repo/local_manifests/"
    5. install necessary programs to build. (look here https://wiki.lineageos.org/devices/chagallwifi/build)
    6. in console run these commands from lineage-18.1 folder
    repo init -u git://github.com/LineageOS/android.git -b lineage-18.1
    repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags
    . build/envsetup.sh
    ./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t universal5420-R
    ./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t chagall-R
    ./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7723 7724 7725 7823 7824 7826
    ./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -t R-tcpinfo-parsing-error
    ./vendor/lineage/build/tools/repopick.py -g https://review.exynos5420.com -f 7864 7825
    brunch chagallwifi
    7. some repopicks will need to be updated over time
    8. repo sync command takes a several hours to finish (depends on internet speed) and approx 150Gb space
    9. brunch chagallwifi takes a several hours to finish too (depends on computer speed)
    10.finished rom is located in folder .out/target/product/chagallwifi/