Database Info

Dead Mic

So I think that my mic died and I'm looking to see if anyone else has experienced this.
1.People on the other end can't hear me, I can hear them fine.
2. When I've recorded a video, the sound playback was nothing but a static, hiss.
I've made no changes whatsoever to the device in a few weeks or so. I've gone through all the settings that I can think of, but I'm still taking suggestions. Thanks gang
Bolted

I had this happen on my incredible from time to time and a restart would resolve it.
Sent from my ADR6400L using Tapatalk

i had this same problem. I called Verizon and they overnighted me a new one, no charge to me, I just had to get the old one back to them in 5 days. They sent a label with it as well. They said they were going to send me a like new replacement. I said I wanted a new one and they said they would send one. It came in OEM packaging, just phone and back cover. whether its new or 'like new' it was immaculate.

I've rebooted a few times thinking the same thing.
I did have my Dinc replaced when the external speaker fried, but that was kind of a progressive failure.
Any more thoughts or ideas are welcome.
Bolted

So I tried using the speach to text, and there's noresponse from the mic. This is just a drag.
Bolted

Well I've tried the voice search and that works. Now the speech to text works as well actually that's what I'm using to make this post. This is just weird. If it weren't so late I could call somebody to test it and see if they can hear me now.
Bolted

Latest: So, this all started yesterday. I flashed an updated radio and the problem continued. This morning I was able to flash a corrected radio update and so far have been able to make two consecutive, successful and troublefree voice calls. I hope that was all there was to it (crosses fingers, knocks on wood, etc.).
Bolted

I've got a friend who has this issue. What radio did you use to fix it.

It's not fixed, I'm still trying to sort it out. For a time I thought that it may have had something to do with the headphone jack, but it wasn't.
My next random thought was to try a different kernel. This one: a.zip seems to be working so far. I haven't had but maybe two or three calls since flashing it and no need to call anyone. Every once in a while I'll do a Voice Search, or a Voice to Text text message, and it's worked. I'll try a Voice Recording or Video as well.
The only other thing that I can think to do is call Verizon and say, Hey, manufacture's warranty.
Before I forget, the kernel is one of Adrynalnye's. Let me know how things go with your friend's device.

Talked with Level 2 tech support and the guy pretty much said that there's nothing that he can do and it certainly sounds like a bad mic. New device will be here tomorrow. Here's a Blinding Flash of the Obvious though, meanwhile I can just use my Bluetooth earpiece...duh. lol

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.

Sensation strange behavior

Got a stock sensation, since 3 weeks ago. updated all the stuff, got 2.3.4 etc.
last night i was watching a movie on my phone, and the phone randomly, without me doing something - starded to call up the last phonecall ive made. THATS STRANGE! i hung up, and it started again, but it hang up itself.
anyone with the same problem?
oh, plus, when end a call - put the phone away, the screen lights up, then turns of.
remember my phone is all stock, no S-off, or custom rom or something...

Did you have the headset in? I've read a few threads where jiggling the headset jack can cause the phone to think you've pressed the headset button and it'll dial your last number.

Actually I only used regular in-ear headset, no mic with buttons or something. Regular ones you listen to music to.

A2DP choppy

First I guess it'd be important to say I'm using Ravers (awesome) Beatiful SG4G build and I love it. It's terrific. The only thing "plaguing" me is bluetooth.
I have a Motorola S9 headset, which sounds beautiful. The problem is sound randomly seems to cut in and out at times, especially when walking around the city. I tried disabling wi-fi, but to no avail. It's fine sitting in my dorm, and seems to always be ok when the screen is on. But if I walk around with it in my pocket, sound goes to crap. Is there any known fix to regain stability.

hampsterblade said:
First I guess it'd be important to say I'm using Ravers (awesome) Beatiful SG4G build and I love it. It's terrific. The only thing "plaguing" me is bluetooth.
I have a Motorola S9 headset, which sounds beautiful. The problem is sound randomly seems to cut in and out at times, especially when walking around the city. I tried disabling wi-fi, but to no avail. It's fine sitting in my dorm, and seems to always be ok when the screen is on. But if I walk around with it in my pocket, sound goes to crap. Is there any known fix to regain stability.
Click to expand...
Click to collapse
have u had that issue on all gb or is this ur first gb?

Sadly that's hard to say. I've been using your roms since Audiophile Froyo. I just got the headset today, so I haven't been able to see if it's a rom issue, phone issue, or a headset issue yet. I'm trying to figure out if anyone else has already been through the process before I flash my phone a few times troubleshooting.
Looking around, signal issues are common with my particular headset, so it may not be a phone issue. I'll try and do some flashing to further test it, and try to use it with other phones.
So I think I figured it out and sadly I don't think software can fix it. The bluetooth has a "blind spot". The headset works fine when my phone is in a bookbag or coat pocket or sitting on my desk across the room, but it fails in my pocket. I guess it'll keep me in a good habit of actually bringing my notes to class

[Q] CM10 Bluetooth Echo

I have had the "other-person-hears-an-echo" on bluetooth a2dp in my truck since at least November. Running CM10. While it is mentioned periodically, most say the problem has been fixed on their handsets. It's driving me insane. The short version:
I think it was a perfect storm of a) CM10 bugs and, b) interface between the ville and the Clarion CZ500 in my truck. Note 1: My wife has the same audio in her car, and a stock HTC One S. No problems at all. Note 2: I always do clean flashes, wipe 3x, etc.
I am sure that whatever minor bugs in CM10 that influenced this have been fixed (NO complaints about CM10 - I've been using it since CM6 on my old MT3GS) - I can now talk to people without the echo on their end - IF...
I use a combination of tweaks to a) the Bluetooth volume on my phone, and b) the volume on my cz500. Where I place my phone (nearer or further away from the cz500 or the microphone) seems to effect things. So I'm getting closer, but...
I cant figure out a reliable pattern of tweaks to fix the problem. Some combinations work at one time, and then another some other time. The most reliable tweaks involve turning the volume on my cz500 so low that I can't hear the other party.
I've already traded the phone in (thanks TMO for an easy process and for taking a rooted phone). Before I buy another car stereo, does anyone have another idea?
Thanks very much in advance for anyone willing to take a minute here. If I've missed a post or discussion about it, it isn't for lack of trying - I've spent hours reading through the forums.