[AUDIO][EXYNOS][OREO][V-1.7.0] Samsung SoundAlive Dolby Atmos - EOL

Huele Fello

Senior Member
Dec 4, 2013
306
122
0
I've read a lot of trial and error fixes and errors on this thread about installing Dolby Atmos. I have a Note 8 Exynos phone with DeluxeROM v9.2, TWRP and Magisk rooted. I would like to try installing Dolby Atmos, but I don't want to go through a lot of experimentation. Is there a sure fire way to install this application on my phone? I can back up my entire OS system and restore it if I have to during this process. Please advise if there is a sure fire way, i.e. no errors. Thanks in advance.
 

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
I've read a lot of trial and error fixes and errors on this thread about installing Dolby Atmos. I have a Note 8 Exynos phone with DeluxeROM v9.2, TWRP and Magisk rooted. I would like to try installing Dolby Atmos, but I don't want to go through a lot of experimentation. Is there a sure fire way to install this application on my phone? I can back up my entire OS system and restore it if I have to during this process. Please advise if there is a sure fire way, i.e. no errors. Thanks in advance.
I don't usually promise anything until I try it, so probably send your Note 8 over for me to test?

Trial and errors are for those legacy or Snapdragon phones only perhaps. I'd recommend you to do a backup and just flash the latest version of the libs installer. There are 2 possible outcomes:

1. Everything just happen to work fine, happy ending.

2. Nothing works, might cause something to force close or bootloop in a worst case scenario (Very unlikely to happen)
At this point you can help to debug the problem by providing logcat and whatnot if you like, I will try to solve when I'm free if I like.
Or you can decide not to help at all and just restore your backup, life still goes on without Dolby Atmos.

Thank you! I could fix my sister's Samsung J5 (2015) with the Snapdragon variant as the custom rom didn't include this audio options!!
I have no idea if my mod works on Snapdragon phone, the zip might not even installs.
You can try to go to Snapdragon thread instead, link is available in first few lines of main post.
 

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Dolby Atmos Test Build 01 [FOR EXYNOS ONLY]

This version of Dolby Atmos libs installer installs Dolby Atmos soundfx libs and and other files required for Dolby Atmos sound effect only.
That said, this test build shouldn't modify other aspects of the audio like loudness and Samsung SoundAlive related effects.

If you'd installed my other version of Dolby Atmos lib installer before, you will have to restore your ROM backup/dirty flash your ROM first before flashing this test build to have your original libs back as those files are already modified and this test build won't be able to restore those modified files to original ones for you.

If you are interested in helping this out, please test and let me know the result.
Also, please keep in mind that in order to test this, keep your ambient environment, phone's audio level and played music constant.
1. Stay in a quiet environment throughout your entire testing process.
2. Same media audio level before and after installing this zip
3. Same segment of the same song before and after installing this zip

**If you have an oscilloscope, you might be able to probe the headphone jack out and determine the changes in amplitudes before and after installing the test build. The amplitude will definitely change due to the added audio effect (Not sure about this if you turn it off after installing), but the changes shouldn't be large enough for you to find the audio volume very low.
 

Attachments

Last edited:

Aker666

Member
Aug 24, 2015
33
10
0
A Coruña
thetechnicallyweakguy.com
I don't usually promise anything until I try it, so probably send your Note 8 over for me to test?

Trial and errors are for those legacy or Snapdragon phones only perhaps. I'd recommend you to do a backup and just flash the latest version of the libs installer. There are 2 possible outcomes:

1. Everything just happen to work fine, happy ending.

2. Nothing works, might cause something to force close or bootloop in a worst case scenario (Very unlikely to happen)
At this point you can help to debug the problem by providing logcat and whatnot if you like, I will try to solve when I'm free if I like.
Or you can decide not to help at all and just restore your backup, life still goes on without Dolby Atmos.

I have no idea if my mod works on Snapdragon phone, the zip might not even installs.
You can try to go to Snapdragon thread instead, link is available in first few lines of main post.
Sorry, english it's not my main language. I wanted to say that that I was able to fix my sister's Samsung J5 (2015) with the Snapdragon thread variant as the custom rom that I flashed on the phone didn't include this audio options!!

Sorry for the confusion. Regards!
 
  • Like
Reactions: ImbaWind

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Sorry, english it's not my main language. I wanted to say that that I was able to fix my sister's Samsung J5 (2015) with the Snapdragon thread variant as the custom rom that I flashed on the phone didn't include this audio options!!

Sorry for the confusion. Regards!
All good, English isn't my native language either.
And by the way, that part of my reply is not intended for you, it was for someone else.

Glad that the Snapdragon thread helped you. Although I've no idea if it really does or just a placebo effect.
 

Aker666

Member
Aug 24, 2015
33
10
0
A Coruña
thetechnicallyweakguy.com
All good, English isn't my native language either.
And by the way, that part of my reply is not intended for you, it was for someone else.

Glad that the Snapdragon thread helped you. Although I've no idea if it really does or just a placebo effect.
No problem! I can confirm that it works, we have listened music with headphones by turning on/off the audio effects and the sound quality improves. Also my sister told me that now it sounds like the stock rom she had before flash this new one. So there is no placebo effect :)
 
  • Like
Reactions: ImbaWind

Huele Fello

Senior Member
Dec 4, 2013
306
122
0
I don't usually promise anything until I try it, so probably send your Note 8 over for me to test?

Trial and errors are for those legacy or Snapdragon phones only perhaps. I'd recommend you to do a backup and just flash the latest version of the libs installer. There are 2 possible outcomes:

1. Everything just happen to work fine, happy ending.

2. Nothing works, might cause something to force close or bootloop in a worst case scenario (Very unlikely to happen)
At this point you can help to debug the problem by providing logcat and whatnot if you like, I will try to solve when I'm free if I like.
Or you can decide not to help at all and just restore your backup, life still goes on without Dolby Atmos.
I can't possibly send my phone to you as I need it daily, as I live in a virtual cave and my only connection to the outside world and aliens is a teletype, Samsung 4K OTA TV and my Note 8. But I'm willing to try flashing the latest version of the libs installer and hope #1 happens. As you say above, I'll just restore my backup if I have problems. So where do I get the latest version of the libs installer? Thanks for your help.
 
Last edited:
  • Like
Reactions: ImbaWind

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
I can't possibly send my phone to you as I need it daily, as I live in a virtual cave and my only connection to the outside world and aliens is a teletype, Samsung 4K OTA TV and my Note 8.
Not sure if aliens want to connect with you.

So where do I get the latest version of the libs installer?
That's a question worth pondering..




You can try the test build a few post above.
 

batuzai04123

Senior Member
Dec 26, 2012
206
66
28
Thank you for this mod, it's working.

However, i noticed that the LOUDSPEAKER is way too low, my old huawei tablet 2016 has higher volume than full volume galaxy s8 exynos playing same audio track.


I checked the /system/etc/mixer_gains.xml to see if i can manually adjust the loudspeaker volume, but I'm afraid to do so since this node,

<path name="gain-media-speaker"></path>

is empty. I'm not sure what strings should i input on that part.

Appreciate any help.

Thank you.
 

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Thank you for this mod, it's working.

However, i noticed that the LOUDSPEAKER is way too low, my old huawei tablet 2016 has higher volume than full volume galaxy s8 exynos playing same audio track.


I checked the /system/etc/mixer_gains.xml to see if i can manually adjust the loudspeaker volume, but I'm afraid to do so since this node,

<path name="gain-media-speaker"></path>

is empty. I'm not sure what strings should i input on that part.

Appreciate any help.

Thank you.
There's a test build last page, maybe you can try that.
Make sure you restore your original ROM files before you do so.
 
Last edited:

DAvinash97

Senior Member
Oct 8, 2016
54
81
38
Bhilai
star2lte:/ $ su
star2lte:/ # logcat | grep SAEffectManager
10-29 16:41:45.004 21068 21068 D SAEffectManager: *****getNewSoundAliveInstance start*****
10-29 16:41:45.046 21068 21068 D SAEffectManager: *****newSoundAliveEffect create Sucessfully*****
10-29 16:41:45.046 21068 21068 D SAEffectManager: *****getNewSoundAliveInstance end****
10-29 16:41:45.046 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:45.048 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:45.049 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:45.050 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:45.063 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:45.065 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:45.065 21068 21068 D SAEffectManager: *****updateSquareUIsetting()*****
10-29 16:41:45.065 21068 21068 D SAEffectManager: position: 40
10-29 16:41:45.065 21068 21068 D SAEffectManager: *****convPresetIndexToGenreIndex()***** presetIndex : 0 genreIndex : 0
10-29 16:41:45.070 21068 21068 D SAEffectManager: set UHQ-Upscaler as : 0
10-29 16:41:45.082 21068 21068 D SAEffectManager: set tube as : 0
10-29 16:41:45.082 21068 21068 D SAEffectManager: set hall as : 0
10-29 16:41:45.090 21068 21068 E SAEffectManager: SAControlPanel Activity is Null
10-29 16:41:45.593 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:45.595 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:52.849 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:52.850 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:52.855 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:52.856 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:52.856 21068 21068 D SAEffectManager: *****updateSquareUIsetting()*****
10-29 16:41:52.857 21068 21068 D SAEffectManager: position: 40
10-29 16:41:52.857 21068 21068 D SAEffectManager: *****convPresetIndexToGenreIndex()***** presetIndex : 0 genreIndex : 0
10-29 16:41:52.861 21068 21068 D SAEffectManager: set UHQ-Upscaler as : 0
10-29 16:41:52.870 21068 21068 E SAEffectManager: SAControlPanel Activity is Null
10-29 16:41:52.903 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:52.904 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:52.909 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:52.910 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:52.910 21068 21068 D SAEffectManager: *****updateSquareUIsetting()*****
10-29 16:41:52.910 21068 21068 D SAEffectManager: position: 40
10-29 16:41:52.910 21068 21068 D SAEffectManager: *****convPresetIndexToGenreIndex()***** presetIndex : 0 genreIndex : 0
10-29 16:41:52.922 21068 21068 D SAEffectManager: set UHQ-Upscaler as : 0
10-29 16:41:52.931 21068 21068 E SAEffectManager: SAControlPanel Activity is Null
10-29 16:41:53.370 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:53.371 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:53.421 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:53.423 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:53.427 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:53.428 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:53.428 21068 21068 D SAEffectManager: *****updateSquareUIsetting()*****
10-29 16:41:53.428 21068 21068 D SAEffectManager: position: 40
10-29 16:41:53.428 21068 21068 D SAEffectManager: *****convPresetIndexToGenreIndex()***** presetIndex : 0 genreIndex : 0
10-29 16:41:53.432 21068 21068 D SAEffectManager: set UHQ-Upscaler as : 0
10-29 16:41:53.442 21068 21068 E SAEffectManager: SAControlPanel Activity is Null
10-29 16:41:53.443 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:53.444 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:53.944 21068 21068 D SAEffectManager: *****getNewDolbyInstance start*****
10-29 16:41:53.945 21068 21068 E SAEffectManager: getNewDolbyInstance::RuntimeExceptionn - e : java.lang.RuntimeException: Cannot initialize effect engine for type: 46d279d9-9be7-453d-9d7c-ef937f675587 Error: -19
10-29 16:41:55.538 21068 21068 D SAEffectManager: set tube as : 0
10-29 16:41:55.539 21068 21068 D SAEffectManager: set hall as : 0
10-29 16:41:57.099 21068 21068 D SAEffectManager: set tube as : 0
10-29 16:41:57.099 21068 21068 D SAEffectManager: set hall as : 0


Device J7Nxt Rom Stock Oreo
 
  • Like
Reactions: Developing Zeus

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Samsung SoundAlive Dolby Atmos Lib Installer
Special Edition for GoogleWiz V87+ ONLY


This build has edited /etc/floating_feature.xml & /csc/feature.xml for highest compatibility and has the UHQ tile enabled.
The libs are further edited to be compatible with GoogleWiz V87+ build.prop edits

I flashed an edited ROM zip which has the edited floating_feature.xml & feature.xml already in it and then replaced the edited Dolby libs manually thereafter, made sure that it worked and put all the modification together into this zip.
That said, I didn't try to flash this zip, but I reckon it should work.


Update to the main lib installer will come once I figured out how to do dynamic edits to the xmls after my exam.
 

Attachments

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Ss attached
The libs need more modification for higher compatibility for non-Samsung phones, as it looked for ro.product.brand=samsung and ro.product.manufacturer=samsung.

I've edited the lib to workaround this, but it requires extra lines in your build.prop, see the updater-script in my special edition zip. Also, you have to use the new libs in that zip.

Can try if you are still interested in this.
 
  • Like
Reactions: vizhigal