yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] simms22:
most likely it didnt. when talking about temps, feel is very inaccurate. all feel does is tell you if something is warmer or cooler the temp of whatever you are using to feel. let me explain further.. take 3 glasses of water. fill one up with hot water, another with cold water, and another at room temp. stick one hand in the hot water, and the other hand into the cold water. leave them in there for about a minute. now remove them both and stick them both into the room temp water. the hand that was in the hot water, will feel the room temp water as cold. the hand that was in the cold water will feel that the water is very warm. so, while both hands are in the room temp water, both hands are giving you different answers. why? because feel is just relative to what temp whatever youre feeling with. and to get real temps, you cant use your hands(body).

if your hands are cool, normal temps can feel extremely hot :)
[Nexus 6  Original Android Development] wrongway213:
This is very true and obviously I cannot give a precise or even estimated temperature. That being said, trust me when I tell you it was not relative heat. It wasn't warm, it was HOT: I am actually very surprised there was no CPU damage it was so hot to the touch. I've never experienced that on any phone I've ever owned, only gaming consoles right before they start to get wonky and shut off on their own mid-game.
[Nexus 6  Original Android Development] big_adventure:
Honestly, I can't say. I put FK on the day I got the phone. The only thing I did on stock was the initial setup and syncs. I think that the stuck CPU thing was related to FKU reading the min CPU freq reported in the appropriate device file after it was artificially boosted by thread migration, and then, for whatever reason, freezing that value in place. Franco stopped the thread migration process, and those few of us who saw this issue haven't seen it since. So I doubt it was the exact same situation on stock, HOWEVER, it is entirely possible that your phone got stuck at some too-high frequency for another reason - a runaway app comes to mind. Without logs and precise setup, it's hard to say. Just feel glad that you've not had to deal with it since!

Runaway app example: on the N5, the Uber app was a nightmare for months for me. After opening it, it would lock running, even if switched away - in fact, even if swiped out of the Recent Apps list. I would have to call my car, receive my car, then remember to go into Settings > Apps > Running and manually kill it there, or it would eat a full battery in a couple of hours.
[Nexus 6  Original Android Development] :
Does anyone have any suggestions for a per app mode for low power games? (e.g. clash of clans) I checked the per app modes thread, but it looks like it hasn't been touched in awhile.
[Nexus 6  Original Android Development] franciscofranco:
Uh... update your Google Play Services?

Don't mess with the GPU governor, let it be.

Uh... I can change GPU freqs just fine...
[Nexus 6  Original Android Development] zephiK:
Thats why Franco Kernel Updater doesn't let you see GPU Governors. The best GPU governor is simply the one that is defaulted simply because its a good balance between battery and performance. The only thing you need to change is the frequency and then you can up the frequency with Per-App-Modes.

Using other kernel apps doesn't ensure compatibility with the kernel. Stock GPU Governor is msm-adreno-tz.

Changes for me using FKU.
[Nexus 6  Original Android Development] abjexstallion:
My Shamu has been sprinkled with Franco Loooove!!! BTW, how's color profiles working? Meaning, is there gonna be profiles as [MENTION=1363323]vomer[/MENTION] used to post back on mako's and hammerhead thread! Sorry for my noobness, it's been a while since my last Nexus(5 months now) ...
[Nexus 6  Original Android Development] Pilz:
It changes now but you have to go back then open GPU freq again and it shows the applied setting.
[Nexus 6  Original Android Development] zephiK:
Color Control is very limited at the time being, only RGB is available and not gamma. Gamma Controls will be further down the line (hopefully),

230/230/255 (extra cool)

237/235/255 (cool temps)

are some good RGB values to use :D I personally prefer 230/230/255 as it makes whites look less yellow on low brightness.
[Nexus 6  Original Android Development] vomer:
Basic "cooler" colors are enabled in the n6 vomertweaks already. Just RGB for now.
[Nexus 6  Original Android Development] InGeNeTiCs:
Aw bummer. No worries though. Even if it shows up in r10, at least something will be done. I love your work.
[Nexus 6  Original Android Development] owyheendn:
Can i Just Flash this Over my LeanK??
[Nexus 6  Original Android Development] oak:
Yes
[Nexus 6  Original Android Development] occtec:
I find RGB values 243/246/255 to have a more brighter white effect, not sure if it's just my eyes, but seems to cool down the tint but still get pop of colors ? just my two cents worth anyway. Try it out for yourself and see what you think..

---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------

What values do you use?
[Nexus 6  Original Android Development] Zenzr:
Testing out these settings. Seems good so far. Thank you!
[Nexus 6  Original Android Development] zephiK:
Vomer doesn't have a N6 :p
[Nexus 6  Original Android Development] nhpctech:
Rocking 230/230/255 and loving it. I really like the Franco App, makes adjustments and flashing updates a breeze.
[Nexus 6  Original Android Development] wrongway213:
It amazes me how some of the people on here can develop blind... talk about talented
[Nexus 6  Original Android Development] zenxaero:
Can someone post a mirror of VomerTweaks because it keeps saying the webpage is unavailable
[Nexus 6  Original Android Development] umair shaikh:
So now i can flash r2 over resurrection remix right ??? Am currently on lean kernel...so should i flash stock kernel first or just flash r2 over lean kernel ??
[Nexus 6  Original Android Development] wrongway213:
Just flash
[Nexus 6  Original Android Development] zephiK:
Eh, vomer has people helping him (like myself) out with the system paths and testing the settings before it's pushed out ;)

Works fine just here.

http://xdaforums.com/android/software-hacking/vomertweaks-perfect-balance-performance-t2873369

http://192.227.135.147/get/VomerTweaks/francokernel/tweaks/

No need to do anything fancy. Just flash Franco r2 zip and thats it. No wiping or any of that needed
[Nexus 6  Original Android Development] occtec:
Just wondering if anyone has the combination of r2 and lightflow. Since I've installed and configured both around the same time I have noticed that my incoming calls and notification sounds now increase in increments whereas before on r1 with lightflow installed but not configured I didn't have this issue. Has anyone else noticed this same behavior? I don't have sound configured in lightflow, it is disabled...
[Nexus 6  Original Android Development] franciscofranco:
The Kernel doesn't touch your notification sound.
[Nexus 6  Original Android Development] Tzfardaya:
The basics of those Pam settings haven't changed, true, they haven't exactly been updated for the n6, but they'd still be a good starting point to tweak your own..
[Nexus 6  Original Android Development] :
Would the settings still be similar now that the default governor is conservative?
[Nexus 6  Original Android Development] simms22:
well, the phone can handle 100C very easily. when it hits 100C itll shut itself down to cool itself off. temps below 100C are safe for the device to run, even if it feels extremely hot.

btw, for those curious. 100C is the boiling point of water, at sea level :)

oh, and sorry, but im out of thanks.
[Nexus 6  Original Android Development] wrongway213:
Yeah, I am definitey glad it's no longer an issue for me.. figured while all this knowledge is being dropped I may as well learn a thing or two though :p This thread is awfully informative as it brings so many different types of users from so many different ROMs together, I always either learn something or enjoy the OT when I come in here.
[Nexus 6  Original Android Development] Tzfardaya:
Yes.
[Nexus 6  Original Android Development] wrongway213:
WOW - would never have guessed this phone could handle boiling temperatures, that is absolutely insane. I suppose I have no reason to be surprised no damage was sustained.. when I touched my phone it felt like the top of a car that's been sitting out in a summer day maybe, didn't burn me though haha

No worries, I'm out of thanks too :p
[Nexus 6  Original Android Development] Tzfardaya:
The phone likely can not... The cpu however, can... Most CPUs can handle that temperature (although it's always better not to get them that warm very often..)
[Nexus 6  Original Android Development] wrongway213:
Haha yeah, for the record I am aware the phone itself would not react well to being boiled:p

I had no idea the CPU could sustain that level of heat though. I wonder if PS4s and Xbox Ones can be left on all day all night with no heating issues... I remember CPU heat issues mainly from playing video games growing up and last I played (PS3) it could still be an issue I thought... interesting how (and in what sometimes seemingly bizarre ways) that technology evolves. Again, sorry, out of thanks, so please accept this written thank you, lol.
[Nexus 6  Original Android Development] Tzfardaya:
Iirc CPUs have always been able to handle that temp... It's the other components in the systems that can't...
[Nexus 6  Original Android Development] simms22:
not about how often you get it hot. as im known to get all my nexus devices hot, all the time. its not a good thing to get that hot for long periods of time. as short periods wont damage the cpu. a long time at 97C might eventually cause somekind of damage(or not).

i think its the galaxy nexus that had the 110C shutdown temp, and no thermal throttle :)
[Nexus 6  Original Android Development] sn0warmy:
OK, I give up. My phone is just destined to remain on the stock kernel, unfortunately.

I've tried absolutely everything, including many various kernels, governors, governor tweaks, forcing all 4 cores to always be on and other tweaks people recommend. Nothing freaking works for me. Most recently I tried simply running r10 with nothing changed except input_boost_freq increased from 1.19 to 1.7. It solved the stuttering/lag without draining battery. However, In the past 2 hours I've run into half my screen not turning on/responding 3 times. So I resorted back to the standard 1.19 input_boost_freq and rebooted, keeping it to 100% stock franco settings. Within 5 minutes of doing that half the screen was unresponsive again. :mad:

I'm beginning to think my phone has a defect of some kind. It's just so strange to me because the stock kernel is flawless. I really don't get it.
[Nexus 6  Original Android Development] funcrusher:
Check your PM, please.
[Nexus 6  Original Android Development] Tzfardaya:
Try stock again and see if its still error free...
[Nexus 6  Original Android Development] sn0warmy:
I'm on it now. Absolutely no issues...
[Nexus 6  Original Android Development] twcobra:
I had similar issues on my old S4. I got it going by backing everything up on my computer. Doing a complete format of data, Unrooting and going back to stock. Then start over with the root process. Its a bit of a pain but if you have tried everything else its worth a shot on the N6. Later on some good kernel cleaners showed up for the S4 then that would take care of my problems when they arrived. For now there has not been a kernel cleaner for the N6 yet. With all the kernels out there now, I hope someone comes out with a good kernel cleaner. So far for me Franco has been running real smooth.
[Nexus 6  Original Android Development] sn0warmy:
Not to begin a discussion about other kernels in Franco's thread, but [MENTION=710997]funcrusher[/MENTION] pushed me back in the direction of leankernel's latest 1.10.1 release, which was developed to stop my exact problem. I've been running it for about an hour now with no tweaks and it's been flawless with absolutely NO stuttering. I'm going to continue testing it and if by this time tomorrow I have no issues with battery drain or half my screen not responding, it will be safe to say a winner has been found. At least for me.
[Nexus 6  Original Android Development] Damon13:
Hey Sn0warmy, have you tried the power save mode on LK 1.10.1? or any other tweaks within Lkconfig such as CPU boost off. Thanks
[Nexus 6  Original Android Development] sn0warmy:
I haven't messed with anything. I've left all settings stock on 1.10.1 and it's perfect so far.

But let's take this to PM or the LK thread so we don't clutter up Franco's thread.
[Nexus 6  Original Android Development] Krunk83:
I'll try this tonight.

Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Wtf I didn't say that. I said that using 1.7GHz as minimum frequency is absolutely nuts and you'll destroy your battery life.
[Nexus 6  Original Android Development] franciscofranco:
That is interesting and actually pretty concerning. I'll revert the same patch that Imo did.
[Nexus 6  Original Android Development] wrongway213:
Out of thanks for the day but it's cool that you and Imo and a lot of the devs on the N6 seem to work together for these kinds of things... instead of getting mad cuz another kernel is being discussed in your thread you actually take the time to look at what is being said and try to use it if it's something actually significant to improve your work for your users... most devs just get mad. Know it's appreciated.. just in the short time N6 development has been going on we've all seen quite clearly how much better things can be when everyone works together (Netflix and kernels working with theme engine sure are nice), and we all know when you and Imoseyon get to talking we all, whether Franco or LK users, generally wind up getting a better product at the end of it all .:good:
[Nexus 6  Original Android Development] sn0warmy:
That would be awesome. If you want to revert that and create a test kernel I'll be glad to test it for you since I seem to be having more issues with the stuttering than most.

I'm now on 3.5 hours with LK 1.10.1 and it's running 100% perfect. This is the first time I've gone this long with no issues on anything other than the stock kernel.
[Nexus 6  Original Android Development] Krunk83:
This is good news and it's awesome that Franco will implement this if our tests hold up. I'm testing lk as well and it's good so far.

Nexus 6
[Nexus 6  Original Android Development] Janzen254:
For those with stuttering maybe try increasing cpu_boost durations and/or frequencies, and try lowering governor and hotplug load thresholds.

Like Francisco Franco said, setting your min freq at 1728000 is just nuts.
[Nexus 6  Original Android Development] Janzen254:
What is being reverted?

This? https://github.com/imoseyon/leanKernel-shamu/commit/014a1ef
[Nexus 6  Original Android Development] anthonyg45157:
Couldn't agree more with this statement! Working together has a much better outcome in the end! :thumbup:

Sent from my Nexus 6
[Nexus 6  Original Android Development] sn0warmy:
Thank you sir. I'll test it and report back tomorrow with results.
[Nexus 6  Original Android Development] letdatbassknock:
Nice work as always Franco. Used your kernel on my N5, and now on my N6. Keep up the good work. Also, does anyone know the terminal code to enable DT2W feature?
[Nexus 6  Original Android Development] Tzfardaya:
My turn

echo AUTO > /sys/bus/i2c/drivers/atmel_mxt_ts/1-004a/tsp

This is what I have in tasker to enable it..
[Nexus 6  Original Android Development] letdatbassknock:
Didn't work.
[Nexus 6  Original Android Development] suku_patel_22:
Applying settings on reboot finally worked for me after I switched to Chroma. Never worked on stock. Such a relief!!
[Nexus 6  Original Android Development] Tzfardaya:
Are you running it as root? It works on my end..
[Nexus 6  Original Android Development] holeindalip:
Works here as well
[Nexus 6  Original Android Development] Janzen254:
Why was /sys/devices/leds-qpnp-f002ee00 changed to /sys/devices/leds-qpnp-f0030e00 ?
[Nexus 6  Original Android Development] Krunk83:
I'll test as well

Nexus 6
[Nexus 6  Original Android Development] DPretzelK:
Hello! I have a problem... I set my CPU to the max value but everytime I reboot the phone it goes back to the default value, the option of apply it after reboot is not working either. :(
[Nexus 6  Original Android Development] big_adventure:
You need to be a lot more precise. Are you talking about the "Max CPU Frequency"?

The default MAX CPU value IS the highest MAX CPU value. If you are seeing a different value there it is because you are:

1. Thermal throttled

2. Running with very low battery

3. Running a script like VomerTweaks that changes that value on its own.
[Nexus 6  Original Android Development] DPretzelK:
That's strange... I'm talking about that, the Max CPU Frequency! Mine is always on the 1,7## and if I change it manually it displays that is changed but when I refresh that part (by going to another submenu or close and open the app) the value is back to 1,7##! I can't manage how to make it stay at 2,649 MHz... reboot option is not working. :crying:

Note: I'm using xTraSmooth ROM for Nexus 6. :/

Note #2: What you mean by "Thermal throttled"?
[Nexus 6  Original Android Development] suku_patel_22:
Thermal throttled means that after phone reaches a specified temperature, the CPU speed is limited to a value.

The default temperature is 70°C on Franco kernel.
[Nexus 6  Original Android Development] GregNexus:
so this reverted commit means that the stutter for some people (like me with r10), should be gone:confused:

EDIT:

Tried the new release of the lean kernel too. My stutters i had before with r10 were gone.

I'll be back on Francos Kernel later (His test kernel which has been posted today )
[Nexus 6  Original Android Development] Magoggles:
Thank you for your as always excellent work. Just wanted to give another +1 to you ever taking a look at what you can do for the Nexus 9, I need a Franco kernel for every Nexus I own dangit :P.
[Nexus 6  Original Android Development] big_adventure:
What you are seeing is exactly what happens when the phone has hit the thermal throttle limit. The FKU app reads the current saved "Max CPU" from a value saved in a temporary sys file, NOT from the value you have manually set. The kernel will temporarily drop that down to 1.7ghz if the CPU gets hot. You can check this in some applications. A common culprit would be if you are playing a game or running benchmarks or doing anything intensive, especially if you are on the charger at the same time, notice that it looks a bit slower than normal, then go to FKU, you'll see that the Max CPU is listed as 1.7ghz. Check the CPU temp to see if it is high. If it is, that's your issue. You can also just go and set the CPU throttle value to 100C (effectively disabling throttling - don't worry, the phone will automatically turn itself off if it actually gets to 100C). If you do that, and find that the phone stays at 2.6ghz, you've identified the issue.

If you leave your phone idle for a while (OFF THE CHARGER) to let it cool, you shouldn't see this anymore, UNLESS you have another issue that is never letting the CPU rest.

If you confirm that it's temp throttling, and letting it idle for an hour off the charger doesn't fix the issue, you likely have something keeping the phone awake and keeping the CPU screaming. Go into FKU, go to the System Monitor Lite app from the menu, and swipe over to the CPU FREQUENCIES tab. Make sure that the phone is mostly in deep sleep (depending on what I'm doing, I get about 75% deep sleep), and mostly in 300mhz when NOT in deep sleep (I spend between 15 and 20% in 300mhz generally). If you note that it's spending all it's time at high frequencies, well, that's why it's hot. You will need to track down what app is holding it at that temperature.

If you are not thermal throttled and not stuck at high frequencies generally, maybe the data for FKU is somehow corrupted - you could try erasing FKU data. But given where FKU reads the data in question, that's not likely your issue.
[Nexus 6  Original Android Development] Krunk83:
It needs more testing than a few hours. But for me so far so good. I'll use it all day today with stock fku settings and report. Great job [MENTION=3292224]franciscofranco[/MENTION] and thanks for listening.

Nexus 6
[Nexus 6  Original Android Development] ultravorx:
disable charging LED

So ive tried finding an answer, but cant find it anywhere.

Im on chroma using r10 with paid FKU. The problem im having is I need the charging led disabled, but the setting will not stick.

Ive tried fresh installs of FKU, reboots, etc and still have the issue.

I dont need the feature as i have the tylt charger and the geen light blinds me at night!

Any ideas, or is this a bug?

Frank
[Nexus 6  Original Android Development] mr_clean5953:
Did you turn it off in chroma settings under sound and notifications?
[Nexus 6  Original Android Development] ultravorx:
Yes, under notifications, battery light setting is off. And with my other notification lights in chroma, none are configured to green color.

Frank
[Nexus 6  Original Android Development] Krunk83:
Turn the colors in chroma to black. That will fix it.

Nexus 6
[Nexus 6  Original Android Development] MrMaverick03:
Cores staying on...

When using trickster, after the screen has been on for a few minutes, I noticed core 2 and 3 stay locked at 2.6 GHz. Once I turn the screen off and back on these cores shut back down. I am not running any mods or even a custom ROM. I also tried freezing some apps before shutting off the screen and the cores stay on.

No other issues with the kernel. Stand by times are unreal with r10. Thanks Franco

Edit: Figured out it was chrome after some more research. I love Chrome's feature but understand now why it drains the battery so much.
[Nexus 6  Original Android Development] DPretzelK:
The rare thing is that I checked the temperature and the max. value that I've ever got is 42°C. ?

Anyway, I will look into this by checking what you said, thank you. :)
[Nexus 6  Original Android Development] franciscofranco:
Nobody changed anything.

Let me guess, you're below 20% battery or something?

That is when an app is consuming cpu cycles, that's actually the driver working as it's supposed to, more load, more cores.
[Nexus 6  Original Android Development] sn0warmy:
So you're testing Franco's new kernel? If so, I'll continue testing LK 1.10.1 for the rest of today to ensure I give it a full 24 hours.

My initial findings are that this LK is still flawless. Absolutely no stuttering after countless times unlocking the phone and it's been completely fluid in my usage with excellent battery. If Franco's kernel ends up performing the same it'll be great to have 2 perfectly functioning options. :highfive:
[Nexus 6  Original Android Development] MrMaverick03:
Is there anything I can do to stop it from happening? When I switch to another app, let's say email, and the cores are still at full throttle I feel like it is using unnecessary power. I think it is silly to have to sleep the screen every time I stop using chrome but before I switch to another app.
[Nexus 6  Original Android Development] franciscofranco:
Dude you have some app doing heavy background work... what do you want me to do? Developer Options -> Show CPU usage then you'll see which process is ****ing you.
[Nexus 6  Original Android Development] DPretzelK:
Nope... this happens all the time! Even at 100%. ?
[Nexus 6  Original Android Development] franciscofranco:
That can't be possible, there's nothing that changes max frequency unless you're thermal throttled or you're below 25 or 20% I don't remember. Or you have some app/script/whatever ****ing you.