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

Can you take a look at the following link. It might be the advanced color/gamma settings we have been waiting for!

http://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
[Nexus 6  Original Android Development] 6-speed:
All is good here with r15. All cores seem to function like they should. The releases keep getting better for me. Thanks Franco!
[Nexus 6  Original Android Development] franciscofranco:
I know that by default we boot with Performance governor and then sometime down the road we change cpu0 to interactive to set up some permissions, and then after boot is completed we change entirely to interactive (this is stock behavior). What's really odd is why does it stay on Performance for cpu2 and 3 since I'm changing to conservative early on the boot process. When you mean reverted thermal commits is reverting the latest thermal commit on r15? I'll take a deeper look, this seems like a good lead.

EDIT: it should not happen anymore with the attached boot.img
[Nexus 6  Original Android Development] Jaspah:
Could that theoretically remove the pinkness from the low brightness modes? Curious if it is the actual display or software that is doing that.
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

The 300mhz thing is still happening even with the latest test img you put up not too long ago.. Seems that verry little load goes through cpu1
[Nexus 6  Original Android Development] franciscofranco:
You can't get it to scale over 300MHz at all? I still can't reproduce this, all my cores are scaling normally. What happens when you go to my app, cpu manager and select conservative again?
[Nexus 6  Original Android Development] Arunabh:
Hey you guys.

I've never ever ever really had a problem with Franco's kernels. I mean ever..

Used em on the n4 and now the n6 but this is the first time I've found myself in some trouble.

Before I claim its an issue I'd like someone to confirm if they're having a problem with r15 when the battery's low ?

I had a dozen reboots today when my battery went under 15.

I had 5% battery the phone switched off and when I switched it on again it just switched off and this happened about 3 times.

Then I had my phone reboot in the middle of a call when I clearly had some juice left. And thats also happened a couple of times before this release.

Day before on r 14 I had my phone reboot after I took about 10+ photos.

And since the past two days my WiFi connectivity is ****ed but I'm pretty sure that's a problem on my end.

If anyone could confirm this, it'd be great.

Thanks in advance!

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
You're the first person to report something like this. Without logs it's impossible for me to understand. Are you undervolting?
[Nexus 6  Original Android Development] yoyoz808:
Nope won't go past that. I tried changing governor and other things but the only thing that will get it back to normal is changing the max freq and back..

Think I need to wipe app data?
[Nexus 6  Original Android Development] raghavmax:
I can confirm the phone rebooting while on low battery

Using r15
[Nexus 6  Original Android Development] schizophrenia:
My phone shutted down itself at 5% too an hour ago and I was on r15 and it did not happen before when I was on stock kernel for the first few days. But i can't think of a reason why would kernel affect it. hmm
[Nexus 6  Original Android Development] stas333:
i do not have any pinkiness no matter how low i go in both brightness modes.

On the other hand, I noticed that cpu 3 and 4 get stuck at full power at times while cpu 1 and 2 are fluctuating at much lower frequencies. A restart fixes the problem, but then after sometime cpu 3 and 4 do the same thing. Im on r15, undervolted by -25 and max cpu set at 2.3ghz. no other mods.
[Nexus 6  Original Android Development] franciscofranco:
Ok, I guess we really need to run stock thermal configuration, there must be a reason why they underclock to 1.7GHz when the device goes low on battery.
[Nexus 6  Original Android Development] franciscofranco:
Does this happen with r13?
[Nexus 6  Original Android Development] yoyoz808:
I'll give it a try and report back.
[Nexus 6  Original Android Development] franciscofranco:
**** it, try the attached boot.img :)
[Nexus 6  Original Android Development] Arunabh:
Hey thanks for the quick reply.

I'll be honest here.

I've had your kernels running on two phones and never ever had a problem, not even when everyone else seemed to have them.

The point I'm trying to make is I've never had to grab a log so I don't know how to grab one. But I'll just check on here on how to go about it. So, sorry I guess for no logs.

I'll send you one asa I have a problem again.

Also, on r15 my phone seems to heat up more than normal while charging. Just charging. And since you integrated your thermal driver in the last update I think it might have something to do with that?

And I'm running stock(encrypted) with fk. That's it!

Also I've had the same apps and everything's the same as what I had on previous versions with no problem.

Just basic apps. No fb twitter sort of crap. No stupid apps. Just some normal basic stuff.

Edit: oh yeah, No undervolting. Stock kernel settings.

Sent from my Nexus 6
[Nexus 6  Original Android Development] trailblazerz11:
Reverting 'msm: thermal: stay throttled for at least a full 1 second to prevent' did nothing

Revert 'msm: thermal: use my simple thermal driver ' and the issue goes away for me.

Thanks! I'll try it out.

EDIT: No locking with that boot.img, Thanks!
[Nexus 6  Original Android Development] rampino:
for some reason my ambient display doesn't work anymore since I use r15.. anyone else? :o
[Nexus 6  Original Android Development] flar2:
[MENTION=3292224]franciscofranco[/MENTION]

Did you try increasing the startup delay of mako hotplug?
[Nexus 6  Original Android Development] schizophrenia:
not me, ambient display works fine here on r15
[Nexus 6  Original Android Development] franciscofranco:
Nop, it starts up 20s after boot. But I guess I can start it after the device boots up completely, I don't see a problem in that :)
[Nexus 6  Original Android Development] franciscofranco:
It works fine any release.
[Nexus 6  Original Android Development] slekkas:
Maybe it's not kernel related but since I'm spending most of my time in this thread maybe someone can help me. Since I installed r15 my phone shuts off at 17% battery. Is there something I must do?
[Nexus 6  Original Android Development] erraggy:
Read back a few posts as this issue is not only being discussed, but actively worked on as well. You may be able to provide more information that can help.
[Nexus 6  Original Android Development] cobyman7035:
R15 and vomer dual seems less laggy then r14
[Nexus 6  Original Android Development] franciscofranco:
Flash this in the mean time until I finish r16 properly.
[Nexus 6  Original Android Development] Tzfardaya:
Is it a kernel glitch, or just bad battery calibrations?
[Nexus 6  Original Android Development] Arunabh:
Btw, I've also noticed that r15 is a little laggy. there's lag in scrolling, transitions and generally the performance isnt what we're used to!

Sent from my Nexus 6
[Nexus 6  Original Android Development] zephiK:
Probably related to the thermal configuration, https://github.com/franciscofranco/Shamu/commit/0ca4e0d63d37546aa38070c614f63f96ea83f451
[Nexus 6  Original Android Development] slekkas:
Its the first time I missed a few pages due to work... I've noticed that when I installed one of the previous versions don't remember exactly which one it started doing this at around 7%. After I updated to this version it started at 17%. Strange.
[Nexus 6  Original Android Development] franciscofranco:
I have absolutely no idea. I'd say there's some issue with the regulator or voltages when it's low on battery (Qcom does some shady stuff with rails voltage on their msm_thermal.c driver). I'm guessing though.

I don't know what you're using to determine that, but it doesn't look like that to me at all. I'll monitor it though.
[Nexus 6  Original Android Development] yoyoz808:
Okay so it seems the last boot.img you had me try worked. Haven't had any problems yet and normally would of happened a long time ago.
[Nexus 6  Original Android Development] franciscofranco:
Yeah figured so!
[Nexus 6  Original Android Development] yoyoz808:
Bad news... It did again! Wtf! It might start doing it because I have some governor control settings tweaked... It might just be a coincidence and just started happening at that time. Its so random...
[Nexus 6  Original Android Development] franciscofranco:
Now I'm seriously doubting that it's something that I've done. What governor settings are you using?
[Nexus 6  Original Android Development] badpanda:
I'm having random shutdowns on r15 for the first time.

Is weird but the log is empty right before shutdown...
[Nexus 6  Original Android Development] yoyoz808:
That's y I think your code is last on what could be the problem. I change freq_step = 10 and input boost duration = 20000

It happened to me on the default settings before but like I said its random times it happens...

Lemme keep testing on default settings again and change those governor settings after
[Nexus 6  Original Android Development] holeindalip:
I have no issues whatsoever with r-15, everything works as it should. Something wrong on your end??
[Nexus 6  Original Android Development] Ladduro:
Any battery changes in r15? My battery is lower than normal for this time a day.
[Nexus 6  Original Android Development] franciscofranco:
Nop.
[Nexus 6  Original Android Development] omer1112:
Getting mad battery issues with Chroma rom. Phone seems to drain battery non-stop whether its on or off. Not sure why! Might have to switch roms, if its not the kernel. But Chroma is designed to be used with franco kernel!
[Nexus 6  Original Android Development] franciscofranco:
Look, install BBS and check which apps are keeping your device awake. It's not about the rom or the Kernel specifically. There's no "rom designed for X or Y Kernel", they all work together the same way. Fix your apps, and you'll be fine.
[Nexus 6  Original Android Development] pantmunu:
Anyone having battery issues .. Try to go clean at least once a while and try to check if something else is eating up your battery. BBS is pretty damn good. Try it. Thus kernel in particular has been really good to me. And others too. Best of luck. Flash away !!!
[Nexus 6  Original Android Development] codygs83:
Had a buddy with a serious battery drain problem. Moto is notorious for battery calibration problems. Let it drain to zero. It might sit at 1% forever. Then recharge to full. Hopefully this helps
[Nexus 6  Original Android Development] warrenis1234:
I'm not sure why people have a problem with this, I always thought it was a feature since I've been using apps to achieve this on my past devices. it's good for eye and sleep health, a lot of research done on it
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

I think that was the problem. I guess it didn't do it on default settings and started doing it when I change those governor control settings to those values I mentioned earlier and will get stuck like that. My fault on that is that a bug on the app or is it my values that I'm using is no good?
[Nexus 6  Original Android Development] CRXed:
Question: I am on stock Rom with Franco kernel (r15) with default settings on Balanced Profile and I noticed that core 1 and 2 scale through all frequencies pretty fast up and down, but core 3 and 4 are either at 2.6 or offline, with no frequencies used in between.

Is this intedend?
[Nexus 6  Original Android Development] franciscofranco:
Nah, not a bug on the app, the app just sends the values to the Kernel. I'll try to reproduce. freq_step 10 and input boost duration 20k?
[Nexus 6  Original Android Development] franciscofranco:
Nop, it's a bug. Fixed on soon-to-be pushed r16.
[Nexus 6  Original Android Development] yoyoz808:
Yup
[Nexus 6  Original Android Development] franciscofranco:
I'll try to reproduce after pushing r16. I need to push Mako and Flo FK updates too.
[Nexus 6  Original Android Development] suku_patel_22:
Was that 3rd and 4th cote stuck at max freq fixed? I had that issue today. I was not doing anything special. Just some twitter and all.

Travelling at the moment so haven't checked the thread a lot.

It is at 2.3 because I have set max freq to 2265

After changing governor to performance and back to conservative, it was back to normal

Sent from my Nexus 6
[Nexus 6  Original Android Development] trailblazerz11:
Out of curiosity did you figure out why it was happening? I see in your latest commits you just reverted to stock thermal.

Yeah see post above, r16
[Nexus 6  Original Android Development] hdtechk:
Change governor to interactive and problem went away then back to conservative still good
[Nexus 6  Original Android Development] trailblazerz11:
Issue was core 3&4 for some reason were using performance governor. Just setting the governor will fix it. Even setting conservative while using conservative.
[Nexus 6  Original Android Development] franciscofranco:
Get r16, it's up.
[Nexus 6  Original Android Development] suku_patel_22:
Couldn't have come at a better time. Train has halted at a station and I am getting constant 30KBps on 2g :D

Sent from my Nexus 6
[Nexus 6  Original Android Development] yoyoz808:
No problem. I know you got many devices to upkeep. So far default values is okay but when changing those values on governor control, the problem comes up for me anyway.
[Nexus 6  Original Android Development] stas333:
the big fix is for cpu 3 and 4 right? the description says 2 and 3
[Nexus 6  Original Android Development] holeindalip:
They start @ 0. Cores 0,1 2,3
[Nexus 6  Original Android Development] Janzen254:
That is just what the app labels them. The kernel sees it as cpu0, cpu1, cpu2, cpu3
[Nexus 6  Original Android Development] stas333:
Got ya
[Nexus 6  Original Android Development] Tzfardaya:
Franciscofranco, looks like disabling the host wakelock might be affecting some incoming calls... Not sure why it wasn't posted here to begin with..
[Nexus 6  Original Android Development] franciscofranco:
Well, good thing I leave it enabled by default :)
[Nexus 6  Original Android Development] duminduweera:
I was seeing why my phone is a bit laggy, and it seems that cpu1 is stuck at 300mhz.

Im on R16.

I have very little knowledge on how to grab a log, if you can let me know what you want me to get, i can google on how to get it.

Ive added a screenshot of the application to show the kernel setting that i've changed
[Nexus 6  Original Android Development] Tzfardaya:
I don't see anything that would lock cpu0 at 300, but... Why do you have fsync disabled.. And maybe lower the thermal threshold a bit...
[Nexus 6  Original Android Development] duminduweera:
I read somewhere that it can give you a little performace boost with possible data loss.

So i did it, and haven't had any issues.
[Nexus 6  Original Android Development] yoyoz808:
Did u by any chance change anything in governor control settings like freq_step?
[Nexus 6  Original Android Development] monkboy24:
Just installed r16 and everything seems to be on point so far. No CPU apps used just flash and live. In Franco we trust!
[Nexus 6  Original Android Development] duminduweera:
Nope, the only settings ive changed are in that screenshot.

---------- Post added at 05:09 PM ---------- Previous post was at 05:08 PM ----------

I dont seem to have any issues though, weird [emoji14]
[Nexus 6  Original Android Development] italia0101:
Care to elaborate? I've been running it for 3 days without an issue, incoming calls have been fine for me?
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

I narrowed the problem with the 300mhz feq being that the freq_step value being changed to 10 it gets stuck. I tried it using 7 as the value and no problem. Although another user mentioned not touching governor settings and still getting that problem....

Edit: tried 9 and getting stuck....weird...
[Nexus 6  Original Android Development] madphone:
same problem here: first core stuck at 300 MHz. Hadn't had any problems with one of the boot.img before r16. now the phone lags a lot. didn't change any settings but color profile.
[Nexus 6  Original Android Development] schizophrenia:
Same problem. First core stuck at 300. R16. Very laggy now
[Nexus 6  Original Android Development] suku_patel_22:
For those who have core0 stuck at 300, please share what settings you changed.

I am running stock r16 and have no such issues

Sent from my Nexus 6
[Nexus 6  Original Android Development] schizophrenia:
Stock r16 without any modification whatsoever. And the "stuck" did not happen until some hours.
[Nexus 6  Original Android Development] big_adventure:
As a counterpoint - I don't see 300 stuck at all, and never have. I've had r16 running since 7AM (it's 1:13PM), and all cores are scaling perfectly.

Conservative governor

load_threshold 0 to force 4 cores on

Colors changed, charge LED off are the only other kernel mods
[Nexus 6  Original Android Development] SmokeyMon:
2 days here. I also have not noticed an issue.
[Nexus 6  Original Android Development] boysetsfire:
I had CPU 1 stuck at 300 too, but problem went away after clearing FKU data and rebooting. Everything's good for now ?

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] duminduweera:
Yes, it a lot worse now, I had to change the governor about 5-6 times during the last 3 to 4 hours back and forth because the cpu1 gets stuck at 300mhz.
[Nexus 6  Original Android Development] biggiestuff:
Oddly ever since I reported my issue I haven't had it happen again. I feel like the boy who cried wolf. I went ahead and updated to r16 anyway and it hasn't crept up. My fku settings are just the default except for turning off the charging led. Hopefully everything is good now. "Knock on wood back cover"
[Nexus 6  Original Android Development] Jaspah:
How would you know? ;)

No, but really... that's why I'm not a fan of just disabling wakelocks that affect your connectivity. It may not affect your particular situation, but it could affect other carriers or bands. Does disabling that wakelock even make a difference in battery? Has anyone tested it? So many questions for what I think at this point might even be a placebo.
[Nexus 6  Original Android Development] franciscofranco:
Sorry guys at this moment I have no clue why that is happening, it doesn't make sense and I can't reproduce. I'll try to figure it out... somehow.

Saying "omg lag 300mhz stuck" doesn't help me at all.

If it happens again, can you please check /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and tell me the output please. Thanks.

Try the attached boot.img.
[Nexus 6  Original Android Development] Arunabh:
Maybe chill out, have a beer, go back to r10 and start over eliminating possibilities for this ****up.

Haha.. I remember your post on g+ when you you were like what else do we do to make the n6 better. R10 was that perfect.

But r16 seems to be fine so far.

Haven't yet experienced the 300mhz bug. Let's see!

Sent from my Nexus 6
[Nexus 6  Original Android Development] beerbaronstatic:
I started having the issue as well, stock ROM, default settings for everything. It seems to happen after the phone is allowed to go to deep sleep, a reboot fixes it temporarily but if I let the phone sit it comes back. Trying the new boot.img, will let you know.
[Nexus 6  Original Android Development] paychex:
Franco. Might it have something to do with hotplug threshold being so high. Either way, what's the reasoning behind the high value?
[Nexus 6  Original Android Development] franciscofranco:
No, it has nothing to do with that.

Because conservative polls every 10ms and updates the struct policy util value every 10ms so when I poll every 100ms when deciding what to do with the CPU cores the util value can be sometimes higher as it picks up any spurious load spikes much easier. To counter that, I raised the value so that cores don't go crazy online/offline.
[Nexus 6  Original Android Development] android_mp99:
Just noticed this happening to me and the output is conservative. Default everything else except colors and double tap enabled. Will try the boot.img.
[Nexus 6  Original Android Development] Ladduro:
Output is conservative for me as well and cpu0 is stuck at 300. All stock except color.
[Nexus 6  Original Android Development] kxhaz:
I just thought I would check as well and sure enough I had cpu0 stuck at 300 as well. Flashed r16 last night from r15. Stock ROM and all setting are stock except color and having VomerTweaks 2 core.

I switch to interactive for a few seconds and back to conservative and cpu0 started fluctuating.
[Nexus 6  Original Android Development] Circaflex:
is it possible your original issue is caused by VomeTweaks 2 core, whatever that is.
[Nexus 6  Original Android Development] kxhaz:
As other are seeing this same issue (and have not said they were running VomerTweaks) and I have not had this issue running running these since r4 I would say no, but anything is possible. I was just putting out there what I was seeing to hopefully be able to help figure out the issue.

I was not bothering me, but I just thought I would go in and check and see if it was doing it on my phone.
[Nexus 6  Original Android Development] jodvova:
I'm running cm12 and r16. Conservative mode.

Never seen CPUs being stuck at 300mhz. They drop to 300, but as soon as I start moving graphs around immediatly goes up to 2.6ghz
[Nexus 6  Original Android Development] szale9001:
Hmm. In my case cpu0 scales fine from 300mhz. What I have noticed, however, is that cpu3&4 virtually never plug in anymore. In the past, loading a website in chrome, or some other resource intensive task would cause all 4 cores to come online. Now, it almost never happens. I had to lower the load threshold to around 50 to get hotplugging to behave the same way as r15. Can anyone else verify this with stock settings?
[Nexus 6  Original Android Development] Jaspah:
It appears to happen randomly. I was not experiencing issues either until today a few hours after flashing r16.
[Nexus 6  Original Android Development] enzoevo:
Add me to the list of cpu0 stuck on 300. Stock, r16, 4 core always on. Seems to happen after long deep sleep.

Conservative.

Via my CleanROM Nexus 6
[Nexus 6  Original Android Development] jodvova:
I confirm that. I can only enable cpu2/3 if I set hotplug threshold to 40.

Even if I switch to interactive mode, cpu2/3 remain offline with the threshold 80-100.
[Nexus 6  Original Android Development] C00lBeanz:
Your kernel killed my cat again!
[Nexus 6  Original Android Development] franciscofranco:
cpu 2 and 3 come online based on system load, they are working fine.
[Nexus 6  Original Android Development] franciscofranco:
So... if you want your cores to come online more often that's why I export the load_threshold. By default they will come online if there's stress on the system, otherwise they stay put...
[Nexus 6  Original Android Development] akellar:
Still not funny
[Nexus 6  Original Android Development] Mistertac:
What's more troubling is that if I flash this kernel I can no longer play the piano.

[emoji30]
[Nexus 6  Original Android Development] dougiefresh36:
CPU0 stuck at 300mhz. Output: Conservative
[Nexus 6  Original Android Development] szale9001:
Yup, I know. I was more pointing out the change I noticed in their behavior from r15. Noting that they tend to plug less, just in case it was unintended.
[Nexus 6  Original Android Development] jodvova:
del