yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Thats good to know...than for me everything is allright :)

I got the same with my Nexus 10 and the ROM "Pure Nexus"....there I also have to flash SuperSU as ZIP via Recovery.

---------- Post added at 10:05 PM ---------- Previous post was at 09:58 PM ----------

OK - LineageOS doesnt will bring a ROM including root...

So for root access (not via the developer options, but via SuperSU) I did flash via the TWRP Recovery

(after the wipe of cache&dalvik cache):

- lineage-14.1-20170124-UNOFFICIAL-v2awifi.zip

- Open GApps ARM 7.1 pico

- the actual SuperSU 2.79 as .ZIP from http://www.supersu.com/download

( https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip )

Now my SMT-900 is working with root like my Nexus 10 with "Pure Nexus"-ROM and SuperSU (flashed via Recovery)

PS: I also got the unsized Background-Image at the lock-screen.....the normal Wallpaper I did get working.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=5230113]killerjay[/MENTION]

I would be interested in seeing the log file, can you get the last kms log please when it happens next, I would love to see if the issue is caused by DOZE, I am having the ocassional freeze or lockup from time to time, and I think it is related to DOZE from what I can gather from the logs.

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] killerjay:
I would love to, but im not sure how to give you that info.. how would i get the last kms log for you?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Hey Guys,

I know it has been awhile since I have personally posted an updated. Life has been super busy for me. Working 60 hours a week, wrapping up this job, starting a new job and moving. Don't get me wrong, I ready everyone of your posts and work with [MENTION=7694560]DGT79[/MENTION] on posting solutions, looking at logs, and making this ROM better.

With the Exynos5420 Team having a build server "Jenkins", I will no longer being announcing builds. We are working on setting a final scheduling on builds but it is looking like weekly builds on Fridays. This week, we will run builds tomorrow due to Jenkins going down for some maintenance. You can find device changes on the Exynos5420's GitHub account. We are working on a change log server but that is a few months out. If you have any questions, about this please let me know.

So a new hot topic item is root. A lot of ROM teams are moving away from baking in root (no longer having the SU binary installed) into the ROM. There is multiple reasons behind this. Some apps just will not flat out work if it detects any form of the SU binary installed. For an example Pokemon Go or TV streaming apps. Also there is concern of identity theft with the SU binary being enabled. We, as a team (Exynos5420 Team), have decided to follow this path. It should be up to the user for this risk. It is easy for you to install the SU binary if you want it though. You just need to flash a root zip after flashing the ROM. From here, you can use whatever SU program you may want such as SuperSU. You can find the SU binaries here from Lineage. I will update OP to reflect this. You can find more information about why root was removed from the ROM here.

Another thing that you may have noticed on the downloads site is there is a new ROM the Exynos5420 team is developing. It is called LiquidDeathOS. It is a ROM based off of the Exynos SOC. We have plans to expand it to all Exynos SOCs in the future. We have a few builds out for Alpha testing and it is looking promising. It is very early in development and has a lot of bugs so please be patient. What we are trying to accomplish is to focus on speed, stability, and battery life. With this new ROM, we will be using AOSP code directly from Google. There will be no CAF code involved. (If you do not know what CAF is, please Google Code Aurora.) As soon as I feel comfortable releasing a build for public consumption I will. So hang in there. It is going to be fantastic and will blow Lineage out of the water.

I think that is all I have for right now for new updates. As always keep giving the great feedback and I will keep putting out the great work. Feel free to donate me a beer or two.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
SU-AddOn (ARM) : https://mirrorbits.lineageos.org/su/addonsu-arm-signed.zip

SU-AddOn-Remove (ARM) : https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip

( SM-T900 / v2awifi should be ARM and not ARM64 )

By now empty LiquidDeathOS-Folder for v2awifi: http://download.exynos5420.com/LiquidDeathOS/v2awifi/

and the "normal" folder - with ROMs - for LineageOS : http://download.exynos5420.com/LineageOS-14.1/v2awifi/

LiquidDeathOS Headquarter on Google+ : https://plus.google.com/communities/109863800475536262348

Exynos5420 - Homepage: http://www.exynos5420.com/

[MENTION=4817899]thompatry[/MENTION] : Do you know if that is a special kind of root on the LineageOS-Page?

Would it be better/more compatible as the SuperSU-ZIP?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] nickster1:
I am using supersu with no issues. Lineage probably doesn't promote it because it's not open source.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=4375661]nickster1[/MENTION]

That would be the reason :)

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dialbat:
wondering if audio levels were fixed in latest build or should we still use Deathly Auditor?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=613766]dialbat[/MENTION]

The Audio levels are now baked into the ROM, it took about 3 weeks of testing various levels in Deathly to get a reasonable effort in obtaining the right workable levels, however I will admit that it is nothing like stock, I cannot find a way to get a workable base level in there, and I dont think the developers have worked that out either.

I am fairly certain that Samsung have something in place to introduce a good base tone, I just wish we could reproduce this.

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] midimench:
SuperSU 2.79R3 works just fine with the Lineage rom. I've had no problems so far. Was there supposed to be a Liquid Death rom to download? I couldn't find the rom, only the folder. Also, will we have to do a full wipe (less SD Card) to install it?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] don123161:
I upgraded to the latest nightly dated 1/30/2017, but when I reboot it never finishes loading. It doesn't go into a bootloop, it just goes to a black screen and freezes. I do a cache and dalvic cache wipe before rebooting. Any thoughts?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=3070148]midimench[/MENTION]

Liquid is not ready yet, and when it is you will 100% need to do a full wipe to do the install, the two ROM's have a different base.

Liquid is still a bit of a way from being ready for public consumption though.

Cheers,

David.

---------- Post added at 07:52 PM ---------- Previous post was at 07:49 PM ----------

Hi [MENTION=5864734]don123161[/MENTION]

So this has been reported and I would suggest rolling back to a previous version.

Since it was moved over to weekly releases I no longer test them before they were released, I guess that is always the potential concerns when going down that path.

I am not in a hurry myself to always upgrade unless there is a specific need to do so, in this case I am waiting on confirmation from the dev team that the video scaling issue has been resolved, and I will do my upgrading then.

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Masayoshi Tadokoro:
I also freeze on a black screen.

I am looking forward to the next update.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] midimench:
I froze on the same January 30th update, which is why I always do a backup before moving forward, just in case this happens. Restoring everything back to the previous version takes 10 minutes, and I'm back in business.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
When ever working with any custom ROM's you should always and I mean always make a backup of your pervious working version, it is crazy not to do so, and since it is provided as part of TWRP it is a small task to get it done.

Just make sure you have ample space on your external storage for it, that is all that is of concern.

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
The latest one 20170204 boots but the autorotate is broken. Just FYI.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] magusberlin:
hey

big thanx also from my side for this rom. i am still on 20170123 that works great. installation was seamless if you really RTFM.

so, two noob questions:

before on 5.1.1. there was an option to directly log in if filled out the correct pin, now i also have to hit enter.

and, i cant connect my tablet over usb to my windows desktop to transfer data . where do i have to adjust settings? thx! keep on rockin!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] tryer2:
I changed the rom on my tablet from CM12.1 to this Lineage 14.1, the 20170124. I am quite happy with it. Thanks for all the work ! There is one thing to complain about: every day I read my newspaper on tablet. When I zoom in on the text, it takes more time to enlarge the text, sometimes one second or more. The CM 12.1 version ran more smoothly in this way. Maybe this can improved on later updates. My compliments for the makers of this ROM !
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
Did you try to change the scale settings in the developer options to .5 or less?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] tryer2:
Thans for help, but it die nog realy help

---------- Post added 8th February 2017 at 12:04 AM ---------- Previous post was 7th February 2017 at 11:30 PM ----------

It takes a second to get the text sharp
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] ianrobbie:
Just flashed the latest build and screen rotation doesn't seem to be working?

New build feels a lot faster, though. Amazing work!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=6246148]magusberlin[/MENTION]

Since version 6.X.X you cannot just directly connect the tablet/phone to the PC and have it work straight away, what you need to do is pull thenotification draw down, you will see a notification there that says "USB FOR CHARGING" click on that and change it to "FILE TRANSFER" and that should get it recognised by Windows once you do that.

NOTE: Sometimes you may have to do this a couple of times as Windows mayneed to install a totally new USB driver, it is not always the case but sometimes it is a requirement.

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikewong27:
If I want to upgrade my existing LineageOS to latest build, do I have to install from scratch and wipe my data? Or can I just upgrade it manually without wiping my data?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
I installed rotation control from the app store and it works. I like to use my tablet with the home button on the top so I use the reverse landscape to do that.

---------- Post added at 08:00 AM ---------- Previous post was at 07:57 AM ----------

You can just wipe dalvik and cache then install new build and supersu. I usually wipe the dalvik cache again then reboot. The two latest builds won't autoritate so I installed a rotation app from thebapp store to control the orientation.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] ugabuga:
I'm on an old stock 4.2 rom and debating about pulling the trigger and upgrading. Quick question, is there any way to keep or add back the Samsing 4 window multi-tasking? Also, has anyone tested and confirmed the Samsung bt keyboard cover and S mouse both work?

Anyway to get double tap to wake to work?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=1090873]ugabuga[/MENTION]

Lets see if we can answer some of the questions :)

1. Firstly you will need to update your tablet to the very latest stock rom, which should be either 5.1.1 or 5.1.2 depedning on your region, you should be able to do that manually by going to SAM MOBILE and downloading it from there. Doing that will also update your bootloader to the correct one, without that you will need to do a manual boot loader update which can be a real pain to do

2. You will loose any and all Samsung TouchWiz features, anything related to the S-PEN, Windowed multi-tasking and other features that are baked into TouchWiz. For many of us we could live with that given that the upgrade to Nougat refreshes the tablet quite considerably, so there is a trade-off. However, in saying that, Nougat has its own multi-tasking window system, it works but not the same way as the Samsung one does, and you can do it with two windows not 4, and you can download an application called CM S-PEN from the pay store to help provide you some features for your S-PEN, but no matter what you wont get the bubble pop-up window when you extract the pen anymore

3. I use the Samsung keyboard (The official clam shell one) and it works really well, however, you need to be aware that about 3 keys do not work and you have to get used to that because they never will, the one that might annoy yout he most is the multi-task key which brings up all your recent windows. But, as I quickly learnt, the one on the tablet sits right above it and it is just as easy to click on it so I got used to doing that :)

4. The Samsung Action mouse I have works great, though I dont have the S-Mouse so I cannot confirm, but I suspect it will work but it will loose any and all special features surrounding it, as it will most likely have all that baked into TouchWiz

If you can live with the above, then you will find your tablet getting a whole new lease on life, but be warned that some cannot and end up reflashing the stock ROM back onto their device as they have become too accustomed to the Samsung TouchWiz features.

Remember to go to SAMMOBILE and download the very latest official ROM, this way you can also go back to the original one if things are not what you want, and it is fairly easy to do that via ODIN.

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] wargear:
Hello! Before anything else Thanks for the time effort and hours spent bringing this ROM to the community! I'd given up and moved on to other things due to the Exynos 5420 compile issues for Slim and Liquid ROM and so haven't been here for some time. I saw a number of posts regarding the 5.1.1 bootloader failing to install properly via ODIN. You MUST use the Power/Volume key down method to get into download mode no other method will work properly! I use and recommend an app called Deviceinfo from the store to check and note the bootloader version before and after flashing. Also, I suggest as always backup everything possible and make copies to your computer and SDcard before starting! Having an older version of TWRP in .tar format in case things get rocky it can make an older nandroid easier to restore.. (Why do I know that?? LOL!) Thanks again to everyone involved in getting this beast of a tablet back in the fast lane!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] nickster1:
Wow you have the Samsung keyboard working. How did you go about doing that? I've tried a few different ideas & unfortunately none of them worked.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] netjetman:
2/11 build

Has anyone tried it yet?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=4375661]nickster1[/MENTION]

Yeah it should work without any issues, in fact I have connected about 4 different Bluetooth keyboards and they all connected perfectly fine.

What type of Keyboard is it? Can you show a picture of it??

What issues are you having???

Cheers,

David.

---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------

Hi [MENTION=533378]netjetman[/MENTION]

Has anyone tried what exactly?

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
Love the latest build. Only negative is auto rotate not working. Yes I downloaded a rotation control app to get around it but not a fan of doing that.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] nickster1:
Well somehow my eyes skipped over the fact you guys were talking about a Bluetooth keyboard lol. I was thinking you somehow got the stock touchwhiz keyboard to work on the tablet.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] DGT79:
Hi [MENTION=4375661]nickster1[/MENTION]

LOL OK I got it now :)

Yeah I have tried to install the Samsung Virtual (On-Screen) keyboard and it would not install, I think it must check and see if TouchWiz is installed or not as it kept on failing.

However I have gotten used to the default Google one :)

Cheers,

David.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
My favorite onscreen keyboard for tablet is the Thumb Keyboard by Beansoft. I can't normal reach the letters I the center but this puts the keypad down the center.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] netjetman:
Sorry, had put the 2/11 build in the title, but I guess it doesn't show. It sounds like that build still has autorotate issues.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
The rotation now works for me on today's release.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
The rotation works within app but not when at home screen for me.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
I use Nova and it rotates on it. A little slow to read the change but it does work.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
I also use nova and was in it and counted to 10 to 15 and no rotation.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] scottlott:
System Won't Load..

Hey Guys,

Having an issue with this rom and the Lineage OS 13 on my T900.

When I flash the rom it boots into Android and shows the fullscreen Lineage logo with a white background and nothing else. I can see only the battery icon in the top right, hitting the volume buttons adjusts the volume and if I hold down the power button I get the Android power off dialogue. This is the extent I can interact with the tablet, swiping or touching the screen has no affect and the buttons at the bottom of the screen only cause the device to vibrate; they have no other affect.

The device doesn't go into any kind of setup wizard, it just boots the logo and stays there.

I have tried at least three times now to completely clear the device in TWRP, flash it with the rom and ONLY the rom, then reboot. The same affect every time. I've also tried flashing the special bootloader before and after flashing the rom, also without any affect.

Hoping someone can help me out here. :)

Edit: A bit more info: I was able to get the settings open, eventually after a few restarts I could drag down the notifications drawer and hit the little gear. I tried setting the default launcher to something in the list, but it had no affect. Still, hitting the home button leads to nothing and if I hit "back" enough times I just return to the Lineage OS screen described before.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] tbjr50:
flashing new lineage

You have to go back to the one you had before and flash it. then you can dirty flash the new update. It will not flash as a new rom. I had the same problem

---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------

First flash lineageOS 14.1 from Feb 11th with gapps then dirty flash newest update. It will then work for you
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
It is a nova issue. I turned off nova and used a different launcher and it does rotate. Any thoughts?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
Found the issue. In Nova there is a look & feel setting and that was set to default instead of auto rotate. Oops!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] scottlott:
Thanks for the reply! I was able to get a stock rom, install it and attempt the dirty flash but didn't get any success.

On that topic, does anyone know how I can confirm my device is a v2awifi, v1awifi or v2wifixx? My device shows a resounding SM-T900 when it boots but I've found references abound to this device being called any one of these three build numbers.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] snapper87:
I have a question concerning the repositories and manifests.

I compared the duplicate repositories from LineageOS and exynos5420 on github. The kernel repository seems to be much newer on LineageOS account, some others seem identical. Can I built this rom by relying on LineageOS/android_kernel_samsung_exynos5420. Last commit in exynos5420 was in October for cm14.1 tree.

thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] tbjr50:
T900

The T900 is v2awifi

---------- Post added at 04:07 PM ---------- Previous post was at 03:59 PM ----------

To flash lineage you should make sure to root your stock rom and flash the recovery for v2awifi then backup your stock rom and flash an older version of lineage first preferably feb. 11th and flash gapps. After that you can dirty flash the latest update. I hope this will work for you this time
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
The 2/25 build tells me my external SD card needs to be formatted. Just FYI.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TommyStarwind:
Tried a few times, but it just stays stuck at the Lineage splash screen. Down two separate installs doing ROM, gapps, and root. Then wiped everything and just tried the rom. The Same exact issue both times. I waited about 15-20 minutes at the splash screen. It did allow me to change the volume and such, so it was reacting somewhat.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Young Gunna:
I had the same problem and read hear that you have to flash the previous week's lineage first with Gapps first, go through set up, and then dirty flash the latest lineage on top. There's a bug or something with the latest set up wizard
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TommyStarwind:
I'll give that a try here in a bit. Thank you!!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] db2boy:
Anyone have problems with trying to open the settings for GBoard and it crashes? I've tried versions of OpenGapps back to Jan and constantly the same.

Thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] harrybarracuda:
I'm stuck.

I started with an unrooted Stock.

Rooted the device

Installed the modified TWRP.

Installed the modified bootloader.

Installed Lineage and GApps.

When it reboots, it eventually ends up at a full screen Lineage Logo and I can't get past it.

Did I miss something?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Young Gunna:
Follow the steps:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] harrybarracuda:
Just to clarify:

When you say the previous week's, is that a particular version number/date?

And by Dirty Flash I assume you mean without wiping?

Thanks for your reply.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] matosrob:
I flashed FEB 11ths build with Gapps, went through the setup, then dirty flashed FEB 18ths on top everything is working great for me.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Young Gunna:
The Feb 11 release is the previous week's and yes dirty flash means without wiping
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] harrybarracuda:
OK gents I'll try that, thanks.