In the last few days I've noticed, or the people I call rather, have noticed that the noise cancellation doesn't seem to be working on my HOX. I've never faced this problem before, and I think it's worse that not having it at all. Basically the noise cancelling mic is picking up the background noise, but not blocking it! So it's twice as loud at the other end, one feed from the NC mic, and one from the normal mic - if that makes Sense (pun unintended).
I can't figure out what may have caused this. I've been cycling through the same custom ROMs - CM10, ICJ, Football, Renovate - none of which update the radio afaik. Never had the issue before with any of them. My radio version number is the same as as it's always been (see signature).
Any ideas? Has anyone had this prolem before? The only thing I did differently in the last couple of days is use the WiFi hotspot as I'm not home. Could this be messing up the radio?
Solution-wise, I am thinking of first trying to reinstall the ROM after full wipe, and then chek if NC is working fine BEFORE I use the hotspot again.
If not, I think I may have to restore my Nandroid, which will hopefully reinstall the radio, and then try again.
Thanks to anyone who can help!
Sorry to bump an old thread but has anyone found a solution for this problem? I'm running cm11 nightlies and since the last few days I've been experiencing this exact same issue. I have to literally put my finger on the noise cancelling mic for the person on the other side to hear anything that I'm saying! I've searched all over the internet but haven't found any solution yet.
Related
Sorry if this has already been discussed. I searched for the same issue but didn't come up with anything, and if it has, can somebody post a link to the thread/threads with the same issue?
I'm rooted and installed the stock Gingerbread 2.3.4, build 4.06.605.3, and the first thing I noticed is that when I'm on a call on my Jawbone Icon and I get a text message while on a call, the call gets transfered to the handset. I've tried everything possible with unpairing/pairing/rebooting/settings, but every single time it disconnects the call from the Icon and transfers it to the handset once a text notification comes through.
I found this on the HTC forums about the Dinc2, (community.htc.com/na/htc-forums/f/124/t/12762.aspx), and it appears to me to be a known Gingerbread issue that many other people are having and not just a hardware issue with a certain phone or certain BT earpiece.
Does anybody else know of this, have this same issue, and if there has been a fix or patch for it yet? I'm about ready to go back to a Froyo ROM or try a Gingerbread one where it works if I can find one I like, but for some goofy reason and after all the futzing around I've done with different ROMS, I always seem to go back to the stock one with Sense UI.
Can anybody help me out here? Thanks a ton!!
Drumznut said:
Sorry if this has already been discussed. I searched for the same issue but didn't come up with anything, and if it has, can somebody post a link to the thread/threads with the same issue?
I'm rooted and installed the stock Gingerbread 2.3.4, build 4.06.605.3, and the first thing I noticed is that when I'm on a call on my Jawbone Icon and I get a text message while on a call, the call gets transfered to the handset. I've tried everything possible with unpairing/pairing/rebooting/settings, but every single time it disconnects the call from the Icon and transfers it to the handset once a text notification comes through.
I found this on the HTC forums about the Dinc2, (community.htc.com/na/htc-forums/f/124/t/12762.aspx), and it appears to me to be a known Gingerbread issue that many other people are having and not just a hardware issue with a certain phone or certain BT earpiece.
Does anybody else know of this, have this same issue, and if there has been a fix or patch for it yet? I'm about ready to go back to a Froyo ROM or try a Gingerbread one where it works if I can find one I like, but for some goofy reason and after all the futzing around I've done with different ROMS, I always seem to go back to the stock one with Sense UI.
Can anybody help me out here? Thanks a ton!!
Click to expand...
Click to collapse
Well i just tested on mine. I called my buddy and then had my wife text me wile i was talking and it did not swith to the handset it stayed connected to my jabra earpice. Not sure what could cause this, never really use my earpice that much but it seemed to work correctly for me.
cmlusco said:
Well i just tested on mine. I called my buddy and then had my wife text me wile i was talking and it did not swith to the handset it stayed connected to my jabra earpice. Not sure what could cause this, never really use my earpice that much but it seemed to work correctly for me.
Click to expand...
Click to collapse
Hmmmmm... I'm not using the GingerTiny kernel, just the htc 2.6.35.13-g55a06e5 kernel. What could be the difference...
Not sure, im not familiar with bluetooth or if it has anything to do with the kernel.
Interesting, I've heard several others mention this problem recently and another who added the same thing happens when getting a text while having a call on speakerphone. Drumznut, do you have the 2.15.10.07.07 radio? If so, it'd be interesting to see what would happen with the GingerTiny kernel since that combo is working for cmlusco.
@cmlusco, can you replicate it with the call on speakerphone + receiving a text scenario?
iowabowtech said:
Interesting, I've heard several others mention this problem recently and another who added the same thing happens when getting a text while having a call on speakerphone. Drumznut, do you have the 2.15.10.07.07 radio? If so, it'd be interesting to see what would happen with the GingerTiny kernel since that combo is working for cmlusco.
@cmlusco, can you replicate it with the call on speakerphone + receiving a text scenario?
Click to expand...
Click to collapse
Yes I'm on the 2.15.10.07.07 radio. My phone is listed as:
Android Version - 2.3.4
Baseband Version - 2.15.10.07.07
Kernel Version - 2.6.35.13-g55a06e5 [email protected] #1
Build Number - 4.06.605.3 CL140944
Software Number - 4.06.605.3
Browser Version - WebKit/533.1
PRI Version - 1.28_002
PRL Version - 52011
ERI Version - 5
I'd give it a try if I knew where to get the GingerTiny Kernel. Anybody have a link to it or have any idea what else to try?
Drumznut said:
I'd give it a try if I knew where to get the GingerTiny Kernel. Anybody have a link to it or have any idea what else to try?
Click to expand...
Click to collapse
http://www.incredikernel.com/?page_id=10
Interested to see how it goes.
Don't mean to be a pain but any new info on this? Quite a few people experiencing this it seems.
hi, i am not having this issue, but i also am using a different BT. I am using nills business sense3.0 v2.3 and kernel gingertiny 2.6.35.10 with the 7.07 radio. the bt phones are altec lansing backbeat 903 BT headset.
i had an idea, it may have something to do with the way the headset handles audio, as a test try setting your text ringtone to silent, and turn off the vibrate too just in case, now try replicating the problem and see if it still switches your audio to the handset. If this fixes the problem then it has got to do with the way your headset deals with notifications as a posed to regular audio. unfortunately i have no idea how to fix this problem other than not setting the notification, and i am sure that is not an acceptable solution, on the other hand you may only have to change a setting in your headset.
well anyway that just popped into my head when i was reading your post, i may be way off base but i figure it worth a try, and hopefully it may be helpful.
Azag Thoth said:
hi, i am not having this issue, but i also am using a different BT. I am using nills business sense3.0 v2.3 and kernel gingertiny 2.6.35.10 with the 7.07 radio. the bt phones are altec lansing backbeat 903 BT headset.
i had an idea, it may have something to do with the way the headset handles audio, as a test try setting your text ringtone to silent, and turn off the vibrate too just in case, now try replicating the problem and see if it still switches your audio to the handset. If this fixes the problem then it has got to do with the way your headset deals with notifications as a posed to regular audio. unfortunately i have no idea how to fix this problem other than not setting the notification, and i am sure that is not an acceptable solution, on the other hand you may only have to change a setting in your headset.
well anyway that just popped into my head when i was reading your post, i may be way off base but i figure it worth a try, and hopefully it may be helpful.
Click to expand...
Click to collapse
Don't mean to be a pain but any new info on this? Quite a few people experiencing this it seems.
Click to expand...
Click to collapse
Thanks for the suggestion and sorry I didn't get to the testing sooner...
Here's what I've found:
I performed all the same tests with the stock htc kernel and with the Gingertiny kernel and had the exact same results.
I use the apps SMS Popup and Missed Reminders, so the first thing I did was uninstall both those apps and run some tests.
Receiving a text message while on my bluetooth still transferred my call to the handset.
Setting the text vibration to off but leaving on sound notification still transferred my bluetooth call to the handset.
Setting the text notification sound off but leaving the vibrate on still didn't matter and it still did the same thing.
Setting the text sound off and the vibrate off too did the trick and there was no transferring of the bluetooth call to the handset when I received a text message.
I then reinstalled SMS Popup, left the text sound and vibrate off and had no problem.
I then installed NotifyMyWay to see if that app's vibrate notification would work and not transfer the bluetooth call to the handset and it worked fine with "no" call transferred to the handset when I received a text message.
So yeah, it's something with how the Sense UI and the handset are interpreting the notification of the incoming text message while on a bluetooth call. I can live without a text sound notification and will have to live with turning the sound notification on and off if and when I have to but I would like to see a patch out to correct this issue. Will that happen?? Good question.
Let me know if anybody has any suggestions or other tests to try. Thanks!!
I am glad i was able to help .
First off, forgive me if this was already answered, I tried searching for about 15 minutes before I decided to post this.
As the title states, I'm having an issue with my gnex where I get this high pitched and crackling sound when receiving SOME incoming calls. I can't hear the person, and whenever they speak, the noises get louder so I can't hear them at all.
I think it's software, rather than hardware, since it doesn't happen on every single incoming call. From what I can tell, actually, it's totally random. But if I call the person back it is fine. They could even call me right back and it's fine.
My friend who also got a gnex from a different vzw store has the same issue. His also appears to be random.
Do you guys think it's just network, random phone problems, software issues, or all three?
Info: Verizon Wireless CDMA Galaxy Nexus running fully stock 4.0.2
For the record, I too am experiencing this issue. I also have the issue via 3.5mm jack and during other audio playback. At first I thought it was just my low-quality aux cable I was using in my car, but then I experienced it on a normal call. I was thinking software for this reason too as it happens via the jack as well as speaker... (Also happened watching Netflix, so that covers all audio output but bluetooth.)
Are people on custom roms experiencing this? I wasn't going to root this phone as I didn't see too much of a need, but I will if it will get rid of this issue.
Xavias said:
Are people on custom roms experiencing this? I wasn't going to root this phone as I didn't see too much of a need, but I will if it will get rid of this issue.
Click to expand...
Click to collapse
if by crackling you mean it almost sounds like a fax sound, squealing, similar to this description, http://forum.xda-developers.com/showthread.php?t=1453769 , then yes I had this when I ran stock but now that im running francos, AOKP, and the 4.0.3 radios(which arent included in most 4.0.3 roms), i have not had the problem.
My GF had a problem where her mic was bad, about 50% of the time i got a call from her she would sound muffled, almost as if underewater. She exchanged it at VZW and haven't had any problems since.
Hi, about a month ago I rooted my Incredible 2, and ever since my call quality has been absolutely awful. Calls sound extremely robotic and distorted. Even the dial tone when you call someone sounds distorted. I could best compare this to when you record something in an audio editor, and then adjust the levels so that the waveform maxes out into a distorted mess. It sounds like that, so a lot of depth in the sound is lost and it becomes mostly unintelligible. It doesn't seem to be related to call volume, because adjusting it just makes it softer/louder but equally distorted. I'm struggling to understand what people are saying most of the time.
This may be connected, but my signal strength has been much worse as well. In areas where I used to get 3-4 bars I only get 2 now. I actually haven't seen it go above 2 bars since I left the stock ROM. I'm guessing they might be related. I've tried flashing different radios (did 0312 initially, then tried going back to 1111, and when that didn't help went back to 0312 again to be up to date) and that didn't help, and I've tried calling *228 and that doesn't help either.
This also persists over ROMs as far as I can tell, so it doesn't seem to be a specific ROM's problem. I initially used CyanogenMod 7.2, and now I am running Kangdemnation 0.5 (ICS) and the quality/signal are exactly the same on both.
Does anyone know a solution to this? Is it a common problem? This is my first experience with rooting so I can't say I know much about what's going on behind the scenes. If I missed anything obvious to fix this let me know. Any help would be appreciated.
Have you tried flashing a stock Sense ROM?
You can try a sense Rom an update radio to 0320 an see if that helps.For sound you can try one of the equalizer apps might help.
Sent from my vivow using Tapatalk
Need some advice or trouble shooting tips.
Lately, my DHD is experiencing a sharp popping sound when I wake the device, use an app, or receive messages via Whatsapp or Line.
Presenting I am on JB and had been on AOSP for a long while. The popping sound only started recently after a period of testing Sense 3.6 and Sense 4 ROM's. Going back to AOSP, I noticed the sound right away. Even with all touch options disabled, the sound remains. It's coming from the rear speaker and even if the device is on mute, the sound can be heard.
As well, with online messaging, if I put my ear on the speaker, you can heard a slight hiss and it gradually gets louder until the pop sound cracks.
This problem doesn't happen with the new Sense ROM's I tested. What I have done was tested different AOSP and JB ROM's with the same result.
My next plan is to download a stock version on GB (ARHD is the choice I selected) and test the issue there. However, I am starting to think that I should return straight back to unrooted stock ROM, but I am not sure if that is really necessary.
My question is,,,, has anyone experienced this sound issue and if so, are there any suggestions or tips? As well, could someone experienced actually offer an explanation for the sound. Is my device on its' last legs?
I am thinking it might be kernel or radio related. I really don't know and hope someone can shed some light on this subject.
Raymond Ebertt said:
Need some advice or trouble shooting tips.
Lately, my DHD is experiencing a sharp popping sound when I wake the device, use an app, or receive messages via Whatsapp or Line.
Presenting I am on JB and had been on AOSP for a long while. The popping sound only started recently after a period of testing Sense 3.6 and Sense 4 ROM's. Going back to AOSP, I noticed the sound right away. Even with all touch options disabled, the sound remains. It's coming from the rear speaker and even if the device is on mute, the sound can be heard.
As well, with online messaging, if I put my ear on the speaker, you can heard a slight hiss and it gradually gets louder until the pop sound cracks.
This problem doesn't happen with the new Sense ROM's I tested. What I have done was tested different AOSP and JB ROM's with the same result.
My next plan is to download a stock version on GB (ARHD is the choice I selected) and test the issue there. However, I am starting to think that I should return straight back to unrooted stock ROM, but I am not sure if that is really necessary.
My question is,,,, has anyone experienced this sound issue and if so, are there any suggestions or tips? As well, could someone experienced actually offer an explanation for the sound. Is my device on its' last legs?
I am thinking it might be kernel or radio related. I really don't know and hope someone can shed some light on this subject.
Click to expand...
Click to collapse
I highly doubt that it's software related. I've not seen anyone report any such kind of behavior and neither have I experienced it with either Sense or AOSP roms. The fact that the pop sound does not happen when you're on Sense roms is a bit strange, however I think it maybe explainable by the fact AOSP versions generally have boosted volume levels for better sound.
Personally, I think that you should get the speaker module replaced before it breaks down completely (which I believe is a very real possibility given the nature of the problem you've stated).
Just tested ARHD and when I make a call, there is a slight tick or crackle sound coming from the front ear piece. The sound is faint, but when put the phone to my ear and press the call button, I can clearly hear it.
I'm going to test the original radio and see if that sound remains. If it does, it seems the previous post above just might be my issue and I really hope not.
You could also try a can of compressed air.
By the way buddy, you've been here too long to be posting in the wrong section
Sent from a dream.
Teichopsia said:
You could also try a can of compressed air.
By the way buddy, you've been here too long to be posting in the wrong section
Sent from a dream.
Click to expand...
Click to collapse
LOL,, did I? HTC Desire HD General Section? Maybe I did... Where should I post?
As for the air compressor, I did that a couple of months ago. I'll give it a go.
As for changing the radio, I did and still have that click with calls. Looking grim at the moment.
It's a thin line between where to post, but yours is a question. :beer:
Sent from a dream.
I havent been able to figure this problem out, I think my phones mic is bad.
VERY low volume. When I call people, they can barely hear me, but I can hear them perfectly. I have confirmed this by calling my other phone, I can barely hear my voice coming from the one V
I have tried rooting, rom'ing, and different kernels. What actually controls the mic? Should I try a radio update?
If there isn't an obvious answer, I think I'll try sending it in. Its only 7 months old, and HTC just fixed another One V i have that was bricked. I have also tested the same software on my other one V and the mic works perfectly...
really weird, because its just very quiet even though it technically works...
edit- the one v thats not working has a radio of 1.00.00.0521_2
and the one v i have that works fine is radio 1.00.00.0928
otherwise, everything else about the two phones is the same. hboot 1.53.0000
edit- before everyone posts like crazy trying to help me (har har), i am rru'ing back to stock, then doing an ota update to try to push to the new radio. i will see if that fixes the mic, and if not, im sending it back to htc!
ugh! partial success! :/
So after the rru, the phone took 3 different OTA updates. Then I tried calls again. I use groove ip, and on default settings my other One V works great. Again, the mic on this phone ive been working on is too quiet! BUT I do notice a slight increase in the volume.
So I went into settings for groove ip and maxed out the mic gain- and it worked pretty well! Its not quite as loud as my other one v with default settings, but it does work seemingly good enough.
So weird! I already tried cleaning the mic with contact cleaner, and even taking the rubber block out. What sucks is now, do I send this to htc anyway? I have a feeling they will tell me it works so they won't know what to do...
Ill update if anything changes...
Fixed.
Sent the phone into HTC. Not sure what they did, it didn't seem like much. But the mic works properly.
I go to install a custom rom, and mic is f'd up again! Restored the backup I made, and the mic works properly again. My other OneV doesnt have this happen with the same custom rom installed :/ The mic actually works, but what I think it is- it's stuck in speaker phone mode. It doesnt matter if your right on the mic or across the room, it sounds the same. Not very loud with lots of background noise.
So, basically, I have to leave this phone with the stock rom I suppose. If I can overclock it I'll be happy. Just so weird why my other phone doesn't have this issue after flashing to custom roms...