yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] NoFaQ:
Have you tried flashing the zip from this post (http://xdaforums.com/showpost.php?p=62758656&postcount=1338)?

I was also have audio issues similar to yours, plus bluetooth audio sync would be off. After flashing that file, my issues resolved.
[Galaxy Tab S Android Development] pezley:
Anyone find the charging slow ?
[Galaxy Tab S Android Development] NoFaQ:
I don't notice any difference in the charging. But, I've always thought the charging was slow, even out of the box stock.
[Galaxy Tab S Android Development] dinekp:
Rom works flawlessly. Great battery. Three days already, no bugs found.
[Galaxy Tab S Android Development] :
New Build: 20150128

Finally I have fixed selinux for gpsd and init.d support (the latter was a really tough one - look at my git...)

For init.d I had to hack in the device's initing process to patch the sepolivy on the fly while device is booting. For that I had to use a program installed by [MENTION=631273]Chainfire[/MENTION]'s SuperSU. From now on my builds are again with selinux set to enforcing. Who wants init.d support (for auto loading modules) MUST flash SuperSU directly after flashing rom.

You can use the rom without SuperSU but with buildin superuser. gpsd will work. Indeed everything but init.d support will work. You just have to execute /etc/init.d/01moduleload and /etc/init.d/10systemtuning by hand: open a terminal and type:

su
/etc/init.d/01*
/etc/init.d/10*

after each boot.

Changelog and Announcment in OP follows tomorrow. I think I will slow down development for a few days: the basics are working: graphics, wifi, video (incl.myoutube and netflix), camera, gps... It's stable, responsibe and battery friendly, so it's time to take a break for me. The selinux was a hard fight with not enough sleep for me. Hope you understand.

Side note for devs using my gits: I will update current-12.0 in the next minutes. To get the branches together without having to revert some commits (which takes time, but more important: is not nice to keep the overview) I will push forced updates. That may break you local clones. If that happens (aka repo sync -d fails), do this from the root of your cm build tree:

find .repo/ -type d -iname \*chagallwifi\* | xargs rm -rfv
for d in device kernel ; do rm -rfv $d/samsung/chagallwifi ; done
repo sync -d

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150128-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5: 36bc597e89be0af6233abf4f4824bc69

Happy flashing,

NVertigo
[Galaxy Tab S Android Development] lionheartk:
Thanks nvertigo!

Clever way to fix it!

Seems that everything is working, rom is clean and stable, feels AOSP fast and stable but with all CM goodies!

Best LP ROM for chagallwifi today IMHO.

Can this build be dirty flashed over my last one or better to clean everything?
[Galaxy Tab S Android Development] Zootopia:
Could you or anyone please test Kodi for me?

If it works, I really gotta try this.

Thanks in advance for checking out.
[Galaxy Tab S Android Development] Bushcrafter:
Thanks again for all your hard work and time invested in this ROM. You deserve a break! We will see back here in a couple of days.Enjoy your time off. Keep you stick on the ice.:laugh::good:

---------- Post added at 03:30 PM ---------- Previous post was at 02:59 PM ----------

Nope it does not work. It loads up but nothing happens in main menu. None of the buttons work when you touch them.
[Galaxy Tab S Android Development] Zootopia:
Thank you so much bushcrafter. :)

Too bad... Kodi is essential to me.

Congrats on the job NVertigo, as I'm sure it delivers as reported here by a lot people. Maybe Kodi becomes compatible hopefully somewhere in the future, and then my time arrives.
[Galaxy Tab S Android Development] Bushcrafter:
Your Welcome!:)

---------- Post added at 03:58 PM ---------- Previous post was at 03:41 PM ----------

This new build seems a lot smoother than previous ones.:good: scrolling up and down on websites are a lot faster. I like it!:D
[Galaxy Tab S Android Development] texaspledge:
I use the instructions at this link to enable on screen buttons and disable capacitive keys. Then just go into settings and disable capacitive button backlight. Working perfectly for me.

https://brandtkrueger.wordpress.com...ation-buttons-on-the-galaxy-s3-requires-root/
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Flashed latest cm12 build. Everything is smooth and working as you said. Daily driver for me! BTW updated the mirrors. See post #1 and there should be a link to my mirrors :)
[Galaxy Tab S Android Development] :
Read OP and follow the given link. Or has xbmc.org has decided to follow the aosp touch api (since 4.4.4)?

EDIT: I explained it too often - but here we go again<.

I aosp (base for cm) the handling of touch input chanhed very subtile. To support xbmc/kodi and some games we need a difficult change in the kernel driver - it's out of my abillities to make this changes. I asked for help - many, many times. Nothing.

Just yesterday I linked again (cause of disable capacitive keys) to the thread I asked for help...

Again: I need help to fix it.

Why doesn't you go to xbmc.org and ask them to adjust their touch handling to the way 99,9 % of apps do?

I don't want to sound harsh, but I explained this so often, I say in OP xbmc isn't working, I link to the explenation and help request - and it comes up over and over again. What should I do? I'm not able to fix it without help - does anybody thinks asking over and over again will do something good, or help me in any way to fix it???
[Galaxy Tab S Android Development] Zootopia:
You know what?

I'm sorry, just read my previous post, and it didn't come out the way I intended really... What a prick! [emoji14]

You're right, you have mentioned it earlier, and I havê read it in the OP.

I'm kind of a newbie what it comes to development, só it just occured to me that maybe it was compatible already... But of course, it isn't, as you só patiently cared to explain... Again.

Don't get me wrong, I didn't want to sound disrespectfull or anything like that, as myself and certainly many others really appreciatte what you have accomplished so far.

Going to nag the Kodi boys now [emoji16] [emoji6]

Cheers nvertigo! [emoji106]
[Galaxy Tab S Android Development] :
One (or two ;) more word for kodi:

I really drives me crazy to know were the issue can be fixed, but beeing not aable enough to do so...

Sammy has implemented the synaptics driver in a way, that it is not possible to use the official synaptics driver updates (yeah, they provide complete sourcecode for linux/android - good guys and girls!). Sammy has even exchanged some kernel CONFIG_* variables compared to official android kernel source as well as compared to official synaptics drivers (again, they are very linux/android friendly on their synaptics_dsx driver).

I'm no friend of to put users off "wait for next release" etc. But I have a 50% hope, when it comes to the days sammy publishes source for a L kernel the synaptics_dsx driver will be updated also - if this will fix kodi issues? I don't know... :(

The best way to get this teally anoying issue fixed, is to find someone who is gifted in kernel hacking and can make the changes for us.

Perhaps you have realized in my first reaction on this topic: I'm very frustrated aboit this... :( I have to find back to the feeling of beeing proud to have fought down the selinux issues.
[Galaxy Tab S Android Development] :
Thanx. Have linked the article in OP as workaround.
[Galaxy Tab S Android Development] lionheartk:
Fast and stable here, just compiled and flashed :)
[Galaxy Tab S Android Development] Bushcrafter:
Yep this build feels a lot faster. It feels closer too baracuda77777 sweet ROM build! Keep up the good work guys!:good:
[Galaxy Tab S Android Development] lionheartk:
By what the benchmarks say at least, this rom is as fast as Barracuda's but without the bugs he didn't have time to fix.
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
I have a problem from installing apps from unknown sources. For example I downloaded a YouTube app from apkmirror and tried to install it. Then after hitting install it would say "app not installed" I then used the play store and it installed it just fine with no problems. I then transfered the same YouTube app (from apk mirror) to my phone and it installed it fine with no errors. So that meant the file isn't corrupted. I couldn't get a log cat as it wouldn't show up as I tried to install the app. I have reflashed and cleaned flashed again and same problem. Then I went back to stock rom and I can install apps from unknown sources ok without any errors and I even tested the same YouTube app from apk mirror and it installs fine. I am the primary user and have unknown sources on. Fixing permissions and wiping caches doesnt do it either.

So what could be the cause if the file isnt corrupted and works fine from the play store? Even using another app from apkmirror doesnt work either. Should I wipe /system and reflash? Thanks!
[Galaxy Tab S Android Development] lionheartk:
Try and make a log with catlog or logcat extreme, both set to DEBUG. If we can see the error happening it would help! I'll try to replicate it and log.

EDIT: Downloaded the newest Youtube app and others from APKMirror and they installed fine with no problems!
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Would this help? I believe its under package manager.
[Galaxy Tab S Android Development] Bushcrafter:
Yep,too bad about baracuda not being able too participate in this ROM build any more. How much faster is this latest build compared to the last one? Is there a fps apk that I can run while playing games like on a PC? I know,I know use the search button!:)
[Galaxy Tab S Android Development] begri:
I have charging problem as well...

The energy input is very low.

Other question is the inbuilt auto udate things work or I need to update through adb?
[Galaxy Tab S Android Development] calj17:
Could you please add T805 LTE RIL(provided by [MENTION=3788878]thermskin[/MENTION] ) to your CM12.1 T800 roms so that we can use these CM12.1 builds in T805 with LTE DATA Support?

I love CM12.1 and would be great to use it with T805 LTE

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Tab S Android Development] lionheartk:
Sorry I'm not the ROM creator, I'm just providing updated builds while he's away.

At least as far as I know, there are no plans for a T805 version of this rom, sorry.
[Galaxy Tab S Android Development] cyaclone:
I am on the Sept 25 release and am able to pair with my cellphone, but unable to connect to the internet with my tablet after being paired. Have not had this problem in the past but it is important that I can get to the internet with my cellphone connected to my tablet. Anyone else have this issue and is there a way to correct this? My tablet is find on my WiFi network but why can I not connect when paired with my cellphone?
[Galaxy Tab S Android Development] chazey2:
Maybe try this to set up hotspot. Works flawlessly for me!

https://play.google.com/store/apps/details?id=kr.core.technology.wifi.hotspot&hl=en
[Galaxy Tab S Android Development] xaneth:
Hangouts Dialer BT not working

Love this ROM on my SM-T800, but the Hangouts Dialer will not work with my BT headset. Showstopper for me, unfortunately. My Runbo android phone decided to die this last month, as the power button quit working, and since it was purchased from China, no way to get it replaced... I need to save the $$ I've been paying T-Mobile anyway, and the Hangouts Dialer works well for both outgoing/incoming calls over wifi for free, and the audio quality is great, but HAVE to have BT capability.
[Galaxy Tab S Android Development] calj17:
Can you guys Add T805 RIL files to this T800 rom so that we can use CM12.1 in our T805 too?

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Tab S Android Development] cyaclone:
Thanks for the tip. Did the download on both phone and tablet.

I setup the password for both units, they are paired, open the app and hit it on both devices and then the tablet will have the WiFi connection of the phone?

Do I also turn Bluetooth on in both devices?

Do I also turn hotspot on for the phone or does the app do that?

Did I miss something to make this work?
[Galaxy Tab S Android Development] chazey2:
Install on both phone and Tab s, Set up details on phone, name and password and turn on hotspot via phone main settings.

Turn on WiFi on Tab s and look for your set up WiFi hot spot in the available list. Hit connect enter the password you set up on phone and you should be done.
[Galaxy Tab S Android Development] bibihub:
Trying to build for the first time

[MENTION=4405529]nvertigo67[/MENTION] [MENTION=1409248]lionheartk[/MENTION]

I'm trying for the first time to build android. I followed nvertigo67's guide in the fourth post but I am confused by the fact that picassowifi is used

source build/envsetup.sh
breakfast picassowifi #this pushes the relevant git repos to .repo/local_manifests/roomservice.xml and fetches them
repo sync # this one fetches our additions to nvertigo_local_manifest.xml

Using this command and the following of the guide, I have the impression that I am compiling for the picassowifi and not the challwifi.

Also I tried to modify what is said for cm12.1 but the following command gives me no other choice but looking into the cm12.0 git

mkdir repackrom
cd repackrom
git init
git remote add origin https://github.com/nvertigo/repackrom.git
git fetch origin
git checkout cm-12.0
git branch --set-upstream-to=origin/cm-12.0 cm-12.0
cd ..

Could one of you help me ?

Thanks !
[Galaxy Tab S Android Development] ol31:
Is there any f2fs support with stock rom kernel?
[Galaxy Tab S Android Development] gyrex:
Can you not quote the entire post please? It's bloody annoying!
[Galaxy Tab S Android Development] calj17:
Ok sorry. Just wanted help to use cm12.1 with T805 by adding RIL. I DO NOT KNOW HOW TO DO IT. just wanted some help

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Tab S Android Development] :
Read EDIT2 nearly at the top of OP: you don't need repackrom any longer.
[Galaxy Tab S Android Development] :
f2fs is build in the kernel:

/ # zcat /proc/config.gz |grep -i f2fs
CONFIG_F2FS_FS=y
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_F2FS_FS_SECURITY=y
# CONFIG_F2FS_CHECK_FS is not set
[Galaxy Tab S Android Development] calj17:
Sir could you please add T805 RIL files to your CM12.1 builds so that we can use it with T805 LTE too?

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Tab S Android Development] :
It's time again:

I don't do any builds for devices I don't have my hands on. This is no subject to discussion.

Sir, would you please be so kind and read the thread before asking for builds. I have said this at least ten times before!
[Galaxy Tab S Android Development] calj17:
Ok it was a mistake

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Tab S Android Development] imachine:
Hey cool to see you back on the thread, I want to know how goes the work on crashing 3d apps - the tablet overheats to the point where artifacts show up and it hangs. Simcity buildit. Happens not on stock lollipop. I think it's worth to check the CPU/GPU frequency values and adapt them adequately to the stock values.

Cheers
[Galaxy Tab S Android Development] hurray:
It's nice to see you back [MENTION=4405529]nvertigo67[/MENTION]!

I am running the whole time without issues CM12.1 on the TabS. *thumbs up*

Tomorrow I will give it to my sister as a gift and I have now the TabS 2, which is pretty good besides the missing vibrator for the haptic feedback. :)

Are you staying with the Tab S or is there a chance that you move on to the TabS 2 too and we see maybe a CM 12.1 for it?
[Galaxy Tab S Android Development] :
On cm11 I've tuned cpu gpu freqs. We have tested the new settings and everyone who tested the tuned kernels was happy. Sadly, not every chagallwifi is the same in matters of power and heat. :( The cpu max speed is configurable (if you don't like echo commands in /etc/init.d/10systemtuning, you can use tools like setCpu or KernelAudiutor).

For the gpu place the following line at the end of /etc/init.d/10systemtuning and reboot. If your tab still gets to hot you can try 420.

EDIT (forgot the shell command):

/ # echo 480 >/sys/devices/platform/mali.0/dvfs_max_lock
[Galaxy Tab S Android Development] :
I'm not planing to get a tab s2. To be honest, I'm not planing to ever mess again with developing for a exynos cpu, cause of the "great" support by samsung for the openensource community. Sorry, I'm such a coding-*****... ;)

BTW and OT: If any company decides to make a real opensource device (no closed source parts in the rom), I would immediatly buy this device.
[Galaxy Tab S Android Development] hurray:
That is sad but I understand you. :)

For now I am happy with the support at the TabS2: after only one week there is the source code for the kernel the actual 5.1.1-rom online so we have root, TWRP and even the xposed-framework is running. That is for me the minimum base to set up everything I like and to de-bloat the Tab. :)

But for sure it isn't enough to bring CM 12.1 to the TabS 2.

If there where a real opensource device with the build quality and capabilities like the Samsung ones (the AMOLED display e.g. is the best I have ever seen) I would buy it too. ;)
[Galaxy Tab S Android Development] imachine:
Thank you, setting it to 480 fixes the issue (so far).

What is the default Samsung ROM setting for this GPU?

What are the default values for the CPU?

I see your ROM setting on 1.9/200 @ interactive

I also see cfq as default sched for the mmcs.

Is that the preferred value? Did you try noop or deadline?

Cheers!
[Galaxy Tab S Android Development] :
On cm11 I tested some schedulers with different tunings: for me cfq gave always the best balance according to battary life and performance. I always said, that in other people usecases this may differ. So: feel free to use other schedulers.

/ # zcat /proc/config.gz |grep IOSCHED
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONF

The same goes for governors.

(See /etc/init.d/10systemtuning. There is an exsample for schedulers.)

For the changes I did to the kernel, please look through my git.
[Galaxy Tab S Android Development] :
With the displays you are so right!

From a developer point of view: even nexus divices or my loved oneplus one have closed source parts regarding display, wlan and touch devices. I.e.: without binary patching the (closed source) mali blobs by [MENTION=3857343]crpalmer[/MENTION], we wouldn't have cm-12.x. That sucks!

Just a OT thought: if VW would build opensource software for their cars... LOL
[Galaxy Tab S Android Development] lionheartk:
WB nvertigo :)
[Galaxy Tab S Android Development] NoFaQ:
I'm interested in what your take is running f2fs vs. ext4, on this ROM and/or the T800? What do you typically use on your device?
[Galaxy Tab S Android Development] diegocr:
f2fs is kernel supported but to add f2fs mount to fstab

https://github.com/diego-cr/android...on/blob/lp5.1/rootdir/etc/fstab.universal5420
[Galaxy Tab S Android Development] :
I have tried to get cm12 to boot with system as f2fs - to no avail. I gave up on that experiment, 'cause even if I manage to get this to boot up, I don't want to have two diffrent builds. On the other hand: twrp is NOT supporting f2fs, so you would need an other recovery, an other flashing procedure. And I don't have the time and the mood to support two diffrent roms and flashing procedures.

I have tried f2fs, fat and ext4 on the external sdcard and copied a file after flashing cache and buffers: f2fs and ext4 was slightly faster then fat. But nearly no difference between f2fs and ext4. Propably the difference gets bigger on a more used fs, because of the dirty bits - but here I'm guessing.
[Galaxy Tab S Android Development] diegocr:
On slimlp same build works with ext4 or f2fs (data & cache partitions), I use ext4 but some users use f2fs
[Galaxy Tab S Android Development] uzi2:
As I understand it, there is no benefit in converting the system partition to f2fs as the benefits of f2fs come from it's superior write speed. TWRP does support f2fs for data and cache partitions, where it will be most effective.
[Galaxy Tab S Android Development] :
I think you are right - data and cache partition are more often a target of write operations than the system-partition. When trying to boot from system f2fs partition, this task occupied me that much, that I did not think about, if that makes sense... I even did not realize, that cache and data are formatable as f2fs in twrp... Brainlock... ;)

F2fs shows it's better performance when writing to areas, where parts of deleted files resides. On the other hand: a trimmed ext4 is not really (aka feelable) slower than f2fs.

I'm still very limited regarding spare time. But if you know a pointer to the fstab changes (preferable a commit in an existing git or a unified diff), I will have a look at it. If those changes enable both (f2fs AND ext4) fs, I will put it in our git - what I won't do: building two diffrent roms.
[Galaxy Tab S Android Development] :
Would you be so kind and give me a pointer to slimlps chagallwifi device tree? Or even better: a pointer to the commit(s) in question. Thanx in advance.
[Galaxy Tab S Android Development] UpInTheAir:
For old times sake ;)

fstab.universal5420

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption

/dev/block/platform/dw_mmc.0/by-name/SYSTEM /system ext4 ro,errors=panic wait
/dev/block/platform/dw_mmc.0/by-name/EFS /efs ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
[COLOR="SeaGreen"]/dev/block/platform/dw_mmc.0/by-name/CACHE /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,flush_merge	wait,check[/COLOR]
/dev/block/platform/dw_mmc.0/by-name/CACHE /cache ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
[COLOR="SeaGreen"]/dev/block/platform/dw_mmc.0/by-name/USERDATA /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,flush_merge wait,check,encryptable=footer[/COLOR]
/dev/block/platform/dw_mmc.0/by-name/USERDATA /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer

# VOLD
/devices/platform/dw_mmc.2/mmc_host/mmc2,/devices/12220000.dwmmc2/mmc_host/mmc2	auto	vfat	default	voldmanaged=extSdCard:auto,noemulatedsd
/devices/platform/exynos-dwc3.0/exynos-xhci.0/usb2*sda,/devices/usb.1/12000000.dwc3/xhci-hcd.2.auto/usb2*sda auto vfat default voldmanaged=UsbDriveA:auto
/devices/platform/exynos-dwc3.0/exynos-xhci.0/usb2*sdb,/devices/usb.1/12000000.dwc3/xhci-hcd.2.auto/usb2*sdb auto vfat default voldmanaged=UsbDriveB:auto
/devices/platform/exynos-dwc3.0/exynos-xhci.0/usb2*sdc,/devices/usb.1/12000000.dwc3/xhci-hcd.2.auto/usb2*sdc auto vfat default voldmanaged=UsbDriveC:auto
/devices/platform/exynos-dwc3.0/exynos-xhci.0/usb2*sdd,/devices/usb.1/12000000.dwc3/xhci-hcd.2.auto/usb2*sdd auto vfat default voldmanaged=UsbDriveD:auto
/devices/platform/exynos-dwc3.0/exynos-xhci.0/usb2*sde,/devices/usb.1/12000000.dwc3/xhci-hcd.2.auto/usb2*sde auto vfat default voldmanaged=UsbDriveE:auto
/devices/platform/exynos-dwc3.0/exynos-xhci.0/usb2*sdf,/devices/usb.1/12000000.dwc3/xhci-hcd.2.auto/usb2*sdf auto vfat default voldmanaged=UsbDriveF:auto
[Galaxy Tab S Android Development] diegocr:
Add the two lines that have posted @ UpInTheAir :good:
[Galaxy Tab S Android Development] :
Thanx, man!

[MENTION=1409248]lionheartk[/MENTION]:

I have committed this one to 121-work. If this proves stable I will push it to current-12.1 and cm12.1.

Would you please send me your changes regarding the *codec*.xml files? I will put them in the git, too.

BTW: THANK you so MUCH for your great and persistent work here!!!
[Galaxy Tab S Android Development] lionheartk:
Sorry people im not at home this week, kind of unexpected trip, will send news and compile ASAP!