yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] CRXed:
Did anyone try FK with unofficial

Systemless

Xposed?

After I flashed FK, it made the Xposed framework go inactive.

I tried it on a stock ROM Nexus 6.

It works fine with official XPosed.

(Don't attack me for using Xposed, just curious if this is FK incompatibility or my own wrongdoing :p)
[Nexus 6  Original Android Development] ouyamaster:
Where can I get the modified Franco kernel with swipe to wake gestures? All links are down that I can find. Is there an r46 version and will it work with fkupdater settings even if I have to flash it manually? Or would I have to use kernel auditor for the wake gestures?
[Nexus 6  Original Android Development] electricpete1:
Franco kernel has double tap to wake. I haven't heard of it having swipe to wake.
[Nexus 6  Original Android Development] NLBeev:
He is looking for a mod kernel?
[Nexus 6  Original Android Development] mohammed510:
I've just had a random reboot. Using the latest kernel version with latest slim rom.

http://cloud.tapatalk.com/s/5770317f2d9ce/dmesg.txt
[Nexus 6  Original Android Development] Wobbledad:
Call me a noob, but I can no longer find the Max Temp Threshold or Max Batt % settings areas after doing a clean flash.

Been using this for ages at this pt & just bought the paid this evening. Any assist would be much appreciated. This phone is too prone to overheating and I don't ever want to over-charge this guy. Thanks in adv!?
[Nexus 6  Original Android Development] thefallen924:
I'm having the same issue. it was there this morning when i first installed both the kernel and the app, and then disappeared. tried uninstalling and reinstalling both and still havent gotten it back...
[Nexus 6  Original Android Development] str8str:
What version of super SU are t you using if any

There were issues with last couple versions causing reboots so you should update to the latest I know it fixed my reboot issues wasn't the kernel at all. Also themes can cause it try using none for a bit and see if it goes away.
[Nexus 6  Original Android Development] icsterm:
i don't think this feature is included in the nexus 6 kernel flavour.

Been using FK since Nexus 4 days and have yet to see such settings in the FKU paid app.
[Nexus 6  Original Android Development] franciscofranco:
r47 is up! https://plus.google.com/u/0/+FranciscoFranco1990/posts/DfphQQMv76d
[Nexus 6  Original Android Development] TonikJDK:
Flashed, only been a little while but all is well.
[Nexus 6  Original Android Development] DominoDoug:
Thank you!

Quick note. I am unable to download the latest kernel via the app.
[Nexus 6  Original Android Development] franciscofranco:
Paid of free app?
[Nexus 6  Original Android Development] DominoDoug:
Paid.
[Nexus 6  Original Android Development] CRXed:
No problem here on the Paid version, flashing the new kernel as I write this.
[Nexus 6  Original Android Development] franciscofranco:
Dunno, tested it and it's fine.
[Nexus 6  Original Android Development] sagar_b93:
Lost Wifi :(

I am on chroma Rom Latest build, July security patch (MTC19Z) .

Any workaround for this ?

thank you.

( ive read the google plus post that said it is compulsory to be on the mob30o just asking if there is a way to use it on the MTC19Z version )
[Nexus 6  Original Android Development] SubwayJrd:
Um... You read FRANCO'S post that specifically said NO, you MUST be on MOB30O, so you already have your answer.
[Nexus 6  Original Android Development] mgear356:
Weird that chroma already has July security patch but wifi is still lost. No support for aosp roms?
[Nexus 6  Original Android Development] franciscofranco:
Probably Chroma didn't update some blobs or something. I can't control what custom roms do and I'm pretty sure there's a mismatch between the Kernel Wi-Fi driver requirements and custom rom's blobs.
[Nexus 6  Original Android Development] franciscofranco:
I'm curious if anyone has a weird static buzz (coming from the speakers) right after there's an haptic feedback (vibration). I have this since day 1 but never thought to ask if it happened with anyone else. The N7 2013 also suffers from this.
[Nexus 6  Original Android Development] rignfool:
I too have had this from day one...

It seems to become more prevalent as the battery level drops...

And... When below 5%... It's unbearable...
[Nexus 6  Original Android Development] martinez5241:
This happens to me when I connect it to a charger and you hear it as I play music. Buzzzzzzzzzz
[Nexus 6  Original Android Development] CRXed:
Yeah, also have it from day 1.

First I thought the speakers were broken, but I read somewhere it's something that's controlled by software.
[Nexus 6  Original Android Development] ktmom:
There were 2 July updates. July 1 and July 5. If July 1 update is incorporated, then the security fixes are there but not the driver updates. July 5 contained both the security and drivers. The August update should bring everything back inline.
[Nexus 6  Original Android Development] franciscofranco:
Interesting. No promises, but I'll see if I can trace it in the Kernel drivers.
[Nexus 6  Original Android Development] rignfool:
Happy hunting...

While rummaging... See if you can find out why the volume is wacky at low battery too...
[Nexus 6  Original Android Development] franciscofranco:
Probably voltage related (I'm just guessing though). I'll see what I can do.
[Nexus 6  Original Android Development] trizzv:
I flashed this kernel and now my wifi isnt working! how do i fix this?

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

* WARNING! DON'T FLASH THIS IF YOU'RE NOT ON THE JULY 2016 SECURITY PATCH VERSION MOB30O OR WI-FI WON'T WORK

I am new to this and I don't understand what this means. can someone please tell me what to do
[Nexus 6  Original Android Development] Tidiroi:
Hello,

I just wanted to install the latest kernel zip (r86) on my rooted stock Nexus 5 running MM with latest July sec patch but in stock recovery when I choose apply update from SD card I get an error: "E: unknown volume for path [/sdcard]".

I guess it´s some kind of mounting problem? Or is it required I use a custom recovery?
[Nexus 6  Original Android Development] TonikJDK:
Just hit the play store and get Franco's FKupdater app. There is a free version that will flash it. The paid version lets you make tons of adjustments and also makes Francos cat happy.
[Nexus 6  Original Android Development] Tidiroi:
Thanks, I will use the app, but am just curious what the issue might be.
[Nexus 6  Original Android Development] Didgeridoohan:
The issue is you're using stock recovery (flash or boot TWRP instead). And, you're posting in the Nexus 6 forum. You'll get better help in the Nexus 5 forum.
[Nexus 6  Original Android Development] franciscofranco:
First you're trying to flash a Nexus 6 Kernel in your Nexus 5. Be glad it failed.

Secondly, you can't adb sideload custom flashable zips on stock recovery.
[Nexus 6  Original Android Development] Tidiroi:
Hi, r86 is Nexus 5 kernel :)

Anyway, I flashed it using FKupdater, thanks for the app and sorry for posting in the wrong forum, didn´t realize it.
[Nexus 6  Original Android Development] mantakos:
Hi guys excuse me if this has been asked before, but is this kernel going to work with Nougat preview 5? Although I have a ferling that it wont :P
[Nexus 6  Original Android Development] SubwayJrd:
I believe Franco stated that he isn't going to update the kernel for Nougat until official release.
[Nexus 6  Original Android Development] gambit07:
+1 on this, wi-fi not working although I'm on the latest mob30o bootloader. What else needs to happen to get this working?
[Nexus 6  Original Android Development] ryanallaire:
If you are new then why are you flashing before you even know what's going on!? It clearly states that you must be on the latest July security patch otherwise Wi-Fi won't work, if you look in your settings ??about phone you'll see which one your on..
[Nexus 6  Original Android Development] cobyman7035:
It's been ages since I last posted here lol... I'm still on. Android 5.0. 1 Franco r19 I think

Is there better battery with latest 6.0 Franco kernel if I flash it or since this phone is like 2 years old... Battery is dying

---------- Post added at 07:33 AM ---------- Previous post was at 07:26 AM ----------

Ot... I sometimes get random reboots when I'm on lte and try to switch back to wifi only or vice versa.. Any1 else
[Nexus 6  Original Android Development] NLBeev:
It's normal that the battery becomes less powerful after 2 years.

On my N6 (almost 2 years) I noticed better battery life with the latest stock kernel. A little bit say 5%.

After flashing Franco's latest kernel the battery life becomes better about 8-10% . Default settings.

So updating to 6.0.x and latest FK can be useful for your device.

Besides that I use black/dark background when possible. So no Gmail but Aquamail.
[Nexus 6  Original Android Development] pedrofidalgo:
Thinking about trying this kernel.

Already used Stock rom with stock kernel, and now im on Chroma ROM with Stock kernel. Will this be better in terms of battery life?

Also, should i buy his app to mess with settings? Or he recommends the "stock" settings on his kernel?~

Just look, i didnt used my phone that much today, only checked for messages and stuff, im on Chroma with Stock Kernel:

I dont think the battery is good at all
[Nexus 6  Original Android Development] leongunblade:
Will this work on latest pure Nexus? July security updates are installed, but I had a problem. I was running elementalx kernel, but I wanted to try Franco.kernel, so I wiped cache and dalvik cache and installed franco on top of elemental, but mi WiFi didn't work. Was it because of installing on top of elemental or it won't work regardless?
[Nexus 6  Original Android Development] TonikJDK:
No, that means Pure Nexus didn't include all of the July patches. I don't believe its going to work.
[Nexus 6  Original Android Development] leongunblade:
I can confirm it is working now. I flashed stock pure Nexus kernel then reflashed Franco and it's working now.
[Nexus 6  Original Android Development] Efrenjr15:
Has anyone flashed 47 with the latest weekly from DU? Last I remember WiFi was borked.
[Nexus 6  Original Android Development] pkgnex:
I can confirm that r47 works fine with the latest (8/5, MOB30W) stock ROM security updates.

I think the stock boot.img changed in August as it was slightly larger than the July boot.img. It appears from the security bulletin to be mostly driver stuff, but apparently nothing that is strictly needed to work with the new system.img since I'm running fine.

I know Franco builds from source and I'm not sure it's available in AOSP quite yet, but I would think r48 will be available in due time.
[Nexus 6  Original Android Development] Deckard_9732:
Can I flash Franco r47 over another custom kernel without a boot.img flash per the instructions?

I am runningt he latest (8/5, MOB30W) stock ROM security updates with a no encrypt boot.img and Hells Core kernel.

Thnaks in advance for a speedy reply.
[Nexus 6  Original Android Development] dark2099:
Nope, should never do that. Just dirty flash your ROM, boot, reboot and flash kernel, then mods after another reboot.
[Nexus 6  Original Android Development] CRXed:
I was running the same setup on my N6 but today my data connection and gps repeatedly lost connection.

Not sure what happened but I restored r46 and then it was fine again.
[Nexus 6  Original Android Development] nfremd:
It's not the kernel or rom. It's a T-Mobile/Google issue. http://www.androidpolice.com/2016/08/04/some-nexus-6-owners-report-data-outages-on-t-mobile/
[Nexus 6  Original Android Development] CRXed:
Yeah I read about that, thanks! I am on Vodafone in the Netherlands, so it's not just T-Mobile.

Temp workaround:

"The issue is tied to location/GPS. It will work fine, until an app (Maps, PokeGo, etc) accesses the location. Once it does, the data cuts out, and won't work until location is turned off and usually a restart. It will work fine until something accesses location services."
[Nexus 6  Original Android Development] franciscofranco:
r48 is up! https://plus.google.com/u/0/+FranciscoFranco1990/posts/KEAX2gKnpXg
[Nexus 6  Original Android Development] pkgnex:
Fully patched for "quadroot" before Google.

You're my hero.
[Nexus 6  Original Android Development] TonikJDK:
Yea, a month ahead of them. Very impressive.

FWIW, I have been on it for a few hours, all is well.
[Nexus 6  Original Android Development] pkgnex:
Ditto.
[Nexus 6  Original Android Development] ben_pyett:
Thanks as always for latest release and continued support.

EDIT:

Another user highlighted your G+ post, read and understand so don't bother replying! :)

Although I notice that in your change log you said we were now fully patched against the vulnerability, but I notice the checkpoint app still claims I'm not...

Although screenshot now shows far fewer vulnerabilities than the previous failure screenshot which can be seen on play store screenshots https://play.google.com/store/apps/details?id=com.checkpoint.quadrooter

Is this a failure by their app?

There are code fix links in each failure shown below, can you please disable check that they're applied and confirm

https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340

https://www.codeaurora.org/projects...r-binding-any-port-control-port-cve-2016-2059
[Nexus 6  Original Android Development] christianpeso:
Have a read at his Google+ post.

https://plus.google.com/+FranciscoFranco1990/posts/BR6NRSYFSrD
[Nexus 6  Original Android Development] franciscofranco:
I'm pretty sure that's all bogus. I saw a screenshot of an older Samsung Galaxy device (probably stuck in some older L or M releases, and it said all vulnerabilities were fixed... yeah right).
[Nexus 6  Original Android Development] TonikJDK:
Gotta be bogus, 2059 was fixed in Google's August update. It shouldn't be showing at all. Mine isn't. And the other two they fixed in August are not showing for him...so obviously the poster has the August update.
[Nexus 6  Original Android Development] SynisterWolf:
My M7 on L said it was patched and i just turned that thing on for the first time in a year. O.o
[Nexus 6  Original Android Development] pkgnex:
Feature Request

Ever since franco.Kernel went to the anykernel2 script, I've felt something is lacking... and I just realized what it is:

The "Now Installing a Virus.... All your bases are belong to us!" recovery text has been omitted!

Any way this could be added back in? It brightened my day a little bit every time I flashed a franco.Kernel!
[Nexus 6  Original Android Development] franciscofranco:
:highfive:
[Nexus 6  Original Android Development] ShapesBlue:
Hey man sorry to bother you. I know your a busy man. I was wondering if there may be a time line as to an update to support android n? I also own your pro version of the updater in the play store and I love using your kernel on both my N6 and N5. Thanks again for your attention to this
[Nexus 6  Original Android Development] franciscofranco:
When N is live for production.
[Nexus 6  Original Android Development] ShapesBlue:
Makes sense. Thanks for the reply. I didn't know if you could work off the dev preview or not. That answers my question and thanks again :)

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
I can work with the dev preview sources, but it's just not worth the hassle since stuff is always changing.
[Nexus 6  Original Android Development] Dashing_97:
[MENTION=3292224]franciscofranco[/MENTION] i flashed this kernel on DU stable v5, the wifi is not detecting networks :/
[Nexus 6  Original Android Development] Efrenjr15:
Nothing he can do, its a problem with the ROM not kernel. Was hoping they'd fix it but don't see them fixing it anytime soon.
[Nexus 6  Original Android Development] rignfool:
[MENTION=3292224]franciscofranco[/MENTION]

Would you consider re-adding BCL and a toggle in FKU...

Reasoning...

My phone, at least, will have random shutdowns at anytime below 25%... And... At anytime below 40% while running navigation in maps...

On kernels with BCL enabled... I do not have this issue... I can consistently drain my battery down to 5% without shutdowns...

The reason for the toggle is... To remove the 'why are cores 2 & 3 stuck at 2649... Or 1958...' questions... Default off... Turned on after FKU apply on boot...
[Nexus 6  Original Android Development] franciscofranco:
Sure thing.
[Nexus 6  Original Android Development] franciscofranco:
r49 is out https://plus.google.com/u/0/+FranciscoFranco1990/posts/PxbmJTgkCtj
[Nexus 6  Original Android Development] pkgnex:
Thanks for the security patch, Franco.

I'll be awaiting the FKU update since I never had the BCL stability issues and prefer to keep my cores all online at all times.

I noticed that the kernel still doesn't install a virus... and all my bases still do not belong to you. :)
[Nexus 6  Original Android Development] franciscofranco:
Yeah I forgot that. This was just a minor release since I saw the CVE starting to blow up today and I found the fix. Doubt there's anyone out there with this fix already.
[Nexus 6  Original Android Development] pkgnex:
Yeah, you're the first to patch it on this device - which is awesome!

No worries on the install script.

Looking forward to the BCL toggle in FKU!
[Nexus 6  Original Android Development] pkgnex:
Not that I would expect otherwise, but r49 has been rock-solid all day (on latest stock rom build).
[Nexus 6  Original Android Development] Phrodini:
Does this kernel offer any sound enhancing?
[Nexus 6  Original Android Development] pkgnex:
Microphone and headset speaker gain only, I believe.
[Nexus 6  Original Android Development] Phrodini:
Thanks
[Nexus 6  Original Android Development] franciscofranco:
Yes. Headphone and mic.
[Nexus 6  Original Android Development] Phrodini:
Gracias..miss that in a kernel
[Nexus 6  Original Android Development] Neejay:
Thanks for the patch. Is there a way to manually disable BCL until the app update?
[Nexus 6  Original Android Development] franciscofranco:
echo 0 > /sys/module/battery_current_limit/parameters/bcl_hotplug_enable
[Nexus 6  Original Android Development] Unoid:
R49 on rooted stock MOB30l 6.0.1 , wifi won't find any networks :(
[Nexus 6  Original Android Development] pkgnex:
This has been discussed many times previously. You need to be on the July build (MOB30O) or newer for any of the recent kernels to work with wifi - this is true of almost all the custom kernels that are in active development, so it's not just a Franco.kernel issue.

I suggest you update to the latest security level, MOB30W.

---------- Post added at 08:52 AM ---------- Previous post was at 08:36 AM ----------

Hey Franco, why are my cores 3 and 4 offline? :p

In all seriousness, you might find this interesting:

I left the BCL flag on (set to 1, cat command returns "Y") and then checked periodically when running my battery down to see what would happen:

The cores weren't actually kicked offline until I hit 21%. Obviously, the phone became quite "laggy" at this point.

I then reset the flag (set to 0) as noted above in my start-up script, and rebooted - twice even - but the cores didn't come back either time even though I verified that the flag persisted at "0" (actually "N") through the reboots.

I then recharged my battery and the cores still didn't come back online even though I had charged to 50%.

I then rebooted again (with flag still set to "0") , and the cores were back online.

So, it seems that once BCL kicks the cores offline, you not only have to re-charge the battery, but recharge well over 40% and then reboot to get cores 3 and 4 back! What a PIA!

Now that my bcl_hotplug_enable flag is set to "0" on boot and my cores are all online, I'm assuming/hoping they don't get kicked back offline. I'll report back if for some reason they do.

All the above said, I echo rignfool's sentiment that BCL should be defaulted to off ("0") in future releases, with a FKU option to force it on for those few (like him) that need it for stability reasons. Otherwise, you'll get the "my cores are offline" whining in the thread again... and unlike my initial line in this post, they'll be serious.

Happy coding!
[Nexus 6  Original Android Development] franciscofranco:
That's a though one to consider. I don't even know why cores would stay offline after boot, on ramdisk I'm forcing them to be online regardless. Then if BCL is active it does its job to offline them if needed. I'll dig into it, mustn't be too hard.
[Nexus 6  Original Android Development] pkgnex:
It could be that they are forced on

during

boot, but if the battery level

after boot completion

is still less than 40%, the BCL driver kicks in and (re)off-lines the cores.

I don't have a way to monitor the cores during boot, but if the cores were offline and battery percent was below 40% when rebooting, by the time I could open FKU's system monitor the cores were still offline. The only fix was to get the battery percent above 40 AND then rebooting.

The behavior kind of makes sense to me... except that I would expect to not have to reboot when the battery gets back over 40% to get the cores back online - especially with the bcl_enable flag set to "0".
[Nexus 6  Original Android Development] franciscofranco:
I'm debugging this. So far spent 1 hour looking at the code and it seemed fine so I need to debug it a little bit.
[Nexus 6  Original Android Development] franciscofranco:
OK I figured it out why cpu2 and cpu3 stay at 2.6GHz if BCL is enabled. It seems that, when BCL is allowed to run, it turns off cpu2 and cpu3 BEFORE the system sets the governor to those cpus, so when they go back online they fall back to the default governor, performance.

I wonder if this happens on all Kernels though (it should since this 100% stock behavior) and I also wonder why I didn't dig into this sooner. My apologies.
[Nexus 6  Original Android Development] pkgnex:
No worries. Thanks for all you do!

I was just about to add an update regarding getting stuck at 2.6 GHz as well...

While this morning I had the problem of the cores being offline and not coming back, this afternoon I had to restore a nandroid (long story - google server / verizon issue, it turns out). After the restore (which was r48), I flashed r49 and booted, then turned the BCL flag to off while the cores already were offline. When I rebooted and came back up, CPU's 3 and 4 were pegged and 2.6 GHz and my phone was cooking! Another reboot "fixed" it insofar as the cores were back offline again (battery was still below 40%).

I can't believe what a mess this BCL thing is. I know it's the stock kernel code...

I still haven't had a chance to get it over 40%, turn off the BCL flag, and then let it drop back down to see if the cores stay online, but I'm assuming that will be the case, at least, so my startup script should keep me out of "BCL Hell" until you work out a fix in the kernel or add a toggle in FKU.
[Nexus 6  Original Android Development] szale9001:
Just FYI to anyone who has a similar issue, I am fairly certain you can get the cores to return to normal without rebooting. Just pop open your kernel app and change the governor to performance and then back to interactive. Pretty sure the cores that are locked to 2.6Ghz are that way because the governor for those cores is not getting changed to interactive on boot up
[Nexus 6  Original Android Development] franciscofranco:
Cores stuck at max freq has been fixed on my local build.
[Nexus 6  Original Android Development] franciscofranco:
Yes, that's what I just said, but most users have no idea what's happening. Took me a bit to understand what was going on though, so imagine users.
[Nexus 6  Original Android Development] szale9001:
Gotcha, missed your previous post on that. Either way, glad you figured it out. Thanks for looking into it.