yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] Robin M:
Two Small Suggested Tweaks

I have two suggestions for tweaks in a future update. The first is very easy....

1. I noticed that unlike the Samsung OEM firmware, all the files in the /etc/permissions/ directory were given execute permission in every category (permission code 0755 rather than 0644). I imagine this is what is responsible for fixing the SD card restriction (and maybe other restrictions) Samsung built into their KK releases. However I still had problems with a few programs writing to the SD card (i.e. "RootExplorer") until I made one small change within the "platform.xml" file. I added the line...

<group gid="media_rw" /> under "WRITE_EXTERNAL_STORAGE".

That fixed the problem. Can you make this small change in the ROM? (I only knew to do this because I found the suggestion in several forum discussions as a solution to the problem. )

2. I've noticed that the backlight brightness slider is scaled just a little too high for the Galaxy Tab S, IMHO. When you read at night with the lights out, it's still just a little too bright at the lowest end of the slide control. Would it be possible to scale down the dim side just a tad more? Don't know how difficult that may be.

Thanks.

---------- Post added at 02:07 PM ---------- Previous post was at 01:36 PM ----------

Thank you for this VERY helpful information, Nvertigo.

(Sorry to re-quote such a long post, but IMHO, it's worth repeating - especially for a semi-noobie.) :good:
[Galaxy Tab S Original Android Development] gsxrfl1k6:
5ghz wifi

Is anyone else having trouble getting the Tab to pick up 5ghz wifi? Mine just doesn't see it.
[Galaxy Tab S Original Android Development] Robin M:
Nvertigo,

I see what you mean about permissions, but I never did any chmod command. I just flashed today's update and then took a look at the permissions folder with Root Explorer. Here is a link to what it looks like. (Tried to included a screenshot in this message but all I got was text.) I checked the permissions with Root Explorer and they really are all 755. Take a look on your tablet with ES Explorer and see if you see what I see.

So the permissions must change while flashing, I dunno. I can tell you that in the stock Samsung firmware they were all 644, but now they seem to be 755. Strange!

As for the alternate "platform.xml" file, that's what I'm doing now, and over-writing the original with each new flash. I figured if you made the change I wouldn't have to do that any longer, but you know best, of course.

Thanks for looking at the brightness issue. Yeah, I'm talking about manual brightness, of course.

BTW, I just took a look at ES Explorer. I haven't used that since the days of Android Cupcake. But it's a really nice app now. I think I'm going to start using it full time. Thanks.
[Galaxy Tab S Original Android Development] Barracuda77777:
New build

op updated with new build 07/11/2014:

07/11/2014

cm-11-20141107-UNOFFICIAL-chagallwifi.zip

changelog:

all updates introduced by nvertigo67

Plus

added support for Ant+

lower manual brightness threshold

upstream update cm sources

happy flashing :)
[Galaxy Tab S Original Android Development] andresv1989:
So I just installed the latest build 11-07 and everything set up fine but after about 15 minutes my screen shut off and now it will not come back on. Anyone else have that happen? If so how did you fix it?
[Galaxy Tab S Original Android Development] Barracuda77777:
Hold the volume down key, home plus power until tablet restarts.

how did you flash?

been watching videos on 07 since I flashed it for testing 5 hours ago.
[Galaxy Tab S Original Android Development] andresv1989:
Sweet that worked...I always clean flash with CWM . then restore apps through titanium backup
[Galaxy Tab S Original Android Development] Barracuda77777:
did you restore any system apps?
[Galaxy Tab S Original Android Development] andresv1989:
No I only restore just the apps...any idea why it might of happened? Maybe something I did wrong?
[Galaxy Tab S Original Android Development] Barracuda77777:
I personally use twrp 7.1.1, I flash as follows:

wipe:

system, cache and delvik then I flash the rom, gapps and supersu.

can you send me the logcat?
[Galaxy Tab S Original Android Development] andresv1989:
That's the same process I use....how do I go about the logcat?
[Galaxy Tab S Original Android Development] Barracuda77777:
download this app, it is the easiest way.
[Galaxy Tab S Original Android Development] :
Mine does work on 5GHz with ac. Region settings in router and tab?
[Galaxy Tab S Original Android Development] hurray:
Thank you very much! Only one question: is the non capacitive kernel from post #2 still up to date and okay to flash?
[Galaxy Tab S Original Android Development] Barracuda77777:
I will be making a new one soon with the latest sources.

Edit, new one is in post #2
[Galaxy Tab S Original Android Development] ramiss:
So I went back to my Stock ROM (backed up with CWM) and almost every app is throwing permission errors. I've tried multiple "fix permission" tools and the "fix internal sdcard permissions" script.

Obviously the only thing I didn't wipe when restoring was internal and external storage, should I have? Do I need to move the nandroid backups off, wipe and back and on? Seems excessive,

What am I missing?
[Galaxy Tab S Original Android Development] Barracuda77777:
this is a problem caused from twrp, if you flash upintheair kernel for the t800 your problems will be solved, only other option is a full wipe.

cheers
[Galaxy Tab S Original Android Development] ramiss:
Thanks for the fast reply. I'm going with the full wipe/titanium restore method now. I'll then make sure I get the upintheair kernel.

---------- Post added at 06:35 AM ---------- Previous post was at 06:33 AM ----------

is the recovery issue at the backup or restore? In other words, if I flash upintheair now will the restore work properly?
[Galaxy Tab S Original Android Development] Barracuda77777:
the issue is at the restore, and yes if you flash now the upintheair kernel it will fix your problem.
[Galaxy Tab S Original Android Development] :
Esexplorer shows the same as ls in a shell - and if esexplorer would show different, I would pu my trust in ls...

So: there is something wrong with your installation.

Which recobery are you using. Try "Clean flash" with twrp-2.7.1.1. And then look at permissions BEFORE restoring apps. BTW: Which su are you using? Buildin or chainfire?

Let's first fix your installation, and then see if it is still a problem. BTW if you move files from fat fs to ext4 have executable bit set.

[MENTION=535343]all[/MENTION]: Does anyone have issues accessing sdcard1 from apps?

When clean flashing take barracudas build - he has already included the lower brightness.
[Galaxy Tab S Original Android Development] ramiss:
Thank you again!
[Galaxy Tab S Original Android Development] Gilg@mesh:
just want to say that latest TWRP 2.8.1.0 works fine for those who use older version.

Tapatalked from my GALAXY S5
[Galaxy Tab S Original Android Development] Crimsonthunder:
I have no problems with permissions or sdcard. I am using latest TWRP.
[Galaxy Tab S Original Android Development] Barracuda77777:
no_capacitive_buttons_chagallwifi_CM_7_11_2014_kernel.zip

here is the latest one tested and working great.

just a reminder that you will not be able to enable the buttons until you either flash the normal kernel which you can download from here or re flash the latest rom.

for anyone interested on how this is done, I disable the driver for the buttons in the config file:

# CONFIG_KEYBOARD_TC300K is not set to disable

and

CONFIG_KEYBOARD_TC300K=1 to enable

everything else in the kernel is exactly the same as the one that come in with the roms.
[Galaxy Tab S Original Android Development] :
What is the advantage of disabling the buttons in kernel over setting sofkeys on (which desable the capacitive buttons - I fixed this a week ago along with fixung the flashing button backlight)?
[Galaxy Tab S Original Android Development] Barracuda77777:
for me I hate the blinking lights when the tablet is off, and I don't ever use them, so hence this kernel
[Galaxy Tab S Original Android Development] :
Flashing is fixed along with disabling buttons when sofkeys are on.
[Galaxy Tab S Original Android Development] Gilg@mesh:
is it something wrong with the CPU frequency in performance settings? minimum CPU freq jumps up to maximum freq if I set maximum freq under 1200MHz. does it happen for anyone else?
[Galaxy Tab S Original Android Development] :
OK. It's not fixed:

If you check the checkbox, everything is fine and seems to be fixed. Tab went stand by and no flashing is visible. After first wake up buttons are active again and flashing after next wakeup. If you go to to settings again and uncheck and recheck softkeys everything is fine... ...until next wakeup... :(

---------- Post added at 12:50 PM ---------- Previous post was at 12:43 PM ----------

When I set Max to 800 Min stays at 250. Current goes down to 250 after some seconds of not touching. Does this answer your question? I'm on 20141106-UNOFFICIAL-nvertigo.

[MENTION=535343]all[/MENTION]: Please always give exact build and kernel (if you flashed other then in build included kernel) when reporting issues. Thanx.
[Galaxy Tab S Original Android Development] Poser:
Is anyone else having issues with tab idling @ 250mhz, but not dropping into deep sleep?

11/01 build. Barracuda cap disable ver 2 flashed.

Edit: also Great Job guys...deving for exynos is no easy feat!
[Galaxy Tab S Original Android Development] Robin M:
Thanks. Hopefully you meant "TWRP 2.7.1.1 or later". I'm using TWRP 2.8.1.0. Now using latest version of chainfire SuperSU, flashed along with yesterday's update.

Line in platform.xml may no longer be an issue. Did not add the media group after yesterday's update. Root Explorer and DropBox are writing to the SD card with no problem now. Will let you know if that changes. Will try a clean flash with TWRP later today, and let you know about the permissions.
[Galaxy Tab S Original Android Development] hurray:
[MENTION=3051725]Robin M[/MENTION]: I have problems with TWRP 2.8.1.0 and writing backups on the external sdcard. I am back on 2.7.1.1 which runs stable and fine even with exfat formatted sdcards.

[MENTION=4193974]Barracuda77777[/MENTION]: thanks for the new build and the non capacitive kernel. Everything went fine and runs good. :)
[Galaxy Tab S Original Android Development] Robin M:
Hmm... OK, I'll try to find a copy of 2.7.1.1 before flashing new update. Thanks.
[Galaxy Tab S Original Android Development] :
To my knowledge flashing with 2.8.1.0 is ok - but in the process of developing I need reliable backup/restore. Therefor I stayed with 2.7.1.1 and encourage other people to do so. Remember: I consider this rom beta!

Question: what is the advantage of 2.8.1.0? Do I miss a superduper impotant feature when using 2.7.1.1?
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Some people are having problems with the latest version. 2.7.1.1 was the build that everything worked perfectly for them on like me. If you can backup everything and restore everything ok then use the latest one. If not 2.7.1.1 might fix the problem. Hope this helps
[Galaxy Tab S Original Android Development] Retiredfinally:
Running the 11/05 build and with the new gmail it crashes when attempting to send an email, anyone else having this issue? Not sure if it is ROM or Google.
[Galaxy Tab S Original Android Development] danny19901:
Where did you get your gmail from also do you have a theme that tries to theme it if so that causes it but I have T705 and had no issues with it using CM11

TAPATALKED WITH MY TAB S 8.4

My Z3 app Ports to all devices
[Galaxy Tab S Original Android Development] Retiredfinally:
Just wiped dalvik and cache and all is good! Thanks
[Galaxy Tab S Original Android Development] gsxrfl1k6:
USA I assume.
[Galaxy Tab S Original Android Development] Robin M:
Short answer.... NO. You do NOT want TWRP 2.8.1.0. Stay with 2.7.1.1. (Mostly, they've added MTP and adb support according to the change lists here. But the newest version may have problems writing to the external SD card on our device.)

Long answer... See hurray's post# 269 quoted above. First thing I did was check that out and do a fresh Nandroid BU. Hurray was correct. TWRP 2.8.1.0 created a folder on my SD card but would not put anything in it. There was no problem backing up to Internal Storage, however.

So... I went looking for TWRP 2.7.1.1. I got ahold of the wrong version (lt03wifiue), and as soon as I tried to boot into recovery, device locked on boot. Reset the battery (with the 4-button method) and still it got stuck. No way I could get it booted again, except into odin mode. What a day I've had. Had to go back to stock firmware, then re-root. Then, originally thinking I did something wrong in odin, I flashed TWRP again and the same dang thing happened. (Yeah, I know. Stupid thing to do.) Reloaded stock firmware again, and re-rooted again, but THIS time, I flashed CWM v6.0.5.0 for chagallwifi, and that seems to work OK. But I don't see a way to access the External SD card at all with CWM, and with a 16g device, that won't do.

So.... Finally, I found TWRP 2.7.1.1-chagallwifi on goo-im. Flashed that and rebooted into recovery with my fingers crossed. It worked. And, like hurray says, it does indeed write to the external SD card - even with stock Samsung firmware (which blocks write access to SD card from many third party apps). So, six hours later, I'm finally ready to clean-flash the latest update to this ROM. (But I learned a hellava lot today! :good: )

BTW, if anyone is looking for TWRP 2.7.1.1-chagallwifi (the correct version for this ROM), here is a link to it.
[Galaxy Tab S Original Android Development] Robin M:
Nvertigo,

OK, I just did a "clean flash" of this ROM (11/7 update from Barracuda). I was coming from a fresh re-install of the stock firmware (as per the above post).

Everything

was wiped except internal storage partition and external SD card. Here are the answers to your questions....

I am now using TWRP 2.7.1.1-chagallwifi, and latest version of chainfire's SuperSU.

Immediately after flashing ROM and BEFORE flashing gapps, all the permissions in the etc/permissions folder were 0644, as you expected.

Immediately after flashing gapps (the file that is linked in the OP), and SuperSU, all the permissions in the folder are now 0755. :eek: I did absolutely nothing in between. Both checks were done with the "File Manager" app that is included in the ROM. I don't know why this happened, but I will point out that the two extra execute permissions do not seem to be causing any sort of problem.
[Galaxy Tab S Original Android Development] :
Great job of researching!

I the updater-script I found this:

set_metadata_recursive("/system/etc/permissions", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");

So I was right: you fired chmod -R uninteded... ;) SCNR

I don't know, why this package changes permissions, and if it's done by intend or accident. I use BankS gapps minimal. That package does not change permissions on /system/etc/permissions. But let's lool at it in a pragmatic way: if everything is working. - it doesn't matter...

As for the gapps from BankS: he has closed his thread. So I don't want to put my copies out for download. But you can find the files, if searching with google. B.'s minimal is VERY minimal (I like it!) So I've to flash Calendarsync and Browsersync inmaddition. Theses are the filenames you can search for:

7-29_GApps_Minimal_4.4.4_signed.zip

7-15_AOSP_Calendar_Sync_4.4.4_signed.zip

7-15_AOSP_Browser_Sync_4.4.4_signed.zip

But as I stated above: if everything is working - then everything iis working... ;)

---------- Post added at 07:10 AM ---------- Previous post was at 06:58 AM ----------

Look in yout wifi advancednsettings on tab. Set region to the region yoir router is using. Some frequencies availible in Europe are not availible in USA and vice versa - so if your router is in auto-select-frequency-mode it might tx on a frequency that your tab can't see, if the region settings missmatch. USA and Europe aremonly exsamples - other region mismatches can lead to the same problem.

So: check tegion settings on router and tab.

All I can state i my asus rt-ac66u is working with my chagall like a charme on 5GHz and 2,4Ghz - both on ac. Same with my manta (n10), but of course only n. For the record: ac is NOT! faster then n. But this is the same on sammy.
[Galaxy Tab S Original Android Development] Barracuda77777:
New nightly build

cm-11-20141108-UNOFFICIAL-chagallwifi.zip

removed ANT+ suppport because it was causing lockups and freezing.

updated Cm sources

new Kernels in Post #2

added 3 extra CPU Governors.

Happy Flashing
[Galaxy Tab S Original Android Development] YusSuF15:
Thank you man

very good
[Galaxy Tab S Original Android Development] Crimsonthunder:
Delete...
[Galaxy Tab S Original Android Development] hurray:
The new governors are selectable but the feature to adjust min/max cpu-frequencies are gone and the the two fields are gray. That's no problem I only want to give feedback. :)
[Galaxy Tab S Original Android Development] YusSuF15:
back after test

is faster thn stock but

battery life bad Screen time 5 hr

the stock 7 hr Screen time

I Don't know way mabe the krenl bad

can u fix that

thank you .
[Galaxy Tab S Original Android Development] suzook:
Thats the price you pay, for aosp. Its not that much of a hit. Well worth it imo.
[Galaxy Tab S Original Android Development] reubenskelly1992:
With tweaking you can get better results
[Galaxy Tab S Original Android Development] danny19901:
Sorry to bother you but what does ANT+ bring in sorry but noticed it in stock as well but when reading what it does like heart rate reading etc... I didn't see anything like that in stock ?

TAPATALKED WITH MY TAB S 8.4

My Z3 app Ports to all devices
[Galaxy Tab S Original Android Development] codeman05:
1108 build is working well for me so far...finally motivated me to Root this tab.

Thank you for your work!
[Galaxy Tab S Original Android Development] Robin M:
Right - no need to worry about it. However it is Interesting! Since the line of code is in the installer script on that gapps file, my bet is that it was intentional - maybe having to do with a "workaround" to overcome Samsung's strategy to limit write access to the external SD card in Android 4.4.x. Maybe one or more of the apps needed the additional permission to work properly. I read that Samsung is limiting external write access because they say that future releases of Google are going to be heavier into multi-user formats.. The reasoning supposedly is that allowing third party apps to write to the SD card makes internal security [between users] hard to deal with. Dumb answer, if you ask me. First of all, there should be a better way to deal with security. And secondly, the whole multi-user concept on a tablet seems unnecessary. A tablet is nothing more than today's version of the PDA with a larger screen. Nobody really needs multi-user capability on a personal tablet or smartphone. That's what desktops and laptops are for.

On a related subject, this SD Card restriction is causing all sorts of problems for OEM software users on the Galaxy Tab S. That is why I originally added the "media group" permission in the platform.xml file. It did resolve the issue for some apps like Titanium BU and Root Explorer. DropBox didn't work at all, but Sumsung wrote their own version of it, and tied it into their proprietary file manager. HOWEVER, I am no longer adding that line now, and no longer seem to be having problems with any of these apps writing to the SD Card in current versions of this CM-11 rom.
[Galaxy Tab S Original Android Development] barth2:
I don't get why sd cards can't be treated like just another storage device. I mean if there is one thing Linux can do is mount devices. If they're concerned about security, just add an optional password when you stick in a card. I don't know how it's a bigger security risks than downloading random stuff from the internet which android is happy to let you do.
[Galaxy Tab S Original Android Development] Retiredfinally:
Wow, had some SD issues so formatted everything and totally reinstalled and what a rocket ship!!! Great job on this rom!!!!?
[Galaxy Tab S Original Android Development] codeman05:
Has anyone had any success with the Google Movies app?

Once I start a download, the app freezes up and FCs until I do a "Clear Data" on the app.

That's the only issue I've had so far with the 1108 build.
[Galaxy Tab S Original Android Development] Barracuda77777:
running perfectly here, I just started watching gravity which is free atm, no issues at all, playing in HD.

what gapps are you on? I am on CM official gapps
[Galaxy Tab S Original Android Development] codeman05:
I am using the CM gapps 20140606 from the OP.

I'll try a reflash and see how that goes. Thanks!
[Galaxy Tab S Original Android Development] danny19901:
I just got gravity on my T705 for free also play movies & TV doesn't fc or anything but won't load the movie at all but it may be my internet but its letting download it and its fast at downloading in HD quality

TAPATALKED WITH MY TAB S 8.4

My Z3 app Ports to all devices
[Galaxy Tab S Original Android Development] Barracuda77777:
try this for me please:

in twrp wipe:

system, cache and delvik,

then flash rom and then gapps.

cheers
[Galaxy Tab S Original Android Development] codeman05:
I have relashed the rom and gapps.

I can stream the movie fine, however if I try to download a movie...the app still freezes up.

Thanks again for the help
[Galaxy Tab S Original Android Development] Barracuda77777:
ok, it happened to me too when I tried to download, will look at logs.....

thanks for reporting
[Galaxy Tab S Original Android Development] andresv1989:
Is YouTube fcing for you guys??....flashed latest build with pa gapps
[Galaxy Tab S Original Android Development] Barracuda77777:
YouTube is fine, it's the first thing that I test :)

please try cm gapps,

look at post # 296 on how to flash.
[Galaxy Tab S Original Android Development] andresv1989:
I found another bug. For whatever reason when I try to screen cast with chrome cast it connects but it does not display i can only hear the audio. Any one else encounter this?
[Galaxy Tab S Original Android Development] Barracuda77777:
I am on 08 build, chromecast working no problems, tried it on my 2 chromecasts just to make sure.

can you try YouTube?

not enough power for chromecast?

can you connect the power with the adapter that it came with?
[Galaxy Tab S Original Android Development] andresv1989:
I am able to cast with Netflix and Pandora etc just fine but when I use cast screen it does not display anything.
[Galaxy Tab S Original Android Development] Barracuda77777:
I am surprised you were able to cast at all.

are you using a hack to see the chromecast?

my Tablet could not detect it, only through apps.

Nexus 5 worked picture no sound

Nexus 4 worked no issues

LG tablet. did not work

Xperia Z1 did not work

Tab S did not work

all running cm11
[Galaxy Tab S Original Android Development] jrock60:
mirror enabler apk available in xda will cast screen on most android devices via the chromecast official app. on cm the app offers the option to add the toggle in quick settings.

on a side note it works quite well on the tab s. the only issue i ran into and it was the same on tw, was that the mirroring does not fill the screen properly. it has black bars on both sides, i correct this by using a resolution changer app.
[Galaxy Tab S Original Android Development] andresv1989:
I use an app called mirror enabler ...I want to say it was working on earlier builds but I need to restore my backs up to verify.
[Galaxy Tab S Original Android Development] jrock60:
yes i checked and its a black screen. i have not used it in a while but it definitely worked on earlier builds of this rom.