yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] Spooner2914:
can i get the link you have for the previous version. i have the same issue
[Galaxy Tab S2 Android Development] Surfer_II:
@ripee: Could you please add the last 12/29 builds again to Google Drive?
[Galaxy Tab S2 Android Development] Flax_:
Latest dez 29 release had bootloop.

But there was a release from 29 morning, that was working (with some errors but no bootloop).

I will stick to 16.1 from dez 20 untill there is a new working 17.1

P.s. @ all of you - Get safe into newyear :)
[Galaxy Tab S2 Android Development] lpedia:
I spoke too soon about it behaving well ... it turned out to be too unstable for comfort, so I've reverted to 1102 until the new build becomes more stable. ☹ I won't detail all the issues because I wasn't using the latest build.

But @ripee, thank you for your hard work on this ROM! It is much appreciated. 👍

And best wishes for the new year, everyone! Just over an hour left in 2020 here. :)
[Galaxy Tab S2 Android Development] Flax_:
Btw with both new versions ill geht the warning about public key signed build. Didnt have this in previous versions!?
[Galaxy Tab S2 Android Development] ripee:
I reverted the sources to my first commit on Dec 29, which was the last one used to make the first build on that day. Then I added those commits that I know work for sure in other devices. I must've reset then re-picked the wrong commits or forgot about some commits when I was cleaning up the changes I intended to make.

New builds are running now.

Edit: The wifi problems were caused by a conflict between building the regular old wifi service and the new legacy service that Q requires for our old tablets. Both were being built so that made wifi unstable. I figured this out while cleaning up the device-common.mk file.
[Galaxy Tab S2 Android Development] Spooner2914:
ok I'm still new to all of this. where are the new source files located? just on first post on page 1?
[Galaxy Tab S2 Android Development] Spooner2914:
where did you get 16.1 from?

kinda at the point now that ill take anything working just to use the tablet again
[Galaxy Tab S2 Android Development] lpedia:
@Spooner2914 , the links on the first post are to the relevant (ie for that specific device type) folder on ripee's Google Drive. Those folders usually contain just the most recent build of both 16 and 17.1. The Drive icon in his signature goes to the folder containing those folders.
[Galaxy Tab S2 Android Development] Spooner2914:
ahk i thought so.

just still had 1230 version. which currently isn't working for me

and 16.0 1225 with gives me error 7
[Galaxy Tab S2 Android Development] lpedia:
... and it's 16.0, not 16.1. ;) I don't think 16.1 existed ...
[Galaxy Tab S2 Android Development] lpedia:
Error 7 usually means you have the wrong version for your device (or that TWRP thinks it's the wrong version).
[Galaxy Tab S2 Android Development] lpedia:
Also I think I once got that error message, on a different device, because the latest TWRP version didn't like the device.
[Galaxy Tab S2 Android Development] Spooner2914:
ok could you point me in the right direction of where I've gone wrong

TWRP

3.4.0-0

Samsung Tab S2 SM-T815Y

So using version - SM-T815/Y: gts210ltexx lineage-17.1-20201230-UNOFFICIAL-gts210ltexx.zip

EDIT: Same with V16.0
[Galaxy Tab S2 Android Development] Flax_:
I think the new versions are not uploaded yet.

Since google drive lists them as last modified 25.12. And 30.12. But should be at least 31.12. Its new year, so please give ripee some time to celebrate :p
[Galaxy Tab S2 Android Development] lpedia:
Well, that sounds like the right ROM for the device. Have you previously flashed anything on your device with this version of TWRP? If not, make very sure you have the TWRP that matches your device. Also, there's a TWRP 3.5 now, on https://dl.twrp.me/gts210ltexx/ - if you're sure you have the right TWRP 3.4, perhaps you could try 3.5? Team Win advises trying the latest version first, then earlier versions only if the latest doesn't work.

There've been a number of other people with T815 and T815Y in this thread. Perhaps one of them can give advice if the above doesn't help. I only have a T710 and no experience of your model.
[Galaxy Tab S2 Android Development] bbortnick:
Unfortunately the 20201231 build still boot poops in a similar manner to 20201229 on my t710. Back to running 20201227 which runs well except for gps and fingerprints.

Happy new year all🎉
[Galaxy Tab S2 Android Development] lpedia:
Another reason to try TWRP 3.5 is that it properly supports Android 10+. https://www.xda-developers.com/twrp-3-5-0-released-android-10-support/
[Galaxy Tab S2 Android Development] dannychow:
I 've tried to dirtry flash from 1229 (1st one) to 1231 for my T815 device. But it has boot-loop as described below:

When the device first boot up, the touch screen work but it keep displaying "device is starting". After a while it reboot itself. And the touch screen can't be used anymore and the device reboot itself repeatedly.

Now, I roll back to 1229 (1st one) and it work well for my device.
[Galaxy Tab S2 Android Development] Spooner2914:
so this actually did the trick. updated my TWRP and was able to install v16 with no issues

cant wait for v17.1 and android 10 apps

thankyou all
[Galaxy Tab S2 Android Development] Flax_:
OK,

For T810 with new TWRP ( twrp-3.5.0_9-0-gts210wifi ) + Full Wipe + neweset build ( lineage-17.1-20201231-UNOFFICIAL-gts210wifi ) you get to the point where you select you nation / language. Then it asks you to wait a sec and gets stuck there until it self reboots to the same screen (wait a sec).

This happens on the afternoon 29th build, 30th build and now 31th build.

The latest build that was working is the morning 29th build (which i sadly deleted)

so back to lineage-16.0-20201220-UNOFFICIAL-gts210wifi (cause the 25th build gets public key warning and 30th build has the same boot loop as of 17.1.

@ripee If it helps you i can get a log file, but i think you already have them and i dont wanna spam even more.
[Galaxy Tab S2 Android Development] lpedia:
That's exactly what I'm seeing with T710 and 20201231. It's not actually rebooting between "Wait a moment" and showing the LOS animated icon, though - I have 'adb shell' running, and it hasn't dropped out at all while this is going on as it would if the system actually rebooted. Also, 'uptime' shows system has been running much longer than since the last animation came up.

I tried re-flashing but not including gapps, and it's doing much the same thing minus the Google setup wizard: boot animation coming up periodically, finishing animation, blank screen, wait a bit, animation comes up again. Repeat ad infinitum.

logcat shows "7872 7897 W Watchdog: *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on display thread (android.display)" coming up repeatedly about every two minutes.

Sigh. Back to 1102.
[Galaxy Tab S2 Android Development] Surfer_II:
Same here, boot procedure of T810 and also T815 of 12/31 build get´s stuck at 'tablet is starting' screen followed by reboot and black screen.

Have re-installed 12/29 build (2nd version) to get both devices running again.
[Galaxy Tab S2 Android Development] Surfer_II:
New build 17.1-20210101 for T810 - booting problem is solved. Thank´s @ripee
[Galaxy Tab S2 Android Development] MrBlubke:
That'll be @ripee his New Years Gift!!
[Galaxy Tab S2 Android Development] ripee:
Changelog

Build 0101 for all variants

* Fingerprint and formatting the SD card as internal storage should be fixed.

* Bluetooth calling should also work, although I'm not sure how broken it may have been since I don't have a bluetooth headset to test with.

* Livedisplay will probably not work, at least not any better than on Pie, but this seems to be a problem shared with the Exynos Note 4, for which ananjaser has no ideas right now. We did as much as we could for it in Pie.

* Synced with LineageOS sources.

On another matter, I am always open to teaching novice users how to build roms from source. I provide linux scripts on my Github that will automatically set up an Ubuntu build environment for you to build on (Ubuntu because Lineage's instructions are written for it, but you can adapt my scripts for any linux distro and revise the scripts for any rom).

If anyone wants to try another rom on their tablet, while I don't have time to maintain any new threads on XDA at the start of a new year because of real life, I do have time to port roms from our existing Lineage sources, so if anyone wants to build or learn to build from our sources linked in the OP, let me know on XDA or Telegram.
[Galaxy Tab S2 Android Development] Surfer_II:
New build 17.1-20210101 for T815 - booting problem is solved as well and running smoothly. Thank´s @ripee
[Galaxy Tab S2 Android Development] wallace5golf:
It apears to be working well on the T810. Many thanks @ripee
[Galaxy Tab S2 Android Development] LifelessDead:
TWRP'd a T710 last weekend with 3.4.0.0.

Error 7 also pops up when trying to install a ROM immediately after doing a full wipe of system/data/everything.

Doing a quick reboot after the wipe, directly back into TWRP, resolves the error ;)
[Galaxy Tab S2 Android Development] lpedia:
I haven't seen this issue myself with either TWRP 3.4 or 3.5 on my T710 (and it's had a number of clean-flashes recently, all without a reboot between wipe and flash). Updating TWRP to 3.5 seemed to get rid of the error for at least one OP without reboot recovery between wipe and flash. :)
[Galaxy Tab S2 Android Development] bbortnick:
Thanks for the 20200101 build. It Boots up ok on my T710. GPS and fingerprints sort of work now, but the related functions are buggy. My GPS app takes minutes to get a lock, occasionally freezing the tablet while waiting. Fingerprints in Settings can cause the tablet to crash. Otherwise, the build works well, and since I don't much use either of these functions, that's ok.
[Galaxy Tab S2 Android Development] lpedia:
Thank you, @ripee!

Clean-flashed 20210101 + opengapps + Magisk on T710 today, and it's very good so far. Bluetooth working is a big step forward - it's actually useable for the first time in LOS 17.1 on this device.

SeedVault recovery during setup worked (effect seems much like a Google recovery). Entering 12 keys is a bit of a pain, but a lot less hassle than having to set everything up manually.

Like @bbortnick, I still don't have a working fingerprint unlock. Settings > Security > Fingerprint worked just once, allowing me to store a fingerprint. Going back into Fingerprint now hangs the Settings app (doesn't crash the system, though). This is what it was doing in previous versions, too.

I have not seen any issues with Location, but have only tested with static location sensing in Maps and a weather app, not in motion.
[Galaxy Tab S2 Android Development] dannychow:
20210101 build works well in my T815 device so far. I don't use fingerprint, so I didn't try on it.

It again is a very good one as my daily drive! Thanks Ripee~
[Galaxy Tab S2 Android Development] l_ornelas:
Thank you, @ripee!
[Galaxy Tab S2 Android Development] CuckooPenguin:
I dirty flashed the last 17.1 over my previous installation (17.1 ftom 20201120). Everythings to work except Wifi Direct Streaming.

It does not show devices , nor corresponding settings.

Once tested it seems log entries explode with wifi p2p messages and don't stop.

Can someone with t810 and clean install confirm if screen mirroring via stream works ?

Thanks in advance
[Galaxy Tab S2 Android Development] bbortnick:
Unfortunately, I am getting random reboots on the 20210101 build. I will probably go back to 20201227 (all 17.1).

It just crashed and could not get past the lineage boot gif. I have gone back to th 20201227 build which has not crashed on me yet.
[Galaxy Tab S2 Android Development] djcasl:
I stored the rom in a sub folder then I got the error 7, if I install it with the rom on root of the sd it works for me.
[Galaxy Tab S2 Android Development] jfmenard:
Installed jan 1st build, and wow, this tablet (T810) never worked that well.

- Battery drain now gone.

- No more Wifi issues. Scratch that, I still see some wifi disconnections, but seem less often than before.

- Can use SD card to extend storage, change everything! I now have more than 100gb of storage!

- Button LED work

- Performance is really impressive, everything runs butter smooth!

Issues I noticed:

- Some Wifi drop out, much less frequent than before.

- Fingerprint reader doesn't work on lock screen, but works otherwise.

- Cannot install Netflix.

All in all, cancelled my plan to buy a new tablet, this one looks like brand new now!

Thank you so much @ripee for your fantastic work!
[Galaxy Tab S2 Android Development] 2stardiver:
I did first time flashed my smt815 with this rom. Version was 2020-11-02 it worked almost, wifi did disconnect quite often. Today I installed 2021-01-01 version and it oloissa working after couple hours.

Strange thing with twitch app, sound works but video stops after 2 two seconds and continues.

Netflix works, at least version com.netflix.mediaclient_6.26.1_build_15_31696-31696_minAPI21(armeabi-v7a)(nodpi)_apkmirror.com.apk

Big thanks for get this working!!
[Galaxy Tab S2 Android Development] Oeps:
Installed 17.1 20210101 on my T710, clean install. TWRP 3400.

Recognizable experience as others:

After clean install wifi connection seemed to 'stutter'. Could not restore installed apps from google cloud.

Performed Factory reset from twrp, let it rest for some time and restore worked fine (initializing wifi slow?)

Had a spontaneous reboot to twrp twice while the S2 was not in use.

Had a spontaneously reboot of system several times after using fingerprint in app keepass2android.

During normal use wifi stayed off once after switching screen. Wifi off/on fixed it as in previous builds.

I should get used again that the lights of the soft buttons work again, nice!

17.1 seems faster than 16.1, very nice!

Thanks ripee for keeping the S2 kicking and more or less brand new!
[Galaxy Tab S2 Android Development] bbortnick:
I would like to point out the battery stand by time over night is now only a few % down - much better than it used to be with LOS16. If I forget to plug it in, it's still good to go in the morning. Fabulous!
[Galaxy Tab S2 Android Development] wallace5golf:
Instance)ed 17.1 20210101 on t810 and have had multiple spontaneous reboots to the Lineage logo. Three button restart required.
[Galaxy Tab S2 Android Development] ArtoD2:
T715 Same results. Also updated the TWRP to 3.5

Fingerprint works also from lockscreen when charging.

Fantastic work on the builds!
[Galaxy Tab S2 Android Development] dombo1970:
T810, can't boot today, was working without problem yesterday.

Boot animation is very slow, then black screen only. Difficults to enter recovery, just slow and rebooting.

Flashed the new magisk yesterday, maybe causing that problem?

Anyone else having issues like this?

Edit:

Found a (the!) reason: Battery was completely empty (zero %).

Was definetly not empty when I turned it off yesterday, that's why I'm still wondering.
[Galaxy Tab S2 Android Development] lpedia:
One of the problems people (including me) have been having is occasional sudden reboots, or dropping into a boot animation loop and never actually booting. If the latter, you usually need to force shutdown (hold Volume Down and Power until it powers off) so you can reboot properly. Sounds like your device went into that mode overnight and managed to drain the battery.
[Galaxy Tab S2 Android Development] dombo1970:
Fun fact: The night before it was 100% charged, I left it turned on, and next morning it was still on 100%.
[Galaxy Tab S2 Android Development] lpedia:
Yes, this ROM is pretty good that way. Mine stays at whatever % it went to sleep at - when it hasn't got itself into a bootloop overnight ... :)
[Galaxy Tab S2 Android Development] stevios:
I did a clean install yesterday (t810, 17.1-20210101-UNOFFICIAL-gts210wifi) and screen mirroring to my bravia TV works.
[Galaxy Tab S2 Android Development] CuckooPenguin:
Thanks stevios, i cant get it to work.

Do i understant this correctly

https://review.lineageos.org/q/miracast+branch:lineage-17.1

that mircast is not supprted and removed on purpose in 17.1 ?
[Galaxy Tab S2 Android Development] Spooner2914:
so installed latest from for T815y, everything working great

a few issues ive come across

- SD card for extended memory didnt work for me at all. formated the SD card and all. but didnt increase my volume.

- wireless drop outs

- unable to install any APK files, have allowed install apps from unknown sources etc. go to install just promts "unable to open app" or "this xxxx app was not installed"

Due to the fact the only reason i use my tablet is for these few apps that are not part of the app store. ill go back to v16 and google apps 9.
[Galaxy Tab S2 Android Development] phaleg:
Hi, I see you move from stock to custom: would you consider to help me reviewing my sequence please?

Howdy, can I move from stock Nougat using Odin (I don't have OEM unlock switch in dev. option) to load TWRP,

(set no auto reboot on Odin),

flash TWRP twice (from next SD or?),

then format data, wipe 2 caches and system,

then flash Lineage os (10), then Arm gapps, then no DFE, then normal magisk, (all files from external SD)

then first boot and wait.

How does it sound, did I miss anything? (I've a T815, latest Nougat stock). I heard no need to root it first

Thanks 👍
[Galaxy Tab S2 Android Development] lpedia:
Yes, you can go from Nougat using Odin to flash TWRP. Yes, if there is no OEM unlock option, it isn't needed. Yes, the device does not need to be rooted to start with.

Download Lineageos ROM, ARM gapps, Magisk to SD card or USB OTG drive because you might not be able to sideload them with adb (I couldn't get adb talking to TWRP on any of three different Samsung device models).

Download the most recent TWRP for the T815.

Use Odin to flash TWRP, making sure to turn Auto reboot off first.

Reboot to recovery immediately - do not let it boot to system, or it will overwrite TWRP with the stock recovery. You shouldn't need to flash TWRP more than once (unless you let it reboot and overwrite the first time :-)).

Prepare for clean flash - wipe system and caches, format data.

Flash ROM, gapps, and Magisk in that order. Magisk must be flashed last if you're doing it at this stage. It can be done any time later, after first boot and setup.

Reboot system.

The first boot is slower than subsequent ones, but not interminably so.

Hope that helps. :)
[Galaxy Tab S2 Android Development] phaleg:
Man, I'm grateful to you. I'll try this on weekend ^_^

Few details left, between 3 and 4, what is advised option to reboot TWRP?

About magical, should I flash also DUE at some point to avoid encryption?
[Galaxy Tab S2 Android Development] CuckooPenguin:
Is there a replacement telegram group/channel somewhere ?

The old one disappeared.
[Galaxy Tab S2 Android Development] bmwdroid:
Best imo (as "auto reboot" in Odin is turned off) the tab is just waiting for your input still showing "Downloading don't turn off etc."

But when Odin shows "Pass" you can just press pwr until it restarts.

BUT press home+vol-up when it restarts.

Otherwise stock recovery gets revived.

Magisk is imo best flashed after testing if system starts if at all.

On some devices/ROMs it works flashing all in one go others like it only after a first system start.
[Galaxy Tab S2 Android Development] lpedia:
To boot to TWRP for the first time, without accidentally rebooting system:

Plug the device into a charger and turn on the charger.

Turn off the device's power: hold Volume Down+Power until the screen goes blank. The device should turn off and stay off.

Now hold Home+Volume Up+Power for about 7 seconds until the Samsung boot logo comes up.

Release the Power button but keep holding the other two until the word 'Recovery' appears at the top of the screen. TWRP should now come up.

Note: step 1 is important. The only button sequence the device will respond to when it's in download mode is Volume Down+Power. If the device is not connected to a power source, holding these buttons makes it reset: that is, power down briefly and immediately reboot - unless you can very quickly switch to Home+Volume Up+Power the moment the screen blanks. It isn't easy to be quick enough. Rebooting system will replace TWRP with the stock recovery and you have to start again! Having the device on the charger makes it turn off and stay off, instead of just resetting.

I don't know what DUE or DRE are, sorry!
[Galaxy Tab S2 Android Development] lpedia:
On my Samsung devices, holding the Power button

when the device is in Download mode

, as it will be when you've been flashing TWRP with Odin, does not force a power off; it just does nothing. Volume Down+Power if the device isn't connected to power (such as a charger) forces a restart. I could not find any Samsung support information about forcing a complete power off when I was first wrestling with this issue a year or so ago, but I discovered the advice about connecting to power before doing Volume Down+Power in this Android Central forum thread: https://forums.androidcentral.com/a...-galaxy-s6-not-restart-when-screen-black.html. It works.
[Galaxy Tab S2 Android Development] phaleg:
I apologise for the typo, I mean DFE, a small file I use on my Poco F1 after flashing to avoid encryption
[Galaxy Tab S2 Android Development] phaleg:
Ok, I will use that system!

Great that I asked, I thought I could use the same TWRP that I loaded to reboot to recovery in between the following

flash TWRP in Odin

load TWRP (still from Odin, but wasn't sure how)

do the other flashing steps in TWRP
[Galaxy Tab S2 Android Development] 2stardiver:
Sorry about late answer, i flashed like told in up. Except I didnt flah Magisk, i thought must be used when device is rooted. I didnt root at this point, because of netflix and bank apps.

I also flashed modem bin with odin, isnt it needed?

Couple time browsing or watching something my wifi connection disconnects but tin this version it comes back after switching it off and on again (® IT crowd 😁)
[Galaxy Tab S2 Android Development] lpedia:
I would guess you'd need to flash it at the same time as the ROM and gapps - and before Magisk, if you're doing that at the same time.
[Galaxy Tab S2 Android Development] lpedia:
:) It would be nice if that could be done, but unfortunately it can't. Odin doesn't have an option to reboot to recovery.
[Galaxy Tab S2 Android Development] kabelgleichung:
The WiFi issue is really a pain in the ass. Sometimes WiFi is stable for an hour, then it's quite impossible to get it working. Turning it off/on only connects for a few seconds.

I tried playing with the the options in wpa_supplicant.conf,but without success. Any ideas how to debug further?
[Galaxy Tab S2 Android Development] phaleg:
Thanks, I am getting all the files, about Odin I see there are several websites who claims to be official Odin...

Where is it adviced to download the real version?
[Galaxy Tab S2 Android Development] KingN96:
Hi guys,

for who are experiencing random reboot/boot animation loop issue maybe disabling fingerprint sensor (by removing any stored fingerprint) could resolve the problem. I disabled it yesterday and for the moment no sudden reboots in 24h
[Galaxy Tab S2 Android Development] lpedia:
Odin is a Samsung internal tool that they don't officially release to the public - but it has been spread around anyway.

For a reliable source, try https://www.xda-developers.com/update-firmware-any-samsung-phone/.
[Galaxy Tab S2 Android Development] lpedia:
Yes, this does help, but is not a complete cure - I did it a few days ago and have had only one boot-animation loop since. Of course, you MUST NOT try to add a fingerprint again ... :)
[Galaxy Tab S2 Android Development] KingN96:
No new reboot at the moment in 48h with fingerprint disabled, but i've noticed huge battery drain in standby, (battery to 0% with less than 2 hours of display usage) while previously, with the November rom version, i did more than 3 hour and no battery drain in standby.