Database Develop

low volume earpiece

hi yall
having trouble with the earpiece the volume is too low
is there any fix for it?
thanks

earpiece?
are you talking about the phone or using audio out via headphones?

Are you on stock our custom rom

while im a call i can bearly hear anything the volume is too low
im not using headphones or BT.
i moved from the stock to the Preception 10.4 but the volume remains the same...

Try hardcore kernel, and or different modem.
Had same issue on first release of andromeda

i have great reception im afraid to lose it..
before i upgraded to Preception 10.4 i had Cognition 3.04 with lilke 7~10
diffrent modems but the same issue.
also with the stock i had trouble with the low volume during a call...
PLS HELP!

I don't know what country your in. So I don't know what modem to recommend. Israel?

Israel it is
i have great reception and even greater satellite reception (11\11 amazing!) i dont want to lose it :|
the only problem is the low volume during calls that's it...
thanks guys for all your help though
my "Modem" is I9000UGJK4

Since you're already using JK4, try KP1 modem. CWM flashable. Links provided. Just keep trying different modems. Probably should write down you apn settings too.
JK4:
http://forum.xda-developers.com/atta...4&d=1292262582
KP1:
http://forum.xda-developers.com/atta...4&d=1295122989

GUARDIANBD said:
i have great reception im afraid to lose it..
before i upgraded to Preception 10.4 i had Cognition 3.04 with lilke 7~10
diffrent modems but the same issue.
also with the stock i had trouble with the low volume during a call...
PLS HELP!
Click to expand...
Click to collapse
already try'd it :| no use...
howcome we dont have HAC (Hearing Aid Compatible) in our Captivate??

On the Market there is a program called SamServiceMode. Load it then go to option 5(audio), then 1(handset), then 1(volume), then 1(SRCSpeech RX Volume.
Option # 5 is defaulted to 92. Raise it to 100(max)
This should help. At least it did for me.
Running di11gaf v6.0
SuckerPunch-SmR #48
BTW this program also makes it very easy to switch to GSM instead of 3G if like me you are in a fringe 3G area it sucks my battery very quickly. Switch to GSM only and I can go for 35+ hrs and still have 40% left......
Good Luck!

im also using 2G network ill tryout your suggetion
is it holding a reboot?
bout the battery life mine suXAss..
---------------------------------------------
its that script of the service mode...

No it does not hold at reboot but I have found that I do not have any reason now to reboot more than once a week, if that.
SuckerPunch kernel seems to be the match for my phone setup. I am experimenting right now on my other Cappy with Supernova 2.3 and SuckerPunch # 50 to see what Battery life I end up with also...

GUARDIANBD said:
hi yall
having trouble with the earpiece the volume is too low
is there any fix for it?
thanks
Click to expand...
Click to collapse
The earpiece volume is a kernel "issue". Speedmod and SuckerPunch are two kernels that have addressed this. Hope to have Andromeda kernel fixed shortly as well.

is there any way to edit this Kernel? or edit the modem?
y the cooker of the roms\kernel cant raise the volume? (im not complaining on there great job they doing,honet)

GUARDIANBD said:
already try'd it :| no use...
howcome we dont have HAC (Hearing Aid Compatible) in our Captivate??
Click to expand...
Click to collapse
Check out this link
I know it says vibrant but it works

No go...same problem

[Q] Poor Sound Quality

This would fall under the don't fix something thats not broke category.
Sound quality was great on my phone with 2.3.3 JVK, but after reading the great reviews on Voodoo sound, I was interested in seeing how much better it could get. After flashing the Voodoo sound driver (came with voodoo control plus 1.0.5) any sound through multiple types of headsets is distorted and almost sounds like the volume is automatically limited (Any high notes or low bass is either completely cut off, or the volume limits when the note hits). Sound quality after this flash is horrible to unusable. The odd thing is that even if I unload the voodoo driver, the sound is still awful. ANY help at all would be greatly appreciated!!
**EDIT** Just to add, I have tested the volume levels to make sure they were not to high in the application. The distortion/limiting happens even if set to a very low volume.
Phone Info:
Model:Samsung Galaxy S i9000m Vibrant
Firmware Version:2.3.3
Baseband Version:I9000UGKC1
Kernel Version:2.6.35.7-I9000XXJVK-CL75655\[email protected] #2
Build Number:GINGERBREAD.XXJVK
Clockwork Recovery v3.0.0.5
CWM Manager v1.20
Superuser v2.3.1-ef
Softkey Backlight Fix
CRT-OFF Animation Mod
All was good before flashing voodoo sound.

How are you controlling your volume?
The best results, will be to max out the phone media volume completely.
Go into Voodoo Sound control and tick "map volume kies hack" and the volume will be controlled by that.

steve-stewart said:
This would fall under the don't fix something thats not broke category.
Sound quality was great on my phone with 2.3.3 JVK, but after reading the great reviews on Voodoo sound, I was interested in seeing how much better it could get. After flashing the Voodoo sound driver (came with voodoo control plus 1.0.5) any sound through multiple types of headsets is distorted and almost sounds like the volume is automatically limited (Any high notes or low bass is either completely cut off, or the volume limits when the note hits). Sound quality after this flash is horrible to unusable. The odd thing is that even if I unload the voodoo driver, the sound is still awful. ANY help at all would be greatly appreciated!!
**EDIT** Just to add, I have tested the volume levels to make sure they were not to high in the application. The distortion/limiting happens even if set to a very low volume.
Phone Info:
Model:Samsung Galaxy S i9000m Vibrant
Firmware Version:2.3.3
Baseband Version:I9000UGKC1
Kernel Version:2.6.35.7-I9000XXJVK-CL75655\[email protected] #2
Build Number:GINGERBREAD.XXJVK
Clockwork Recovery v3.0.0.5
CWM Manager v1.20
Superuser v2.3.1-ef
Softkey Backlight Fix
CRT-OFF Animation Mod
All was good before flashing voodoo sound.
Click to expand...
Click to collapse
Firstly, when did you buy Voodoo Control Plus? Cos 1.0.5 is an old version the current version is version 2.0 Beta2-4.
Secondly, what did you flash? All you need for Voodoo Control Plus is root, it loads the module on reboot. Did you reboot after unloading the driver?
I'm running the current version on JVB with no problems and I've previously flashed the Voodoo soundmod kernels on three other phones (Froyo) and they all sounded amazing afterwards.
Contact the dev at [email protected]

steve-stewart said:
Sound quality was great on my phone with 2.3.3 JVK, but [...] after flashing the Voodoo sound driver (came with voodoo control plus 1.0.5)
Click to expand...
Click to collapse
When you use Voodoo Control Plus you're not flashing anything! All it does is load a module, which is the reason it needs root btw. No need to reboot either. If that doesn't work for whatever reason, you can just unload the module again.
Conclusion: Either you made a mistake or you're a troll. Did you try to use the VCP module with a kernel that has (an older version of) Voodoo compiled in by any chance?

ok.....slow down guys. Noob-Yes, Troll? not likely. Heres the thing, I cannot remember what I used to get this on my phone. The one thing I can tell you is it came from somewheres on xda. Also, I have maxed out the phone volume, and enabled the Keys hack. No difference. Even if I un-load the module, the sound improves "slightly" but is still "volume limited" somehow. The only way I can explain it, is if the song has a loud part, the phone seems to automatically limit the volume, also all low range (bass) audio seems to be missing from any song regardless of weather the module is loaded or what audio settings are enabled.
You know the best way you guys could help me out? Tell me if it is safe to upgrade to the newest gingerbread. The reason I ask this is:
1.I have installed the "new" bootloaders from the JVK 2.3.3 (I believe stock) rom, but then I have the clockwork mod on top of that and the phone is rooted, also flashed the softkey fix and the crt off animation. ALSO, i had to flash the BELL KC1 modem to get the 850mhz band to work here in cape breton. I just need to know what needs to be done to make it safe to flash the newest stock firmware.
2.I just want to rid the phone of the voodoo mod and stay as far away from it as I can. I'm thinking flashing the newest firmware will help me do this.
3. I have searched multiple topics and I am just having a hard time getting a stright answer on what needs to be un-modded/removed/etc to make it safe to upgrade.
I really didn't mean to come off as a "troll".

steve-stewart said:
I cannot remember what I used to get this on my phone. The one thing I can tell you is it came from somewheres on xda.
Click to expand...
Click to collapse
I don't think anyone can help you without knowing what you did to your phone and what's on it right now. The only solution I can see would be a factory reset and a full (including bootloaders) stock 2.2.1 ROM flashed via Odin. Then you at least have a known-good baseline configuration and can go from there.
steve-stewart said:
I just want to rid the phone of the voodoo mod and stay as far away from it as I can.
Click to expand...
Click to collapse
You don't have a clue about what you're doing, that's fine. Do a little reading and all will be well. But there's no need to blame Voodoo (or any other mod).

I think you might have took this whole thing the wrong way. This is why I don't ask many questions and only have input if I think it will help. Sorry to have affended anyone. I wasn't blaming voodoo at all, I was just saying that all was fine before I installed it. It IS most likely my mistake. Thanks to "those" that helped. I'm just going to re-flash 2.3.3 JVK stock, as I know it worked before. I only started the thread to see if anyone ran into the same thing or had any better ideas than reflashing.
Also to those that questioned, the voodoo mod was the only thing I did to my phone that I didn't fully research before implementing. I'll take this as a lesson.

Hi!
What is your transaction number, for Voodoo Control Plus?

I have no idea, it was all in one thing that I found on a forum which probaly wasn't the best thing to do. I reflashed the phone to froyo and then back to 2.3.3 and without any mod's the sound works great. I would say this had nothing to do with voodoo, and 100% me not researching how to install it.

steve-stewart said:
I have no idea, it was all in one thing that I found on a forum which probaly wasn't the best thing to do. I reflashed the phone to froyo and then back to 2.3.3 and without any mod's the sound works great. I would say this had nothing to do with voodoo, and 100% me not researching how to install it.
Click to expand...
Click to collapse
Okay so please send me the link to what you found with a pirate version of Voodoo Control Plus.

I'm not sure of the link it was a while ago. Had I of known it was pirated I wouldn't have used it. I was looking for something to make the line out louder and came across a zip-file while doing some random googling. Had I of known where I got it I would have posted it in the first post. Listen, I'd be more than happy to pay for software, and have many times.

Cool, you'll find the latest version on Android market.

Ok, I see the one on Android market, Is there anything I have to do besides root the device again to have it work properly? It has been completely factory reset and reflashed to 2.3.3 JVK so there shouldn't be any reminants from whatever I installed last time.

steve-stewart said:
Ok, I see the one on Android market, Is there anything I have to do besides root the device again to have it work properly?
Click to expand...
Click to collapse
Nope, that should do it. Welcome to the club!

Can you make In-call Volume louder??

Hi, I have hearing loss and some times I have a difficulty hearing people on the other line and I was wondering if there was was a way to make the volume louder than stock??
Thanks, any help is greatly appreciated
Sent from my GT-I897 using XDA App

Nothing?? :/

I know two ways to do that: First method which I use all the time on gb and there is also this second method which for me it doesn't work cuz Galaxy tuner app is FC over on gb but I remember that back in froyo days it used to work just fine. Cheers

I tried the first method is it supposed to be a big difference i put it on 99...???

Results may vary,as u'll find it in the thread I linkend u those methods from,for some it made a big and for others no difference at all. For me it does, it's a notable change but I have it on 100.
Also try out different modems, some ppl reported better results after switching. I'm on kc1but ur phone and ur location might like a different one.

This is usually a kernal tweak or a .prop tweak. I use Sgs.Tools for .Prop tweaks. Make a nandroid befforehand

Glitch kernel on cm7 has incall volume script now. (v12b3)

Smasher816 said:
Glitch kernel on cm7 has incall volume script now. (v12b3)
Click to expand...
Click to collapse
This would work if your on Cm7/miui/espresso/or biffmod roms.

[Q] No Sound in CM9 or CM10

Hi community! Thanks to all the developers who make this project fly!!!
I fear I have a resistant Touchpad that does not want to output any audio in Android CM9 or CM10.
It has sound in WebOs so I don't think it is a hardware problem.
I've tried CM9 (123012) and heard some soundtap noise after a reflashed gapps, but then the sound went away, I think
when the wifi started (?).
CM9 was extremely slow and the system would be very laggy and freeze when I tried to change the volume by using
the volume buttons. Many times I'd have to do a power+home button shutdown.
CM10 (121612) on the other hand was very responsive, quick and smooth and there was no lag or freeze on pressing the
volume button- but still no audio.
I used ACMEuninstaller to remove CM9 and used:
ACMEInstaller3, CWM6, moot 0.35 for both installs, flashed cache and dalvik, and fixed permissions.
Is there anything else I can try?
Thanks!

Briefly hold the power button to bring up the menu and make sure it isn't set to mute should be the bottom Line with a line under the speaker on the right .

I brought up the screen, and it shows the speaker icon on the right side with the line under it.
It looks like volume is on and not mute, but still no sound.
Thanks for the suggestion.
Thinking it was something to do with WebOS 3.05, I used the thread in this forum to bring back the Touchpad to WebOS 3.00, and
then 3.04 and still the same issue appears in Android.
I'm now thinking that this 32GB Touchpad may not have the same hardware for the audio codecs to work in android?
(Actually, I'm clueless and just guessing, and, hope I'm wrong.) :fingers-crossed:

Well it was worth a try, it shouldn't be anything to do with webos (I'm on 3.05) . Do the headphones work as it has been suggested that the socket my be causing problems .
Otherwise I'm also clueless .

Good to know that it isn't WebOS 3.05 related.
I tried the headphones and no sound either. So I rebooted with the headphones plugged in and no sound.
One other thing I can't figure out is why would CM10 be more stable than CM9 on this device, when the consensus seems to be
that CM9 is much more stable?

No idea , I'm using Oat's at the moment but also have a backup of jcsullins so that I can test out things on both and have stopped using CM9 completely .
I take that you get no sounds when typing and that the volume cursor moves when you use the rocker switch .

Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).

north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
Try going to settings > sound > volumes, and see if the settings are correct.
If I think of something else, I'll post it.

I have the exact same problem. Tried all the resolutions mentioned above, no result. Wiped out android and used WebOS doctor for full recovery, then installed the latest nightly (24 Nov 2013) still no sound. Somewhere it was mentioned that it is due to a firmware (A6) problem but I don't know how to downgrade or upgrade the firmware.
Any help is appreciated.

Hp Touchpad on CM9 and CM10
I have also tried for nth times but my touchpad 16GB has no audio output (including 3.5mm jack) on CM9 or CM10......... somebody help

I have the same problem, but can install older CM9 builds and have sound. 6/12/2012 nightly is one that has sound for me.

My problem ended up being the head phone jack. I rapidly inserted/removed the headphones several time and my speakers came back to life.
Still very odd that I had audio in WebOS and older cm9 builds the whole time, but I'll refuse the question that logic and am thankful that I was able to get it working.

north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.

CJMax said:
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.
Click to expand...
Click to collapse
Have you guys considered submitting alogcat to the developers? It might be more productive than just stating that you have a problem. Submitting a logcat might help to get the problem fixed. I remember hearing issues with 64GB Touchpads not playing sound with CM9 Roms. Flashing the audio libs helped a few of those users.

I created a log on pastebin: MyfU2DDU (not allowed to post full urls yet). Who should I send it to? At the beginning of the log, sound was still working, then (I think line ~1280) sound stopped. Afterwards, I'm getting out of memory errors. Running CM10, same problem in CM9 and CM10.1.

Had the same prob and now back on cm-9-20130512 and disabled system sounds. It works now.

Vivid ROMs and in-call volume issues

I'm doing research for a friend's phone. He has the AT&T HTC Vivid. My old phone actually. I have yet to root it or do any of the dirty work as I am concerned with the stability and flaws in ROMs for this device. A little advice would be appreciated.
I have read about the Dirty Unicorn ROM with the Pac kernel (or since updated stock kernel). They say the volume is fixed in this ROM. Can anyone confirm?
Also would like to know of other ROMs and what is available out there through others advice. I want to find him stable as he cannot be flashing daily the way I can. I have seen lots of bluetooth issues called out. I am more concerned with stability, call volume, and definitely good data/wifi. Someone point me in the right direction perhaps?
I would love to see Sense gain more support for this device, but I'm not a dev so I'm sure it's no easy task. I have used CM alot in the past, and loved most of it, but it always had its bugs so I hesitate to flash without gathering information.
Thanks guys.

acw928 said:
I'm doing research for a friend's phone. He has the AT&T HTC Vivid. My old phone actually. I have yet to root it or do any of the dirty work as I am concerned with the stability and flaws in ROMs for this device. A little advice would be appreciated.
I have read about the Dirty Unicorn ROM with the Pac kernel (or since updated stock kernel). They say the volume is fixed in this ROM. Can anyone confirm?
Also would like to know of other ROMs and what is available out there through others advice. I want to find him stable as he cannot be flashing daily the way I can. I have seen lots of bluetooth issues called out. I am more concerned with stability, call volume, and definitely good data/wifi. Someone point me in the right direction perhaps?
I would love to see Sense gain more support for this device, but I'm not a dev so I'm sure it's no easy task. I have used CM alot in the past, and loved most of it, but it always had its bugs so I hesitate to flash without gathering information.
Thanks guys.
Click to expand...
Click to collapse
No DU just fixes The volume increase decrease while in a call
If you care about in call volume try a sense 4.1 rom or a sense 3.6 rom

Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
bilibox said:
No DU just fixes The volume increase decrease while in a call
If you care about in call volume try a sense 4.1 rom or a sense 3.6 rom
Click to expand...
Click to collapse

acw928 said:
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
Click to expand...
Click to collapse
It's always going to be work. and for me my volume is just fine. In call works loud enough for me. But everyone has their own preferences. Other people cant use the roms due to the volume issue

To answer your question... I would put CM10.1 from albinoman... Prolly the most stable we gots
Sent from my Vivid 4G using Tapatalk 4

acw928 said:
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
Click to expand...
Click to collapse
I have an AT&T Vivid, and have had varied results in this department. Though, I work in a server room/data center, so I have more ambient noise to contend with, but I've experienced horridly low volume on some builds all the way to just less that stock quality. The first ROM I experienced this on was a Sense 4.1 ROM, but also experienced it in different ways with aosp/aokp builds as well. I don't know if it is related, but I did notice a significant increase in the in call volume after performing the S-OFF wire trick. Though that could just be a coincidence. But one common theme I have found, is when the in call volume has been low, don't even attempt speakerphone use. As when I did, it either didn't work at all (or so low it's inaudible) and then when returning to the earpiece, 6/10 times (guesstimate) the issue of no volume followed for the duration of the call. And the odds would increase when activating speaker before the call is answered on the other end (making calls). However, I must say that I the in call volume using bilibox's unofficial rootbox, I do not experience the low in call volume, but the speakerphone is (mostly) useless. (Still an awesome ROM though, just waiting for mobile data fix )
Not sure if my ramble is helpful or not, but those are summed up experiences I've had thus far. If you really just want it to work without goofing with anything, I 'd recommend either a rooted/modified/de-bloated stock ROM.
There's my 2 cents {plunk plunk}