yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] PewPewK:
I took my SD Card out and now I'm not getting Mediaserver eating the battery, but I'm still dying just as fast. Now it's being attributed about 50-50 to Android System and Kernel (Android OS).

So in short...

SD Card In: 1h 10m SoT with 80% battery being eaten by Android (mediaserver)

SD Card Out: 1h 10m SoT with 40% battery being eaten by Android System and 40% being eaten by Kernel (Android OS)

So... yeah. Battery woes continue.
[Galaxy Tab S Original Android Development] hhairplane:
RaymanFX has been working on a CM12 Galaxy Note port, which seems to run the same Exynos chip as ours. Might want to take a look at this post. Thanks again for everything, can't wait to see what the future has in store for this ROM...

http://xdaforums.com/showthread.php?p=57842930
[Galaxy Tab S Original Android Development] interfreak:
Getting 4+ hours SOT with some minor kernel tweaks, still experimenting for the best compromise of speed/power. Will be great one the camera is working!!
[Galaxy Tab S Original Android Development] SS2006:
Why not share your tweaks?
[Galaxy Tab S Original Android Development] interfreak:
I downloaded Kernel Tweaker and set my max CPU speed to 1000MHz, down from 1900MHz. I've not noticed any performance degradation, and have added a crap load of SOT. :)
[Galaxy Tab S Original Android Development] ccnarutofly6@gmail.com:
How stable is this ROM?

How stable is this ROM on Tab S ? I'm currently running Unofficial Cm 12 on Note 3 runs SUPER NICE, absolute no stutter or lag.

How Stable is this ROM? what are most common problems currently facing this ROM?

Thanks for any replys
[Galaxy Tab S Original Android Development] eousphoros:
It will crash on you, it will do things you don't expect, it will consume your battery in 30 seconds and take 8 hours to charge. Unless you like development projects I wouldn't install it.

Since I'm posting I suppose I should give an update.

Last week the hard drive in my laptop died. I have since replaced the failed drive but there was some data loss. Probably wont be a new build till the weekend.
[Galaxy Tab S Original Android Development] SS2006:
I look forward to it ! Thanks man
[Galaxy Tab S Original Android Development] atoy74:
Delete
[Galaxy Tab S Original Android Development] Poser:
Jeeeeez just "lunch" ing on this ROM "clobber" ed your hdd. =D

(I crack myself up)
[Galaxy Tab S Original Android Development] fedecape:
Hey, take it easy [emoji14]

I'm super happy with it and I really appreciate your effort.

I only get about 4 hours of screen on time, yes. But that's enough for a day. My main device is not the tablet, is my OnePlus One!

The only crashing apps were Weather, Google Pay Newsstands, and all that useless bloat. I disabled them and no more annoying poo up messages.

Regarding "things I don't expect", not really! I use it everyday as a copilot (charts, maps, approach plates, PDFs) and it never failed me! (Don't worry, I only fly small training airplanes [emoji14])

Cheer up! Looking forward to your next build
[Galaxy Tab S Original Android Development] fedecape:
Update: pic
[Galaxy Tab S Original Android Development] eousphoros:
Thank you for posting the pic. It is cool seeing the rom in the wild. :)
[Galaxy Tab S Original Android Development] lionheartk:
Yes I am, but on the T800 Lollipop ROM. Seems it's a CM12 source issue then. Any crashes when taking pictures?

Here's the Log of when I try to move the Kindle app to the SD:

http://pastebin.com/xaANaFrP

Also, a log of the Google Camera crashing with the error "Cannot connect to camera" after taking a picture:

http://pastebin.com/zvPqqjyC
[Galaxy Tab S Original Android Development] eousphoros:
One more quick update. Release 8 will be the last release... of series 1. Due to the data loss from the hard drive failure I decided to just start from a pretty clean slate.

This means series 2 will most likely have regressions when it gets released.

The current series 2 build is using the J2 kernel (Decided to go back to samsungs kernel for now) with binary blobs from K2. Just doing some burn in before I post it.
[Galaxy Tab S Original Android Development] interfreak:
Awesome mate, can't wait! :D
[Galaxy Tab S Original Android Development] HobbitCy:
Standing by waiting for series 2 :)
[Galaxy Tab S Original Android Development] Sporbillis:
CANT WAIT!! This rom was one of the reasons i bought the tablet!!! :D Love your work
[Galaxy Tab S Original Android Development] dancress:
DSQ: Is there any way to resolve the video issue yet? Or is it resolved?
[Galaxy Tab S Original Android Development] eousphoros:
Series 1 Release 8 will require you to disable hw overlays in developer options.

It appears to be fixed in my Series 2 Release 1 candidate build. Though there are other issues present there that are making me hesitant to release. (Book cover is no longer working, I am using the open source gralloc atm which causes graphic corruption on rotation and occasionally in app switch, and a few other minor issues.)

On that note is anyone familiar with the kernel change that fixes the book cover switch [MENTION=3511708]UpInTheAir[/MENTION] [MENTION=4193974]Barracuda77777[/MENTION] [MENTION=4405529]nvertigo67[/MENTION]
[Galaxy Tab S Original Android Development] :
I grabbed them from picassowifi (kernel_samsung_exynos5520) cm-11.0 branch. Their were two of them: the first renamed the constants and the second switched valus for constants.

https://github.com/nvertigo/android...mmit/fdf46bfd62252467fe75916ff75c3952c32679f6

https://github.com/nvertigo/android...mmit/ce28d69de11dad28ea067f5ca0afe265469d4230

I haven't worked on cm-12 so far, but have done a few small changes to compile with gcc-4.8, so perhaps my cm-11.0-sh branch will work with cm-12...

For the graphics glitches - sounds like the ones we had on cm-11.0 too): there are two commits in my device tree. One is an aaddition to BoatdConfig.mk or device.mk the other one is a build.prop statement, one fixed rotation glitches and one screenshot glitches:

https://github.com/nvertigo/android...mmit/b8314fc9060da39841962224cd3d3e0e752e0e20

https://github.com/nvertigo/android...mmit/206d21f5a1b7045b00e74d39c5556b8f037d9a19

Hope this helps.
[Galaxy Tab S Original Android Development] eousphoros:
You rock, thank you. I'll get a new build going right away.

Just to follow up. Those commits fixed the graphical issues and the book cover issue. Thank you again. :)
[Galaxy Tab S Original Android Development] jewnersey:
I tried using those CM-11 commits to fix graphics glitching and had no luck.. let me know if you fare any better

here is another good repo to track https://github.com/RaymanFX?tab=repositories , guy has been working with crpalmer and he plans on rebuilding the video blobs (facing same issues as our device)
[Galaxy Tab S Original Android Development] eousphoros:
The graphic glitches are completely gone (at least I haven't been able to produce them despite my best efforts.)
[Galaxy Tab S Original Android Development] jewnersey:
oh sweet! will have to play around and see why it's not working in my builds.
[Galaxy Tab S Original Android Development] eousphoros:
If it matters I did a make clean and rebuilt from scratch after making those changes. I haven't looked into how that build flag affects things though so it may not matter.

So for everyone else the two issues I'm working on tracking down is Netflix hates me again (their DRM is so damn fussy) and mtp is a little grumpy. Once I get those two sorted out ill upload a new build unless someone is really itching to use hw overlays ;)
[Galaxy Tab S Original Android Development] :
Netflix: just an idea: do a diif against our (@barracuda77777s and mine) media_codecs.xml. It was the fix for Netflix - but after getting it to work I never tracked down, which codec was misbehaving. BTW: I changed later on one codec from OMX- (hardware) to ffmpeg-codec (sofware) in order to get preview thumbs for some mp4 videos...

For the record: did I tell youe I hate media_codecs.xml and media_profiles.xml? ;)
[Galaxy Tab S Original Android Development] Xlythe:
Has anyone reported / found a fix for storage space running out? As soon as that warning appeared, it refused to go away no matter how many files I delete. I can't download apps (or app updates) because of the low memory errors.

Thanks for the work on the ROM :) I've been getting 2days+ battery life and the hw overlays fix solved the only other bug I've seen.
[Galaxy Tab S Original Android Development] eousphoros:
Just kicked off a new build with a repo sync and your media_codecs.xml

Also for those interested I just synced my device repo with my working branch.
[Galaxy Tab S Original Android Development] Sporbillis:
Can we have the link? or is it still uploading ? :D Love your work
[Galaxy Tab S Original Android Development] eousphoros:
https://github.com/eousphoros/android_device_samsung_klimtwifi.git

It was in the first post but there it is again.
[Galaxy Tab S Original Android Development] Sporbillis:
Oh, i went to the first post but i saw ( release 8 ) and i thought it was still the V1 not the V2 . Sorry :D

edit: Just realized this was not the new rom but a new build. i ll be waiting for the rom
[Galaxy Tab S Original Android Development] eousphoros:
Ah the binary bits haven't been released yet. I am doing one final sync and fresh build before I release. Should be out in about 6 hours. (Building inside of a virtual machine on a slow machine.)

One thing that people are probably not going to like about s2r1 is I will not be supporting dirty flashes. I did a factory reset and so should you. (ideally even format your system/data/cache partition, get rid of that cruft.) Though as long as we are in series 2 I will make sure to support dirty flashes between series 2 releases.

EDIT: Damn still no love on netflix. Back to the drawing board.

EDIT2: Synced kernel code with cm-11.0 branch (Since it will work with cm-11 or cm-12 and hopefully we will get new kernel code when samsung releases lollipop officially)
[Galaxy Tab S Original Android Development] Sporbillis:
Appreciate the hard work u put into this!
[Galaxy Tab S Original Android Development] :
I've seen [MENTION=3857343]crpalmer[/MENTION] has taken some widevine drm blobs from manta for his picassowifi cm-12.0 builds. Perhaps that helps. Propably you know already: you can get binary blobs for cm nightly supported devices (for example for manta) from github.com/TheMuppets...

Good luck! May the source be with you... you are one of my developer-jedis... ;)
[Galaxy Tab S Original Android Development] eousphoros:
This is what I did for my series 1 releases, looks like I will need to do the same thing for series 2. Hopefully it doesn't reintroduce the flashing video since I never nailed the specfic cause and instead took a shotgun to it. One way to find out. :)

You are a Jedi as well, thankyou for all the help and time saved. :)
[Galaxy Tab S Original Android Development] Sporbillis:
Since i am a noob in the xda world i have a noobish question. When (if) samsung releases lollipop for our tablet will the build/rom of cm12 for our tablet be easier? Thanks
[Galaxy Tab S Original Android Development] danny19901:
It will help development but probably wont make it any easier but it will help as in drivers etc...
[Galaxy Tab S Original Android Development] eousphoros:
Damnit

I/ ( 5014): PLATFORM VERSION : JB-MR-2

I/OpenGLRenderer( 5014): Initialized EGL, version 1.4

D/OpenGLRenderer( 5014): Enabling debug mode 0

D/WVCdm ( 2288): Instantiating CDM.

I/WVCdm ( 2288): Level3 Library Nov 20 2013 18:09:31

D/mali_winsys( 5014): new_window_surface returns 0x3000

E/wv_dash ( 2288): OEMCrypto_Initialize(): Already initialized state(CE_ST_INITIALIZED)

D/WVCdm ( 2288): OEMCrypto_Initialize Level 1 success. I will use level 1.

E/WVCdm ( 2288): App requested unknown byte array property securityLevel

E/MediaDrm-JNI( 5014): Illegal state exception: Failed to get property: Unsupported scheme or data format (-2006)

I am still missing something. I may just end up doing a s2r1 with broken netflix. Unless this rings a bell [MENTION=4405529]nvertigo67[/MENTION]
[Galaxy Tab S Original Android Development] :
Sorry, not really. But amwild guess: if I temember right we have in cm-11.0 blobs at least one libWVstream_something (which relates to WideVine - I guess). Perhaps that one has to be replaced by a manta blob, too. My guess: mixup between different versions of parts of widevine... :confused:

BTW: for rexaing I have ordered a opo end of last year: no exynos and official support from cm and super nive kernel from anarkia. Only thing I had to do was changing ntp server for gps and enable call recording... not nearly as challenging then developing for klimt and chagall, but if one needs a success expirience after some nights of struggling... ;) (I love both: the challanging as well as the easy way.)
[Galaxy Tab S Original Android Development] eousphoros:
Here are the files I grabbed from manta.

+vendor/lib/libdrmdecrypt.so

+vendor/lib/liboemcrypto.so

+vendor/lib/libwvdrm_L1.so

+vendor/lib/libWVphoneAPI.so

+vendor/lib/libWVStreamControlAPI_L1.so

+vendor/lib/drm/libdrmwvmplugin.so

+vendor/lib/mediadrm/libdrmclearkeyplugin.so

Next up I am going to just revert my entire vendor directory (minus the bcm wifi drivers) and try again.

I am scheduled to buy both a new tablet and phone in march. I will be looking for one easy, one challenging. Hopefully both of them will be 64-bit as I am really interested in doing some 64-bit android.

Well it was definitely a blob issue. Went back to using the picassowifi blobs (minus the sensors/wifi/gps stuff which is from k2 release) and netflix loaded. I don't have an active account but usually if it gets this far it will end up working. Someone who pays for netflix will have to let me know.

MTP is still grumpy and camera is broken though that is close enough for me to not feel uncomfortable doing a release 1. So thats uploading now.

Here is series 2 release 1. If you like a stable build with everything working this is not for you. If you like bleeding edge and don't mind things like mtp not working and doing a clean install (factory reset) have fun. :)

https://blck.io/cm-12-20150112-UNOFFICIAL-klimtwifi.zip
[Galaxy Tab S Original Android Development] interfreak:
Thanks mate!!

Will give this a whirl when I get home. :D
[Galaxy Tab S Original Android Development] open1your1eyes0:
So against everything you mentioned (many times) that a factory reset would be required I still refused :p (after all what did I have to lose, if it didn't work could always reset later).

I flashed this new series 2 build after coming from the last series 1 build (12-22-2014), wiping cache/dalvik-cache/system first (but left data and storage alone), then flashed the ROM, Gapps, and SuperSU zip in order.

Here are things I noticed:

Device booted fine with zero crashes

All my data remained intact as before

Actually seems to be faster now too (although could be a fluke just to wiping cache)

All locally stored videos playing perfect at stock this time (in VLC) without having to mess with hwoverlays and such

Netflix/Youtube/Hulu all playing perfectly fine now without a hitch!

Camera is indeed crashing and not working (personally don't care too much, it's a tablet after all :p)

MTP is indeed not working; neither is PTP nor USB Storage mode (shows removable disk in Windows but asks to insert one)

This is all I've noticed so far from playing about 10-15 mins with it. Let me know if you guys want me to test anything else. Otherwise looking like a very promising first build. :highfive:
[Galaxy Tab S Original Android Development] :
[MENTION=3313404]open1your1eyes0[/MENTION]: Could you please try google camera from play store, and provide a logcat from the crash? Thanx.

---------- Post added at 07:54 AM ---------- Previous post was at 07:45 AM ----------

[MENTION=2346758]eousphoros[/MENTION]: Which kernel repo do you use?
[Galaxy Tab S Original Android Development] open1your1eyes0:
Kindly see attached. I started logcat from app drawer then pressed Google Camera and waited for the crash the closed it and stopped it there.
[Galaxy Tab S Original Android Development] :
Wow. The fastest logcatter on the block... Thanx... (also for putting what I want to see at the beginning!)

[MENTION=2346758]eousphoros[/MENTION]:

E/AndroidRuntime(19341): java.lang.RuntimeException: startPreview failed

...looks familar to me. You can try two things

1. opt out threaded start in overlay, or - if this doesn't help -

2. take a look at my camera2 repo: I reverted 4 commits in order to get camera2 working.

What makes me wonder: google camera was working while Camera2 was crashing (on cm-11.0 of course).

EDIT: In your vendor repo: have you copied

vendor/samsung/chagallwifi/proprietary/lib/hw/camera.universal5420.so:system/lib/hw/camera.vendor.universal5420.so

to have camera.universal5420.so from the camerawrapper not overwrite the vendor blob?
[Galaxy Tab S Original Android Development] eousphoros:
https://github.com/eousphoros/android_kernel_samsung_exynos5420/tree/cm-11.0

And yeah I am using camera.vendor, did that in my initial port as well. Haven't spent any time looking at the camera stuff yet.
[Galaxy Tab S Original Android Development] lionheartk:
I'm on a T800 but I got both those bugs on all lollipop builds I tried so far:

When I try and use the "move App to SD Card" feature under the app info screen, it says it can't move the app because the SD is full, which isn't true.

Here's the Log of when I try to move the Kindle app to the SD:

http://pastebin.com/xaANaFrP

Also, a log of the Google Camera app from market crashing with the error "Cannot connect to camera" after taking a picture:

http://pastebin.com/zvPqqjyC

Hope this helps somehow!
[Galaxy Tab S Original Android Development] eousphoros:
You arer going to need to talk to whoever is doing your t800 build. Sorry.
[Galaxy Tab S Original Android Development] lionheartk:
Um don't the T700 builds have the same camera bug also?
[Galaxy Tab S Original Android Development] eousphoros:
Let me put this another way, I am not going to set the precedent where I end up supporting anything other then the t700 in this thread. Cheers.
[Galaxy Tab S Original Android Development] lionheartk:
Geez, I just pasted the log because you asked for logs from the camera bug happening. Never asked you to do anything for the T800.

I'm fairly sure that the problem will be the same on both roms. Just tried to help.

Thanks for the contribution with code to fix those bugs tho.
[Galaxy Tab S Original Android Development] :
All the artists from moma (klimt, chagall, picasso...) are quite similar - but not equal. Even klimt and chagall have some very small but very essential differences. So we all try to help each other. But asking in the t700 thread for a bug from two other roms (even if the bug is present over several devices) does not make a developers life easier, nor does it help to fix the bug - in one rom or an other...

EDIT: quotednwrong post - but I think you all get the point.
[Galaxy Tab S Original Android Development] lionheartk:
Like I said, I posted the log because I though it would help since the bug is the same, and like you said, helping each other is what we should do. I guess I'm sorry then?
[Galaxy Tab S Original Android Development] eousphoros:
We always love logs but these projects and communities are chaotic at the best of times. Nvertigo67 described the situation far better then I ever could.

No need to apologize, I'm just trying to keep this thread focused and not introduce possible confusion.
[Galaxy Tab S Original Android Development] asferreira:
Hi,

I flashed this new version on my T700, and things have worked (and not worked too) as described earlier.

I also noticed a bug that I had experienced before using S1R8. While using Kodi/XBMC player, the screen does not respond to any touch. The same problem occurs in the game Need for Speed, what make me believe that the bug is related to full screen apps.

Otherwise, anything else looks fine and I looking forward for the next release!

Thanks for the good work!
[Galaxy Tab S Original Android Development] dancress:
just so you can prioritize and get right on the most burning, painful bug: BOINC won't work. just hangs at the logo screen. you might have to put the baby in an orphanage but hey, this takes priority ;)
[Galaxy Tab S Original Android Development] eousphoros:
[MENTION=4405529]nvertigo67[/MENTION] So tonight I spent a couple minutes tweaking/compiling your kernel for klimt (Nothing major just some defconfig stuff). Boots and everything looks good. MTP is even working with your kernel so thats exciting. A couple more things to test but would you be ok with me releasing it as part of s2r2? (Used the cm-11.0-sh branch)
[Galaxy Tab S Original Android Development] :
We have to ask [MENTION=3511708]UpInTheAir[/MENTION] as well - send both of you pm.

---------- Post added at 09:56 AM ---------- Previous post was at 09:48 AM ----------

I am not smart enough to edit installer-script inline rom building, I have a script that unpacks updaterscript, patches it and put it back in zip. Then resign the zip (git repackrom on github). Do you know how to costumize installer-script in a smarter way?
[Galaxy Tab S Original Android Development] :
We know of the problem. We even know the reason. We even know the path to go to solve it - but it's out of my scope to go this path. I have asked several times for help in [MENTION=4193974]Barracuda77777[/MENTION]s cm11 thread - you guess it: so far no one has offered help. So I started this thread in the help forum.
[Galaxy Tab S Original Android Development] eousphoros:
https://blck.io/cm-12-20150116-UNOFFICIAL-klimtwifi.zip

s2r2

Using a new kernel with most of the work from [MENTION=3511708]UpInTheAir[/MENTION] and [MENTION=4405529]nvertigo67[/MENTION] with a few small tweaks by me.

MTP is now working and its a current sync of the cm12 tree.
[Galaxy Tab S Original Android Development] open1your1eyes0:
Downloading and testing now. Will report back if camera or MTP fixed or any regressions from my previous notes (or new bugs).

---------- Post added at 11:13 PM ---------- Previous post was at 10:50 PM ----------

Looks like everything working in previous build is still working (all video players and such).

Camera still not working.

MTP is now fixed though! :laugh:
[Galaxy Tab S Original Android Development] eousphoros:
Thankyou for the qa. I love the validation I actually fixed something. Make sure to check out the kernel stuff if you get a chance. A lot of under the hood changes. Settings -> performance. Can tweak min max CPU, io schedulers, and more. Eg go for snappy performance, or longer battery life. There is also a new sysfs interface for disabling the capacitive buttons if that's your thing
[Galaxy Tab S Original Android Development] lionheartk:
I'm trying to learn how to build your ROM for the T800, I think it will take some time since I never did this LOL

Is it ok if I eventually do?
[Galaxy Tab S Original Android Development] jewnersey:
great work!! could i get in on this by any chance? either by building the kernel from your sources, or obtaining a flashable that folks can use with the bliss rom?
[Galaxy Tab S Original Android Development] open1your1eyes0:
That's great, I didn't get a chance to look into Settings. Will be sure to. Thanks for all your hard work! :good:
[Galaxy Tab S Original Android Development] casasroldan:
Hi,

Testing version s2r2 with no problems but I can´t find option to disable hardware keys when I enable on-screen nav bar. Is there a way to do it without modifying keyboard files?

thanks in advance
[Galaxy Tab S Original Android Development] eousphoros:
http://xdaforums.com/galaxy-tab-s/help/kernel-development-t800-t700-t3002774

The kernel code went in with s2r2, but I didnt update the java code that interacts with it. I will make sure it gets into release 3 since it sounds like at least one person wants it.
[Galaxy Tab S Original Android Development] open1your1eyes0:
I wouldn't mind that as well. Might as well make it official on-screen keys only like a Nexus. ;)