yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] Lawlrus:
Or people can just read before flashing
[Nexus 6P Original Android Development] franciscofranco:
r57 is out, started from scratch and all seems ok, no more weird Twitter app crashes or random reboots. Starting from scratch is a lengthy and boring process. Let me know if all is ok!
[Nexus 6P Original Android Development] mprziv:
Franco rocks!
[Nexus 6P Original Android Development] franciscofranco:
Thanks for all who reported issues etc. Major Android release upgrades are always messy and slightly annoying.
[Nexus 6P Original Android Development] pvtjoker42:
just flashed r57, on first boot i got a FC at the unlock screen (at boot up) but then it booted the rest of the way fine.

I just rebooted to get the exact FC error, but it didn't come up this time. However, it did reboot just after the unlock, and now is showing no sim. Powered my phone down, brought it back up.. no fc's and now sim is working. So i'll keep playing with it and see if I can get through the day with it or if i have to go back to stock.
[Nexus 6P Original Android Development] franciscofranco:
It can be caused by 34984395 different things. This is a very clean Kernel build, couldn't reproduce any of the issues being reported before hand.
[Nexus 6P Original Android Development] rizqi_ir:
thanks master! it works fine now
[Nexus 6P Original Android Development] hern1989:
Same issue for me. I flashed r56 in the morning and it was bootloping. Thanks for the fix. Will reflash again. Cant live without franco kernel. Lol
[Nexus 6P Original Android Development] mongonexus:
hey FF, i had one reboot at the lock screen after installing fk app, more like a quick reboot, app still shows r1 as version, im assuming the app is having something to do with it??
[Nexus 6P Original Android Development] elitistphoenix:
Seems a lot better than the last build. This is only after half an hour of testing though. Thanks!

Here is what the app shows so you know what everyone is talking about :)

[IMG="Franco App saying R1"]http://i.imgur.com/Ir88iZv.png[/IMG]
[Nexus 6P Original Android Development] ahpatel:
On Oreo, r57 installed successfully over stock kernel. FK Manager app is laggy. when switching sections (even after clearing data and rebooting for safe measure). For example, switching to "Battery Labs" results in ~5-20 second delay. Kernel and CPU settings seem to have a brief ~1-2sec delay. Other sections seem normal (like Backup or Automation).

Note: this is with Magisk 13.6 (but that wasn't an issue with FK and any of the O Dev Preview versions.
[Nexus 6P Original Android Development] eak1080:
It's been laggy with magisk for a few versions now...since magisk 13 I think
[Nexus 6P Original Android Development] sjancura:
Odd that I have no lag on Superex 8.0 with r57. Wonder what the difference is?
[Nexus 6P Original Android Development] revanmj:
I also have a bootloop. I tried those configurations (flashing in that order):

Stock boot.img + fk57 - bootloop

Stock boot.img + fk57 + Magisk 13.3 - bootloop

Stock boot.img + fk57 + Magisk 13.6 - bootloop

Stock boot.img + Magisk 13.3 - works fine

It seems there is an issue with userdata as colors don't change to sRGB during bootanimation (which happens almost right after beginning the animation when system boots properly).
[Nexus 6P Original Android Development] billycar11:
mine wont boot on 57 rip me
[Nexus 6P Original Android Development] preducer:
same here, boot loop on r57
[Nexus 6P Original Android Development] mobileman88:
Stock boot.img + fk57 - works fine

Stock boot.img + fk57 + Magisk 13.3 - works fine

Stock boot.img + fk57 + Magisk 13.6 - bootloop

Stock boot.img + Magisk 13.3 - works fine
[Nexus 6P Original Android Development] franciscofranco:
Yeah guys look, Oreo is pretty fresh. I know that r57 works just fine with stock + r57 and SuperSu. I can't vouch for the rest and there's really nothing I can do. It's a pretty fresh clean Kernel build and I don't touch anything root related anywhere. My ramdisk changes are all on my github and they are clean. Oreo is a pretty substancial update and it probably needs those tools to catch up.

My app shows r1 because accessing that file is now protected with a SELinux policy so I'll have to read it work root instead of a normal java File read. I change the sepolicy if you're rooted and it'll work fine, but without root it'll show r1 until I update the app to go around this new security measure.
[Nexus 6P Original Android Development] franciscofranco:
My app doesn't reboot devices.

I need to use root commands for that section so if Magisk is derping out (Magisk is crazy slow compared to SuperSu) I can't help it.

Dunno, I don't touch any of that, sRGB is handled by the framework.
[Nexus 6P Original Android Development] elitistphoenix:
For others - I've got stock oreo 8 system image + v57 + magisk 13.3 and it seems good.
[Nexus 6P Original Android Development] mongonexus:
hey FF r57 running fine,all i was saying is the updater app needed an update to register kernel properly,,not that the app was causing reboots,, sorry if it seemed like i said that,,thankyou again
[Nexus 6P Original Android Development] trimeistr:
Same problem here. r57 + stock ROM + Magisk doesn't boot. Elemental X works fine.
[Nexus 6P Original Android Development] revanmj:
I didn't talk about sRGB specifically. I simply meant that if colors don't change to sRGB, it usually means there is an issue with mounting user data partition (or problem occured before this happens) or reading data on it and that's causing the bootloop.
[Nexus 6P Original Android Development] franciscofranco:
Well I don't know. I don't touch any of that. fstab for ext4 userdata is stock. I just tested rebooting on my device and sRGB is already applied when Android finishes booting. Nothing's weird here.
[Nexus 6P Original Android Development] revanmj:
I gathered /sys/fs/pstore/console-ramoops contents from this bootloop (waited about 5 minutes before force rebooting to bootloader) and attached to this post (it would be nice to put info about this in the first post, finding this path wasn't easy ;), so maybe you could find the cause of the bootloop.

For clarification, so far I always end up with a bootloop after flashing r57, no matter if alone or with magisk right after (attached log is from flashing boot.img + r57 and nothing else). I also always flashed stock boot.img first.
[Nexus 6P Original Android Development] franciscofranco:
The log shows absolutely nothing wrong. The Kernel has booted and it's functioning correctly. No idea what-so-ever. You confirm you're on a 100% stock factory image device?
[Nexus 6P Original Android Development] revanmj:
Yes, the only non-stock things I use these days are your kernel, TWRP (3.1.1-0) and Magisk (which I'm now leaving out until I can get booting sorted out). Everything else is completely stock. Originally I installed Oreo via factory images, but now I also did this via Google OTA and stock recovery (as Oreo Full OTA doesn't seem to work with TWRP) to be sure, but bootloop with r57 still happens.
[Nexus 6P Original Android Development] Snowers96:
Stock Oreo 8.0.0 rooted with Magisk 13.3, i have TWRP 3.1.1.0 installed and Sustratum....and from yesterday´s night i haven´t got any strange reboot. I tested dt2w and night light and works well
[Nexus 6P Original Android Development] dunjamon:
Same problem here. Flashed r57 and was stuck at the Google animation screen for hours. Flashed the full factory image again and left out the kernel this time and it loaded up no problem. I'm on full stock with TWRP and SuperSU.
[Nexus 6P Original Android Development] BeDesireS:
The same here. No bootloop, no reboots and everything works fine.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] dunjamon:
Did you install the kernel after booting up for the first time? I installed the kernel before first boot. Not sure if that might be the issue.
[Nexus 6P Original Android Development] kd-:
Was f2fs support removed (or not added yet) with Oreo/r57? I'm seeing the same endless boot issue everyone else has, and am wondering if that's the root cause since my /data partition is f2fs...

EDIT: Flashed back to r55 and everything boots fine.
[Nexus 6P Original Android Development] Badger50:
All is well on mine as well. Thank you very much kind Sir :good:
[Nexus 6P Original Android Development] franciscofranco:
Shoot. F2FS fstab entry is there, but I regen my defconfig and forgot to enable F2FS. Sorry. I'll re-compile and re-upload. I knew forgot something.

EDIT: well I'll do it after waking up, it's 5am.
[Nexus 6P Original Android Development] BeDesireS:
When I go stock, I always do a clean flash with the factory image and take a backup, before I flash anything further.

Maybe try to go through setup first, take a backup and then flash the kernel. If still anything goes wrong, you can restore the stock boot image and everything should be fine again.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] dunjamon:
Taking a stock kernel backup using the FK app should be fine right?
[Nexus 6P Original Android Development] BeDesireS:
No. Take a backup in TWRP. Otherwise you are not able to restore stock if you end up in bootloop.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] dunjamon:
Cheers. I'll wait for Franco to release the new kernel and then give it a go. I'm at work, so might wait till tonight. Stock Oreo is not good for me so far. Terrible battery drain and random reboots. Hopefully the new kernel will help.
[Nexus 6P Original Android Development] BeDesireS:
Hm. Then there is something wrong on your side. For me Oreo is the best stock rom I ever had. Great battery, really smooth and I had no single issue till now.

You should flash the complete stock image and wipe your whole device if you have these issues.
[Nexus 6P Original Android Development] dunjamon:
I generally do a full flash (without the user data clear). I'll give it a couple of days to see if it settles. When I first got it booted up it was really sluggish, then randomly restarted a couple of times. I had it on charge and when I tried to turn the screen on this morning it restarted again. I might see about clearing data this weekend.
[Nexus 6P Original Android Development] phantom146:
You already stated what your problem is.
[Nexus 6P Original Android Development] dunjamon:
I know. I just hate setting everything up again.
[Nexus 6P Original Android Development] noamagil:
hey,

i need a device without root (work app).

i know i can flash the kernel, but is there a way to activate dt2w or other features without root and without using the app?

thanks :)
[Nexus 6P Original Android Development] soccerman821:
I think you'd have an easier time just using magisk to hide root from the work app. Since Android pay works with magisk root I'm sure your work app will.
[Nexus 6P Original Android Development] noamagil:
thanks, it's certainly an option.

i'm still curious if it's possible without root.
[Nexus 6P Original Android Development] franciscofranco:
r58 is up re-enabling F2FS!
[Nexus 6P Original Android Development] mosky91:
Anyone knows why i keep getting a bootloop? :( I did a clean install, then flashed the kernel (the last one, r58), no luck! i'm on stock 8.0
[Nexus 6P Original Android Development] franciscofranco:
You're on 100% factory images, no other changes?

Can you show me a logcat during the bootloop: adb shell logcat > logcat.txt
[Nexus 6P Original Android Development] revanmj:
Yeah, I also still get a bootloop on r58 (though I'm not 100% stock as I have TWRP). I thought it may have been related to F2FS (even though I didn't recall changing filesystem), but it seems it's not (I checked using mounts and I don't seem to have any F2FS partitions).

All versions up to r56 booted fine (I used 55 for a while on Oreo and didn't have any issues, r56 booted but have issues later on), only r57 upwards end up with a bootloop.
[Nexus 6P Original Android Development] franciscofranco:
Damnit. Can you get me a logcat during boot please? Thanks.
[Nexus 6P Original Android Development] mosky91:
Yes. 100% stock, no other mods.

Sorry for my ignorance, but how i'm i supposed to do the "adb shell logcat" command if my phone isn't recognized by adb as a device while in the bootloop?
[Nexus 6P Original Android Development] franciscofranco:
Damnit. Don't worry. Someone else will help me with that. Sorry for inconvenience, I'm at a loss here.
[Nexus 6P Original Android Development] revanmj:
I would, but my device is not seen by ADB at all during bootloop (that's the first thing I tried before going for /sys/fs/pstore/console-ramoops thingy few days ago :)

If there is a way to enable it or If there is something like last_kmsg for logcat that can be pulled from recovery (I couldn't find any info about it), I will gladly provide the file since I really want to be on FK instead of stock kernel :)
[Nexus 6P Original Android Development] dunjamon:
R58 solved my boot loop issues. Although the app is still saying there is a new version available.

Are you guys using SuperSU? I had massive problems with the beta version and have moved to magisk now. Don't know if that would cause bootloops tho.
[Nexus 6P Original Android Development] mosky91:
Did you wipe before flashing the r58? Didn't solved mine
[Nexus 6P Original Android Development] agmyers76259:
Is it just me or is the stock Oreo kernel better than any other 8.0/Oreo Kernel out right now?
[Nexus 6P Original Android Development] E30Nova:
I had weird issues with SuperSU. I flashed the factory image and then SuperSU and all was well for a couple days. Then I turned my phone off, went to turn it on a few hours later and it would just bootloop.

Ever since then SuperSU wouldn't let the phone boot up.

Have since gone to magisk and have been trouble free.

Never had any bootloops or random reboots on r56 or r57.

I'd update to r58 but I'm not going through the hassle of formatting to f2fs. Too lazy, lol.
[Nexus 6P Original Android Development] d.brown:
Im with you on this one... Don't know what Google did but only one kernel worked on my phone with 8.0 and performance was bad... Now I'm back to stock and it's great with great standby battery... Franco is not working for me my phone doesn't go past Google screen...haven't tried the 58
[Nexus 6P Original Android Development] Chrono Leggionaire:
Delete please
[Nexus 6P Original Android Development] escavi:
running the latest version of the ROM Pure Nexus Android 7.1.2 Nougat. I want to try this kernel but see builds 56 and up are for O. I do not see a link in the main post for 7.1.2 for me to download. Where can I find it please?
[Nexus 6P Original Android Development] SlimSnoopOS:
Press "Parent Directory" twice then click on 7.1.2/Anykernel
[Nexus 6P Original Android Development] FrancoGag:
I was having bootloops after installing r58 on a fresh/clean installation of 8.0.0

But I "fixed" it by installing r54, I let it boot (with r54) and then installed r58.

I'd love to hear if anyone can reproduce this behavior.
[Nexus 6P Original Android Development] trimeistr:
r58 bootlooping for me aswell.
[Nexus 6P Original Android Development] mobileman88:
I started from stock kernel the went to r58. Worked well so far
[Nexus 6P Original Android Development] brunes:
I had the exact same issue. r54 will boot in Oreo, r58 will not.

Since I do not root my device, I can not use the in-line updater, so I am just stuck running Oreo with r54 until this is fixed I guess (??)
[Nexus 6P Original Android Development] swallowingled:
No issues here. I wiped data and upgraded to 8.0 with the factory images on Friday. I was hesitant to flash FK after seeing reports of boot loops but decided to try it anyway on Saturday. I flashed in recovery rather than using the auto flash in FKU and it booted right up and I've had no issues. I was already rooted with SU 2.82 SR3 and have TWRP 3.1.1 installed. FKU does still show an update available and my kernel version being r1 but that's a known issue that should hopefully be solved with an update to the app.
[Nexus 6P Original Android Development] Godaemon:
Could someone plz post the Default High Perf CPU Cluster Min/Max freqs ? Mine says 633/1344 is this right ? Thank you
[Nexus 6P Original Android Development] Badger50:
1555/384 on the little cluster.

1958/633 on the big cluster.
[Nexus 6P Original Android Development] Sheetzie03:
Which dark theme is that? Thanks
[Nexus 6P Original Android Development] Badger50:
Swift dark :good:
[Nexus 6P Original Android Development] Ashanmaril:
I tried r56 on my Nexus 6P, stock Oreo, OPR6.170623.013. It was working fine at first. Then I tried quick launching the camera (double tap power button) and it rebooted my device. It got to the lock screen, I wanted to check to see if it was the quick launch that caused the reboot, so I tried it again and it rebooted. This time when it got to the lock screen, the speakers started blaring a high-pitched squealing noise, so I shut it down. Every consecutive boot after that would just reboot once it got to the lock screen. Flashed back to stock boot.img and there doesn't seem to be any permanent damage.

Any idea what went wrong? Am I using the wrong version of TWRP? I flashed TWRP 3.1.1-0-angler beforehand.
[Nexus 6P Original Android Development] revanmj:
I can confirm that flashing r58 on top of the pre-Oreo FK (r55 in my case) fixes bootloop issue.
[Nexus 6P Original Android Development] tcoursey:
Have not been a kernel flasher in the past...but many roms. Just saw this post and it intrigued me. I downloaded/purchased your FK app and I'm impressed. Running the 6P with a few modifications from your app. Playing golf today I lost 2% of battery with a few checks of the email and texts, over 4 hours! Can't wait to see the long term benefit. Thanks for the development.
[Nexus 6P Original Android Development] :
Anyone know where older kernel downloads are?
[Nexus 6P Original Android Development] Toutatis_:
https://kernels.franco-lnx.net/Nexus6P/
[Nexus 6P Original Android Development] mosky91:
Wow it actually worked for me :D. Thanks!
[Nexus 6P Original Android Development] Pipiou211:
There are about 3, or 2 weeks I have Custom AOSP 8.0 based rom with francoKernel and there are no bugs. Everything works and no reboots.

Just onforming even if I do not help.

Peace! Try propertly wiping before flashing, quote me and ask me questions about rom, kernel or whatever, my versions and generally my setup. I can help you.

(P.S. as long as I remember I have European angler, "motherboard" inside my Nexus 6P)
[Nexus 6P Original Android Development] kd-:
+1, I'm still bootlooping on r58 with F2FS and would be happy to provide a log if I can figure out how. Did some googling but didn't find any guidance on how to capture one of a bootloop.

For now, I'm stuck on r55 which seems to have awful battery life - kernel "bluesleep" wakelock all the time :(
[Nexus 6P Original Android Development] mprziv:
Does anyone have a link for the stock Oreo 6p kernel?

The stock kernel seems to give better battery life than f56-f58.
[Nexus 6P Original Android Development] Badger50:
If you made a backup of your rom before you flashed Franco, just restore the boot.img. if you flashed SU before you flashed franco, just flash SU again and that'll return you to stock kernel. Or, you can extract the boot.img from your downloaded factory image, and flash it with fastboot or TWRP. Or, if you backed up the stock kernel with the EXKM app, you can restore it with that.
[Nexus 6P Original Android Development] pr0crast1nate:
I couldn't get r56-58 to boot AT ALL on stock Oreo with a fresh install and this r54 to r58 method worked! I can now use Android Pay finally! :victory:
[Nexus 6P Original Android Development] dunjamon:
Is the app showing as r58 for you guys? Mine keeps saying an update is available.
[Nexus 6P Original Android Development] carlosivanduarte:
Fk Manager issue

I have the same issue, in about shows franco#58 but the app still showing r1.
[Nexus 6P Original Android Development] swallowingled:
The app needs to be updated.

https://xdaforums.com/nexus-6p/orig-development/kernel-franco-kernel-r1-t3266864/post73595244
[Nexus 6P Original Android Development] dunjamon:
Ah OK. The kernel works so that's the main thing. Cheers mate.
[Nexus 6P Original Android Development] Pipiou211:
[MENTION=3292224]franciscofranco[/MENTION]

Can you take a look at this for us? It is a mod for battery improvement, for Snapdragon 810 v1.0.

Nexus 6P got Snapdragon 810 v2.0 but maybe you can let us have it too.

https://xdaforums.com/nexus-6p/general/power-settings-battery-life-improvement-t3668683

Love,

George!
[Nexus 6P Original Android Development] franciscofranco:
Pushed r59. Took me a while to figure this whole bootloop thing out. I think it was because of fstab partitions misconfiguration. I was stripping some valuable information from there so the device couldn't mount the partitions. I managed to reproduce it on my Nexus 6. I fixed it and r59 should be all good. I STRONGLY suggest you to flash stock boot.img before flashing r59 to get fstab into a clean state.

My apologies for the derp. Let me know how this goes!
[Nexus 6P Original Android Development] franciscofranco:
That thing is absolutely useless, the parameters it's changing don't even exist on the 6P. It's another placebo zip.
[Nexus 6P Original Android Development] mosky91:
Thank you for the good work. Appreciate it! I'm flashing the stock boot and then de r59 :good::D
[Nexus 6P Original Android Development] crixley:
Working great! This kernel gets me the best standby life I've had to date. It pretty much flatlines when I go to sleep.
[Nexus 6P Original Android Development] revanmj:
Yes, this finally fixed the bootloop issue for me, thanks!
[Nexus 6P Original Android Development] franciscofranco:
This really consumed some of my nights scratching my head.
[Nexus 6P Original Android Development] bluetigger68:
That was in issue with an updated version some weeks ago, latest SuperSU is working flawlessly now

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] resarfekim:
Does "Builds from r50 are for Android 7.1.2 Nougat." mean that 50-59 (current) can be used for Nougat? I ask because I flashed 59 (was on 56) and got a boot loop, though I did not try Franco's recommendation of flashing a stock boot.img.
[Nexus 6P Original Android Development] kd-:
Still no luck here, even after flashing stock boot.img then r59. I also tried the "r54 then r59" method and that didn't work either. r54 (and r55) still works for me, so that's what I'm using for now.

If I can get any other info let me know... getting pretty close to giving up on f2fs and wiping /data :(
[Nexus 6P Original Android Development] franciscofranco:
56 and newer is only for Oreo.

No idea. Just use ext4, f2fs won't give you any magic.
[Nexus 6P Original Android Development] グリッチ:
Yay, nice job~

So now time for Pixel work to get started? ^_^ *joke
[Nexus 6P Original Android Development] franciscofranco:
Yup. First 5X needs work, then the pixels, which needs a different look and care.
[Nexus 6P Original Android Development] dunjamon:
Flashed on top of r58 and works great. I might do a restore stock and re-flash just to be safe tho.
[Nexus 6P Original Android Development] Daniel91z:
trying to follow Franciscofranco advice but, i have tried flashing the boot.img via flashify, adb and twrp but i am always getting stuck on the "google" logo.

what can i do?

thanks for the great work anyway :)
[Nexus 6P Original Android Development] ironjon:
Yup same here

Coming from ElementalX, flashed stock boot then r59 with no luck

Flashed stock boot, then r54 and then r59 with same result it doesn't boot. :eek:
[Nexus 6P Original Android Development] franciscofranco:
No clue, sorry. fstab is correct and it works. I assume ya'll trying r59 are on Oreo.
[Nexus 6P Original Android Development] crixley:
Are you guys on official Oreo or a rom?
[Nexus 6P Original Android Development] ApoelEllhnwn:
For me everything it's ok like always.

Just wait too see the battery life

#francothebest?