yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] jpq:
Well il u wanted to know whitch one is the last build

U answered by yourself ?

---------- Post added at 09:24 AM ---------- Previous post was at 08:54 AM ----------

Toiuch buttons work nos

We may vide Navbar

Can anybody give us the right command to do this ?

---------- Post added at 09:55 AM ---------- Previous post was at 09:24 AM ----------

I found thé answer

To hide navbar

Accessibility : select Gesture Navigation
[Galaxy Tab S2 Android Development] dombo1970:
When charging the device while switched off the battery level shown is wrong.

Like now, it's showing 68%, but when turning the tablet on the battery level is 77%. Turning it off it's 68% again.

T810.
[Galaxy Tab S2 Android Development] dannychow:
Just tested the 2nd 1028 build on my T815 device (dirty-flash). The navigation buttons (MENU/BACK) works perfectly now with light! What a great build! Thanks ripee again~

Let me observe the power consumption especially the off-screen mode in these few days.
[Galaxy Tab S2 Android Development] MrBlubke:
I experienced similar difference in procentage using previous builds, in recovery versus in system.

At first after dirty flash lights still didn't seem to be working (after all I enabled navbar)

they lit up while I was in settings and playing with the button light settings... so decided to do a simple userdata wipe of the device in recovery. which fixed the back and recent apps button... but the home button still doesn't light up... it works though...
[Galaxy Tab S2 Android Development] halloarno:
Here also T810, nav buttons working fine, including menu button.

Only the installed Netflix app won't start.
[Galaxy Tab S2 Android Development] MrBlubke:
I think by default LOS doesn't pass safety net, so that might be an issue I fixed this by installing and configuring magisk, but I don't have a Netflix account so haven't tried it...

also t810 here btw...

does the home button light up for anyone?

edit: I'm actually kinda wondering if it ever did now... ??
[Galaxy Tab S2 Android Development] bmwdroid:
Never did on any of my 8 devices.

At least not the hardware button. ?
[Galaxy Tab S2 Android Development] bringatore:
Clean install last version in t710

Hardware back button and recents not lightning up nor functioning, is there a fix for this issue?
[Galaxy Tab S2 Android Development] skinnyquiver:
Latest flash clean t810 things are working well for me. magisk is required if you want netflix etc.
[Galaxy Tab S2 Android Development] crcowan:
All seems good on T-710 with latest 17.1 build

Things looking very good on T-710. Faster boot. HW keys light and work.

NOTE: if you used "settings put --lineage system force_show_navbar 1" on the previous build to get the "soft" Navbar, you will have to set it back to "0" with this build to get the HW keys and lights to work.

As always, thank your Ripee
[Galaxy Tab S2 Android Development] ripee:
No, thanks to Lunarixus, Stricted and ananjaser1211.
[Galaxy Tab S2 Android Development] bmwboyee:
Just to share, on T810 and flashed the last update. Everything seems to be running smooth. Thanks! Will install magisk to see if netflix will work
[Galaxy Tab S2 Android Development] aboulafia1901:
To use Netflix ,i install it with Aurora store as anonymus ans Also hide with Magisk .I dont sure Magisk necessary for Netflix.
[Galaxy Tab S2 Android Development] sal82:
The buttons work as well?
[Galaxy Tab S2 Android Development] bmwboyee:
On mine, yes. I dont see anything that doesn't as of right now. Haven't installed magisk yet for Netflix
[Galaxy Tab S2 Android Development] lpedia:
20201028 17.1 on T-710 looks good but still no hw keys

I agree - looks good on my T-710, and boots faster. Many thanks to Ripee (et al)!

Interesting that the hw keys work on your T-710 with this version. Mine still doesn't have hw keys working (in spite of force_show_navbar zero).
[Galaxy Tab S2 Android Development] MrBlubke:
have you looked in settings -> system >buttons> backlight? play with the enable/disable there see if they respond (mine on t810 did only while in settings at first) if this is the case, do a userdata wipe in recovery, this fixed it for me...

sidenote: I've had my t810 reboot occasionally (Android, not the tablet) after long sleep, woke up the tablet entered my pin, and suddenly I saw the lineage os loading curve with circles again, after once more logging in, it stayed alive, so that's why I suspect it being deep sleep related...
[Galaxy Tab S2 Android Development] lpedia:
Thanks for the suggestions :) ... but still no hw nav keys. Neither playing with backlight settings nor userdata wipe made any difference. :(

I've seen one sudden reboot, like your 810. I'm not sure now whether it was just after waking from deep sleep.

I'm impressed with the battery life improvement on LOS 16.0 and 17.1 compared with stock Nougat. Also, the charge level doesn't drop while in deep sleep, unlike with the stock ROM. :)
[Galaxy Tab S2 Android Development] wwmhf:
I used the 20201028 17.1 on T-710 in the last couple of days. Everything worked, all the buttons and button lights. The only shortcoming was that the battery life seemed to be obviously shorter than the Lineage 16.

Tonight, I installed I used the 20201031 17.1 over 20201028 17.1 on my T-710. The installation is smooth. Everything works except for the button lights. I hope the battery life improves.

I would like to thank ripee again.
[Galaxy Tab S2 Android Development] tripLr:
1. Log in to chrome with your Google account

2. Type tiny.cc/ripee

3. Download quota will now be on your account
[Galaxy Tab S2 Android Development] halloarno:
Working Netflix (from playstore): magisk -> module magisk hide props -> set fingerprint to (I chose) tab S3
[Galaxy Tab S2 Android Development] ripee:
Have any Q builds been able to download Netflix from the play store? Any Pie builds that could not? I kept the same build fingerprints from years ago, that had been proven to pass safetynet. I suggest you also try Magisk 21.
[Galaxy Tab S2 Android Development] halloarno:
Sorry, I can't recall correctly. Now I refound this module, I can recall that I used it before. But I can't remember if it was necessary on Los16 or not? (Alway dirty flashed new builds).

Anyway, big thanks, never thought our tab s2 would ever update to a smooth working Los 17!!
[Galaxy Tab S2 Android Development] dombo1970:
Dirty flashed the 1031, T810, hardware buttons don't light up. Menu/recent button still not working.
[Galaxy Tab S2 Android Development] numbfall:
1028 is working great on gts28wifi - T710. No problems. Using for 10 hours now.

thanks ripee
[Galaxy Tab S2 Android Development] yhdelir:
Are u having this strange problem?

When answering a call it is always on speaker and everybody hears the dialog sound

is this a problem with all android 9 and 10 custom Roms?

any solution or workaround?
[Galaxy Tab S2 Android Development] Davivigo:
Build 1028 running PERFECT on my T715 (only GPS not working). Build 1031 running too , the only difference I've noticed are hardware keys (1031 no lights). Thank you again Ripee, our S2 will have an extra life!
[Galaxy Tab S2 Android Development] syd-3:
with my SM-T810, i dirty flash 20201031 on 20201028, buttons working now.

Great job, many thanks to ripee
[Galaxy Tab S2 Android Development] MrBlubke:
T810 dirty flash 20201031 over 20201028 here as well... buttons still work (they worked before with lights) but now the lights stopped working...
[Galaxy Tab S2 Android Development] slaytanic:
Same, but I'm on the sprint variant. Buttons didn't work before though for me though, but now work. Just no lights. Thanks dev(s)!
[Galaxy Tab S2 Android Development] luisalberto.rouco:
Install clean ROM And now work perfect.

Thank ripee

Enviado desde mi SM-T710 mediante Tapatalk
[Galaxy Tab S2 Android Development] lpedia:
20201031 on 710 - Nav keys now work!

Nav keys on my T710 are now working after dirty flash 20201031 over 20201028! :good: They weren't working on 20201028.

Lights still aren't working.
[Galaxy Tab S2 Android Development] MrBlubke:
Clean installed on My t810 still no lights for the buttons, but they work.
[Galaxy Tab S2 Android Development] freddy_galaxy:
First of all: Thanks for this great ROM. Appreciate all the work that has been put in.

I'm on T810 using 17.1-20201028. Buttons work with backlight. I have one small issue though: Fingerprint unlock is not consistently working. Sometimes work, sometimes not. Seems like it's working after manual lock, but not after timeout? Fingerprints are always recognized in settings and when used within apps so don't think its a hardware issue.

Anyone else experience this with this or a newer build? Should I dirty flash the latest version?

Thanks
[Galaxy Tab S2 Android Development] dannychow:
Dirty flash from 1028 to 1102 on my T815 device. The button light doesn't light up now. But it doesn't really matter to me.
[Galaxy Tab S2 Android Development] MrBlubke:
T810 (forgot to mention the device)

Dirty flash 20201102 over 20201031 wifi issues that were introduced in 1031 build are gone (guess I didn't even have time tot report them)

Button lights still not working,..
[Galaxy Tab S2 Android Development] jpq:
T710 Dirty flash 1102 o over 1028 (buttons+ light worked on 1028, no light on 1031)

On 1102 no light on buttons

Longer time on lineage logo

Atm 1028 seems Being the best build
[Galaxy Tab S2 Android Development] lpedia:
20201102 on T710 looking good

Dirty flashed 20201102 over 20201031 on T710. No significant issues so far (and nothing seems to have broken that was working before :)). Still no backlight on nav keys, but they're working, and that's the main thing. Importantly, fingerprint unlock is now working! It wasn't, with 1028 or 1031 on this device.

Thanks to ripee et al!
[Galaxy Tab S2 Android Development] dombo1970:
Menu seems to work, but I can't reach recent apps. Even the double tap on the menu button for switching to last app is not working.

Tried already to config Nova launchers gestures to reach last apps, but just no reaction.
[Galaxy Tab S2 Android Development] robertmc8:
Guess let me know when Rc1

Comes out thanks!
[Galaxy Tab S2 Android Development] BizzaBoy:
Running 1028 17.1 on a t810 since 10/29. Works very nicely. Buttons work (plus they light up). No crashes so far. Using stock gapps with a bunch of useless things removed.

Thanx sooo much.
[Galaxy Tab S2 Android Development] MrBlubke:
I've had network disconnects with that build, if you experience the same, make sure to update to the most recent version... while the button lights stopped working again, I've yet to experience any other bugs...
[Galaxy Tab S2 Android Development] mparmpas122321:
Thanks for the rom. It is the first time I am flashing a custom rom on my T810. I flashed 20201102. Everything seems to work smooth and perfect. The only problems that I have faced is the nav bar light and extreme battery drain during screen off. 20% drain over night with WiFi closed. I wish it gets better in the next builds as it is an overall great rom which resurrects our old and beloved tab s2! ?
[Galaxy Tab S2 Android Development] benwatkins:
Is there any advice for what to do when stuck on the Samsung / Powered by Android screen (before Lineage logo appears)?

I clean installed v16 20200902 on my T715 (gts2ltexx) last month and it worked fine most of the time - just the occasional random restart. Decided today to start again with 20201014. Wiped and reinstalled using the same process as I used before* and now when I restart the tablet it gets stuck on the initial Samsung / Powered by Android screen - the one that comes up before the Lineage logo appears. I've left it for 20 minutes just in case it's working in the background but no go. I am able to reset using power+vol down and get back in to recovery and from there I have tried wiping/re-installing several times but still the same outcome. Interesting thing - if I plug it in to power I get the battery/lightning bolt logo but when I unplug it's still there. The battery does charge.

Any suggestions?

*my process was to unlock the bootloader via adb, flash TWRP via adb, use TWRP to format then install Lineage and GApps from the links provided by ripee above, wipe cache/Dalvik, reboot.
[Galaxy Tab S2 Android Development] BizzaBoy:
I have seen a few. But overall super stable. There is some more battery drain over the 16.1 variant (0923 I seem to recall).

---------- Post added at 12:52 PM ---------- Previous post was at 12:46 PM ----------

I do not like the term "resurrect here". My T810 (a hand me down from my dear wife actually) is my reading device. Datasheets, research articles, browsing github, this sort of thing, gmail. In any case for me the display quality is what matters. Just had ordered a nice new Tab A, and promptly send it back ... really lousy display. For all the newer Tab Sxx devices, there simply are no good custom ROMs, and I cannot bring myself to use the Samsung GUI (I'd say "crap", others call it "improvements, matter of style I guess). So IMHO, the Tab S2 right now is the only game in town.
[Galaxy Tab S2 Android Development] MrBlubke:
only thing I can suggest is find someone here who posted his experience with the same tablet (t715 in your case apparently) and read up on their experience and which build worked and which didn't... if stuck on the Samsung logo it may very well just be a nonworking build. from what I'm reading your install process seems ok...
[Galaxy Tab S2 Android Development] ArtoD2:
Did you upgrade the TWRP to 34?
[Galaxy Tab S2 Android Development] benwatkins:
Thanks ArtdoD2 and MrBlubke. An interesting thing has happened... out of desparation I tried one of the v17 builds I had on my drive from an earlier test and it worked fine. So apparently nothing wrong with the tablet and my method. Bizarre how neither of the two v16 builds I tried would work (including the latest one from ripee's site and and older version I'm sure I installed successfully before!).

I need GPS so cannot stay on 17. Does anyone have a copy of 20200921 v16? I see many people report that one is working well on T715.

P.S. answering the question, yes I am on TWRP 3.4
[Galaxy Tab S2 Android Development] freddy_galaxy:
Re v16: Same issue with my T810 when I attempted clean install of 16.0-20201014. Seems like a broken build? Used 16.0-20200921 for a while. Great build, only thing missing was fingerprint not working consistently. Would love to try a working updated 16.0 actually. It was really snappy and I think less battery drain compared to 17.1.
[Galaxy Tab S2 Android Development] M.Miethke:
3 soft button navigation

Hello and

first of all thanks to devs and supporters.

Own a SM-T815,

installed

twrp-3.4.0-0-gts210ltexx

clean flash

lineage-17.1-20201102-UNOFFICIAL-gts210ltexx

the hardware navigation buttons are working

but without light – not nice, but I can live with it

my biggest issue are the software navigation buttons

since Android 10 – lineage-17.1 – gesture Navigation is default

I use the tablet only in landscape mode and

3 soft button navigation on ground is preferred

research means - activate in settings

settings/system/gestures

and system navigation

but I did not have any system navigation

only jump to camera and prevent ringing

is it possible to add this or

fill some configs by hand to activate

3 soft button navigation
[Galaxy Tab S2 Android Development] MrBlubke:
if you look back a few pages, you will find a way to activate software buttons, but by default these don't show up on devices with hardware buttons hence also the reason why these settings are hidden because the device has hardware buttons...
[Galaxy Tab S2 Android Development] yhdelir:
Flashed the latest version 1102 on my t715

Still the loud sound problem remains and this is a serious problem becouse it affects the main application of a mobile phone.

When answerng a call, no voice is coming or going to the other side, onle when I touch "turn on speaker", the voice comes and goes but when l turn it off the voice is still loud and on speaker so every one hears our dialog. I have this problem in whatsapp too. To make it short calling is out of use

Does anyone have this problem? Any solution?
[Galaxy Tab S2 Android Development] M.Miethke:
Thanks I finally found it

found it on post 1379

keyword is navigation bar

as su in terminal

settings put --lineage system force_show_navbar 1
[Galaxy Tab S2 Android Development] robertmc8:
Any updated getting stable for Tab s2 t713? Some reason the blue tooth battery icon is gone in Lineage OS 16 and can't save camera photos to sd card?
[Galaxy Tab S2 Android Development] -DIO-:
Tab S2 T815, On first launch bootloop, LOS 16.1
[Galaxy Tab S2 Android Development] freddy_galaxy:
T810: 16.0-20201110 stuck on Samsung logo. Tried both dirty and clean install + gapps. Waited 10+ mins, no action.
[Galaxy Tab S2 Android Development] sal82:
Why are you installing 16? 17 works now.

BUT if you really wanna install 16, uncheck "install TWRP as a system app" when prompt. I have the same tablet and had the same problem.
[Galaxy Tab S2 Android Development] -DIO-:
Installed 17, tell me how you can make the hardware buttons light up, the command did not help in the terminal #1379
[Galaxy Tab S2 Android Development] MrBlubke:
I guess you wait till next build, or try to find a previous one, but in my experience the previous one had network issues this one doesn't... the absence of the lights bothers me less, then wi-fi not connecting...

btw... there seems to be a newer build for los 16 now, so a newer 17.1 might be coming soon...
[Galaxy Tab S2 Android Development] freddy_galaxy:
17.1 is great, everything works and it's beautiful. Reason I dropped to 16 is I use Foxit reader for my daily studies and for some reason the rendering was significantly slower with 17.1. Been using 16.0-20200921 for a while and everything works except fingerprint which fails to wake up the device from deep sleep. It works when using a wakelock app to keep the system awake, but not an ideal solution of course.

Still unable to install 16-2020-1110, have unchecked the install TWRP app and pressed "Do not install". Retried to make sure. Even tried clean flash without gapps and still stuck at Samsung logo.

Thanks though.

PS: I'm on TWRP 3.4.0.0
[Galaxy Tab S2 Android Development] snsnse:
MHL/HDMI broken with latest build

As I noted above, video over MHL/HDMI worked just fine on my T815 with "Disable HW overlays" active. It did up to build 20200902, but build 20201102 broke that. Now whenever I connect an HDMI source the device immediately reboots/softboots.

I went back to 20200902 for now, but it would be great if the respective commit could be amended/reverted since the MHL/HDMI interface working (at least for video) is crucial for me, and I would prefer to not have to go back to stock ROM.

I'm not sure a logcat would help in this case, but please let me know.

Cheers
[Galaxy Tab S2 Android Development] ripee:
Please identify whatever change made the difference here and I will go back to it. Seriously, I have no idea how it worked before.
[Galaxy Tab S2 Android Development] sal82:
You need the lighted buttons? They work. That's what matters, is it not?

It might be TRWP. I have 3.2.2.0. Worked perfectly with the unchecking.
[Galaxy Tab S2 Android Development] freddy_galaxy:
Downgraded to 3.2.2.0, still no go here...
[Galaxy Tab S2 Android Development] MrBlubke:
what about todays build? 20201111?
[Galaxy Tab S2 Android Development] freddy_galaxy:
Oh yeah it works! Thanks. Dirty flashed over 16.0-20200921. Takes a while to boot, but seems to be working as a charm after.

Fingerprint still not waking up device from deep sleep, but I think that's a general issue with LOS 16:

https://gitlab.com/LineageOS/issues/android/-/issues/778

From my logcat this is what happens when device enters deep sleep:

11-11 03:53:28.120 3668 3668 V FingerprintService: stop client com.android.systemui
11-11 03:53:28.121 3474 3474 I chatty : uid=1000(system) fingerprint@2.1 expire 5 lines
11-11 03:53:28.122 3668 3668 W FingerprintService: client com.android.systemui is no longer authenticating
11-11 03:53:28.122 3668 3668 V FingerprintService: Done with client: com.android.systemui
11-11 03:53:28.122 3668 3668 V FingerprintService: handleError(client=com.android.systemui, error = 5)

Looks like there's a lockout happening, which explains why I need to unlock with pattern even after waking up device with home button.

As mentioned, my workaround is using a wakelock app to prevent deep sleep.
[Galaxy Tab S2 Android Development] jaysusw:
Works on T810, clean installation

Thanks, Nov 2 build works here.

Issues:

-nav buttons not working, nor illumination (using soft buttons instead)

-WiFi sometimes unreliable, not finding networks, switching on/off helps

-2nd user account unstable, spontaneous reboots

-not able to setup family link (daughters device), loop error message: "This profile manager is required for Google accounts managed with family link."
[Galaxy Tab S2 Android Development] MrBlubke:
maybe you should add your specific device... each device has different users with positive experiences...
[Galaxy Tab S2 Android Development] IngoPan:
What nav bars please ? You mean the back button isnt working ?

Regards, Ingo
[Galaxy Tab S2 Android Development] MrBlubke:
he means the hardware buttons
[Galaxy Tab S2 Android Development] MrBlubke:
for the t810 try the more recent build
[Galaxy Tab S2 Android Development] bmwdroid:
Just checked but I don't see a more recent one for gts210wifi 17.1 than 20201102??
[Galaxy Tab S2 Android Development] jaysusw:
Isn't T810 specific enough?
[Galaxy Tab S2 Android Development] MrBlubke:
yeah sorry, as my quote showed didn't show in the xda app on my phone...

there are more recent builds where the buttons work (leds don't in latest build, but the buttons do)
[Galaxy Tab S2 Android Development] sal82:
Try installing without gapps. See if it works.

Not sure what you're doing, but I have the same tablet. And 16 worked beautifully.
[Galaxy Tab S2 Android Development] freddy_galaxy:
Hey yeah it works now with 16.0-20201111
[Galaxy Tab S2 Android Development] sal82:
What was wrong?
[Galaxy Tab S2 Android Development] snsnse:
I'll try my best. I guess the T815 related code repo is hosted here

https://github.com/universal5433/android_device_samsung_gts210ltexx

but I don't seem to be able to find the changelog/commit list for the 20201102 17.1 release. Could you please point me to it? Thanks!
[Galaxy Tab S2 Android Development] freddy_galaxy:
Don't know. The 1111 version worked, was never able to run 1110.
[Galaxy Tab S2 Android Development] MrBlubke:
ah yes for 17.1 that's the most recent one and the one I'm running (seems download folder has been cleared up for confusion as well).

it's confusing when answering posts about 16.0 and 17.1 simultaneously ??

that being said, with a clean install of this latest version the buttons should work, however they don't light up, (in the previous build (I actually think it might have been 2 builds previous but not more) they lit up as well. WiFi still sometimes doesn't recover after deep sleep..., but took me longer to experience the issue than the build with the lights lighting up...

what issues are you having can't find another recent post by you?

---------- Post added at 03:52 AM ---------- Previous post was at 03:50 AM ----------

from what I've read the 1110 version worked for no one, hence the fast coming of this new build. glad to see you're up and running again.?
[Galaxy Tab S2 Android Development] bmwdroid:
Having no issues.

Mine is still on AEX ROM V6.7 from May 2020 but I was thinking of upgrading.

With that ROM I'm using software nav bar anyhow but with six buttons what LOS can't offer.
[Galaxy Tab S2 Android Development] Kyrat:
Hi, I am using los 17, its very smooth I only have a problem with app Movistar Play, appears a message box about not passed a compatibility test with DRM player or something like that. Can you fix it please?