yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] franciscofranco:
I think you were too fast :)

As for the power saving profile I increased the frequency of cpu0 and cpu1 to 1.5GHz up from 1.2GHz, and decreased the frequency of cpu2 and cpu3 to 881MHz down from 1.2GHz, changed hispeed_freq to 729MHz I think too. I wanna see how this works out! :)
[Nexus 6  Original Android Development] ryanallaire:
[MENTION=3292224]franciscofranco[/MENTION], dt2w has disappeared in my FKU2 kernel settings again, is there a fix for when this happens? Thanks for another update too :good:
[Nexus 6  Original Android Development] franciscofranco:
It shows up on mine. Are you sure you have root?
[Nexus 6  Original Android Development] TonikJDK:
Its on mine, and I just tested it and it works.
[Nexus 6  Original Android Development] franciscofranco:
How's r52? I put some good effort into it :)
[Nexus 6  Original Android Development] Prack:
WOAH we jumped from 52 to 92, sweet update skillz yo.

52 seems good, no issues so far. One question though is I'm now using Magisk so I can play pokemon go still and FKUpdater screams the whole time that it doesn't have root. Is there a way to disable that toast message?
[Nexus 6  Original Android Development] pkgnex:
Seems all good here, Franco.

I just run balanced mode, not power saving, so I can't comment on that update. Also, the bump in cpu boost to 1.7 GHz didn't seem to improve performance noticeably, so I personally set it back to 1.5 GHz to save a bit of juice. Coincidentally, I have been running hispeed-freq at 1.2 GHz for some time, so the new default just matches what I have been doing for a while!

Aside from that, my cores 3 & 4 are still off-lining at some point below 40% battery even though I have BCL disabled in both FKU and in a su.d script. I still also have to recharge above 40% AND then reboot to get them back online, which is a bit of a pain. I still wish BCL was just disabled altogether like it was on r48 and prior, but no big deal - I understand that this is stock behavior and that not having BCL caused stability issues for at least one user.

In the meantime... I'm impatiently waiting for Nougat to be pushed "in the coming weeks." and holding out hope that the Nougat franco.kernel install script will say it's installing a virus :p
[Nexus 6  Original Android Development] Neejay:
Great so far! I run the balanced profile. I have to admit, I try other kernels, but I ALWAYS end up coming back. Yours is the ONLY kernel that I never get not even one random reboot. As soon as I get one reboot, it's "welp, back to franco". I think I'm done trying other kernels for a while.

Been using your kernels since my galaxy nexus days. Keep up the good work brother.
[Nexus 6  Original Android Development] TonikJDK:
It seems amazing so far. I am on Power Saving. Used 8 percent of my battery this morning. Normally would have used twice that if not a little more. It says I wont run out for THREE days.

I love you man.
[Nexus 6  Original Android Development] franciscofranco:
I'll check it out!

That's weird because with BCL disabled that shouldn't happen. Anyway, I'll work on it a bit more.

Your soul belongs to me!

:highfive:
[Nexus 6  Original Android Development] Didgeridoohan:
Well... Actually, you're probably not on FK r51. When you flash SuperSU the script looks for modifications already done to the boot image. If found the script restores a backup made the first time rooting.

So... If you first flashed SuperSU on a stock boot image, flashed FK and then flashed SuperSU, you'll be back with a stock boot image. :)
[Nexus 6  Original Android Development] Mikeybray16:
Hey there Franco I'm new to the thread I have the nexus 6 and encoutered a really strange problem with sound on the nexus 6, every time I use YouTube the volume is loud then it goes really quiet and on every other media output like notifications I play the notification tone its quiet then ramps up loud same with Facebook messenger too its quiet then ramps up does your kernel fix that issue? Do you know what I mean by this issue? Thanks
[Nexus 6  Original Android Development] franciscofranco:
Because Media & notifications sound is separate now. Go to Settings -> Sound.
[Nexus 6  Original Android Development] rignfool:
You have flashed some other mod...

Magisk has SELinux issues and messes up FKU for dt2w and CPU boost... For instance
[Nexus 6  Original Android Development] ryanallaire:
I'm using phh superuser now, but I've had this problem before and didn't change anything between updates. It was there before, and now it's not.. Anyways not a big deal I'll just wait to see if it comes back..
[Nexus 6  Original Android Development] Tysovwik:
As I see, at r52 default I/o changed to noop. Is it better than stock cfq?)
[Nexus 6  Original Android Development] Mikeybray16:
Could you read this please Franco and get back to me please apparently its BLC throttling something to do with battery and this is disbaled in lean kernel someone said http://xdaforums.com/nexus-6/general/curious-speaker-volume-lowering-issue-t3136759
[Nexus 6  Original Android Development] pkgnex:
Just about any scheduler should be "better" than CFQ on SSD / EMMC devices. CFQ is the linux default because it ensures "fair" scheduling on rotating hard drives with some optimization on batching / queuing in order to not be skipping all over the disk to read / write files.

In theory, noop should be one of the best, if not the best, scheduler on phones / tablets because there is very little overhead in the scheduler, and there is no benefit from all the batching / queuing reads / writes that CFQ does on emmc.

That said, all of the schedulers can be tuned to work well enough on our devices that the differences are really imperceptible - especially with today's fast multi-core processors. If you think you notice much of a difference in actual usage, it's probably just a placebo effect.
[Nexus 6  Original Android Development] rignfool:
Oooo.... I have a question...

What about deadline over noop...

I've heard the small batching and not switching between read and write so fast is actually better...

Thoughts?
[Nexus 6  Original Android Development] franciscofranco:
I'm merely following what Google changed for Nougat that's why it's set to noop. There's extensive documentation about all the stock schedulers, no one here knows better than what's written on the Kernel docs so I suggest you read them ;)
[Nexus 6  Original Android Development] coremania:
Hi,

i'm new to thread and kernel. How can i get rid of vibration on dt2w ? KAM doesn't give me that option.
[Nexus 6  Original Android Development] franciscofranco:
Such option does not exist
[Nexus 6  Original Android Development] Isley_:
I'm not sure if that depends on the Kernel but with the EX app you can.

(If this is what you mean).
[Nexus 6  Original Android Development] coremania:
Ok, so it's not app related, thanks
[Nexus 6  Original Android Development] rignfool:
The option you are looking for is associated with [MENTION=4684315]flar2[/MENTION]'s wake gestures... Which is kernel driven...
[Nexus 6  Original Android Development] pkgnex:
Deadline works well. Benchmarks similarly to Noop and is one of my (and I think Franco's) favorite schedulers. The old "Franco Dev Team" found a combination of Deadline tunables that improved it somewhat (you can search XDA or PM me).

You can find situations in which Deadline outperforms Noop, and vice-versa, so I wouldn't worry about it too much either way. These things made more a difference several years back (think Galaxy Nexus days), but fiddling with them is really just playing at the margins with new devices.

---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------

Nice! Glad to see Goog kicked CFQ to the curb (finally).

I think when (if?) Nougat ever drops for the N6, I'll take some time to audit the stock boot.img and see if there are any other interesting updates - things like read-ahead buffer, various vm parameters, and tcp congestion avoidance algorithms come to mind that were clearly taken straight from Linux upstream when Android started but have really never been optimal for android / mobile devices with the horsepower they have now.
[Nexus 6  Original Android Development] ben_pyett:
I've started to get unexpected reboots nearly each time I initially put my device on to a charging mat, any ideas?

Will upload last _kmsg when I get one next
[Nexus 6  Original Android Development] franciscofranco:
Yeah /sys/fs/pstore/console-ramoops would be great.
[Nexus 6  Original Android Development] ben_pyett:
Here a fresh one, same thing just happened, put on charging mat and boom restart.http://cloud.tapatalk.com/s/57dc8fdbafc60/console-ramoops.zip
[Nexus 6  Original Android Development] ben_pyett:
Pretty sure you only need the one, but just in case something was different this time.... Here's anotherhttp://cloud.tapatalk.com/s/57dd0853ee1de/console-ramoops.zip

Strange thing is that it only appears to do it the first time I place or on the charging mat, it doesn't continue to restart while charging, which is obviously very fortunate. After I place it on mat, it initially restarts but then continues to charge to 100%.

EDIT:

It's rare that I use a charge cable, but just did and guess what....yep, another reboot, so it would seem that its charging of any kind that seems to cause my device to reboot. Annoying.
[Nexus 6  Original Android Development] Shamestick:
I'm running r52 stock settings on Neo's unofficial RR 9-9 build and I've noticed that 4 cores are always online. Battery and performance have still been good but I'd like to see mako hot plugging like it should, unless something's been changed? I thought maybe mpdecision might be enabled still and causing issues so I turned it off in /system/bin/mpdecision and rebooted but no dice. [MENTION=3292224]franciscofranco[/MENTION] could you hit me with a little input?

Edit: went and read the r52 change log again, could this be part of the power-saving performance profile?
[Nexus 6  Original Android Development] rignfool:
Mako Hotpluging is loong gone...
[Nexus 6  Original Android Development] Shamestick:
Oh lol, well thank you for the response (:
[Nexus 6  Original Android Development] franciscofranco:
That's beyond weird. I can't reproduce. I'll check your logs when back home :)

All cores online during screen on for a long time now. There's no need to turn them off since they achieve low power states while they are online.
[Nexus 6  Original Android Development] ben_pyett:
I clean flashed the latest update this afternoon and since then that bizarre charging reboot issue appears to have resolved itself and has magically gone away. I would be curious if you can find any specific cause, but don't waste too much time on it, as its probably more to do with my funk'ed up setup as I'm still over flashing the last catalyst mod update over stock images, as nothing still comes to close to the polished stock feature rich production quality with the exception of plain stock. Although strange that the same setup of catalyst on the latest released factory images update doesn't exhibit the same issue......but that's life I guess.

EDIT:

Typical the moment I hit post, the bleeding device reboots next to me, after being on cable charge for the last fifteen minutes.

I'll attach another log.

http://cloud.tapatalk.com/s/57ddd2374addb/console-ramoops.zip
[Nexus 6  Original Android Development] rignfool:
You realize flashing cataclysm mod over newer stock images is a terrible idea...

Your rewriting systemui... Telephony... Framework-res... With files that are easily a year old...

I would worry about NPEs and database mismatches...
[Nexus 6  Original Android Development] ben_pyett:
Yep, sadly I do appreciate that.

Hence my explaination and comments explaining the situation above, .. "my funk'd up setup".. along with my suggestion that he didn't spend too long looking into it as that might be the cause.

If that turns out to be the cause then I'll jump at Nougat, I'll leave that setup once the final production image is released, and I'll then be rid of both cata and the charging rebooting issue, although other users who are also running exactly the same haven't reported the same issue which is ultimately the only reason I asked and bothered reporting.

I was just slightly concerned it might be a hardware related issue, which would lead me on the direction of seriously considering one of the new pixel xl phone.
[Nexus 6  Original Android Development] franciscofranco:
I checked the logs, I don't think your issues don't originate from the Kernel. I think the other user above is right though, you're mixing some whacky stuff...
[Nexus 6  Original Android Development] MrBrady:
Is there a write-up available for the various wakelock settings in the FK app? I'm not sure if I should enable or disable these. Currently I have a terrible Bluetooth Share wakelock, but I don't think the FK app remedies that.
[Nexus 6  Original Android Development] SupraRZ95:
I'm new to the Nexus 6 scene. Had a Droid X and Samsung S4. I have the latest Pure Nexus Rom, is it safe for me to flash this over? What do I need to know/edit?
[Nexus 6  Original Android Development] ben_pyett:
Yes this is safe... Just download the zip and flash in recovery, All information you need is in post #1
[Nexus 6  Original Android Development] franciscofranco:
They are all disabled by default to boost battery performance (as you see by the "Disabled" in the app itself). There's not much info, we don't know what most of those wakelocks do (besides keeping the phone awake). There's nothing I can do about bluetooth. If the wakelock is bluedroid_timer then FK can fix it, if it's bluesleep, sorry not possible.
[Nexus 6  Original Android Development] imarq24:
OK been using this kernel and it's great ...just got one question...fast charge...I don't see the option in the kernel auditor
[Nexus 6  Original Android Development] franciscofranco:
There is no fast charge. The device has Turbo Charging from Motorola.
[Nexus 6  Original Android Development] imarq24:
Dang...lol... Don't have that turbo charger. But the wife does and don't like when u use it lol
[Nexus 6  Original Android Development] ShapesBlue:
It came in the original box with the OEM turbo charger. I also use two other 3rd part turbo chargers that work great

Sent from my Nexus 6
[Nexus 6  Original Android Development] imarq24:
Yeah but got my N6 off Swappa and didn't get a turbo charger. That sucked. What kind of 3rd party turbo charger do you use
[Nexus 6  Original Android Development] ShapesBlue:
I use the same brand for both work and car chargers. Tronsmart from Amazon. Both have given me zero issues

Sent from my Nexus 6
[Nexus 6  Original Android Development] imarq24:
Thanks in going to check that out
[Nexus 6  Original Android Development] gitchrodd:
These are pretty good to. https://www.amazon.com/Combo-Adaptive-Charging-Technology-Smartphones/dp/B00XK6YWM8

they sell just the wall one for $10 I use them at work and home. Works great. Cables suck though
[Nexus 6  Original Android Development] imarq24:
Good looking out definitely check it out
[Nexus 6  Original Android Development] :
I'm one of those guys with the split screen device and it doesn't happen with r51. R51 is flawless but with r52 it happens very aggressively.

The split screen also doesn't happen with r41 (the first version with anykernel I think) but it happens with all versions after that.

I also found that setting the cpu to around 800mhz alleviates the issue somewhat on "problematic" kernels.
[Nexus 6  Original Android Development] MrBrady:
Interesting. I have split screen as well, though far less with when running FK. I'll have to give R51 a spin and see if it'd eliminated.
[Nexus 6  Original Android Development] franciscofranco:
It's been stablished the issue also occurs on stock rom + stock Kernel. No one knows the cause and no one really knows how to prevent it.
[Nexus 6  Original Android Development] MrBrady:
I completely agree. It's just that some kernels (not necessarily this one) makes it worse. Apparently it'd a hardware issue that Moto knows about. Unfortunately my N6 is out of warranty so they won't fix it.
[Nexus 6  Original Android Development] MrBrady:
I have to say though I don't seem to have that issue with your kernel NEARLY as often as others. Some kernels make the issue appear daily or hourly while yours has only happened once in the last week, so :good:
[Nexus 6  Original Android Development] 2020shyboy:
my nexus 6 is on CM13 android 6.0.1 with Stock kernel

can i flash this Kernel on this ROM

EDIT:

just flashed this from Hope my OST increases,

My Phone OST is just 2.35hr & people are getting more than 6+OST so battery is main concern
[Nexus 6  Original Android Development] TonikJDK:
Yep, just flash it in recovery. That part about the 42 dirty flash is old info, you can ignore it. It was part of a transition in how the kernel was built. It only applies to peeps that previously used older versions.
[Nexus 6  Original Android Development] 2020shyboy:
Flashed this Kernel and wow on CM13 6.0.1

My N6 SOT has increased From 2.35hr to 4.10hr even 36% of battery is remaining ��

But its Charging time is increased

It was on 47% it takes about 2:10hr to charge100% how to solve that��

Installed Xposed Nap,Greenify, and Switchedoff 2 cores
[Nexus 6  Original Android Development] icsterm:
Since I updated to r52, my N6 is randomly rebooting by itself every 24-48 hours.

I installed syslog app from the Play Store, but the last_dmesg option is grayed out since is not supported by the kernel (or not activated).

How should I troubleshoot what exactly crashes my phone, since after reboot the logcat starts from scratch?
[Nexus 6  Original Android Development] sempot:
I can confirm this. I had BCL hotplug disabled, other than that it's stock.
[Nexus 6  Original Android Development] franciscofranco:
Are you disabling BCL?

Then enable BCL. It's there for a reason :)
[Nexus 6  Original Android Development] icsterm:
Indeed, I disabled BCL.

Such a pitty Motorola used a chipset that can't work nice with all cores online no matter the battery level.

I will re-enable and see if it works out.

I also experience some weird speaker cracking sounds while playing Youtube videos on r52, it happens mostly on the new power saving profile, but it also happens on balanced but not so obvious.

Can anyone confirm?
[Nexus 6  Original Android Development] ryanallaire:
Has anyone had issues disabling the bluedroid_timer wakelock?
[Nexus 6  Original Android Development] franciscofranco:
Can't reproduce.

Not that I know of.
[Nexus 6  Original Android Development] ben_pyett:
7.0.0 (NBD90Z) image now out for N6
[Nexus 6  Original Android Development] ShapesBlue:
Damn it's about time!!!!

Sent from my Nexus 6
[Nexus 6  Original Android Development] pkgnex:
7.0 N6 Kernel Parameters - 'Cause I Said I Would

Since I mentioned that I'd investigate the stock 7.0 kernel and system a bit when it dropped, I have done so with the factory image posted today, and here are some interesting, though minor, things I found:

/proc/sys/vm/min_free_kbytes changed from 3350 to 3175 (why the minor drop?).

/sys/block/*/queue/read_ahead_kb changed from 128 to 512 (it's about time!).

/sys/module/battery_current_limit (and therefore all the sub-folders) no longer exists (so where the heck is BCL, or was it dropped from the stock kernel?).

Verified that the stock N6 I/O scheduler is STILL CFQ on 7.0, NOT NOOP (not sure why it apparently changed on the newer device kernels but not N6).

I expect Franco will be able to glean all this once the source drops on AOSP, but this is an advance look that some might find interesting.
[Nexus 6  Original Android Development] rignfool:
I wonder what the solution is if they indeed dropped BCL...

That would (without another solution) force me to replace my battery if not the whole device...

This could be scary
[Nexus 6  Original Android Development] :
/sys/module/battery_current_limit

This was never the proper path for this... Its a path that people added in custom Kernels, I think for one of those hotplug disabling hacks.

Try looking for it in its correct location:

/sys/devices/qcom,bcl.39/
[Nexus 6  Original Android Development] pkgnex:
It's still there.
[Nexus 6  Original Android Development] JNewms:
Kernel source is out now for 7.0 Shamu. ?
[Nexus 6  Original Android Development] franciscofranco:
Yeah Nougat is out, finally. It'll take me at least about a full day to merge things together since when there's a new version of Android I tend to start over fresh.
[Nexus 6  Original Android Development] TonikJDK:
Remember everyone, once he gets it done, his cat still needs a day or two for QA.
[Nexus 6  Original Android Development] pkgnex:
Looking forward to it! Spending a few days on the stock 7.0 system and kernel is allowing me to "recalibrate" my performance and battery life expectations and investigate a few things anyways. But I am already really missing color control, vibration control, and the high brightness auto mode, among other things!
[Nexus 6  Original Android Development] franciscofranco:
Rebasing an entire Kernel is really revealing from time to time. There's a lot of crap that I always remove when starting fresh! I'll probably take more than 24-48 hours, I usually read all the commits one by one, read the code and decide what goes in.
[Nexus 6  Original Android Development] pkgnex:
Take your time to get it right.

After the Pixel announcement yesterday, there are a lot of us who are going to want to stretch our phones out for another year!
[Nexus 6  Original Android Development] franciscofranco:
Here we go! r53 for Nougat! https://plus.google.com/u/0/+FranciscoFranco1990/posts/MvCdL1AnCbX

Before you ask about BCL, I left it all stock for now to see if there's any change (I doubt it though) from Marshmallow. I'll adjust based on feedback if needed.
[Nexus 6  Original Android Development] biggitybakes:
Thanks for your hard work man!!

As for the BCL, I'm at 36% battery and it has 2 cores off. Yesterday, I was monitoring it after the nougat update and it had one core off at around 75% and 2 cores started at around 50%. So, my vote is to turn it off.
[Nexus 6  Original Android Development] pkgnex:
Thanks, Franco!

r53 is good right out of the box, but I did notice a couple things that aren't quite right between the new kernel and the FKU app:

Color control changes don't stick: You change them, back out of the interface, go back in, and they are back to where they were. Odd thing is it looks like the colors do change the first time they are altered after a boot... just that the app doesn't recognize the changed values or something?

GPU control doesn't work: Clicking on governor or max or in freq just presents the option of "0", and if you hit it, the app force closes.

There's always a few things like this when a kernel is re-started, and it's obviously nothing too important (phone runs great!). I'm obviously just starting to use r53, but I'll let you know if I come across anything else.
[Nexus 6  Original Android Development] franciscofranco:
I know about these things, it's ****ing permissions, selinux tightned up a bit ;)
[Nexus 6  Original Android Development] franciscofranco:
Thanks. I'll wait a bit more to read feedback.
[Nexus 6  Original Android Development] pkgnex:
Understood.

Could you add the Westwood TCP congestion avoidance algorithm back in for the next release?

Also, I just noticed that the HBM auto-enabler only half-works: It turns HBM on when entering a bright environment, but doesn't turn it back of when going back into a low-lit environment. You need to turn the screen off and back on to reset it. I'm guessing this is due to the permission issues, too. :)
[Nexus 6  Original Android Development] pkgnex:
deleted
[Nexus 6  Original Android Development] franciscofranco:
Good find about the HBM listener thing. I don't know where the issue comes from yet, I'll debug.
[Nexus 6  Original Android Development] szale9001:
Hey franco, just FYI, this patch is a dup

https://github.com/franciscofranco/Shamu/commit/947f19039e5bffde7ae1a1541e6ae47f6e1cafc2

Also, I've been curious, why do you think Google disabled rq_affinity? Naturally there is nothing in their commit log, so I'm curious if you have any speculation?