yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] ripee:
The 20160722 unofficial build is still affected with "About phone". Would this help in system.prop given that it's stubbornly set to "default" in build.prop?

# Device form factor

ro.build.characteristics=tablet

Other than that, thank you so much for all your work! :)
[Galaxy Tab S2 Original Android Development] Phil DeGrave:
The 7/22 update has put a lock on my tray so I cannot select any apps in the tray or the round app drawer button and when I do push on any of the apps or app drawer button a lock appears over the app drawer button and a phone icon appears on the left side and the drop down notification starts to open but goes away when I release. This problem also blocks my space bar and the whole row above it so my keyboard is now useless also if I try to update to either the 7/22 or 7/23 updates. I tried to find a way to deactivate this new change and I cannot find a way to remove it, I think its live lock screen doing it. I think this is the culprit that was changed on 7/22, 1c93b57 SysUI: Add first time use lock screen hints. Anyone know how to solve this problem? Thanks in advance, I would appreciate any help, otherwise I think 7/21 is my last update. ?
[Galaxy Tab S2 Original Android Development] bill1clinton:
Thanks for the response. I hope I did not offend you; I only wanted to solicit the opinions of members whom are using this ROM.
[Galaxy Tab S2 Original Android Development] Phil DeGrave:
So I assume I must be the only one having the lock screen issue, I am running the German version of MM if that might be the cause, idk, only thing I could think of that might be different about my system. So should I just do a factory reset and see if that will solve my issue? Strange how it seems I am the only one having this issue with the locked tray going on with the updates of 7/22 on. I figured others had experienced it also and maybe fixed it.
[Galaxy Tab S2 Original Android Development] T_I:
I haven't seen this, screen lock works as I expect it to work.

Also, there is no 'German' version of Cyanogenmod. There is only one to rule them all. :D (Libs are from stock European MM)
[Galaxy Tab S2 Original Android Development] Phil DeGrave:
Cancel that.... The 7/24 update seems to not have the same issue for me, all is well and great once again! ☺

Lol, yes, I was referring to the S2 MM update I downloaded months ago was the German version ☺ Thanks again for the wonderful CM OS, TI!
[Galaxy Tab S2 Original Android Development] ripee:
About "phone" is still there in 20160724 but otherwise working great! :)
[Galaxy Tab S2 Original Android Development] fozzy056:
Just a detail ;)
[Galaxy Tab S2 Original Android Development] T_I:
A nagging detail, as I added the fix for it... [MENTION=3463426]RaymanFX[/MENTION] found I patched the wrong file, it's a device makefile setting, not a boardconfig setting. The latest unofficial upload has this one fixed.
[Galaxy Tab S2 Original Android Development] lewmur:
I still have the problem that high 5ghz channels for the USA aren't available. My favorite Pub uses channel 161 for its wifi and I can't use this ROM while I'm there watching sporting events.
[Galaxy Tab S2 Original Android Development] T_I:
That'll be one I'm hunting after, I have 2 channels available, 36 and 52. As I have other issues as well, maybe I'll see if I can use the AOSP wifi completely instead of partial stock libs.
[Galaxy Tab S2 Original Android Development] lewmur:
I just know that when the stock ROMs for MM, first came out, the ROMs for Cellular South and New Zealand had all of the channels while the ones for Germany and the UK didn't. This was true for both the T810 and the T710.
[Galaxy Tab S2 Original Android Development] T_I:
It's worth a test. Will check what differences there are in the blobs for wifi, as soon as the firmware is in.
[Galaxy Tab S2 Original Android Development] T_I:
Drat, USB port got damaged, charging is an issue, adb access is now a real problem...

Filled in a warranty repair request, they're quick, pickup this evening, delivery tomorrow evening. (even though I requested pickup Thursday morning as I had to pick a morning or afternoon)
[Galaxy Tab S2 Original Android Development] Dekan54:
I am sorry to hear about your T-810 and it's hardware issues..... For a minute I thought your development on the T-810 would come to an end.

Thank you for all you do and if I can help in any way don't hesitate to ask.
[Galaxy Tab S2 Original Android Development] peacepipe:
Is something planned for T813?
[Galaxy Tab S2 Original Android Development] Delta wolf:
I had this issue on my note 2 cm 13 as well i changed my screen lock to "slide to open" option then it went away I set up a password right after and have not had an issue since
[Galaxy Tab S2 Original Android Development] T_I:
I hope the device will be fixed, they have the nasty Knox warranty void stuff now.

When they try to hide behind Knox for a faulty charger port, then I think I'll reconsider my work on any Samsung device I don't own.
[Galaxy Tab S2 Original Android Development] DroidIt!:
That's really kind of bogus. Simply rooting won't cause hardware issues like charging port malfunction. That's just a plain simple cop out. To bad there's no wireless charging on this sucker.
[Galaxy Tab S2 Original Android Development] T_I:
Indeed, when they try it... in Germany they can't, as hardware issues with ports can never be software related. On the other hand, The Netherlands are a bit more pro company. We'll wait and see.

Ah well, time to work on the Moto G4 for a while, haven't got anything building there. Only thing I really mis is having a nice tablet for my games. (The Asus Memopad 7 is really bad for the games I play :crying: )
[Galaxy Tab S2 Original Android Development] ivanox1972:
[MENTION=4557146]T_I[/MENTION] Rom is great, just 1 Q.

Initially and after fiest few night updates there was option in advanced screen to change mdnie mode (4 options as on stock rom adaptive, dynamic, phot amoled, basic). But in 1 moment, don't know when, just gone. How to recover
[Galaxy Tab S2 Original Android Development] hga89:
I am on CM 12.1 from April and have downloaded the nightly build from July 29th of CM 13.0: what is the recommended way of updating while hopefully retaining all user programs and settings?

Thank you.
[Galaxy Tab S2 Original Android Development] CuckooPenguin:
1 st create a full nandroid. 2nd titanium backup of all apps. For cm 13 to work you need to install mm stock first afaik. After that i would flash cm after wiping (see instructions on 1st page) an restore apps and settings via titanium.

hf and good luck
[Galaxy Tab S2 Original Android Development] hga89:
I am already on CM 12.1. Why would I need to reinstall mm stock again?
[Galaxy Tab S2 Original Android Development] CuckooPenguin:
Read 1st action in the instructions , first page.
[Galaxy Tab S2 Original Android Development] hga89:
I have lost Wifi access with CM 12.1 for no obvious reason - see separate thread in the Help forum, prior to losing it, however, I got notified about nightly builds of CM 13 in settings which I believe I could have downloaded from there and installed. I did not do not, however, but now have CM 13 on the sdcard ready to be installed.

The fact that CM 13 was available for download - and, I presume, installation - in the settings menu would suggest that there is an easier way to upgrade without doing what you suggested and presumably losing a lot of information. Right or wrong?
[Galaxy Tab S2 Original Android Development] CuckooPenguin:
Well if you are brave enough give it a try , but i trust Ti , if he tells us to flash stock via odin before :)

If don`t mind a maybe not booting device .. go ahead.

Still i suggest to have a nandroid ready :)

God speed

Let us know if it went well ...
[Galaxy Tab S2 Original Android Development] hga89:
The first page with instructions does not specifically address upgrading from CM 12.1, hence my question.
[Galaxy Tab S2 Original Android Development] CuckooPenguin:
Ok, understood, then you have to wait for some else to answer. I think i just remember while Ti was working on a cm 12 for our tablet he mentionend in the cm 13 unofficial that its mandatory to flash mm stock even with his cm 12 before.

Anyhow if you have a nandroid backup you can just give it a try to dirty flash the cm 13, not sure what the cm upgrade process does in detail. Sorry.

Still, good luck and hf
[Galaxy Tab S2 Original Android Development] lewmur:
Won't work. The stock MM upgrade via Odin resizes the partitions. Dirty flashing this ROM via TWRP doesn't and neither will wiping for a clean flash. Wiping erases the partitions but doesn't resize them.
[Galaxy Tab S2 Original Android Development] T_I:
It not only resizes, but adds a partition (when I'm correct) which has MM specific code in it. When you don;t have that partition, it just won't boot.

I tried the dirty path myself, even the clean path without stock MM on the device. When it hasn't been on the device (which it wasn't on mine, as it got CM12.1 as soon as I got it compiling) the device will just show the Samsung splash screen until the battery dies.
[Galaxy Tab S2 Original Android Development] hga89:
OK, not sure I quite understand what would be the path to upgrade from CM 12.1 to the latest build of CM 13.0 then?

Can I use TWRP to install CM 13.0 over CM 12.1? Or what do I need to do?

The background is that I have been running the unofficial CM 12.1 release from April on my Tab S2 T-810 since that date but suddenly lost WiFi access where the WiFi button is darket grey than the Bluetooth button and it is not possible to turn WiFi on again. No reason as far as I know for this sudden loss: not installed any new software, no new OS, and battery was still at 71%...

I thought I might as well go to CM 13 but do not want to lose any data or settings.

Thank you.
[Galaxy Tab S2 Original Android Development] pilspeda:
Just clean flashed latest nightly and everything is awesome. Any idea if the finger print scanner will be available?
[Galaxy Tab S2 Original Android Development] lewmur:
The instructions in the OP state clearly what you have to do. You must use Odin to flash the stock MM and TWRP. Only then can you download this ROM to the tablet and use TWRP to wipe, and then flash the ROM and gapps.
[Galaxy Tab S2 Original Android Development] farell23:
Actually I have CyanogenMod 12.1-20160616-UNOFFICIAL-gts210wifi - Android 5.1.1

I want install CyanogenMod 13 but can you tell me where is stock image Android 6.x for my T810 distributed for country: Poland, I see only 5.0.1

I must install it firstly, before CyanogenMod 13.
[Galaxy Tab S2 Original Android Development] lewmur:
You get the ROM from Sammobile

Have you downloaded the Samsung drivers for ODIN on your Windows machine?
[Galaxy Tab S2 Original Android Development] farell23:
For my country - Poland is only 5.0.2 :(

Can I install other country ?
[Galaxy Tab S2 Original Android Development] lewmur:
What country you install doesn't make any difference. All you want is for the install to create the disk partitions and put the code in the new Samsung partition. That is the same for all countries.
[Galaxy Tab S2 Original Android Development] T_I:
Indeed, this is what needs to be done, stock MM must have been on the tablet at least once before you install CM 13.0.

Easy check, when you have a working camera in cm 12.1, you need to flash stock MM, when camera is b0rken in cm-12.1 you already had MM on the tab and

probably

(untested if it's a requirement then) won't need to flash stock MM before going to cm 13.0 .
[Galaxy Tab S2 Original Android Development] hga89:
Thank you, thus since I already have CM 12.1 on my T-810 and now want to move to CM 13 - and, I believe (cannot check it now) the camera works, I will have to reinstall stock MM, then, I assume, again install TWRP, and then CM 13.

I would think that I will - again - lose all software installed? Since I have ca 125 Google Play books, this is a bear to reinstall and takes multiple days until /everything/ is installed.

Can you venture a guess why WiFi suddenly disappeared from my CM 12.1 setup? Have not been able to reactivate it and the "button" for WiFi is darker than the one for Bluetooth (which seems to still work fine)? No new software, battery still at 71% when this happened overnight. May, and I stress may, have happened exactly six months after rooting and I first installed a CM 12.1 build...

Thank you.
[Galaxy Tab S2 Original Android Development] Ovevhkin:
My 128GB Micro SD from SanDisk doesn't work as internal storage. It's say the card is damaged.
[Galaxy Tab S2 Original Android Development] ad454:
Stupid question, but all Tab-S2-9.7" wifi (SM-T810) firmware, including this one, are incompatible with the Tab-S2-8.0 wifi (SM-T710), right?

Looking at the specifications, other than the physical size and mass, the "guts" of the T810 and T710 are nearly identical, with same processor/chipset, memory, display resolution, etc., and made by the same company and of the same product family. So it is not completely unreasonable to hope that compatibles exist.

Since there are no "official" Cyanogenmod for the SM-T710 as there is for the SM-T810: https://download.cyanogenmod.org/?device=gts210wifi

I wanted to make sure, just in case this and newer SM-T810 Cyanogenmod images would safely run on my SM-T710. I cannot stand the Stock firmware, and Cyanogenmod (with its Privacy Guard) is my first choice Android distro.
[Galaxy Tab S2 Original Android Development] T_I:
Correct.

Depends, when you make a backup with tools like Titanium Backup, you can restore from there, which saves time.

BTW aren't the google play books stored on the internal sdcard? (/data/media when I remember correctly) If so, you don't need to wipe that partition.

Haven't got a clue, haven't been using cm-12.1 since I got my first cm-13.0 build.
[Galaxy Tab S2 Original Android Development] T_I:
Yep, screens differ in required rotation and driver.

http://xdaforums.com/tab-s2/development/rom-cyanogenmod-13-0-tab-s2-8-0-t3409700

T810 isn't official as well, it's nightly, nothing more. (I know, I wrote it)

You can run it safely when you rebuild the image (remove the T810 check) and don't mind having a black screen. :D (I guess it'll boot, as the rest of the code is the same)

I'd say, good luck, when you don't want to use the T710 build.
[Galaxy Tab S2 Original Android Development] hga89:
Unfortunately Google Play books seem to be stored in /data/data/..google...books so they will be wiped...

Also, I installed the pico set of applications does not include a camera and since I have lost WiFi access, I cannot download any third-party application to try. Thus, cannot try your suggestion to see if the camera works and maybe skip the stock ROM reversion.

My take from the comments so far is that even though I had CM 12.1 installed, I need to reinstall stock 6.0 which will repartition the internal storage which is then in turn required by CM 13.0.
[Galaxy Tab S2 Original Android Development] CuckooPenguin:
Correct. And as this has to be done by odin and usb cable anyhow, .. how about downloading titanium apk to your pc, push to device via usb, install, make your app backups and pull to pc or store on ext sdcard ?

After that, stock, then cm13 and restoring from titanium.

hf
[Galaxy Tab S2 Original Android Development] ad454:
Thank you very much for your helpful explanation, and also for working on these Tab-S2 CM images!
[Galaxy Tab S2 Original Android Development] hga89:
Thank you. Asking many questions because I view my tablet as an indispensable tool and want to make sure I do not screw things up... My understanding, however, is that this tablet cannot be bricked - which is good ;)

I looked at the http://www.sammobile.com/firmwares/database/SM-T810/ website and could not find 6.0 for the US which surprised me! However, my reading of earlier messages is that all releases are identical for this particular purpose so I'll go with the Canadian release.

I have over 50 Gb of user data on the tablet, on both the internal and external SD cards that I do not want to download again. Luckily I do have Titanium on the unit already so I will use that to reinstall apps, settings and their data.

Will do this tomorrow.
[Galaxy Tab S2 Original Android Development] lewmur:
The U.S. and Canadian ROMs are NOT the same. The Cellular south ROM is the one for the U.S.
[Galaxy Tab S2 Original Android Development] hga89:
Oops. thank you. Will now download the Cellular South ROM. I thought, however, that this would just be used to install something temporarily in a partition to later be replaced by the CM ROM?
[Galaxy Tab S2 Original Android Development] lewmur:
I don't know about you, but I use the stock ROM as my goto ROM and experiment with this ROM and the Resurection one. Though it is bloated, everything works on the stock ROM including the camera, the fingerprint scanner, the Mic and all of the wifi channels. Even Netflix works, though if you root your tablet, you have to uninstall the PlayStore version and load an older apk.

The way I do it is to get everything working on the stock MM and then save that via TWRP. Then I can experiment with other ROMs and save them with TWRP also. That way I can switch back and forth between ROMs without losing any data or settings. And, of course, I save the backups on the external SD card so that I don't accidentally erase them by wiping.
[Galaxy Tab S2 Original Android Development] hga89:
The stock ROM 6.0 is the Cellular South ROM, is it not?
[Galaxy Tab S2 Original Android Development] lewmur:
Yes. It is the U.S.A. stock ROM.
[Galaxy Tab S2 Original Android Development] Lightn1ng:
[MENTION=4557146]T_I[/MENTION] about your warranty claim

AFAIK manufacturers in the European Union have to prove that your modification caused the issue.
[Galaxy Tab S2 Original Android Development] hga89:
I am in the US but I fail to see how installing another ROM could cause the WiFi to fail... I have received the UPS labels and will ship it to them on Friday when I have time.

It would be nice if a tool existed to find exactly why WiFi cannot be turned on. Don't know what tools Samsung technicians would be using.

---------- Post added at 10:16 AM ---------- Previous post was at 09:26 AM ----------

In response to another post I made, Ashyx suggested downloading syslog to check the logs. I will do so.
[Galaxy Tab S2 Original Android Development] Lightn1ng:
FYI this is a gapps issue.
[Galaxy Tab S2 Original Android Development] T_I:
Nice to know, I expect this should be in a more extended gapps then pico. (I've never seen/used it, so I wouldn't know)

Updated OP.
[Galaxy Tab S2 Original Android Development] DeadPicsel:
Is there any chance of getting CM on the SM-T819?
[Galaxy Tab S2 Original Android Development] Lightn1ng:
No, its just a bug that has been fixed in newer opengapps versions. Quick settings is built into the ROM, not gapps, but older opengapps had a bug where it would break quick settings.

---------- Post added at 03:20 PM ---------- Previous post was at 03:19 PM ----------

Its a whole different device - that being said, I'm working on CM for the Qualcomm tablets. I've been able to get part of the kernel building but not entirely. Be patient ;)
[Galaxy Tab S2 Original Android Development] T_I:
Sorry for the late response, I've been messing with CM to get it working on my Moto G4. Looks like I'll need to let that one to the team that's working a lot faster then a single developer can. (especially with my experiences)

I just noticed it's indeed gone. (had it on stock, so didn't notice) I saw someting mentioning this come by in the patches for gts2-common will look into it.
[Galaxy Tab S2 Original Android Development] nostupidthing:
Deleted
[Galaxy Tab S2 Original Android Development] T_I:
Just compiled the sources we had, changes I/O scheduler in kernel from noop to cfq. The tablet seems more responsive. Uploaded the image in the UNOFFICIAL location. Patch needs to be tested for T815 before it van be uploaded to cm.
[Galaxy Tab S2 Original Android Development] suzook:
Screen color controls broken in this build. No complaints, just letting you know.
[Galaxy Tab S2 Original Android Development] T_I:
Yeah, I noticed that as well, MDNie settings haven't been change in the gts2 sources, so must be an issue in the general code.
[Galaxy Tab S2 Original Android Development] suzook:
Bummer. Tab is def a lil speedier. Back to last build though, as I hate the yellowish screen. Thanks again!
[Galaxy Tab S2 Original Android Development] ivanox1972:
So no solution for broken screen modes? Is there some old build which has them
[Galaxy Tab S2 Original Android Development] T_I:
The image went nightly 29-06, I think it then still worked. You can try the unofficial builds from then to check which in which one this breaks.
[Galaxy Tab S2 Original Android Development] Delta wolf:
You say fingerprint scanner now works is there a way to add fingerprint lock screen then? Also my about thing says about tablet now no longer phone
[Galaxy Tab S2 Original Android Development] NeWONEx:
Is there fingerprint options ?
[Galaxy Tab S2 Original Android Development] hga89:
I received my SM-T810 back from warranty service about a week ago and have restored applications and data, TitaniumBackup was extremely valuable of course. However, now that I am on CM 13 rather than CM12 prior to the WiFi dying, I have discovered three problems with applications, not sure if the problem lies with them or with CM:

- running TItaniumBackup I am not able to access the Settings Menu, I only have two icons in the upper right-hand corner rather than three.

- running Tasks the task title and task details in the top part of the screen are not visible at all, only empty space.

- running Business Calendar Pro calendar events are not synced unless force-synced, however, tasks stored in the same calendars on my own owncloud server sync fine. Lack of sync is also true when using the calendar using the Google calendar in the pico-package, thus the problem may lie with the sync adapter.

The above all worked on CM 12.1 but I am now on CM build 20160903. If anyone else can confirm the above, or confirm it working on another build, please do so.

Thank you!
[Galaxy Tab S2 Original Android Development] T_I:
Nop, no fiingerprint scanner. (we never got that one to work as far as I know)

It's at 'Problems ?' and then Preferences. Looks like a 'hardware menu button' option sneaked in the settings somewere.

I don't use tasks/have it installed, so can't confirm or deny.

I'm running Business Calendar 2 pro and have no issues. Are you using version 1 or 2?

I'm running the unofficial 10-09 version. (as I have to tweak the /system/etc/wifi/nvram_net.txt and _mgf.txt files to have support of channel 12 and 13, somehow we haven't gotten this to work with ccode 'all')