[ROM][S9+/S9][UNOFFICIAL][LineageOS 18.1][21-03-2021]

Search This thread
By:
Advanced…
Neurotical

Neurotical

Senior Member
Feb 7, 2011
244
400
ElPakoTech said:
Hi,

Many reason I guess, :)

Because It's fun ! teaching yourself how to do it, making your own and learning how to do it, having a better understanding of how it works, this is something I like to do.

I also want to see If I can apply small patch, maybe try to resolve some bug in the future, not sure if my knowledge would be enough.

But I understand what you mean, and team up to make a build for everyone look like doing an Official support. It would be nice, but you need a good understanding of the source code. Also you need to follow the Lineageos requirements : https://wiki.lineageos.org/submitting_device.html , https://github.com/LineageOS/charter/blob/master/device-support-requirements.md

@sinnl0s , @gnarf49

Using WSL to build look tricky but I am glad you did it !
I used a docker image for making my builds : https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd
- sources: https://github.com/lineageos4microg/docker-lineage-cicd

It work really fine to me, it's base on ubuntu 20.04 and updated for lineage 18.1. You can sign the build with keys and there is also options for MicroG signature spoofing if you want (I'm not using it).

I am just a bit confuse about one thing: the tag "dev-keys" instead of "released-keys" in the build name, not sure if it's normal as the process look different than the official docks (https://wiki.lineageos.org/signing_builds.html). But the build looks correctly signed so I guess it's ok.

Let me know if for some reason it's better to not use this docker image, I am very open to advice.


Today I uploaded a new build for starlte with security patchs from June 5 : https://github.com/pakaoraki/OTA/releases
I am currently running it and so far so good, no problem. I am happy to share it, but the build is signed with my own keys so dirty flash won't work (you will need fresh start with TWRP), but OTA is ok if you're already installled the previous one. For people who want to use it, let me know if you have any issues.
Click to expand...
Click to collapse
How did you get github to accept such a large file to upload? I tried it but it said it was too big.

On another note, maybe we could keep regularly checking in on this sub to just let each other know the compile worked with each new security update. I can confirm that the LOS 18.1 compile with June 5th security update works, just as you completed it 😀
 
G

geronimoge

Senior Member
Aug 4, 2016
516
128
Is there any chance to get regularily updates without having to make a clean install? I assume not.
I'm asking since it always takes me many hours until the device is set up as needed.
So propably I'll switch to ArrowOS hoping that updates will be delivered there for the next year or so.
 
M

murtzsch

Member
May 10, 2014
36
20
I've also built it and dirty flashed it, looking at logs (dmesg/logcat) I can see my kernel logs are flooded when the screen is on :
" [3: kworker/u17:2: 5042] [SSP]: MSG From MCU - SSP_batch_full 60 60 0

Any of you ever encountered this issue ?
edit: looks like it's gone with the lineageos-18.1 branch instead of 4.9.118.
still having weird issues, probably related to old vendor files
 
Last edited:
  • Like
Reactions: ElPakoTech
E

ElPakoTech

Member
Apr 18, 2020
21
30
Neurotical said:
How did you get github to accept such a large file to upload? I tried it but it said it was too big.

On another note, maybe we could keep regularly checking in on this sub to just let each other know the compile worked with each new security update. I can confirm that the LOS 18.1 compile with June 5th security update works, just as you completed it 😀
Click to expand...
Click to collapse
You can actually upload until 2GB as "released":
"Each file included in a release must be under 2 GB. There is no limit on the total size of a release, nor bandwidth usage."

https://docs.github.com/en/github/a...y/releasing-projects-on-github/about-releases
 
E

ElPakoTech

Member
Apr 18, 2020
21
30
murtzsch said:
I've also built it and dirty flashed it, looking at logs (dmesg/logcat) I can see my kernel logs are flooded when the screen is on :
" [3: kworker/u17:2: 5042] [SSP]: MSG From MCU - SSP_batch_full 60 60 0

Any of you ever encountered this issue ?
edit: looks like it's gone with the lineageos-18.1 branch instead of 4.9.118.
still having weird issues, probably related to old vendor files
Click to expand...
Click to collapse
Hi, I having the same messages too. I'm a bit confuse, what do you mean by lineage-18.1 branch / 4.9.118 ? The branch we use is Lineage 18.1, the kernel version is 4.9.118, right ?

The vendor I used is G960FXXU8DTC5 that I flashed to use Official Lineage 17.1 (April 2020).
 
M

murtzsch

Member
May 10, 2014
36
20
ElPakoTech said:
Hi, I having the same messages too. I'm a bit confuse, what do you mean by lineage-18.1 branch / 4.9.118 ? The branch we use is Lineage 18.1, the kernel version is 4.9.118, right ?

The vendor I used is G960FXXU8DTC5 that I flashed to use Official Lineage 17.1 (April 2020).
Click to expand...
Click to collapse

roomservice.xml ( https://github.com/synt4x93/local_manifests/blob/lineage-18.1/roomservice.xml#L3 ) uses revision="4.9.118".
With this branch I was getting constant kernel log flood. (enough to make logd/adb logcat crash).
I replaced 4.9.118 by lineage-18.1 in roomservice, I'm now running 4.9.218.
There're still a lot of repeated kernel logs (errors and warnings).

Iodé says the kernel sources they use is https://github.com/LineageOS/android_kernel_samsung_universal9810 but there's no 18.1 branch, and it looks like the same as https://github.com/synt4x93/android_kernel_samsung_universal9810/ branch lineageos-18.1, the one I'm now using.

For ArrowOS it looks like they're also using the same branch.

In the mean time synt4x93 has recently commited to his GCC branch. (but it's still based on 4.9.118)

I'll post a dump of the repeated kernel logs I'm getting.
 
Last edited:
  • Like
Reactions: dreas74, gnarf49 and ElPakoTech
M

murtzsch

Member
May 10, 2014
36
20
I've been trying 4.9.219 but it did not make any change WRT the recurring "dhd_rpm_state_t" error/warning logs.
I've just upgraded BL & CP to G965FXXUFFUE1, looks like the error/warning logs are gone.
 
K

king1990

Senior Member
Oct 13, 2012
518
878
murtzsch said:
I've also built it and dirty flashed it, looking at logs (dmesg/logcat) I can see my kernel logs are flooded when the screen is on :
" [3: kworker/u17:2: 5042] [SSP]: MSG From MCU - SSP_batch_full 60 60 0

Any of you ever encountered this issue ?
edit: looks like it's gone with the lineageos-18.1 branch instead of 4.9.118.
still having weird issues, probably related to old vendor files
Click to expand...
Click to collapse
Pick this commit to suppress these logs
github.com

drivers: ssp_debug: suppress SSP log spam · ArrowOS-Devices/[email protected]

ssp_debug uses pr_info to constantly print useless information to dmesg. This makes identifying actual issues in dmesg needlessly more difficult. Remove the primary abuser of the ssp_debug to grea...
github.com github.com
 
M

murtzsch

Member
May 10, 2014
36
20
king1990 said:
Pick this commit to suppress these logs
github.com

drivers: ssp_debug: suppress SSP log spam · ArrowOS-Devices/[email protected]

ssp_debug uses pr_info to constantly print useless information to dmesg. This makes identifying actual issues in dmesg needlessly more difficult. Remove the primary abuser of the ssp_debug to grea...
github.com github.com
Click to expand...
Click to collapse
Thanks for the msg, but the kernel I've compiled is already based on this tree, the commit is about removing debug messages.

The info/warn/err messages I was constantly getting are more like these :
Code: 
06-23 20:48:15.922     0     0 W [3:dhd_rpm_state_t: 2833] dhd_runtimepm_state: DHD Idle state!! -  idletime :11, wdtick :100
06-23 20:48:15.922     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_bus_suspend: Entering suspend state
06-23 20:48:15.922     0     0 W [3:dhd_rpm_state_t: 2833] __dhd_txflowcontrol: Netif Queue has already stopped
06-23 20:48:15.922     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_send_mb_data: H2D_MB_DATA: 0x00000001
06-23 20:48:15.925     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_send_mb_data: send H2D_HOST_D3_INFORM to dongle
06-23 20:48:15.937     0     0 W I[4:      swapper/4:    0] D2H_MB_DATA: D3 ACK
06-23 20:48:15.937     0     0 W I[4:      swapper/4:    0] dhd_bus_handle_d3_ack: D3_ACK Recieved
06-23 20:48:15.937     0     0 W I[4:      swapper/4:    0] dhdpci_bus_read_frames: Bus is in power save state (2). Skip processing rest of ring buffers.
06-23 20:48:15.938     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_bus_suspend: Got D3 Ack
06-23 20:48:15.938     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_dump_resource: BAR0(VA): 0x0000000000000000, BAR0(PA): 0x0000000011c00000, SIZE: 32768
06-23 20:48:15.938     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_dump_resource: BAR1(VA): 0x0000000000000000, BAR1(PA): 0x0000000011800000, SIZE: 4194304
06-23 20:48:15.938     0     0 W [3:dhd_rpm_state_t: 2833] dhdpcie_suspend_dev: Enter
06-23 20:48:15.939     0     0 W [3:dhd_rpm_state_t: 2833] BEFORE_EP_SUSPEND: BaseAddress0(0x10)=0x11c00004, BaseAddress1(0x18)=0x11800004 PCIE_CFG_PMCSR(0x4c)=0x4108
06-23 20:48:15.964     0     0 W [3:dhd_rpm_state_t: 2833] AFTER_EP_SUSPEND: BaseAddress0(0x10)=0x11c00004, BaseAddress1(0x18)=0x11800004 PCIE_CFG_PMCSR(0x4c)=0x410b
06-23 20:48:15.965     0     0 I         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_poweroff, start of poweroff, pcie state: 2
06-23 20:48:15.965     0     0 I         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_send_pme_turn_off: link state:d
06-23 20:48:15.965     0     0 E         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: Current LTSSM State is 0xd with retry_cnt =0.
06-23 20:48:15.965     0     0 E         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: ack message is ok
06-23 20:48:15.965     0     0 E         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: received Enter_L23_READY DLLP packet
06-23 20:48:15.965     0     0 I         : [3:dhd_rpm_state_t: 2833] SysMMU alloc num : 1092(Max:1130), lv2_alloc : 52, fault : 0
06-23 20:48:15.965     0     0 I         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_poweroff: Set PERST to LOW, gpio val = 0
06-23 20:48:15.965     0     0 I         : [3:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_poweroff, end of poweroff, pcie state: 0

Code: 
06-23 20:48:18.957     0     0 W [0:dhd_rpm_state_t: 2833] dhdpcie_bus_suspend: Entering resume state
06-23 20:48:18.957     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_poweron, start of poweron, pcie state: 0
06-23 20:48:18.957     0     0 E         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: pcie clk enable, ret value = 0
06-23 20:48:18.957     0     0 I         : [0:dhd_rpm_state_t: 2833] Set TLB MATCH address for TLB1 Pinning : 0x9_7cc00000 ~ 0x9_7ce00000
06-23 20:48:18.957     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_establish_link: Set PERST to HIGH, gpio val = 1
06-23 20:48:18.978     0     0 E         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: phy clk enable, ret value = 0
06-23 20:48:18.978     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: Set I/A for CDR reset.
06-23 20:48:18.978     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: D state: 0, 47b100
06-23 20:48:18.978     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_establish_link: Link up:1dd8411
06-23 20:48:18.979     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: Current Link Speed is GEN1 (MAX GEN2)
06-23 20:48:18.979     0     0 E         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: l1ss enabled(0x0)
06-23 20:48:18.979     0     0 I         : [0:dhd_rpm_state_t: 2833] exynos-pcie 116a0000.pcie0: exynos_pcie_poweron, end of poweron, pcie state: 3
06-23 20:48:18.979     0     0 W [0:dhd_rpm_state_t: 2833] dhdpcie_resume_dev: Enter
06-23 20:48:18.981     0     0 W [0:dhd_rpm_state_t: 2833] AFTER_EP_RESUME: BaseAddress0(0x10)=0x11c00004, BaseAddress1(0x18)=0x11800004 PCIE_CFG_PMCSR(0x4c)=0x4108
06-23 20:48:18.982     0     0 W [0:dhd_rpm_state_t: 2833] dhdpcie_dump_resource: BAR0(VA): 0x0000000000000000, BAR0(PA): 0x0000000011c00000, SIZE: 32768
06-23 20:48:18.982     0     0 W [0:dhd_rpm_state_t: 2833] dhdpcie_dump_resource: BAR1(VA): 0x0000000000000000, BAR1(PA): 0x0000000011800000, SIZE: 4194304
06-23 20:48:18.982     0     0 W [0:dhd_rpm_state_t: 2833] dhd_bus_hostready: Read PCICMD Reg: 0x00100006
06-23 20:48:18.983     0     0 W [0:dhd_rpm_state_t: 2833] dhd_bus_dump_dar_registers: DAR not supported for corerev(23) < 24
06-23 20:48:18.983     0     0 W [0:dhd_rpm_state_t: 2833] dhd_bus_hostready: Ring Hostready:244
06-23 20:48:18.983     0     0 W [0:dhd_rpm_state_t: 2833] __dhd_txflowcontrol: Netif Queue has already started
06-23 20:48:18.983     0     0 W [0:dhd_rpm_state_t: 2833] __dhd_txflowcontrol: Netif Queue has already started
06-23 20:48:18.983     0     0 W [0:dhd_rpm_state_t: 2833] dhd_runtimepm_state: runtime resume ended
 
M

murtzsch

Member
May 10, 2014
36
20
Code: 
star2lte:/ $ getprop |grep G965                                                         
[gsm.version.baseband]: [G965FXXUFFUE1,G965FXXUFFUE1]
[ril.product_code]: [SM-G965FZKDFTM]
[ril.product_code2]: [SM-G965FZKDFTM]
[ril.sw_ver]: [G965FXXUFFUE1]
[ril.sw_ver2]: [G965FXXUFFUE1]
[ro.boot.bootloader]: [G965FXXUFFUE1]
[ro.boot.em.model]: [SM-G965F]
[ro.bootloader]: [G965FXXUFFUE1]
[ro.build.PDA]: [G965FXXUCFTK1]
[ro.build.description]: [star2ltexx-user 10 QP1A.190711.020 G965FXXUCFTK1 release-keys]
[ro.build.fingerprint]: [samsung/star2ltexx/star2lte:10/QP1A.190711.020/G965FXXUCFTK1:user/release-keys]
[ro.odm.build.fingerprint]: [samsung/star2ltexx/star2lte:10/QP1A.190711.020/G965FXXU8DTC5:user/release-keys]
[ro.odm.build.version.incremental]: [G965FXXU8DTC5]
[ro.product.build.fingerprint]: [samsung/star2ltexx/star2lte:10/QP1A.190711.020/G965FXXUCFTK1:user/release-keys]
[ro.product.model]: [SM-G965F]
[ro.product.odm.model]: [SM-G965F]
[ro.product.product.model]: [SM-G965F]
[ro.product.system.model]: [SM-G965F]
[ro.product.system_ext.model]: [SM-G965F]
[ro.product.vendor.model]: [SM-G965F]
[ro.system.build.fingerprint]: [samsung/star2ltexx/star2lte:10/QP1A.190711.020/G965FXXUCFTK1:user/release-keys]
[ro.system_ext.build.fingerprint]: [samsung/star2ltexx/star2lte:10/QP1A.190711.020/G965FXXUCFTK1:user/release-keys]
[ro.vendor.build.fingerprint]: [samsung/star2ltexx/star2lte:10/QP1A.190711.020/G965FXXU8DTC5:user/release-keys]
[ro.vendor.build.version.incremental]: [G965FXXU8DTC5]

CSC+ODM haven't been upgraded.

here are the logs I'm now constantly getting when screen is off/device locked and plugged to computer (charging):
Code: 
06-26 12:33:08.578     0     0 I         : [3:  kworker/u16:1:28090] [FG] 0080h,ff9bh,7f80h,ff01h,1900h,0919h,491eh,5b81h,1c00h,ccd8h,0657h,05ech,0010h,4dc8h,4a1fh,093ch,0c7ah,ffffh,3201h,5f00h,05a3h,0148h,1c4dh,
37a0h,0ce7h,cbe5h,3b0ch,d899h,20d3h,0314h,0460h,092dh,004ah,6200h,2481h,0bcfh,1403h,2305h,1c4dh,7f88h,2656h,cea4h,2039h,0890h,e3e1h,290eh,0400h,0001h,7ebbh,59dfh,1e04h,ffffh,1deah,0c71h,0a52h,05e0h,004ah,1a2dh,a7
e2h,05ech,1680h,1008h,c9d7h,e000h,07fch,abach,1902h,0094h,caf7h,05e2h,639ch,01fah,4a7ah,2241h,0900h,00a6h,2478h,24a0h,a0b7h,0c8ah,0000h,66d8h,0007h,2d94h,7f80h,0005h,0076h,059fh,0000h,006bh,090ch,0050h,0048h,0204
h,0c19h,0000h,0e75h,0000h,0000h,0000h,0000h,0000h,0000h,0000h,0000h,0000h,0000h,0010h,0010h,ffffh,4a15h,092ch,1cd4h,0e00h,e680h,3b0ch,0011h,0000h,f200h,ffffh,4aeeh,000ch,4678h,0000h,4000h,0000h,7d00h,0920h,ffffh,
ffffh,ffffh,ffffh,20aah,0000h,0000h,f9c2h,3fc2h,577eh,01feh,c828h,0043h,2910h,ccf6h,4bceh,                                                                                                                       
06-26 12:33:08.579     0     0 I         : [3:  kworker/u16:1:28090] [FG power] ISYS(47mA),ISYSAVG(49mA),VSYS(4113mV),IIN(469mA),VBYP(4977mV),QH(9376000uah)
06-26 12:33:08.579     0     0 I [3:  kworker/u16:1:28090] max77705_fg_read_vfocv: VFOCV(4003)mV, data(0xc828)                                                      
06-26 12:33:08.580     0     0 D [3:  kworker/u16:1:28090] max77705_fg_read_current: current=521mA                                                                                                               
06-26 12:33:08.580     0     0 D [3:  kworker/u16:1:28090] max77705_fg_read_avg_current: avg_current=474mA                                                                                
06-26 12:33:08.587     0     0 D [3:  kworker/u16:1:28090] max77705_fg_write_temp: temperature to (279, 0x1be6)                                                                                                  
06-26 12:33:08.589     0     0 D [3:  kworker/u16:1:28090] max77705_fg_read_avg_current: avg_current=474mA                                                          
06-26 12:33:08.589     0     0 D [3:  kworker/u16:1:28090] max77705_get_fuelgauge_soc: soc(731)
06-26 12:33:08.589     0     0 I         : [3:  kworker/u16:1:28090] sec_bat_get_property cable type = 4 sleep_mode = 0                         
06-26 12:33:08.590     0     0 I [3:  kworker/u16:1:28090] max77705_fg_get_scaled_capacity: current_standard(1000)                         
06-26 12:33:08.590     0     0 I [3:  kworker/u16:1:28090] max77705_fg_get_scaled_capacity: CABLE TYPE(4) INPUT CURRENT(475) CHARGING MODE(CC Mode)capacity_max (1000) scaled capacity(73.1), raw_soc(73.1)
06-26 12:33:08.590     0     0 D [3:  kworker/u16:1:28090] max77705_fg_get_atomic_capacity: NOW(73), OLD(73)      
06-26 12:33:08.590     0     0 I         : [3:  kworker/u16:1:28090] sec-battery battery: sec_bat_get_battery_info:Vnow(4096mV),Vavg(4077mV),Inow(521mA),Imax(475mA),Ichg(550mA),SOC(73%),Tbat(279),Tusb(276),Tchg(2
90),Twpc(279)                                                                                          
06-26 12:33:08.591     0     0 I         : [3:  kworker/u16:1:28090] sec-battery battery: sec_bat_cisd_check: [CISD] iavg: 474, incur: 475, chgcur: 550,
06-26 12:33:08.591     0     0 I [3:  kworker/u16:1:28090] cc_T: 0, lcd_off_T: 0, passed_T: 1194, full_T: 0, chg_end_T: 0, cisd: 0x0
06-26 12:33:08.591     0     0 D [3:  kworker/u16:1:28090] calc_ttf: cc_time: 6498                                                                                                                               
06-26 12:33:08.591     0     0 D [3:  kworker/u16:1:28090] calc_ttf: cap: 3500, soc:  731, T:   6878, avg:  474, cv soc:  976, i:   70, val: 475
06-26 12:33:08.591     0     0 I         : [3:  kworker/u16:1:28090] sec-battery battery: sec_bat_calc_time_to_full: T:  6938 sec, passed time:  1194, current: 475
06-26 12:33:08.591     0     0 I [3:  kworker/u16:1:28090] max77705_chg_set_wdtmr_kick: WDT Kick
06-26 12:33:08.592     0     0 I [3:  kworker/u16:1:28090] max77705_get_charging_health: reg_data(0x3)
06-26 12:33:08.592     0     0 I [3:  kworker/u16:1:28090] max77705_get_charging_health: details00(0xe0)
06-26 12:33:08.592     0     0 I [3:  kworker/u16:1:28090] max77705_get_vbus_state: VBUS is valid. CHGIN < CHGIN_OVLO
06-26 12:33:08.593     0     0 I [3:  kworker/u16:1:28090] max77705_get_charging_health: vbus_state: 0x3, chg_dtls: 0x1, iin: 469mA, vbyp: 4977mV
06-26 12:33:08.593     0     0 I [3:  kworker/u16:1:28090] max77705_check_cnfg12_reg: valid_data = 0x60, reg_data = 0x60
06-26 12:33:08.593     0     0 I [3:  kworker/u16:1:28090] sec_bat_swelling_check: swelling highblock(410), highrecov(390)
06-26 12:33:08.594     0     0 D [3:  kworker/u16:1:28090] max77705_get_float_voltage: battery cv reg : 0x13, float voltage val : 4350
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_swelling_check: status(1), swell_mode(0:0:0), cv(4350)mV, temp(279)
06-26 12:33:08.594     0     0 I         : [3:  kworker/u16:1:28090] sec-battery battery: sec_bat_fullcharged_check: Charging Mode : Normal
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_set_current_event: current event before(0x0), after(0x0)
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_calculate_safety_time: EXPIRED_TIME(10565968), IP(2375000), CP(2392500), CURR(490), STANDARD(2500)
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_calculate_safety_time: CAL_EXPIRED_TIME(53908000) TIME NOW(48138) TIME PREV(48107)
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_calculate_safety_time: REMAIN_TIME(10559892) CAL_REMAIN_TIME(53877000)
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_check_mix_temp: mix_limit(0), temp(279), chg_temp(290), input_current(475)
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_check_afc_temp: cable_type(4), chg_limit(0) vbus_by_siop(0)
06-26 12:33:08.594     0     0 I [3:  kworker/u16:1:28090] sec_bat_get_charging_current_by_siop: incurr(475), chgcurr(550)
06-26 12:33:08.598     0     0 I [3:  kworker/u16:1:28090] max77705: [0xb1]0x1a, [0xb2]0xdf, [0xb3]0xe0, [0xb4]0x31, [0xb5]0x00, [0xb6]0xff, [0xb7]0x15, [0xb8]0x38, [0xb9]0x4b, [0xba]0x9c, [0xbb]0x13, [0xbc]0x3c,
[0xbd]0x6c, [0xbe]0x34, [0xbf]0x02, [0xc0]0x92, [0xc1]0x10, [0xc2]0x00, [0xc3]0x60,
06-26 12:33:08.599     0     0 I [3:  kworker/u16:1:28090] max77705_chg_monitor_work: [CHG] MODE(0x5), B2SOVRC(0xc), otg_on(0)
06-26 12:33:08.599     0     0 I         : [3:  kworker/u16:1:28090] sec-battery battery: sec_bat_monitor_work: Status(Charging), mode(Normal), Health(Good), Cable(USB, USB, 1, 0), level(100%), slate_mode(0), sto
re_mode(0), HV(NONE, 0), sleep_mode(0), Cycle(-1)
06-26 12:33:08.599     0     0 I         : [3:  kworker/u16:1:28090] sec-battery battery: sec_bat_set_polling: Polling time 10/30 sec.
06-26 12:33:08.599     0     0 I         : [3:    kworker/3:0:25086] sec_bat_get_property cable type = 4 sleep_mode = 0
06-26 12:33:08.602     0     0 I         : [5:[email protected]: 4151] sec_bat_get_property cable type = 4 sleep_mode = 0
06-26 12:33:08.611     0     0 I [2:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_set_state, led_num = 1, brightness = 0
06-26 12:33:08.612     0     0 I [2:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_set_state, led_num = 2, brightness = 0
06-26 12:33:08.614     0     0 I [2:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_set_state, led_num = 3, brightness = 0
06-26 12:33:08.614     0     0 I [0:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_ramp
06-26 12:33:08.614     0     0 I [0:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_blink
06-26 12:33:08.614     0     0 I [0:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_set_state, led_num = 1, brightness = 63
06-26 12:33:08.615     0     0 I [1:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_set_state, led_num = 2, brightness = 5
06-26 12:33:08.616     0     0 I [1:vendor.samsung.: 4169] leds-max77705-rgb: max77705_rgb_blink
06-26 12:33:08.616     0     0 I [1:vendor.samsung.: 4169] leds-max77705-rgb: store_max77705_rgb_blink, delay_on_time: 0, delay_off_time: 0, color: 0xffff00, lowpower: 0
06-26 12:33:09.449  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:09.449  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:09.449  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:10.450  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:10.450  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:10.450  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:11.450  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:11.451  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:11.451  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:12.451  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:12.451  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:12.451  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:13.452  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:13.452  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:13.452  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:13.478     0     0 I [2:  kworker/u16:4:28292] [SSP]: debug_work_func(0) - Sensor state: 0x1fff07f6bf, RC: 0(0, 0, 0), CC: 0, TC: 0 NSC: 0 EC: 0 GPS: false
06-26 12:33:14.122     0     0 I [3:    kworker/3:0:25086] max77705_muic: max77705_muic_print_reg_log USBC1:0x2f, USBC2:0x05, BC:0x81, CC0:0x91, CC1:0x8, PD0:0x19, PD1:0x7 attached_dev:1
06-26 12:33:14.122     0     0 I [3:    kworker/3:0:25086] max77705_muic: max77705_muic_print_reg_log UIC_INT_M:0x4, CC_INT_M:0x20, PD_INT_M:0x0, VDM_INT_M:0xf0, PMIC_MASK:0x2, WDT:0, POR:0
06-26 12:33:14.453  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:14.453  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:14.453  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:15.180     0     0 I         : [3:      watchdogd: 3990] s3c2410-wdt 10050000.watchdog_cl0: Watchdog cluster 0 keepalive!, wtcnt = fff5
06-26 12:33:15.399     0     0 I         : [7:  kworker/u16:4:28292] etspi_work_func_debug ldo: 1, sleep: 1, tz: 1, spi_value: 0x0, type: egis
06-26 12:33:15.453  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:15.454  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:15.454  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:16.454  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:16.454  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:16.454  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:17.455  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:17.455  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:17.455  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982
06-26 12:33:18.456  4309  4783 D bauth_FPBAuthService: pcf : 0x1012, 0 ,1 ,0 ,0 ,0 ,0, 5.0.0.0
06-26 12:33:18.456  4309  4783 D bauth_FPBAuthService: thread id : 1, preenroll_flag : 0, nd cnt : 0, cso : 0, et : 0
06-26 12:33:18.456  4309  4783 D bauth_FPBAuthService: FPBAuthService, 10982

Basically I expect most of these messages to vanish when I stop building as userdebug.

EDIT: logs are indeed quite quiet with user build
I guess I'll try to merge from https://android.googlesource.com/kernel/common/+/refs/heads/android-4.9-q but from I've seen it's not that straightforward.
4.9.219, I merged it from https://github.com/exynos-linux-stable/starlte
 
Last edited:
  • Like
Reactions: gnarf49
G

gnarf49

Member
Jan 21, 2013
48
30
Thanks murtzsch for the hint with user build!

Same here, works fine and excessive logging is gone.

Two more hints:
- User can be dirty-flashed on top of userdebug, no problem, only Magisk root needs to be reinstalled via adb
- To get user build, run "lunch" where the official guide says "breakfast starlte". You'll get a list of available targets, choose user build then continue with mka bacon final step
 
  • Like
Reactions: ElPakoTech
G

Galaxy9plus-support

Member
Mar 19, 2021
21
5
gnarf49 said:
After reading the last few pages I also started my own builds - thanks very much to @Synt4x.93 for the S9 repo and @gusnz for the helpful hints!

In case any of you want to build with signature spoofing for MicroG:
1. Download the patch from the MicroG repo as described here: https://github.com/microg/GmsCore/wiki/Signature-Spoofing
2. Follow the official build guide + roomservice.xml step as per gusnz
3. Apply the MicroG patch before the "breakfast" step in the official build guide
4. git commit -a (otherwise build will fail with repo versioning error)
5. Continue with official guide
Click to expand...
Click to collapse
Throw us a bone champ !!!

can you write the steps to self build a little more "newbie" proof :p
no idea about roomservice or breakfast step , you mean the "building" section of that github address then building tab ?

And that github > lineago with microG refers to LOS 15/16 , huh ?

Thanks :)
 
G

gnarf49

Member
Jan 21, 2013
48
30
No problem :)

Here's my complete build activities A-Z. Please note this is NOT a script, do one by one. Read the official build guide first, it tells what packages to install to be able to build android.
I run this on the latest Ubuntu, things may be different on other Linuxes or even Ubuntu versions.

Have fun!

---------------------------------

# prep folders and copy roomservice.xml + SigSpoof patch
mkdir -p ~/bin
mkdir -p ~/android/lineage

# Get and copy Syntx roomservice.xml and MicroG patches and copy to build directory.

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
source ~/.profile

# gr configure git
git config --global user.email "YourEmailHere"
git config --global user.name "YourGitAccountNameHere"

# enable caching
export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache
ccache -M 50G

cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1


# ---------------- from here for rebuilds ----------------

# ensure roomservice.xml and patches are copied/updated at this point

repo sync

cd ~/android/lineage
source build/envsetup.sh

# signature spoofing patches for MicroG
cd ~/android/lineage/frameworks/base
patch -p1 -i android_frameworks_base-R.patch
git commit -a
cd ~/android/lineage/

# choose build type user
lunch

# instead of brunch which may be too much for 16GB RAM
mka bacon -j 4
 
  • Like
Reactions: Neurotical, Galaxy9plus-support and aureljared
G

Galaxy9plus-support

Member
Mar 19, 2021
21
5
gnarf49 said:
No problem :)

Here's my complete build activities A-Z. Please note this is NOT a script, do one by one. Read the official build guide first, it tells what packages to install to be able to build android.
I run this on the latest Ubuntu, things may be different on other Linuxes or even Ubuntu versions.

Have fun!

---------------------------------

# prep folders and copy roomservice.xml + SigSpoof patch
mkdir -p ~/bin
mkdir -p ~/android/lineage

# Get and copy Syntx roomservice.xml and MicroG patches and copy to build directory.

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
source ~/.profile

# gr configure git
git config --global user.email "YourEmailHere"
git config --global user.name "YourGitAccountNameHere"

# enable caching
export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache
ccache -M 50G

cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1


# ---------------- from here for rebuilds ----------------

# ensure roomservice.xml and patches are copied/updated at this point

repo sync

cd ~/android/lineage
source build/envsetup.sh

# signature spoofing patches for MicroG
cd ~/android/lineage/frameworks/base
patch -p1 -i android_frameworks_base-R.patch
git commit -a
cd ~/android/lineage/

# choose build type user
lunch

# instead of brunch which may be too much for 16GB RAM
mka bacon -j 4
Click to expand...
Click to collapse

Awesome !!

Boosted swap to 10G, so -j 4 threads, with 12GigRam + 10Gig swap, building ....

How serious should I take the warnings? Should it really build perfectly without any warnings?

If it produces a file, I'm going to dirty flash ( no wipe ) straight over the @Synt4x.93 UNOFFICIAL 18.1 .... we'll see tomorrow morning .... building ...

+++ Update +++
built the user version, a few warnings but got the green
#### build completed successfully
installed right over @Synt4x.93's unofficial LOS 18.1 ( no wipe etc ) thru recovery menu

no data lost ( pics/ settings/ files/ apps/ msg/ phone log / contacts etc)

about >> android version >> android security update shows 5-june-21 security update

Will run as daily, but everything looks fine. Settings Icons have changed ( updated??)
YAY !!!

NB googles EXPOSURE APPS - covid19 as per

Use the COVID-19 Exposure Notifications System on your Android phone - Android Help

To help understand whether you've been exposed to someone who reports having COVID-19, you can turn on Exposure Notifications. If you change your mind, you can turn it off. To use the system, you nee
support.google.com

is NOT on the device, MicroG steps Not installed on my user build

Tnx heaps to @Synt4x.93 for the S9 repo and @gusnz + @gnarf49
Gr8 community !!
 
Last edited:
Neurotical

Neurotical

Senior Member
Feb 7, 2011
244
400
FYI:

Was able to successfully compile 18.1 (using roomservice.xml from synt4x) in windows 11 using WSL2 :) Compile and repo sync appear to take less time than in windows 10.
 
  • Like
Reactions: Galaxy9plus-support
G

Galaxy9plus-support

Member
Mar 19, 2021
21
5
Neurotical said:
FYI:

Was able to successfully compile 18.1 (using roomservice.xml from synt4x) in windows 11 using WSL2 :) Compile and repo sync appear to take less time than in windows 10.
Click to expand...
Click to collapse

did you build the
eng
user
userdebug

build? whats the difference? besides reports of a very active logfile on the debug version?
( debug - which is the one @Synt4x.93 was building for this thread )
 
Last edited:
Neurotical

Neurotical

Senior Member
Feb 7, 2011
244
400
Galaxy9plus-support said:
did you build the
eng
user
userdebug

build? whats the difference? besides reports of a very active logfile on the debug version?
( debug - which is the one @Synt4x.93 was building for this thread )
Click to expand...
Click to collapse

Yeah it shows as the userdebug version. The log file was quite active but the ROM performs properly and can be flashed over the existing ROM to keep all information on the phone.


Rebel25 said:
Are there any newer LineageOS 18.1 builds?
Click to expand...
Click to collapse

lineage-18.1-20210704-UNOFFICIAL-starlte:
(June security update)
https://github.com/Geoknyda/OTA/releases/tag/starlte
 
Last edited:
You must log in or register to reply here.

Similar threads

jesec
[ROM][8.1.0][OFFICIAL][WEEKLY] LineageOS 15.1 for S9 and S9+ (Exynos)
Replies
1K
Views
317K
Hicccx
Hicccx
jesec
[RECOVERY][OFFICIAL] TWRP for Galaxy S9 and S9+ (Exynos)
Replies
916
Views
320K
R
rainbowxxl
yash92duster
  • Poll
[S9/S9+][OneUI Pie][JetBlackUI][03-Jan-2020][v25] LightROM
Replies
1K
Views
166K
T
the_ice_master
yash92duster
  • Poll
[S9/S9+][Oreo][01-Jan-2020][v30] LightROM
Replies
1K
Views
189K
J
jehemera
AlexisXDA
[Alexis Rom 3.2_FVB4][11/03/2022][03/2022 Patches][G96xF/FD OneUI3.0 Apps Ported]
Replies
2K
Views
320K
R
ramone01

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 45
    Synt4x.93
    Synt4x.93
    2okPze5.png


    REQUIREMENTS:
    • Stock Samsung Oneui 2 - 2.5 (Android 10) Firmware. (Bootloader + Vendor)

    INSTRUCTIONS:
    • Lineage Recovery or TWRP
    • Format /system + /data + /cache
    • Flash
    • Reboot

    WORKING:
    • Wi-Fi
    • Bluetooth
    • Mobile Network
    • GPS
    • NFC
    • Audio
    • Camera
    • Fingerprint Sensor
    • HDMI
    • Ethernet
    • MTP/ADB
    • Call Recording
    • Encryption
    • SELinux Enforcing
    • Android Auto
    • Glove Mode
    • OTA Updates

    BROKEN:
    • Iris Scanner
    • VoLTE

    DOWNLOADS:

    XDA:DevDB Information
    LineageOS 18.1, ROM for the Samsung Galaxy S9

    Version Information
    Status:     Stable
    ROM OS Version: Android 11
    ROM Kernel: Linux 4.9.118
    ROM Firmware Required: Oneui 2 - 2.5

    Contributors
    synt4x.93

    Source Code: https://github.com/synt4x93/

    Created: 16-12-2020
    Last Updated: 21-03-2021
    View
    6
    E
    ElPakoTech
    OpenMinded said:
    would you mind specifying exactly what you did to build this? I am using the lineage for microg docker based build and it currently succesfully builds 17.1. I would like to build 18.1 with OTA and sign it myself and provide the OTA like you do.
    There are fragments of info across this thread, it would be great if you or anyone else can put them together.
    Thanks!
    Click to expand...
    Click to collapse
    Hi,

    Sure I can share what I did.

    1. Prepare directories and get Lineage sources (https://wiki.lineageos.org/devices/starlte/build)

    # Create directories
    Bash: 
    mkdir -p ~/bin
mkdir -p ~/android/build
mkdir -p ~/android/build/src
mkdir -p ~/android/build/ccache
mkdir -p ~/android/build/keys
mkdir -p ~/android/build/logs
mkdir -p ~/android/build/zips
mkdir -p ~/android/build/manifests

    # Get repo tools
    Bash: 
    curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

    # Create a "~/.profile" file and paste this into:
    Bash: 
    “if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi”

    # Prepare git
    Bash: 
    cd ~/android/build/src
git config --global user.email "[email protected]"
git config --global user.name "Your Name"

    # Init repo
    Bash: 
    source ~/.profile
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1

    # Time to sync (it can take a very long time, so be patient).
    Bash: 
    repo sync

    2. At this point, I forked all Synt4x.93 related repositories on my Github. But, you don’t really need to do that if you just want to build.

    For OTA, the only repo you will need to fork is android_device_samsung_starlte.

    3.     Create an other repository named OTA.

    4. From your forked android_device_samsung_starlte repository, modify the file lineage_starlte.mk

    Change the last line with your GitHub username:
    Code: 
    PRODUCT_PROPERTY_OVERRIDES += \
lineage.updater.uri=https://raw.githubusercontent.com/<Your_username>/OTA/lineage-18.1/starlte.json

    5. Then you need to add the roomservice.xml file to add the device and kernel sources.

    You can use the resources from Synt4x.93, mine or from Neurotical (He’s maintaining a more recent version of the kernel, you should have a look: https://forum.xda-developers.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/ )

    Get one of the manifests:
    -Synt4x.93: https://github.com/synt4x93/local_manifests
    -pakaoraki: https://github.com/pakaoraki/local_manifests
    -Neurotical: https://github.com/Geoknyda/local_manifests

    Then modify the file roomservice.xml: change "project name" with your GitHub username to match your repository:
    Code: 
    ...
<project name="synt4x93/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" revision="lineage-18.1" />
...

    Copy your version of roomservice.xml into ~/android/build/manifests directory.

    # Update source again
    Bash: 
    repo sync

    6. Generate your own keys (https://wiki.lineageos.org/signing_builds.html)

    From the root of your Android tree, run these commands, altering the subject line to reflect your information:
    Bash: 
    subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/[email protected]'

cd ~/android/build/src
for x in releasekey platform shared media networkstack testkey; do \
    ./development/tools/make_key ~/android/build/keys/$x "$subject"; \
done
make a copy of the “keys” directory and keep it safe.

    7. Install docker and get docker-lineage-cicd image:

    You can use lineaos4microg : https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd/Dockerfile
    Bash: 
    docker pull lineageos4microg/docker-lineage-cicd

    Or

    I also re-write my own docker image to add some options. You can try: https://hub.docker.com/r/pakaoraki/docker-lineage-cicd
    Bash: 
    docker pull pakaoraki/docker-lineage-cicd

    8. Then you are ready to build:

    Execute this command (change pakaoraki/docker-lineage-cicd with lineaos4microg/docker-lineage-cicd if needed)

    Bash: 
    docker run \
-e "BRANCH_NAME=lineage-18.1" \
-e "DEVICE_LIST=starlte" \
-e "INCLUDE_PROPRIETARY=false" \
-e "SIGN_BUILDS=true" \
-v "~/android/build/src:/srv/src" \
-v "~/android/build/zips:/srv/zips" \
-v "~/android/build/logs:/srv/logs" \
-v "~/android/build/ccache:/srv/ccache" \
-v "~/android/build/keys:/srv/keys" \
-v "~/android/build/manifests:/srv/local_manifests" \
pakaoraki/docker-lineage-cicd

    9. When build is done, create a new release on your OTA repo: choose a tag and upload recovery.img and zips file.

    you will need to create a starlte.json that match to your build and release information:
    Code: 
    {
   "response": [
      {
         "datetime": 1627204505,
         "filename": "lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
         "id": "39b85208c5c30edfafd983673a703d60",
         "romtype": "UNOFFICIAL",
         "size": 608774193,
         "url": "https://github.com/<username>/OTA/releases/download/<tag>/lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
         "version": "18.1"
      }
   ]
}

    <tag>: the tag you use when creating the release on Github.
    <username>: your username.

    Then, upload starlte.json to your OTA repository.

    It's possible that I forget something but you get the global idea.
    View
    4
    E
    ElPakoTech
    dreas74 said:

    @ElPakoTech​

    Thanks for your work!
    I will test the build and give you feedback.

    Nice , if we have a maintained LOS with current security patches.
    Have you a paypal adress, that i can buy you a beer?

    Regards
    dreas
    Click to expand...
    Click to collapse
    I will do my own build anyway if there is no official support so I'm happy to share it. No need to tips but thanks :)
    View
    4
    Neurotical
    Neurotical
    Galaxy9plus-support said:
    5th July security update ready on this build if you are compiling your own.
    How to check when its available besides going thru the make process and checking
    ~/android/build/core/version_defaults.mk
    once complete for the security update date ?

    Also checking the
    //source.android.com/security/bulletin
    for the monthly date and
    https://lineageos.org/blog/
    changelog
    isnt helpful. How to know what patch is ready to build before I go thru the whole process ???

    Need to keep the device patched to the latest at all times to be able to use as a daily for work :p
    Click to expand...
    Click to collapse
    To check for security update version of Lineage 18.1 before building your own: https://github.com/LineageOS/android_build/blob/lineage-18.1/core/version_defaults.mk#L243

    There is a build with July security update and an upstreamed kernel here: https://forum.xda-developers.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/

    I am upstreaming the kernel daily and building these new builds daily as well.
    View
    4
    Q
    Queeq
    noahthedominator said:
    Don't mean to be a jerk, simply stating my choices. The person who made this unoffical rom has been online several days this past week and has given us zero communication on future updates.

    I'll be heading to arrow os soon.
    Click to expand...
    Click to collapse
    In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.
    View

New posts