[ROM][8.1.0] LineageOS 15.1 (Unofficial)

[ginore]

I did a clean install on p5110: unfortunately it keeps crashing, only thing I can do is a forced shutdown.

 

[Catfish78]

yes, you can build flashable kernels where its a zip that just replaces vmlinuz (or whatever its called in android, the linux kernel image basically)

i havent tried aurora store yet but some apps seem to be broken for whatever reason (newpipe, even tho GPU acceleration seems to be working fine)

anyways, try smartpack kernel manager (you can get the apk here), when it freezes just try again and again to get it installed (thats how i got newpipe installed)
if i recall correctly, there were some zram related settings available in there, but that was on a much newer kernel version.

if that doesnt work tho, you can always disable it from adb (swapoff /sys/block/zram0)

The app before, kernel adjutor, i did use some years ago. I found a setting of zram size (and set it to zero). Before, i rooted LineageOS, and tried to use "swapoff /sys/block/zram0" on terminal, which was quitted without error message. I do not know if it changed something in system, but, after this, it was more stable (or was this coincidence?). In named apps, i just wanted to see what changed (and still there were 64m set). It randomly freezes
nevertheless, but more stable.

 

[RDS5]

I did a clean install on p5110: unfortunately it keeps crashing, only thing I can do is a forced shutdown.

you cannot boot into lineageos? or it sometimes freezes in lineageos?

The app before, kernel adjutor, i did use some years ago. I found a setting of zram size (and set it to zero). Before, i rooted LineageOS, and tried to use "swapoff /sys/block/zram0" on terminal, which was quitted without error message.

you ran this on the current build of lineageos? because theoretically that should fix the issue entirely

I do not know if it changed something in system, but, after this, it was more stable (or was this coincidence?). In named apps, i just wanted to see what changed (and still there were 64m set). It randomly freezes nevertheless, but more stable.

it shouldnt have a swap option or say 0mb in the swap option, not 64m..
strange but you might be changing its frequency of swapping, not actually disabling it.. (so it uses it less often and therefore crashes less often, called swappiness im pretty sure)

 

[ginore]

crashes in lineageos...randomly after a few minutes of use

 

[RDS5]

crashes in lineageos...randomly after a few minutes of use

yes thats because of zram
every time you use alot of ram, it begins to compress part of it. that function seems to work.
after that, it tries to unmap it, which crashes
i cant know any of this for sure tho because i cant get a log from my tablet (last_kmsg doesnt appear after crashes) and im not sure if its even possible to get a proper log of this issue without funky business like UART (i dont wanna solder wires to my tablet!!)

so could you try getting a log (just in case its only me)?
after your tablet freezes, reboot directly into recovery, grab the last_kmsg file from /proc/last_kmsg and do not let it boot into lineageos, otherwise the log will be overwritten.
last_kmsg = last kernel message
if you boot back into lineageos, it will create a new kmsg and overwrite the last one, so get it right after the crash.
if the file doesnt exist after the crash occurs, i am clueless as to why. the same happens to my tablet and its incredibly frustrating.

 

[Alotheone]

Finally got the tablet on. Flashed the latest ROM but couldn't pass the welcome screen due to touch not responding. Had to force restart. Auto rotate having problems also.

 

[Catfish78]

yes thats because of zram
every time you use alot of ram, it begins to compress part of it. that function seems to work.
after that, it tries to unmap it, which crashes
i cant know any of this for sure tho because i cant get a log from my tablet (last_kmsg doesnt appear after crashes) and im not sure if its even possible to get a proper log of this issue without funky business like UART (i dont wanna solder wires to my tablet!!)

so could you try getting a log (just in case its only me)?
after your tablet freezes, reboot directly into recovery, grab the last_kmsg file from /proc/last_kmsg and do not let it boot into lineageos, otherwise the log will be overwritten.
last_kmsg = last kernel message
if you boot back into lineageos, it will create a new kmsg and overwrite the last one, so get it right after the crash.
if the file doesnt exist after the crash occurs, i am clueless as to why. the same happens to my tablet and its incredibly frustrating.

Will try Monday to get it frozen again, and check if there's a file.

For testing purpose, maybe a build without zram would be interesting. If i got it removed, it is still not very stable.

 

[RDS5]

Will try Monday to get it frozen again, and check if there's a file.

For testing purpose, maybe a build without zram would be interesting. If i got it removed, it is still not very stable.

im likely going to do that soon until i can work out what's going on with zram at the moment.

Finally got the tablet on. Flashed the latest ROM but couldn't pass the welcome screen due to touch not responding. Had to force restart. Auto rotate having problems also.

i didnt notice anything fishy with autorotate, but i used the tablet mostly in landscape..
sometimes it crashes/freezes, its not the touch, its the entire OS crapping itself.
its related to zram, when it happens, reboot to twrp (dont let the OS boot) and get a log from /proc/last_kmsg!

 

[Alotheone]

im likely going to do that soon until i can work out what's going on with zram at the moment.

i didnt notice anything fishy with autorotate, but i used the tablet mostly in landscape..
sometimes it crashes/freezes, its not the touch, its the entire OS crapping itself.
its related to zram, when it happens, reboot to twrp (dont let the OS boot) and get a log from /proc/last_kmsg!

I didn't see the last_kmsg but i got kmsg.

 

[Alotheone]

XDA behaving weird. I attached the file in the previous post but they're gone. Also the offline cgarging is not present.

 

[Catfish78]

im likely going to do that soon until i can work out what's going on with zram at the moment.

i didnt notice anything fishy with autorotate, but i used the tablet mostly in landscape..
sometimes it crashes/freezes, its not the touch, its the entire OS crapping itself.
its related to zram, when it happens, reboot to twrp (dont let the OS boot) and get a log from /proc/last_kmsg!

Weird... after an freeze, i've tried to copy kmsg to another folder in twrp (internal and sdcard) - both did not work, it shows endless the copy process.

An started LineageOS session freezes while on the desktop wthout using the tablet. If i start kernel adjutor, and let it show only cpu load, it runs without freezing more than four hours now (will now not edit this time anymore).

Can someone check what happens with touch usability, if the tab is switched on in landscape mode? If i start it like that, it's wrong working. Started in portrait mode, it works correctly (in portrait and landscape).

 

[RDS5]

XDA behaving weird. I attached the file in the previous post but they're gone. Also the offline cgarging is not present.

are you sure its not working at all? or it works but doesnt show anything on screen? i didnt test it correctly but ill likely upload new builds with it working as soon as i disable zram while i work out how to get it working correctly. (maybe just take the zram from 3.0 staging? i tried it but the version i used seemed to have extra patches on it. would really like some logs so i can figure out what exactly is crashing!!)
it might not be working tho, i dont recall if i added the offline charging patches correctly or not. best is not to use it until its confirmed working tho.

I didn't see the last_kmsg but i got kmsg.

kmsg might be the kmsg of twrp, last_kmsg was whatever the last kmsg was created by whatever linux kernel was last running (we want the linux kernel from lineageos, at the time it crashed)

Weird... after an freeze, i've tried to copy kmsg to another folder in twrp (internal and sdcard) - both did not work, it shows endless the copy process.

strange, probably because your copying kmsg and not last_kmsg tho (kmsg = the current kernel message = the kernel message coming from twrp = its still being generated as the kernel is still running. last_kmsg = the kernel message from the last running kernel on the tablet = the kernel message hopefully from lineageos when it crashed)

An started LineageOS session freezes while on the desktop wthout using the tablet. If i start kernel adjutor, and let it show only cpu load, it runs without freezing more than four hours now (will now not edit this time anymore).

wait so after running kernel adiutor you were able to disable zram? or just after running it (and not changing anything) it stopped crashing? try running free in adb to see what the output is (specifically of swap/zram)

Can someone check what happens with touch usability, if the tab is switched on in landscape mode? If i start it like that, it's wrong working. Started in portrait mode, it works correctly (in portrait and landscape).

the touchscreen acts funky when rotating? mine doesnt, what model do you have? 7" or 10.1"?

 

[Catfish78]

are you sure its not working at all? or it works but doesnt show anything on screen? i didnt test it correctly but ill likely upload new builds with it working as soon as i disable zram while i work out how to get it working correctly. (maybe just take the zram from 3.0 staging? i tried it but the version i used seemed to have extra patches on it. would really like some logs so i can figure out what exactly is crashing!!)
it might not be working tho, i dont recall if i added the offline charging patches correctly or not. best is not to use it until its confirmed working tho.

kmsg might be the kmsg of twrp, last_kmsg was whatever the last kmsg was created by whatever linux kernel was last running (we want the linux kernel from lineageos, at the time it crashed)

strange, probably because your copying kmsg and not last_kmsg tho (kmsg = the current kernel message = the kernel message coming from twrp = its still being generated as the kernel is still running. last_kmsg = the kernel message from the last running kernel on the tablet = the kernel message hopefully from lineageos when it crashed)

the touchscreen acts funky when rotating? mine doesnt, what model do you have? 7" or 10.1"?

Ok, so it tries to save its own kmsg in twrp, which could not work. The other one i cannot find.

I´ve meant, as long as kernel adjutor was running without using the tablet, it did noch freeze.

If i change zram to 0 in smartpack, it has the next start of the app 64MB again. But for now, i´ve played a bit around with settings there, set "oom kill allocating task" to 1, and "panic on oom" to 1, too. I'm writing with it. Don´t hit me, i am no expert, but try to find out by testing it for myself with setting i mean they can be a thing for the problem. Please, help to understand it if you can .

Until now, after restart and settings in usage, it did not freeze again (also by used web browser, instaling and deinstalling some apps).

I own a 7" wifi model. I mean, if you switch the tablet off, then switch it on in landscape mode, the screen rotation to the touch is not correct.

 

[RDS5]

Ok, so it tries to save its own kmsg in twrp, which could not work. The other one i cannot find.

thats the same issue for me, i dont know why it does this tho

I´ve meant, as long as kernel adjutor was running without using the tablet, it did noch freeze.

thats bizzare.. maybe its just staying in zram so zram doesnt have to unallocate anything

If i change zram to 0 in smartpack, it has the next start of the app 64MB again. But for now, i´ve played a bit around with settings there, set "oom kill allocating task" to 1, and "panic on oom" to 1, too. I'm writing with it. Don´t hit me, i am no expert, but try to find out by testing it for myself with setting i mean they can be a thing for the problem. Please, help to understand it if you can .

oom is not related, it kills processes when android is running out of ram (and panic on oom im presuming crashes the kernel if it runs out of ram)
these are ram related tho, so it makes sense you'd go to them, but these arent related to the issue we're having (i doubt at least, its still a posibility but very unlikely)

also smartpack not changing zram size is bizzare since you can change it in terminal and im presuming it just uses the same terminal command just as a frontend..

Until now, after restart and settings in usage, it did not freeze again (also by used web browser, instaling and deinstalling some apps).

you probably fixed something in smartpack and disabled zram, show me the output of the free command (there should be a section talking about swap/zram if zram's enabled)

I own a 7" wifi model. I mean, if you switch the tablet off, then switch it on in landscape mode, the screen rotation to the touch is not correct.

strange, but i dont have a 7" model to diagnose the issue (and i have no idea where the root of the issue is coming from either)
it sounds like a relatively easy fix tho, but in what exactly im not sure..

 

[Catfish78]

thats the same issue for me, i dont know why it does this tho



thats bizzare.. maybe its just staying in zram so zram doesnt have to unallocate anything

oom is not related, it kills processes when android is running out of ram (and panic on oom im presuming crashes the kernel if it runs out of ram)
these are ram related tho, so it makes sense you'd go to them, but these arent related to the issue we're having (i doubt at least, its still a posibility but very unlikely)

also smartpack not changing zram size is bizzare since you can change it in terminal and im presuming it just uses the same terminal command just as a frontend..

you probably fixed something in smartpack and disabled zram, show me the output of the free command (there should be a section talking about swap/zram if zram's enabled)

strange, but i dont have a 7" model to diagnose the issue (and i have no idea where the root of the issue is coming from either)
it sounds like a relatively easy fix tho, but in what exactly im not sure..

thats the same issue for me, i dont know why it does this tho



thats bizzare.. maybe its just staying in zram so zram doesnt have to unallocate anything

oom is not related, it kills processes when android is running out of ram (and panic on oom im presuming crashes the kernel if it runs out of ram)
these are ram related tho, so it makes sense you'd go to them, but these arent related to the issue we're having (i doubt at least, its still a posibility but very unlikely)

also smartpack not changing zram size is bizzare since you can change it in terminal and im presuming it just uses the same terminal command just as a frontend..

you probably fixed something in smartpack and disabled zram, show me the output of the free command (there should be a section talking about swap/zram if zram's enabled)

strange, but i dont have a 7" model to diagnose the issue (and i have no idea where the root of the issue is coming from either)
it sounds like a relatively easy fix tho, but in what exactly im not sure..

This is what is left with settings reversed, before it started freezing again. Zram, right? So forget the rest.

Would it be possible, that a sensor or its driver crashes, so touch/screen rotation goes the wrong way?

 

[Mighty]

I'll jsut disable zram for the future builds, if the user wants they can enable it!
Digging into its issues doesnt seem worth :/ as we have more pressing issues at hand.

 

[RDS5]

This is what is left with settings reversed, before it started freezing again. Zram, right? So forget the rest.

aight, well as mighty said i guess we wont fix it (i might keep looking into it tho)

Would it be possible, that a sensor or its driver crashes, so touch/screen rotation goes the wrong way?

its likely not any sort of sensor driver crashing because otherwise it wouldnt rotate at all, its probably just mapped wrong (eg. when value = xx then rotate to yy)

 

[Catfish78]

Found something in an unknown "sp" folder.

Edit: last_kmsg, but attaching a file seens really not to work.

 

[RDS5]

Found something in an unknown "sp" folder.

Edit: last_kmsg, but attaching a file seens really not to work.

try sending it with https://send.vis.ee or https://www.pastebin.com

 

[Mighty]

Currently issues we have are
Random freezes (zram)
Vendor mismatch
Landscape touch (?) - If tab boots in landscape touch is unusable (Ideally should not happen as we set the hwrotation)
GPS
RIL
SELinux

First issue fixed by disabling zram in builds, future reference we can use zram from the 3.0 kernel.
Second, by removing the vendor lines in device tree
Third, its hard to reproduce, getting any logs would be useful
GPS needs a few more things to be added to device tree
RIL No idea, there's no 3G SIM for me to test
SELinux - A huge pain, will touch only when everything else works

Anything else/feature requests?