JamesDSP Audio Manager [MMT-EX]

[Techguy777]

What should I do? If I install James module, I cannot install this AKP
View attachment 5920715

It looks like your trying to install kernel SU. I have no experience with that yet even though I plan to eventually. I hear people say its better than magisk but I don't understand how yet because I havent heard of 1 thing it can do that magisk cant do.

 

[smallKING81]

magisk delta Magisk fdac22ba-delta (25210) is the latest canary and it works perfectly

yes, you are right! I installed Magisk Delta Canary 25210 and JDSP is working now, woohoo!!! Thank you for your help, buddy!

 

[sawdoctor]

Running the rootless version on the zfold 3 and really impressed. Shame about Spotify but it works perfectly with Tidal and Plex. Only thing I'd say is make the headphone/earbuds profile's a bit easier to find. Unless you read the playstore instructions you'll probably not find them and most users are too lazy to read

 

[21071992]

Running the rootless version on the zfold 3 and really impressed. Shame about Spotify but it works perfectly with Tidal and Plex. Only thing I'd say is make the headphone/earbuds profile's a bit easier to find. Unless you read the playstore instructions you'll probably not find them and most users are too lazy to read

Which android version are you using? I cant get rootless jamesdsp to work on my poco f3, I tried Miui 14 and Pixelos 13, both cant get rootles jdsp to work properly. As soon as I enable jdsp, sounds is distorted, reverb, stutter, lagging, unusable at all. I really want to try rootless because I dont want to root my phone, I have no need for any module.

 

[m0han]

.... As soon as I enable jdsp, sounds is distorted, reverb, stutter, lagging, unusable at all....

FYI from this post: Just make sure you have enough RAM to run both of them at the same time as well as your audio app while......

You can try the attachment there.

 

[21071992]

FYI from this post: Just make sure you have enough RAM to run both of them at the same time as well as your audio app while......

You can try the attachment there.

This post refer to root version, and I have problem with rootless version, I also don't use v4a so can't relate to this post. I tried root jdso and it works fine, only rootless version gives problems

 

[sawdoctor]

Which android version are you using? I cant get rootless jamesdsp to work on my poco f3, I tried Miui 14 and Pixelos 13, both cant get rootles jdsp to work properly. As soon as I enable jdsp, sounds is distorted, reverb, stutter, lagging, unusable at all. I really want to try rootless because I dont want to root my phone, I have no need for any module.

I'm on the zfold 3 but my son has a xaiomi redmi note 10 pro and it works. Auto dynamic range compressor caused distortion for me so I just leave that toggled off

 

[m0han]

.... Auto dynamic range compressor caused distortion for me so I just leave that toggled off

Although I know sound can differ from device to device, it would be nice if you can post your JDSP settings, preferably with screenshots. Or, is there a simple User's Guide somewhere?

 

[sawdoctor]

Although I know sound can differ from device to device, it would be nice if you can post your JDSP settings, preferably with screenshots. Or, is there a simple User's Guide somewhere?

Tbh I'm still playing with it and haven't actually decided on the best settings but have noticed 2 things. Auto dynamic range compressor caused terrible distortion and secondly less is more. The more options I toggle on the more likely I am to have issues

 

[zgfg]

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

I have adapted both modules and successfully tested on my two phones, one with Magisk v25210 and the other with Magisk v26102 (Canary)

Ie, I have now both Viper4Android and JamesDSP (drivers merged with AML) co-working both on Magisk v26 and v25

My modded modules are attached, you can install and test

@Zackptg5 - please take a look and fix/release your official modules

For JAmesDSP, I had to adapt $ORIGDIR in functions.sh

For AML, I had to adapt $MAGISKTMP in post-fs-data.sh and $MODPATH both in post-fs-data.sh and service.sh

They are adapted to work both for Magisk v26 and earlier

All the rest is same/original in both modules. Your excessive logging helped a lot to fix/adapt them

---

Edit:

Per OP developer @Zackptg5 (see his post #1357 below), 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'm removing my JDSP module (fix for Magisk v26) from the attachment.

Please use his official JDSP (or newer, if/when released):
id=ainur_jamesdsp
name=JamesDSP Manager
version=v4.7 (8-4-2022)
versionCode=87

 

[m0han]

.... excessive logging helped a lot to fix/adapt them..

 

[zgfg]

Yeah, but the first step was to make the AML scripts to start logging somewhere

With the original env variables (incorrect for Magisk v26), post-fs-data.sh and service.sh scripts didn't even log

When I got them to start logging, then I had to inspect all "no such file" or "read only filesystem" errors in the logs to further correct the scripts to do their job

But at the end (easy to be a general now after the battle) it was all about properly setting the few env variables at the beginning of the scripts

---

Edit:

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

was adapted and should work on Magisk v26 (I tested and it worked for me on Magisk v26102 Canary) hence I've removed my JDSP module (fix for Magisk v26) from the attachment.

Please use his official JDSP (or newer, if/when released):
id=ainur_jamesdsp
name=JamesDSP Manager
version=v4.7 (8-4-2022)
versionCode=87

 

[m0han]

.... the first step was to make the AML scripts to start logging somewhere.... it was all about properly setting the few env variables....

You seem to have edited your earlier post a short while ago. Have the attached files been changed or are they the same as before?

 

[zgfg]

You seem to have edited your earlier post a short while ago. Have the attached files been changed or are they the same as before?

New attached versions print few more lines to the logs and differentiate their module names as on the screenshot

 

[Lughnasadh]

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

I have adapted both modules and successfully tested on my two phones, one with Magisk v25210 and the other with Magisk v26102 (Canary)

Ie, I have now both Viper4Android and JamesDSP (drivers merged with AML) co-working both on Magisk v26 and v25

My modded modules are attached, you can install and test

@Zackptg5 - please take a look and fix/release your official modules

For JAmesDSP, I had to adapt $ORIGDIR in functions.sh

For AML, I had to adapt $MAGISKTMP in post-fs-data.sh and $MODPATH both in post-fs-data.sh and service.sh

They are adapted to work both for Magisk v26 and earlier

All the rest is same/original in both modules. Your excessive logging helped a lot to fix/adapt them

Both mods are working on my devices:

Pixel 2 XL
Android 11
Magisk Canary 26102
JamesDSP also working with V4A (latest hoch)
AML (Magisk 26)

Pixel 6 Pro
Android 14 Beta 2.1
Magisk Canary 26102
JamesDSP also working with V4A-RE (Reverse Engineered)
AML (Magisk 26)

Interestingly, JamesDSP was working on the Android 14 DPs, but stopped working on the Android 14 Betas. I believe something changed with the betas to make it stop working. A few others with Pixel 6/7 devices also reported that JamesDSP stopped working when they updated from the Android 14 DPs to the Betas

This Android 14 Beta bug is unrelated to Magisk 26, I believe, as I was using Magisk Canary 26001 with Android 14 DP2 and it was working fine. . . So these two mods may have killed an Android 14 Beta "bug" as well.

Also, on both devices replacing the JamesDSP apk with the Rootless apk version works fine for me.

Thanks for updating these two mods!

UPDATE: Both mods are also working on my Pixel 7 Pro running Android 13 (May) & Stable Magisk 26.1, although both older mods were working on this device and setup beforehand as well.

 

[21071992]

I'm on the zfold 3 but my son has a xaiomi redmi note 10 pro and it works. Auto dynamic range compressor caused distortion for me so I just leave that toggled off

It's weird because I cant get the rootless version to work on my poco f3, tried stock rom, xiaomi.eu and aosp rom like pixelos but it just doesn't work, I really want to try the rootless version.

 

[Zackptg5]

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

I have adapted both modules and successfully tested on my two phones, one with Magisk v25210 and the other with Magisk v26102 (Canary)

Ie, I have now both Viper4Android and JamesDSP (drivers merged with AML) co-working both on Magisk v26 and v25

My modded modules are attached, you can install and test

@Zackptg5 - please take a look and fix/release your official modules

For JAmesDSP, I had to adapt $ORIGDIR in functions.sh

For AML, I had to adapt $MAGISKTMP in post-fs-data.sh and $MODPATH both in post-fs-data.sh and service.sh

They are adapted to work both for Magisk v26 and earlier

All the rest is same/original in both modules. Your excessive logging helped a lot to fix/adapt them

I already updated jdsp a couple days ago, aml should obtain whatever magisk --path is

 

[sawdoctor]

It's weird because I cant get the rootless version to work on my poco f3, tried stock rom, xiaomi.eu and aosp rom like pixelos but it just doesn't work, I really want to try the rootless version.

Is the distortion on both speaker and earphones and have you tried toggling all the options off then enable one at a time. Can't think of anything else

 

[21071992]

Is the distortion on both speaker and earphones and have you tried toggling all the options off then enable one at a time. Can't think of anything else

Distortion from both speaker and earphones, if I only toggle the master switch and no options on, there is noticeably noise in the background

 

[zgfg]

I already updated jdsp a couple days ago, aml should obtain whatever magisk --path is

If you think this AML:

https://raw.githubusercontent.com/Zackptg5/Audio-Modification-Library/master/install.zip

module.prop:
id=aml
name=Audio Modification Library
version=v4.2
versionCode=57

That one does not work for me on Magisk v26:
- it produces empty folders /data/adb/aml and /data/adb/modules/aml/system,
- and there were no even log files debug-pfsd.log and debug.log

Indeed, your post-fs-data.sh script starts with:
[ -d "/sbin/.magisk" ] && MAGISKTMP="/sbin/.magisk" || MAGISKTMP="$(find /dev -mindepth 2 -maxdepth 2 -type d -name ".magisk")"
MODPATH=$MAGISKTMP/modules/aml

I don't have /sbin (and never had) and now for Magisk v26
its tmp dir has moved from /dev/<something> to /debug_ramdisk

hence your setup produces:
$MAGISKTMP = ""
$MODPATH = "/modules/aml"

As a result, post-fs-data.sh cannot read/write or do anything with that non-existing $MODPATH folder,
and it can not even write the log to "$MODPATH/debug-pfsd.log" to see what/why went wrong

So please see the path changes I made in my 'fix-for-Magisk-v26' for $MAGISKTMP and $MODPATH, they work for me on Magisk v26 and v26 as:
[ "$(magisk --path 2>/dev/null)" ] && MAGISKTMP="$(magisk --path 2>/dev/null)/.magisk" || MAGISKTMP="/sbin/.magisk"
MODPATH=/data/adb/modules/aml

or simpler:
MAGISKTMP="$(magisk --path 2>/dev/null)/.magisk"
MODPATH=${0%/*}

I have tested my fix both on Magisk v26 and v25

On Magisk v26 it cannot be anymore:
MODPATH=$MAGISKTMP/modules/aml

since /debug_randisk/.magisk/modules is now read-only folder on Magisk v26 (hence that change is also needed for service.sh, otherwise even service.sh cannot write its debug.log)

There are also few other users (here and in the AML thread) who confirmed that this fix now works for them, while the original AML did not work on Magisk v26