yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] Sporbillis:
Are we really going to get official nightlies for cm12? A dream comes true!! :D
[Galaxy Tab S Original Android Development] eousphoros:
Build instructions are complete. Now I just need to sort out the vendor git repo, I also need to make a couple updates to the device repo file proprietary-files.txt to pull the proper files.

For now you will want commit 11819673c86fea338cc5847aa34a0f60f8d991b5 for exynos5-insignal.

Initial pass at vendor blobs has also been committed. The probability of getting a working build out of the instructions now is pretty high.

And finally. I have sent the official port request to cyanogenmod. Here we go!
[Galaxy Tab S Original Android Development] dknk99:
Nice, thank you. Will try sometime today to make a build...
[Galaxy Tab S Original Android Development] :
Hi mate,

should I send you congrats or pitty? Your choice - either is honestly. ;)

Thanx for your touchkey interface, but it doesn't work on chagall, since we have a tc300k.

My kernel git has meantime got a cm-12.0 branch with some small fixes from exynos5420 cm git. I my thread I have a commit, if you have probs with HWCService while building.

May the source be with you...
[Galaxy Tab S Original Android Development] eousphoros:
Like you said both are suitable for the situation.

The thing that would be nice about you taking that commit is its the only delta on my side and it would be easier for me at least if my fork varied as little as possible from your kernel. I could put some ifdefs in there so it won't show up unless klimt is defined if that is a concern.

Cheers
[Galaxy Tab S Original Android Development] :
Bro, there is so much anoying issues waiting for you, the sysfs if we are not using is surely none of them: done. Do you need a branch cm-12.0? Or can you live with cm-12.0-sh? (BTW: no ifdefs needed: it is working - we just don't have cypress. And if there is one defconfig file more or less - who cares? I don't.)

Three? Two: the proposed gerrit cherrypicked from [MENTION=3857343]crpalmer[/MENTION], and my "git format-patch -1 --stdout" generated patch, that is "git am" applieable. Do I mis something? (I'm again in the selinux trap: tying to fix powerdoff charging... This selinux stuff one day just hard bricks my brain...)

Hope I helped.
[Galaxy Tab S Original Android Development] eousphoros:
A cm-12.0 branch would be great. Thank you for the clarification on the crpalmer fix. I also found it in your thread like you mentioned.

Exciting times we live in. :)
[Galaxy Tab S Original Android Development] :
Done.

12-work is my personal branch - I test things and may break things.

current-12.0 is where the tested things will go: it is always buildable (in the first place for [MENTION=1409248]lionheartk[/MENTION] and [MENTION=2779578]jewnersey[/MENTION]).

cm-12.0 is where the things go, that have proven to work.

This is for device and vendor gits the same. Ideally all branches are on the same commit.

From exactly now on this rules apply to kernel git:

12-work is my personal branch - I test things and may break things.

current-12.0 is where the tested things will go: it is always buildable (in the first place for [MENTION=1409248]lionheartk[/MENTION] and [MENTION=2779578]jewnersey[/MENTION]).

cm-12.0-sh is where the things go, that have proven to work. This branch has the appendix -sh to give credit to [MENTION=3511708]UpInTheAir[/MENTION].

Additionally I just created cm-12.0, which is on the same commit as cm-12.0-sh at the moment. I will not touch it any more. If you want a commit, drop me a note. I you don't need it any longer, drop me a note.

(If you decide to fix kodi/xbmc issue in synaptics_dsx, drop me a note... ;) )

Take care and good luck!
[Galaxy Tab S Original Android Development] eousphoros:
I will probably get around to the xmbc issue now though its in the middle of my list as far as priority. Thank you for the branch. also good news, it looks like crpalmers fix got merged in. My build is almost finished, if there are people willing to test it I will drop a link. Unfortunately I don't have a device in hand so I haven't had a chance to smoke test it so be brave and patient. There is a good chance it won't work.

https://blck.io/cm-12-20150202-UNOFFICIAL-klimtwifi.zip

Here ya go. Remember I haven't tested this. It might cause your device to turn into a pumpkin.
[Galaxy Tab S Original Android Development] Enddo:
Seems good. Apps work, settings work, MX player works. No explosions so far. The animations for the new boot animation seem very slow
[Galaxy Tab S Original Android Development] eousphoros:
Yay! Thank you for being brave and testing that for me. Can you check netflix and the camera?
[Galaxy Tab S Original Android Development] :
You are welcome.

Take your time... It was half kidding.

And now I give you a good laugh (for relaxing): let's wait for sammy L blobs and kernel sources - they will fix everything for us... :lol:
[Galaxy Tab S Original Android Development] eousphoros:
Right? That is what I keep saying, screw this hard work. Lets just wait for the sammy L blobs *cough* ;)
[Galaxy Tab S Original Android Development] dknk99:
Clean install

SM-T700

Went smoothly without problems

Boots up quickly, boot animation works fine to me

Netflix works

Camera does not work! "Unfortuately Camera has stopped" error msg.

Keys do not work, I tried to set up in preferences (Buttons), no go. Recent button would not do it's thing or vibrate. Rebooted and applied the BlissPop keysON.zip, and the Keys now work. http://xdaforums.com/attachment.php?attachmentid=3117425&d=1421376173

That's what I've noticed so far, overall its smooth and nice...

BTW, I'm compiling from your build instructions. Had two failures earlier today, I updated your git stuff, seen some changes and it appears to be going further than this morning. The errors I got this morning were:

"hardware/samsung_slsi/exynos5-insignal/libhwcService/ExynosHWCService.cpp: In member function 'virtual void android::ExynosHWCService::getHdmiResolution(uint32_t*, uint32_t*)':

hardware/samsung_slsi/exynos5-insignal/libhwcService/ExynosHWCService.cpp:335:22: error: 'ExynosHWCCtx' has no member named 'mHdmiCurrentPreset'

switch (mHWCCtx->mHdmiCurrentPreset) {

^

make: *** [/home/dean/cm12/out/target/product/klimtwifi/obj/SHARED_LIBRARIES/libExynosHWCService_intermediates/ExynosHWCService.o] Error 1"

Thanks for all your efforts, it's appreciated....
[Galaxy Tab S Original Android Development] killall:
Don't use Netflix myself but Camera isn't working. Everything else is smooth as butter. Keys sre working fine here as well.

Thanks.

Edit: signed up for the Netflix trial. Works perfectly. ?
[Galaxy Tab S Original Android Development] eousphoros:
You need to do a repo sync the fix for that was merged today.. And right.. I need to update the gpio file. Thank you for the reminder.

That is a bummer about the camera, can you give me a logcat?
[Galaxy Tab S Original Android Development] Enddo:
I can't check Netflix, but the camera force closed
[Galaxy Tab S Original Android Development] jewnersey:
here is a paste from camera log. (google camera fc)

http://pastebin.com/KmBFTzLC
[Galaxy Tab S Original Android Development] eousphoros:
02-03 14:32:26.100 E/ExynosCamera(2303): [CAM-BACK]-ERR(bool ExynosCamera::m_openIsp(int)):exynos_v4l2_open(/dev/video44) fail (-1)

02-03 14:32:26.101 E/ExynosCamera(2303): [CAM-BACK]-ERR(bool ExynosCamera::m_openInternalISP(int)):m_openIsp(0) fail

Hrmm. That doesn't look good. Thank you for the logcat. This will probably have to wait till I have a device in hand.
[Galaxy Tab S Original Android Development] clutz2000:
I flashed the update over my existing install. I had the same keys issue but the above file fixed the issue. I also noticed that the flashlight option on the notification area will force close if used.

Great work so far though. Keep it up :)
[Galaxy Tab S Original Android Development] dknk99:
Oh yeah, I clicked on the flashlight in notification area. System reset itself, tried it one moire time, same thing. In looking at the logs, it appears to be the camera kernel driver. The camera of course is not working too. I'm not a developer, but it seems the kernel driver needs attention.
[Galaxy Tab S Original Android Development] eousphoros:
Had someone send me a dmesg dump which was the bit I was missing.

<3>[ 90.959664] [B2: Binder_1: 2722] failed to filp_open - /system/vendor/firmware/fimc_is_fw2.bin

<3>[ 90.960185] [B2: Binder_1: 2722] failed to filp_open - /system/vendor/firmware/fimc_is_fw2_3L2.bin

<3>[ 90.960465] [B2: Binder_1: 2722] failed to filp_open - /system/vendor/firmware/fimc_is_fw2_IMX134_EEPROM.bin

Camera is now working after having them rename two files. fimc (EEPROM) and setfile (eeprom). I'll commit the changes next time I'm near a laptop.
[Galaxy Tab S Original Android Development] dknk99:
That's great news, good ole dmsg, I'm a bit rusty (retired), should have thought of that ...

---------- Post added at 08:25 PM ---------- Previous post was at 07:37 PM ----------

I can confirm that the camera and flashlight both work after renaming the two files and a reboot. Awesomne job!
[Galaxy Tab S Original Android Development] eousphoros:
https://github.com/eousphoros/propr...mmit/c1f3b5f75b626fc6f8989fe8fa4d2332339b8816
[Galaxy Tab S Original Android Development] dknk99:
Thanks, I updated my sources and built using your how-to from page one. I skipped the the first part using lxc-docker since I already have a build machine set up with cm-12 source. The compile went smoothly, no errors.

Results:

Clean install on SM-T700

Camera, flashlight, and video works fine.

It's a smooth, lightweight system, installed some Google Play services.

The recent keys vibrate and work using a fix that I applied to my local source code with the help of BlissPop:

http://xdaforums.com/showpost.php?p=57810090&postcount=2

Only thing I have seen so far is that the audio cracks/pops (not too noticeable, but it's there) when screen sleeps. No pops/crackles when screen is active.

Thanks for your help.
[Galaxy Tab S Original Android Development] kisypher:
Does the mic work? I place a lot of VOIP calls hence the curiosity.
[Galaxy Tab S Original Android Development] dknk99:
Ah, good one. Just checked the built in mic app. It works, records, and saves the recording. BUT, no sound during playback on different music players, buit-in, Google Music. Seems we have a microphone hardware issue. Tried Skype test, no audio from mic.

Time for some log checking...
[Galaxy Tab S Original Android Development] open1your1eyes0:
Posting on behalf of a friend who updated the build with confirmed working camera on his device.

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

Feel free to check with him on Twitter if you have any questions.

https://twitter.com/rhcp011235
[Galaxy Tab S Original Android Development] eousphoros:
Hrmm it was working. I wonder what broke. If you have any dmesg or logcat during the first few seconds of boot and during the attempt to record audio it could be useful

EDIT: ril_connect failure, but nothing obvious in dmesg. My first guess is https://github.com/eousphoros/android_device_samsung_klimtwifi/blob/cm-12.0/audio/mixer_paths.xml I should have the device in hand tomorrow. So if someone doesn't fix it before then expect a slew of commits in the next couple days.

02-05 16:25:49.401 I/MediaCodecSource( 2296): MediaCodecSource (audio) starting
02-05 16:25:49.403 I/MediaCodecSource( 2296): MediaCodecSource (audio) started
02-05 16:25:49.414 V/audio_hw_primary( 2296): select_devices() devices 0x2 input src 1 output route media-speaker input route media-main-mic
02-05 16:25:49.424 V/audio_hw_primary( 2296): adev_set_call_audio_path: ril_set_call_audio_path(2)
[B]02-05 16:25:49.424 E/ ( 2296): ril_connect() failed[/B]
02-05 16:25:52.187 V/audio_hw_primary( 2296): do_out_standby: output standby: 0
02-05 16:25:53.364 E/AudioTrack( 2676): AudioTrack::set : Exit
02-05 16:25:53.377 V/audio_hw_primary( 2296): start_output_stream: starting stream
02-05 16:25:53.378 V/audio_hw_primary( 2296): start_output_stream: stream out device: 2, actual: 2
02-05 16:25:53.404 I/MediaCodecSource( 2296): encoder (audio) stopping
02-05 16:25:53.407 I/MediaCodecSource( 2296): encoder (audio) stopped
02-05 16:25:53.407 I/MediaCodecSource( 2296): puller (audio) stopping
02-05 16:25:53.413 I/MediaCodecSource( 2296): puller (audio) stopped
02-05 16:25:53.420 V/audio_hw_primary( 2296): select_devices() devices 0x2 input src 0 output route media-speaker input route none
02-05 16:25:53.427 V/audio_hw_primary( 2296): adev_set_call_audio_path: ril_set_call_audio_path(2)
[Galaxy Tab S Original Android Development] dknk99:
Looked at the logs when using the camera to capture video and sound (works), it appears to grab the mic from a different route (media-second-mic) than the mic app. (media-main-mic)

02-06 10:58:06.745 V/audio_hw_primary( 2301): select_devices() devices 0x2 input src 5 output route media-speaker input route media-second-mic

You are most likely on the the right track with the mixer_paths.xml file! (My humble newbie dev opinion...)
[Galaxy Tab S Original Android Development] dknk99:
So I went ahead and edited my local copy of mixer_paths.xml and changed one line just for fun. Rebuilt cm-12 current, clean install, with the change. I'm happy to report that the Camera, flashlight, Video with audio, Sound Recorder, and Skype test call all work.

Just made media-main-mic (soundrecorder and skype use this) the same as media-second-mic.

<path name="media-main-mic">
<path name="channel-left" />
<path name="back-mic" />
</path>

to this

<path name="media-main-mic">
<path name="channel-right" />
<path name="back-mic" />
</path>

channel-left changed to channel-right.

This may not be all that needs to be done (or even the proper change!) on the xml file but this one change made the mic work for what I tested.
[Galaxy Tab S Original Android Development] eousphoros:
Want to give me a pull request for the change? I'll merge it.
[Galaxy Tab S Original Android Development] dknk99:
Looks like rhcp011235 has put in the request already.
[Galaxy Tab S Original Android Development] open1your1eyes0:
Courtesy of [MENTION=2666421]rhcp011235[/MENTION]

Changelog:

- Fixed Camera

- Fixed Microphone

https://www.androidfilehost.com/?fid=95916177934524350
[Galaxy Tab S Original Android Development] interfreak:
Thanks for this!!

Have installed it, working like a charm. :D
[Galaxy Tab S Original Android Development] dknk99:
It is definitely working, there are issues with certain channels in the 5 GHz range. Turn off auto channel in your router and manually set it to one of these channels: 36, 40, 44, or 48.
[Galaxy Tab S Original Android Development] kisypher:
T700 clean install.

·· No 5G

·· Mic does not function for VOIP calls in textPlus.

Sold ROM otherwise. Nice work. [emoji106]
[Galaxy Tab S Original Android Development] eousphoros:
Just got the replacement tab today. To kick it off here is a new cyanogen recovery. Next up a new build of CM12 with the camera fix, @dknk99 & @ rhcp011235 media_mixer.xml fix, some kernel patches from @nvertigo67, and a couple other misc fixes that I will mention when I post the build.

https://blck.io/c-recovery-20150207-UNOFFICIAL-klimtwifi.img
[Galaxy Tab S Original Android Development] Enddo:
Is this new recovery critical? Has anyone tested this by flashing it with Flashify(I'm lazy like that :p)?
[Galaxy Tab S Original Android Development] eousphoros:
Nah, in fact I am not a huge fan of the new cyanogen recovery, but for those who want to use the complete cm suite I am providing it.
[Galaxy Tab S Original Android Development] dknk99:
As I mentioned earlier, there is an issue on 5ghz wifi, but if you can change your wireless router settings in it's 5ghz config, turn off auto channel scan (if on) and manually set 5ghz to one of these channels: 36, 40, 44, or 48. I'm currently using 5ghz with latest build, have my wifi router set to Channel 48 - 5.240 GHz.

The mic in textPlus is another issue and I believe I see the problem. Will test it this weekend.
[Galaxy Tab S Original Android Development] eousphoros:
Updated the first post with the new recovery and cm12 build (s2r5). It includes the before mentioned fixes as well as faster bootup times and now properly configuring the capacitive keys by sec_touchkey.kl
[Galaxy Tab S Original Android Development] dknk99:
The keys work, but if you want them to vibrate I've found you need to add VIRTUAL to the end of both entries in sec_touchkey.kl and reboot to pickup the change.
[Galaxy Tab S Original Android Development] eousphoros:
My earlier builds had that flag set but I found it would cause those keys to be active even when the device was a sleep which is less then ideal. Have you tried it?

EDIT: Just tried it and that issue is still there.
[Galaxy Tab S Original Android Development] dknk99:
Yes it is, but I guess it's a personal thing, I like the vibration when using the tablet. When it's asleep, I really don't care that they vibrate. It would be a nice if there was a way to turn it on or off via gui though, or somehow have it turn off when asleep. But it's a minor thing...
[Galaxy Tab S Original Android Development] eousphoros:
I could probably throw some java code together to do that if there is interest
[Galaxy Tab S Original Android Development] CrashTestDroid:
I'd like to see the hardkey vibration jettisoned or at least optional. That brutally bright backlight is bad enough without adding vibration to it. Thanks for your persistence and awesomeness [MENTION=2346758]eousphoros[/MENTION]
[Galaxy Tab S Original Android Development] dknk99:
I dont care for the button backlight either, and its easy to turn off in Settings. The vibration is off in this build so its all good. I don't mind the vibration,so I turn it on by editing the file. It should be in settings too, enable/disable vibration. But, I think there are other more important things to do before any dev time is spent on that.
[Galaxy Tab S Original Android Development] Duskye:
I'm still having issues with sound while the tablet screen is off. If I play music with headphones on and if I have the screen turned off, I have a lot of static, turning the scream on fixes this problem, no static is heard when the screen is turned on.
[Galaxy Tab S Original Android Development] eousphoros:
Bluetooth or wired?
[Galaxy Tab S Original Android Development] fedecape:
Hey guys, thanks for this great rom. One quick question: why do I have 2 Android os/system draining my battery? Thanks
[Galaxy Tab S Original Android Development] CrashTestDroid:
You're right and I've made the jump to Lollipop with this CM12 as daily driver. So far very good.
[Galaxy Tab S Original Android Development] danny19901:
Android L has been confirmed by Samsung

I know CM12 is better than Touch Wiz but this is great news as we should have new drivers and Blobs :D which should help improve CM
[Galaxy Tab S Original Android Development] mrcet007:
Good but cm 12 is better than Samsung touch wiz..
[Galaxy Tab S Original Android Development] dancress:
way to treat customers of their top tier tablets. 9 to 10 months! they should be rolling out L to their 99 euro bargain bin tabs by then.
[Galaxy Tab S Original Android Development] dknk99:
I have the same issue when playing through the device speakers and screen is off, when on, no problems. Bluetooth works fine, no cracks/pops screen on or off.

,
[Galaxy Tab S Original Android Development] Duskye:
Basically what dknk99 said. Anything wired or speakers has a lot of static when the screen is turned off, when on there is no static.
[Galaxy Tab S Original Android Development] eousphoros:
Weird I can't reproduce this. What is the audio source?
[Galaxy Tab S Original Android Development] kisypher:
Has anyone attempted using the mic with apps like textPlus to place VOIP calls? That lack of function is the only thing keeping this ROM from being my daily driver. Love everything else about it.
[Galaxy Tab S Original Android Development] eousphoros:
There is a pull request to fix that. I'm just waiting for him to clean it up before I merge it. Worse case you should have a working build tomorrow.
[Galaxy Tab S Original Android Development] kisypher:
Thank you for your efforts on this! I, like many others here, really appreciate your work. [emoji106]
[Galaxy Tab S Original Android Development] eousphoros:
Just kicked off a new build with two audio microphone patches, 5 ghz ccode change, and a repo sync.

https://blck.io/cm-12-20150209-UNOFFICIAL-klimtwifi.zip (s2r6)
[Galaxy Tab S Original Android Development] jewnersey:
thanks

which commit fixes the 5ghz issues?
[Galaxy Tab S Original Android Development] dknk99:
I would like to know too as I don't see anything obvious. It seems to work as I'm able to connect 5 ghz on my router at a higher frequency (channel 149), than before. It would only work for me previously on channels 36 through 48, good job.
[Galaxy Tab S Original Android Development] eousphoros:
https://github.com/eousphoros/propr...mmit/a4c42e76d293fdf67a7b8495f86c502d127f8e2f

Also another random factoid. The latest build has been downloaded 202 times already.

I was digging thru the other artist devices commits and it looks like [MENTION=4405529]nvertigo67[/MENTION] has fixed the move to SD (app) bug with an fstab change. I am also working on the soft keys reenabling themselves and some fixes for gps. Anything else people would like to see in the next release?

On the problem of soft keys re-enabling. How long does it usually take? Does it happen after being asleep for awhile? Trying to reproduce it but haven't been able to yet.
[Galaxy Tab S Original Android Development] kisypher:
The mic works perfectly for textPlus now, thank you! Absolutely love this ROM!
[Galaxy Tab S Original Android Development] dknk99:
Ok, so I have been playing around with the performance settings as I have been having the same issue. If you go to Settings -> Performance -> Processor -> CPU governor. The default is "interactive". Set this to "performance", see what happens. For me, it removes the pop/crack when screen is off. Try other ones too, see what happens. I found "powersave" seems to work too. Your mileage may vary. Try it out, not sure what else would be affected by the change, remember this ROM and what I am proposing is cutting edge, good luck. I'm using powersave for now all good. Pops/cracks are gone from builtin speakers, listening to podcasts with great results......and screen is off....
[Galaxy Tab S Original Android Development] eousphoros:
Hrmm that is an interesting bit. What audio app are you using that generates static? Or do all audio apps do it? Youtube? Google Music?
[Galaxy Tab S Original Android Development] dknk99:
I am using the built-in Music app or Google Music to play local mp3's or Podcast Republic to stream podcasts, even download podcast to storage and play then. I get pops/crackles when screen is off (not overbearing, but there). With the CPU Governor change it appears to be gone.

As well, before CPU Governor change, often if playing music and screen is off when I turn screen on, I often but not always, get a music hiccup(pause). Seems like processor sleeping - not ready for the wake action....(make sense?)
[Galaxy Tab S Original Android Development] eousphoros:
Yeh totally makes sense. I am just confused why I haven't noticed this yet. I'll dig into this one too, but no promises it will make it into the next release.

Good news on one of the issues I was having trouble reproducing. (Disabling the touch keys will re-enable themselves). I found one way to reproduce it is to reboot. That makes sense and I can fix that pretty easily. Are there other scenarios that people are encountering that causes this to happen?