yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Dougi:
[MENTION=3292224]franciscofranco[/MENTION],

I've never used your kernel, it's my first time with a nexus, and I love it.

I just bought your app, best one available on the market, amazing would be the right word.

After flashing r6, my phone became a jet, an airplane, I mean, my nexus is just sooooo smooth I can't believe how fast and smooth it is..

Just dropping by to say BRAVO and thank you for sharing your work with us :)

See you around
[Nexus 6  Original Android Development] CRXed:
The hint is always the same as the value you previously entered.....so it looks like an entered value if you open it (by misstake for example) and then when you hit apply, the opton will be empty.

A textfield should not be empty when you open it.....it's very easy to mess things up this way.
[Nexus 6  Original Android Development] big_adventure:
Any ideas on my phone automatically forceing 1728mhz as CPU min on boot?

There is a ton of junk in the logs, but I specifically found this odd...

01-14 18:17:20.389 W/BroadcastQueue(850): Permission Denial: receiving Intent { act=android.intent.action.BOOT_COMPLETED flg=0x8000010 (has extras) } to com.google.android.apps.authenticator2/com.google.android.apps.authenticator.seedrotation.SeedRotationService$StartupListener requires android.permission.RECEIVE_BOOT_COMPLETED due to sender null (uid 1000)

Is this somehow blocking the BOOT_COMPLETED, and therefore the kernel can't back down to the appropriate freqs?

The entire log from beginning (minus the first four useless lines) to end of boot+stabilization is attached. It's too big for pastie.org. There are no entries from the end of this extract for another 10 minutes, and nothing after remotely refers to CPU stuff.
[Nexus 6  Original Android Development] franciscofranco:
Yes, exactly. The hint is there to provide context. It's greyed out for that purpose. Duh, you know you entered a value or not, or you don't remember what you did like 2 seconds ago? I know what you're saying, but I think this is common sense. You're the first one to say anything like this. The hint has been there for a long time, since the old branch and all.

How can you mess with it? You open it, you see the hint so you know what value is set on that option - you're not going to apply the same value that is already there. If you want a new value you click it and you apply a new one and hit apply. I'm sorry but I don't really see how this can be confusing in any way.
[Nexus 6  Original Android Development] franciscofranco:
There's nothing on the Kernel that sets your min to that value indefinitely. Are you sure your min is 100% of the time that frequency? Have you opened up a system monitor and see? No one has that issue but you.
[Nexus 6  Original Android Development] wrongway213:
You on LiquidSmooth or another ROM that has performance tweaks for the kernel built in? This happens to me on LiquidSmooth until I go into performance and set it down to 300, then it sticks but does not stick on boot, have to set with ever reboot.
[Nexus 6  Original Android Development] big_adventure:
I let it run for an hour and a half, with max set to 1.9 (what I'm running), and BBS and System Monitor (pro) show only deep sleep, 1.7 and 1.9 being used until I manually set the min back down to 300. I let it run for 45 minutes with pure default settings, and all I see are deep sleep and 1.7 though 2.6. Of note, I've (pretty obviously) never set the min to 1.7ghz. Could there be a problem with something cached in FKU causing this? I have not tried clearing data.

Doing that now...

...and, it seems to have taken care of the issue. I'll continue testing. Any idea what would have caused that?
[Nexus 6  Original Android Development] wrongway213:
Check my reply. Are you on LiquidSmooth or another ROM with performance settings? If so it sounds like they're overriding your FKU settings.
[Nexus 6  Original Android Development] almujhool:
Hi guys

I wanted to know if there's anyway I can turn off the led when charging the phone?

I have searched for some options in the FKU without any luck.

I'm one of those who can only sleep in a pitch darkness so for me it's very annoying.

Anyway I would like to thank Franco and keep up the good work.
[Nexus 6  Original Android Development] BRKotucs:
http://xdaforums.com/showthread.php?p=58156610
[Nexus 6  Original Android Development] nexusmaniac:
Ooh! r7 :D
[Nexus 6  Original Android Development] franciscofranco:
Pushed r7! It's more a tune up from the previous release, but you definitely should flash it now, or you'll be eligible to face my wrath any time I decide that is appropriate :angel:
[Nexus 6  Original Android Development] zephiK:
New app update too ;) addresses charging led enable/disable
[Nexus 6  Original Android Development] wrongway213:
Not seeing this.. hmm. Glad to see those settings fixed, definitely work better in my experience having applied them myself on r6 than stock r6 settings.
[Nexus 6  Original Android Development] michmeister:
Where do I find the led enable in the update?
[Nexus 6  Original Android Development] pinoyflayv:
just need sweeptosleep feature!

Please give us this feature! Loving the r7!
[Nexus 6  Original Android Development] anthonyg45157:
Woohoo! You're a beast Mr. Franco. I can't keep up.. :D

Also thanks again so much for the beautiful app! Its the best material designed app I've used!!

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Same place you find all app updates, Play Store...
[Nexus 6  Original Android Development] zephiK:
Franco already pushed it, it'll be available in the Play Store in the upcoming hour or so.
[Nexus 6  Original Android Development] michmeister:
Not the app update the led enable/disable

---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------

Never mind got it. Thanks
[Nexus 6  Original Android Development] pinoyflayv:
SW2S not there yet.

---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------

Never say never bro!
[Nexus 6  Original Android Development] wrongway213:
So since I flashed r7 I can't deep sleep at all, constant kernel wakelock "msm_hsic_host" and a reboot does not fix it. Franco any idea what's going on? Never had wakelock issues from any of your kernels.
[Nexus 6  Original Android Development] cmo220:
Very happy that improvements have been added to the cat! My cat has been deep sleeping very well since r4.
[Nexus 6  Original Android Development] wrinklefree:
Seeing the same thing. Odd
[Nexus 6  Original Android Development] vomer:
I am assuming u mean swipe to wake or sleep?

If so, never gonna happen going by franco's older posts :)
[Nexus 6  Original Android Development] czonin:
Just upgraded from r6 to 7 and I don't have any data. Running stock on Tmobile.

Edit: It eventually worked but it took much much longer than usual.
[Nexus 6  Original Android Development] franciscofranco:
Here go go again. msm_hsic_host comes from the radio. Without it you lose your data connection. If the lock is being keep held then I can guess your signal is beyond ****. There are no changes to that subsystem on r7 and nothing we can do about it. It's what it is.
[Nexus 6  Original Android Development] wrongway213:
It's absolutely constant, tried rebooting and clearing FKU app data but nothing works. On LiquidSmooth.
[Nexus 6  Original Android Development] pinoyflayv:
I guess missed that older post bro. What was the reasoning behind it? Not battery friendly?
[Nexus 6  Original Android Development] franciscofranco:
This is beyond odd, I haven't touched anything that is remotely related as far as I know. Lemme check something really quick.
[Nexus 6  Original Android Development] wrongway213:
Odd.. don't mean to question a kernel genius like yourself but I just restored r6 in FKU and things are fine, I get good signal where I am as well. I've never seen this before until just now on r7 so I just assumed that something changed on r7 was the cause... if not now I'm even more confused.
[Nexus 6  Original Android Development] paychex:
Thought that would end endless questions regarding the led
[Nexus 6  Original Android Development] wilson289:
Can anyone provide me with a s/s of the stock cpu voltage on FKU please? Would be much appreciated :good:
[Nexus 6  Original Android Development] paychex:
Why would it be? He never said he was adding it.

Try his for screen off. Works good, Easy on the battery

https://play.google.com/store/apps/details?id=it.android.smartscreenon
[Nexus 6  Original Android Development] franciscofranco:
Can you please re-flash r7? I just pushed a different binary. Thanks. Let me know ASAP if there's any change.
[Nexus 6  Original Android Development] paychex:
I got it on a great wi-fi signal and a decent lte signal. Blame the cat
[Nexus 6  Original Android Development] phishfi:
Just trying to make sure: do the latest VomerTweaks still work with r7?
[Nexus 6  Original Android Development] wrongway213:
Fixed, 8 thanks limit is unfortunate in times like this... gotta love having a problem fixed in ten minutes flat. Thanks Franco!
[Nexus 6  Original Android Development] franciscofranco:
Obviously that they work, they will ever work regardless, it's just a bunch of shell commands...
[Nexus 6  Original Android Development] paychex:
Reflashed. Deep sleeping now. Awesome! Thanks

---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------

Not voodoo?
[Nexus 6  Original Android Development] anthonyg45157:
I'm at 50% battery with 3 and half hours of screen on time with r6(VT quad) Absolutely incredible .

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
You wanna know what it is? It ****ing grinds my gears. So Google on the new 5.0 CTS (Compatibility Test Suit) fails the devices that ship with an option called DIAG. It's basically an old communications protocol that Qcom uses for debug. I turned it off and assumed (note to self, stop ****ing assuming, it never works with Android and it's amateurish) that if they fail it on the CTS then no harm is done in doing the same on their new Flagship device. Of course all hell broke loose. **** this.
[Nexus 6  Original Android Development] wrongway213:
...and that takes you ten minutes to figure out, fix and re-release. I can really truly understand about half of the words/acronyms in that post at best.
[Nexus 6  Original Android Development] Media_Blitz:
Happened to me out of nowhere while on r6. It takes linger to reconnect from a restart and as of now, I'm stuck on HSPA+. Pretty sure T-Mobile is at fault
[Nexus 6  Original Android Development] wilson289:
Noticed that the I/O Scheduler default was changed from deadline to noop from r6 to r7?
[Nexus 6  Original Android Development] franciscofranco:
It was never deadline to begin with, been noop since the beginning.
[Nexus 6  Original Android Development] wrongway213:
My governor was always set to noop and I update FK as soon as it's released like clockwork, I thought deadline was default from VomerTweaks, not FKU.. could be wrong but I never recall seeing it set to deadline.
[Nexus 6  Original Android Development] paychex:
Think he's always used noop on the N6
[Nexus 6  Original Android Development] wilson289:
Sorry, must've confused with LK, which was what I was using before discovering FK :D
[Nexus 6  Original Android Development] zephiK:
Or used vomertweaks as vomertweaks sets default io to deadline
[Nexus 6  Original Android Development] wilson289:
or VT, either or!
[Nexus 6  Original Android Development] jriv:
Is conservative still the governor to roll with on r7 like it was on r6 mine was set to interactive by default after I flashed r7
[Nexus 6  Original Android Development] franciscofranco:
Conservative is the default.
[Nexus 6  Original Android Development] akellar:
I have tried updating again from both the app and the zip here, still no deep sleep
[Nexus 6  Original Android Development] wrongway213:
Mine is back to deep sleeping like normal.. try restoring to r6 then autoflashing to r7, I'd delete the r7 backup and the zip download as well because it sounds like the first pushed r7.. just an idea, worked like a charm for me, went from 97% msim kernel wakelock to 90% deep sleep
[Nexus 6  Original Android Development] jasonsymack:
I don't think mine is deep sleeping either. On sinless ROM and just updated to r7
[Nexus 6  Original Android Development] akellar:
That seemed to have worked, thanks
[Nexus 6  Original Android Development] Skripka:
The new r7 deeps sleeps fine here.
[Nexus 6  Original Android Development] wrongway213:
Yes, there was a little error when he pushed r7 initially that didn't allow deep sleep due to a kernel wakelock, but if you didn't install in the first ten minutes or so you would never have seen it, Franco fixed it that quickly.
[Nexus 6  Original Android Development] Skripka:
Yea well,some of us are a bit crazy when updates are posted :)
[Nexus 6  Original Android Development] mpgolfpro:
New to Franco Kernel.....quick question.....Do all of the "tick" boxes need to be checked within the app in order for the settings to take effect? Just wanna make sure I am using this kernel like it is intended. Thanks.
[Nexus 6  Original Android Development] zephiK:
The check boxes are for set on boot.
[Nexus 6  Original Android Development] michmeister:
How can you tell if it's in deep sleep
[Nexus 6  Original Android Development] mpgolfpro:
Can you elaborate? Im not sure I'm following. Wouldn't I want everything to "set on boot"?
[Nexus 6  Original Android Development] akellar:
Only if you made changes to the default setting
[Nexus 6  Original Android Development] wrongway213:
Download an app like BetterBatteryStats, you can find it right here on XDA. Just download the newest APK from that thread,install it, open and install as a system app and reboot. Then let it sit for a while and open it.. you can see your battery stats such as deep sleep, wakelocks, etc
[Nexus 6  Original Android Development] zephiK:
Franco Kernel Updater is finally available in the Play Store. Get it, you can control charging led and change zip path for download
[Nexus 6  Original Android Development] noneabove:
Just reflashed r7 and its now sleeping again, thanks! (Though to be fair reflashing alone might have fixed it)
[Nexus 6  Original Android Development] biglilsteve:
Can't you check in the battery stats too in settings? Or is that not the same thing.
[Nexus 6  Original Android Development] noneabove:
not the same thing
[Nexus 6  Original Android Development] boysetsfire:
Just flashed r7, is it normal that core 3 and core 4 are ALWAYS on and at 2,6 GHz? Tried clearing FKU data but no change... No other tweak or kernel app installed.

Update: went back to r5 and it continues to do the same :(

Update 2: rebooted and it was fine, flashed r7 again and now all is good :)

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] jimmypop13:
Thank you Franco for adding the option to disable the charging led. I've had no issues at all with your kernel. Thank so much for making my phone so much better!
[Nexus 6  Original Android Development] holeindalip:
Cores 3+4 stuck on max too, reboot fixed it
[Nexus 6  Original Android Development] noneabove:
So here's something that's confused me for awhile.. If I'm looking at for example System monitor and looking at CPU speed and load, often times load will go up to like 10% and suddenly the CPU scales to 1.7 GHz.. But upthreshold implies that it should reach 98% load before scaling up, no? The way I figure it one of two things is happening, one, the app isn't updating as real time as i think and that 10% is actually just what happened to be what the load was when the data updated or something a bit more complicated...

we see that 300 mhz is, lets just round to 10% cause i'm lazy, of the max CPU speed, so if we are at 10% load that means we need every cycle of the CPU (so while the CPU is under 10% load, we are at 100% load for the current speed). If we're at 20% load we need then 600mhz, and so on.. Am I completely misunderstanding or is it one of these two options?

On a similar note, I changed the down_threshold to 80 (which, if my understanding is correct means when there's less than 80% load it should start scaling down) but it seems to regularly display a cpu speed of >1.5ghz with a load of 10-15, but it still sits up there for quite some time
[Nexus 6  Original Android Development] franciscofranco:
Sigh... if the CPU is pegged with some kind of work, it's obvious that it will be using it's max frequency... comon guys...
[Nexus 6  Original Android Development] phishfi:
There's *some* risk involved when setting everything to set on boot. If, for example, you set the voltages significantly lower and then select set on boot, those lower voltages could crash the device when it gets put under heavy load. With set on boot, the device will restart, and then very early into the device booting up those settings will apply again, which could cause the crash to happen again... And now you're stuck trying to stop it before the settings apply.

The best way to handle this is to set settings the way you want them and leave set on boot turned off until you're confident that the settings are stable. At that point you can go ahead and enable it without worrying about causing any unrecoverable problems.

Hope that helps!
[Nexus 6  Original Android Development] franciscofranco:
The 1.7GHz boost comes from a thread migration and its independent from the CPU governor.

You gotta see that the app only reads the sample once per second. You realize that during that second there were a gazillion different CPU frequency scales up/down? It samples every 10ms. 10ms = 0.01s. Now 0.01 x 100 = 1s. So while you sit there waiting to see the monitor refresh the frequencies can change up to 100 times. Not everything is what it seems.
[Nexus 6  Original Android Development] suku_patel_22:
Well my options are not sticking on boot. Max cpu, Thermal threshold, GPU frequency and color settings. All got reset after reboot. I have allow su on boot enabled.
[Nexus 6  Original Android Development] franciscofranco:
It works for me. What I'm guessing is that Android has some bug on the BOOT_COMPLETED broadcast or something, there's no way in the world that my code is wrong,
[Nexus 6  Original Android Development] suku_patel_22:
I am assuming that the reboot fixed your deep sleep issues.
[Nexus 6  Original Android Development] noneabove:
in fairness i had guessed that that might be one of the issues. :P

Is there an advantage to having it scale up at 98% load but only scale down below 20% as opposed to scaling up at 98% and down at 97%? This is for anyone who might know, I've been trying to find good documentation of the behind the scenes workings and there seems to be no middle ground between "oversimplified/wrong" and "way too complicated, come back with your engineering degree first"... Does changing the speed tax the CPU?

---------- Post added at 10:38 PM ---------- Previous post was at 10:38 PM ----------

I had already tried rebooting to no avail
[Nexus 6  Original Android Development] 619619:
r7 Kills WiFi for me, wifi networks are seen but it won't connect

Flashed r6, everything returned fine

I always use the autoflash option, maybe it was a bad flash?
[Nexus 6  Original Android Development] noneabove:
must have been, no issues with wifi here, worth giving it another shot i suppose ? Also try turning airplane mode off and on/rebooting, sometimes wifi just conks out on me for a bit
[Nexus 6  Original Android Development] wrongway213:
Strange - I autoflashed and I have good wifi connection right now, downloading a file right now
[Nexus 6  Original Android Development] tommy0823:
Can somebody see what I'm doing wrong?? I made sure that nothing is checked set on boot in fku, su access is granted to terminal, I even selected "trust system apps" in su. I'm on liquid smooth. Nothing is set on boot in built in performance settings either. Thanks in advance. BTW, WiFi connects fine for me on r7.
[Nexus 6  Original Android Development] gamewarden234:
Everything is working good on r7. Cpu is still a little more active then when on interactive but it is a big step in the right direction. WiFi works. No wake locks. Sleeps like a baby.

---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------

No WiFi issues. It has to be on your end.
[Nexus 6  Original Android Development] franciscofranco:
Duh... so basically you're saying that if goes >= 98 it scales up, if its < 98 it goes scales down... that's pretty stupid and I pretty much guarantee that you'll have major performance problems.
[Nexus 6  Original Android Development] paychex:
Is there really that much going on that the kernel needs to poll for load 100 a second?
[Nexus 6  Original Android Development] numerouknow:
+1

autoflashed r7 and no issues whatsoever. everything butter smooth & rock stable.
[Nexus 6  Original Android Development] franciscofranco:
This is an operating system, what were you expecting? Sitting there doing nothing? ;)
[Nexus 6  Original Android Development] suku_patel_22:
Had a reboot. Where is the kernel log file? couldnt find it.
[Nexus 6  Original Android Development] Svid:
Someone else have deep sleep issues with the latest kernel?
[Nexus 6  Original Android Development] zephiK:
redownload r7 for version 2
[Nexus 6  Original Android Development] shivindera:
Hi,

I know I should go through the thread for this... but 150 pages is a lot.

Could somebody please tell me the optimum settings for the franco kernel app to get the most out of battery and the kernel itself... I understood basic things like CPU frequency and all. But, need help with things like Hotplug Control, CPU Boost etc.

Screenshots would be appreciated.

Thanks :)
[Nexus 6  Original Android Development] big_adventure:
I had replied a couple of pages back to this suggestion. No, I'm stock, no custom ROM at all, and minimal mods to stock (DT2W from modded power.shamu, battery percentage from the app, reduced tcp keepalive for Google services). And the issue happened whether FKU was manually configured or not.

That said, clearing data in FKU seems to have done the trick.
[Nexus 6  Original Android Development] zephiK:
The optimal settings are the ones out of the box, they're the reason why they're defaulted to those values.

If you want to try other settings, theres vomertweaks and erm... theres my ROM, Chroma (shameless plug :p )
[Nexus 6  Original Android Development] big_adventure:
Wanting to "get the most out of battery and the kernel itself" is a little vague. If battery life is your goal, trying something like VomerTweaks Dual or a similar group of settings is probably a good place to start. Basically, limiting your CPU to two cores, reducing GCPU max and reducing GPU max are going to be your biggest kernel-related battery-life improvements. Everything else is generally tuning, as long as you don't really screw something up. You will want a few apps to help you identify improvements:

The paid version of FKU is a good idea - it makes finding and changing the variables a snap, plus it links right into system monitor.

BetterBatteryStats (the version on XDA, not on the play store) is a must for unifying information on things that drain battery, CPU states and such.

Something like Wakelock Detector if you find that your phone isn't sleeping as it should and you can't find the lock in BBS.

But if you don't want to do too much work on your own, start off just leaving the thing the way it shipped. If you notice it's draining faster than you'd like, try reducing CPU and GPU max (I run at 1.9ghz and 500mhz at this time). If that's STILL to much, try flashing Vomer's scripts.

And have fun!
[Nexus 6  Original Android Development] Svid:
Franco's website have only the regular r7.

Did i missed something?