JamesDSP Audio Manager [MMT-EX]

[ichmyselfandi]

Since there are substantial changes in magisk --path between Magisk v26 and earlier, both official latest AML and JamesDSP modules don't work on Magisk v26

Hello, I can't get JamesDSP to work, it crashes with 'JamesDSP keeps stopping'. I also allowed the 2 app permissions.
My steps: installed your AML version via Magisk; restart system; install your JamesDSP via Magisk; restart system; error. Without AML and James only I get the same error.

LineageOS 19, Android 12
Magisk Official 26.1 (26100)
Zygisk: No
Ramdisk: Yes


Edit:

It worked with Magisk Delta (from HuskyDG) and official AML.
I also enabled Zygisk, but did not test if necessary.

Releases · HuskyDG/magisk-files

Contribute to HuskyDG/magisk-files development by creating an account on GitHub.

github.com

 

[zgfg]

Hello, I can't get JamesDSP to work, it crashes with 'JamesDSP keeps stopping'. I also allowed the 2 app permissions.
My steps: installed your AML version via Magisk; restart system; install your JamesDSP via Magisk; restart system; error. Without AML and James only I get the same error.

LineageOS 19, Android 12
Magisk Official 26.1 (26100)
Zygisk: No
Ramdisk: Yes

When installing, you should be prompted to choose Huawei or not (Vol+/Vol-). It's not really about Huawei but about 64bit audio drivers

If it doesn't work as 'non-Huawei', try as 'Huawei' (64bit audio drivers) - install, reboot and test

Btw, when you you install the module from Magisk app, before you reboot, observe the 'diskette' icon on top-right - click to save the installation log (see the screenshot attached)

Take that log from Download folder (magisk_install_log_2023-06-***) and attach here to see - but (re)try first both as 'Huawei' and 'not-Huawei'

----

Anyway, per OP developer Zackptg5 (see his post #1357 above), his latest JDSP module version
https://raw.githubusercontent.com/Zackptg5/JamesDSPManager/master/install.zip

was adapted and should work on Magisk v26 (I have also tested and it worked for me on Magisk v26102 Canary) hence I've removed my JDSP fix for Magisk v26 (not necessary anymore), please use his official JDSP module

 

[ichmyselfandi]

When installing, you should be prompted to choose Huawei or not (Vol+/Vol-). It's not really about Huawei but about 64bit audio drivers

If it doesn't work as 'non-Huawei', try as 'Huawei' (64bit audio drivers) - install, reboot and test

Btw, when you you install the module from Magisk app, before you reboot, observe the 'diskette' icon on top-right - click to save the installation log (see the screenshot attached)

Take that log from Download folder (magisk_install_log_2023-06-***) and attach here to see - but (re)try first both as 'Huawei' and 'not-Huawei'

----

Anyway, per OP developer Zackptg5 (see his post #1357 above), his latest JDSP module version
https://raw.githubusercontent.com/Zackptg5/JamesDSPManager/master/install.zip

was adapted and should work on Magisk v26 (I have also tested and it worked for me on Magisk v26102 Canary) hence I've removed my JDSP fix for Magisk v26 (not necessary anymore), please use his official JDSP module

I got it work with Magisk Delta (see edit).

What is better? 'non-Huawei' (128bit??? audio drivers) or 'Huawei' (64bit audio drivers)?

 

[zgfg]

I got it work with Magisk Delta (see edit).

What is better? 'non-Huawei' (128bit??? audio drivers) or 'Huawei' (64bit audio drivers)?

Some new devices have only 64bit audio drivers and JDSP will never work as 'non-Huawei' with 32bit audio drivers

For devices that have only 32bit drivers or both, 'non-Huawei' will work

Don't know if there is any audible difference (if both work on your device/ROM), but generally, if 64bit drivers work, stick with them (they should be default for the ROM)

You should always try one, if not working than the other

---

It's similarly for Viper4Android - old V4A modules (for 32bit drivers) cannot work on devices that require 64bit drivers, but there is a beta V4A module available, for 64bit audio drivers

 

[Ghisy]

Hey guys,

I just realized I have 4.6 installed and the latest is 4.7. Can I just flash the newest one in Magisk on top of the older one? Or should I uninstall 4.6 first then install 4.7?

 

[zgfg]

Hey guys,

I just realized I have 4.6 installed and the latest is 4.7. Can I just flash the newest one in Magisk on top of the older one? Or should I uninstall 4.6 first then install 4.7?

Usually, for the modules, updating should work

Hence why don't you try - if it won't work, then uninstall and clean install

 

[Ghisy]

Usually, for the modules, updating should work

Just fyi, it worked!

 

[ichmyselfandi]

Is it normal that JamesDSP app doesn't ask for root permission?

 

[zgfg]

Is it normal that JamesDSP app doesn't ask for root permission?

Yes. It's just the app/mngr, audio patches are installed by the Magisk JDSP module

 

[smallKING81]

Samsung Galaxy M51, Android 12, root Magisk Delta Canary 25210, Poweramp build-963-uni. When connecting wired Beats Pro headphones (in the player settings for wired headphones, Hi-Res audio output is set, the sampling rate is "Device frequency", the sample format is "Auto") and the JamesDSP v4.7 magisk module is turned on, the sound starts to stutter. In the Hi-Res audio output settings for wired headphones, the maximum audio buffer size is set: Buffer 100 ms, number of DSP-8 buffers. Does not help, the sound stutters. Additionally, in the phone settings item "Developer settings" the maximum log buffer size is set to 8 MB, which also does not help, the sound stutters. When listening to music through the speaker and outputting the speaker sound to Hi-Res or OpenSL ES audio output with JamesDSP active, the sound does not stutter. With Viper4Android FX 2.7.2.1 turned on, the sound in wired headphones does not stutter, sound processing goes as expected. How can I overcome the problem of stuttering in wired headphones with active JamesDSP?

 

[vjx012]

Both V4A and James DSP failed to install/launch on my Galaxy S9+ running LineageOS 20 - V4A would stop at adding Magisk module and James would force close.

The solution to both is to downgrade from Magisk 26.1 to 25.2 and V4A would successfully add the Magisk module while James DSP would launch and work properly. And after the install, feel free to upgrade to 26.1.

To downgrade, download the 25.2 flashable ZIP and APK, flash ZIP through recovery, boot into system, uninstall Magisk 26.1 and install 25.2, install James DSP or V4A, reboot, wait for install to complete, and then upgrade to 26.1.

Note that you won't lose your data or modules by uninstalling and downgrading Magisk, so you don't have to worry about reinstalling your modules, configuring Zygisk or DenyList and so on, but Shamiko deactivates itself (without uninstalling).

 

[Zackptg5]

JDSP updated to MMTEx v3.0 template! This adds support for magisk delta (users with audio_effect confs in odm should be good to go now) and for KernelSU

 

[xerel89]

JDSP updated to MMTEx v3.0 template! This adds support for magisk delta (users with audio_effect confs in odm should be good to go now) and for KernelSU

For my is everytime crashing jsdp with the latest test v4.0 and the new aml V5.0

 

[kalehrl]

Can notification crackling be fixed somehow?

 

[Zackptg5]

For my is everytime crashing jsdp with the latest test v4.0 and the new aml V5.0

You try new stable zip? Try uninstalling all audio mods first and fresh jdsp install to start. Some of the test builds had breaking bugs

 

[Zackptg5]

JDSP updated to v5.0!
App update changelog:
* LiveProg update: Clean up EEL RAM disk before new script being loaded
* EEL engine update:
* Unify string, thread pool, convolver in one virtual data type
* Introduce efficient running min/max, median filter
* Allow STFT window function to be specified
* Correct STFT phase value(Yield no difference for any previous scripts that depends on relative phase / magnitude only spectral processing)

 

[Jbonn765]

Hey I love your work.

Im having a little bit of a problem though. I have the OnePlus 9 Pro 5g Evolution Rom OS13. When I start up my phone and I use my Bluetooth earbuds jamesdsp works fine for a few seconds to a few minutes because I can obviously hear the increase in the gain that I set. But then randomly it just stops working. Even if I stop the app and restart it. I figured my battery saver or something like that was shutting it off in the background but I checked the apps settings and everything. And everything seems to be in order. So I'm just unsure of why it would work for a bit then just shut off and not work again until I restart my phone again. Any help would be awesome thank you.

 

[Big Kettle]

Hello, I have a problem with JamesDSP.
Every time I'm on YouTube or any other app that supports JamesDSP. You know in the app, at the bottom center there is a power button, I press it and then after max 10 mins out just turnes grey and I have to press it again.

 

[Techguy777]

JDSP updated to v5.0!
App update changelog:
* LiveProg update: Clean up EEL RAM disk before new script being loaded
* EEL engine update:
* Unify string, thread pool, convolver in one virtual data type
* Introduce efficient running min/max, median filter
* Allow STFT window function to be specified
* Correct STFT phase value(Yield no difference for any previous scripts that depends on relative phase / magnitude only spectral processing)

Whats the odds you could make a jamesdsp script that would automatically install the 32 bit and 64bit without the volume buttons? Im trying to install on android windows subsystem and I have magisk and everything setup but you have to use the volume buttons and I have no way of doing that on windows.

There is supposed to be a way with wireless adb but for whatever reason my wireless debugging wont turn on the developer options. I am still looking for options but I do believe it would be beneficial if there was a straight install zip or a file we could setup to install the options we pick.

I would assume with your knowledge you could easily do it. I'd be interested to hear your thoughts thanks

 

[zgfg]

Whats the odds you could make a jamesdsp script that would automatically install the 32 bit and 64bit without the volume buttons? Im trying to install on android windows subsystem and I have magisk and everything setup but you have to use the volume buttons and I have no way of doing that on windows.

There is supposed to be a way with wireless adb but for whatever reason my wireless debugging wont turn on the developer options. I am still looking for options but I do believe it would be beneficial if there was a straight install zip or a file we could setup to install the options we pick.

I would assume with your knowledge you could easily do it. I'd be interested to hear your thoughts thanks

Yeah, that's really like a relict from the times when modules were to be flashed through custom recoveries, and more, from the times of CWM custom recovery (prior to TWRP) - CWM had no touch control, options had to be selected by scrolling up/down by Volume Keys and confirmed by pressing Power Key)

Btw, customize.sh / install.sh script could automatically detect if 64bit drivers are needed or not - without asking user is it 'Huawei' or not (Huawei was first and at that time only, but it was also four or so years ago, that needed 64bit drivers)

---

Once I had a Huawei with broken Volume Key and for all other apps I simply used slider but for installing JDSP it was like a showstopper

So, do the following:

- unzip "JamesDSP_Manager-v5.0(89).zip"
- go to "Common/addon/Volume-Key-Selector" folder
- open "install.sh" script
- scroll to "chooseport()" function
- write before "while true; do" loop
- ie, to the line 30
- insert a line with "return 0" or "return 1" (without quotes)
- "0" hard-codes as if you had 'selected' Vol+ (Up)
- "1" hard-codes as if you had 'selected' Vol- (Down)
- save, re-zip and install without the need for VK