yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] apophis9283:
#define INIT_DELAY	(60 * HZ) /* Initial delay to 60 sec */

#define DELAY	(HZ / 2)

#define UP_THRESHOLD	(40)

#define MIN_ONLINE	(1)

#define MAX_ONLINE	(4)

#define DEF_DOWN_TIMER_CNT	(10)	/* 5 secs */

#define DEF_UP_TIMER_CNT	(2)	/* 1 sec */

Looks good here
[Nexus 6 Android Development] apophis9283:
Updated OP to 1.6.1, AUTOSMP is showing up finally. Stupid code issue. Im out for a bit
[Nexus 6 Android Development] Thunderbolt69:
Well its not working here.
[Nexus 6 Android Development] apophis9283:
What app? Have you tried wiping cache/dalvik cache and flashing ukm and kernel? Mabve something got hung up?

I just tested on Synapse. It works fine.
[Nexus 6 Android Development] apophis9283:
Im thinking of getting rid of either mako hotplug or zen decision. I have until next time I release to decide. I may also ditch Intelli_plug. Does anyone even use Intelli_plug, personally I think its terrible
[Nexus 6 Android Development] II_DiE_4:
I played with sound options through Synapse..

If you play music and change the headphone volume it starts to go up and down.

This doesnt happened with kernel adiutor. Seems to be some problem with Synapse and sound settings.

Can you look it up if you can?

Loving the kernel btw.
[Nexus 6 Android Development] apophis9283:
I will be getting rid of MAKO hotplug and Dynamic hotplug. Mako is going because its similar to AUTOSMP and Dynamic (even though I just added it) is inferior to AUTOSMP.
[Nexus 6 Android Development] DreamFX:
I use it. But can live without it.
[Nexus 6 Android Development] apophis9283:
We use FAUX SOUND. If I may suggest, set faux sound to loudness and high performance and download the DOLBY flashable zip. Sounds amazing together.

Follow the directions from here, youll be amazed.

http://android.wonderhowto.com/how-to/get-dolby-atmos-surround-sound-any-android-0162010/
[Nexus 6 Android Development] Thunderbolt69:
Everything is working fine now since flashed 1.6.1, Dynamic hotplug is killer. I wouldn't remove it.
[Nexus 6 Android Development] apophis9283:
Very similar to AUTOSMP but that has more options. I have way too many. I may kick zen_decision
[Nexus 6 Android Development] apophis9283:
So MAKO and ZEN got kicked. There are plenty of hotplugs to choose from and are better IMO
[Nexus 6 Android Development] Thunderbolt69:
Hope you decide and keep the Dynamic Hotplug in your kernel. The best combo I've used so far is the Dynamic Interactive governor with the Dynamic Hotplug. Been the best kernel I've used so far. Thanks for sharing your time and work.
[Nexus 6 Android Development] apophis9283:
even though I havent released a build with recent changes I updated the OP with the hotplugs Im keeping. Made a build for myself. Hopefully hotplugs arent as cluttered

EDIT just flashed my changes. Hotplug page is much better

Im out for the night. Hope you all enjoy the kernel
[Nexus 6 Android Development] apophis9283:
I kicked Mako and Zen. Youre safe :)
[Nexus 6 Android Development] DontPushButtons:
Well, you've sure had a busy day. Thanks for the effort, I'll be giving autosmp a spin tonight. Dynamic has been pretty good to me so far as well, so if you're saying autosmp is better, we should be in for a treat.

Thanks again.
[Nexus 6 Android Development] str8str:
Yes I use it with the consecutive or eco consecutive setting and dyninteractive with great results. Also use mako with good results. If you know how to set it it's great. I'm using157.1 and it's working friggin great. Awesome job.

---------- Post added at 22:41 ---------- Previous post was at 22:18 ----------

I'll agree with you on Dolby I use sokp rom which has it built in by default
[Nexus 6 Android Development] apophis9283:
Well, it was one of those things where, no matter what I did, I was possibly gonna make someone mad. I just had to make the decision and thats what I chose to remove, mako and zen never impressed me
[Nexus 6 Android Development] ztotherad:
just my two cents, i use intelli plug, i prefer it actually. or seems to keep my phone cool but fast!
[Nexus 6 Android Development] apophis9283:
I kicked mako and zen. The ones i kept you can see in the OP
[Nexus 6 Android Development] str8str:
Have you uploaded a build with all the changes? Thx

---------- Post added at 11:10 ---------- Previous post was at 11:05 ----------

He kept it. I agree I stopped using it to try out all the different ones but I agree it's snappy and good on battery especially if you use the Eco conservative or one of the eco modes. Gonna try out the dyna plug when he uploads a build with the changes

---------- Post added at 11:11 ---------- Previous post was at 11:10 ----------

I can live with that. I still have the previous build if I want to use mako don't care about zen at all.
[Nexus 6 Android Development] apophis9283:
Ill try to have a build today. Its a good possibility. Worse case scenario tomorrow
[Nexus 6 Android Development] buckmarble:
Just my 2 cents on zen, remember its NOT a hotplug replacement. It is an mpdecision replacement. Mpd does not do any hotplugging either. Mpd does input boosting as driven by power hal and brings the cores back online after deep sleep. Zen online does the online part of it and leaves the boosting to a generic touch boost driver that most kernel devs are familiar with. The hotplugging is controlled by the governors.
[Nexus 6 Android Development] apophis9283:
I knew some of that, thanks for filling in the rest. Much appreciated
[Nexus 6 Android Development] apophis9283:
Hence why its called zen decision and not zen hotplug
[Nexus 6 Android Development] apophis9283:
[MENTION=2967322]buckmarble[/MENTION] You are always welcome here
[Nexus 6 Android Development] apophis9283:
1.6.2 is up in the OP. Mostly clean up. I did update ALUCARD governor. Also tweaked AUTOSMP (Its my favorite ATM). Let me know what you think, or if you have better settings please share and Ill make it that way out of the box. :)

Tonight and/or tomorrow I want to go through all my governors and hotplug and get it all sorted out

Also, i may kick Dynamic hotplug. If you look at it, its the same as AUTOSMP, AUTOSMP has more features

Im taking request too. Governors or hotplugs. The ONE THING is I have to have source to work with. and the featires CAN NOT resemble one i already have

Also, if any of you need help or have questions. My hangouts is steaven.android@gmail.com

If I dont answer right away, I will get back to you as soon as possible
[Nexus 6 Android Development] apophis9283:
I know Zen Decision isnt a hotplug, but if someone wants a mp replacement they would need to use zen. Zen is probably comming back and Dynamic is probably going away
[Nexus 6 Android Development] str8str:
Do your saying you would or should use zen for mpdes replacement and also a hot plug as well? So you would have two selected? Unless not using zen then only would have a hot plug cause kernel has own mpdes replacement. Sorry if that is hard to get

---------- Post added at 18:30 ---------- Previous post was at 18:25 ----------

They all say they replace qualcoms built in mpdes
[Nexus 6 Android Development] apophis9283:
we have several hotplugs, but no mpdesicion replacement. AUTOSMP hotplug has everything dynamic hotplug plus more. So really dynamic hotplug is redundant. So get rid of dynamic and add zen back. I will end up doing what i feel is right but if anyone wants to plead their case about dynamic ill listen
[Nexus 6 Android Development] apophis9283:
Any time. Thanks for the help and explanation
[Nexus 6 Android Development] apophis9283:
Im trying some code i found, supposed to be fast shutdown. Ill know if it works or blows up in my face tonight
[Nexus 6 Android Development] Thunderbolt69:
The only thing ive noticed when using AUTOSMP it spikes each core to max frequency too much and erratically does it. Dynamic runs each core more smooth and fluid and evenly with no erratic spikes. That's just my observation and experience trying it out.
[Nexus 6 Android Development] apophis9283:
I will look at autosmp file code, you can edit some of those settings to stop that

Just edited it some. I wont remove dynamic until at least next build where the modified autosmp can be played with
[Nexus 6 Android Development] apophis9283:
The hell with it, I brought back Zen Decision and Ill keep the other hotplugs. Seems not everyone uses the same 1 (or 3) so they can all stay. Hopefully everyone stays happy
[Nexus 6 Android Development] str8str:
Lol your funny. Thx bro
[Nexus 6 Android Development] apophis9283:
I just want everyone to be happy
[Nexus 6 Android Development] buckmarble:
If you use zen, don't use any of the other hotplug with it. Even though zen doesn't do hot plugging, there are some functions like core wake-up after sleep that conflict and can cause battery drain or erratic CPU behavior and possibly kernel panics. Really, any add-on hot plug is redundant because the governors already do hotplugging.
[Nexus 6 Android Development] str8str:
So we should just pick one of the mp decision replacements/hot plugs under hot plugs?
[Nexus 6 Android Development] apophis9283:
No, pick mpdecision or zen. If you choose neither then pick a hotplug
[Nexus 6 Android Development] SanJoseCA:
vortex 1.6.2 { dynamic_interactive + (AutoSMP || MSM MPDecision) } == ( Amazing Battery + smooth Performance ) == profit
[Nexus 6 Android Development] SanJoseCA:
Somehow I can't see it charging fast enough on USB. It always draws normal ( USB 2.0 ) current (500mA), when connected to USB 3.0.

Can someone confirm?

Stock LYZ28K + vortex 1.6.2
[Nexus 6 Android Development] Thunderbolt69:
Wanted to say thanks. The Dynamic Hotplug has been working great and the best for me.
[Nexus 6 Android Development] str8str:
You have both msm mp decision and auto smp enabled?
[Nexus 6 Android Development] mattlowry:
have you looked into pegasusq governor? when I used it on my note 2 it worked great.
[Nexus 6 Android Development] apophis9283:
I have np issues looking into it. I know there are a few "pegasusq" type governors. The issue I have, is the built in hotplugging. If I were to add it I would use zen decision instead of a hotplug
[Nexus 6 Android Development] apophis9283:
Do you have fast charge enabled in your kernel app
[Nexus 6 Android Development] SanJoseCA:
I use either of them. My favorite is msm mpd, but AutoSMP isn't bad either. I get around 1.2 days battery with msm mpd, no additional juice savers. I have more than avg usage. Also I do multiple reboots for flashing the stuff. I have to be on Wifi all the time too.

---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------

Yes, I do. I use Synapse.
[Nexus 6 Android Development] apophis9283:
Ok let me see whats up
[Nexus 6 Android Development] apophis9283:
Version 1.6.3 is up. Should fix a few things. I still need to go through all my governors and hotplugs, the buildd I posted should do you all for a day or two
[Nexus 6 Android Development] apophis9283:
Ok so I am getting better charging stats from USB. You will not see the highest it will go. Let me explain. You know the N6 has a fast charger. Heres what you may not know. If the phone is almost dead and you charge it, its going to charge stupid fast but as the battery gets more full, it slows down the charge quite a bit so that it wont harm the battery. You can see for yourself. See how fast it charges in empty state vs somewhat of a full state. Needless to say again, I did get faster charging from usb on 1.6.3
[Nexus 6 Android Development] galaxyman4g:
Does kernel make phone run faster or battery or both thank you for your help
[Nexus 6 Android Development] apophis9283:
As everyones setup is different and the fact I have a wide variety of options. I say this, flash it, play with it. See if you cant get it where you like. If not its easy to flash another kernel
[Nexus 6 Android Development] galaxyman4g:
Thank you so much
[Nexus 6 Android Development] apophis9283:
Theres plenty of people in this thread that would help if you needed it. Im around most of the time
[Nexus 6 Android Development] apophis9283:
I can get MSM_LIMITER to see my max cpu frequency. Not sure why
[Nexus 6 Android Development] apophis9283:
I have some commits ready to go all local. I want to test them out but if they work should save more battery

Also if anyone had any ideas on why msm limiter isnt seeing the overclock steps (the last two) Im open to suggestions
[Nexus 6 Android Development] dreamteam:
i dont have this problem. both of the slides are still there.
[Nexus 6 Android Development] apophis9283:
No i added 3.0 GHz + frequencies that arent showing
[Nexus 6 Android Development] adio201:
What setup you have?
[Nexus 6 Android Development] apophis9283:
been at this for some time now. I cant get MSM LIMITER to show proper frequencies. 2899 is as high as it goes
[Nexus 6 Android Development] Droidphilev:
Hi all,

Probably been asked before but:

1) can i flash this kernel without setting anything up? I mean it works ok without Synapse and extra zips to flash?

2) i know it works on cm based roms (bliss of course) but does it also work on stock roms?

3) will my usb stick work (usb otg or usb host)?

4) multirom is no problem?

That's all i will ever ask here so give me some credit please :)
[Nexus 6 Android Development] apophis9283:
OP updated to 1.6.5. Enjoy.
[Nexus 6 Android Development] apophis9283:
None of that should be an issue. You still need a kernel app. It boots with performance and it remains onbootcompleted, so youll want to pick a different governor. If there is an issue, just let me know
[Nexus 6 Android Development] Droidphilev:
Hi,

Thanks for your answer apophis9283!

You wrote that i still need a kernel app. Do you mean that the standard settings are not the best one?

I did some tests and something from my questions didn't work :) : usb otg works on a cm based rom but not on a stock based rom it seems. i tried cleancore rom with vortex and with that combo inserting my usb stick does nothing :) AFAIK usb-otg has something to do with the kernel but this i know from some reading. kinda noob at these things :)
[Nexus 6 Android Development] apophis9283:
Look at post 2. Thats my setup. Using synapse. Its a little old but close to what i still run
[Nexus 6 Android Development] Droidphilev:
I saw the second post, thanks for that info. Still i would like to keep it as simple as possible. Is kernel adiutor and setting governor to "CONSERVATIVEX" enough for daily use?
[Nexus 6 Android Development] apophis9283:
yeah, theres probably gonna be a few more tunables you should set, but otherwise good to go
[Nexus 6 Android Development] Droidphilev:
thank you for this wonderful piece of soft and all the help!!!
[Nexus 6 Android Development] apophis9283:
You're welcome. Enjoy!
[Nexus 6 Android Development] apophis9283:
So im at i little over 2 hours screen time,68 percent and its saying 15 hours left
[Nexus 6 Android Development] :
Depends on your governor I think. A few of your governors have the max frequency hardcoded at 2899000.

https://github.com/APOPHIS9283/vortex/search?utf8=✓&q=2899000

Basically, if you're running one of those and try to use msm limiter it probably won't allow past that hardcoded max.
[Nexus 6 Android Development] apophis9283:
I just made some changes and gave credit to you

Edit, still only goes to 2899
[Nexus 6 Android Development] :
No worries, hopefully that was what was causing it.
[Nexus 6 Android Development] apophis9283:
I just posted above you. Still at 2899. WTF is really going on lol
[Nexus 6 Android Development] apophis9283:
https://github.com/APOPHIS9283/vortex/commits/lp5.1

you can see what ive tried. I just edited the defconfig buiding now

[MENTION=2967322]buckmarble[/MENTION]. Any ideas? I hate to ask you
[Nexus 6 Android Development] :
Honestly, it might be worth cleaning things up a bit by creating a shamu specific ukm script.

I'm going to pay around with it for a bit and see if I can't figure something out.
[Nexus 6 Android Development] apophis9283:
I would be appreciated. Im still digging around
[Nexus 6 Android Development] apophis9283:
It has to be my coding. Kernel auditor doesnt show it either
[Nexus 6 Android Development] :
Just from looking at your commits...

The way that xileforce is doing his OC'ing seems... dirty...

Why wouldn't you have just done it similar to how Flar2 did the OC? Looks much cleaner, and you're not just deleting big chunks of code.

That, and you have the same *sort* of code committed twice... one from Xileforce to limit cpufreqs, and one from flar2. But you never reverted the first to do the second.

https://github.com/APOPHIS9283/vortex/commits/lp5.1/drivers/cpufreq/qcom-cpufreq.c
[Nexus 6 Android Development] apophis9283:
Ill have to revert those and find flar2's commit
[Nexus 6 Android Development] :
You had it at one point, and overwrote it with the ones from Xileforce.

Committed here: https://github.com/APOPHIS9283/vortex/commit/0680bcd1fb8c1071c000c4e88bd9c43a5f8a93af Then the next commit reverted it for some reason. The following takes Xileforce's 3.03ghz OC commit.

Then somehow you reverted this https://github.com/APOPHIS9283/vortex/commit/f6dec4aed142d34503a7ea2df48b8ab179dafab5 basically twice.

Personally, I'd roll the commits that affected that file back to where you had Flar2's OC committed, then just modify it for 3.09ghz if that's what you want to use.... Then do the 2 or 3 commits that are still applicable.

I'm guessing that somewhere in that mess something got messed up.

Not that I'm trying to nitpick or criticize, just the most likely scenario
[Nexus 6 Android Development] apophis9283:
I think i got it.
[Nexus 6 Android Development] apophis9283:
Zen kernel dev took flar2's oc and made it better as i read in the comments. Then it show zen dev bringing in xileforces oc stuff. This should work
[Nexus 6 Android Development] apophis9283:
Ok, I compile it but in synapse ssseekbar has failed

something went wrong
[Nexus 6 Android Development] xtcdk:
Thanks for a great kernel . btw . wouldnt it be easier to have ukm/UCI support in kernel so no need for sepperat ukm zip . ?? Not that i know anything about kernel devolepment

Shamu/Hammerhead/Flounder Dkwhq
[Nexus 6 Android Development] Mr_S:
Funny behaviour changing different governor per core. It doesn't seem to stick and changing core 1 and 2 to on demand for example(or whatever)

And 3 and 4 to hells results then pressing tick sets them all going to the core 1 and 2 governor.

Hope that makes sense! Also don't like the setting to change all cores together. There's definitely something going on with the governor per core control. I'll get a log later
[Nexus 6 Android Development] apophis9283:
Im probably just gonna remove it. been wanting to for some time
[Nexus 6 Android Development] apophis9283:
Not everyone uses Synapse, Im not gonna force then to have UKM code is its useless to them
[Nexus 6 Android Development] :
It's trying to set a value that doesn't exist then.

Is check where the value for that seek bar is being pulled from. I'd guess that the sysfs entry for the value doesn't exist.
[Nexus 6 Android Development] apophis9283:
I tried something else. If this doesnt work then ill have to get back to it monday
[Nexus 6 Android Development] apophis9283:
Its not showing so this will need to be put on hold until the time UKM can be edited for a fix
[Nexus 6 Android Development] xtcdk:
Yeah . thats a good point . didnt think about that. Have a nice weekend ?

Shamu/Hammerhead/Flounder Dkwhq
[Nexus 6 Android Development] apophis9283:
I looked at ukm, look like it will need editing. Im just not sure where. It tries to pull from sh $DEVICE CPUFrequencyList

and I suppose its not finding the higher clocking
[Nexus 6 Android Development] :
Yeah, currently there isn't a case match in device.sh and there isnt a shamu.sh script. So I'm not entirely sure where it's even getting the values from tbh.
[Nexus 6 Android Development] apophis9283:
It lets me min to 35 and max to 2899. Im not sure either
[Nexus 6 Android Development] :
Actually, just looking at it... it's doing exactly what it's supposed to do...

adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
35800 98300 300000 345600 422400 652800 729600 883200 960000 1036800 1190400 1267200 1497600 1574400 1728000 1958400 2265600 2457600 2496000 2572800 2649600 2726400 2803200 2880000 2899200

if you want UKM to show anything higher than 2899200... you'll need to make the kernel update the available frequencies listed in that sysfs path.
[Nexus 6 Android Development] apophis9283:
I see it but may need hellsgod to help
[Nexus 6 Android Development] :
After looking at it some more. I don't think it's got anything to do with MSM limiter.

root@shamu:/sys/devices/system/cpu/cpu0/cpufreq # cat cpuinfo_max_freq
2899200

The overclocked frequencies aren't showing as an option.

Maybe it's something with the way you added them into the frequency table?
[Nexus 6 Android Development] apophis9283:
I got it to 3.03!

We have major oc. Im trying some other stuff real quick
[Nexus 6 Android Development] apophis9283:
Version 1.7 is now in the OP. I added a few things, one the ability to oc up to 3.03. Ypull notice I have 2 UKM files. 4.1 will stay up for those who like the cpu governor one click deal. 5 has it taken out so you have to set all 4 manually. thanks to Hellsgod who has been a never ending help. He awesome.
[Nexus 6 Android Development] apophis9283:
I had to take it down for a bit.
[Nexus 6 Android Development] Thunderbolt69:
The download says 404 not found.

---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------

Disregard my post.
[Nexus 6 Android Development] apophis9283:
I will be up soon as long as what I want works
[Nexus 6 Android Development] apophis9283:
Ok I know I posted this in a previous post but to recap

Version 1.7 is now in the OP. I added a few things, one the ability to oc up to 3.03. You'll notice I have 2 UKM files. 4.1 will stay up for those who like the cpu governor one click deal. 5 has it taken out so you have to set all 4 manually. thanks to Hellsgod who has been a never ending help. He is awesome.

the hold up was after I got it to oc it took 35MHz away, so I had to add it back. Theres also some other commits I needed as well. Im out, I hope you enjoy! :)
[Nexus 6 Android Development] apophis9283:
If your going to overclock heres a few things to keep in mind, Use the thermal stuff to keep it from getting too hot. Dont use a performance type governor. I would stick to conservative type governors. I also switched to intelli plug and using conservative 4 settings. It pays to be careful. I would NOT increase voltages. Ive been running it at max frequency for a bit and there doesnt seem to have any bad things happening. Seems smooth as can be

(you dont HAVE to oc)
[Nexus 6 Android Development] an21281:
Updated to 1.7 and for some reason my phone now says im running out of internal storage, was running 1.6.5 previously
[Nexus 6 Android Development] apophis9283:
Ive had it happen. Simply reboot and wipe cache/dalvik cache. It goes away
[Nexus 6 Android Development] an21281:
Tried that, the screen just goes dark after the boot animation. Also tried re-downloading then restoring A Nan backup reflashing still same problem.
[Nexus 6 Android Development] apophis9283:
Everything is fine here. maybe a ROM issue?
[Nexus 6 Android Development] an21281:
Haven't had any problems(except cpu freq NOT sticking using KA) running any of the past builds on Pure, I will try another rom and see how it goes. Thanks for the great work so far, love this kernel
[Nexus 6 Android Development] wrongway213:
Click the little menu button toward the bottom right that says "zips" and select "Images" and it will show up
[Nexus 6 Android Development] jolly_roger_hook:
Is this going to be made to work on both cm and aosp ROMs because it doesn't work on pure for sure
[Nexus 6 Android Development] DreamFX:
Couple people have already confirmed it does work on AOSP and CM. I can't personally confirm as I'm on a cm based rom at the moment.
[Nexus 6 Android Development] jolly_roger_hook:
Strange I tried it last night and had to start over from a clean install couldn't even restore a backup