yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] Gytole:
Will Franco work for AOSP also? I havent used franco kernel since my 2013 Nexus 7, bought the app a coyple years back and sold my tablet two months later...

Great to see it again!
[Nexus 6P Original Android Development] tehpud:
Yep. Looking forward to your solution. Haven't flashed yet as I'm on 2.65 currently. I don't have any issue going to 2.62-3, but if you have a better suggestion I'll do it.
[Nexus 6P Original Android Development] Ryanscobberwash:
Hmm I'm on su 2.64 and flashed kernel. Have no issues. :o
[Nexus 6P Original Android Development] rebretz000:
I was running SuperSU 2.64 and flashed R4 and my root was fine. No issues at all.

I was running CleanCore
[Nexus 6P Original Android Development] Gytole:
2.64 here on Pure Nexus and didnt need to reflash Systemless. Came from R3 also. First thing I checked when the rom booted was SU in the menu and its on and working fine.
[Nexus 6P Original Android Development] jasondowning85:
I auto flashed through the app and went into boot loops.

Originally using system root before flashing Franco originally (r1) flashed unsu.zip, Franco r1 and supersu2.63. Upgraded to r2 and r3 via zip files.

To fix the bootloops from r4 I went into recovery and flashed r3 and 2.63 again.
[Nexus 6P Original Android Development] :
Really excited for r4. I've been reaching 8+ hours sot on r3, so I'm gonna see hiw far we can push this. Glad you've been focusing on battery life thus far.
[Nexus 6P Original Android Development] -X5-:
Same here. Flashed r4 manually fixed the problem.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] Brembo109:
Yeah flashing the R4.zip + SU2.65 works as always

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] gakirby:
Tried auto-flashing r4 from the FKU app, had systemless 2.62-3. Ended up boot looping 12+ times before, I gave up and manually flashed back to r3 and 2.62-3 in recovery with no issues.
[Nexus 6P Original Android Development] lenixroman:
This kernel support otg
[Nexus 6P Original Android Development] Neverendingxsin:
R4 and 2.62-3 flashed fine for me, I just made it a habit to reflash SU in recovery right after flashing the kernel.
[Nexus 6P Original Android Development] jamespat93:
Manually flashing R4 and 2.65 worked fine with me. Unfortunately marvel contest of champions is still force closing. Also it is now randomly pausing the game mid battle.
[Nexus 6P Original Android Development] lenixroman:
Same problem with walking war robot i am on r4
[Nexus 6P Original Android Development] UZ7:
Flashed 2.65 over 2.64 rebooted, flashed r4 over r3. All's fine :)) been waiting for this! Thanks :))
[Nexus 6P Original Android Development] kinesics:
Heads up if you're on 2.61 SU DO NOT autoflash r4 it will boot loop you. I thought i would have to reinstall everything and then I remembered I was on 2.61

Edit: Or just read patch notes like Franco mentioned lol
[Nexus 6P Original Android Development] franciscofranco:
Well, I don't know. I tried Marvel Future Fight, played for almost 5 hours straight with r4, not a single lock-up, freeze, anything.

I'll try Context of Champions now.

EDIT: it's working fine too.
[Nexus 6P Original Android Development] franciscofranco:
I just spent some time reading Play Store reviews, and I've read some about the game crashing when the battles are starting. GPU drivers are 100% stock here, so I don't know.
[Nexus 6P Original Android Development] franciscofranco:
Anyone with older SuperSu versions, can you 'fastboot boot' the attached .img and tell me if it boots normally? Don't worry if it bootloops just press the power button and it'll reboot with the older Kernel. Thanks.
[Nexus 6P Original Android Development] belvedere:
I just wished it and Santa busted through the door. He magic'd my 6P with R4, no problem! SOT increased to 69 hours - Christmas miracle!
[Nexus 6P Original Android Development] troymz1:
Thanks [MENTION=3292224]franciscofranco[/MENTION] for another awesome update. [emoji3]
[Nexus 6P Original Android Development] mgear356:
Thanks bro, I will try marvel future fight and report back.. Haha 5hrs, are u addicted to the game now?

Edited : still getting hangs and auto close in future fight.. I am using chroma 10/12 rom r4 + 2.65 :(

EDIT2 : seems like once it hangs, even after closing the game and reload, it keeps coming back within 5mins. Experienced hang at loading screening. Gonna reboot phone to see if it persist.

EDIT 3 : after reboot, hangs at loading screen after 30mins.. Completely random..
[Nexus 6P Original Android Development] Jaisham:
I dont know if this is kernel related or not but i cant seem to get my wifi to turn off automatically when it goes to sleep. I have set it to be only active when charging when the phone goes to sleep. before it did function well but after flashing from r3 i have had this problem. updated to r4 and still the same. can anyone let me know if this is kernel related or not?
[Nexus 6P Original Android Development] jamespat93:
Hmm I'm really not sure then. Forgot to mention I'm using the latest build of pure nexus too but the game works perfectly on stock and elemental kernel.
[Nexus 6P Original Android Development] shawnaye:
Judging by everyone's posts.

I can just flash r4 followed by su 2.6.5?
[Nexus 6P Original Android Development] troymz1:
That's what I did. Works fine
[Nexus 6P Original Android Development] :
Holy **** franco, 2 hours sot and I'm still at 85% battery.
[Nexus 6P Original Android Development] Subiegsr:
Sorry for the newb question. But I would definitely would like to try this kernel out and just had some questions.

I'm currently on supersu 2.61 (only for Android pay compatibility), chroma and lean kernel. Am I able to flash r4 with supersu 2.61? Or is that strictly for r3 and older? Also, if I can flash r4 can I just flash it straight up or should I flash unsu.zip and supersu 2.61 after?

Edit: flashed r4 fine, flashed unsu and supersu again to be safe. Thanks!
[Nexus 6P Original Android Development] Rahulrulez:
Finally unlocked bootloader.. Flashing R4 :D

---------- Post added at 03:43 PM ---------- Previous post was at 02:47 PM ----------

Ok, first hurdle.. I unlocked bootloader, flashed TWRP and flashed Franco R4.. However I still can't get root access. Do I need to flash Systemless SuperSU after this? Changelog suggests I don't have to.
[Nexus 6P Original Android Development] oOuzzielOo:
Yup,you only dont have to if you were rooted beforehand

Sent from my Nexus 6P
[Nexus 6P Original Android Development] Rahulrulez:
Thanks my friend :) Flashing root now.
[Nexus 6P Original Android Development] :
WiFi issues with channels 12 & 13 (2.4 GHz)

Hello,

I noticed one annoying WiFi problem and, although it does not seem to be specific to FK, maybe someone here (? :)) might offer some insight or even a solution.

First a bit of background: at home I have two APs, both with the same SSID and security, one on channel 4 and the other on channel 13. I only use the 2.4 GHz band due to the limited reach of the 5 GHz and those two channels are the least crowded in my area.

Normally the phone can change seamlessly between one AP and the other depending on the signal strength, as expected. However if I leave my place and the phone switches to the cellular data network, upon returning WiFi no longer sees channels 12 & 13. This means that the telephone connects to the AP on channel 4 and stays there even if when sitting less than 2 meters from the AP on channel 13. Incidentally, I am located in Europe and I have a European (Swiss) SIM in the phone: here are channels 12 & 13 perfectly legal and normally used. I am using stock 6.0.1 with FK R4, but I observed the issue also with R3 and with the stock kernel (with stock it seemed worse: often I had to reboot to recover the channels above 11, with FK disabling and re-enabling WiFi does the trick). Last but not least: the APs are fine. I have other 12 devices (of which 3 running Android 5.1.1 and three 6.0.1) using the same WLAN and they all work fine with both APs. I also tried swapping channels (the two APs have different hardware and firmware) and the problem is indeed the channel frequency.

I assume that the 6P's WiFi driver is at fault here and I also assume that this is a Qualcomm binary object (closed source), but maybe I'm wrong.

Has anyone else experienced this problem? Any idea of a potential solution?

I temporarily moved the second AP to channel 11, of course, but there are other 10 APs on that channel...

Thanks!
[Nexus 6P Original Android Development] NuLLV01D:
Glad to confirm that been playing Marvel Future Fight since 1.5hrs and no force closes, lags, hangs or anything! Also, battery life has increased tremendously, even between r3 and r4! (Using r4+Stock ROM)Thanks a ton [MENTION=3292224]franciscofranco[/MENTION]

P.S. those getting FCs on the game, are you using stock ROM?
[Nexus 6P Original Android Development] 220volt:
Just flashed r4 to se how it's stands up against ElementalX. Any settings to use to get best battery life without sacrifice any performance?

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Original Android Development] NuLLV01D:
The stock balanced profile is already great at battery saving and no extra stuff needs to be done. Already got 4hrs SOT on r3.
[Nexus 6P Original Android Development] 220volt:
4hrs is not that much.

I use to get about 5 - 5,5hrs with ElementalX.

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Original Android Development] Hussainally:
Hi guys sorry for the delay.. Was moving House today.. Yeah when on r3 wasn't dozing.. No flatline on battery stats unlike on elemental.. Maybe my install was not right I don't know.. Will keep testing r4 and report in future.. Thanks guys
[Nexus 6P Original Android Development] wazka2:
My first full cycle with r3 yesterday.

Very happy, at least 1h more over the stock!
[Nexus 6P Original Android Development] handols:
I am getting a boot loop after installing R4. Tried installing it via zip and fku updater with SuperSu 2.65
[Nexus 6P Original Android Development] troymz1:
I flashed the zip in twrp then SuperSU 2.65 and had no issues
[Nexus 6P Original Android Development] NuLLV01D:
I play a lot of games incl XCOM. So battery life takes a hit. Still getting 4hrs SOT is awesome IMO
[Nexus 6P Original Android Development] Bxrider117:
Good morning,

I'm using R3 and su 2.61 because I like using Android Pay. If I want to use R4 and Android Pay, what would be the process. I tried

1. Load Chroma

2. Unsu.zip

3. Franco's R4

4. SU 2.65 zip

When I go to Android Pay I get an error. Do I not need to flash unsu.zip any more.
[Nexus 6P Original Android Development] 220volt:
Sounds good! I never play on my phone so this looks promising.

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Original Android Development] SuperQvas:
I was trying to get an answer from Franco, but if you are right, then that wiuld mean I wasted my money for the FKU.

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 6P Original Android Development] mystertom101:
I just was getting to like 5 hours 10 mins on stock now on cataclysm with franco I get the exact same roughly its not bad though
[Nexus 6P Original Android Development] xUniverse:
Just a short question, what rom are you using ? with Franco kernel :)
[Nexus 6P Original Android Development] senthilrameshjv:
8h sot? No location.?no wifi? No data? No g now?

How do people even get more than 4 h sot I am not able to understand, when I struggle to reach 4..i can only do it if I have location in batter saving.. High accuracy I can never do.
[Nexus 6P Original Android Development] rebretz000:
You need to disable the XBIN folder in SU.

Also not sure if you need the UNSU.zip.

Does Chroma come with Systemless SU?

Flash ROM/Gapps

go to advanced in TWRP, press Terminal, press the little box in the bottom right.

type the following

echo BINDSYSTEMXBIN=false>>/data/.supersu

echo FSTABSYSTEMRW=true>>/data/.supersu

echo SYSTEMLESS=true>>/data/.supersu

you only need the first and last but I always add the 2nd also.

flash Franco

flash SuperSU

I'm currently running CleanCore with Franco r4 and SuperSU 2.65 and Android Pay works.

---------- Post added at 09:00 AM ---------- Previous post was at 08:57 AM ----------

Signal strength is a factor. It's impossible to compare Screen Time. No two use their phones the same way with the same apps.
[Nexus 6P Original Android Development] Rahulrulez:
On Franco R4, tweaked doze configuration just a little bit.. Idle battery drain is almost none now.. 5% in 1.3 hours with 30 minutes of SoT.. This is going great. Will keep updating :)
[Nexus 6P Original Android Development] senthilrameshjv:
this is how my signal looks
[Nexus 6P Original Android Development] aeppacher:
Used the app to update to r4 last night via autoflash. Phone went into bootloop after. Can't get into recovery, bootloader, or boot. Usb won't recognize either. I was running stock with r3 supersu 2.46. Guess I am gonna have to RMA
[Nexus 6P Original Android Development] Phazmos:
I bought the app when it came out, and never use it. But I don't consider a donation to a dev, especially a good one,a waste of money.
[Nexus 6P Original Android Development] rebretz000:
Looking at that I'd say your cellular signal is below average. I notice mine battery drains faster when I go into a bad signal area. So add your signal strength with the screen being on in that area will drain faster than if you are in a strong signal area.
[Nexus 6P Original Android Development] x.Orville.x:
Where i can find the the latest su?? I can find
[Nexus 6P Original Android Development] rebretz000:
http://xdaforums.com/showpost.php?p=64161125&postcount=3
[Nexus 6P Original Android Development] Didgeridoohan:
If you click the link in the "nope" you quoted you'll get Franco's answer...
[Nexus 6P Original Android Development] mgear356:
Nope, I am on Chroma.. How did u get it to work? However it doesn't hang or freeze with elementalx, lean or kylo

In my last gaming session, strangely I got it to work for the last 1.5hrs also.. No hangs at loading screen or freeze during gaming.. It seems completely random.
[Nexus 6P Original Android Development] :
I see quite have people a few pages back saying they got bootloops after updating the kernel. For me I am running stock odex rom, same as the rom that came on phone but the rom is rooted with system-less root, supersu 2.61. So when I update kernel I flash kernel then supersu 2.61, reboot and all is good. Im thinking wrong version of supersu was flashed.. Anyway hope that helps someone. Being here reminds me of back in the Galaxy Nexus day. It was live back then! Literally hundreds of posts a day. Ha-ha. I'm going to mess with colors and see if I can get it how I like. Hope we can have the profiles like we have before in the app. That was super bad ass! I know Franco is busy as he stated on G+. Wish I was educated in that area.. I'd buy a color control app in a minute for this kernel. Js. Color and sweep to wake/sleep are my personal fav kernel features. I drank too much coffee. [emoji15] [emoji15] [emoji15] Gonna run this a few days and see what kind of battery I get. I'm quite confident it will be a good outcome. Happy New Years to everyone. 2016 is going to be great! [emoji12] [emoji12] [emoji12]

Sent from San Antonio Tx- Nexus 6p
[Nexus 6P Original Android Development] jasondowning85:
I had the same issue and was trying to hold the power button to get the phone to turn off with no luck, so I just held volume down and power while it was stuck in the boot loop and finally got into the bootloader which allowed me to get to recovery.
[Nexus 6P Original Android Development] ViciousMo:
So, we can't run R4 with latest version of SU? I'm on R3 on 2.62 SU.
[Nexus 6P Original Android Development] DocteurN:
I'm using r4 with su 2.65 with no problem under chroma 10/12 :D
[Nexus 6P Original Android Development] Brembo109:
You can. But you have to manually flash both zips like before. I'm running it right now

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] franciscofranco:
Can you repeat your question?

Stock.

Of course you can access bootloader. Auto-flash just writes to the Kernel block, the rest is intact. Just power button and vol up (or down, I never remember) and you'll be on bootloader and you can access recovery to flash superSu. Everything is well documented in the change-log.

You can, but if you're on 2.62-3 you don't need to re-flash SuperSu.
[Nexus 6P Original Android Development] aeppacher:
Something unrelated must have happened then. Can't access bootloader or recovery. Power + Volume down for bootloader. Volume up for recovery. No clue what happened
[Nexus 6P Original Android Development] franciscofranco:
Then that's not Kernel related or FKUpdater related or anything like that, it's impossible. Maybe you're out of battery?
[Nexus 6P Original Android Development] SuperQvas:
A reply if I may, if I buy something, I am gonna use it, if that something turns useless my money is wasted. Mine wasnt a donation to a dev but a purchase from a dev.

I like Franco but there must ne other solutions around.

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 6P Original Android Development] rebretz000:
It seems like the people bootlooping are auto flashing the kernel from the FKU app.

I flashed r4 through TWRP and mine booted fine. I was on SuperSU 2.64 so even though r4 had SuperSU 2.63v3 I had no issues. Android Pay still worked and my disabling of the XBIN folder was still in effect.

I was running CleanCore
[Nexus 6P Original Android Development] SuperQvas:
Thanks, I thought it was my browser giving me fake links.

Sad but I will find an alternative

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 6P Original Android Development] rebretz000:
Don't even attempt to blame Franco. You failed in the first rule. You didn't read. Did he say he was going to support the 5X? No he did not. You bought the app expecting him to make a kernel for it when he never said he would. It's your own fault. You bought the app on your own, he didn't tell you to.
[Nexus 6P Original Android Development] SuperQvas:
I got my answer so thanks

Inviato dal mio Nexus 5X utilizzando Tapatalk

---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------

Can't see where is i am blaming Franco.

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 6P Original Android Development] aeppacher:
I wish I were. Its switching between the warning the bootloader is unlocked screen and the plain google screen. Can't even get to bootanimation. Something else must have done it then. Maybe volume rocker is broken? Either way going to have to RMA it
[Nexus 6P Original Android Development] Brembo109:
Man, you are in a normal bootloop. Press Volume down + Power, in bootloader navigate to "Boot to recovery", from there flash an old version of the kernel + Superuser or restore a backup. If you have neither of them, you have to use a Nexus toolkit to return to stock.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] aeppacher:
This may come as a shock to some people but I know how to boot into recovery and bootloader. My device is ducking bricked. Not saying it is francos fault or even the result of FKU, just first thing I checked since it happened right after I flashed r4. Definitely something else but dear god please stop telling me to boot into recovery
[Nexus 6P Original Android Development] mindfever91:
Even if he doesn't have the files on his internal storage, he could still do an 'adb push' command from his PC while in recovery if I'm not mistaken.
[Nexus 6P Original Android Development] nathanchance:
TWRP even supports MTP so you can just plug in and drag files over.
[Nexus 6P Original Android Development] Brembo109:
Yeah, but given that he can't help himself to this point I assume he can't do a add push either. I pointed out the fail proof ways. There a plenty of options excluding RMA

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] franciscofranco:
[KERNEL][GPL][N6P] franco.Kernel - r4

I'm sorry for insisting, but there's no need to RMA. If the device boots up into that Warning corrupted something and then proceeds into Google's logo then your device is NOT bricked. Brick means no matter what you do the device doesn't even inits the bootloader so nothing happens, ever. I bricked my first N5 once because I mistakenly flashed a corrupt bootloader image into its partition. I spent a couple sleepless nights trying everything you can possibly imagine, every obscure LG tool etc. I only have one Debug port being detected by my computers USB port. That's a brick. Instead of panicking I suggest you take a deep breath and make sure you're hitting the correct booloader key combination in its correct timing. I'm trying to help so don't be mad at me.
[Nexus 6P Original Android Development] franciscofranco:
[KERNEL][GPL][N6P] franco.Kernel - r4

I never said I would support the N5X, but I ve had so many requests that I'm still considerig if shelling out 450 euros to never use it as a phone is a good investment.
[Nexus 6P Original Android Development] rebretz000:
That is my bad. I misread and misinterpreted what you wrote.

I apologize for what I said/wrote.
[Nexus 6P Original Android Development] franciscofranco:
Guys I need some help. I need your opinion on this.

1. Should I add support for SuperSu 2.65 so that you don't have to reflash it after ever kernel flash, but potentially causing bootloops on older SuperSu releases (and maybe newer ones until I add support for it)

2. Remove built-in SuperSu ramdisk changes and users can reflash SuperSu after a Kernel flash regardless

Please vote.
[Nexus 6P Original Android Development] aeppacher:
I understand but to be honest there is nothing I can do. I can hold power to restart it but beyond that it won't boot to recovery, bootloader, and my computer won't recognize it nor will adb. It just keeps bootlooping. Not sure what else there is to do beyond rma it?
[Nexus 6P Original Android Development] rebretz000:
remove it. We can reflash SuperSU. It's only one extra step and that will eliminate possibility for the bootloops.
[Nexus 6P Original Android Development] Gytole:
Agree, flashing SU takes 2 seconds.

Very courteous gesture of combining but if is a dancing tumor in your brain just nix it for the moment.

Once again no problems here though.

I personally like the combined kernel/su but I can understand where it would be more headache due to people not reading changelogs if you were to say, "Hey starting on this kernel preflash 2.6*SU befote AIO takes over.

Thanks franccooooo
[Nexus 6P Original Android Development] igalmarino:
2

Sent from my Nexus 6P
[Nexus 6P Original Android Development] remeic:
For me 1
[Nexus 6P Original Android Development] kinesics:
I'm with option 2, if people can flash an update they can take two seconds to flash SU. Save yourself the headaches of the zillion bootloop questions.
[Nexus 6P Original Android Development] lenixroman:
Option 2
[Nexus 6P Original Android Development] Vangelis13:
2, because nobody reads anymore so 1 will end up being a right cluster feck. Nobody has time with dat..
[Nexus 6P Original Android Development] johnandbodhi:
option 2 - no big issue flashing supersu after flashing yer kernel..
[Nexus 6P Original Android Development] franciscofranco:
How about you hold power and vol down until it restarts and leave them pressed until bootloader is up? Thats what I do.
[Nexus 6P Original Android Development] Baby_Phil:
2.
[Nexus 6P Original Android Development] Casyis:
Option 2. It's no hassle to have to reflash and I prefer to do it to avoid problems. Also it's one less thing for you to have to maintain.
[Nexus 6P Original Android Development] frost_nz:
Let's go 2 - otherwise the thread will get overwhelmed with people reporting boot loops that haven't bothered to read....
[Nexus 6P Original Android Development] vimmer77:
I vote for option 2 as well.
[Nexus 6P Original Android Development] Craxx:
option 2

best regards

Craxx

Sent from my Nexus 6p