yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] benrees21:
I've installed and left it at default settings except I changed I/O Scheduler to deadline. Everything is perfect for me. Using Rastapop ROM.
[Nexus 6  Original Android Development] simms22:
funny thing is that [MENTION=4770693]Krunk83[/MENTION] is right. and ive read about it in the q&a section, as others have been reporting it. i did get to work with someone that started one of these threads 2 weeks ago, that only the stock kernel wasnt stuttery(and he tried them all). and eventually we got him set up properly(on another kernel, not stock). so it takes a little work to figure out what cpu settings would work the best for your device, but it is possible.
[Nexus 6  Original Android Development] wrongway213:
Ohhh just now re-read that post and he said enabling/disabling, not just disabling. I thought you were saying you thought that in this case (the no-freq-mpdecision zip) we are enabling mpdecision, didn't know the 'case' you meant was this particular user's issues, I feel dumb lol
[Nexus 6  Original Android Development] big_adventure:
Something to try would be boosting input_boost_freq above Franco's 1.19ghz default. Set that to 1.5ghz or 1.7ghz or something and see if that helps. You'll lose some battery, since every touch will flash your cores to that level (which is still less than stock, I think), but you'll be instantly getting the phone up to a higher speed for the CPU as well as higher speed states for memory and bus. Every one of those things will boost response-time. You may also need to play with sample times, but I'd start with input boost freq.
[Nexus 6  Original Android Development] Tzfardaya:
Hey, franciscofranco, is there a system path to toggle the charge led on/off
[Nexus 6  Original Android Development] big_adventure:
There is!

...

...

...

Oh, you want this...

echo 0 > /sys/devices/leds-qpnp-f002ee00/leds/charging/max_brightness
[Nexus 6  Original Android Development] Tzfardaya:
Perfect, thank you.
[Nexus 6  Original Android Development] SilkyJohnson:
Hey there, old bud. It took you this long to get the 6? Lol. I know you were in 1+1 land for a bit. You still rocking the 5 as well?

Sent from my Nexus 6
[Nexus 6  Original Android Development] Michael2907:
Hi there i change to Franco and now in call no one can hear me,?

What is it?
[Nexus 6  Original Android Development] big_adventure:
Just reboot. I had that problem once, and a reboot fixed it - it never came back.
[Nexus 6  Original Android Development] Michael2907:
I do 2 reboots and nothing change
[Nexus 6  Original Android Development] big_adventure:
Do you have unlock sounds turned off? I recall an issue with one of the old Nexus phones, as well as with the GS3 (I believe), where, for whatever reason, the mic wouldn't work until the phone had made some noise on its own. Leaving screen lock/unlock sounds on would avoid the issue. So basically, if you booted the phone, unlocked the screen, and made a call, since the phone hadn't yet made a sound, the mic wouldn't work. I don't know if that's an issue here, but try turning on the lock/unlock sound (Settings > Sound & notification > Other sounds > Screen locking sounds and toggle that to "On") and seeing if that changes anything.

The only other thing I can think of is that the phone thinks you have a headphone or a bluetooth mic connected, and is trying to receive sound from that instead of the internal mic. You could try turning off bluetooth and plugging/unplugging a headphone with mic into the phone to be sure.

I highly doubt that Franco has touched the code for the mic hardware in his kernel, and I can confirm that calls work fine for me.
[Nexus 6  Original Android Development] Michael2907:
I do it.

Flashing kernel Form APP and reboot now works fine.

So will See how battery life is
[Nexus 6  Original Android Development] slekkas:
SOT is draining my battery like crazy. I don't understand what is happening. My deep sleep is fine but as soon as I start to read some news in Tapatalk or chrome I can see the battery percentage dropping very fast. I have adaptive brightness on and ambient display off.
[Nexus 6  Original Android Development] big_adventure:
How fast is "fast?"

The display on this phone eats power pretty quickly. It is NOT an efficient design as far as that goes. But when you say "fast", what do you mean exactly?
[Nexus 6  Original Android Development] GregNexus:
Has anyone else the problem that the phone crashes sometimes when you open the camera from the lockscreen? This happend now several times to me.

The screen goes black and the phone is off.
[Nexus 6  Original Android Development] wrongway213:
Every single time this happens to me I check kernel wakelocks and sure enough, it's sensor_Ind kicking up.
[Nexus 6  Original Android Development] big_adventure:
Just to add something - wrongway213 is (almost certainly) not replying to GregNexus here. :)
[Nexus 6  Original Android Development] GregNexus:
Yes, i will add a log:)
[Nexus 6  Original Android Development] wrongway213:
Good catch, having some issues quoting on XDA One app from time to time.. Reply just goes to a new post. Was referring to the SOT issue a few posts up lol
[Nexus 6  Original Android Development] Tzfardaya:
Yeah, I missed out on the launch batch... Running the 4, 5, and 1+1 as well as the 6..
[Nexus 6  Original Android Development] GregNexus:
I will add the log later... My only problems are the stutters and the crash of the phone sometimes, when i open the camera from lockscreen. When the problem will happen again with the crash of the phone because of the camera the log will be posted

But for now, has the attached Screenshot maybe something to do with the stutters? I get a large amount of this message when i touch the display.
[Nexus 6  Original Android Development] pr0cl1v1ty:
The 1 button push for Dynamic, made all my lag go away and my battery life is AMAZING.
[Nexus 6  Original Android Development] slekkas:
Unnaturally fast. In half an hour I lost 50%.
[Nexus 6  Original Android Development] big_adventure:
No, that's apparently not an issue. Basically, there is a touch_boost function that PowerHAL is calling that is there in the stock kernel, but which isn't there in FK. So, the missed function causes a log entry. Everyone running FK has that spam, according to Franco. There are a couple of other functions PowerHAL calls that equally fail (though much less frequently), but I don't see any consistent link to dropped frames in Choreographer from any of them.

If you are getting noticeable stuttering on touch, try raising the input_boost_freq. Franco's default is 1.19ghz for all 4 CPUs. Try 1.5 or 1.7 (or higher) as a test, and see if that changes what you see. Stock touch boost is CPU max, I think, so, if you have something running in the background, the much-lower touch boost means that you'll have to wait an instant before the kernel reads that the 1.2ghz boost isn't enough, and will then need to bring on all 4 cores, or to ramp frequency higher.

You could also try setting load_threshold to 0 instead of the default, to force 4 cores on when awake. I do this, and don't notice stutter or decreased battery life. Of course, I just also tested it at 90 (to have normal-ish core hot-plugging) and 100 (forcing 2 cores all the time), and neither of them caused me visible stutter either. My homescreens are pretty basic - bunches of icons, but only one widget.

---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------

Wow, that's insane. Were you gaming? In two games at once? :)

Kidding aside, you're going to need to get BBS running and take a log showing what's up. Even gaming on this phone doesn't use 50% an hour for me. When various reviewers ran things like intensive benchmarks until phone death, they didn't get life down under 2 hours.
[Nexus 6  Original Android Development] slekkas:
I'm not gaming. Just using the phone for Web browsing and reading news etc... You are right it's crazy. I also notice my phone running a little hot. I'm using pure shamu latest rom and Franco 10 default settings. I see that my phone goes in deep sleep as soon as I stop using it for example after I unplugged it at 7:15 am until 8:15 the phone was still 99%. As soon as I started reading the news I saw the battery dropping really fast.
[Nexus 6  Original Android Development] Tzfardaya:
Grab a system monitor and track what cpu freqs your phone is using while you're browsing and the like..

Also, what apps (specifically) are you using at that time? Sounds like something is ramping up the cpu speeds and not letting them drop back down..
[Nexus 6  Original Android Development] slekkas:
This i actually didn't do. I have all the monitor apps. I'll check it out. Thanks
[Nexus 6  Original Android Development] sn0warmy:
It was my understanding that Franco was telling me not to pair the conservative kernel with 1.7ghz min freq. But that using interactive governor with 1.7ghz min freq would be fine. That's what I did yesterday and all my lag/stuttering is gone.

However, I am seeing significantly more battery drain. I'm at 82% right now with very light usage since taking the phone off the charger 2 hours ago. I'd typically be at 92%-95% remaining right now and would retain over 80% battery left when leaving work 7 hours from now . So while the stuttering is gone, the battery is draining way too quickly. Which has me thinking that's what Franco meant all along.

I think that was me. We did get a setup working well but after a day or so all the stuttering came back and half the screen stopped turning on from time to time.

I did this in the Vomer app while I had interactive kernel and min freq set to 1.7ghz in the franco app. It lead to an inactive display and a reboot. I'm not going to revert all my kernel settings to stock and try that dynamic Vomer setting to see what happens.

I'm not giving up just yet but all this seems to be way to much of a pain simply so I can get a non-stuttery phone with RGB color setting options. I'm getting closer and closer to just sticking with the stock kernel and stock crappy screen color settings. It looks like I can only get one or the other, at this point. :(
[Nexus 6  Original Android Development] Tzfardaya:
Stock kernel is tuned aggressively for smoothness in the UI (performance) ... Third party kernels are generally tuned for better battery life.. It is possible to tube Franco to eliminate any stuttering you see, but there will likely be a battery life hit because of that... What you need to tune is the governor so it ramps up higher/faster than Franco's default and sits there longer, but is still able to drop down into the lower freqs when screen on idle....

Try decreasing your min cpu freq to where the stutters are barely noticeable for you and see if that helps with the rapid drain.. (1.7 is very high for a min freq)
[Nexus 6  Original Android Development] sn0warmy:
Right now I'm testing stock settings with input_boost_freq increased from 1.19 to 1.7 to see if that helps eliminate the stuttering/lag I see after initially turning on the screen and unlocking the phone. For me, that seems to be where it is the most noticeable. Once the screen is on and I've done a couple of taps/gestures, the lag goes away. It's mainly just the initial lagginess.
[Nexus 6  Original Android Development] simms22:
i personally hate animations, and have kept them off 100% of the time on any nexus that ive owned. since i disable the animations, the "stuttering" thats reported i never see. if you do have stuttering, try disabling the animations.
[Nexus 6  Original Android Development] blueren:
but... but... Lollipop is all about animations!
[Nexus 6  Original Android Development] Tzfardaya:
No, lollipops are all about sweet sugary goodness...
[Nexus 6  Original Android Development] simms22:
lol!

functionality versus animations.. to me lollipop is about android, not animations. animations just confuse many, since they can look pretty :)

---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------

thats what i was going to say :p
[Nexus 6  Original Android Development] Krunk83:
So far so good with these settings and vomer app set to dynamic and Franco performance profile set to balance.

Nexus 6
[Nexus 6  Original Android Development] sn0warmy:
Let me know how your battery drain is with interactive kernel and min cpu freq set to 1728. Mine was draining super fast.
[Nexus 6  Original Android Development] anuragvivek93:
Why always it's pulling my cpu frequency to 1574mhz :((
[Nexus 6  Original Android Development] wrongway213:
Ever see any issues? I've hear some people say disabling causes problems and so they just go .5x. Also, is this just a habit for you at this point, or did it seem to make a difference even on the N6? I've been reading about this a little as I had no clue what you were talking about at first and it sounds as if this little "trick" could make an N4 do a total 180, but that on a powerful phone like this it wouldn't do much, curious as to what you experience with that has been. I don't have any stutter, but then again I was happy with r8, yet I'm happier on r10, so nothing wrong with making a good thing better.
[Nexus 6  Original Android Development] Tzfardaya:
How are you checking and what are you doing at the time?
[Nexus 6  Original Android Development] simms22:
well, it started on the g1. disabling animations have always made it seem faster. then over time, it just became a habit of mine. but on every device ive owned, even on the n6, it really "seems" faster this way(as it doesnt waste time on animations. i say seems because in reality, it probably isnt faster, but it actually turns out faster since its not running the animations. if that makes any sense. all i can say is try it, after a few minutes you will know if its for you. btw, no issues disabling animations.
[Nexus 6  Original Android Development] Krunk83:
So far today.

Nexus 6
[Nexus 6  Original Android Development] anuragvivek93:
Checking through fku app.. Just chatting on Whatsapp.. I sense sluggishness, when I check it's 1574 :(
[Nexus 6  Original Android Development] wrongway213:
So that's your max cpu? Is your min 300? Are you running any scripts, VomerTweaks, etc?
[Nexus 6  Original Android Development] Tzfardaya:
Been a while since I've gotten to say this.. Is your phone thermal throttling? Use a system monitor to track cpu usage up to where it starts feeling sluggish... Does the phone feel warm when it's sluggish?
[Nexus 6  Original Android Development] anuragvivek93:
yes min 300. No scripts.. I was using vomer tweaks.. But I deleted the folder weeks ago.

When battery reaches 16 17.. It becomes sluggish.. Then after that during charging also it's sluggish.
[Nexus 6  Original Android Development] Tzfardaya:
Charging would likely be thermal throttle... Not sure why a low battery condition would, unless you have apps that switch to a battery saving profile automatically...
[Nexus 6  Original Android Development] anuragvivek93:
How to take care of thermal throttle?
[Nexus 6  Original Android Development] Tzfardaya:
Thermal throttle is there to help protect your device... Overheating bad for an electrical circuit... You can underclock and not let the cpu ramp up as high, this helps limit heat, undervolting can as well (but I *strongly* recommend against uv) raising the thermal limit in fku will allow the device to get warmer before it throttles....
[Nexus 6  Original Android Development] wrongway213:
You asked and got a response from Franco himself a while back - this is supposed to happen when your battery is low.
[Nexus 6  Original Android Development] __NBH__:
Just wanted to say r10 is running very nicely on SlimLP using Vomer's dynamic setting.

I unplugged the phone on Wednesday morning at 5.45am, went through my normal work day of Facebook, messages, XDA forums, listening to music with Poweramp for about 1.5 hrs then a bit of YouTube on wifi when I got home. By 11pm it was down to 68% and I left the phone not charging overnight, woke up at 5.45am today and it was on 64% (so only 4% drain overnight). I have had another day of similar usage at work and it's currently at 34% with 3hrs 15 mins screen on time and time off charger of 1 day 12 hrs 45 mins.

This is with sync on, location on battery saving, Google Now and location reporting off, adaptive brightness and ambient display on with brightness slider in the default middle slider position and I Greenify some apps that keep running like Facebook, Messenger etc. I have frozen Hangouts.

I have had sensor_ind wakelocks but they didn't seem to affect the battery. Seems like others are having big problems with it but mine went up to 50 minutes the day before I charged my phone and the battery life was still good. I never change my display settings, one day it was 50 minutes, the next day its 1 minute sp I'm not so convinced it's related to the display.
[Nexus 6  Original Android Development] simms22:
when your battery goes below 20%, your cpu speed automatically gets reduced to 1.7ghz. but should go back up after going over 20% battery.
[Nexus 6  Original Android Development] anuragvivek93:
I'm even getting at 40 - 50% while phone is getting charged.
[Nexus 6  Original Android Development] simms22:
shouldnt be then, not from the battery at least. do you have mpdecision enabled? which version kernel?
[Nexus 6  Original Android Development] Tzfardaya:
Could be the rapid charger heating the battery, board, and chips to the point of thermal throttle...
[Nexus 6  Original Android Development] big_adventure:
Running those settings will be smooth as hell, but it'll kill your battery. You are preventing your phone from ever running at low power gated levels when it is awake, screen on or off.

I would set JUST the touch boost (input_boost_freq) to 1.7 (instead of 1.2) and see how that goes. Setting the overall CPU min to 1.7 is battery suicide.

To understand - input_boost_freq is the level the CPU goes to as soon as the screen detects a touch. This is the main way the much-discussed "Project Butter" dealt with UI lag - instead of waiting for load to drive the CPU up, it just instantly maxed the CPU on any touch event, then ramped it back down. Franco (and other kernel folks) get a lot of battery advantage by reducing touch boost down to a level that still handles smoothness for most people, but which lets the CPU, memory and bus stay in lower power states unless needed. So if your phone is slower than you'd like reacting to an initial touch event, try boosting that first.

Boosting min CPU to 1.7 is like dropping a nuke on your garden to kill a few weeds. Sure, it'll kill the weeds, but it'll also blow up the neighborhood. It's drastic overkill.

---------- Post added at 09:22 PM ---------- Previous post was at 09:21 PM ----------

If it's on the turbo charger, you are, as stated above this, perhaps overheating. Try checking temps in a suitable app.
[Nexus 6  Original Android Development] Krunk83:
I'll try this thanks. What should I set the min CPU to, stock 300?

Nexus 6
[Nexus 6  Original Android Development] wrongway213:
This isn't an issue for me but I still felt the need to say thank you for such a thoroughly helpful post. It's always nice to see someone go to such effort as to provide that kind of assistance for another user and is just an awesome reflection of the community spirit that XDA is all about.
[Nexus 6  Original Android Development] big_adventure:
I would start with it there - you want the CPU to be able to gate down that low when it's not actively in use. If it can't, it's a cascade effect - it's not just the CPU cores, but also all of the other subsystems (memory, bus, etc.) that consume more power based on internal logic when the CPU is ramped up. So, if you are gaming, it's probably not a HUGE deal - the system is going to be running at high CPU anyway a lot. But if you are reading or surfing, the CPU will spend most of the time at CPU Min - so making that low is important.

But yeah, if I was having stutter, I would start with input_boost_freq, then, if that wasn't sufficient, try load_threshold 0 (keeping 4 cores on at all times).

---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------

Now I'm blushing. Thanks+You'reWelcome. :)
[Nexus 6  Original Android Development] simms22:
i use the temp monitor app. it puts a live cpu temp reading into my status bar, so i always see a live cpu temp. oh, and i always disable thermal throttle as well, as the system keeps a safety shutdown temp, that i adhere to. anyways, i never have seen the cpu temp go high enough while charging to hit throttle temps. but, it is still possible.
[Nexus 6  Original Android Development] big_adventure:
I haven't personally seen it either, but I suppose if one was using the phone while on the charger, you could get there. I recall being able to hit throttle on the N5 pretty easily if I did anything graphic while it was charging.
[Nexus 6  Original Android Development] simms22:
yea, thats what i was thinking. like when playing a game or watching a movie. i also kept my n5 with thermal throttle disabled all the time. i remember watching a movie, when plugged in, and its cpu temp got to about 93C before i unplugged it. well above thermal throttle temps!
[Nexus 6  Original Android Development] big_adventure:
Yup, the N5 was quite the hand warmer if plugged and used to the limits. :)
[Nexus 6  Original Android Development] wrongway213:
The very first time I charged my N6 it got HOT, like how a PS3 does when you leave it on too long. I thought my phone was defective and I was gonna have to take it back lol, never done it since.. also haven't ever used it stock since. I really wonder if my phone was doing what you guys are currenty referring to: not familiar with thermal throttle or charging's effect on heat, but this conversation definitely makes me wonder if that's what I was experiencing. My phone has never even gotten abnormally warm since.
[Nexus 6  Original Android Development] Krunk83:
Great, thanks. I don't game much. Mostly chats, forums, news, social apps, and texting. I'll try this setup with vomer dynamic. Then I'll try performance.

Nexus 6
[Nexus 6  Original Android Development] big_adventure:
My N6 got really hot on charge one time and one time only - it was plugged into the turbo charger, which can prevent deep sleep since there is a program that runs a wakelock. And it was one of the times I experienced the no-longer-present bug where my phone got stuck with a CPU Min of 1.7ghz. So it was sitting there, awake and therefore stuck at 1.7, for more than an hour on the turbo charger. I didn't bother checking the temp - but it was hot to the touch. I opened BBS, checked CPU States, noticed that it had been at 1.7ghz minimum since boot (2 hours), changed the setting down and unplugged it.
[Nexus 6  Original Android Development] funcrusher:
When you get a chance, try LK v1.10.1 - want to see if it fixes your issues like it did mine. Not trying to get you to leave FK, just hoping it fixes that stutter issue! He reverted an early commit.
[Nexus 6  Original Android Development] wrongway213:
Is that possible on stock or only with the min sticking on a custom kernel? That's exactly what I experienced, but it was before I rooted so no BBS or stats checked, was using turbo charger though. Interesting either way.
[Nexus 6  Original Android Development] big_adventure:
Go for it, but honestly, I'd try changing one thing at a time.

I would do it like this:

Disable VT, clear FKU data, reboot.

Set input_boost_freq to 1.7ghz or something.

Test. If you get stutter, perhaps try forcing 4 cores with load_threshold 0. If you don't, go ahead and load up VT to whatever mode you want. But beware, VT is going to change the settings you put into the kernel, so I don't know that it's going to "respect" your manual input_boost_freq.

Test again. If you like it, and it's giving you good battery and performance, stick with it.