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

[Detonatte]

How do you say it would be better? Flash with ODIN files BL and CP N960FXXS8FUE5 Android 10 Germany (DBT) (03.06.2021) ? Should I flash these two new files over Q16?

Edit: flash Bootloaders and Modem with:

https://github.com/corsicanu/9810-bootloaders_and_modems/releases/download/N960FXXS8FUE5/N960FXXS8FUE5-twrp_flashable.zip

Now i have Q16 with last bootloader and modem.

 

[ykkfive]

How do you say it would be better? Flash with ODIN files BL and CP N960FXXS8FUE5 Android 10 Germany (DBT) (03.06.2021) ? Should I flash these two new files over Q16?

Edit: flash Bootloaders and Modem with:

https://github.com/corsicanu/9810-bootloaders_and_modems/releases/download/N960FXXS8FUE5/N960FXXS8FUE5-twrp_flashable.zip

Now i have Q16 with last bootloader and modem.

ok, now you can test how's the battery consumption for a while. is it still draining battery like before you flashed the bootloader?

 

[Detonatte]

Charge battery 100%. Now testing.

 

[ykkfive]

v2.03 released
- basic "magisk detected" fix

 

[chuyennho184]

@ykkfive: V2.03 still have to detect root with citi bank app. See below pictures.

P/s: I'm still testing v2.02. It's take much time to test. But now still have a drain battery in first day test.

 

[ykkfive]

@ykkfive: V2.03 still have to detect root with citi bank app. See below pictures.

P/s: I'm still testing v2.02. It's take much time to test. But now still have a drain battery in first day test.

for the citibank app:
you need to apply this https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/ in magisk, as well as magiskhide props configs, then in magiskhide section, check (select ) the whole citibank app subprocess

for the battery problem: how's battery consumption now? you may need to replace some files from ue5 ultimately

anyway, try to fix citibank app 1st. for me, it's ok (not the same citibank app as yours)

 

[chuyennho184]

for the citibank app:
you need to apply this https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/ in magisk, as well as magiskhide props configs, then in magiskhide section, check (select ) the whole citibank app subprocess

for the battery problem: how's battery consumption now? you may need to replace some files from ue5 ultimately

anyway, try to fix citibank app 1st. for me, it's ok (not the same citibank app as yours)
View attachment 5349839

With magisk safetynet v1.1 make my device bootloop before. Also I'd hide magisk app in setting. I know a solution to bank app working is hide magisk app by rename magisk app to another name app. Don't worry about it. Only care about battery saver.


You said "you may need to replace some files from ue5 ultimately". I don't know this sentence. Please explain detail to me. Thanks mate.

With your kernel, sometime my device have random boot. I don't have idea about your kernel or rom (Alexis rom v2.8)? So, I need test more.

 

[ykkfive]

With magisk safetynet v1.1 make my device bootloop before. Also I'd hide magisk app in setting. I know a solution to bank app working is hide magisk app by rename magisk app to another name app. Don't worry about it. Only care about battery saver.


You said "you may need to replace some files from ue5 ultimately". I don't know this sentence. Please explain detail to me. Thanks mate.

With your kernel, sometime my device have random boot. I don't have idea about your kernel or rom (Alexis rom v2.8)? So, I need test more.

well that's not looking good, i mean the battery consumption. however the 2nd and the 3rd apps in the list seem consuming a lot of battery

for replacing the files from ue5, i mean, since you are using Q16 and it's UE1 based, some of the files may not be compatible with UE5 and this could cause problems. so what i did was, extracted those related files from the original UE5 stock rom and replaced them on my phone with Q16, like build.prop etc, in order to make it look like a real UE5. so if I can make it, why cant you, rite?

but i wonder if this helps since your battery consumption seems a bit unusual

this is mine

 

[ShadoVeX]

How to activate dt2w (double tap to wake) in Alexis 2.8 rom?

 

[ykkfive]

How to activate dt2w (double tap to wake) in Alexis 2.8 rom?

it should be on by default
note that you'll have to turn on display always on , i didnt know too at first

in case this is not the way you want (just like me before) and want to have dt2w with unlock, ie no need to press hard at the bottom, sorry the answer was no, that's what i got from other kernel developer. i think it can be done on the rom level as to bypass it, but yet to have time to investigate

 

[ykkfive]

NOTE

for those using kernel manger like hktweaks, mtweaks, etc:

if you have been playing around with the cpu page and turning on and off the cpu cores before
AND
if you have saved the settings in profile, please check your profile settings in those app by clicking on the menu in the profile page and select profile details to see if you are actually running with one or more cpu cores offline

if you find in the details something like below, then you have turned off one or more cores, ie you are not running with all cores online! look for a line looks like:

echo 0 > /sys/devices/xxxxxxxxxx/cpu/cpu7/online

0 means off, so the above command will turn off core 4 in m3 (cpu 0-3 refers to the little cores, 4-7 refers to the big cores)

i have checked by command these app will actually turn off the cpu core but just do not show them properly in the app, and have problems in turning the cores back online

remedies for normal users:
- disable run at boot option and reboot (to let all cores online again)
- re-apply the settings you have made before but DON'T touch the online/offline toggles
- save as a new profile
- check the profile details again and make sure you didnt bring any of them offline before applying auto start option

OR (just found out last nite)
- click one the profile's menu, choose edit
- select those unwanted item one by one in the list, and delete


good luck!

 

[ykkfive]

EDIT 20210804
a more aggressive gpu voltage settings is posted here awaiting a fix



BM-Kernel-v2.04m released

20210726 - v2.04m
- compatible with FUF5 (** may have problems if you use lockscreen or samsung account with possible fix here. ALWAYS do a full backup first)
- overclocked: cpu little to 2002000Mhz, gpu to 598000Mhz
- undervoltaged: cpu/memory
- support gpu under voltage
- linux upstreamed to 4.9.250
- cherry picked some kernel tweaks
- for undervolting the gpu, you may refer to my initial safe settings below and adjust them by yourself. there are still rooms to undervolt, but it is suggested you do it bit by bit, and one by one and test the new voltage before next

 

[danerrickcuba@gmail.com]

f2fs support is still further ahead or implemented?

 

[jayjay1234]

Couldn't get pass lockscreen after flashing v2.04m.

 

[ykkfive]

f2fs support is still further ahead or implemented?

some problems for data partition causing boot loop , besides, i found that twrp 3.3.x produces some errors when formatting to f2fs. not recomended at this point
but if you wish, you may try the twrp provided by whitewolf kernel, there's a n9 version

 

[ykkfive]

Couldn't get pass lockscreen after flashing v2.04m.

fuf5? i personally dont use lockscreen
let me try later today
sorry and thanks


edit btw, i have a test build for addressing fuf5 compatiblility issues (link removed), see if you wanna give it a try

 

[jayjay1234]

Thanks! I'll give it a try.
Here's my firmware info.

 

[jayjay1234]

Thanks! I'll give it a try.
Here's my firmware info.
View attachment 5370741

FYI, just tried new test build and still a no go. Couldn't even dirty flash back to get in ROM. Had to do a factory reset.

 

[ykkfive]

FYI, just tried new test build and still a no go. Couldn't even dirty flash back to get in ROM. Had to do a factory reset.

my apology... i will remove the link then.
which rom you are on? from what i have read most of the lockscreen problems can be fixed on the rom level . otherwise u may have to wait for samsung to release the latest sources

edit by the way you may follow the solution provided by @evdenis :

"You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin."
note that the solution for samsung account didnt work for me unfortunately

original posted here https://xdaforums.com/t/kernel-2020-12-01-cruel-kernel-s10-note10-v3-9.4063495/post-81959141

 

[jayjay1234]

my apology... i will remove the link then.
which rom you are on? from what i have read most of the lockscreen problems can be fixed on the rom level . otherwise u may have to wait for samsung to release the latest sources

edit by the way you may follow the solution provided by @evdenis :

"You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin."
note that the solution for samsung account didnt work for me unfortunately

original posted here https://xdaforums.com/t/kernel-2020-12-01-cruel-kernel-s10-note10-v3-9.4063495/post-81959141

Thanks for the suggestion. I'll try it if it happens again.

I'm on ALEXISROM_2.9.