[MOD] Make Handset Speaker Louder
- Thread starter bchalk
- Start date
It's crazy loud through Vibrant's headphone even at lowest setting. How do I make it even lower.
Thanks for the mod. However I'm not hearing the difference on the speaker and my hearing is perfectly fine. Plus I can't seem to make the headset/headphones softer, even if I have the 0 and 5th value set to 22! I tried changing the ___ VT settings but when I get to the input page, it gives me an error saying the following:
Code:
MNU NOT EXIST
PRESS BACK KEY
Current Command is 56110I answered this in another thread, I thought it might be useful to have it in here as well.
WARNING: 100 IS VERY LOUD!
Dialer *#*#197328640#*#*
[5] AUDIO
[1] HANDSET
[1] VOLUME
[1] SRC Speech RX Volume
[5]5_lvl : 88
Menu -> Key Input
Change to any number greater than 88 (Max:100)
OK
Press back to save.
Default values:
0_lvl: 63
1_lvl: 68
2_lvl: 73
3_lvl: 78
4_lvl: 83
5_lvl: 88
sir this code dosent work on my x10i (Dialer *#*#197328640#*#*)
Dialer?
Hello, New to Android O/S.. Looking to try the volume boost mod suggested, but have no idea where to put in the code given? Maybe irrelevant to my Droid Eris, but wanted to know exactly where am I supposed to enter this "Dialer" code? I tried entering it as if I where placing a call *#*#197328640#*#* but when I click the last "*" it just clears my whole entry. I think I may be putting this in the wrong place or maybe punch in characters I don't need? Any help would be appreciated. Tried looking this up, and all references to dialer are for apps to place calls?
Hello, New to Android O/S.. Looking to try the volume boost mod suggested, but have no idea where to put in the code given? Maybe irrelevant to my Droid Eris, but wanted to know exactly where am I supposed to enter this "Dialer" code? I tried entering it as if I where placing a call *#*#197328640#*#* but when I click the last "*" it just clears my whole entry. I think I may be putting this in the wrong place or maybe punch in characters I don't need? Any help would be appreciated. Tried looking this up, and all references to dialer are for apps to place calls?
call volume
Sometimes these posted codes are wrong. Try, *#197328640#*, or, *#*#197328640#*. Play around with those symbols.
Sometimes these posted codes are wrong. Try, *#197328640#*, or, *#*#197328640#*. Play around with those symbols.
check your gear!!!
I know, I am a Noob, but; I got my vibrant for my birthday and immeadiately got a shell. set it up turned it on, and was reallllly underwhelmed with the volume. I then reached way back to something I read somewhere and realized this was a hard shell. a little love time with the dremmel, i carved out a majority of the plastic on the back and walla, double the volume. now this might not be your problem but without the excess, it is loud enough for me.
ParrotBob
BTW i am new to android, and a retired nuk engineer. i would appreciate any honest advice about the best direction to go this week with my vibrant. i downloaded and installed the one touch root from the bible and installed true stock 2.1, fixed the GPS tried to install the WIFI hub with only partial success on the hub.
Im a great student if any of you would care to mentor.
Have a good background in programming.
PB
I know, I am a Noob, but; I got my vibrant for my birthday and immeadiately got a shell. set it up turned it on, and was reallllly underwhelmed with the volume. I then reached way back to something I read somewhere and realized this was a hard shell. a little love time with the dremmel, i carved out a majority of the plastic on the back and walla, double the volume. now this might not be your problem but without the excess, it is loud enough for me.
ParrotBob
BTW i am new to android, and a retired nuk engineer. i would appreciate any honest advice about the best direction to go this week with my vibrant. i downloaded and installed the one touch root from the bible and installed true stock 2.1, fixed the GPS tried to install the WIFI hub with only partial success on the hub.
Im a great student if any of you would care to mentor.
Have a good background in programming.
PB
PB,
(1) Download and install paid versions of (a) ROM Manager, (b) Titanium Pro, and (c) Root Explorer or Astro (I have both but find myself using Root Explorer most of the time). These are critical tools to (a) access an important recovery environment and do an image backup of the entire system; (b) back up individual applications and data including settings (system and downloaded apps and data); and (c) browse and cut/paste to all areas of the flash system; (a, b, and c, respectively).
(2a) Download and learn to use Odin. This is an application that runs on your desktop and provides direct access to protected areas of your flash memory. It is used to flash firmware to the phone and is particularly important if you need to recover from experimentation. On the phone side, you must activate a "flashable recovery environment" to use Odin. You will know that recovery is activated if a big yellow triangle with an android digging with a shovel appears.
(2b) An alternative to flashing with Odin is to flash from an environment created from ROM Manager called "Clockwork Mod Recovery" ("CWM"). However, the ROM image files to use with CWM are different than those used with Odin. Odin ROM (PDA) files are .tar files, while a CWM-flashable file has a .zip extension. Such zip file contains the same image files as do Odin .tar files but also includes a script to tell the CWM environment where to put the files. Odin, on the other hand, is pre-programmed to know where to put the files.
(3) Note that a complete firmware flash of the OS includes three categories of files. The big one, formally called the "PDA," includes the user interface (UI), app and data management, etc. The second portion is a single binary file named "modem.bin" and controls the radios. The third is a single file named "zImage" and is the hardware kernel containing the drivers, a reduced version of Linux, etc. The actual nomenclature used in practice is a bit confusing. People use the term "ROM" ambiguously to mean either the PDA or all three of the elements discussed above in this paragraph. Generally speaking, the modem and kernel may be flashed separately or together with the PDA. So, it is important to know whether the "ROM" includes or excludes the modem and kernel, especially when using Odin, because these files may be entered on separate fields on the Odin interface.
(4) Create a “nandroid” backup (a binary image of the entire system) using ROM Manager. Copy these files to your computer, because they will not do you much good if the phone including the backup files gets wiped. The nandroid can be used to restore after a “mistake.” Of course, you can always “Odin” back to stock JFD as explained below. The difference, however, is that the nandroid includes all of your settings, phone directory, emails, etc. that are very painful to have to re-enter into your phone. In practice, it is usually best after a disaster to Odin back to JFD and then restore with your nandroid. (Note that I have never experienced such disaster, probably because I am an EE, am careful, and do not flash very often. Even so, I always do backups before flashing anything.)
(5) Ok, so the nandroid will restore everything. But what if you need to restore only one or a few things? (Settings, a list, one or more apps with their data, etc.) That is what Titanium is for. It backs up apps and data as individual files for selective restoral. As with the nandroid, Titanium backups should be copied to your computer to assure their availability in case of a complete wipe of the phone. In practice, I use the following method: (a) create nandroid using ROM Manager; (b) do a complete backup of all apps and data using Titanium; and (c) copy the entire internal sdcard to a backup space on your computer. Step (c) will ensure that all backup files are transferred to your computer.
(6) This raises the confusing question of Vibrant’s storage structures. One normally thinks of an “sdcard” as an external card that can be plugged into a device to increase storage capacity. Vibrant has a 16 GB internal memory chip. 2 GB of that chip is partitioned off as protected system memory. The remainder is available to the user and can be seen on your computer browser. The terminology problem is that Vibrant refers to that remainder of the 16 GB internal flash chip as “sdcard” because the chip is of the same type as used in external “sd cards.” Thus the need to clarify as to “internal” sdcard or “external” sd card. When you use Root Explorer to see your file structure from a Linux point of view, from the root location, you see /sdcard/sd, where sdcard is the internal user-available flash memory and sd is the external sd card (the latter stock card being 2 GB and containing the movie “Avatar”). Very confusing, but that is the way it is. All other files under root (seen with Root Explorer) are protected system files residing in the 2 GB space partitioned off from the 16 GB internal flash memory and visible only when a phone is “rooted,” ("rooted" meaning that a R/W protect flag has been removed from that portion of the file system so that you can access this area with Linux tools such as Root Explorer or a Windows-based tool, "adb").
(7) Download stock JFD ROM (combination PDA, kernel, and modem). This is the version of firmware that is on the phone when you purchase it. You may need this to get back to stock if you mess up your phone. A sure way to clean up any mess is to Odin back to JFD.
(8) As of this date (1/15/2011), download JL5 and flash over JFD. Then flash the latest (KA5) modem over JL5. Next, download the Voodoo version of the KA5 kernel from here: http://xdaforums.com/showthread.php?t=870480 and flash over JL5. At that point you will be at the latest and greatest stable (read: stock) system that I have tested and use daily. (Note that I am not a ROM junkie. I really do not have time for this hobby and am only doing it to make my phone more usable.)
(9) I consider the "Voodoo" kernel enhancement to be the most valuable modification to the Vibrant available on XDA. It speeds up file access by perhaps as much as 50%.
(10) As you can see, this post is a general “how to get started” overview of Android ROM management on the Vibrant. It may be useful to a newbie to avoid “can’t see the forest for the trees” syndrome. However, it merely complements and does not replace seeing the trees themselves. Each of these steps is explained in gory detail many times on multiple posts on XDA. I strongly suggest that anyone who wishes to get started safely read and understand detailed instructions for each of these steps before flashing anything. There is a very protected memory area containing three hierarchies of boot loading code, including the code required to execute the recovery environment to restore a system using Odin. Although hard to do, if you wipe this out it will probably cost more than the phone is worth to find a technician with a specialized piece of equipment required to access these memory locations to restore the primary boot loader.
(11) How is it possible that mature adults could be wasting time like this?
i know its "Blast from the Past" but does some1'ns knows how to
raise the call volume during calls higher?? its too damn low and dont have
HAC im menu...
raise the call volume during calls higher?? its too damn low and dont have
HAC im menu...
well..i m using captvate i896...2.2 froyo..
i guesss sound is a problem with all the galaxy s model..if we talk abt the speakerphone..for listenin to music or watchin a movie..or even for ringing purpose...
i m ok with my callin sepaker and mic..
but i hav a peculiar problem..when i connect it to my bluetooth device..(plantronics discovery 925)...the sound loudness is fine..but there is a huge distortion even to me and even to the other party who is listenin to me..
though this plantronics device is perfectly working device..and i m using it with other phone..like nokia...and even i connect this headphone to my laptop..and its working fine...so seems the issue is with the phone...not with the bluetooth device..
ppl can give suggestion or share their ideas on this...?
i guesss sound is a problem with all the galaxy s model..if we talk abt the speakerphone..for listenin to music or watchin a movie..or even for ringing purpose...
i m ok with my callin sepaker and mic..
but i hav a peculiar problem..when i connect it to my bluetooth device..(plantronics discovery 925)...the sound loudness is fine..but there is a huge distortion even to me and even to the other party who is listenin to me..
though this plantronics device is perfectly working device..and i m using it with other phone..like nokia...and even i connect this headphone to my laptop..and its working fine...so seems the issue is with the phone...not with the bluetooth device..
ppl can give suggestion or share their ideas on this...?
Last edited:
Maybe we're looking in the wrong place guys...when I go back to stock 2.1, the audio on my Captivate will blow my doors off. Ringer, handset, speaker all of it is super-loud. I thought it was one or two of the ROMs that I was installing that was causing the low audio but...I recently flashed back to stock 2.1 and checked the audio => nice and loud. Rooted => audio still loud. Installed CWM => audio took a dive.
For me, CWM is the culprit...unfortunately, I do not know how to fix it short of flashing back to stock.
For me, CWM is the culprit...unfortunately, I do not know how to fix it short of flashing back to stock.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3I answered this in another thread, I thought it might be useful to have it in here as well.
WARNING: 100 IS VERY LOUD!
Dialer *#*#197328640#*#*
[5] AUDIO
[1] HANDSET
[1] VOLUME
[1] SRC Speech RX Volume
[5]5_lvl : 88
Menu -> Key Input
Change to any number greater than 88 (Max:100)
OK
Press back to save.
Default values:
0_lvl: 63
1_lvl: 68
2_lvl: 73
3_lvl: 78
4_lvl: 83
5_lvl: 88
3
PB,
(1) Download and install paid versions of (a) ROM Manager, (b) Titanium Pro, and (c) Root Explorer or Astro (I have both but find myself using Root Explorer most of the time). These are critical tools to (a) access an important recovery environment and do an image backup of the entire system; (b) back up individual applications and data including settings (system and downloaded apps and data); and (c) browse and cut/paste to all areas of the flash system; (a, b, and c, respectively).
(2a) Download and learn to use Odin. This is an application that runs on your desktop and provides direct access to protected areas of your flash memory. It is used to flash firmware to the phone and is particularly important if you need to recover from experimentation. On the phone side, you must activate a "flashable recovery environment" to use Odin. You will know that recovery is activated if a big yellow triangle with an android digging with a shovel appears.
(2b) An alternative to flashing with Odin is to flash from an environment created from ROM Manager called "Clockwork Mod Recovery" ("CWM"). However, the ROM image files to use with CWM are different than those used with Odin. Odin ROM (PDA) files are .tar files, while a CWM-flashable file has a .zip extension. Such zip file contains the same image files as do Odin .tar files but also includes a script to tell the CWM environment where to put the files. Odin, on the other hand, is pre-programmed to know where to put the files.
(3) Note that a complete firmware flash of the OS includes three categories of files. The big one, formally called the "PDA," includes the user interface (UI), app and data management, etc. The second portion is a single binary file named "modem.bin" and controls the radios. The third is a single file named "zImage" and is the hardware kernel containing the drivers, a reduced version of Linux, etc. The actual nomenclature used in practice is a bit confusing. People use the term "ROM" ambiguously to mean either the PDA or all three of the elements discussed above in this paragraph. Generally speaking, the modem and kernel may be flashed separately or together with the PDA. So, it is important to know whether the "ROM" includes or excludes the modem and kernel, especially when using Odin, because these files may be entered on separate fields on the Odin interface.
(4) Create a “nandroid” backup (a binary image of the entire system) using ROM Manager. Copy these files to your computer, because they will not do you much good if the phone including the backup files gets wiped. The nandroid can be used to restore after a “mistake.” Of course, you can always “Odin” back to stock JFD as explained below. The difference, however, is that the nandroid includes all of your settings, phone directory, emails, etc. that are very painful to have to re-enter into your phone. In practice, it is usually best after a disaster to Odin back to JFD and then restore with your nandroid. (Note that I have never experienced such disaster, probably because I am an EE, am careful, and do not flash very often. Even so, I always do backups before flashing anything.)
(5) Ok, so the nandroid will restore everything. But what if you need to restore only one or a few things? (Settings, a list, one or more apps with their data, etc.) That is what Titanium is for. It backs up apps and data as individual files for selective restoral. As with the nandroid, Titanium backups should be copied to your computer to assure their availability in case of a complete wipe of the phone. In practice, I use the following method: (a) create nandroid using ROM Manager; (b) do a complete backup of all apps and data using Titanium; and (c) copy the entire internal sdcard to a backup space on your computer. Step (c) will ensure that all backup files are transferred to your computer.
(6) This raises the confusing question of Vibrant’s storage structures. One normally thinks of an “sdcard” as an external card that can be plugged into a device to increase storage capacity. Vibrant has a 16 GB internal memory chip. 2 GB of that chip is partitioned off as protected system memory. The remainder is available to the user and can be seen on your computer browser. The terminology problem is that Vibrant refers to that remainder of the 16 GB internal flash chip as “sdcard” because the chip is of the same type as used in external “sd cards.” Thus the need to clarify as to “internal” sdcard or “external” sd card. When you use Root Explorer to see your file structure from a Linux point of view, from the root location, you see /sdcard/sd, where sdcard is the internal user-available flash memory and sd is the external sd card (the latter stock card being 2 GB and containing the movie “Avatar”). Very confusing, but that is the way it is. All other files under root (seen with Root Explorer) are protected system files residing in the 2 GB space partitioned off from the 16 GB internal flash memory and visible only when a phone is “rooted,” ("rooted" meaning that a R/W protect flag has been removed from that portion of the file system so that you can access this area with Linux tools such as Root Explorer or a Windows-based tool, "adb").
(7) Download stock JFD ROM (combination PDA, kernel, and modem). This is the version of firmware that is on the phone when you purchase it. You may need this to get back to stock if you mess up your phone. A sure way to clean up any mess is to Odin back to JFD.
(8) As of this date (1/15/2011), download JL5 and flash over JFD. Then flash the latest (KA5) modem over JL5. Next, download the Voodoo version of the KA5 kernel from here: http://xdaforums.com/showthread.php?t=870480 and flash over JL5. At that point you will be at the latest and greatest stable (read: stock) system that I have tested and use daily. (Note that I am not a ROM junkie. I really do not have time for this hobby and am only doing it to make my phone more usable.)
(9) I consider the "Voodoo" kernel enhancement to be the most valuable modification to the Vibrant available on XDA. It speeds up file access by perhaps as much as 50%.
(10) As you can see, this post is a general “how to get started” overview of Android ROM management on the Vibrant. It may be useful to a newbie to avoid “can’t see the forest for the trees” syndrome. However, it merely complements and does not replace seeing the trees themselves. Each of these steps is explained in gory detail many times on multiple posts on XDA. I strongly suggest that anyone who wishes to get started safely read and understand detailed instructions for each of these steps before flashing anything. There is a very protected memory area containing three hierarchies of boot loading code, including the code required to execute the recovery environment to restore a system using Odin. Although hard to do, if you wipe this out it will probably cost more than the phone is worth to find a technician with a specialized piece of equipment required to access these memory locations to restore the primary boot loader.
(11) How is it possible that mature adults could be wasting time like this?1You could always try HAC mode
Settings/Call Settings/HAC mode....this survives a restart....This makes the phone quite loud
