Database Info

[Q] Extremely Low Call Volume - Is this a common problem?

Hi all.
Recently got myself my first smartphone, the Nexus S on Telus. (Well, had a Samsung Omnia before, but getting a WM6.1 phone in 2010 can hardly be considered smart )
Everything was going swimmingly. I have a penchant for changing up the software innards on the devices I own, so naturally I rooted my shiny new phone and had a good time trying out all these ROMS. This was approximately a month ago.
About a week ago my phone inexplicably began to act up. My in-call volume dropped to barely a whisper, and my touch-sensitive search button would for some reason go off on it's on.
After a bit of Googling, I found out that the search button issue is affecting many other Canadian users also, something about a bug in the new radio (AUCKD1).
But I've yet to find anything conclusive about the in-call volume. There are threads who are complaining of either low or high volumes, but no workable solutions.
So as a last resort I have restored my phone to fully stock 2.3.4. One to see if it was my messing around that caused it, and to also prepare for the possibility of having to return my shiny. It may just be my imagination/denial, but the call volume seems slightly better. Not good enough for me to hear outside, but inside, with no background noise it's just slightly quieter than normal.
Another thing that is very odd. Skype volume is much louder than voice calls. To be frank it's still not loud enough to be considered acceptable, but it is definitely louder. They use the same speakers right? Why would that be?
If at all possible I'd like to avoid having to take the phone back since Telus will no doubt charge me exuberant fees for having touched the phone for more than 3 seconds and moving more than 18 millimeters away from the store I bought it from.
Please advise, XDA!

U can try install kernel voodoo sound from supercurio and apps. U can see the different.
I had try most of the custom rom. There is one rom who give me loudest call volume, but I can't remember which ROM it is. U should explore more rather than bring it to the store.
Now I'm on liquidnexusbread, but not giving me a good volume in call.
I knew it sucks... but I love this rom performance.
Sent from my Nexus S I9020T

Does hacking fix EVERY problem with this device?

I have three days to change my G2x for the Nexus S.
I need to know whether putting ANY custom ROM/root/whatever can fix every single problem with this phone:
Battery life drain
Software bugs
MOST IMPORTANTLY (why doesn't anyone care/notice?!): NOISY HEADPHONE JACK OUTPUT
Is this problem entirely software, or partly hardware? I have such minimal LCD bleed that its not noticeable.
Please chime in and check my thread on noisy output and take my FIVE SECOND test with your modded device to tell all of us whether it is fixed or not.

nevermind.

Using CM7 + Faux's EXT4 undervolt Kernel + GPS fix pretty much makes this phone perfect for me. I have absolutely no issues at all EXCEPT for screen bleed. That cant really be fixed with software though. Battery life is great. Yesterday I didn't use my phone much but I went OVER 24 hours on one charge. Didn't plug it in once. Woke up this morning and it still had about 15%. Of course I turned off data while I slept though so that probably helped a lot.

voodoo takes care of the headphone jack noise. in fact i've never ever experienced music with low of a noise floor below

adevilfish said:
voodoo takes care of the headphone jack noise. in fact i've never ever experienced music with low of a noise floor below
Click to expand...
Click to collapse
Can you please elaborate and confirm that you noticed the exact same noise as I described (for a second after any sound stops, or during a completely silent track playing?) And voodoo took care of it? So it is software causing the noise and not hardware?

I'm finally at peace with my G2X and it is solid reliable. ****ty battery life but what can you expect.
In my case my phone did have reboots and freeze while charging. I still don't trust having this phone charging overnight because it might crash.
Also went and deleted both Internal/External SD and properly WIPE like 5 times. Flashed CM7 RC1 + Google apps and fixed permissions. I had issues where email syncs failed after 8+ hours but after doing this full clean flush and Wipe, this piece of **** phone finally is reliable.
Its solid and finally enjoying the phone. Just need CM7 out of RC and I'm golden.
However, every time I went to stock I had issues. If you don't plan on Rooting/Flash don't bother with this phone. Its a piece of crap and LG sucks at making ROMS.

I love my phone but I reccimend you get the nexus S. I'm sorry, its just a better phone.
Ps....Please don't ostracise me from this forum lol.
Sent from my LG-P999 using Tapatalk

britishtomquin said:
I love my phone but I reccimend you get the nexus S. I'm sorry, its just a better phone.
Ps....Please don't ostracise me from this forum lol.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Software-wise, yes. It's a better phone... Hardware-wise, HELL NO!

CM7 with Trinity kernel gets 24 hours of battery and no reboots from my experience.
Sent from my Nexus 5g using XDA Ultimate App

youd be a fool to trade for that phone... yes every problem fixed.. no problems for awhile for me... love my phone..

I have to agree. The G2x is a million time better then the Nexus S. The Nexus doesn't even do 4G.

The Nexus S is last generation, the only competition for the g2x is the htc sensation and the samsung galaxy s2.
Sent from my Nexus 3 using XDA Ultimate App

KingDavid63 said:
youd be a fool to trade for that phone... yes every problem fixed.. no problems for awhile for me... love my phone..
Click to expand...
Click to collapse
Long live the King!

G2x - July baseband/radio, Cm7 Nightlies, Faux OC/uv Kernel, Launcher Pro, Straight Beast Status! No Bugs! Smooth as my ps3 or 360 on gaming... gameloft is making some killer gamez... I love this phone... It's a sense or no sense issue if you ask me... I like both.. My last phone was the htc glacier i gave to my momma, it was a good phone... I wanted a senseless device and im glad i got this one.. not another 6-8 months down the road when the next 1.3+ Ghz batch of phones comes out i might go back to sense, but im completely content where im at right now with the g2x with the games and now netflix... dont get no better.. maybe the sgs2 but that's the most powerful phone in the world as far as buyin out the store... but the sensation.... NO!

k00zk0 said:
Can you please elaborate and confirm that you noticed the exact same noise as I described (for a second after any sound stops, or during a completely silent track playing?) And voodoo took care of it? So it is software causing the noise and not hardware?
Click to expand...
Click to collapse
I've never had a noise issue with the Jack and I use my g2x like an iPod. Battery life sucks but with Google music its been awesome. I've also been using the leaked gb off LG the only thing with that is now I can't seem to root my phone.
Sent from my LG-P999 using XDA App

I don't notice noise. I plug my G2x into my surround and crank it. Sounds like any other device I've owned (ipad2 being one of them)
LG G2x - Miui
www.SnapSiteAdmins.com
www.MiiWiiChat.com

NVfllash cwm and then install or restore rom = root...

So after getting CM7 and Faux's OC/UV/etc/Voodoo kernel I still have noise with the sound. Do I need the Voodoo app to enable a different kind of processing or something? I cleared 3x caches/data, installed .zips: CM7 b89, gapps, and Faux [2.6.32.41] (v0.3.4) before restarting.
This makes the sound even more apparent: Go to a silent place and turn the volume on the phone all the way down to vibrate. Put the speaker at the bottom right into your ear and push volume up once. You'll hear the quiet boop tone and a second of very loud hiss before it cuts out. Wait until the sound disappears after two seconds to notice that it was even there in the first place, before pushing the volume button again. It even turns the amp on when you set it to vibrate and there is no tone played. Two new units fresh out of the box have had this same noise. I can't believe users, especially devs don't notice this or see it as irregular, so I must be doing something wrong with Voodoo, and every unit in Canada is the same hardware-faulty. I've got three hours to swap it for the nexus; a primary use for this phone would be monitoring detailed music, and this is an unacceptable level of noise. Please try this and let me know if it's every unit or just every one in Canada, and if the 3 dollar Voodoo app is necessary to fix it!

k00zk0 said:
So after getting CM7 and Faux's OC/UV/etc/Voodoo kernel I still have noise with the sound. Do I need the Voodoo app to enable a different kind of processing or something? I cleared 3x caches/data, installed .zips: CM7 b89, gapps, and Faux [2.6.32.41] (v0.3.4) before restarting.
This makes the sound even more apparent: Go to a silent place and turn the volume on the phone all the way down to vibrate. Put the speaker at the bottom right into your ear and push volume up once. You'll hear the quiet boop tone and a second of very loud hiss before it cuts out. Two new units fresh out of the box have had this same noise. I can't believe users, especially devs don't notice this or see it as irregular, so I must be doing something wrong with Voodoo, and every unit in Canada is the same hardware-faulty. I've got three hours to swap it for the nexus; a primary use for this phone would be monitoring detailed music, and this is an unacceptable level of noise. Please try this and let me know if it's every unit or just this one, and if the 3 dollar Voodoo app is necessary to fix it!
Click to expand...
Click to collapse
I had never noticed the issue before, but when performing your test I hear it. This isn't a precisely calibrated, professional audio-phile level piece of equipment. For most people, this would not be an issue. If it is for you, then this is likely not the device for you.

Persistant Volume Issue in Gingerbread

Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
open1your1eyes0 said:
Hmm maybe it's just me but I think I discovered the oddest bug ever. For some reason, the first sound I hear after like 30 seconds of idle is quieter than what I'm set to in the volume settings and then if I keep using the device without idle all the sounds are loud like normal after that first sound.
For example, I have the device locked with screen off for a while, I unlock the device and the unlock sound is really quiet, then I immediately lock it and unlock it again and now the sound is loud like normal. I keep doing that and it sounds fine each time after that, but as soon as I lock it and leave it idle for like 30 seconds or more and unlock it again, the unlock sound is quiet again.
Also this doesn't only affect the unlock sound, it affects everything, notifications, alarm, ringer, etc....and all my volume is set to maximum I even checked with a 3rd party app. The same thing happened on the previous 2.07 and 2.10 leaks, it's almost like Gingerbread introduced this weird "automatically lower master volume after idle mode". I can't seem to find any option that would affect it.
Click to expand...
Click to collapse
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.

I've noticed this as well. I didn't find it to be a big deal, but thought I'd share.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1

all i know is even with volume+ the volume sucks on this phone. my wife's lg vortex is 5x louder. we need a dev to look into this.

I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.

arunningpir8 said:
I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.
Click to expand...
Click to collapse
aosp roms are louder but not loud enough. we for sure need a volume boost. i cannot imagine it would be that hard to do.

I was just getting ready to start a thread about a possible volume booster.. I can't remember if it was the tb or fascinate i had it on but, adrynalyne had a program called drm i think in his roms that enhanced the volume.. the problem I'm having is the media volume.. I'm trying to listen to MLB at bat here at work but can barely hear the broadcast.
Sent from my ADR6400L using XDA App

Hmm volume booster does seem to be a good workaround idea but I think the main issue is the fact that the volume level automatically changes regardless of the volume loudness. If only someone might be able to figure out what this can be caused by.....
Also I noticed something interesting today. On some sounds it actually seems like it starts off quiet and then makes it louder while the sound is playing. It's hard to tell cause it's so fast but it's definitely noticeable in some cases.

On cm7 there is an option to play notifications and ringtone through the speaker (even though I thought they did anyway) but I haven't noticed the problem with that selected.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1

someone should look into the lg vortex volume and try to port the mod over. my wifes phone is 10x louder than my tbolt. hers is aosp too.

FYI, I have only tested this on the official leaks. No custom ROMs or AOSP yet. Though I'm quite tempted to find out if this occurs on other ROMs as well (especially AOSP).

open1your1eyes0 said:
Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.
Click to expand...
Click to collapse
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk

nelboy said:
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?

open1your1eyes0 said:
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?
Click to expand...
Click to collapse
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk

nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm I see. FYI, I also noticed this issue is extremely obvious when opening the phone dialer for the first time and just press like the number 1. You can hear for a split second as if it "boots up" the audio amplifier the dialing sound for the button grows from silent to normal volume. Then as you dial the rest it sounds fine. But cancel out of the phone dialer and back into literally after like as short as 5 seconds press a number on the dialpad again, you hear it making dialing sound quiet to louder and then normal for the rest of the dialing.
Such a bizarre issue, I really don't understand why this problem just occurred in Gingerbread builds if it's been absolutely fine on older Froyo builds. You would think something as obvious as this would be one of the first bugs they try to resolve. And it seems like it wouldn't be that hard also (assuming it's just a setting in the kernel coding or something).
FYI, if it helps anyone willing to look into it I found out the audio amplifier for the Thunderbolt is a TI TPA2051.
I am really hoping some of our higher up guys can take a look at this. I am really curious to know what (if anything) can fix this issue.

i do know the overall volume on sense roms are much quieter than aosp. what a waste of a good speaker. we for sure need a fix here.

It might not be as easy as it sounds. Audio can be handled quite differently from OEM to OEM. I'm not sure if the thunderbolt is using the native Android audio or if HTC is using their own implementation. You also have to throw the audio Codec into the mix. Here is a link that although it doesn't explain our specific problem, you can see the complexity and the inherent issues with Android audio http://groups.google.com/group/android-ndk/browse_thread/thread/1744088af0924ed9/7170773c13aabe2f i'm not sure about now but the general consensus with audio developers used to be that google needed to stop trying to implement fancy bells and whistles in the audio and get a good solid foundation to start with. Gingerbread was supposed to address some of these issues but I don't believe it did.
Anyway, i'm not positive but you may notice the problem more in gingerbread because there were quite a few changes in the native audio implementation.
Sent from my A501 using Tapatalk

nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Gingerbread Kernel Source for Thunderbolt just released: Link

I know this thread is old, but something i've noticed in regards to this. Im running a semi-stock ROM (xda-bolt), with a stock kernel. I noticed the volume changes don't happen on this ROM, however with a modified kernel such as IMOs 6, the problem arises. Any other non-stock kernel i've used has this problem, but stock kernels do not.

Terrible Bluetooth Range

I'm curious if anyone else is having this issue or can confirm this is happening on their phone.
I'm pairing my phone up to a bluetooth car stereo (4 different ones) and a couple bluetooth sound docks, and the result is the same no matter what.
If I walk more than a couple feed away the music cuts in and out. it completely disconnects at around 12 feet.
I have never seen bluetooth range this poor, even on my cheepo chinese bluetooth adapter a coulpe years ago.
I called HTC and their only options were telling me to factory reset my phone.

I believe it is by design as part of HTC's "aggressive" power management...I have tried to find a way to increase the Bluetooth power but have not been successful...I have to be no more than 2 feet or so for mine to work..I'm sure there is a way to increase bt power but I'm not sure how...I think I remember seeing this in another thread..
Sent from my HTC One X using xda premium

^It was probably my first thread.
I'm assuming the reason the range is so bad is because the phone is running in low power mode, a feature of bluetooth 4.0.

Yeah, BT 4.0's main attraction is the low power usage. You can't have both great range (the old BT devices) and great battery life. Given a choice, I'd prefer great battery life.

foxbat121 said:
Yeah, BT 4.0's main attraction is the low power usage. You can't have both great range (the old BT devices) and great battery life. Given a choice, I'd prefer great battery life.
Click to expand...
Click to collapse
Bluetooth 4.0 is multiple standards of bluetooth plus a low power version.
It should have better range than bluetooth 2.0, but with the added ability of a low range/low power mode.

The audio will cut in and out even if the phone is just in my pocket and I am using a bluetooth headset (Motorola Elite Sliver). If I cant find a way to fix this or it doesn't work with a different headset I am not gonna be able to keep this phone. I really like the device but the non-existent multitasking and the terrible bluetooth performance is pushing me away. When I work I use my bluetooth all day for either customer calls or just to listen to music/radio on down time and I can't deal with this for too much longer. I'd hate to go back to my iPhone but I may have to unfortunately..

pretty disappointed.
I'm also out of my return policy on this phone now, and they have no other good phones.
Hopefully htc comes out with a fix for this soon.
I've called them 3 times now and havn't gotten a single good answer to why its so bad.
Also emailed them and still no response.

I have also noticed poor range. Much less range when streaming Bluetooth audio to my LG soundbar compared to my iPad and buddies iPhone.

UseYourIllusion said:
The audio will cut in and out even if the phone is just in my pocket and I am using a bluetooth headset (Motorola Elite Sliver). If I cant find a way to fix this or it doesn't work with a different headset I am not gonna be able to keep this phone. I really like the device but the non-existent multitasking and the terrible bluetooth performance is pushing me away. When I work I use my bluetooth all day for either customer calls or just to listen to music/radio on down time and I can't deal with this for too much longer...
Click to expand...
Click to collapse
Same Here.

Me too, This is the worst BT I have ever had on a device.

+1
If my headset is on one ear, but the phone's in the opposite side's pocket. It cuts out.

ackliph said:
+1
If my headset is on one ear, but the phone's in the opposite side's pocket. It cuts out.
Click to expand...
Click to collapse
hey guys, i just bought a One X and im having similar issues. there should be no excuses to have bluetooth cutting out like this on a new phone. My old Desire HD did it and i just thought it was because i had dropped it, but looks like its a HTC thing!

pappas99 said:
hey guys, i just bought a One X and im having similar issues. there should be no excuses to have bluetooth cutting out like this on a new phone. My old Desire HD did it and i just thought it was because i had dropped it, but looks like its a HTC thing!
Click to expand...
Click to collapse
I have no problem at all anywhere in my car, I listen music and radio an average 40 mins a day (while comute). I have a bluelogic bt that came built-in the car.
I also haveno problems and no cutoffs on my stereo bt headphones and I often leave my phone on the table while I workout (true, under 10 feet away). If that matters, I'm on 2.20 stock.
Sent from my HTC One X using xda app-developers app

Same here
i never used bluetooth with my ONE S before now. But I have moved it in to take over my business phone needs and replace my Sensation 4g. It is definately worse range. And if it it 10-15 ft away on the hood of my truck and i turn my headset away from the phone, the signal from my phone can't carry through my head. The sensation had no problems. The newer plantronics headsets are worse than the older ones as well. And putting the phone in my work belt on the opposite side from the earpiece is really bad. I don't know what to do. Might be time to fix my sensation and move back to an old headset.

Ringer Volume

My wife just got a blaze coming from a MT4G. Her ringer volume is extremely low and we've turned the setting up all the way. Is this a known issue or has anyone had similar issues? If so what was done to fix it?

claytonj said:
My wife just got a blaze coming from a MT4G. Her ringer volume is extremely low and we've turned the setting up all the way. Is this a known issue or has anyone had similar issues? If so what was done to fix it?
Click to expand...
Click to collapse
Haven't really had a issue with sound volume. You may want to give Volume+ a go. Great app and I have had it installed on every phone I ever owned even when I didn't need it.
Sent from my SGH-T769 using XDA Premium App

Allow me to put on my cynical, bitter, jerk hat.
You're getting old man. You can use a different ringtone file that you might have better success with. Have one you like, but it's not loud enough still?
Throw the file in audacity or some other sound editing application (for your desktop) and raise the DB gain a few points.
Presto, now you can really annoy people with the ringtone. (If you raise the DB too much, the sound will distort of course)

It seems you have a cynical edge to every post...I've been lurking around the Blaze forum for tips and all I have seen is you interjecting your opinion as gospel wherever you go.
Volume + does not work, along with several other apps...I have tried to no avail.
altering db levels has minimal effect with this phone. I imagine the audio processor clips at a certain level so regardless of the limit on the file, the internal amplifier will not allow beyond a certain level so you are pushing an overdriven input to a clipped output. I have yet to measure this, but can tell you that by adding +6db gain to an audio file, which essentially doubles the output power twice over it's existing level, the overall difference in output through the speaker is negligible where it should have been noticeable.
I imagine the changes must first take place in the phone software, which up until this point has not happened most likely due to the fact that no developers have these lesser phones.
A small lesson in decorum...advise as though you think you MAY be correct, not as though you are sure you are. Your advice MAY be far more welcomed.

Let's have an internet argument.

Cirkustanz said:
Let's have an internet argument.
Click to expand...
Click to collapse
lets not...
if you dont have anything nice to say.. dont. it is not welcome on xda. <-- (period)

I think my 1st gen vibrant is louder than the blaze...just by a little though. I love how fast the blaze is though.
Sent from my SGH-T769 using xda premium

I got a Blaze last week. I quickly noticed that the ringer and speakerphone volume are quite low, compared to other phones I have (Samsung Exhibit 2, Motorola Defy and Nokia C-7). I was hoping to find that my sample is defective, but after reading this thread I understand that they are all like that. I like this phone a lot, but for me it fails in the most basic functionality.