yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] DespairFactor:
Yes, or install someone else's kernel for the version of android you want to use. Obviously stock is preferable.
[Nexus 6 Android Development] cruzzmz:
i usually use the stock kernel ...

to be clear i should do:

1. Enter recovery

2. fastboot flash boot boot.img (inside image-shamu.zip)

3. enter twrp

4. flash despair kernal & super su

right ???

thanks
[Nexus 6 Android Development] DespairFactor:
Except the first step is bootloader, not recovery
[Nexus 6 Android Development] cruzzmz:
ok my bad

bootloader mode :)
[Nexus 6 Android Development] andrewk36:
Is there a way to flash the latest despair kernel and supersu on the M Preview 2 without getting the device verification failed error?
[Nexus 6 Android Development] beepea206:
I had some odd lag and text format issues with zen(which made no sense at all), but this kernel seems to have resolved all that jazz. I've seen lots of reboots/issues with the zen scheduler.... Stay away from it or is it working on R20.6?
[Nexus 6 Android Development] DespairFactor:
It should be working, but if not use fiops or sioplus
[Nexus 6 Android Development] beepea206:
How do those two fair compared to bfq? I'm not overclocking and I'm using elementalX.

Btw, I thank you for all the governor and scheduler options you provide... I like options and that's really missing from all other kernels available.
[Nexus 6 Android Development] DespairFactor:
BFQ is more conservative, FIOPS/SIOPLUS are performance based(which works a lot better for me) I use despair and zen hotplug with a max freq of 1497.
[Nexus 6 Android Development] curtdragon:
I just did a clean install of Preview 2 and the 3.3 kernel but I can't get any app to mount system while it is running. I am able to get apps to work when in TWRP though. Is that normal? I can't get Busybox installed because of this
[Nexus 6 Android Development] cruzzmz:
I got a very odd error massage that something is corrupted and then my nexus 6 boots up ...

was a bit shaken ...
[Nexus 6 Android Development] DespairFactor:
Remember, my work is garbage
[Nexus 6 Android Development] micmars:
I certainly hope you're being somewhat facetious...your work is stellar, nothing less.
[Nexus 6 Android Development] DespairFactor:
I am hoping some people take it seriously and leave me alone:P
[Nexus 6 Android Development] MarceloSiciliano:
Hahahahahahaa you are awesome.
[Nexus 6 Android Development] beepea206:
*in Zoidberg voice* "your kernel is bad and you should feel bad." how's that? ;)
[Nexus 6 Android Development] DespairFactor:
I have a feeling my name scares people away from talking to me.
[Nexus 6 Android Development] cujo6801:
Yours is the only kernel I run....

My phone stays nice and cool

Sent from the "DOG" pound...
[Nexus 6 Android Development] curtdragon:
Not sure what the big deal is. Just pointing out a bug and wasn't sure if it was your kernel or the preview build
[Nexus 6 Android Development] DespairFactor:
This kernel sucks, it causes reboots, causes lag, causes your phone to get corrupted, sometimes it even makes you throw your phone. I have even seen it make dogs randomly reboot.
[Nexus 6 Android Development] micmars:
I've borne witness to all of this and more...
[Nexus 6 Android Development] curtdragon:
Awesome thanks!
[Nexus 6 Android Development] DespairFactor:
Yeah, it even made a guy jump into a body of water with alligators, needless to say...

He didn't survive
[Nexus 6 Android Development] the.emilio:
This kernel turned my phone in to a Moto Cliq
[Nexus 6 Android Development] pantmunu:
Been switching between this and hellscore and have been doing it for a while . never had anything to complain . and I still have not found anything to complain. For people having issues, please go for a clean wipe before reporting any issues. It helps most of the time. Try to get the logcat to help the dev help u back instead of just saying your phn started bit***g with u . lol. [MENTION=5169465]DespairFactor[/MENTION] I was using ur work on my one plus and now and nexus 6 for months. And as always amazing job Sir.
[Nexus 6 Android Development] hutzdani:
I'm running r3.3 here but can't for the life of me enable the charging led.

Everything else works sweet as normal :D

I guess google borked it good and proper with M.P2
[Nexus 6 Android Development] :
I always just delete the system/etc/init.d folder then flash new kernel I'm trying out. Been a crack flashing kernel flasher since preview 2 dropped. :sly: I stay on og preview because of the bugs on the 3rd party M roms.. Preview 2 runs great with this kernel. :)
[Nexus 6 Android Development] Thunderbolt69:
[MENTION=5169465]DespairFactor[/MENTION] ... In your CFS Kernel, I was wondering if you would ever consider adding the Simple GPU Algorithm to the GPU settings? Excellent kernel by the way.
[Nexus 6 Android Development] DespairFactor:
Nope, it will not be added to any of my kernels, we have adreno idler.
[Nexus 6 Android Development] Thunderbolt69:
OK, thanks.. Thought would check before continue using it.
[Nexus 6 Android Development] LunaticSerenade:
Out of curiosity, can I ask why?

In any event, this kernel is fantastic. Thank you for your work.
[Nexus 6 Android Development] DespairFactor:
Adreno idler and simple gpu use the same trust zone on the governor, they would conflict.
[Nexus 6 Android Development] Darian71:
ROTFL Over here in Missouri. BTW, I think I adopted that rebooting dog. And your name is one of last resort. Lol. You guys running the M2 preview, check [MENTION=344056]jdx[/MENTION] thread on his version and all your questions will be answered. I ran his ROM for a full week with Despair 3.3 with absolutely no issues. M will be nice once they get those bugs worked out. Downloading 20.7 now sir. Thanks for the early morning laughs. ?

http://xdaforums.com/showthread.php?t=3121053
[Nexus 6 Android Development] DespairFactor:
R20.8 is up:)
[Nexus 6 Android Development] Darian71:
R20.8 running smoothly. Gonna charge to full and try despair Governor for a couple days with Zen. Not exactly sure why yet, but Zen seems to work great for me. Knocks down 55,000+ everytime when combined with performance [MENTION=326942]272[/MENTION]6 MHz. Haven't figured out how to keep my device on at the 28xx MHz setting yet. That's with thermal controls off, but never seen Temps get above 120°F. Anyway, thanks for the heads up on the update. Let the testing begin! :D:sly:
[Nexus 6 Android Development] MarceloSiciliano:
Wow never above 120F?? Where do you live?
[Nexus 6 Android Development] DespairFactor:
Updating the CFS version now:)
[Nexus 6 Android Development] Darian71:
In the Boot heel of Missouri but I'm indoors. Lol. But I'm telling ya, with Despair kernel, My phone runs cool as a cucumber. I have been texting non stop for the past 15 minutes, on facebook and the Web with performance governor and the maximum allowed MHz setting just so I could Screenshot my Temps after I got the email you quoted my post.
[Nexus 6 Android Development] Darian71:
Awesome!
[Nexus 6 Android Development] DespairFactor:
The small amount of feedback on the new release can mean 2 things, either it's amazing or you all think it sucks and have moved on:)
[Nexus 6 Android Development] MarceloSiciliano:
Hahaha im still on 20.6
[Nexus 6 Android Development] quaman:
I'm running it with euphoria right now on a clean flash. I'm getting some significant drain but I'm going to give it some time to settle
[Nexus 6 Android Development] DespairFactor:
I've noticed the same, I am testing it still, I am not sure if it is the new Google stuff or not.
[Nexus 6 Android Development] LunaticSerenade:
I've gotten a lot of drain also. I briefly reflashed 20.6, and the battery was magically at 90% again.

I'm going to let it get down to about 5%, then charge, and see what happens.
[Nexus 6 Android Development] DespairFactor:
It could also be my crypto stuff I added
[Nexus 6 Android Development] Andromendous:
I did a fresh flash on croma, with the latest slim gapps, and everytime i reboot, it gets all the way to the lock screen and just reboots itself. Could it be slimgapps?
[Nexus 6 Android Development] DespairFactor:
Not sure, I am on chroma with slim zero gapps and my kernel

Anyone with battery drain, try R20.7 for now, I will be home in about 2 hours and will work on the issue.
[Nexus 6 Android Development] quaman:
I will drop down but the funniest thing happened. My phone was at about 27% battery I probably let it charge for 20 mins and it was already at 82. Lol I couldn't believe my eyes
[Nexus 6 Android Development] Andromendous:
I had this as well, restored my backup and gained 20%
[Nexus 6 Android Development] DespairFactor:
I think google's battery reporting commits are broken, I went back to R20.7(all my commits prior to Google's new stuff) and battery seems phenomenal
[Nexus 6 Android Development] KonoeKyon:
Well I'm on M preview 2 with 3.6 with no issues thus far, battery is the same for me as I've always gotten. Sitting at 51% left with 2 and half hours screen time and 17 hours 15 mins off the charger. Performance wise its slightly smoother but that could just be placebo.
[Nexus 6 Android Development] DespairFactor:
Perhaps these parameters only work properly with an M ROM. Maybe LP reads them differently, which causes issues.
[Nexus 6 Android Development] KonoeKyon:
I saw on some of the M threads about issues with battery reporting being off until after few cycles, maybe it just needs to recalibrate itself, battery did drain fast after flashing the update but I chocked it up to rebooting the phone multiple times but it's been fine since for me.
[Nexus 6 Android Development] DespairFactor:
I am not on M, but Google did update their kernel source last night, I have merged it to LP and we have seen significant drain due to some of the commits, I am going home to troubleshoot if it is just the commits for the power drivers.
[Nexus 6 Android Development] LunaticSerenade:
20.7 is killer.
[Nexus 6 Android Development] DespairFactor:
I am working on a new test build right now remotely without the power commits from Google.

EDIT: It is up now as R20.9

UPDATE: it is looking good so far
[Nexus 6 Android Development] info[]box1:
Apex_Predator™ #beastmode #shamu #DF-Kernel 20.8 !!!
[Nexus 6 Android Development] DespairFactor:
Use the 20.9;) 20.8 had battery reporting problems due to new commits from Android M
[Nexus 6 Android Development] info[]box1:
#again

Apex_Predator™ #beastmode #shamu #DF-Kernel !!!

Update your thread & OP buddy.. wtf :p
[Nexus 6 Android Development] adl:
Thanks guys, thought my phone was fudged... Flashed latest hells Kernel and hat weird drain problems, charged the phone and after 5 minutes it was back to 100% (from 35%!). Felt something is not right and flashed 20.8 DespairFactor kernel and draining continued. Now I was convinced I need to clean flash cause something was really clearly not eight anymore. Glad I came here to read that it's not my phone but Googles fault, will flash latest 20.9 build now.
[Nexus 6 Android Development] DespairFactor:
I literally just posted it[emoji14] I will update it when I get home
[Nexus 6 Android Development] Darian71:
I wasn't gonna report until morning on the battery drain as I'm running a nightly of Euphoria. Oddly enough though, I'm on my 2nd battery charge, (which by the way is amazingly fast when charging with 20.8 ) and I've noticed at around 50% this time she slowed down on consumption alot. But I also checked my play services and noticed it had checked my contacts 701 times over the past 5 hours so I enabled always ask before checking. It's asked me once since. Weird for sure. Thanks for the update but I think I'm gonna go one more charge cycle just to see what happens. :thumbup:
[Nexus 6 Android Development] quaman:
I don't know if you read the last few pages but 20.8 has some new Google code that's affecting battery but 20.9 is out and is a lot more stable without those mentioned commits
[Nexus 6 Android Development] DespairFactor:
it's not really affecting the actual battery life, just the reporting really.
[Nexus 6 Android Development] Darian71:
Yep. I did and thank you just the same. I just usually try and test a few things through a few battery cycles before switching. Plus I really like the lightening fast charge speeds I'm getting. Lol. Normally my charger has cooled off by the time I hit around 90%. On 20.8 that sucker is still cooling off at 99% and on to 100. Monitoring my battery Temps on charging and the darn thing never even exceeds 110°F. Insane because I've always been able to even feel my phone getting warm on charge especially as I'm using it but for some great reason I can't even get this version to run hot on max MHz setting running performance governor for hours. Kinda like it! Lol. :o:D
[Nexus 6 Android Development] Hen Ry:
Tonight in flight mode with R20.8
[Nexus 6 Android Development] Megaflop666:
I just want you to know Sir that you've ruined my phone... I get great battery, stays cool, runs smooth, and so much more! Wtf?! How dare you release this crap onto the nexus 6?!

...

...

Keep it up! ;)
[Nexus 6 Android Development] networkdood:
[MENTION=5169465]DespairFactor[/MENTION]

In your first post you write:

"Meet the machines the fuel my projects"

Do you mean:

"Meet the machines that fuel my projects"

Anyways, great job on the M Kernel as it is working its magic with xtraSmooth's M preview ROM...
[Nexus 6 Android Development] info[]box1:
Battery barely moved over night. Great job.

Edit: Thank you. OP. For all your help on and off xda. ;)
[Nexus 6 Android Development] networkdood:
http://xdaforums.com/showpost.php?p=60866792&postcount=3

I have been using the settings in that post, but was curious if anyone has tweaked it further for improvements.

I am using the conservative governor, min/max at 35/1497, no changes to voltage, using mako hotplug, default GPU settings, zen scheduler, and CDG congestion algorithm for a few days on the Dandvdh1_AOSP ROM and the device is running smoothly.

Anyone else using the same governor, I was curious what settings you preferred and why, especially with the GPU, hotplug and scheduler settings.

Thanks
[Nexus 6 Android Development] networkdood:
Only about 2 hours and 15 min of screen time, with little over a third of battery life left...odd thing is that the percentage stats showing battery usage add up to 90%, when added back into the battery percentage left.

But, phone is running cool and smooth with Despair...at least that is something to smile about...

Sent from....a phone
[Nexus 6 Android Development] DespairFactor:
not sure what your settings are, but this battery life sounds atrocious and something I wouldn't use.
[Nexus 6 Android Development] Darian71:
I still haven't flashed R20.9. 20.8 has leveled off and doing well today. I'll get 12 good hours of fairly constant use today. Biggest difference I've noticed is it is no longer "showing" to lose 10% per hour sleeping. I think I lost maybe 4% over 5 hours of sleep last night and never did get below 20% on my battery before I finally plugged it up before I left for the day. BTW, I timed it from 20% to 100% while using it at 42 minutes. Despair Governor seems pretty smooth today also. Had a couple small freeze ups exiting the Web and hanging up on a call or 2,but most likely due to the ROM. Again, great work sir. :thumbup:
[Nexus 6 Android Development] DespairFactor:
I just pushed a new M kernel too
[Nexus 6 Android Development] Darian71:
Dang it. Now I'm tempted to restore my M backup and try it out! Lol. I must admit, M Roms definitely beat all the 5.1.1 L Roms for battery life. My observation anyway.
[Nexus 6 Android Development] networkdood:
Well, looking at my battery stats, it seems my MLB AT BAT app uses battery without really being used and I even restricted its keep awake permission, so that could be one small issue, but in terms of use it is primarily CPU, although mobile radio active time was only for a few seconds.

Media server was somewhat busy, so I cleared its data and rebooted, just in case.

One bigger issue could be that the device does not shut off at 0% battery, but around 8%, and per the Google Product forums I went into the bootloader and cleared the logs as some people say this helps, but I am skeptical.

I notice that your kernel does not use the etc/init.d folder, is that correct?

I suspect the battery issue is more hardware, than software related as I have had similar SOT results on both M and Lollipop ROMs using different kernels.

I like your kernel for its options, as having options is always a good thing, IMO

Final solution is to enact the warrant replacement through T Mobile, but only after I go back to stock via flashing a stock zip or via adb, or by using WugFresh's rootkit.
[Nexus 6 Android Development] Megaflop666:
Dang it! 20.9 flashed with no issues and my phone is still running great. Why can't I get something to complain about?
[Nexus 6 Android Development] DespairFactor:
Dev has really slowed down on this device, I am going to try to update fq_pie possibly this weekend, I am not too sure how successful I will be because it has to be backported from Linux 4.1.1
[Nexus 6 Android Development] MarceloSiciliano:
How the new ROM is going?
[Nexus 6 Android Development] KonoeKyon:
Just updated to the 3.7 M kernel, I was at 50% when I updated, upon startup it had lost 10% battery, and has been fluctuating and draining rapidly for the following hour afterwords. It was at 16% and I rebooted it again and was at 26% on boot up. Right now I have it charging I'll report back if it continues to drain oddly after a full charge. Other than that thanks for the updates!
[Nexus 6 Android Development] DespairFactor:
It should work fine, there is apparently a freezing issue after recording, that I know how to fix, I am also going to look into what of the power commits was the issue on the earlier build and try to include all commits except problematic ones.
[Nexus 6 Android Development] KonoeKyon:
It was just odd is all, I had the same issue until after I cycle when I first went to M, then it was fine after. I'll be sticking with 3.7 until the next update so I'll report back if it's still happening. It was likely just a fluke after flashing the kernel. :)
[Nexus 6 Android Development] DespairFactor:
I have updated to 3.8 for M and 21 for LP.
[Nexus 6 Android Development] Hen Ry:
Which app allows the kernel to adapt best?
[Nexus 6 Android Development] moraytadroidz:
What is wrong with 21 why the quick update to 21.1 ?
[Nexus 6 Android Development] DespairFactor:
21.1 is the ubertc 5.2 test
[Nexus 6 Android Development] :
I use kernel auditor. Works great.
[Nexus 6 Android Development] Hen Ry:
what kind of a keyboard
[Nexus 6 Android Development] caballon:
Is F2FS m ready in this kernel, preview m2.Thank's in advance.
[Nexus 6 Android Development] Darian71:
Trying out R21.1 on Euphoria Rom 7/17 stable release and just now hit 99%! Not sure if it's accurate but will report back.
[Nexus 6 Android Development] jodvova:
Which device do you mean? Nexus 6?

Why has it slowed down?
[Nexus 6 Android Development] Darian71:
Getting stats now on R21.1. If my battery ever dies, I'll let ya know how it went. Lol. So far I've got an hour and a half of SOT, but am fully expecting 6 if this continues. Your the man [MENTION=5169465]DespairFactor[/MENTION]!
[Nexus 6 Android Development] quaman:
What are you kernel settings? Do you use ambient display or adaptive brightness?
[Nexus 6 Android Development] Darian71:
Ambient with Zen. Here are the rest. But keep in mind this is just the first battery cycle.
[Nexus 6 Android Development] DespairFactor:
Guys, I am rebasing the kernel because the new Google patches apparently conflicted with some of the stuff I already had, I will be removing problematic commits and a couple other features that I find are not beneficial.
[Nexus 6 Android Development] adl:
Nice! Trim that sucker down! [emoji41]
[Nexus 6 Android Development] DespairFactor:
I am about to build lollipop rebased build
[Nexus 6 Android Development] info[]box1:
Looking forward to it.
[Nexus 6 Android Development] DespairFactor:
It's up, next is M
[Nexus 6 Android Development] DespairFactor:
Alright, M and Lollipop are up.
[Nexus 6 Android Development] info[]box1:
Got it and flashed. Ty
[Nexus 6 Android Development] Andromendous:
Can i just dirty flash over 21.1?
[Nexus 6 Android Development] DespairFactor:
It should be fine
[Nexus 6 Android Development] Tylog:
Nice, thank you :)
[Nexus 6 Android Development] DespairFactor:
I am putting it through some testing to make sure the battery issues are gone
[Nexus 6 Android Development] Tylog:
Yes, let's see. It happens with the most kernel that use the latest source but I read you have check it with laurent (Hells) so let's see what's happen with the latest build.
[Nexus 6 Android Development] DespairFactor:
It does happen, but I'm not sure if it takes a few cycles to learn the battery
[Nexus 6 Android Development] ridobe:
Just flashed R4. Hope its as good as 3.8. FYI: R4 still reports 3.8 in about phone.
[Nexus 6 Android Development] DespairFactor:
That's weird, I'll have to look in a bit.
[Nexus 6 Android Development] pantmunu:
Checked from the link on op and all I can find is 20.8
[Nexus 6 Android Development] crimsonedge:
I posted in the wrong thread. Sorry.
[Nexus 6 Android Development] KonoeKyon:
Just curious if you cleared the boot loader logs? That seems to reset the battery stats, maybe charge it until it's completely full while turned off and clear the boot loader logs
[Nexus 6 Android Development] DespairFactor:
The issue is with leaving it off really, I can't really go without a phone for that long
[Nexus 6 Android Development] KonoeKyon:
True I haven't tried that myself, I did clear the boot loader logs though after flashing r4, will see how it goes tonight at work battery wise
[Nexus 6 Android Development] DespairFactor:
When you say bootloader logs, what are you referring to?
[Nexus 6 Android Development] networkdood:
On the product forums, Google told people with battery issues, specifically issues where the phone shuts off when the battery has a reading of 10%, or more, to clear the boot loader logs. I did that and removed the old battery stats file, let the battery drain completely, and then charged to 100%, while off, and my battery life had improved. Removing the old battery stats file is more of a placebo, though, but, I do it out of habit.

I use governor elementalx with min/Max 35/1497, all four cores active, under volt at a global value of -50, fiops scheduler, CDG congestion algorithm, no hotplug usage, and I finally surpassed the 5 hr SOT mark..first time for me with the N6, on a lollipop AOSP ROM.

Now, the options I use suck if I decide to play a few games and that is probably because the kernel/CPU/gpu have to work harder, and my device is under bolted, underfreq'd.

Anyone want to share what they use if they decide to do some heavy gaming? I figure the kernel aduitor app can be used to save multiple profiles...

Sent from....a phone

---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------

Option in fastboot mode is where I go for that...

Sent from....a phone
[Nexus 6 Android Development] KonoeKyon:
Reboot to boot loader it's the last option, you hold power button until it reboots from there to clear the logs. :good:

---------- Post added at 06:34 PM ---------- Previous post was at 06:25 PM ----------

My settings, I use conservative with touch boost set at 1 second, boost freq is 1.2GHz. Min freq 35 max 3033MHz. I don't undervolt at all and I have the voltages boosted on 2918 and above for stability. I run bfq with 1536 read ahead, and I still use cubic. The only other real 'tweak' I did was make a init.d script to disable the bcl driver on boot since it annoyed me lol. I don't game on my phone so I can't really comment on that much but I do average 5 hours SoT on my normal usage which is mostly texting, calling, XDA browsing and web browsing. If I don't have my camera on me then I do use the camera on the phone as well.
[Nexus 6 Android Development] info[]box1:
R23 is up for LP