yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] bobbytomorow:
I just flashed this and it is suddenly not recognized by any computer, I've tried two Windows computers (windows 7 and Windows 10) as well as my Macbook. ADB is not recognizing it, Odin is not recognizing it, I can't get it to mount from TWRP or be recognized in download mode. It WILL charge from computer USB ports but is totaly and completely not recognized beyond that.

Build Jul 27 2018

*Edit switched cables and all good*
[Galaxy Tab S Android Development] Crescendo Xenomorph:
posibility of Android Go fro this device?
[Galaxy Tab S Android Development] jpearn:
Is this for the T700 or just the T800 ? I was running official on my T700 and tried unofficial but no fingerprint enabled. I am wondering if all the fixes were pulled into the T700 branch as there's not been an update on github for a while
[Galaxy Tab S Android Development] bobbytomorow:
Switched cables and all good.
[Galaxy Tab S Android Development] M9x3mos:
I just tried the unofficial from them too and cant get fingerprint either. Guess that isnt for the 700.
[Galaxy Tab S Android Development] jtcnb:
Seems to me the 7.1.1 variant had a working fingerprint scanner.... wonder why it is not in this newer one
[Galaxy Tab S Android Development] jpearn:
Looking over github, there are only commits to enable it on the SM-T805, not sure why ?
[Galaxy Tab S Android Development] lollo78:
With the latest build Deathly Adiutor stopped working. Have you changed Kernel?
[Galaxy Tab S Android Development] DarkExistence:
its being worked on for SM-T700, SM-T705 and SM-T800
[Galaxy Tab S Android Development] gruuvin:
I guess at some point this went official and "root for apps" option I find in all my other Lineage installs is not available in this one? (only option is adb only) The first page of this thread mentions nothing of an su binary we can flash or a root method of any kind. Could someone kindly point me to a working and proper method of root access with this ROM that gives me the option to grant root access to apps?

I've searched the thread, and found nothing definitive.

Thanks!
[Galaxy Tab S Android Development] SkOrPn:
You use the same root app as we have always used, either LineageOS su or magisk, from the same location they have always been. And you flash them immediately after you flash the ROM, or immediately after you flash your rom+gapps of choice.

https://download.lineageos.org/extras (you want su (arm) for 14.1)

https://xdaforums.com/apps/magisk (magisk 16.0 is good enough)
[Galaxy Tab S Android Development] gruuvin:
I re-ROMed maybe five tablets and four phones over the last eight years, about every 6 - 12 months; all Android, since Android 2. Rooting methods were all different. I've done debloated tw ROMS CM 10 and 12 and LOS 14 and 15--actually did an LOS 14 and a 15 on two other devices within the last week, and both of those builds had root built in for ADB and apps and selectable in dev options (no flashing su binary suggested or recommended). I've not done 14 on this tablet in over a year. People report screwing up their devices too often by trying to root via a method that's not exactly right. I had the su zip on this device from a year ago when I flashed it on an old LOS build, but I wasn't privy then to LOS builds just baking them right in like I've seen on two others I've done this week.

Thanks again for the help. It got me going in no time. I even flashed it after I installed LOS and gapps, then booted up and installed another 30 apps. Seems fine!
[Galaxy Tab S Android Development] SkOrPn:
Your welcome. Yeah root for apps uses the same root files. Nothing special unless you need to do something special. If you just want simple root I would use LineageOS SU, but if you want a systemless root to do more advanced tasks, like hiding root from certain apps, then you need Magisk.

Yeah I have been doing this too ever since the world's very first Android device. Before Android I was using those slider windows mobile phones (HTC TyTN or Hermes as it was called) and Blackberry's of course. I was there in line at 6am waiting for the first Android phone to sell (My old HTC Dream, which I bought several of those)... Lol, anything to replace my Blackberry was fine with me. And yeah I skipped iPhones altogether, I just don't like Apple products at all, not yet anyway.
[Galaxy Tab S Android Development] gruuvin:
I LOVED HTC back in the first days of android! My good friend had the Hero, and I got the Glacier--all metal case, replaceable battery, thin but built like a tank. I still have it. I should see if something newer could run on it. I love reviving old gadgets!
[Galaxy Tab S Android Development] SkOrPn:
HTC was way a head of the game back then and willing to try new things, but sadly they misstepped many times and let Samsung and Apple and several others take over. With money like Samsung and Apple has for R&D, they will probably always stay on top now.

Good luck with your T700 :good:
[Galaxy Tab S Android Development] jotade:
Hi everyone. Is the IR Blaster working with the T700 version? Thanks
[Galaxy Tab S Android Development] hotrodwinston:
Anybody else having issues with the tablet locking up on the latest update? Mine has locked up twice since a clean install - this morning it was locked for about 2 hours - no response from touch or buttons , couldn't even force it to reboot by holding power button.
[Galaxy Tab S Android Development] stormy_gale:
[Deleted wrong rom thread]
[Galaxy Tab S Android Development] Angel2112:
I have the T700 and can confirm the IR blaster is working as expected.
[Galaxy Tab S Android Development] ghalalb:
I've had locks, only while playing video. I've been able to reboot though by holding either vol down and power or vol up and power, I can't remember which. It's probably happened to be half a dozen times over the last 6 months, not only on recent updates.
[Galaxy Tab S Android Development] RAGEdemons:
As of the latest build, Deathly Adiutor is no longer supported, nor does it work - it throws up a message saying an incompatible kernel has been installed.

Dev has mentioned in recent past that this is due to kernel changes.

So, since this affects a number of us, what is now the alternative? - I wish to modify charging rate etc.

Alternatively, are the changes in the new kernel vs deathly adiutor supported kernel worth the incompatibility? i.e. Can I flash a recent build of Deathly Kernel to have the configurable options back? (Deathly Kernel seems to have been last updated 3 years ago, which isn't very encouraging).

Any other good configurable kernels that can be flashed and used with LOS 14.1 on T700?

I'm not sure which direction to turn now :(
[Galaxy Tab S Android Development] gellmar:
I wonder who told you Deathly is abandoned? All updates the official kernel gets are ported into Deahtly at the same time. This includes CVE patches and security bulletin fixes. Say, tomorrow the September Android Security Bulletin will be merged and on Saturday the updated kernels will be built wity Exynos5420 unofficials and starting Sunday - for officials.

For me though an official kernel is far more stable and the particular charge rate issue will be fixed for all Exynos5420 devices (official and unofficial) after T805 goes official.
[Galaxy Tab S Android Development] RAGEdemons:
gellmar and others,

Please pardon my ignorance - I am not completely familiar with LOS but I wish to learn; I come from a technical background.

What you have said intrigues me a great deal. It raises questions - Would you kindly elaborate on what you mean?

1. When I google "Deathly Kernel", I am brought to threads on the XDA forums from 2015 which seem to be dead. Is there another thread for the deathly kernel?

2. a. Where can I download the unofficial and / or official builds which contain the updated deathly kernel that you speak of? I downloaded the latest from the LOS website, and presumably this didn't come with Deathly Kernel, which is why I am posting...

2. b. How does one know when deathly will be updated, and when it will be built into official/unofficial LOS builds?

3. a. You speak of the "particular charge rate issue". Has this been officially identified as a problem that others are having too? How do you know when it will be fixed?

(For reference, I had reported the bug here: https://jira.lineageos.org/browse/BUGBASH-1763 , but a dev failed to reproduce it so I sent him a USB tester to see for himself - no reply since, but the bug was 'workarounded' by simply adjusting the sliders in Deathly Adiutor with a supported kernel.)

3. b. When will the "T805 go official"? How does one know?

I appreciate your insight and would love to learn. Thank you :)
[Galaxy Tab S Android Development] gellmar:
No problem :) Here we go:

There is no dedicated thread to Deathly kernel but Deathly kernel is the one powering the unofficial builds from Team Exynos5420 (https://www.exynos5420.com). All fixes to it can be tracked in team Gerrit: https://review.exynos5420.com The "cm-14.1" branch of project "exynos5420/android_kernel_samsung_exynos5420" is Deathly kernel source, while "cm-14.1-new" branch of the same is the mirror of LineageOS kernel used in official LineageOS builds.

Unofficial builds featuring Deathly kernel can be found here: https://download.exynos5420.com/

With official LineageOS builds, the best is to check https://www.lineageoslog.com for chagallwifi - the changelog will list exynos5420-related merged commits into LineageOS repositories.

With unofficial builds, the only way is to track Exynos5420 Gerrit.

Not officially confirmed but [MENTION=4222965]deadman96385[/MENTION] asked me to check this out as you made some efforts to prove the existence of a bug.

I hope to have in the upcoming days. It depends on LineageOS directors to approve the shipping of device (yes it is rather formal but the same story is with every device). I will create a separate topic for official ROM.
[Galaxy Tab S Android Development] RAGEdemons:
Thank you very much for this insight [MENTION=5214636]gellmar[/MENTION].

It sounds like the most straight forward option would be to use the https://www.exynos5420.com unofficial builds. Is there a significant difference between this and the official builds with "exynos5420-related merged commits into LineageOS repositories"?

Thank you kindly for also checking out the charging issue. Do you have a USB charge counter to aid you, or would you like me to paypal you some money so you can buy one for your testing purposes?

Kind regards :)
[Galaxy Tab S Android Development] gellmar:
Yes, for now obtaining unofficial build from Exynos5420 is the simplest variant. The official kernel is more stable as it lacks all Exynos5420 customizations like UKSM, charger, undervolt etc and one of these customizations brings occasional freezes. They have gone with official kernel.

I do have access to usb tester at the friend's repair shop so I think I will be able to check it locally + I will send you updated kernel so you can confirm with your measurements.
[Galaxy Tab S Android Development] SkOrPn:
Hey guys, got a question. I am on latest Lineage as of last Fridays release. My T700 also has TWRP 3.2.2-0.

It has been running great for months now, Every Saturday morning I download the latest LOS and go into TWRP and update my tablet. However, today, for no apparent reason whatsoever it is suddenly in a bootloop. It has never had a bootloop before, it boots into the normal TWRP logo and then suddenly reboots, shows the Samsung GALAXY TAB S screen, then tries to go back into TWRP, over and over and over again. 10 minutes ago I was in the LineageOS and everything was working perfectly.

So, was there something wrong with last weeks build that I am not aware of (I never reboot the device except for on Saturday mornings for the update), or am I just finally unlucky with the consistent updating? TWRP has been on the device ever since I got it years ago without any issues, but now it "suddenly" fails to boot into TWRP for no apparent reason. What should I now try to do? I can't seem to force shut it down either.

EDIT: Woa, nevermind. My instinct told me to pull the sd card out (which is currently formatted as internal) and then TWRP booted up just fine. Why on Earth would the SDcard suddenly cause it to bootloop? I hope all my data is still in tact, lol.

EDIT2: OK, solved I think.

If this happens to you do THIS---> Pull your sdcard out of your device. The tab will now boot into TWRP. Now put back your sdcard and boot to Android normally. Now all your apps etc will be back per normal. Now start transfering your data off your device, including any apps/data you may have such as Titanium backups or TWRP backups (as I am doing right now). Once all your data is safely on a USB pen drive, download the latest LineageOS, latest Gapps and latest TWRP etc and install everything fresh and clean from the USB pen drive. You might as well because obviously something is now wrong with the setup. You really do not want to lose data or your long time running setup for no reason.

I will now flash the latest TWRP, LOS, Superuser and Gapps, just because I am forced to, and then I will use Titanium to put everything back the way it was before a normal reboot screwed everything up. Lol

I hate being forced to do this on a Saturday morning without any explanation as to what happened :confused: Maybe it is just time for a clean install....
[Galaxy Tab S Android Development] heliosue:
To kernel or not to kernel?

Search didn't find an answer for me. I haven't rooted and installed custom ROMs for several years and I've either forgotten or never knew the answer. Q. Does this ROM include a kernel. Sorry, I can't seem to figure out whether or not I need to separately download and install that kernel link on the OP, or if it is there for another reason. I'm finding conflicting answers regarding ROMs and kernels all over the place.

Thanks.
[Galaxy Tab S Android Development] SkOrPn:
All ROM's include the linux Kernel or they wouldn't run. You can't have an OS without its engine, just like you can't have a car or train or plane without its engine. Without the kernel the OS would just be bricked.

EDIT:

1. Install the ROM LineageOS 14.1. This will come with the basic latest 7.1.2 Android. No Google apps and a very few basic apps will be included.

2. Install OpenGapps if you would like some Google Apps and the Play Store. Use ARM and the 7.1 package. I like using the OpenGapps mini package because anything else I need I can install from the play store myself.

3. If you want the device rooted you can use either SuperSU, or Lineage 14.1 SU, or Magisk. SuperSU is aging and not being maintained, LineageSU is the recommended for simple SuperUser use, and Magisk is for more advanced SuperUser stuff and currently the most updated and maintained of them all. This is solely a user choice.

Good luck... :good:
[Galaxy Tab S Android Development] heliosue:
Thanks so much for the quick reply. I did root using CF Root and installedl TWRP yesterday, but the kernel being listed separately from the GAPPS and the ROM in the first post sort of confused me. I did download the GAPPS in the first post, but I don't think it was the one you mentioned. I'll look for it. I am using Super SU and it seems to be working okay. Can I install one of the others and then delete Super SU?

Thanks again for your help. I'm trying to do this one step at a time and the next step is getting this ROM on the tab.
[Galaxy Tab S Android Development] SkOrPn:
The OP says to use opengapps, just like I said above. For this device Gapps is ARM and the 7.1 package. I use the mini normally or even pico, but the choice is a user choice.

I would put the rom, gapps and superuser of your choice on a USB pen drive for now. I would then do a full DATA Format after backing up whatever you want on the device.

Then

1. Boot into TWRP

2. Click on the WIPE button and then format DATA by typing yes (you cant miss this option)(This is usually recommended when coming from another ROM).

3. Go back into the Wipe section of TWRP and click on Advanced Wipe, then select Dalvik ART Cache, system, internal storage and Cache.

4. Go to the Install page, click on the Select Storage button and select your USB device, and install first LineageOS 14.1, then select "Add More Zips" and select Gapps, then select "Add more Zips" and select your Super User Zip. Once all three Zips are selected go ahead and swipe the BLUE ARROW Bar to the right and all three Zips will install one after the other.

You should be good to go after that. Remember the first boot always takes a little longer than normal Android boots. Just ask here any more questions if you get into trouble installing this LineageOS.
[Galaxy Tab S Android Development] heliosue:
Okay, I finally clicked on the correct GAPPS. Will try to download and get the ROM, etc. installed. Knowing me, I'll most probably be back with more questions. Thanks again.
[Galaxy Tab S Android Development] Crescendo Xenomorph:
speaking about T705, I see in github of T700 that the fingerprint is enabled in T700.

why it isn't in T705?

what's the problem / difference?
[Galaxy Tab S Android Development] gellmar:
It will be enabled in next unofficial ROM on Saturday. All was about lack of testing. In case you want to become a beta tester (i.e you can allocate ~30min on demand to make a backup, flash ROM clean if required, test and restore then in case something goes wrong), please let me know.
[Galaxy Tab S Android Development] Crescendo Xenomorph:
I think I'm more than willing to become your beta tester :highfive:
[Galaxy Tab S Android Development] qbic2:
Another T705 user (Exynos).
[Galaxy Tab S Android Development] evo_tr:
The finger print service is working finally in the latest rom for T700
[Galaxy Tab S Android Development] C0derbear:
I had no problems registering fingerprints on mine, seems to work reliably. Not quite as nicely as my GS8+ but considering the hardware difference I'm quite impressed it works as well as it does.

Thanks LOS team, appreciated.
[Galaxy Tab S Android Development] Flaggusp:
How is possible to install this rom to the T705? Thanks
[Galaxy Tab S Android Development] lefti696:
Hello guys, I need your help, I have no idea what is going on.

I finally decided to flash my T700 with LineageOS 14.1 and when I have done that the device is stuck on Galaxy Tab S logo with backlit keys at boot.

First I had a problem with entering twrp (yes i know the key shortcuts). I flashed twrp as AP with Odin, knox flag was tripped as 0x034 or something similar but there was still stock looking recovery. I had to first downgrade from newest stock to stock Android 4.something. Then twrp flashing succeed (setting knox to 0x1) so I can enter it and flash custom roms.

I flashed all 4 newest available LineageOS with no success. When verification of zips is checked i got error 7. (no matther if downloaded with pc or tabler, to sd card or OTG usb). Flashing was done after disabling it. I used open google apps v7.1 for arm but even with skipping this zip, problem with stuck at boot persists. The same with LiquidDeathOS. Of course with formating partition, clearing Dalvik or Cache and all that stuff.

But when flashing old CyanogenMod 12.1 with gapps 5.1 everything works fine (verification of zip and device booting).

I also done same procedure at the same time for my old Galaxy S4, with twrp and lineageos 14.1 and all went smooth from newest stock rom.

Maybe you have any clue what is wrong here?
[Galaxy Tab S Android Development] lefti696:
Ok, I figured it out. I had to flash first stock Android 6 rom and then flash twrp and lineageOs 14.1 and it booted with success. Great :)

As suggested here:

https://www.reddit.com/r/LineageOS/comments/75t1tv/galaxy_tab_s_smt700_stuck_on_boot_logo_installed/

Edit:

Used LineageOS for a few day and wow I like it so much! Way smoother, lighter and faster than stock rom. System is using less ram, which means more ram for apps. So pleased :) Thank you great developers of LineageOS!
[Galaxy Tab S Android Development] j1505243:
Hey [MENTION=4222965]deadman96385[/MENTION]

My brother used an old CM12.1 build for long and we cleaned it all. Now we are on the newest official LOS and there's some bug or a feature:

Minimal brightness in the manual mode is *20* in the /sys brightness node. While after selecting auto, we easily get the value of 1. Since this device is more likely to be used indoors, I don't feel any reason to limit manual setting. We really aren't going to blame LOS or anyone but ourselves for setting the brightness too low when sitting on the bright side of Mercury. Although requests suck, I hope you'll notice it :> Thanks for all the work done!

Edit: found the commit https://review.lineageos.org/#/c/LineageOS/android_device_samsung_exynos5420-common/+/222169/
[Galaxy Tab S Android Development] vitor.rego:
Hi everyone!

I had a stock 4.4 Rom and decided to install this ROM.

What I did was:

1. Downloaded this ROM file lineage-14.1-20181109-nightly-klimtwifi-signed.zip from LINK provided on the post

2. Downloaded the GApps file open_gapps-arm-7.1-stock-20181110.zip from the site opengapps.org/ as link provided on the post

3. Installed TWRP Recovery (twrp-3.2.3-0-klimtwifi.img)

4. Restarted in Recovery mode

5. Wiped Cache/Data

6. Successfully installed the ROM from External Card

7. Successfully installed GAPPS from External Card

8. Wiped cache and rebooted device.

Now the device is stuck on "Samsung Galaxy Tab S" screen.

Tried redoing the above process but still stuck.

Could someone give me tip on solving this?

Thank the community in advance.
[Galaxy Tab S Android Development] SkOrPn:
It is well known fact that you must first have upgraded to stock Android 6 (Marshmallow Bootloader) at very least before going to newer roms. These lineage threads sometimes assume that the user knows that because that is ALWAYS learned first when doing proper research ;) You now need to go back to 4.4 and then upgrade to stock 6.0 or what ever the latest stock rom is and then upgrade to Lineage 14.1 (which is pure Android 7.1.2). OR this might be easier, flash the Marshmallow bootloader directly yourself using Heimdall or Odin. You can find the latest bootloader at the link below. Good luck...

https://xdaforums.com/galaxy-tab-s/general/t705-marshmallow-bootloaders-t3477462
[Galaxy Tab S Android Development] vitor.rego:
I'll do that and reply the results here! Thank you again!!
[Galaxy Tab S Android Development] SkOrPn:
I tried to see if there was a flashable bootloader.img but I am not sure, or I simply forgot, on how to flash the bootloader using TWRP. I think that was possible too since TWRP can now flash images. But, you might as well learn how to use Odin or Heimdall. Just look for all the guides on the internet.
[Galaxy Tab S Android Development] vitor.rego:
Just updated the BL(using odin) as you said and the Device successfully rebooted and loaded the OS.

I'm just installing GApps now.

You were straight to the point. Thank you so much!
[Galaxy Tab S Android Development] SkOrPn:
Your very welcome.... Enjoy Android 7
[Galaxy Tab S Android Development] _ig_:
Is battery life any better? Also does everything work (e.g. fingerprint sensor, bluetooth, etc.) Many thanks.
[Galaxy Tab S Android Development] KingUsman:
I've noticed sound gets really distorted at high volume
[Galaxy Tab S Android Development] evo_tr:
I have the same problem, I thought the speakers were dead. Are you sure it is about the rom?
[Galaxy Tab S Android Development] lefti696:
I haven't benchmarked but I'm sure it's not worse than this on stock rom. I have one year old battery replaced at Samsung Service.

Everything that I use is working fine (it's my mutimedia machine so don't need bluetooth or fingerprint sensor). I read earlier that FP sensor is supported in current versions of Lineage OS.

two post earlier I same same question and wrote about solution :)
[Galaxy Tab S Android Development] KingUsman:
Pretty sure it's the rom
[Galaxy Tab S Android Development] lefti696:
Also noticed that in night its too bright in manual mode. Thanks for the tip that with auto brightness you can go lower than that! My eyes are grateful :)
[Galaxy Tab S Android Development] SkOrPn:
Anyone know why we didn't get a new build on Friday? Just curious.