yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] :
Honestly, I would for now if you're having this issue.

Like I said, I thought it was an intellithermal issue when I started having it. As I played around, I found it was still doing it regardless of the thermal daemon I used.

I'm pretty sure it's scaling down, but never scaling back up.

Like I've said before.... We're winging this. Neither of us are professional programmers. What we're doing is pulling in a bunch of people's code from all over the web and trying to make it play nice. I had an issue setting governors in the MSM_LIMITER interface that apophis did not. I ended up asking neobuddy89... we were missing a few commits for cpu_freq.c... but why did I have problems and he didn't? I dunno... magic? I was looking over my logs, never saw it. I may have had the debug level too low. W/E.

have you ever had your entire extended family in town for a holiday?

....Yeah, It's like that.

For instance, I've spent all night trying to make Blu_plug able to be turned on and off, and I'm getting stupid errors with comparisons for if statements that *I SHOULDNT BE GETTING*. No idea why.

Give it time guys, we'll get to the bottom of it. I know I come of like a ****, but I'm really not. I just have no patience for XDA turning away from people trying to learn/develop/help contribute... into "OMGz I WANT THE NEWEST FEATURES ON THE NEWEST BASE NAO!!!!!"

It used to be that you had to watch XDA Noobz as part of the signup.

These days, it's all coddling and hugs... wtf.

*edit*

I know I quoted you, but that's not directed at you...
[Nexus 6 Android Development] apophis9283:
For now. We are looking into this as fast as possible. We are comparing issues between each other and issues you all are having. we'll get her going soon

I use synapse with 0 issues. Not one flaw. Holds even after a reboot. others arent so lucky. trying to figure out why might take a bit
[Nexus 6 Android Development] str8str:
No worries I get it
[Nexus 6 Android Development] apophis9283:
Flashing my newest build with ukm 9 will bring back vibration control and more wakelock control
[Nexus 6 Android Development] ztotherad:
random question, but is there anyway to get synapse to stick after reboots and not have to input the information again? it's just a little hiccup that bothers me lol.
[Nexus 6 Android Development] :
Honestly I'm not sure. Mine does the boot stability check wake each boot even though it's unchecked. It annoys me too, just haven't tried to figure what triggers that yet... Especially with it being unchecked to check that.
[Nexus 6 Android Development] apophis9283:
mine stick
[Nexus 6 Android Development] ztotherad:
what the hell do you do differently? lol
[Nexus 6 Android Development] apophis9283:
flashed cataclysm rom, then permissive.zip, then ukmv9, then the kernel. I restore my apps, set my rom up, then set my kernel settings

go into synapse, youll see in the cpu page msm limiter. it should be checked. set min to 98 and resume max to 2956, suspend max frequency to 960. now make sure all 4 off your cores are at 98 min and 2956 max. see if that works

Also try wpining cache and dalvik cache. @ days ago I came across code that should have added the ability to on/off a wakelock, but it wasnt there, I was confused as hell. I knew the code was there but couldnt for the life of me figure out why not. for sh*** and giggles i decided to go all in. I wiped cache and dalvik cache 4 times. (probably not needed but wanted to make sure) reflashed ukm-9 and kernel. I did it originally because i killed autosmp but it was still showing up. So once it rebooted I started going through snapse to set it up. This time autosmp was gone (should have been gone the first time i compiled with removed code, but even the second time it was till there) and that wakeelock setting was there this time. I honestly dont know whats going on, but maybe the phone just needs a massive dalvik cache/cache clearing.
[Nexus 6 Android Development] str8str:
Is the doze feature done by the kernel?
[Nexus 6 Android Development] wrongway213:
Synapse is ridiculously finicky in terms of booting with different parameters allowed in the kernel than were allowed with last saved settings. For instance, if I attempted to flash your kernel over Elite and boot, even if I flashed stock kernel in between, I would get all the options from Elite, and not your options from Vortex - I have found that it's a quite unreliable combo of wiping caches, wiping UKM data, re-flashing the kernel and even occasionally reflashing UKM itself. Given your kernel has so many options and you are constantly adding and removing parameters, I believe you may be having the same issues on boot as one would have when switching from one kernel to the other without properly clearing data. A clear kernel install was very simple with UKM on LP, but on M I get very unreliable results no matter what process I follow.
[Nexus 6 Android Development] :
Yeah, I've noticed similar. It's a nice tool.. But its self to be more and more of a headache all the time.

I'm starting to think it might be better to just write a static uci and ditch it
[Nexus 6 Android Development] apophis9283:
Ok, I tweaked Preservative governor and added ZEN_DECISION, ZEN_DECISION will NOT show up in Synapse but I found it in Kernel Adiutor

OP has been updated.
[Nexus 6 Android Development] spevil07:
For my opinion Kernel Auditor is better than other apps to change something.

Thanks for updating!

Gesendet von meinem Nexus 6
[Nexus 6 Android Development] MrSplaat:
Works a little better, but it's still pretty high. Peaking at max freq a lot, while dropping down to 1497, and once inn a while down to 1036 and 960. Takes around a second or two before it shoots up to 2457 again.

Had to tweak one of the hotplugs to make it work a little better, but even without any screen inputs it's pretty high.

Would've liked to see it act stable, at least.
[Nexus 6 Android Development] apophis9283:
Ill look at it and smart max eps later on today. They are actually pretty similar
[Nexus 6 Android Development] wrongway213:
Use this modified build from [MENTION=4517211]Xileforce[/MENTION] and Synapse will have options for Zen, among other things

https://docs.google.com/file/d/0B6n0VW96A9MoYTRUc0NRRjQybEU/edit
[Nexus 6 Android Development] apophis9283:
Thank you. Youre awesome. I am going through every governor now and tweaking them
[Nexus 6 Android Development] apophis9283:
OP has been updated..... again

I went through and tweaked all the governors. well 95% of them. Please let me know if you have any issues
[Nexus 6 Android Development] apophis9283:
Link in OP has been fixed. Its url'd now. No copy and paste just click on the link. Sorry about that
[Nexus 6 Android Development] wrongway213:
No problem man, I love messing with kernels so I'll probably pop in from time to time as this develops.. I can't stay away from kernel threads lol
[Nexus 6 Android Development] hellsgod:
Like me :cowboy:

hells
[Nexus 6 Android Development] MrSplaat:
Aah, now it works just fine, thanks!

Edit:

Looks like I'm missing DanceDance.
[Nexus 6 Android Development] apophis9283:
I removed dancedance and one other governor when i brought in conservativex. I want to give you the most and exotic options, but i dont want it to be a cluster fu**. If you all get a chance, thank hellsgod, he has been amazing. Helping out when he didnt have to. True XDA spirit. Thanks man(fyi he gave me his any kernel zip so everyone could enjoy vortex)

:)
[Nexus 6 Android Development] rignfool:
Exotic options....

I would love to see another kernel with Yank555's hard limit driver...
[Nexus 6 Android Development] apophis9283:
Im sure i can find it, not sure how it would react to msm limiter
[Nexus 6 Android Development] 875295391:
Good kernel.Works well with AICP.
[Nexus 6 Android Development] Psych0t1c20:
I'm having a strange issue. I flashed the kernel, battery dropped to 26%. I reboot to recovery, and it says I have 50%. Anyway to fix the battery reading?
[Nexus 6 Android Development] apophis9283:
maybe just a fluke? could be ROM as well. As I havent had that happen it would be hard to say.

I played with hard limit, it gonna take some playing with, which ill get to tomorrow. Thanks for everyones patience as I get things sorted out. Kernel noob, Im still learning
[Nexus 6 Android Development] Psych0t1c20:
Idk. Weird. I'm on blisspop. Could be the ROM. Kernel still good regardless. ?
[Nexus 6 Android Development] apophis9283:
Im a bliss team member :)
[Nexus 6 Android Development] Lemagex:
Hnnnng got all the features i want and more. This could very easily become my new daily driver
[Nexus 6 Android Development] wrongway213:
A static uci to use.. without UKM? If I may clog up this lovely development thread with a total noob question, may I inquire as to what this statement might mean to the layman? Unfortunately Google thinks I want information on IMAP (or to be redirected to the Synapse thread) when I try to search for android uci info - if you could either break that statement down a bit or simply refer me to a resource (or even the correct search terms - "Android uci" is not cutting it) to find some more information on this, I'd greatly appreciate it. I am quite fond of all UKM can do but it has caused me tons of headaches as well, so the idea of an alternative is quite interesting to me.
[Nexus 6 Android Development] :
No, that's fine. This is the kind of stuff that actually doesn't bother me at all. It's a constructive question.

Here's all the information that you are looking for: https://github.com/AndreiLux/Synapse/wiki

Basically, UKM is doing a few things. It uses an init.s script called "UKM" which is intended to clean things up on boot.

The uci that it uses in system/xbin is a script that reads through all of the ukm json files to generate the desired options.

The difference is that ukm is designed to be flexible by checking the sysfs paths for various things to ensure that they exist, if they do it shows the sections. This is great, except that init.d doesn't necessarily run at a precise point during boot like you would expect. This means that its possible that the sysfs nodes aren't generated yet when it runs.

Using a static uci, you just put the stuff for the features you have. No need to check if the nodes are present to determine if a feature is there.. M you know it is.

Not sure it would help, but I think it would get weird of some of the weirdness. It's just more hassle sometimes if you're changing a bunch of features.
[Nexus 6 Android Development] wrongway213:
Man, you are certainly a plethora of information. That was all I could ever want know about uci and then some, I quite appreciate the link and the explanation. I find the concept of a static uci interesting, as by your explanation and by simply looking at the word "static", I am wondering if you are really speaking to resolving the big "flaw" in Synapse - the dynamic config/control. I have spoken to several kernel developers at length about numerous issues as I am quite a fan of kernel toying, testing and all that jazz. All have at some point found out I use UKM and Synapse as opposed to the "standard" Kernel Adiutor, and all have expressed a worry about Synapse's dynamic nature. It almost makes me wonder if it'd be simpler for devs to just, say, add a UKM branch specifically for commits that enable features or sysfs nodes and use said branch to build static ucis from. Not sure how else one would accomplish keeping said static uci up to date with an ever changing kernel like this one, but something along those lines could possibly really make things easier - I am sure I quite oversimplified it but the idea sounds like it could be a good one to me. Alas, if only Faux Sound for the N6 worked without Synapse.. I could just use another app and ditch the headache, haha. Thanks again for the info, a lot of reading to do now :good:
[Nexus 6 Android Development] :
Honestly if you're only using synapse for FauxSound (and it's flaky). Just do it manually with an su.d script, it'll be a lot more reliable imo.

Just change the following bit's "XX" values to what you want them to be, then toss this into a file in /system/su.d (you may need to make the folder if it doesn't exist) and make sure the permissions are set to 0755

#!/system/bin/sh

echo XX > /sys/kernel/sound_control_3/gpl_cam_mic_gain
echo XX > /sys/kernel/sound_control_3/gpl_headphone_gain
echo XX > /sys/kernel/sound_control_3/gpl_headphone_pa_gain
echo XX > /sys/kernel/sound_control_3/gpl_mic_gain
echo XX > /sys/kernel/sound_control_3/gpl_sound_control_hw_revision
echo XX > /sys/kernel/sound_control_3/gpl_sound_control_locked
echo XX > /sys/kernel/sound_control_3/gpl_sound_control_rec_locked
echo XX > /sys/kernel/sound_control_3/gpl_sound_control_version
echo XX > /sys/kernel/sound_control_3/gpl_speaker_gain

If you're not sure what the default values are, you can adb in and cat those files (or look at them in a root enabled file browser).

The added benefit of this, is that you can actually just make a flashable zip that adds this file, or push it over.

I think there may also be a version of su.d that runs from /data/local but I'm not 100%. If there isn't you might be able to create a junction for su.d to point to a folder in your /data path. This way you would just need to recreate the junction on flash.
[Nexus 6 Android Development] apophis9283:
Updated UKM to version 10. Some clean up.
[Nexus 6 Android Development] rignfool:
On your sdcard... There is either a synapse... Or a UKM directory... Delete that between kernels...

If that doesn't solve it...

In /data/ there will be a UKM directory... Delete that between kernel flashes
[Nexus 6 Android Development] apophis9283:
Hold off on that. Im gonna release UKM 11 which has the cleanup but also adds BLU_PLUG. Thank again to yoinx, BLU-PLUG can be toggled
[Nexus 6 Android Development] apophis9283:
Ok, UKM version 11 is up and has to go with vortex kernel 1.6 which has been updated. A few commits for kernel, yoinx did an amazing job. We have BLU_PLUG and it can be toggled. YAY! As far as UKM 11 not only is it needed for BLU_PLUG to work, I cleaned a lot of it up.

As always ENJOY!

I screwed up im re compiling the kernel
[Nexus 6 Android Development] apophis9283:
I screwed up. i had BLU_PLUG commented out when I built the first time. I just updated the OP with a fixed version 1.6
[Nexus 6 Android Development] imaverik:
good news

Moving in the right direction.

still have the msm off but....

UKM11 and v1.6 seems a lot better before installing kernel auditor.

I am able to set the cpu speed for many of the governers and it will stick if the msm's are off.
[Nexus 6 Android Development] apophis9283:
got some stuff merged, also killed DYNAMIC_HOTPLUG seeing as we have better ones and it needed to be less messy. Not releasing a build just giving you a nightly info type thing
[Nexus 6 Android Development] wrongway213:
Yeah.. this was a very simple and reliable method for me on LP and as far as I know this is the correct way to do it.. I dunno if it's n issue with my BusyBox setup on M (using Busybox X instead of normal Busybox so UKM will set on boot), but this is very hit or miss for me on M ROMs thus far... it's a mess trying to flash from one kernel to another on M on my device.
[Nexus 6 Android Development] Mr_S:
Get this error message in synapse

Anyone?

Edit, last LP kernel blisspop
[Nexus 6 Android Development] beepea206:
It looks like the freq lock is setting automatically (on MM), rather than staying off. Is that normal?
[Nexus 6 Android Development] :
I exposed those values in the mm kernel, because people like to see them. I don't think the same was done in LP. It's nothing to worry about.

You're right. It's something that I didn't notice originally. It's something that I messed up on. I've got to redo some things to get it fixed
[Nexus 6 Android Development] apophis9283:
So, Vortex V1.7 is live and updated in the OP. Should be a little smoother.
[Nexus 6 Android Development] zero100101:
Misc control>network> is it OK to change that on highspeed?
[Nexus 6 Android Development] apophis9283:
Feel free to set anything you want.
[Nexus 6 Android Development] apophis9283:
Im gonna be honest. Im gonna remove fauxsound from ukm. His app is better. I also have to fix fauxsound. Plan on doing all this tomorrow
[Nexus 6 Android Development] :
Personally, I'd ditch faux sound altogether and go with Franco's sound driver. Faux hasn't touched his in a long time and it doesn't seem to actually do anything. Francois driver is much more straight forward as far as the code goes imo for troubleshooting.
[Nexus 6 Android Development] zero100101:
Cool kernel BTW ,but its having a hard time on first boot ,im on mm with chroma ROM , idk why n I can't help much on logcat cus idek how :p ,but I just have to reboot it then it work on second reboot :). Thx for sharing ur kernel :)
[Nexus 6 Android Development] apophis9283:
Yeah first boot can take awhile
[Nexus 6 Android Development] apophis9283:
Id have to find source, get rid of faux sound and make sure it works with ukm, but i would be willing to switch
[Nexus 6 Android Development] wrongway213:
Gotta say one thing.. Faux's app definitely does not work better than Synapse on the N6. To be honest, Synapse is the only app that has functional FauxSound - Faux app and KA both are broken in terms of FauxSound. Afaik Franco's drivers do not offer PowerAmp gain controls either.. to be honest, from all I have read, researched, and flashed, it seems like pulling FauxSound from UKM would basically kill audio tweaking on the Nexus 6 entirely. Obviously your work, your vision, your decision and I'll respect it whatever you do - I just want to make sure the fat that the feature would indeed be missed does not go unheard. Whatever you guys do, I know you will do it well.

As an aside, I did try the solution of just making FauxSound values a su.d script, but it refuses to recognize for some reason - probably new M root/perm issues.
[Nexus 6 Android Development] apophis9283:
Well either way, atm fauxsound is busted to pieces. Im gonna look into i totday
[Nexus 6 Android Development] :
It doesn't, but it's pretty trivial to add.
[Nexus 6 Android Development] apophis9283:
I just reverted faux sound, and re implemented it. Curious, there were some things that needed to be worked out. Compiling now
[Nexus 6 Android Development] apophis9283:
That driver is too old its from 2014. Neither Synapse or his app seem to work, tested on pandora. Its the latest driver i could find. But at this point there is no reason to have his sound controls in UKM. Just doesnt work
[Nexus 6 Android Development] :
Is anyone still experiencing the Max Freq stickiness that was happening before?

I haven't seen it happen in a few days now. I was trying to track it down, but it doesn't seem like it wants to happen again.
[Nexus 6 Android Development] apophis9283:
Kernel V1.8 is up along with UKM-V12. Basically switched from FAUX SOUND to FRANCO'S. Enjoy.
[Nexus 6 Android Development] apophis9283:
Im having really good luck with UC/OC and UMBRELLA_CORE. Im really happy with what we've done so far.
[Nexus 6 Android Development] beepea206:
Wunderbar! Downloading newest now.
[Nexus 6 Android Development] SanJoseCA:
Is anyone missing sweep2sleep option in wake controls in synapse? I don't find that.
[Nexus 6 Android Development] :
I'm pretty sure I removed that.

Did you ever used it in this phone? Typically that's a rom side feature to swipe across the navbar.
[Nexus 6 Android Development] apophis9283:
I changed some hotplug stuff and made bricked the default hotplug. I chose bricked because even though I use Blu_plug in my experience bricked is the most solid. If you want to use another hotplug please make sure you uncheck bricked first. (When I release the next kernel)
[Nexus 6 Android Development] apophis9283:
Added FSYNC toggle back. As well as a few commits that im hoping help everyones CPU issues
[Nexus 6 Android Development] SanJoseCA:
I am on stock. I always used it after enabling it from Synapse.
[Nexus 6 Android Development] :
Easy enough to add back in. It just got removed from ukm, figured out was just wasted real estate.
[Nexus 6 Android Development] SanJoseCA:
Thanks.. :good:
[Nexus 6 Android Development] str8str:
Do you recommend flashing stock first before updating for ram disk or don't matter
[Nexus 6 Android Development] apophis9283:
Should be fine. Always have a backup. We will have another release sunday or monday.
[Nexus 6 Android Development] jcrompton:
[MENTION=4392154]apophis9283[/MENTION]

If you have a minute could you please send / post your current settings or are you still using the settings like you listed in the OPs? Even on the M builds?

Thank you guys for your work
[Nexus 6 Android Development] apophis9283:
Ive always got time for you guys

http://xdaforums.com/showpost.php?p=62671296&postcount=2
[Nexus 6 Android Development] str8str:
Got a random reboot when updating an app in play store and trying to open XDA app. Hope this helps. If you need last kernel log can you tell me how to get it ? https://www.dropbox.com/s/fbks2tlw4uuoq0j/2015-10-31_13.31.zip?dl=0
[Nexus 6 Android Development] apophis9283:
Was it a one time deal or is it repeating? What was the app? What ROM? Im not sure if it would be a kernel thing. So more info the better

Ive got my sons halloween tonight so i will peek at it when get a chance
[Nexus 6 Android Development] str8str:
All info is in the log I sent. I used syslog app which captures everything. Only happened once so far on cat rom,I was updating ie keyboard on play and we'nt to open xda app at same time. Don't know if was kernel just trying to figure it out.
[Nexus 6 Android Development] :
That logs a little weird to me.

there's definitely something strange with the thermal control trying to create duplicate entries (are you using intellithermal?).

But, your dmesg is only about 98 seconds long... and your other logs vary up to about 3 hours. Not really sure they all match up to each other.

Also, on a side note. It doesn't seem like the sound control drivers really work anymore. it's possible that they may for positive values, however they're broken for negative values. As most of this can be tuned through third part apps, I'm giving up on trying to rework them. Since they're broken, we're looking at just removing them.
[Nexus 6 Android Development] str8str:
Was probably a layers
[Nexus 6 Android Development] apophis9283:
Thats probably what caused it. Not a kernel issue. You updated a keyboard app then tried to open something that uses the keyboard relatively quick. I wouldnt worry about it
[Nexus 6 Android Development] jcrompton:
I sure hope nobody takes this wrongly and thinks that I am merely making an observation :

I had been running some of what listed in [MENTION=4392154]apophis9283[/MENTION] 's example post -- mainly the governor. I was using 98 min and 2803 max and I was using BluPlug hotplug..... I think I had maybe put the I/O scheduler read ahead to about 3000. Other than that I had not any of the many changes that you do (most of which I don't have a clue exactly what they do and I haven't experimented much).

The device felt snappy with my changes and still feels snappy with the [MENTION=4392154]apophis9283[/MENTION] settings ...

Here's the weird thing ... with an AnTu test I got about 54k with the minimal changes except the slight OC to 2803. With the full changes I just got a 46k AnTu. Is this because of the inherent deficiencies of a benchmark test like AnTu or is because the full changes still have good user experience but some changes that aid in battery life?

Just opening a discussions ... maybe others can share their full settings
[Nexus 6 Android Development] apophis9283:
Part will be the kernel, part will be the rom. We are still a long way off of where we want to be. By the time marshmallow has completely drowned out lollipop, we should be in good working order. We are not releasing every day either. Making sure stuff works and all around making it better. No offense taken