yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] :
I'm glad my finger crossing has helped to get yoir ne device to you... ;)

Everything is totally understandable. I myself wouldn't take my hands of aa mew toy (as proofed in the last 4 weeks...). And developing for a device I have no access to is completly out of my scope.

Thank you very muchfor your offer. I will look in your source in a few days - at the moment I'm fighting with migrating /system to f2fs. If I manage to build your kernel for our device, i would build it seperatly to have a reference and a SkyHigh kernel for flashing independently of rom-kernel. Of course all the credits go to you!

Before asked for an ETA: it's another "time will show".

Have a fast (5433!) time of fun and thanx again,

Nvertigo

---------- Post added at 07:58 AM ---------- Previous post was at 07:38 AM ----------

Missing driver I think. I was thinking of making the roms kernel modular and add some device drivers. But thats very low on my priority list. Do you know which driver/drivers are needed for xbox-controler?

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

Capacitive Buttons: the "recent apps"- and "back"-buttons below the screen.

Softkeys: the on screen navigation bar buttons.

I can configure backlight for capacitive buttons in settings->buttons->backlight (disable/enable, durationmfrom 1 to 5 seconds) It's disabled if you are using sofkeys (remember to flash kernel to disable capacitive buttons permanently).

Can anyone confirm backlight settings for capacitive buttons are available, please?
[Galaxy Tab S Original Android Development] UpInTheAir:
In my kernel, I implemented F2FS but never tested........ Apart from source changes and enambling in defconfig to compile, I also aded a script run from ramdisk /sbin/mount.sh . Can't remember where I got the idea from, but I adjusted to suit.

#!/sbin/busybox sh

mkdir /dev
mkdir /dev/block
mknod /dev/block/mmcblk0p18 b 259 10
mknod /dev/block/mmcblk0p19 b 259 11
mknod /dev/block/mmcblk0p21 b 259 13

#Trying to partitions mounting etc

mount -t ext4 /dev/block/mmcblk0p19 /cache
if ! grep -q /cache /proc/mounts ; then
echo "mounting /cache with ext4 failed, trying f2fs..."
mount -t f2fs /dev/block/mmcblk0p19 /cache
fi
mount -t ext4 /dev/block/mmcblk0p18 /system
if ! grep -q /system /proc/mounts ; then
echo "mounting /system with ext4 failed, trying f2fs..."
mount -t f2fs /dev/block/mmcblk0p18 /system
fi
mount -t ext4 /dev/block/mmcblk0p21 /data
if ! grep -q /data /proc/mounts ; then
echo "mounting /data with ext4 failed, trying f2fs..."
mount -t f2fs /dev/block/mmcblk0p21 /data
fi

# remount partitions with noatime
for k in $(mount | grep relatime | cut -d " " -f3);
do
mount -o remount,noatime,nodiratime,noauto_da_alloc,barrier=0 $k
done;

and from

ramdisk init.universal5420.usb.rc

on fs
mount_all /fstab.universal5420
[COLOR="Red"] exec /sbin/mount.sh[/COLOR]
setprop ro.crypto.fuse_sdcard true

Maybe help, maybe not.
[Galaxy Tab S Original Android Development] :
[...] code deleted

Yeah, thats a great idea.

At the moment I'm fighting twrp (build from source) to first support f2fs at all; and second to get it to mount and backup either ext4 or f2fs. I belive if I've hunted down the first your mount script will propably solve second. Thanx, man!

I want a migration path without loosing data on /data... so backup/restore has to work on both fses...
[Galaxy Tab S Original Android Development] Robin M:
Nvertigo,

Thanks for your reply. I can confirm that in 1115 settings->buttons->backlight, you can disable/enable and configure the duration from 1 to 30 seconds or "on all the time" (which is an improvement over 1 to 5 seconds).

I misunderstood when you said "configure the backlight". I was looking for a way to make the capacitive buttons dimmer. I like to use the hardware capacitive buttons, but they are too bright. The high brightness is distracting. The on-screen softkeys are much less bright. Is it possible to make the capacitive buttons dimmer (like the softkeys), OR... make them stay on very dim when they "go out", so you can find them? (Either way would work.)
[Galaxy Tab S Original Android Development] :
"dimm" values are only 0 or 1. As far as I know this is the way the hardware is designed and not a limitation of cm. At least the sammy supplied tc300k driver is only capable of 0 or 1. As far as I remember this isn't possible on sammy factory rom. I may be wrong, but with this kernel sources we can only have the backlight off or on.
[Galaxy Tab S Original Android Development] tahlsr:
Thanks so much for your reply.

Another xda forum post said something about:

..there is no xpad.ko kernel module. Ask the ROM/kernel developer to compile it.....

I hope that's useful information to you. If not, let me know if I may be of assistance with any more searching. Here is a nexus 5 forums search with the keyword 'xpad.ko' http://xdaforums.com/search.php?searchid=319953483

I understand this is totally low priority and I have no expectation of it getting included. Just figured I'd mention it since I noticed it.

Thanks again for all your hard work. It's appreciated!
[Galaxy Tab S Original Android Development] Robin M:
OK, I understand. Thank you for looking into it. I wasn't using the original software long enough to really notice before moving to this ROM.
[Galaxy Tab S Original Android Development] :
Fair enough - that's a really good reason... *lol*
[Galaxy Tab S Original Android Development] maxrdlf95:
Link for latest build is down:(
[Galaxy Tab S Original Android Development] Barracuda77777:
I will mirror it on android file host soon, we must have ran out of bandwidth or need to restart server.

Edit:

mirror link is up. check op
[Galaxy Tab S Original Android Development] :
Will work on the hdmi issue. Had to get a cabkle first. Could you please give me the exaxt type/name of the cable, that worked on sammy rom?

But be patience - last days lots of real life thingsmleft behind, I had to catch up first. So hdmi is not my highest priority at the moment - but I wil dig into it later.
[Galaxy Tab S Original Android Development] Gilg@mesh:
EPL-3FHUBEGSTD, I use it myself

http://www.ebay.com/sch/i.html?_from=R40&_sacat=0&_nkw=EPL-3FHUBEGSTD&_sop=15
[Galaxy Tab S Original Android Development] SmooK_LV:
From what I've read, since Samsung uses different MHL version that is optimized for Sammy roms, it is not quite possible to get the MHL/HDMI cable working with CM11 on Tab S (or any Sammy device since 2012). However I might be wrong. Either way, Chrome cast does the job well.

Has anyone tried this on T805. I suspect mobile network connectivity won't work, but what about everything else?

Thanks for the work man, I appreciate it - if there is any way I can help out - ask.
[Galaxy Tab S Original Android Development] johoja:
Hey were you able to test this cable with CM11 ROM on the T800 ?

What were the results ?
[Galaxy Tab S Original Android Development] Gilg@mesh:
well I have a Galaxy S4 as backup phone with CM11 and the MHL cable I use on my T805 works w/o any problem, but can't say anything about CM11 on Tab S, would be nice to try it though, even though I barely use the mobile network on it at all it would be nice to have it working... but I guess I could try flash it on my T805 if it works?

no, I have the T805.

Tapatalked from my GALAXY S5
[Galaxy Tab S Original Android Development] johoja:
ChromeCast only works if you are on the same WiFI - etc when you are in hotels that's hard to do - and hotel wifi is horrendous as it is :)

I think it should be doable though - as the image, etc seems to be working the color just seems to be off for some reason with my dongle.

---------- Post added at 01:58 PM ---------- Previous post was at 01:57 PM ----------

Let me know if there are any logs I can provide in the meantime to help out.
[Galaxy Tab S Original Android Development] Gilg@mesh:
ok, I just flashed nvertigo67 lastest build on my T805 and it boots fine :D hopefully in future mobile network can be enabled for us with the LTE version
[Galaxy Tab S Original Android Development] :
Sammy is tricky - lte will obviously not work. Sound, Mic, Wifi everywere little difftences between the devices (even t700 and t800). So you can try, but don't be dissapointed. You have to change something in the zip. I belive suzook knows.
[Galaxy Tab S Original Android Development] Gilg@mesh:
see my previous post, everything is working except mobile network :D
[Galaxy Tab S Original Android Development] :
Wow - you see me surprised. But then you can take our gits to start off. I would start with s5 lte, and looking in the kernel source in arch/arm/condigs chagalllte_00_defconfig for differences to chagallwifi_00_defconfig these differences had to go to cyanogenmod_chgallwifi_defconfig - the merge is (of course) cyanogenmod_chagalllte_def_congig.

For them s5 device trees, thes are seperated in common and device specific gits. So it could be a good start.

---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------

You flash too fast for me to respond in time... ;)

---------- Post added at 07:44 PM ---------- Previous post was at 07:39 PM ----------

Thanx. Wouldmhave pressed the button but I'm limitted to 8 thanks per day...

I will look - have never used mhl cables so far, have to read first. Any pointers? Do they change the adapter and their software, or do thes change their cable,,their sw and their hardware onmthemdevice side? But as I said, now the rommis running I will slow down onmdeveloping.
[Galaxy Tab S Original Android Development] Gilg@mesh:
I just tried the MHL cable on my T805 (flashed with nvertigo67 build) and it works but I get strange colors here and there, also no audio to the TV only from the tablet...

here is two pics I took to show how it looks (in this case orange/yellow color)

http://i.imgur.com/pWlUf9z.jpg

http://i.imgur.com/97pvPdL.jpg

[MENTION=4405529]nvertigo67[/MENTION] other than that, great work guys.. I will run with this for a while (but would be very nice if the MHL/HDMI works 100%) if there is anything you need help with just ask :D I only use this tablet for watching series/movies, I don't use it for "everyday use" so I can experiment on it if you need it.
[Galaxy Tab S Original Android Development] hurray:
Try "External Keyboard Helper Pro". This app is worth its money. It can remap (special)buttons from an external BT-Keyboard as well as shown a dialog which input is to use if a BT-Keyboard is connecting or disconnecting. There is a testversion from it in the playstore too.
[Galaxy Tab S Original Android Development] johoja:
Yup I have the same issue with the colors/audio ! At least its consistent -- hopefully its doable/fixable !

---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------

Thanks for the suggestion I'll try it out - for now I"ve used a tasker profile - to switch the keyboard to 'null input' keyboard which is free - and used 'secure settings' to get tasker to be able to change the keyboard without any user input - seems to work great!
[Galaxy Tab S Original Android Development] SmooK_LV:
Oh, thanks for flashing. You've encouraged me to flash it myself.

And thanks for pointing out that MHL cable works for you. In many cases it doesn't, so it's nice to know that it's not dead end.

By the way, I have a MHL cable, but it seems to be little too sluggish, could you please check your HDMI connection info and see at what hertz are you running? Because I'm running at 30hz with bothersome delay and slowdown, as well as playback not being smooth. I want to understand if the MHL adapter I got is faulty or my t805 handles video streaming badly. Thanks.

For pointers, if you are ordering one, make sure it's 11pin MHL cable (often it's labeled For Galaxy S3/s4) 11pin one is MHL 2.0 if I'm not mistaken. As for what is in the config files, I'm not sure - last time I was configuring my unofficial port, I just tried getting everything to work - I managed to get it boot up, but nearly nothing (bluetooth, wifi, lte, camera) worked, not long after that I stopped developing it - it just came down to the lack of time. I hope you have better time doing it.
[Galaxy Tab S Original Android Development] luis250:
Very good rom

installed on galaxy tab s 32gb T-800
[Galaxy Tab S Original Android Development] Barracuda77777:
good to hear positive feedback about our rom :)

I will be making a second rom with the capacitive buttons enabled and the ability to switch them off, but will keep also the build with the completely disabled capacitive buttons for us who loath them :)

also I will be making a one off build for users on the T805 to enable Data for them :)

I have already ordered an MHL cable to try and fix the issue, in the meantime if someone can ask other users of the cm picasso or t900 users if their MHL is working, I remember from the i9300 days that sammy's mhl function needed proprietary stuff.
[Galaxy Tab S Original Android Development] Gilg@mesh:
thank you, I'm waiting for the T805 build :D that and HDMI fix and this will be awesome !!

about the MHL function, it does work on the Galaxy S4 with CM11, but maybe it's a different story?
[Galaxy Tab S Original Android Development] Barracuda77777:
should be up in about an hour.
[Galaxy Tab S Original Android Development] Gilg@mesh:
thank you, I edited last post about the MHL function.
[Galaxy Tab S Original Android Development] SmooK_LV:
Thanks.

I flashed this rom on my t805 and it runs great (A side from LTE, of course). Camera however doesn't seem to work - not sure why, maybe a faulty flash or something. As for the issue about on-screen keyboard not disappearing when a Bluetooth keyboard is connected, it seems that the device doesn't recognize the Bluetooth keyboard as a physical keyboard - not sure what config files govern this, but if it gives you an idea, then that's a start.

When the build is available for t805, is it going to be only a slight modification? I'm asking this because I would want to flash it over this rom as I've gone through the process of setting it up already. Well, I will appreciate it either way.
[Galaxy Tab S Original Android Development] :
Addedum to build 1115

I've forgotten to mentoon two changes I did on the last (1115) nvertigo build:

Also I have disabled tethering, 'cause it's not really of any use and not working on our 3g/4g-free device.

I have changed my build environment from oracel-java-1.7 to icedtea-7 (bootsttaoed and build locally on my gentoo system). Though cm build script is spitting warnings it builds just fine.

Added this information in #5.

For now I consider we have a working, solid and stable build. So don't expect any updates for the next days.

My f2fs project for this rom is on hold for now: it will break most flashble zips that expecting /system as ext4 and try to mount it that way - so the installerscripts on all had to be adjusted. So I decided, that the advantage of f2fs over ext4 seems to be not that significant to pay this price... (to be honest: it's no wow! and Ahhh! - it's more a marginal speed increase in normal use. I.e. rebuolding caches after wipe cache & dalvik seems to be faster by 10%. On normal use I feel no difference. And as stated before I give a s#!|| on benchmarks.)

I'm planing to make the kernel modular. For that reason I would like you to tell me what modules (read: drivers) you are missing. So far only xpad.ko is reported to be missing. So let's get a wishlist.
[Galaxy Tab S Original Android Development] hurray:
I flashed successfully the newest build (1115) with wiping system, cache and Dalvik-cache. Till now I see only one issue: I am not able to change the language anymore. The language-setting is grayed out or I get a FC from the whole settings dialog.

About the wishlist: I don't know if you want only "specials" as module but if not of course the exfat- and ntfs-support as module please.

And a CM11-version of UpInTheAirs kernel would be very awesome! :)
[Galaxy Tab S Original Android Development] Barracuda77777:
can confirm also that I am on 115 build too and I also get the force close if I choose language and input.
[Galaxy Tab S Original Android Development] salahfathi:
So sad here

Why the lte variant (t-805) is not supported in the development of this tab at all ?

Please I was waiting along time for cm release for my t-805

how i can flash these builds now without losing my lte or 3g connectivity ?

waiting
[Galaxy Tab S Original Android Development] UpInTheAir:
Buy the Dev's your device model. That should help immensely ;)
[Galaxy Tab S Original Android Development] salahfathi:
Thanks for your answer which is useless and sarcastic but Iam waiting for an answer from someone who is more respectiful
[Galaxy Tab S Original Android Development] :
I belive UpIntheAirs answer wasn't disrespectful - perhaps a littLe bit sarcastic. But it was funny... ;) At least it gave me a laugh...

On the other hand if you read the whole thread, you will realize that your "request" was answered before.

I won't develop for a device I have no hands on. I don't ask for giving me a chgalllte - I ask for respecting my decission. I ask for respecting my spatetime I invested by taking the time to read through the thread - all the answers to your questions are there.

And as stated many times before: feel free to use my gits toe make a build for t805.
[Galaxy Tab S Original Android Development] salahfathi:
Thanks for responding

but didint understand last line

what gits to use
[Galaxy Tab S Original Android Development] :
Ok, thats an issue. i just tries changing my language from German to English (Australian English of course!; ;) ) and it was working. I use a build I repo synced later 'cause of my testing with f2fs. The build itself has only initial f2fs support in kernel and recovery. So upstream changes could be one reason. The other reson could be, thats its time for a clean install: after softbricking my device several times through testing with recovery and modified fs on /system I decided to do a "very clean flash" (read posting #3).

Has anyone done a "clean flash" or "very clean flash" and has the same problems?

I changing languahe all running apps are closed. System-apps are restarted. User-apps restart as you use them. You aren't reffering to this effect but to force close of settings, aren't you?

Do you use AOSP keyboard (the one from the rom) or any other?

---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------

https://github.com/nvertigo/android_*_samsung_chagallwifi/

---------- Post added at 08:34 AM ---------- Previous post was at 08:28 AM ----------

I'm sure I'm missing something obvious (have a bad influenca at the moment and mind is real slow), but why do you think this is usefull?

My idea is: having a kernel with al the common essentials build in and some "exotic" rarely used drivers as module.

---------- Post added at 08:43 AM ---------- Previous post was at 08:34 AM ----------

In deed! Give me a little bit time. It's on my list. And belive me, if it was only compiling it, it would have been done... It's on my list. And I promise I won't forget it.

Let's get up a stable build everyone can use (and test) in a lomg term run, so we can be sure when testing SkyHigh and running in issues they aren't from the rom.
[Galaxy Tab S Original Android Development] Barracuda77777:
hope your flu is on the way out :)

I tested my device tree with the latest upstream commits and did not break the language selection, also the T700 that is based on your tree is also force closing on the language selection, so I think there is something in the device tree, I will go through your commits and compare with what I cherry pick and what not, I will hopefully catch the culprit for you.

and I fully agree with Nvertigo67 that it is a bad idea to develop for a device that we don't have, I have built for the T700 which I thought would be a walk in the park as it is very similar to ours, I already regret my decision, not easy :), but imagine doing a build for LTE which is a totally different and much harder to port to start with.

cheers
[Galaxy Tab S Original Android Development] :
Save your time. it's working with my 1116 build. i'm uploading. Think it's upstream - only difference between 1115 and 1116 is f2fs support (though not used) and repo sync time.
[Galaxy Tab S Original Android Development] Barracuda77777:
thanks that's great, did you change anything?
[Galaxy Tab S Original Android Development] :
This build I use at this very moment - and switching languagr IS working:

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

---------- Post added at 10:15 AM ---------- Previous post was at 09:45 AM ----------

Would you test the 1116 build, please?

Only change was putting f2fs support in recovery. It's build from my-work branch in device tree and my-work-f2fs in kernel tree. Only other difference I can imagine is my "very clean install" before installing 1116.

If 1116 is working for you it only can be a change upstream....

If you can confirm 1116 is working I will make the two kernel packages and adjust #5.

(OT: In i9300 device tree using navigation bar (aka softkeys) is all together disabled. I'ver thought of doinhnthe same on my device tree until we get the sysfs change in tc300k driver. Leaving this option in and providing a kernel for disabling capacitive keys while using softleys is only for you, my friend! 'Cause I know how you hate capacitive keys and don't want you to use duct-tape on them...:) )
[Galaxy Tab S Original Android Development] Barracuda77777:
Thank you :)

Downloading now, give me about 10 -15 minutes, and I will report back. its always easy to flash a kernel witht he tc300 driver disabled, so please don't worry :)

cheers

Edit:

confirmed language selection is fixed with the 116 build, already uploading to mirror site, will edit OP once done.
[Galaxy Tab S Original Android Development] :
Thanks for testing!

'Cause I'm 100% sure it's not the f2fs change (since this applys only to recovery-image and kernel), this must be a regression implemented and fixed upstream. "If debugging is the process getting errors out of the executable - coding had to be the process of getting errors in executables..." [author forgotten, but it wasn't me]

Will prepare the kernel zips and update #5.

---------- Post added at 11:21 AM ---------- Previous post was at 11:19 AM ----------

For the record - here's the original one:

“ If debugging is the process of removing software bugs, then programming must be the process of putting them in. ” - Edsger Dijkstra

---------- Post added at 12:01 PM ---------- Previous post was at 11:21 AM ----------

The Build from 201411116 is up in #5. There are also new kernel flash zips for disabling/enabling capacitive keys. I will remove the 1115 Build and kernel zips completly from the server to avoid congusion.

Happy flashing!
[Galaxy Tab S Original Android Development] eousphoros:
I love watching you guys progress even if you make me feel a little lazy in my own development process. Keep up the great work!
[Galaxy Tab S Original Android Development] :
Thank you for your kind words! But all this wouldn't have been possible without you doing the pioneer work (phrase????). Afew days ago I rebased my copied files cortectly. So my git reflects the way from klimtwifi over picassowifi to chagallwifi. Everybody who wants to take the time to look at will know. Thank you man and all the best for you pushing klimtwifi to cm12.

BTW: does a bt headset work on klimtwifi for voip or skype?
[Galaxy Tab S Original Android Development] eousphoros:
I haven't tested mic over bt, I'll flash my last public dev build and let you know.
[Galaxy Tab S Original Android Development] hurray:
[MENTION=4405529]nvertigo67[/MENTION]:

Now I have flashed the build 201411116. If I flash only the build itself I am able to change the language settings. If I flash the non capacitive kernel "chagall-20141116-wo-tc300k.zip" I cannot change the language anymore and the setting dialog crashes.

About the modules:

We mean the same, only exotic drivers build as module. As you write to make a wishlist this wasn't clear so I wrote down the very basic drivers. :)