[Kernel | Android 10 | One UI 2.5 | FUF5/FUH1/FUJ2/FUK1/FVC2/FVH1] BeastMode Kernel v2 for N960F | v2.18f1a3 | 20230223

[moderndaycowboy]

thanks for reporting

just learned that it may be due to a bug with ext4 but not get patched in linux 4.9
let me check

You're welcome, overall Performance seems to be equal than before. Decreasing read speed doesn't feel bulkier than previous version.

 

[TechNoobForSale]

As expected the performance is the same as before. I don't usually do storage benchmarks for non F2FS platforms because they will be obviously not as fast as they can possibly be. Not much else to say. These are pretty useful tweaks though. Keep it up man.

 

[TechNoobForSale]

I wonder what does FUH1 and FUF5 mean though. I don't know which one to flash

 

[ykkfive]

I wonder what does FUH1 and FUF5 mean though. I don't know which one to flash

goto dialer, type *#1234# and read AP

 

[ykkfive]

You're welcome, overall Performance seems to be equal than before. Decreasing read speed doesn't feel bulkier than previous version.

As expected the performance is the same as before. I don't usually do storage benchmarks for non F2FS platforms because they will be obviously not as fast as they can possibly be. Not much else to say. These are pretty useful tweaks though. Keep it up man.

glad to hear at least it performs on par with the previous one, as more and more features added the performance could be affeced especially some tracing functions have been introduced

anyway, thanks for you guys' time as i cannot check every aspects every time i release a new version. of coz i would like to see perfomance gain each time but it's not guaranteed. so keep me informed or otherwise we wouldnt have a revised version based on the previous built which out performed as much as 30%

so pls continue to provide me feedbacks and tell me if you like it

thanks

 

[amit_coolcampus]

I am using this version since yesterday night, and it's definitely working well. Less heating and screen used to get non-responsive with the earlier version. But no such case with the newer version so far.

 

[TechNoobForSale]

Either way, the same previously known issues remain, and they can be quite bad for gaming and work performance. I'll do the usual summary.

1: CPU only goes to 2886MHz in single core (I have found 2964MHz as maximum frequency in the sys files but it isn't in the freq table so it isn't used for single core). Dual core and Quad Core are at 2314MHz and 1794MHz respectively. Pushing Dual at 2496 or 2652MHz and Quad at 2314MHz will dramatically increase performance at a moderate battery life cost (2314MHz was originally the intended Quad Core mode frequency of the 9810, and in fact, above that, diminishing returns suddenly appear.).

2: System throttles at 70°C. It is an extremely conservative choice considering we are overclocking a phone. Throttling causes a bug that makes the user unable to reach 2002MHz on small cores (Hard caps at 1950MHz even if I try to change in hKTweaks). Same for GPU, but the hard cap frequency varies there. Putting 90°C is a good balance between safety and maximum possible performance.

3: GPU frequency just does whatever it wants. Rising the minimum frequency to anything higher than 260MHz in an attempt to get more gaming performance doesn't work. Boost frequency threshold at 15% doesn't seem to make the GPU boost aggressively either.

4: If the GPU overclock is ever enabled again, it seems that there is a 775MHz frequency in the table. It would bring huge benefits to gaming. 598MHz is meh. It's just an extra 26MHz so.

That's all. The first 3 are bugs. The last one is just a suggestion.

 

[ykkfive]

I am using this version since yesterday night, and it's definitely working well. Less heating and screen used to get non-responsive with the earlier version. But no such case with the newer version so far.

you mean compared with 2.10?
i didnt notice any huge differences except better battery consumption, could be due to there were too many internal builts for self testing, but it's a bump for you guys with about 10 builts skipped

 

[amit_coolcampus]

you mean compared with 2.10?
i didnt notice any huge differences except better battery consumption, could be due to there were too many internal builts for self testing, but it's a bump for you guys with about 10 builts skipped

Yes 2.10 vs 2.11. My phone used to get over heated and then no response on touch. I dont know why. But it was random, normally it worked fine. Once touch was non-responsive, then only hard restart was the way. This one is working fine, fingers crossed.

 

[ykkfive]

Either way, the same previously known issues remain, and they can be quite bad for gaming and work performance. I'll do the usual summary.

1: CPU only goes to 2886MHz in single core (I have found 2964MHz as maximum frequency in the sys files but it isn't in the freq table so it isn't used for single core). Dual core and Quad Core are at 2314MHz and 1794MHz respectively. Pushing Dual at 2496 or 2652MHz and Quad at 2314MHz will dramatically increase performance at a moderate battery life cost (2314MHz was originally the intended Quad Core mode frequency of the 9810, and in fact, above that, diminishing returns suddenly appear.).

2: System throttles at 70°C. It is an extremely conservative choice considering we are overclocking a phone. Throttling causes a bug that makes the user unable to reach 2002MHz on small cores (Hard caps at 1950MHz even if I try to change in hKTweaks). Same for GPU, but the hard cap frequency varies there. Putting 90°C is a good balance between safety and maximum possible performance.

3: GPU frequency just does whatever it wants. Rising the minimum frequency to anything higher than 260MHz in an attempt to get more gaming performance doesn't work. Boost frequency threshold at 15% doesn't seem to make the GPU boost aggressively either.

4: If the GPU overclock is ever enabled again, it seems that there is a 775MHz frequency in the table. It would bring huge benefits to gaming. 598MHz is meh. It's just an extra 26MHz so.

That's all. The first 3 are bugs. The last one is just a suggestion.

will look into these as i mentioned before since this one was focused on the file system updates. hopefully we can push it further after the ext4 problem just mentioned got fixed

 

[ykkfive]

Yes 2.10 vs 2.11. My phone used to get over heated and then no response on touch. I dont know why. But it was random, normally it worked fine. Once touch was non-responsive, then only hard restart was the way. This one is working fine, fingers crossed.

that's weird.... i have never faced that kind of problems before even with test builds. could it be dirty flashing custom roms?

anyway, glad to hear it finally get solved

 

[amit_coolcampus]

that's weird.... i have never faced that kind of problems before even with test builds. could it be dirty flashing custom roms?

anyway, glad to hear it finally get solved

No dirty flashing. But I am happy to continue with the current one. Many thanks.

 

[TechNoobForSale]

Also to add that while trying to make my phone use F2FS I got such a big L. Thank God I had backups. I had changed system, cache and data to F2FS. So I formatted the phone. Tried to boot like an idiot forgetting I had...deleted the damn system with the conversion LMAO. I was on stock One UI 2.5 and Kernel Version 2.11c6. I have returned the partitions to EXT4 and also while trying to put the backup on the phone in TWRP I noticed I couldn't move the system emmc.win file because it's over 4GB. Making me unable to move the backup. Though I have others that I should be able to restore since their system is smaller. I am going to restore this EXT4 backup and hope it brings everything back to normal.

The bad part however is that the system_image.emmc.win file is 4.8GB therefore can't be moved on the phone. And having no system, I definitely can't move that. So what I wanted to ask you is that if the system.ext4.win files will be enough for me to restore the system. I don't even know if I should make the vendor partition F2FS too.

 

[TechNoobForSale]

Well the backup didn't restore my system properly I suppose . It goes to the Samsung logo with a blue led for a while and then goes back to the Samsung Galaxy Note9 logo with a blue led endlessly. ykkfive, do you have any idea how to help me here lol? I would really appreciate it.

 

[TechNoobForSale]

I will try to move on AlexisROM One UI 2.5. With my phone unusable I can't keep providing benchmarks for your Kernel versions. Therefore I have to do absolutely everything I can.

Edit: Moving over to AlexisROM was successful. However being unsure whether it supports F2FS or not I will stick with EXT4 for the time being.

 

[ykkfive]

I will try to move on AlexisROM One UI 2.5. With my phone unusable I can't keep providing benchmarks for your Kernel versions. Therefore I have to do absolutely everything I can.

Edit: Moving over to AlexisROM was successful. However being unsure whether it supports F2FS or not I will stick with EXT4 for the time being.

so you have restored your phone now? i mean at least it is working properly atm ?
there are something that need to be done before going f2fs, i will tell you later why

 

[TechNoobForSale]

so you have restored your phone now? i mean at least it is working properly atm ?
there are something that need to be done before going f2fs, i will tell you later why

Yes I managed to restore my phone from the soft brick status. The whole problem was actually due to a distraction mistake I made. It’s working and fine now though. But I am on EXT4 because I am not sure if the Alexis ROM 3.0 supports F2FS.

 

[ykkfive]

Yes I managed to restore my phone from the soft brick status. The whole problem was actually due to a distraction mistake I made. It’s working and fine now though. But I am on EXT4 because I am not sure if the Alexis ROM 3.0 supports F2FS.

don worry, all (or most) custom roms, as well as stock rom, by default will format partitions to ext4, so you wont brick it. on the other hand, your f2fs partitions will be reformatted back to ext4 when you install a rom. although it's not ideal, you have to live with it unless they change the way how they handle the file system

for f2fs, you will need to modify the fstab.xxxxx file under vendor/etc/ by adding entries to tell the system to mount the partitons as f2fs or otherwise the mount process will fail

i don wanna talk about this too much as it is out of my control and out of the scope of a thread talking about kernel, since this should be discussed in the rom's thread in my humble opinion. however there are some good tutorials regarding how to convert from ext4 to f2fs though

i hope you will understand my situation

 

[TechNoobForSale]

don worry, all (or most) custom roms, as well as stock rom, by default will format partitions to ext4, so you wont brick it. on the other hand, your f2fs partitions will be reformatted back to ext4 when you install a rom. although it's not ideal, you have to live with it unless they change the way how they handle the file system

for f2fs, you will need to modify the fstab.xxxxx file under vendor/etc/ by adding entries to tell the system to mount the partitons as f2fs or otherwise the mount process will fail

i don wanna talk about this too much as it is out of my control and out of the scope of a thread talking about kernel, since this should be discussed in the rom's thread in my humble opinion. however there are some good tutorials regarding how to convert from ext4 to f2fs though

i hope you will understand my situation

To be honest as far as I'm aware for ROMs like LineageOS, you can simply format the partition to F2FS and the ROM installer will simply write on that since Lineage does support F2FS. And either way there are different setups for F2FS. Like putting only data and cache as F2FS (which still grants the vast part of the speed boost), while system remains EXT4 if F2FS is unsupported.

Either way yeah you're right and I understand you. I've already fixed my phone and EXT4 does the job nearly as good as F2FS in 2021. We can easily close this little parentesis and move on. You know the drill with my observations lmao.

 

[ykkfive]

To be honest as far as I'm aware for ROMs like LineageOS, you can simply format the partition to F2FS and the ROM installer will simply write on that since Lineage does support F2FS. And either way there are different setups for F2FS. Like putting only data and cache as F2FS (which still grants the vast part of the speed boost), while system remains EXT4 if F2FS is unsupported.

Either way yeah you're right and I understand you. I've already fixed my phone and EXT4 does the job nearly as good as F2FS in 2021. We can easily close this little parentesis and move on. You know the drill with my observations lmao.

yeah you are right
and tbh that's why when i heard f2fs is rom dependent at first, i was so shocked. although i understood why later since the fstab has been moved from the initrd to /vendor