yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] FormeriPhoney:
Have you guys tried any of the cm12 themes over this build? That stark white LP is damaging to my eyes on this amoled screen. Dark or nothing for me for more reasons than battery life.
[Galaxy Tab S Android Development] :
Sorry, guys, but: wrong thread. Thanx for keeping this one for cm12.
[Galaxy Tab S Android Development] :
In the next build we will have some kind of mdnie control. Just testing at the moment.
[Galaxy Tab S Android Development] kdkinc:
I've been using this one.

https://play.google.com/store/apps/details?id=com.nitinvaid.theme.neoncolorsl

It's working pretty good with this EXCELLENT rom.
[Galaxy Tab S Android Development] lionheartk:
Today I take a break then :p

It's carnaval!
[Galaxy Tab S Android Development] FormeriPhoney:
Thanks. I was jumping back and forth from iron rom and Bliss.

I was running Nvertigo cm11 build for months before that.

Gonna give this a run
[Galaxy Tab S Android Development] barth2:
[MENTION=4405529]nvertigo67[/MENTION] is it possible on user end to adjust GPU frequency and governor? I see some stuff in /sys/devices/platform/mali.0 but those files seem to be dynamic and/or not editable. Thanks
[Galaxy Tab S Android Development] :
I've only unlocked 533 MHz step and adjusted tresholds on mali. I have not messed with making everything settable. So: no.
[Galaxy Tab S Android Development] Retiredfinally:
I was running nvertigoo cm11 build previously and thought it was smooth but this is remarkable! Chromecast now is working after many tries with cm11 it finally works! Great work again, everything works!! Thanks for your hard work!
[Galaxy Tab S Android Development] lionheartk:
Today's build is ready!

All commits made by CM12 team and Nvertigo since last build are in.

cm-12-20150217-UNOFFICIAL-lionheartk-chagallwifi.zip 237.5 MB

cm-12-20150217-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 144 B

Dirty flashed here and working!

If you have any kind of problem, please read the first post entirely to check if you didn't miss any step, then clean flash and try again before posting a bug report!

Next: the Sex build! :D
[Galaxy Tab S Android Development] FormeriPhoney:
I'm going to be flashing this build later tonight but had 2 questions.

Are you building a totally different build than Nvertigo's build? What's the difference? Just a more frequent build?

I've read about this "sex build" a few pages back. What's this all about? Lol
[Galaxy Tab S Android Development] reubenskelly1992:
Same build just with any new cm and nvertigo commits:)
[Galaxy Tab S Android Development] FormeriPhoney:
Been trying to download Lion build for past hour.. Server is so slow just decided to download nvertigo build.. 1 minute flat.
[Galaxy Tab S Android Development] lionheartk:
My build is exactly what Nvertigo would post. I just post more frequently to help, and he uploads the major milestone ones.

I don't know any other free faster place to upload them, any suggestions? Mega is the best one I know :(
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
If you would like, I can download your builds and mirror them to mediafire. Just gimme some time :)
[Galaxy Tab S Android Development] lionheartk:
Mirrors would rock! Thanks!
[Galaxy Tab S Android Development] reubenskelly1992:
Google drive is good. I just downloaded fine . only took 10 mins
[Galaxy Tab S Android Development] maxal:
Hi, Yes I know there is a work around for the Sdcard read issue I was just confirming it. The problem I have with Super Su is when I open it I get the message The SU binary needs updated Continue? so I click on continue which gives you the option to update normal or twrp/cwm so I click normal as I always do.

I then get a message after trying to update which says installation failed please reboot and try again which I tried but it fails again.
[Galaxy Tab S Android Development] :
PLEASE!!! Don't write me pms saying "can you make a new build - there is just a new XXX commit in cm"! I won't react on that. If I would I could make each day 5 or six builds. (received in the last 5 hours 7(!) of these requests via pm).

What I will do:

Work on the issues (priority: gps, init.d, netflix). When I make a step forward I post a new build (perhaps once or twice a week). Before releasing a new build I wil - of course - repo sync. Promised.

Keep in mind: I'm a single developer. Help in a way that someone provides a ready to use patch or commit is rare to null (I spended in cm11 and now cm12 tohether about 400 h of work - I do not complain, I just ask you to remember I'm a noob-spare-time-home-builder, and therefor I'm limited in capacity, ability and time). I'm connected to the net via 3g - that means: every repo-sync and build upload does reduce my data plan and each upload takes 30 to 50 minutes - if completed on the first try.

Please understand me - Rom (*) was not build over night.

(*) Capital "R"; it is the Capital of Italy, not that included in *zip. Though the idea matches to both of them... ;)

For protocol: I ****ing hate the look of L. The guy who selected i.e. the colors for clock should go for professional psychatric help!

So - of course - I will try to provide the few themers here with updates to the theme engine as soon as possible for me. Pease make things darker again (it better matches the color of my soul... ;) )
[Galaxy Tab S Android Development] :
Go to [MENTION=631273]Chainfire[/MENTION]s SuperSU thread and get the flashable version. Or try the flash method from SuperSU's gui. Have you enabled root in development settings?
[Galaxy Tab S Android Development] maxal:
Hi, yes I have enabled root in development settings. I will download SuperSU and try flashing it in recovery now.

---------- Post added at 01:14 PM ---------- Previous post was at 01:00 PM ----------

Hi, Yes I know there is a work around for the Sdcard read issue I was just confirming it. The problem I have with Super Su is when I open it I get the message The SU binary needs updated Continue? so I click on continue which gives you the option to update normal or twrp/cwm so I click normal as I always do.

I then get a message after trying to update which says installation failed please reboot and try again which I tried but it fails again.

---------- Post added at 01:55 PM ---------- Previous post was at 01:14 PM ----------

Hi, SuperSU working ok now thanks for your help.:good:
[Galaxy Tab S Android Development] bobbarker2:
Man, you just got cm12 running on the 800 and people are already bugging you for features and specific commits? Come on guys, atleast let the dev get the ROM stable before requesting crap..

Thank you for your work, I'll flash this tonight.
[Galaxy Tab S Android Development] reubenskelly1992:
Pretty funny really
[Galaxy Tab S Android Development] sgarrand:
We have Lollipop/CM12 already. It's just a matter of getting the most up to date, feature rich ROM. (http://xdaforums.com/galaxy-tab-s/development/rom-blisspop-team-bliss-t2987234 for reference)
[Galaxy Tab S Android Development] Bushcrafter:
+1
[Galaxy Tab S Android Development] lionheartk:
I'm trying to learn how to compile from nvertigo sources, when I get it working I can try and post them here aswell if it helps? It won't be synched with nvertigo code since he will update his GIT only before he releases his own, but should have the latest CM12 commits?
[Galaxy Tab S Android Development] lionheartk:
All compiled, flashed and working! Now struggling to make the wifi patch work!
[Galaxy Tab S Android Development] :
I would prefer not having to much builds. I can't support daily builds with some builds I don't have done my self... It's a matter of keeping the overview.

Please try to understand my last posting: this is a one man show. By postings like yours I feel under preasure - even if you don't intent to set my under preasure.

Of course I would be more than happy if you provide commits or patches. REALLY!!!!!

Of course you can use my work making and posting your own builds (it's all gpl2 or apache2). But please do it in your own thread - I want to have the overview over the published builds. And belive me, mate, more and faster builds does not help to track down issues.

If you decide to make you own builds, I would like you to clone, cherry-pick, format-patch, merge or rebase with git, so that the authorship of the work isn't changed. I hate people just clone copy to other dir, commiting there and push that to a git server claiming the changes under their authorship. Thats bad manner.

BTW: do you know selinunx/sepolicy? gps seems to be a selinux problem (my trys are in branch 12-work); and my guts grumbling init.d is so, too... I'm not very firm in selinux... :(
[Galaxy Tab S Android Development] :
If you are looking for the most features you are better of with bliss. I just want to have a plain working cm. No special features. No point of discussion.

If up to date for you means something like nightlys, I must disapoint you: till the three main issues are ironed out I plan one to two builds per week (on brekthroughs perhaps I'll make an exception).

I will not make a feature- or commit-race of this.

Some of the people reading here know my development is slow but I try to publish solid work and friendly support. Today I start to feel a pressure of "make this, implement that, do next build, when is xxxnworking" and the pressure of explaining my self. Thats no fun. And the joy of doing this is the only motivation I have. Reread tha last sentence...
[Galaxy Tab S Android Development] :
Wifi patch? Are you speaking of the repackrom script? It only modifys updater-script to make some symlinks like in sammyfactory rom. If you have the same files with different names/locations use symbolic- or hardlinks. If you keep same files multiple times you are doing something wrong... ;)

I just havn't found out how to customize updater-script while brunching. But repackrom does the job and is surely easy to understand and to use...
[Galaxy Tab S Android Development] lionheartk:
Sorry nvertigo! I was just offering to send builds in between yours in case you needed it, but I completely understand! I'll keep them for my personal use only, and If I happen to find and fix a bug I'll surely submit the patch!

I don't know selinunx/sepolicy but I'll look into it, having a great time learning!

On the repackrom front, yep the one on your git! When I run it, it gives me an error saying that Hunk 1 failed at 138. I'm looking at the patch file trying to understand why that is happening...
[Galaxy Tab S Android Development] sgarrand:
I understand everything you're saying. You do what you're willing to do, when you're willing to do it. No pressure intended.

I am just a user. I was simply stating that users want up to date ROMs with features that work (what else should they want?). That's all. If another ROM works better or is more up to date, people are free to switch. We are at the mercy of the developers if we want to use CM12. If it weren't for you and others, we'd have nothing. Thank you for what you do. When your ROM is ready and can be used as a daily driver, I'll be flashing it. Take your time.
[Galaxy Tab S Android Development] tiesum:
I'm a super noob and therefore cannot help you build this Rom. Can I help you with your reduced data plan or just buy you a beer? Maybe the first new thing you should add is a Donate button. Right guys?
[Galaxy Tab S Android Development] reubenskelly1992:
Agreed
[Galaxy Tab S Android Development] lionheartk:
okay, from what I've tried so far:

Camera works perfectly!

SD card needs to be mounted following the instructions on first post, then it works.

EDIT: Upon rebooting after deleting the GPS folder, it stopped working. Says "modprobe: can't change directory to '/lib/modules': No such file or directory"

Still cant move apps to SD, same error (card is full). Will attach a logcat here asap.
[Galaxy Tab S Android Development] :
The modprobe issue is known: this happens if you install an app that installs an incompatible version of busybox. The posting about that problem is linked in first post.

So: gettinig init.d to run is my job, finding what messes with systems own busybox is yours... ;)

After getting init.d and gps up, I will look in moving to sdcard.
[Galaxy Tab S Android Development] :
I'm not asking for donations.

Perhaps I overreacted a bit, cause I'm really pissed at the new sepolicy stuff - not at you!

Know we know what to expect.

BTW: take a close look on the left side of my postings below my name... has been there since quite some time... ;)
[Galaxy Tab S Android Development] FormeriPhoney:
Its all good... I have both downloaded as well as the latest Supersu.

Is this Gapps thread ok to use? I plan on using the Mini gapps

http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900

Latest build still doesnt have the On-screen Nav keys? Think I'll use LMT pie in the meantime if not.

Am i missing anything else?

---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------

It took a while but its fine.. Md5 matched up and im ready to go as soon as i fully charge.

---------- Post added at 07:02 PM ---------- Previous post was at 06:03 PM ----------

Are all the cm12 themes compatible with this rom?

Im interested in this one in particular.

https://play.google.com/store/apps/details?id=com.bds.theme.darkholo.cm12
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Yep should be fixed. I bought it too and it works fine. Ill be using that theme too :)

And there was a delay on uploading.. Internet went out because the power went out for a second lol.
[Galaxy Tab S Android Development] FormeriPhoney:
That looks great man.

It's there an Theme engine app or its built into the rom settings?

---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------

I seem to be having an issue with Titanium backup. I tried to back up 1 app to test it and I get the message that says "backup failed, insufficient storage"

Any ideas?
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Its built into the settings. As for titanium backup, I have that problem too. It worked fine on the last build? It might be the apk or rom. But I believe it worked fine on the valentines day build.

Btw mirror added. Its under lion builds :) Ill be uploading to Gdrive as a request from users and since lionheart uses mega. Mirrors: http://xdaforums.com/showthread.php?p=58424120
[Galaxy Tab S Android Development] FormeriPhoney:
No biggie for now. It restored just fine.

Any way to turn off the vibration when pressing the hardware nav keys? I tried disabling it in "other sounds" but the vibration is still..... Vibrating
[Galaxy Tab S Android Development] :
No onscreen navbar as long as capacitive buttons kernel driver has no interface for disabling them. Read OP. (BTW: never has been in this rom.)

I recommend pa gapps pico. Read OP.

The theme engine in these builds are as current as in any other officialmsupported devices - if one theme is bugfreemwith our rom? You have to try.

Always do a nandroid!
[Galaxy Tab S Android Development] :
Settings is under heavy rework at the moment. You looked in the right place - it's broken/not implemented in cm12. Just wait (you temember: no M1, early stage...). Meanwhile you can remove "virtual" from /system/usr/keylayout/sec_touchkey.kl and reboot.
[Galaxy Tab S Android Development] :
Titanium and move to sdcard is broken again. Will look into it.
[Galaxy Tab S Android Development] :
My internet connection is limmited by volume and by upload speed due to a 3g data plan. So [MENTION=1409248]lionheartk[/MENTION] has jumped in. The plan has been that I publish once a week or so., when I have some new development or milestone like fixes. M builds will be with changelog in OP, [MENTION=1409248]lionheartk[/MENTION] throughs his builds in the threafs discussion.

Yesterday I want to push a build, but was not able to repo sync due to problems with my internet connection.

But here is the changelog:

power off charging fixed: changed from lpm to universal android charging.

new section in /system/etc/init.d/10systemtuning:

# set mDNIe colour mode
# 0 = Standard
# 1 = Dynamic
# 2 = Movie (note: this is the only non-saturated mode)
# 3 = Natural
# 4 = Auto (note: this is the rom standard)
# echo 2 >/sys/devices/platform/s5p-mipi-dsim.1/lcd/panel/mdnie/mode

Just uncomment the last line and set whatever mode you like and reboot or execute 10systemtuning as root. This was suggested by [MENTION=6179912]rklrkl[/MENTION]. Thanx for that.
[Galaxy Tab S Android Development] lionheartk:
Uh oh, maybe some CM12 new commit broke the fix?
[Galaxy Tab S Android Development] :
Yeah, the framworks/base commit that claims to fix move to sdcard breaks it for us... And the commit from picasso, which should work with that cm commit did not work and additionally breaks Titanium - but it's both fixed in 12-work. I have to do a few quick checks before pushing it to current-12.0.

EDIT: fixed and pished to current-12.0. (Additional patch in devices/samsung/chagallwifi/patches; see patches README)
[Galaxy Tab S Android Development] lionheartk:
AWESOME compiling howto!

Thanks for that!

I use a .repo/local_manifests/roomservice.xml file, like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_picassowifi" path="device/samsung/picassowifi" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_exynos5420" path="kernel/samsung/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi_exynos" path="hardware/samsung_slsi/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi_exynos5-insignal" path="hardware/samsung_slsi/exynos5-insignal" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi_exynos5420" path="hardware/samsung_slsi/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi_openmax" path="hardware/samsung_slsi/openmax" remote="github" />
<project name="nvertigo/android_device_samsung_chagallwifi" path="device/samsung/chagallwifi" remote="github" revision="current-12.0" />
<project name="nvertigo/android_kernel_samsung_chagallwifi" path="kernel/samsung/chagallwifi" remote="github" revision="current-12.0" />
<project name="nvertigo/android_vendor_samsung_chagallwifi" path="vendor/samsung/chagallwifi" remote="github" revision="current-12.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
</manifest>

Instead, but it was a patchy solution. I'll change it to yours and test :D

PS: you typed tepackrom.sh instead of repack.sh above!
[Galaxy Tab S Android Development] :
There is more then one way. I like to leave roomservice.xml alone, cause breakfast and brunch shell functions deal with this file, so I put my stuff in a seperate file. Also I like to have it as short as possible, therefor I defined own repos for everything I use. But that's personal taste, it works both ways.

To be honest: this one wasn't for you (you are more than able to build), but a try to help one of the blisspop users to get a start in varrying on [MENTION=2779578]jewnersey[/MENTION]s work.

I'll fix the typo right now. Thanx.
[Galaxy Tab S Android Development] lionheartk:
I know it wasn't! I was just happy to learn the right way, cause to make it work till now I had to crash along until I made it work LOL

It's good to see a nice, structured way to do it and learn! That just adds to what you already taught me, thanks!!!
[Galaxy Tab S Android Development] lionheartk:
oh just noticed, you fixed the typo but the file that needs to be called is repack.sh not repackrom.sh?
[Galaxy Tab S Android Development] :
No, you are right. Wrote completley from memory... And in my age thats no gurrantee for accuracy... ;) I'll fix it in the postings. Thanx.
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Is it me or is the camera a bit wonky/streached a bit on the default camera application. Its sorta pixelated for me. I switched to google camera and it works/looks fine. When you use the stock camera it looks weird but when you take it, its perfect. Here is the screenshots from google camera and the stock cm camera. Also a side by side of what it appears to look like(wonky pickture) and after the took the picture with cm camera(looks perfectly fine) I am runing Lionhearts 2015-02-17 build. No HDR and any other settings. Both are set to default but I changed the resolution to 6.0 Megapixel. Both are also the same distance and I have cleared data etc on both

First pic= stock cm camera

Second pic= google camera

Third= side by side of stock cm camera and before and after result
[Galaxy Tab S Android Development] :
I've done (wit 8mp) a screenshot from the camera window and a photo. Both look equally good. But I'm not sure, if I get your point.

EDIT: screen representation on back camera for 16:9 seems to be inaccurate. I don't know if it's camera2 (that would mean upstream) or camerawrapper (that would mean device tree). And to be honest: it's lowest possible priority to find out and fix it, as the result (the photograph) is accurate. But if you find an error in the logs, I will look into it.
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Odd. Ill guess Ill use google camera for now. Might be because I dirty flashed or something related.
[Galaxy Tab S Android Development] :
Look at my EDIT in last posting.
[Galaxy Tab S Android Development] Zootopia:
Amazing feedback! You guys rock.

Wish I had the free time to dedicate to building (work is a *****, you know? It seems chalenging and attractive enough. :)
[Galaxy Tab S Android Development] lionheartk:
Surprise extra build!

MEGA:

cm-12-20150218-UNOFFICIAL-lionheartk-chagallwifi.zip 237.5 MB

cm-12-20150218-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 142 B

MediaFire MIRROR:

cm-12-20150218-UNOFFICIAL-lionheartk-chagallwifi.zip

cm-12-20150218-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum

Seems MEGA is better, so I'll be sticking with it.

Deleted everything here and built all sources from scratch using nvertigo's posted instructions.

Should contain the fixes nvertigo commited to fix the SDcard bug plus any new CM12 commits since yesterday.

Enjoy!
[Galaxy Tab S Android Development] Srikar_NBK:
32 GB model?

Can this ROM be flashed on SM-T800 32 GB model? The thread title specifically mentions 16 GB only, so wanted to know. I'm trying to buy a new 32 GB tablet and being able to flash AOSP is kinda important for my tablet experience.

I did a search of the thread, but didn't find anything specific being asked for the 32GB model. Sorry if it was answered elsewhere
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Used the method you posted and for some reason it wouldnt paste in pastebin so I uploaded to my drive. https://docs.google.com/file/d/0B5DZenb7A53ceU1oR0lXekVtcEE/edit?usp=docslist_api
[Galaxy Tab S Android Development] :
Thank you very much! I've run out of thanx for today... (eight thanx isn't that much :( )

I would suggest, that everybody who flashed the yesterdays build, flashs as soon as possible this one.

BTW: the commit I reverted to get app2sd working again is subject of discussion in gerrit. [MENTION=3857343]crpalmer[/MENTION]s picasso- and mondrian-builds seem to dislike that commit, too.

BTW2: the ugly reprensentation in camera2 seems to be a result of our camerawrapper, 'cause I can't reproduce the mismatch with different ratios on manta. I will not try to fix it, 'cause the picture is ok. Sorry, but in my oppinion it's not worth the time...
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Mediafire doesnt work on mobile. The app doesn't seem to connect to it either because of the capta. Can you upload it to mega and ill mirror it to google drive so you wont lose space on your drive? :)
[Galaxy Tab S Android Development] :
And now? I wrote: if you find an error... That was inacurate, I meant: if you find an error regarding camera2 and aspect ratio...

I looked through the log you sent, and found nothing regarding camera2, sorry. But as stated: very low priority.