yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Here's all my sources:

GitHub - andi34/android_hardware_ti_omap4

Contribute to andi34/android_hardware_ti_omap4 development by creating an account on GitHub.

github.com

GitHub - andi34/android_device_samsung_espresso3g

Contribute to andi34/android_device_samsung_espresso3g development by creating an account on GitHub.

github.com

GitHub - andi34/android_device_samsung_espressowifi

Contribute to andi34/android_device_samsung_espressowifi development by creating an account on GitHub.

github.com

GitHub - andi34/android_device_samsung_espresso-common

Contribute to andi34/android_device_samsung_espresso-common development by creating an account on GitHub.

github.com

GitHub - andi34/android_kernel_samsung_espresso

Contribute to andi34/android_kernel_samsung_espresso development by creating an account on GitHub.

github.com

GitHub - andi34/proprietary_vendor_ti

Contribute to andi34/proprietary_vendor_ti development by creating an account on GitHub.

github.com

My local manifests I used in all ROMs:

GitHub - andi34/local_manifests

Contribute to andi34/local_manifests development by creating an account on GitHub.

github.com

Rom specific changes have been applied before compiling via patch files (not everything was added to the official sources, especially the ddk related changes)

GitHub - andi34/android_pull

Contribute to andi34/android_pull development by creating an account on GitHub.

github.com
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Thats some great news! Lets hope for the best!

Gerrit has been down since a while now :(

So ideally changing to another wallpaper should fix it? One preferably 1280x800 or 1024x600?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Yeah iirc they had lineage 15 with 3.0 kernel.

ouch that is not great, its just getting harder to pinpoint the issue, I'll recheck dmesg and logcat just in case if I missed something
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
On Omni7 I had to use a prebuild HWC. There must be changes somewhere on my repos, maybe also on one of the official Omni 7 repos (don't remember where exactly)

(CUSTOM) HWC: we're using a prebuilt HWC on ddk 1.14 · andi34/android_hardware_ti_omap4@87d90f7

- fixes HWC issues on Omni7

github.com

About the wallpaper: trying won't hurt
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
Problem: on my wifi tab2 (5110) i press on the power button to dim the display; when I press the power button again to turn on the dsplay remains black: to be able to use the tab I have to hold down the power button for 5 seconds, the tab restarts.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
yes, this is a known issue on both espressowifi and espresso3g

technical-ish details:

its caused by HWC and omapfb (aka the system that draws your waifus onto the screen) seemingly failing to communicate that the cpu needs to start drawing content onto the screen again, and so it doesnt start the display. (cpu doesnt know to initialize it because omapfb never sent a request because hwc sent garbage to omapfb)

so hwc is the culprit, and it does seem to be broken in lineageos.

at least thats what i understand of this issue so far (based on a logcat from UA and lineageos)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
where's the build and source?

im pretty sure the issue is in hwc (based on the errors) but im not sure what the exact issue in hwc is (especially since it was working in aosp-8.1)

this might work, but i havent had time to try anything related to this device this week.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Yup we use prebuilt ones, I used airend's hardware_ti_omap4 as it has all the changes we needed for UA.

TARGET_USES_PREBUILT_HWC flag doesn't exist on lineage xD.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
24/01/2023

Sleep issue fixed.

Tested zram, but it may cause random freezes.

Issue: Offmode charging only shows the backlight without % or battery logo
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
alright, once i get some time to build (likely this afternoon) i will post the builds here.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
I've pushed espresso3g to afh, link is in #1

This should fix sleep and video for espressowifi as well

I think OMAP_ENHANCEMENT flag isnt needed as well but just to be sure :P
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
thats wonderful to hear!

im likely going to push these changes to a github repository once i get the time, since its alot easier just to sync from github..

i also noticed that random crashing issue seems to occur when i have zram enabled, i might look into that, but its not that big of an issue.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Yeah zram is causing random freezes for me as well, could be because of my janky(?) rebase from 3.10, I'll try a 3.15 rebase with zram streams, or I'll have a look here https://github.com/Unlegacy-Android/android_kernel_ti_omap4/commits/3.0/zram

About the changes they are on gerrit of lineage as well just abandoned :P
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
The problem with the display not turning on seems to me to have been fixed with the Jan 25 version but only for tab 3g. Possible to have a version that solves the problem for espressowifi as well?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
Sorry...double post
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
yeah, im going to build a version for the espressowifi with the locking issue fix soon
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
Hello,

as some posts before said, i would be happy to fullfill this hole from time to time, but that work is to far away for me to say "yes, i can do it in a few days, weeks, ... " or so. First i have to take one laptop, and put an older Linux on it. If then someone could help, if it will get stuck in setup for building an actualized build... this would be great. After this, the machine will only been used for this task.

Regards
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
for now ill try to get this building, but my slow hard drive means that syncing and building takes absolute ages (at least the cpu's okay)

id be glad to help with build issues after you've finished your current projects and are in a better position to work on this

remember: its a hobby, theres no pressure or rush for anything, its done in our spare time.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
Well, i think the computer which i thought to use, will be slower than yours. But better get an update than getting no update... yes, it's a hobby, but only demanding without giving was never mine.

My projects we'd pn about, are so many, i think when everything would be finished, it's too late. And btw.: i want to use the Tab 2 for tiny tasks at my electronic hobby (parts data, search the web, etc.), so updated builds would be a goal for me, too. Let's see if i get time the next days to try something.

Regards
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
The thing i feared happened (again), my espressowifi's battery is at absolute 0%. I forgot to remove UA 8.1 and last left it on at 71%. Now i have to hope that with the 11+ hours of charging and unplugging the battery from the motherboard that it can turn on. Fellow Tab 2 owners, NEVER let your tab 2 go 0%.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ze7zez:
It is good to remember not to power off the problematic android, but reboot to TWRP, then reboot again to TWRP and only then in TWRP perform a power off.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
@RDS5

+on property:ro.bootmode=charger
+ start pvrsrvinit

Add this to rootdir/init.espresso.rc and offline charging should be fixed.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
build is booting.

screen on/off is working now thanks to @Mighty's patches

offline charging hasnt been tested yet (will test later)

rule of thumb: still dont discharge your tablet to absolute 0% until this is confirmed to be working 100%
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
Dirty flash above the last build (with installed gapps) freezes shortly after reaching the desktop. Now a fresh deploy is going on, will edit this post later.

Newly flashed without gapps, it did freeze three times while first (setup-) boot. Now again, clean flash with gapps, it freezes just a few seconds in setup.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
i clean flashed and it worked (previous build wasnt working)

mine froze when first booting, but after force restarting it worked and passed setup into the home screen

which model do you have? i have GT-P5113 (10.1" model) and its working fine

which version of twrp did you use to flash it?

are you sure you completely wiped all the partitions (besides recovery and sdcard) before flashing?

mine booted with this exact build using twrp 3.4.0-0 and seems to run perfectly fine without crashes.

could you post last_kmsg from twrp?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Could be that zram is enabled, could you post outputs of free and lsmod from adb shell
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
zram for me is enabled and seems to sometimes cause crashes, but it seems to work when its not using zram

ill make a build with zram disabled in the kernel for the time being
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
After several tests, i reflashed a backup of ua, for checking that nothing is wrong with the tablet. That works.

I have a 5110 / Tab 2 7.0 WiFi.

TWRP is 3.4.0-0, like yours.

And yes, there was wiped everything (after that dirty flash test, which seems to have been fine except the cause of freezing (zram?). I just forgot, that i had downloaded the new build to internal memory, and had to download it again with my pc, to copy it to the tab 2 plugged into my laptop in twrp. So the second try was with another download, a corrupt file could be excluded as cause.

I didn't find or get last_kmsg in twrp (followed two instructions for below and up kernel 3.4).
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
hmm, yours is 7" but that shouldnt change anything..

when mine was first booting (took almost 10 minutes) it froze when i touched the screen/pressed power button/volume button, so make sure you leave the tablet alone. (although i restarted after that and it worked fine)

and if the version of twrp is the same then that narrows it down even more

also, did it crash as soon as it got to the home screen or crash after some usage? (it seems to crash when it tries to page to zram? havent gotten logs to confirm this yet)

nevermind, theres a kernel log at /proc/last_kmsg for me, so you should be able to find one on yours too.

does anyone here have a 10.1" variant of this tablet? has anyone else gotten the newer version of this rom booting besides me?

i will reset my tablet and see if it boots this time or if the first time was just a fluke.

EDIT: it appears to freeze on first boot, then after force restarting it completes booting and appears to run just fine..

it gets frozen at setup screen or on the bootanimation?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
the random reboots issue seems to be caused by zram, so we should disable that for the time being since it seems like the zram driver we're using is broken.

maybe we should look into using a different driver from a different kernel (preferably another 3.0 or 3.4 kernel)

i know that the driver was only officially introduced into linux with version 3.15 but there are some 3.0 kernels that use an older driver (compcache)

@Mighty

EDIT: zram does work with an older staging driver (work = it actually pages to the zram partition before crashing) but it still "randomly" freezes, seemingly also related to zram

i cant seem to reboot into recovery right after the crash most of the time, and when i do last_kmsg isnt there..

can anyone else who experiences the random freezes try to grab last_kmsg from the recovery (/proc/last_kmsg, right after the tablet freezes reboot into recovery)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
Help!

I currently have the AOSP 8.1 rom installed on my P5110 wifi 10.1": in "developer options" I can't find the "advanced reboot" option to reboot into recovery .... I tried many times to hold down the POWER + VOLUME DOWN keys simultaneously ' but the tab always restarts in normal mode....and I can't get into recoveri to install the january 27 rom.....
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
im pretty sure advanced reboot is a cyanogenmod/lineageos feature, not AOSP, so thats why.

dumb answer: are you sure the volume keys work? and if so, are you fully turning off the tablet before pressing them

oh and also, check if you can reboot into download mode, as if you can then your recovery might be corrupted (just flash a new one with odin/heimdall)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
I can't even reboot into download mode, by pressing POWER + VOLUME UP, this prevents me from using Odin....
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
theres a hardware issue then, or your firmware's messed up.

volume buttons work inside android?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
I was able to boot into recovery from AOSP! The correct procedure is:

1. Turn off the tab.

2. With the tab off, first press the VOL - key and then the POWER key

3. Keep both keys pressed: Samsung etc appears...DO NOT release the keys!

4. Wait for the writing to disappear, when the Samsung writing reappears for the second time release both keys at the same time.

Done!!!!!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
So i'm a bit more happy. The same like i found.

Is there a way to change settings in a flashed android without booting it? Some years ago, there were some changed kernels to flash. It could save time not to make a new android build every time.

I've tried to get play store started, for an app to change (especially zram-) settings, but it froze before.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
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)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
I did a clean install on p5110: unfortunately it keeps crashing, only thing I can do is a forced shutdown.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
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.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
you cannot boot into lineageos? or it sometimes freezes in lineageos?

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

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)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
crashes in lineageos...randomly after a few minutes of use
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
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.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] 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.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
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.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
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!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
I didn't see the last_kmsg but i got kmsg.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
XDA behaving weird. I attached the file in the previous post but they're gone. Also the offline cgarging is not present.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
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).
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
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)

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)

the touchscreen acts funky when rotating? mine doesnt, what model do you have? 7" or 10.1"?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
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.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
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..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
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?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] 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.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
aight, well as mighty said i guess we wont fix it (i might keep looking into it tho)

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)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
Found something in an unknown "sp" folder.

Edit: last_kmsg, but attaching a file seens really not to work.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
try sending it with https://send.vis.ee or https://www.pastebin.com