I am wondering if any of you fellow Verizonites would be willing to help me test this out, as I have already asked my friend with the AT&T version if his does this, and it does not:
When connected to the aux in (very common on cars and stereos nowadays, you know, so you can listen to music off your phones and iPods and MP3 players, etc.) I now have the SAME incredibly aggravating problem I could never resolve with my Fascinate. As usual, I have my bluetooth connected to take the call. When I answer the call, I hear NOTHING over my bluetooth unless I disconnect the audio cable out of the headphone jack!!! This is a huge safety hazard, as it takes your hands and eyes off the road, requiring you to disconnect a cable every time you get a call!!
I called Verizon and complained about this with my Fascinate to no avail. I never had this issue with my Droid X, HTC Eris, or my Galaxy Nexus, another dual core Snapdragon based Verizon LTE phone made by Samsung.
Not to mention the SGS III is laggier and less responsive than my Nexus, although not as bad once you disable S Voice (S is for stupid, by the way, at least in my opinion ... I can't get it to work worth a darn!! Could be that I'm the stupid one, but I've certainly given it a lot of effort in a very quiet environment.)
This is horrible because the screen is incredible, and the battery life far outpaces every other smartphone I've ever had by a ridiculous margin, so PLEASE, fellow Verizon SGSIII friends, help me out if you can!! I don't want to have to return this phone, but reasons to do so are stacking up.
If there's no fix for the audio cable thing, that is a definite deal breaker, and enough to make the phone "defective" in my opinion. That is such a blatant safety hazard. I do NOT want a "Fascinate 2". The other issues pale in comparison to the audio cable issue.
Here is a video of the AT&T version NOT having this glaring safety and functionality issue:
http://www.youtube.com/watch?v=A37p4fF-h-k
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
I tested it with Bose Bluetooth earpiece and that works, somewhat. If you have the Aux plugged in and get a call, the phone picks up your voice from the Bluetooth and plays the other guys voice through the Aux. Unplugging the Aux mid-call will route the other guys voice back to the Bluetooth. In both cases both me and my friend could hear each other.
There is a problem though. When the Aux is plugged in, with Bluetooth our not, the call quality will drop significantly. It will sound as if you're in a horrible signal area and will cut out every other second or so making it impossible to carry on a conversation. Funny thing is as soon as I unplug the Aux the call is back to normal and we can hear each other just perfect. It's as if with Aux the noise cancellation kicks in and starts cancelling out everything, including your and the other guys voice, lol. Not sure if that's just my phone or SGS3 in general. I actually intentionally used this "glitch" to avoid taking to annoying person. Just tell them "I'm in a bad area and can't talk" and plug in the aux mid-call and they will stop bugging you as soon as they hear the voice glitch up
My bluetooth headset works fine with the audio out through the "dock" connector.
macdroid01 said:
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
Click to expand...
Click to collapse
Same here
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
same here too
I upgraded from a fascinate to a s3 and have the same problem on both phones. It is really annoying and I'd love to find a fix for it.
adsbar said:
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
Click to expand...
Click to collapse
I think I am having the same problem with the Bluetooth in my 2010 G37. It seems like if u connect via Bluetooth for media audio, I can't get calls and vice versa. Plus when I connect to media audio and try and switch back to just phone, it doesn't auto connect when I get in the car.
My Rezound didn't seem to have any of these issues.
Sent from my SCH-I535 using xda app-developers app
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
sinman02 said:
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
SirKronan said:
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
Click to expand...
Click to collapse
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
CIPuyleart said:
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
Click to expand...
Click to collapse
Does the S3 fit into the dock ok? Any stability problems? And you get proper 3.5 inch output for your car's input, plus your bluetooth call works? I have the same kind of deck in my Freestyle. Installed it myself. It does bluetooth for calls but not A2DP. Thanks for your responses so far! I am willing to buy a dock if it works like that. I would just appreciate any reassurance you could give me that it will work out ok ...
but that's a really nice idea that i didn't consider. I would really like to get this thing working and willing to apply any dev fix. what's interesting is that skype calls work fine, yet regular phone calls do not i'll give this doc a try.
Ok, I have the dock now, and wanted to update everyone on this. Audio quality is good, better than bluetooth, but an ever so slight downgrade from just plugging straight into the headphone with an audio cable, but it's certainly good enough.
The one thing that is annoying enough to prevent me from using it is that there is an audible click between each song. I haven't a clue how to get rid of this!! ARGHH!!! I haven't tested the dock with video or pandora output to see if the clicks persist, but as of right now, it's a bit annoying on a long trip. Otherwise, this would work really nicely, and is a pretty cheap fix for $18, not to mention getting a fully functional windshield/dash mount to use your phone as a GPS with.
Hoping my new ROM I installed might solve the audio issue. It has a custom kernel, and possibly improved car dock compatibility. We shall see...
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
misterpat1975 said:
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
Click to expand...
Click to collapse
SoundAbout Pro is an app that will override Samsung's stupidity when it comes to BT/AuxJack audio routing. Well worth the price of admission.
Related
I always use my bluetooth headset when talking to family and friends(due to the length of time, hate holding phone). Since, I switched from my nexus one people have griped about the interference/noise they hear when I'm on my bluetooth headset. It is not my BT headset as I've tried a few(motorola S305, and two smaller bluetooth earpieces), all of which exhibit the noise. I was wondering if anyone else has had this problem ?
Running the Galaxy S I9000 ROM rooted.
Everyone complains about hearing me whenever I try to use a headset. Seems like the stack sucks or the radio is terrible.
Got the same problem. My bluetooth calls are loud and clear on my side, but everyone on the other side complains about static noice and I sound very distant.
I tried the original ATT rom (stock unrooted) and the most current 2.1 that is available for download. No difference.
Any ideas what to try to remedy this?
I haven't noticed anything like this on my Motorola S9-HD headset.
I have noticed sometimes it will cut the music every once in a while, whereas my iPhone never did.
konawayne said:
I always use my bluetooth headset when talking to family and friends(due to the length of time, hate holding phone). Since, I switched from my nexus one people have griped about the interference/noise they hear when I'm on my bluetooth headset. It is not my BT headset as I've tried a few(motorola S305, and two smaller bluetooth earpieces), all of which exhibit the noise. I was wondering if anyone else has had this problem ?
Running the Galaxy S I9000 ROM rooted.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
This is a known issue with the I9000 ROM... Bluetooth doesn't work well for some...
I'm running the stock rom... is that the I9000 rom?
None of my friends have mentioned such a problem when i've called them, although I've only made bluetooth calls a couple of times (including on the bus and at home).
Using after-market Nokia BH-503s.
I'm definately seeing the same problem on the stock rom. Not as bad as athe I9000 ROM but still bad enough for them to complain. Seems like it's made worse by the different roms/kernels we've been flashing but there's definately a problem.
wpb2 said:
I haven't noticed anything like this on my Motorola S9-HD headset.
I have noticed sometimes it will cut the music every once in a while, whereas my iPhone never did.
Click to expand...
Click to collapse
I'm seeing similar symptoms, except my music cuts out every 30 seconds or so. My setup is a Kensington iPhone adapter connected through aux input in my car with an Anycom FIPO on the iPhone adapter (it converts the iPhone/iPod adapter into a bluetooth receiver). I then stream from my Captivate to the adapter and it works fine except that it cuts out every 30 seconds. Did you ever figure out how to fix it?
UPDATE: Just wanted to add that I figured out what was causing my problem: having Wifi turned on. Once I turned it off, my bluetooth streaming worked beautifully, with no hiccups.
Still have a problem with this. Stopped using my BT headset completely... sucks having this thing stuck to my head for calls.
I have encountered several problems:
Party can not hear me at all; though I can hear fine.
Party hears tinny sound to my voice.
Headset disconnects while playing music.
Using a Motorokr S9-HD. Works fine with Samsung A-737.
I too have the static problem. This phone sounds wonderful on my end, but everyone complains that that can't hear me! This is so far the only complaint I have.... I hope someone will have a fix, or come up with something.
I have this problem too !
Hey guys,
I've just got droid charge last week and I like everything about it (only after rooting and installing Gummycharged), but there is one huge problem for me. Well, it might be 2, but one of them is slightly better with Gummycharged and voodoo lagfix.
Here's the issue - I love listening to music in my car through bluetooth and until recently I've been using my Ipod touch 4g and it has been working flawlessly and music quality was great. Now, once I got the Droid Charge, I've noticed 2 things - every minute or 2 the songs would skip (interrupt), and the sound quality was pretty terrible (mainly with the high end - sounded like tweeters were being overloaded).
Rooting the phone helped with skipping - it now happens once in 10 minutes or so, so that's acceptable, however the sound quality is still pretty horrible. I've looked around on these forums and people had similar issues with quality with their stock phones and most people suggest CyanogenMod. I'm not all that familiar with what different ROMs are available for Charge, but as far as I can tell this one isn't. Does anyone know if there is way to fix/configure the quality of bluetooth transmission on this phone? Is there any mod I can install? Anyone having similar issues?
Any help is much appreciated!
FuriousOne said:
Hey guys,
I've just got droid charge last week and I like everything about it (only after rooting and installing Gummycharged), but there is one huge problem for me. Well, it might be 2, but one of them is slightly better with Gummycharged and voodoo lagfix.
Here's the issue - I love listening to music in my car through bluetooth and until recently I've been using my Ipod touch 4g and it has been working flawlessly and music quality was great. Now, once I got the Droid Charge, I've noticed 2 things - every minute or 2 the songs would skip (interrupt), and the sound quality was pretty terrible (mainly with the high end - sounded like tweeters were being overloaded).
Rooting the phone helped with skipping - it now happens once in 10 minutes or so, so that's acceptable, however the sound quality is still pretty horrible. I've looked around on these forums and people had similar issues with quality with their stock phones and most people suggest CyanogenMod. I'm not all that familiar with what different ROMs are available for Charge, but as far as I can tell this one isn't. Does anyone know if there is way to fix/configure the quality of bluetooth transmission on this phone? Is there any mod I can install? Anyone having similar issues?
Any help is much appreciated!
Click to expand...
Click to collapse
Have you looked at this thread? It's more about disconnections, but the fix they list might help you, too.
http://forum.xda-developers.com/showthread.php?t=1099603
chadness said:
Have you looked at this thread? It's more about disconnections, but the fix they list might help you, too.
http://forum.xda-developers.com/showthread.php?t=1099603
Click to expand...
Click to collapse
Thanks, but the problem is more fundamental, I suppose. Looks like HTC and Samsung use some custom bluetooth code in their ROMs. Apparently it limits the bitpool value at 32, which makes the audio quality terrible over bluetooth. Surprisingly, everyone knows what the problem is but so far the only reported solution is the cyanogenmod.
Here's more about it:
http://forum.xda-developers.com/showthread.php?t=708685
http://code.google.com/p/android/issues/detail?id=9888
Wow, nasty and long standing! Glad I didn't buy one of those headsets like I was going to. *sigh*
Hey guys,
I'm running GummyCharged 1.85 w/ the voodoo kernel (pbj) and also getting skips over bluetooth to my car stereo. It's seriously distracting and annoying. My Droid 2 worked flawlessly in this respect, but it seems like any time the Charge does any "thinking" it makes the BT audio skip.
Any hope of a fix for this?
My Charge is stock and I haven't had a chance to try the bluetooth audio streaming yet, but when I plug my phone into my car to listen to music through the aux jack it does the same thing, about once every song it skips. Seems odd. I'll try bluetooth today on my way to school and see what happens. You'd think with Bluetooth 3.0 on board the signal would be strong enough to stream decent quality music...
I can confirm this issue is there and in your face a lot. I tried it on the way to school (about a 40 minute ride), it skipped once or twice every few minutes, no big deal. The quality was acceptable for wireless transfer, nothing to write home about. Not a lot of low end, and just a hint of static and slightly over-boosted highs. However I tried it again on the way home once I realized I had forgotten my aux cable, and it skipped so often I just switched to FM. It was so annoying. I can confirm your suspicions that it seems to happen when the phone is trying to do something. Switching towers, background apps, turning on data and checking traffic with Google Maps really freaked it out, but it was fine once I was done. Kinda sucks for those who wish to use the feature regularly.
Update?
I have a droid charge, and the bluetooth streaming quality really sucks, like the OP pointed out, highs are really bad.
Tried with my friends iphone and it worked flawlessly.
CyanogenMod is still unavailable for the droid charge as far as I can tell.
Is there any other fix that anyone has found that will fix the bluetooth sound quality when streaming music?
Any help or places to look is appreciated.
I hate bluetooth with a passion. I am a earbud/headset guy.
I noticed when I first got my Skyrocket that there was always a background hiss, like the sound you get out of speakers when it is not shielded good enough.
Any other owners try this? Use the stock headset or iphone earbuds then simply launch an App enough to get it to play a simple sound... do you here a slight hiss for a few seconds after the sound plays?
Also try calling someone using the headset and listen for background noise. I just got a replacement Skyrocket in and it is making the same noise. If I use the speakerphone or Bluetooth it is fine.
My last phone the I had was an Infuse. It is still in my possession and I retested. The hiss is there but it is so quiet I almost could not hear it.
Please let me know if you notice this, it is driving me crazy!
I posted about this shortly after release. Mine does it VERY noticeably, only in the car, only while charging. All 5 skyrockets have done it.
I have found No fix
Redbeard80 said:
I hate bluetooth with a passion. I am a earbud/headset guy.
I noticed when I first got my Skyrocket that there was always a background hiss, like the sound you get out of speakers when it is not shielded good enough.
Any other owners try this? Use the stock headset or iphone earbuds then simply launch an App enough to get it to play a simple sound... do you here a slight hiss for a few seconds after the sound plays?
Also try calling someone using the headset and listen for background noise. I just got a replacement Skyrocket in and it is making the same noise. If I use the speakerphone or Bluetooth it is fine.
My last phone the I had was an Infuse. It is still in my possession and I retested. The hiss is there but it is so quiet I almost could not hear it.
Please let me know if you notice this, it is driving me crazy!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
00mred00 said:
I posted about this shortly after release. Mine does it VERY noticeably, only in the car, only while charging. All 5 skyrockets have done it.
I have found No fix
Click to expand...
Click to collapse
I can hear it regardless of what the phone is doing. Charging doesn't seem to make a difference as far as I can tell.
Thanks for the feedback in any case. I really... really like the phone other than that.
Its much worse when charging. Search YouTube for "skyrocket feedback'
Oddly enough I can't get it to do it under other scenarios
Redbeard80 said:
I can hear it regardless of what the phone is doing. Charging doesn't seem to make a difference as far as I can tell.
Thanks for the feedback in any case. I really... really like the phone other than that.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
Redbeard80 said:
I hate bluetooth with a passion. I am a earbud/headset guy.
I noticed when I first got my Skyrocket that there was always a background hiss, like the sound you get out of speakers when it is not shielded good enough.
Any other owners try this? Use the stock headset or iphone earbuds then simply launch an App enough to get it to play a simple sound... do you here a slight hiss for a few seconds after the sound plays?
Also try calling someone using the headset and listen for background noise. I just got a replacement Skyrocket in and it is making the same noise. If I use the speakerphone or Bluetooth it is fine.
My last phone the I had was an Infuse. It is still in my possession and I retested. The hiss is there but it is so quiet I almost could not hear it.
Please let me know if you notice this, it is driving me crazy!
Click to expand...
Click to collapse
If you are within your 30 days buyers remorse or have insurance, get it switched out. I believe its a defective issue. I had that happen on my white SGS2SR and I returned it for a new one in box and it no longer has that issue.
s0cal said:
If you are within your 30 days buyers remorse or have insurance, get it switched out. I believe its a defective issue. I had that happen on my white SGS2SR and I returned it for a new one in box and it no longer has that issue.
Click to expand...
Click to collapse
I called ATT up and complained. They sent me another skyrocket that is brand new in the box. It also makes the same noise.
I am more curious to hear if anyone else can hear the noise as I have described it.
Skyrocket Hiss
I'm right there with you. Never noticed it until today because thinking back, I haven't used the headphones yet. I was trying to listen to Pandora and noticed a hiss and crackle. It's gotta be interference because i notice it picks up a little when the screen is on. But It happens whenever there's sound that has or is playing. I notice it during quiet parts of videos or songs and when you unlock the phone it hisses for a second (with the unlock sound) and then shuts down until you go to play anything with audio. I can't handle it. Is this on all skyrockets for certain? Software fix? I'm not paying as much as I did for this to be a problem. I know it sounds picky but it really does bother me during use.
I am not sure myself. I can tell you that I had 3 brand new skyrockets lined up and they all made the exact same noises. I ended up selling the one I did not returnes and got a open box Galaxy Nexus from Expansys. I has it's own issues (like the screen) but the audio jack has no problems.
if you have root try installing voodoo control it helps with audio playback
Redbeard80 said:
I am not sure myself. I can tell you that I had 3 brand new skyrockets lined up and they all made the exact same noises. I ended up selling the one I did not returnes and got a open box Galaxy Nexus from Expansys. I has it's own issues (like the screen) but the audio jack has no problems.
Click to expand...
Click to collapse
Man that's a bummer. I'm not sure I can give up LTE now that I've had a taste. I'm going in this weekend to the store and will test every phone they have to see if it's maybe a specific batch problem. I have a couple more weeks of my 30 day comfort zone. This phone is just perfect for me apart from that one flaw. Unfortunately I do try to use it for music so I'm having trouble getting over the fact. How do you like the nexus? I was holding out for that when my captivate fell apart.
The noise while charging is normally not a phone issue and will likely happen with a lot of devices. It's the grounding issue with the CAR chargers and the Headphone Aux in.
I been in Car audio for many many years and have competed in IASCA SQ comps. One of the biggest offenses is 'alternator whine'. Isolating any alternator whine from the sound system was always the factor of proper grounding and wiring. If you run your amp power cable, RCA signal cables and speaker cables to where they crossed the powers cable, you're bound to get the noise.
It all depends on the car, the wiring, the grounding etc etc.
My Galaxy s I has an EXCELLENT audio codec/dac and on it's own is a great player. But in my car as soon as I plug in power and use aux, it's unbearable.
Even though the Skyrocket suffers from poor audio on it's own, the whine while plugged into a car's 12v socket is not Skyrockets fault.
Pull your car into your drive way and use a 120v regular charger and then plug the aux into the car, turn on the car.... you won't hear the whine/noise.
All very good info....but out of our 6 android devices and two iPhones....the skyrockets are the only two that do it.
n19htmare said:
The noise while charging is normally not a phone issue and will likely happen with a lot of devices. It's the grounding issue with the CAR chargers and the Headphone Aux in.
I been in Car audio for many many years and have competed in IASCA SQ comps. One of the biggest offenses is 'alternator whine'. Isolating any alternator whine from the sound system was always the factor of proper grounding and wiring. If you run your amp power cable, RCA signal cables and speaker cables to where they crossed the powers cable, you're bound to get the noise.
It all depends on the car, the wiring, the grounding etc etc.
My Galaxy s I has an EXCELLENT audio codec/dac and on it's own is a great player. But in my car as soon as I plug in power and use aux, it's unbearable.
Even though the Skyrocket suffers from poor audio on it's own, the whine while plugged into a car's 12v socket is not Skyrockets fault.
Pull your car into your drive way and use a 120v regular charger and then plug the aux into the car, turn on the car.... you won't hear the whine/noise.
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
Wow, bad screen and bad audio...
n19htmare said:
The noise while charging is normally not a phone issue and will likely happen with a lot of devices. It's the grounding issue with the CAR chargers and the Headphone Aux in.
<snip>
Pull your car into your drive way and use a 120v regular charger and then plug the aux into the car, turn on the car.... you won't hear the whine/noise.
Click to expand...
Click to collapse
The issues I have had are not while charging, only when using headphones.
TrCeaAstTer said:
Man that's a bummer. I'm not sure I can give up LTE now that I've had a taste. I'm going in this weekend to the store and will test every phone they have to see if it's maybe a specific batch problem. I have a couple more weeks of my 30 day comfort zone. This phone is just perfect for me apart from that one flaw. Unfortunately I do try to use it for music so I'm having trouble getting over the fact. How do you like the nexus? I was holding out for that when my captivate fell apart.
Click to expand...
Click to collapse
I realllly like the Nexus. ICS is great for the most part and it is nice to be able to flash roms that are straight from google.
Also the phone feels a bit more solid and a little heavier (GSM version) than the Skyrocket in a good way. I do have the grey screen issues at low light levels that other people complain about but at >40% brightness it is pretty much a non issue.
Mine does it too, but it doesn't particularly bother me. I think it might even be a software issue, as the hiss cuts out a few seconds after a sound plays.
Frogacuda said:
Mine does it too, but it doesn't particularly bother me. I think it might even be a software issue, as the hiss cuts out a few seconds after a sound plays.
Click to expand...
Click to collapse
Isn't that the strangest part!? I think I could get over the fuzz when music is playing, just gotta turn the volume up a bit. But the killer for me was when I tried using the headset during a phone call and it was a lot more noticeable then I dunno I'm just still so in love with everything else about the phone that I've been reluctant to take it back.
I have this hope where maybe we all got the same batch and they're all a bit defective. I'm waiting until as close to my 30 day mark as possible to ask for another one and then we'll see. If it's still a problem then I think I'll just make due and hope it is a software problem.
Okay so new solution! Wait for the Samsung Galaxy S II Skyrocket HD and see if IT has an audio hiss lol. I mean seriously how many models are they gonna push out before it's over. I'd be so mad if i got the original GSII.
Hello,
Pardon if this has been answered already, I simply did not find my exact question answered.
I am using my unmodified Nexus 5 (not even rooted), with the latest KitKat (v.4.4.2 build KOT49H) with quite a few wired and wireless headsets and people always complain they cannot hear me. Eventually I got my hands on an old Samsung Galaxy S2 and tried my best bluetooth headset with it: Imagine my surprise, I could hear myself quite clearly even when I was talking really really softly, barely above a whisper. My headset is excellent. My phone is not.
My questions revolve around what to do about it.
Nothing in KitKat allows me to adjust the bluetooth microphone gain, nor does it let me use an equalizer on my microphone. I can adjust the volume of the headset, but this does not do anything to the microphone gain.
So...
Question 1: am I the only person with this problem?
Question 2: what do you people do about it?
Question 3: are there any mods / custom ROMs out there that attempt to fix this problem? Google does not appear to be interested in doing so.
Thanks in advance!
*bump*
Any ideas? I have tried re-pairing my bluetooth headset - no go. I have tried flashing custom ROMs and kernels - no go again. It seems to be a problem with the phone, but I have no idea how to fix it. And Google searches always return other people having this problem. Noone with solutions, though.
Using a wired headset results in even worse results, if that were at all possible.
Has anyone tried to replace the bluetooth stack or driver with something that works?
Thanks!
*bump*
Yesterday I spent quite a few hours tinkering with my phone. I tried every last radio out there for the Nexus 5 and none had any effect on bluetooth microphone levels. Then I tried a few AOSP ROMs: CM11 and Omni. They turned out to be so closely related I might as well have just tried one. None had any effect on bluetooth microphone. Heck if CM11 doesn't do it, there really are no alternatives out there! I tried the FauxAudio tweak, even paid $2 to Faux, which successfully managed to do nothing: app didn't was written badly. Finally, I tried a bunch of volume boost tweaks. That worked, actually. That is, it boosted the wrong volume. Finally, in a moment of true and utter desperation, I opened an ADB shell and edited that mixer file by hand. I then discovered that microphone gain on bluetooth is not controlled there.
I tried all my wired headsets again: Etymotic HF3's microphone produces such an atrocious sound, if I am to rely on it I need to seriously consider becoming a mime. Then there were my Bose QC15 headphones with a remote cable for Android by some off-brand company: that was terrible, the cable is useless. Heck, not even mime lessons can help me there.
Eventually I chanced upon an old microphone cable for my QC15 headphones. Just microphone, no remote. Surprisingly, this one is loud and clear! That after being anything but loud or clear on my old cell phone. Interesting. Unfortunately, it's been out of production for a few years. My working theory is that Bose realized putting a decent microphone on expensive headphones gives people real value, makes them spend money, and that way lies madness. We can't have that, can we. So when that cable starts cutting, so does my use of this cell phone.
I am screwed.
In any case, I will stop bumping my own thread, you guys obviously don't know a solution or there would have been a lively conversation right now. And I am pretty sure there is a moderator or two frowning right now, possibly getting ready to throw an encyclopedia at me. My only hope is that Google is going to do something about that pesky Broadcom driver that doesn't work sometime before the mass exodus to the iPhone. And before my precious microphone cable stops working, or I will be leading the way for that exodus. It's a phone, damnit, if it doesn't work like one it's no good.
Hmmm.... it should be possible to wire a good lavalier mike on a cell phone cable... maybe I can get an op-amp from an old tape recorder to get decent amplification... When attaching a 9V battery on my headphone cable begins to look appealing, we really have a problem.
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
same issue
Dany XP said:
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
Click to expand...
Click to collapse
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
pitchdown said:
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
Click to expand...
Click to collapse
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
kangelov said:
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
Click to expand...
Click to collapse
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
pitchdown said:
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
Click to expand...
Click to collapse
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
kangelov said:
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
Click to expand...
Click to collapse
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
pitchdown said:
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
Click to expand...
Click to collapse
My guess is either the bluetooth baseband or the bluetooth kernel driver used in the N5 is flaky. This is why I think so:
Problem does not exist on my old Samsung Galaxy S2, including when it runs the same nightly of CM11, nor does it exist on my computer or my desk phone. All the headsets I've owned performed admirably there, so the headsets are not directly the cause. From what I've seen no ROM and no kernel out there seem to be making a difference as far as Bluetooth gain is concerned, the problem is persistently there and the same. Best I could tell it's just the N5 with a problem and it's just for the phone profile. I've tried the Bose headset (the worst performer headset with the N5 of the lot) on a colleague's N5 and his phone was just as bad with it as mine. I am not sure if it's a small batch of N5s having a problem, I don't own lots and lots of N5 phones to try on, but I doubt it: with anything digital things are usually all-or-nothing and the N5 has an off-the-shelf Bluetooth chip, which is not unique to the N5. My guess is it's the entire model, but having only tried on 2 N5 phones, this is no more than a guess.
From what I saw online, the entire Nexus line has poor Bluetooth performance, not just the 5, and Google changed the Bluetooth stack with KitKat besides possibly introducing more problems. If you have a non-Nexus phone, the manufacturer most certainly replaced the Bluetooth driver and radio with one of their own, so problem goes away, but the Nexus line does not enjoy such attention.
An interesting thing to try would be for someone to put the LG G2 Bluetooth driver on a N5 kernel and try it out. I don't have the time or the expertise to do that, but there are plenty of people who do. Assuming the G2 does not have problems with bluetooth gain, if the problem still persists it will tell us if it's the N5 baseband or hardware doing it, and noone can help us there if that's the case.
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Shiver2005 said:
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Click to expand...
Click to collapse
That's a different problem. The wired headset problem is easily solvable with FauxAudio and a supported kernel.
This maybe realted to the changes Google made to the core Bluetooth stack as of Android 4.3+ I know they made adjustments for the BLE [low poer Bluetooth devices like pedometers and other senor type crap]. It is BEYOND me as to why Google keeps adding functionality ot the core Bluetooth stack when it is GLARINGLY OBVIOUS they have real problems with Bluetooth as a whole. WHY NOT fix the core issues so Bluetooth is much better at the basics before trying to add functionality or more complex?
I know they complained it would cost a bit for a different newer Bluetooth license but I mean in my personal experience with many different phones Bluetooth is SUPER flaky even at it's best in Android, and does not even work the same way across devices [I have used 3 different Jabra speakerphones on my bosses Galaxy 3 recently and they all worked to varying degrees even though they all use the same version of Bluetooth protocol], but my T989 [Galaxy 2 T-mobile], my parents G2s My bosses older Bionic, My fathers new Droid X, etc. all have random problems. You can usually find one device that works well with a certain phone/ROM, but that can change between ROM versions and devices so it is like you need to go and buy 1 of everything every time there is an update and go crazy finding the ONE that works [and as noted on page 1 with the gentleman using the same Platronics Voyager Platinum as I have it is a super expensive very nice device that worked BEAUTIFULLY in ICS, but now in 4.1 + you can not get more than 1 or 2 words across the mic unless you are YELLING at it like a crazy person on the SAME device].
So all that to say I think it is prolly related to changes Android made in 4.3+ flipped the Bluetooth operability on it's head.
Mic Volume OK with KitKat 4.4.4 and cheap "HB-800" headset
there've been no posts for a while so maybe the problem has gone away with the KitKat updates.
But anyway:-
I have a Nexus 5 and recently bought a cheap generic stereo earbud headset with mic from eBay .... $14.82 Ozzie including delivery to Western Australia.
I've actually asked the other party whether they can hear me (specifically "am I loud enough?") because I read this thread and have been assured that it's all good.
In fact it's a pity the sound quality at MY end isn't better, but that's probably the low quality ear buds rather than electronics / firmware reasons.
Of course, ymmv.
Here's the ebay item title in case anyone wants to look it up or I can pm the item number if it helps.
"Headphones Earphones with MIC 1st Stereo Bluetooth Hands-Free Wireless HV/HB-800"
No, the problem is still there. Reason there are no posts is that no one has a solution. Nothing has changed since March. I am somewhat controlling it with CM11 running on the ElementalX kernel. Without this kernel Bluetooth performance is unbearable. With it it is barely adequate.
It's funny that a cheap headset would work okay while multiple top-of-the-line everything-but-the-kitchen-sink models like the Plantronics Voyager Pro would still be having problems.
I was seriously considering getting the OnePlus One, the Nexus 6 and even the iPhone 6 hoping the issue would finally be fixed. It's ridiculous that a phone commonly accepted as the measuring stick of the Android world would be having problems with simple tasks like driving a bluetooth headset. *very disappointed*
Me too. Two days with my new N5 and when I use my Sony SBH20 people hear me bad... With my N4 no problem. Its annoying! Ive to speak with headset because Ive problems with my left arm and legs, I only have the right to hold the phone, I cant do anyhing more and when I walk I need that arm to hold my cane.
I dont see a real solution, I will have to return the N5
Having some very annoying BT issues. Phone pairs fine with pretty much anything. But when streaming audio it cuts in and out pretty frequently but never lost its connection. Called ATT and they sent me a new one. Phone does they same thing. This one actually looses its connection periodically, some days are worse than others. Main issue is in my 2013 Subaru Outback. Does it sometimes with my Phillips BT speaker but not as consistently.
I'm not rooted and have tried both ART and dalvik and the issue is present no matter what.
Since this has happened with two phones I figured I can't be the only one. Anybody else have this problem?
I drive a semi all day, I connect my phone via BT to the stereo and listen to audiobooks/slacker radio for 12 hours a day and have never had this issue. In the BT menu there is an option to 'Turn on Audio Channel Mode' have you tried that? I don't have it on but perhaps it will help? Also I know this phone supports some new BT standards for low power, perhaps this is causing an issue with you devices, I don't know if you can turn that off, or if it's something that is just not very backwards compatible?
i have a similar connect/disconnect issue but only if its not in use it seems. like when its just connected but not streaming i'll notice my car will say it disconnected and reconnected. sometimes when i'm on the phone it gets all staticky and robot sounding...but only with my cars bluetooth. never had an issue with my og pro on 4.4 so i dont think its 4.4. havent done a factory reset yet, hopefully thats all it is cuz there are some other little quirks too
I don't experience audio cut outs, but I do experience severe cracking no matter what tweaks/adjustments I make.
Another problem is that it doesn't read my texts to me while connected to my car. Works fine with my Nokia Lumia 1520 and HTC One x. Its pretty annoying.
You guys should post details on the bluetooth devices you're connecting to. I had a white G3 and now have a black one and both did nothing you guys are talking about when connected to Pyle, Klipsch, Logitech or Chrysler Uconnect bluetooth audio devices. I use Spotify, Car Home Ultra, Google Maps Navigation, make calls via the phone and the Uconnect system will pick up the activity and play the audio correctly, initiate and receive calls in UConnect, Send/Receive Texts via UConnect, control audio volume and tracks. None of that causes disconnects or static for me.
I do have serious problems when playing music with the stock music app over bluetooth. If I try to rewind or ff the G3 starts freaking out and will begin playing the music slower despite not having touched the advanced audio controls. It really sucks. Luckily it doesn't do that with Poweramp or Subsonic clients. Doesn't happen with headphones directly connected either.
If this is not a problem with the G3 when paired to certain devices I think your bluetooth radios are defective. There would be way more complaints if this was prevalent.
---------- Post added at 03:58 AM ---------- Previous post was at 03:51 AM ----------
absinthex said:
I don't experience audio cut outs, but I do experience severe cracking no matter what tweaks/adjustments I make.
Another problem is that it doesn't read my texts to me while connected to my car. Works fine with my Nokia Lumia 1520 and HTC One x. Its pretty annoying.
Click to expand...
Click to collapse
Text reading will depend on your device and your car's bluetooth stack compatibility. My GS5 could do everything but call out in my car. It worked good for a month then an update broke it. iPhone 5S could do everything but read and send texts. My G3 does everything great. If you research your car radio model and the G3 I'd bet you'd see that nobody has it working with the AT&T G3. You may see people with variants have it working especially international. Sometimes there are weird tricks to get things working. I had to disconnect and reconnect my GS5 a few times in order for it to work.
GorillaPimp said:
You guys should post details on the bluetooth devices you're connecting to. I had a white G3 and now have a black one and both did nothing you guys are talking about when connected to Pyle, Klipsch, Logitech or Chrysler Uconnect bluetooth audio devices. I use Spotify, Car Home Ultra, Google Maps Navigation, make calls via the phone and the Uconnect system will pick up the activity and play the audio correctly, initiate and receive calls in UConnect, Send/Receive Texts via UConnect, control audio volume and tracks. None of that causes disconnects or static for me.
I do have serious problems when playing music with the stock music app over bluetooth. If I try to rewind or ff the G3 starts freaking out and will begin playing the music slower despite not having touched the advanced audio controls. It really sucks. Luckily it doesn't do that with Poweramp or Subsonic clients. Doesn't happen with headphones directly connected either.
If this is not a problem with the G3 when paired to certain devices I think your bluetooth radios are defective. There would be way more complaints if this was prevalent.
---------- Post added at 03:58 AM ---------- Previous post was at 03:51 AM ----------
Text reading will depend on your device and your car's bluetooth stack compatibility. My GS5 could do everything but call out in my car. It worked good for a month then an update broke it. iPhone 5S could do everything but read and send texts. My G3 does everything great. If you research your car radio model and the G3 I'd bet you'd see that nobody has it working with the AT&T G3. You may see people with variants have it working especially international. Sometimes there are weird tricks to get things working. I had to disconnect and reconnect my GS5 a few times in order for it to work.
Click to expand...
Click to collapse
I found this, but my 2014 FJ Cruiser isn't on the list, neither is my G3.
https://www.google.com/url?sa=t&so...woHcO6CgPFvWsEew&sig2=QZyBxl51eRFrONj056uGBg
Still looking.
absinthex said:
I found this, but my 2014 FJ Cruiser isn't on the list, neither is my G3.
https://www.google.com/url?sa=t&so...woHcO6CgPFvWsEew&sig2=QZyBxl51eRFrONj056uGBg
Still looking.
Click to expand...
Click to collapse
I'm guessing you don't have the JBL radio. http://www.toyota.com/fjcruiser/features.html#!/interior I love FJCs especially for offroading. They're beasts.
I can't find the model info for your radio. You can check Toyota parts for it. Should be the only one besides the JBL. The notes on that interior page reference needing to have a compatible bluetooth stack. I went through similar crap with my 2013 Durango. Nothing past the Galaxy S 2 from Samsung on CDMA (Verizon or Sprint) works with UConnect stereos for placing calls which can suck really bad if you're moving around during the day. No texts read aloud on my radio will say the number or name because of some issue with the was texts in the US are sent as opposed to international ones.
The G2 works well with the Entune Toyota radios so it looks like you just got screwed with that FJC radio. Those Fj radios have always been kinda outdated and more durable looking if not in function. It's kinda like Wrangler radio systems. They don't want a little mud or water to break em or something.
You could try a work around. You could just toggle Settings >Sound> Message/call voice notifications. It's at the bottom of the Sound page. When it's on its supposed to read the texts for you. If the stereo can pause music during a song to allow navigation commands to be heard it may announce the texts for you. Some radios and phones have problems with that too.
If that works maybe use a shortcut to the Sound settings in an app like Car Home Ultra or use something like Tasker to switch it on when bluetooth connects to your car. That second option would be pretty seamless.

GorillaPimp said:
I'm guessing you don't have the JBL radio. http://www.toyota.com/fjcruiser/features.html#!/interior I love FJCs especially for offroading. They're beasts.
I can't find the model info for your radio. You can check Toyota parts for it. Should be the only one besides the JBL. The notes on that interior page reference needing to have a compatible bluetooth stack. I went through similar crap with my 2013 Durango. Nothing past the Galaxy S 2 from Samsung on CDMA (Verizon or Sprint) works with UConnect stereos for placing calls which can suck really bad if you're moving around during the day. No texts read aloud on my radio will say the number or name because of some issue with the was texts in the US are sent as opposed to international ones.
The G2 works well with the Entune Toyota radios so it looks like you just got screwed with that FJC radio. Those Fj radios have always been kinda outdated and more durable looking if not in function. It's kinda like Wrangler radio systems. They don't want a little mud or water to break em or something.
You could try a work around. You could just toggle Settings >Sound> Message/call voice notifications. It's at the bottom of the Sound page. When it's on its supposed to read the texts for you. If the stereo can pause music during a song to allow navigation commands to be heard it may announce the texts for you. Some radios and phones have problems with that too.
If that works maybe use a shortcut to the Sound settings in an app like Car Home Ultra or use something like Tasker to switch it on when bluetooth connects to your car. That second option would be pretty seamless.

Click to expand...
Click to collapse
Yes, they are! That's the main reason for purchasing one; and that it's the last year that they are being sold in the US, so I thought I'd pull the trigger on one.
But, no, I don't have the JBL head unit. I have the stock FJammer unit, but at least it's an upgraded model of those that were being sold in prior years.
I tried that work around when I first got my phone. Didn't work. I've gone through all Google, Google Now and all LG settings that have anything to do with Bluetooth and TTS. The nagivation works, but when it wants to. Sometimes, it will pause music, whether the music is playing through a CD or Bluetooth, and sometimes it won't pause the music, and it's barely audible. Even though I can hear it, it doesn't mean it's working how it should. When I should be hearing, "In a quarter mile, make a left turn at blah blah..." I really end up hearing, "ake left turn at bla..."
I think I'm just gonna live with it. Hopefully there will be a Bluetooth fix for this when LG releases an update.
Thanks for the replies.
absinthex said:
Yes, they are! That's the main reason for purchasing one; and that it's the last year that they are being sold in the US, so I thought I'd pull the trigger on one.
But, no, I don't have the JBL head unit. I have the stock FJammer unit, but at least it's an upgraded model of those that were being sold in prior years.
I tried that work around when I first got my phone. Didn't work. I've gone through all Google, Google Now and all LG settings that have anything to do with Bluetooth and TTS. The nagivation works, but when it wants to. Sometimes, it will pause music, whether the music is playing through a CD or Bluetooth, and sometimes it won't pause the music, and it's barely audible. Even though I can hear it, it doesn't mean it's working how it should. When I should be hearing, "In a quarter mile, make a left turn at blah blah..." I really end up hearing, "ake left turn at bla..."
I think I'm just gonna live with it. Hopefully there will be a Bluetooth fix for this when LG releases an update.
Thanks for the replies.
Click to expand...
Click to collapse
Yeah I read about it being the last year. If I had it to burn I'd buy one and import a 2014 rereleased 70 Land Cruiser.
Damn that sucks. My Nexus 4 wouldn't make those pauses in music or other audio apps for navigation at all. It really sucked after having it with HTC and Samsung phones for a few years.
There's always those Jabra Freeway & Tour units. Not the best builtin option but a lot cheaper than an upgrade of radio. In my experience counting on a manufacturer fix for stuff like that hasn't worked out for me. That's why I am cancelling my Sprint account this week. I got stuck with a phone that wouldn't work and they wouldn't cut me any slack at all. It's probably because I just moved over from T-Mo.
I hope it works when ATT finally updates us. Rock climbing in that FJ should take your mind off things.
GorillaPimp said:
Yeah I read about it being the last year. If I had it to burn I'd buy one and import a 2014 rereleased 70 Land Cruiser.
Damn that sucks. My Nexus 4 wouldn't make those pauses in music or other audio apps for navigation at all. It really sucked after having it with HTC and Samsung phones for a few years.
There's always those Jabra Freeway & Tour units. Not the best builtin option but a lot cheaper than an upgrade of radio. In my experience counting on a manufacturer fix for stuff like that hasn't worked out for me. That's why I am cancelling my Sprint account this week. I got stuck with a phone that wouldn't work and they wouldn't cut me any slack at all. It's probably because I just moved over from T-Mo.
I hope it works when ATT finally updates us. Rock climbing in that FJ should take your mind off things.
Click to expand...
Click to collapse
It's a damn blast!! Sucks it's my daily driver; I want to mod it out more and more. Thanks for the help. If I ever get this resolved I'll let you know.