yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] :
Thank you for finding this conjunction!

Now for the bad news: I can't do anything about it. We need this additional sysfs file to solve this - as described earlier.

I could remove the settings for activating on screen navigation bar.

[MENTION=4193974]Barracuda77777[/MENTION]: could you add "set language BEFORE flashing tc300k-less kernel" or something like this to your explanation in OP, please?
[Galaxy Tab S Original Android Development] hurray:
That is no problem at all as my workaround to manually disable the buttons is still working. So now I only flashed the pure Rom and made the changes per hand.

If anyone is interested in the workaround I can post it again.
[Galaxy Tab S Original Android Development] :
Would your workaround work if I disable the setting for onscreen navnar completly? I would really like to get rid of that second kernel!
[Galaxy Tab S Original Android Development] hurray:
I do not use the navbar settings from the settings-dialog. The app for the workaround I use makes a soft buttons nav bar at their own.

If you want I can test for sure a cm11 build for you where the navbar settings are disabled and give feedback.
[Galaxy Tab S Original Android Development] :
Sounds great - I'll come back to your offer.
[Galaxy Tab S Original Android Development] sirrkitt:
Hey! Thanks for pumping out this awesome ROM for us all!

Not sure if you want us to report any buggies or the such here or somewhere else, but the one weird bug I've encountered is that at my university we're using 802.11x for WiFi and the tablet seems to connect and authenticate to the network but then no packetes get sent out and it shows full bars of WiFi it just acts as though there isn't any internet access (and struggles to get an IP)

Lemme know if you want and dumps from my tablet and I can pastebin em
[Galaxy Tab S Original Android Development] :
Please check region settings in wlan/advanced.

If this doesn't help, switch off wifi truncate logcat (logcat -c), redirect logcat to file and start wifi. So we get mostly the relevant parts and (hopefully) not to much logging....

BTW: I hope you mean by x something like a/b/n/ac. Never heard of x before.
[Galaxy Tab S Original Android Development] sirrkitt:
802.11x is a security type. The wifi itself is fine but it isnt authenticating right on this ROM with Radius Servers
[Galaxy Tab S Original Android Development] Barracuda77777:
the user svardman in the T700 forum svardman has found a way to add haptic feedback to software nav keys, I have made a flashable zip to add the fix:

virtual_keys_fix.zip

[MENTION=4405529]nvertigo67[/MENTION] maybe we can add this to the rom by default?

cheers
[Galaxy Tab S Original Android Development] :
As long as we don't have the needes driver fix I'm planing to disable onscreen navbar in rom.
[Galaxy Tab S Original Android Development] Barracuda77777:
fair enough :)
[Galaxy Tab S Original Android Development] :
I have just looled in the zip. The change relates to sec_touchkey, which is in turn a file also (or better primely) used by capacitive buttons. What effect has this change on them? Has it any at all?
[Galaxy Tab S Original Android Development] Barracuda77777:
all it does is to add haptic (vibration) when you press on the built in nav keys that's all.
[Galaxy Tab S Original Android Development] :
OK. I'll add it. I. misunderstanded your first post: thought "softwate nav keys" was refering to onscreen navnar. I just didn't tealize you was refering to capacitive keys... Consider fix as added to next build. Thanx.
[Galaxy Tab S Original Android Development] :
First daily driver release: Build 1122

Build 1122

As stated I try to develop towards stability and useability, not towards features and speed. Fot those of you waiting for a SkyHigh kernel with all the settings, OV, UC I'be bad news: some of the kernel enhancements does not play nice with our rom.

But back to the new build: I've decided to take everything which is not fully supported by our rom out: last time I kicked tethering, this time I took out the on screen navbar (we are missing a sysfs interface to disable capacitive keys permanently while usimg onscreen navbar - the workaround with capacitive-keys-driver-free kernel broke language settings; so it was time to get a feature we can't completly support out of the rom). But before you you cry: There will be an alzernative! Hurray will publish a step-by-step HowTo to get onscreen navnar and disable capacitive keys. So even without the setting in the rom you have the freedom to use what you want.

By cleaning out the rom this is the first time I feel able to recomment this rom as a true daily driver! (Of course this doesn't mean it's bugfree, but it's stable, fast, featurefull and usefull.)

Fixes:

haptic feedback on capacitive keys (thank you [MENTION=3430960]svardman[/MENTION] !)

fix capacitive buttons / fix broken languahe support by taking out setting from rom

New:

make kernel modular

add eseay to use /system/etc/init.d/01moduleload script (simply add module to MODLIST and execute script on shell or reboot)

make some fs (which are not needed for boot) modular and load them automaticaly on boot

added kernel support for nfs3 (not activated in 01moduleload)

added xpad.ko (not activated in 01moduleload)

MD5: a2d9452255998f455540ecaae3c789f2

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141122-UNOFFICIAL-nvertigo-chagallwifi.zip

Happy Flashing!
[Galaxy Tab S Original Android Development] Gilg@mesh:
[MENTION=4405529]nvertigo67[/MENTION] any news on MHL? :)
[Galaxy Tab S Original Android Development] Robin M:
Don't get any haptic feedback on capacitive buttons with 1122. ...unless I need to turn that on somewhere. Nothing under settings- buttons. Thought maybe settings- sound -system-vibrate, but that doesn't work either. (Did not wipe data on flash.)
[Galaxy Tab S Original Android Development] :
No. I would have mentioned.

---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------

It is settings->sound->vibrate. And it works here. It's very soft compared to my i9300 (s3 phone) but it's there.

Please take a look at /system/usr/keylayout/sec_touchkey.kl should look like this:

key 158 BACK VIRTUAL
key 254 APP_SWITCH VIRTUAL

BTW: when first tested tnight I was in my quiethours and had disabled vibrate... ;)
[Galaxy Tab S Original Android Development] naomile:
[MENTION=4405529]nvertigo67[/MENTION] is XBMC work now with the new version? Thanks
[Galaxy Tab S Original Android Development] :
ieee 802.11x is not existent. Sometimes it's used and refers to ieee 802.11a/b/n/ac.

You are speaking of ieee 802.1x. That's a authentification/encryption standard relying on radius. I have no chance to test it here, but googling "wifi radius android" brings up quite a lot information. Quite a lot people seems to have problems setting this up. Perhaps you try.

---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------

No. I would have mentioned.

Why you guys think there is no mention of xbmc, mhl or "can make espresso (barista system service included)" under "Fixed" or "New"?
[Galaxy Tab S Original Android Development] suzook:
LOL, Thats great. BTW, Great build. So now we move to CM12???;)
[Galaxy Tab S Original Android Development] :
I'm away from home from November the 30th till 2nd week of January. Due to 3g connectivity I'ber no acces to my development host. When neein back I propably start on cm12. But I've always said: let's wait for M1 or M2 at least before porting. (Yeah, I've,seen the smiley, but I just want to inform you all, why there won't be new builds in December - and your post gave me a nice opportunity to do so. BTW: that's the reason why my first priority at the moment is stability.)
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Newest build works and is all smooth. Haptic feedback works OK but the light in the keys stays on a bit longer when touched. Doesn't bother me as it looks better like this. Other then that everything is good.

Edit: nvm you can change it in the settings I think. But everything is stable.
[Galaxy Tab S Original Android Development] Robin M:
Hmm. . sec_tyoughkey.kl is as you described above. Settings->Sound->System->"Vibrate on Touch" is checked. Quiethours is disabled (for now). Problem is, I do not seem to have ANY haptic feedback on anything - not even the AOSP keyboard when that setting is turned on. Is there a system file I can check for total lack of haptic feedback?
[Galaxy Tab S Original Android Development] tahlsr:
nveritgo67, thanks so much for the update.

If anyone else has a wired xbox 360 controller and a usb otg cable or adapter, please chime in:

I just updated to the 11/22 build.

I edited the 01moduleload file line:

MODLIST="cifs f2fs fat msdos ntfs vfat" to

MODLIST="cifs f2fs fat msdos ntfs vfat xpad"

I then restarted my tablet.

I plugged in my xbox controller via my usb otg cable and get the blinking green lights on my controller as expected but no control with the gamepad.

Anyone have any thoughts on what to try or do next? From some online searching, I did open a terminal emulator prompt and ran lsmod and one of the lines of the output says:

xpad 7546 0 - Live 0x00000000

so I think it loaded properly.

Loving the rom either way!!!! Thanks.
[Galaxy Tab S Original Android Development] :
AOSP Keyboard haptic setting is independent from the system->sound->vibrate setting. Sounds wired. From what rom do you come from? Does vibrate worked there? Frommwhat you describe I would suggest a clean install - but if vibrate never had worked it could be hardware... :(

---------- Post added at 09:54 PM ---------- Previous post was at 09:41 PM ----------

I wasn't sure if xpad.ko works standalone, therfore I asked you some days ago. Propably you need some more modules, like hid-somthinggampadrelated.ko... You said, someone else said that xpad.ko is sufficient. If you need an other kernel module let me know. Your diagnostic conclusion is right: module loaded properly.
[Galaxy Tab S Original Android Development] tahlsr:
Thanks so much for the awesome ROM, support and responsiveness. I'll do some more digging and see if I can find anything.

It looks like we might need: ff-memless.ko I found that info here: http://xdaforums.com/showthread.php?t=1692368

I didn't want to download the one on that page as I think it needs to be compiled for our kernel?

Also here is a link where they mention joydev.ko and gameport.ko as well but I'm not sure if that's for other gamepads or whatnot. http://www.freaktab.com/showthread.php?14395-S802-Xbox-support-installer

Happy to test out anything to assist.

Let me know your thoughts if you can. Thanks!
[Galaxy Tab S Original Android Development] Barracuda77777:
I have made a kernel for you to test with XBOX gamepad support:

chagall_T800_xbox.zip

can you flash and report back if it works?
[Galaxy Tab S Original Android Development] tahlsr:
You are amazing. I will have to try tomorrow morning. Having a housewarming party and have to go help out. Can't wait to try it.
[Galaxy Tab S Original Android Development] Robin M:
Thanks. Came from rooted stock. I think it worked then, but I have a nandroid of it, so I'll go back and test. If that works, I'll come back and do a "very clean" install.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
After testing the latest build of today there's a couple bugs. When you touch the screen or press the home button, the backlight of the hardware buttons turn on. And also haptic feedback vibration is a bit to high. Perhaps lowering it down a bit when it's pressed? Other than that I get 8 hours screen on time on till it reaches 2 percent vs stock rom gets 8 and a half hours. So not that much of a battery change but everything else is smooth and no overheating problems! Hope this helps!
[Galaxy Tab S Original Android Development] :
Hi Robin,

dirty flashing from other roms doesn't work. I you com from stock you have to clean flash.

[MENTION=4193974]Barracuda77777[/MENTION]: Hey Mate, I think we don't have this in long flashing text. I have not thought of crossflashing from other roms, when writing that. Would you be so kind to add something like this, please:

"Always do a clean flash when comming from other roms or versions:

Stock -> cm-11.0: clean flash

Build 1116 - -> Build 1122: dirty flash should be sufficient"
[Galaxy Tab S Original Android Development] Barracuda77777:
I added it to OP, and also to to post #3.
[Galaxy Tab S Original Android Development] :
Turn on backloght of capacitive buttons on screen- or home-button-touch is not a bug, but a "feature". I don't like it, too - but it's the way cyanogenmod implemented this. It's the same on my i9300. I've disabled capacitive buttons backlight for that reason. Sorry. (Digged here for two days to try to implent in cm11 - with no success.)

Haptic feedback: that's strange. My hapticfeedback feels a little to low. Our sysfs vibrator interface does not know about different settings (on i9300 there is a slider setting for haptic feedback, but the sysfs has more files. On my manta (nexus 10) I also have no setting for vibration strength, so I think it's hardware or driber related, and I don't know how to change it). What's really strange: my vibration is to low - your's too high, so either we both feel different, or it vibrates at different strenghts...!?! From whatmrom do you come? Clean or dirty flash?

Batterydrain: of course it depends on use case. But if you go to accounts and disable everything you don't use (i.e. in google I have only calendar, contacts and notes) and deinstall all system apps you don't use (i.e. I use k9, busynesscalendar and nova; so I unstalled email, calendar and trebuchet) and set wifi to the safe power while active and to wifi on only when connected, you can get 3 -8 % more screen on time.

---------- Post added at 08:09 AM ---------- Previous post was at 08:07 AM ----------

Thanks man, you are so fast...

---------- Post added at 08:19 AM ---------- Previous post was at 08:09 AM ----------

[MENTION=288006]barracuda[/MENTION]: Thank you! Again: youre are so fast...

[MENTION=673371]tahlsr[/MENTION]: If you test this kernel delete all modules from /system/lib/modules and /system/init.d/01moduleload. Othewise you mix a nonmodular kernel with the module loading mimik from the rom.

Instead I would like you to wait. I will make the modules you mentioned and we checkoit which we really need.

Give me about an hour.
[Galaxy Tab S Original Android Development] :
ff-memless is stativally build in our kernel. gamport.ko itself is the base for gameport 15-pin adapters like the ones you find i.e. on Soundnlaster Cards (if you have foumd an pci slot on chagall plesase let me know *kidding* SCNR).

joydev.ko makes joysticks/gamepads accessable via /dev/input/j*, so I think thats the one missing. Attached you find a twrp flashable zip with kernel and modules: xpad.ko is modified (included now forced feedback and something about LED) and joydev.ko (OT: funny name... ...joydev is hotplugable... ;) ).

Edit 01moduleload, reboot to recovery, flash attached zip and boot to system.
[Galaxy Tab S Original Android Development] :
Double post due to sh#!! g3 conectivity deleted. Sorry.
[Galaxy Tab S Original Android Development] Robin M:
I know. Didn't mean to imply otherwise. I meant that I "dirty flashed" from build 1116 to 1122.
[Galaxy Tab S Original Android Development] :
I'm confused. You answered my question from what rom you came one page back with "from rooted stock". Now you say you came from 1116... I this confusion I recommend doing a clean flash...

EDIT: Kidding: Maybe you have a memory CRC-Error... ;)
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
I came from stock rooted rom. Did a clean flash and flashed gapps and supersu. Like when I press the menu or back button, I can tell its slightly higher then stock. Usually its close to the lowest vibration setting but a bit higher. Idk it might be how we feel it differently? And thanks for the battery tips!
[Galaxy Tab S Original Android Development] tahlsr:
Thanks for making this .zip

I edited 01moduleload and took out the xpad entry, rebooted to recovery, flashed and booted to system.

It didn't seem to enable gamepad support. I checked that the flash worked by seeing the new files in system\lib\modules.

I opened a terminal emulator and ran lsmod and didn't see an entry for xpad or joydev.

For kicks I edited 01moduleload and added them and rebooted but the gamepad still doesn't seem to work.

If you have any thoughts, let me know otherwise I may try Barracuda77777 's kernel that was posted.

Thanks again for all your help guys.
[Galaxy Tab S Original Android Development] :
Open shell, there type:

su -

/system/xbin/modprobe joydev

/system/xbin/modprobe xpad

/system/xbin/lsmpd

This way I checked if the modules load before posting the new zip. Do the others modules load? Just not xpad an joydev? Typo? Forgot doubble quotes?

Yo can try barracudas kernel, but my builds will be in futre with modular kernels - so you must always remember not to mix and not to try loading modules in barracudas kernel...

Oh, I reed again.To load xpad and joydev BOTH must be IN 01moduleload of course. My kernels will always be modular from now on. Every module must be loaded by init.d script or by hand - see above.
[Galaxy Tab S Original Android Development] :
New Kernel: v3.4.104 based on NJ2

I found newer Kernel sources: NJ2 from opensource.samsung.com. It hasmminor updates to net and futex. I has also updated mali400 drivers. I don't understand the latter: exynos54xx has mali6xx, so this is not for us.

I based NJ1 on regular kernel tree (www.kernel.org) v3.4.39 and merged every single tag from v3.4.40 to v3.4.104, so we have now a kernel v3.4.104 based on sammys NJ2. You can find this in my git: https://github.com/nvertigo/android_kernel_samsung_chagallwifi Branch: my-work-update.

Who does not want to wait for next rom build can flash attached zip. It's modular and has xpad and joydev.

Happy Flashing!
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Here is how much battery life I get if anyone wonders if battery life is different from stock. Basically the same a bit more since there's no Samsung crap on it. 8 and a half hours screen time on. For me to get a bit more was draining battery and recharge it to 100% completely. Took me 2 tries but managed to get it to work. Sorta like a recalibration? Also used greenify, WiFi optization on. Hope this helps anyone.
[Galaxy Tab S Original Android Development] UpInTheAir:
I had also DL the source last night, but might not have much time this week to look at it. I'd like to know what's relevant for the 8.4 and what's common. Did a quick diff, but no time to study it or merge/patch yet.
[Galaxy Tab S Original Android Development] reubenskelly1992:
I find this Rom much smoother than touchwiz. But I do miss multi window. Is there a good alternative app or workaround.? I've tried a couple but they don't cut the mustard
[Galaxy Tab S Original Android Development] Robin M:
No, no DMA-related CRC error. Just a minor transmission glitch. ;) Didn't completely understand your question. I ORIGINALLY flashed. CM11 from a clean re-installation (and re-rooted) stock ROM. But that was a few weeks ago, and of course involved all very clean flashing. But just the other day, when going from 1116 to 1122, I didn't wipe Data. After current Thanksgiving holiday (here in US), I'll investigate current haptic feedback problem in detail, as now you've got me curious to know if I've always had it, or when it showed up.

FWIW, one of the things I'm thankful for this Thanksgiving is your (and Barracuda's) work on CM11 for this Samsung Tab S. Not rushing you at all, but at some point, whenever it's ready, it will be exciting to see Android LP (CM12) on this tab.
[Galaxy Tab S Original Android Development] :
Thankmyou for your kind words.

I will publish a maintainance build with the new kernel the next days before leaving home for a couple of weeks (which implies I can not access my development host). Perhaps you will wait for next build. On the other hand it will have no further fixes or features - just repo sync and kernel 3.4.104.
[Galaxy Tab S Original Android Development] tahlsr:
Thanks. I installed the new latest kernel, loaded the ko files manually using your commands above and the gamepad is still not detected. lsmod does show they are loaded. Maybe it's not a software issue.

The micro to usb cable I'm using works with other devices like a thumb drive so I think that's ok.

The xbox 360 has a wired and wireless controller. Technically I'm using the wireless controller plugged in. Not sure if that should matter though.

Thanks for all your help so far. Maybe this device just doesn't power it properly or something.
[Galaxy Tab S Original Android Development] jodvova:
Hi,

Im using your 22/11 driver build and have one question.

How can i disable hardware buttons ? So when i press on them nothing happens ?
[Galaxy Tab S Original Android Development] pingtiao:
I use tasker and xposed gravitybox to switch off the hardware buttons and enable expanded desktop whenever the device is rotated into portrait mode. Details on request!
[Galaxy Tab S Original Android Development] Jason761:
Is this working on 32gb version?
[Galaxy Tab S Original Android Development] :
Don't know the specs of 32Mb version. I the ONLY DIFFERENCE is larher DATA partition it works - if SoC differs it won't.
[Galaxy Tab S Original Android Development] hurray:
Howto deactivate the capacitive buttons

For those who are also do not want the capacitive buttons anymore I have a workaround:

Step 1:

- reboot into recovery and flash the appended "virtual_keys_disable.zip"

Step 2:

- Install GMD Auto Hide Soft Keys ★ root

- Open GMD Auto Hide Soft Keys (give root-access if prompted)

- Under "General" set "Device Has Soft Keys" and "Start On Boot"

- Under "Trigger" set "Hide in Fullscreen"

- Under "Quickbar" set under "Look & Feel"-"Theme" a Theme of your choice (I set "Galaxy")

- In the upper right corner set Service to "On" and enable Notification

- Now you have a hideable Navigation Bar which does not make your screen smaller and the original capacitive buttons are disabled as well. :)

I made the appended zip quick & dirty and test it on my T-800, so any feedback is welcome. :)

Edit: Please use "virtual_keys_disable_v2.zip" as there was a typo in the first version.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Usb debugging seems to be not working on nov 22 build. Tryed kies and kies 3 but doesnt connect. It dectects that is connected but never loads. Odin works fine i believe.

Let me try a few things to make sure its not on my pc that the probelm is at. Worked fine when i had stock rooted rom.

Edit kies still saids unsupported device on both 3 and 2.6. Does it have to do something with cm11?
[Galaxy Tab S Original Android Development] ramiss:
Yes. I have tried almost every kernel and rom in this forum built for the S 10.5 on my 32gb version. Everything works.
[Galaxy Tab S Original Android Development] suzook:
Would kies connect when running cm??? I dont think it would.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Lol i did some reasearch. I think it doesnt work running cm11. Atleast odin works!
[Galaxy Tab S Original Android Development] suzook:
Kies is for samsung touchwiz, thats why it wont connect.
[Galaxy Tab S Original Android Development] SmooK_LV:
Yeah, I've been using the GMD Auto Hide Soft Keys since I flashed this ROM - makes life so much more easier. Thanks for sharing with others.
[Galaxy Tab S Original Android Development] Retiredfinally:
Works on my 32gig just fine
[Galaxy Tab S Original Android Development] Gilg@mesh:
tried that but the buttons is still working
[Galaxy Tab S Original Android Development] javichulo:
thanks so much for this ROM. my tab S was collecting dust, was about the sell it then saw this and it rocks. I would call v 1116 a daily driver