Does anyone have a fully working DSPManager on XXEMB5? - Galaxy S III Q&A, Help & Troubleshooting

Hi!
Does anyone have a fully working DSPManager on XXEMB5?
There are so many different versions, but I can not find one that has no FC if changeing the presets. Rest seems to be working fine.
The version I used to have in XELLA and earlier seems not to be working anymore. It does not FC but has no effect at all.
Edit:
Found the solution.
I was using the file DSPmanager-v3.zip from this thread: http://forum.xda-developers.com/showthread.php?t=1636914
This is pretty much what I was using for months and it worked utill the last update to XEMB5.
So after sitting the whole night, trying out a dozen of different archives and mods, I noticed this one does not contain the /system/vendor/etc/audio_effects.conf file. I missed it, because there was already a file in my system with the same name. But now I looked inside it and found that it is a different file to the one that comes with DSPManager. So I renamed the file I had in my phone to audio_effects.conf.old (just in case) and copied /system/etc/audio_effects.conf to /system/vendor/etc/audio_effects.conf and, to my surprise, now (after a reboot) DSP manager works as it used to.
Yay!
So here the steps I did in clear:
1. Flash DSPmanager-v3.zip in CWM
2. Reboot
3. Copy /system/etc/audio_effects.conf to /system/vendor/etc/audio_effects.conf

Related

[Q] Making updater-script... doesn't make any sense!!

I was tying to make a fancy updater-script for an add-on for my ROM, but I kept getting a Status 6 error when flashing, so I stripped it back to nothing, just the most basic commands, and eventually got it to work. I made a copy, tried editing it to add the fancy stuff back in... broke again.
So I stripped the copy back to the basic commands... and it still breaks .
As far as I can see, the two files I have attached are identical in every single way, but one fails with a Status 6, the other flashes (BattMod works, update doesn't). Both are edited using gedit on Ubuntu, both zips are created in Ubuntu, neither are signed.
Can anyone see why, I am really tearing my hair out here... all I want to do is add some ui_prints and some progress bars .
I haven't looked it them yet, but make sure you are using the correct update-binary. Different ones support different number of parameters in the mount command.
Don't leave junk files in the update like updater-script.old, it's bad practice
My guess would be that since it's named update.zip, it's looking for a signature and it can't find one. Try renaming update.zip to battmod.zip and see if it works, or sign it first with testsign.
l0st.prophet said:
I was tying to make a fancy updater-script for an add-on for my ROM, but I kept getting a Status 6 error when flashing, so I stripped it back to nothing, just the most basic commands, and eventually got it to work. I made a copy, tried editing it to add the fancy stuff back in... broke again.
So I stripped the copy back to the basic commands... and it still breaks .
As far as I can see, the two files I have attached are identical in every single way, but one fails with a Status 6, the other flashes (BattMod works, update doesn't). Both are edited using gedit on Ubuntu, both zips are created in Ubuntu, neither are signed.
Can anyone see why, I am really tearing my hair out here... all I want to do is add some ui_prints and some progress bars .
Click to expand...
Click to collapse
With what are you editing it?
I've found out that editing it with notepad or any program won't work even if i'm using the right commands, so i decided to use amend2edify, you select an update-script (an update-script you can edit it with notepad without any problem) and it converts it into updater-script, updater-binary, but you have the possibility to edit anything in the output that you want and save it, or just copy-paste into the output the commands in your updater-script onto output by overwriting the converted output.
Don't know if i explained myself well.
Good luck
Try This One
Blank-CWM.zip
It's made for the Moto Photon, so you will need to:
1) Replace the update-binary with one from your phone.
2) Copy the file you wish to flash
3) Delete the txt files in it as well as any folders that you do not need to use in the process of flashing
4) Be sure to set the permissions to target the folder or file you are flashing. If you do NOT update this, you will end up in bootloops (Don't say I didn't warn you)
5) Flash away
Cheers!

[In-Call Volume] **FIX** (Finally)

So after using the Samsung Galaxy S II for over a month now I've had one complaint. In-Call Volume using the handset ear piece. It was "OK" in quiet places but anywhere else...way below par.
So, after looking around for several weeks trying to find a fix I finally got help from a well know dev (Entropy512) as well as using system/lib audio files from Designgears ROM 'Perception'.
So...how do you finally get your in-call volume increased?
First and foremost...Always backup whatever you're changing. Better safe than sorry. Just make a copy of your current system/lib folder, rename it something like 'backup_lib' and place on your sd card somewhere.
Option 1
Download this flashable zip, flash it in CWM, Reboot, Enjoy. (This zip includes some audio files from the Perception ROM, if for any reason DesignGears has an issue with this PM me and I will remove the zip. I'm only using the files to help others solve their in-call volume issue)
MAKE A BACKUP BEFORE FLASHING
Download the Flashable Update Here
I have tested this on three different SGSII's and all seems well! This is a NO WIPE flash, I do reccomend clearing your Dalvik Cache and Cache Partition though.
-Reboot into Recovery
-Scroll down to 'Advanced' and select
-Select "clear Dalvik Cache"
-Flash this update
-Reboot your phone and enjoy!
Option 2 (Incase the flash doesn't work or I am asked to remove the the zip file)
1) Download Designgears ROM 'Perception' Found Here
2) Open the zip file of your current ROM (doesn't matter what ROM)
3) Open the system folder and then open the system/lib folder (of your current ROM)
4) Next, Open the same folder in the Perception ROM
5) Copy the files listed below from the Perception ROM and paste them over the files in your ROM:
- lib_Samsung_Acoustic_Module_Llite.so
- lib_Samsung_Resampler.so
- lib_Samsung_Sound_Booster.so
- libaudio.so
- libaudioeffect_jni.so
- libaudioflinger.so
- libaudiohw_op.so
- libaudiohw_sf.so
- libaudiopolicy.so
- liblvvefs.so
- libmediayamaha.so
- libmediayamaha_jni.so
- libmediayamaha_tuning_jni.so
- libmediayamahaservice.so
- libsamsungAcousticeq.so
- libsamsungSoundbooster.so
- libsoundalive.so
- libsoundpool.so
- libSR_AudioIn.so
- libyamahasrc.so
*Only copy/replace the files listed above as they are only audio files. DO NOT COPY/REPLACE all system/lib files... You'll have unwanted consequences and you'll probably kill a puppy.
6) Now go to the Perception ROM and open system\app and find phone.apk. (Save a copy of your current phone.apk...Just in case)
-Copy (Perception's) phone.apk and replace the phone.apk on your current ROM.
7) After you replace the files listed above on your ROM, reflash your ROM and enjoy your increased call volume.
Note: If you don't want to reflash your ROM and risk losing any settings, you should be able to copy the files and replace them with Root Access and a file explorer, then Reboot your device immediately after. I haven't tried this yet so if someone wants to try and leave feedback, please feel free.
EDIT: Copying the files using a root explorer does work but may cause your phone to crash/reboot afterwards. I'd still recommend just re-flashing the ROM to avoid potential issues. Once again, make sure and make a back up so you can revert any changes if something doen't work properly.
I will try uploading a zip file with appropriate files so you can download but currently I do not have Designgears permission. This is their code and I don't want to step on any toes.
EDIT: I have tried reaching out to DG for permission but had no luck, if he asks that I remove the zip file, I will do so.
Known Potential Issues:
- When flashing over a stock/rooted ROM this update may cause the phone application to crash/force close. I have tried this update personally on every ROM I could flash and haven't had any issues. However, I have not tried it on the stock ROM. If you're on stock/rooted, please make a backup so if it does cause issues you can simply revert the changes.
Much thanks goes to Entropy512 for the help with solving this issue and Designgears ROM 'Perception'. Using Perception showed me that increasing the in-call volume was possible! (it's a very stable and awesome ROM as well )
***UPDATE***
Due to some people being a worried about flashing the update I have taken the liberty of making the backup files for you and making them flashable!
- I have made revert files for all of the major ROM's we currently have for our device. I did not include Perception because that ROM is where the audio files originated from. Below is the download links for the backups.
IF my volume fix does NOT work, simply download the backup for your ROM and flash it. It will revert all the changes my fix made.
- Revert_CM7.1_Stable
- Revert_H8s2_1.2.2
- Revert_Serendipity_8.2
- Revert_Stock_UCKH7
- Revert_UnNamed_1.2
- Revert_MIUI 1.11.4 v1
- If you are using Perception ROM you do NOT need the volume fix as this ROM has the files built in
As a side note, I have tried this on several I9100 ROM's as well and had luck with them all.
If this thread helps, please click the thanks button for me, I'm new to the XDA community.
Any I9100 ROM should work here for the libs - however:
Your mic will be screwed up for outgoing audio unless you change the Samsung Noise Reduction settings. (DG forced this in Perception, I believe he did it in an APK somewhere and not in the libs.)
Entropy512 said:
Any I9100 ROM should work here for the libs - however:
Your mic will be screwed up for outgoing audio unless you change the Samsung Noise Reduction settings. (DG forced this in Perception, I believe he did it in an APK somewhere and not in the libs.)
Click to expand...
Click to collapse
I just tried a call and you're correct, the mic isn't working properly. Do I need to find the APK or do you know what changes I need to make? This is a popular issue and I'm hoping this thread can help.
Edit: I found some APK's....any idea which one would deal with the mic?
-CallSetting.apk
-Phone_Util.apk
-Phone.apk
-Settings.apk
Ahahaha, good thing I made a backup before pasting, but pasting the files in root explorer does work, however your phone will crash and reboot, but it is louder.
Doesn't work on the apk :v
penguinlogik said:
Ahahaha, good thing I made a backup before pasting, but pasting the files in root explorer does work, however your phone will crash and reboot, but it is louder.
Click to expand...
Click to collapse
I'm testing different apk's right now. As soon as I figure out which apk the fix is located in I'll edit the post.
Maybe DG can drop a hint to me
Hmm does this enable the AUDIO part of the Samsung Service mode?
penguinlogik said:
Hmm does this enable the AUDIO part of the Samsung Service mode?
Click to expand...
Click to collapse
I haven't tried the audio menu yet, feel free to try if you'd like and let me know. 2 birds 1 stone.
Nope... ATT WHY YOU DISABLE THE MOST IMPORTANT MENU.
penguinlogik said:
Nope... ATT WHY YOU DISABLE THE MOST IMPORTANT MENU.
Click to expand...
Click to collapse
I figured out which apk fixes the mic issue it's the phone.apk. I updated the original post. Sorry for the set back. Let me know if you experience any issues
Just posting another screenshot to show the phone.apk.
penguinlogik said:
Ahahaha, good thing I made a backup before pasting, but pasting the files in root explorer does work, however your phone will crash and reboot, but it is louder.
Doesn't work on the apk :v
Click to expand...
Click to collapse
Try copying the CallSetting.apk as well (use both). If you still don't have any luck with fixing the mic issue and you're using a file manager to make the switch, try re-flashing your ROM with the apk changes instead.
Make a backup before doing it so you can restore all your settings if it doesn't work for some reason.
It works after I replaced it in my ROM zip
Sent from my SAMSUNG-SGH-I777 using xda premium
penguinlogik said:
It works after I replaced it in my ROM zip
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Did you have to re-flash? Just trying to make sure my instructions are correct.
Did you need to add both apk's as well?
No, I just added replaced the files in the Unnamed 1.1.0 full update zip, ran an update via CWM, with only the phone.apk and microphone works.
penguinlogik said:
No, I just added replaced the files in the Unnamed 1.1.0 full update zip, ran an update via CWM, with only the phone.apk and microphone works.
Click to expand...
Click to collapse
Ok, glad it works and the kinks are worked out thanks for you patience and tests.
Thats awesome news. Low mic has always been an issue for me. Just wondering if someone can create a flash able zip that automates everything, if possible.
Great work guys.
daraj said:
Thats awesome news. Low mic has always been an issue for me. Just wondering if someone can create a flash able zip that automates everything, if possible.
Great work guys.
Click to expand...
Click to collapse
IF I can get approval from Designgears to use some sources from his ROM I shouldn't have any issues putting this into a zip file for everyone. I've reached out to DG, just awaiting a response
Great keep us posted please. It will make a big difference to many people
Sent from my SAMSUNG-SGH-I777 using XDA App
crazyagg said:
IF I can get approval from Designgears to use some sources from his ROM I shouldn't have any issues putting this into a zip file for everyone. I've reached out to DG, just awaiting a response
Click to expand...
Click to collapse
Excellent! Been looking for something like this, because I also noticed that the volume was really horrible... Keep us posted on a zip file. Rather be "SAFER" than sorry with doing something that does it automagically for me
Knowing my patience, I'll probably manually do it once I get home from school... lol
SpectraDawn said:
Knowing my patience, I'll probably manually do it once I get home from school... lol
Click to expand...
Click to collapse
LOL! Me too! I all over this!

[Q] question on removing a2sd scripts

Thanks to the limits on new accounts, I cant post this in the relevant thread, so...
I recently used http://forum.xda-developers.com/showthread.php?t=1716124&page=73 on a new rom flash for the admire.
I found I had no gps, so I reflashed my phone then installed the gps fix script. Seemed like it worked, so I went about spending 6 hours tweaking my phone over the day.
Gps is gone again - not sure if maybe cell phone tower setting was turned on in locations tab and maybe got apps to work without it, but whatever the reason this script doesnt work for me.
The thread states that to flash one of the scripts in that doesnt have a gos issue, i need to uninstall the prior script.
How do I go about that without flashing my phone again and losing tons of work?
Do I have to look at the script and manually go in and delete every file it created and unalter every script it changed then reflash the new script?
Help?
Asking in your devices forum could be better.
But in general, yes, take a look at the zip you flashed. Inside META-INF/com/google/android you'll find an updater-script file that can be opened as text and tells you where everything inside the zip got flashed to.
Generally, scripts that run at boot get flashed to system/etc/init.d
Use a root explorer to locate the init.d address, or the name of the files that you saw inside the zip.

[Q] Wifi Problem with Korean Tab (SHW-M380W) after 7510 conversion

Hi Everyone!
I'm posting this here since I don't have posting privileges in the development area.
I have converted my Korean Galaxy Tab 10.1 as explained in the development section in this thread:
http://forum.xda-developers.com/showthread.php?t=1360588&page=5
to a 7510.
Everything worked fine.
Just one tiny problem I am experiencing:
My Wifi reception has greatly decreased after the conversion.
I noticed this imediately after the conversion but hoped it would "go away" once I had rooted the Tab an installed a modded ROM.
Unfortunately this was not the case.
Does anyone of you other "converters" have any experience with this problem or am I the only one?
best regards an looking forward to your answers
Krügge
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
kruegge99 said:
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
Click to expand...
Click to collapse
i have same problem with you. can you please explain to me step by step how to fix the wifi like you did?
Hi Everyone!
I have done some more experimenting.
Since I wanted to install different Android Versions and different Kernels and the fact that the Kernel Drivers are always compiled to work with only one particualer Kernel, I needed to find a way to improve Wifi reception without having the korean drivers.
I acomplished this by just pasting the config file nvram_net.txt from the korean Android into the directory /system/etc/wifi.
I renamed the original file to nvram_net.txt.orig and pasted, Afterwards I adjusted the permissions to be the same as the ones of the original file and rebooted.
This has worked with every Android Version I installed so far.
I have attached a Screenshot of the directory and the nvram_net.txt file of the korean tab.
I hope I can help somone with this.
To me it seems that the korean tab has just a slightly different Wifi Hardware than the P7510.
best regards
Krügge

[Q] replacing modem.img within custom ROM (zip) --> (both) SIMs offline

After lots of reading XDA and using the many tweaks and fixes one can find here (thanks!) I ran into a problem I can't seem to solve.
I'm modifying a custom ROM (by www.jiayu.es --> version 20131203-000001) for the Jiayu G4B (basic 1/4 3000mah) for use in the Netherlands. I already applied some fixes (GPS-fix, APN-settings, SMS-fix, add some APKs) and created a flashable zip file for use with CWM (thanks to dsixda kitchen).
One thing I can't seem to implement is the replacement of modem.img (in system/etc/firmware) with an updated version that fixes frequent drops of the connection to the network. This fix is documented on the dutch site tweakers.net.
The original fix is quite simple: you just replace modem.img (using a file explorer) with the updated one, straighten out the file permissions and reboot the phone. The thing is I don't want to have to do this manually everytime I flash a new ROM, and furthermore it's fun to learn how to customize my own ROM.
So I thought I could just replace modem.img in my working folder with the newer one and be done with it. Problem is that after I flash the ROM containing the new modem.img both my sims remain offline and the only way to go online again is by restoring a CWM backup.
I already checked the file permissions and they are correct. Unfortunately google also couldn't help me find the answer. Does any here have an idea how to solve this?
matthijsph said:
After lots of reading XDA and using the many tweaks and fixes one can find here (thanks!) I ran into a problem I can't seem to solve.
I'm modifying a custom ROM (by www.jiayu.es --> version 20131203-000001) for the Jiayu G4B (basic 1/4 3000mah) for use in the Netherlands. I already applied some fixes (GPS-fix, APN-settings, SMS-fix, add some APKs) and created a flashable zip file for use with CWM (thanks to dsixda kitchen).
One thing I can't seem to implement is the replacement of modem.img (in system/etc/firmware) with an updated version that fixes frequent drops of the connection to the network. This fix is documented on the dutch site tweakers.net.
The original fix is quite simple: you just replace modem.img (using a file explorer) with the updated one, straighten out the file permissions and reboot the phone. The thing is I don't want to have to do this manually everytime I flash a new ROM, and furthermore it's fun to learn how to customize my own ROM.
So I thought I could just replace modem.img in my working folder with the newer one and be done with it. Problem is that after I flash the ROM containing the new modem.img both my sims remain offline and the only way to go online again is by restoring a CWM backup.
I already checked the file permissions and they are correct. Unfortunately google also couldn't help me find the answer. Does any here have an idea how to solve this?
Click to expand...
Click to collapse
So did you ever find the solution to this problem??? Did it involve taking the battery out immediately after you flash the ROM with the desired modem.img?
No it was never solved, I gave up after a while.
I don't have the phone anymore, so I can't test your solution.
matthijsph said:
No it was never solved, I gave up after a while.
I don't have the phone anymore, so I can't test your solution.
Click to expand...
Click to collapse
having that kinda problem, thinking to replace system.img 1st with push adb, then use dd if=...of=.. not sure if gonna work

Categories

Resources