yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] relaxable:
Update to my prior post from a day ago where was stuck on boot animation & went back to r63...

Tried flashing r64 again with TWRP - and this time - it worked - booted. Seems stable. Rebooted after some hours and again started up fine. It seems that there is a longer delay after I enter my PIN at the first security screen, with the 'Android is Starting...' text displaying much longer before the boot animation resumes, but no problems, no stuck, no bootloops...

(Yesterday, I had tried to flash r64 with TWRP after having the stuck on boot animation with the app's auto-flash - but that was flashing r64 over r64 where today it was r63 to r64...)
[Nexus 6  Original Android Development] firewhank:
I'm having some trouble on my per app profile. I set the input boost frequency to 1.3 GHz and only the first core stays in that frequency. The rest use the default one 1.7 GHz. Anyone know why?
[Nexus 6  Original Android Development] franciscofranco:
How odd is that. I just reproduced it. Dunno if it's a bug on the app or Kernel. Will check. Thanks for the report.
[Nexus 6  Original Android Development] firewhank:
And happens exactly the same with my Nexus 5 ?.

So maybe it's the app and not the kernel.
[Nexus 6  Original Android Development] franciscofranco:
Yeah it's a bug on the app. Wow, how long do I have this bug here and I never noticed.
[Nexus 6  Original Android Development] Surge1223:
To all 3:

I think the better idea would be just to adapt setools natively for android via ndk. Since sepolicy-inject already is a variant of available tools and depends on several setools libs (libsepol, libapol, libqpol etc) it might be smarter to just use make the tools already available to be ndk buildable.

Most of the libsepol repos I see on git have hardly any edits to source for android (such as the path differences, especially in regards to where to find policy on device, not to mention the lack of ability to change loaded policy)

sechecker, sediff, seinfo, sesearch, dispol, dismod, and checkpolicy are only a few of the vast array of sources that can already expand on what sepolicy-inject does.

At this point, race for which su/sepolicy tool can be the best is just dumb. Fragmenting is ridiculous.
[Nexus 6  Original Android Development] franciscofranco:
Your suggestion makes sense to me. This fragmented Root method scene is already getting out of hand anyway.
[Nexus 6  Original Android Development] fiverings:
I installed PN 1/21 update, clean flash, full dynamic Gapps, used Nexus tool kit to install root, twrp, super su and the other things it installs, like busybox.

On my Nexus 6.

My battery drain is bad, I used to lose 5-8 % overnight and now it's 20 or more %

Will the Franco Kernel improve this and can I install it now or do I have to wait for the next PN update
[Nexus 6  Original Android Development] dark2099:
Double check any apps aren't holding the phone awake, also, learn how to not use a toolkit, much easier than you think.
[Nexus 6  Original Android Development] Merazomo:
As I mentioned before in a previous post, this Kernel and the Stock Android ROM is all I need; however, seeing that the N6 is less than a year away from being officially unsupported, is there a way that one such as myself can keep using the N6 with the Stock ROM and this Kernel, long after that safely? If Custom ROMS are still being released after that, would it be safer to use one of those?

My N6 has been running better NOW than when I first got it. That's the truth. I apologize for not knowing how Android truly works. I'm somehow imagining that it's kind of like Windows XP, which I used long after it was no longer supported without any problems, by installing an Anti-virus and Anti-Malware program that still supported the OS. Again, I apologize for my ignorance on the subject. I just hate upgrading devices or getting rid of phones and stuff like that, when they're sometimes better than some of the so called newer better devices.
[Nexus 6  Original Android Development] Venkatesh1406:
Well I tried to update my kernal through the app but unfortunately my Android was not booting , so I did a factory data reset . But when I opened my phone after factory data reset , Franco kernel was already installed .

Pls answer this question

1) Do I need to install Franco Kernel again

2)Does franco kernel add any kernel setting in the setting menu ?
[Nexus 6  Original Android Development] relaxable:
Back to r63 again (stuck on booting returned!)

As title says - although I've rebooted several times since successfully getting r64 running with my n6, this afternoon, phone rebooted and got stuck on the boot animation. (This was an unplanned reboot - I have a case that use to clip to my belt and this case often presses volume/power buttons unintentionally which sometimes causes phone to reboot - have had this occur often, but never had it fail to reboot until this r64..!)

Had to go into recovery and reinstall r63 to get running again...!
[Nexus 6  Original Android Development] usafle:
+1 Same issue with me. Soon as I install 64, I get a bootloop. Never got the phone to turn on with R64. Had to roll it back via TWRP. Thank goodness the app backs up previous kernels.
[Nexus 6  Original Android Development] Luny Lennon:
I Never Issue and Problem in Franco kernel r64 ( Nexus 6_ 7.11-7th February )
[Nexus 6  Original Android Development] gk1984:
And if it helps at all - updated with the app, auto flashed, no issues. Reboots just fine. Stock ROM with ARISE installed and Magisk.
[Nexus 6  Original Android Development] wewlad123:
Can us mob31s (Jan 2017) 6.0.1 users get some love? I feel like there's a lot of people who haven't upgraded to nougat for obvious reasons.
[Nexus 6  Original Android Development] usafle:
I've tried manually flashing and auto flashing neither makes a difference, goes into a boot loop on the newest kernel

I'm running ChainFire SU and no Xposed or anything of that nature.
[Nexus 6  Original Android Development] adm1jtg:
xposed are you on a 6.x build aka marshmallow?
[Nexus 6  Original Android Development] usafle:
Nope

7.1.1
[Nexus 6  Original Android Development] adm1jtg:
ok well no issues here installed on both RR NEO version and PN. Installed via zip in twrp
[Nexus 6  Original Android Development] MrBrady:
7.1.1 Pure Nexus using r64 kernel. Unable to boot once Magisk is installed. Anybody else have this issue or have tips to resolution besides SuperSu?
[Nexus 6  Original Android Development] adm1jtg:
I am using phh superuser

https://superuser.phh.me/

use the 259 zip then load phh superuser apk from playstore
[Nexus 6  Original Android Development] Didgeridoohan:
Pure Nexus 7.1.1_r13 here with both FK r64 and Magisk v11.1 (MagiskSU). No problems.
[Nexus 6  Original Android Development] maximumentropy:
Stock N6F26R + SuperSU 2.79 bootlooped with r64 from updater app. OK with r63 flashed from TWRP.
[Nexus 6  Original Android Development] manojpy:
Been using r64 since day one and flashing with Twrp. Have had no bootloops or random reboots. Stable and smooth.
[Nexus 6  Original Android Development] adm1jtg:
Just did more testing and still no failures. Loaded up PN 2/15 then added Franco via twrp... it booted fine.... then added in magisk 11.1 and still no issues. For those having issues are you trying to install Franco and magisk in one pass? As I did mine as 3 steps. Load rom and gapps, reboot, load franco, reboot, load magisk. Might work other ways but this is the process I used that worked perfectly for me.
[Nexus 6  Original Android Development] xtc_24:
r64 booted up just fine with PN 2/15 here.

SU v2.79 stable
[Nexus 6  Original Android Development] MysticKing32:
R64 boots perfectly with new pure Nexus. No bootloop at all. Flashed everything in one go. Rom gapps magisk Franco. In that order. No problems at all
[Nexus 6  Original Android Development] xpose17:
Need help

Hi I'm running dark ROM on Nexus 5 and I recently flashed this kernel on it. But for some reason Snapchat isn't working. could use some assistance. Thanks! :D
[Nexus 6  Original Android Development] gideonlfc:
You do realise that this kernel is for Nexus 6 right?

I'm surprised your phone even booted up
[Nexus 6  Original Android Development] usafle:
No. Just installing / flashing the kernel by itself.

I've tried to wipe cache and data before a flash and after, makes no difference. R64 just won't work.
[Nexus 6  Original Android Development] maximumentropy:
Same here. Flashing r64 gives a bootloop, I reboot to recovery then flash r63 and it boots fine. No other changes.

My N6 is encrypted. Pure speculation, but I wonder if r64 is having trouble booting on encrypted devices.
[Nexus 6  Original Android Development] githyanki:
Is not encryption, mine is encrypted since release, I did not have any issues until the update last night. I had been flashing nightly's of AICP and the kernel at the same time.

Last night, it never finished booting. Wiped system, flashed rom, gapps, and kernel. Still did not finish boot. Wiped system again, flash rom and gapps, booted up fine. Then I flashed r64 from twrp, it would not boot again. Flashed rom, booted up and downloaded r63, flashed that and it booted up just fine.

Something AICP did in the last 3 days did not agree with r64.

They had changed to Magisk for root a few days before that, so I don't think it's that. I did have to wipe system and flash everything that time also, but it worked the first time.
[Nexus 6  Original Android Development] enzoevo:
Hey [MENTION=3292224]franciscofranco[/MENTION], I see you list the SafteyNet bypass in list of features. However, I don't see the commit in your Shamu repo. Are you doing something different from the cmdline.c patch, or am I just missing it? Thanks.
[Nexus 6  Original Android Development] adm1jtg:
Not sure what the commit may look like but I can tell you saftynet passes with his latest.
[Nexus 6  Original Android Development] maximumentropy:
Interesting but it's not just AICP since I'm having the same problem on stock 7.1.1. Also not Magisk - I'm using SuperSU. It all seems very random.
[Nexus 6  Original Android Development] adm1jtg:
Are we all running the latest bootloader version?
[Nexus 6  Original Android Development] githyanki:
Yes, random. Today's nightly flashed with r64 at the same time. No issues.
[Nexus 6  Original Android Development] MandoH:
Nevermind
[Nexus 6  Original Android Development] NLBeev:
My N6 is decrypted. Debloated stock rom 7.1.1. Never issues with fk. Now using r64.
[Nexus 6  Original Android Development] Cobra11Murderer:
Custom Roms will be released even after that, the only thing that might hamper that would be Google stop making 32bit which isn't gonna happen for now. So yes installing a custom ROM specifically one that gets updates will be a good choice for a few more years. I've been running neo resurrection remix runs great but if your just dabbing in I'd go with linage ROM. In any case nexus toolkit helps yah big time just read up a little bit and back up your phone before doing anything on it.

Side note kernel is doing great on neos I'm so happy that I purchased your app franko it's helped alot. Not just on my n6 but also n7 2013
[Nexus 6  Original Android Development] tuanpz0:
Best kernal for battery life

best best <3 best battery for standby :3
[Nexus 6  Original Android Development] rignfool:
[MENTION=3292224]franciscofranco[/MENTION]

This is most likely an FKU issue... But my phone will not automatically come out of the powersave profile when I get above the preset threshold...

I know this because I flipped the 'put me in battery saver' switch...

What would you like from me to help you?
[Nexus 6  Original Android Development] Axel85:
Hi, I have a question to ask you, since you're running Franco kernel on a nexus 6 and a nexus 7 2013 exactly like me. Yesterday I noticed that when I turn on or the device go to battery saving mode I can't surf the internet, in nexus 6 the problem is present in wi-fi or mobile data mode. The only thing my 2 device shares is the fk . Do you have the same problem? I m running pure nexus on the 6 and resurrection remix on the 7
[Nexus 6  Original Android Development] gideonlfc:
I'm surfing the internet as I type and I have battery saver on. No issues here
[Nexus 6  Original Android Development] mikejr83:
Hey guys,

I was using Franco's kernel a long time ago. Had some hardware issues with the phone and have had a new one on bone stock for a good while now. Been out of the loop so forgive me if these are a bit noobish. I've looked around and haven't found any posts that are from a recent timeframe so I don't know if these questions are valid.

I'm on the latest official DU (no weekly or anything). I've rooted it (DU isn't pre-rooted anymore), setup FK Manager, and auto flashed r64. Upon reboot I just hang at the ROM's boot screen. I've waited around 15min before going back to recover and running the supersu flash for root which gets me back to a bootable state. Any thoughts as to what could be happening? For the life of me I can't recall how to get logcat on boot. For some reason it just doesn't want to work (a little help there, please).

I read (somewhere on a different FK thread for another device) something about auto flash not working correctly. I didn't look at the timestamp on the post but should I try flashing from recovery instead?
[Nexus 6  Original Android Development] githyanki:
Flash R63. This is a known issue, but the logs don't show why it is happening. Sometimes it works, sometimes not.
[Nexus 6  Original Android Development] mikejr83:
That worked. Running R63 fine now!
[Nexus 6  Original Android Development] titaniumcocacola:
this kernel disable throttling (when the battery is 50% or less) ?
[Nexus 6  Original Android Development] Jakeor2:
Screen glitch

Has anyone run into this same issue while running the latest Franco Kernel?

https://xdaforums.com/nexus-6/help/wierd-screen-glitch-issue-t3525101

It happened to me while running pure nexus and elementalX, then moved on to LineageOS and Franco kernel and it started happening again. Is this a known bug for Franco Kernel? What's the proper way to fix it? I have tried to change it when I was on elementalX with an app, but the settings dont seem to stick. I purchased the franco kernel app and installed it that way. It's been good besides that.
[Nexus 6  Original Android Development] githyanki:
It is a hardware issue and happens on almost any kernel other than stock. Use interactive governor for best fix, or stock kernel
[Nexus 6  Original Android Development] Jakeor2:
That sucks, I had no clue. Ok, I'll try changing it over to the interactive governor, and see how it goes. Thanks
[Nexus 6  Original Android Development] pkgnex:
Wait for r65 on March 7.1.1 security update!

To save others the frustration I had - it appears something in the March update isn't playing nice with r64 regarding the phone speakers. When I flash r64 on the March update, I have no sound (rings, alarms, notifications, music, or anything else) coming from the phone speaker. With stock boot.img, no such issues.
[Nexus 6  Original Android Development] elkay:
Might be related to the speakerphone fix included in the March build.
[Nexus 6  Original Android Development] pkgnex:
Could be!
[Nexus 6  Original Android Development] franciscofranco:
New Franco Kernel version for the Nexus 6

r65

DO NOT FLASH THIS IF YOU'RE NOT ON MARCH 2017 SECURITY PATCHSET OR IF YOUR CUSTOM ROM DOESN'T HAVE THE LATEST SOUND BLOBS FROM MARCH 2017 SECURITY LEVEL SOURCE DROP

1. Merged the latest security patches from the March 2017 Security patchset

2. Merged additional security patches from Google's AOSP Kernel common tree

zip: https://kernels.franco-lnx.net/Nexus6/7.1/anyKernel/fk-r65-anykernel2.zip

Franco Kernel Manager & Updater is the best companion for this Kernel (https://play.google.com/store/apps/details?id=com.franco.kernel)

If you don't (yet) have my full featured app you can always just download its free counter part which lets you seamlessly and automagically update Franco Kernel on your device. It's free and my cat approves! (https://play.google.com/store/apps/details?id=com.franco.kernel.free)

I also strongly suggest you install Naptime (https://play.google.com/store/apps/details?id=com.franco.doze), for free, to achieve the best battery life through out the day. Try it, you won't be disappointed!
[Nexus 6  Original Android Development] pkgnex:
r65 is running like a boss, boss!
[Nexus 6  Original Android Development] githyanki:
Bookmarked so I can quote it the next few weeks when people install this before their rom is updated.
[Nexus 6  Original Android Development] nada324:
I have some force closes when battery is below 50% in Google + app with r64 version and Pure Nexus rom

Enviado desde mi iPhone utilizando Tapatalk
[Nexus 6  Original Android Development] wavedashdoc:
Boot looping with R65. Was able to boot elemental x March update.

I might be in a unique situation, I'm still running an older ROM, because of stability. The ROM uses the 7.0 blobs before the whole issue with the speakerphone. It's 7.1.1 though. Developer hasn't updated in awhile and I understand Franco, if something was changed I can just jump back to your r58 which I was previously on.

Edit: yes I did read the disclaimer. I'm more interested in why elemental works, sound included, on this build vs yours. I was able to get past the first boot splash, entered in my passcode then stuck a that animation.
[Nexus 6  Original Android Development] gk1984:
FYI, speakerphone fixed in March update. No need for the older ROM for that purpose
[Nexus 6  Original Android Development] franciscofranco:
Not Kernel related.

I don't know about other Kernels, sorry.
[Nexus 6  Original Android Development] elkay:
If anyone manages to pass SafetyNet with R65 let us know what you did here. There are even people not rooted failing the check now.
[Nexus 6  Original Android Development] franciscofranco:
Yeah, I'm unrooted on my Pixel and no System changes what-so-ever, just with FK flashed, and it's tripping SafetyNet. No idea what it might be.
[Nexus 6  Original Android Development] garywojdan81:
Uncheck USB debugging?
[Nexus 6  Original Android Development] franciscofranco:
Well, that worked. It's passing the check now.
[Nexus 6  Original Android Development] garywojdan81:
Good. Saw it on another forum as a workaround/fix
[Nexus 6  Original Android Development] requiiiem:
Stock march 7.1.1 USB deb off

But Pokémon Is working fine:eek:
[Nexus 6  Original Android Development] franciscofranco:
Dunno. That's beyond my control.
[Nexus 6  Original Android Development] gk1984:
I'm having stability issues but unsure if it's the March update or the kernel. Not very familiar with logs, but would that help determine?

Issue is random reboots when driving using navigation on Google maps with Android Auto (on my phone, no car integration) and streaming music with Google Play Music. I'm usually charging at the same time and thought that might be related but tried this morning without charging and it still happened.

Yesterday driving home from work doing this, it was fine for maybe 10-15 minutes, then it would just reboot within minutes doing the tasks I described. Same scenario this morning. I tried navigation by itself after a reboot and worked just fine for about 10 minutes (no music streaming, no Auto). Obviously haven't had time to really test much though.
[Nexus 6  Original Android Development] Didgeridoohan:
OT, but Pokemon doesn't check the CTS profile only Basic integrity.
[Nexus 6  Original Android Development] franciscofranco:
Dunno. Can be 293084234 things. Post /sys/fs/pstore/console_ramoops and I'll try to see what causes it.
[Nexus 6  Original Android Development] gk1984:
Yeah, I figured. Just didn't want to blanket blame the kernel. Would it be more helpful to pull the log after this occurs or any time? And I appreciate the help.
[Nexus 6  Original Android Development] franciscofranco:
Next time it occurs pull that up for me. Best if you paste it on pastebin or something.
[Nexus 6  Original Android Development] franciscofranco:
New Franco Kernel Manager & Updater 2.2.7

1 - Added full support for the One Plus X

2 - Added an option to change governors per-cluster

3 - Added a new Per-App Profile option to change Maximum Display Brightness

4 - App features were abstracted to allow other devices not in the supported list to access them (if they have the Kernel support of course)

5 - Fixed a frequencies bug on Per-App Profiles. If you have profiles which reproduce this bug you need to delete & re-create those profiles (sorry)

https://play.google.com/store/apps/details?id=com.franco.kernel﻿
[Nexus 6  Original Android Development] gk1984:
Thanks again. Here's a log from the last time this occurred exactly as I described earlier -- [url]http://pastebin.com/CxWrLa6W[/URL]

This just occurred while browsing on my phone, not streaming music, navigating, or using Auto. [url]http://pastebin.com/dhMf2unC[/URL] -- looks like a lot of sections that make no sense in this one.

My setup is Nexus 6, stock ROM (March security update since these problems started), Magisk, ARISE, and your kernel, version 65.

EDIT: this morning I reverted back to the February update and planned to push the OTA but found Google pulled the OTA and factory images for March. Originally, I pushed the full factory image. If you do/did look at the logs, great. Maybe you found something I can benefit from. But if not, no problem. Looks like Google acknowledged a problem which is why they were pulled. Maybe that related to my issues, maybe not.
[Nexus 6  Original Android Development] franciscofranco:
Those logs are cut off, they're not complete. I saw you're running F2FS, you should try and use the default filesystem.
[Nexus 6  Original Android Development] gk1984:
Thanks for taking a look. I have not made any intentional attempts to change my file system. Not sure why it's reporting that. Could it be Magisk trying to determine the file system? I'll look more into this. And those logs are as I received them. I selected all and copy/pasted to pastebin. Not sure what happened there. I'll just see stick with the Feb. update until Google fixed the now pulled March update and take it from there. But I'll double check my filesystem setup and see what's going on there.
[Nexus 6  Original Android Development] elborak:
I've always used the interactive governor and that doesn't fix it for me. The only way I've ever found of avoiding this is to stick with stock (or extremely close to stock) kernel.
[Nexus 6  Original Android Development] franciscofranco:
The issue is present since day 1, regardless of rom or Kernel used. Some devices manifest it more often than others.
[Nexus 6  Original Android Development] S0UTHPAWK1LLA:
Disable HW overlay under developer settings. You'll have to redo it whenever you reboot.
[Nexus 6  Original Android Development] relaxable:
Not directly related to the Kernel - but to Naptime which is promoted in this thread (don't see a naptime thread):

Would like to know WHY does Naptime "aggressively" try to make outbound Internet access to various hosts

I installed Naptime, and use AFWall Firewall - seeing no need for an app like Naptime to use Internet, have it blocked by firewall and get persistent and frequent notifications of Naptime's attempt to access Interenet. Why?

And, when it fails, why does it keep trying over and over and over and over? Ip addresses blocked include 23.21.222.252, 23.21.59.163., 107.21.98.91, 54.243.89.65 and many more... (all seems to be AmazonAWS ip's)
[Nexus 6  Original Android Development] franciscofranco:
It's the ads, I don't have any control over that.
[Nexus 6  Original Android Development] franciscofranco:
Speakerphone echo thing fixed on the latest March release it seems.
[Nexus 6  Original Android Development] franciscofranco:
Is it just me or this forum is kinda dead?
[Nexus 6  Original Android Development] Phrodini:
All in working order in most cases
[Nexus 6  Original Android Development] gk1984:
Dead, but that's ok. A lot of N6 users have moved on and most people post to report problems. Looks like all is good for the moment. Unless you don't have enough to do.