yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] Brigham999:
the 1st May build is turning into a bit of a nightmare, to be honest. Did a clean install, then realised my last nandroid backup was in January (!!). Also got the setup wizard crash so having to get the latest Gapps to see if that solves it. Maybe getting to old for all this :)

Update:

It was Gapps. All good now. Just got spend an eternity downloading and configuring apps. That'll teach me!!
[Galaxy Tab S Android Development] DarkExistence:
Each device has a different kernel, there isn't one set lineage kernel. But yes, this is the official one for our device, and the op links you to that download page on lineage.
[Galaxy Tab S Android Development] DarkExistence:
No new build, wrong thread. My bad, sorry haha
[Galaxy Tab S Android Development] jrock60:
Great ROM, loving it! I was curious, is it possible to add the new Pixel C recent app previews to to this ROM?
[Galaxy Tab S Android Development] Dreamdancer.6666:
I can't find the new built

Gesendet von meinem SM-T800 mit Tapatalk
[Galaxy Tab S Android Development] Jors55:
update?

Thank you! Please posted the file. I can not wait ?
[Galaxy Tab S Android Development] DarkExistence:
Yeah, wrong thread lol. Was meant for AICP. Lineage build is tomorrow, sorry haha
[Galaxy Tab S Android Development] Barracuda77777:
Happened to me as well, so I made my own build with the capacitive buttons hardware disabled for good :)

if its okay with Dark, I can post a link to the kernel that you will have to flash, that will disable the capacitive buttons for good.

if I can't post a link, you can pm me and I will give you a link to the kernel.

also I noticed the buildprop still referenced T805 instead of T800, and there are still some overlays related to T805 which I took out from my build.

I would like to thank [MENTION=6663552]DarkExistence[/MENTION] for his excellent work on this rom, it's amazing how the open source community work. Thank you
[Galaxy Tab S Android Development] lurgainn:
First of all, thanks to DE and the team for this wonderful rom. I installed the last build and I wish to report two possible bugs about the hardware keys that I prefer to use:

whenever I touch the screen, the hardware keys they light up like I touched them;

the first time that I tried to disable them but immediately after then I re-enabled them, my tablet crashed and rebooted.

Sorry for my poor english and thanks again
[Galaxy Tab S Android Development] gserp4sox:
+1
[Galaxy Tab S Android Development] DarkExistence:
You can post the link, but the minute a different kernel is flashed all support from me will be dropped as the OP says.

Thanks for that! We based chagallwifi on chagallte tree and took out RIL, so theres still some SM-T805 stuff mixed in. Thanks!
[Galaxy Tab S Android Development] DarkExistence:
From this build onwards OTA should be working, however you do need to install the latest TWRP build from here as it adds support for Lineage OTA updates!

Please read post #3 also

Thanks
[Galaxy Tab S Android Development] _RoRo_:
Hey darkexistence. Thank you very much for your work. I see improvement here and there in every build. I have a question regarding TWRP. I am using this one at the moment: https://xdaforums.com/showthread.php?t=3074633

To install the new official one, do I have to just use Odin as usual and it overwrites the old TWRP, or is there a different procedure?
[Galaxy Tab S Android Development] DarkExistence:
You can flash the new twrp in twrp. Just press the view img button when you press install, choose the twrp build and select recovery
[Galaxy Tab S Android Development] ElsaReyes:
Hey DarkExistence quick question. Under downloads on the first page, the Kernel and Device Tree links. Do I need to install those as well? I've never been able to figure out if I am or not and if I am that might explain the odd little problems I get that others don't seem to.
[Galaxy Tab S Android Development] DarkExistence:
No, thats just what is used to build the software.
[Galaxy Tab S Android Development] rspaulo:
I´m having problems to install any build after dec/2016. Instaled de MM bootloader via Odin, instaled TWRP 3.1 via TWRP, wiped everything (sometimes even internal storage), installed the rom, beans gapps, wiped cache and stucks on LOS boot logo.
[Galaxy Tab S Android Development] oceansoul:
upgrade from stock 6.0.1 with touchwiz, this rom feels really sluggish compared the stock to me, is that normal?
[Galaxy Tab S Android Development] Mark7A:
Error 7 - Incompatible data

Thanks to DE and all the helpers here!

I am trying to upgrade from an older Cyanogen rom.

I have updated TWRP to 3.1.0-1.

I think I flashed the bootloader correctly (the ODIN image on page one was missing). Factory resetted

When I boot into the bootloader (TWRP) and flash the new Lineage ROM, I get an Error 7 - (Cannot install this package on top of incompatible data)

What am I doing wrong?

---------- Post added at 10:49 PM ---------- Previous post was at 10:30 PM ----------

I didn't do the proper wipes. All is well except for a message at the top that says:

Kernel is not SEANDROID Enforcing

What is the cause of this?
[Galaxy Tab S Android Development] rspaulo:
Hi, I´ve solved my problem. I changed the cache file system from F2FS to ext4 and worked.
[Galaxy Tab S Android Development] pmgnet:
Also you can flash this with official twrp manager.
[Galaxy Tab S Android Development] kaodd:
could be a nuclear disaster LOL

all good, it's normal, turns from red to blue.
[Galaxy Tab S Android Development] kogone:
Can you link the commit to do this?
[Galaxy Tab S Android Development] Barracuda77777:
You can find the commit here

Although I noticed that Dark have updated the kernel so I have not tested it with the changes.

you can find the compiled original kernel with capacitive buttons enabled and the one with the capacitive buttons disabled HERE

I have been using the tablet for over a week without a single problem.

you can easily use flashify to try it and then if not happy re flash original kernel.

Cheers
[Galaxy Tab S Android Development] DarkExistence:
[MENTION=4193974]Barracuda77777[/MENTION] feel free to push the button commit to the exynos5420 gerrit. We can review it then and decide if we will implement it or not into our Lineage Repos etc. https://review.exynos5420.com/# :)
[Galaxy Tab S Android Development] _RoRo_:
It's faster on mine, except on a couple app. Google play games is a bit more sluggish. All my games run just as before except SimCity buildit, which seems a bit sluggish. But it feels like it's running at higher resolution in lineage is than in stock. Icons are smaller.

I also notice embedded Twitter messages and videos you can find in news app (like the Huffington Post app) tend to make app crash
[Galaxy Tab S Android Development] Mark7A:
Scary!

So far so good. The google Play Store frequently (every few minutes) stops/closes. I used the BeansGapps recommended in the OP.

Any remedy for this?
[Galaxy Tab S Android Development] breaker_evert:
My ota updates do not. I installed the bootloader listed in the 2 post and installed the new TWRP via the TWRP app.

During the update, I get the message that he can not open in recovery.

I now have lineage-14.1-20170501 but updating via ota does not work with me.

What am I doing wrong?
[Galaxy Tab S Android Development] lurgainn:
With the last build 20170508 (BeansGapps 20170415 and TWRP 3.1.0-1) I confirm that the first bug is still present: whenever I touch the screen the hardware keys light up.

Thanks again for this wonderful ROM :good:.
[Galaxy Tab S Android Development] ElsaReyes:
I seem to of encountered a bug I don't see mentioned, but whenever I try to open up the youtube app, it immediately crashes.
[Galaxy Tab S Android Development] DarkExistence:
After speaking with the team, this isn't a fix. TC300K is chagallwifi, chagallte's driver, and Cypress is for klimtwifi, klimtlte etc. So you are basically disabling the whole chagall driver so the buttons do not work at all, which is not good, and you are enabling the klimt driver which is incompatible, also not good :)
[Galaxy Tab S Android Development] Barracuda77777:
Hi Dark,

I am fully aware of this, the reason I do this so the kernel compiles, I never claimed it's a fix, I did state in my initial post that this

hardware

disables capacitive buttons by taking out the correct driver and putting the wrong one. I hate capacitive buttons with passion, this goes back all the way from me and invertigo first ported CM11 to Chagall, the issue always was that software capacitive disabling the buttons never fully worked.

cheers
[Galaxy Tab S Android Development] DarkExistence:
Yep sadly software buttons are really awkward for Chagall, keeps crashing and force rebooting the system. But enabling the cypress driver for chagallwifi isn't something that is very good but you can use it if you like until we find a proper fix, hopefully soon.
[Galaxy Tab S Android Development] Barracuda77777:
Dark,

the kernel also have many more drivers that sit idly unless called upon, its how Linux works which android is based on, the Cypress driver was included by me so the kernel compiles, when the tablet is running the Cypress driver will not run or load as there is no hardware for it to run on, Android software will add the software Nav keys automatically as it does not detect the capacitor buttons.

by flashing the original kernel containing the correct driver everything will work again with no harm done.

this is why I think this fix will only be beneficial to someone who will not want to use the capacitive keys at all, as it's a pain to keep flashing between kernels to enable or disable the keys.

I have a 2 year old daughter that uses the tablet, with capacitive keys it's unusable for her as she keeps touching the sides of the tablet the way she does on her iPad.

I would like to congratulate and thank you again for this rom, it breathed new life into the tablet, up until a week ago I was still running my original CM11 port.

cheers
[Galaxy Tab S Android Development] DarkExistence:
Yep I know how kernels work, don't worry haha :) (this isn't meant to sound sarcastic btw) :p

I am glad you are providing a link back to the original one though, thanks.

Also cm11? Wat, how did you live with that? O.o
[Galaxy Tab S Android Development] eekiemaster:
sd card issue

Hi, I installed the	lineage-14.1-20170508-nightly-chagallwifi-signed. Get problems to install app data on the external SD card. I formatted it in the device (becomes fat32), also formatted it in PC (extFAT), latest format in the tab S 10.5 wifi (fat32). When using X-plore or other browser I can go to all folders on the External SD card except for the Android folder. I see no entry's there. But there is data in it because browsing via root-->storage--><nameofSDcard>-->Android I see all other folders below data. Some applications have issues, for instance TomTom. When enabling the External SD card than the app will istall but after initializing it gives an error about storage full and no write access. When ejecting the external SD card tomtom will install but the maps are downloaded to internal memory after inserting (mounting again) the external SDcard. Apps do have difficulties. The external SD card is not formatted as internal memory but traditional (for photos etc). THis is unexpected and was no problem on my previous 14.1 rom (lineage-14.1-20170117-UNOFFICIAL-chagallwifi).

Before install I errased everything including format of internal memory.

Any idea what may be the isue? Bug or is it by design of android 7.1.2? Thanks.
[Galaxy Tab S Android Development] ElsaReyes:
Quick update on the youtube issue. If I click subscriptions fast enough the app doesn't crash. But just letting it load up normally it crashes every time.
[Galaxy Tab S Android Development] DarkExistence:
Did you try clean flashing, because your the first report of this.
[Galaxy Tab S Android Development] :
What is the changelog of the last update please ? [MENTION=6663552]DarkExistence[/MENTION]
[Galaxy Tab S Android Development] DarkExistence:
press the chagallwifi download link in the op and then press changelog
[Galaxy Tab S Android Development] robhug:
That's great, on the latest build (in general, since approximately the official builds, but getting better every weeks ) it's really smooth and responsive, mostly animations are really smooth now and not "jerky or stuttering" like before (don't know how to say in English but I mean before some system animations were a little bit laggy , for example we see the begging and the end of the animation only , like a fast animation in 5fps) and now apps opening and loading very quickly when launching, and battery has improved as well.

No bugs or lags noticed until now. Thanks a lot

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

I use the LOS changelog app on play store, give everything we need , notification when new build available and changes are made, etc... If I can interests someone (it's free)
[Galaxy Tab S Android Development] abushami:
Viper4android work on this rom or not ?
[Galaxy Tab S Android Development] DarkExistence:
Have any of you guys been facing the issue where the device totally freezes, and needs to force reboot? I've had reports of it on AICP, but not lineage, and have on lineage for klimtwifi, but not aicp.
[Galaxy Tab S Android Development] robhug:
I have this one or two times in lineage but back in the first builds , nothing like that in the latest ones. (Until now :) )

And I have just a little question , since I use aosp (so since ever ) I don't know if it's normal that it takes so long in boot logo (splash screen) when booting up and even worst when booting to twrp, it can stay 10-20 sec in the boot logo before twrp come . On all my other devices (s5, s7, tab pro) its more "normal" , like 3-4 sec on boot logo
[Galaxy Tab S Android Development] John_Br:
Looks 'normal' because i experience the same ;)

i dont know since when but it wasnt always like this.

Grtz,

John
[Galaxy Tab S Android Development] meduza:
That issue was in all of the 3 ROMs?

m.
[Galaxy Tab S Android Development] pnomandk:
Sounds great, thanks! Was this mainly just a sync with upstream or did you change other things (like fixing the missing GPS libraries in some ways)?

- Per.
[Galaxy Tab S Android Development] DarkExistence:
Nope just lineage, building conflicts lol.
[Galaxy Tab S Android Development] DarkExistence:
Yes GPS is fixed and working
[Galaxy Tab S Android Development] pnomandk:
Great -- makes it easier to update then!

Was considering making a zip just to flash on top with the two missing libs I found missing, but this is much easier then :)

Thanks!
[Galaxy Tab S Android Development] DarkExistence:
new build posed.GPS fixed + general bug fixes
[Galaxy Tab S Android Development] chibot75:
[MENTION=6663552]DarkExistence[/MENTION]

Howdy. Are you able to assist with the T700 builds/updates? The OP there is currently offline and made his work available for someone to take over

https://xdaforums.com/galaxy-tab-s/...geos-14-1-sm-t700-t800-coming-t3535159/page37

Thanks in advance
[Galaxy Tab S Android Development] aegeuss:
Thanks for this great rom. I am coming from ReSurrection after learning that I have to install from scratch for the new theme engine; bad news for me since I had set up my device, installed many apps and tweaked them and looking for bug fix updates; it's ok, this is a development thread here :) No one is complaining; I think we should thank you for keeping this device after a long time. Anyway. I have come accross these small problems.

1. I think root is not implemented now. So, I will have to install it from here: https://download.lineageos.org/extras I am not after tricks but adaway requests the root; so I have to. Anything we should be aware of?

Edit: root option in the developer settings is limited to adb now. it does not include applications. Chrome is very hard and slow to use in ad mode.

2. I use original physical bluetooth keyboard EJ-CT800 without a problem in ReSurrection rom from the first install for Turkish characters. However, LineageOS and default GKeyboard does not recognise Turkish characters in the keyboard; then I insall my belowed Swype keyboard and choose it, suddenly physical keyboard starts to write Turkish characters :) ReSurrection rom does not have this kind of a problem.

Edit 2: After reboot, shift key does not work now :) I was trying to change the language to Turkish in first setup when settings restore crashed. May be there's something wrong in language and/or regional settings. ReSurrection Rom does not have any of these problems.

3. I am coming from clean flash with factory reset. Settings crashed right after I have set up wi fi hotspot at the beginning. So I could not restore my apps and setting automatically. I think it needs some polishing.

What I want from this rom is stability and constant automated updates in a cyanogen fashion. I try other roms for fancy stuff, this rom is for serious business. Did I tell you that I run most of my business over this rom and tablet abroad by using Gmail - Google Drive - GDocs? That's why I love you :)

Regards.
[Galaxy Tab S Android Development] meduza:
How about substratum guys? I'm not able to install themes but I wss on previous build... .

m.

---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------

I'm always flashing chainfire `s supersu directly after ROM, never got any problems by doing so.

m.
[Galaxy Tab S Android Development] 3DSammy:
I am having no problems with Substratum including it auto updating the applied theme but I read in the previous LinageOS 14.1 thread that Substratum: "You need to do it in a clean install to make sure the frameworks install correctly". I roughly followed that advise (clean ROM and nano Gapps flash, rebooted then rebooted to recovery, flashed Supersu, (updated Supersu pro which I had purchased) which reboots again, installed substratum and started it, granted root and it sets up those frameworks (I assume). I then installed a theme (Spectrum from Playstore). Downloaded and installed themable Gapps from Team BlackOut then (requires a reboot) finally applied the Spectrum theme it using Substratum manager and rebooted to a themed UI.
[Galaxy Tab S Android Development] meduza:
... hmm ... the February build, is actually a clean install ...

I just went back to the backup of the January build ( once dirty) with substratum working and I will flash the ROM update from here dirty... . Of course I've a backup of the clean install :)

m.
[Galaxy Tab S Android Development] 3DSammy:
As I wrote before I've had less than ideal battery performance compared to the AOSP Nougat ROM. After [MENTION=4662107]meduza2[/MENTION] suggested using Deathly Auditor to modify the battery settings I've experimented with said settings until I found enough improvements to make this ROM my T800's daily driver. I could tweak the battery settings for a while longer but I don't see the point unless something changes. I attached my current settings (screenshot) from Deathly Auditor below but they're just a slice in time.

My goals as previous stated:

1. No loss of battery percentage while the screen on and charger attached

- I've not been able to achieve this goal but it drains so slowly that I don't feel it's an issue any longer

2. A faster rate of re-charge when the screen is off

- This issue is resolved with the changes to the settings

3. A faster rate of re-charge when the unit is powered down

- This issue is also resolved with little to no difference between this and my previous ROM.

During my battery testing I noticed, through BetterBatteryStats+, that this ROM goes into deep sleep as well as any other ROM. There is no indication of rouge wakelocks or processes using excessive battery.

On a completely different topic, it appears [MENTION=794682]aegeuss[/MENTION] can pick an alternate keyboard (SwiftKey) and does not get the hard reboot I always get. It leads me to ask [MENTION=6663552]DarkExistence[/MENTION] if the lastkmsg.log I posted gave you any clues to the issue I've experienced when trying the change keyboards setting? Assuming the next release does not resolve the issue and the lastkmsg.log did not help is there any other information I can supply?

On the topic of bluetooth keyboards I own a Perixx Periduo-880 KT-1332 bluetooth keyboard which includes a mouse pad. I've successfully paired this keyboard and both the mouse pad and the keyboard work as expected.

Thanks for all your hard work.
[Galaxy Tab S Android Development] meduza:
success

Method worked :) Themes, kill app with back button, security settings, everything works like it should.

Only think left for me is deathly auditor not saying it`s settings. I will try to reinstall it... .

m.
[Galaxy Tab S Android Development] aegeuss:
I have installed Swype, am not using Swiftkey, I don't know if it would make a difference. Thanks for your opinions. My exact problem is about the Turkish characters; choosing different character set; otherwise bluetooth keyboard is fully recognised and connected. Now people say on RR thread that, dirty flash works with subratum, whatsoever; I had taken a backup; now am planning to take a backup of this rom, restore and update the other one and see what's going on :)

Regards.
[Galaxy Tab S Android Development] 3DSammy:
As an update build for the ROM will be available soon, is there anything I need to set up for post ROM flash files such as nano Gapps, SuperSU ... etc? With the AOSP Nougat ROM you put those flash tiles in a directory called /sdcard/OpenDelta/FlashAfterUpdate so is there anything similar for LineageOS?
[Galaxy Tab S Android Development] DarkExistence:
Keyboard issues are not happening on my RR builds nor my LD builds, so I am pinning it down to an issue which will be fixed upstream by the actual LineageOS team.
[Galaxy Tab S Android Development] meduza:
... I'm using Swype and have no problems.

m.
[Galaxy Tab S Android Development] 3DSammy:
Thanks for your input. I installed he Swype trial and went through the set up including a reboot then tried to change to Swype and had the same forced reboot I've had with both Swiftkey and Hackers keyboard alternatives. I took a nandroid backup then disabled the AOSP keyboard (using settings), rebooted with only the SwiftKey as an alternative.

Unfortunately Google voice was substituted and when trying to switch keyboards caused the same forced reboot issue. I figured I was stuck.

After the forced reboot I re-enabled the AOSP keyboard in settings and rebooted then went to test that the AOSP keyboard was working. Low and behold SwiftKey popped up as the keyboard. I never once got as far as changing the keyboard to SwiftKey. I'm happy but totally confused. Guess I'll wait to see if applying the next update build messes that up :D

Thanks again.
[Galaxy Tab S Android Development] aegeuss:
I am back to RR now, everything is in order :) I think there's a problem for that in LineageOS. DarkExistence says the other rom is the most stable for exynos; I'll try that later when I have more time; let's spoil ourselves in the dawn of Tab S3 :) Thanks to DarkExistence!
[Galaxy Tab S Android Development] meduza:
Battery drain

How is the battery for you guys? I had about 3%/h during the night that's definitely much to high. 0.1% - 0.3 % is norml... .

m.
[Galaxy Tab S Android Development] robhug:
Not a big deal but still strange

I always get stressed at the beginning, I thought it was boot looping or soft brick ^^
[Galaxy Tab S Android Development] rookie12:
Lineage os and aokp freezes but not as much as aicp

They freeze once in awhile then it goes away but aicp its very often sometimes 2 3 times in a row

Talking about T700 BTW
[Galaxy Tab S Android Development] johnhwyman:
Yes, I have had 2 hard freezes with this build, none in the past builds.
[Galaxy Tab S Android Development] amit_sen:
Yes I have had freeze with aicp-T700 everytime after using the tab for 20-30 mins.

I'm not on the very latest update though.

I'm on 1st build of May2017