• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[MOD][4.0.3+][32-bit] Dolby Digital Plus (Huawei) [r9]

Search This thread

worstenbrood

Senior Member
May 14, 2008
1,063
1,405
This is basically the Dolby Digital Plus audio effect ported from the latest Huawei Ascend P6 beta kitkat rom.
I also ported the configuration app which you can launch from the launcher.

- Notes
If you flash this on Lollipop, make sure you uncheck "Use NuPlayer" in Developer options!!
When having FC's, put SELinux in permissive!!! SELinuxModeChanger
This started out as a Nexus 4 only project, but should work on any device now

- Versions
v1 - 20/03/2014
- Initial release

v2 - 20/03/2014
- Added /system/etc/dolby_config.xml
- Modified DolbyMobileAudioEffectService to load config from /system/etc instead of /data/cust/.../xml
- Added revert

v2.1 - 20/03/2014
- GlobalDolbyEffect uses default theme now, not Light anymore
- Flash this update after flashing v2 (it only updates the apk)

v2.2 - 23/03/2014
- Removed unused permissions from DolbyMobileAudioEffectService
- Resigned DolbyMobileAudioEffectService with CM platform key
- Flash this update after flashing v2 (it only updates the apk)

v3 - 25/03/2014
- Two versions now, one for stock based roms, one for CM based roms
- In CM based version, the DolbyMobileAudioEffectService uses shareduserid android.uid.system. This should make the service running without
a notification.

v4 beta - 27/03/2014
- Merged DolbyMobileEffectService into GlobalDolbyEffect
- Disabled call to startForeground (This disables the notification, but now the service could be killed by the system in case of memory shortage)
- When connecting a headset, a notification icon will be shown and you can change presets by clicking on the notification.
- Still in beta, I'm still testing it, but it seems to run fine, and the service wasn't killed yet in a few hours of listening to music.
Feedback is welcome !

v5 - 23/05/2014
- Target sdk changed to 17
- GlobalDolbyEffect.apk signed with private key

r6 beta - 26/11/2014
- New install script
- On lollipop or higher, new app folder structure is used. On older versions old structure is used.
- Audio_effects.conf is patched now, not overwritten, flashing this mod doesn't disable other effects.
- Added audio effects api v2 library, so it should work on <4.3 versions
- Revert zip patches audio_effects.conf now, so no other effects will be disabled during revert.

r7 - 09/12/2014
- Materialized icon
- Added addon.d script, on supported roms it survives rom updates now
- Reverter deletes addon.d script

r8 - 03/01/2014
- Hide from recents

r9 - 08/01/2015
- Also hide alert dialog from recents
- Final release, i don't think i can improve it much further.

Downloads

XDA:DevDB Information
Dolby Digital Plus (Huawei), App for the Google Nexus 4

Contributors
worstenbrood

Version Information
Status: Stable
Current Stable Version: r9
Stable Release Date: 2015-01-08

Created 2014-12-02
Last Updated 2015-01-08
 

Attachments

  • Screenshot_2014-03-20-09-23-47.png
    Screenshot_2014-03-20-09-23-47.png
    150.4 KB · Views: 110,927
  • Screenshot_2014-03-20-12-56-38.png
    Screenshot_2014-03-20-12-56-38.png
    79.8 KB · Views: 117,332
  • Screenshot_2014-03-20-12-56-54.png
    Screenshot_2014-03-20-12-56-54.png
    84.3 KB · Views: 116,951
Last edited:
T

tykate

Guest
This is basically the Dolby Digital Plus audio effect ported from the latest Huawei Ascend P6 beta kitkat rom.
I also ported the configuration app which you can launch from the launcher.

- Notes
This mod works in combination with DSP Manager other effects may be disabled by flashing this mod.

- Versions
v1 - 20/03/2014 - Initial release

- Git
https://bitbucket.org/worstenbrood/dolby_digital_plus_mako

It doesn't need DSP manager. If you have DSP manager, enabling one of the options in there will disable the dolby effect. Once you disable all effects in DSP manager, the dolby kicks back in.

is there a revert?
 

ravinder0003

Senior Member
Mar 14, 2012
476
884
It doesn't need DSP manager. If you have DSP manager, enabling one of the options in there will disable the dolby effect. Once you disable all effects in DSP manager, the dolby kicks back in.

superb bro... clearly hear the difference ... surround sound effects also there ...
Also, very easy to switch between DSP and dolby ...turn on dsp turn off dsp... no need to delete or revert anything

thanks again buddy ...
 

bamsbamx

Senior Member
Aug 2, 2011
572
591
Bilbo
livenfun.com
It seems not working for me on Purity rom.... When I click the checkbox it doesnt happen anything. Cant check the box

Tried before and after flashing DSP Manager

EDIT: Reading the logcat it says: mDolbyMobileSystem = null
 
Last edited:

bamsbamx

Senior Member
Aug 2, 2011
572
591
Bilbo
livenfun.com
Thats not necessarily a bad thing, could you provide a full (or filtered on dolby) logcat after changing a preset in the app ?

Well, it doesnt give so much info:

Code:
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient(14802): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioHeadsetByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioPreset() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
 

worstenbrood

Senior Member
May 14, 2008
1,063
1,405
Well, it doesnt give so much info:

Code:
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient(14802): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioHeadsetByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioPreset() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null

Is the dolbymobileaudioeffectservice running ? Do you see the notification ?

Sent from my Nexus 4 using xda app-developers app
 

worstenbrood

Senior Member
May 14, 2008
1,063
1,405
It seems not working for me on Purity rom.... When I click the checkbox it doesnt happen anything. Cant check the box

Tried before and after flashing DSP Manager

EDIT: Reading the logcat it says: mDolbyMobileSystem = null

The logs I posted above are all the logs related to Dolby, no service logs found

There must be a reason why the service isn't running, search for it in the logcat
 

bamsbamx

Senior Member
Aug 2, 2011
572
591
Bilbo
livenfun.com
There must be a reason why the service isn't running, search for it in the logcat

Okay, I think I found something, activityManager says that it was unable to start service intent with U=0

Code:
I/ActivityManager(  691): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity} from pid 1227
I/ActivityManager(  691): Start proc com.huawei.android.globaldolbyeffect for activity com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: pid=2914 uid=10023 gids={50023}
I/DolbyMobileAudioEffectClient( 2914): activity bindToRemoteRunningService()
W/ContextImpl( 2914): Implicit intents with startService are not safe: Intent { act=android.media.dolby.IDolbyMobileSystemInterface } android.content.ContextWrapper.bindService:517 android.media.dolby.DolbyMobileAudioEffectClient.bindToRemoteRunningService:121 com.huawei.android.globaldolbyeffect.GlobalDolbyEffectFragment.initDolbyMobileAudioEffectClient:236 
W/ActivityManager(  691): Unable to start service Intent { act=android.media.dolby.IDolbyMobileSystemInterface } U=0: not found
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
I/ActivityManager(  691): Displayed com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: +460ms
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient( 2914): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): getGlobalAudioSpeakerByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
 

worstenbrood

Senior Member
May 14, 2008
1,063
1,405
Okay, I think I found something, activityManager says that it was unable to start service intent with U=0

Code:
I/ActivityManager(  691): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity} from pid 1227
I/ActivityManager(  691): Start proc com.huawei.android.globaldolbyeffect for activity com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: pid=2914 uid=10023 gids={50023}
I/DolbyMobileAudioEffectClient( 2914): activity bindToRemoteRunningService()
W/ContextImpl( 2914): Implicit intents with startService are not safe: Intent { act=android.media.dolby.IDolbyMobileSystemInterface } android.content.ContextWrapper.bindService:517 android.media.dolby.DolbyMobileAudioEffectClient.bindToRemoteRunningService:121 com.huawei.android.globaldolbyeffect.GlobalDolbyEffectFragment.initDolbyMobileAudioEffectClient:236 
W/ActivityManager(  691): Unable to start service Intent { act=android.media.dolby.IDolbyMobileSystemInterface } U=0: not found
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
I/ActivityManager(  691): Displayed com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: +460ms
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient( 2914): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): getGlobalAudioSpeakerByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null

You sure you flashed v2 before v2.1 or 2.2 ?

Sent from my Nexus 4 using xda app-developers app
 
  • Like
Reactions: bamsbamx

worstenbrood

Senior Member
May 14, 2008
1,063
1,405
Oooooppsss nope, i didnt.... I got excited and didnt read the post... Hahahaha

Flashed v2 then v2.1.went to dsp manager, disabled all and now its working :D

Sorry for making you waste your time in so silly way

Hahaha, no problem. I'll create a full 2.2 zip tomorrow for the overexcited ones ;)

Sent from my Nexus 4 using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 82
    This is basically the Dolby Digital Plus audio effect ported from the latest Huawei Ascend P6 beta kitkat rom.
    I also ported the configuration app which you can launch from the launcher.

    - Notes
    If you flash this on Lollipop, make sure you uncheck "Use NuPlayer" in Developer options!!
    When having FC's, put SELinux in permissive!!! SELinuxModeChanger
    This started out as a Nexus 4 only project, but should work on any device now

    - Versions
    v1 - 20/03/2014
    - Initial release

    v2 - 20/03/2014
    - Added /system/etc/dolby_config.xml
    - Modified DolbyMobileAudioEffectService to load config from /system/etc instead of /data/cust/.../xml
    - Added revert

    v2.1 - 20/03/2014
    - GlobalDolbyEffect uses default theme now, not Light anymore
    - Flash this update after flashing v2 (it only updates the apk)

    v2.2 - 23/03/2014
    - Removed unused permissions from DolbyMobileAudioEffectService
    - Resigned DolbyMobileAudioEffectService with CM platform key
    - Flash this update after flashing v2 (it only updates the apk)

    v3 - 25/03/2014
    - Two versions now, one for stock based roms, one for CM based roms
    - In CM based version, the DolbyMobileAudioEffectService uses shareduserid android.uid.system. This should make the service running without
    a notification.

    v4 beta - 27/03/2014
    - Merged DolbyMobileEffectService into GlobalDolbyEffect
    - Disabled call to startForeground (This disables the notification, but now the service could be killed by the system in case of memory shortage)
    - When connecting a headset, a notification icon will be shown and you can change presets by clicking on the notification.
    - Still in beta, I'm still testing it, but it seems to run fine, and the service wasn't killed yet in a few hours of listening to music.
    Feedback is welcome !

    v5 - 23/05/2014
    - Target sdk changed to 17
    - GlobalDolbyEffect.apk signed with private key

    r6 beta - 26/11/2014
    - New install script
    - On lollipop or higher, new app folder structure is used. On older versions old structure is used.
    - Audio_effects.conf is patched now, not overwritten, flashing this mod doesn't disable other effects.
    - Added audio effects api v2 library, so it should work on <4.3 versions
    - Revert zip patches audio_effects.conf now, so no other effects will be disabled during revert.

    r7 - 09/12/2014
    - Materialized icon
    - Added addon.d script, on supported roms it survives rom updates now
    - Reverter deletes addon.d script

    r8 - 03/01/2014
    - Hide from recents

    r9 - 08/01/2015
    - Also hide alert dialog from recents
    - Final release, i don't think i can improve it much further.

    Downloads

    XDA:DevDB Information
    Dolby Digital Plus (Huawei), App for the Google Nexus 4

    Contributors
    worstenbrood

    Version Information
    Status: Stable
    Current Stable Version: r9
    Stable Release Date: 2015-01-08

    Created 2014-12-02
    Last Updated 2015-01-08
    6
    It works fine for me.... I can hear the effects, both on speaker and headset on my N7...

    I found out why it didn't work for me .. Make sure that you have turned off "Use NuPlayer" in Developer options. Seems like when you use NuPlayer, the effect doesn't work. Using Awesome Player it just works !
    Fixing the SE stuff as we speak ... L flashable zip soon..
    4
    I'm working on a lollipop version which also will have a new install method so that it can be installed on any rom, without interfering with other sound effects. It would be nice if someone could make me a materialized version of the launcher icon (see attachment).
    3
    Anyway to disable the icon in the notification drawer?

    Try v4 beta from the OP

    Changes:
    - Merged DolbyMobileEffectService into GlobalDolbyEffect
    - Disabled call to startForeground (This disables the notification, but now the service could be killed by the system in case of memory shortage)
    - When connecting a headset, a notification icon will be shown and you can change presets by clicking on the notification.

    I'm still testing it, but it seems to run fine, and the service wasn't killed yet in a few hours of listening to music.
    3
    edit: added to first post