Unofficial LineageOS 20.0 Android 13

Search This thread

retiredtab

Senior Member
Nov 16, 2017
1,498
1,194
Logs in attachments, happened around 14:50.

Looks like surfaceflinger crashed due to null pointer (from your logs). I don't know what would cause this.
Code:
03-11 14:50:54.176   518   663 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x17 in tid 663 (TimerDispatch), pid 518 (surfaceflinger)
03-11 14:50:55.026 25665 25665 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-11 14:50:55.026 25665 25665 F DEBUG   : LineageOS Version: '20.0-20230215-UNOFFICIAL-klte'
03-11 14:50:55.026 25665 25665 F DEBUG   : Build fingerprint: 'samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CSA1:user/release-keys'
03-11 14:50:55.026 25665 25665 F DEBUG   : Revision: '14'
03-11 14:50:55.026 25665 25665 F DEBUG   : ABI: 'arm'
03-11 14:50:55.026 25665 25665 F DEBUG   : Timestamp: 2023-03-11 14:50:54.482702441+0100
03-11 14:50:55.026 25665 25665 F DEBUG   : Process uptime: 143979s
03-11 14:50:55.026 25665 25665 F DEBUG   : Cmdline: /system/bin/surfaceflinger
03-11 14:50:55.026 25665 25665 F DEBUG   : pid: 518, tid: 663, name: TimerDispatch  >>> /system/bin/surfaceflinger <<<
03-11 14:50:55.026 25665 25665 F DEBUG   : uid: 1000
03-11 14:50:55.026 25665 25665 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x00000017
03-11 14:50:55.026 25665 25665 F DEBUG   : Cause: null pointer dereference
03-11 14:50:55.026 25665 25665 F DEBUG   :     r0  a292d110  r1  00000001  r2  00000000  r3  00000000
03-11 14:50:55.026 25665 25665 F DEBUG   :     r4  a292d0f8  r5  a292d110  r6  a6f1fd18  r7  00000003
03-11 14:50:55.026 25665 25665 F DEBUG   :     r8  00000000  r9  00000001  r10 a292d098  r11 a6f1fd00
03-11 14:50:55.027 25665 25665 F DEBUG   :     ip  a523556c  sp  a292d048  lr  a5227b09  pc  a7729b32
03-11 14:50:55.027 25665 25665 F DEBUG   : backtrace:
03-11 14:50:55.027 25665 25665 F DEBUG   :       #00 pc 00429b32  /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, android::scheduler::Timer::Timer()::$_0> >(void*)+434) (BuildId: 2b3b46d628dd456df4afba3c69de492a)
03-11 14:50:55.027 25665 25665 F DEBUG   :       #01 pc 000ac637  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: ce53a0580fb2dd3478c0227726171fb4)
03-11 14:50:55.027 25665 25665 F DEBUG   :       #02 pc 0006255b  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: ce53a0580fb2dd3478c0227726171fb4)
 

RDS5

Senior Member
The difference is not only speed but the flash memory used for internal memory - it is much more durable than sd-cards.

I have never had internal storage of a device fail on me and I used to flash roms on a weekly basis just for fun. Restore backups, all that.

In the same period of time I had 3 unrecoverable RAW sd-cards, 2 with serious slowdowns (good indicator that it will die soon) and iirc 4 that didn't even made a beep when inserted.

Just to show how much difference there is.
while yes, sdcards do have less endurance, they're also alot cheaper and easier to swap out than the BGA soldered on nand on our phones

especially for me who films alot of video on my phone, i need some extra storage and endurance, i dont want my phone of 9 years to fail on me suddenly.

but it depends on how much data you store and how much you've already written to the phones internal storage (this phone's a hand-me-down from my parents and hasnt had a break longer than 5 months at a time, its always been in heavy usage and therefore i presume the nand isnt doing as well as it could be)
 

mostafa3bdou

Member
Jul 8, 2022
22
5
- Hello guys, Just I'd like to share my thoughts with you regarding not releasing of the next official version of this ROM to our device after 18.1 due to the AOSP’s removal of IPTables in favor of eBPF which is much more efficient kernel side implementation as stated before.
- As per my knowledge, the IPTables is a firewall program that is built into the Linux kernel and it is a default module in AOSP.
- So, what if we disabled this default firewall and use a third-party one, can this solve the problem or even part of the problem?
- Generally, we can do that in Linux servers but I am not sure if this is applicable in AOSP or not and what will be the impact.
- I can see many firewall applications (free or paid) that can help for your reference:
- Please correct me if there is something wrong/unclear with my understanding and thanks in advance.
@khalvat
 

RDS5

Senior Member
- Hello guys, Just I'd like to share my thoughts with you regarding not releasing of the next official version of this ROM to our device after 18.1 due to the AOSP’s removal of IPTables in favor of eBPF which is much more efficient kernel side implementation as stated before.
- As per my knowledge, the IPTables is a firewall program that is built into the Linux kernel and it is a default module in AOSP.
correct
- So, what if we disabled this default firewall and use a third-party one, can this solve the problem or even part of the problem?
depends what you mean by "third-party one"
- Generally, we can do that in Linux servers but I am not sure if this is applicable in AOSP or not and what will be the impact.
if im not mistaken we'd have to bring over quite a few modules into the AOSP kernel to make things like ufw work (android uses different network stack than most distros iirc)
- I can see many firewall applications (free or paid) that can help for your reference:
- Please correct me if there is something wrong/unclear with my understanding and thanks in advance.
the problem here is that these are frontends for the underlying firewall of the kernel
iptables was the firewall 'framework' of sorts that apps would need to hook into, or hook into through android's api
same goes for ebpf
but android's frameworks no longer support iptables, so many of these apps likely wont even work on a12+

a viable solution would be to use a newer kernel than this legacy 3.4 garbage that requires so much care and attention to not break down (khavalt's doing god's work maintaining this 2013 kernel with 2023 OS)
klte is blessed to have its device trees and most drivers already in mainline linux and therefore in newer android common kernels!!
klte is able to boot regular linux distros, and booting mainline kernels with android has already been done (here).

if i had a spare klte i would try some of this (by no means am i remotely an expert but i have worked on similar things before), but its currently my daily driver so i cant do dev on it (i dont wanna lose my data)

klte dts in android common kernel
device tree for sdm845 mainline aosp
 
Last edited:

Hasan1122behj

Member
Aug 26, 2021
18
1
hi i install the 2023-02-15 version plus bitgapps 1.8 and magisk and it was very very slow . then after changing some kernel setting and noticing that nothing happend just befor i decide to change the rom and go back to older roms i just then remove the google play store and google play services then things get alot smoother 😃
is there anything wrong that i did ?
is there anyway to have both google and lineage 20?
 

craP_cillA

Senior Member
Jul 10, 2012
739
362
use the stock kernel that comes with the rom, do a clean flash and don't change any kernel settings and you should be fine! :)
 

bersem

Senior Member
Jan 19, 2014
366
164
Anyone has 5ghz wifi issue ? My phone doesn’t see my 5ghz Wi-Fi hotspot.

G900F klte latest bootloader and modem.

Thanks in advance!

Regards !
 

JeyC79

Senior Member
Feb 12, 2014
79
20
Hi!

Thanks a lot for the work for this ROM!

Coming from a 18.1, I wipped the SYSTEM, DALVIK and CACHE partitions. Then I installed the LOS 20 ROM + NikApp.
The system booted well, I found my app and settings. Then I noticed my SIM card was not seen. I powered off the phone, removed/replaced the SIM card, than I power on the phone, and... boot loop on the LineageOS animated logo + reboot of the phone.

So I remove the battery, tried again.

Then, I wipped the SYSTEM, DALVIK, CACHE and DATE partition to reinstall it again.

But now, TWRP 3.7.0_9.0 doesn't work. I see the TWRP logo, and... nothing more.
Sometimes the screen becomes black during less than 1s, then the logo...
It's like that since 30 minutes.

Please, do you have any idea?
 

JeyC79

Senior Member
Feb 12, 2014
79
20
My phone is not working since 2 days.
I don't understand why. Please, do you have an idea? :)
 

JeyC79

Senior Member
Feb 12, 2014
79
20
I flashed TWRP, but the phone is still stuck on the logo of TWRP.

If I boot normally, the phone go itself on the DOWNLOAD MODE.

I just wiped SYSTEM, DATA, CACHE and DALVIK. No error, I'm sure.

So why it's impossible to go in recovery mode ? :(
 
Last edited:
  • Like
Reactions: Hasan1122behj

Top Liked Posts