yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] note3userr:
I'm using better battery stats and it's not showing any rogue apps. In terms of wakelock only thing I see is powermanagerservice.display/wakelock and I currently have location turned off. I'm starting to think my phone is just defective. Even on stock it was heating up with simple tasks and starting to lag
[Nexus 6P Original Android Development] Sylynce1:
I'm also having this same issue. Root verified
[Nexus 6P Original Android Development] franciscofranco:
Oh I know why now! My app is still sdk 25, and for lower than 26 sdk Android by default sets a different selinux group for. So I'm changing sepolicy for "untrusted_app" and my app is "untrusted_app_25" or something like that. That's the reason. It'll be fine with the new update which I had plans to get out this week but I got them fevers and I've been pretty much destroyed the last 2-3 days.
[Nexus 6P Original Android Development] Sylynce1:
You are the best! Looking forward to seeing the update come rolling in
[Nexus 6P Original Android Development] Matrix1999:
Yes, sir. I double checked. The only thing odd I see is the main screen where it says I am running R1 kernel despite the fact that I am running R60. And afaik, I am running your latest and greatest version of the updater app.
[Nexus 6P Original Android Development] franciscofranco:
Yes, I explain it in the last page ;)
[Nexus 6P Original Android Development] Matrix1999:
So when does the new version of the app come out?
[Nexus 6P Original Android Development] franciscofranco:
When it's ready, but sooner than later. I have to go through all the different screens and update/fix things. Oreo brought some API changes too, specially regarding background services, needs changes, and the app had some issues with layouts which needed improvement. Things take time, rushing it isn't pleasant for anybody.
[Nexus 6P Original Android Development] Matrix1999:
Thanks for your prompt reply. I just flashed the Oct release of the firmware and I am going to leave r60 out for now until your new app is ready then I can go back and install the kernel and the updater app.
[Nexus 6P Original Android Development] franciscofranco:
r61 is up with the newer security patches, newer Binder driver code and other security patches not included in the October release. Auto-flash with http://get.franciscofranco.xyz
[Nexus 6P Original Android Development] mobileman88:
I still see the description for r60 when I checked the past 3 hours. Not sure if it is taken down?
[Nexus 6P Original Android Development] aquatix:
Same here, has there gone something wrong, or is it just not reporting the right version?
[Nexus 6P Original Android Development] franciscofranco:
It was just the changelog doing that, I was tired and forgot to update it. Fixed though.
[Nexus 6P Original Android Development] aquatix:
Cool, no worries, appreciate your quickness in any case! Should've just tried instead of posting :)
[Nexus 6P Original Android Development] dsaucex:
I just flashed r61 but after reboot it still says r1? Is that fix coming later?

Also, until this is fixed, does it mean that kernel is not properly working, as in the CPU tweaks?

(using Nexus 6P Oreo)
[Nexus 6P Original Android Development] sethukrishnan:
This might seem dumb or off topic but

Is thr anyway to make an add on for Pixel launcher (or any)

wr the app could detect the app icon press event for launch and suddenly crank up cpu's to Max OC freq for short bursts inorder to increase app launch faster ? Or anyway to make such a mod and implement in a kernel?

(Sry but it's just something that came across my thoughts ignore if it's dumb)
[Nexus 6P Original Android Development] franciscofranco:
Input boost frequency already ramps the CPU when there's an input touch.
[Nexus 6P Original Android Development] cosmoa:
I used oreo,I changed data partition and cache partition to f2fs , it got a bootloop for r58,r59,r60,and r61. While R55 could work properly, but I want to use the latest version r61, can you help me?
[Nexus 6P Original Android Development] Will008:
I've experienced some of the early shutdowns with the kernel on nougat builds and now on the latest build. This happens on stock and custom roms. If I flash stock kernel or another custom kernel without changing anything else I do not get early shutdowns. Shutdowns happen anywhere between 10-15%. Can anyone please help?
[Nexus 6P Original Android Development] placebo_domingo:
Same thing happens to me. Only on this kernel.
[Nexus 6P Original Android Development] franciscofranco:
https://productforums.google.com/forum/#!msg/nexus/_GL8HM8rdAI/PQQoz0nzAwAJ

https://www.google.pt/url?sa=t&rct=...loop-issues/&usg=AOvVaw1eJFBwzO5mTeZWjVxoZwIj

https://www.google.pt/url?sa=t&rct=.../M4wetzVBbhU&usg=AOvVaw0zeZsVKXIGuKpTxj2V9zlE

https://www.google.pt/url?sa=t&rct=.../ExGRaRkWvxW&usg=AOvVaw2P1GgJJUgfzsLTLFJDSyZF
[Nexus 6P Original Android Development] datsoy:
Is your batteties shows 1% after turning it on or it wont turn on at all?

I would suggest to replace your batteries.

It fixes mine.
[Nexus 6P Original Android Development] placebo_domingo:
I'm not in the same league as these poor souls. Running stock I have zero issues. It's when I root, flash, mod & theme the crap out of my phone when it goes bonkers.
[Nexus 6P Original Android Development] franciscofranco:
Nothing we can really do about it!
[Nexus 6P Original Android Development] birdy3636:
anyone else having system ui has stopped on reboot? I got this after flashing r61 on cortex rom, it was fine prior to flashing kernel from app
[Nexus 6P Original Android Development] burningcreation:
I'd suggest reflashing the ROM.
[Nexus 6P Original Android Development] Will008:
[MENTION=3292224]franciscofranco[/MENTION] your kernel is far superior to any other kernel I've tried hands down, great work.

I really tried the cutom rom's stock kernel and EX kernel and didn't have this issue. I've reproduced the problem multiple times, thats why its safe to say my problem is with the kernel. Before posting I searched the thread and didnt find a single mention to this problem with your kernel specifically, thats why I'm asking for help, cause I want to keep the kernel.

Running Nitrogen OS (Oreo) and FK R61.
[Nexus 6P Original Android Development] Will008:
Usually shows 5-8% if I boot to TWRP. If I load to system it shows 0 then shuts off.

---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------

Man caused by the kernel or not, I love the kernel and keeping it anyway.
[Nexus 6P Original Android Development] v3rk:
Noon question here... Back to Android after 3 year hiatus. Which takes precedence: battery labs underclock settings or performance profiles? Or do the underclock settings further lower the clock speeds used for the selected profile?
[Nexus 6P Original Android Development] franciscofranco:
Whichever you applied last preceeds it. If you apply power saving perf profile, then apply the underclock percentage it'll always underclock based on the maximum frequency, not the current max freq.
[Nexus 6P Original Android Development] Sylynce1:
Magical enhancements incoming

I am still trying to auto flash r61, however it doesn't auto bit and install, same issue from r60. Is there anything I can do manually to flash r61 manually, or is there something else going on. Have been using the FK Manager and Installer
[Nexus 6P Original Android Development] inimaitimepass:
Replacing the battery or a getting new phone is the way to fix this. :cool:
[Nexus 6P Original Android Development] mobileman88:
Same issue with mine, it dies when it says anything less than 25%. Changing the battery fixed it.
[Nexus 6P Original Android Development] franciscofranco:
Are you rooted?
[Nexus 6P Original Android Development] Sylynce1:
Sure am.
[Nexus 6P Original Android Development] franciscofranco:
Can you double check you gave my app root permissions?
[Nexus 6P Original Android Development] Sylynce1:
SuperSU v2.82-SR4.

Removed FK Manager & Updater, reboot, granted permission.

Downloaded r61, got a pop up message that started something to the effect of ' the was a problem installing *shrugs*'

Currently states in on r1
[Nexus 6P Original Android Development] Snowers96:
Hi! How can set the kernel to use 4 cores to avoid bootloop?
[Nexus 6P Original Android Development] aoaleman:
Flash this in TWRP after the ROM. Then flash r61. I got this boot image from the boot loop thread.

https://drive.google.com/file/d/0B-MzhB211uc8Y21yNXR3UE03MXM/view?usp=drivesdk

Edit: then you'll probably need to reflash root.
[Nexus 6P Original Android Development] arhung:
Same here, already installed r61 but in app still showing r1.
[Nexus 6P Original Android Development] Sylynce1:
How do you know you installed it? How did you install it? I don't get the auto flash to work, so I have no idea the version I'm on
[Nexus 6P Original Android Development] arhung:
I think #61 means r61
[Nexus 6P Original Android Development] frank604:
More info about this just 2 or 3 pages back. If you installed r61 then u are on r61 regardless of it saying you on r1

Cheers!
[Nexus 6P Original Android Development] franciscofranco:
Weird, maybe the servers were in maintenance or something. Sorry, no idea.

Already explained it's because of Oreo's security changes. It'll be fixed in the next app update, which is almost due.

SYSVIPC was disabled by the Android team for security reasons. That said, if you need it you can grab my config from /proc/config.gz, enable the options, and recompile the Kernel with it.
[Nexus 6P Original Android Development] SirVilhelm:
How do you get the application to show the correct kernel version. App says r1 but I've installed r61
[Nexus 6P Original Android Development] EnvyOne:
Anyone figure out what's up with Nitrogen and r61/r60(according to others)? After I boot up (successfully leaving boot animation) it goes into bootloop. Currently gonna flash r59.

Edit: I'm on latest version of Nitrogen, had similar problems on the last september update as well.

Edit2: Gave up on trying to figure it out. Installed latest Oreo ElementX kernel instead.
[Nexus 6P Original Android Development] franciscofranco:
Hi. Explained literally the post above yours :/

Absolutely no idea. My Kernel installation is very minimal and unintrusive. Maybe [MENTION=4544860]osm0sis[/MENTION] can help?
[Nexus 6P Original Android Development] SirVilhelm:
Sorry, missed it completely. Thank you
[Nexus 6P Original Android Development] EnvyOne:
Flashed to latest bootloader (03.67 -> 03.75) and baseband (03.81 -> 03.84). That didn't seem to fix the issue either. I haven't tried flashing another rom after updating those two things so it could be something else related to my phone and not the kernel.
[Nexus 6P Original Android Development] Roger.T:
[MENTION=3292224]franciscofranco[/MENTION]

Please try to find out why your kernel does not work on Nitrogen Oreo..

There are many confused and somewhat annoyed ?

It would be a pity if we could not use your great kernel anymore..?

Thank you in advance ?

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] zelendel:
It is most likely a rom issue as I know of a few roms that do not work with Francos kernel. Most because the roms are coded to use the up streamed updated kernels which is ahead of francos
[Nexus 6P Original Android Development] PCWright86:
I flashed nitrogen with Franco and ran for a day before swapping to SuperXE with Franco
[Nexus 6P Original Android Development] akshaysalunke13:
Latest App.Latest Kernel r61.Stock Rom w/ September Patches. App crashes in System Monitor on RAM tab.
[Nexus 6P Original Android Development] franciscofranco:
Not really, those incremental patches don't really do that. I'm debugging this right now.
[Nexus 6P Original Android Development] franciscofranco:
Ok I figured why things go south with Nitrogen, it's not the Kernel, it's some syscalls in my init.fk.rc ramdisk file. Now figuring out why this happens.
[Nexus 6P Original Android Development] zelendel:
I can say that ever since my rom has been using upstream kernels as default, your kernels always bootloop the devices.
[Nexus 6P Original Android Development] franciscofranco:
Currently with Nitrogen the issue is with some of exec calls with su and supersu security contexts, the device boots and after the lockscreen it just crashes to the bootloader. Getting rid of the exec calls and do it differently fixes it and I'm running FK on Nitrogen just fine. I wonder if that's the case for you too.

Anyway thanks for the feedback. I'll just wait for [MENTION=4544860]osm0sis[/MENTION] to give me some feedback on my changes since he's the MVP for these things and if all's ok I'll push. I suspect this might be an issue for other devices too.
[Nexus 6P Original Android Development] zelendel:
Yeah my devices never get that far. It just bootloops the boot animation. I only use magisk as I no longer can trust SU with chains gone.

Glad you found the issue for it though.
[Nexus 6P Original Android Development] DEVILOPS 007:
FYI, this is how it goes for me. For me it showed the Google splash screen and would then go black and reboot. I couldn't get to the boot animation. Hopefully what you think you've fixed fixes this as I see you and other users reporting being able to get to the boot animation and lock screen or so. Thanks
[Nexus 6P Original Android Development] osm0sis:
Sounds like they broke the /init binary upstream if it can't handle several failed exec commands due to non-existent contexts without triggering a kernel panic. :(

What about a device where we can't set the zram parameters in the fstab? Starting a service for each command needed is insane and ugly. This is clearly a ROM issue (albeit in their ramdisks) and ROMs should fix it.
[Nexus 6P Original Android Development] fezzy102:
I currently build the 6p for nitrogen what do I need to do on my end to fix if it is ROM related ? Just let me know I do what I can.
[Nexus 6P Original Android Development] franciscofranco:
Oi! I never thought Nitrogen was the culprit, your init is pretty much stock. [MENTION=4544860]osm0sis[/MENTION] nailed it to the mkbootfs we use, either permissions or ownership issues. So don't worry about it, it's on our end. By the day now I have your attention, why are you booting with a root shell even if the device is not rooted? That's a major security flaw.
[Nexus 6P Original Android Development] DEVILOPS 007:
Osmosis said it was a rom issue didn't he? Maybe ROM and kernel?

https://xdaforums.com/nexus-6p/orig-development/kernel-franco-kernel-r1-t3266864/post74104582
[Nexus 6P Original Android Development] franciscofranco:
I have a Slack channel with [MENTION=4544860]osm0sis[/MENTION] I'm not making things up :p
[Nexus 6P Original Android Development] fezzy102:
As far as I know it is set that way in the ROM. Is this the commit that enables that root shell? https://github.com/nitrogen-project...mmit/c8df7490660d614ac7ddc826fca453cd642c4b65
[Nexus 6P Original Android Development] franciscofranco:
I know, and that's a major security hole, anyone can pick up the phone, rooted or not, plug it in, adb shell, boom root.
[Nexus 6P Original Android Development] franciscofranco:
I pushed r62 couple hours ago, it will work on Nitrogen but auto-flash from my app won't work, it'll need an app update pretty soon. Sorry, but it's the only way.
[Nexus 6P Original Android Development] ps000000:
I am glad to see devs talk together like this.

:fingers-crossed::fingers-crossed::fingers-crossed:
[Nexus 6P Original Android Development] franciscofranco:
It's just for the cameras, in the backstage we're all punching eachother :angel:
[Nexus 6P Original Android Development] JetonZ:
Hi, Franco!

can you add this option to your kernel again? :o
[Nexus 6P Original Android Development] DEVILOPS 007:
For me r62 is not booting in nitrogen. I am getting to the Google splash screen and then it goes black and reboots just like r61. I've tried flashing the ROM and kernel and the ROM, gapps, root, kernel with he same results. Could it be something to do with f2fs because someone in the nitrogen thread got it to boot fine so I'm not too sure what is going on. Thanks [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 6P Original Android Development] osm0sis:
mkbootfs changing the permissions/ownership somehow triggers init to turn exec failures into a kernel panic.

There's definitely something in the upstream init that isn't handling things as well as it used to (ie. it should fail gracefully and the boot should continue), but we can fix it on our end as well by dropping mkbootfs from the package, avoiding the trigger.

mkbootfs is the solution to many problems but also the cause sometimes, and I'm getting pretty tired of fixing it. I tried some things yesterday and came up with a more badass way to unpack and repack a useable ramdisk from booted Android, so sit tight, it'll be in the next FKU. :cool::cowboy:
[Nexus 6P Original Android Development] DEVILOPS 007:
Okay cool, good to hear. Any idea why I have the same issue on r62 as you know what you're doing?:confused:
[Nexus 6P Original Android Development] osm0sis:
Extract the boot.img from the ROM zip and flash it first?

Are you rooted?
[Nexus 6P Original Android Development] DEVILOPS 007:
Well my process is to wipe all partitions except for internal storage and flash the ROM and kernel. I've tried different combinations with and without root. I'm using SuperSU sr5 currently. The issue is kernel related I think because stock kernel would boot if I wasn't in f2fs

Also ex kernel works for people on nitrogen so maybe you or Franco could check what their differences are in the ramdisk that is making it work. I'll try extracting the boot.img from the ROM and flash it later once I get home from college and have charged my phone a bit. I hope this gets sorted soon.:fingers-crossed:
[Nexus 6P Original Android Development] osm0sis:
I just know Francisco installed Nitrogen to reproduce the issue, and it's working for him now.. Maybe it is f2fs related?
[Nexus 6P Original Android Development] DEVILOPS 007:
Maybe, I don't really want to have to go through the trouble of changing to ext4 and plus I notice slight performance increases in f2fs too. Is there any way you think that he could do something about that or would you say it is ROM related? If he can't do anything about it then I might wait a bit for other ROMs or kernels and see what combo works for me. I'll still try the boot.img later though. Thanks Franco for checking btw. It's a shame if f2fs is not supported Ron or kernel side. Thanks.
[Nexus 6P Original Android Development] osm0sis:
Maybe he can reformat his test device to f2fs to figure it out. :good:
[Nexus 6P Original Android Development] DEVILOPS 007:
Would be nice as then we'll know for sure if it is an issue only I have for some reason or an f2fs issue. I'd try ext4 myself to test but I don't really have the time or resources available for that right now. Hopefully Franco is able to test at some point because then he can debug it and sort it out.:fingers-crossed:
[Nexus 6P Original Android Development] Daandofreak:
i am using r62 since early morning with latest nitrogen, no issues at all.
[Nexus 6P Original Android Development] DEVILOPS 007:
Probably cause you're on ext4 not f2fs?
[Nexus 6P Original Android Development] franciscofranco:
Ok.

:highfive:
[Nexus 6P Original Android Development] Aircraft800:
Is there any known compatibility issues? I'm running [ROM][OPR5.170623.007][10/11] Benzo Rom 8.0.0 on my Nexus 6P. I tried to install fk-r62 via the manager/installer and it hangs at "Google" screen and reboot. I also tried to flash in TWRP and the same thing, boot loop.
[Nexus 6P Original Android Development] franciscofranco:
Not that I know of, it should work fine.
[Nexus 6P Original Android Development] mikezf:
Same hier, on stock OPR5. Back to r61.
[Nexus 6P Original Android Development] osm0sis:
He explained pretty clearly it should be flashed via recovery to resolve ROM compatibility issues until the new FKU comes out with the new booted AK2 flashing method we're working on.
[Nexus 6P Original Android Development] ZedAz:
Is it just me or the 'Performance profiles' is removed ?

Release #62, Nexus 6P, Stock Oreo, latest FKUpdater app
[Nexus 6P Original Android Development] franciscofranco:
No, but I found out late last night without mkbootfs I have to make some file permission/ownership changes to get my init files to run. I'll push r63 with them fixes. Losing mkbootfs was a big change.
[Nexus 6P Original Android Development] franciscofranco:
Alright! Good news, [MENTION=4544860]osm0sis[/MENTION] and I (well, mostly [MENTION=4544860]osm0sis[/MENTION] to be fair) finally cracked how to auto-flash without mkbootfs. There's no one in the Android community doing this so I'm very happy how this turned out. I know it's not _very_ exciting for regular users, but this is gigantic for auto-flashing a Kernel zip package with a Kernel binary + ramdisk edits in a live system walled off with SELinux and strict permission based file/directory scheme (specially since Oreo). Mind you, this isn't the typical writting a boot.img to the boot partition, it's way more advanced. It was particularly challenging since we could run everything manually through adb, but when running the code from the app space the device never booted up. This wouldn't be possible without [MENTION=4544860]osm0sis[/MENTION] and his gigantic bubble of knowledge on this field (the idea + script is all his).

Anyway, r63 is up and running which fixes some of the issues introduced with r62 due to the removal of mkbootfs. You can flash it through the recovery just fine, though it won't work if you auto-flash since it requires a new app update which will come up very soon.

If you have/had issues with flashing FK it might've been related to mkbootfs so try again.
[Nexus 6P Original Android Development] DEVILOPS 007:
Sounds great, thanks! Is f2fs supported in this build?
[Nexus 6P Original Android Development] tr1gg3r.man:
I don't see builds r50 - r55 on the download server for Android Nougat 7.1.2
[Nexus 6P Original Android Development] SlimSnoopOS:
It's there. Click "Parent Directory" twice after selecting the download link.
[Nexus 6P Original Android Development] tr1gg3r.man:
Thank you, here is a link for a parent directory of all the different versions of Android...

https://kernels.franco-lnx.net/Nexus6P/
[Nexus 6P Original Android Development] franciscofranco:
Yes, and r50-r55 are there inside 7.1.2/anyKernel
[Nexus 6P Original Android Development] Cywair:
Does the newest version support F2FS?
[Nexus 6P Original Android Development] franciscofranco:
It should yes.
[Nexus 6P Original Android Development] Cywair:
I find that it will stuck in the Google screen and bootloop when using r61-r63, and r55 works just fine.
[Nexus 6P Original Android Development] mikeandjaimie:
Just out of curiosity, but for those running oreo, may I ask which rom you're running Franco on?
[Nexus 6P Original Android Development] cosmoa:
So do I
[Nexus 6P Original Android Development] franciscofranco:
I'll check.

All SELinux denials will be fixed when the app update is finished. It's about ~80% done.
[Nexus 6P Original Android Development] Jay Rock:
Anybody have a clue as to why FK manager keeps underclocking my cpu and doesn't restore the setting when I hit the restore button under battery life labs? One minute it was off and my max cpu frequencies were at their max. Next minute I check and it enabled itself and the max cpu frequencies are scaled down and I can't restore them to their actual max. The performance profile is on balanced. Android 7.1.2.
[Nexus 6P Original Android Development] franciscofranco:
Don't think you should assume it's my app's fault. Are you under thermal throttle?
[Nexus 6P Original Android Development] nameback:
Kinda newbie question here. Can I just install this over any ROM or is it only designed to work with the factory image?
[Nexus 6P Original Android Development] bigtym535:
I'm using Nitrogen OS. r.62 worked perfectly for me but r.63 bootlooped me (I am using the stock file system format).
[Nexus 6P Original Android Development] franciscofranco:
I have Nitrogen installed with r63 and it's just fine.
[Nexus 6P Original Android Development] franciscofranco:
Any rom works.