yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] franciscofranco:
Theres a big difference in how stock boosts cpu on touch and how I do it, but ultimately it comes down to this: stock leaves cpu on 1.5GHz for 3 full seconds, I leave it for 40ms, which is 0,04s.

If you want you can increase it to a higher value.
[Nexus 6  Original Android Development] xet:
Hello ...

Does anyone knows .. Whats the baytery difference between stock kernel 5.1 and franco r20?

I am usong currently stock kernel and i feel tha the battery drains quick .. Is there a noticable dofference with franco's kernel?

Thank youu
[Nexus 6  Original Android Development] wrongway213:
Mp-decision is disabled, so yes, of course battery is improved.
[Nexus 6  Original Android Development] GregNexus:
Thanks Franco!!! This should fix this problem i was wondering about since r6 or r7:D

How do i change this in fku?

And do you know how the touchboost works on the leankernel? Same as yours?

Because the leankernel is smooth as the stock kernel
[Nexus 6  Original Android Development] wrongway213:
To those of you on 5.1/r20, has there been any improvement/change to Google's stock DT2W implementation? I've never been able to reliably get Google's DT2W working on 5.0, only haptic offered by flar2 wake gestures. I'm wondering if this is one of the things that's been fixed in 5.1, as I know this kernel only offers stock Google implementation and not haptic. Anyone notice a change, or is haptic DT2W still the only way to get a reliable response?
[Nexus 6  Original Android Development] Didgeridoohan:
No matter how I scroll, there's no stutter... That's with FK r20 (default settings), stock 5.1 , unencrypted.
[Nexus 6  Original Android Development] v12xke:
I'm still running 5.02 (N6) so I can't speak to any improvement/change to Google's implemenation, but have you tried the Nexus 6 Doubletap to wake enabler?

http://xdaforums.com/nexus-6/themes-apps/doubletap-to-unlock-enabler-t2949218
[Nexus 6  Original Android Development] wrongway213:
This uses Google stock implementation just like Franco kernel, unfortunately. It's also actually redundant to be honest - this exact option is offered in FKU, no reason for anyone on Franco Kernel to use that app as it is offered in FKU. Appreciate taking the time to respond, just don't think you quite understand the question or even the difference between haptic and stock Google DT2W based on this response.

So to anyone on r20/5.1 - I'm just curious if DT2W actually works well in 5.1 or if it has been left only halfway functional like a lot of 5.0. I have not heard mention of it either way to indicate it has or has not been improved, but this is one of the few kernels that still uses the stock Google implementation exclusively instead of flar2's haptic implementation, so I figure this would be the place to ask. The question remains to any of you who are actually on 5.1/r20 - any improvement to Google's DT2W, or is it still totally unreliable?
[Nexus 6  Original Android Development] GregNexus:
Another question : currently i'm on 5.1 with Franco kernel and i am unencrypted. If i flash the stock kernel, will there be an encryption on the next Boot? Do i need an unencrypted stock kernel ( is one here on xda?)
[Nexus 6  Original Android Development] PhilDX:
I'm on 5.1 and still with the stock kernel, and I installed one of the available apps to enable stock DT2W. might be just me, but I think the responsiveness of stock DT2W is actually worse than on 5.0.1. I was using Lean Kernel on 5.0.1 (sorry Franco) which includes flar2's haptic D2TW, and that works much more consistently, probably in the high 80's to 90ish%.
[Nexus 6  Original Android Development] bikeryder007:
I can't answer your question on if google changed anything but dt2w is working for me every time on r20, activated in FKU. This stock ROM is the smoothest thing I have ever experienced on a phone. And for me r20 is just as smooth as the stock kernel as well. Great work Franco.
[Nexus 6  Original Android Development] enzoevo:
Scosler posted an unencrypted boot.img

Via my CleanROM Nexus 6
[Nexus 6  Original Android Development] LPT:
Not sure if I should ask this here. But is this common error in battery graph of Lollipop? Since the wifi is always on (even when I disable the "google always scan" option) :(. Btw, I got some msm_hsic_host wakelock with r20 and vanillapop rom[emoji14]
[Nexus 6  Original Android Development] szale9001:
I think Lean uses mpdecision, so it probably has the 3 second touch boost Franco was describing.

To change the boost in fku (paid only, I believe), go to CPU manager, and select Governor control. Then click on input_boost_duration and you can edit the value from there. If you want 3 seconds, enter 3000000 and it will boost for that duration. Personally, I think that's obscenely high. In your case I would try not to exceed 250000. That way you won't be hurting the battery life that much. But experiment with some values and see what feels good to you.
[Nexus 6  Original Android Development] p-slim:
I know battery was better on unencrypted devices on 5.01 but that I that was because of the performance issues on encrypted devices. Now that 5.1 has fixed most problems is battery still better on unencrypted or is it about the same?
[Nexus 6  Original Android Development] franciscofranco:
Governor control, input boost duration. 1000000 = 1 second.

LeanKernel uses MPDecision.
[Nexus 6  Original Android Development] stevessvt:
Nice.
[Nexus 6  Original Android Development] franciscofranco:
Double tap to wake code is unchanged and I'm pretty sure they won't change obsolete code.

But they made changes on the touch driver, not related to double tap to wake.
[Nexus 6  Original Android Development] schizophrenia:
honestly, anyone here think the battery life improved? or get worse?

mine looks like draining a lot faster than before. I am on r20 already.
[Nexus 6  Original Android Development] franciscofranco:
I think Wi-Fi is still borked, I had the exact same experience, again, where wifi is off, but shows as on. Pretty ****ed up if you ask me.

That wakelock is part of the radio, already explained 10000 times.
[Nexus 6  Original Android Development] LPT:
Thnks franco ;) just asked to make sure not only my phone got that problem [emoji14]. But I still cant believe even in 5.1, google still hasnt fixed that bug yet:(
[Nexus 6  Original Android Development] Snit91:
somebody noticed fast battery drain on 5.1 + r20?

the screen time is taking much more percentage than before.. (~5%/h)

plus, it seems that cores 3+4 are stuck on 300mhz+ and wont go offline.. (r20)
[Nexus 6  Original Android Development] enzoevo:
The cores won't go offline by design. That's not an issue.
[Nexus 6  Original Android Development] Snit91:
but on 5.0.1 they did go offline.. is that 5.1 "feature"?
[Nexus 6  Original Android Development] fahadali2315:
Yes that's what google introduced, after franco already found it [emoji14] keeping all cores on low power is better than keeping 2 cores online at higher.
[Nexus 6  Original Android Development] curtdragon:
Happened to me yesterday before I updated to 5.1 Phone was at about 20% and I was like why is the phone shutting down. Turn it on and it's at 25%
[Nexus 6  Original Android Development] Snit91:
thanks. what about the SOT? why am i getting high draining percentage? (now its 6~ pre hour!)
[Nexus 6  Original Android Development] fahadali2315:
You gotta give it 2-3 cycles to settle . In theory it should give better results.
[Nexus 6  Original Android Development] enzoevo:
Because Google has a lot of their bloat sucking down your battery. I saw a marked improvement in battery life on 5.01 when I switched to CleanRom( which is just stock minus Google bloat.) Be patient and let the devs figure out how to optimize 5.1. As for 4 cores always on, that's the way I ran Franco and ElementalX on 5.01. I had the same battery life, the device was more stable, and better performance than hotplugging cores. I think I read a post here by [MENTION=3292224]franciscofranco[/MENTION] stating this, and have been convinced since.
[Nexus 6  Original Android Development] Utini:
If I untick "voltage on boot" and reboot, will it reset the values in fku so that I can check the stock voltage values?

Thanks
[Nexus 6  Original Android Development] nexusmaniac:
Yes it will :)
[Nexus 6  Original Android Development] hlxanthus:
I can confirm this works on the verizon images on LMY47E . . not that I thought there would be any issue what so ever . .

Sent from my Nexus 6
[Nexus 6  Original Android Development] tmrma:
Everything fine with 5.1 and r20 (now)

But i have one problem. what is the reason that the max CPU in fku always set 1,7ghz or after new Installation or erasing cache and data never higher than 2,3ghz?
[Nexus 6  Original Android Development] nexusmaniac:
I think this same problem has been discussed previously :P

Pretty sure it's to do with the stock thermal code. (Someone can correct me if I'm wrong though haha :) )
[Nexus 6  Original Android Development] tmrma:
OK sorry, it works after another reboot. Max CPU now at 2,7ghz

---------- Post added at 06:04 PM ---------- Previous post was at 06:00 PM ----------

OK thank you. I thought that i had read something. But Didnt know the reason.
[Nexus 6  Original Android Development] franciscofranco:
Probably some current protection that Google/Motorola put there. We don't really know more about it.
[Nexus 6  Original Android Development] paychex:
can you pull the newer radio?
[Nexus 6  Original Android Development] stas333:
Has anyone noticed, disabling sensor_ind wake lock I'm the kernel settings prevents ambient display from working?
[Nexus 6  Original Android Development] franciscofranco:
I wouldn't be surprised if that happened, of course. I was under the impression sensor_ind bug is fixed on 5.1, so I doubt there's need to disable it anymore.
[Nexus 6  Original Android Development] iJekyll:
I must buy the pro version of the app to enable double tap to wake feature? Cause it doesn't seem to work after flashing the kernel.
[Nexus 6  Original Android Development] franciscofranco:
You can do it from your terminal, adb, whatever. App is just a graphical and easier way to do it. Double tap to wake is disabled by default just like stock.
[Nexus 6  Original Android Development] nexusmaniac:
Would also like this :)
[Nexus 6  Original Android Development] iJekyll:
Then how do I enable the double tap to wake feature by your kernel? what code should I write at the adb? I pretty much searched the thread but didn't find a straight answer for my case.
[Nexus 6  Original Android Development] franciscofranco:
I don't remember the path from the top of my head. Quick Google search should help you, the path is around the web.
[Nexus 6  Original Android Development] iJekyll:
You're right. Google is my friend :) http://www.androidpolice.com/2014/11/24/how-to-enable-double-tap-to-wake-on-your-rooted-nexus-6/

Thank you so much. Meanwhile I experience HUGE improvement with your kernel! thanks a lot! Gonna donate you a beer ;)
[Nexus 6  Original Android Development] stas333:
i was just used to turning it on r19 so i did it on r20 also.
[Nexus 6  Original Android Development] wrongway213:
Edit: I see I had not refreshed and there's another page, Franco beat me to it quite awhile ago
[Nexus 6  Original Android Development] hlxanthus:
Here you go . .

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

Sent from my Nexus 6
[Nexus 6  Original Android Development] Utini:
Thanks, and will I have to reboot during the changes of voltages?

Cause I thought .50mV was causing me troubles so I reduced it to -25mV and ran the Antutu stability test without any problems. Then I closed the app, went to FKU and changed to -50mV to run Antutu stabilty test again.. without any troubles :o
[Nexus 6  Original Android Development] Ladduro:
Hi, I am currently on 5.1 stock kernel unencrypted.

I don't want to insult anyone but for me battery life and feeling are really good. Much better than r19 on 5.0.1. You can see attached battery with light usage. I am not heavy user and for me stock 5.1 performance until now is excellent.

There for I was wondering if there are any real improvements on r20, not placebo. Don't get me wrong, I have paid for FKU app and I was happy with tweaks on 5.0, but now I don't see the benefit on using a custom kernel.
[Nexus 6  Original Android Development] nexusmaniac:
After you un-tick set on boot, you will need to reboot yes :)
[Nexus 6  Original Android Development] Utini:
Obviously, yes :P

But I meant, If I increase or decrease the voltage, do I need to reboot in between decreasing/increasing ?
[Nexus 6  Original Android Development] hlxanthus:
Double tap 2 wake, color control, vibration control, charging led . .

Sent from my Nexus 6
[Nexus 6  Original Android Development] reinert012:
Buy the app. It's one of the most beautiful apps out there place is supports Franky!
[Nexus 6  Original Android Development] nexusmaniac:
Ooooh! Sorry haha ^^ Now I get what you mean ;)

Nope, as soon as you set a voltage in FKU, it'll be applied straight away (No need to reboot :) )
[Nexus 6  Original Android Development] Utini:
Hmm weird.. i just did a stability test with -50mV as I thought it would cause random reboots on my phone but the test worked well. It looks like tge problem really is with the power-safe profile.
[Nexus 6  Original Android Development] stas333:
speaking if voltages. I had a question. This is my 2nd Nexus 6. The first one was at 700mv out of the box. The new one i have is 680mv. why is there a difference in mv between the 2 devices.?
[Nexus 6  Original Android Development] nexusmaniac:
Just a slightly better binned CPU :)
[Nexus 6  Original Android Development] laureanop:
OT.

Warning to people fastboot flashing images, sideloading ota , locking and unlocking bootloaders. The OEM UNLOCK option in developers DOES NOT SURVIVE reboots. It needs to be toggled on on every boot.

People have been borking their phones left and right the last couple of days!!!
[Nexus 6  Original Android Development] occtec:
The workaround is DON'T lock your bootloader after upgrading to 5.1 ;)
[Nexus 6  Original Android Development] SilkyJohnson:
Running beautifully on 5.1 stock. Thank you!
[Nexus 6  Original Android Development] laureanop:
Yeah that's correct. New threads and users on Google + keep popping up with hard bricked devices.

Just looking out for FK users
[Nexus 6  Original Android Development] franciscofranco:
Besides all the cool interfaces (color, vibration etc), and soon sound control interface, we're running a different governor with some of my custom code tuned specially for what I think its a better experience. And running a 0,04s touch boost vs 3 second touch boost on stock, which ultimately will lead to better battery.

There's also a ton of patches and fixes, I don't even wanna go there ;)
[Nexus 6  Original Android Development] wimmetje:
I just purchased the app, love all feature's especially the color control.

Love to see all the upcoming features:thumbup:
[Nexus 6  Original Android Development] manup456:
Anything on led or am I asking a stupid question?
[Nexus 6  Original Android Development] stas333:
A quick update, I switch to power saving profile and now I'm getting 20 minutes for every 5 percent usage just like I did before 5. 1
[Nexus 6  Original Android Development] franciscofranco:
Power saving bends the device to its knees, it should give you uber battery life, but...hello lag.
[Nexus 6  Original Android Development] franciscofranco:
What are you asking exactly?...
[Nexus 6  Original Android Development] manup456:
The led was blue until at 90% or better then turned green and when a notification came in it would turn a white/pinkish color now its only green and notifications don't turn led on at all.
[Nexus 6  Original Android Development] dxwilliams40:
Color control is definitely my favorite feature
[Nexus 6  Original Android Development] jvidia:
Is the r20 working fine over stock 5.1 ??

Parabéns pelo bom trabalho Franco ;)
[Nexus 6  Original Android Development] GregNexus:
Unencrypted Boot IMG is unencrypted stock kernel?
[Nexus 6  Original Android Development] franciscofranco:
No... The Kernel doesnt do that, you need an app to set that up.
[Nexus 6  Original Android Development] stas333:
Actually, I have 0 lag.
[Nexus 6  Original Android Development] manup456:
My question is on 5.0.1 and using your kernel to activate the feature that is how it worked and now its not working the same. Why is this not the case anymore? The kernel must play a part because the led only gets activated with a kernel edit.
[Nexus 6  Original Android Development] cobyman7035:
does r20 still work on stock 5.01 kernel...im too lazy to upgrade to 5.1 lolli
[Nexus 6  Original Android Development] wrongway213:
No, r19
[Nexus 6  Original Android Development] manup456:
r20 is only for 5.1
[Nexus 6  Original Android Development] grayskul:
Kernel is running great on Scott's Clean ROM!
[Nexus 6  Original Android Development] mystifiyer:
Like some others, I have micro stutters when scrolling, most noticeably when scrolling on image intensive or extremely wordy text app like gReader.

For anyone who experience the same, you can try increase the input boost duration from the current default 40000 to something higher.

Just a little something to share to all.
[Nexus 6  Original Android Development] grinchyyy:
This information is in the first 4 lines of the OP.

Good rule of thumb in all these forums is read the OP thoroughly.

Sent from my Nexus 6
[Nexus 6  Original Android Development] GregNexus:
Same Problem... Even if i increase the settings, the stutter is still there:/ stock is as smooth as possible here.. Has anyone another solution to raise the smoothness?:D

---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------

Is it just me, or is the battey more worse against 5.0.1?

I think i'm on my 2 oder 3 cycle after the factory image flash, maybe my device has to get some cycles more?
[Nexus 6  Original Android Development] eggydrums:
Seems you're not far off... The device is noticeably slower, but not by much. I'm gonna use it like this the whole day to see how far I go
[Nexus 6  Original Android Development] GregNexus:
I gave it a try, there isnt a real difference to the 40ms...stock is still way smoother

Is there maybe another function, that i could increase?

EDIT: Had to reboot the device, now it works, awesome. I had to set it to 1000000 (1 sec) Hope the battery impact is not that big against your 40 ms:)

I will look how much i can go down, without any impact on smoothness
[Nexus 6  Original Android Development] enzoevo:
Those with stuttering, you may be experiencing a crash that's writing to a log. I had the exact same behavior. The stutter was 30 MB file being written to the SD card. I don't remember what directory the file was written to, but it was definitely a core dump.

Just throwing ideas out. I haven't experienced any lag whatsoever running default r20.

Stock 5.1, only changes are frozen Google doc apps.

Via my CleanROM Nexus 6
[Nexus 6  Original Android Development] sirbanger:
Hey guys,

I see a lot of you saying that you are unencrypted with franco kernel. How did you achieve that?
[Nexus 6  Original Android Development] GregNexus:
It is the same way as you did this with 5.0:)

Flashing an unencrypted Boot. Img, make a factory reset with twrp, reboot, setup your device and flash the Franco kernel, the fk comes without forcing the encryption:)
[Nexus 6  Original Android Development] bikeryder007:
I did it in twrp. Once you are on a kernel that does not force encryption, you can format data and that will do it. It will also wipe your ENTIRE phone. I did it on purpose for a fresh start.
[Nexus 6  Original Android Development] GregNexus:
input_boost_duration is now set to 1000000, hope the battery impact isnt that big:)
[Nexus 6  Original Android Development] grayskul:
I used wugfresh's toolkit. All the necessary files have been updated!
[Nexus 6  Original Android Development] stas333:
I honestly don't notice any difference in performance. I have it set at 2.6ghz and only 2 cores work. I don't play games on my phone and it is decrypted, so maybe that's why it's not lagging
[Nexus 6  Original Android Development] franciscofranco:
Can anyone run input boost at max freq for a couple battery cycles? Curious to see if there's any impact on battery life. I doubt it since 40ms is really really small. Let me know.
[Nexus 6  Original Android Development] enzoevo:
Sorry if I'm being obtuse. What settings specifically would that be to achieve that?
[Nexus 6  Original Android Development] curtdragon:
Done, any other settings?

I have CPU gov on conservative

GPU on simple_ondemand

voltage -75MV throughout

---------- Post added at 10:51 AM ---------- Previous post was at 10:50 AM ----------

In his app under governor control
[Nexus 6  Original Android Development] franciscofranco:
Thats all there it. I'm curious to see if theres a battery hit in the long run. In theory I don't really think we'll see any extra drainage during usage, 40ms nothing.
[Nexus 6  Original Android Development] GregNexus:
Who has much better battery life with 5.1?

And who is noticing a way higher drain on 5.1 against 5.0? Or does Android need some cycles to get the better battery life after flashing an factory image?

Everywhere you a reading about the better battery life in the news, but i dont notice it...
[Nexus 6  Original Android Development] schizophrenia:
i noticed worse battery drains... now all the apps I use (e.g. G+) has a bigger battery usage than before (when i looked at the battery usage screen)...
[Nexus 6  Original Android Development] nexusmaniac:
I'm trying :)

Will report back if battery is Ok/Not Ok :P
[Nexus 6  Original Android Development] myepicyear:
I don't know if it's just me, but I've found that having Franco Kernel Updater app (paid) installed on my device with stock kernel causes cores 1, 2, and 3 to eventually get stuck at max frequency. I'm using the newest beta version of the app. Once I uninstalled, it went right back to normal.

Wiping the app settings doesn't even stop it--only removal. If your phone starts to feel hot, and you're using stock 5.1 kernel with FKU app installed, go and check System Monitor. You'll see 3 of 4 cores sticking at max frequency.

Just thought I'd put that out there, in case my suspicions are correct.
[Nexus 6  Original Android Development] stas333:
i had worse battery life with 5.1 initially. try out the battery saving profile but make sure to set the cpu to or above 2.2ghz. My phone is better then 5.0.1 now and still very very smooth.
[Nexus 6  Original Android Development] franciscofranco:
Everyone has a different usage. There are so many ****ing variances... You can't just judge based on others, your experience is all that matters.
[Nexus 6  Original Android Development] franciscofranco:
My app doesnt do any of that -.-
[Nexus 6  Original Android Development] myepicyear:
I'm probably crazy. :eek: lol
[Nexus 6  Original Android Development] GregNexus:
Yes, i know franco:)

My usage is the same as on 5.0 and there is an noticeable higher drain.

I was just asking if other people notice this too, depending on their same usage as on 5.0

I wasnt asking to compare their usage with mine, just if they notice the higher drain
[Nexus 6  Original Android Development] franciscofranco:
For my usage 5.1 is quite a bit better, but I think r21 will improve it a bit.
[Nexus 6  Original Android Development] Arunabh:
Lol!! The performance gain, with this, is immense. Everything's so smooth. But I've just been using it for like half an hour with those settings.

I'll report after a full cycle!

Also in governor settings up threshold is still at 98.

Even though all cores are online shouldn't that be at 0?
[Nexus 6  Original Android Development] TR2N:
Hi guys, hi Franco.

I noticed a bug(?) in r20 with stock 5.1 ROM. I have activated the charging LED feature and on r19 and versions before the LED shut off when the device was fully charged. Now the LED stays active until I pull out the charger. Is there a way to fix this?