where to begin to port to a newer Lineage Release?

[bluess57]

Doing a make clean for me means waiting 8 to 10 hours for a build. That's something I want to avoid when I'm trying out fixes, new code, etc. At minimum, even the simplest change takes 15 minutes to compile.

What specs on pc/build machine here ? sounds excessively slow.
using ccache ? Currently getting cache hit rate 94.96 %
Grab an SSD and start building on that.
Clean build here in under an 1hr, a dirty build 3mins

 

[garak elim]

I have these two lines in my .bashrc file

export USE_CCACHE=1
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx10G"

 

[thompatry]

I have these two lines in my .bashrc file

export USE_CCACHE=1
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx10G"

Jack server is no longer around after android 8.1 (LOS-15.1). You could drop that variable if you want. Source

 

[garak elim]

I have this for cm14.1. When we finally finish lineage 16 build I drop this.

 

[garak elim]

What specs on pc/build machine here ? sounds excessively slow.
using ccache ? Currently getting cache hit rate 94.96 %
Grab an SSD and start building on that.
Clean build here in under an 1hr, a dirty build 3mins

#### build completed successfully (01:02:01 (hh:mm:ss)) ####

 

[retiredtab]

I had CCACHE=50GB at one point, but then I repartitioned my main boot drive and forgot to add it back in so my cache was sitting at 5GB with a 38% hit rate. However, even before when it was 50GB, it would still take 8 to 10 hours to compile. Unfortunately, I didn't look at the cache hit rate stats back then so I have no idea.

My build machine is a i5 660 @ 3.33Ghz, 12GB DRAM and multiple used 250GB to 500GB hard drives that I recently bought for $2.50 CAD each.

I tend to use older hardware that I get for free because they are broken and require repair or buy them for very little money. I get the most use out of them by using lean OS and lean applications.

For my i5 660 compile machine, it cost me $10 CAD with 4GB DRAM + no hard drive. This is the fastest computer I have at home. I have multiple computers at home for use, but most are older Intel duo core E8500 with 2GB to 4GB DRAM. They work perfectly fine for my simplistic use.

I just updated 2 of my roms with the latest Jan 2021 patches. Both builds were untouched since the Dec 2020 security patches until I did a repo sync today.

SM-T350. Compiler needed to compile over 5,000 files (out of 70,000).

#### build completed successfully (01:33:44 (hh:mm:ss)) ####

SM-T560NU. Compiler needed to compile over 5,000 files (out of 70,000).

#### build completed successfully (01:37:24 (hh:mm:ss)) ####

I have 2 more roms to build as I write this. I suspect both will take roughly 90+ minutes each as well. I use one hard drive for each rom so I can keep all the changes separate.

If this were my "day job", I would invest in a faster machine, 32GB DRAM and multiple 1TB SSD drives. I have learned to schedule my day around compile times.

 

[garak elim]

i5 660 is 10 years old processor. Now it's clear why it takes so long.

Intel Core i5-660 @ 3.33GHz vs AMD Ryzen 5 3600 [cpubenchmark.net] by PassMark Software

 

[retiredtab]

Firefox no more cause system crash, but every web page are blank. I see net traffic, page is downloaded, but blank.

This is CR

https://review.exynos5420.com/c/exynos5420/proprietary_vendor_samsung/+/7567

 

[retiredtab]

I fixed issue with Firefox. We need this commit https://review.exynos5420.com/c/exynos5420/android_kernel_samsung_exynos5420/+/7088
More info here https://github.com/mozilla-mobile/fenix/issues/14008

Could you please do a commit for lineage-16.0 branch.

The above is

https://review.exynos5420.com/c/exynos5420/android_kernel_samsung_exynos5420/+/7543

and now merged. I tested this on klimtwifi (SM-T700) with Firefox 84.1.4.

 

[retiredtab]

I have 16.0 klimtiwif SM-T700 booting now. With the same changes from SM-T800, it got stuck at the boot animation. I had to remove [email protected] so it would boot. I know the sensors code is still pending merge so I'm not too worried about this.

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

https://review.exynos5420.com/c/exynos5420/proprietary_vendor_samsung/+/7568

 

[retiredtab]

i5 660 is 10 years old processor.

A make clean of SM-T700.

Package Complete: klimtwifi/out/target/product/klimtwifi/lineage-16.0-20210117-UNOFFICIAL-klimtwifi.zip

#### build completed successfully (06:04:36 (hh:mm:ss)) ####

 

[garak elim]

Suggestion to commit https://review.exynos5420.com/c/exynos5420/android_device_samsung_klimtwifi/+/7565
You should change the path too to lineageos (like in chagallwifi)

 

[retiredtab]

Suggestion to commit https://review.exynos5420.com/c/exynos5420/android_device_samsung_klimtwifi/+/7565
You should change the path too to lineageos (like in chagallwifi)

Thank you for checking my work. I was so focused on fixing the sensors that I missed that.

 

[garak elim]

This path too, but I meant path /lineagehw/org/cyanogenmod/hardware/DisplayColorCalibration.java to change to /lineagehw/org/lineageos/hardware/DisplayColorCalibration.java

 

[retiredtab]

This path too, but I meant path /lineagehw/org/cyanogenmod/hardware/DisplayColorCalibration.java to change to /lineagehw/org/lineageos/hardware/DisplayColorCalibration.java

Okay, I see that. I'm going to have to figure out how to push that change though. Thanks again!

 

[tabletmen]

Do you have a testbuild to share with use for Chagallwifi ?

 

[thompatry]

Do you have a testbuild to share with use for Chagallwifi ?

Patience is a virtue.

 

[tabletmen]

I am Patience, Only was wondering if there something to test like with the LineageOS 15.1 Build.

 

[mac231us]

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

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)

AVAILABLE Lineage OS 17.1 (Android 10) Tab S (Docomo wifi cellular version)-can anyone take this up for T705?

Hello I found this developer who created Lineage 17.1 for the Docomo version of the cellular Tab S 8.4 - wondering if someone can take this on/promote to a developer to do a similar one for the SM-T705...

forum.xda-developers.com

Downloads for : Samsung Galaxy Tab S 8.4 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

 

[knosso]

Hi guys, I'm just a user and I have a Klimtlte so it's not the focus of your development. However I would like to help with your builds. If there is a way to provide my computing power to build tell me so hopefully you don't have to wait as much (or most likely you wait the same amount of time but in the meantime you can use your pc for something else). I have a 6 core phenom 1090t which seems old when you say it but I have yet to encounter something that old beast cannot do.