yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] drdrewdown:
appreciate the advice, she's leaving town tomorrow so i'm nervous to play with it before but i'll keep what said in mind for more testing when she returns. but yeah we've both purchased all your apps since nexus4 lol

thanks again :)
[Nexus 5X Original Android Development] ViRb3:
Is there any way to make this kernel work with SuperSU 2.50 (the last system-mode version)?
[Nexus 5X Original Android Development] nathanchance:
Nope. You can always compile it yourself with a modified sepolicy but Franco has said he is sticking with systemless root.
[Nexus 5X Original Android Development] skulldreamz:
When i boot into twrp I'm aware that twrp decrypts the data but is it possible to have the phone say decrypted under settings > security > encryption using this kernel? I could swear when i was running EX kernel the phone said decrypted but maybe I'm incorrect
[Nexus 5X Original Android Development] nathanchance:
It will say Encrypt Phone if you are decrypted. If you aren't decrypted already, you need to boot into TWRP, select Wipe then hit Format Data. This will nuke your internal storage and app data so make a backup before you do that.
[Nexus 5X Original Android Development] skulldreamz:
Huh... I did format data. Weird, that it says encrypted. I'll boot into twrp and format data again and post if that works for me now. Appreciate the quick response [MENTION=6842057]nathanchance[/MENTION] ;)

So I did format data like you said and now it says encrypt phone. Thanks again my dude
[Nexus 5X Original Android Development] blinkin:
Does it say encrypt phone encrypted? It's displayed under settings / security right?
[Nexus 5X Original Android Development] LazerL0rd:
It would be great if the battery life mods could restore on boot :D!
[Nexus 5X Original Android Development] franciscofranco:
Yes. I explained why in the medium post ;)
[Nexus 5X Original Android Development] Eurofighter_ty:
Hi,

[MENTION=3292224]franciscofranco[/MENTION] do you have the problem regarding the battery dropping 2% at a time?

I have this problem for a long time. I am not expecting for a fix. Just tell me if you have the same problem or is just me.
[Nexus 5X Original Android Development] LazerL0rd:
Try calibrating the battery. It might just need that :eek:.
[Nexus 5X Original Android Development] Eurofighter_ty:
It is 2 months old.... I don't think that new phones needs calibration
[Nexus 5X Original Android Development] LazerL0rd:
Ohhh, I'm not sure. Try a clean flash and only use mods and ROM from well-known developers.
[Nexus 5X Original Android Development] Eurofighter_ty:
I tried to use stock & locked bootloader and the same problem. I don't know why this happens.
[Nexus 5X Original Android Development] LazerL0rd:
[MENTION=3292224]franciscofranco[/MENTION] could you add Dynamic FSync to this kernel? It would improve performance and it's quite safe. It doesn't have to be enabled by default and I'm happy to test it out...

---------- Post added at 11:43 AM ---------- Previous post was at 11:35 AM ----------

I really don't know then. I'm sorry mate. You might have a fault battery. If you haven't, try doing an factory image flash.
[Nexus 5X Original Android Development] Dread This Day:
It can't hurt to try.
[Nexus 5X Original Android Development] Eurofighter_ty:
I did a wipe reflashed the kernel and the battery life is good just the dropping 2% is still here. Anyway I changed the thermal limit to 60 C beacuse it was throttling to much.
[Nexus 5X Original Android Development] BS86:
It is already included since forever? just change the I/O fsync to disabled in FKU's kernel settings
[Nexus 5X Original Android Development] franciscofranco:
That's just the battery algorithm over correcting itself. Don't worry about it.

Nope. I talked about fsync with a Kernel engineer for the Pixel and it's not something I'll pursue due to a chance (even if small) of data corruption if there's a power failure.
[Nexus 5X Original Android Development] LazerL0rd:
We are able to disable it normally, couldn't you add it as an option at least?
[Nexus 5X Original Android Development] franciscofranco:
Not likely. I won't share the conversation, but he was pretty darn vehement about it, so I'm not going to play the chances. While on disabling fsync altogether you know where you're getting yourself into, but with that "dynamic" mode you're relying on screen off for the device to sync in everything to-from disk, flushing dentries etc, and you don't want to crash while that operation is underway.
[Nexus 5X Original Android Development] Polloos:
For some versions the volume of the headphones is low, I have to upload it +8 in the app to make it the normal volume. Anyone else wrong?
[Nexus 5X Original Android Development] franciscofranco:
The volume is the same on all releases since day 1.
[Nexus 5X Original Android Development] James1o1o:
I can't seem to get F2FS working. Everytime it boots up it resets the /data partition to EXT4.

I saw some people suggesting that I flash SuperSU BEFORE flashing franco.Kernel, however it does not make a difference.
[Nexus 5X Original Android Development] ndarkside93:
In twrp. Go to settings and check rm -rf. That way when you reformat and flash a room it won't revert to ext4. Should fix your problem
[Nexus 5X Original Android Development] James1o1o:
I tried that aswell mate. I'm not even reformatting or flashing a room when I change to F2FS. I flashed SuperSU, flashed Franco.Kernel. Converted data and cache to F2FS then rebooted. It would take a wee while to boot then Cache would be on F2FS but Data had reverted back to EXT4.
[Nexus 5X Original Android Development] ndarkside93:
Oh, okay. I'm sorry to hear that. I wish I had another suggestion.
[Nexus 5X Original Android Development] franciscofranco:
I really dunno. I have everything setup as it should on my side, including fstab mount entries. I'm sorry :(
[Nexus 5X Original Android Development] LazerL0rd:
You convert them BEFORE you flash SuperSU and franco kernel. Remember SuperSU needs the data how it is flagged unto for it's su.img and franco's anykernel 2 mod thing edits the loopback on that same su.img file for it to work!
[Nexus 5X Original Android Development] Nicktheprofessor:
Just as an aside to the kernel talk regarding f2fs and i'm sorry Franco because it is off topic.

There is absolutely no noticeable difference between using ext4 without journalling and f2fs and in most cases unless you are running a 150GB+ SQL database on your device you will never see any difference.

It is not worth the effort.

Also, reviewing the fstab it will be mounted as f2fs if it is at all possible and ext4 if it is not.

Whatever the problem is it's not on the kernel side, if you formatted your data partition as f2fs and installed the kernel it will be mounted as f2fs.
[Nexus 5X Original Android Development] Eurofighter_ty:
[MENTION=3292224]franciscofranco[/MENTION] Hi, I have a little problem with the big cores. The Bic cross gets limited to 633 MHz when certain temperature is reached even when I changed the thermal limit to 80°C. (I know I am crazy)

How can I get 1.8 GHz on big cores even on high temperatures?

I know the risks..
[Nexus 5X Original Android Development] AlienTeck:
First time user and I noticed this as well. I run dolby atmos and for some reason that started working with VLC but not the music app. The volume was low so cant use it without a boost. Went back to original boot/kernal for 7.1.2 and now the sound level is back to normal but dolby atmos wont work with VLC but it does with other apps. So the kernal is doing something with the sound. Sound mods seems to have problems with N5x for lots of people.
[Nexus 5X Original Android Development] LazerL0rd:
There's a low-level hardware thing that stops them, and before that in the ROM is the thermal.config that stops them at dangerous levels. Therefore it's not the kernel's fault.

---------- Post added at 01:00 PM ---------- Previous post was at 12:55 PM ----------

I've explained it here: https://xdaforums.com/android/software/sound-mod-z-soundmod-v1-beta-t3419416/post70977453
[Nexus 5X Original Android Development] AlienTeck:
Okay seems you have to flash vendor and then flash install the dolby sound mods or it crashes and might be why so many had problems, due to vendor mismatch there.. Although still strange that the kernal from 7.1.2 wont allow dolby sound to work with VLC.. So This kernal r34 is not exactly the same base as the google 7.1.2 kernal in that respect and the difference is the reason for low volume.. Hmmm seems quite a steep learning curve..
[Nexus 5X Original Android Development] marcelotoma:
Hey [MENTION=3292224]franciscofranco[/MENTION], I have been a user and appreciate your work since my LG P500, then Nexus 5 and now on Nexus 5X.

I just want to thank you for the r34 of February 7. Everything working perfectly.

Thank you!
[Nexus 5X Original Android Development] James1o1o:
Just tried this and it's still not working. Convert /data and /cache to F2FS, flash SuperSU, flash kernel, reboot, takes a while to load, and suddenly its back on ext4.
[Nexus 5X Original Android Development] LazerL0rd:
That's weird, it should work. Have you tried doing that as a format with a clean install?
[Nexus 5X Original Android Development] James1o1o:
Yeah I just did that a few minutes ago, fresh factory image.

Flashed the recovery, formatted the data partition to remove encryption, converted FS to F2FS, did same for /cache.

Flashed SuperSU, flashed, Franco Kernel, checked the fstab entries, shows F2FS. Reboot, and then I can either into Disk info from playstore or just reboot once I'm at the Welcome screen and go into recovery to check the /data partition. It's back at ext4, /cache is still on F2FS though.

It's a genuine mystery.
[Nexus 5X Original Android Development] LazerL0rd:
Is it possible to run file-based encryption on f2fs? According to Wikipedia, the f2fs file system supports it.
[Nexus 5X Original Android Development] James1o1o:
Well the first time I tried on the fresh install I actually converted it without formatting first, even though it still converted BACK to ext4 it was still encrypted, so on the second time I tried I made just to format before converting just in case. Both ways just resulted in the same conversion back to ext4.
[Nexus 5X Original Android Development] LazerL0rd:
It would be cool to... But our TWRP doesn't support file-based encryption so that'll be quite annoying.
[Nexus 5X Original Android Development] Carach_CZ:
Supports Lineage OS?
[Nexus 5X Original Android Development] zurik:
I flashed with LineageOS and it's working.
[Nexus 5X Original Android Development] franciscofranco:
Of course it's working :highfive:
[Nexus 5X Original Android Development] BS86:
The only thing that is different on LineageOS is that it somehow overrides the kernel-default and sets the I/O scheduler to bfq.

It happens that way on my N5X and on my N7 2013 - you can change it back to the kernel-default in FKU and if set on boot is activated, it will stay that way.

[MENTION=3292224]franciscofranco[/MENTION] I suppose there is no other way for you to revert that override? They are doing it like that:

https://github.com/LineageOS/androi...mmit/5c5e0f6f60e7ce6f89daa46a57dc115752062be6
[Nexus 5X Original Android Development] Carach_CZ:
I dont have paid version of FKU. But i doenloaded Kernel Adiutor. Which I/O is default?

Thanks for pointing it out! :)
[Nexus 5X Original Android Development] jcmm11:
noop is default for Franco.
[Nexus 5X Original Android Development] :
Pro tip: Get FKU, the donate version. ;) Js

Noopers
[Nexus 5X Original Android Development] franciscofranco:
Yes that's easy to override.
[Nexus 5X Original Android Development] LazerL0rd:
[MENTION=3292224]franciscofranco[/MENTION] Why do you prefer noop over bfq?
[Nexus 5X Original Android Development] buffer overflow:
[MENTION=7836278]LazerL0rd[/MENTION] By the book; "Modern smartphones now use Noop as the default scheduler due to the fact that it works quite well with flash based storage. However older devices may experience slower performance when selected. If you want a very simple I/O scheduler algorithm (because of battery life or latency reasons), you can select this." :)
[Nexus 5X Original Android Development] LazerL0rd:
I'm testing out bfq. It seems to perform better.
[Nexus 5X Original Android Development] Carach_CZ:
Ill buy it, no worries! ? Otherwise; pretty neat kernel. Not using anything else. Like - ever. Thanks!
[Nexus 5X Original Android Development] jcmm11:
It really depends on usage patterns. On a regular HDD bfq would win out. On flash memory/SSD drives not so much. You're not likely to see a huge difference no matter which you choose. See http://androidmodguide.blogspot.com/p/io-schedulers.html
[Nexus 5X Original Android Development] franciscofranco:
No particular reason. I/O schedulers on Android are kinda irrelevant.
[Nexus 5X Original Android Development] LazerL0rd:
I find using bfq only useful for big transfers. I might just try using deadline. Seems quick and snappy. I'm trying them out, bfq does seem to take more battery than noop though.

Also,I think they are relavent. Unless you use UFS 2.0 then you can use the double helix to read and write at the same time. So they kinda do affect it.
[Nexus 5X Original Android Development] BS86:
at work, I use deadline on the SSD and cfq on the HDD - the kernel in the distro only offers noop, deadline and cfq - the later 2 have performance issues with the applications I use on the SSD (they are heavily caching on the SSD)

at home, my distro also offers bfq and I use that one on my HDD and SSD's

on the phone, I try to follow what Google's dev's and franciscofranco are using as default - and they both use noop since the release of Nougat. They both usually know what they are doing.
[Nexus 5X Original Android Development] pirigu:
hi francisco! i just want tell you thank you to do this great work! but one question just for kick away my doubt... if i use your performance profile from your app for play games (i'm a vainglory player) did you think that profile increase the FPS and speed of the game? because if i set high quality on the game after 1 match i get an fps reduction but at medium quality he goes well! and second question... if i use that performance profile for 2 h playing vainglory and goes a little hot... did you think he can get a few hardware problems? thank's for answers and sorry for my bad english :)
[Nexus 5X Original Android Development] franciscofranco:
You'll be fine, it heats up but it throttles as much as it needs.
[Nexus 5X Original Android Development] LazerL0rd:
Maybe adding an option in your app to disable throttling? This and the Nexus 6P seem to have a bad case of it.
[Nexus 5X Original Android Development] ndarkside93:
Not really a good idea for the the rest of the soc. Also we gave known hardware issues on this device. Extra heat well only speed up their manifestation because of the heating and cooling cycles
[Nexus 5X Original Android Development] LazerL0rd:
I've disabled it and I've got less heating up. The throttling only forces some apps to need to go faster or something and just heats up even more. Well, disabling it worked for me. It's safe for most users and I've been using for 3 months and finding it cooler than my first 3 months of the phone.
[Nexus 5X Original Android Development] ndarkside93:
Well I'm glad it works for you. In my experience my phone just starts a runaway heating cycle when I disable thermal throttling. By any chance do you still have core control enables?
[Nexus 5X Original Android Development] LazerL0rd:
EDIT: it's enabled.

I did it like this, via a su.d script:

echo 1 > /sys/module/msm_thermal/core_control/enabled
echo N > /sys/module/msm_thermal/parameters/enabled

The only time I ever lag, is in Battery Saver.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Then why not having only one without choice?
[Nexus 5X Original Android Development] ndarkside93:
Well I'm glad it works for you. In my experience my phone just starts a runaway heating cycle when I disable thermal throttling. By any chance do you still have core control enables?

---------- Post added at 08:33 PM ---------- Previous post was at 08:04 PM ----------

Well that solves that conundrum. Core control is a hardware level thermal throttling system. It's actually more aggressive than the regular thermal throttling, but it works well most times
[Nexus 5X Original Android Development] buffer overflow:
[MENTION=6478047]jugoslavpetrovic[/MENTION] Well, some one maybe want to have choices. :p
[Nexus 5X Original Android Development] jugoslavpetrovic:
Then we could also have more irrelevant choices on cpu governors and included features, disabled by default but still possible to choose for whom ever would like to have to choose, I guess.
[Nexus 5X Original Android Development] buffer overflow:
[MENTION=6478047]jugoslavpetrovic[/MENTION] That's the spirit of open source, my fellow ! ?
[Nexus 5X Original Android Development] LazerL0rd:
[MENTION=3292224]franciscofranco[/MENTION], if I were to manually add an I/O scheduler, how would I do it?
[Nexus 5X Original Android Development] franciscofranco:
I doubt that's the case. The big cluster is a powerhouse of heat generation, cores should be offlined asap if things go crazy.

1 - I would be publicly hanged

2 - The available ones are standard on Linux

Fork the source, add them, compile, build the boot.img, flash it, profit.
[Nexus 5X Original Android Development] ndarkside93:
Turns out he disabled the temperature throttle parameter but left core control enabled, solved why it didn't overheat like crazy.
[Nexus 5X Original Android Development] jcmm11:
[MENTION=3292224]franciscofranco[/MENTION]

Why is /sys/module/msm_thermal/parameters/enabled set to N by default? At least that's what I have and I haven't changed it.

Also what exactly does /sys/module/msm_thermal/core_control/cpus_offlined do? Mine is set to 0. Is that correct?
[Nexus 5X Original Android Development] ulxerker:
Everything is correct.

According to intense researches msm_thermal should be disabled and core_control enabled.
[Nexus 5X Original Android Development] LazerL0rd:
Would I have permission to add it to yours, no sharing will be done.
[Nexus 5X Original Android Development] Paulino Necro:
Does this kernel have doubleTap2Awake? first of all, Thanks
[Nexus 5X Original Android Development] Tech_Savvy:
nope
[Nexus 5X Original Android Development] buffer overflow:
Is useless for this device.
[Nexus 5X Original Android Development] ndarkside93:
No, and it won't because the hardware isn't there to support it properly. To run d2w on this device rewrrites powering the lcd screen and leaving the digitizer powered on, thus preventing the phone from sleeping and inducing a massive power drain. That is why Franco will not put it in his kernel,and no kernel had it enabled by default.
[Nexus 5X Original Android Development] franciscofranco:
Just leave it, that's the same as stock.

You can do whatever you want with it, it's open source.
[Nexus 5X Original Android Development] :
Really big thanks for the last version of your App franco kernel updater 2.2.6 ! The battery life lab section is awesome ! More battery more FUN ;).

Really thanks you!
[Nexus 5X Original Android Development] Nicktheprofessor:
BFQ is probably the worst option possible since it is an advanced algorithm for a simple task which does take CPU power to perform while noop is the simply just not regulating io per any algorithm at all, it just provides it in the order it was requested.

Not that it will be noticeable at all either way.

I don't get this fascination with storage speeds on a phone that has adequately fast storage. If you moved to ROW and F2FS you might save half a second of load times in a week for your apps.

Here's another idea though, just use your phone and keep your apps in memory, never reboot or clear the memory unless you are absolutely forced to though hangs or software updates. That is how the phone is meant to be used.
[Nexus 5X Original Android Development] LazerL0rd:
I just moved to f2fs for the sake of it. But yeah, you're right. I've decided if I ever use a mod it's only if it runs system-level. Like normal system things. No "editing" or cleaning required. I do, from recently, use my phone like that. I don't even clear caches until a massive update comes. I just like speed for optimisation purposes, that's all.
[Nexus 5X Original Android Development] Nicktheprofessor:
You don't have to clear recent apps and you don't have to reboot, you never have to clear caches and you can let android do the cleaning on it's own.

"optimization" that does absolutely nothing but to make you spend time reformatting and using a less stable file system that will not be any faster (and in most cases slower unless you are running very large databases) is an exercise in futility.

Get involved in the actual code, improve it and add to it. That is the only way you will ever optimize anything.
[Nexus 5X Original Android Development] LazerL0rd:
Actually, f2fs is much faster. The UI is smoother too.
[Nexus 5X Original Android Development] franciscofranco:
F2FS does nothing to the UI. It's a file system, and most ****s are in ram cached anyway. It only really matters when reading/writting to/from the disk.
[Nexus 5X Original Android Development] :
Could you add an option in your App (franco kernel updater ) to control the power save mode please.

Because you lower the CPU usage to 1.24 GHz and let two big cores activated and we can't modify that actually with your App.
[Nexus 5X Original Android Development] BS86:
you can with a workaround: Set the throttle - temperature to 10°C or something that you will be always above - big cores switch off
[Nexus 5X Original Android Development] franciscofranco:
No because the Power saving profile is tied to the device's ramdisk, it's not editable. It actually didn't occur to me that I could disable the big cores on that profile. I'll probably do that for r35.
[Nexus 5X Original Android Development] :
OK thanks for helping ! :)

---------- Post added at 07:22 PM ---------- Previous post was at 06:47 PM ----------

Sorry to disturb your hard work again but as I know you are the best/ more advanced developer for our device I want your opinion of a tweak (that I suppose you know which I'm speaking...) that speed up the charging time by increasing to 2800 mha ?

Is it really "useful" (is it worth it), is it secure (I'm pretty sure that's not)?
[Nexus 5X Original Android Development] LazerL0rd:
Use this on CHARGING ONLY https://xdaforums.com/nexus-5x/orig-development/mod-xthermal-mod-fast-charging-cpu-gpu-t3477639

It's secure as it doesn't change the extreme/dangerous charging throttle temps so it'll just be warmer. By default throttling is thought with coolness in mind but I'm sure you don't mind having a slightly higher temp when charging for a higher speed.

---------- Post added at 07:17 PM ---------- Previous post was at 06:52 PM ----------

Sorry I meant that incorrectly. By UI I meant UX (User Experience in like Antutu for example). As in, I have faster app opening speeds and google play downloads + installations (/cache/downloads is in f2fs so it's faster). But you're right. The UI is RAM cached.
[Nexus 5X Original Android Development] franciscofranco:
Just leave it alone, it already charges fast.
[Nexus 5X Original Android Development] :
Thanks for sharing your opinion I need it to ne sure ?
[Nexus 5X Original Android Development] Giorgos Chatziioannou:
sorry to budge in, but try viber and scrolling through the stickers with and without f2fs, same deal with browsing in chrome (and i imagine the rest of browsers). tried f2fs in jolla kernel and the difference is easy to notice, so while i have no idea about the code in android, f2fs is an upgrade in my eyes
[Nexus 5X Original Android Development] zurik:
In r34 installed on LineageOS slow down a bit my phone. ...
[Nexus 5X Original Android Development] BS86:
it works without issues here, I am on LineageOS since the first official builds started and updating weekly.