yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] codygs83:
I kind of doubt this. I had this issue on a diff kernel using a diff app to tweak it.

Fix for me was a couple of reboots and clearing cache.

Hope this helps somebody.
[Nexus 6  Original Android Development] machNex:
Is SuperSU set to enable su during boot?

Other than that, if it is an FKU problem, try uninstalling FKU and then monitor the situation.
[Nexus 6  Original Android Development] Alaris:
So the settings under CPU manager aren't active unless I check set on boot? Because my min CPU frequency is set to 1700 and I have never touched CPU management.
[Nexus 6  Original Android Development] slekkas:
Anyone? :(
[Nexus 6  Original Android Development] frenchy714:
I've done this without success, thank you for the suggestion though.

No it isn't. I'll give these a try. Thanks for the suggestion.

I pooped my pants once, it's a long story....

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

Stock settings should be good to go. The battery life and sot you achieve will depend heavily on your usage, apps installed, signal strength, etc. What works for many may not work for you and vice versa. Your best bet would be to experiment with different settings yourself, just make sure "set on boot" is unchecked just in case your phone doesn't play nice with the setup you're experimenting with.
[Nexus 6  Original Android Development] slekkas:
Thank you for answering. The reason I ask is because I've read in previous pages people saying they get better SOT with interactive and better idle with conservative so I just wanted someone to tell me if this is a fact or just speculation.
[Nexus 6  Original Android Development] frenchy714:
Gotcha. The truth is it may be fact on one person's device and speculation on another's. They're both great governors, give them both a try. Naturally YMMV ;)
[Nexus 6  Original Android Development] wrongway213:
I actually would say this is fairly accurate in my personal experience. That being said, SOT on r9 is a lot better than on previous conservative governors, while idle has not suffered any.
[Nexus 6  Original Android Development] paychex:
Doubtful. Plenty of people using the app without issue. Most likely they other settings, apps, scripts, ROM, etc causing their issue
[Nexus 6  Original Android Development] Svid:
Maybe adding headphone boost? [emoji1] miss this feature alot
[Nexus 6  Original Android Development] resynx:
r9 performance is straight up awesome, smoothest my N6 has ever been :D
[Nexus 6  Original Android Development] franciscofranco:
Soon yes ^_^
[Nexus 6  Original Android Development] SmokeyMon:
Sweet!

Tonight my cat brought me my slippers as well!
[Nexus 6  Original Android Development] franciscofranco:
Wait until your cat runs "sudo give me food".
[Nexus 6  Original Android Development] Skripka:
Or discovers Virtual Studio.

HAI

CAN HAS STDIO?

VISIBLE "ARCH IS TEH PWNZ LOL!"

KTHXBYE
[Nexus 6  Original Android Development] Binary Droids:
My cat frequently runs "sudo give me food" and usually follows it with "rm owners sleep". :)
[Nexus 6  Original Android Development] rauschkugl:
It is an issue. Click the info button besides the min frequency in fku. What does it say? And what does it display? Not the same. Also as another one said. It's a place where the user sets the static min value the CPU should scale back to. If I want to see the actual value I go to the system monitor. It's just not correct there. It's also not the touch boost value because mine is set to another one. Yes it's just a visual thing and the CPU scales back anyway but the value displayed in fku should be the min value set by the user.

I had it also stuck at this high frequency once.

And no, there is no performance setting in the rom and no scripts were ever running.

Probably applied because I opened fku and didn't change it back to 300? I don't know exactly but it only happened once.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] CRXed:
Totally agree and Franco confirmed this bug himself by showing his screenshot

Now that screenshot shows exactly what is wrong in FKU.

The info button says "This is the minimum frequency your CPU supports". Then why would it show 1728 Mhz ??

I just had the same issue, it's stuck at 1728 and

- I am NOT using a custom ROM, stock Lollipop here.

- I am NOT using any scripts

- I DO have SuperSU set to use root at startup

- I have NEVER enabled the "set on boot" option for Min CPU frequency.

It is stuck on 1728 forever. Closing the app does not work. So it also has nothing to do with "updating the tab".

Again, a static value set by the user should not change to some random number.
[Nexus 6  Original Android Development] franciscofranco:
Quoting myself:
[Nexus 6  Original Android Development] machNex:
But this is a settings menu, not a system monitor. Why does it need to read the current state at all? Shouldn't it only show the user setting?
[Nexus 6  Original Android Development] datajosh:
I only have the lite version but my CPU never drops below 1.7GHz on r9

Edit: Could there be a circumstance that could cause FKU to set that false minimum it briefly reads? Or could the CPU be getting stuck when ramping up? I'll admit that I don't know about kernel development but it does seem to be something that's actually happening to some of us.
[Nexus 6  Original Android Development] franciscofranco:
Dude, it reads the CURRENT when you open the menu. What do you want me to read? Or you want me to hardcode the minimum frequency for each CPU I support? This is how all apps work. But don't worry, I will disable the thread migration feature, min won't be boosted to 1.7GHz anymore for 20ms periods at a time.

No, that is impossible, it only updates the min frequency IF and ONLY if the user clicks the chooses the frequency on the dialog.
[Nexus 6  Original Android Development] SweetwaterBurns:
Yes, but what if the user clicks that dialog and then the cpu ramps up as the dialog saves causing the app to read and store the higher value? I'm just spit balling here, but I've experienced it as well, whether you believe me or not. If you look through my previous posts, I reported something similar concerning the nexus 4 and recently the 6. I'm trying to figure out some way to reproduce it regularly, but I haven't been able to. I'm not being negative, just trying to be constructive. I have a lot of respect for your work, but between the reports of issues with color settings sticking on reboot and this issue, it seems that there is a bug somewhere in the FKU state saving/restoring. Like I said, I'm trying to find a reliable way to reproduce it, but my time is limited. If I get a log that seems relevant, I'll be sure to post it, but outright denying there is an issue when I've seen and made reports of similar issues on multiple devices is frustrating.

Again, thank you for your time on all of your kernels and the app. I love the quality of your releases and that's why I run franco on every device I am able to.
[Nexus 6  Original Android Development] franciscofranco:
Again, that cannot happen. I know what I coded lol. It only SAVES the value if the user CLICKS the frequency from inside the dialog.

Starting from r10 this min boosted thing won't happen anymore, I'm disabling the thread migration thing.
[Nexus 6  Original Android Development] ZiggSVO:
Disabling performance boosting features because people lack common sense? Lol

Or another reason?

I'd understand completely for that first reason as some people can just be too much lol

Sent from my Nexus 6
[Nexus 6  Original Android Development] machNex:
I'm not a developer, so sorry if my comments exasperate... I just figured that a settings menu would save a data file of some sort with with settings made. The menu would read that file both on boot to apply the settings, and while opening the menu with the possibility of changing those settings... leaving the display of current states to the system monitor.

I must add, I haven't seen this behaviour. My menu always shows 300mhz for the min and not the current state.
[Nexus 6  Original Android Development] franciscofranco:
First of all I think we don't need it at this point due to Conservative being omfgFast to decide what to do when there's a load change that really requires a ramp up. Might save us some power too!

And yes, also I'm pretty much done with this why min is boosted question. I don't mind people asking, but it's pretty easy to find the 10 replies by doing a small and quick search :) you can still enable the thread migration anyway, it's just a sysfs knob.
[Nexus 6  Original Android Development] SweetwaterBurns:
If you'd taken the time to read my posts, you'd see that my issue was with the wrong maximum clock setting getting saved. Removing the boost doesn't solve that, or the color issues at all. Thanks for not solving the problem. I'm done with this thread and will leave it at that. But you refusing to admit there might possibly be a bug introduced into your code back when you updated FKU for lollipop is the problem not a bunch of stupid users.
[Nexus 6  Original Android Development] mgear356:
Honestly I don't give a **** about 1728min speed.

As long as

- I opened up cpu spy, it shows 300mhz as the longest time

- my phone doesn't get hot during idle

- it is cooler compared to stock

I can very well ignoring that min speed. Franco knows best.
[Nexus 6  Original Android Development] frenchy714:
I agree with everything you posted however, in my case that isn't so. When I pull up CPU Spy it shows hours spent on 1728 with virtually no time spent at any lower freq other than deep sleep.

Franco I love your work, I paid for your app to show support, and highly respect you as one of the key Developers in our community. This will be the last time I post about this issue in your thread.

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] paychex:
Yeah it's your problem, not mine--or the many people here not having the problem. It's not a kernel problem or an fku problem. It's something else you did to your phone that's causing the issue. If you're not running stock--start there and add your tweaks, scripts, rom until you find the culprit. Stop crying here
[Nexus 6  Original Android Development] michmeister:
You just need to grant fku superuser rights and color and settings will stick on boot.
[Nexus 6  Original Android Development] paychex:
No, he didn't. He confirmed people are crying about nothing. He proved, once again, the displayed min--at times--displays something other that the user selected min (because of touch boost--the same effing reasoning behind why EVERY kernel app will display a lower frequency than the user selected max when the phone is thermally throttled).
[Nexus 6  Original Android Development] nhpctech:
also need to click the check box too. :)
[Nexus 6  Original Android Development] dhufford81:
How do you honestly expect anyone to take you seriously anyways when you have a signature like "I pooped my pants once, it's a long story..."?
[Nexus 6  Original Android Development] frenchy714:
Really? You chose to attack my signature?? Now that's funny.

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] ZiggSVO:
Thought so :p

And good to know about the technical reasoning ad well :p

Sent from my Nexus 6
[Nexus 6  Original Android Development] Svid:
Well the 1728Mhz min speed "bug"? in the FKU just a visual bug i guess.

Check the attached screenshot.
[Nexus 6  Original Android Development] murdok83:
Can anybody help me? Since i falshed r9, my phone never goes into deep sleep but stays at 300mhz... Never had such problem when on r8...

I have stock rom with nothing weird on it... just stock ....

any suggestion?

thanks
[Nexus 6  Original Android Development] big_adventure:
The issue here is that a few users are having a bug where 1.7ghz gets taken as the min frequency and it stays there for real. It may totally be a bug in display for 99% of users, but it's a bug in functionality for a few others. I still have this issue if I set the MAX CPU to anything other than the default, and set it to set on boot. I can boot the system, and it'll force itself to 1728mhz as the MIN. I can confirm in CPUSpy and in BBS that, in fact, the only CPU states being used are deep sleep and 1.7ghz and higher. NOTHING ELSE gets used, and I've done this for more than an hour on two occasions. As pointed out before, I do not have any other app on my phone that would effect min CPU, dn't have any scripts configured and don't have init.d support in any case. Phone is stock rooted. Further diagnosis seems to show that doing this without any CPU parameters set on boot in FKU doesn't tend to screw up the MIN cpu freq. It'll show 1.7ghz in min thanks to the display bug, but it won't actually force the CPU's min freq there.

It's not a big deal for me: I just check it after each boot and fix it if needed. I only boot the phone when troubleshooting or when flashing a new kernel, so it's not a huge deal for me. But the attitude of some of the posters here about a legit issue for a few users is pretty awful - it's why I stopped mentioning it.

The idea that something isn't a bug if it doesn't affect everyone is pretty silly.

I mean, people who had WiFi issues really had the issues and they got fixed, but not everyone had them. People who had set on boot issues really had them, but not everyone did. Franco's a great dev and I've been using his kernels for years, but he, just like every other great dev, occasionally makes a derp. And Franco, like every other great dev occasionally reacts by saying "not a bug in my code!" only to find eventually that it is - and to his credit, he fixes such things as soon as possible. Not an attack at all on the man - coding is complicated work.
[Nexus 6  Original Android Development] big_adventure:
You have something keeping your phone awake. Get Better Battery Stats and perhaps Wakelock Detector and try to find out what process is doing this to you. Since it's awake ALL the time, it should be really easy to find. Remember two obvious things: the phone doesn't deep sleep when the screen is on, and I've noticed that if the phone is on the turbocharger, it doesn't deep-sleep at all - there is a module that supports the turbocharger that keeps the phone awake. At least, it does on mine. I noticed this the second day I had the phone - I rebooted it before sleeping, plugged the thing into the turbocharger, checked when I woke up, and noticed 0% deep sleep. I WTF'd, then checked the processes and noticed the module I mentioned. Once I unplugged the phone and let it sit, deep-sleep was normal. YMMV
[Nexus 6  Original Android Development] rauschkugl:
And what if it doesn't show 300 anymore if you open cpu spy? That's what some are experiencing.

Gesendet von meinem Nexus 6 mit Tapatalk

---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------

No its not. My phone is totally stock and I'm flashing for years and am a software dev myself earning my money with it, so you don't have to tell me that I'm doing something wrong.

And if it's not your problem you should just not reply, some users have problem, if you're not one of them just shut up!

There is no script, I already said that!!

Gesendet von meinem Nexus 6 mit Tapatalk

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

Yes he displays a actual cpu state where a static value should be displayed. Also that's what the info text says.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] murdok83:
I had already controlled BBS and no wakelocks or app showing... I reflashed the kernel and now it seems to go into deep sleep just fine
[Nexus 6  Original Android Development] paychex:
And I've said as much. I also said that it isn't a kernel issue as everyone isn't having the issue. What part about that don't you get?

Well if you are such an awesome developer you should be able to figure out with some simple logic this isn't a kernel issue. So you have no apps installed either? Again start completely stock and ads if you are really interested in finding your issue.

---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------

Look bub the min shows 1.7. Perfmon shows lower. How much more do I have to dumb it down to a "developer"?
[Nexus 6  Original Android Development] franciscofranco:
I think you are overreacting.

When the user clicks the max frequency from the dialog it is echoed to the appropriate path, then, if you choose to set it on boot I save the current max frequency to the shared preferences file as in a <key, value> map. Then, after boot, FKU listens for the BOOT_COMPLETED system broadcast to be sent. Once it's sent, it starts a service that reads from the HashMap and then I have a for each cycle that reads each key and value, and I echo the value to the key (path). I do this for every <key, value> pair. So if you've set 1728MHz as the max I'll be re-applying it as max during the boot service. Same thing goes for the Display color parameters. I've set them like 1 month ago on my device, I've rebooted more than 100 times, it always gets restored. I'm not saying my code is flawless, but I've been doing this thing for a long time, I'm pretty darn sure my code, at this point, is not the issue. But if you get me a reproducible case

I'm more than happy to try and trigger a possible bug.

If you think I'm ****ing with my users, well, you don't know me and quite frankly there's nothing else I can do.

Maybe, for some reason, there's a bug on CPU-Boost that doesn't reset the min frequency to it's normal min after a thread migration. I've seen this happen in the past, that's why I disabled the thread migration boost for r10.
[Nexus 6  Original Android Development] big_adventure:
See, this is completely wrong. We've had heaps of bugs that only affected a subset of users. Like WiFi bugs, issues setting on boot - and these are things that Franco's fixed as he's found them. YOU are not seeing this issue - great. Good for you. But that absolutely doesn't mean that it doesn't exist. And there is no reason to be needlessly rude to someone who isn't doing the same.

Except, as he says, that's not what some few of us are seeing in certain circumstances. And again, why are you going out of your way to a) be rude to someone describing an issue and b) pollute the thread with your obviously non-pertinent comments on same? Saying "Based on my experience, I would say that you have another app messing up the settings" would be basically fine. Saying "Duuuuuuude, you douche, stop annoying me with your comments about your 'facts' about what you 'see' with your own 'eyes' on your own 'phone' and accept that all of Franco's and Google's and Qualcomm's and Motorola's code is 100% bug-free because I don't see what you see so it doesn't exist", though? That's...a little rough.

Franco's the dev here - if he doesn't want to do anything about it, or doesn't think it's an issue, well, it's his kernel, his code and that's fine. Like I said, it's a trivial fix for when it affects my phone - I just check 5 minutes after boot to ensure I'm seeing speeds less than 1.7ghz. Takes literally 2 seconds. And if I'm not, I simply go into FKU and throttle it.

EDIT: ANNNNNNND blitzed by Franco agreeing that it theoretically could be possible, and that he is taking correctives. Like I said before - Franco's a great dev.
[Nexus 6  Original Android Development] wrongway213:
Hopefully disabling thread migration boost will be able to definitively put an end to everyone thinking their kernel is malfunctioning, those of us enjoying the kernel without (possibly perceived) issues would be glad for the rest of you to join us in enjoying your device.
[Nexus 6  Original Android Development] big_adventure:
Why would you assume that we're not enjoying our phones? Has anyone of the very few people who seem to see this issue said that having to check one situation that takes literally 2 seconds one time after boot is ruining their experience with their phone or FK? I haven't seen that. I adore my whale. When my N5 was stolen (why I dropped out of FK on that device), I used a smaller device for a while - and basically stopped communicating extensively, thanks to painful typing and crappy notifications. Jumping up to a phone the size of a snowboard has me writing novellas instead of texts. That alone is amazing. One two second thing once in a long while couldn't possibly outweigh even that one good thing.
[Nexus 6  Original Android Development] wrongway213:
I think you misinterpreted my post: I'm saying that hopefully disabling that feature will cause everyone to realize the kernel is working as it should be, therefore causing this debate to end and allowing the users in this thread who appear to be pretty concerned with this issue to go back to enjoying using their device without worrying about whether the kernel is functioning correctly or not. "Enjoying" your device, as I intended it, implied enjoying your device without worrying about the statistics or whether it is correctly functioning, as I am enjoying mine now because mine is correctly functioning and I know that it is based on my own experience and Franco's explanation of cpu boost, which I have found to be the correct explanation for the behavior I see on my device after some investigation in FKU.
[Nexus 6  Original Android Development] cobyman7035:
for those that have min. cpu of only 1.7ghz...have u tried vomer tweaks to see if it goes down to 300mhz? i use PERFMON app to check cpu states on idle
[Nexus 6  Original Android Development] franciscofranco:
Using or not using vomer tweaks it's completely irrelevant for the topic in question, sorry to burst your bubble :)
[Nexus 6  Original Android Development] big_adventure:
Gotcha. No harm, no foul. Like I said, the issue just isn't that big a deal, when it happens. It just requires a tiny bit of vigilance: for me, ONLY after boot, and ONLY when I've got something else forced to set on boot in FKU. And after that, it doesn't seem to come back. Plus, I reboot my phone only in the 20 minutes after Franco sends out a new version of the kernel. :)
[Nexus 6  Original Android Development] SweetwaterBurns:
You are right, and I apologize. I was responding to more than just you. The whole "I don't have a problem so you must be lying or stupid," mentality of some of the people here just got under my skin, and seeing it reinforced by you saying what I am experiencing is impossible irked me. I seriously am trying to reproduce it, but I've not been able to grab any relevant logs when it has happened so you can see exactly what is going on on my (and others) phones. I uninstalled FKU on my Nexus 4 in December and had no issues since. I took it off of my 6, two weeks ago after seeing the same behavior and not had any more issues, just run the kernel at your defaults. I've recently reinstalled it just see if it still occurs for me. I'm thinking of setting up a Tasker profile, to watch for changes to cpufreq stuff and dump a log if it catches something. I work 60+ hours a week and go to school so I don't always have the time or tools to fully diagnose the issue when it happens. I'm used to just readjusting the settings and getting on with my day. I'm just tired of the denialism.
[Nexus 6  Original Android Development] rauschkugl:
Did you even read one thing? Already told you twice that I already was completely stock. I also said that I don't have a problem with it in my first post and that just the value displayed in fku should be changed. Please just don't answer to my posts anymore.

I don't care about the screenshots of others that don't have the issue. There are also screenshots of people which have proven the issue.

And what's your simple logic that says it's not the kernel? You didn't have one argument so just stop answering to my posts.

Gesendet von meinem Nexus 6 mit Tapatalk