I have searched this but can't find my particular issue. I just flashed CM7 (previously had bionix). I followed the instructions on the CM7 wiki and all works smoothly and fine except in call volume.
It is extremely loud when I make/receive a call. When I adjust the volume it adjusts to what it is set to. How do I set the in call volume or solve this issue?
This may work with CM7's stock kernel. But I do know that if you flash a custom kernel like Glitch for say, then you could download a Call Script... http://androtransfer.com/fascinate/90call_vol.zip... With this file you can tweak all the call volumes to your liking.
Instructions (if you have Glitch kernel running):
1. Download the Call Script.zip
2. Extract the .zip
3. Move the file to your phone's internal SD card
4. In Root Explorer hit the "Mount R/W" button
5. Still in Root Explorer move the 90call_vol from the /sdcard to /etc/init.d
6. After it has been pasted into the init.d folder long press on the 90call_vol file and hit "Open in text editor".
7. Once the file is opened, the file will take you through the rest of the steps.
8. Once you have tweaked the settings in the file do a reboot and test out your phone. It may take a bit to find the perfect balance but with a little patience you will .
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
sokey70 said:
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
Click to expand...
Click to collapse
I was having the same issue on Glitch. Even if you're not on Glitch, I suggest flashing another kernel.
Sent from my SGH-T959 using xda premium
sokey70 said:
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
Click to expand...
Click to collapse
No problem. But did you try these steps w/ the Glitch kernel (because I don't think the stock CM7 kernel supports Call Script)? I was having the exact same issue and the Call Script fixed the issue for me. I'll upload my Call Script (already tweaked) in a few. In the mean time I would suggest you look into Glitch, much better then the stock kernel in terms of battery, stability, and color. Plus it will allow you to fix the horrible loud distortion present in CM7.
Yes, I installed Glitch and edited the file as explained and still had the issue. even a screen of your file would be good, I tried all different settings from 0-3 and each started off way loud and then when I adjusted the volume it went to where it was supposed to be.
each time you edit the script, you want to reboot the phone for the settings to take effect. also, make sure all permissions are checked by longpressing on the script using root explorer, select permissions and check all selections.
with glitch kernel, set all incall boost to 0. the highest would be 1. settings 2 and 3 cause distortion. in any other kernel, i've found setting 3 is the same as setting 1 in glitch.
This worked perfectly for me! Glitch kernel on MIUI SGSII rom.
Thanks!
Se7eN43 said:
each time you edit the script, you want to reboot the phone for the settings to take effect. also, make sure all permissions are checked by longpressing on the script using root explorer, select permissions and check all selections.
with glitch kernel, set all incall boost to 0. the highest would be 1. settings 2 and 3 cause distortion. in any other kernel, i've found setting 3 is the same as setting 1 in glitch.
Click to expand...
Click to collapse
Question....I can't get this to work. I notice in the file it says, "just be sure you do the chmod and chown commands below in any case." I think that's the piece that people are missing, and I can't seem to figure that out. I tried to go into terminal emulator and say
Code:
chmod -R 750 /etc/init.d/
and
Code:
chown -R root:shell /etc/init.d/
...but for both commands, I get that the operation is not permitted. I think this is what is causing my changes to not apply correctly, and I can't seem to figure out how to do these two commands. Both the etc and init.d folders are set to r/w/x, as well as the file itself
Are these commands extremely necessary and if so, what can i do to more easily make them work?
Perhaps someone would be so awesome as to create a flashable script for linux dummies like myself?
jakemg said:
Question....I can't get this to work. I notice in the file it says, "just be sure you do the chmod and chown commands below in any case." I think that's the piece that people are missing, and I can't seem to figure that out. I tried to go into terminal emulator and say
Code:
chmod -R 750 /etc/init.d/
and
Code:
chown -R root:shell /etc/init.d/
...but for both commands, I get that the operation is not permitted. I think this is what is causing my changes to not apply correctly, and I can't seem to figure out how to do these two commands. Both the etc and init.d folders are set to r/w/x, as well as the file itself
Are these commands extremely necessary and if so, what can i do to more easily make them work?
Perhaps someone would be so awesome as to create a flashable script for linux dummies like myself?
Click to expand...
Click to collapse
You don't need to use Terminal Emulator. It's 100.1% easier to use Root Explorer. Here's what to do. These are similar to the steps I posted above, but I simplified it to make it easier for yah...
Instructions (While on Glitch):
1. Download the 90call_vol (To make it easier use mine which is already configured)
2. Move the file from your PC to your phone's internal SD card
3. In Root Explorer hit the "Mount R/W" button
4. Still in Root Explorer move the 90call_vol from the /sdcard and paste it into /etc/init.d
5. Now the most important step... REBOOT
6. Done! Now test your device
Yep, that's exactly what I was doing and still, when I make or receive a call, the in-call volume jumps up to max unless I turn it down. T. Then if I make or receive another call, the in-call volume jumps back up again. This cycle constantly repeats itself. No matter what, the actual in-call volume keeps jumping up to max.
Thanks for trying, though.
And you're on the Glitch kernel right?
Yep. Glitch V13...
Boo. First off thanks for the help and guide but unfortunately it does not work for me. I've tried this twice now on cm7 and miui fresh installs. Neither worked and I followed the steps exactly. Man this is lame. Is there a previous version of either miui or cm that doesn't have this issue?
N00B_IN_N33D said:
You don't need to use Terminal Emulator. It's 100.1% easier to use Root Explorer. Here's what to do. These are similar to the steps I posted above, but I simplified it to make it easier for yah...
Instructions (While on Glitch):
1. Download the 90call_vol (To make it easier use mine which is already configured)
2. Move the file from your PC to your phone's internal SD card
3. In Root Explorer hit the "Mount R/W" button
4. Still in Root Explorer move the 90call_vol from the /sdcard and paste it into /etc/init.d
5. Now the most important step... REBOOT
6. Done! Now test your device
Click to expand...
Click to collapse
This did not work for me.....
You all are selecting ALL permissions in the script with the script in the /system/etc/init.d folder correct? the permissions must be done while the script is in the init.d folder. If you make the permissions before moving the script over to the init.d folder, it will not work. It should look like rwxrwxrwx (Read Write eXecute) for the User, Group & Other fields.
How do get to the permissions? I didn't see that. Also, does anyone have a link to the original cm7 kernel to replace glitch if it doesn't work again?
Never mind. Got the permissions set and it still starts out loud, this is ridiculous.
wow... sounds like your phone just doesn't like you. haha.. kidding.
another thing you can do is use Script Manager from the Market.
run script manager
navigate to script (doesn't matter what folder the script is in)
select script (window pops up)
select "Su" (android skull & bone crosses icon)
select "Edit"
select "File Editor" (make sure the settings are what you want)
press the phones menu button to save (you may be asked to save again when pressing the back button to go one screen back, of course save it again.)
select "Run" (window changes)
select "Close"
you need not to reboot or set permissions using Script Manager, so go ahead and test.
if this works, you need to set the script to run at every boot using Script Manager by selecting the script again and select "Boot" (gear looking icon) and run again. (Su should still be selected as well)
if you end up tweaking the script again, just select "Run" after you are done editing, then "Close". no need to reboot.
IF this too does not work, then you might want to try a fresh install of CM7+Glitch without any other extras, besides the script just for testing. and if you are not on the latest CM nightly, i suggest you update to it.
Boo, my phone does hate me! It must know that I want a Galaxy 2 lol. Well I tried the script manager and it didn't improve. Right now I am on MIUI and like it but could try the CM7. Both ROMs with glitch 13 gave me the same issue. I wonder if my speaker is messed up or somethingm although previously on bionix it was okay...
Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
Before I start, I'm not sure if this is know or whatever, but I wanted to contribute it anyway. So yeah.
There's a vid on the bottom showing the results.
So I ran into a really cool mod for our TPs. I found that I was able to change all the system sounds on the ICS rom. I was able to replace the default system sounds with custom sounds of my own. I ran into this idea when I was replacing the system sounds on my laptop's OS (Windows 7). And I thought, hey, why I couldn’t do this with my TP. So I began my research here and various places in search of custom sounds that others had used. I found none mainly because I cut my search short. Anyway, I replace several SS (system sounds) with really cool, IMO, sound effects and synthesize speech. For instance, my lock and Unlock system sounds. My "Lock" sound, this is when you push the power button to allow the TP to sleep of shutdown, has been switched from a "Click" sound effect to a synthesize speech saying "Good bye." The same goes for my "Unlock" sound, which is now "Welcome." I also switch the "tick" sound with a single water drop sound effect and “Notification sound” to a speech synthesis saying “Your Attention is required”. You’ll find all of them attached to this thread. AND IF YOU HAVE ANY CUSTOM SOUND EFFECTS PLEASE POST THEM HERE!! I'D LOVE TO HEAR THEM!!!
It's really neat IMO. Anyway, you can do this too and here's how:
Disclaimer: I will not be responsible for any harm or damage that you may cause to your device. Proceed at YOUR OWN RISK.
Requirements: Must have rooted device.
Things you'll need before you start:
•Desired sound effects. You can use the one I supplied if you like or you can use your very own.
•An audio converter. There are tons of free audio converters out there. TONS. I used Switch Sound File Converter. It’s free and incredibly fast.
•A root explorer app. It must be able to access, read, and write system files. Root Explorer is perfect.
• BACK UP YOUR DEVICE. You don’t have too but I don’t want to hear crap.
Installation:
1. Download your desired sound effects.
2. Convert, if not already, these sound effects to an “.ogg” file. With Switch Sound File Converter, simply drag and drop selected files into the “add files” box of the program. Then, on the bottom left of the window there is an “Output Format” field. Select .ogg in that box.
Explanation: We must convert to an .ogg file because it is the only kind of file android recognizes in the system folders.
3. Compile all newly converted sound effects into a folder and name it whatever you like. Something you can remember. Now drag and drop it to the root of your device. We just need it to be somewhere where we can access it quickly.
So at this point you should have the folder that contains all the converted sound effects in a folder in the root of your device.
4. Now with your *Root* File Explorer, navigate to the folder containing all the converted .ogg files. Choose one to begin with. I’ll switch up my “Lock” system sound with a speech synthesis saying “Good bye”
5. Select and long hold the desired sound effect.
6. Select the “Copy” option
7. Now navigate to the system folder. You’re going to have to push back several times to get to that folder. This is the path: system>media>audio>ui
8. Now paste the file to this folder.
9. Okay. Now we must rename that file we just pasted to the one we want to replace. In this instance we’ll be replacing the “Lock” file.
• To avoid troubleshooting, rename the file to “Lock1.ogg.” Do not forget that “1.” I did this because I didn’t know how the ROM would react to two files in the system with the same name. I basically did it to be safe.
• And Spell it out exactly how the original file is spelt.
So now we have the original file and the pasted file. Do whatever you desire to the original file. Delete it. Copy it to back it up. I don’t care. Just remove it from this folder.
10. Now rename the file currently named “Lock1.ogg” to just “Lock.ogg” without the “1.”
11. Now we have to set permisions. To do that, press and hold the system sound file that we just renamed. Select "Permissions." Make sure that the only ones that are check are the entire "Read" column and in the "Write" column the user should be check marked. It should look like an upside down L.
Explanation: We cannot simply use a file with a random name because the Android OS only recognizes these specific tittles or descriptions. Trust me; I have tried many times in the “notifications” folder. I thought it was just a drag and drop thing. Boy was I wrong.
12. Now test it by pushing the power button. If you don’t hear the custom sound effect, try doing a hotboot and try again.
In addition, you can use these sound effects on your PC. Of course you'd have to use the original files and not the converted ones. But they work all the same. I've replaced most of my PC system sounds with these.
Again, Please post your custom sound effects if you have any! I'd really like to hear all of them.
RESULTS
Thanks. I was searching for how to set the permissions. It worked perfectly on my Galaxy S on AOKP ICS rom
disclaimernotice said:
Thanks. I was searching for how to set the permissions. It worked perfectly on my Galaxy S on AOKP ICS rom
Click to expand...
Click to collapse
Don't mention it pal.
More sounds
In regards to more sounds/notifications this site has literally thousands, all in mp3 so need to be converted http://soundjax.com/ . I use " Captain incoming message" just search Worf , for my E-mail notification .
Hope you find it useful.
A quick question. How does one disable the CD ROM pop-up that appears when connecting the phone? I tried using the same code as on the original Incredible (##7764726), and while it does take me to the same feature editor and I can select CD ROM option and do "disable", it reverts to "enabled" immediately.
Thanks in advance!
PS If anyone knows how to move apps onto an external SD Card?
Boris1M said:
A quick question. How does one disable the CD ROM pop-up that appears when connecting the phone? I tried using the same code as on the original Incredible (##7764726), and while it does take me to the same feature editor and I can select CD ROM option and do "disable", it reverts to "enabled" immediately.
Thanks in advance!
PS If anyone knows how to move apps onto an external SD Card?
Click to expand...
Click to collapse
you ll need root and access to /system/
nitsuj17 said:
you ll need root and access to /system/
Click to expand...
Click to collapse
I do have that. Would you happen to have instructions how to get rid of it?
Thanks!
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
*Madmoose* said:
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
Click to expand...
Click to collapse
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
ceayuso said:
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
Click to expand...
Click to collapse
hmmm ##PROGRAM# does nothing for me.
The ##PROGRAM## worked for me and gave me the menu, but no matter how many times i set the cdrom to disabled it never changes, just remains enabled.
Void4ever
ceayuso said:
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
Click to expand...
Click to collapse
I'm with void4ever. Dialing the ## code was the first thing I did, just like on old Inc. I see the menu, but the change to CD ROM setting does not stick. It reverts to Enabled as soon as I hit OK on the selector...
you go to system/etc/ and remove (or re-name to .bak) CDROM.ISO
*Madmoose* said:
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
Click to expand...
Click to collapse
Thanks! That worked. Not quite the way I like to make config changes, but as long as it works.
So I know many of you enjoyed using this amazing mod in the past and something in our builds caused it to break after 4.3.1 roms started rolling out. Look no further as i have a fix for you that is guaranteed to work again.
Step 1.) For the first step you will need to edit your build.prop file found in /system folder. Personally i use Rom Toolbox lite (found here https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en) as it comes with a built in build.prop editor and root browser and it is free. Some of these edits may already be in your build.prop so check the edits posted below to see if they are already there or just need a slight change before just adding it as having 2 of the same edits with a different value may conflict with eachother
the edits are:
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
it may ask to reboot on some or just one of these but we can skip rebooting for now. once set we can now move forward.
Before starting the next step MAKE SURE YOU REMOVE AND UNINSTALL DSP MANAGER. you can do so via app manager in ROM Toolbox Lite.
Step 2.) Now we download viper4android according to your rom version. For 4.3.1 roms get this one https://play.google.com/store/apps/details?id=com.vipercn.viper4android4x&hl=en
Once downloaded and installed you will now have to copy and paste it from /data/app to system/app. When it finishes copying over delete the app from /data/app as it will not work otherwise. Make sure permissions are properly set to rw-r--r-- or 0644 in numerical terms. Rom Toolbox will make this whole process easier and faster.
At this point you will now reboot your device for the next step
Step 3.) Once rebooted open the app and it will have you install its driver Select cortex A8 option (3rd one down). It will ask to reboot but dont do it yet. Last thing to do is while in viper4android app hit the sttings button and you will see a long list of things. Select FX Compatible Mode and switch from Normal to Compatible mode and now you reboot for it to take effect and work.
After this you are all set to start setting your sound otions in viper4android and enjoy
I Give great Thanks to:
@zhuhang for making this great app/mod
@jrummy for creating rom toolbox (another amazing app)
@Bradl79 for the build.prop idea
@bbgreen for confirming this works
And Anyone else i may have missed
If i have PM me and ill gladly add them in
So far for the headset option i have the following enabled and set
Under MASTER POWER:
Enable V4A-FX is checked and powered on
Under FIREQUALIZER:
Enabled is checked and powered on
Select Preset is set to Rock
Under DYNAMIC SYSTEM:
Enable is checked
Select Listening Device is set to Common Earphone (v2)
Select Dynamic Bass is set to 2 percent
Under FIDELITY CONTROL:
Enable ViPER Bass is checked
Select Bass Mode is set to Natural Bass
Select Bass Frequency is set to 100Hz
Enable ViPER Clarity is checked
Select Clarity Mode is set to XHiFi
Select Clarity is set to 3.5 db
thats all i have set for now but i'm using skullkandy heaphones with this setup will vary for other headphone brands and models. with this setup it gets very loud and clear as well as amazing bass so dont damage your eardrums lol
Other aidio profiles can be found here by scrolling down to second post http://forum.xda-developers.com/showthread.php?t=2324454&highlight=viper4android
Thanks @sixcarnage for posting that as well
REV3NT3CH said:
So I know many of you enjoyed using this amazing mod in the past and something in our builds caused it to break after 4.3.1 roms started rolling out. Look no further as i have a fix for you that is guaranteed to work again.
Step 1.) For the first step you will need to edit your build.prop file found in /system folder. Personally i use Rom Toolbox lite (found here https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en) as it comes with a built in build.prop editor and root browser and it is free. Some of these edits may already be in your build.prop so check the edits posted below to see if they are already there or just need a slight change before just adding it as having 2 of the same edits with a different value may conflict with eachother
the edits are:
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
it may ask to reboot on some or just one of these but we can skip rebooting for now. once set we can now move forward.
Before starting the next step MAKE SURE YOU REMOVE AND UNINSTALL DSP MANAGER. you can do so via app manager in ROM Toolbox Lite.
Step 2.) Now we download viper4android according to your rom version. For 4.3.1 roms get this one https://play.google.com/store/apps/details?id=com.vipercn.viper4android4x&hl=en
Once downloaded and installed you will now have to copy and paste it from /data/app to system/app. When it finishes copying over delete the app from /data/app as it will not work otherwise. Make sure permissions are properly set to rw-r--r-- or 0644 in numerical terms. Rom Toolbox will make this whole process easier and faster.
At this point you will now reboot your device for the next step
Step 3.) Once rebooted open the app and it will have you install its driver Select cortex A8 option (3rd one down). It will ask to reboot but dont do it yet. Last thing to do is while in viper4android app hit the sttings button and you will see a long list of things. Select FX Compatible Mode and switch from Normal to Compatible mode and now you reboot for it to take effect and work.
After this you are all set to start setting your sound otions in viper4android and enjoy
I Give great Thanks to:
@zhuhang for making this great app/mod
@jrummy for creating rom toolbox (another amazing app)
@Bradl79 for the build.prop idea
@bbgreen for confirming this works
And Anyone else i may have missed
If i have PM me and ill gladly add them in
Click to expand...
Click to collapse
Been trying to get this to work for a while as well as you may recall from past comments. Sure this guide will produce a desired "universal" sound effect as before? I had no luck with SoundCloud getting processed by V4A after this. However, I may needed to retry steps verbatim on a fresh ROM install too as I had some other conflicting things to clean up along the way.
Idk about soundcloud...I does work like it did before in Apollo...my guess is that its directing to basic sound while using other apps or stuff like soundcloud
Sent from my ADR6425LVW using xda app-developers app
Nice find Rev! Works great.
Thanks for the write up I just tried it. Unfortunately it only seems to work with Apollo. When I try it with Power Amp or Pandora it no longer works. On my old sense 4.0 ROM viper4android would modify those programs as well Ive tried the current version and the version off the play store with the same results. Thanks for the write up though very easy to follow.
Please post any questions about Viper4Android here not just 4.3 ROMs.
Sent from my ADR6425LVW using Tapatalk
How To Bake Viper4Android into a ROM zip (BASED OFF OFF v.2322)
@REV3NT3CH Consider adding this to the thread (Not trying to hijack the thread) this may be super long
@PTuT @Chucktr you asked for a pm of how to bake v4a into a rom, i decided to post it here for everyone
If you dont want to download the apk and install the apk/drivers you can merge the drivers and app from your pc.
ill probably end up making a script for this but right now i don't mind copying it into new builds for now
Latest apk - http://www.mediafire.com/download/z1mqg58hz1sfais/ViPER4Android_FX_v2322.zip
driver - http://d-h.st/xHh
driver config - http://d-h.st/axM
i usually use 7zip for archive viewer ect..
1. Open the rom zip in 7zip or whatever you choose to use
2. In 7zip navigate to "system/priv-app/" and drag/drop the apk you downloaded into the 7zip window.
3. In 7zip back out of the "prive-app" folder and navigate to "system/lib/soundfx/" and drag/drop libv4a_fx_ics.so you downloaded into the 7zip window
4. in 7zip back out of "soundfx" & "lib" and navigate to "system/ect/" and drag/drop audio_effects.conf you downloaded into the 7zip window
Exit 7zip, Now you have the app and driver baked in the rom :good:
Now what happens when any of this stuff gets update?.... well
Drag/drop the latest apk to priv-app (obviously lol)
The Driver can be pulled from the inside the apk in the assets folder using 7zip. Use any of the drivers containing "libv4a_fx_ics_NEON" based on the quality of the driver they are named different but i use libv4a_fx_ics_NEON_HQ, rename it to libv4a_fx_ics.so and copy it to the rom zip
We cant use the JB drivers on jb or kk, only ics
i dont know how often audio_effects.conf gets updated but just add the fallowing to the audio_effects.conf in the rom zip (ONLY IF NEEDED) the download link above should be good fine good for a while:
Line 9 to 11 :
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
Line 69 to 72:
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
all of this is based off of v.2322 so i cannot guarantee this to work within the next year or so ect... if someone updated something
bunchies said:
@REV3NT3CH Consider adding this to the thread (Not trying to hijack the thread) this may be super long
Click to expand...
Click to collapse
thanks for this...will deffinately be very useful and will do...your not hijacking bud your contributing to a very useful cause... you tha man @bunchies
Guys,
I can't post in the official thread here:
http://forum.xda-developers.com/lg-g3/development/guide-headphone-speaker-volume-booster-t2819821
But I just wanted to confirm that if you root your device and follow the directions here, I've got confirmed working on the Sprint LS990 variant of this phone. The thread mentions nothing of this on Sprint or the LS990 but I can confirm that it is indeed working.
You'll need to:
1. Have root with SuperSU installed
2. Install Root Browser and 920 Text Editor (Available in market for free)
3. Navigate to system/etc and then mixer_paths.xml
4. Change file permissions to rw-r-r
5. Save to your downloads folder just in case you trash your phone or something
6. Navigate to markers mentioned in thread link above. The LS990 variant will have aforementioned markers listed approximately 15 lines later in the code. Edit them to your liking.
7. Save, reboot, pray not to get caught in limbo.
8. Enjoy having better sound than everyone else with a phone.
Just an FYI anyone attempting this: If you do not edit the permissions correctly when overwriting the file the phone will not boot. It will get stuck at the yellow sprint screen and you will have to preform a reset.
Root browser did not allow me to change permissions correctly and when going quickly I did not notice it when overwriting.
However, second attempt after recovery it worked great.
Thanks for the info TROPhouse
So i havnt edited yet but permissions look right here. Will they change after I edit and save. And then change them back right. I don't wanna get stuck since we have no custom recovery yet.
Did it. It was way worth sweatin through the reboot process. Haha.
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
sinisin said:
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I'm using viper. Works perfect. After installing I moved the app from data/app to system/app. Heard people were having it being stopped after using it for awhile and this was there fix for that.
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
stagejuan said:
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
Click to expand...
Click to collapse
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
delete
Mahapederdon said:
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
Click to expand...
Click to collapse
I did 69 which seems perfect to be honest... I mainly hear music at the gym and usually use soundcloud... at 69, I don't even get close to full volume on the phone now. Its perfect
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Super loud
Thanks! Great volume!:victory:
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
Don't know if this is too late to help, but...
I don't use 920, but my guess is there's an option somewhere (probably in settings for the app) to switch the file system to read - write mode, instead of read-only. I use the FX app, and that's what I had to do with it. Be sure to set it back to read-only when you're done.
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
SUCCESS!
So you need to download an app that will mount your system, I used an app called mount/system. You launch it then select Mount r/w. Once you do that you have the needed access to edit the files as listed. I used this guide as well and had success....hope this helps others!
copy the original mixer_paths to your memory by ES file
edit it by notepad++ on windows and put it again in your memory
copy it from internal to your /system
highlight it and set permissions rw r r
move it from /system to /system/etc/
reboot and enjoy
Has anyone tryied playing with bluetooth volume i cant find where to change it any sugestions?
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
RandomPooka said:
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
Click to expand...
Click to collapse
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
dk2463 said:
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
Click to expand...
Click to collapse
ES's current interface does hide a lot, and is in almost every way inferior to the original interface. But the option is there. It's also in FX (File Explorer) which is my root editor of choice.
the pursuit of sound quality! bullet for my valentine cant be heard on stock!!!!!!!
tried this. guess i messed up. stuck on spark screen. sat and read through the pages here. gotta fix my phone when i get home tonight.
what did you change you volume levels to?
So can those who have successfully made the edits share what volume levels you changed and what are the new numbers? I've made the change to mine and even with my $100 earphones there's distortion at what I feel is a low level. I'm thinking maybe there's a balance among these that I need to achieve?
thanks!
dk2463