Hi.
I am having this weird thing with my TP2.
If I am in the middle of a phone call and someone else tries to call me I can head the "knock-knock" sound normally but after that the person I am talking currently with can not hear me anymore. I still can hear him/her.
Any suggestions?
I have tried a few ROM's now and the thing is still there. I have updated my radio and next thing is that I am going to buy an iPho... ... take the call waiting option off.
My phone is having the same problem! When I get a call while on a call (call waiting beep) suddenly nobody can hear me anymore! If I click over then "sometimes" the second caller can hear me and sometimes they cannot. I am currently using radio rom ver. 4.49.25.77 and energyrom build 23678. The problem started on a previous version of the same rom but continues, and it is quite distressing and unprofessional to get so many "dropped calls" (how else do you describe it to your business associates!). Does anybody else have this problem or better yet a fix for it???
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 .
Hey guys,
When im connected to my car's hands-free system via Bluetooth, whenever I receive a call and I pick up, I can hear the other party for about 2 seconds, then nothing...
The call doesn't drop but neither I nor the second party can hear each other . It's as if we've both muted the call.
If I'm making the call, however, everything works just fine...
I've updated my ROM (v4.0.4 Sense v4.1) and changed my kernel (Faux123 007)
I don't have this problem on my DHD ..
Any ideas?
Sent from my HTC One X using Tapatalk 2
I'm sorry for bumping this thread, but the problem is still there and no one has replied to it.
I haven't been able to find any solution yet.
Hopefully someone can help me out..
hangouts dialer problems mic not working end call speaker not working
Hi,
I have a couple android phones and hangouts dialer works just fine on my rooted htc evo 3d. The galaxy s3 sprint phone has problems with hangouts dialer that maybe some one can help me with.
The microphone is not working again. Last time I did an update it stopped working so I uninstalled and reinstalled and it started working again. Today it will not work again and I tried reinstalling the app but it did not work.
The speakerphone and end call button will not work on the galaxy s3 sprint phone. when I select these items it takes me back to the main dialer page showing an ongoing call. I can not hang up and I have to shutdown the phone to end call. If I have bluetooth connected these end call and speakerphone buttons will work though.
Does anyone know what the problem is with the galaxy s3 on hangouts dialer? Maybe I should just stick to HTC phones for now on?
Same problem here. Only fix so far is using a Touchwiz ROM. Lame. Hopefully someone fixes this. Stay vocal and talk to the devs. Ive been trying to sort this out all month. No one is of much help, honestly.
STAY VOCAL.
totbl said:
Same problem here. Only fix so far is using a Touchwiz ROM. Lame. Hopefully someone fixes this. Stay vocal and talk to the devs. Ive been trying to sort this out all month. No one is of much help, honestly.
STAY VOCAL.
Click to expand...
Click to collapse
I have the same problem. No one can hear me when I call them on google hangouts with out bluetooth. If I used a wired headset they still cant hear me. They can only hear me if I use bluetooth
customromlover said:
I have the same problem. No one can hear me when I call them on google hangouts with out bluetooth. If I used a wired headset they still cant hear me. They can only hear me if I use bluetooth
Click to expand...
Click to collapse
on the latest CM11 and 12.1 (unsupported) I found that it activates the microphone on the TOP of the phone, rather than at the bottom. Not sure how to swap it around. Had to go back to stock
I noticed that the "mute connected phone" stopped working for calls since the latest wear update (1.0.4.1580939) . It works fine for notifications but phone calls still ring my phone. Is it only me, or is it a general problem?
(Nexus 5, Android L - LRX21O)
Seems ok for me. Maybe its an Android L problem?
I am still on Kit Kat on my Note 3, unrooted.
Sarusani said:
I noticed that the "mute connected phone" stopped working for calls since the latest wear update (1.0.4.1580939) . It works fine for notifications but phone calls still ring my phone. Is it only me, or is it a general problem?
(Nexus 5, Android L - LRX21O)
Click to expand...
Click to collapse
Mine mutes things during the day but not at night, I'm gonna request a call back from Google wear support and try to get it fixed.
I have the same problem, since android 5.0
Guillaume CdF said:
I have the same problem, since android 5.0
Click to expand...
Click to collapse
wear app 1.0.5 doesn't fix it, looks like this is YET another issue that will never get fixed.
mute not works during calls
after updated to lollipop mute stopped working during calls, is there any alternate way to use it? thanks.
Any fix for mute issue?
Any fix I am badly needing.
Sent from my GT-N7000 using Tapatalk