yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] zigonneux:
does this mean that you are done with cm12.1 for chagalwifi and going to cm13 slowly but surely ?

anything else you want to fix in CM12.1 ? I wonder what more you could do...
[Galaxy Tab S Android Development] :
Second question first: I still would like to fix bt/wifi, mhl and onscreen navbar - but for the first two issues I run out of ideas, and for the latter I need some kernel hacking help (see OP).

For the first question: I don't know. Cm-13.0 is quite disapointing. The "under the hood" changes in cm-13 make all "hacks" to bring cm-11 and cm-12 to chagallwifi useless. At this moment drm, hardware accelerated video de-/encoding and gps is broken. For using some blobs, I need some dirty symbol hacks...

Of course this is no real showstopper to push an alpha rom, but I'm really afraid of user reactions: most of the users don't want to read any more, when asking for logs, I'm blamed for being harsh; and quite some users behave like they have hired us devs.... :( So this is no good place to push an alpha status rom. :(

At this moment I don't know how to continue.
[Galaxy Tab S Android Development] chazey2:
I have to say [MENTION=4405529]nvertigo67[/MENTION] I used your 12.1 on my T800 for some time and found it brilliant! Along came a CM13 T800 Rom and I switched to try it and have never gone back, for me and how I use my tablet the only fault on the cm13 is no working camera. But then I never used it anyway. Can see how for some this would be a deal breaker video/web based calling. I believe you would be able to given time produce a dam good version of cm13 for our tablets.

The second part- If some morons cannot read, cannot appreciate, and cannot understand the work you and other Devs put into updating our devices then sod them! Ignore them, if we all did then they would just fade away!

So I say continue what your doing at your own pace, ignore the morons and you and the normal decent XDA members will profit.
[Galaxy Tab S Android Development] :
To avoid confusing some one: at this moment there is no cm-13 for chagallwifi - I think you are talking about aosp6 from [MENTION=2371134]Schischu[/MENTION].

I tought often about ignoring some postings. Sadly rumors, half baked "knowledge" and false information have their own lives: if one doesn't correct those statements, the false information will hit back... Just read in an other thread, that all custom roms for chagalllte have a jeating issue... But my point on putting out an alpha rom, is the disturbing noise: I'be seen dev threads with basic flashing questions on nearly each page, again and again... Belive me, if you are struggling with some masty, ugly hacks to get proprietary code from LL running on MM, this noise isn't helpfull at all.
[Galaxy Tab S Android Development] chazey2:
Sorry my bad you are correct not Cm13 but AOSP.

But my point on idiots remains the same,

nobody

has the right to demand this and that or anything from anyone for something that is provided for free. The only expense is to the creator in his hard work and probably limited spare time- not the end user, period.
[Galaxy Tab S Android Development] Schischu:
You will also get there, believe me ;) Gapps on MM are annoying as hell.

Also I tend to leave certain things to the ROM community, a ROM creator can and should not respond to every question in my opinion.

Who has the time anyways? ;)

Btw. I had this issue with HW accel to, that's why I switched back from the -cm hw repos an using the old one again. At least these work without any issues.

(I saw your switch on github and just thought, ok good luck there. ;))

If you have specific issues, you can send me a note. I'm pretty sure that I had them all. :P

PS: I like smileys :)
[Galaxy Tab S Android Development] zigonneux:
Nothing burn me more than when I read on the Schischu's thread : hurry up to fix the camera issue, i use this rom as my daily driver and I need my camera. !!!!!! WTF are they thinking

[IMG="hair"]http://i66.tinypic.com/1ze8tur.gif[/IMG]
[Galaxy Tab S Android Development] :
;);):angel::laugh::laugh::silly:

Just when you wrote that, I started switching from slsi-cm back to slsi-insignal. And what should I say: you caught me not reading! ;) I was always following your device-, kernel- and vendor-gits, but never at you other gits... You have already done the work. When starting the "downgrade", I was only thinking of hardware accelerated video: if the new stuff doesn't work, let's take the proofed to ne working old stuff. But after reading your frameworks/* commits, I think that's a way: use the old camera stuff as well. My roadmap: getting OMX and drm up again, getting gps up again and then tty to use old camera blobs (KK), 'cause our old camerawrapper does not want to play with LL blons. Any way, I will kang like a caribian pirate, and report back. Thank you.

I don't want to disapoint you: but gapps was the only issue I wasn't running into. Mate, I was so prepared: had three different gapps packages on my usb stick (I was sure LL will eat my external sd card), but after I wiped /data, /cache, /system and dalvik-cache dirs, rom and opengapps nano flashed like a charme, and I never saw a forced cloasedmon play services. What cought my eye, was in the flashable zip: in this zip there is a directory system with only the build.prop file. I'm not sure, if this safed me from gapps hell.

Sidenote on camera: I have never used my chagallwifis cam, other then for video calls (front) and test pictures. For taking poctures I use my mobile - so much for my personal usecase...
[Galaxy Tab S Android Development] Schischu:
FYI regarding camera. This seems to be a problem with the new linker binary. It resolves the NEEDED libs differently. Especially for recursive libs.

That can be easily confirmed by adding a print to libion and libionexynos in the ioctl function. It uses the wrong one.
[Galaxy Tab S Android Development] :
Not sure here: if you look at [MENTION=3594812]ShevT[/MENTION]'s lt033g git or official cm treltexx, what they do to het gpsd running (libdmitry, libsamsung_symbols and the loading of this two libs), this could be a way to fool the linker... Honestly I had to admit, that I understand only half of the stuff, they do with the proprietary gpsd (libdmitry implementation is quite well documentated in the source code.
[Galaxy Tab S Android Development] :
W EXYNOS_COMP_REGS: dlopen failed: dlopen failed: cannot locate symbol "_ZN7android19GraphicBufferMapper4lockEPK13native_handleiRKNS_4RectEPPv" referenced by "/system/lib/omx/libOMX.Exynos.VP8.Encoder.so"...

Get them for each single OMX lib. Will now try to build and load linsamsung_symbols.so. Did you have this issuue?
[Galaxy Tab S Android Development] Schischu:
Of course ;)

I don't like the _symbols or dimitry libs. CM calls them shim libs.

They don't have an alternative cause adding manufacture specific symbols to the source does not scale well to the many devices they support.

However for us it is way easier to simply add the missing symbols to our code.

If you check my frameworks repos you can see that I added several symbols which are needed for our blobs.

I'm at work so you have to look for yourself. ;)

The libion error also occurs for hw acceleration. You can see it in the log that lots of ion_ioctls fail. However it seems to work nevertheless.

The stupid thing about libion is that the functions have the same name so the lib which is first loaded wins. Or was it the last one, hm.

And exactly this behaviour has changed with MM in the linker binary.
[Galaxy Tab S Android Development] :
You are right - and in condradiction to libsamsungsymbols, I understand your chanhes better.

I have completely merged framworks/av frameworks/native and system/core into cm-13.0 branches (frameworks/base seems to have only some featueres and gps commit reverted) . OMX is working again, drm is loading, but failing later (this device does not support widevine), but I think this will be solved when changing drm blobs to chagalls.

Do I need more merged?

I have no libion errors. But I have still a lot of "E hwcomposer: invalif gralloc handle (at 0x0)" and some EGL errors.

I will push all merged gits tomorrow, alaong with some more educated log excerpts. Today I' to tired - and nobody wants me to have chaos pushed... ;)

Thank you very much - I like the way you think!
[Galaxy Tab S Android Development] Schischu:
Probably, we will see ;)

I already have some drm fixes which are not pushed yet. They are not complete yet however the drmtest at least that we are widevine capable.

It fails later on nevertheless. I think I have some secure storage stuff missing.

Yeah thats the error. Caused by the invalid libion function.

A quick hack for it would be to misuse the shim function.

on init
export LD_SHIM_LIBS "/system/lib/libexynoscamera.so|libion_exynos.so:/system/lib/libhwjpeg.so|libion_exynos.so:/system/lib/libcsc.so|libion_exynos.so:/system/lib/libbinder.so|libion_exynos.so:/system/lib/libexynosv4l2.so|libion_exynos.so"

This way we are forcing some libs to use the proper lib. With this line you should also get further with the camera init. It will still fail, but at least at a later point.

It could be that we could solve the whole issue by using these shims, but figuring out which functions all use the wrong call, hm. ;)

Better way would be to patch linker binary to use the old behavior again.

For that we would have to trace how it is done on cm-12 and then what happens on MM.

But I really don't want to flash CM again. :P
[Galaxy Tab S Android Development] Schischu:
The EGL error I never had.

DRM: Yes I added the needed functions to boringssl, will push later today.

Also make sure that the vendor drmserver is running and not the android native one.

GPS: I think this is due to gpsd not running. Start it from console, it will probably tell you that symbols are missing.

Camera: Yes that is the error when the wrong ion functions are used.

Interesting that shim behaves different on CM. Have to check my shim implementation.

I don't think that it is gralloc. Anyways this can be easily testet by adding the printfs in the functions and run it once for cm and once for mm.

At least thats how I done it.
[Galaxy Tab S Android Development] Schischu:
Not using Samsung blobs is cheating !!! ;)

I'm currently unable to make a log, however at least this

Could not read /data/mediadrm/IDM1013/ay64.dat2: No such file or directory

I also get with the samsung blobs.

Btw. I have the same behavior on P605 MM which is Snapdragon.

So more or less a general MM port error.
[Galaxy Tab S Android Development] :
Just checked opo: drm is not running at all (build three days ago). Let me try cheating with the old (but known to ne working) widevine manta blobs. (BTW: I was told, it is not cheating, as long as you don't put off yoir clothes of - I promise I develop at least with underwear on... ;) SCNR)
[Galaxy Tab S Android Development] dwarfer66:
Is the latest download link available yet?
[Galaxy Tab S Android Development] :
Just a thought (or two): If I understand whats going on in gerrit, insignal is definetly dead (I remember the attempt to remove insignal and only use cm's slsi when going from cm11 to cm12). Also cm seeems to move from gcc to clang as default compiler frontend. I'm really not sure, which way to follow: using the ported insignal version is a solid and quick way to het cm13 up and running, but on the long run cm's slsi is better integrated, maintained and supported.
[Galaxy Tab S Android Development] ristokoo:
I've been a happy user of nvertigo67's CM version for some time. A big thank you for nvertigo67 and Schischu for having your discussion here. Not being a developer, I understand very little but still it makes an inspiring read. It seems we have something interesting to look forward to :)
[Galaxy Tab S Android Development] :
You are welcome.

For cm13: the differeces from cm12 to cm13 under the hood are much more complex, then I thought. It wil take it's time to get it to an usable state. To get it to a stable status like cm12 will take even more time. I don't want to make you expect a stable cm13 for chagallwifi in the near future. For a user looking for a full featured, stable, bat friendly and daily-driver-ready rom, cm-12.1 will be the rom of choice for quite some time.
[Galaxy Tab S Android Development] ristokoo:
Good point, this is exactly what I plan to do. Your unofficial CM12 is an excellent rom and it works perfectly for my use. And just to clarify: I don't mean to put any pressure to CM13 development ;)

I suppose the hardware of our Tab S will still be valid for at least a year or two (probably more). So let's hope you two, and why not also other developers, will find a way to bring us a nice MM experience.

Isn't Samsung going to release MM for Tab S at some point? If they do, will it help your development?
[Galaxy Tab S Android Development] Schischu:
I however have no problem with calling my ROM stable. ;)

To be fair, it's already 4 months old.
[Galaxy Tab S Android Development] :
Latest rumors I heard of, say no MM for Tab-S.

Maybe. On the one hand it is helpfull, to have blobs and kernel sources matching the android version you develop for. On the other hand, if kernel sources don't have drivers for the blobs (and I belive samsung is doing so by intent to decallerate opensource development), like on BOCC, developing becomes even harder.
[Galaxy Tab S Android Development] :
My dear friend, I was talking about my cm13 attempts compared to cm-12.1 rom. I never would judge your aosp rom (I have tested it for about 3 h - not nearly enough expririence with aosp6 to make a statement on stability).

After rethinking, I decided to go back to slsi-cm: slsi-cm and building with clang seems to be cm's path of development. I will try to follow them on that path, because maintaining a released cm rom will ne much easier. Anyway: great work to push insignal to android6, and thank you for letting me use your work.
[Galaxy Tab S Android Development] Hookmt:
Ran into one strange problem. Tried to search and couldn't find any other mention of it in the thread or on Google, but for some reason when playing Mp4 video, I get a strange audio distortion, especially on speakers, where the voices all sound like they have a lisp. Seems both odd and specific. I had been using IronRom until about a week ago so I restored a Nandroid and, sure enough, the distortion was gone.

I'm not sure my video watching is a priority (except to me), and shouldn't be for the dev, but I'm curious if anyone might know why this might be happening.

Thanks in advance for any help and apologies in advance if I missed something in my searches. This is a fantastic ROM.
[Galaxy Tab S Android Development] Mrodfr:
Hello, Its my first post here. sorry for my english.

previously a user of the stock samsung rom rooted with a handmade clean and now a user of this cm12.1. this is my first custom rom and first android device, even if I use it since more than one year.

I would like to report problems and remark about this custom rom cm-12.1-20160203 on my galaxy tab s t800.

agenda program: (from the builds):

launch this program and choose the planning menu. the tool try to show the planning window and quit with a "Agenda" has stopped. this problem everytime.

android keyboard (AOSP) with the manerial dark theme and french keyboard:

if I used, from a,z,e,r,t,y.... keys, there are second choice more or less big list of another keys. if I use the a, I can choose 1 and others keys. if I use the a key and keep it pressed, a little window show me the other keys available. this little window have a white background and light grey keys. Impossible to read. NO problem when remplacing by the google keyboard from the play store.

3c TOLBOX PRO:

On the 3c TOOLBOX PRO, there are features and one of them is the system management menu with:

build, sysctrl, entropy, FS cleaner, SD, memory and others.

most of the menus don't work, for example, sysctl, entropy, sd....

for example, sysctrl is completely empty and entropy do nothing...

Theses menus work well with my previous stock rom samsung rooted. I don't know if Its caused by 3c toolbox pro or CM12.1. just would like to report and have a point of view.

the 2 hardware buttons at the bottom of the tablets:

on the original stock rom, the 2 hardware buttons show light only when used by a finger. on the CM12.1 rom, the light is showed also when using all on the screen. I prefer myself a use like with the stock rom than now.

can I change the use of the light for the 2 hardware buttons to look like the original sansung ROM or is is impossible ??? Could we have the samsung ROM use for the 2 hardware buttons in the futur ???

The display:

on the original stock rom, samsung add 4 or 5 configured mode display: optimiser, standard, cinema, pictures. The standard display mode was the best for me, and confirmed on internet review of the tablet I have read previously( 6762 Kelvins). Now The display on the CM12.1 rom is too heavy in color for my point of view. Unfortunately, I don't know how found again the display I have used with the stock rom.

Is it possible to add again this features on the CM12.1 rom ??

This CM12.1 rom is verry good rom and I like it a lot now. Thanks for the work done for this rom. I'm a verry verry happy user of my tablet with this rom now.

I have just would like to share a few little problems I have found and maybe, good remark.
[Galaxy Tab S Android Development] :
You missed nothing.

To my knowledge m4v is apples proprietary container format. It's basically very similar to standard mp4, but with proprietary code for drm added. From you description I guess, drm is working. That's good (in cm13 drm isn't working on opo and chagall). I'm not familar with m4v, 'cause I try to avoid apple and microsoft propriatary **** in my life.

The sound dissortion may be caused by an missconfiguerd audi codec, player or unsupported audio codec.

Now it gets complicated: I would like to test the file you are using with the player you are using, what would be illigal, if the m4v has copyprotection on. If this is the case, please tell me what player you are using and provide a logcat: play your m4v for 20 sec, then get the logcat (posting #3).

What you can try meanwhile: try an other player (mx player, diceplayer, etc.). If you are familar with ffmpeg on the command line, try converting your m4v to mp4 (aka throw away drm part ;) ). With ffmpeg you can also convert the audi stream from the m4v, just for testing.
[Galaxy Tab S Android Development] Hookmt:
Yes, it would help if I didn't make an outrageous typo in my help request. :rolleyes: These are MP4 files, some I have encoded using Handbrake, some not, makes no difference. I have the same result whether playing on VLC, Act One or DroidTV.

Additionally, I restored a Nandroid of IronRom and it no longer does it.

Later today, I'll flash back and try getting the logcat, thanks.
[Galaxy Tab S Android Development] :
[MENTION=7228239]Mrodfr[/MENTION]:

For agenda:

Please provide a google play link. I can't find an apk called agenda from builds.

For the keyboard:

There are quite some designs out there, which will introduce some funny issues. Please check keyboard without any theme installed. Uninstalling is you first try, but perhaps you need to clean flash. You can also check the version of your gapps package: some replace aosp keyboard. I use opengapps nano. Which does NOT replace the keyboard. On other gapps packages you have to configure to omit keyboard replacing.

3c toolbox:

I don't use that app. So I can only test with toolbox without "PRO". As you can see in the attached screenshot, entropy is not empty. What does the developers say to your support request (they are explicitly asking for support requests for their current version (at least if you first time start the non-PRO bersion)? Have you ever tried the free, sourcecode open (I hate rooted apps without open source on my devices: ad enabled, rooted apps without source code are evil! I have deinstalled toolbox ditectly after taking the screenshot for that reason: apps loke that are a real security hazzard - YMMV, of course.)

Capacitive buttons:

Sadly this is a "feature" of cm. I don't like it, too. I have disabled the buttons lights all together and I'm happy with it. I won't change the standard behavior of cm. So your only chance will be a feature request on cm.

Display:

We have dnie lite - but all SamsungService implementations I found are for dnie (without lite), which is slightly different. So I put for your convience a file in /system/etc/init.d/ called 10systemtuning. At the end of this file you can set your display profiles by uncommenting and setting the desired value. Reboot and you are done. This file is overwritten, if you update (aka flash) the rom. If you want it persistant move the file to /data/local/userinit.sh and make it executable.
[Galaxy Tab S Android Development] NoFaQ:
I haven't used 3c Toolbox, in a while, (Kernel Adiutor works fine for my needs), but I have the pro version and will redownload and check what was mentioned.

Edit: I've gone through all menus on 3c Toolbox Pro. I can't find anything that doesn't work on it. I also double checked the items that were mentioned. I am on your last unofficial build dated 20160123.
[Galaxy Tab S Android Development] zigonneux:
I've never had problems with M4v files, they play very well here. I use VLC player
[Galaxy Tab S Android Development] Hookmt:
Yeah, I kind of figured this had to be some kind of specialized problem at my end. Believe me, if other people heard this kind of distortion off the TAB S, they'd be screaming, so I didn't really think it was the ROMs fault. Was just hoping the smart rounds here could help me figure it out.

However, since technology likes to humiliate me...

I reflashed the Nandroid backup I made of my setup on this ROM just before restoring IronRom to test, and now everything works perfectly. I'm happy because I love this ROM and I love watching videos on the commuter train, but I feel like an idiot. :rolleyes:

Thnaks to [MENTION=3456089]nvertigo[/MENTION] (and you) for taking me seriously enough to answer. :good:
[Galaxy Tab S Android Development] zigonneux:
Anyway we should have a new Rom version soon because of the february security fixes, so it would be your chance to try it once again and use another Gapp and a VERY clean install. Those Roms are strange, I have a game that play well with every 5.1.1 Rom except CM12.1, but i don't bother with it because I can play it on my nexus with MM6

( game : PRUNE, it won't start) since i'm using CM for T-800 , that game never played anymore. Not a big concern.

Question to nvertigo, what size Gapps maximum can we install ? I know it's written nano in the main page but could we go for more ? like micro or mini... ? If you're not sure I can just try and report ...
[Galaxy Tab S Android Development] :
I'm uploading at this moment for the third time... If I could have some stotge where I could use "rsync --partial" The first two attempts ended at 91% amd 88% due to my bad internet connection. :( So stay tuned... ;)

Have not the time to check prune today. Have you zried enabling 4x MSAA lin dev options?

(Any question is appriciated, as long as it gibes enough information to deal with. What bothers me is something like that: "audio has issues; please fix it." [audio is just an example])

Upload finished in this second. For you:

https://github.com/nvertigo/android...-20160204-UNOFFICIAL-nvertigo-chagallwifi.zip

All others have to wait till my next posting... *lol*
[Galaxy Tab S Android Development] :
New Build: 20160204

Build 20160204:

Maintain release.

ROM: https://github.com/nvertigo/android...-20160204-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5: 21e12daf9066c1a66f41666bb213a83c

Happy Flashing!