yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Let me know what you guys think!

Noteworthy features:

-CyanogenMod Theme Engine (CMTE)
-Kernel Aduitor App
-Rom Control
+ Wakelock blocker
+ Slim Recents
+ PA Pie
+ Lockscreen DT2S
+ Status Bar AOKP logo
+ Breathing missed calls
+ Status Bar icon control
+ Status Bar network traffic
+ Smart Pulldown
+ Hardware key settings
+ Power menu screenshots and screen record
+ Volume step adjustments
+ Gesture Anywhere
+ Toast Animations changer
+ App Circle Bar
And more!

I highly recommend setting your LCD density to 320 to get the most from this screen.

Bluetooth work around:

Okay, so I finally got a cheap Bluetooth speaker so I could better understand the Bluetooth problems, and I too received the call of death.

However, I realized what darazor has been trying to tell everyone all along, and now I want to expound on that to help others.

When using Bluetooth, if you pair with an audio device (speakers, car, headset, etc.) And you have not adjusted any settings, the default for each audio device is phone and media. This will cause the COD if you get a phone call while playing music or other media.

So, if you want to use Bluetooth devices to play music:

Go to settings, Bluetooth, and click on the gear (settings) icon next to your paired speakers, and choose media, and unchecked phone. (See picture.) Now, when playing music, my phone vibrates and the screen comes on to tell me I have a call. Then, I can answer it, and the music stops. All is well.

If you want to use your hands free headset, choose phone and unchecked media. (See picture for reference.) And it should work for calls.

I now understand what everyone was talking about, and will do my best to look into it. Thanks [MENTION=2571065]darazor[/MENTION] for pointing this out, hopefully this lengthy explanation makes it clearer.

Governors:

If you want to save battery life, I recommend that you use the Kernel Aduitor app, and set your Governor to SmartMax, and your I/O scheduler to Noop. This may affect performance slightly, but will save on some battery power.

If you want to increase performance, I recommend that you use the Kernel Aduitor app, and set your Governor to Lionheart, and your I/O scheduler to CFQ. This will boost performance slightly, but will have a negative impact on battery power.

The governor is currently set to Interactive, which is a good balance.

Fast Charge:

To use Fast Charge, you must enable it in the Kernel Adiutor app. If you want to set custom settings, you will need to get another app from the Play Store, such as Device Manager or other apps that allow you to control the fast charge settings. Note that some fast charge settings apps do not change the appropriate values to function. The lockscreen may still say "slow charge" as the rom itself does not natively support fast charge, even though the kernel does.

Thanks [MENTION=5296208]khaoticking[/MENTION] for sharing that this rom works on jflteaio!

Thanks [MENTION=6712740]alesu69[/MENTION] for sharing that this rom works on jfltexx (i9505)!

Thanks [MENTION=2571065]darazor[/MENTION] for testing and finding that Xposed modules work on this rom!
[T-Mobile Samsung Galaxy S 4] kazzxtrismus:
Standard bluetooth issues?

.

Thanks for the hard work!!
[T-Mobile Samsung Galaxy S 4] christoophat:
always cool to have more ROMs for our phones! Many thanks, and yes also wondering about BT stability.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks.

As for the Bluetooth, I do not have any devices to test with, so I test it by sending and receiving a file to and from someone else's phone, which works great. However, I would think the standard Marshmallow Bluetooth issues would apply here as well.

I took the base of the device tree from the SlimLP build, in which the Bluetooth was great, but I had to use vendor blobs from Marshmallow ROMs to make it work, so it will probably have the same Bluetooth issues as the other CM Marshmallow ROMs.

EDIT: The Bluetooth does work, but you need to adjust a setting. For working Bluetooth see post #3 "Bluetooth Workaround".
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
For what it is worth, here was the benchmark result:

Not bad, but not as good as the benchmark from the SlimLP ROM.
[T-Mobile Samsung Galaxy S 4] darazor:
I found your marks to be pretty accurate even with AdAway, Task Killer, lookout and nova launcher running I got just under 39900.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks, I am glad that the ROM is measuring up! ;)
[T-Mobile Samsung Galaxy S 4] darazor:
I can report that Bluetooth seems to work fine. Connected to my Garmin Nuvi and was able to make calls from same. While not a definitive test it is very promising.
[T-Mobile Samsung Galaxy S 4] cirrus97:
Great Rom

So far in a week of using this rom, it works pretty damn good. very stable only a couple of issues...

Contacts list disappears randomly.

Takes about 2 -3 minutes to reboot.

Waze app force closes.

The bluetooth works without problems.

Overall, I'm pretty happy with the results.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Cirrus97,

Thanks for the feedback. Yes, the reboots seem a bit slow to me as well. As for the contacts issue, I haven't seen it here, but for reference, which gapps did you use?

Also, does Waze app fc on startup, or randomly during use, or is there a specific action that causes it?

If you have the time, pulling a logcat for when these errors happen would be great! If not, that is okay, too.
[T-Mobile Samsung Galaxy S 4] darazor:
I have not encountered this either. Using open gapps nano date 20160604. Contacts version 6.0.1
[T-Mobile Samsung Galaxy S 4] ivoe:
Bluetooth issues slightly

(works great but may experience a Sim disconnected, Bluetooth share stops responding and some other issues that dont effect to much)

Bluetooth audio / call works tested both on speaker and car

Have not used default music app

Notice that audio effects makes the audio alot lower (bluetooth)

Battery life is great compared to last rom I was running just ate all my battery in a hour with screen off

Superuser enabled/disabled for quick settings (for those who use snapchat an ect)

------------

Just some ideas about status bar/notification center

Anyone want a challenge? Notification drawer quick settings (make it like Samsung quick settings which is a single row with scroll)

Wish they made different notification drawers would be a lot nicer then current. Or at least a way to replace parts. Or even a horizontal status bar/notifications.
[T-Mobile Samsung Galaxy S 4] djrddragon:
Hi

I'm new to relatively new xda. I have tried this custom rom on my s4 m919 and it works great. The only problem i have is that my battery dies really fast, Any suggestions or kernels that i can try?

Thanks
[T-Mobile Samsung Galaxy S 4] darazor:
I'm actually getting better battery life than on my lollipop rom. Some thoughts:. Gapps nano so that you only use what you need. I use advanced Task Killer Free (by ReChild) . Also use Disable Service, AdAway, and Net Guard No Root Fire wall. You can read more about each one and see if they help. There are olther settings in the rom that will help reduce battery drain as well. If You don't use an app uninstall it. Good Luck.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Better battery life options: kernel tweaks.

When I put this together, I figured most AOKP users would be more on the power user scale, so I set the kernel for Performance and IO scheduler for BFQ. Pretty standard for average to heavier loads. However, if you want better battery life, you can download this free app on the play store. No-frills CPU Control found here (there are other apps, but I can vouch for this one working):

https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU

With this, you can set your kernel governor and io scheduler to anything you want. From a battery only perspective, you can set it for:

Powersave

Noop

But that is a bit extreme. You will notice "stuttering" when doing any task. A good alternative is to set your system for:

Conservative

Noop

Which can give moderate gains while not sacrificing too much performance.

Conversely, if you want more speed, use this:

Performance

CFQ

Which will just eat through your battery, but will really give your phone some "pep in it's step".

Many will argue facts and fiction, but the general community accepted power saving to performance chart looks like this:

I/O scheduler: Noop > BFQ > CFQ

(Row is Read over write, so it is really smooth for video playback, but very slow on writing to disk, which makes it hard to judge power saving vs performance.)

Governor: Powersave > Conservative > Interactive > Ondemand > Performance

(Userspace governor lets the app tell the kernel what speed it requires, this is unusual for a phone, usually used on servers. Most apps do not know how to use this function. I like to include it though, as a power user may have a use for it.)

Hope that helps.
[T-Mobile Samsung Galaxy S 4] christoophat:
L-Speed from the Store is also a good tool for some simple tweaking
[T-Mobile Samsung Galaxy S 4] cirrus97:
Fixed

OK fixed the contacts & waze issue, cleared the cache & family, imported the contacts & reinstalled wake. Works great now! the battery life seems to be excellent and really good memory management. Like I mentioned the only issue is the long boot time. Keep up the great work. :)
[T-Mobile Samsung Galaxy S 4] darazor:
I've always been a bit leery of just this type of problem and have not gone the encryption route. I also felt and heard that it would have a impact on speed. So no, haven't and no plans to.

BTW new rom is super-stable from my perspective.
[T-Mobile Samsung Galaxy S 4] darazor:
Wow! You are truly a dedicated person. I am worn out even reading about this. This only guarantees that I will not encrypt. I don"t know if I would have been able to restore it to pre encryption if I did. But, thanks for the saga. I think I'll just go back to finding new fundamental particles of the Universe. It"s easier.
[T-Mobile Samsung Galaxy S 4] dtriguero:
No haven't tried the full encryption but try installing the package installer again or just pull the one from gapps

---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------

New release up and running great so far

It's probably the keys are missing was the apps installed prior to encryption or after maybe try wiping dalvik/cache and reset permissions of the apps
[T-Mobile Samsung Galaxy S 4] darazor:
As I said before, very stable.

But, I've noticed using Kernel Adiutor that no matter what I set the GPU governor to; it always stays on the default "ondemand" and, just as with the CPU frequecy that you changed in the previous build there are no options between 320MHz and 487MHz on the GPU. Perhaps I'm doing something incorrectly. I have set it to apply on boot.

One thought came to mind. Is it possible that without steps between 320MHz and 487MHz some governor setting are precluded? Just guessing, though I grasp the concept, I know nothing re the governor profile process. Also, there was a Play Store update to the app, if that makes any difference. Thanks.
[T-Mobile Samsung Galaxy S 4] dtriguero:
updated kernel auditor from play store changed alot no longer uses plugin for selinux toggle have to manually add it or import it

---------- Post added at 09:04 AM ---------- Previous post was at 08:57 AM ----------

Here's the file to import for the toggle switch if un able to setup

Here's the file to import for the toggle switch if un able to setup just extract and import it into kernel auditor for the selinux toggle may need to have pro to use the import feature

http://cloud.tapatalk.com/s/57a73f8fee141/selinux switch.json.zip

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

Sorry last post got a jumbled not to sure what happened

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

True there is nothing in between but I did try changing the governor and found after reboot it switched back to ondemand until it applied the setting after the boot delay and it then stayed maybe u have another app or init.d script running after competing with kernel auditor
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks, but I can change the CPU governor; the GPU governor is the only problem? Other changes work as expected.

I did notice that SELinux plugin was no longer there.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Ah. I see. There is more than meets the eye here.

The new kernel adiutor app still has the option for "custom controls" however, you either have to donate to get that function, or build the app from source yourself. I will continue supplying my old build, which does have these options for free. On one hand I prefer free software and sharing, but I also realize that he has done a lot of work on this app, and does deserve some donations.

As for the governor for the GPU, I will look into it some more. This weekend I am testing the new security patches for SlimLP. I did test this briefly, though, and it is not the ka app. See the attached screenshot. It appears that you can select performance or on demand only. I will investigate further.

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New Kernel is up!

The new Kernel is up in the kernel thread, which includes the 450 MHz GPU setting, as well as the overclocked 487 MHz setting. I am still working on the GPU governor choice issue, but I wanted to get this frequency out to you while I work on the other issue.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Okay, I got it figured out!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] darazor:
I know nothing of this language but does this mean that a file was missing for the simple governor and therefore could not be accessed? You create it and voila!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Not quite my friend. The terminal is just showing what the KA app does behind the scenes. Technically, we don't need the kernel adiutor app, it just is a fancy, sleek, and easy way to make changes. Instead you could just hand type it in the terminal.

What this is showing, however, is that I was able to compile a kernel that does allow both the over clocked GPU and the simple governor. This is the kernel on my phone right now. Tomorrow I will package it up and post it for you all to download.

Essentially, the GPU has a trust zone where the governor resides. I needed to add the simple governor to the trust zone so it could be selected. There were 5 options listed, performance, power save, conservative, simple, and on demand, but before only on demand and performance were in the trust zone. Now I have added simple to that zone and it can be used. It is not quite a one liner like it sounds, but thanks to Faux123, I had plenty of code to review to put it together.

Here is a link to the commit, if you want to see the code (the green is what I added) :

https://github.com/alaskalinuxuser/kernel_samsung_jf/commit/9c61ec1218b9c9c463b3f2ace11f3734a0c5432b

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] darazor:
I was just looking at your previous post again as I rec'd the quote notice and I had just come to that conclusion re trust zone. So I was elated to see your new post.

I realize it is not a trivial exercise and I am greatly appreciative of those efforts that you have so very freely lavished upon we the users. Thanks D.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Well thanks, but you guys give me too much credit. Fortunately [MENTION=3332811]faux123[/MENTION] already did all the hard work, I just reimplemented it here. Have a great night!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] darazor:
You are a true perfectionist; I wouldn't prefer it any other way. Silk right out of the box. Super work! Thamks D.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New Kernel is up!

The latest news from the kernel thread:
[T-Mobile Samsung Galaxy S 4] darazor:
Just a quick aside. I am finding the battery drain to be extremely good. I wonder if anyone else is seeing this as well.
[T-Mobile Samsung Galaxy S 4] darazor:
Flashed and I was going to look at the voltage changing section but before I could I dozed off and when I woke up it was last week. So, I believe that the S-T continuum portion is working to a T. Found my way back eventually and now I see an array of voltages. I can only consider the possibilities. Will have to research this a bit before I do any playing. Thanks again. D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Glad you made it back to our spacetime! Hey, next time that happens do you think you could let me know that I am going to need a pair of vice grips over the next few days? It would have really come in handy a few days ago when I was broke down in an intersection..... [emoji3]
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
All,

Below is a nice guide for undervolting another phone, but the principles of voltage control are the same.

http://xdaforums.com/showthread.php?t=1558080

Here is a YouTube video explaining a few quick facts about undervolting:

https://m.youtube.com/watch?v=5nrOWZUsEEc

The bottom line is that you can save a little bit of battery power, but not much. The adjustments are in millivolts. However, properly tuned your phone will run cooler, which is a bonus.

So again, use voltage control at your own risk, but as with anything, the options being available gives you that much more freedom to choose how you want to use your phone. [emoji3]
[T-Mobile Samsung Galaxy S 4] darazor:
Well, I read the entire an dissertation; it is interesting and informative for sure. Though, I can't help but think that the parties of the 2nd part are most unlikely to adhere to the process put down by the party of the first part given that the value of pi will not change by more than 1 part in 10^-52 also, even if it did I feel certain that the expansion of the universe would remain flat.

But seriously. It's a delightfully elegant process however the time factor makes me even more pleased that you have incorporated the new S-T continuum function into your most recent kernel since my age would most surely preclude a venture into this exercise.

More or less the same conclusion as that of the video.

And, of course I jest. I may yet try it. I certainly love having the options. And, options are maybe the most important reason for owning an Android phone. Thanks to you and Linus T. D.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Yeah, I thought the time space continuum function might come in handy! :D

I am also pretty sure that I am not worthy to be in the same sentence with Linus Torvalds.

That being said, yes, the ability to change the voltages of your CPU are options that are not for everyone. However, for the daunted, consider this:

When I open up the Kernel Aduitor app, and go to the frequency table, I see this:

MHz -- % of use
1998 -- 2%
1890 -- 0%
1782 -- 0%
1566 -- 1%
1458-486 -- 0%
384 -- 6%
Deep Sleep -- 84%

So, 84+6+1+2=93% of my usage. The 0% MHz frequencies combined only make up 7% of my usage. The reason I point this out is that changing my voltages will have very little affect on my phone, since my processor usage is generally pretty low.

If, and only if, I wanted to make any changes (which I personally do only make one), I should focus on the "big users". I can't change the Deep Sleep settings from within, that has to be compiled. However, of the ones I can change, I would actually only need to focus on three settings:1998, 1566, and 384. If I was further pressed for time/effort, I should only focus on the biggest user, which would be 384 MHz.

Personally, the only one I change is the 1998 MHz. The default for my phone is 1200mV. I change it to 1175mV. The reason I do this is that is the original setting that I gave it when I overclocked it the first time. Some users reported instability, so I bumped it up to 1200mV to ensure that it worked well for everyone. I am effectively changing the mV for 2% of my time to be 2% more efficient. Overall that is perhaps a 0.04% battery saver/cooler phone temperature.

So, long story short, small changes may be easier than you think!

I will note however, that it will likely not make a noticeable difference in your heat/battery usage unless you start taking it to the extreme, which I personally, do not do.

If any body comes up with some good voltage tables, you are welcome to share them here! Be sure to include your PVS#, and your final mV, since not all of our phones use the same mV table. There are 6 different possible tables based on PVS0-6. My phone is a PVS3, since I start with a 1200mV 1998 MHz frequency.

To determin your PVS#, compare your default 1998 MHz frequency:

0 -- 1300
1 -- 1275
2 -- 1250
3 -- 1200
4 -- 1175
5 -- 1150
6 -- 1125
[T-Mobile Samsung Galaxy S 4] darazor:
Once again, you have cut to the chase and make perfect sense. I was a bit daunted by the elegant if some what impractical process of the "dissertation". I also hadn't given KA a really good enough examination to really grasp the significance of the apps opening screen and the usage %s. Hence, the small changes is almost certainly the way to clear the fog from the windshield.

So. I will thank you.

And, now I will thank LT. :good:D.

Sent from my AOKPMMALU powered semi-smart phone!
[T-Mobile Samsung Galaxy S 4] darazor:
Now That I've begun to look more closely at the frequency vs voltage for various steps, I am intrigued by two things. In the grand scheme they most likely don't mean much; I'm curious nevertheless.

All of the KA frequency steps increase by 108MHz except the first (384MHz to 486MHz) which is 102MHz and the 12th (1566MHz to 1782MHz) which is in effect a double jump of 216MHz precluding a 1674MHz setting. I was wondering if there could be any real world significance to those selections/exclusion or merely the result of quatum field fluctuations. D

Truthfully, my OCD side confesses to being uncomfortable with the break in symmetry.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Good observation!

You are very sharp, and correct, the rule is 108 MHz, and those are the only exceptions.

384 MHz: this should be 380, however, much like a car that is idling too low, there can be problems with stalling. For instance I had to adjust smartmax, because it has its own frequency table for deep sleep that was too low. This being too low can cause the Sleep of Death (sod). Other kernel devs use 384 as the minimum, so I followed suit, as their experience outweighs my own.

1674 MHz: If you were to use the space time continuum function, and look at my old kernels, or Arc-Team's kernels (where I got the source from), you would find that they have 1674 before the over clock was added. The kernels have limited "seats" at the frequency "table". More experienced devs could build a bigger table with more " seats". Due to my lack of knowledge, I am using the chairs available. To add 1998 MHz, someone had to lose their seat. At first I dropped 1890, but by request brought it back and ditched 1674. It was not random, however, because of two factors:

1 - 1566 and 1782 are both used in different governor settings, Lionheart, and I think intellidemand or badass. Yet 1674 was not a specifically called out frequency. For instance, when you poke the screen, the Lionheart jumps to 1566 MHz, etc.

2 - there are different tiers of frequencies. So to add 1998 MHz, something from the highest tier *should* go to maintain a deeper symmetry that is not viewable to the users, but to the coder.

Great question though. Hope that answers it! Keep those questions coming - iron sharpens iron, and your questions are always good ones!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com