yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] raptoro07:
Pretty sure it's just some code in the existing GPU governor that changes how it idles. same adreno Governor as it has been.
[Nexus 6 Android Development] stuff:
Cool, and this is implemented in the M kernel?
[Nexus 6 Android Development] fedef12evo:
i raised min cpu to 300 and no more freezes,lowering to 95 or 35 mhz result freezes when someone call me
[Nexus 6 Android Development] jodvova:
What app do you use to change it?
[Nexus 6 Android Development] fedef12evo:
kernel adiutor
[Nexus 6 Android Development] DespairFactor:
What?

It is just an algorithm for idling
[Nexus 6 Android Development] housry23:
I think he was saying that he almost has Moto X Rom booting on N6. I didn't quite get it either, but I read his post in the thread he linked to and I think that's what they're trying to do. Your kernel helped I think.
[Nexus 6 Android Development] Azlun:
yes, [MENTION=2043788]housry23[/MENTION] is right, I have use your Kernel here to boot up moto X Pro system.img, ON MY NEXUS6 devices,

but blocking now is on NFC Service stopped, looking forward you can help.

after that I also tried other 3rd paties Kernel, most of them bring such same result,

so I have posed the shamu_cn kerel sourcecode link and logcat -d log on that thread, tying to bring development forward.
[Nexus 6 Android Development] DespairFactor:
I need a personal contact via hangouts and stuff to look at support
[Nexus 6 Android Development] xonelith:
This might be intentional, but it seems the last few versions (C and D) have SELinux set to permissive. I might be doing something wrong too:)
[Nexus 6 Android Development] dany20mh:
[MENTION=5169465]DespairFactor[/MENTION]

What's new in R3, cause I can't find anything about it in github.
[Nexus 6 Android Development] DespairFactor:
It's all there now
[Nexus 6 Android Development] DespairFactor:
M kernel will be updated shortly.
[Nexus 6 Android Development] DespairFactor:
Its intentional, I am using the same source as M with a lollipop ramdisk.
[Nexus 6 Android Development] quaman:
Hey could you shed a little light on the despair CPU governor? Do you recommend it?
[Nexus 6 Android Development] DespairFactor:
I am still working on it:) It is a tweaked conservative governor with a couple extra values exposed, it tends to be a bit more conservative with battery than the conservative governor by default. I am currently trying to find the best values.
[Nexus 6 Android Development] DespairFactor:
Okay guys, I am compiling the M kernel and Lollipop updates now.
[Nexus 6 Android Development] billydroid:
So is NFC the only thing not working? That is pretty great! Please share if you feel you have something good.

Sorry for the off topic stuff. This is cool news.
[Nexus 6 Android Development] jodvova:
Is it 3.1 that you compiled? Or 3.2 is coming?
[Nexus 6 Android Development] DespairFactor:
3.1
[Nexus 6 Android Development] Tylog:
19H is very good. Good performance, very good battery for me. Well done.
[Nexus 6 Android Development] KonoeKyon:
I'm having an issue on this kernel when using the camera to record video. After starting to record it unplugged 2 cores and maxed out CPU usage on the remaining 2 cores at 1.9GHz causing the recording to be jittery and laggy. I've tried everything from changing hotplug options, CPU governors, io schedulers and tried under clocking also. I tried kernels 19A to 19H and it happens on all of them, it doesn't happen on stock kernel and it didn't happen on lean kernel 2.9ocuc or vindicator 2.5t4ak. I noticed it will do the same thing when downloading large files (such as a factory image). I attached a logcat from during a quick video recording when it unplugged the 2 cores. Thanks for any help you may offer, the kernel has been flawless for me otherwise.
[Nexus 6 Android Development] raptoro07:
Try mako hotplug or another hotplug option.
[Nexus 6 Android Development] DespairFactor:
Are you sure you've configured everything the same across those kernels? A logcat doesn't tell me anything about the scheduling or anything worthwhile, I would need dmesg
[Nexus 6 Android Development] KonoeKyon:
Ah ok sorry about that wasn't sure what type of log would be useful. Anyway here's a dmesg using the kernel defaults. I tried many configurations to try and eliminate the issue including trying to copy the configuration of lean kernel and I tried the same configuration on vindicator also without the issue. Thanks for the reply. Also, not sure if it matters but my phone battery is bellow 40% during that dmesg so the CPU clock is set for 2.2GHz. The issue does happen when at full charge also. If a dmesg from full charge would be useful let me know and I'll grab one as soon as I can charge my phone after work.
[Nexus 6 Android Development] DespairFactor:
This is what I see

bcl_handle_hotplug turning off cores, bcl=battery current limit, did you manage to get a charge and try again?
[Nexus 6 Android Development] DespairFactor:
I released R19.I of despair kernel with zzmoove, I want someone to test it currently, just to see how it works and if they see any issues. You will need to refer here for setup info: http://xdaforums.com/show...87&postcount=3
[Nexus 6 Android Development] Tylog:
I give it a try. I used zzmoove sometimes in the past and always get good results.
[Nexus 6 Android Development] KonoeKyon:
Sorry I wasn't able to get back to you quickly, I did a couple more tests, and looked in the logs, if it's over 90% it seems OK but under 90% it will do the 2 core thing and lag. The logs show the same bcl_handle_hotplug, is there any way to prevent it from happening? Again tested with the kernel defaults, here's a log from just now at work. No access to a charger at work and I'm working 12 hour swing shifts so I don't have much time to test unfortunately. I am try any suggestions you may have though over the week. Thanks again for the help :)
[Nexus 6 Android Development] raptoro07:
You can go and turn on msm_hotplug and set min cores on to 4 and then the cores won't shut off. Like this.View attachment 3372475
[Nexus 6 Android Development] KonoeKyon:
Thanks for the suggestion but I've already tried the different hotplug options whole trying to figure out out and it still ended up happening unfortunately
[Nexus 6 Android Development] cabagekiller:
Trying to find 3.1 on the download link. It's only showing 3 for me. :/ maybe I'm missing it?
[Nexus 6 Android Development] dany20mh:
Direct link:

http://renderserver.net/devs/DespairFactor/shamu/kernels/M/Despair.M.Shamu.R3.1.zip
[Nexus 6 Android Development] cabagekiller:
Thank you. I appreciate it.
[Nexus 6 Android Development] gmack523:
I'm receiving a message when I reboot my Nexus 6 (with Android M and 3.1 of your kernel). The message says, "Your device has failed verification and may not work properly". After about 5 seconds, my phone boots normally though. What can I do to get rid of that warning message? I've tried reflashing TWRP and even the kernel itself but am still receiving the same message.

Any assistance is greatly appreciated. Thank you in advance!
[Nexus 6 Android Development] DespairFactor:
That's not an issue really
[Nexus 6 Android Development] DespairFactor:
This log looks like it is turning the cores on and off as it has tasks queued on them. I don't really see an issue in this log. Does it do this on older versions too?
[Nexus 6 Android Development] KonoeKyon:
I've tried 19.A to 19.I, I can download some older versions today during my breaks to try though.
[Nexus 6 Android Development] DespairFactor:
Look at March 23, you can blame Google

https://github.com/android/kernel_msm/commits/android-msm-shamu-3.10-m-preview?page=3

I can try to change the thresholds, but I would need you to contact me directly to test as this won't be a release I can publicly supply due to the experimental voltage limits I would have to use
[Nexus 6 Android Development] KonoeKyon:
Interesting so it drops course if the CPU requires too much voltage compared to what is available? I'm wondering if there is a way to modify that threshold value somewhere. Thanks for the help! Greatly appreciated, at least I know why it's doing it now. :)
[Nexus 6 Android Development] DespairFactor:
It looks like that is the issue, I mean I could raise it to the old thresholds for testing purposes, but I don't want everyone to be using that build in case it causes issues for some phones. It would need to be thoroughly tested.
[Nexus 6 Android Development] KonoeKyon:
Ah, so there is no way to modify the threshold value without compiling a new kernel? I was hoping it was something like the frequencies throttling to 2.2 and 1.7 Ghz at certain battery levels, which could be adjusted by modifying the thermal conf file. Is it possible to make it a user configurable value?
[Nexus 6 Android Development] DespairFactor:
It may be possible, but I am unsure if it should really be done at that level, we will need to hardcode it for now if we want to see if it will even fix the issue.
[Nexus 6 Android Development] KonoeKyon:
Well I'm willing to try testing it if you're interested, I'll be limited in time due to work today but I can do some stuff during breaks and possibly over the week as well. The commit mentions it being changeable through sysfs, not sure how to do that though.
[Nexus 6 Android Development] DespairFactor:
I couldn't find the tunable, hangouts message me and I will message you when I have something ready to test, I can have something done today for sure.
[Nexus 6 Android Development] ProRules:
Hello, first of all I really like this kernel and its features!

Especially FBS scheduler and zen io scheduler.

Anyways I have a problem.

My previous setup was aosip ROM and elemental kernel.

I scored 53k on antutu and games worked nice but my n6 was getting hot real fast.

Right now I'm using aosip ROM and your despair kernel.

Zen io scheduler.

Bfs variation.

1536 redhead buffer.

GPU governor performance/original andreno.

CPU governor interactive.

I'm scoring only 47-48 k at max. Also games lag more compared to elementalx kernel.

Thanks ahead!
[Nexus 6 Android Development] info[]box1:
DF, Is R19.I a test kernel or stable?
[Nexus 6 Android Development] DespairFactor:
Its both in a way. I'm trying to get feedback on zzmoove
[Nexus 6 Android Development] info[]box1:
What's the attributes zmoove..? Adjusting the Gov now..

Edit: OP answered my question, excuse the waste of bandwidth.. xD
[Nexus 6 Android Development] KonoeKyon:
The log you requested
[Nexus 6 Android Development] DespairFactor:
What profile are you using?
[Nexus 6 Android Development] KonoeKyon:
Log from latest test
[Nexus 6 Android Development] joeyddr:
Had a reboot running antutu, checked /proc but there is no last_kmsg.
[Nexus 6 Android Development] papikev:
You can always run "cat /proc/last_kmsg > /sdcard/last_kmsg" in terminal and see of it gives you some viable output. No quotes on the command. Post it.

---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------

Sorry, .txt at the end of kmesg. Save as text and post it.
[Nexus 6 Android Development] joeyddr:
yeah the file is not there... no such file
[Nexus 6 Android Development] papikev:
Maybe it was just a watchdog reboot.
[Nexus 6 Android Development] DespairFactor:
The fact that is happened during antutu doesn't clarify anything, this can be an app problem, voltage problem, lock up. If you have no way to provide a log there is no way to troubleshoot.

With that being said, antutu benchmarks are useless, benchmarking a device definitely does not reflect real world performance.
[Nexus 6 Android Development] ggrant3876:
A little off topic, but does anyone have the Sensei 58 zip?
[Nexus 6 Android Development] spd2230:
https://www.dropbox.com/s/sesfb40s01m8itg/SENSEI.R58.zip?dl=0
[Nexus 6 Android Development] schmolch:
Rebooted while using the kindle app. No kmsg.
[Nexus 6 Android Development] DespairFactor:
Check pstore next time, kmsg is notorious for being missing it seems. On this note, I am testing blu plug and new recommended kernel app is kernel adiutor(it's free too)
[Nexus 6 Android Development] pantmunu:
Blu plug is awesome and the app is so freaking cool. :)
[Nexus 6 Android Development] DespairFactor:
I was very weary about that app until the newest release:)
[Nexus 6 Android Development] pantmunu:
2 updates before it was acting kinda weird but this latest update seems to pretty stable . looks nice too.
[Nexus 6 Android Development] DespairFactor:
With that being said, I just uploaded R7 with blu plug and blu active
[Nexus 6 Android Development] pantmunu:
Wohoo. U too fast sir !!
[Nexus 6 Android Development] DespairFactor:
Enjoy it, I am going to work on heavily tweaking blu plug and blu active to my likings, I will share my settings afterwards
[Nexus 6 Android Development] DespairFactor:
Guys, I am trying bioshock governor with blu plug, seems to scale decently, we will see how it goes.
[Nexus 6 Android Development] pantmunu:
Kept rebooting on purity ROM. And can't get any logs ATM. Boots all the way up to start screen . hangs for a sec and reboots.
[Nexus 6 Android Development] DespairFactor:
Did you have another kernel before it? Try clean flashing everything(make a nandroid first)
[Nexus 6 Android Development] pantmunu:
Yeah was running code blue. I think that's the issue . gotta head to work. Night shifts are kinda crazy. Will flash clean when I get back home.
[Nexus 6 Android Development] DespairFactor:
Sounds good!

Or try flashing your current rom then the kernel
[Nexus 6 Android Development] KonoeKyon:
And with thermal turned off ( using kernel adiutor)
[Nexus 6 Android Development] KonoeKyon:
And still doing it on the highly experimental build lol
[Nexus 6 Android Development] DespairFactor:
Guys please do not download anything past R20, R20.1 is a voltage testing right now, I will give the go ahead when it is safe
[Nexus 6 Android Development] KonoeKyon:
Log from mystery build
[Nexus 6 Android Development] KonoeKyon:
And over 50% battery
[Nexus 6 Android Development] yashau:
Can't wait to try out zzmoove on M. Currently on your Despair governor with good results so far. Max clock is at 1728MHz min is at 35MHz.
[Nexus 6 Android Development] DespairFactor:
I'm building it now:)
[Nexus 6 Android Development] DespairFactor:
Guys, I have put up BFS Lollipop R20.1, CFS lollipop R20.1 and BFS R3.2 Android M builds.
[Nexus 6 Android Development] RoboJoe:
Do we consider this the go-ahead that they're safe?
[Nexus 6 Android Development] DespairFactor:
Yeah should he good to go
[Nexus 6 Android Development] Blaiser47:
Delete wrong thread
[Nexus 6 Android Development] jimpsar:
Hello

Was using. 3.2 in M preview and was very satisfied.

In euphoria 5.1.1 can we use it also ?

Thank you dev
[Nexus 6 Android Development] DespairFactor:
You will need to use R20.1
[Nexus 6 Android Development] DespairFactor:
Has anyone done a comparison between CFS and BFS on their devices yet? At this moment they seem pretty close for me.
[Nexus 6 Android Development] KonoeKyon:
I tried it a bit, not extensively though. Most things feel similar though BFS feels more fluid/responsive for some things such as clearing all recents and scrolling in Google calendar.
[Nexus 6 Android Development] raptoro07:
It seems cfs is sleeping better for me than the bfs. It could be placebo. Once I hotplugged all for cores on, stuttering on either goes away.
[Nexus 6 Android Development] idiotzach15:
ViperAudio

Has anyone found particularly good settings kernel for listening to music using Viper4Android? zzmove seems to heat up the cores too much for me on profiles 4, 5 and 9. I'm currently testing other governors, but I was just wondering if anyone else had already done this
[Nexus 6 Android Development] vincentfarran:
Just updated from R18.F to R20.2. I have to say I've arrived in heaven! So fast and smooth, it's absolutely wonderful! Feels like the phone had a hardware upgrade! I want to buy U beer!
[Nexus 6 Android Development] DespairFactor:
I use profile 2, I don't listen to music on my phone though.
[Nexus 6 Android Development] LunaticSerenade:
Sweep2Sleep isn't working for me. Otherwise great!
[Nexus 6 Android Development] Tylog:
I think cfs had a little bit better battery for me. Can't say how huge the difference is but looks a little better.
[Nexus 6 Android Development] idiotzach15:
Hm, I'll give it a shot. I just found out that the ROM I had was responsible for the heating. But Viper4Android is still pretty taxing on the CPU.
[Nexus 6 Android Development] yashau:
Battery life is insane for me on profile 5. Thanks for the sweet kernel. Using Mako hotplug btw.
[Nexus 6 Android Development] idiotzach15:
What ROM are you using?
[Nexus 6 Android Development] DespairFactor:
What were your settings? If we really see a difference I will make a second M kernel with CFS
[Nexus 6 Android Development] Tylog:
CPU Max 1958 and conservative with two Changes, nothing more changed. It's hard to say how much difference, I flash to much to give a answer but I always have the feeling battery is better.

I will make two tests for full circle in the next days with both, then I can say more in detail.

Edit. I forget / Mako Hotplug and zen, I test atm what's better for me. And cfs powersave.

Give me a few days and I let you know which one is better for me at the end.
[Nexus 6 Android Development] aSquard:
I'm back to using Vomer's M build and when flashing 3.2 for M and SU 2.49 beta, my device won't boot.

I get the weird message about not passing validation, it says it'll restart in 5 seconds and it pretty much powers off at that point. Anything I can do to get this rooted again?
[Nexus 6 Android Development] DespairFactor:
weird, try an earlier kernel build.
[Nexus 6 Android Development] aSquard:
3 boots, skipped to 3.2 and we're all good now! Thanks!!
[Nexus 6 Android Development] Tylog:
After three days of testing, it's hard to name a significant difference. Ultimately, I would say that CFS and Bfs are relatively equal. Cheers.
[Nexus 6 Android Development] phia:
Not to sound like a noob but I'm a little confused as to which is the latest kernel for that M preview stock.
[Nexus 6 Android Development] Tylog:
http://renderserver.net/devs/DespairFactor/shamu/kernels/M/

3.2
[Nexus 6 Android Development] MandoH:
Couldn't get R20.3. To boot past Google screen.. :confused:
[Nexus 6 Android Development] quaman:
He needs a little more info than that. Did you wipe caches or try a clean install? I'm running that kernel on euphoria right now
[Nexus 6 Android Development] DespairFactor:
I am using it on optipop, used it on broken a couple days ago.
[Nexus 6 Android Development] xonelith:
Using it on minimal, broken and Tesla with no issues.
[Nexus 6 Android Development] 31ken31:
My 6 will be in on Friday. First kernel im flashing
[Nexus 6 Android Development] info[]box1:
I booted just fine on 2 different cm12 based ROMs.
[Nexus 6 Android Development] cujo6801:
R20.4 on Tesla ROM from Ground Zero Rom's runs sooooooo

Good...

Thanks

Sent from the "DOG" pound...
[Nexus 6 Android Development] Custodian:
Where can one find this ROM? Link please to the latest.
[Nexus 6 Android Development] cujo6801:
https://plus.google.com/communities/109330559573276360638

O and its from ground zero roms

Sent from the "DOG" pound...
[Nexus 6 Android Development] DespairFactor:
R20.5 is up now, I have added a brand new congestion control and updated the CAKE packet scheduler.
[Nexus 6 Android Development] cujo6801:
Thanks bro...

Love your kernel....

Sent from the "DOG" pound...
[Nexus 6 Android Development] DespairFactor:
I forgot to say what the new congestion avoidance algorithm is called, it is CDG (CAIA-Delay Gradient).

Refer to OP for details.
[Nexus 6 Android Development] cujo6801:
Just switch from Westwood to CDG.

I'll give it a go and see how she does

Sent from the "DOG" pound...
[Nexus 6 Android Development] networkdood:
Using this kernel on the latest JDX M ROM, and this sucker is fast.

I have Kernel Adiutor. Any recommended changes, or are the defaults awesome enough?

My sincere thanks to the OP. :)
[Nexus 6 Android Development] LunaticSerenade:
The sleep time on 20.5 is insane. Excellent work.
[Nexus 6 Android Development] adl:
The Dev postet here his personal settings, maybe try these (not sure if they are up to date) :

http://xdaforums.com/showpost.php?p=60866792&postcount=3
[Nexus 6 Android Development] networkdood:
Cool, and thanks.

Next thing:

Look at this photo and tell me, is my battery being underused?

View attachment 3394902

I ask because it was taking at around 20% battery left, and the numbers seem odd.

Sent from ....me
[Nexus 6 Android Development] DespairFactor:
Android M is weird with battery life, I was using it and noticed that lollipop boated an extra hour of screen on time for me. I will update the M kernel to include all the new stuff from the lollipop kernel today.
[Nexus 6 Android Development] DespairFactor:
I just updated the M kernel.
[Nexus 6 Android Development] networkdood:
Already on it. Same miscellaneous battery stat shows up, and to me it is saying that a portion of the battery is not being utilized. I even did a factory reset and a full wipe, then installed latest JDX and Despair...but, phone is running great, and that is most important above all else.

Sent....from me
[Nexus 6 Android Development] DespairFactor:
This is an android ROM issue, its likely something in the system image google released
[Nexus 6 Android Development] DespairFactor:
I just released a new build with tons of bcmdhd(wifi driver) updates for lollipop, I will release the M update in a few hours and bring the CFS for Lollipop inline with the BFS build.
[Nexus 6 Android Development] quaman:
I have no idea what that means but I flashed and everything is running fast and smooth with euphoria
[Nexus 6 Android Development] DespairFactor:
Basically the wifi drivers for the phone have been updated:P
[Nexus 6 Android Development] networkdood:
DespairFactor, can you tell me the main difference between your M kernel and the ElementalX M kernel?

Thanks!

Sent...from me
[Nexus 6 Android Development] DespairFactor:
He tends to keep his kernels more simple, I tend to go very complex with mine, I like to include tons of options and stuff that is meant for advanced users as well. A huge thing I do that others don't(that I have seen) is packet scheduler and congestion avoidance algorithm backports. I also forward port some governors that other's don't use.

Another thing I do is included several hotplug options that are patched to be disabled and enabled.
[Nexus 6 Android Development] cujo6801:
Thanks as always bro...

Love your work...

Sent from the "DOG" pound...
[Nexus 6 Android Development] DespairFactor:
If you have questions about a feature feel free to ask here or hangouts message me
[Nexus 6 Android Development] gdonanthony:
hhhhmmmm intelliplug is fixed by aosip kernel devs..
[Nexus 6 Android Development] gdonanthony:
remember we try to use intelliplug but the settings cant be change? aosip kernel uses intelliplug now so i think they fix everything about that hotplug.. and maybe if you like to include it for the advanced users
[Nexus 6 Android Development] DespairFactor:
They didn't fix it, they just pulled the commits, its BFS that causes it to act weird. I have it in my CFS kernels.
[Nexus 6 Android Development] jodvova:
3.3 doesn't seem to work on Preview 2.

Or is it only me ?
[Nexus 6 Android Development] DespairFactor:
Only you
[Nexus 6 Android Development] jodvova:
Right. It works now.

Do I need to flash SuperSu beta 2.49 with kernel or no ?

---------- Post added at 06:40 ---------- Previous post was at 06:31 ----------

For some reason when I updated to Preview 2 by just flashing system image, 3.3 kernel and supersu 2.49, the phone didn't boot.

I then flashed bootloader/boot/cache/system again, then 3.3 kernel and supersu 2.49 and it boots fine now.
[Nexus 6 Android Development] DespairFactor:
You need to flash a boot.img before my kernel always, I don't ship a full boot.img, that's probably why it didn't boot. Sorry, for not specifying.
[Nexus 6 Android Development] jodvova:
Got it, thanks for clarifying!
[Nexus 6 Android Development] :
3.3 running beautifully on Preview 2. Tks! :D
[Nexus 6 Android Development] cruzzmz:
so i need to fastboot flash boot.img first

then install kernel and supersu via twrp??