I'm running AOKP 35, and I'm being told by multiple people that when they talk to me, they hear an echo of themselves.
I've confirmed this with 3 people now, on cell and land lines, and cannot figure out what is going on.
Has anyone else experienced this? I'm not hearing an echo of myself, but rather, the other person hears themselves echo. I'm about to perform some tests:
1. Install stock ROM and retest
2. Test without the case installed on the phone
3. Turn the vol down on my ear-speaker
UPDATE: see my post below. I have now confirmed AOKP to be the issue. Frustrating, but hopefully ProTekk will be able to tackle this one.
I only seem to have that on bluetooth--there are some other threads on speaker issues also--
I just got off the phone with my brother (he called me). He has a One S also and is running AOKP.
I could hear myself echoing also. So yeah it looks like it might be an AOKP thing.
OK, I've done some testing, and I am 100% sure that AOKP is the culprit.
ProTekk: On a fresh installation of b35 and 4/22 gapps and NO OTHER INSTALLS (apps, etc), the echo occurs. Here's my findings:
1. If another T-Mo user calls me, their end only rings once, then goes silent. My end rings more than once, and I answer only to hear silence as well.
2. I can call other T-Mo users, and DO get through. However, they can hear an echo of themselves quite a bit.
3. In-call volume is quite low compared to stock ROMS, so there's a volume issue here as well.
I've talked on the phone w/b35 with several people today, and all of them noticed an echo. I also called myself from a landline and verified it. I then decided to wipe everything (/system too) and install the stock USA ROM. Upon installation, I retested with these people, and not a single person had an issue with echoing. I also noticed that the volume through the ear-speaker was significantly louder on stock ROMs.
With this in mind, I decided to make absolutely sure that AOKP was the problem, so I wiped everything again, and then installed AOKP b35 and 4/22 gapps. I made sure not to install any other apps or utilities. I immediately tested it in the same process, and everyone reported back that they were once again hearing the echo, and I was once again experiencing an issue where T-Mobile users cannot get their calls through to me. Land lines can call me just fine, interestingly.
ProTekk: I hope this information is helpful, as I've tried my best to eliminate any doubts in my testing.
I'd like to ask that each and every one of you that is running AOKP on a USA One S (please indicate which build/milestone of AOKP) to test what I have just laid out.
I'm 99% sure that everyone else will get the same results. I just need a few of you to confirm, then every last doubt will be removed.
UPDATE: OK, I've talked to some people in the CM9 IRC channel, and theyre experiencing similar issues (on US models, if it matters). This is obviously not JUST aokp, but rather a problem with source-based ROMs. I'm betting MIUI has the exact same problem as well.
Callers hear an echo on mine as well. Running build 35.
Sent from my HTC One S using xda premium
AOKP build 36 does not fix this either
---------- Post added at 09:41 PM ---------- Previous post was at 09:19 PM ----------
The echo is worse when on speaker phone.
In my tests, on speaker phone you can clearly hear just about everything you just said as an echo.
Without speaker phone, you'll faintly hear the last bit of whatever you say and maybe a little in between.
I would test it but AOKP just boots straight to recovery. Though I did get MIUI up and running (was loving it) I could receive calls from anyone, including T-Mo users, but couldn't make any outgoing calls.
The next release of AOKP will have this issue fixed.
ProTekk said:
The next release of AOKP will have this issue fixed.
Click to expand...
Click to collapse
Awesome. Thanks Jacob! Always appreciated! Can't wait to get back to my fav ROM.
Related
Hey guys. I installed CM7 over the weekend and am sporadically getting issues when receiving calls. Occasionally I get what, more or less, sounds like an odd ring/alarm sound over my set ringtone. This issue isn't a big deal in and of itself, but when it happens, the ring/alarm sound continues on through the call and both the person who made the call and I can hear it. This results in me having to end the call and call them back. I never have this problem when making calls and it doesn't happen all the time when receiving. The way the lock screen stutters when it happens makes me think it has something to do with it but that's a wild guess.
Is anyone else running into this issue? It's happened twice since I installed CM7. Everything else seems to be working great btw, it's nice to have this rom out. Just thought I should make this post since I doubt I'm the only person with the issue.
Also -- I don't use any ringtone apps or sound software at all other than whats on the rom.
There's probably a hundred posts about this over in the fascinate forum for this rom. I have been running CM7 for a few days now and haven't had this happen. I don't get many calls tho. Check out the fascinate development thread for more info on this.
Sent from my SCH-I500 using XDA App
Ahh. I should have done some searching over there considering it's a port. My apologies - thanks for the heads up!
Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot
fix the a2dp on gb and i'll give you your first donation.
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..
Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.
So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium
ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?
No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?
hey,
I bought the nexus s (9023) about two months ago, stock rom, not rooted, and for the last week or two, it started making problems.
about 1-5 times a day, i can't here the other side at all. as if it's on mute. not even the ringing tone, before I'm answered. the only thing that solves it, is to restart the phone.
in other forums i've read that it's a mess, and that i should use my warranty. the problem is i bought the phone abroad, and shipping it should take about 3 weeks.
is it a common issue?
can i solve it alone, mabye by switching to a non-stock rom?
i'll be very happy to read some good news here, but bad news is better than non.
thanks a lot,
tal
p.s, iv'e downloaded system info to monitor the temp, and it doesn't happen necessarily when the phone is hot.
I don't know... I am rooted, I have used 5 different roms since purchasing my phone.
Stock
CM 7
Savaged Zen
Oxygen
Soju
I have also used several kernels
CM Stock
Netarchy
Matrix
James Bond
Trinity
So far, on all roms and kernels I have experienced the same problem. You make a call and it connects, looking at the screen the time counter is going but there is no sound; it will sit there and hold the call for 30-55 seconds then ends call. A quick redial and bam it works. Some people have reported that they answered and there was nothing. I don't know, it's really obnoxious.
The other, more annoying problem is that randomly on calls throughout the day the phone will just reboot itself. Right in the middle of a call. AHHHH like 3-5 times daily!
help, anyone?
i'm stuck with this, and a bit clueless.
Well, somehow I discovered that the problem is related to the bluetooth. as long as it's turned of, nothing will happen, on the other hand, when I use my earphone (most of my conversations happen while driving) i need to restart my phone every 1-2 calls
any ideas?
just u can't hear other one while calling u?
thanks.
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
tal89 said:
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
Click to expand...
Click to collapse
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
it's quite obvious, unfortunately it doesn't work.
cutiyar said:
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i can't hear, and he can't hear as well.
tal89 said:
i can't hear, and he can't hear as well.
Click to expand...
Click to collapse
hehee its problem ,
am really disappointing with nexus s , but i dont have enough money to buy HTC product again.
any solution?
Hi, did anybody have any solution to this problem?
I live this problem on almost half calls of specific numbers.
I am desparate...
Try setting discoverable timeout to never? Have you tried a different Bluetooth device?
Sent from my Nexus S 4G using xda premium
I have this problem too. This seem to happen on some Kangs and nightly, but not all of them. I can't hear when someone calls me. But when I call someone, I can hear them. I always have Bluetooth off (do not use them).
I live the same problem. No problem for outgoing calls. For incoming calls, I cannot hear caller's voice but they can hear me. It is not for all numbers.
I am on t-mobile and nexus s (cynagenmod nightlies). For all incoming calls from tmobile numbers no problem. But for almost all other carriers, it is just random.
I feel like I started having this problem after updating from CM 7.0.2 to 7.1 RC and thereafter(but not very sure on this).
If anybody still following this topic, I would suggest you to contact samsung if you still have warranty. On the second attempt they sent me a brand new phone with box and accessories.
Sent from my SGH-T989 using XDA
Or, you might give it a try with a different radio for your model:
http://forum.xda-developers.com/showthread.php?t=1116884
If you go this road, make sure you backup your EFS folder.
What i would do is if it is still in warranty just give it back to them and they'll probably give you a new phone. Since you said it takes 3 weeks to ship, just wait for it and use another phone if possible. Its not like your life is going to end. I think the problem is, not every phone is the same so there will be problems especielly when flashing a rom. For example unstable roms might not allow you to use this app or have serious effects on your phone.
Best to give it back to samsung and get a replacement.
Hello,
I've been a user of the xda ROMs for quite some time and i appreaciate all the work that's been put into the community.
Sadly, i have stumbled onto an issue i cannot solve myself, so i am seeking your help.
Description: When receiving a call and answering it (phone vibrates and rings), i cannot hear the other person, but they can hear me. (Speaker on/off doesn't do a thing, volume rocker up/down either). If the person calls back within a few minutes, i can almost always hear them and have a normal conversation. This does not happen in 100% of the cases, but in more than 50%. I have switched ROMs, kernels and radios (ATM i have CM7.1 RC, mar1x bfs v4,5, and XXKB3)
Is there any hope?
same issue on i9020t
I been having the same issue, but not quite as frequent, on my I9020T. I've experienced it with Cyanogenmod 7.1RC1 and NSCOLLAB (also based on CM71). I think I had it with CM7.0.2 and CM7.0.3, but can't remember for sure. The problem does not occur when I revert back to stock 2.3.4 rooted.
A somewhat related post in this forum, http://forum.xda-developers.com/showthread.php?t=1188264, got me thinking. The OP had a similar problem on an I9023 when bluetooth was enabled. I've noticed on NSCOLLAB that DSPManager is running a "Headset" service. I do not have DSPManager installed on my stock install.
Can someone more knowledgeable tell if its possible this service could be related to the problem with callers not being able to hear me. FYI, my bluetooth is normally off and I don't use a headset. I'm back to running NSCOLLAB 1.3.8, but I've disabled the Headset service. If the problem doesn't occur for a couple days, I think I may have something.
dinuvali, is the Headset service running on your build?
Removed DSPManager earlier. Just answered a call where they hear me but I can't hear them. They called me back, all normal.
Oh well, rolling back to stock for now.
Sent from my Nexus S using XDA App
Thank you for the reply,
Yes my CM 7.1 is running the DSPManager service.
Also, my neighbour who has the exact device as me, but stock unrooted, has never experienced this problem.
Along with this problem of not hearing the other person on the first call, i also get the dropped call once in a while (not only after 3 mins of talking, but also while the phone is ringing and they still haven't picked up yet)
From all the posts i've read concerning this issue, i think it's mainly a hardware issue, but maybe it can be bypassed with some sort of tweak.
Major breakthrough imo
Pressing Hold (left upper corner) and then unholding will render me able to hear the other person!
dinuvali said:
Major breakthrough imo
Pressing Hold (left upper corner) and then unholding will render me able to hear the other person!
Click to expand...
Click to collapse
Great find! Come to think of it, I never had it happen when I answered someone and immediately hit speakerphone, something I do alot when in my car mount.
I think I'll reload NSCollab, new version just came out today. When it happens again (unless they fixed it) I'll try this out. Thanks!
I want to see how many of you are experiencing an issue on AOKP/CM9/MIUI where the person on the other end of your phone conversation is hearing an echo of themselves.
I've confirmed this with several other users, and done some testing on the matter, and find that stock-based ROMs (including all variants, like Black Dragon, Noble, etc) do NOT exhibit this behavior.
Who else has this issue? Many people don't even know they have it, because it affects the OTHER person, not the user of the One S.
There's also another issue I think that's related, where other mobile phone users have trouble getting calls through to the One S. It'll ring once on their end, then suddenly go silent.
http://forum.xda-developers.com/showthread.php?t=1653914
EDIT: Just noticed you started this thread as well, my bad. I'm sure you've seen it already.