yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Shouldn't matter, it's Ubuntu 20.04 in wsl that I use.

Sources are in #1 post

The issue of device not waking up seems to be much deeper, once it's in sleep it doesn't change its state no matter what :(
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] petefoth:
If you or @Mighty can share your manifest, or let me know which branch of @Mighty's repos to use, I can try t make a build of LineageOS for microg
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Semen8991:
Wow! It's amazing! I still use my tablet and I'm glad to see that someone supports it! Looking forward to the Wi-Fi build! Thank you very much!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
here they are without some of @Mighty's new kernel patches

NOZRAM = without zram (should stop crashing)

MOD = zram built as a module (@Mighty's change, not sure if it helps with crashing or not).

MOD md5: 9b9f834d145db568416d1ae8afd752e4

NOZRAM md5: 14335b1c32075784a912a79293066a73

(nozram build hasnt finish building yet)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
Ok, i can sent you the link of that one rom from tab 3, tab 4 get stuck at bootlogo
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] retiredtab:
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon

This makes an engineering build that starts adb logcat immediately. That way, you can see all the messages as soon as the device boots. It helps a lot in troubleshooting stuck at boot animation problems.

The -j2 indicates how many CPU cores I have. If you have more, say 4, then -j4.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
same results as the first two builds in my case, just the Lineage OS Splashscreen for over half hour.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
ive most likely missed something quite severe, but i cant figure out what exactly..

ive uploaded a nozram build now so try that, i doubt it'll work if the first one didnt even get past the splash screen.

i probably forgot some essential file/repo to this but whatever it was i cant seem to figure out, everything seems to be in the same place it was last time

i wish i had documented what i changed a little more..

oh hi retiredtab! thanks for the tip, i completely forgot android's other build types allowed for debugging on boot

ill build a debug build with these parameters "shortly" (excruciatingly slow drive..)

alright, but right now im having issues even getting this one to boot, and i dont have a tablet to test on, so its likely going to take me a while..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
it shouldnt have zram enabled, ill be building only zram-less builds for now until i can get these to boot.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] retiredtab:
For those trying out these untested builds, once @RDS5 makes an engineering build, you can hookup your PC to the tablet and log the messages.

# start logging to screen
adb logcat
# if you see log messages on your screen, then hit Ctrl-C to stop
# seeing messages means the eng build is working wrt to adb logging
# start logging messages to file
adb logcat > boot.txt
# wait 3 minutes, then hit Ctrl-C to stop log
# ZIP the file and upload here. You must zip the file as .txt attachments usually never show up.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
and here is a debug build (nozram if i recall correctly).

md5: b5415d8559bb882b513fa5b1e69ffed1
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Sorry, havent been able to make any builds for the time being, hopefully I'll get time next week to work on it
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
One from thread is broken, https://drive.google.com/file/d/1DDtTVcmeWx31H45NsG0aIcLZx6hGpDZM/view?usp=sharing this one show boot animation
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
aight, ill likely get to working on that when i get these builds working, but where's the source code for it?

ah okay, but have you tested your recent changes? (to kernel and device, the Feb2 changes)

people arent able to boot with them, im not sure if removing them would fix it or not (ive built without the kernel changes but it didnt fix it. not sure about device changes)

if you havent tested these changes ill build a reverted version with zram disabled/as a module.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
ok thanks,you can pressent is as your rom, what is source code?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
wdym

source code is the code used to compile into the finished rom?

i want it so i can transplant whatever changes they've made into normal android and maintain those changes

without source code its very hard to maintain (if not impossible if its compiled into machine code) or even get working properly if its a booting issue

its why maintaining touchwiz rom ports is so difficult, because touchwiz is mostly proprietary so working with it isnt very easy
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
i attach file, i mean present is as you rom, that you mace ity
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
but where did you get this rom from?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
CM,https://xdaforums.com/t/rom-4-4-4-p3110-unofficial-cm-11-0-for-galaxy-tab-2.3737392/

link to cm11 post,doesent actualy know where i find touchwiz, i take if from tab 3 7.0 deodexed stock if i find link i would post

https://www.mediafire.com/download_...wlr5b&qkey=6hvjgucvt7chzow&ip=109.111.249.100 tab 3
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Afaik all of them do work, could you send me the commit ids exactly, last I checked eveything was working as stated in the thread :/
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
device tree

Add Offload HIDL · MightyM17/android_device_samsung_espressowifi-1@99b1421

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

Add GNSS HIDL · MightyM17/android_device_samsung_espressowifi-1@1f6d5e8

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

manifest.xml: binderize audio (IDevicesFactory and IEffectsFactory). · MightyM17/android_device_samsung_espressowifi-1@b24f0c2

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

audio: Android.mk: move audio hal to vendor/lib/hw. · MightyM17/android_device_samsung_espressowifi-1@3421d7f

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

audio: audio_hw.c set application target sdk version to fix audio hal. · MightyM17/android_device_samsung_espressowifi-1@92f0e55

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

Remove build info and fingerprint · MightyM17/android_device_samsung_espressowifi-1@cd1ca0d

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

Remove Launcher3Go · MightyM17/android_device_samsung_espressowifi-1@73db84b

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

kernel

UPSTREAM: capabilities: ambient capabilities · MightyM17/android_kernel_ti_omap4@e764d14

Credit where credit is due: this idea comes from Christoph Lameter with a lot of valuable input from Serge Hallyn. This patch is heavily based on Christoph's patch. ===== The status quo =====...

github.com

BACKPORT: commoncap: don't alloc the credential unless needed in cap_… · MightyM17/android_kernel_ti_omap4@cbd5eea

…task_prctl In function cap_task_prctl(), we would allocate a credential unconditionally and then check if we support the requested function. If not we would release this credential with abort_cre...

github.com

im just wondering if you tested these already or if there's something wrong with my builds..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
I've tested them and they work, i don't have lineage on my laptop now (busy with some other things) but this should work without any issue for sure, also there's loggy so if it doesn't boot just go to recovery and check the /cache folder
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
do you need something else for porting?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
i think i have everything but possibly some touchwiz roms from this device

still dont get why you'd rather use touchwiz mini-apps than freeform (its successor)..

okay, hopefully people testing it do that, im still outta luck with my tablet..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
i cant find any custom rom with mini apps, tw is only one that have it, only Tab2 and Tab3 series i think, ok when you finish sent a link to me to test it on tab2, thanks
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Welp :P
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Wdym by porting? My trees are working for Lineage/UA both
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
bc i like TW, and tab 2 has mini-apps, really cool feature, any cm or other rom doesent have that
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Ah that feature, you man use multiwindow or smth, adding that feature to a rom is quite the task hence not many have it (iirc miui has floating windows)

Or you can find some apps that recreate the mini apps feature

Having it on a rom, that is porting from touchwiz (which is ancient and not even open source) sounds like a nightmare
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
its hard, i only have media and camera died error, i cant find any rom with that function
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
holy crap

what changes did you make! i notice how your mac address seems messed up tho..

is wifi gone?

also those buttons i remember there being a specific patch for so the graphics should be relatively easy to fix

getting android 10 and then 12 are the only major hurdles left before getting this tablet running really modern software.. (10 because of system-as-root and 12 because of BPF, although syncing from lineage-UL should fix the latter)

when will the sources be up? i wanna try and build this and maybe see what i can do..

also, this is based off UA? or lineageos? because it says UA in the build number..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
technically 7+ has freeform windows (this rom is 8), so you should just be able to use the taskbar app and get similar functionality (+ dex-like taskbar for pc-type multitasking)

as @Mighty said, touchwiz isnt very easy to port over and alot of the bug fixing involves just using different binaries and hoping they work..

if it doesnt work, it just doesnt work, thats the problem..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
know that Touchwiz is different for each device and request many litle changes to get to work
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
not just that but its also proprietary so making those changes is difficult
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
heres a build (everything default) to see if stuff's still broken (wiped my previous install by accident, cant test on my own hw tho)

someone please test (zram is set as a module here)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
ah yes wifi is broken, i mismatched some paths for the wifi config files and forgot to binderize it hence it isnt working.

But putting my focus on Pie (coz somehow it builds faster than oreo and still feels smooth without gapps) what would you people want? LineageOS or Unelgacy Android?

Sources arent pushed yet as there arent many changes tbh

This is UA currently, and with my current storage and demands I can only build one rom for espresso3g (unless i get more storage/build server)

Regarding future upgrades, 11 is the max we can go if im not wrong, 12 needs kernel backports which arent available for 3.4

OR we can use the 3.0 kernel to get camera and zram working.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
id be on favor of lineageos since im more familiar with its build system (not that UA's much different but UA is also now legacy..)

not really, the galaxy s5 runs 3.4 and there are android 12/13 roms for it

the problem is 12/13 roms remove many features from android itself since their kernels dont support it (eg. packet filtering and encryption, 13 requires FBE and 12 requires BPF)

even the s2 with its 3.0 kernel got android 13 (still with those things patched out)

yeah but the 3.0 kernel's even older and i doubt we'd have much luck using it with lineage-UL (ultra-legacy, it patches out these functions that dont work with kernels older than 4.4)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
So for the future scope, we'll just do LineageOS 16 with 3.4 kernel now? and do things like patch out unsupported things like S3/S5 are doing? I wanted to fix video but binderzing all things should make it work and thats needed for pie hence the abrupt jump
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] An2rejKK:
What it best android 4.4 rom for tab 2? I would start porting and try again with different base rom, now i will try stock deoodexed tab3 rom
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
yeah that seems like the best option if we want to restart proper support for this tablet (other than switching to a mainline kernel for android but thats not really feasible since it hasnt been done on any devices besides the OP6 and some xiaomis with SD845)

something as close to AOSP as possible since the less stuff there is the easier it is to bring over samsung's proprietary stuff..

maybe something like UA (i doubt they had a 4.4 version tho) or just AOSP, cyanogenmod was quite heavily modded at the time and while it was still closer to AOSP than (as an example) htc sense, its not like it was that close either..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Okay LineagseOS 16 it is then, I'll continue the development there!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
Will the new Android 9/LineageOS16 development be on a new thread?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ginore:
......let's wait and see.....
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Blazekitten:
will there be a wifi variant build? or only 3g, for Lineage 16
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Lineage16 will get a new thread ofc :D

Regarding the builds my laptop can only handle a 3G build (no storage) but espressowifi is from where we derive espresso3g it shouldnt be hard to make espressowifi builds with my sources.

Or it can be ported as well as we've seen before
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
ill make a wifi build
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Will release one till Wednesday if it works out of the box
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
Ok, but when the thread is created, could a link be posted here because xda app and in extent the website is confusing to navigate.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Do you have that patch?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
i might be recalling wrong but ive looked everywhere i could think of and cant find this patch

ive seen that issue on some other tablet but i just dont remember which one (possibly gtelwifiue, maybe even this one) but i cant find anyone reporting the bug nor a patch for it after searching around for like 30 minutes..

im guessing its something related to gpu layers (which seem to be quite broken on pvr) based on this device's hardware and other issues it has??
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
No clues about the broken graphics, it's worse on Lineage, anyways to give some updates

Pie is built and booting but we have more issues in there like no wifi, mtp broken, files doesn't work and so on. Hence no release yet.

I'm thinking to make a thread with the zip and update my sources so hopefully the community can give some help?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
maybe we could look into using a newer driver if there is one?

unfortunate that powervr has a history of being pretty proprietary tho..

wasnt there a fix you had used for wifi in UA? or is the wifi chip itself not detected.. (driver issue)

id be inclined to believe its the latter since your current sources seem to be based on 8.1 device trees..

also, you're using lineageos sources or UA sources currently?

yes!

especially updating the sources so i can also make a build for espressowifi and we can start testing too

also, is last_kmsg working on this version? on 15.1 it doesnt seem to work properly for certain crashes (eg. zram) and it'd never save (there wouldnt be a last_kmsg file)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
We're already using ddk1.14 which is the newest ig (there's 1.17 but noones using it)

Also the graphics issues never occured in Android 7.1 whether it be AOSP or UA, but it occurs in Oreo and above on all ROMs, maybe some overlay missing?

Nah it isnt the wifi chip.

`wpa_supplicant: Could not set interface wlan0 flags (UP): Operation not permitted`

Dunno what permisson its missing :/ even occurs if i do it manually as root.

Will do in a day or two

last_kmsg is kernel specific so if it works on any version it should work on all, anyways for Lineage I've added loggy, so /cache should have logcat and dmesg of previous boot
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
no clue as to what it could be xd

often when in fullscreen on newpipe it'd glitch out like half of the screen, im wondering if i could get a log of that to see what exactly's gone haywire

since SELinux is disabled and you're running as root im guessing "operation not permitted" means its trying to execute something thats marked as noexec or changing something readonly

but these are just guesses, ill have to try for myself once the source is released :P

that'll probably help alot with diagnosing issues like zram crashes
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ManzPk:
I am getting, Wifi download error, on these links, and error 7 on twrp while flashing linage os
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
wifi download error is strange

the error 7 is likely because you are using the wrong version of twrp tho, so use the one from android-andi for espressowifi/espresso3g (the common version, not the specific 7/10" versions)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ManzPk:
hey @RDS5 , i have a samsung nexus which has the ti omap 4460, but there is no android 8 or even 9 rom out there. but the tab 2 has the 4430 which is "worse" then the 4460, is it posible if you can make a android 8 rom or 9 rom for the gnexus (sorry for bad grammer in a hurry)

-thx manz
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Sorry man, unless we have a device on hand its hard to test out the chanegs, if im not wrong you can use the same kernel as we use here and the try and replicate commits that we did to bringup the tab 2 for gnexus, that should make things work (tldr you need to build from source)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Updated sources (zram disabled as well :P)

GitHub - MightyM17/android_device_samsung_espressowifi-1 at lineage-16.0

Contribute to MightyM17/android_device_samsung_espressowifi-1 development by creating an account on GitHub.

github.com

GitHub - MightyM17/android_device_samsung_espresso3g-1 at lineage-16.0

Contribute to MightyM17/android_device_samsung_espresso3g-1 development by creating an account on GitHub.

github.com

GitHub - MightyM17/android_kernel_ti_omap4

Contribute to MightyM17/android_kernel_ti_omap4 development by creating an account on GitHub.

github.com

GitHub - MightyM17/android_hardware_ti_omap4 at lineage-16.0

For Android Oreo and above. Contribute to MightyM17/android_hardware_ti_omap4 development by creating an account on GitHub.

github.com

GitHub - MightyM17/proprietary_vendor_samsung

Contribute to MightyM17/proprietary_vendor_samsung development by creating an account on GitHub.

github.com

GitHub - Unlegacy-Android/proprietary_vendor_ti

Contribute to Unlegacy-Android/proprietary_vendor_ti development by creating an account on GitHub.

github.com
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] LR7875:
I have tested the wifi version of the lineageos oreo rom just now.

The system will freeze up after very light use, possibly due to z-ram issues.

To stop this, I rooted with magisk (rename magisk.apk to magisk.zip literally in order to flash in twrp) and used smartpack kernel manager to disable z-ram altogether, under the virtual memory section in the options -> slide z-ram disksize to 0 -> toggle “apply on boot”.

Now, after 10 minutes of by no means conclusive testing the ui is no longer freezing in use. If any problem still persist the frequency of it happening had been drastically reduced.

SmartPack-Kernel Manager (Android)

A modified version of official Kernel Adiutor

smartpack-kernel-manager.en.uptodown.com
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
yes, unfortunately i couldnt get any logs of the reboot after zram crashing so the only options remaining are pretty much applying commits relating to zram or using a UART cable..

fixing zram would help since this tablet only has 1G of ram (and zram isnt that cpu intensive)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] retiredtab:
I don't know about 15.1, but usually there's crash/log info in

/data/tombstones
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
im pretty sure thats when apps/processes crash but i could be wrong

im specifically looking for kernel crash

ill check it soon

its strange that the tablet doesnt save /proc/last_kmsg
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] retiredtab:
Even with the msm8916 kernel, it's not defined by default. For msm8916, if I need /proc/last_kmsg, I have to add this patch

https://github.com/retiredtab/andro.../lineage-19.1/patches/sec_log_last_kmsg.patch

You might be able to adopt it for your kernel?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Check /cache for logs, I have put loggy in this rom....
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
last_kmsg is common for all kernels, on hard boot (ie pressing power button) ram gets cleared and so last_kmsg is gone, if we can soft reboot to twrp by adb or something it should stay :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Eon125:
Still working?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ETech_101:
Is LineageOS 16.0 Coming?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Pretty busy currently, but I am planning to get back to development in early June
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ETech_101:
Alright!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] bossman88:
how do i know if my bootloader is unlocked? can someone please help me to unlock bootloader? i would like to try this rom out on my tab 2 p5113
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Isnt the bootloader unlocked by default on such older devices?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ETech_101:
It comes pre unlocked in our tabs, as in that era they came unlocked by default.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] BinZaidX:
Hello bro I have Samsung galaxy tab 2

Running Rom RR (6.0)(espresso3g)

I am install lineageos 15.1 with micro gapps when I fully installed I am getting so many problems when I am doing Android setup it stopped after a hard work finally device turned on but it is tooo sloww and so much laggy bugs when I go into setting click developer option setting crashes 😩😔

Please tell me any solution if have