yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] ristokoo:
Here's a DropBox link for a new build.

https://www.dropbox.com/s/4l9y09kvc...FICIAL-ristokoo-nvertigo-chagallwifi.zip?dl=0

MD5SUM:

3c8a97c3afedc234789d111d7cd0dccd

---------- Post added at 11:26 PM ---------- Previous post was at 11:22 PM ----------

Something strange happening with the forum. I tried to reply to [MENTION=7000441]zigonneux[/MENTION] but my text kept going to the end of my previous post. Trying XDA app now...

Edit from PC again. Why can't I create a new post, everything I write just ends up here? Technology hates me...

---------- Post added at 11:30 PM ---------- Previous post was at 11:26 PM ----------

Testing reply again. Looks fine in preview post, but...
[Galaxy Tab S Android Development] zigonneux:
yeah, the forum is acting weird, but seem to have settle down now, It might be the admin making some tweaking. I have your file and will install now... Thanks !
[Galaxy Tab S Android Development] ristokoo:
Ok one more try: this is what I was going to answer you earlier:

Oh no, I'm not a developer, just building the zips. I just happen to have time and a laptop available The point is to make use of nvertigo's additional work to CM 12.1 which means I build the ROM using the instructions he gave in this thread.

So what happens when I build a new one is this: I sync with the current CM 12.1 source (which gets new stuff also from deadman96385) , and with nvertigos work from github. The result being an up to date CM 12.1 ROM with added spices from those guys.

(Those who know better: correct me if I'm not making any sense.)

All credit for developing the software goes to [MENTION=3456089]nvertigo[/MENTION] and [MENTION=4222965]deadman96385[/MENTION], and the good folks working with CyanogenMod.

Let's hope your DAC problem gets solved. Keep an eye on the change log, and if you see something related to that you can remind me here to build a new one right away. Otherwise I suppose something like a weekly build would do.
[Galaxy Tab S Android Development] deadman96385:
If you want to build cm-13.0 for chagallwifi use the 13-work branch for vendor and device tree and the 13-work-old for kernel, same bugs as klimtwifi for cm-13.0
[Galaxy Tab S Android Development] ristokoo:
Thanks for the tip. I'm tempted and might actually try some day;) I didn't realise we could actually have a (at least somewhat) working ROM that way.
[Galaxy Tab S Android Development] zigonneux:
Everything is working fine, Autuntu benchmark 50,450 stable. Now a question about a logcat, since i want a log about my usb device I can't use ADB because the usb is connected on the dac. I have downloaded the app " alogcat " so, what level should i choose: verbose, debug, info,warning, error, fatal. Then the format : brief, process, tag, Thread etc... buffer: main or event ? I am reading and watching video about it but no answers so far... might be faster here to get an answer..

what i can see is DEV/SND/PcmC1Dop file doesn't exist. I will create it and see
[Galaxy Tab S Android Development] :
If you like it minimalistic: In dev opts enable local terminal, start local terminal, just execute "su" in terminal and accept the root request. Then just

logcat -d >/extSdCard/Download/logcat.log && \
dmesg >/extSdCard/Download/dmesg.log && \
zip -9 /extSdCard/Download/logfiles /extSdCard/Download/*log && \
rm /extSdCard/Download/*log"

You also can execute the commamds one by one, but in a row it looks cooler, and the boolen AND (&&) will ensure, that the execution is aborted if something goes wrong.

I like the minimalistic aproach for two main reasons: 1. It's always there - you can do this on a bare install without gapps installed. 2. I call it my "Heisenberg paranoia": propably the app you additionally use to observe an issue, changes what you observe... ...sounds strange, I know - with the words of Kernighan and Ritchie: debug your debugger first. ;)

May you put the complete line (+/- 15 lines) of the missing device file. I'm not sure, but I think we can't just create this file: worst case there is a kernel driver missing, but even if the kernel driver is in place, we would need to know if we shoild create a block or character device (I guess for the latter), and which major/minor number belomg to this interface.

What really makes this a mystery is the fact, that it works for one song...
[Galaxy Tab S Android Development] :
Cm13 alpha works quite well and stable, but camera and widevine (google drm) is still broken. But the real show stopper is the fact, that it only works in permissive mode, which not only allows forcing proprietary apps (i.e. gpsd) to use defined libs (so called shimming), but also allows malware to do all kind of evil. Considering the thechnical understanding of MM-hyped "normal" users, and considering that computer criminals just wait for such a setup, I would strongly recommend NOT tu publish such a build. I don't want to offend anybody - but I want to make published builds as secure as cm/google intended.

Though everybody can build for his own. I hope, that someone, who can build a rom, is able to judge the consequences of running a permissive rom...
[Galaxy Tab S Android Development] ristokoo:
Good info, thanks. I certainly don't plan to publish any CM13 builds but might try building it just to see if I can get it done ;) Not sure about that, my understanding of these different versions is still very limited. Interesting stuff anyway.
[Galaxy Tab S Android Development] Mrodfr:
Hello

I'm very happy to see that things are moving again... Thanks to all involved. ;)

I love this rom a lot and one particularly things I really appreciate is the fact of charging at full speed. With stock rom, I have rarely charged my device more than 500 mah. Always playing with différents plugs at home until, by change, found one plug with decent charging speed.

Now, since I use this rom, I have always or practically around 1500 mah at start of all my charging and the normal decrease around 80 to 100%. Very good!!! :good:

And now my question. Is it possible to use successfully a fast charger device with galaxy tab 's?
[Galaxy Tab S Android Development] :
That's a good one! Try it, log it, report it. I've only used the stock charger (european version), and thought it would be very fast (at least compared to manta... ;) which is knownto charge very slowly.
[Galaxy Tab S Android Development] dwarfer66:
I use my S6 edge fast charger with my Tab S 10.5 and it seems to charge faster than the normal charger I got with the tab.
[Galaxy Tab S Android Development] zigonneux:
Then, someone can activate the permissive option if he want to use the camera and revert back when it has finished. !

It would need a reminder popping up after using the camera ! just an idea.

Ok now about this DAC. I've been able to read the catlog and figure out part of the problem. Just create a file : dev/snd/pcmC1D0p and set the permission to read ,write and execute. Now I can change the song for the WAV files but not the Flac, Isn't it weird ? . Anyway, the sound of this DAC is very similar to the sound of the T 800. So i'll just continue to play with this and try to fix the nexus 7 2013 instead.
[Galaxy Tab S Android Development] ristokoo:
I understood the problem is that permissive mode is not an option but the only possibility at the moment. And regardless of that, camera and widevine don't work at all.
[Galaxy Tab S Android Development] deadman96385:
Currently we do not support Flac because it uses a proprietary encoder/decoder and prebuilt ones do not work. I will look into this file any chance you can post that log you examined?
[Galaxy Tab S Android Development] zigonneux:
Thanks for your offer Deadman. Not such a great DAC to spend so much time and effort.

I've decided not to use this dac or any dacs with the T 800 because all this connecting and disconnecting with a heavy setup of otg wire + DAC + wire for the sennheiser headphones attached to it seem to loosen up the mini usb input. It's not as tight as before. I'll keep using the headphone jack because anyway the sound is the same or even better than this inexpensive Fii0 K1 DAC .

I'm setting up my T 800 so that I use the usb only for recharging and will use the wireless file transfer or streaming. I've also deleted the file that I've created ( pcmC1D0p) because even wav files don't play anymore with the Fii0 dac .....
[Galaxy Tab S Android Development] ristokoo:
Maybe that FiiO DAC hardware is somehow problematic? I don't usually use my T800 for listening music but got curious and tried. My regular gear is an Objective DAC/O2 Amp combo. I also have an old Stoner Acoustics UD100 DAC. Both DACs worked fine. I also had no problems playing FLAC files.

I also tried my Sennheiser HD650 through the headphone jack. It sounded surprisingly good and didn't need the volume to be cranked up too much. I have Dolby Atmos installed, it helps with the volume.
[Galaxy Tab S Android Development] bouwew:
Thanks for the ROM!

I performed a clean install yesterday and everything seems to work fine. The screen is quite responsive, the best I've seen so far :)

A question: at first use after the flash I noticed there was a notification about an update, the 19feb nightly. That is not yours right?

I should stay away from it?
[Galaxy Tab S Android Development] ristokoo:
Good to know there are users :) IMO this is the best ROM we currently have for the T800. Unless for some reason you need the Samsung stuff or an unrooted ROM.

---------- Post added at 12:04 PM ---------- Previous post was at 11:52 AM ----------

Correct, not my build. You get notified about the automated nightly official CM builds by default. This can be changed in Settings - About tablet - CyanogenMod updates - Check for updates.

Edit:

There's not really any reason to stay away from official builds, they work well as far as I know. But with official you will miss the nice stuff from nvertigo67. With unofficial (my builds) you sort of get the best of both worlds.
[Galaxy Tab S Android Development] :
The file needs to be a device-node, but not a plain file. The problem is (and I havn't seen any logs, I'm guessing from the filename), that if the dac is connected, ueventd should generate the /dev files what doesn't happen. Generating a plain file only makes the file not found error go away. Ueventd should also generate a new control inter face.

The node you need is a charcter special file, but we don't know the major and minor number of the node. (yes, I really need logcat and dmesg from connecting the dac)

You can try in a rooted shell something like this:

mknod /dev/snd/pcmC1D0p c 116 48

. But this is only a part of the game: you also have to mknod a new control file (/dev/snd/comtrolC1, i guess). Better fix ueventd issue, because if the event "dac connected" occurs, ueventd should trigger the generation of this files. Anyway: without log it's guessing.

Never ever put plain files to /dev: this can NOT be working, but propably may introduce some really strange issues!
[Galaxy Tab S Android Development] :
Since nobody really wants to read (as well the differences from nvertigo builds to official builds, as the reason, why only official updates are shown, are discussed MANY times in detail - we discussed this very problem, and why we use custom build id 3 pages back), I really think of taking CMUpdater completely out of our rom.
[Galaxy Tab S Android Development] ristokoo:
[MENTION=4405529]nvertigo67[/MENTION]:

Just a thought: would you benefit from my logs whem plugging in/unplugging my (working) USB DAC?

---------- Post added at 01:39 PM ---------- Previous post was at 01:31 PM ----------

Yes it seems official/unofficial can be confusing. If it's really simple and fast for you to remove CMUpdater (or just change the default check for updates to manual), then why not.

But otherwise, don't waste time to that. I don't mind explainig it every now and then;)
[Galaxy Tab S Android Development] :
For usb-dac: yes. For a first view, plug in the usb dac; immidiatly get a dmesg and logcat output (in a rooted shell: "dmesg >/extSdCard/Download/dmesg.txt && logcat -d >/extSdCard/Download/logcat.txt"), please also take a look at /dev/snd before and after.

[MENTION=535343]all[/MENTION]: if someone has a stock (5.0.2) nandroid backup and a usb dac device at hand, could do the same on a running stock rom (I consider here, that usb.dac works on stock - if I'm wrong, and stock has the same issue, we don't need logcat and dmesg, of course).

For CMUpdater:

Just put this line

<remove-project name="CyanogenMod/android_packages_apps_CMUpdater" />

to your local manifest before running repo sync - that's it. It worked for a dirty build (building without clean/clobber before), I'm just trying a clean build. If clean building fails, I'll report back - if I don't report back it's just working.
[Galaxy Tab S Android Development] ristokoo:
[MENTION=4405529]nvertigo67[/MENTION] here are my logs, and what is in /dev/snd before and after plugging in the DAC. I have a backup of stock ROM so I'll get those from it as well in a short while.

Edit: dmesg from Samsung 5.0.2 ROM. For some reason, logcat gives nothing. Need to look at that.

Edit2: Only tried listening now. Doesn't work on Samsung ROM, sounds like static...
[Galaxy Tab S Android Development] :
Ähm - now I'm confused, your logs and your listings looks like, usb-dac is working for you. Both needed nodes (the pcm* and controlC1) are generatet and the subsystem gets registered with the kernel. Can you play audio via usb-audio? (have you enabled usb audi routing in dev-opts? This should allow to use usb audio with ALL media players.)

[MENTION=7000441]zigonneux[/MENTION]: if the pcm* and controlC1 nodes aren't generated, your installation seems to be messed up. If you take a look at devsnd2.txt from [MENTION=2983236]ristokoo[/MENTION] zip, you can see, that the additional nodes for the new "soundcard" are generated.

EDIT: Sorry, friend, I was too late: as your cm installation does, what I expect it to do, the dmesg from stock wasn't neccessary any more - too late. So I examined it anyway: Cm and stock do the same with dac pluged in.

EDIT2: [MENTION=7000441]zigonneux[/MENTION]: You mentioned an app for using usb-dac. Could it be, that that app is breaking the registering of the new sound subsystem? To my understanding, you just need to enable audio-routing for usb, and you can use all media players.
[Galaxy Tab S Android Development] ristokoo:
No problem. At least I know now that my DAC works on CM 12.1 but not on stock Samsung;)
[Galaxy Tab S Android Development] :
One step after the other... When [MENTION=7000441]zigonneux[/MENTION] reported the missing node, I was thinking of some issue when connecting (you can think of the dac as a new attached soundcard) the dac. Propably (I'm guessing here blindly) the very same app, that breaks the kernel wise registering of the dac on cm, is need to use the dac on stock...

At this point, we can be sure, that everything is ok on kernel- and early system-side. Dac is registered and available through /dev.

My next question has been, if you can use it on application level: I consider your answer as confirmation that usb-dac is working on our rom.

Thanx for helping and providing logs.
[Galaxy Tab S Android Development] ristokoo:
Cool! Just flashed a new build, CMUpdater gone like expected. So the future ones won't check for nightly updates.
[Galaxy Tab S Android Development] zigonneux:
I have another usb DAC based on Via chipset, it does work very well with any audio apps, radio, youtube, flac player , all audio output. It's just this Fii0 K1 that is incompatible . Even those 2 expensives apps won't do it: onkyo player $ and USB Audio Player PRO ( work part time) .Some chipsets play fine while other don't. As easy as that. So yes many DAC will work with Cyanogenmod, as reported by many websites . Sorry for the missing logcat but we've had 1 meter of snow yesterday and I was half dead after shovelling all day, and as I've said that heavy set of dongle is tough on the usb port which is getting as loose as a whore on broadway. .....
[Galaxy Tab S Android Development] :
From what I know, the usb-audio kernel driver is generic and should(*) work with any chipset. Really strange. What does dmesg say, when you've plugged in the dac? If the additional nodes does not auto-appear, theres something wrong on kernel level...

(*) "should", "could" and "but": the three most hated words in computer-sience... ;)
[Galaxy Tab S Android Development] zigonneux:
Got myself a better OTG cable. It fit better in the usb slot.

ok just to get at the bottom of this story i'll get a logcat :) so there you go. At first , files were playing fine, then it started going bad. Any other audio app that i actually have won't work. I use an app named HibyMusic this is the only free usb player, support Flac. The second log is all about this player, shorter. The first one contain more stuff, disconnect and reconnect the dac etc.
[Galaxy Tab S Android Development] :
What I can see from dmesg, the FIIO K1 is recognized by the kernel and (like in [MENTION=2983236]ristokoo[/MENTION]'s dmesg) registered; but then it gets unregistered and closed (that's why the node is missing). I have no idea what the process 5506 is, but that's what is initiating the unregistering.

From the logcat I can see, that hiby loads some own libs and is referencing one of its own libs as audio out interface. ithout further inspection, I don't know if the unregistering belongs to this.

To my understanding, an attached dac is an additional audio device. To use it, you need to enable usb-audio rooting in dev-opts, to make this device availible for apps using audio (i.e. videoplayer). An additional app, trying to bypass system and kernel shouldn't be neccessary.

Also: you shouldn't need any additional software to play flac. It plays nice on our rom on internal speaker as well as on bt. I see no reason, why you should need additional software to play on usb audio.

If you want to go to the ground, I would suggest a clean flash with only gapps installed. Plug in the dac and get a dmesg. Start the buildin videoplayer with any video with sound (sound from dac or internal speakers?). Get a dmesg as well as a logcat. Enable usb-audio in devopts, start the buildin videoplayer with any video with sound (sound from dac or internal speakers?). Get a dmesg as well as a logcat.

The general problem with debugging closed source third party software, is that it is closed source... ;) Therefor it's neccessary to get the additional software ou of the game.
[Galaxy Tab S Android Development] zigonneux:
hi, i always activate usb audio in developer option. No other programs would do anything at all with the Kii0, total silence, but my other small DAC play fine with 90% of the audio apps,so I'm OK. I also wonder why they sell some USB audio player apps , they should all play automatically like the other small DAC I have( VIA chipset 24/96 khz Startech) . Obviously a lot of DAC need their own lib to play we can see many apps that are specific to certain brand of DACs,

Thanks for the testing . I'll give this Kii0 to my sister, it will be better than her motherboard chipset.
[Galaxy Tab S Android Development] :
Thanx for the feedback. I would be completly with you, if this dac has problems on all devices. But though it runs on some devices, I think thee might be a solution - or at least - a workaround for that. Such issues are itching me.
[Galaxy Tab S Android Development] ymlik:
Hi [MENTION=2983236]ristokoo[/MENTION],

Could you build a CM13 version for our T800 please?

Regards.

Ymlik
[Galaxy Tab S Android Development] ristokoo:
Sure, I'm at home so no problem. Should be up in an hour or two.

Edit: nooo it won't. I misread, thought you were asking for 12.1 :)
[Galaxy Tab S Android Development] :
Please don't publish if you use my source: it's still permissive and therfor very dangerous in conjunction with root enabled. That's exactly the reason, why I was holding this back since 2 weeks till I've (or anybody else for that matter) fixed the selinux issue. Nvertigo builds are known to be stable and secure - the current status of cm-13.0 for chagallwifi is not good enough to be an nvertigo build.

And please, don't publish in this thread - this one is for cm12.1 only. Discussing two roms in one thread will end up in an unreadable thread.

EDIT: feel free to build cm-13.0 from my sources, and open your own thread - I would recommend a massiv warning about the risks users take, if running permissive and root at the same time.
[Galaxy Tab S Android Development] ristokoo:
Oops it's me and my lack of paying attention again;) I just glanced quickly and thought someone wants a fresh build of the ROM this thread is about.

Of course I won't publish a CM13 build. I have stated this earlier and nvertigo67 has given us good reasons why it is so.

Edit:

Sorry if this is too much off topic. A friendly note to those interested in CM13 for the T800:

Build it yourself, it's not rocket science! What you need is a Linux (or a Mac I suppose) machine. This can very well be a virtual machine, running on Windows and the brilliant free VirtualBox software (I think VMWare Player is also free for personal use). A decent, modern PC should be powerful enough to run a virtual Linux box.

I admit it takes quite a bit of reading and probably some trial and error but is doable. If you're not familiar with Linux it takes even more reading. But help is available all over the net, XDA being one obvious source. I managed to set up a building environment following the excellent instructions given by [MENTION=4405529]nvertigo67[/MENTION] in this very thread.

CM13 will not be offered in this thread, please respect that. But it's a good thing to want to try it. If you want it hard enough, you might even learn to build it. Sources are available... ;)
[Galaxy Tab S Android Development] :
No problem - propably I wouldn't have noticed myself, but since I have two cm trees at the same time on my disc, I'm looking very(!) carfull at version numbers.. ;)

BTW: anybody is invited to check my cm13.0 stuff, since the klimts and even chagalllte has shimming and preloading working with enforcing... The problem is, that I can't see any denials - simming and preloadingjust stops working, if I use an enforcing kernel. I'm quit lost here, because I see no errors at all - it jus stops working. Since this is 12 thread, I would ask you to reort any findings via pm. Thanx in advance.

Sidenote: even if we sort out this issue, cm-13.0 is far away from beeing a full featured daily driver - I would call it somthing between proof of concept and alpha. I know, that everybody is marshllow hyped, but at the moment this rom is the way to go, to get the most out of your chagallwifi.
[Galaxy Tab S Android Development] :
Awesome. This is a nugget! Yo are soooooo damn right! I don't know if I should put it in OP or in my signature.

EDIT: sory, ran out of thanx for today.
[Galaxy Tab S Android Development] zigonneux:
ok guys , call me crazy, I've found a great price on another DAC, a Fiio Q1 with his own battery pack ( the other was a K1 ) *** super sound ***. This one is working great with the T-800 with most music apps ,YouTube, Vivo with Dev option OFF or ON, no need for a USB player ... So, It must depend of the firmware of the DAC if it work with android or not.

Even my old nexus 7 2013 sound like a super device with the Q1 :good:

Question, what is this option in dev options: Use AwesomePlayer ( deprecated) instead of Nuplayer ....
[Galaxy Tab S Android Development] :
The more important question is, what is the usb-audio-rooting setting for? ;)

Cm comes with two different media player engines: the deprecated AwesomePlayer and the default NuPlayer - with this option you can choose between them.