[ROM][G96xF/DS/FD/N][ALEXNDR] * UHFVG4 * DevBase v7.4 * Encryption support [Sep-20]

[bilbonotry]

I also had the random reboots issue with 7.3. I disabled magisk bluetooth patcher module, installed 7.4, re-enabled magisk bluetooth patcher module, and voilà ! no more reboots
thanks @_alexndr for your awesome ROMs

I have to say that reboots came back, I finally switched to aosp ROMs

 

[measel]

After updating to the latest version I have severe battery drain, like 3-4 times faster discharge. Battery stats are non conclusive I flashed the latest bootloader as well but that didnt help.

Is there a know fix maybe?

 

[bilbonotry]

After updating to the latest version I have severe battery drain, like 3-4 times faster discharge. Battery stats are non conclusive I flashed the latest bootloader as well but that didnt help.

Is there a know fix maybe?

Usual suspect is Bluetooth library patcher Magisk module.

 

[measel]

Usual suspect is Bluetooth library patcher Magisk module.

Thanks for your help. Unfortunately I don't think that's it.
My steps so far:

• full backup with twrp
• System update to Alexandr SHFUJ2
• Battery drain started
• Restored backup
  => still battery drain
• System update again including bootloader (not sure if i tried that in the first run already)
• Uninstall the Bluetooth Library Patcher, flash the update again and reinstall the BLP (on Friday)
  => That did not fix the battery drain.
• Test if just uninstalling BLP stops the battery drain but it doesn't look promising so I flashed the update again.
  => That did not fix the battery drain.
  Plus: Having to re-pair everything after every reboot is not an option in the long run.
• Check 'top': the process 'tee_fastcall' is always on 65-85% CPU.
  - flight mode and the process is gone
  - disable mobile data and wifi, process gone
  - disable one of those two: process persistant and high cpu

Any idea what could be the culprit and solution here?

My setup:
I use two SIM cards both without VoLTE or WIFI callling.
Magisk active usually with two modules:
- F-Droid helper
- Bluetooth Library Patcher

I have to mention: I did the whole update just because I prematurely updated magisk to v24 ending up in all kinds of trouble and after trying to downgrade I couldn't Hide the app anymore (unfortunately I only figured out after the attempted system update that I just had to change the download path within the app).

/edit: Added logs, password: xda-batterydrain

 

[XDroidA]

@_alexndr
New SM-G960F firmware available (DBT): UHFVB4, Changelist 23733677, Security Patch Level 2022-03-01

 

[super_nooby]

let the chief cook....

 

[Stelvinov]

@_alexndr
Hello,
after upgrading to the latest version I get: failed to mount /odm no such file or directory.
My device is Samsung S9+ SM-G965F
All previous versions had worked flawlessly. Not any though. Now when I install older version have the same error displayed.

Update:
After several T&E the latest(and greatest) rom is installed by removing the *_noroot* switch. Which is a bit of a bummer. If there is a way to install this rom without rooting enabled will be just awesome.
Thank you for your continuous great work!

 

[measel]

Thanks for your help. Unfortunately I don't think that's it.


Any idea what could be the culprit and solution here?

For some reason the problem stopped after some time. Maybe updating some app or firewall rules helped mitigate the battery drain. I cant tell for sure.

 

[_alexndr]

@_alexndr
New SM-G960F firmware available (DBT): UHFVB4, Changelist 23733677, Security Patch Level 2022-03-01

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

 

[spamtrash]

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

The magisk after (including) 24.0 is without the magisk hide and requires a hell lot new workaround.
In my humble opinion: I would leave the base with 23, as everyone could update the magisk after flashing the ROM, while downgrading can be problematic.
That would be especially important in your situation, as direct checking and advice on potential problems would be impossible.

 

[spamtrash]

For some reason the problem stopped after some time. Maybe updating some app or firewall rules helped mitigate the battery drain. I cant tell for sure.

If you've made a "clean" install (or in some cases even in a case of dirty), then the Samsung's Battery Care need some time to learn what to put to sleep.
Perhaps is is the reason. I am actually observing similar - though: not dramatic - effect after each update.

 

[measel]

If you've made a "clean" install (or in some cases even in a case of dirty), then the Samsung's Battery Care need some time to learn what to put to sleep.
Perhaps is is the reason. I am actually observing similar - though: not dramatic - effect after each update.

You might not have read my cited post: There was a process gone rogue. Nothing to do with battery calibration. I did an upgrade, not a fresh install and I never experienced bad battery experiences with new phones (just my one data point).

 

[spamtrash]

You might not have read my cited post: There was a process gone rogue. Nothing to do with battery calibration. I did an upgrade, not a fresh install and I never experienced bad battery experiences with new phones (just my one data point).

Could you please point me: where I wrote about battery CALIBRATION?
Battery Care, although uses name: "Battery", it is actually OPTIMIZING processes by assigning priority to each one, e.g. which shall go to sleep at what moment/what time since last use.

 

[measel]

Could you please point me: where I wrote about battery CALIBRATION?
Battery Care, although uses name: "Battery", it is actually OPTIMIZING processes by assigning priority to each one, e.g. which shall go to sleep at what moment/what time since last use.

I'm not a programmer or engineer, maybe you have a point maybe not. In my case I'm sure that was not the source of the problem and if you read my post, you might agree with me.

 

[spamtrash]

I'm not a programmer or engineer, maybe you have a point maybe not. In my case I'm sure that was not the source of the problem and if you read my post, you might agree with me.

Oh yes, I fully agree with you: nobody have a clue, one process went nutts, process priorities resetting after update have nothing common and it was settled by a new firewall rule.
Happy that using your skills and efforts you have sorted the problem out.

 

[super_nooby]

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

it's working without any problems.

 

[franz.palmy]

it's working without any problems.

Same for me

 

[killer777]

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

Magisk 24.3 work fine for me on my G965F. And my banking apps also work with zigisk and safetynet fix

 

[noteespirit]

please advise if this can be installed on s9 scv-380 (japan) device.
a short guid is appreciated also.
thanks.

 

[blixer]

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

For me it's working fine, too