yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] poondog:
Livedisplay drivers aren't merged in FK

https://github.com/LineageOS/androi...mmit/0b8a3bdb68a6202dd2f45d0dfea7fa0347c537c2

https://github.com/franciscofranco/bullhead/commits/oreo-mr1/drivers/video/msm/mdss

Alternative is to use KCAL which doesn't go into the native settings app
[Nexus 5X Original Android Development] syferdevil:
Using February security patch and r52 and working smoothly. 2 things I've noticed in the first 10 minutes are even though I turn on the cooler display temp in Developer settings, it seems it reverts to default yelowish display after reboot. And secondly, I know the dev said that he didn't touch fingerprint but sometimes fingerprint scanner doesn't work, rebooting the device seems fix the issue.

On stock and rooted with Magisk, also I didn't touch kernel configs as I haven't installed the Franco Kernel Manager yet.

edit: I'm also using osm0sis bootloop fix, because this device decided to bootloop for some reason.
[Nexus 5X Original Android Development] franciscofranco:
r53 is up with February's patches. Auto-flash it with http://beta.franciscofranco.xyz or download the zip from the OP.
[Nexus 5X Original Android Development] EmiRus:
Thanks first francescofranco,

Does the kernel mamager need twrp recovery or so for updating kernel?

Or just 1click and reboot,done?

Since i have no custom recovery..
[Nexus 5X Original Android Development] j-a-d-z:
If you use the beta of FKM the autoflash function should work without a costum recovery.
[Nexus 5X Original Android Development] franciscofranco:
One click, it auto-flashes and reboots for you. You need to be on the beta though http://beta.franciscofranco.xyz
[Nexus 5X Original Android Development] EmiRus:
Thank you for work man everything worked flawlessly.
[Nexus 5X Original Android Development] zurik:
Live display doesn't work on Resurrection Remix 6.0.0 with FrancoKernel r53
[Nexus 5X Original Android Development] jcmm11:
I'm getting an error trying to install r53. Nexus 5x, Stock February update. Magisk - both 15.3 and 15.4.

"Signing image failed. Aborting"

Relevant portion of log attached, but not much there other than the error message.
[Nexus 5X Original Android Development] kevtrysmoddin:
Using magisk and Franco fine here, are you flashing Franco kernel before or after magisk?
[Nexus 5X Original Android Development] EmiRus:
Just a Question,

Do u have problems by rebooting?(like stuck at google logo?)

Coz i had at stock newest patch with magisk,stuck at google logo

Thx.
[Nexus 5X Original Android Development] kevtrysmoddin:
Only occasionally say once a day
[Nexus 5X Original Android Development] rp158:
[MENTION=7590113]EmiRus[/MENTION]: it's a Magisk problem. Maybe after wipe caches. Holding power button gives the needed push.
[Nexus 5X Original Android Development] EmiRus:
Yeah man as i had to do this multiple times and switched to su/suhide..
[Nexus 5X Original Android Development] franciscofranco:
Are you sure you're on the latest TWRP?
[Nexus 5X Original Android Development] jcmm11:
Yes - TWRP_3.2.1 And it works fine with ABC ROM. Looks like I'm stuck there for the moment in any case. With flashfire not currently working on latest 8.1 I have no way to apply full ota to get back to stock. (Computerless at the moment. Very painful.) So I can't test any potential fixes.

Actually not true. I do have a nandroid of the stock install, pre-magisk. I can get you a nandroid copy of the boot image if you want.
[Nexus 5X Original Android Development] jcmm11:
After. And since it works on ABC rom I don't think it's a magisk issue. Flashing Franco after magisk.

Hmm, maybe I'll restore the nandroid and see if elemental works. If so not until tomorrow.

I really wish there was a good ROM left for the Nexus 5x. I haven't found one yet.
[Nexus 5X Original Android Development] kevtrysmoddin:
Validus is a good rom it's here, https://xdaforums.com/ground-zero-r...05-11-7-1-2-ground-zero-roms-validus-t3605719
[Nexus 5X Original Android Development] jugoslavpetrovic:
I am very satisfied with the AICP rom.
[Nexus 5X Original Android Development] rp158:
[MENTION=4487388]jcmm11[/MENTION]: I'm even happy with ABC. No overload & very solid. /OT :)
[Nexus 5X Original Android Development] Lughnasadh:
Me too. Rock solid with plenty of features and nightly builds for us flashaholics :D. I like ABC as well.

Apologies for the OT Franco...
[Nexus 5X Original Android Development] jcmm11:
I'm going to try reinstalling stock I think. I'm back on Pure Nexus for the moment. Will report back, going to try something to get a better handle on what's causing the error.

Thanks for the feedback on other ROMs. I have problems with AIM and ABC (caused to at least some extent by the way I like to do things. I mess with any ROM I install but that's way too much off topic).

I do have one question, if anyone can answer it. Does anybody know how to get the settings command to work from a terminal emulator? It's the only way I know of to reset an Android ID (among other things) and it gives me a "failed transaction" message in 8.1

Franco - I do apologise for the off topic. Will get back to you on what I find with stock. Probably some time later today, tomorrow at latest.
[Nexus 5X Original Android Development] jcmm11:
Ok, don't know what happened but I reapplied the ota and it worked just fine.

I'll just blame it on cosmic rays ??

Sorry for the false alarm.
[Nexus 5X Original Android Development] Elcivor:
Just a newbie question (I have used custom kernels before, but always had trouble with having to reroot the device and sometimes losing settings because of it):

After installing the newest kernel with security updates, do I need to apply the official security updates as well?

Or do these two things do the same thing?
[Nexus 5X Original Android Development] jcmm11:
They do the same thing. This kernel incorporates the official security updates, along with some other tweaks.

Just note that you should apply Franco kernel *after* whatever root method you use.

If root (not the root manager but root itself) gets updated you'll need to reapply Franco. If Franco gets updated no need to reapply root, just apply Franco.
[Nexus 5X Original Android Development] nathanchance:
Delete /su/xbin_bind, reboot, and try again.
[Nexus 5X Original Android Development] gdskp:
With r3 everytime I press back button to return launcher from an app (e.g. Whatsapp), it has to reload and press twice when switching to the app again through recent menu. No issue in r2.
[Nexus 5X Original Android Development] franciscofranco:
Can't reproduce. That seems random enough. Show me in a screenrecord.
[Nexus 5X Original Android Development] gdskp:
Strange now I can't reproduce too. I tried several times and it didn't work but it is okay now. Will have a screen record if it appears again. Thanks for your quick response :)
[Nexus 5X Original Android Development] szucsgf:
Did it only happen shortly after a reboot? I get this too for about 15 minutes after reboot. Happens to me on stock rom stock kernel too.
[Nexus 5X Original Android Development] perrocaliente:
Is there a way to adjust the minfree ram values? I'm sick of having piss poor multitasking because android feels the need to clear every app from ram immediately after I switch to another one.
[Nexus 5X Original Android Development] franciscofranco:
Minfree values are fine, leave them alone.
[Nexus 5X Original Android Development] perrocaliente:
Dammit franco let me screw my phone up in peace :p It can't even keep instagram and hangouts in memory at the same time if I open chrome. It's ridiculous. I also don't have any unnecessary services running in the background using up memory. It's absurd (in my opinion) how much of a hog marshmallow is.
[Nexus 5X Original Android Development] linqdesires:
I agree. MM is using RAM very bad and it's an elephant. I have to reboot after some days. Uninstalling facebook app was a little improvement.

I don't know if minfree tweaking can solve the issue.
[Nexus 5X Original Android Development] franciscofranco:
Are you both on r3? There isn't much more I can do Kernel wise. I'm usually with 900Mb free after a couple days of runtime. I wonder if leaving ZRAM enabled on this device makes sense... Same thing happened with stock?
[Nexus 5X Original Android Development] insang-droid:
trying this kernel with stock rom... I usually get around 3H15M on completely stock image.. I'll report back with results in a few days.
[Nexus 5X Original Android Development] gdskp:
I also have similar situation. Maybe we can have to option to toggle ZRAM to test?:)
[Nexus 5X Original Android Development] iPwn_:
So I flashed the stock boot image, and then r3 to start from a clean slate.

Ran like a dream for a few hours. As smooth as the stock kernel and my big cores were no longer turning off for the time I used it. None of the slowly appearing animation lag either.

Then my phone randomly froze, shut down, and failed to boot up completely again (always froze at some point on the colored boot animation or on Starting Apps) until I reflashed the stock boot image.

The only tunable change I made was raising the thermal limit to 52, but that shouldn't preclude the device from booting 10 minutes later if the original crash was caused by some catastrophic thermal failsafe.

What's odd is that the device was actually sleeping when it randomly reboot the first time.
[Nexus 5X Original Android Development] franciscofranco:
Does this happen since r1? Or only in the latest release?
[Nexus 5X Original Android Development] franciscofranco:
Are you 100% sure there's nothing else you changed? What rom are you using? Not booting is kinda weird. Did you grab a log for me after the crash?
[Nexus 5X Original Android Development] gdskp:
Since r1 for me.
[Nexus 5X Original Android Development] iPwn_:
Looks like I have the two wakelocks disabled too and a different vibration setting.

And no :( I was too concerned with getting it to boot up again because I had to make a call.

If it happens again, I'll grab one.
[Nexus 5X Original Android Development] franciscofranco:
Did you disable bluesleep?
[Nexus 5X Original Android Development] franciscofranco:
That's not good. Doesn't happen with stock, correct?
[Nexus 5X Original Android Development] iPwn_:
I did disable bluesleep, but don't have Bluetooth enabled.
[Nexus 5X Original Android Development] BS86:
Of course you need to flash a ROM containing the monthly security updates first. The security updates are in both components, ROM and Kernel. Flashing a ROM overwrites the Kernel.
[Nexus 5X Original Android Development] Elcivor:
Thanks guys. Yeah I already have my device rooted and everything, so this reassures me.
[Nexus 5X Original Android Development] Elcivor:
The only issue I see is that my device still thinks this is the January update.
[Nexus 5X Original Android Development] jcmm11:
That's the ROM patch level.
[Nexus 5X Original Android Development] Elcivor:
Aah, now I understand it... Hmm that means I'll have to revert the kernel and then apply the ROM. Let's see what happens.
[Nexus 5X Original Android Development] jcmm11:
No need to revert the kernel. ROM update will overwrite the kernel so simply reapply Franco after updating the ROM (and reapplying root, if applicable)
[Nexus 5X Original Android Development] BS86:
if you use stock ROM and want to use the official OTA tool, yes. Otherwise no.
[Nexus 5X Original Android Development] Elcivor:
Hmm, I have no idea how to do the rom update properly...

I tried flashing the ota with flashfire and then applying Magisk root and then the kernel, but nothing changed... It was the January update.

But when I tried connecting it to my PC, both my Android device and PC didn't detect each other. (On my phone I couldn't select from charging mode to data transfer mode, and my PC didn't detect a new USB device on my computer in both ADB, fastboot mode and just regular boot)

I've always had issues getting my Windows device to detect fastboot or ADB, but this is something else...
[Nexus 5X Original Android Development] giannism13:
Search for "Nexus 5x system images", download the latest full system image (not the ota), extract the system, bootloader, radio and vendor images and flash them with fastboot. That's how I do it

Also after those, before you boot to the system, go into recovery and wipe cache and davlik/art cache and reboot
[Nexus 5X Original Android Development] Elcivor:
I cannot use fastboot if my PC doesn't detect my device.
[Nexus 5X Original Android Development] giannism13:
Sometimes I have the same problem too. It seems there is a problem in the physical connector on the devices. Make sure you have the proper drivers installed and try moving the wobbling/ moving the cable while connected until it's detected. After a few tries this fixes the problem for me.
[Nexus 5X Original Android Development] Elcivor:
As you can see, I cannot even select the option to gain access to the data storage.

My CMD closes the moment I open it

And there's no single detected device in device manager.

For both bootloader, while booted to the system and recovery for adb.

Drivers are already installed.
[Nexus 5X Original Android Development] manpildo:
Have you tried different cables and different ports?
[Nexus 5X Original Android Development] giannism13:
I understand 100% your problem, since I have the same too. The only fix you can try is moving the cable when its connected to your phone. Try reversing the connector and slightly moving it up and down. As I said, after a few tries this fixes the problem for me. If this doesn't fix it for you, you may consider buying a new cable ( I have an aftermarket c cable and the problem is still there. So it's the phones connector fault)
[Nexus 5X Original Android Development] Elcivor:
In the end I fixed it through flashfire.

Simply by downloading the correct factory state files (vendor, system, boot) and flashing those and then root it again. Then applying the kernel.

I accidentally flashed the February files instead so I didn't need the OTA anymore because of it. ?
[Nexus 5X Original Android Development] jugoslavpetrovic:
I have been flashing kernel before supersu for a long time already. All worked fine on my side with any custom kernel.
[Nexus 5X Original Android Development] Lughnasadh:
The reason you should flash the kernel after root is b/c when flashing root (SuperSu or Magisk) it will make a backup of your stock boot.img. It can't do this if you flash the kernel 1st b/c the kernel will modify the stock boot.img. This is handy in cases where you may need to revert back to the stock boot.img. :good:
[Nexus 5X Original Android Development] jugoslavpetrovic:
Oh, sure, but I always have boot.img extract from the rom.
[Nexus 5X Original Android Development] jcmm11:
It will work either way. If you flash the custom kernel first the backup will contain the custom kernel. As long as you're aware of it and can adjust you're fine. Personally I think it makes more sense the other way, but ultimately no harm, no foul. Of course if you take a nandroid of the stock kernel before applying root you can have it both ways ?
[Nexus 5X Original Android Development] :
One Kernel to Rule Them All

This Kernel has been my main stay since its release. Buttery Smooth performance when I want it. Unmatched battery life when I want that. Thank you for bringing light to Bullhead when there was once only darkness. :good:
[Nexus 5X Original Android Development] zurik:
Hello [MENTION=3292224]franciscofranco[/MENTION] , may you add LiveDisplay support or your custom kernel already have support for it? Because on RR the livediaplay is broken with R53.
[Nexus 5X Original Android Development] salim0786:
Hi can anyone post battery ss
[Nexus 5X Original Android Development] sigurd_LU:
This kernel doesn't support LiveDisplay as of now (drivers aren't merged).

I'm using this app as a replacement: https://xdaforums.com/nexus-5x/themes-apps/app-simple-night-shift-t3670109
[Nexus 5X Original Android Development] Gopal6600:
Is this MultiRom compatible? Great work Franco :)
[Nexus 5X Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION] any idea if SMB2/3 is enabled or cifs is update to date? I usually connect to samba running on debian box at home, but I've just noticed I can't connect to windows 10 share unless I enable SMB1 support..
[Nexus 5X Original Android Development] BS86:
you need to tell samba to use a higher version then 1.0 on linux (and thus also on android). You can do so by adding vers=3.0 to your mount options when mounting with cifs.

You should do that on any linux system as version 1 is totally insecure and also slow.
[Nexus 5X Original Android Development] jcmm11:
[MENTION=3292224]franciscofranco[/MENTION] I've noticed that on 8.1 it seems that FKM posts the message about "will process boot script in 10 seconds" but it never seems to post the follow up msgs about actually applying the scripts. I think the scripts are applied (although I haven't verified that - I probably should. Will edit this after I check)

This is with FKM 3.0b8

Edit: Double checked and yes the values are correctly applied. That makes this a very minor niggle but I still wonder why the "applying" and "finished" toasts aren't showing up.
[Nexus 5X Original Android Development] :
Yeah I tried that, but it failed with invalid argument.
[Nexus 5X Original Android Development] miodrag.cutura:
Hey [MENTION=3292224]franciscofranco[/MENTION]

This kernel no longer supports exFast as usb OTG?

I flashed it, but says that my USB OTG is corrupt.

Thank you!
[Nexus 5X Original Android Development] dr.nunu:
[MENTION=3292224]franciscofranco[/MENTION]

Great job! I'm impressed by your work.

Truly amazing kernel > battery life, responsiveness...

Best! Thank you!
[Nexus 5X Original Android Development] skinner12:
I'm using r53 but FKM tells me that's an update. I've tried to flash from the app, but I still see that message.

It seems that FKM see r1 as kernel version.
[Nexus 5X Original Android Development] jcmm11:
Try the beta version of FKM. I thought he had already pushed this particular fix to stable but I guess not.
[Nexus 5X Original Android Development] skinner12:
Ok, resolved with beta. Thanks
[Nexus 5X Original Android Development] franciscofranco:
Sorry for the delay, have been busy with my new app https://play.google.com/store/apps/details?id=com.franco.agenda

r54 - March 8th, 2018

1. Merged March security patches

2. Some fixes

Auto-flash with http://beta.franciscofranco.xyz or get the zip from the OP
[Nexus 5X Original Android Development] duffymm:
I would like to report couple of random reboots on r54 that never occurred on r53 and I had to force-restart of the phone once too.

Thanks
[Nexus 5X Original Android Development] franciscofranco:
Can I see a log? /sys/fs/pstore/console-ramoops
[Nexus 5X Original Android Development] duffymm:
I really would love to provide them but... I've to admit I never learnt how to get them ! :D

Any app that would simplify the operation ? I'm rooted
[Nexus 5X Original Android Development] holmesmcgee:
I've lost the fingerprint scanner functionality with r54.
[Nexus 5X Original Android Development] holmesmcgee:
It came back after a random reboot.
[Nexus 5X Original Android Development] jcmm11:
After a random reboot simply copy the file that Franco referenced (the ramoops) and post it as an attachment (zip it first if needed).
[Nexus 5X Original Android Development] weaselskhs:
I have had the same random reboots on 54 also but I made a mistake and reloaded 53 before I saw some else post. I am going to reload 54 and see if it happens again then I will post a log.
[Nexus 5X Original Android Development] holmesmcgee:
I just had another fingerprint/reboot issue, but that directory on my phone is empty.
[Nexus 5X Original Android Development] jcmm11:
The directory is /sys/fs/pstore/

There should be 2 files in there, one of which is named console-ramoops. That's the file you want.

If that file really doesn't exist double check and make sure you're actually running Franco - because it should definitely be there.
[Nexus 5X Original Android Development] holmesmcgee:
I can't seem to find it. (I also can't post links to photos, apparently.) Edit: Now they're working.

https://photos.app.goo.gl/RyKp1OkWSBeT3rLO2

https://photos.app.goo.gl/RkJ58SoM8wBUSfhh2

https://photos.app.goo.gl/cSZ3BxvTYQeqDZpH3
[Nexus 5X Original Android Development] jcmm11:
Just have to wait on him. Don't know what to tell you.
[Nexus 5X Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION] is your defconfig on github update to date? CONFIG_CIFS_SMB2 isn't set which is needed for SMB2/3
[Nexus 5X Original Android Development] duffymm:
Directory is empty even for me
[Nexus 5X Original Android Development] osm0sis:
Check /proc/config.gz when your device is booted for the config for the build you're running.
[Nexus 5X Original Android Development] :
Ta for that, checked that as well.

# CONFIG_CIFS_SMB2 is not set

Need that set to enable SMB2/3.
[Nexus 5X Original Android Development] paaaulo:
I also get random reboots on r54.

Fingerprint scanner (hardware not available) occurred on my device as well.
[Nexus 5X Original Android Development] weaselskhs:
I checked the log location in the pstore directory and it was also empty.
[Nexus 5X Original Android Development] eak1080:
Reboots with 54.... Also no logs in the usual places to look... Directories empty
[Nexus 5X Original Android Development] aeroseek:
Also had random reboot on r54. Log attached.
[Nexus 5X Original Android Development] zurik:
I have too random reboots with r54. I moved temporarily to stock.
[Nexus 5X Original Android Development] emiliocolombero:
i have the same issue. Where can i find ths stock kernel? Im running 8.1
[Nexus 5X Original Android Development] j-a-d-z:
Download your factory image and flash only 'boot.img' in Fastboot mode.

Or copy the file 'boot.img' to your internal memory and flash it in TWRP to the partition named 'boot'.
[Nexus 5X Original Android Development] paaaulo:
You can revert to r53. It works fine.
[Nexus 5X Original Android Development] zurik:
download factory image and extract the zip file from the zip file (inside of the zip file there is an another zip that includes boot.img file.)
[Nexus 5X Original Android Development] um.z:
Got reboots and weird behaviour (screen didn't turn on when pressing power button, had to hard reset) when charging with non-stock charger on r54.
[Nexus 5X Original Android Development] jcmm11:
Something similar here. Ramoops attached
[Nexus 5X Original Android Development] :
Reboots and Freezes at 100% Charge

As the title suggests I only noticed it reboot once it reached 100% battery. I am using the stock charger that came with my 5x. The kernel is smooth as hell and the only problems I've experienced were during charging and ONLY once it reached 100%. No random reboots or crashes here. A couple of mornings of my phone not waking up while on the charger and having to force restart got me thinking that was the trend. Here's the log. Let me know if I can provide any more information!
[Nexus 5X Original Android Development] eak1080:
[MENTION=3292224]franciscofranco[/MENTION] you don't touch the charging tables at all right? From logs I think it's something with coming out of sleep not charging...
[Nexus 5X Original Android Development] reekoh:
Here's another console-ramoops from an unexpected reboot while the phone was on the charger.

app.box.com/s/xbgyl4nkfji1skvsueg0x2r99mu4b3to
[Nexus 5X Original Android Development] um.z:
I saw that the changelog for r54 said something like 'implemented March security updates.' Could it be that the weird behaviour I experienced on r54 (am back on r53 now and all's fine) was due to me being on a rom that is still based on Google's February factory image?
[Nexus 5X Original Android Development] jugoslavpetrovic:
It definitely not should be from security patches since I tried ElementalX and Shadow kernels with the same patches and no issues.