yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] :
Thanx for sharing your expirience. Just as I have said many times before: dirty flash whenever you want to, but if you seem to have issues with a new build: clean flash.

To avoid confusion (and so far 7 pms regarding nightlies): This rom has no nightlies. This rom is an unofficial userdebug build. Even if I would put out a build every night (what I don't intend to do), they wouldn't be nightlies but unofficial userdebug.
[Galaxy Tab S Android Development] ol31:
I do confirm the situation is much better. But still a dozen of glitches per hour.
[Galaxy Tab S Android Development] pzengota:
Oh I understand, just said "nightly" for lack of a better term. I suppose just "build" makes a little more sense.
[Galaxy Tab S Android Development] :
???

What do you mean? With or without wifi? (Please always give precise information, as I asked for in the posting above.)
[Galaxy Tab S Android Development] ol31:
With 2.4Ghz Wi-Fi on. Not tested other conf yet. My bt speaker is the mini bose sound Link.
[Galaxy Tab S Android Development] :
If completing the other tests, please don't forget to give router model, router country setting and channel used.

[MENTION=535343]all[/MENTION]: please don't make my begging for information all the time. It takes time I don't have and is very frustrating. I don't use bt-audio, so YOU want that fixed - not me...
[Galaxy Tab S Android Development] NoFaQ:
What issues are you seeing? At my other job, my boss has the mini bose sound link, and I've used it frequently with the Tab S and this ROM. It was previous ROMS that I flashed the audio profile, but that was integrated into this build. I played it and have watched movies on it. So, I know I can go at least 2 hours with no issues on that BT stereo.

I'm working there this weekend, so I'll test it again, but I doubt I'll see any issues.

Are you having issues with local files or streaming files? Music or video? Not enough information.
[Galaxy Tab S Android Development] :
Welcome to my world, dude... ;)
[Galaxy Tab S Android Development] :
The future of this rom

This thread has become a consumer thread. Nothing wrong with that. Each user should be able to do, what he wants to.

I'm developing for fun - nothing wrong with that, too. When I started this thread, I decided to try to support you here in this thread. Two weeks ago I decided to iron out the last hassles and put out a non-beta stable build.

Due to the change in users participation and state of mind, I received (with one single exception) no helpful responses. I have given detailed information on what tests I need: no one is responding. You ask me to implement a new feature (f2fs on cahe and data), I put out a test build for that, and again: nothing.

Again: it is ok for me, if the consumer mentality is droping in: "XXX is not working, make it working, but leave me alone with your logcat and your digging for information." Everybody has the right to do so.

And it is my right, to decide, in which way I spent my spare time. At the moment it does not make any sense to me developing this rom. As I told above, I do this for fun - and developing, testing and supporting the way you seem to want it, is no fun at all for me. So I will spend my spare time on activities, that are more valuable for me.

I will not any longer give support here. I will develop for my private use, and will put from time to time a build here.
[Galaxy Tab S Android Development] Hannibal226:
I'm sorry to hear that, but fully understand this.

Also when starting to use this rom I had more time to test and report things, but know I'm happy, when using a stable daily driver and just flashing a bit from time to time.

So I really can imagine what this means for u and so it's a logical consequence.

Anyway thanks for all of ur work and time u spend and maybe we see some build from time to time anyway.

CHEERS!

EDIT: But as u r the only one who really brought CM to our tablets really well.

Do u anyway spend us a CM13 based version in a some weeks?

Work began on it or u completly try to make a cut with end of CM12.1?
[Galaxy Tab S Android Development] ol31:
I reported that your F2FS support is working perfectly.
[Galaxy Tab S Android Development] :
You are right. I received on each test-build (bt and f2fs) one usefull response. I just have forgotten to add "(with one exception)". BTW: I've used f2fs on data and cache for 10 days now. In this time I haven't read complains about ext4 (which is the setup - I belive - most people use). So I'm pretty sure, that this change is stable.

I'm not blaming anyone here. It's just a matter of what I want to do and how I want to do it.
[Galaxy Tab S Android Development] My Public:
Big thanks [MENTION=4405529]nvertigo67[/MENTION] for all your work and efforts for our Tab S!

I hope you will continue to share your work from time to time.
[Galaxy Tab S Android Development] chazey2:
Thanks

[MENTION=4405529]nvertigo67[/MENTION] Just a thanks for your work. Not had my Tab S very long but have found your Rom very stable, slick and smooth. If you update from time to time great! If not and you enjoy your time away also great. Many thanks.
[Galaxy Tab S Android Development] NoFaQ:
I just want to start out with a huge THANK YOU!!

I appreciate all your effort, from your free time, and you've asked little in return (user input). Through all iterations I've used, this ROM is the first that made my tablet feel like I thought it should, based on specs. It has been very stable, since March, and has only gotten better with each adjustment.

Through working through my issues, I have learned a lot about trying to fix my own issues, and I have learned a great deal by fixing my mistakes, and how to deal with finicky issues my tablet throws at me.

I fully understand your frustration and decreased motivation to put into continuing minute issues that appear for some. It's a fantastic ROM, very stable, and the best ROM I've used for any device. Good luck and enjoy whatever endeavors you pursue for enjoyment. I hope to continue seeing you tinker with it. It always gives me enjoyment to test out the newest build, but if you choose not to continue working on it, then I wish you loads of fun in whatever fills the time.
[Galaxy Tab S Android Development] zigonneux:
Don't get so angry, dear German character friend ! If there are no bugs to be found , what do you want me to do beside a big thank you !!! the f2fs on cache and data work fine, Bluetooth work fine also.... There are 150 pages on this thread, the f2fs on cache and data was only a few days ago, I did it only yesterday. Once you said : "OK, now my German character kicks in..." I'd say that it's a fact that you have a German character.... ;) and building roms is your hobby, but dealing with the public is not easy and can be very frustrating. So, it's time for a beer and a reboot.... take a break, but don't forget that many peoples here have a lot of respect for you and their T-800 are working very well because of you. As You say : You are always permitted to read the whole thread, I did so many times and I've learned a lot of thing ... Anyway your thread have 236,942 views, so you were not talking for nothing I guess.

Vielen Dank für Ihre harte Arbeit !

Zeit für eine Pause , und hoffentlich werden wir Sie wieder hier zu sehen. !

Cheers from Canada !
[Galaxy Tab S Android Development] :
And I thought canadians speak french, when not playing hockey or speaking english... ;) And: if I would call your posting diplomatic, that would be very euphemistic. It was mote than that. I know I'm a pedantic control freak. And issue's I cant reproduce myself are driving my crazy... :(

Thanx to all ecouraging me.

I would really like bt-audio working for all users, before putting out a non-beta release build.
[Galaxy Tab S Android Development] zigonneux:
BT devices ( mostly speakers) are the worst gadgets to have to deal with. With the same BT speakers here, sometimes they take a long time to pair with my tablet, but will pair fine and quickly with my friend's phone, ( both samsung) Unless we pay a lot of $$ for some Bluetooth speakers, i wouldn't worry too much about that. Trying to fix a $20 Chinese Bluetooth device will just give you a headache. Those who use Bluetooth all the time can always try another kernel and rom and see if it will fix their problem. My cheap Bluetooth speakers were dead a few days ago, but decided to resuscitate today , I am testing them right now, with wifi 5g ON and it's OK. Slight stuttering when I've switch to wifi 2.4 on the fly, but after restarting the radio stream, no more problems at all, even when loading heavy web pages with chrome at the same time. (320 AAC radio stream, RadioParadise )

Maybe that those who have a problem have not loaded the kernel properly, dirty flashing or some other strange problem. but it look like most of us don't have a problem with Bluetooth. OOOps a 0.2 second hicup with the music... i don't call this a bug. I am using the web at the same time and the T-800 decided to reconnect on the 5G by itself.

----------------

By the way, Canadians speak English, only the Province of Québec is French. We were conquered by the English because we were too drunk to fight properly :silly: ....
[Galaxy Tab S Android Development] :
First and most important: I like your sense of humor. And: hey, a good drink is always better then a fight. If we germans would have sticked to this, 20th century would have been much more peacefull. So: cheers! ;)

Back to business:

My latest theorie to bt-audio/a2dp: There are two issues: slight crackling and skipping when 2.4GHz wlan is on heavy use, and jitter all the time when bt-speaker is connected. For the first I have no idea. For the latter: a user of [MENTION=583692]nexor[/MENTION]rs chagalllte build is using a bose soundlink mini. The specs of lthis device are stating, that only 48KHz is supported by soundlink mini. Our chagallwifi audio_policy.conf has only 44.1KHz sampling rate (as the original sammy stock rom).

If somone is owning a bose soundlink mini and has plenty of time, I would like to know, if this one is really always jittering on cm-12.1, and if this does not appear on sammy stock rom.
[Galaxy Tab S Android Development] zigonneux:
slightly off topic... testing new kernels and roms on an old nexus 7 2012 and brick it like some guys have done this week made me imagine what it will be like when it will be the time to flash MM 6.0 on the T-800. People might have some incentive to flash an old and slow nexus 7 2012 to try to make it faster. But I can hardly see the point of flashing my T-800 with MM while your rom is working very well. Battery last a long time and there is no lag at all. I know that i'll flash it because I'm a tester, but it will be a scary event :) clean flashes all the time and i won't be the first one in the lineup ... End of thread Hijacking !
[Galaxy Tab S Android Development] :
Hihi, from hockey you know, it's all about courage and fitness... *lol*

But if you look at the adrenaline/effort relationship, I can promise that it's the best when you flash your first homebuild to a device...

As for MM: if you like aosp and have a nexus device, I completely understand to flash MM. If you like cm - as I do - and like the cm-ish features, then you should wait till the cm guys have ported their features. When I switched from developing cm11 for chagall to cm12, I was MUCH to early: only some features was ported. I'm quite curious, if cm is using the aosp multi window feature.

And for having a device bricked: who has never bricked his device, is flashing not often enough... Who has never softbricked his/hers device, was never walking on the edge. Who has never hardbricked a device, was never over the edge. (Before you ask: yes, I have often softbricked devices, when developing. Yes I have hardbricked a device once, when I flashed some dd partition backups via fastboot flash, and sadly crossflashed primary-bootloader- and modem-partition.... Sometimes you have to pay the price for your learning curve...)
[Galaxy Tab S Android Development] zigonneux:
At least you bought a sondlink mini II , so when you'll go back to that store they won't hide from you and call the men in white coat ! :eek: I know that you will release a MM 6 , so I'm patiently waiting. ( sort of) As soon as a CM 13 will be out, you'll jump on it and port it to chagall. Don't tell me that you will stop after cm 12.1, you'll sound like Amy Winehouse... Quite a few softbricked devices on my part, adrenaline start pumping and we wish we had 4 hands and more buttons to push. Hardbricked only 1 router so far = garbage. My kid told me yesterday to stop flashing his old nexus 7 , It's driving him crazy, he never know if he will loose it or not :D

The problem with 5GHz is that the signal doesn't go far enough. We all think that we will eventually have to use it because the 2.4 band is too crowded, but the TV cable co. are also using 5gz with their wireless Tv receivers so I start seeing quite a few 5ghz devices on my scanner.

Now I'll go check what's the difference between Bluetooth 3.2 up to 4.2, there are BIG differences. Like speed and Ipv6 support for 4.2. So , the outcome of testing a bluetooth speaker would depend of the hardware also. http://arstechnica.com/gadgets/2014...rings-ipv6-better-privacy-and-increased-speed >
[Galaxy Tab S Android Development] hurray:
[MENTION=4405529]nvertigo67[/MENTION]: thanks for the tip with the Bose mini II. I think I have to go into a shop and test one of them a little bit. :D

For the Tab S I am a little sad that I give it away as for now the Tab S2 is a little bit "boring" from a flashing perspective: no CM in sight and the original rom (debloated of course) runs fast and stable. :)

It was a lot of fun to test new features that you brought to us. I miss this a little bit... ;)
[Galaxy Tab S Android Development] :
How to build cm12 for chagallwifi

I have updated and reworked "How to build cm12 for chagallwifi" in posting #4.
[Galaxy Tab S Android Development] :
I've updated OP. Main difference are my recommendation for twrp and gapps. At this moment I recommend:

TWRP: http://xdaforums.com/galaxy-tab-s/development/twrp-2-8-6-1-unofficial-sm-t800-805-807-t3074633

Gapps: http://opengapps.org/
[Galaxy Tab S Android Development] hurray:
I was so impressed from this little sound devil that I bought today a white Bose SoundLink Mini II. :D Especially in conjunction with the Neutron Music Player (which is worth every cent) an awesome and powerful portable sound solution.
[Galaxy Tab S Android Development] :
TESTBUILD or better: RC1

(Hopefully) the last TESTBUILD before leaving beta status.:D

I added ant+ from [MENTION=583692]nexor[/MENTION]r (the hero who is fighting cm-12.1 to the chagalllte). Anyone has a ant+ device (ant and ant+ is used for sensors like heartbeat monitor; it's a prprietary protocol originating from a group of companies around Garmin)? Would be nice to know, if this works.

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

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

Happy flashing!
[Galaxy Tab S Android Development] :
Yes, I know, what you mean: I saw this device first, smiling selfconfident while thinking 'Mhh, they want that much money for this toy". Then I heard the sound emerging from "this toy"...

Just downloaded the free version of Neutron Music Player. The sound (with soround sound enabled, all other settings left to their defaults) of this app is great; I would give 6 of 5 stars. But the interface... ...is -1 star. So I give 5 stars... ;)
[Galaxy Tab S Android Development] hurray:
You are right: the interface isn't that good but I never have a player that has a so well optimised output. The "automatic gain protection" e.g. is an awesome feature for preventing clipping and if your use the 4 or 10 bands graphic equalizer with care you are able to optimize the output to the maximum possible. For me e.g. I use it to raise the lows and mids a little bit (for me the 4 band eq is enough).
[Galaxy Tab S Android Development] :
To be honest, I'ver read so much specs, standards and protocol definitions, that I only have overflown the link and the pdf referenced in that article. I may be wrong, but I can't stand the feeling, we should kill all salesmanagers.... ;) It seems to me, that they are doing all the proprietary ****, they had done to wlan standards, now with bluetooth.

i.e.: wlan 802.11n is still draft. But all companies build and produce based on the draft - but not stick to the word - leading to all kind of issues in interoperability. :( Let's go ahead to 802.11ac, 'cause the salesmanager command this, 'cause it reads so nice in the ads. In the end we all (users, software developers, hardware developers) suffer from so called standards, of which each network device vendor has a slightly own version or understanding...

And for the speed: if the vendors of network devices would be treated like VW with their faked data, they had to pay billions... i.e.: I have seen ftp througput for gigabit ethernet of nearly 120MB/s between two netbsd boxes. That's exactly the the theoretical speed a 1000Mbit network can handle. But even on an unsed 802.11n wlan with 300MBit connection, I can hardly produce a throughput of 3,5 MB/s. Theoretical 300Mbit equals 36MB/s. We are betrayed by over 1000%. Even car vendors betray with their numners about consumtion "only" by 14% - 20%.

Extrapolated to bt that means: if they are promising ipv6 through a simple software/firmware update (WITHOUT recertification - that one must be a joke, I can't laugh about - we don't get ipv6 in bt 4.2, but ipv1.317... *lol*

Again this german character: I like standards - theoreticallythey should make life easier. Theoretically... ;

When in doubt, blame the OS vendor! ;) ;) ;)

Rethinking it's no surprise, that bt and wlan interfere. It's no surprise, that bt-audio struggles here and there. The real surprise is, that we can hear something from the bt speakers at all.
[Galaxy Tab S Android Development] :
Will try your settings.

After seeing your screenshot, I should have tested the player with my bacon. On the chagall the interface is more ugly - i.e.: the checkboxes not only violates android/cm style guidelines, on the chagall they are much too LARGE and spread their uglyness (does this word exists in English? over our wunderfull amoled-display.

Again: the sound is hearable better then with Music.apk.
[Galaxy Tab S Android Development] :
Hotfix for RC1

I made a mistake, when thinking my adjustments to media_codecs_google_video.xml and media_codecs_ffmpeg.xml were obsolet. The thumbnail cache of gallery tricked me.

Anyway, this is - of course - no showstopper fo a non-beta release.

And here comes the hotfix:

Download the attached two files, and copy them with a root enabled filemanger (or from a root shell with /system mounted rw: "mount -o temount,rw /system") to /system/etc over the existing two files. Then reboot (not fast reboot).

EDIT: Attached the two file as 7zip archive: xda don't like xml files.
[Galaxy Tab S Android Development] imachine:
I have a huge translation error, of the clock calendar widget. Where to message about a possible fix? I also miss the Polish keyboard layout as an option for physical, Bluetooth keyboard - having an option to choose Slovenian, Slovakian and Czech, I think it's clearly an error - Slovenia is like 2 million people. Where to report these two errors so they get fixed asap?
[Galaxy Tab S Android Development] :
Thanx for the feedback.

Sadly, I have bad news: The translations of system apps and their widgets is in cyanogenmod repo. The same goes for the keyboard layouts. But you can't report that on jira, 'cause chagallwifi is not an official cm supported device.

But this problem should appear in other (official) builds, too. So I belive, that this gets fixed - sooner or later. If you own an other android device, which is cm supported, and you have the same errors there, you can report on jira.

https://www.google.de/search?client...q=cm-12.1+polish+layout+for+physical+keyboard

The 4th match:

http://android.stackexchange.com/questions/30256/how-to-add-a-physical-keyboard-layout

As for the headcount: I feel sorry about the missing layout for your keyboard, and thats definitly something cm should fix. But following your arguments regarding the count of slovenian people vs. the count of polish people, I would suggest we all learn mandarin and use kanji keyboards in future... ;)
[Galaxy Tab S Android Development] zigonneux:
thanks for the OMX hotfix !
[Galaxy Tab S Android Development] My Public:
I've made some tests with OruxMaps and 2 of my ant+ devices (Mio Fuse heart rate monitor and Garmin Tempe), but i'm unable to pair the sensors with the Tab S.

The app 'ANT Tester' states that there is no firmware implementation (see screenshot).

PS: "ANT Radio service" and "ANT+ plugins service" (from PlayStore) must be installed.
[Galaxy Tab S Android Development] imachine:
Edit: I sorted the translation issue, together with one of the translators - the keyboard issue is on the way.

Cheers and waiting for RC2.

After you Release, what's left to do in order to make it an official cyanogenmod port?

--

This is how much they care:

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-6725

I think if one plans to include a layout for a country of 2 million, its only logical to include a layout for a country of 40 million. Chinese have they own layout so I find your suggestion bogus in regards to this statement - though I wholeheartedly think Chinese is a language worth learning.

Is the widget I described also a CM application? If so, is the jira the correct place to report bugs?

Chagallwifi or not, it's universal part of software that's broken, I think it has little to do with chagallwifi specifics.

Regards & waiting for RC2
[Galaxy Tab S Android Development] :
I've found some cm-packages, that need to be build. Not sure, but I think ANT Radio Service is then in the rom:

commit ec7598ea777f9cfe7e6ed9b822cda4427f440753
Author: nvertigo <ingo@tipanet.dyndns.org>
Date: Mon Nov 2 12:10:04 2015 +0100

ANT+: device.mk: add PRODUCT_PACKAGES AntHalService, com.dsi.ant.antradio_library and libantradio.

diff --git a/device.mk b/device.mk
index a59dd10..817bc07 100644
--- a/device.mk
+++ b/device.mk
@@ -25,6 +25,12 @@ DEVICE_PACKAGE_OVERLAYS += device/samsung/chagallwifi/overlay
PRODUCT_AAPT_CONFIG := normal xlarge hdpi xhdpi xxhdpi
PRODUCT_AAPT_PREF_CONFIG := xhdpi

+# ANT+
+PRODUCT_PACKAGES += \
+ AntHalService \
+ com.dsi.ant.antradio_library \
+ libantradio
+
# Audio
PRODUCT_PACKAGES += \
audio.primary.universal5420 \

Will be in RC2.
[Galaxy Tab S Android Development] :
If you give my an polish keyboard layout file, I'm happy to put it in the rom, till upstream is fixed.
[Galaxy Tab S Android Development] :
First and most important: you need to find someone, who wants to mess with cm team and who is willing to become the maintainer. Most work which had to be done, is merging all of chagallwifi kernel source in the exynos5420 kernel source.
[Galaxy Tab S Android Development] :
Bad news: I will remove the attempts to get ant/ant+ running: if I use as device vfs-prerelease the ant service is build for qualcomm bt devices, if I try to build with bcm433x (which would match our bcm4339 bt chip), the build breaks: it seems that the bcm433x implementation is based on bluet - andriod uses since kitkat bluedroid. For the moment I gave up on that, and will revert all according changes.

RC2 will have no ant support.

For devs:

I will keep my ant changes in the branch ant.
[Galaxy Tab S Android Development] My Public:
So you will say me that i can't mount my Tab S on my Scott racing bicycle to monitor my heart rate while pedaling? Shame on you!! :mad:

I'm kidding. Ant+ seems to be shabbily treated from the firmware producers. It worked fine on my OnePlus One (CM based firmware) which i used as cycle computer, but at the moment don't work on my new OnePlus 2 (OxygenOS 2.1.1)...