yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] zephiK:
Yes it will cause issues, all you'll have to do is remove the file. I don't remember the file on the top of my head but it's something relating to thermal.

With some searching, you'll find it in previous Franco threads for other devices.
[Nexus 6  Original Android Development] wrongway213:
Unless you plan to stay stock (no root, no roms, etc) you'll have issues with updates... gotta learn to flash factory imamges or to force factory images with Wug's Nexus Toolkit.. disregard if you plan to stay totally stock and just run Franco Kernel
[Nexus 6  Original Android Development] digweed4me:
Amazing battery life on power saving profile as good as my one plus one and the same time its so snappy well done Franco
[Nexus 6  Original Android Development] uhguy:
I'm rooted and all that jazz, but no custom rom right now. I flashed everything to update to 5.0.1. While this is my first Nexus device it isn't my first time with Android or root so I'm familiar with flashing images and roms.
[Nexus 6  Original Android Development] Krunk83:
I see most people haven't changed in the Franco thread. Adios.

nexus 6
[Nexus 6  Original Android Development] stas333:
Tryin out my first kernel on my first nexus phone :D

so far the battery saving profile is super smooth
[Nexus 6  Original Android Development] franciscofranco:
Hmm... I didn't change the thermal driver, but I can include my simple solution coming next release. Stock msm_thermal is a cluster****.

They can work together.

I'll try to reproduce, thanks.

Maybe thermal throttling. Tried increasing the throttle threshold?

Yeah, I've noticed. I'll fix it coming next release.

System files are unchanged.

I dunno, that subsystem is 100% stock, I haven't changed a thing.

Any numbers for before/after applying those patches?

Sure, sometime.

You've given root permissions to FKU?

Thanks for clearing that up for the rest of the users!!
[Nexus 6  Original Android Development] paychex:
It's the game not being optimized for the dpi
[Nexus 6  Original Android Development] elijahah:
Min Freq

Anyone else having trouble having the min frequency stick? I'll set the min to 300mhz, close the app and reopen and it gets reset to a random frequency about 900mhz.
[Nexus 6  Original Android Development] zephiK:
CPU Boost is changing the minimum frequency. The minimum frequency will revert back to 300 MHz.
[Nexus 6  Original Android Development] DizzyThermal:
Thanks!

Just wanted to say thanks for the kernel, I will post battery results and overall first impressions with nightly-r1

Keep it friendly guys! ;)
[Nexus 6  Original Android Development] Circaflex:
Im not sure if those are the same as what Faux implemented here, https://lh3.googleusercontent.com/-.../AAAAAAAAG08/ifNKkursL9s/w683-h1214-no/14+-+1
[Nexus 6  Original Android Development] wrongway213:
Same issue

Mine actually removed 300mhz from my BetterBatteryStats and all, lowest showing was 1.19 ghz. Is that a bug in BBS or do I need to change my CPU Boost settings? Obviously a noob with kernels
[Nexus 6  Original Android Development] stas333:
Is it normal for max freq not to stick after a reboot in the power saving mode? I had to increase the max freq from 1 to 1.5 because i was seeing a little lag. I enabled set on boot. after a reboot, the box is still marked but the max freq is back at 1.
[Nexus 6  Original Android Development] cobyman7035:
New fku app… does backup work? I saved a backup… when I go back.. Its empty screen again?

Says u dont have any backups yet

I'm using vomer dual tweak.. Bug ??

Via my NeXus™ 6 on Tapatalk⁴
[Nexus 6  Original Android Development] SweetwaterBurns:
Yeah, uninstall and reboot so that it loads the kernel defaults. Make sure you don't have any other kernel control apps installed. I tried trickstermod and anytime it makes changes, core 3 and 4 get stuck at 2.6 for some reason.
[Nexus 6  Original Android Development] Krunk83:
Just uninstalled the app, rebooted and it happened right away. Stutter still there.

nexus 6
[Nexus 6  Original Android Development] SweetwaterBurns:
And it's not thermally throttling? Not sure what else it might be as franco is a big improvement over Stock as far as smoothness.
[Nexus 6  Original Android Development] Krunk83:
I am not really much of an expert one kernels, not going to lie. I always leave the kernels on stock settings because I believe the dev knows best. I've only been tinkering to try and solve this issue I am having. My experience with franco kernels have always been good. What should I be changing the thermal throttle to that may improve my experience?
[Nexus 6  Original Android Development] vomer:
ignore it.
[Nexus 6  Original Android Development] rignfool:
Have you tried using performance governor?

If that doesn't change it... Nothing will...

Sent from my Nexus 6
[Nexus 6  Original Android Development] SweetwaterBurns:
If I remember right, franco has it at around 70C, which seems about right. If your phone seems sluggish after gaming or charging(especially with the new quick charger, it heats up my phone noticeably) but not after its been sitting a while, it's probably a thermal issue. The system monitor included with fku has a nice graph that you can check to see if and when it is getting hot. Or you can buy it separately and use the floating windows to monitor it in real time. I would check that out or look for rogue apps running in the background. Not sure what else you could check, honestly.
[Nexus 6  Original Android Development] michmeister:
Kernel is great, but colors do not stick on boot. Have to reapply every reboot.
[Nexus 6  Original Android Development] wrongway213:
Set them to set on boot and then go into your SuperSu app, go into settings and tick "enable SU during boot". It fixed a lot of my "not sticking on boot" issues, might help for colors as well.
[Nexus 6  Original Android Development] SilkyJohnson:
They stick just fine here using Franco's app.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Krunk83:
I don't really game. I'll try performance again but I've tried that and it still seems to stutter. Like I said, stock is completely smooth.

Nexus 6

---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------

When I change my input_boost_freq this happens when I go back to check. Is this normal?

Nexus 6
[Nexus 6  Original Android Development] trickster2369:
franciscofranco, I am thoroughly enjoying your kernel on the N6. Was just wondering, however, if you had any plans to update the kernel for the N10 to Lollipop. Thanks for the work you've put in to this device.

Sent from my Nexus 10
[Nexus 6  Original Android Development] abnormalreply:
Disabling double tap to wake doesn't stick. Don't even have to reboot for it to go back to enabled. It just auto-enables after the screen is turned off. Replacing power.shamu.so with the one linked below helped.
[Nexus 6  Original Android Development] wrongway213:
I think it sticks, you just have to enable it, tick set on boot, open SuperSU, settings, and tick enable SuperSu during boot. A lot of stuff not sticking seems to be fixed simply by enabling SU during boot... makes sense given it's a root app though.
[Nexus 6  Original Android Development] nextelbuddy:
You say that like the N5 days were like years ago. The n5 is only a little over one had old.
[Nexus 6  Original Android Development] bigdog_nick:
I go through phones like girls with purses. Since my n5,ive had oppo and LG g3
[Nexus 6  Original Android Development] stas333:
For those who's settings are not sticking, try to clear fk app data. That seems to work for me.
[Nexus 6  Original Android Development] slekkas:
I'm a little confused. I'm using fk with pure shamu and I've bought the FK updater app. If I reboot I go into CPU adjuster and I see the min CPU is around 1700 and max is 2700. If I just open the FK updater app and I go back to the CPU adjuster then min CPU is 300 and max is 2700. What is the default normal? Meanwhile my battery is really not good at all. Any tips? Thank you.
[Nexus 6  Original Android Development] zephiK:
What you're seeing is a prime example of cpu boost. Do a Google search or search in the thread about it I made a whole post explaining it.

Is your phone properly sleeping?

Do you have any wakelock?

If you want to optimize your battery further, take a look into vomer tweaks. Do a Google search on that. It's a good start, if it doesn't fit nicely then tune accordingly until you hit the sweet spot.
[Nexus 6  Original Android Development] Krunk83:
I can't find any resolution on my stutter issue. It must be an issue with my phone when a custom kernel is installed. When on stock, it runs smooth. As soon as I flash franco, lean, elementalx kernels I get the stutter. I've tried clean flash with no apps installed and no google log in. Guess I'll just use stock and try new franco updates to see if anything changes. Thanks for those of you that tried to help.
[Nexus 6  Original Android Development] slekkas:
Thanks for the answer. I've already tried vomer and the phone always stayed at 300 and rarely deep sleep. Have a look at my deep sleep. It seems OK I think.
[Nexus 6  Original Android Development] gambit07:
Yeah same here, everything else sticks now except for dt2w. This is with supersu enabled on boot, data wipe of the app, dt2w disabled in rom settings, etc
[Nexus 6  Original Android Development] Z-Man™:
Deep sleep looks fine. Grab BBS and check your wakelocks if you feel you have a issue.
[Nexus 6  Original Android Development] franciscofranco:
Let me guess you're using that special power.shamu.so?
[Nexus 6  Original Android Development] boysetsfire:
DT2W is not sticking for me either, and I'm not using any special power.shamu.so.

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] franciscofranco:
Well, it works for me, the code on the app is bug-free.
[Nexus 6  Original Android Development] gambit07:
Not that I know of, I'm using a Slim rom variant and I didn't do the so mod. I did just check and forgot this rom doesn't have an option for dt2w in settings so I did not turn that off in the rom (I don't think the rom came with it available now that I think about it). Anyway, not a big deal. Probably switching to a different rom will fix that.
[Nexus 6  Original Android Development] franciscofranco:
https://github.com/SlimRoms/device_motorola_shamu/commit/1c205afe3724154ce6b274595b45258f24a86b6d

There you go. Every time you screen off double tap to wake is enabled. It's so easy to blame the Kernel/app isn't it?
[Nexus 6  Original Android Development] gambit07:
Hey I'm not trying to be hostile or anything, just wanted to let that other user know I was running into the same issue not necessarily that it was a kernel related problem. I'm not a dev and not very familiar with github, but thank you for sending that it makes perfect sense. Like I said in the previous comment, I figured it would be fixed by switching ROM's since not everybody was running into this issue. Again, thanks for looking into that, your app is one of the best I've used and this kernel has always performed well. :good:
[Nexus 6  Original Android Development] franciscofranco:
Yeah my remark wasn't specific towards you, just a general sarcastic question :p
[Nexus 6  Original Android Development] Mauijpm:
Thank you so much [MENTION=3292224]franciscofranco[/MENTION] for your amazing kernel! I've used it on my Nexus 4, 10, 5, and now 6. I am having trouble with my input _boost_freq settings sticking on reboot at 1497. I have the SuperSU set to allow on boot. My color settings stick and so do my per app profiles. It is just the input boost that isn't. I've cleared app data. I've also uninstalled and re-installed, with no success.

Thanks for your help!
[Nexus 6  Original Android Development] altimax98:
Are there any plans to include the Theme Chooser specific patches? I only ask because my device runs butter smooth on your Kernel and I may have to switch back to CleanROM just so I can lose the stutters I get with Sensi and LeanKernel
[Nexus 6  Original Android Development] franciscofranco:
I have absolutely no clue, it should work! I'll try to reproduce.

It's not "patches", I just need to add a rule for SELinux to work with it. Next update will work with Theme Chooser.
[Nexus 6  Original Android Development] szale9001:
Hey franco, just FYI. The balanced performance profile is setting the hotplug threshold to 80.
[Nexus 6  Original Android Development] Fadakar:
Good to hear! Hate so say anything bad about other devs works, but I'm getting these stutters for fractions of a second with Sensei and LK on Euphoria when I didn't with Franco. Driving me nuts, can't wait for r9, thanks again for all your work. :)
[Nexus 6  Original Android Development] franciscofranco:
I know.
[Nexus 6  Original Android Development] altimax98:
Thanks, I wasn't sure what they were but i didn't want to call them fixes as calling it a fix implies it was broke to begin with :)
[Nexus 6  Original Android Development] nextelbuddy:
not sure if it was always like this but I now on R7 and now R8, I still have issues with certain settings not sticking or changing...

example:

1. Min CPU frequency will randomly change to 1267 but nothing else changes and if I have that set to boot which was set at 300.. now im booting at 1267.. for now ive just unchecked for boot so it always defaults to 300

2. Scheduler keeps changing from Deadline to NOOP.. its random bit it does continue to happen.

i tried conservative for R7 and now R8 but for my uses I have found that interactive is much more battery friendly for me with my screen on. conservative may give better scaling and performance with apps and screen on time however I have yet to see any benefit to using conservative over interactive with my actual use and app use so I am thankful we have the option to use interactive.

Also not sure if it was an SU think or FKU thing but:

I had SU NOT SUPRO installed not that it matters, and I had all teh default settings for SU which meant Default access was set to prompt and Tapjacking protection (I believe was absent from non Pro APP) was set to disabled.

when i updated the FKU APP the other day i was being prompted by Su to grant and no matter what I could not touch grant... i could for other apps like Quickboot and Root explorer but the FKU would not let me choose grant...

Tapjacking protection Unchecked= "The superuser prompt dialog will not respond to input while obscured by other window or overlay"

Tapjacking protection Checked = "The superuser prompt dialog will always respond to touch input.

i upgraded to SU PRO and unchecked the option for Tapjacking Protection and then went back into FKU and now I could choose grant..

not sure what all that was about but it was so weird.
[Nexus 6  Original Android Development] franciscofranco:
Comon not this again. Min freq gets boosted to certain frequencies for 20ms, that's part of thread migration boost.

NOOP is the default I/O scheduler. Set on boot works fine to me.

SuperSu also works fine for me, I test it more than 100 times a day.
[Nexus 6  Original Android Development] lobrau:
Any plans to incorporate other I/O schedulers? Particularly fiops.
[Nexus 6  Original Android Development] nextelbuddy:
hi Franco, i not talking about just getting boosted for the first 20ms.. i'm talking about the actual setting in FKU>CPU manager>min CPU frequency setting shows 1267 value as if I had chosen to set that value and it stays there until i change it back no matter if i do it in the first 20 MS of a boot or if its been several hours and i'm just poking around the app looking at settings.

i understand NOOP is the default but i'm just telling you my experience. in my setup. Maybe i'm the only person in here that has it.. maybe i'm the only one that notices it.. you know as well as I do that as a developer there are many cases that one person will experience an issue and someone else doesn't... even developers can experience this if they run an app in a DEV environment depending on their settings to mask things like optimization/virtual settings/global etc.... often times i report bugs to devs and they say "works fine for me" and then later they try it outside of their developer environment and experience the issue.

What is this thread for? is it just for you to offer the app and kernel development process and that's it? is it for Feedback from testers/users? is it for pats on the back?

i'm just giving feedback, i'm sure you deal with tons of BS on here and i'm sure it gets tiring and "annoying" but I have better things to do then to whine on here about things. I thought I was giving honest polite feedback, no finger pointing, no demands etc and certainly not ungrateful.

if you are getting tired of repeated issues that you may have already covered pages and pages back and are simply tired of re explaining.. then it may be time for you to implement a defect tracking system in Google docs that people have rights to add defects to that you can track and paste the results daily/weekly/monthly etc on the first page so people dont have to search and thumb through numerous of other posts or people using incorrect or different terminology causing skewed search results thus causing you less overall frustration and headaches in here.

again very thankful for your work and in no way am I chastising, just trying to let you know that I am serious about my defect findings and reporting and am no just another person looking for a kernel to help me only but am very much into giving back helpful feedback.
[Nexus 6  Original Android Development] franciscofranco:
No. All you need is what is there, that fiops thing was an experiment from an Intel engineer, it was never merged mainline, therefore I'm not going to merge it.
[Nexus 6  Original Android Development] lobrau:
I had no idea that it wasn't merged thanks for the information.
[Nexus 6  Original Android Development] Beast84:
So enabling tap to wake in the updater app means I don't need the other tap to wake app?
[Nexus 6  Original Android Development] numerouknow:
right.
[Nexus 6  Original Android Development] codygs83:
I'm glad I'm not the only one who feels this way and has noticed this. Very well put.

On a side note Ive purchased fku app awhile back to support the dev. But no longer use it because of the problems I've seen with it and I personally get better results with a diff app. No biggie. But I'm not about to point out those issues because I know how hard dev works on this and I appreciate every second of it ?
[Nexus 6  Original Android Development] SilkyJohnson:
Well said, and in addition: chastising those who support you and made you who you are is not good form. I think the term is "biting the hand that feeds you".

I remember when you just got started. You were humble and kind. Don't let your ego get the best of you. You wouldn't be here right now if it wasn't for us.

I mean this in all due respect. Sometimes people need a wake up call. I flashed lean kernel not because I was upset with your kernel, I did it because I was getting sick of the way you talk to people. I'm sure I'm not alone.

Peace.

Sent from my Nexus 6
[Nexus 6  Original Android Development] lazarus2297:
Question regarding the tap to wake.. First it seems as though you tried other tap to wake options.. Does enabling this one give more reliability to the tap to wake? I have tried the root needed app, and the power.so mod and both were unreliable at best.. I am coming from an LG G3 and their version is very reliable. I would really like to have that feature back but I would also like it to be reliable.

Thanks!
[Nexus 6  Original Android Development] franciscofranco:
Let's start with the beginning. A typical interaction goes in this flow:

1 - CPU0 min = 300MHz

2 - You click the CPU Manager tab

3 - CPU0 min gets boosted to 1.2GHz and stays there for 80ms

4 - During that 80ms period the CPU Manager tab is loading and I read the CURRENT CPU0 min frequency, which is, at that time 1.2GHz

5 - Before the tab is showing you all the values and stuff, I've already saved the values to the adapter

6 - CPU0 min freq returns to 300MHz

7 - CPU Manager shows up, but shows 1.2GHz because that was the frequency that was written on the cpufreq knob when CPU Manager was initiated.

This is a simple interaction. Even if the value isn't the 1.2GHz there is also another event that boosts min, which is when a thread migrates from one CPU to another. Imagine CPU1 is doing something and its frequency its at 1.5GHz. If it migrates that task to CPU0 then CPU0 min will be boosted to 1.5GHz for 20ms. If you happen to load CPU Manager during that 20ms window then Min frequency will obviously show up at 1.5GHz.

I don't dynamically update Min frequency every second on that panel, because that isn't the goal, so of course until you either refresh the tab you'll still see the same min freq that was there when the file was scanned.

I'm sorry if my reply sounded ungrateful, most of the times I just write whatever goes through my head, and that feeling was exactly what I had when I read the 1.2GHz min thingy again.

Couple things:

1 - Adding info to the OP doesn't change anything, 99% of the users won't read it, and it's just a waste of my time

2 - Making a bugtracker is also just another overhead for me and most of the reports will be bogus. Been there before, doesn't work

3 - I'm here actively reading and replying for 14h a day, sometimes even longer. I read every post, every question, every complain, every compliment... I seriously don't know what else I can do more, I can't always be mr. nice guy because honestly 99% of the questions are answered either on the same page or the page before.

I understand your concerns, I appreciate the feedback. Now please put yourself in my position as well.
[Nexus 6  Original Android Development] franciscofranco:
The Kernel code is the same regardless of what method you use for double tap to wake, it's just a sysfs knob to enable or disable.
[Nexus 6  Original Android Development] franciscofranco:
Alright so what problems are you having with my app? I can't figure them out if I'm not having issues, so please let me know and I'll do my best, as usual, to improve the experience.

Ah comon cut the crap. I've always been like this, I write what I think, I don't hold back. I'm not biting any hands for ****s sake. Isn't the Kernel work that I do 100% for free? Don't you flash it for free? Don't I give you support for free? Sure we can talk about the app. Haven't I issued more than 200 updates since December 2012 (app release) 100% for free? Have I asked for anything more in return? Don't I give hourly support to all my users? I just frickin' rebuilt the app from scratch for 5 months. I slept through Christmas because I spent the week before having 1h sleep per-day to finish the app on time for Christmas so that users could enjoy it? Comon dude! Just because I'm direct and say what goes to my mind I'm already "biting on users hands" ?

What I just wrote is a perfect example of writing what goes through my mind. From dealing with me this phrase says it all: "What you see is what you get".

I'm sure LeanKernel will be awesome as well, Imoseyon's a great guy and knows his ****. Good luck!
[Nexus 6  Original Android Development] javacody:
I get that min stuck on 1.2 as well. Doesn't matter if I refresh, restart Franco, etc. It stays there until a reboot.

If you say it's not a bug, I believe you, just seems odd that it won't go back down to 300 min until after rebooting.
[Nexus 6  Original Android Development] franciscofranco:
Pushed r9. Pretty happy with it. Enjoy.
[Nexus 6  Original Android Development] pinoyflayv:
Franco no sugar added!

Haters gonna hate! Stay the way you are bro! Good **** about you is your personality! You do not sugarcoat your posts here in the forum. Straight to the point!