Database Develop

please delete thread

Ainur JamesDSP is now available in Magisk Manager. Thanks to the devs for their great work. Enjoy!

Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)

biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
Yikes. I wonder if AML doesn't support Pixel yet. I will look into it and add a note to the OP. Thanks for the heads up.

biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
By the way, were you running any other audio mods at the time?

s8m said:
By the way, were you running any other audio mods at the time?
Click to expand...
Click to collapse
no

I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl

yung40oz84 said:
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
Click to expand...
Click to collapse
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.

s8m said:
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
Click to expand...
Click to collapse
Great! Looking forward to it.

When users provide logs...

I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.

ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users.
Click to expand...
Click to collapse
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.

s8m said:
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
Click to expand...
Click to collapse
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.

ahrion said:
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
Click to expand...
Click to collapse
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.

s8m said:
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
Click to expand...
Click to collapse
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Since you're looking from outside, in. Was Unity easy to configure for you? The entire point for AML is to link everything to together for Magisk. Then we created Unity to be an all in one installer. Any AML modules are encouraged and welcome. Ainur is running AML currently.

Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !

s8m said:
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
Click to expand...
Click to collapse
Awesome. You can thank @Zackptg5
Another addition is SETools-inject for Android, that functions like sepolicy inject that MagiskSU/SuperSU have. Essentially, it allows rootless and other forms of root to also use it via init.d. As of yet, no one has actually used SETools for this.
We've also added init.d patching, for rootless and other root methods. Essentially, ramdisk will be automatically patched for AML system modules to use init.d (even if your rom didn't support it before). So init.d patch for all Android versions, MM/N+, has been added. Currently nearly all (if not all) init.d support is broken.

ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
Click to expand...
Click to collapse
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.

24imelqui said:
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
Click to expand...
Click to collapse
It's not that he has been picky. It's just it takes some time to get approved.
Topjohnwu is a busy man.

BTW, Unity allows system mode installation natively if Magisk is not installed, includes addon..d as well.
Magisk is not required for any Unity zips.

ahrion said:
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Click to expand...
Click to collapse
It may be a dumb question, but does your Ainur JamesDSP module require Ainur or can it run independently without Ainur installed?

[MODULE][SD820/1|OP3/T + SD835/1|OP5] AKT Profiles for Magisk

AKT Profile for Magisk​
AKT Profile by Asiier & Senthil360 for Magisk in order to use service.sh(late_start).
Why?
I can't fully mount the /system partition and so /system/etc/init.d/99AKT is not editable.
The result is that at each boot/reboot I have to go through the whole procedure to apply the setting.
This module should make things easier: instead of rely on init.d, it uses the built-in function of magisk.
Profiles/Project Credits:
// Nameless by @Senthil360 | Fusion by @patalao | Burnout PR3 by @Mostafa Wael \ // Project Zhana & X.A.N.A by @Asiier | GhostPepper, HawkPepper and FairPark by @Asiier \
OP5 SupportMostafa Wael | @Funk Wizard
[AKT] Advanced Kernel Tweaks v1.0 For OP5 & S835 devices
I have just editet the /system/bin/AKT file to make it compatible with Magisk
Original Project:
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
Change Log
v1.0 - Initial release
v1.1 - Fixed apply profile on boot
v1.2 - OP5 Support + Magisk Template v15
Requeriment
Magisk 15.0
Installation
-Uninstall the original AKT package through terminal
-Download the module from the Download section below(different zip for SD835|OP5 and SD820/1|OP3/T)
-Flash the zip package from Magisk Mangaer and reboot
-Apply the desired profile like you do with the default package from the Terminal emulator:
Code:
su
AKT
Download:
SD820/1 | OP3/T: https://github.com/Razorphyn/AKT_Pr...2/AKT_Profiles_Magisk-1.2.SD820.821-OP3.T.zip
SD835 | OP5: https://github.com/Razorphyn/AKT_Pr...oad/1.2/AKT_Profiles_Magisk-1.2.SD835-OP5.zip
Source:
Repository: https://github.com/Razorphyn/AKT_Profiles_Magisk

cool, do i need to uninstall the original atk?

What's the advantages of this module over AKT app provided in AKT thread?

well i think this will apply auto at boot.
How i verify if profile is activated ?

gatalon said:
cool, do i need to uninstall the original atk?
Click to expand...
Click to collapse
I am not sure that magisk will overwrite the already exixtant bin file, so I would say yes.
Just remember to apply the profile once you have installed the module.
pinoholo said:
What's the advantages of this module over AKT app provided in AKT thread?
Click to expand...
Click to collapse
Theoretically:
-No files are added directly to/system
-Do not need additional mod to enable init.d and potentially break SafetyNet
Practically:
I am not able to mount /system in rw, but only ro, this means that I can't edit the file inside the init.d folder, especially 99AKT which stores the profile info to apply on boot.
Also the removal of the bin file is a pain(only through TWRP)
Basically what happens is that instead of editing
Code:
/system/etc/init.d(su.d)/99AKT
, this module save the profile to apply on boot in
Code:
/magisk/mymodule/post-fs-data.sh
mmm273 said:
well i think this will apply auto at boot.
How i verify if profile is activated ?
Click to expand...
Click to collapse
I have never thought about it, but in principle, from the Terminal you should see the active profile.
To be sure I think you need to check the real value with some app and compare them with the profile file.
Probably an easier way is to use an app that display the value(I think Kernel Auditor does this, you can check the CPU freq and other value) and compare those value with te profile enabled and the profile disabled(once you have rebooted)

Well because when I apply it (Zhana / XANA whatever it doesn't matter), swipe to appdrawer lags. When I restart phone it doesn't lags. So I suppose it's not activated auto?

mmm273 said:
Well because when I apply it (Zhana / XANA whatever it doesn't matter), swipe to appdrawer lags. When I restart phone it doesn't lags. So I suppose it's not activated auto?
Click to expand...
Click to collapse
You know why? Because it doesn't work, but I have fixed it: now the module runs the script at late_start instead of post-fs-data, the stage is NON-BLOCKING, it will run in parallel with other processes (by documentation)[Basically it can take "few" seconds to show the results]
I have just checked and it should works: it edits the files in /sys/ with the value of the selected profile.
I will be grateful if you can test it again.

Tried but don't know feel still same like not fully loaded.

mmm273 said:
Tried but don't know feel still same like not fully loaded.
Click to expand...
Click to collapse
I have done few more tests and it looks like the value shown in Kernel Adiutor corresponds to the one of the selected profile...have you applied the profile as a "fresh installation"(not the "Reapply" option)?

Yeah sure I deleted all AKT files and module. Restart phone. Apply your new module. Restart phone. In terminal selected profile. All seems slower but that's ok, restarted phone and yet it was smooth. When I applied it again, again it became slower.
Something isn't right there.

mmm273 said:
Yeah sure I deleted all AKT files and module. Restart phone. Apply your new module. Restart phone. In terminal selected profile. All seems slower but that's ok, restarted phone and yet it was smooth. When I applied it again, again it became slower.
Something isn't right there.
Click to expand...
Click to collapse
My two-cents is tat since the profile is applied during boot you don't feel any slowing down/adjustment of the performance.
I reality I'm not sure, because as I can see the values displayed by Kernel Adiutor(and by the relative involved files) are the same of the profile and they change respect the default one.
I don't know if Nougat behaves differently respect the previous OS or Magisk "init.d" does not process as the "real" one, I have just adapted the module, maybe someone that has more knowledge respect me can solve this doubt.
I would say that it works, however I think that the important thing is that you notice a battery/performance increase.
I am sorry I cannot help you more...but at least the module now doesn't put any file in /system directly...

Razorphyn said:
AKT Profile for Magisk​
AKT Profile by Asiier & Senthil360 for Magisk in order to use service.sh(late_start).
Why?
I can't fully mount the /system partition and so /system/etc/init.d/99AKT is not editable.
The result is that at each boot/reboot I have to go through the whole procedure to apply the setting.
This module should make things easier: instead of rely on init.d, it uses the built-in function of magisk.
Profiles/Project Credits:
// Nameless by @Senthil360 | Fusion by @patalao | Burnout PR3 by @Mostafa Wael \ // Project Zhana & X.A.N.A by @Asiier | GhostPepper, HawkPepper and FairPark by @Asiier \
I have just editet the /system/bin/AKT file to make it compatible with Magisk
Original Project:
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
Change Log
v1.0 - Initial release
v1.1 - Fixed apply profile on boot
Requeriment
Magisk 14.0
Installation
-Uninstall the original AKT package through terminal
-Download the module from the Download section below
-Flash the zip package from Magisk Mangaer and reboot
-Apply the desired profile like you do with the default package from the Terminal emulator:
Code:
su
AKT
Download:
Module: https://github.com/Razorphyn/AKT_Profiles_Magisk/files/1447769/AKT_Profiles_Magisk-1.1.zip
Source:
Repository: https://github.com/Razorphyn/AKT_Profiles_Magisk
Click to expand...
Click to collapse
can it be for Lenovo zuk z2 plus sd 820 device
will it work on that as well?????

Any chance of you doing this for the OP5 version, I have the 5T and AKT for 5 works well on it... Thanks.

It would be great if someone did this for the SD 835.

yung40oz84 said:
Any chance of you doing this for the OP5 version, I have the 5T and AKT for 5 works well on it... Thanks.
Click to expand...
Click to collapse
tech_head said:
It would be great if someone did this for the SD 835.
Click to expand...
Click to collapse
Sorry for the delay, I have adapted the code for OP5, but I am not able to test it. If you want to try, then let me know.

Razorphyn said:
Sorry for the delay, I have adapted the code for OP5, but I am not able to test it. If you want to try, then let me know.
Click to expand...
Click to collapse
I have the OP5T, it should work for that and I would be willing to test. Thanks bud!!! Just let me know and pass along the module, I will flash

I have an Essential. I'm willing to try it.
I have Magisk installed and I know how to back anything out if it doesn't work correctly.

tech_head said:
I have an Essential. I'm willing to try it.
I have Magisk installed and I know how to back anything out if it doesn't work correctly.
Click to expand...
Click to collapse
He said he adapted code for OP5, lol. U can try on Essential but it's a long shot.

yung40oz84 said:
I have the OP5T, it should work for that and I would be willing to test. Thanks bud!!! Just let me know and pass along the module, I will flash
Click to expand...
Click to collapse
I have misspoken, I have adapted the code and updated the first post, you can find the attached module at the end of it.

yung40oz84 said:
He said he adapted code for OP5, lol. U can try on Essential but it's a long shot.
Click to expand...
Click to collapse
tech_head said:
I have an Essential. I'm willing to try it.
I have Magisk installed and I know how to back anything out if it doesn't work correctly.
Click to expand...
Click to collapse
He is not fully wrong, it should support every SD835, but the result is not guaranteed.
Anyway, the module zip is attached at the edn of the first post, in principle nothing or irreparable should occurs

[MOD] Audio Modification Library v4.2

Audio Modification Library is a library of known audio mods. It'll search your magisk directory for any supported audio mods and incorporate them into itself. It's been completely redone to act as a standalone module so devs no longer need to worry about using a framework for their audio mods and users no longer are limited to just mods using that framework.
Some history
Originally, Unity Installer and AML were combined into one. That's what's archived on ahrions github.
Nowadays, unity is its own thing and AML was completely redesigned into what it is today. The whole purpose of aml is to combine the audio effect/policy/mixer/etc files from multiple audio mods into one set because only one copy of a file can be active mounted at any given time. With non-magisk installs, the actual copies of those audio files are all modified by various mods (aka they all work with the same copy) and so there's no need for aml
What is the purpose of this?
Audio mods often function in part by modifying some audio files (such as audio_effects, mixer_paths, etc.). The problem here is that each mod has it's own copy of the files and magisk can only mount 1 copy of each, so only 1 mod will completely work. AML functions by combining them all into one set of files to remedy this issue.
So how does it work?
It's now a standalone zip that is flashed once and forgetten about. It's magisk only for obvious reasons and will incorporate all supported audio mods into itself automatically during install, and then during each boot if any changes were detected. So it will adjust for any changes in audio mods such as new ones being installed, some being removed, or an existing one being updated.
Where the Mod is Located:
This is more of the nitty gritty for anyone interested but the aml specific copies of audio files and the mod itself are stored in the aml folder in the magisk directory like a typical module. However, it moves any detected audio files out of the folder of any audio mods so they won't be mounted by magisk and conflict. They're moved to .core/aml for safe keeping so they can be restored back to the mod later if you choose to uninstall aml or if upgrading aml
When do I flash this?
Unlike with older version of aml, order doesn't matter. However, it's best to flash aml FIRST. The reason for this is that an increasing number of audio mods look for aml and behave differently if it doesn't yet exist.
Troubleshooting:
If a mod didn't work before you flashed aml, it probably won't work after. Take up the issue on the mod's thread.
Otherwise, if a mod works before flashing aml and doesn't after: First, try uninstalling all audio mods and then reinstalling them (including aml). If that doesn't work, then I'll need you to make a post with this in it:
Recovery log after flashing AML
List of Audio Mods Installed
AML version last working on (if applicable)
Zip attachment of your aml magisk module (/data/adb/modules/aml) folder (note that there's a debug.log file in here that's shows everything)
Zip attachment of your aml backup folder (/data/adb/aml) folder
Currently Supported Mods:
AM3D
AudioWizard
V4AFX
V4AXhifi
Dolby Atmos (ahrion's ports)
Dolby Atmos Axon 7 Oreo (guitardedhero's port)
Dolby Digital Plus
Bang&Olufsen ICEPower (only tested ainur version)
Arkamys (only tested ainur version)
Dirac (only tested ainur version)
Dirac Hexagon (only tested ainur version)
JamesDSP
MaxX Audio 3
Audio Compatibility Patch (formerly universal deep_buffer remover)
Ainur Sauron
SquareSound
Sony Xperia Z2 Sound System
Ainur Narsil
Ainur DTSX
Ainur DTS Ultra
Dolby Atmos Pie/Q+ (guitardedhero's ports)
Want an audio mod added to AML?
Make a post about it and I'll see if it's eligible. No guarantees that I'll add it but these are things that it must have to even be considered:
Original/unique (so not a repackaging of other audio mods)
Universal(ish) (support a large number of devices - not specific to a handful of devices)
Patches files rather than replaces them (the whole point of aml is to be a collection of patches)
Patches must be static (won't be changing with each mod update)
Audio Mod Can't be Added to AML Directly? You can still add it in!
If it doesn't meet these requirements, you can still make it aml compatible.
You just need your mod to create a file called ".aml.sh" in the root of the mod directory ($MODPATH typically). It'll need to have the patches for your mod in a format that aml can understand:
For patching audio_effect files, AML includes a 'patch_cfgs' function that makes life much easier. So if you have an effect and library to add:
Code:
patch_cfgs <effect_name> <UUID> <library_name> <library_path>
For example:
Code:
patch_cfgs v4a_fx 41d3c987-e6cf-11e3-a88a-11aba5d5c51b v4a_standard_fx /vendor/lib/soundfx/libv4a_fx.so
Note that this patch_cfgs function is for audio effects files only. If you're patching audio policy or mixer_paths files, then you'll need to make the patches the old fashioned way yourself.
So if you're not patch audio effects files, skip on down to the 'Some other variables/options' section
'patch_cfgs' has several flags that can be used (the format followed by an example for each is listed here as well):
-l: patch library
Code:
patch_cfgs -l <library_name> <library_path>
Code:
patch_cfgs -l v4a_fx /vendor/lib/soundfx/libv4a_fx.so
-e: patch effect
Code:
patch_cfgs -e <effect_name> <UUID> <library_name>
Code:
patch_cfgs -e v4a_standard_fx 41d3c987-e6cf-11e3-a88a-11aba5d5c51b v4a_fx
-o: patch output_session_processing (postprocessing). Typically used with both 'l' and 'e' flags as well
Code:
patch_cfgs -ole <osp_section> <effect_name> <UUID> <library_name> <library_path>
Code:
patch_cfgs -ole music atmos 9d4921da-8225-4f29-aefa-aacb40a73593 atmos /vendor/lib/soundfx/libatmos.so
-q: patch pre_processing (preprocessing). Typically used with both 'l' and 'e' flags as well
Code:
patch_cfgs -qle <pp_section> <effect_name> <UUID> <library_name> <library_path>
Code:
patch_cfgs -qle music atmos 9d4921da-8225-4f29-aefa-aacb40a73593 atmos /vendor/lib/soundfx/libatmos.so
-p: patch proxy effect (note that since this is a special kind of effect, it cannot be used with '-e'). When used by itself
Code:
patch_cfgs -p <proxy_effect_name> <proxy_UUID> <sw_library_name> <sw_UUID> <hw_library_name> <hw_UUID>
Code:
patch_cfgs -p dax 9d4921da-8225-4f29-aefa-6e6f69726861 dax_sw 6ab06da4-c516-4611-8166-6168726e6f69 dax_hw a0c30891-8246-4aef-b8ad-696f6e726861
But it's typically used with 'l'
Code:
patch_cfgs -pl <proxy_effect_name> <proxy_UUID> <sw_library_name> <sw_UUID> <sw_library_path> <hw_library_name> <hw_UUID> <hw_library_path>
Code:
patch_cfgs -pl dax 9d4921da-8225-4f29-aefa-6e6f69726861 dax_sw 6ab06da4-c516-4611-8166-6168726e6f69 /vendor/lib/soundfx/libswdax.so dax_hw a0c30891-8246-4aef-b8ad-696f6e726861 /vendor/lib/soundfx/libhwdax.so
-r: replace. Normally, aml will only apply any of the above if it doesn't exist in the audio cfg file. With this flag enabled however, it'll replace any existing effects. It's pretty rare that this would be needed (none of the mods patches built-in to aml have this)
no flag specified: if no flags are specified, patch_cfgs will use -le by default (patch library and effect). This is what's typically used (like in the first example before this list)
For patching other files: just add you script logic like it it was in your mod.
If you're patching mixers for example:
Code:
for i in $(find $MODPATH/system -type f -name "*mixer_paths*.xml"); do
<add_patch_here> for mixer '$i'
done
MODPATH is equivalent to aml's directory since it's running the aml.sh script
Then when AML is installed, it'll detect this .aml.sh file and apply the patches accordingly
Source
Download

Awesome work! Excited to try it out. Will the usual AML mods such as ainur and v4a be updated or can I go ahead and test out with the current v2.9 zips?

nonchalantroller said:
Awesome work! Excited to try it out. Will the usual AML mods such as ainur and v4a be updated or can I go ahead and test out with the current v2.9 zips?
Click to expand...
Click to collapse
Just finished updating everything. Usual aml mods are now unity mods so you don't even need to worry about that anymore. I'll put a list of supported mods to the op in a min
Edit: OP updated, ainur mods will likely be released tomorrow so you'll need to hold off until then to use them

Here's the install log from Magisk where Viper is asking for drivers.

MrBrady said:
Here's the install log from Magisk where Viper is asking for drivers.
Click to expand...
Click to collapse
Can you try this test zip and send the recovery log?

Zackptg5 said:
Can you try this test zip and send the recovery log?
Click to expand...
Click to collapse
Sure! Installation failed. Log attached.

MrBrady said:
Sure! Installation failed. Log attached.
Click to expand...
Click to collapse
Danget, dumb error on my part. I reuploaded the attachment in my last post so try that. Sorry!

Zackptg5 said:
Danget, dumb error on my part. I reuploaded the attachment in my last post so try that. Sorry!
Click to expand...
Click to collapse
Installed the updated file. Still asking to install drivers. Log attached.

MrBrady said:
Installed the updated file. Still asking to install drivers. Log attached.
Click to expand...
Click to collapse
Dang, still same error on recovery log but now I'm starting to hone in on the problem. Thanks!

MrBrady said:
Installed the updated file. Still asking to install drivers. Log attached.
Click to expand...
Click to collapse
Does this aml work for you? (Post recovery log and aml folder please)

Zackptg5 said:
Does this aml work for you? (Post recovery log and aml folder please)
Click to expand...
Click to collapse
Installing this caused V4A to ask for drivers again. Folder and log attached.

MrBrady said:
Installing this caused V4A to ask for drivers again. Folder and log attached.
Click to expand...
Click to collapse
Think I got it. I'll need the same stuff as before

Zackptg5 said:
Think I got it. I'll need the same stuff as before
Click to expand...
Click to collapse
Bingo! That works now. Attached is the directory and log.

MrBrady said:
Bingo! That works now. Attached is the directory and log.
Click to expand...
Click to collapse
Sweet! Thanks for all your help, I really appreciate it :good:

Zackptg5 said:
Sweet! Thanks for all your help, I really appreciate it :good:
Click to expand...
Click to collapse
My pleasure! Thanks for making this mod! I know we all really appreciate it, even if it's not voiced often enough.

AML has been updated to v1.1! Main changes are fixes or xml cfg files (should fix issues with pixel 2's) and some other minor fixes. Thanks to @MrBrady for the troubleshooting help

v1.2 has been dropped. Hopefully this will be the last release for a while.
Changelog: Fixed janky bootmode stuff, Fix uninstall/upgrade when a supported audio mod has just been upgraded in bootmode
So basically any weird things that happened when flashing in magisk manager are now fixed

Zackptg5 said:
v1.2 has been dropped. Hopefully this will be the last release for a while.
Changelog: Fixed janky bootmode stuff, Fix uninstall/upgrade when a supported audio mod has just been upgraded in bootmode
So basically any weird things that happened when flashing in magisk manager are now fixed
Click to expand...
Click to collapse
Thanks! Seems to be working right on Pixel 2 XL now.

Safety net got tripped,RR unofficial 7.1.2, I passed again after uninstalling aml.
Gonna try again but install from twrp...seemed to fix my viper issues, might do the same for aml
---------- Post added at 08:27 AM ---------- Previous post was at 08:18 AM ----------
preference said:
Safety net got tripped,RR unofficial 7.1.2, I passed again after uninstalling aml.
Gonna try again but install from twrp...seemed to fix my viper issues, might do the same for aml
Click to expand...
Click to collapse
Yep, twrp install works with no safety net trip. I've never had this many issues using the direct install in magisk. I doubt that it's a module issue, I'm probably messing up the process.

Dropped v1.3. Fixes issues with output_session_processing patching - mainly applicable to dolby oreo

[MOD][FIX] Audio Bitrate Increase For Poco X3 NFC

Disclaimer :
Code:
I am not responsible for any damage to your device!
Use this mod at your own risk!
What's this?
This mod increases the audio bitrate on video recording from a disgraceful 96kbps to a respectable 320kbps. Thus, giving a richer, more pleasing audio quality.
Still confused? Click here for a better explanation
Requirements :
- A rooted phone with magisk installed
- An opened mind (important!)
Contributors :
@Jt380p
@Slim K
* NOTES * (READ) :
- Not all ROMs are compatible with this mod, you might end up in a bootloop. YOU HAVE BEEN WARNED!
Download :
https://drive.google.com/file/d/1wr-p7puOL8nYb1wj1AyVbh9XmMp5kRKI/view?usp=sharing (Flash with magisk manager)
Source :
https://forum.xda-developers.com/Mi-9/themes/magisk-audio-bitrate-increase-t3927810
Audio files provided by @Slim K
Thanks to :
@Slim K
@topjohnwu for Magisk
Created : 7/11/2020
Last updated : 7/11/2020

reserved

Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:

Slim K said:
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Click to expand...
Click to collapse
For me it works on Stock, but not on Urnyx05 GCam. Thanks Dev.

Lineage android 11 will benefit from it, or that is already implemented in them?

So which ROMs are not compatible?

Aki-to said:
So which ROMs are not compatible?
Click to expand...
Click to collapse
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.

Slim K said:
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Click to expand...
Click to collapse
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
This mod is also so extremely tiny, you could pretty much make these changes manually. Just take care of permissions and replace the file, that's it. It's even less complicated than working with /etc/fstab, it seems.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.

Aki-to said:
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
Click to expand...
Click to collapse
You assume correctly. The path to the functions can be usually found in /data/adb/magisk/util_functions.sh on your device.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Click to expand...
Click to collapse
Why write code twice when it already exists and works for everyone.

Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.

nike1973 said:
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
Click to expand...
Click to collapse
Yes it works

Thank you. Works on MIUI EU 12.0.6.

Eu 12.0.6, super stabilization (on stock camera) crashes when module is active.

I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!

Anyone tried on Xiaomi.eu rom?
Running 12.0.8.

Hi!
gkhnkaanyrtc said:
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
View attachment 5272691View attachment 5272693
Click to expand...
Click to collapse
Hi! I have the same problem ... Did you fix it? I use Miui 12.0.1 with Android 11

320kbps should be the default, I wonder why the f**k Xiaomi gives us 96kbps.

Does it work in Pixel Experience rom on Surya?

[MODULE] Mega Audio Mod - A collection of mods to give you the best audio experience.

Before I start, I'd like to apologize if you don't understand something I say. English isn't my native language
Mega Audio Mod​Overview​
Improve your audio experience
Install Audio Modification Library
Install DTS:X Ultra
Install ViPER4Android
A wide majority of you are probably already familiar with most of what happens here, in fact this module happens to be a collection of pre-existing Magisk modules helping keep your audio experience the best your device can provide. I earlier had to go through the pain of installing all of these modules every time I changed a ROM. (Which happened once or twice everyday) I, thus decided to make a module that automates the process for me and installs everything I need. I plan to keep updating this and learn even more magisk development in the future
To do:
Add some presets to the viper directory in Android folder (once I figure out how to write to /data via magisk modules)
Add some more audio associated improvements
Add some more modules
If you happen to have any idea on how to write to /data via magisk modules please reply to the thread..
If you have any suggestions please reply to the thread.
Credits​ @Team_DeWitt \ ViPer4Android
@UltraM8 @Nemuritor01 @JohnFawkes @LazerL0rd \ DTS:X Ultra
@Zackptg5 \ Audio Modification Library
I am not able to post links for some reason so please cope with me and copy and paste what I type below
Download:
Source: github.com/Maitreya29/Mega-Audio-Mod
Download: sourceforge.net/projects/mega-audio-mod/files/

reserved

reserved2

Can't get Viper driver to install. Even in permissive Selinux. DTS works. On Pixel 5

Your Android version is and have you a custom rom with custom kernel on your device or using stock rom?A lil bit more info where great.Cheers!!!

-CALIBAN666- said:
Your Android version is and have you a custom rom with custom kernel on your device or using stock rom?A lil bit more info where great.Cheers!!!
Click to expand...
Click to collapse
Android 11 stock rom
Magisk canary
Pixel 5