yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] hurray:
A nice find! The app looks good. I only have to test if the "apply on boot" is working.

Edit: the settings are applied perfectly after a reboot. :)

---------- Post added at 09:20 PM ---------- Previous post was at 09:13 PM ----------

You are right: ondemand scales down all cores to 300 MHz and interactive the first two cores to 100 MHz and the third and forth core to 200 MHz (that are the readings from "kernel aduitor" of course).
[Galaxy Tab S Original Android Development] :
I was not tough enoigh to test "set on boot"... ;)

what you describe is one of the "oscilating" things, when setting min to 200 MHz. That's why I choose to set min to 400 MHz, then you have much less of this symptoms. I would like to get intelliplug with our kernel (I hope more cores get earlier unpluged), but I can't get it clenly patches in the source so far.
[Galaxy Tab S Original Android Development] UpInTheAir:
Just woke up.... Haven't looked at your source, but are you using the Samsung stock on-demand and not from other sources?
[Galaxy Tab S Original Android Development] :
...just woke up myself... TZ mystery...

Your source:

ingo@adler /usr/local/src/android/kernel/samsung/chagallwifi $ (cd ../sh; git lg1 -- drivers/cpufreq/cpufreq_ondemand.c )
* 2fb04eb - (vor 4 Monaten) CPUFREQ: ondemand: use power efficient wq! [halaszk] UpInTheAir
| * 8d0ae78 - (vor 4 Monaten) CPUFREQ: ondemand: use power efficient wq! [halaszk] UpInTheAir
|/
* 0647f71 - (vor 5 Monaten) T700OPU1ANG2 source UpInTheAir

Our source:

ingo@adler /usr/local/src/android/kernel/samsung/chagallwifi $ git lg1 -- drivers/cpufreq/cpufreq_ondemand.c
* 9e948e8 - (vor 4 Monaten) CPUFREQ: ondemand: use power efficient wq! [halaszk] UpInTheAir
* b682b99 - (vor 6 Wochen) importet sammy NJ2 Nvertigo

Or the simple way (...before first coffee it takes a while to find the easy way...):

ingo@adler /usr/local/src/android/kernel/samsung/chagallwifi $ diff -u drivers/cpufreq/cpufreq_ondemand.c ../sh/drivers/cpufreq/cpufreq_ondemand.c
ingo@adler /usr/local/src/android/kernel/samsung/chagallwifi $

So the difference must be elsewhere... I'm lost (in need of a cup of coffee... ;) )

---------- Post added at 08:58 AM ---------- Previous post was at 08:26 AM ----------

No color adjustment with ui. Though you can edit mdnie by directly manipulating /sys/class/mdnie/mdnie/* in 01systemtuning.

APT-X: I don't think so.
[MENTION=4193974]Barracuda77777[/MENTION]: you have fallen in love ro mixer_path and tinyuml when fixing mic, have you seen anything about APT-X in bluetooth sound routing?
[Galaxy Tab S Original Android Development] Barracuda77777:
I did try, could not get it going. gave up.
[Galaxy Tab S Original Android Development] :
Perfectly ok with me: I don't need it... :lol:

I was so happy [MENTION=4193974]Barracuda77777[/MENTION] fighted those two files! I surely won't mess with them. So answer to APT-X is: no - not in near future. Sorry.

Does anybody know if cm11 of klimt or picasso has implementrd APT-X?
[Galaxy Tab S Original Android Development] :
ondemand has not known about 200 (aka 100) MHz min_cpu_freq This commit makes him knowing... ;) (BTW: it's tha last commit in my-work branch - if stable it goeas to cm-11.0-sh). By now it seems it scales down to 200 (aka 100) MHz without oscolating issues:

From 130f0e5a8a064963230e31ee08e9775a588ef23c Mon Sep 17 00:00:00 2001
From: Nvertigo <nvertigo67@gmail.com>
Date: Sat, 3 Jan 2015 22:57:20 +0100
Subject: [PATCH] omdemand: lower down_step_level to 100 (aka 200) MHz.

---
drivers/cpufreq/cpufreq_ondemand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/cpufreq/cpufreq_ondemand.c b/drivers/cpufreq/cpufreq_ondemand.c
index bc42ddb..d3ad5e4 100644
--- a/drivers/cpufreq/cpufreq_ondemand.c
+++ b/drivers/cpufreq/cpufreq_ondemand.c
@@ -64,7 +64,7 @@
#define MICRO_FREQUENCY_UP_THRESHOLD_L (85)
#define MICRO_FREQUENCY_UP_STEP_LEVEL_B (1200000)
#define MICRO_FREQUENCY_UP_STEP_LEVEL_L L_MAX_FREQ
-#define MICRO_FREQUENCY_DOWN_STEP_LEVEL (250000)
+#define MICRO_FREQUENCY_DOWN_STEP_LEVEL (100000)
#define MICRO_FREQUENCY_DOWN_DIFFER_L (20)
#define MIN_FREQUENCY_UP_STEP_LEVEL (500000)
#define MAX_FREQUENCY_UP_STEP_LEVEL B_MAX_FREQ
--
2.0.5

Thanx for the tip. Will test now. To be honest: on webbrowsing and writing here I see/feel now difference - but give me a day or so.

Kernel attched. If you want to scale down to 200 MHz you must set 100 MHz.
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks, never really looked at that or tuned the govs too much. Thing is with TW (anyway, on my SkyHigh TW ROM + kernel), I have no osc of freq when set to 200 MHz (100) and idles like a deisel engine. It just scales up and down smoothly as required. Dunno, just the diff between TW and CM I suppose................

Edit: will apply the patch to test, but doubt I'll "see" much though. Just busy with other things right now :)
[Galaxy Tab S Original Android Development] jodeltje:
I just want to thank you guys for this ROM.

I was hesitant to buy a tablet with Exynos and Touchwiz, but because it's my bedroom tablet/tv I was set on an AMOLED tablet since the release of that 8.9" one long ago.

All my fears of no decent software development were unnecessary, it only takes a few geniuses' like you guys to perfect/correct the work of Samsung.

Thank you! Thank you! Thank you!

Havent noticed any bug, glitch, or anything since Christmas build. Awesome :D
[Galaxy Tab S Original Android Development] Offica:
Kernel posted drains battery way more then the previous one.. sorry I don't have any logs
[Galaxy Tab S Original Android Development] :
Have you used interactive or ondemand? I'm still testing ondemand: with 200 (set to 100) MHz it's draining a little faster then with 400 (set to 200) MHz. I jave also observed that battery lasts longer on second or third loading cycle...

Thanx for feedback!
[Galaxy Tab S Original Android Development] FormeriPhoney:
Well.. It's all good. Lol

[quote name="DUHAsianSKILLZ" post=57971622]Knox is ok to disable. You already tripped knox so its pretty useless. It doesnt protect you against anything and drains battery. Updating the binary normally is fine as it updates root stuff[/QUOTE]

Hey fellas.. just wanted to chime in with a fun story.

I sent my Tab T-800 in for warrenty service (power button not working correctly). Being that it was just hardware I said F-it and just sent it in running Cyanogenmod just for kicks.

Well.. tripping Knox isnt the end all be all after ....:D:D

Also.. From the time I dropped it off at ups until I got it back.. 5 days. Amazing

C

Now to Root and put TWRP back on since they flashed it back to stock.<br/>
[Galaxy Tab S Original Android Development] reubenskelly1992:
Would touchwiz launcher work ok with cm11 if there were a file availble."?
[Galaxy Tab S Original Android Development] FormeriPhoney:
Hey guys. Where are the latest builds located at? Not in the OP?
[Galaxy Tab S Original Android Development] hurray:
Here is the latest build:

http://xdaforums.com/showthread.php?p=57896638

Have fun with your replacement TabS. :)
[Galaxy Tab S Original Android Development] Offica:
Yeah on-demand and power saving, lastest build with the new Kernel was losing 1% over night, this kernel just browsing drops fast, no other apps running then chrome and what's needed. Glad to see your working on the kernel :) my pc got seized breaking bail, when I get it back on the 23rd I'll take a look at the sources and contribute as much as I can :)
[Galaxy Tab S Original Android Development] :
Glad you received your repair without any problems.

[MENTION=535343]all[/MENTION]:

As stated in OP (btw: in bold letters...): Latest builds and chanhelogs for nvertigombuilds are in posting #5.

---------- Post added at 09:05 AM ---------- Previous post was at 09:02 AM ----------

Don't know for sure, but I wouls guess that teir are to many diffrences in framworks from aosp to cm to sammy. I would suggest: backup your system and try it.

---------- Post added at 09:17 AM ---------- Previous post was at 09:05 AM ----------

You can always change governor, but I would recommend to try it for at least three complete loading/use til 4% cycles. I was really surprised, when realising, after flashing kernel or rom it takes at least two of those cycles to bring up good battery performance...

At the moment (third cycle) ondemand gives me same onscreen time (about 10 h) then interactive.

Don't matter which gobernor you use: if lowering cpu_min_freq to 200 (setting 100)MHz results in poor battery performance.

With "power saving" you refer to performance profile, aren't you? I use balanced, and app-profiles is checked.
[Galaxy Tab S Original Android Development] reubenskelly1992:
I've been flash crazy lately. Can't decide whether to stick with a stock ROM (iron ROM) smoothest I've used that's stock or cm11. Just can't decide. Please help
[Galaxy Tab S Original Android Development] FormeriPhoney:
I've been using this rom day 1 since I've owned the tablet.

The dev is great and I've experienced almost zero bugs. Literally never ran stock.

If you want to try lollipop, Bliss rom has been solid for me for the past 24 hours.

What is this "Iron Rom" you speak of? Id like to try a stock based rom to retain all the features.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
http://xdaforums.com/showthread.php?t=2973107

I am running it as well along with the discreet blue theme (black touchwiz ui-ish) that i fixed up.
[Galaxy Tab S Original Android Development] reubenskelly1992:
http://xdaforums.com/showthread.php?t=2973107 beat me to it lol, i personally dont like the discreet blue theme but its def the quickest and most stable stock rom ive ran. Stocks great for multi tasking and i personally dont mind touchwiz at all (fully customised and debloated lol) but cm has some awesome features like theming too. Cant decide
[Galaxy Tab S Original Android Development] reubenskelly1992:
So back on to this ROM, I'm getting some lag here and there, can someone tell me what the best procceser setting and I/o scheduler settings etc?
[Galaxy Tab S Original Android Development] biogon:
Strangely, I upgraded from the 1106 build to the 0101 build and went from completely lag-free to having a little lag, although I did dirty flash.

Currently on 200mhz/conservative (which apparently is what it defaulted to, not interactive).

I'm planning on trying the interactive governor, and then, a clean flash if it gets too annoying and see if that helps.
[Galaxy Tab S Original Android Development] reubenskelly1992:
Interactive is better than conservative right?
[Galaxy Tab S Original Android Development] biogon:
If by "better" you mean faster, then, yes.

Conservative is (as I understand it) the most battery-saving governor, whereas interactive ramps up to max CPU immediately and only slowly trickles down over a kernel-set timer.
[Galaxy Tab S Original Android Development] barth2:
Could you share the theme? Thanks
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
http://xdaforums.com/showthread.php?p=57975549
[Galaxy Tab S Original Android Development] :
Build/rom default is interactive and always has been, as my recomedation always was interactive!

Check you settings. Don't mess with 01systemtuning as long as you don't know what you are doing. Deinstall all tweaking apps as long as you don't know what you are doing (also batterymsavers can mess system defaults). And of course: if you experience issues, do a clean flash.

conservative is known (on a lot of roms through many devices) is known to be laghy on interactive use.

---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------

That depends on usecase. For me consrvative is just a bit laggy, but don't save any battery compared to interactive. But thats for me.

---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------

That depends on usecase and your definition of "better".

---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------

IMPORTANT!!!

Before judging battery of rom/kernel/governor give your settings at least two recharge cycles! I don't know why, but it takes some time before you get good battery life...
[Galaxy Tab S Original Android Development] biogon:
nvertigo67,

Thank you for all your hard work on this! You've turned a middling-to-poor tablet into a fantastic one.

I don't know why mine was on conservative, but I'll change it back to Interactive once I get home. I've never played with system tuning or tweaking apps that change the processor (I did change the build.prop to make the DPI smaller and add the on-screen buttons.)

FYI, my dominant use case is reading comics, books, and the web... I don't play games on it (bought a couple but never really enjoyed them). Every so often I use it to control a DSLR or something like that.
[Galaxy Tab S Original Android Development] UpInTheAir:
Updated SkyHigh kernel

Hi Devs

Have just updated my T700/705 TW kernels with a few new commits. Not sure if you have them already, but might be of interest :)

https://github.com/UpInTheAir/Galaxy-Tab-S-Kernel/commits/SkyHigh

Cheers,

UITA
[Galaxy Tab S Original Android Development] biogon:
[MENTION=4405529]nvertigo67[/MENTION].

Yup, switching from Conservative to Interactive makes it a lot snappier, plus, I see little battery impact.

Thanks!
[Galaxy Tab S Original Android Development] :
I did a lot of testing the last two weeks. For my personal usecase (hacking through ssh on my devhost with black background, browsing the web and watching videos with mxplayer) I can summarize:

For ondemand the last kernel I published is most battery friendly. For interactive the kernel contained in last rom is most battery friendly. Both give me nearly 10 h screen on time (between 9:40 and 10:15 h); both give me on deepsleep (7 -8 h each night) 0 -1 % battery loss. So I think both are pretty good. Which is best for you depends on your usage. For me the solution with rom kernel and interactive feels a little bit faster without usimg more battery.

For the interested: rom kernel is branch cm-11.0-sh, last published kernel is my-work.
[Galaxy Tab S Original Android Development] :
an other cm11 build? And: XBMC issue

I'm thinking of putting a new (and propably last) cm11 build out. I wonder if this is wanted any longer. There would be no new featueres or fixes for xbmc or capacitive button switching, but only a repo ssnc against cm. Let me know.

For the both mentioned issues ('cause I'm quite sure they will remain in cm12 as well) I'm still looking for some help to fix them. 'Cause nobody reacted on my requests for help in this thread I started this thread in the help forum.

The last days I have started build cm12 for my manta to get a feel and understanding for the changes in L. I learned that the cm migration to L is in a very early stage. Even on manta (nexus device with early source support by googles aosp) there is no automatic backlight and no quiethours. So don't expect a cm12 build by me to early - but: you can expect development will continue on cm12 by me. At least our kernel will be able to build and boot cm12 (as proven by [MENTION=2346758]eousphoros[/MENTION] on his klimt build). So there is a path to go...

Again: please read the thread in the help forum. I want to sort that out - on cm11 as well as on cm12! Thanx.
[Galaxy Tab S Original Android Development] biogon:
[MENTION=4405529]nvertigo67[/MENTION],

I use your CM11 build daily and really love it. However, it is incredibly stable, has great battery life, and fits my use case so far, so I don't know if much more development on cm11 is necessary.

I wish I could help your development efforts, but I am a bureaucrat, not a programmer, so I can't help you at all. ;)

I will of course be happy to test CM12 in the future. If donation funds will be helpful, I think that is the only way I can contribute to the effort. ;)
[Galaxy Tab S Original Android Development] pingtiao:
[MENTION=4405529]nvertigo67[/MENTION], I also use this rom as my only driver, and have since it was first released. It is absolutely brilliant, and breathes life into this sophisticated machine. I'd happily donate to you - do you have a PayPal account?
[Galaxy Tab S Original Android Development] hurray:
I can only say: CM11 runs wonderful good and I enjoy my Tab S every day with this.

I wait with CM12 as a daily driver till (hopefully) xposed is running under Android 5.

For the development I can mostly only help with testing and give a detailed feedback.

I am very thankful for the work all developers are made to make this Rom (and of course the kernel enhancements) possible!

Btw: After testing three full battery loads with on-demand I am back to interactive as I don't see much battery savings and the interactive governor feels a little bit snappier for me.
[Galaxy Tab S Original Android Development] :
Thanx for your kind words. I'm happy to hear [MENTION=4193974]Barracuda77777[/MENTION]s and my cm11 port is still used as daily driver. By all the L-Hype I thought kitkat is consideed too old. But here we go:

OK. Maintain release with small changes in kernel (from memory: reverted bfq and powereffizient workque - 'cause this not only makes ondemamd more battery friendly, but also makes interactive a bit more battery draining - bfq has for disk io and battery efficiency nomadvantage over cfq, so I want to keep it simple - haven't tested the new changes from [MENTION=3511708]UpInTheAir[/MENTION], so I have left them out for now). Repo synces against cm yesterday.

There will be no further changelog and no announcment in #5 (changes too small to call it a real release.... ;) )

There will be at least one more update to cm11: [MENTION=2346758]eousphoros[/MENTION] will try to implement the sysfs interface for the capacitive buttons - but we are not in a hurry.

Rom zip and md5sum file can be found here:

http://charlesingo.mine.nu/ftp/nvertigo/

Happy flashing!

OT: [MENTION=2346758]eousphoros[/MENTION]: I would recommend to use kernel-branch cm-11.0-sh. Branch my-work is stable, too but only gives good battery life with ondemand - interactive somehow doesn't like the wq changes. But as always when it comes to performance and batterylife: your milage may vary...
[Galaxy Tab S Original Android Development] hurray:
The update to the newest version runs fine and till now everything runs smooth and well. :)
[Galaxy Tab S Original Android Development] Offica:
Any chance of battery fast charge in the kernel ;)
[Galaxy Tab S Original Android Development] biogon:
That would be sweet, but I thought specialized hardware was required?
[Galaxy Tab S Original Android Development] Offica:
Is there a way to decrypt the device? / stops from flashing roms I need to reflash after testing my new security app.. it messed up iptables so Wi-Fi stopped working. There's no option to decrypt the device under security?
[Galaxy Tab S Original Android Development] :
I'm not sure, 'causr I never played with encryption but once back in the cm-10.2 days on manta. And the only way to revert decryption was doing a factory reset (which makes sense from the secirity point of view). But as mentioned that was 10.2. So I give the question back to community:

Is there an other way than resetting the device to disable encryption in cm-11.0?
[Galaxy Tab S Original Android Development] Offica:
Seems you can't, but backup, wipe. Arghh I need to get me a test device haha
[Galaxy Tab S Original Android Development] Joker87:
Deleted
[Galaxy Tab S Original Android Development] cyaclone:
Sorry that I am late to the party for CM 11, but still want to try it. One big question that has cause issues on other ROMs is the External SD card. Will the latest Feb release allow apps to be sent to the extSD?
[Galaxy Tab S Original Android Development] :
As far as I know there is no cm11 build from Febtuary. Cm11 has no support for move to sdcard - so my builds does not have that feature, either.

[MENTION=535343]all[/MENTION]: when moving to cm12 I have droped my cm11 development. You know my philosophie: don't publish something, I've not testet myself before - so there will be no more cm11 builds from my side. Sorry. Thanx for your support, your help and your friendly and kind words. I'm happy you liked [MENTION=4193974]Barracuda77777[/MENTION] and my rom! Hope we read us all in the cm12 thread again. cm12 is still under heavy development by cm, but I manged to put together a stable rom with all basics working. It's usable as daily driver.

BTW: cm12 builds have move to sdcard fixed.
[Galaxy Tab S Original Android Development] cyaclone:
Thanks for the reply and will go directly to your latest cm12 build.
[Galaxy Tab S Original Android Development] Barracuda77777:
this is possibly the last CM11 for whoever is still on CM11 like myself:

1/03/2015

cm-11-20150301-UNOFFICIAL-chagallwifi.zip

cm-11-20150301-UNOFFICIAL-chagallwifi.zip.md5sum

Fixed Kodi/xbmc touch issues, and with many games that had no touch register issues.

all credit for the touch issue patch goes to [MENTION=5087332]Patrick L[/MENTION]ower

updated to latest CM11 sources
[Galaxy Tab S Original Android Development] hurray:
Thank you very much!

I am still on CM11 as a daily driver so the new build is very helpful. :)
[Galaxy Tab S Original Android Development] :
Cm11 still has MUCH MORE features than cm12. If I hadn't started cm12 development and need to test what I'm doing, I would use cm11, too. Great idea to put a new build!
[Galaxy Tab S Original Android Development] Barracuda77777:
LOL, I had to drink 3 double shot coffees to patch and make the builds, no sleep at all, babies are hard work lol...

Build kept breaking due to some commits which I had to revert.

Good find BTW for the touch patch.

I have been checking on and off waiting for someone to crack it, I tried taking out the glove mode once thinking it was the culprit, was so close lol.

I have been following the progress on lollipop, great work. But I still prefer cm11 for now, way more polished with almost no issues at all.
[Galaxy Tab S Original Android Development] hurray:
Even with no or little sleep your build runs pretty well. :)

I made a dirty flash and everything runs fine till now.

I am able to install and use Kodi 14.2 beta. Netflix runs also good. So for now I would like to say: A stable and complete Rom. :)
[Galaxy Tab S Original Android Development] biogon:
Nice! Going to try the new build when I get home.

This is still my daily driver. It works beautifully.

I did change the theme to a different one but that caused it to reboot randomly so I switched back to the stock theme.
[Galaxy Tab S Original Android Development] jalchemyst:
Hi. The rom is awesome! Just one very minor question. Would you happen to know why the wallpaper stutters sometimes when unlocking or rotating? ie. screen goes black and then goes back to normal?
[Galaxy Tab S Original Android Development] AV1d:
Its because the image has to re orientate its self to the position you hold it. since stock android is not native to (all) Samsung device, it would take a lag or stutter to adjust its self right.
[Galaxy Tab S Original Android Development] trazfer:
My tab gets hot with this at middle top of the screen. While playing coc using multiuser with 3 accounts. Haha. But when i use stock it doesnt become hot?? Any suggestions?
[Galaxy Tab S Original Android Development] Barracuda77777:
Graphic drivers never performed as good as stock. So the cpu picks up a bit of the slack causing your tablet to heat. Usually the case with intensive 3d gaming.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Does vpn work on cm11? I know that it works fine on cm12. Thanks!