[Q] Manage DSP Manager with Tasker?

[alanthing]

I recently got some BlueTooth headphones for running and they don't sound that great but I was able to really brighten them up with DSP Manager. The problem is that I also use BlueTooth audio in my car, which doesn't need any enhancement by DSP Manager since it has ample sound quality already.

Can I automate changing DSP Manager preferences via Tasker? I can put it in a shell script and run with the Tasker Execute plugin, but I'm not sure what it would entail. Could I keep two copies of the preferences files and swap them in and out via tar? I guess I'd need a way to reload DSP Manager after doing so...

I guess some helpful hints would be where to look to find the DSP Manager preferences on the file system, and then how to reload the app/settings after editing the files outside of the GUI.

Thanks!

---------- Post added at 06:57 PM ---------- Previous post was at 06:39 PM ----------

I found the location of the XML files, but no combination of shuffling versions of the files and force quitting/relaunching the DSP Manager enabled the new preferences. I'd appreciate any ideas if anyone has them.

 

[alanthing]

I'm new at this, so bear with me please

Through checking out the AndroidManifest.xml file, I was able to launch the DSP Manage app via:

# am start -a android.intent.action.MAIN -n com.bel.android.dspmanager/.activity.DSPManager

And into the Bluetooth headset preferences screen directly via:

# am start -a com.bel.android.dspmanager.BLUETOOTH

But I'm still having the issue where if I edit the xml settings file, the changes are not reflected when launching the app. I feel like I'm on the verge of figuring this but I can't string together the correct search term in Google to find it.

 

[thx1200]

Did you ever figure this out? I want to do basically the same thing.

 

[alanthing]

I was able to change the XML preferences file and launch the various settings, but nothing would activate the changes in the XML file. Maybe there's a way to intentionally crash the app and then have it reload the XML file but I was not able to figure it out and abandoned it.

 

[thx1200]

I was able to change the XML preferences file and launch the various settings, but nothing would activate the changes in the XML file. Maybe there's a way to intentionally crash the app and then have it reload the XML file but I was not able to figure it out and abandoned it.

That is very disappointing. :-(

I take it you tried closing the app via the app close task in Tasker? That's really the only way I can think of to terminate the app in memory. I'm guessing, though, that it's not the main app that needs to be recycled, but a service associated with the app.

Who wrote DSPManager? Do you happen to know? Any way to contact the author and request a feature?

 

[alanthing]

DSP Manager is part of CyanogenMod core code. It can't be restarted like a regular app. I suppose the GUI could be punted but it won't reload in any new configs without interacting with the GUI. It'd be nice if they could extend it to include profiles and then allow Tasker integration.

 

[thx1200]

DSP Manager is part of CyanogenMod core code. It can't be restarted like a regular app. I suppose the GUI could be punted but it won't reload in any new configs without interacting with the GUI. It'd be nice if they could extend it to include profiles and then allow Tasker integration.

I'm not using a CyanogenMod ROM. I'm on a Sense ROM. So it must be fairly modular? That's encouraging. I wonder if I can modify the source code and replcae the version on my ROM with that version. A lot of work, though...

 

[alanthing]

From what I understand, it can be flashed on any rooted rom via Clockwork recovery, so it hooks into the core of Android instead of a regular "app." When I meant it's part of the CM core code, I meant that the code is now maintained as part of the CM project. But yeah, because it's not a regular application, I think this stands to be nearly impossible without Tasker hooks from the developers.