yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] :
Good morning, bro. No reason for excuses - as I mentioned before: without your persistent work, everybody would use my April-build... ;)

I'm not at home, too; but I will try to put out a build Tuesday or Wednesday.

OT: [MENTION=535343]all[/MENTION]: Please, please, please, stop sending me pms asking for cm-13.0. I just don't know if and when I will look in cm-13.0.
[Galaxy Tab S Android Development] :
TESTBUILD

Testversion for using alternately ext4 or f2fs on /cache and/or /data.

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151011-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151011-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum

Build from branch 121-work.

Please test this version extensively and report back here. If now one encounters problems, I will put the change in the other branches.

[MENTION=1409248]lionheartk[/MENTION]: I have changed the omx-patch. Could you please review that commit in 121-work?
[Galaxy Tab S Android Development] Hannibal226:
Hey [MENTION=4405529]nvertigo67[/MENTION]

nice to see u back again in developing.

Just 2 things:

1) What the result for daily usage of this changes? Faster and/or saving storage?

2) If u want me to upload mirrors again (on stable for sure), just let me know then

CHEERS ;)
[Galaxy Tab S Android Development] :
Which twrp version (for bacon) are you refering to? I have tried 2.8.4.x and 2.8.7.0 (latest): both are not supporting f2fs at all (means: twrp-bacon-2.8.x.x is lacking f2fs support - these recoverys does not have f2fs-tools [i.e. mkfs.f2fs]).
[Galaxy Tab S Android Development] chazey2:
Been using since available and can report very stable smooth and quick for me. I'm using Deadman kernel from 18th September for the slight over clock. Have xposed V75 running as well no issues found so far. Thanks for great build for the T800.
[Galaxy Tab S Android Development] :
Thanx for rewelcoming me.

On 1)

I don't know, 'cause twrp-chagallwifi seems to not support f2fs. But as I mentioned before, I doubt there will be a feelable improvment in performance, as a fstrimmed ext4 is nearly as fast as f2fs (in a root shell: fstrim -v /data). But what I can tell: the change in fstab does not influence using ext4 on cache and data. YMMV, but my very personal oppinion on performance improvements migrating ext4 to f2fs is: very marginal and not feelable in daily use - but it has a great potential of placebo..... On the other hand - measurable even if not feelable for me: f2fs gives on writes to deleted but not freed blocks a better performance than ext4. But as long as we have no twrp with f2fs, it's all very hypothetical.

The other change is just a kind of cleanup in response to the upstream changes.

On 2)

Thanx for your offer. And - of course - you are right: mirroring makes only sense on stable versions.

EDIT: my oppinion on 1) is based on my experience with migrating my oneplus one to f2fs.

EDIT2: I refer to chagallwifi and not to bacon in my first statement - changed.
[Galaxy Tab S Android Development] uzi2:
This is your chagallwifi thread... chagallwifi twrp has f2fs support.
[Galaxy Tab S Android Development] :
Thanx. I did not know about this unofficial version.

[MENTION=535343]all[/MENTION]: please test also f2fs on /cache and data.

EDIT:

ext4 to f2fs migration how-to

Downloads:

https://www.androidfilehost.com/?fid=24052804347803617

http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151011-UNOFFICIAL-nvertigo-chagallwifi.zip

You need both of this files, which support f2fs.

Install recovery:

open a rooted shell (adb or terminal)

untar the downloaded file in your rootshell: tar -xvf twrp-2.8.7.2-f2fs-t800.tar

flash the file recovery.img: /system/xbin/dd if=recovery.img of=/dev/block/platform/dw_mmc.0/by-name/RECOVERY

Reboot to recovery and flash cm-12.1-20151011-UNOFFICIAL-nvertigo-chagallwifi.zip

Migrating /cache from ext4 to f2fs:

This one is straight forward.

In twrp go to wipe->advanced wipe and check cache

tab on repair and change filesystem

tab on change filesystem, select f2fs and swipe

Migrating the data partition from ext4 to f2fs without loosing data:

go to the top evel of twrp menu, and select backup

select at least the data partition to backup (I recommend a full backup, 'cause you never can have enough backups... ;) )

Go to the toplevel menu again and select wipe-advanced wipe

check data (NOT internal storage, but data)

tab on change filesystem, select f2fs and swipe

from the toplevel menu go to restore and restore your just made data backup - you will receive a warning regarding the mismatch of the backed up fs and the current fs, but ignore that one and continue with a dalvik and cache wipe. Finally reboot to system.

I have done this from memory, so the name of some of the menu items names may not be 100% accurate, but I think it's easy to understand.

Now your chagallwifi uses its /cache and /data with f2fs:

/ # mount|grep f2fs
/dev/block/platform/dw_mmc.0/by-name/CACHE on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,flush_merge,active_logs=6)
/dev/block/platform/dw_mmc.0/by-name/USERDATA on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,flush_merge,active_logs=6)

Again: please test this extensivly! If no one complains I will put this in the other branches.
[Galaxy Tab S Android Development] aegeuss:
Guys, I have battery reading problem in latest versions. The device seems to run out of battery and closes itself, then I reboot it shows around 15% this time etc. Any ideas?

SM-T800 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Tab S Android Development] :
The test version I posted yesterday has normal battery-life. Can't comment on other versions.
[Galaxy Tab S Android Development] NoFaQ:
I did a very clean flash, with the 10/11 build. Converted the /data and /cache to f2fs. Restored user apps with Titanium.

I've been using it for about 6 hours and I've not noticed any issues, and it's running the same. I was previously using the 09/11 build, for comparison. Battery consumption is normal (though I usually keep the CPU at 1200), and no crashes.
[Galaxy Tab S Android Development] yeiyei0891:
What keyboard are you using with this rom? Google keyboard looks bad for me. Is it possible install Samsung keyboard?

Enviado desde mi SM-T800 mediante Tapatalk
[Galaxy Tab S Android Development] NoFaQ:
I am using the ai.type Tablet Keyboard Plus. There is a free version you can try.

I really like the Samsung Keyboard, but I've not been able to get it installed and working. This keyboard I linked was the closest I could find to the functionality, and I tried at least 10 different keyboards. I really miss the control key on the Samsung keyboard.
[Galaxy Tab S Android Development] :
I use HackersKeyboard. It's a pc-style keyboard with ESC-, CTRL-, ALT- and cursor-keys. The only kb I know of, whicht with you can use screen and vi (my IDE ;) ). 99% of the porting of this rom to our device was done by this IDE.
[Galaxy Tab S Android Development] cyaclone:
I have used SwiftKey on all my devices.
[Galaxy Tab S Android Development] NoFaQ:
Thanks for that recommendation of HackersKeyboard. It's exactly what I've been looking for.

Also, after using the 10/11 build for a couple days, it's still been very stable. Still, no crashes, and everything works as expected. Battery life - I can't tell a difference, maybe even better. I do use Amplify, Greenify, and Deep Sleep Battery Saver, but I used my tablet for 5-10 minutes over 14 hours, last evening to this morning, and it only lost 3% battery, which is great, in my opinion.

Edit: For anyone looking for the HackersKeyboard, it's on the play store or on F-droid.
[Galaxy Tab S Android Development] lionheartk:
Hey everyone,

Sorry again for the lack of builds. I'm having serious financial problems in my family so I'm having to work double to try and pay some debt, so I'm lacking time to build, upload etc.

Glad that NVertigo is timely back right now and provided a test build. As soon as things gets better here ill be back on board, hopefully soon.

[MENTION=3456089]nvertigo[/MENTION], what I did to fix the patching issue was moving the file from the new location to the old and it worked... wasn't the right way to fix it but since I was already lacking time...

Have fun everyone! And thanks Nvertigo for apparently fixing the battery problem!
[Galaxy Tab S Android Development] ol31:
The test build of nvertigo works perfectly, with f2fs support. Good battery drain. No freeze. Stable and fast. Only issue is still the same : BT speaker is not working well, it is unsusable (lots of glitches).
[Galaxy Tab S Android Development] :
Thanx for testing and reporting!

Due to my lack of time I have used my last April build all the time till last week when doing my test-build. I'm not at home, and do not have my logitech pure hifi with me. So please consider that the following refers to my last bt-audio tests back in March or April:

Bt interfers with 2.4 GHz wlan: if 2.4 wlan is active AND used, bt-audio has glitches, jumps and audio out of sync. I.e.: streaming a mp4 video from my server via 2.4 wlan, I exprience bad audio. If the very same video is streamed via 5GHz wlan or having the mp4 stored localy on the chagall, the audio is christal clear (propably germanism, if so: sorry) and in sync.

I know that not all devices and all roms have this issue, but at least on my tf100, nexus10, s3 and chagallwifi these interference with wlan 2.4 was there.

Could you please try bt audio with wlan disabled (requires local file)?
[Galaxy Tab S Android Development] :
Sad to hear about your problems, my friend.

I haven't done anything to fix the battery problem. You can see my changes in branch 121-work: OMX-patch and fstab for f2fs.

At the moment I'm still waiting on more reports - if the changes proof to be stable I will merge them to current-12.1 and cm-12.1. After that I will do a build (weekend or beginning of the week.
[Galaxy Tab S Android Development] :
Future development of this rom

Hi all,

I'm starting of in a new (or better: additional) job. So I will not have that much time for developing like in the last winter season.

That means for you:

I will put out new builds once or twice every two weeks. I don't know, when I come to fix build with lollipop kernel sources and bolobs (we are still using kitkat kernel sources and blobs).
[Galaxy Tab S Android Development] mx900:
Good luck with the new job nvertigo67. We cannot thank you and other members enough for the time you guys have spent in the development of this ROM.
[Galaxy Tab S Android Development] hurray:
There is nothing to add. [MENTION=4405529]nvertigo67[/MENTION]: Thank you very much for your work which made the TabS much more useful and have a very good start at your new job!!
[Galaxy Tab S Android Development] toyanucci:
Once every few weeks is more than anyone can ask for something you do in your spare time. You've made a very stable ROM. I installed it only last night and so far have had really good battery life in usage and standby, my only issue has been that Bluetooth audio can get Skippy sometimes but other than that it's the best ROM I've installed on my tab S.

Good luck in all your new endeavours and thanks again for giving of your time.
[Galaxy Tab S Android Development] pzengota:
Bluetooth with local music and in airplane mode (WiFi is off) I still have terrible sounding music. It never worked well for me with any combination of WiFi on/off, local/streaming music. I don't think WiFi frequency is to blame. At least on my end. An other thoughts?
[Galaxy Tab S Android Development] :
As stated above: I have no bt device at hand at the moment. I have no chance to reproduvce this. Would you please provide a logcat over the period the glitches.
[Galaxy Tab S Android Development] My Public:
Sh...

10-11 build in combination with exposed v72 (newer versions give me an error while flashing) ends for me in a persistent bootloop (blue android forever). I'm unable to shut down the tablet. Holding down power key does nothing, holding down power key and volume down reboots the tablet, but not in recovery mode, blue android again... :-/

Any hint how to proceed?

Thank you!
[Galaxy Tab S Android Development] :
Do a clean install with only gapps installed.

Edit: it's quite a timing matter: holding the power button initiates a reboot. You have to press the power button and then press vol+ additionally, just in the moment before the roboot starts. Good luck. Or: if the the booting process reaches the start of adbd, you can try "adb reboot recovery". Again: good luck!

(OT: I have given my oppinion on Xposed and other apps, that replace system files, many times. If Xposed does not play with the current upstream CM12-code, xposed has to be fixed.)
[Galaxy Tab S Android Development] Carlosk1966:
Hallo.. Try this http://xdaforums.com/galaxy-tab-s/h...k-disaster-t2838473/post54618555#post54618555. Work for me every time i get bootloop.
[Galaxy Tab S Android Development] My Public:
Thanks for the reply!

As said holding down power button does nothing, so holding down power button and volume up. Only power button and volume down reboots the tablet. I have tried releasing and pushing again volume down when reboot starts, but no success. So i'm unable to power off, no adb and no fastboot. Seems that the hardware buttons don't work as expected... Don't know whats happened. Probably the only thing at this moment is waiting for a empty battery... Only way to power off. ;)
[Galaxy Tab S Android Development] pzengota:
Thanks so much for taking a look. Here is a logcat:

https://drive.google.com/open?id=0B-cxMJOOMHhZRUF6Qm9sZm93QWM
[Galaxy Tab S Android Development] :
Please give me a text file - the htmled version is not readable or searchable. Best is: start a local terminal or use adb shell. "logcat -d >/path/to/logcat.txt && gzip -9 /path/to/logcat.txt", the resulting logcat.txt.gz can be attached here.
[Galaxy Tab S Android Development] My Public:
You're my king for today Carlos!

Sent from my reborn Galaxy Tab S! :)
[Galaxy Tab S Android Development] Carlosk1966:
No problem My Public.
[Galaxy Tab S Android Development] pzengota:
Here you go. File attached.
[Galaxy Tab S Android Development] :
Some more questions:

Does it make a difference, if screen is on or off?

Does this occure on all sample rates (try audio files with different sample rates)?

Can try again with different minimum cpu frequency settings (i.e. 500 MHz [which is in deed 1GHz])? You can use SetCPU or KernelAudiutor. Or you can use an echo-command on a rooted shell, like in /system/etc/init.d/10systemtuning.)?

Do you have access to other bt-audio-devices? If so, please test them with files with different sample-rates.

Bottom line: to be honest, I've no clue at the moment.
[Galaxy Tab S Android Development] NoFaQ:
Just an FYI on the Bluetooth speaker. I was having issues, also, but someone posted a Samsung audio.zip file (somewhere in this thread). Once flashed, I don't have any BT speaker issues. Sound in sync, sound clear. I'm using a JBL Charge, for my bluetooth speaker, and Jaybird Freedom for my bluetooth headphones.
[Galaxy Tab S Android Development] :
Thanx. This zip replaces the audio_policy.conf from picassowifi with a modified one for the N9005. Does this have any side effects on other audio input or output devices like jack-bound headsets and inzernal mic and speaker? For how long did you use this workaround? Was this all the way from April on? Or did bt-audio on the way?

I will include the changes to audio_policy.conf in the next build, if you can give a solid statement about all other audio devices don't suffer from side-effects. Anyway, thanx again.
[Galaxy Tab S Android Development] NoFaQ:
I started using it because I was having major audio sync issues to the BT speaker. I've used it since around July/August, and each time I flashed a new image I flash 1) ROM, 2) gapps, 3) xposed, 4) audio policy.

I've only used wired headset once, and it was fine during the time I used it, but I can't give a lot of comments on this output method.

I do use the built in speaker, and I never had issues with it before or after using the zip. As far as I can tell, the internal speaker works fine, either way.

I don't ever use the mic on the tablet, so I have zero comment on how, or if, there is any issues there.
[Galaxy Tab S Android Development] pzengota:
I tried everything you suggested, no luck. Happens with JBL Charge speaker and also a set of wireless headphones. All files types, any minimum CPU, screen on or off, wifi on or off.

Thanks for taking time out to offer these suggestions.
[Galaxy Tab S Android Development] FearlessSpiff:
There's also still the issue that A2DP doesn't work when connected to a 2.4GHz Wifi. It works with a 5GHz though. And I guess it should work with Wifi off as you tried also.
[Galaxy Tab S Android Development] :
Next test-build will have the audio_profile.conf changes, that seem to cure this (can't test myself). Meanwhile you can flash the recommended audio-profile.zip.
[Galaxy Tab S Android Development] :
OK. Two different bt-audio issues. Thanx for pointing out.

If somebody has a pointer to a flashable zip, that addresses this one... ;) But for sure I would appriciate that! ;)
[Galaxy Tab S Android Development] NoFaQ:
I use my JBL Charge at work (which is 2.4 ghz), and my BT headphones on my phone (which is LTE at the time). I will test both tonight, at home, which I can connect to both 2.4 and 5ghz, to see if I can duplicate on my tablet.
[Galaxy Tab S Android Development] :
Great!

Later today I will put up a new test-build with the changed audio_profiles.conf. Would be very kind of you, if you can test bt-audio without flashing audio-profiles.zip. Thanx in advance.
[Galaxy Tab S Android Development] NoFaQ:
Yep, I'll grab it and flash it, as soon as it's up.
[Galaxy Tab S Android Development] :
New Test-Build: 20151020

this build contains an updated audipo_profiles.conf and all upstream chanhes till 09:00 h (UTC).

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151020-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151020-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum

Happy flashing!
[Galaxy Tab S Android Development] NoFaQ:
So far, so good. I played some videos, at work, on the BT speaker, and I haven't gotten any audio issues. Clear sound, in sync audio. I'll test the others after work.
[Galaxy Tab S Android Development] :
...and wlan at work is 2.4MHz, isn't it?

I've tested internal mic and speakers - as far as I can tell: perfect.
[Galaxy Tab S Android Development] NoFaQ:
Yes, work is 2.4ghz. Still working perfect here.
[Galaxy Tab S Android Development] toyanucci:
I'm still getting stuttering on 2.4ghz. I have 2 networks at home and 5ghz works flawlessly but 2.4ghz stutters if I'm browsing.

To the person reporting no problems on 2.4ghz have you tried browsing while the bluetooth audio is being played?
[Galaxy Tab S Android Development] pzengota:
Does bt audio play stutter free if you have wifi off? Did you flash clean?
[Galaxy Tab S Android Development] toyanucci:
Didn't clean flash. With wifi off there are no stutters. With 5ghz on, connected and browsing, no stutters. 2.4ghz on, no stutters, connected no stutters unless data is being transmitted.
[Galaxy Tab S Android Development] pzengota:
Interesting. What type of Bluetooth device are you streaming to?
[Galaxy Tab S Android Development] toyanucci:
An LG Tone Infinim bluetooth headset.
[Galaxy Tab S Android Development] Retiredfinally:
Got an error message after flashing 10-20 saying was running out of memory. Booted very fast, no updating of Android or apps.
[Galaxy Tab S Android Development] pzengota:
I just flashed and am still stuttering no matter what. WiFi on and off. What the hell am I doing different? Why are others having no problems?!
[Galaxy Tab S Android Development] toyanucci:
So quick update. I connected a bluetooth speaker and it was stutter free regardless of wifi on or off, 2.4ghz or 5ghz. I'm not sure why the headset stutters on 2.4ghz but it does.
[Galaxy Tab S Android Development] :
Even on a dirty flash, I recommend wiping dalvik, cache and system before flashing. Sounds like dalvik and cache wasn't flashed.

My policy on dirty flashing: if dirty flashing works - great for you. If issues occur: clean flash with only gapps installed.
[Galaxy Tab S Android Development] :
As I staed before: there is a problem with bt-audio if 2.4GHz is active and used. I know of this problem, but I've no idea how to address this.

About 4 or 5 years ago I got my first android driven tablet: asus tf100. With asus rom as well as with cm-10.x I had this issue (and tf100 only suppprt 2.4 GHz). Then I got a sammy s3: the same; with sammy rom and cm-11.x. I replaced the tf100 by a nexus10 - still the same with google rom, home build aosp and cm-11.x and cm12.x. I even expirienced this on an iphone 3.

About one year ago I received the tab s, and the story is still the same. While writing this, I'm not sure, if I've tested 2.4GHz wlan and bt-audio, 'cause I started very early trying to get cm11 for chagallwifi running.

OK, now my german character kicks in: we have to standardize testing.

Please test with two files (one sound file, preferable flac; one video file with sound, preferable 720p or better) and a streaming video from youtube, with resolution adjusted to the speed of you internet connection.

Put the two files localy to your device, and a copy of these two files on a server in your wlan.

Verify that the two files play stutter free and insync, whith wlan disabled at all.

Now for the test:

Play sound file from server.

Play video file from server.

Play youtube video.

Please do the above three tests with 2.4GHz and 5GHz wlan.

Additionaly to the tests, please always report model of bt-device, model of wlan-router and its country settings and channel used.
[Galaxy Tab S Android Development] Tinderbox (UK):
Hi.

Have you tried playing HEVC H.265 video`s on the Exynos T800 version as the soc does not support hardware decoding hevc and software is jerky and kiss the battery, but some version of Android cm12.1 can hardware accelerate HEVC using the opencl function built in the SOC so you get perfect playback with reduced battery usage.

thanks

John.
[Galaxy Tab S Android Development] NoFaQ:
Yes, I can do anything on my tablet, while using any BT audio source (BT Headphone or BT Speaker).

I tested it on both 2.4ghz and 5ghz and I'm not experiencing any problems. On both networks, I played files locally, through Plex, through Hulu, through Netflix, through Google Play Music, and no issues on any.

I will say, from my experience, I have some type of issue if I do anything other than a clean or very clean flash. I've tried dirty flashing and I get some type of issue with this ROM. Example, I used the 0911 build and it worked great. I dirty flashed the 0925 build, and had issues. I went to go back and clean flash the 0911 build, but accidentally flashed the 0925 build again. This time, it worked great with none of the issues I was previously experiencing.

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

Have you tried using Plex to transcode to an acceptable framerate and syncing that file to you device? That's how I've been playing those files, while keeping it at a good quality video, for the device.
[Galaxy Tab S Android Development] airmaxx23:
I've been away for a while, has deathly kernel been added to this yet?
[Galaxy Tab S Android Development] NoFaQ:
It's not integrated, but you can flash it and it will work.

Edit: http://xdaforums.com/galaxy-tab-s/development/dev-info-t3140513
[Galaxy Tab S Android Development] :
No. It is the kernel from the source I pointed to in OP.
[Galaxy Tab S Android Development] pzengota:
So I just did a clean flash of the latest nightly. Bluetooth works and is 99% glitch free. One blip probably every 5 mins or so. Local music/streaming (Google play music, YouTube, etc), WiFi on (2.4ghz, don't have a 5ghz), screen on or off. Fingers crossed! So if you having miserable time with Bluetooth, CLEAN FLASH! :):thumbup: