yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] franciscofranco:
I don't really know. I guess its to leave to the scheduler to decide where to migrate the requests to whatever cpu it decides the best. That may probably help on battery life since the scheduler won't, most likely, wake-up cores from idle to process this and just migrate to already waken-up cores. I'm speculating since I don't know the code, but that's my go at it.
[Nexus 6  Original Android Development] bamboohao:
Another vote to turn off the throttle
[Nexus 6  Original Android Development] Tysovwik:
What hotplug used in your latest kernel for shamu? Mpdecision ?

Btw r53 works like a magic (stock 7.0), smooth and fast :)
[Nexus 6  Original Android Development] blackbird5308:
BCL should bite the dust

I confirm everthing said on BCL, it's still there, have been there even on DPs, and it's as aggressive as it's ever been.
[Nexus 6  Original Android Development] Stroky:
Will test stock kernel for a few days. The kernel runs really good. After that I will test Franco.
[Nexus 6  Original Android Development] ShapesBlue:
Thank you so much for the newly updated kernel for Android 7! I couldn't wait for this one to be released!

Sent from my Nexus 6
[Nexus 6  Original Android Development] blackbird5308:
[MENTION=3292224]franciscofranco[/MENTION] Welp, got SoD today on r53, was walking in the mall, got my phone out of my pocket to check the time and had to reboot it forcely. I answered a message 5mins before, so it hadn't been dead for long. Had no way to grab a log though, since i was in the mall lol

Is there anything you may need, like a last reboot log?
[Nexus 6  Original Android Development] Stroky:
On stock Rom?

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6  Original Android Development] blackbird5308:
Obviously stock rooted, nothing else.
[Nexus 6  Original Android Development] DDQW:
i don't want to sound rude, but is ther any information on what this kernel actually does different/better than stock?

The changlogs are not exactly detailed
[Nexus 6  Original Android Development] vsot13:
Cook you breakfast and get you laid in a evening. That's all...Everything else is like stock
[Nexus 6  Original Android Development] gk1984:
Just providing feedback - 2 cores seem to stop after around 50%... Or they stop lower and never come back on. Been having lag issues since DP5, even with a full wipe on official Nougat. Hoping this can be fixed in the kernel.

Edit: wanted to add I'm using Franco kernel too. Same issue
[Nexus 6  Original Android Development] rasengan82:
Got a hard reboot. What log should I provide? This is stock rom rooted.
[Nexus 6  Original Android Development] Stroky:
Has someone a backup from the original Kernel from the final 7.0?
[Nexus 6  Original Android Development] TonikJDK:
Google "android factory images" First link, grab the whole thing and extract it.
[Nexus 6  Original Android Development] gk1984:
Adding to this, flash the boot image with fastboot
[Nexus 6  Original Android Development] holeindalip:
https://drive.google.com/file/d/0B7bRZTho5nezSUJZVHN3RG52VFE/view?usp=drivesdk
[Nexus 6  Original Android Development] franciscofranco:
I disabled Mpdecision.

:(

Dunno. Could be a million different things, that's hard to debug/guess.

As I already said countless times, I don't provide a list of "magical" features. Most of the things are just fancy buzzwords and mostly no one understand what they mean and they'll just give you a big ass placebo. All the commits are here https://github.com/franciscofranco/Shamu and the changelogs are detailed enough. It has standard things like display color control, ability to boost your headphones volume etc plus my own magic.

It's the ****ing BCL.

/sys/pstore/fs/console_ramoops
[Nexus 6  Original Android Development] Tysovwik:
So no hot plug at all in your kernel ?
[Nexus 6  Original Android Development] pkgnex:
Nope. And it's not needed!

---------- Post added at 04:12 PM ---------- Previous post was at 04:09 PM ----------

BCL:

Kill.... it.

Kill it!

Westwood:

Add... it.

Add it!

:)
[Nexus 6  Original Android Development] gk1984:
I have another issue and not sure if it's a kernel issue or not. The lag and shut down of cores caused me to reboot my phone in the car. However, it wouldn't reconnect to the car's Bluetooth. I had this problem on DP 5 and thought the car was at fault. When official Nougat released, my phone would reconnect to the car after a reboot.

It does connect at first. It's just after a disconnect or reboot where it fails to reconnect. Only change between it working and not was this kernel.
[Nexus 6  Original Android Development] franciscofranco:
BT code is 100% stock.
[Nexus 6  Original Android Development] gk1984:
Thanks. I'll check audio driver related stuff.
[Nexus 6  Original Android Development] wavedashdoc:
R53 working great! Just as smooth if not smoother than stock with much better battery life.

One issue. Per app profiles don't seem to be working correctly.

Once I leave the profiled app the CPU clock speed doesn't return to the system default I set it to. Example I've under clocked to 2496. Exiting my custom GPS mode where I set the clock to 1728, keeps the system clock to 1728 instead of reverting to 2496. Sometimes it will go back to the default clock of 2649.

Other than that awesome work.
[Nexus 6  Original Android Development] Meowdib:
Sound through headphones is awesome. Just wanted to say that.
[Nexus 6  Original Android Development] franciscofranco:
That's pretty hard to debug. Maybe you were thermal throttled before the profile kicked in, so it read 1.7GHz as the current freq before it applied the profile.

:)
[Nexus 6  Original Android Development] wavedashdoc:
I was thinking that too. No issues with the CPU clock going back to default when I was higher than 50? battery.

So I'm definitely for the death of the throttling. Seems like an unnecessary addition to the stock kernel carried over that causes more problems than it solves.
[Nexus 6  Original Android Development] blackbird5308:
logs

[MENTION=3292224]franciscofranco[/MENTION] There you go, ramoops log from my SoD. Not completely human readable though lol
[Nexus 6  Original Android Development] franciscofranco:
Yeah I'll see if I can remove that freq capping, definitely kills performance unecessarily.

Yeah I can't read that. SoD can be many things though, since no one has reported anything similar I doubt it's directly caused by FK.
[Nexus 6  Original Android Development] Prack:
[MENTION=3292224]franciscofranco[/MENTION] is high brightness mdoe auto enabler broken in android 7 or is it just me? Soon as the sun hits it I go full brightness and never back down, even after moving to a dark room. I have to open the app and toggle it off and on again for it to dimm. Guessing it's a permissions issue in android 7?
[Nexus 6  Original Android Development] pkgnex:
Yeah, it's not working right, and Franco is looking into it already.

One time saver - you don't need to go into the app and toggle anything, just turn the screen off and back on and it resets... at least it does for me.
[Nexus 6  Original Android Development] rignfool:
[MENTION=3292224]franciscofranco[/MENTION]

I went digging thru the BCL directory in sys...

There are tunable values for BCL...

Do you know what they do... And could they be 'tuned' to not have BCL be so relentless?
[Nexus 6  Original Android Development] requiiiem:
what bug have on r53? 7.0
[Nexus 6  Original Android Development] franciscofranco:
I don't know, but most likely not related to what you're asking.

?
[Nexus 6  Original Android Development] carlo1024:
Hello, I'm very new in updating kernels and stuff, sorry for the noob question.

My question is I have an app called Color Control which I know is compatible only on certain kernels like franco. I plan to update from mm to nougat, I know it will revert back to stock kernel after I flash the nougat, do I have to Uninstall my color control app and just install it after I flash again the new r53? Thanks for the help in advance =). BTW I plan on using flashfire to flash the image and the r53 as well.

My device:Nexus 6 MM, supersu2. 78,twrp3.001,franco kernel.
[Nexus 6  Original Android Development] pkgnex:
Your plan should work.

Before you start, though, upgrade TWRP to the latest (3.0.2-0). Either the one you are on or the one after that (but not the latest) had issues. After you have the latest recovery, do a complete backup. That way if something goes wrong, you can always revert to where you were before and try something different!
[Nexus 6  Original Android Development] requiiiem:
I read auto brightness does not work
[Nexus 6  Original Android Development] holeindalip:
Auto brightness works fine, it's the high brightness mode when turned on and activates it won't go back down to normal brightness until screen is switched off. Permissions issue is what is causing the problem and hopefully Franco fixes it in next iteration. Make sense??
[Nexus 6  Original Android Development] carlo1024:
Thanks For the Response. About the color control app, do i need to uninstall it first or just leave it as it is?
[Nexus 6  Original Android Development] franciscofranco:
Leave it ;)
[Nexus 6  Original Android Development] :
As far as the brightness issue people are reporting... This still works fine in ka-mod on N. Feel free to take a look at how I'm doing it there if you like.
[Nexus 6  Original Android Development] franciscofranco:
HBM?
[Nexus 6  Original Android Development] franciscofranco:
How did you find those? Just reading drivers? The patch makes sense, I'll merge it and test! If you want, you can make a pull request on my repo so it retains commit authorship etc. Whatever suits you best :)
[Nexus 6  Original Android Development] franciscofranco:
Just fixed HBM automatic listener. Was a simple selinux rule denial. r54 will have it working properly.
[Nexus 6  Original Android Development] ben_pyett:
Can anyone else comment?

To me it looks like the tunable colour settings aren't sticking permanently.

I only use the out of the box Franco setting.

I can't seem to pin down what causes it, but after a while, colours certainly reset to default and need to be toggled back and forth to get correct application.

Thanks
[Nexus 6  Original Android Development] Nautilus74:
works on f2fs data partition?
[Nexus 6  Original Android Development] franciscofranco:
I have no clue, never seen anything like that.

Yes.
[Nexus 6  Original Android Development] rignfool:
Are you running the stock ROM...

Or are you running something that has the built in night mode/color calibration thingy exposed?
[Nexus 6  Original Android Development] holeindalip:
Hes right the color profile goes back to default after some time, idk if that would be a permissions setting thing or not

Edit: looks like it's just on a reboot like the set on boot switch isn't working
[Nexus 6  Original Android Development] ben_pyett:
Stock

Of course I'm right <joke>

Happened more than once, so pretty convinced that its not me or my setup.

Can confirmed it is after a reboot, even though I've the set on reboot switched.
[Nexus 6  Original Android Development] JNewms:
I can also confirm that. After reboot the the color settings have to be selected again.
[Nexus 6  Original Android Development] wavedashdoc:
Same. Running Pure Nexus 10/10/16
[Nexus 6  Original Android Development] bamboohao:
For me the color profile sometimes reset back to the default after a reboot, although it still says it's set to my chosen color profile.
[Nexus 6  Original Android Development] pkgnex:
For me, the colors set to what I want at boot (I don't use one of the custom profiles, but change all the slide values to basically split the difference between the two "wrinklefree" profiles). However, every time I go into the FK app the sliders show up at the stock position - which I know there not really at because you can see the color change take effect upon boot right when the "finished applied settings at boot" toast message pops up.

This, the inability to change anything GPU-related, and the HBM listener (already fixed on the next build) are the only issues I've found with r53.

I also wish for the "westwood" tcp algorithm to be added back in because it speeds up my upload / download speeds substantially vs. either of the "cubic" or "reno" algorithms included.
[Nexus 6  Original Android Development] AlxMAX:
I am not interested in authorship. I am interested though in letting Google developers know about it since even in the kernel for Nougat those mutexes are left locked.
[Nexus 6  Original Android Development] franciscofranco:
Maybe it's permissions **** or something, I'll look now just before pushing r54.

GPU thing has been fixed, HBM too. I'll add those tcp algorithms back too.

https://github.com/franciscofranco/Shamu/commit/27f203a59c60212692d65691020227024ae8c167
[Nexus 6  Original Android Development] wavedashdoc:
Awesome. Thank you Francisco!

Note: I don't believe I had the color issue on Stock, if I recall.

Yes I checked permissions too.

Thank you for your continued support!
[Nexus 6  Original Android Development] pkgnex:
Thank you, Franco!
[Nexus 6  Original Android Development] holeindalip:
If this could solve mine and everybody else's reboots that would be sweet
[Nexus 6  Original Android Development] gk1984:
Can someone please ELI5?
[Nexus 6  Original Android Development] gk1984:
Sorry, explain it like I'm 5.. simplify what this does. Just curious what to expect from it.
[Nexus 6  Original Android Development] franciscofranco:
But explain what?
[Nexus 6  Original Android Development] gk1984:
The commit - metux unlock
[Nexus 6  Original Android Development] :
Its not really something that an end user should need to worry about. They're essentially stability fixes.

If you're developing, you shouldn't need it explained like you're 5.

https://en.m.wikipedia.org/wiki/Lock_(computer_science)
[Nexus 6  Original Android Development] franciscofranco:
r54 is up and running! Get it now!

https://plus.google.com/u/0/+FranciscoFranco1990/posts/dAs9qW1p4ny
[Nexus 6  Original Android Development] pkgnex:
Got it!

HBM listener turns down brightness automagically.... check.

GPU controls now accessible from app... check.

Color control un-borked in app (shows correct settings and stick after reboot)... check.

TCP congestion avoidance algorithm, include westwood... check.

Thanks, Franco!
[Nexus 6  Original Android Development] franciscofranco:
That'll be 100€. Thank you.
[Nexus 6  Original Android Development] pedrofidalgo:
what about the 2 cores offline after 50% battery gone?
[Nexus 6  Original Android Development] pkgnex:
How much is that in USD ($)? Can I wait until the Brexit to do the conversion?
[Nexus 6  Original Android Development] franciscofranco:
Nope. The issue there is that some devices will crash if cpu2 and cpu3 don't go offline at certain voltage thresholds. There's really no way to indenfity which, the driver reads the voltage and depending on that it'll do whatever it needs to do. I merged a couple BCL patchces to improve how the driver works regarding cpus online/offline just like stated on the changelog.

No! Now!
[Nexus 6  Original Android Development] wavedashdoc:
I didn't think it was possible. But this release is definitely smoother. All scrolling lag is non existent.

Running -50 under-volted

max 2496

Everything else left alone.

Pure Nexus
[Nexus 6  Original Android Development] pedrofidalgo:
Does the -50 undervolt gives a better batery life?

Also, lowering the max freq to 2496 makes the phone noticeable slower?
[Nexus 6  Original Android Development] LordDeath:
Not noticeable. But afair my 805 has a pretty bad binning and if I push it too far, it will go down to ~1 GHz instead of 2.7 GHz. Undervolting will defer the throttling a little.

I doubt that and again: This could defer the throttling even further. How is your CPU binned? You can find its binning value in /proc/cpu/msm_acpu_pvs﻿

edit: Just for reference: Mine is at 4.
[Nexus 6  Original Android Development] wavedashdoc:
Exactly my thinking. No noticeable slowdown. Longer performance sustainability with lower clock speed and voltage.

Mines at 8. What does this mean?

Did we research, looks like it has to do with tolerance when under volting. Higher is better.
[Nexus 6  Original Android Development] snipz:
This is the second time using the app I updated the kernel and it days I have no sim card on reboot. I manual went in the recovery installed again and wiped dalvik\cache and it still says no sim card. Anyone know a fix?
[Nexus 6  Original Android Development] gk1984:
I've had this happen a while back. I don't think it's the kernel. Try a full wipe/factory reset and see if the problem is still there
[Nexus 6  Original Android Development] snipz:
Turning on airplane mode, restarting, and turning it off seemed to work

Edit: in the past dirty flashing the ROM fixes it also without a factory wipe
[Nexus 6  Original Android Development] caballon:
Running great.:highfive:
[Nexus 6  Original Android Development] ShapesBlue:
Franco I just want to say thank you for the work you've put into this kernel. I unfortunately had to recently revert back to the factory images due to the kernel not allowing me to connect to WiFi. It's never done this before and I was really confused by it. None the less I'll still use the kernel in the future as I've purchased the app in the play store but I wanted to make you aware of it as well as any members of this issue.

I looked at everything I had on my device and this was the only app I had recently updated or installed that gave me the issue. I just want to say thank you for all your hard work and dedication

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
I don't see how that is related to the Kernel or my app. My app doesn't touch or doesn't give a **** about Wi-Fi. Kernel has stock Wi-Fi drivers.
[Nexus 6  Original Android Development] SubwayJrd:
Does he think that updating fk.Updater stopped his WiFi working? Because that's how I read it.

Either way, that's extremely silly.
[Nexus 6  Original Android Development] franciscofranco:
I had a couple issues understanding too :(
[Nexus 6  Original Android Development] ShapesBlue:
Actually its the only thing I installed two days ago. Flashed it via recovery and followed the steps to flash, I've been doing this for quite a long time so I do know what I'm doing. Yes it disabled WiFi, and previously when I first installed the kernel the day it came out it also created random reboots. The WiFi being disabled was not because of any other app. I know you both think that I have no clue what I'm talking about but believe it or not I do. I'm also not questioning your app Franco I'm just letting you know what issue I experienced. Why exactly am I getting bashed for stating what my issue was? Did I miss something?

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Oi? No one is bashing you in any post. I'm just trying to understand so I can help you. You mean disabled Wi-Fi as in impossible to turn on? What rom are you on?
[Nexus 6  Original Android Development] ShapesBlue:
I was am still on stock. Yea disabled as in it won't even turn on. But I had to reflash the factory images so I can't reproduce the issue.

And I'm sorry if I took it that way that I was being bashed, my apologies

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Which Stock version were you in when you flashed? Because I think it was August security patch release needed new Wi-Fi drivers both in userspace & Kernel, and if one of those components mismatched, goodbye Wi-Fi. So my guess is you had an older system version so the Kernel is updated with the latest and greatest and then mismatch.
[Nexus 6  Original Android Development] ShapesBlue:
Android 7, I was waiting patiently for your kernel to be released and I tried your kernel first

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Dunno something smells funny.
[Nexus 6  Original Android Development] pkgnex:
I understand your frustration, but since there are many other people running the stock 7.0 factory image with Franco's kernel (r53 and r54) with no wifi issues, it makes logical sense that there must be something unique going on that is specific to your situation (device, apps, settings, router, etc.). That and the fact that Franco's kernel uses the stock wifi drivers!

I have no idea what it could be, but maybe try re-downloading and installing the 7.0 factory images again from a clean slate (checking MD5's along the way), confirm wifi works with the stock boot.img, then re-download and flash r54 to see if it repeats.
[Nexus 6  Original Android Development] holeindalip:
R54 is flawless, thanks Franco!
[Nexus 6  Original Android Development] ShapesBlue:
I will probably do that in the future. Thank you everyone for your help

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
:)

Let us know how it goes ;)
[Nexus 6  Original Android Development] franciscofranco:
FKUpdater 2.1 beta 2 new features: https://plus.google.com/u/0/+FranciscoFranco1990/posts/dQ1tGpSsiX1
[Nexus 6  Original Android Development] ShapesBlue:
Going to attempt to flash it again. Everything works so far. I'm on the stock 7 rom and kernel

Sent from my Nexus 6
[Nexus 6  Original Android Development] cobyman7035:
ok so im finally on franco r5 now , using vomer dual n6 script

so is the max cpu speed is 1250mhz no matter if all FOUR cores are on right? im using perfmon app to check and i see that cores 3 and 4 sometimes go to 1.9ghz...is that correct or do i have to lower that... i have fauxclock app as well as FKU app

also using nova prime launcher with flex icon pack...it does seem to stutter when i scroll the home screens and app drawers...not as smooth as elementalx, but i guess thats the trade off when u use less cpu speed and get more SOT

i might have to try per app mode to speed up nova launcher screens?

when i try per app mode, add new profile it FCs the FKU app unfortunately ....

another quirk i found is when the LED is flashing while charging...it flashes normal blink blink blink blink then a 'weird' 5th blip blink...can anyone else confirm this?

i use trickster mod app to have charging blink
[Nexus 6  Original Android Development] davey11:
Haven't been on xda for awhile, then today I see a franco thread. Hot dam, right on! DL and installed. ?
[Nexus 6  Original Android Development] akellar:
Has there been a fix for colors not sticking after reboot?
[Nexus 6  Original Android Development] zephiK:
Not with FKU.
[Nexus 6  Original Android Development] mgear356:
Sadly not yet.. Thats why I am on trickster for now..
[Nexus 6  Original Android Development] owyheendn:
Can you controll certain things on the LED light from the Updater App?
[Nexus 6  Original Android Development] zephiK:
Nope, FKU is for kernel settings not notification LED. Look at screenshots/descrpition to see what you can do with it. https://play.google.com/store/apps/details?id=com.franco.kernel
[Nexus 6  Original Android Development] angieri918:
Franco you are the ****! My phone has been in straight beast mode since switching from sensei to your kernel. Kept getting sod even with stock settings.. Haven't had a single issue with yours :)
[Nexus 6  Original Android Development] comicbookguy72:
Left lightflow uninstalled overnight but it rebooted this morning before i had chance to reinstall..... Flashed pureshamu 3.93 and franco r4 before i go back to work for stability
[Nexus 6  Original Android Development] regime2008:
I have had nothing but great results with this kernel. Vast improvement of battery life throughout the updates. I'm getting close to 6 hours of SOT with batt intensive apps like Facebook, Facebook messenger, and clash of clans, with a third of battery life left!
[Nexus 6  Original Android Development] cobyman7035:
I don't want to plug flars elementalx but thats another kernel with good battery sot if ur not a power ? user.. Underclock to 1.9ghz -25uv ing… I get 6hrs sot easily… now with vomer and franco I expect 7hrs sot with my same usage… phone ? duz seem to stutter more because its only 1.2ghzmaxd

Via my NeXus™ 7FHD on XDA Premium app