Database Develop

Audio Compatibility Patch (Formerly Universal deep_buffer Remover) [MMTEx]

This fixes music and streaming apps (Spotify, Pandora, etc) that aren't processing audio effects for various equalizer applications through the modification of audio policy.
Starting with v1.6 USB_policy patcher (upp) and Notification_helper remover (nhr) have been combined with acp. upp is to be used for usb dacs for v4a/jdsp. nhr is to remove notification_helper from audio_effects or delete the libvolumelistener.so binary. this prevents the "ducking" of v4a when you recive a notification and that notification comes in while playing music and v4a unprocesses and the processes again after the notification causing the volume to be extra loud. this stops that.
The vol key options are as follows :
- " Do you want to skip audio_policy patching? (Original acp before became 3in1 module)" This is asking if you want to skip what acp was before the combining of modules. if you are installing acp for spotify to process with v4a or jdsp then you'll want to select no here.
- " Would you like to skip notification_helper remover?" If you dont mind the "ducking" v4a does or if it doesnt happen or your device then you'll want to select yes here.
- " Would you like to skip usb policy patching for usb dacs?" If you dont use a USB extrenal DAC and v4a then you can select yes here.
- " - Use lib workaround? -" If you arent having issues then you can select no here. Pixel 2's, 3's, and essential phones will have this selected as yes automatically.
Download
XDA:DevDB Information
Audio Compatibility Patch, Tool/Utility for the XDA Community Apps
Contributors
ahrion, zackptg5, JohnFawkes
Source Code: https://github.com/Magisk-Modules-Repo/acp
Version Information
Status: Stable
Current Stable Version: v2.3
Stable Release Date: 2020-11-10
Created 2017-03-21
Last Updated 2020-11-10

Update.
[UPDATE] Universal deep_buffer Remover <2.1>
v2.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6
Download: Link - Mirror
Previous Changelogs (Unified installer):
HTML:
v2.0:
- Initial Magisk release
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support

Prepare for a new update to AudModLib.

[UPDATED] Universal deep_buffer Remover
v2.2:
- Added audmodlib.sh post-fs-data.d script
- Install script fixes
- post-fs-data.d script fixes
- Push AudModLib v1.2 hotfixes
Download
Previous Changelogs (Universal deep_buffer Remover):
HTML:
v2.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6
v2.0:
- Initial Magisk release
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support
[UPDATED] Universal deep_buffer Restorer
Reverts the changes made from the Universal deep_buffer Remover.
v2.1:
- Script fixes
Download
Previous Changelogs (Universal deep_buffer Restorer):
HTML:
v2.0:
- Initial Magisk release
- Unified uninstaller that will uninstall the mod for both Magisk and System installs
- Pixel support included
- Magisk Template v3 support

Will this affect safteynet ?

SyCoREAPER said:
Will this affect safteynet ?
Click to expand...
Click to collapse
That's the point of it being a magisk module buddy...

SyCoREAPER said:
Will this affect safteynet ?
Click to expand...
Click to collapse
DroneDoom said:
That's the point of it being a magisk module buddy...
Click to expand...
Click to collapse
Lol.
Also it makes for easy module management and uninstall/install/updating.

ahrion said:
Lol.
Also it makes for easy module management and uninstall/install/updating.
Click to expand...
Click to collapse
I found that with v2.2, deep_buffer wasn't actually being removed for me.
Culprit:
Code:
sed -i '/deep_buffer {/,/}/d' $CFG
Should be:
Code:
sed -i '/deep_buffer {/,/}/ d' $CFG
I changed that in the update-binary and su.d script and deep buffer was then removed. I uploaded a copy with these changes. Thanks!

Zackptg5 said:
I found that with v2.2, deep_buffer wasn't actually being removed for me.
Culprit:
Should be:
I changed that in the update-binary and su.d script and deep buffer was then removed. I uploaded a copy with these changes. Thanks!
Click to expand...
Click to collapse
That's because whoever added the deep buffer section of your config had a typo.
These patches aren't 100% fool proof to incompetent coders or ROM developers.

Zackptg5 said:
I found that with v2.2, deep_buffer wasn't actually being removed for me.
Culprit:
Code:
sed -i '/deep_buffer {/,/}/d' $CFG
Should be:
Code:
sed -i '/deep_buffer {/,/}/ d' $CFG
I changed that in the update-binary and su.d script and deep buffer was then removed. I uploaded a copy with these changes. Thanks!
Click to expand...
Click to collapse
As I told you earlier, the space between "/ d" is an issue with your particular config file. This is not a sed issue or a typo in my scripts. sed is my specialty. This is the reason why it doesn't work.
I will not be changing it. However I thank you man for being proactive in trying to find alternative solutions.

How to uninstall ur module via recovery?
Hi bro i flashed ur module and after the reboot i cant find root... Even after flashing supersu systemless zip again.. Still no root. Bcoz of no root i cant uninstall ur module from magisk manager. Need ur help plz

umeshbluezzz said:
Hi bro i flashed ur module and after the reboot i cant find root... Even after flashing supersu systemless zip again.. Still no root. Bcoz of no root i cant uninstall ur module from magisk manager. Need ur help plz
Click to expand...
Click to collapse
Go here and scroll down to "Module causing issues":
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828/

So I've used your module, and it works great now, but my safetynet failed. Is this supposed to happen?

S4G4R said:
So I've used your module, and it works great now, but my safetynet failed. Is this supposed to happen?
Click to expand...
Click to collapse
Sometimes Magisk Hide doesn't restart properly on a reboot, especially after installing a new module. Try toggling Hide off and on again in settings.

Didgeridoohan said:
Sometimes Magisk Hide doesn't restart properly on a reboot, especially after installing a new module. Try toggling Hide off and on again in settings.
Click to expand...
Click to collapse
Worked! Thanks.

Good news guys. I finally found a fix for AM3D and Dolby Atmos to work 100% in enforcing on both MagiskSU/SuperSU, Magisk OR System install.
This will be available in the AudModLib v1.3 update I will be pushing soon. I'll obviously fix any more bugs or make any other additions in the meantime.

where are the Deep buffer entries located at?

ahrion said:
Good news guys. I finally found a fix for AM3D and Dolby Atmos to work 100% in enforcing on both MagiskSU/SuperSU, Magisk OR System install.
This will be available in the AudModLib v1.3 update I will be pushing soon. I'll obviously fix any more bugs or make any other additions in the meantime.
Click to expand...
Click to collapse
Hey I love your Magisk modules. Do you have a Dolby Digital Plus Magisk Module too? Thanks.

ELoTRIX said:
Hey I love your Magisk modules. Do you have a Dolby Digital Plus Magisk Module too? Thanks.
Click to expand...
Click to collapse
Check out his collective dolby thread in his signature

Installing this module on OP3 stock 7.1.1 rom break data connection
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

[Magisk][Module] Xperia Z2 / Z3 / Z3c Torch Boost v1.2

Here I present you my first Magisk module.
Description:
It boosts the torch on SONY Xperia Z2 / Z3 / Z3c devices by replacing system/etc/flashled_calc_parameters.cfg with a file that sets if_torch_vr = 500000 instead of just 25000, which is the default value by SONY.
By doing this, the flash LED is operated at 500 mA instead of just 25 mA.
In my experiences, 500 mA is a sweet spot which provides good brightness, but at the same time doesn't heat the LED too much. Still, I would advice you to not use the torch for more than about 5 minutes at a time. You use this module at your own risk. If you want to set a lower brightness, then you can edit system/etc/flashled_calc_parameters.cfg in the zip and change if_torch_vr to a value lower than 500000 before installing the module. Of course you can also use a higher value, but I wouldn't exceed 1000000 (this is also the value that SONY set in the line # Max current for Torch (uA) i_batt_max_torch of the flashled_calc_parameters.cfg file.)
Background:
The method I used was first described in a thread by @olokos which you can find here. For comparison: The extreme version you can download there (which is a flashable zip and not a Magisk module obviously) sets if_torch_vr to 1000000, which corresponds to 1000 mA or 1 A. As users reported, even at this setting the torch can be used for 5 minutes before temperature increases significantly, but I want to keep it safe by using just half of that value. If you want to know more about the user experience with different settings, I recommend you to read the above mentioned thread, as well as @antkalaitzakis96's thread, who uses the same method, which you can find here.
Compatibility:
This module should work on any SONY Xperia Z2 / Z3 / Z3c device running on Android 5.0 - 8.1.0, rooted with Magisk. I'm quite sure about this since I compared the flashled_calc_parameters.cfg files from Android 4.4 (SONY stock KitKat ROM) with Android 6.0.1 (SONY stock Marshmallow ROM) and also with Android 7.1.2 (LineageOS and Carbon Nougat ROMs) and the files were always completely identical! If you still want to check if the module will be compatible with your system before installing it, grab system/etc/flashled_calc_parameters.cfg from your system by using a root file explorer and then compare it with the flashled_calc_parameters.cfg file from the module zip file. The only difference between the two files should be the if_torch_vr line.
Enjoy!
Please leave some feedback if the module works for you.
Thanks:
Many thanks to @topjohnwu for the ingenious Magisk universal systemless interface and to @olokos for the initial torch boost mod.
Changelog:
v1.0 - Initial release
v1.1 - Updated to Magisk Module Template 1500
v1.2 - On Oct 26, 2020 @t.Lancer published an updated version in post #25 which works on newer Magisk versions. Thanks a lot!

Needed this. Thank you so much.

I love this module, I always wondered why my light was dinner than everyone else's. My light cuts through the darkness now!

Hi okij, I've used your module a bit reduced. Good work! Now there is the stock camera and I believe that the flash light so not in the camera settings is considered?The images are over-exposed in the close range. Once the module has been deactivated. Perhaps the setting can be automated to take pictures?

bussi2010 said:
Now there is the stock camera and I believe that the flash light so not in the camera settings is considered?The images are over-exposed in the close range. Once the module has been deactivated. Perhaps the setting can be automated to take pictures?
Click to expand...
Click to collapse
The module only changes if_torch_vr (comment line: "# LED If setting for Torch or video recording (uA)"), so it just affects the brightness when using the torch or when using the flash LED as a lamp when doing a video recording (which is good, because you have a brighter video lamp).
On the other hand, flash brightness is controlled by max_if_flash (comment line: "# Flash LED_If max current (uA)") which is set to 1500000 by default and not altered by the module. Therefore the module doesn't change anything when taking pictures.

Anybody having problems to install this module on Magisk 13.3? When I go to MODULES, select it and install, Magisk app freezes and I have to restart my phone. After that, I cannot open Magisk app anymore. I have to completely uinstall it and install again to be able to open the app again. On Magisk 12 it was working perfectly.

@maecar: The Problem is not Magisk 13.3, but Magisk Manager 5.1.0. There are numerous reports on the last few pages of the Magisk Support thread about the freezing issue. Until @topjohnwu fixes it, reverting to Magisk Manager 5.0.6 helps.

Mind making modulesl universal for Xperias...
Thanks... I use Z5!

Thanks for proper credit mate, nice work

olokos said:
Thanks for proper credit mate, nice work
Click to expand...
Click to collapse
I have to thank you and @AndroPlus for the initial MOD! I've been happily using it since about 2 years, but of course always had to re-apply it when updating a ROM. Now with Magisk, we can just "set and forget".

Is 500,000 secure?

SALL666PL said:
Is 500,000 secure?
Click to expand...
Click to collapse
IMHO it is.
This mod is known for about 2 1/2 years by now (long before my Magisk implementation) and I haven't read of any user who damaged his phone by using it.
Anyway, as I wrote in the OP, I would advice to not use the torch for more than about 5 minutes at a time, just to go safe.

okij said:
IMHO it is.
This mod is known for about 2 1/2 years by now (long before my Magisk implementation) and I haven't read of any user who damaged his phone by using it.
Anyway, as I wrote in the OP, I would advice to not use the torch for more than about 5 minutes at a time, just to go safe.
Click to expand...
Click to collapse
Thanks for the answer

Hello. This module didn't work for me. I tried to install it via Magisk and TWRP, but I get '' installation failed'' in Magsik and two red ''ERROR'' in TWRP. Do you know how to fix it?

DARKBUB said:
Hello. This module didn't work for me. I tried to install it via Magisk and TWRP, but I get '' installation failed'' in Magsik and two red ''ERROR'' in TWRP. Do you know how to fix it?
Click to expand...
Click to collapse
Since you don't provide any logs (installation or recovery) it's impossible to know for sure.
But, a likely issue is that this module is old and hasn't been updated for later versions of Magisk. If you're on Magisk v14+, this module won't install...

DARKBUB said:
Hello. This module didn't work for me. I tried to install it via Magisk and TWRP, but I get '' installation failed'' in Magsik and two red ''ERROR'' in TWRP. Do you know how to fix it?
Click to expand...
Click to collapse
Didgeridoohan said:
Since you don't provide any logs (installation or recovery) it's impossible to know for sure.
But, a likely issue is that this module is old and hasn't been updated for later versions of Magisk. If you're on Magisk v14+, this module won't install...
Click to expand...
Click to collapse
Yes, @Didgeridoohan is right, the module used an old template. I didn't notice that it doesn't install correctly anymore on newer Magisk versions because I only installed it once and then just updated Magisk to each newer version, which always kept the module installed.
I now updated the module to v1.1 which uses the current Magisk Module Template 1500. You can find the download in the updated OP.
Xperia Z2 / Z3 / Z3c Torch Boost v1.1 installed well on my Z3 Compact, running on Magisk v16.
Please leave a note if it works for you too now.

okij said:
Here I present you my first Magisk module.
Description:
It boosts the torch on SONY Xperia Z2 / Z3 / Z3c devices by replacing system/etc/flashled_calc_parameters.cfg with a file that sets if_torch_vr = 500000 instead of just 25000, which is the default value by SONY.
By doing this, the flash LED is operated at 500 mA instead of just 25 mA.
In my experiences, 500 mA is a sweet spot which provides good brightness, but at the same time doesn't heat the LED too much. Still, I would advice you to not use the torch for more than about 5 minutes at a time. You use this module at your own risk. If you want to set a lower brightness, then you can edit system/etc/flashled_calc_parameters.cfg in the zip and change if_torch_vr to a value lower than 500000 before installing the module. Of course you can also use a higher value, but I wouldn't exceed 1000000 (this is also the value that SONY set in the line # Max current for Torch (uA) i_batt_max_torch of the flashled_calc_parameters.cfg file.)
Background:
The method I used was first described in a thread by @olokos which you can find here. For comparison: The extreme version you can download there (which is a flashable zip and not a Magisk module obviously) sets if_torch_vr to 1000000, which corresponds to 1000 mA or 1 A. As users reported, even at this setting the torch can be used for 5 minutes before temperature increases significantly, but I want to keep it safe by using just half of that value. If you want to know more about the user experience with different settings, I recommend you to read the above mentioned thread, as well as @antkalaitzakis96's thread, who uses the same method, which you can find here.
Compatibility:
This module should work on any SONY Xperia Z2 / Z3 / Z3c device running on Android 5.0 - 8.1.0, rooted with Magisk. I'm quite sure about this since I compared the flashled_calc_parameters.cfg files from Android 4.4 (SONY stock KitKat ROM) with Android 6.0.1 (SONY stock Marshmallow ROM) and also with Android 7.1.2 (LineageOS and Carbon Nougat ROMs) and the files were always completely identical! If you still want to check if the module will be compatible with your system before installing it, grab system/etc/flashled_calc_parameters.cfg from your system by using a root file explorer and then compare it with the flashled_calc_parameters.cfg file from the module zip file. The only difference between the two files should be the if_torch_vr line.
Enjoy!
Please leave some feedback if the module works for you.
Thanks:
Many thanks to @topjohnwu for the ingenious Magisk universal systemless interface and to @olokos for the initial torch boost mod.
Changelog:
v1.0 - Initial release
v1.1 - Updated to Magisk Module Template 1500
Click to expand...
Click to collapse
Hey there. I've just replaced values in flashled_calc_parameters.cfg as it's written (25000 changed to 500000) using root explorer and then rebooted my phone. It worked our too! Btw, I'm running CarbonROM 8.1 rooted with SuperSU.

@okij Hi, could u make it working with Magisk V18 and newest template + Android 9.0? But i tried searching that file and it isnt here?

Bartekreaper said:
@okij Hi, could u make it working with Magisk V18 and newest template + Android 9.0? But i tried searching that file and it isnt here?
Click to expand...
Click to collapse
I didn't try Android 9 CarbonROM yet and most likely won't use it for the next couple of weeks since I need my Z3c as my daily driver and the ROM must be reasonably stable and bug-free.
Are you saying that flashled_calc_parameters.cfg isn't in folder system/etc/ anymore on Android 9?
The Torch Boost Magisk Module v1.1 still works fine with Magisk v18.0 under Android 8.1, so currently there's no need to update to the newest template.

okij said:
I didn't try Android 9 CarbonROM yet and most likely won't use it for the next couple of weeks since I need my Z3c as my daily driver and the ROM must be reasonably stable and bug-free.
Click to expand...
Click to collapse
I'm using the latest version of CarbonROM on my Z3C and the module works fine.

[ROM][9.0][N935F]Project Pixel 1.0[27/7/19]

Project Pixel P 1.0​
What is Project Pixel?​
Project Pixel is a small team of developers that work on porting most, if not all of the Google Pixel features to stock firmwares.
We mostly specialize in Stock Samsung Firmwares, although we may do work on ports of OneUI once in a while. Our objective is to deliver the best performance by using stock firmware whilst also improving upon it by debloating and tweaking whilst also giving you all the features of a Pixel device.
Pixel Pie 1.0 Feature List:​1. AdAway
2. Deep Debloat and DeKnoxed (Apps, permissions, framework, unnecessary features-stripped and removed)
3. Dolby Atmos with Correct Tuning and Gain (Main Speaker has most power and Earpiece just adds detail and treble)
4. Eleven Music (Lineage OS 15.1)
5. Files GO (File Manager)
6. GCam (Note: GCam might not work on all devices, because of hardware compatibility) v6.3
7. Google Calculator
8. Google Calendar
9. Google Chrome
10. Google Clock
11. Google Contacts
12. Google Keep (With Handwriting Libs)
13. Google Lens (Works within Google Photos and Recents in Pixel Launcher)
14. Google Messages
15. GPay (Working Payment Method along with NFC functionality)
16. Google Phone
17. Google Pie Emojis (Not Samsung Ones)
18. Google Play Games
19. Google Tasks
20. GBoard
21. Mtweaks (Has Hardware Control - Similar to Kernel Adiutor but more tailored to Exynos)
22. Pixel Fonts
23. Pixel 3 Boot Animation
24. Pixel 3 Live Wallpapers with Normal Wallpapers
25. Pixel Google Photos (Free Original Quality Storage)
26. Pixel Module V1 - Pixel Animations, framework and configs.
27. Pixel Launcher with new recent menu
28. Pixel Sounds
29. Samsung Digital Wellbeing
30. Samsung App Lock
31. Samsung Gallery (Stripped Down and lightened to improve performance)
32. Samsung's Stock Camera with HDR parameter changes, debloated and additional video modes (4k30 at HDR- Not Fully Tested)
33. SystemUI Tuner (Provides battery stats along with other useful customiztions - Check QS icons and add it to QS Panel to view)
34. VoLTE Supported
35. YouTube Vanced (Ad-free Youtube)​
CHANGELOG 1.0
Initial Release
Bugs:
ROM will not boot without Magisk.
Notes:
1. To view Battery Stats and Storage, pull down the Quick Settings Panel and on the top right click the three bubbles button and then Button Order. Then move the new Battery and Storage icon to the Quick Settings.
2. Make sure you set Google Phone as your default phone app. Go-to Settings/Apps. Click the three dots in the top right corner. Then click default apps. Then Calling App and select Phone.
3. After first boot, reboot your device once to ensure dalvik optimization.
INSTALL INSTRUCTIONS:
1. Download the zip and the latest Magisk.
2. Wipe System, Data, Dalvik Cache and Cache
3. Flash the zip and then flash Magisk.
Download Link and Sources:
Feel free to join us telegram via the group: https://t.me/joinchat/G-BflEMjGlgp1NeWxDA2bA
Download Link 1.0 :https://drive.google.com/file/d/14j_RVzN2ZmJuxeZElwsMmtkbCuZB5z8V/view
Magisk:https://github.com/topjohnwu/Magisk/releases
Kernel Source: source.samsung.com
Credits:
Google for Android and Framework
Samsung For Their Kernel
Check the screenshots tab to see screenshots of the ROM in action.
XDA:DevDB Information
Project Pixel P, ROM for the Samsung Galaxy Note FE
Contributors
Visera, Skulldron
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Bootloader & Modem
Based On: OneUI
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-07-27
Created 2019-07-27
Last Updated 2019-07-26

Reserved
Hey guys, some things:
1) Read the first post if you don't know how to fix the dialer problem. I get this a lot.
2) This is the new version of Team Pixel, so the old thread will re-start here.
3) The rom currently doesn't boot when you don't flash Magisk. It's something with the stock rom, so flash Magisk after you flash the rom.

Looks good among the two other ROMs for Note FE which I see many people complain about them!
Can anybody confirm if from experience it's better than stock or not?

Is it same as the previous PIXEL PIE-1 or new update?

fahad0000 said:
Is it same as the previous PIXEL PIE-1 or new update?
Click to expand...
Click to collapse
New

Some feedbacks for this rom are Screen Off Memo and write on screen features are not working. Beside that everything is fantastic. This rom gives me the most stable mobile network and signal amongst the others and I didn't have to reset and manually set my network in order to receive and make calls like other roms, they all shared the same problem from stock to custom except this one

which gcam 6.3 version works with Note FE exynos pie?
I thought only gcam 5.1 is stable, 6.1 and 6.2 are full of bugs/crash

I'm having problems figuring out how to get root access on this ROM.
- I've unlocked Developer options (there seems to be nothing in there).
- I've installed SuperSU from the App store. It doesn't see root.
- I've tried the root method from the base installer; installing the TWRP Hack from Download mode. No luck.
- I've tried installing SuperSU from TWRP. That causes the system to boot loop.
- I've tried updating Magisk. That causes the system to boot loop.
I feel like there is something super simple I am missing.

Hello. Is this tested on bootloader v5?

viper001 said:
Hello. Is this tested on bootloader v5?
Click to expand...
Click to collapse
I'm using the bootloader from this thread:
https://forum.xda-developers.com/note-fe/how-to/sm-n935f-ds-how-to-flash-twrp-root-t3733030
I can confirm that works. That one is Bootloader v5.
I should state that the only version of Magisk that works from what I've found is the one in this thread. Newer versions cause bootloops.

LighthammerX said:
I'm having problems figuring out how to get root access on this ROM.
- I've unlocked Developer options (there seems to be nothing in there).
- I've installed SuperSU from the App store. It doesn't see root.
- I've tried the root method from the base installer; installing the TWRP Hack from Download mode. No luck.
- I've tried installing SuperSU from TWRP. That causes the system to boot loop.
- I've tried updating Magisk. That causes the system to boot loop.
I feel like there is something super simple I am missing.
Click to expand...
Click to collapse
You flash Magisk? SuperSU doesn't work anymore afaik.

viper001 said:
Hello. Is this tested on bootloader v5?
Click to expand...
Click to collapse
Skulldron said:
You flash Magisk? SuperSU doesn't work anymore afaik.
Click to expand...
Click to collapse
I actually planned on getting back to this. Thanks for the followup.
The resolution was this:
- I flashed the Magisk link in this thread and then the most current Magisk app.
This was seemingly the problem but I don't exactly know why.
The fix was to make sure I had the most current Magisk app and Magisk flashed.

Rom is buttery smooth even without Magisk. (used the TWRP patch by RicePlay after installing the rom then it started to boot afterward).
Here's a couple of snapshots:
What I did to install this was:
1) Download the ROM image and the TWRP patch
2) Format/clear system, data, cache, etc..
3) Install ROM image
4) Wipe dalvik
5) Install TWRP patch
6) Wipe Dalvik
7) Reboot to System
Optional step for root access:
8) Install Magisk Canary (debug)
I'm not sure if anyone else has experienced this but we cannot disable the core-only mode once Magisk 19.3 is installed. I even tried toggling off the core only mode via Magisk Manager module via TWRP Terminal yet to no avail after a restart.

Bình said:
Some feedbacks for this rom are Screen Off Memo and write on screen features are not working. Beside that everything is fantastic. This rom gives me the most stable mobile network and signal amongst the others and I didn't have to reset and manually set my network in order to receive and make calls like other roms, they all shared the same problem from stock to custom except this one
Click to expand...
Click to collapse
Install Samsung Notes and you'll be good.

Logcat for bugged Magisk core only mode
I have sent a logcat to the Magisk Canary Debug thread and the latest build(19.4-f383d11d) did not fix the core only mode issue. Kindly refer to this post on the thread for the logcat. I hope a fix can be done on it but other than that, this is a great custom rom

How's the CSC selection or setup on this rom? Been wanting to use my NoteFE for awhile (wanted stock) but can't get my sim settings to stay after reboot (aka just reboots into twrp and doesn't complete) so figured I'd try custom rom

Ok so CSC stuff I answered on my own.
Was curious if anyone having trouble with the CTS profile showing false under the securitynet check? ( Aka want to know if I'm wasting my time trying to figure out how to fix it)

Thank Visera,
"]https://i.imgur.com/FBKKg4h.jpg[/IMG]
"]https://i.imgur.com/oz59lbF.jpg[/IMG]
"]https://i.imgur.com/oU9ZGun.jpg[/IMG]
Hơi thất vọng về Rom. Bản rom này chỉ là một bản SamsungRom được tùy chỉnh lại. Tôi cứ cho rằng là GoogleRom tùy chỉnh lại. Tôi dùng trải nghiệm thì thấy nó chỉ có Launcher giống Google.
A little disappointed about Rom. This rom is just a customized SamsungRom version. I keep claiming that GoogleRom customizes. I used the experience and found it only has Launcher like Google.
:good::good::good::good::good::good:

Is it a bug? Even If I full wiped, I can't get the google login screen at the first boot so that I can't recover my back up data.

cannot place regular voice calls, and theres no incoming call answer or reject menu, the phone just ringing.
is something wrong with the dialer? or just me.

Oxygen OS port for Redmi note 7 (Lavender) (Android 10)

Hello, Today I sucessfully port Oxygen OS from OnePlus 6T (ErfanGSIs) for this beautyfull device.
Its based on Android 10 with preinstalled Magisk(because Magisk help me fixing some stuff).
Its Fox/Twrp recovery backup and have over 5GB.(download size is 1.7gb because not every one have fast internet)
Its running on MengT kernel R1.8.0.
What works:
everything except : WiFi display (Not tested yet because I forgot set in overlay "<bool name="wifi_display_enable">true<bool/>" )
Bluetooth Audio (bluetooth works but if you connect headphones or bt speaker audio not work)
Always On Display (just black screen without clock or battery percentage)
Included Apps: Open Camera, YT, Gmail, Google photos, OnePlus Aplications, and some other stuff....
Some Answers for recently asked questions:
Magisk need sets up please download......... just ignore it click cancel and you get fully working super user
Module did not installed update magisk...... Magisk version is 19.3 because this is only version to make bootable this port.
Open Camera has not permissions..... you must update from Play Store.
If some oneplus apps didnt open or open not correctly you must set theme to colorfull (because overlays)
If you want dark mode set theme colorfull and then go to developer options to enable "override-dark mode".
WARNING
DO NOT UPDATE MAGISK because you get bootloop OR update if you known some working versions on erfan GSIs(and please share me).
Credits : https://forum.xda-developers.com/member.php?u=6298645
https://forum.xda-developers.com/member.php?u=8704698
Download Link: https://mega.nz/folder/hvwgXY7b#Jqr0_3ry5quNtFj81h0B4w

Samuel Ladziansky said:
Hello, Today I sucessfully port Oxygen OS from OnePlus 6T (ErfanGSIs) for this beautyfull device.
Its based on Android 10 with preinstalled Magisk(because Magisk help me fixing some stuff).
Its Fox/Twrp recovery backup and have over 5GB.(download size is 1.7gb because not every one have fast internet)
Its running on MengT kernel R1.8.0.
What works:
everything except : WiFi display (Not tested yet because I forgot set in overlay "<bool name="wifi_display_enable">true<bool/>" )
Bluetooth Audio (bluetooth works but if you connect headphones or bt speaker audio not work)
Always On Display (just black screen without clock or battery percentage)
Included Apps: Open Camera, YT, Gmail, Google photos, OnePlus Aplications, and some other stuff....
Some Answers for recently asked questions:
Magisk need sets up please download......... just ignore it click cancel and you get fully working super user
Module did not installed update magisk...... Magisk version is 19.3 because this is only version to make bootable this port.
Open Camera has not permissions..... you must update from Play Store.
If some oneplus apps didnt open or open not correctly you must set theme to colorfull (because overlays)
If you want dark mode set theme colorfull and then go to developer options to enable "override-dark mode".
WARNING
DO NOT UPDATE MAGISK because you get bootloop OR update if you known some working versions on erfan GSIs(and please share me).
Credits : https://forum.xda-developers.com/member.php?u=6298645
https://forum.xda-developers.com/member.php?u=8704698
Download Link: https://cb.run/35z0
Click to expand...
Click to collapse
Do you have any screen shot?

KackBarton said:
Do you have any screen shot?
Click to expand...
Click to collapse
well i didnt but I go make it plz wait (I must restore this port because i reflashed stock miui because iam using bt headphones every day but on this rom is not work:crying

DO NOT USE its seems to be
well after restoring I have rescue party i try to fix it
well I Fix It, there is the problem In firmware version I upload files on to mega.nz

Update V1.0 + screen shots
Information about this rom update:
:MTP not working (Only PTP)
:lockscreen camera shortcut didnt wok because there is not OnePlus camera
:FaceUnlock didnt work
:in this rom is my own port of stock xiaomi music
:all these overlays and fixes are edited by apk editor pro v1.9.6
how to flash :
open download link (its mega.nz)
open folder "10"
download folder cust,persist,tz patch for OxygenOs
after that download the recovery backup OxygenOs_lavender_Q***********.zip
format system vendor data
flash tz.mbn.img
flash cust.img
flash persist.img
after that put the backup of the rom in to /"internal storage or sdcard"/"Fox or TWRP"/BACKUPS/"serial number"/
restore the backup
wipe cache/dalvik
reboot
frirst boot is litle bit longer
after that setup your device and all of the stuff
there are some screenshots

Samuel Ladziansky said:
Hello, Today I sucessfully port Oxygen OS from OnePlus 6T (ErfanGSIs) for this beautyfull device.
Its based on Android 10 with preinstalled Magisk(because Magisk help me fixing some stuff).
Its Fox/Twrp recovery backup and have over 5GB.(download size is 1.7gb because not every one have fast internet)
Its running on MengT kernel R1.8.0.
What works:
everything except : WiFi display (Not tested yet because I forgot set in overlay "<bool name="wifi_display_enable">true<bool/>" )
Bluetooth Audio (bluetooth works but if you connect headphones or bt speaker audio not work)
Always On Display (just black screen without clock or battery percentage)
Included Apps: Open Camera, YT, Gmail, Google photos, OnePlus Aplications, and some other stuff....
Some Answers for recently asked questions:
Magisk need sets up please download......... just ignore it click cancel and you get fully working super user
Module did not installed update magisk...... Magisk version is 19.3 because this is only version to make bootable this port.
Open Camera has not permissions..... you must update from Play Store.
If some oneplus apps didnt open or open not correctly you must set theme to colorfull (because overlays)
If you want dark mode set theme colorfull and then go to developer options to enable "override-dark mode".
WARNING
DO NOT UPDATE MAGISK because you get bootloop OR update if you known some working versions on erfan GSIs(and please share me).
Credits : https://forum.xda-developers.com/member.php?u=6298645
https://forum.xda-developers.com/member.php?u=8704698
Download Link: https://mega.nz/folder/hvwgXY7b#Jqr0_3ry5quNtFj81h0B4w
Click to expand...
Click to collapse
I'm using this port from another developer much more stable

LEANDROMENDES said:
I'm using this port from another developer much more stable
Click to expand...
Click to collapse
Interesting

Samuel Ladziansky said:
Interesting
Click to expand...
Click to collapse
Is tour ROM prerooted? Is there any update in future?

KackBarton said:
Is tour ROM prerooted? Is there any update in future?
Click to expand...
Click to collapse
I'm sorry to answer so late. This rom is prerooted and updates are not planned.

there is update for magisk : https://mega.nz/file/AvgS2aKD#hDRhaCEgAIgDsAxlq3Q4PIRnqcIRingCSow8gUc861M
version 21.4

I think you should make a flashable zip out of this gsi, it's way more efficient to flash than a backup

In rooted os UPI apps does not work.
Please confirm , Is this ROM pre rooted for sure?

testingpatiala2 said:
In rooted os UPI apps does not work.
Please confirm , Is this ROM pre rooted for sure?
Click to expand...
Click to collapse
Yes is rooted via magisk, and what is UPI apps? Because I didnt heard about it.

LineageOS 17.1 Magisk Garage !

Hi there,
This is a dedicated thread for LineageOS 17.1 where i will upload my Magisk modules !
Use Magisk Manager to install/remove the provided .zip modules (Recommended)
(You can install via TWRP too, but don't make any space if you change the .zip name, otherwise the installation will fail ...)
Enjoy !

Tell us a little about what each module is for!

veloz46 said:
Tell us a little about what each module is for!
Click to expand...
Click to collapse
it's inside the module itself !

veloz46 said:
Tell us a little about what each module is for!
Click to expand...
Click to collapse
Yes a small review, why not? Please!!!

here

Great contribution, @janhammer504
The following questions come to mind:
Call Recorder: I guess this module is device independent, as long as the LOS Dialer is used?
Google Sans: What difference does it make installing these fonts and where do you see them?
Notch Hide: So does this actually revert "has_notch" already set in the ROM and what's the purpose (I mean, having a punch hole may imply trying to prevent any content to be shown in that area)?

Master One said:
Great contribution, @janhammer504
The following questions come to mind:
Call Recorder: I guess this module is device independent, as long as the LOS Dialer is used?
Google Sans: What difference does it make installing these fonts and where do you see them?
Notch Hide: So does this actually revert "has_notch" already set in the ROM and what's the purpose (I mean, having a punch hole may imply trying to prevent any content to be shown in that area)?
Click to expand...
Click to collapse
1. Call Recorder is for LineageOS Dialer only (as mentioned in the module description)
2. Look to the screenshot to see the difference (these are the original fonts used in pixel devices)
3. This is an overlay to hide the notch (developer options : type cutout there to see where to apply) : useful for Netflix, YouTube, Gaming ... etc

Notch Hide / Update :
change the internal package name and use the official one !
How to enable :
developer Options > type display cutout
if not working : delete with TWRP or RootExplorer this folder ... and reboot !
/data/system/package_cache

Would be great to have more individual font modules. And system sounds. Preferably without loosing the default ones. Just sayin'...

Thank you for all your effort. This will be very usefull after official. Specially for some stuff... that will have to be removed

gardiol said:
Thank you for all your effort. This will be very usefull after official. Specially for some stuff... that will have to be removed
Click to expand...
Click to collapse
Which is?

Safetynet Fix added ... Enjoy !
All credits go to Didgeridoohan from Magisk Subforum !

janhammer504 said:
Safetynet Fix added ... Enjoy !
All credits go to tenow from Magisk Subforum !
Click to expand...
Click to collapse
Thanks! Is it possible to flash zip file via recovery or is it necessary to install magisk?

Shermo1208 said:
Thanks! Is it possible to flash zip file via recovery or is it necessary to install magisk?
Click to expand...
Click to collapse
yes you can copy-past the files in the system ... but how are you going to do that without ROOTING ???

janhammer504 said:
yes you can copy-past the files in the system ... but how are you going to do that without ROOTING ???
Click to expand...
Click to collapse
Flashing zip file with ofox recovery. Before ctsProfile problem I didn't have root and safety net passed without problem. Then, for the moment, I don't need root in my phone, therefore my question is if I can flash this zip file with ofox recovery. Thanks

Shermo1208 said:
Flashing zip file with ofox recovery. Before ctsProfile problem I didn't have root and safety net passed without problem. Then, for the moment, I don't need root in my phone, therefore my question is if I can flash this zip file with ofox recovery. Thanks
Click to expand...
Click to collapse
Magisk modules are stored to /data/adb/modules and mapped to /product/system/vendor/ ... without Magisk Root you can't load them !!!

janhammer504 said:
Magisk modules are stored to /data/adb/modules and mapped to /product/system/vendor/ ... without Magisk Root you can't load them !!!
Click to expand...
Click to collapse
Ok, thanks!!

any of you guys have tried installing ANX camera? because in my case I can't take any HDR pictures, wondering if it happens to anybody else.

FrameworkOverlay added :
. improve low brightness (new linear overlay) for more battery saving (works great)
. fix compatibility issue with chrome & webview (choose chrome as default system webiew in developer options to avoid yellow tint in chrome browser)
. add more color mode
. improve WiFi stability for both (2,4 & 5 GHz)
. update power_profile
. address some display glitches in some apps (related to the aspect ratio)
. many more things ....
I hope that @gardiol can merge this to the device three in the future !
edit : reuploaded here (XDA UI sucks again !!!)
update : fix some info in AndroidManifest

janhammer504 said:
FrameworkOverlay added :
. improve low brightness (new linear overlay) for more battery saving (works great)
. fix compatibility issue with chrome & webview (choose chrome as default system webiew in developer options to avoid yellow tint in chrome browser)
. add more color mode
. improve WiFi stability for both (2,4 & 5 GHz)
. update power_profile
. address some display glitches in some apps (related to the aspect ratio)
. many more things ....
I hope that @gardiol can merge this to the device three in the future !
edit : reuploaded here (XDA UI sucks again !!!)
update : fix some info in AndroidManifest
Click to expand...
Click to collapse
Already did... but you have to wait a few days before release.... because i want to test properly first.