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

I

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Nov 27, 2018 at 7:53 AM
BaljitTech said:
I have the stereo speaker mod, that's why I use it. I think the battery has to do with some other mods, not sure which. But do you happen to know about the sound boosters? I thought they were responsible for the cracky sound, since I now have the 700, 810 and 900 but can't delete them.
Click to expand...
You can restore soundfx/libsamsungSoundbooster_plus.so and your original version of soundbooster and delete all other versions as depending on the version of libsamsungSoundbooster_plus, only one will be used.

EDIT
*Or use the latest magisk module as it contains only the bare minimum files that are required for Dolby Atmos and nothing else.
 
Last edited:
S

SilentWorld

Senior Member
Nov 6, 2018
183
107
0
Nov 27, 2018 at 8:54 AM
ImbaWind said:
You can restore soundfx/libsamsungSoundbooster_plus.so and your original version of soundbooster and delete all other versions as depending on the version of libsamsungSoundbooster_plus, only one will be used.

EDIT
*Or use the latest magisk module as it contains only the bare minimum files that are required for Dolby Atmos and nothing else.
Click to expand...
Thanks! I can't use the latest one because it has device checking and I am on s7 edge
 
F

four ruttrawit

Member
Feb 25, 2018
31
15
0
Dec 1, 2018 at 10:38 AM
ImbaWind said:
Your mod combination looks complicated there, I'd recommend you to double check if every required files and edits are in place
Click to expand...
I checked everything and it was in right place, and build prop , it still not working and I try to use the patched lib and still not working. Same thing appear in terminal like before after type logcat | grep SAEffectManager [cant intialize effect] any suggestion? (I try disable all module once and still not working.)
 
I

ImbaWind

Senior Member
Jul 12, 2011
1,774
3,895
143
?
Dec 2, 2018 at 1:42 AM
four ruttrawit said:
I checked everything and it was in right place, and build prop , it still not working and I try to use the patched lib and still not working. Same thing appear in terminal like before after type logcat | grep SAEffectManager [cant intialize effect] any suggestion? (I try disable all module once and still not working.)
Click to expand...
If you are using my mod (1.5.1), the zip already has the patched libs that includes all the edits you need to use Dolby on a non S9+ Samsung phone, so I'm not sure why you'd say this:
... I try to use the patched lib ...
Click to expand...
Make sure you didn't change your build.prop ro.product.manufacturer and ro.product.brand to something else other than 'samsung'

Your situation sounds like 2 previous guys (1-2 pages before) who also had this problem.
The first one I have no idea how he 'installed' and 'checked' the installation but he got it working after following another post, which does the exact same thing that my installer zip supposed to do.

The second guy used the Magisk module which is not exactly the same as my mod and replaced some of the system drivers/files and caused some issues.

Which means I haven't been able to isolate a case where a Samsung device with an Exynos processor is used and isn't able to use the mod, what I'd recommend you is:
1: Check if all the edits are really in place, if true:
2: Check again, still no go?
3: Check once more, still no go?
4: Try to edit the files manually and place, replace, delete the modded files manually according to this test zip
- Manually edit your floating_feature.xml, build.prop, you may read this as ref
- Replacing audio_effect.conf should be fine, but would be better if you know how to manually edit yours
- You can skip the csc files
- Other necessary libs and files
5: If still no go? Try to flash the attached zip in this post.
 
  • Like
Reactions: four ruttrawit
F

four ruttrawit

Member
Feb 25, 2018
31
15
0
Dec 2, 2018 at 3:54 AM
ImbaWind said:
If you are using my mod (1.5.1), the zip already has the patched libs that includes all the edits you need to use Dolby on a non S9+ Samsung phone, so I'm not sure why you'd say this:


Make sure you didn't change your build.prop ro.product.manufacturer and ro.product.brand to something else other than 'samsung'

Your situation sounds like 2 previous guys (1-2 pages before) who also had this problem.
The first one I have no idea how he 'installed' and 'checked' the installation but he got it working after following another post, which does the exact same thing that my installer zip supposed to do.

The second guy used the Magisk module which is not exactly the same as my mod and replaced some of the system drivers/files and caused some issues.

Which means I haven't been able to isolate a case where a Samsung device with an Exynos processor is used and isn't able to use the mod, what I'd recommend you is:
1: Check if all the edits are really in place, if true:
2: Check again, still no go?
3: Check once more, still no go?
4: Try to edit the files manually and place, replace, delete the modded files manually according to this test zip
- Manually edit your floating_feature.xml, build.prop, you may read this as ref
- Replacing audio_effect.conf should be fine, but would be better if you know how to manually edit yours
- You can skip the csc files
- Other necessary libs and files
5: If still no go? Try to flash the attached zip in this post.
Click to expand...
How to edit audio_effect.con which line should I add?
 
S

SilentWorld

Senior Member
Nov 6, 2018
183
107
0
Dec 2, 2018 at 8:48 AM
ImbaWind said:
If you are using my mod (1.5.1), the zip already has the patched libs that includes all the edits you need to use Dolby on a non S9+ Samsung phone, so I'm not sure why you'd say this:


Make sure you didn't change your build.prop ro.product.manufacturer and ro.product.brand to something else other than 'samsung'

Your situation sounds like 2 previous guys (1-2 pages before) who also had this problem.
The first one I have no idea how he 'installed' and 'checked' the installation but he got it working after following another post, which does the exact same thing that my installer zip supposed to do.

The second guy used the Magisk module which is not exactly the same as my mod and replaced some of the system drivers/files and caused some issues.

Which means I haven't been able to isolate a case where a Samsung device with an Exynos processor is used and isn't able to use the mod, what I'd recommend you is:
1: Check if all the edits are really in place, if true:
2: Check again, still no go?
3: Check once more, still no go?
4: Try to edit the files manually and place, replace, delete the modded files manually according to this test zip
- Manually edit your floating_feature.xml, build.prop, you may read this as ref
- Replacing audio_effect.conf should be fine, but would be better if you know how to manually edit yours
- You can skip the csc files
- Other necessary libs and files
5: If still no go? Try to flash the attached zip in this post.
Click to expand...
Mine actually works fine now, even got the speakers working, but I am not sure what this is and why it is sucking battery
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone