yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] Paulicat:
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

This thread is for Unofficial LineageOS 14.1 builds for klimtwifi (SM-T700 and very soon SM-T800). The following will not be supported here:

Custom kernels

Mods

Xposed

I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:

Flashed a custom kernel

Installed or did mods from untrusted sources

Modified system files

First time flashing LineageOS 14.1 on your device, or coming from another ROM?

Download the zip(s)

Install a compatible Recovery

Perform a nandroid backup of your current ROM (Optional)

Wipe data/factory reset

Flash LineageOS

Install the Google Apps addon package (Optional)

Reboot

​

SM-T700: 2017-01-17

Google Apps:

http://opengapps.org/

Kernel

https://github.com/exynos5420/android_kernel_samsung_exynos5420

Device Tree

https://github.com/Paulicat/android_device_samsung_klimtwifi

[MENTION=4222965]deadman96385[/MENTION] (for answering questions and help!)

[MENTION=4193974]Barracuda77777[/MENTION] (For helping along the way)

[MENTION=3511708]UpInTheAir[/MENTION] for his kernel magic and misc fixes

[MENTION=3857343]crpalmer[/MENTION] (for picassowifi device and kernel gits - the base [MENTION=4193974]Barracuda77777[/MENTION] and [MENTION=4405529]nvertigo67[/MENTION] started of from)

[MENTION=2346758]eousphoros[/MENTION] (for his device git)

[MENTION=4405529]nvertigo67[/MENTION] (for his work on chagallwifi)

[MENTION=2287118]Nexorrr[/MENTION] (for his work on chagalllte)​
[Galaxy Tab S Android Development] Paulicat:
Known hardware bugs:

Fingerprint sensor not working yet.

Known lineageOS bugs:

Setup wizard doesn't give option to restore device from Google yet.

Suggested:

Format data and cache as f2fs since you have to clean flash to this anyways.
[Galaxy Tab S Android Development] aumast:
What about t705?

Envoyé de mon SM-T705 en utilisant Tapatalk
[Galaxy Tab S Android Development] Sprelle:
Already installed! Looking good so far :)
[Galaxy Tab S Android Development] amateurhack:
I look forward to giving this a try soon. I take it the the camera issues listed also means that the video issues that were present in the AOSP ROMs are in this ROM as well?
[Galaxy Tab S Android Development] Paulicat:
No the video issues are not in this rom.

Video is working perfectly.

Camera will be fixed in the next hour or so, I broke the camera with a typo. :D
[Galaxy Tab S Android Development] amateurhack:
KAZINGA!!!! We may have a winner!!!
[Galaxy Tab S Android Development] Paulicat:
[MENTION=4222965]deadman96385[/MENTION] is already handling the T705 klimtlte, look for his thread here:

https://xdaforums.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t705-t3534828
[Galaxy Tab S Android Development] Paulicat:
First post link to rom updated with camera fixed.

You MAY have to clean flash to get camera app back (if camera app is missing).
[Galaxy Tab S Android Development] amateurhack:
I was going to wait for the weekend, but I might just have to flash this tonight!!!! I can't wait!

Perhaps [MENTION=6064372]malosasha[/MENTION] would like to take a look at your fixes and see if they can be applied to the AOSP ROM.
[Galaxy Tab S Android Development] cucumbersmell:
Awesome!! Any chance of an OMS version until Lineage Theme Chooser is available?
[Galaxy Tab S Android Development] Paulicat:
Sorry but I don't plan on diverging away from the Lineage rom.
[Galaxy Tab S Android Development] Paulicat:
You know what, I've been using it for an hour or two, and it is definitely worth upgrading to this.

Biggest bonus thing I've found in Nougat that I didn't really see use for in a phone...setting the "Display size" up a few notches in the settings.(without the dpi hacks from older android) and having much better control over ui size without dpi hacks.

I couldn't deal with the small dpi's...and some apps would screw up if you blew it up too much.

Nougat seems to be doing a great job handling this now.
[Galaxy Tab S Android Development] dknk99:
Did a dirty flash of current version with the camera fixed over previous version. No stock camera app showed up so I installed "Open Camera". That works, so it looks like you need a clean flash to get the stock camera app to show up. Great job on this ROM...
[Galaxy Tab S Android Development] cloud1250000:
im ready to flash this on my T800 when its out ;)
[Galaxy Tab S Android Development] cucumbersmell:
Greatly appreciated, as is! :)

I assume you mean stock LineageOS, as there are LineageOS roms with OMS for Substratum. :)

Example: LineageOS with OMS for Moto G4
[Galaxy Tab S Android Development] Paulicat:
Ya I figured that might happen, the camera app is actually there but it just gets hidden.

Clean flash will have camera though, I did it on mine.
[Galaxy Tab S Android Development] Paulicat:
Yes stock LineageOS is what this thread will be for.

First post updated with T800 test build!

Reminder though this is a blind build as I don't own a T800.
[Galaxy Tab S Android Development] Paulicat:
Check first post!!
[Galaxy Tab S Android Development] greeg32:
Hey Paulicat, just FYI the hangouts SMS bug has persisted ?. Thanks for all you do.
[Galaxy Tab S Android Development] rloebrloeb:
What are the standards for T-800 to no longer be deemed "test"?
[Galaxy Tab S Android Development] Paulicat:
It would seem there are enough reports to remove test status now!

I'm resyncing and rebuilding today for T700 and T800 so whatever new commits from lineageos team will be included as of today.

Links will be updated in a few hours.
[Galaxy Tab S Android Development] rloebrloeb:
Great, will give it a try this week.
[Galaxy Tab S Android Development] Mtotallywired:
How new is your tab? Wondering if maybe it's just my battery at this point? I drained 12% in 5 hours last night. Any other mods to your settings or deathlyadiutor?

May try to uninstall everything and drain to zero and recharge and see.

However, I will say, I've noticed that the battery drain is consistent with the drain on my phone when it's in a weak service area... I don't know if there's a bug that's causing it to "scan" for a network or what not but as it stands there's no way to turn it off.
[Galaxy Tab S Android Development] Bart1981:
Hey, this is really great news. Running vanir now which has a great standby time (already 8 days now). So very curious to this rom.
[Galaxy Tab S Android Development] koimr:
I just switched from Vanir to this ROM this morning (as I completely trust [MENTION=5168758]Paulicat[/MENTION]). Although I really should give it a few days to settle in, all I've done is restore my apps with TiBu and charge up to 100% and then unplug. So far it's been sitting here for two and a half hours and still at 100% so this is promising. :)

This is pure standby time on a T700.
[Galaxy Tab S Android Development] Paulicat:
Cheers to everyone enjoying the rom.

To touch on standby time...I am having the exact same standby if not slightly better than Vanir.

If you have drain, get BetterBatteryStats on and find out what apps causing it because I'm quite sure its not the rom.

New builds up for T700 and T800.

Added: Ambient display from Exynos5420 repos, nice work guys!

Added: LineageOS now has a boot animation.

Added: Various commits from LineageOS team.
[Galaxy Tab S Android Development] Bawdy George:
Just bought a refurbished unit. Battery seems near-new.
[Galaxy Tab S Android Development] neozen21:
Just installed the new 20170117 version for T800.

I noticed that now in Developer Options, there only "ADB only" and "Disabled" choices for Root Access. The "Apps and ADB" option disappeared. Now we don't have root for apps, unless you install SuperSU..

Also, now there is no su command. I don't see su in /system/bin.
[Galaxy Tab S Android Development] kurt0815:
Ditto
[Galaxy Tab S Android Development] amateurhack:
I've said it a thousand times: battery issues are almost never related to the ROM.
[Galaxy Tab S Android Development] Mtotallywired:
Just clean installed newest build. Paulicat and those who experiencing great standby times, have you done anything to your settings to optimize? Did you / do you use deathlyadiutor to modify kernel behavior at all? I noticed it's not included in the latest version. Also are you guys rooted? If so what version of supersu are you using?
[Galaxy Tab S Android Development] swazau:
Does the latest version have deathly kernel? If not how would I install it
[Galaxy Tab S Android Development] neozen21:
You mean the Deathly Auditor?? It's available in the Google Play Store.

https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads

https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree (Premium ad-free)
[Galaxy Tab S Android Development] Paulicat:
LineageOS change...not me! :D
[Galaxy Tab S Android Development] Paulicat:
Default settings to everything, pico gapps. I don't use google search app or facebook...two of the biggest battery suckers out there.
[Galaxy Tab S Android Development] pitrus-:
Exactly, this is to make the ROM safetynet compatible for Google Pay service by removing root in the normal user builds, there's a build flag that can be set to true to re-enable built-in root for apps if one doesn't care safetynet passing.
[Galaxy Tab S Android Development] swazau:
Why would we want built-in root when u can just flash SuperSU?
[Galaxy Tab S Android Development] pitrus-:
Ha ha, it's like saying "why not replace the steering wheel in my car, when I have one lying around" ?
[Galaxy Tab S Android Development] Carlosk1966:
GPS

Hello.

Anybody try GPS? For me is not working.
[Galaxy Tab S Android Development] deadman96385:
GPS is not working yet, only way to get something is if you enable it to use wifi and be hooked up to it.
[Galaxy Tab S Android Development] weeekwo:
just linking some posts from sm-t805 thread for 14.1 since here more attention; catlogs attached at the actual posts

rare wifi instability experienced using rom:

another that seems related to accessng storage; also hanging are browser downloads:

random crash opening a screenshot after using youtube app:

and agreeeing with last guy gps seems to hang even after permission is given

hope this goes well; happy to help!
[Galaxy Tab S Android Development] deadman96385:
Wifi instability will happen sometimes its low on my to do list, not sure on the browser one i will take a look, youtube is unstable on N due to the omx codecs not functioning properly that is why things are zoomed as well when the resolution is raised.
[Galaxy Tab S Android Development] weeekwo:
it's actually browser videos where I've seen scaling problem; YouTube videos seem fine at least on my device except for that one crash I logged.
[Galaxy Tab S Android Development] deadman96385:
If it starts on a low resolution then auto goes up by say your internet speed going up then instead of getting higher res it will just zoom.
[Galaxy Tab S Android Development] kaodd:
Nothing beats superSU:cowboy:
[Galaxy Tab S Android Development] swazau:
Its like saying "why not replace my steering wheel, when I have a better one just laying around" ??
[Galaxy Tab S Android Development] zigonneux:
about slow browsing, get the app DNS changer and write down in there the dns ip that your router is using and see the difference... it's flying. Without this it's a wait and wait... ( for some people)

about the battery drain, if you have facebook and MAPs that stay on all the time, your battery won't last long. In the wifi options, fix it so that wifi is OFF when the device is sleeping and use the notices timer to totally ignore the notices at night. If you want the notice when your device is sleeping, then leave the wifi on but put it off at night... ( airplane mode or timer) Go to facebook in your browser NOT the app.

My 2 cents.
[Galaxy Tab S Android Development] meduza:
Last build is running great :) Deathly Adiutor is saving it's settings and GPU can even be overclock :) (or maybe I haven't noticed that before... ).

Camera and galerie came back, they disappeared when I flashed test2.

m.
[Galaxy Tab S Android Development] DBCAB:
IKR that facebook app is battery sucker from hell I always use the browser to look when and if I do at facebook, totally agree about that app.
[Galaxy Tab S Android Development] koimr:
I'm rooted, using SuperSU 2.79 (latest stable). I've done nothing in the way of optimizing, even using the official notoriously-battery-eating Facebook app. According to BBS I lost 4% overnight over seven hours so standby time is great. I bought my Tab S in early 2015 so it's certainly not a new-ish battery either.

If you are having issues, definitely install BBS (Better Battery Stats) and see what's eating up your battery.
[Galaxy Tab S Android Development] amateurhack:
Like many things, it's a matter of preference. I like SuperSU, and since I've invested in the Pro upgrade, I feel even more strongly compelled to use it. But for others, I'm sure that having the convenience of not having to flash another app is appreciated.
[Galaxy Tab S Android Development] tebra:
Thanks for the update. Dirty install last version on my T-700. Now Deathly Adiutor is missing and still have hardware buttons bug ?
[Galaxy Tab S Android Development] koimr:
For the hardware buttons, are you wanting the buttons completely disabled (other than Home) or just the backlights off?
[Galaxy Tab S Android Development] amateurhack:
In the new build, I still get a system ui force close when switching back to my main account from a restricted account. I have not had any browser crashes, however.

On an aesthetic note: I preferred the boot animation of the previous build. Simpler is better, less is more, and all that.
[Galaxy Tab S Android Development] amateurhack:
And the hangouts big is still there. [crickets]
[Galaxy Tab S Android Development] deadman96385:
Can you explain what bug you mean? I must of missed when you first talked about it sorry.

Can you post a log of that systemui force close please.
[Galaxy Tab S Android Development] greeg32:
Force close of hangouts when typing an SMS (Google voice integrated on the t700) it's been happening since cm13. Thanks in advance for any help.
[Galaxy Tab S Android Development] johnseidel:
Clean flashed on T800 using TWRP 3.0.2.0

Flashed gapps mini.

Using Nova Launcher.

No problem with youtube or other videos.

No problem with widgets.

Downloaded a few apps.All but one ran ok.

Last Pass launched but hung at the logo screen. The back button had no response. The Recent Apps button finaly let me close it. Uninstalling/reinstalling and reboting had no effect. The same thing happens on RR 7.1.1.

Last Pass runs fine on my old Galaxy S3 phone running CM 14.1.

If Last Pass had worked I would have considered using Lineage for my daily driver. I will continue testing nightlies to see if the last pass problem is resolved. Until then I am back to RR 6 for my dd.

Overall very excited and looking forward to this roms development
[Galaxy Tab S Android Development] tebra:
I want to completely disable them. It works until the device go to sleep and wake-up.
[Galaxy Tab S Android Development] amateurhack:
The hangouts bug goes back to CM14. We know it was also present in builds for the Nexus 7, so it's an upstream issue. Basically, when you open Hangouts and try to type in an sms message, it will crash upon touching the first character. I tried looking into how we might get someone who actually works on lineage to look at it, but other than a becoming a dev and signing up to work on the gerritt, I didn't find anything.

I'm not sure about the bug report for the other issue. Since the restricted account doesn't have access to developer options, in not sure that taking the report after the fact would help. I will try to figure it out. Maybe, since I have Super SU, I could grant root access to that account and then use another app to take the bug report? If you have any ideas on how to do that, let me know. I will try tomorrow.

Thanks for your help on this ROM. It's off to a great start!
[Galaxy Tab S Android Development] physwizz:
Thanks for the great ROM. It's the only nougat ROM I've been able to flash as a secondary extSD ROM using dual boot patcher.

All working well now. Finally managed to flash superSU 2.79
[Galaxy Tab S Android Development] razholio:
That's odd, as I just opened an old Google voice SMS conversation and typed in and sent a message without any trouble.

EDIT: I see it now, only happens on opening a new SMS conversation.
[Galaxy Tab S Android Development] chibot75:
Just installed on T700 with nano GAPPS and supersu. Rebooted and now just stuck at the lineage logo. Anyone else have the same issue?
[Galaxy Tab S Android Development] razholio:
No, but how long did you wait? Supersu can take a couple reboots. I wiped system after factory reset then flashed rom, supersu and then stock gapps. It took a few mins, but booted up fine.
[Galaxy Tab S Android Development] chibot75:
Been almost 20 minutes. I can't even turn it off to boot back into TWRP
[Galaxy Tab S Android Development] Mtotallywired:
Just a quick update: so after clean flash last nite, (wiped everything: data, dalvik, cache, internal, system) with latest pico gapps, flash supersu 2.79 stable ver.

charged to 100% before unplug and kept everything stock except for changing a few settings like turning off all google sync/backup, set wifi off when sleep except for when plugged in, Battery optimization is set to automatic and balanced profile, and activated advanced power menu (for reboot to recovery option) in dev options. I've installed no apps (not even BBS until now) so facebook or maps we can rule out as the culprits.

I used it for about 45 min which drained 11% with 30% screen brightness and wifi on. left it on standby for about 8 hours and it had drained over 15% down to 74%. Left it again all day today without touching it. and it was basically drained down to 50%. I know I haven't done a complete battery cycle yet but is this what you guys experienced?

I took screenshots of nougat battery stats:

See the first where I have a solid red "cellular network signal" bar. What does that mean? Is my tab searching nonstop for a cell signal?

Second screen shot shows: screen took up 4%, browser 3%, Tablet idle 2%, Android os 1%, Android system 1%. That's only 11% usage. basically what I had used in that 45 minutes of actually playing with the thing. What happened to the other 40%??

Anyway, sorry to belabor this. Just hoping for some potential insight as I've never experienced this on the tablet until the Nougat Roms (was doing this on schisu's 7.0 and his successor's build too, although seems even more pronounced on stock lineage without greenify or anything else running). Does the battery need to be recalibrated? even if I wiped internal before flashing (meaning, do batterystats get wiped too if I do that?) Thanks again and in advance for all your insights as I am beyond stumped with this one.
[Galaxy Tab S Android Development] amateurhack:
Mine crashes on any SMS, even old ones. But it has been reported that it works as expected on hangouts conversations. I never use hangouts conversations, only SMS/Google Voice, so I can't test this.
[Galaxy Tab S Android Development] steamrollerpark:
This Rom is great, everything works!
[Galaxy Tab S Android Development] chibot75:
Looks like I'm the first one to brick it whilst installing!
[Galaxy Tab S Android Development] dschulz72:
another brick...

I'm the second one... after dirty flash of last update, startup is stuck in the animated boot logo of Lineage. Even after 8 hours. I was able to restart to download mode, but not to recovery. Will try to reinstall recovery tomorrow and start fresh, perhaps that helps.
[Galaxy Tab S Android Development] swazau:
I think I will clean install build 2, Im getting screen freezes and reboots randomly
[Galaxy Tab S Android Development] physwizz:
I had this issue with SuperSU 2.5

---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------

Hold down on/off + vol up + vol down + home till it goes black then let go of vol down. It will boot into recovery
[Galaxy Tab S Android Development] dschulz72:
Hi physwizz,

just read your hints, after several tries you hint worked, I'm back in recovery.

Thanksa lot man!
[Galaxy Tab S Android Development] chibot75:
You're my hero!
[Galaxy Tab S Android Development] stedmakr:
Another thanks for physwizz!!! I had the exact same issue, softbricked after attempting to install SU 2.5 to the latest build and not being able to turn the tab S off or boot to recovery. The key sequence, "Hold down on/off + vol up + vol down + home till it goes black then let go of vol down" and I was able to successfully reinstall stock.

Thanks again
[Galaxy Tab S Android Development] Paulicat:
GPS is working fine for me on T700:

Screenshot
[Galaxy Tab S Android Development] deadman96385:
Why in the world are you using SuperSU 2.5 the latest version is 2.79 which i know for a fact works https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
[Galaxy Tab S Android Development] koimr:
All right, this is at your own risk (standard disclaimer). You WILL need to be rooted and this is what worked on my T700.

Use a text editor to edit the file /system/usr/keylayout/sec_touchkey.kl

(There is also a sec_touchscreen.kl file there as well with the same entries - do NOT change this one, just the one above!)

There should be two entries in this file - put a # in front of each line, this will "comment out" these entries. It should look like this:

#key 158 BACK_VIRTUAL

#key 254 APP_SWITCH VIRTUAL

Save the file and reboot, this will effectively disable the hardware "Recent" and "Back" keys.

If you re-flash (fresh or dirty) you will need to repeat the above!

For the illumination/backlight however, I have always had an issue (with every ROM except full stock) where the capacitive lights will still come on even after disabling the keys themselves (as per above) after a reboot. After every reboot I have to go to the Buttons settings and re-enable and then disable the illumination and then they will stay off until the next reboot:

Settings->Buttons->Enable on-screen nav bar (turn off)

Backlight->Illuminate buttons (enable then disable)->Ok

Enable on-screen nav bar (turn back on)

Good luck, I hope the above works for you too!
[Galaxy Tab S Android Development] amateurhack:
I can't figure out getting a bug report on the system u.i. crash. There didn't seem to be any way of starting a bug report in a restricted profile. I can take one right after I change users, but I have to clear the pop up, and system u.I. immediately restarts before I can start the report. If that bug report wool be helpful, I can post it.