yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] damir_balto:
[MENTION=1039674]ArtoD2[/MENTION]

yes, I try with 3.4 as well. Same results. Samsung logo appears and that's it.

I tried a clean install and also install over lineage-16.0-20200816-UNOFFICIAL-gts28wifi.zip.
[Galaxy Tab S2 Android Development] dannychow:
17.1 (build 0902) works fine in my T815 (gts210ltexx) device.

I was using twrp 3.3.1 with clean install.

It 's pretty smooth and stable! Thanks for your great work, [MENTION=6005084]ripee[/MENTION]!

The problem I find so far is only the build-in VPN client. It can't connect to the VPN server (both PPTP and LT2P).
[Galaxy Tab S2 Android Development] marhensa:
according to 3-4 previous pages, it seems there's a problem in latest build.

what is the stable recommended build then?

I don't mind using 9 Pie, but if there's 10 it's preferable.

nevermind, I already install LOS 17.1 (Android 10) build 20200902 (mine gts28ltexx), fresh clean install + gapps + magisk, on twrp 3.4

also got stuck black screen after samsung logo.

what I did to overcome this problem:

1. force restart to download mode (press and hold volume down + home + power, until there's blue screen download mode)

2. while on download mode, connect usb to computer with sound

3. press volume down to restart / cancel download mode

4. wait patiently.......... if there's no usb sound on your computer after 1 minutes, unplug usb cable and then repeat step number 1.

5. after there's usb sound on your computer, it's already processing and will boot successfuly.

it works!

now I have Android 10 on 2015 tablet.

thank you @ripee
[Galaxy Tab S2 Android Development] ripee:
17.1 is still experimental, which is why I didn't rename the thread. Use 16.0 for now and don't expect much from 17.1 for now. As always, none of the devs can promise if or when 17.1 will become stable.
[Galaxy Tab S2 Android Development] marhensa:
I see.. That black screen occasionally happened when reboot, but with method I mentioned earlier, that's a simple workaround. I can live with that, it's okay.

Thank you for your amazing work.
[Galaxy Tab S2 Android Development] 1000jaguar:
Hello, can you help me? I stopped installing custom roms a long time ago. But thanks to this great job I did it again with my TAB S2, now I want to update the most recent version of version 16 (0816) my question is if I should only install it from recovery, and I don't need wipis, or put GAPSS again?
[Galaxy Tab S2 Android Development] paul c:
Depends what version you are coming from. If it's close to the 0816, you should be ok. You'll still need to reinstall Gapps though.

If it's a different Android version for example, take a nandroid backup, full wipe and install the new ROM (plus Gapps).

If you haven't already bought it, download Swift Backup, which is a modern functional version of Titanium Backup . Makes restoring so much easier.
[Galaxy Tab S2 Android Development] MrBlubke:
We understand, and appreciate you at least take the effort. we'll just report with each new build, and revert back to los16 after failed attempts... so far I'm reading some are having luck wirh gts210ltexx (t815) and gts28ltexx versions none so far with a t810 (gts210wifi)

Keep up the awesome work! you're giving us something to look forward to where Samsung is letting us down. really appreciated.
[Galaxy Tab S2 Android Development] aboulafia1901:
My experience

Hello ,

Excuse my poor english but it is not my usual language .

After having previously said that I had not encountered too many problems installing lineageos 17.1 on my SM-T815, I realized that I sometimes encountered some bugs such as a black screen on startup or while I am in an application as well as reset for no reason .

Also, I wanted to install a new kernel in order to see if it didn't improve the rom a little bit . I use for that the kernel explained here : https://xdaforums.com/tab-s2/development/kernel-9-11-18-rg2-rh1-710-810-715-815-t3841316

For this, I have:

- made a backup of the installed lineageos 17 via twrp

- as explained in the thread, installed via Odin, a Rom stock

- I let the tablet restart and finish the installation of the rom stock .

- Turn off the tablet .

- Still via Odin, installed again TWRP .

- performed via twrp a nandroid backup ("System", "Cache", "Data", "EFS" and "Boot" ) .(to reinstall eventually the kernel stock)

- Finally installed the kernel as explained .

The installation went well.

On my SM-T815, the startup is faster and in use the tablet seems more fluid. I have so far no more black screen, nor other bugs.

On the other hand, I did not manage to use synapse: I still have the mention "No UCI support detected" in spite of the solutions explained in the link quoted above.

Finally, I removed synapse and Magisk, not having the use of them at this moment.

This is my solution which suits me, I can't say for other models, this kernel is made for the models 710-810-715-815.

I am not a developer, I just wanted to share my experience.

I knowed ,there were risks

. If you have any questions about the installation of the kernel, it is better to ask them in the link above. Before I start, I read the whole thread .:)
[Galaxy Tab S2 Android Development] np.trivial:
having trouble flashing

I cannot get a flash of 16.0 to work on my T710. I am using TWRP 3.4, but I did accidentally try a clean install of 17.1 first. (Coming from stock ROM.) Whenever I try to do a clean flash of 16.0, I'm still getting ERROR 7. Any advice? (I've tried all three currently posted versions of 16.0.)
[Galaxy Tab S2 Android Development] aboulafia1901:
What is the message with error 7 ?
[Galaxy Tab S2 Android Development] metterschling:
Please search this thread for "error 7". A work-around that helped at least one user has recently been provided.
[Galaxy Tab S2 Android Development] np.trivial:
mkdir "/cache/recovery/c5e35...f18/" failed: No such file or directory
E1001: Failed to update system image
Updated process ended with ERROR: 7
Error installing zip file '/external_sd/lineage-16.0-20200816-UNOFFICIAL-gts28wifi.zip'
[Galaxy Tab S2 Android Development] aboulafia1901:
After error 7 ,in twrp go to the terminal (advanced) ans tape mkdir /cache/recovery and reinstall.

Normally it resolves the problem . 🙂
[Galaxy Tab S2 Android Development] MrBlubke:
I used to have this as well, and it went away after reinstalling TWRP 3.4 again. not really sure what fixed it... going back to older TWRP should work too
[Galaxy Tab S2 Android Development] dannychow:
After the usage of around 1 week, I find that the off-screen battery life of this 17.1 is not good as 16.0. After fully charge and put over-night for ~8 hours, the battery dropped over 10%.

One observation is that, during off-screen, when I touch the back or menu key, the device still has the key vibrate. It seems that the device doesn't sleep completely.

Anyway, it still run good and can act as my daily drive.
[Galaxy Tab S2 Android Development] ali_techno:
hi

anyone does have os 17.1 (build 0902) download link for T815 ?
[Galaxy Tab S2 Android Development] bmwdroid:
What's wrong for you with the link provided in #1?

Didn't try to download it (mine is T810) but at least it's shown.
[Galaxy Tab S2 Android Development] AkiroX:
I'm on 16.0. Was working fine until I rooted it with magisk. Now my keys don't light up. What do? owo
[Galaxy Tab S2 Android Development] benwatkins:
My device is a gts28ltexx (t715). This is the first time I've installed a custom ROM. Thought I'd give 17.1 a try knowing it is still experimental for this device. The install went fine and having tested it this evening the only issue seems to be GPS which is not working at all. Interestingly, according to location settings my 'GPS Test' app has not tried to access location services. Looking at previous builds I can see it's quite common for GPS to not work in early builds. I just wondered if there is a common fix? Or if anyone managed to get it working? It would be a shame to go down to 16 just for GPS.
[Galaxy Tab S2 Android Development] w1dowman:
I'm keen to try and get this os to work, but twice I've tried and get boot loop.. clean install, following the guide same every time. It hangs at the boot os logo for a few mins then just reboots and into recovery again?

I've got this working on my Sony tablet z with no issues. Trying to sort my wife's tab2 with it on. Currently running the havoc ROM but with Google account issues so want to try and get this to run.
[Galaxy Tab S2 Android Development] ali_techno:
+1
[Galaxy Tab S2 Android Development] JoshReuben:
For me that one's a feature not a bug ?
[Galaxy Tab S2 Android Development] Alsnchd:
For me encrypting my tablet solved this problem.
[Galaxy Tab S2 Android Development] ripee:
Changelog

Build 1001 for all variants

* Switched TARGET_SLSI_VARIANT from the old cm to the new open source bsp, among other changes, courtesy of Stricted.

* Synced with LineageOS sources.

Edit: New Q builds are coming tomorrow, will post a new changelog in around 9 hours.
[Galaxy Tab S2 Android Development] mbducati:
can't install

I have version SM-T810 and had a very old TWRP. I flashed the new version 3.4.0-0 and went back into recovery. I wiped everything per instructions and attemted to install 16.0. I received ERROR 7, what should I try to do?

---------- Post added at 08:45 PM ---------- Previous post was at 08:19 PM ----------

I went back to version 3.3.1.-0 and 16.0 now installed properly... donno!
[Galaxy Tab S2 Android Development] dannychow:
After I dirty flash from 0902 (17.1) build to this 1001 build, my T815 device stuck at the "Samsung Galaxy Tab S2" logo. But I guess it is not simply hang because after a while, the logo goes a bit darker and when I press the BACK or MENU key, it has vibration. But the display still stuck at that logo.

Rolled back to 0902 now.
[Galaxy Tab S2 Android Development] aboulafia1901:
It's the same with my sm-t815 . rolled back also to 0902 .Thanks for the work Ripee .
[Galaxy Tab S2 Android Development] dombo1970:
No 16.0-update for T810 anymore?

My latest experience with 17.x ended in boot loop.
[Galaxy Tab S2 Android Development] srvoleti:
It's also the same with my SM-T815. Flashed back 0902 .

Thanks to @ripee for giving us the newer builds!
[Galaxy Tab S2 Android Development] ArtoD2:
Same results with 715
[Galaxy Tab S2 Android Development] ripee:
Changelog

Build 1003 for all variants

* Another attempt at the new bsp sources.

* Synced with LineageOS sources.
[Galaxy Tab S2 Android Development] dombo1970:
Hanging during Samsung boot logo.
[Galaxy Tab S2 Android Development] srvoleti:
Just like previous build, my T815 device is again stuck at the "Samsung Galaxy Tab S2" logo.
[Galaxy Tab S2 Android Development] CuckooPenguin:
Still on 16 as daily driver i dirty flashed 09 over 08 version. Since then random wlan disconnect (mostly not self-recovering) happen more often.

.. just reporting.

[MENTION=6005084]ripee[/MENTION] thanks for keeping our tabs kicking

Tried 17 - last version - stuck on Samsung Logo.
[Galaxy Tab S2 Android Development] ripee:
Try 17 again with the 1003 builds that are up now.
[Galaxy Tab S2 Android Development] dobber81:
T710 Full wipe 1003 build, twrp 3.3.1.0 works. Stuck on Boot screen for about 2-3 minutes and then booted.

However the capacitive buttons do not work.
[Galaxy Tab S2 Android Development] srvoleti:
T815 1003 build, Stuck on Boot screen for about 4 minutes and then booted. However the capacitive buttons do not work and no backlights also.
[Galaxy Tab S2 Android Development] frankieboy1233:
T810 1003 build : slowly but it boots, it waits 10-15 seconds at Samsung logo, then 5 sec till lineage logo appears. Only bug I have found is hardware keys (back and windows) are not working. Thank you ripee, good job.
[Galaxy Tab S2 Android Development] CuckooPenguin:
No luck, tried it again , always full wipe, using latest twrp 3-4 (not installing twrp app btw). Will give it another try later.

If anyone has an idea what i miss or if there is a log file i can pull before restoring my 16 again, let me know.

Thanks
[Galaxy Tab S2 Android Development] syd-3:
I try on sm-T810 1001, and 1003 roms: dirty flash on 16 and clean with all wipes (except SD) with twrp 3.4 --> no boot, stay on samsung logo all times...

wait for new ROM(s)...

thanks to ripee for the time to developing some roms.
[Galaxy Tab S2 Android Development] MrBlubke:
Same experience here, both hard/software buttons not working yet, but apart from that decent experience.

Awesome work!

I suggest you try again t810 here too, and working apart from the buttons next to the home button
[Galaxy Tab S2 Android Development] crcowan:
T710 Similar experience

Installed latest 17.1 yesterday on my T710. My experience is similar to others. A few observations:

1) The capacitive buttons do not work and do not light

2) Slow to boot, but once up and running the performance seems better than on 16

3) Restored my apps using Titanium Backup. Almost all restored fine, but some have problems that can be fixed by re-installing them

Ripee: Thank you for your hard work and I look forward to the next update
[Galaxy Tab S2 Android Development] make_tinker_jr:
I've successfully installed Lineage 16.0 in my S2 SM-T710! Thank you so much for the great work creating and maintaining the project. I didn't want to risk installing LOS 17.x since the first post said it was still experimental, but I was wondering if I'll be able to update in time once it becomes more stable and what steps should I follow?

Also, a big thank you to [MENTION=11003697]aboulafia1901[/MENTION] for recommending a workaround to the dreadful "Updated process ended with ERROR: 7" which was to manually create the missing directory (see post #1263). To be honest this thread has been immensely helpull so thank you all for sharing experiences and fixes.

I just to share my experience in case someone knows what went wrong, when I was already inside Recovery I was planning to sideload the image I had in my PC but adb wouldn't recognize it i.e., adb devices did not recognized any devices connected, and adb sideload <path/to/image> failed due to the same error.

Even trying replacing the cable and usb port it still wouldn't work, and I had to copy the image into an SD card and insert that into the tablet, from where I was finally able to install LOS. Any ideas as to what caused that? Hopefully this can help someone else.

Anyway, thanks again for the great work :D
[Galaxy Tab S2 Android Development] aboulafia1901:
glad my solution could help you [MENTION=11162571]make_tinker_jr[/MENTION] . It was the goal .:)
[Galaxy Tab S2 Android Development] CuckooPenguin:
Well - i think i tried everything - TWRP 3.4 , 3.3.1 , 3.2 .. dirty flashes, clean flashes even with full data formated .. but always the same result on my 810 - stuck at Samsung Logo .. and left it running for 30 minutes to be certain, even couple of restarts.

Any Idea what i might miss - silly question - used latest pico open gaps version ... ok actually tried to reboot even without them as well - no luck.

Fingers crossed for the next version

if i can help to pull any logs etc let me know.

Cheers
[Galaxy Tab S2 Android Development] frankieboy1233:
Have you wiped your system partition before flashing? It's not part of the full wipe, also use TWRP 3.4 only.
[Galaxy Tab S2 Android Development] CuckooPenguin:
Well i do "advanced" and choose all partitions all the time (except micro and usb)

Hm but you say you used 3.4 ok - then i will upgrade it again - and give it another try - which opengaps version did you use ?
[Galaxy Tab S2 Android Development] frankieboy1233:
Nano.
[Galaxy Tab S2 Android Development] dannychow:
Same here on my T815 device after flashing 1003 build. MENU and BACK key doesn't work.

Thanks ripee for your work!
[Galaxy Tab S2 Android Development] jpq:
Hi

Installed 10 03 17.1 on m'y T 710

ATM perfect ?
[Galaxy Tab S2 Android Development] sal82:
I'm on 10. Clean installed with nano gapps. The OS seems smooth. The touch buttons don't work like many have said.

T810 here. Thanks, ripee. :good:

---------- Post added at 07:03 PM ---------- Previous post was at 06:49 PM ----------

Use nano gapps and turn on the tablet. You're going to see it get stuck at the Samsung logo and eventually turn off. After it turns off, wait about 10 seconds and you're gonna see the lineage os logo appear. I tested this method 3 times. You have to do this every time you turn off the tablet until it's fixed. Good luck.
[Galaxy Tab S2 Android Development] luisalberto.rouco:
Hi

Installed 17.1 1003 on m'y T 710 PHE With gapps pico and work perfect.

Only thats physical buttons don't work.

Good Jobs ripee.

Enviado desde mi SM-G986B mediante Tapatalk
[Galaxy Tab S2 Android Development] jpq:
After one d'Ay on 17.1 with T710

- touche buttons dont work

- vidéo error on some applications code 4500

- Netflix not supported
[Galaxy Tab S2 Android Development] luisalberto.rouco:
Good Morning.

Install Netflix from apkmirror.

I have installed and work fine.

Enviado desde mi SM-G986B mediante Tapatalk
[Galaxy Tab S2 Android Development] CuckooPenguin:
sm-810 - stuck at samsung logo

Thanks Sal - stil NOK : tried it again .. sm-t810, twrp 3.4.0, full wipe and data format, lin 17. version from 03.10 version + opengaps nano installed, dalvic wipe again, not installing TWRP as app - and then rebooted ... into Samsung Logo .. and left it alone for more then 2 hours .. nothing, tried a reboot and then again 1 hour .. nothing. Will revert back to 16 and check if any of the logs TWRP copied will show something.

If anyone has more tipps let me know.

Thanks everyone
[Galaxy Tab S2 Android Development] MrBlubke:
just wondering when you say "full wipe" did you include system? you need to wipe system when coming from los 16 to 17.1 that made it work for me
[Galaxy Tab S2 Android Development] jdbeitz:
I'm having the same issue with the hang on the Samsung logo after a full clean install and install of gapps. I'm on the t810 wifi as well. I noticed the file name in the download link says 210? lineage-17.1-20200902-UNOFFICIAL-gts210wifi.zip
[Galaxy Tab S2 Android Development] CuckooPenguin:
I wiped all partitions i could find under advanced wipe, system, boot, recovery, cache, internal storage ... all except ext microsd.
[Galaxy Tab S2 Android Development] MrBlubke:
20200902 is not the latest version and will not boot.... the version of 20201003 however worked, but seems to have been removed? (maybe temporarily)?
[Galaxy Tab S2 Android Development] luisalberto.rouco:
I have installed 17.1 and the are a problem with drain batery. I put muy tablet all night in fly mode and batery down 80% to 20% in 24 hours.

With 16.0 this problem doe not exist.

Enviado desde mi SM-T710 mediante Tapatalk
[Galaxy Tab S2 Android Development] chappatti:
Can anyone please confirm if ver 20201003 works? On T810.
[Galaxy Tab S2 Android Development] MrBlubke:
on my t810 Samsung Tab S2
[Galaxy Tab S2 Android Development] MrBlubke:
Here you can see it's the t810
[Galaxy Tab S2 Android Development] CuckooPenguin:
So there is hope ;) Yeeha

Still - i am curious - after failed boot pulling dmesg.log would be of the failed boot or is it dmesg from TWRP

as when i check for the kernel version i find

dmesg.log:<5>[ 0.000000] Linux version 3.10.9-g0892caab (root@ubuntu) (gcc version 4.9 20150123 (prerelease) (GCC SMP PREEMPT Thu Aug 9 22:48:34 CEST 2018..

and not some string like we see on your screenshot 3.10.9-Lunari... ?
[Galaxy Tab S2 Android Development] jdbeitz:
Thanks - any mirror to it?
[Galaxy Tab S2 Android Development] aboulafia1901:
20201003 had problem with capacitive buttons .I think [MENTION=6005084]ripee[/MENTION] works to solve this problem .Be patient .

Thank you [MENTION=6005084]ripee[/MENTION] for all the work ! ?
[Galaxy Tab S2 Android Development] bmwboyee:
downloaded the stable release and have the bootloop issue. Waiting on the new revision.
[Galaxy Tab S2 Android Development] MrBlubke:
yes could definitely be the reason to remove it, then again he didn't remove the non booting build, so I was fantasizing that it might be because it was posted as a candidate for 'official' lineage os 17.1 for our device. I've seen this behaviour happen before... but like I said merely a hypothesis I hope to be true.?
[Galaxy Tab S2 Android Development] ripee:
See the OP: no official builds from me ever. Too much hassle and not enough dev skills.
[Galaxy Tab S2 Android Development] MrBlubke:
fair enough... I understand the too much hassle part☺️ but imho you have enough skills, if it weren't for you we'd all still be stuck on stock...
[Galaxy Tab S2 Android Development] ripee:
If it weren't for raymanfx, bonuzzz, T_I, ananjaser, lunarixus, and many others, we'd be stuck on stock.
[Galaxy Tab S2 Android Development] make_tinker_jr:
Hi, I just recently managed to install v16 on my S2 SM-T710 and everything is working great so far. I just have a couple of questions that I want to ask just in case these are known issues, or maybe I did something wrong, etc.

In the camera app the shutter button appears partly "out of screen" both on portrait and landscape orientation. I have not tried any other camera apps just the default one, and I most likely won't use it much if at all so it's not a big problem for me but anyway just something I found and wanted to report.

Another thing, I keep getting these notification warnings every time I boot up the tablet. I'm not sure what they mean and if I should do something about it.

Trust - System security
This build was signed with public keys

Trust - System security
SELinux is not enforcing, your security has been weakened

For reference these have been there since I flashed v16 the other day, so even before I installed anything at all, in fact I didn't even install GApps, custom firmware and whatnot. I took a couple of screenshots about these issue but I can't find an option to attach them?
[Galaxy Tab S2 Android Development] MrBlubke:
love it that you're staying this humble, and love it even more that you give credit to all who deserve it!

I'm gonna be sticking around for future releases ☺️
[Galaxy Tab S2 Android Development] CuckooPenguin:
You can switch off those warnings under -> Settings > Security > Trust
[Galaxy Tab S2 Android Development] CuckooPenguin:
You can switch off those warnings under -> Settings > Security > Trust

---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------

Wtf - sorry for the repeated post.
[Galaxy Tab S2 Android Development] halloarno:
The 11-10 build doesn't boot on t810: stuck on Samsung splash screen.

(included opengapps nano)
[Galaxy Tab S2 Android Development] jpq:
T-710 doesn't boot 17.1 with 10-11 Build

It worked with 10-03 except touch button
[Galaxy Tab S2 Android Development] dannychow:
Same here for my T815 device. Thanks for the new build anyway~
[Galaxy Tab S2 Android Development] ytccts:
Exactly same problem for me, after full total wipe, install 17.1 10-11 and pico gapps, then wipe cache/dalvik and reboot: stay on the splash screen.
[Galaxy Tab S2 Android Development] wallace5:
I applied the 10/11 update to v16 on my T-810 and it now stops on the Samsung Splash Screen before eventually returning to TWRP
[Galaxy Tab S2 Android Development] ripee:
How about you all stick with 16.0 until 17.1 is more refined. We are in a transition period. ananjaser is working hard on Q and I will pick his work on the Note 4 for gts2. Be patient.
[Galaxy Tab S2 Android Development] ytccts:
On T-710, same issue.
[Galaxy Tab S2 Android Development] hollaho:
Same here, stuck on Samsung boot logo after dirty flashing my T-810 from 20200921 to 20201011. Have tested it with and without magisk with the same result.

Vol-Up+Home+Power took me to TWRP. Then dirty flashed 20200921 back and everything works as before.

As always, thanks for your work ripee, am a happy fan of your work!
[Galaxy Tab S2 Android Development] bmwboyee:
I flashed the 16 2020 09 and working well. I'll wait till the 17 is more stable but at least it's working. Thanks!