yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] dirtyhank:
In what way? I use Google Music myself and works fine but I'm curious about the origin of this disruption and I'd like to take a look.
[X Style (Pure) Android Development] Hitti2:
Enable blue active. Play a song in poweramp. Hit power button to lock phone. Few seconds later you should hear music cut in and out.

I uninstalled and passed the 2 hour refund window for ex kernel manager. Not worth 4 bucks. It doesnt pick up temp, imho adiutor should be 4 bucks.

Sent from XT1575, TrupureXMM 2.4, FrankenClark 0.5.2.
[X Style (Pure) Android Development] HikingMoose:
I can't stream music on my phone if I'm using stock MM, for the same reason. That, and the laggy scrolling is MMs biggest downfall on this phone. I'm trying to use this kernel to fix it, but it still struggles.

---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------

That's awesome, because I refuse to use the Facebook app AND messenger app. I held out as long as I could on messenger. Then Facebook kept getting errors, saying the app I was on would no longer work, I needed to update. They force you to use two apps that use over 100mb if your ream, to do a simple task task that should only use like 15mb. I just use my browser now. But might check out your app.
[X Style (Pure) Android Development] dirtyhank:
While reviewing [MENTION=6176046]Digital Cha0s[/MENTION] screenshots I've remembered something I mentioned a while ago but it's worth repeating.

This kernel allows Fsync enable/disable but for safety reasons it's enabled by default. However, there's a bug in Kernel Adiutor that makes it misread FSync default value and it'll show disabled when actually it's enabled. No big deal unless you change anything in that tab and enable the "Apply on boot" switch, because next reboot Adiutor will disable FSync (remember the misread value I mentioned).

Bottom line: whenever you change anything in the "Misc Controls" tab of Kernel Adiutor make sure Fsync is set to your desired value. And keep in mind it always should be enabled unless you know what your doing.

Don't forget this advice because with next release you'll probably use that tab quite often ;)
[X Style (Pure) Android Development] HikingMoose:
Good to know, thanks! Hey I have a question for you (out anyone that knows the answer for sure), is there a difference in the two touch body interval sliders? The descriptions are identical. Not sure why there are two.
[X Style (Pure) Android Development] Digital Cha0s:
my understanding of those sliders is...

the first one is for CPU boosting with out any touch input and the other is for when your actively using the phone
[X Style (Pure) Android Development] HikingMoose:
Well, no matter what I say them to, it never seems to boost. Which I'm not used to. On my old phones with KToonz I could set up touchboost and it boosted the cores I wanted for however long I wanted then boosted. I can't get that to happen with this kernel and these kernel apps.
[X Style (Pure) Android Development] Digital Cha0s:
have you set up the CPU governor tunables for boosting? I noticed the the boost setting will say at 0 on interactive for my little cores no matter what I put the sliders at
[X Style (Pure) Android Development] ffonegod:
Question.. Which kernel app do you use kernel auditor or ex kernel manager? And why? I have a problem with kernel auditor keeping my settings when I reboot even when I save a profile and apply to boot
[X Style (Pure) Android Development] HikingMoose:
Yes, I try to set it up to boost, it just never works. It stays 0 like you said.

But there is no way to keep the big cores online long enough to adjust them. The kernel isn't set up to allow you to make changes. He has something set to make the cores go offline immediately.

I've been trying both, but they both have issues for me.
[X Style (Pure) Android Development] dirtyhank:
By taking a quick look at the source I'd say:

Interval: minimum time before the boost driver can attemp to offload CPU running thread to other CPU

Input Interval: minimum time the boosted CPUs will stay at or above the boost frequency.

The problem you're having with the BIG cores is related to hotplug. If you disable hotplug you'll notice boost works as always. Hotplug takes precedence over boost, in the sense that the BIG cores will stay offline unless the system load is high enough no matter you boost settings. This could be changed but IMHO it'd defeat the purpose of hotplugging.
[X Style (Pure) Android Development] HikingMoose:
Than you for the explanation. I don't quite understand the last statement though. If hotplugging nearly disables the cores, then turning it off doesn't defeat the purpose. At least not if your trying to make the kernel smooth. I'm just trying to get rid of the stuttery, laggy scrolling that MM suffers.

I do think I'm making progress though. I and boosting up my small cores, success they are the ones that want to run. And I'm just leave the big cores hotplugging. It's getting smoother. I'll keep trying things, and reading up on governor settings in unfamiliar with.
[X Style (Pure) Android Development] dirtyhank:
I meant you tipically want hotplug to offline cores to save power and only get them online when system load is high enough. You can always disable hotplug and see what happens but then you'll have to manually select the cores you want online.

In my experience the GPU plays a big role in smooth scrolling. Try the cpufreq or performance GPU governors (I use cpufreq myself).
[X Style (Pure) Android Development] guraki:
Can you explain the gpu governors please? Which do you suggest for smoothness?
[X Style (Pure) Android Development] dirtyhank:
I suggest you take a look at this comprehensive guide (scroll down to the GPU section):

http://www.androidmodguide.blogspot.com.es/p/blog-page.html

I like bluactive these days.
[X Style (Pure) Android Development] guraki:
About gpu which do you suggest? For cpu governors I have read a lot

---------- Post added at 07:35 PM ---------- Previous post was at 07:22 PM ----------

Moreover have you changed the default values of entropy?
[X Style (Pure) Android Development] chindynasty:
Want to share my experience with this kernel. I am on v5.2 and trupuremm 2.5. Used greenify left everything as is after flash. Getting great battery life. This is with play games.
[X Style (Pure) Android Development] chindynasty:
Here is what I got. Usually, I'm out of battery with this much SOT.
[X Style (Pure) Android Development] Hitti2:
[MENTION=2400758]dirtyhank[/MENTION]

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

Ima do some testing but it seems for now 0.5.2 broke a few things.
[X Style (Pure) Android Development] HikingMoose:
Thanks again. Very good info. I had already tried two other GPU governors, but they cause my phone to reboot immediately. I don't think I have tried cpufreq, but just switched it. It does seem smooth. Maybe you just solved all of my issues! Any other smoothness tips you can give would be greatly appreciated. Lol
[X Style (Pure) Android Development] SpasilliumNexus:
The kernel didn't break anything. Running 0.5.2 with ViPERAtmos and both mod and Google speech are working. Too lazy to dig through that thread for a link, but find my post and the OP's response to my solution over there and install the original libeffectproxy he attached to his response.
[X Style (Pure) Android Development] Hitti2:
Horse crap.

It broke poweramp reading files off the sd card.

It broke google speech in chrome beta.

It broke atmos.

Dont tell me it didnt break anything.

In fact I really don't see you sitting here by my side watching the entire time.
[X Style (Pure) Android Development] SpasilliumNexus:
Again. It didn't break anything. Not even that horrendous looking music player. User error. Fix it instead of having your hand out for advice all the time, based on your history and all.

You're the only one posting about these issues. Logic should've been kicked in.
[X Style (Pure) Android Development] Hitti2:
Again you're wrong.
[X Style (Pure) Android Development] HikingMoose:
PowerAMP reads from SD fine here. Haven't tried voice in chrome and hand no idea what atmos is. Lol
[X Style (Pure) Android Development] ffejy462:
Same rom and kernel

PowerAmp working fine(and with a good skin, it's not ugly)

Can't comment on Google speech, but doubtful.

Atmos working fine

Viper working too

mxpe 6.0
[X Style (Pure) Android Development] Hitti2:
Doesn't matter any longer. Went back to kernel 0.4 all is well.
[X Style (Pure) Android Development] Hitti2:
This funky. I installed 0.5.2 over a good backup that had 0.4.

I am trying to track the source of the problem I had.

Only thing now I haven't done is updated xposed to latest version. In which a lot of updates for programs came out around the same time and installed them.

My bad at blaming frankenkernel.

I don't get it.

I flash software the proper way. Clean flashing all the time. Never dirty flash.

I dunno what went bad.

My apologizes.

No poweramp issues no atmos problems, speech works. Like all the problems disappeared.
[X Style (Pure) Android Development] dirtyhank:
For performance I use cpufreq. For battery life simple_ondemand.

I haven't changed entropy values, at least not on purpose :)
[X Style (Pure) Android Development] dirtyhank:
Yep, for some reason all the *bw* GPU governors are quite unstable. I'd stay away from them.
[X Style (Pure) Android Development] dirtyhank:
Here we go:

v0.6

Vibration control (non-haptic)

Relaxed CPU macros for better power usage

File hosting now on AndroidFileHost

NOTES:

Vibration level can be changed with Kernel Adiutor, on the Misc Controls tab (read this). You can also control it vía sysfs by writing your desired value (0-127) to /sys/vibrator/pwmvalue

Haptic vibration (like when you press some buttons) can't be controlled yet. Fortunately the most annoying earthquake-like app/notification vibrations can :)

Kinda offtopic but loving the new TWRP 3.0. I was sick of the "SuperSU installation" prompt every time I flashed the kernel and, believe me, I've flashed plenty :)
[X Style (Pure) Android Development] guraki:
I installed twrp 3 but gives me error when installing systemless root zip.... The su zip is installed without errors!
[X Style (Pure) Android Development] dirtyhank:
Good to know, I didn't try to reinstall systemless supersu, just the kernel over the already rooted ramdisk.
[X Style (Pure) Android Development] lafester:
Awesome you are on a roll.

Any idea what causes the blinding full brightness at boot? Hoping it's a kennel level fix.
[X Style (Pure) Android Development] dirtyhank:
You mean the during the boot animation?
[X Style (Pure) Android Development] countryfolk07:
Pretty sure that is what he's talking about.
[X Style (Pure) Android Development] Hitti2:
I don't have a brightness problem at boot.

at the unlocked bootloader screen it is very bright for 8 seconds.
[X Style (Pure) Android Development] guraki:
Just to mention that cpufreq governor solves the problem of no smooth scrolling!!!! Curious about battery life though...
[X Style (Pure) Android Development] dirtyhank:
Well, I'm afraid there's no free lunch, it'll have some impact but I haven't noticed a huge drain.
[X Style (Pure) Android Development] unitz0mbie:
hi can you tell me the process you took to make viper work, idk man i tried and whenever i change the settings i dont hear the audio changing. and then when i try to delete it viper wont delete and my stock eq crashes. and i end up doing a clean install of rom again lol..
[X Style (Pure) Android Development] ffejy462:
http://xdaforums.com/showthread.php?t=3289075

You'll want a clean rom install (wipe everything but sdcard) If you flash this Viper installer if you're having those kinds of issues.

mxpe 6.0
[X Style (Pure) Android Development] HikingMoose:
My wife and I HATE that with a passion as well! Half the time I'm working on my phone is at night in bed. So rebooting sucks. Even face down, it lights up the entire room! I've almost burned my retinas out countless times by forgetting to put it facedown lol.

If that could be a kennel fix, that would be awesome. There is just no need for a screen brighter than my car's headlights. Haha
[X Style (Pure) Android Development] HikingMoose:
Sunnova, you just released one yesterday! What are you, going to start releasing nightlights now? Ha-ha. Well, back into recovery I go.
[X Style (Pure) Android Development] tombepa:
Is it normal for cluster 2 to show n/a?
[X Style (Pure) Android Development] dirtyhank:
Yes, it means both cores are offline (hotunplugged)
[X Style (Pure) Android Development] dirtyhank:
Well, yes and no. I can limit the brightness at the kernel level but it wouldn't apply during the first stage of the boot sequence, that's controlled by bootloader (I think).
[X Style (Pure) Android Development] ffejy462:
Change the logo.bin to a dark one. I deleted boot animation as well. Stock boot up was insanely bright, but with a dark logo.bin and the dark android default of boot animation it's not bad.

Edit: I used this: https://tapatalk.com/shareLink?url=...p?p=62878079&share_tid=3200607&share_fid=3793

Not a flashible zip. Extract logo.bin and flash via fastboot.

mxpe 6.0
[X Style (Pure) Android Development] lafester:
Makes sense as logo.bin survives rom flashes.
[X Style (Pure) Android Development] erikiksaz:
I had a brain fart, does SuperSU still need to be manually flashed after flashing this kernel?
[X Style (Pure) Android Development] dirtyhank:
It shouldn't be necessary, it patches the current ramdisk.
[X Style (Pure) Android Development] noorul89:
Fantastic Kernel [MENTION=2400758]dirtyhank[/MENTION] keep up the good work :)

Works brilliantly with TruPureXMM 2.5 and I just flashed TWRP 3.0.0.0 :)
[X Style (Pure) Android Development] cerobles1:
Yo [MENTION=2400758]dirtyhank[/MENTION] I've been playing with hotplugging and I gotta say there is something buggy. I set my min and max cores when screen is on, but whe. i go back to the CPU tab it shows all little cores on and one Big core on. Then slowly the other two little cores turn off and leave two little on one big one. Everytime I restart I noticed the min goes back to one and the max goes back to six. Trying to run two cores altogether. Would like to permanently turn off both big cores and run only two little while the extra two little are turned off permanently.

Running v0.5 and not sure if this has been polished off on v0.6

Also, I'm also using Kernel Auditor and I am leaning more towards a bug on the app and not the kernel but figure I ask. Any insight or tips???
[X Style (Pure) Android Development] pizza_pablo:
Thanks, for this! I dumped Facebook and Messenger apps. Installed this and am giving it a go.

Pretty functional, so far.

The pics may not be as big of pretty, but it's using a FRACTION of the RAM that the other two used! Like 4MB as opposed to 40MB+!
[X Style (Pure) Android Development] HikingMoose:
Maybe it's my settings, but it scrolled HORRIBLY. I deleted it almost instantly. I use the an internet browser, and it's silk smooth.
[X Style (Pure) Android Development] pizza_pablo:
It does studder, I've not found any functionality missing. I recently tried using Chrome, on phone for Facebook, but something I use often, was missing. I can't recall what, tho.

Still day one, but RAM use by the lite version is a tenth of the full app AND Messenger app. While they are both running anywhere above 40MB, each the lite app, which does both functions is running 4-6MB.
[X Style (Pure) Android Development] HikingMoose:
It was very light. But I can't stand scrolling lag. I've finally got rid of most of it with this kernel on stock MM. I can't revert back to something that has that much lag (for me, it was exception, like a 1 second delay before the screen moved, and it only moved a few centimeters, then stopped, then moved agian). I've been trying to do away with FB anyway, sick of the drama, and what the app represents. I'd rather live my own life, than watch others live theirs. I only check it for my Jeep groups, and a firearm group, that's it.
[X Style (Pure) Android Development] pizza_pablo:
Oh no, for me it only lags a bit.

As for using FB to check a couple groups, all the more reason not to use the full, resource hogging app.
[X Style (Pure) Android Development] Digital Cha0s:
hahaha I never said it was a perfect app but it will get the job done with less strain on the system.

The only real reason I use it is... it gives me a notification for messages where the browser didn't..... not to say the browser can't give a notification for that just never looked and this mini app seemed easier at the time
[X Style (Pure) Android Development] urimevs509:
geekbench scores are almost identical to TruPure with VadimTk's kernel. I thought the big cores were overclocked to 2ghz...
[X Style (Pure) Android Development] HikingMoose:
Chrome will notify you. But I switched to R browser and that doesn't.
[X Style (Pure) Android Development] Digital Cha0s:
right on but lets try to keep to the subject here Kernel related and all
[X Style (Pure) Android Development] dirtyhank:
You're right about the max/min resetting upon reboot, it seems like a Kernel Adiutor bug.

Regarding the BIG cores shutoff, unfortunately what you want to achieve is not possible yet. The Bricked Hotplug codebase I used is not aware of the BIG.little architecture so it only sees a pool of 6 cores and plugged/unplugged as it sees fit. I've implemented a quick hack so it always unplugs BIG cores first, but when it comes to plugging it still can happen that a BIG core is plugged before a little one. Gotta take a look at that and see what I can do.
[X Style (Pure) Android Development] Faschoda:
I can't download from androidfilehost. It says it has been removed. Someone got a mirror?
[X Style (Pure) Android Development] dirtyhank:
It is. I honestly don't care much about benchmark scores but since you ask here's an Antutu score I've just run.
[X Style (Pure) Android Development] Sheetzie03:
Haven't used the facebook app in years. Do all yourselves a favor and just use Facebook thru the browser, set a shortcut to it on your homescreen. Is it really that big of a deal ? Are you going to miss it that much? It's way too much trouble for what its worth. Hope you all that are still using it listen to me.
[X Style (Pure) Android Development] urimevs509:
I can definitely feel it's smoother, and I haven't felt the hit on battery (actually, the opposite)
[X Style (Pure) Android Development] HikingMoose:
Dirtyhank, which scheduler do you use? I've pretty much always used row, but when I was trying things to smooth everything out, I noticed zen seemed to increase smoothness. I have tried many of the others. I read up on then a a couple years ago and row sounded the best. But you may know better.
[X Style (Pure) Android Development] Sheetzie03:
Yep chrome notifications for Facebook might be better than the official app. LOL

Also, if there are ppl that completely will not consider using Facebook via chrome, there's always Metal for Facebook.

Edit: and apologies for off topic, will stop that now.
[X Style (Pure) Android Development] dirtyhank:
I use noop, might not be the best in any particular task but it's among the best in everything. Take a look at this:

http://andrux-and-me.blogspot.fr/2014/05/io-schedulers-and-performance-2.html
[X Style (Pure) Android Development] HikingMoose:
So.... In case you guys have not noticed, I've been working really hard to get this kernel dialed in to perform as smooth as stock lollipop. I think my current settings are actually SMOOTHER, thanks to the tips from dirtyhank and the reading I've been doing (and some past experience with Ktoonz). Here's what I'm running:

Small cores set to 1248MHz, with conservative goveror.

Big cores to 1536MHz. Interactive governor (I may still try other governors for the big cores).

I'm using the fiops I/O scheduler, and a read ahead of 1048.

GPU I haven't touched the speed, but I'm running cpufreq gov.

I have kernel samepage merging (ksm) enabled under miscellaneous settings.

For TCP congestion I always use Westwood.

It's the smoothest Android I've ever used, but I'm not sure how battery life will be.

I was running elementalx for the small cores for the last week. But it would lag slightly when you first touch the screen, buy was smooth when you were touching it. It would ramp down too fast, but could probably be adjusted to ramp down slower with the governor options. But I'm pretty happy with conservative, which is what I always used on my S4 with KToonsez kernel.

Hope this helps others with performance and hopefully decent battery life.
[X Style (Pure) Android Development] argenteloup:
Dirtyhank's performance profile is really smooth, but I could only got close to 4 sot.

So, I tweaked it here and there to get an extra hour sot without sacrificing much of smoothness. I did lower the resolution to 1080p since I play some heavy games.

I will just follow the format in OP:

CPU

LITTLE Cluster

CPU Governor: bluactive

CPU Max Frequency: 1440MHz

CPU Min Frequency: 302MHz

BIG Cluster

CPU Governor: Lionheart

CPU Max Frequency: 1824MHz

CPU Min Frequency: 302MHz

CPU Boost

Input Boost Frequency Core 1: Disabled

Hotplug (No change from the original performance profile)

MSM MPDecision

Minimum CPU online: 1

Maximum CPU online: 6

Max Cores Screen Off: 2

Idle Frequency: 384MHz

Thermal (No change from the original performance profile)

Core Control: Off

VDD Restriction: Off

Temperature Throttle: On

GPU

Max Frequency: 600MHz

Min Frequency: 180MHz

Govenor: msm-adreno-tz

I/O

(Internal)

Scheduler: sio

Read-ahead: 512KB

(External)

Scheduler: fios

Read-ahead: 256KB
[X Style (Pure) Android Development] ffonegod:
Wow.. How did you achieve this score.. What rom and what kernel settings and apps running???
[X Style (Pure) Android Development] Hitti2:
Ionno but I sure couldn't beat his score.

http://imgur.com/hEgtjD5
[X Style (Pure) Android Development] HikingMoose:
Is MSM set to MPdecision by default? Because ex kernel app doesn't have that. Nor does it have the internal and external I/O schedulers.
[X Style (Pure) Android Development] ffonegod:
Me either
[X Style (Pure) Android Development] treydilla:
What do you all use to edit the kernel? I'm new to this and I am using Kernel Aduitor, but I can't seem to find the touchboost setting anywhere
[X Style (Pure) Android Development] Chuckleb0ne:
I keep updating to the newest kernel builds but I still never get the option of having other than just the plain old regular CPU Governors. I don't have blue active, lion heart, etc. What am I doing wrong here? I flash the kernel via TWRP all the time and it works and boots fine.
[X Style (Pure) Android Development] dirtyhank:
ROM is MM stock and I was using my performance profile with a twist: disabled hotplug and kept all CPUs online. Not that this setup is very practical for everyday use but it certainly is quite a performer.

Hotplug is pretty aggressive in Frankenclark (especially with some governors) so it can affect benchmark scores, a for that Antutu run I just wanted to know the real horsepower :)
[X Style (Pure) Android Development] dirtyhank:
Yep, default values for MPDecision are:

Enabled: True

Min Cores: 1

Max Cores: 6

Screen off Cores: 2

Idle Freq: 480MHz

Start delay: 10sec
[X Style (Pure) Android Development] kadopt:
Guess ex kernel manager is kinda incomplete and kernel auditor is better...
[X Style (Pure) Android Development] ffonegod:
Where can I get the stock rom and how do I disable hotplug and keep cpus online in detail plz
[X Style (Pure) Android Development] xxBrun0xx:
I like the blue active governor setup, and it's certainly the smoothest I've seen the phone run. That being said, battery life is not good, barely 3 hours of SOT. I've seen 6 out of that tuned interactive setup, granted that was straight use vs 3 hours SOT over 16 hours, so the difference may not be as big as it seems. Just wanted to say thanks again for giving us a kernel we can play with!
[X Style (Pure) Android Development] Hitti2:
It is. And for 4 bucks, its not worth it.

Sent from XT1575, TPXMM 2.5, Frankenclark 0.5.2