yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Very strange: trying to download the file with Chrome and it stops (& autoerase file) downloading the temp file when reachs 105MBs ~.

Using native browser it downloads a .bin file, complete at least, but I have to rename it to .zip to be able to flash.

What's wrong??

__

Wtv, can you add a simple way to access cpu governors and such by android settings so don't need to use Adiutor?

Thanks.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] static25:
Can I flash the bootloader firmware with TWRP?

I don't have a wins.h.i.t to install Odin on.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Fine :) vibrations are now working fine :)

One question: since flashing the Lollipop Bootloader with Odin I got the following red Message at Boot:

"KERNEL IS NOT SEANDROID ENFORCING"

and when restarting into recovery:

"RECOVERY IS NOT SEANDROID ENFORCING"

Is this the normal behaviour?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] tbjr50:
Cm13 for the t900

Yes that is normal
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Yes. I not found another way yet. You can always fire up a Virtual Machine or barrow a friends computer.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] havocki:
I have v1aWIFI on my t900 I try to flash to this version but I get message your device is v1 and your are trying to flash v2?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Hmmm you could take a look at the "Java"-Version of Odin, which should work on Linux, Mac and Windows....but I dont know if it works with our TabPro

and where it can be downloaded....because I couldnt find a working download-link:

JOdin3 at XDA-Forum:

http://xdaforums.com/showthread.php?p=49133090#post49133090

english URL about JOdin:

http://androidnews.co.in/2014/01/16/jodin3-open-source-odin-windows-mac-linux-can-used-browser/

german URL about JOdin:

http://linuxwelt.blogspot.com.tr/2014/03/jodin3-als-odin-alternative-ubuntu-1404.html

[EDIT]: This download-link should work :)

XDA-Forum internal download:

http://xdaforums.com/devdb/project/dl/?id=20803

Please "Thank" the Uploader:

http://xdaforums.com/showpost.php?p=69021732&postcount=353
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
You need to flash the t900 version of twrp.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Can you clear up naming confusion for this tablet / ROM for me? TWRP only lists v2wifixx version so one would think this was the name of the tablet that they believe. Your CM12 version listed v2wifixx. CF autoroot lists v2wifi and has root tools for v2wifixx and v2wifiue. Now this CM13 version header says v2awifi. As we know, the P900 is v1awifi so calling this v2awifi seems logical but I do not see this use anywhere else. Adding to the confusion is that those of us who have been using P900 ROM while we were waiting for T900 ROM to appear have had to use a v1awifi twrp. I'm sure there is a reason why you changed.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] toolhas4degrees:
because you didn't need to use the p900 twrp. all you had to do was edit the p900 roms updater script. and since the dev made this rom for the t900 it only makes sense that you should use the correct twrp for the t900.

as for naming... i know in my from with lollipop that v2**** was the firmware version, but i don't know how it applies to cyanogenmod
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
I get that you can edit the updater in the P900 ROM and I actually learned how to do that but I frankly found it easier to change to the P900 TWRP until we had a T900 ROM and then change back to the T900 TWRP. It didn't seem right but everyone was using the P900 TWRP and it worked for me. Maybe v2wifixx is the firmware number but what is v2awifi?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
v2awifi is the technical codename from Samsung. I think people started using v2wifixx out of the blue. The v2awifixx is the variant device name. Everything should be standardize on v2awifi.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Thank you! Then v2awifi is the proper device name for T900 (and v1awifi for P900). Our variant is v2awifixx and our Samsung firmware is T900XXUBPA1_T900PHNBOI1_PHN.zip. This is finally making sense to me. Therefore, chainfire and TWRP have mistakenly used v2wifixx. We need to remember, then, that they should have really used v2awifixx.

May I suggest you make reference to this in the OP as I am sure I am not the only person who has been confused by this and it might help others understand the naming convention more quickly. May I also suggest you link the correct TWRP (https://dl.twrp.me/v2wifixx/) in your OP as well, and refer to the confused naming convention?

Again, thanks for the great work on both the P900 and T900. We all appreciate your work and for putting up with our chatter.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Shveesus:
Is there a way to enable fast charging?

First off, thank you for bringing life back to Rom development for this tablet, I'd almost given up hope. I was curious if there was a way to enable fast charging on the tab, some games will actually drain the battery while my tab is plugged in. I'm using the stock charger, which works fine for fast charging my s5. The lock screen also says charging slowly, so I assume that it's not the charger. I've been using your build for the past two weeks and am loving it. Thanks again for keeping it going!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
I have contacted a couple of the guys at TWRP to make this correction. I have also fixed the kernel so vibrations, mtp, and adb now work. If you would like to flash it, here is the link. You can flash this in TWRP directly. Hit install, then select image button, then select the .img file. Then reboot back into recovery and these features will now work.

NOTE: You can only flash roms that allow v2awifi with this device name as of right now. This is only for testing. dMy next build that I put out, you can use this recovery or the old one. Any previous builds that I have built was built for the old recovery. I will see what can I can do to allow flashing of the v2wifixx rom in this new recovery.

Ignore the words that say fast charging. This tablet did not technically come with fast charging. If you would like to to see the charging rate, you can use the app called Ampere. Link
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
I think it's going very hot sometimes, i'm experienced some auto resets. Maybe going to undervolt a little with Kernel Adiutor.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
I am again confused, so sorry. The way you worded this quote I was expecting to find a new kernel for download in your link. Instead, I found an apparent new TWRP appropriately named v2awifi. Is this a new TWRP with zero change except for a correct name? Where is the alluded to kernel for flashing?

Maybe you are saying that your most recent ROM had the kernel update and the link was for TWRP img?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
I fixed the kernel in TWRP. Also the TWRP naming is correct too. It will match v2awifi. This link is only for TWRP.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] toolhas4degrees:
wifi is wifi tablet. guessing note (P ver) was released first that is why it is 1
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Just discovered that mediaserver process are killing my battery and making my tab hot. Don't know why. :/

EDIT: SOLVED installing Media Scanner Optimizer
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Flashed your new TWRP. Nice. Indeed, vibrations now work on TWRP. And I can say they work on the ROM as well. So now we really have a TWRP made for the T900. Is there any place in TWRP to identity the build info/date. I can't tell the old version from the ones by looking at it. I know it is the new version from the vibrations. Are your buddies going to put this version on the TWRP site? Can you put this link on the OP?

Is there anyway to get rid of the red warning from Samsung "recovery is not seandroid enforcing" that agitates so many people? I sure would like to not have that red warning even when I know it is meaningless.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] toolhas4degrees:
that red warning usually means that you are using a permissive kernel
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
So I have never seen that warning on any TWRP before. If it doesn't make any difference, why do we have to see that warning that seems fearsome to so many? Why should we care if a recovery is permissive or enforcing? If anybody cares, why don't we make the recovery enforcing so we can get rid of that warning?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] deadman96385:
It wouldn't matter if twrp was enforcing or not its due to the samsung bootloader not finding SEANDROIDENFORCE at the end of recovery or the kernel. The warning means literally nothing for custom recovery or rom users.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
So I know that it means literally nothing, but many people don't know that inherently and are worried that it is something important, including myself when I first saw it. So why can't some smart person modify TWRP so the Samsung bootloader thinks TWRP is seandroid enforcing since it means nothing and we can get rid of the threatening warning in red? Then every 2 weeks some worried person doesn't have to angst and ask.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] toolhas4degrees:
how about the OP just puts it in comments of installation so new flashers don't fret
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
I think that would be very helpful along with a link to the proper TWRP. Having said that, have you ever had that error message using any other device, ROM, or TWRP? Not me. Doesn't mean it doesn't happen. I just installed an AOSP Marshmallow ROM on a 5 year old Galaxy Nexus with TWRP 3.0.2-0 and no red error message.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
New nightly is up. Something to note is in the OP, I have updated TWRP. I have notified the guys over at TWRP to update their site but I figure I would be the first to get the updates to you. The changes in TWRP is the kernel, mtp, adb, and performance. Also, I got rid of that pesky message saying Recovery is not SEAndroid Enforcing. So make sure you upgrade TWRP to take advantage of these features.

Changelog

SELinux is now Enforcing. You can verify this under "About Tablet"

Ramdisk updates (This really helps with things like gps locking.)

Updated Audio, Wifi, Media configs

Added WifiLoader module

Sorry I have been dumping a bunch of new stuff on you but this is all good stuff and I want you guys to have it! Kernel, we are still working out some kinks. The two best CPU schedulers I recommend is Interactive and Conservative. As always, give me feedback. I want to create the best ROM out there.

Enjoy! Link
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Just a heads up for everyone, do not feel obligated to flash a new version of TWRP. I figured I would put it out there since there were a lot of fixes.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Hi ThomPatry,

thanks for the changes in the recovery (which I did flash) - the red message is gone for the recovery :)

BUT at the new nightly I did get also the red Message for the Kernel and in the "About Tablet" Tab I could read

SELinux-Status

Strikt

Did I miss something on my system or do you got a newer kernel/nightly than

cm-13.0-20161017-UNOFFICIAL-v2awifi.zip

with SELinux-Status Enforced?

EDIT: the geman "Strikt" is the english "enforced"....but when its is enforced - why did I get the red message for the nightly? Shouldnt it have the same Kernel as the new TWRP which you did configure?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] KoningBas:
Hi ThomPatry, would it be possible to post a bit more extensive installation guide for a noob? I've been away for some years that's why

---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------

And I have a non-rooted T900 BTW. The help would be highly appreciated.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Please read up a couple of post....

[MENTION=4222965]deadman96385[/MENTION] could have not explained it any better. "It wouldn't matter if twrp was enforcing or not its due to the samsung bootloader not finding SEANDROIDENFORCE at the end of recovery or the kernel. The warning means literally nothing for custom recovery or rom users." So in short, ignore it. I know it looks ugly and mean but it is just saying, "Hey you are not running the Samsung Software." The TWRP version (Recovery) I linked above and the OP puts "SEANDROIDENFORCE" the end of the Recovery kernel so you don't see this. I have not figured out a way to integrate this into the ROM kernel yet.

Please dig through the general section. Here is a link to get you started: Rooting and Installing Custom Recovery

I have updated the OP. After this point, I will no longer answer anymore questions about this. Not trying to be rude, just want to make sure everyone reads the OP fully.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
Some detective work....

Guidol is of German descent (even though his nickname sounds more like a French one :) j/k

---------- Post added 18th October 2016 at 12:04 AM ---------- Previous post was 17th October 2016 at 11:57 PM ----------

Hi Tom,

I've noticed that the Home button no longer wakes up the tablet in the latest build Oct-17-2016. If the table just goes to sleep and you press the Home button, it may wake it up. However, if it has been sleeping for a few minutes, pressing the Home button does nothing.

I did verify that that the "Wake up device" setting is enabled for the Home button. That setting worked properly in the previous build.

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
Live Wallpaper / Home button

Flashed the new recovery and update without issues.

I wanted to report I have the same actions/issue with the home button.

I also noticed two of the four live wallpapers do not work as well (report an error). Black hole and Phase Beam. "Unfortunately _______ has stopped"

-Mike
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Masayoshi Tadokoro:
Thank you for the update!

Very nice work! I am grateful! !

However, you do not wake up even my home button.

Best wishes,Masayoshi

---------- Post added at 02:42 AM ---------- Previous post was at 02:23 AM ----------

Screen shots do not work.

Screenshot In 20161014 was at work.

Best wishes,Masayoshi

---------- Post added at 02:53 AM ---------- Previous post was at 02:42 AM ----------

Screen shot worked.

Is my way was bad.

Best wishes,Masayoshi
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
I did read many times a couple of posts and did read that the red message doesnt matter, but after the correct recovery I did miss the bold message above from you about that you couldnt it append at the end of the nightly-ROM-kernel.

So its OK for me and I wouldnt make you angry or to be rude to us :)

Its the current state of the ROM and you have done a great job.

PS: About the home button.....as my SM-T900 did go to sleep I cant it wake up like the ohter guys, but if I press the power button to wake up and then to set it to sleep...then the home-buuton does work as wakeup-button....seems to be only when it puts itself after the timeout to sleep....
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Super nice job on updating TWRP with the kernel upgrade and the SEANDROIDENFORCE insertion. It is very professional! I hope you keep the fix for the ROM kernel in the back of your mind for a later day. Thanks for the OP additions which are VERY helpful. I'm in love with this tablet thanks to you.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
I can confirm this and I have found a fix. I will have this fix in the next build I put out.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
[OFFTOPIC]

Yes - I was born in Frankfurt/Germany :) (now living in Turkey with my family)

Guido is normally a name in Italy - the l/L after Guido is from my surname - so its easier the get a free nickname in a forum :)

[/OFFTOPIC]
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
I have a problem: Marshmallow suppose to have native Midi support but some apps i use don't detect it. Can you look at this please? Very thanks!

--

Just tried to select on developer options and Midi one don't keep selected, the other ones keeps (MT,PTP,RNDIS,Audio Source) but not Midi. Are Midi active in this Kernel? I need it badly.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
I will look into this.

------------------------------------------------------------------------

New Nightly: Link

Changelog:

Fixed the home button waking issue

I know it is not much but I am working on some other major Camera changes for the device and trying to tap into and take advantage of the Wolfson DAC and fix the quiet audio issues.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Thanks.

In regards to the quiet audio i think it's normal. The only way to get more louder is trough compression/limiting. I've always used Viper4Android for that on all my devices. But quiet audio is like it should without any processing. Not really an issue.

ps: a serious issue for me is that I'm getting a lot of random device reboots. I'm the only one?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
Actually this version seems to have fixed my random revolts from CM12.1 and also the delay in turning the screen on when it goes in screen saver mode.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
Viper4Android

Hi Bertoxo,

I tried to install the latest Viper4Android on SM-T900 with Tom's latest CM 13 build 10-19-2016, but its driver status always showed "no enabled" even after successfully installing its driver and rebooting. Basically it does nothing to enhance the audio. Does it work for you on SM-T900 with Tom's CM13 images?

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
I didn't tried yet on this cm13, but i think it needs an xposed module to work. I'll install it soon and let you know.

Xposed works, i know cause' i'm using it since day one.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
Hi Bertoxo,

I did have Xposed running properly on my SM-T900 / TOM CM13. Did you mean I need to install some extra Xposed module in addition to the Viper4Android apk I downloaded from XDA?

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] midimench:
Has anybody had the same boot looping problem by installing the 10-17 update over the 10-14 install and try to update the binaries on SuperSU (Version 2.78), only to create an endless bootloop?

Sent from my Samsung Tab Pro

---------- Post added at 07:49 AM ---------- Previous post was at 07:35 AM ----------

I'm sure this has probably been asked before. When you upgrade to the next nightly, is wiping the davlik and cache enough, or is there more I should be wiping?

Sent from my Samsung Tab Pro
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
I always format the partitions system/dalvik cache/cache (in TWRP Advanced ...), then install the new ROM and the SuperSU zip as well. Never have any problem going that way.

Thanks,

Eric

---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------

---------- Post added at 04:20 PM ---------- Previous post was at 04:16 PM ----------

I've tried all kinds of audio packages (Viper4android, Dolby ATMOS etc.) and none of them would work on this CM13 for SM-T800. Either they could not actually install drivers (despite showing successful messages) or their apps were forced closed upon opening.

No more audio enhancement attempts for me :)

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
I always wipe cache and dalvik cache.

I never need to install SuperSU (for me) because CM13 (and also CM12 before) is already rootet via the Developer-Options.

For which purpose do you need SuperSU?

Normally I do flash with the nightly CM13 (today I used the version from the 19.10.2016 with the working Wakup-Button) the latest Open GApps pico for ARM/6.0 (today the version 22.10.2016)

My SM-T900 is working fine :)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] midimench:
You're super helpful, thanks

Sent from my Galaxy S7 Edge

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

All this time, I thought I needed SuperSU, so that's a relief.

Sent from my Galaxy S7 Edge

---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------

I thought I needed SuperSU for Busy Box, Titanium Backup and Flashfire.

Sent from my Galaxy S7 Edge
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
if you need additional features of SuperSU you could try to read here:

http://xdaforums.com/apps/supersu/supersu-cm13-t3461432
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
SuperSU is especially useful for app root management

SuperSU allows users to keep track of the apps for which the root permission is enabled. That's why I always install it in any device with rooting capability (either using non-CM or CM images).

[/QUOTE]
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Viper4Android works perfect for me: you need to use a permissive selinux. Luckily i didn't flash the the new cm13 updates which are ENFORCED.

There are a some ways to change selinux mode. Maybe we can ask for Thompatry to back it to permissive in the next update too.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
Thanks a lot Bertoxo.

If that's the case, the XDA app (SELinuxModeChanger) did not actually do anything despite saying so. I did still see the Enforcing status in About even when SELinuxModeChanger indicates a change to "Permissive".

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
SELinux = Permissive

Hi Tom,

Could you please compile your CM13 kernel code with the SELinux permissive mode enabled (e.g. the flag EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=false) so that users can switch the SELINUX mode from Enforcing to Permissive if such need may arise?

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
Bug reports regenerated now and then

Hi Tom,

With the newest build 10-19-2016, I've noticed some strange behaviors:

1) Sometimes after a full charging, the tablet may get quite warm/hot, especially near the camera area.

I never noticed this strange behavior before in CM 12.1.

2)Bug reports generated now and then for no particular reason. I attached one of them to this post.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Planet X:
I just cannot believe what i just see here. cm13 for my lovely T900 tablet. Thank you for your great work [MENTION=4817899]thompatry[/MENTION]. Did you fix the slow wake issue I have had with cm12 too?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
It did for me.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Planet X:
I've just installed latest build and it's working fine. Also the wakeup delay is gone as I hoped. But I'm missing the proximity sensor setting. I mean it would be nice that my screen switch off when I close the cover. Is it possible to add that?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] KoningBas:
My tablet switch off when closing the cover...(3rd party one). Didn't have to do anything for that...worked out of the box.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Same here. My cover works perfect.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] midimench:
Beautiful job making a great working CM13 for us Tab Pro ppl

Sent from my Samsung Tab Pro