yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] :
Again: I wasn't rude. OP asks for logfiles, when reporting issues (insisting reporting an issue, does not imply the wish to get it fixed, is an oxymoron and in this case also polemics), I just reminded you directly. If that offended you, the reason of feeling offended is not me. But perhaps I should stick to the rule of thumb of some of the devs: just ignore all postings without logs. And I honestly doubt, you have searched to find a solution yourself (see the solution). Also: you ignored the polite asking for logs - that's a lack of respect for the devs asking politly. And again: that wasn't rude but honest.

I trusted your statement, you have done the first three points - and that was misleading.

The workaround is easy and the very same like for hearthstone: http://xdaforums.com/showpost.php?p=64454091&postcount=1714.
[Galaxy Tab S Original Android Development] bp_ballistic:
Sorry you don't trust that I searched.

Thanks for pointing this out, I see that you are familiar with this issue so it was easy for you to find/reference. I'd call this a needle in a haystack find: it's for an UNOFFICIAL CM build on a different device and for a completely different game, which would probably explain why I didn't find it in my searches. Enabling 4x MSAA in the development options appears to resolve the issue and the game runs and does not crash when trying to run it on newer versions of the ROM.
[Galaxy Tab S Original Android Development] :
I was not aware, that this was the problem, 'cause I found no egl errors in your log. If I would have known that, it would have been my first answer instead of begging for logfiles. After searching your logs for errors for one hour, I searched for "ea games black screen android" (without the quotes, of course), and it was the 4th or 5th entry... Then I realised, it's the same issue then with heartstone. What nobody - at least not me - wouldn't have guessed from the log... What should has rang my bells, is the company name: ea. BTW: this is a workaround for missing size check of a buffer used for creating a new gl surface, luckily 4x MSAA creates surface buffers of the size starwars expects. A real "fix" could only be applied to the prog (or the underlaying engine). Again luckily: I can't see any sideeffects to other apps, if you enable 4x MSAA.

Use the source, Luke! ;)
[Galaxy Tab S Original Android Development] optionalmgrr.la:
Hi everyone, just asking, if anyone is using this, and also used the S2 8.0 (stock or custom ROM), how do they compare?

I'm seeing some interesting deals for used S 8.4 local.
[Galaxy Tab S Original Android Development] h22aboi:
I searched, but wasn't sure if this was an issue for people...

I am running the latest nightly CM12.1 with TWRP 2.8.7.0

(see attached screenshot of details.)

I don't like to use my hardware buttons, so in this CM 12.1 I use the on screen nav bar and turn my tablet hardware buttons OFF.

Settings -> Device -> Buttons

Enable on-screen nav bar (ON)

The only problem is, when I set it, it works, but as soon as I lock the screen or reboot, the settings don't 'stick'.

Can someone verify and could I possibly get a fix for this?

(sorry if this issue has already been addressed.)

Yes, I searched, factory reset my tablet, and recreated that one problem.

Yes, I do have a log file, but not sure who to send it to.
[Galaxy Tab S Original Android Development] h22aboi:
I started using the nightly, but I had an issue with hardware buttons.

The overall ROM seems pretty good, but I feel it's somewhat sluggish compared to my rooted debloated TW stock rom. I might go try a different ROM as well.

Alot of the TW stuff that I like is no longer there (obviously), like multi-window and stuff, but I guess I put xposed module and get that back. The camera app kinda sucks with limited options, but you can run a different app I suppose for that.

Pro: basic CM12.1 ROM that I am used to putting on all my android devices

Con: felt it wasn't super super polished (ie lag) like the CM I'm used to seeing (ie. my nexus devices) but I guess since it's a nightly I have to expect that

I can't disable my hardware buttons.
[Galaxy Tab S Original Android Development] Nedle:
This actually seems to affect a lot of games, since quite a lot of mine were crashing and couldn't figure out why. Enabling forced 4x MSAA did fix all of them though.
[Galaxy Tab S Original Android Development] kleinmischa:
I'm back at 100% batery drain per hour ;(
[Galaxy Tab S Original Android Development] rookie12:
What do you do? I play game and if im lucky 2 hours and im drained
[Galaxy Tab S Original Android Development] kleinmischa:
it looks like that it always happens when I'm not usind the tablet for 4-6 days. If I upse it again it drains the full batery in 1 hhour
[Galaxy Tab S Original Android Development] hochoch:
Hi folks, I just upgraded to a new PC and it is not recognizing my tablet. I'm on the 1/12 nightly. Not sure if it's the new PC, something w/ the nightly or a hardware issue. It also won't recognize any usb otg devices, not even while in twrp.

It is showing as charging from the usb on pc though. when i go to storage and hit the options for usb, it just says "usb is now disconnected". hopefully just a software issue! thanks for any replies
[Galaxy Tab S Original Android Development] methslushee:
Make sure you install the samsung drivers on your new PC

USB (Driver) ver.1.5.45.0 - Win XP/Vista/Win 7/Win 8/Win 8.1 (32bit,64bit) (EN, 15.27 MB)

http://www.samsung.com/us/support/owners/product/SM-T700NTSAXAR#
[Galaxy Tab S Original Android Development] roter$baron:
Why can't I install candy crush soda saga using this?It says my device is not compatible, when I try to download.
[Galaxy Tab S Original Android Development] hochoch:
thanks for this. I updated to latest nightly and it's working perfectly. not sure if something just needed a reboot, or if it was a software issue, but i popped in the usb cord and the pc recognized it instantly.

just glad it wasn't a hardware issue! Otherwise, it's working perfectly, loving CM12 but hoping for 13 ;)
[Galaxy Tab S Original Android Development] :
Obviously the vendor of ccss has decided not to accept this build as compatible - vendor issue, not rom issue. Open ticket at vendors support site.

Meanwhile you can just sideload the apk.
[Galaxy Tab S Original Android Development] methslushee:
I can't get my external sd to mount as UMS (USB Mass Storage), only can get MTP to recognize. Is there a known issue mounting with UMS?
[Galaxy Tab S Original Android Development] :
Had that problem on chagallwifi, too. Without logcat this is all guessing, but I could emagine that one of these can help:

https://github.com/nvertigo/android...mmit/8e483e20ec424a3062ac3bbd9cd0e561c2c3c418

https://github.com/nvertigo/android...mmit/35a7e8b64f4fdfd35fe5f7f226e6895cc3ef97f0
[Galaxy Tab S Original Android Development] macs:
nvertigo67, do you know if the double tap to wake feature was fixed? When you annouced it, you mentioned that the feature had some problems (when typing on the keyboard for example).
[Galaxy Tab S Original Android Development] :
It's some kimd of working: somtimes you have to double tap 15 or 20 times before it works, bit it does... ;)
[Galaxy Tab S Original Android Development] macs:
Great, thanks. I'm asking that because I'm building the rom by myself to add support to xbox gamepad and I was wondering if it's worth to build it again. My last build was in december 10th.
[Galaxy Tab S Original Android Development] dimeim:
Hello! Just gave in, forfeited my warranty and flashed CM - and it really feels great.

Everything seems good so far. One hiccup: Google Play Books opens but seems to not be able to connect to the internet and exits.

I searched the thread but didn't find anything about play books.

I'm on the latest nightly. Anyone got an idea?

Thnx!
[Galaxy Tab S Original Android Development] Kevinc25:
Problem with Nightly updates

Hi have been enjoying this build for some months but since the Dec 22 nightly I have been unable to flash new nightlys either using the auto reboot/install method or direct install from TWRP 2.8.7.2. The most important bits of the log for the auto install shows "error installing zip @/cache/recovery/block.map ". I have googled and seen this problem reported for other devices. Per those posts I have made sure signature verification is off and when that does not work tried manual install. When I install manually, I see the TWRP splash screen, back to home, and the log shows nothing (updating partition details done, Full SELinux support present, MTP enabled). Does anyone have any ideas? Could it be because I have my tablet Encrypted? TWRP seems to handle that ok, allowing me to decrypt/mount the encrypted data.

(Update: I wondered if I should be using a different Recovery like Cyanogenmod Recovery but I just flashed that and it didn't help.)
[Galaxy Tab S Original Android Development] :
I'm not sure, but maybi you mix up console output and log. To het the log, go to Advanced->Copy log to sd, thenboot rom and get the logfile.
[Galaxy Tab S Original Android Development] Kevinc25:
Thanks nvertigo67, your are of course correct, I should have said console.

After trying Cyanogenmod Recovery, I have reverted to TWRP and so I now attach the TWRP recovery log following an attempted manual install of the latest nightly. Any thoughts would be appreciated.
[Galaxy Tab S Original Android Development] dimeim:
Hey thanks for a great rom!

I've noticed that wifi in the battery details shows as always on even when I set it to go off with screen off, and even in airplane mode. This makes the tablet is always awake and the battery life is very bad. Any help?
[Galaxy Tab S Original Android Development] Kevinc25:
OK SOLVED: After using TWRP 2.8.7.0 and trying Cyanogenmod Recovery with no difference I updated to TWRP 3.0.0 and managed to do a manual install of the latest nightly. I will try the auto install next time.
[Galaxy Tab S Original Android Development] optionalmgrr.la:
Hi can you drop by S2 some time? :D

http://xdaforums.com/tab-s2/development/rom-cyanogenmod-12-1-tab-s2-8-0-t3268767
[Galaxy Tab S Original Android Development] SkOrPn:
Is this still the case? I have several apps that request Permissive mode just to show information, such as TWRP Manager. I tried SELinuxModeChanger.apk but the ROM refuses to let it be installed. That is the same app I used successfully on both my Nexus 7 and several TV boxes, and this tablet with other ROMs. Has Google found a way to completely prevent us from using Permissive mode?

Where are we on possible F2FS support with CM12.1? I read that in mid January F2FS got a major update, one of the biggest most exciting updates that F2FS has ever gotten and it would be really nice if we could start using this NAND friendly File System for our storage devices on this tablet. This SoC needs as much help as possible, LOL. F2FS would be a really nice option here. Whats funny is my 4 year old 2012 Nexus 7 with Marshmallow and F2FS /data /cache feels faster and smoother than this flagship TAB S device. HAHA

Anyway, just curious about those topics above. Love this ROM guys and thanks for such great CM work. Thanks :good:
[Galaxy Tab S Original Android Development] deadman96385:
My unofficial cm-13.0 builds have f2fs support, i can merge cache and data support for it into Official cm-12.1 so the next nightly will have it. I will look into updating the f2fs kernel files soon.

Edit: Merged the change https://github.com/CyanogenMod/andr...mmit/5ce3205e4fbb47bd0408661427441539c18a7cc4
[Galaxy Tab S Original Android Development] SkOrPn:
Thanks a lot deadman. That is very much appreciated. Now lets hope TWRP 3.0.0 gets F2FS support, or I will have to downgrade back to 2.8.7.2. lol
[Galaxy Tab S Original Android Development] deadman96385:
I will get f2fs support merged into official twrp soon.
[Galaxy Tab S Original Android Development] ExplosiveTrout:
Just wanted to add my thanks to deadman96385 for putting 5.1.1 out. Received my Tab S fairly recently and just last night decided enough was enough at TouchWiz with all the bloat removed was still rather laggy. This rom absolutely flies on the T700's hardware. I do have only one issue that I can see so far and I'm looking into it as it has been just 10hrs since I installed the rom. I have trouble with charging the device from my usual charger. The charger charges everything else just fine at 5v 2amps except the Tab. However the Tab charges from the stock samsung charger just fine. I suspect something on the software end is being rather picky but I need to look into it further before I report back.

Thanks again dude!

Edit: I am using the 2016-02-20 nightly.
[Galaxy Tab S Original Android Development] hvdl:
Thanks for the good job deadman96385! I've tried the nightly build from yesterday, with should have f2fs support, but is gets stuck during boot. I've only changed the cache and data partition to f2fs.

Any ideas or suggestions?
[Galaxy Tab S Original Android Development] SkOrPn:
I don't think it is part of the ROM just yet. Looking over at the changlog for klimtwifi I see "(android_device_samsung_klimtwifi)" listed in red text. Not sure what that means but according to Carter on Stargate Atlantis episode 416, red means BAD. lol
[Galaxy Tab S Original Android Development] hvdl:
It means that it's specific for that device. And Carter was on SG-1 ;)
[Galaxy Tab S Original Android Development] deadman96385:
She made a few cameo's on Atlantis. I also can't test f2fs because i need some data on my tablet for a little longer.
[Galaxy Tab S Original Android Development] SkOrPn:
Carter was on Atlantis several times including the episode 416 that I clearly mentioned. When McKay, Jennifer and Carter are trapped in a room under ground Carter runs to a blue door and McKay runs to the red door. When McKay asks Carter why she chose the door she did she replies, because "red means bad". However they can't get the blue door open so they try the red door anyway only to discover it leads to a deep hole they would fall to their death in proving she was right, red means bad. Later in the episode, after finding a convenient stash of rope, the red door proves to be the only way to escape the very dangerous situation they found themselves in just moments before the room falls into oblivion.

F2FS will not harm the performance of cache and data partition so no reason for me to wait for data to fill up. It's still in the lead when writing data. However there are a few features that make it superior to ext4 when the topic changes to mmc. Not sure what brand model nand this device uses (Samsung I would have to guess) but there should be a benefit to using F2FS. Prior tests have shown that it slightly lags behind ext4 in reading data which is why we don't need to use it on a read only partition such as /system. However cache is a completely different animal with many random writes. All in all, when everything is said and done its not really needed, however a small improvement in write performance and possibly a small increase in battery life is still welcome, and in my opinion, even if not noticeable. As the old saying goes, you won't know until you try. I think I will do some before and after tests today for fun. Lol
[Galaxy Tab S Original Android Development] :
Theoretically you are right. And f2fs is theoretically also more bat friendly.

I've used f2fs on cache and data on manta, bacon and chagallwifi for about three months each. Practically there's no difference at all. The increased write speed of f2fs should be more feelable, the fuller the fs is - but in real world you won't notice any difference.

Conclusion: it's nice to have f2fs, but there's no real advantage in day to day usage over ext4 on the devices I mentioned.
[Galaxy Tab S Original Android Development] SkOrPn:
Yeah I was afraid of that on these newer devices. On my Nexus 7 F2FS was a major improvement. It's like the idea of using it on an SSD. You can only "feel" the difference if you benchmark the crap out of it and then it's only really seeing the difference. I can't feel any difference using the newer nVME PCIe devices yet it's crystal clear they are faster. The lack of human perception is no reason to not adopt newer technology. Not for me anyway...

Case in point: Intel will be spending hundreds of millions of dollars in R&D just to try and get down to 10nm fab by the end of 2017. Why spend so much on a measly 4nm drop in fabrication when every expert says its not going to be "feelable" (as you put it)? Because it is an improvement none the less, even a 1nm drop is improvement. Intel went from the 1990's with pentium at 800nm, 500nm, 350nm then down to 250nm, 180nm, 130nm, 90nm, 65nm, 45nm, 32nm, 22nm and now 14nm. Going to 10nm is the smallest reduction in fabrication to date. And it will prove to be the first fabrication drop that human won't be able to perceive a benefit from. Then why do it? Because it must be done and they deemed 10nm their next step in fab improvement. After that they may only be able to get down to say 8nm, then 7 and then 6.5, but the point is every step down is improvement regardless. Storage tech is the same exact way, even if humans cant perceive or "feel" the benefits, it is improving none the less. And we must have improvement apparently regardless of how little it may be. If F2FS writes at just 10mb/s faster, then I am OK with that, and if its only 1mb/s faster I am OK with that too. Its the improvement that counts, however small it may be, however unnoticeable I may feel it ;) In my head I know something was improved, lol.
[Galaxy Tab S Original Android Development] SkOrPn:
[MENTION=4222965]deadman96385[/MENTION]

Hey man, is the method to implementing F2FS the same as it has always been? I was using F2FS back in early 2014 when I was the official BETA tester for USBhost when we were pushing it onto the Nexus 7 devices. I have two years experience using F2FS yet I can't get CM12.1 to boot after changing to F2FS. So I ask, isn't the implementation the same as I am used to doing?

This is what I did for clarity.

1. Format DATA (not necessary but I did it anyway for a truly clean setup)

2. Selected /data and changed it to F2FS.

3. Selected /cache and changed it to F2FS.

4. Wiped /system allowing it to format the normal ext4.

5. Rebooted back to Recovery.

6. Flashed CM12.1 0220 Build.

7. Flashed OpenGapps PICO (The same package that worked perfectly on 0220 a few days ago)

8. Result, Cm12.1 is forever trying to boot. Let it sit for 60 minutes but nothing happens.

9. Tried everything above over from scratch a second time and same result, CM12.1 is just stuck in the Boot Animation. (now going on like 45 minutes the second time)

Has this method changed from how its done on my Nexus 7? Just curious, if nothing has changed in how we implement F2FS, then I'm afraid F2FS is not working on your ROM. Just an FYI mate. :good:

EDIT: I think I remember you saying that your CM13 builds have F2FS support. So going to try that real quick. Will report back as soon as I know something. Thanks

EDIT2: CM13 also would not boot. Tried twice and both times it just sat at the boot animation a very long time.

EDIT3: OK, the 3rd ROM (3rd time is a charm huh? lol) from Schischu boots just fine with F2FS. So both CM12.1 and CM13 from [MENTION=221356]Deadman[/MENTION] just sits at the boot animation for nearly an hour before I gave up and tried again (I know an hour is a long time to wait but I wanted to make sure). The ROM By [MENTION=2371134]Schischu[/MENTION] booted right away using F2FS. So at least we know TWRP 3.0.0 is OK. Yay! I wanted to test F2FS on CM though, so going to abandon Sundays plan of testing F2FS because all my previous EXT4 tests were done using CM12.1. It wouldn't be a fair comparison to do my F2FS tests on a AOSP ROM. I don't think anyway.

EDIT4: Now that I have verified TWRP 3.0.0 works with F2FS and a AOSP ROM, I have decided to try official CM12.1 a 3rd time and sadly it doesn't appear its going to boot. :confused:

Since I need the CM theme engine, I am going to format back to EXT4. Anyone else get F2FS working on CM12.1 yet? And how did you manage it please? Thanks

EDIT5 (ONE LAST TIME FOR COMPLETENESS)

OK, formatted back to EXT4 using the exact same procedure as I used for F2FS and now Official CM12.1 boots again.
[Galaxy Tab S Original Android Development] :
[MENTION=4222965]deadman96385[/MENTION]:

https://github.com/CyanogenMod/andr...configs/cyanogenmod_klimtwifi_defconfig#L3288

You have enabled f2fs for data and cache in fstab, but not in defconfig. ;)

SkOrPn: we totally agree. As stated above: it's nice to have (that's why I just looked at the source for you), but it does not influence user expirience. I have not argued against using f2fs.
[Galaxy Tab S Original Android Development] deadman96385:
Derp your right i always get confused between my work and what i have merged on cm.

Edit: Enabled it should be in the next nightly, all of the other variants had it enabled ;/

https://github.com/CyanogenMod/andr...mmit/766de8bcba14dd6ba66936091c952dd6a302cf37
[Galaxy Tab S Original Android Development] hvdl:
That die the truck :D Everything seems to be working OK.
[Galaxy Tab S Original Android Development] SkOrPn:
Yeah thank you nvertigo67, and yes I know you were not arguing about F2FS and I promise I was not trying to argue back. I was just making a valid point that we "need" the newer options, otherwise if we don't adopt/test newer technology we might as well only have EXT or FAT as the only file system options, lol. No reason to stop at EXT4 and give up looking for the holy grail of file systems especially since the hardware has changed considerably. F2FS is just another step of many towards trying to do things proper on NAND. It may be years before it takes over, or it may even fail completely, who knows? In fact, if Btrfs becomes the go to file system for Linux, I wonder if Android will even bother? I would assume both Btrfs and F2FS (or F2FS2) would eventually become defaults on mobile devices powered by the Linux kernel. That's just my guess anyway. Things might change again since single layer NAND maybe nearing EOL.

Anyway bud, thanks for taking a look at the source and spotting the problem for me. I thought maybe I was doing something wrong or my nice new custom TWRP was faulty, or that maybe something I missed (a software switch somewhere) was changed since my Nexus 7 F2FS testing days. I spent thousands of hours and nearly half a year beta testing F2FS kernels for developers over in the Nexus forums, so I was fairly sure I remembered how to do it. I been using this TAB S T700 since April and did not bother with F2FS on it as it was fast enough for me, and still is. Anyway thanks again :good:

[MENTION=4222965]deadman96385[/MENTION] also thanks to you for the hard work on official 12.1. Between you two guys (and many others not mentioned) this tablet appears to getting nicer and nicer as time passes by. Thanks for that...
[Galaxy Tab S Original Android Development] duese22:
Hi!

Is somebody here familiar with widevine drm? Cannot get drm working with streaming on e.g. Netflix. I am stuck at 720x480 resolution. With stock-like rom (iron rom) no prob, full 1080p. Thats the only thing keeping me from cyanogenmod as i am using my tab s a lot for (binge) watching series. Drm info says that google widevine is supported on 12.1, but the security level is not specified. Drm level 1 is needed for hd streaming.

Any ideas on this issue?

Cheers

Duese
[Galaxy Tab S Original Android Development] deadman96385:
DRM has always been a problem on the tab s, we are lucky it works at all. Once i get ril working properly i will see about working on the drm again. We should be able to use source built but i do not know yet.
[Galaxy Tab S Original Android Development] :
It's not widevine drm, it's netflix. Didn't you read the contract? *lol* Kidding.

But sadly this is no kidding.
[Galaxy Tab S Original Android Development] SkOrPn:
[MENTION=4222965]deadman96385[/MENTION]

Is it OK for me to go a head and attempt another go with F2FS?