I have tried searching for the solution to my problem with no luck.
I have a rooted Inspire 4G. With the stock radio and ROM, whenever I had my headphones or my 3.5mm audio cable plugged into my phone, I could use the headphones or my vehicle's speakers for phone calls (like bluetooth). I also could hear my notification sounds (text, email) through the headphones or speakers as well. Since I have rooted my phone and changed radios and ROMs, I no longer have this capability - the calls and notifications go through the crappy phone speakers. I was wondering if anyone else had this problem or noticed the difference.
FYI - I have checked the call settings (Settings->Call) and nothing helps. I have read about HAC/TTY settings from the stock ROM/radio, but these options don't show up in the Rom I am using. I was wondering if maybe those settings made the difference and if there was a ROM or a mod that can access those settings.
Any help or direction would be appreciated.
I've flashed many many roms and have never encountered that problem. By default, it should automatically switch to headphones once you plug in the jack.
I would suggest flashing a different rom ...such as the BB Mod rom or Absolution (both are aosp roms).
Or if you prefer the stock look with sense, try Cleardroid.
I believe any of these will solve your problems ...unless its maybe hardware related (bad jack) ?
If you decide to switch & try another rom...don't forget to wipe, so you can get started fresh.
Good Luck to you.
Sent from my Inspire 4G using xda premium
Yea I've flashed plenty as well and I've never run into this problem. Sounds are routed to whatever is plugged into 3.5 jack
Dinman said:
I've flashed many many roms and have never encountered that problem. By default, it should automatically switch to headphones once you plug in the jack.
I would suggest flashing a different rom ...such as the BB Mod rom or Absolution (both are aosp roms).
Or if you prefer the stock look with sense, try Cleardroid.
I believe any of these will solve your problems ...unless its maybe hardware related (bad jack) ?
If you decide to switch & try another rom...don't forget to wipe, so you can get started fresh.
Good Luck to you.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
homeslice976 said:
Yea I've flashed plenty as well and I've never run into this problem. Sounds are routed to whatever is plugged into 3.5 jack
Click to expand...
Click to collapse
Most likely is an issue with the ROMs because after I posted this, I flashed the Revolution HD 6.1.5 ROM (w/ the 12.62.60.27_26.13.04.19_M radio) and the notification/call sound is heard through the 3.5mm jack as in the stock ROM/radio. Previously I was using the CoreDroid 8.1 and GB 2.3.5 Sense 3.0 ROMs with two different radios (12.54.60.25_26.09.04.11_M2 and 12.59.60.26P_26.11.04.21_M).
So I can't exactly pinpoint what the cause was because I (stupidly) changed two items - though I could reflash one or the other with the new radio and see if that made a difference - but I would bank on the ROMs being the problem since the both of you have not experienced this problem with the ROMs you use.
Thank you both for your input.
Radio would have no effect on this. Sometimes you just have a bad installation. This is why myself and others always make sure people know how to properly wipe their phones and then tell them to re install before validating a problem as an actual bug.
Gizmoe said:
Radio would have no effect on this. Sometimes you just have a bad installation. This is why myself and others always make sure people know how to properly wipe their phones and then tell them to re install before validating a problem as an actual bug.
Click to expand...
Click to collapse
Gizmoe, I understand that there are a lot of people who don't research and don't follow directions when flashing ROMs, so I can understand the tone of your comment. I actually do a full wipe every time I flash a ROM, upgrade or not. And before I posted this, I tried reinstalling and researching the problem. I admit that I am new to all this, so it was more of a lack of knowledge about how ROMs and radios work than ignorance because I try searching out the answer before posting.
Anyhow, I did determine the cause of my problem, and it was not ROM-related. It's actually my setup in my truck. Because I don't have an aux jack, I have to use an FM transmitter. My previous transmitter died a couple of weeks back, and I got a new (presumably better) one. I can adjust it between stereo and mono, and I had it on mono because of interference/static issues.
As I found out yesterday, having it on mono plugged into my phone, it will only transmit music and navigation to my stereo. Phone calls and notification sounds don't get transmitted. However, when I switch it to stereo, all sounds get transmitted to my stereo.
So problem solved - non ROM issue. Somewhat user error issue.
I wasn't doggin on ya . Although I can see how it could be read that way. It was late and I was responding to many threads. It was just a general statement to anyone reading, cause people have been getting fussy when I ask to clarify their install process so I can get the whole picture of exactly what they are doing. People seem so sure its a bug when in fact it was something they did wrong. Though that is not the case here and I can tell you get it a lot better than most people.
Related
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?
I cant ask this in the Development section under the rom to I am hoping to get some help here.
I recently flashed (this is my 4 or 5th Rom I've flashed so I'm still somewhat new to this) NexusMod 4 UCLA3 2.3.6 to my phone and it has been working great. Up until I started using my headphones (that came stock with the phone) to talk on the phone and answer calls. About 4 mins into a call the phone will say "SIM card ejected. Reboot Phone." if I reboot the phone with the headset plugged in I get the same error. Once I unplug the headset and reboot the phone can see the SIM card again and everything works fine. I am confused about the correlation between the headset and a SIM card.
Is there a setting or something I'm doing wrong to cause this? I know the simple solution is to just stop using the headset, but I love puzzles and cant figure out what would cause this.
That's a really weird problem, I've had no trouble with this rom on my rogers phone. Did you flash the radio first like it said?
Hardware behaviour is usually related to the kernel, so maybe try a different kernel that supports your phone and hope that might fix the problem?
Yep, I made sure to flash the modem first then NexusMod. I'll do some Kernal research (see what works best for others) and try a different one. Any recommendations??
I was coming from SkyICS, but I did the full wipe as instructed. so I'm not sure if this has a influence.
GooSe275 said:
Yep, I made sure to flash the modem first then NexusMod. I'll do some Kernal research (see what works best for others) and try a different one. Any recommendations??
I was coming from SkyICS, but I did the full wipe as instructed. so I'm not sure if this has a influence.
Click to expand...
Click to collapse
Not sure, I haven't used the stock headphones but I use iphone headphones with a mic for calls with nexusmod4 and it works fine. I use the kernel it came with after trying all the rest of the kernels and having my battery murdered with them I returned to romracer0.3. For me it delivers the best battery life
Sounds like very abnormal behaviour, if you did a full wipe then it's probably a hardware not software thing. Especially if it only happens '4 minutes into a call', maybe your headset itself is doing something funky.
Its not exactly 4 mins into the call, but it does not happen immediately, the times it "ejects the SIM Card" varies. I will try another headset before I start flashing other kernels.
People can either barely hear me, or not hear me at all. Yet, when I switch to speaker phone they hear me fine. I'm currently on the latest CM10 rom, but I've had this issue ever since I've started rooting from GB, CM9 etc etc therefore I doubt it's a rom issue. Any help is appreciated
If its been present since gb its probably the bottom mic because I think the top one does speaker phone.
I would suggest a bt or wired headset. Since you're on jb wired would be the way to go.
If you bought within a year ago flash back to stock and bring 'er to you're closest att warranty center
Or if you're good with soldering and such you could find a replacement mic
Hope this helps
Sent from my AOKP'd Infuse 4G
lahwf said:
People can either barely hear me, or not hear me at all. Yet, when I switch to speaker phone they hear me fine. I'm currently on the latest CM10 rom, but I've had this issue ever since I've started rooting from GB, CM9 etc etc therefore I doubt it's a rom issue. Any help is appreciated
Click to expand...
Click to collapse
everybody has this issue i think. Ive heard a lot of people complaining about this particular issue. I think it's a hardware thing, because it persistent from Froyo days. I'ts just how the infuse is built i guess.
Hello,
I have had some issues with Bluetooth on jellybean ROM and not connecting to my radio correctly to play music from my phone it never seems to connect and send the music to the radio just stays on the phone and was wondering if anyone else had had similar issues. Bluetooth works the way it should when i go back to ICS Roms, when i get in the and the radio is on the music will switch from the phone to radio with out problem might take 30 sec or so but will switch over
thanks
I know on AOSP there has been numerous bluetooth issues with different devices. I'm not sure if its because it's AOSP or JellyBean. More than likely its the same problem you're running into. What ROM are you running? Scan thru it's thread to see if there are any fixes, if not ask in the thread describing the device you're trying to connect.
thanks for the reply .... the latest one i was using was CM10 ....right now im using SynergyROM and all is working ok .... yeah i tried to post in the rom i was having trouble with but im blocked from posting since i don't have enough post undender my belt i guess lol
Yeah, I didn't notice at first, I was on my phone. You need 10 posts to reply to a thread in the dev forums. It's not very hard to come up with 10 quality posts tho. There's so much general discussion.
I do know for a fact that CM10 was having issues with car bluetooth's along with other devices besides earpieces... it's the ROM I've been running and following. I didn't pay too much attention to the bluetooth problems tho as my earpiece works fine and I don't have a car to hook my phone up too lol.
yeah i just started using it more so now ive notice , about the only time i have ever use bluetooth
Hi,
I've got a HTC sensation, which I have rooted and is now running Bruce's CM10. The problem with my phone is that some of the time the microphone doesn't function. This was already a problem under the offical firmware and one of the reasons I switched to CM. This may be a hardware problem, but i'm not sure. The (headset)microphone works if i plug in the headset and it does work some of the time without the headset. Once I experienced a spontaneous cutoff of the microphone during a call.
What I'm looking for is the driver/apk which controls the microphone to flash it. Does anyone have this, or know where to get it?
Greetings,
Martijn
jules.binkem said:
Hi,
I've got a HTC sensation, which I have rooted and is now running Bruce's CM10. The problem with my phone is that some of the time the microphone doesn't function. This was already a problem under the offical firmware and one of the reasons I switched to CM. This may be a hardware problem, but i'm not sure. The (headset)microphone works if i plug in the headset and it does work some of the time without the headset. Once I experienced a spontaneous cutoff of the microphone during a call.
What I'm looking for is the driver/apk which controls the microphone to flash it. Does anyone have this, or know where to get it?
Greetings,
Martijn
Click to expand...
Click to collapse
Everything you mentioned points out that your phone (mic) is broken, if you got same bug on Sense and AOSP, and if it works over Headphones mic just fine thats just another pointer..
Flash STOCK RUU and check once more if you got MIC problems and if yes send phone to HTC for repairs..
ivicask said:
Everything you mentioned points out that your phone (mic) is broken, if you got same bug on Sense and AOSP, and if it works over Headphones mic just fine thats just another pointer..
Flash STOCK RUU and check once more if you got MIC problems and if yes send phone to HTC for repairs..
Click to expand...
Click to collapse
I opened the case and started to see if I could remove the mic, before ordering a new one. This was enough to make it work again (so far). Possibly some part had moved around.