yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] zer0_Clover:
go back to marshmellow or buy a new tablet. or just dont install gapps
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] SupaSiblings:
I think there's a small bug, whenever you try to download an APK, the tablet crashes. Not sure why tho
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] drnightshadow:
There is no such bug, its you... you didn't followed the instructions and don't use GAPPS, more troubles.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Djiban:
Dev seems stodpe for almost a year now.

Offline charge issue could be avoid by a proper cable.

But rom is not realy usable as daily.

Am I right ?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Djiban:
Anyone tried this build ?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Eon125:
Wasnt useable for me. Had a lot of lags, freezes and crashes.

I installed a older, more stable version and sold it on eBay for 25€ with accessory and original package.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Goalach:
@Mighty

I tested your ROM. But unfortunately it's not going as well as I thought.

Apps crash or the screen freezes. Sometimes just a restart helps. Very unfortunate.

I'm now back to LOS 14.1.

Basically I'm looking for a really minimalist Android, just the simplest basic settings.

The tablet (P5110) only serves as a display for my home assistant.

Do you have a tip. Or can you make a stable, minimalist LOS (no mail, calendar, camera, contacts, browser and so on). The main problem is the little memory.

Even 14.1 doesn't run very well, even though I've already disabled all unwanted apps.

As I said. It should only work as a display for my home assistant. It's only one App.

Overall, it's nice to see that you're having fun giving life to such an old device.

I think it's too bad to throw it in the trash.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
We're already running Android Go with LOS, plus since it is so old we're bound to run out of memory here or there, you can root and remove the system apps if needed. I cant build since I dont have a build pc anymore (my laptop's fans fried so no building there now)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Pidzi92:
I have a problem. There was no electricity in the apartment and I forgot my tab. It is drained to zero and now it won't charge. Is there a problem with charging while off? And is there any workaround? 7 inch WiFi only model.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Keep it in charge for few hours it should boot
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] kartik_09:
any hopes of getting newer development like LOS 16 or even LOS 17 by any chance if u got it fixed or some other solution, and if u would come back to the building scene or if u would get it fixed or get a newer laptop/pc
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] zer0_Clover:
probably not. we have been waiting for oreo for years. doubt this thing could run pie without making a thermite reaction
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] kartik_09:
Yeah ig
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Pie does run but still bugs need to be ironed out and patches need to be done for such old hardware, havent found the time for that yet
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] baronaccio:
Dear all, thank you for this ROM for the ancient TAB2. I think it's its last breath...then oblivion! :-D

When I start up the table a message appears: "Lack of match with Producer's ROM. Check Procducer's ROM is JDQ39". First start up was OK, at the second this message. I can't go further, the OK key can't be pressed.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] jabuti_sorridente:
I also got the "Lack of match with Producer's ROM. Check Procducer's ROM is JDQ39" error. Is needed first to flash the stock android 4.2.2?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
okay, ill likely share my roomservice.xml as soon as i finish getting everything working.

kinda busy atm with other devices too and my "setup" sure isnt helping (external usb 3.0 hard drive with qemu ubuntu virtual machine, not very fast but has lots of space and quite cheap)

ill update this with my roomservice.xml quite soon

EDIT: made a stupid spelling error in the roomservice.xml, the path is espressowifi, not espresso.

heres the roomservice.xml for anyone interested in building themselves:

<manifest>
<!-- device specfic files -->
<project name="MightyM17/android_device_samsung_espressowifi-1" path="device/samsung/espressowifi" remote="github" revision="lineage-15.1"/>

<project name="MightyM17/android_device_samsung_espresso3g-1" path="device/samsung/espresso3g" remote="github" revision="lineage-15.1"/>

<!-- kernel -->
<project name="MightyM17/android_kernel_ti_omap4" path="kernel/ti/omap4" remote="github" revision="3.4/common"/>

<project name="MightyM17/android_hardware_ti_omap4" path="hardware/ti/omap4" remote="github" revision="stable"/>

<!-- proprietary -->
<project name="MightyM17/proprietary_vendor_samsung" path="vendor/samsung" revision="master" />
<project name="Unlegacy-Android/proprietary_vendor_ti" path="vendor/ti" revision="stable"/>
</manifest>

seems like i get an error about lz4 zram compression, did you ever test zram @Mighty? (aka test the latest changes on your repo)

it doesnt seem to build for me because it cant find lz4.h in kernel/ti/omap4/include/linux (linux/lz4.h: no such file or directory)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Disable it in arch/arm/configs/espresso_defconfig (CONFIG_ZRAM_LZ4 or smth) but zram doesnt seem to work idk why
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
alright, after disabling it the build seems to have completed succesfully.

here's the build, it boots on my espressowifi! (10.1")

seems to take a little more than 6 minutes on first boot tho (like 10-15 minutes) but it does end up working, although pay attention to it while booting, as if it goes to sleep the whole tablet crashes. @Mighty

md5sum: aa94be7e32f40516dd61611aca8aa495

below are also pictures, sorry for the blurry quality, i took these in a rush on my old phone..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
After testing the latest build curtesy of @RDS5 and @Mighty here are some bugs i've experienced on my GTP3113:

The first time boot was in landscape mode (most likely due to it suiting the bigger tablet variant. After first boot, there was a black screen for a good 10 seconds before loading up the set up screen. While on Set Up, rotation was behaving opposite the way the tablet was placed (Landscape would become potrait and vice versa). The next bug was touch not accurate, it was like water was spilled on the screen and touching the 'next' button on set up would offer a feedback from the 'emergency call' button. Again i thought it had something to do with the ROM being based on the bigger tablet variant so i gave it a good 10 minutes to 'sort itself out' and that seems to fix most of the bugs listed above. After the tablet started behaving properly, there were more things i noticed:

1. The sleep bug that requires a force restart is still present. Not even plugging the charger to wake it up would help.

2. The tablet would randomly shut off which complemented Issue #1 regarding not responding to charger. Giving the tablet time to 'sort itself out' would decrease the randomness.

3. When powered on and on the lockscreen, there's only 1-2 seconds to react before the tablet sleeps. This complements Issue #1.

4. There's no charging screen when powered off.

5. Strangely enough at least for me, when in dark mode the tablet is slower than light mode. (there was a AMOLED dark mode, did not test that one)

6. (Minor) Battery percentage would drop by 2, realized that this was specific with all 8.1 roms i've tried.

so far those are the bugs.

One thing note is that during those experiences only the first and only one flash of the ROM was done. ROM was not interrupted or corrupted when downloaded. Will reflash to see if anything will change.

Edit: Issue #4,5,6 was tested before Issue #1,2,3 showed up, listed them in order of priority with #1 being the most urgent.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Seems like an espressowifi.

Thats normal for 7" variants.

@RDS5 did you face it on espressowifi? Works fine for me on 3g.

You've built from sources right? So the touch/size issue should not be an issue imo, maybe you have a different panel? ORR it could be that the tab is lagging on initial boot? :P

Known, dont have time currently as finals are going on. Help would be appreciated.

Never faced it :/ Could you send /proc/last_kmsg the next time it reboots randomly?

Similar issue on Unlegacy Android, i am not sure what changed in Oreo to break this :(

The black dark mode works smooth for me, maybe give it some time? :P

Could you elaborate?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
nope, mine's rotating just fine, however i have the 10" variant, and @Alotheone's espressowifi is 7"

he did say it stopped happening after it "sorted itself out" (i presume after he waited a bit after it booted) so it might've just been the tablet bugging out.

ive never experienced this, even pushing the tablet to its ram "limits" (eg. using the web browser, since zram isnt enabled) wouldnt get it to randomly crash.

that is a part of android, the problem is:

ill look into this, not sure if i have the "expertise" to fix it, but ill try my best to..

cant be that hard since it was working in UA, so its a lineageos specific problem.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
computer broke and resent a message
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
https://review.lineageos.org/c/LineageOS/ For refering commits
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Yeah that happens with me as well, weird
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Alotheone:
@RDS5 Here's some screenshots I did with UA as you requested, hope I captured the critical data because I have no idea:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
could you just send the logcat/paste it in a pastebin?

Also afaik UA has wireless debugging from developer options?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
```

espresso3g:/ # free

total used free shared buffers

Mem: 1027522560 957108224 70414336 0 24498176

-/+ buffers/cache: 932610048 94912512

Swap: 1073737728 0 1073737728

```

zram is on!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] KappaTheCapper:
Nice! You got Android 8.1 working :). Just wondering though did you manage to fix that charging issue when the device is turned off? where it used to constantly try to show the battery charging icon and was looping so it couldn't actually charge?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
it does? i didnt find it..

i looked for wireless debugging in UA and i didnt find anything in developer options

i even tried searching for the setting but found nothing (settings search bar)

from what i see in these screenshots, the omapfb error isnt here.

so yeah, the device's framebuffer driver is crashing in lineageos but not aosp, very peculiar...

it might have to do with android's HWC, maybe lineageos changed something..

how did you get zram working? mine kept throwing errors when trying to compile the kernel because lz4.h didnt exist, and when i added lz4.h it gave me a compilation error (forgot what it was, seemed like a warning being interpreted as an error tho)

i would love to build this rom again with zram enabled, it would help performance a ton.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Enabled it manually with lzo compression instead of lz4

cd /system/vendor/lib/modules
modprobe zram.ko
echo 512M > /sys/block/zram0/disksize //whatever size you like
mkswap /dev/block/zram0
swapon /dev/block/zram0
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
oh, we can just use lzo? i probably shouldve thought of that.

anyways, i think ive narrowed down the locking issue to surfaceflinger sending bogus to omapfb, and in UA there appears to be a patch for this (in frameworks/native).

im going to try to sync with their android_frameworks_native and see if that works, otherwise ill just cherrypick commits that seem like they may work...

GitHub - Unlegacy-Android/android_frameworks_native at aosp-8.1

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

github.com

i have no idea if this will work, but everything points to this being the issue, so im guessing this is what'd fix it.

we can only wait and see tho.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Could you link the commit?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
https://github.com/Unlegacy-Android...mmit/7280ae353a50e36b199fa7bf916f962f19b4b066 sounds possible

https://github.com/Unlegacy-Android...mmit/16392a119661fd1da750d4d4e8e03442578bc543 sounds possible too

none of these describe the exact issue we're having, but they sound very similar.

theres some more but these are the ones i think are the most likely.

im going to try and build lineageos with the entire repo from UA, since thats alot easier than just picking commits..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Both of them are in LineageOS

sf: Initialize DispSync in SurfaceFlinger_hwc1 · LineageOS/android_frameworks_native@e11e1f5

SurfaceFlinger_hwc1 was not initializing DispSync. The hw vsyncs were not getting processed resulting in 1 frame per second. Fixes b/65484547. Test: Boot Hikey/Hikey960. Frame rate should be high...

github.com

surfaceflinger: make vsync injection more robust · LineageOS/android_frameworks_native@16392a1

There are more issues than I expected :) - no lock to synchronize enable/disable and injection - Every time injection is diabled and enabled, a new EventThread is created - mCallback might b...

github.com
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
Hello,

on my Tab 2 WiFi 7" device, with mindthegapps 8.1, it feels like it works faster than your AOSP 8.1 build. If that screen-off problem wouldn't be there, this build now would be really nice. Some apps now do work, which did not in aosp 8.1.

Some things i've tried:

- when screen is off while running, i did try to switch it on blindly, and unlock, then shut it down. It never seems to work

- charging while screen is off: works

- ending standby with loud/silent buttons did not work

One thing does not work properly: contrary to aosp, my streaming apps shows no video. But that's not the biggest problem, the device seems to be too old and slow for that anyway.

And here's my problem again: helping to build a wifi version. Willing yes, but can't. Sorry!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
oh.. i didnt think to check

i guess it likely wont work then

ill still try and see (since UA did work while lineageos doesnt) but i guess it likely wont work.

ill keep looking into it tho
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
the device fails to initialize the entire screen, which seems to include the touch screen?

its a very bizzare and low level error that didnt happen in UA for whatever reason.

im looking into it now but i dont know if i know enough to fix it..

yep, because the tablet still works perfectly fine besides the display. it even plays music while the display is locked, so the tablet doesnt crash or anything..

the problem lies in when it tries to start the display again it throws an error, android doesnt crashe tho.

it used to work with newpipe on UA but newpipe no longer works on lineageos for whatever reason. youtube.com through the browser does tho, so its likely not that severe. (i hope, havent looked into it yet)

the device can still (barely) handle 720p playback tho.

what do you mean by this? you failed to build a wifi version of the rom? what error did you get?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Thanks :D

The offmode charging? I've gotten some leads on the lineage gerrit but since we do not get any logs for that I'll just have to try out multiple builds
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
The issue the display fails to start, something with hwcomposer, havent gotten enough time to investigate properly, thats why just the display doesnt light up, evne running surfaceflinger leads to a fatal crash :/ Something nasty going on.

About the video issue, on UA/AOSP i had put these commits https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/185875/1 and https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/185876/1 which fixed it, but seems like Lineage needs more?

I dont know what changes other devs had done to cm-14.1 since its ages old now, maybe @Android-Andi could remember something? YouTube should work tho, only native player seems broken.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
@Rd5 maybe we should use https://github.com/LineageOS/android_hardware_ti_omap4/tree/cm-14.1 but that'll requirq cherry picking commits for oreo from my repo since it doesnt work out of the box, too bad Unlegacy gerrit is down :/
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] KappaTheCapper:
Perhaps you could ask HTML6405 about the issues your having? Hes been supporting the Galaxy Note 10.1 and still quite active. The tablets appear to be quite similar to the Galaxy Tab 2 10.1, he should have a lot of experience with issues of supporting ancient hardware especially since that note tablet was released only 4 months after the samsung galaxy tab 10.1
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
A test with youtube in browser did not work. While testing around, it tells me something about missing codecs. I'll try something when i get time.

I did not only fail by building a version by myself, but also i do not understand that fully what i am doing. Much howtos are different and obsolete, or differ. My try was to build an updated version for another tablet.

Regards
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
thats strange, it worked fine for me.. (you could see it was working with the screenshots i provided)

what errors did you get?

were you using my roomservice.xml?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
unlegacy-android.org just recently shut down it seems.

hopefully its just temporary..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
A question: what does TWRP with the display? Only rough driver support? In there, display goes on and off like it should.

Can i do something as a user?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
thats strange, it worked fine for me.. (you could see it was working with the screenshots i provided)

No, no, it was years ago with a Lenovo A7600 tablet, not this one here.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Sadly I formatted the wrong SSD 3 or 4 weeks ago... All android stuff was on that one...

I'll see if I find anything when I got more time. My little brother came to the hospital today and is in bad condition... I get more information tomorrow, maybe he wakes up tonight.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
even unlegacy android running android 8 (same version as what we're running here) supports locking and unlocking, so this issue is likely not a very complicated one and has already been solved before in UA.

all we need to do is find what fixed it, or what we did that broke it.

for now we have the logs from both so i dont know of anything..

you could try learning how to build android (follow lineageos's guide for espressowifi but use my roomservice.xml and initialize branch lineage15.1 instead of cm-13.0).

honestly im not an expert (far from it), i just look for whatever seems like it may fix it (not a very effective strategy!) and do that.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
oh my god, thats very sad to hear.

i hope he gets better, thats far more important..
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Catfish78:
No, no, it was years ago with a Lenovo A7600 tablet, not this one here.

I'll try my best, if i get time in near future!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
ohh okay!

alright, looking forward lol
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Protopia:
Hope your brother's health issue is improving. I don't really know you (only knowing of you) by my thoughts are with you nonetheless.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Mighty:
Thats sad to hear! Take care :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Hey!

My brother woke up and I visited him yesterday. He's still in bad conditions and will stay in the hospital for a while. The nurse told other people in that condition never woke up again... Thanks to his neighbor who had a bad feeling (no footsteps from him or his dogs in the Snow) he's alive!

About the android stuff:

I have used the 3.0 kernel and a newer ddk than on the one official lineage builds in the past.

Haven't checked your sources, but you're using the updated ddk stuff?

Needs changes in different places. Not sure if we had kernel changes for that on Gerrit to use on 3.4 kernel.

I'd need to ask our webmaster what was happening to the Gerrit, don't have any information.

Since Android 7 the tab2 had issues depending on the size of the default wallpaper.

Add proper sized Wallpaper for Tablets · Unlegacy-Android/android_frameworks_base@4b358c2

OMAP4 DDK doesn't like textures larger than 2048px; let's resize the new tablet wallpapers so they fit within the limits (size based on previous wallpapers). Change-Id: I33ec4b91a4698b79c8...

github.com

On lineage those have been in vendor/cm or vendor/lineage.

Best regards

Andi
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] MIcHiJK:
I'm glad your brother is doing better.

Im a owner of a Tab 2 10.1 since 2012 and still use it to watch video over newpipe. It was the first device i installed a custom rom back then. I was so happy after i figured it out as a kid. It was a android 5 rom. I always wanted to make my own custom roms but i never got around to it. I became a software developer but in a different field. I check the forums from time to time in case there is something new. I think it's great to still be able to use hardware after such a long time. good to hear from you again and thanks to all the devs still working on this device.

Regards
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] RDS5:
thats great to hear! im glad your brother's doing okay

to build cm14.1? or lineage15.1 with 3.0 kernel?

@Mighty

i tried to add all the stuff from cm 14.1's hwc, but it either gave me compiler errors or compile successfully but fail to boot or would still not unlock.

ill likely return to this eventually but at the moment im busy with some other devices and school, so i likely wont be available for the rest of this week..