Hi everyone.
I am using a Bluetooth head phone LG hbs730 tone+ with my nexus 5.
I don't know why the sound is so loud even when I turned off the volume on my nexus.
I tried it with nexus 7. Everything was fine
But now when I use it with nexus 5. It just blow up my head. I set the lowest sound on both my nexus 5 and my Bluetooth headphone but it is still so loud. I tried to find some app on app store but it didn't help.
Does anyone have solution? Please help me!
Thank you.
Sorry for my bad English
Sent from my Nexus 5 using Tapatalk
This is not a Nexus 5 issue. It is Kit Kat issue on all devices that use the default Google Bluedroid Bluetooth stack, meaning Nexus devices and Google Play versions (other devices running a modified stack may not be affected).
Supposedly, it is an extension to Bluetooth AVRCP 1.3 that enables Bluetooth audio devices to directly control Android's system volume. It seems some genius thought two independent volume levels (headphone volume and handset bluetooth level) was too confusing for folks. Clearly they did not think about (or test) that some Bluetooth audio devices with their own volume controls might default to a very high or low level, and control of only the handset's bluetooth level would not provide sufficient range of adjustment.
So once again we have Goofle googing up bluetooth in Android. Please share your disappointment in the following threads so that we might see a fix ASAP. Guessing they are facing law suits for hearing damage if it is not addressed quickly.
http://productforums.google.com/forum/#!msg/nexus/X6Hwt2qMYDo/7qd-JGylQv0J
http://productforums.google.com/forum/#!msg/nexus/dsf7hQPesds/zWhIE27o2KwJ
http://productforums.google.com/forum/#!topic/nexus/uXzs0e3l7rI
http://productforums.google.com/forum/#!msg/nexus/b5h94ggUIac/qkBs9WUIh4oJ
Pandora causing full volume on Bluetooth
I was having the same issue with the volume on my Motorola SF 600 headset blasting and refusing to turn down. After a lot of searching, I discovered that Pandora was causing the issue. I got it to work normally by disabling the "Bluetooth for Automotive" in the Pandora settings. It then came back. I then reverted to Pandora 4.1 and got rid of the problem. You can Google and find versions of Pandora 4.1 in the wild.
Here is more information on the helpful post.
http://productforums.google.com/forum/#!topic/nexus/dsf7hQPesds
ssnacks said:
I was having the same issue with the volume on my Motorola SF 600 headset blasting and refusing to turn down. After a lot of searching, I discovered that Pandora was causing the issue. I got it to work normally by disabling the "Bluetooth for Automotive" in the Pandora settings. It then came back. I then reverted to Pandora 4.1 and got rid of the problem. You can Google and find versions of Pandora 4.1 in the wild.
Here is more information on the helpful post.
http://productforums.google.com/forum/#!topic/nexus/dsf7hQPesds
Click to expand...
Click to collapse
Thanks, but I am seeing this in Pocketcasts and Play Music on both Nexus 4 and 7, and Pandora has never been installed on either of them.
Related
Hey guys
Strange issue here. I paired my phone with my car through Bluetooth to make and receive calls using the car audio system. It works well.
However, if I fire Google Navigation, I can't here the spoken instructions through either the phone speaker or the car speakers.
I was not expecting navigation audio to be routed through Bluetooth audio, but I did expect the navigation instructions to come out of the phone speaker, as it does on the nexus one or the vibrant both running Android 2.2.
Is anybody else having this issue?
Thanks
Sent from my Nexus S using XDA App
bluetooth wont turn on
It just flashes the icon and does not turn on. From in settings same. Any ideas?
vapor311 said:
It just flashes the icon and does not turn on. From in settings same. Any ideas?
Click to expand...
Click to collapse
did you flash a new kernel or anything because the kernel in the dev thread is known to break bluetooth
if it does this stock out of the box try doing a system restore and then take it back if its still acting up because bluetooth should turn on
yea i used the pkg one that had SU etc on it. Suppose Ill have to flash back to stock arg.
just so peeps know with the bt issue flashing this fixed
http://forum.xda-developers.com/showthread.php?t=882333
Anyone?
Sent from my Nexus S using XDA App
Locking up slash rebooting while streaming bluetooth audio
Anyone else experiencing any sort of lockups rebooting streaming bluetooth audio. It seems like I can only get about 10 to 15 minutes streaming audio before the phone becomes completely unresponsive won't power on or anything
Sent from my Nexus S using XDA App
You should be thankful...I can't get more then 10 sec without it being cut off and play again...for...10 sec
what rom?
I had same issue once...i on CM7
Bluetooth doesn't stream audio to car - what's your experience
I've got a Ford Edge with the new Ford MyTouch/Sync system.
The Nexus S connects to the Bluetooth just fine; makes and receives calls perfectly. It will also connect to the Bluetooth Audio Stream for music playback, but won't play the audio over the car's speakers. Also, sometimes it connects, holds the connection for just a few seconds and then disconnects. My SGS and Nexus One work as expected, as does the iPhone, so it doesn't appear to be an issue with the car.
Seems like a bug in the NS to me.
I'm curious if others are streaming audio/music to their auto's BT system without issues?
It would be especially nice to know what anyone else with a new Ford/Lincoln is experiencing, but I'd also like to compile a list of what cars work and what don't.
I'm going to have to find some other BT device that I can test the stream on to see if my phone works with it or not. Maybe my Nexus One dock? I've never used that to stream audio even with the Nexus One.
In terms of troubleshooting my problem, I've already rebooted the phone and the car, un-paired and re-paired the phone with the car.
I've got a Mazda RX8 R3 and the NS will pair with the in-built car BT but drops the connection after a few minutes. It then refuses to connect again unless I re-pair, then a few minutes later it drops and we're back to square one.
The car's in-built BT worked fine with my HTC Desire, Hero, iPhone 3G and Blackberry 9700 so I'm guessing the Nexus S has a Bluetooth issue.
Mine works fine on my aftermarket Sony receiver.
having issues with bluetooth audio too, stream keeps breaking every now and then. Any fixes?
I've only streamed to the car stereo and had no issues. The phone is only about 10cms away.
Haven't tried my BT headphones yet, maybe range is the issue.
*On original ROM.
Mujja said:
I've only streamed to the car stereo and had no issues. The phone is only about 10cms away.
Haven't tried my BT headphones yet, maybe range is the issue.
*On original ROM.
Click to expand...
Click to collapse
tried placing the phone right next the the BT reciever and same problem. Only tried this once, maybe I'll try rebooting the phone.
no problem here
using Bionix 1.2
You're lucky, I can't even get BT music streaming to work with my car. No other BT devices to check with besides my Nexus One dock, which has no speakers.
BT works great for the phone, though, to make and receive calls.
Problem with Bluetooth
I cant get to work bluetooth on Nexus S.
When i enable it and try to send something from SGS to Nexus S it says me "This tranfer was canceled by the user" (Nexus S)
SGS says "Remote device rejected your request"
When i try send something from Nexus S, but use not function Send, i use function Bluetooth - it says me "The application Bluetooth Share (process com.android.bluetooth) has stopped unexpectedly. Please try again"
I tried factory reset, wipe cache, tried flash any other roms, but got NOTHING helpt me. I have this problem on 2 phones (2xNS).
Can someone give me files of BlueTooth share? (com.android.bluetooth)
That's an interesting problem you have. Mine did the same thing transfering from my computer to my NS. I just tried it again when I read your post (to make completely sure what the error was) and it has automagically fixed its self.
Well, seems i need a file \system\app\bluetooth.apk
I cant find any info on successfully accessing the audio hidden menu.
I have a problem that when I use a 3rd party music player and google navigation at the same time (i play the sound through the car stereo) then the volume of the navigation directions is reduced to almost zero when a headset/lead to car stereo is plugged into the headphone socket.
I've had a really goof look around and the fix mentioned in post 8 here looks to be the most educated and likely fix that I cant try as I cant find out how to access the hidden menu which leads to the audio tuning menu mentioned.
Any advice or direction would be greatly appreciated
Acne
Bump.
I'm having this problem too. The only way I know that I'm coming up to a turn is that the music goes quiet for a few seconds.
This problem seems well documented across most phone platforms but fixes are few and far between, with most either waiting for an android or navigation update to fix the problem.
From my testing it shows that the problem only occurs when the 3.5mm head phone jack is being used so it seems sensible to try and access the volume control to control how the phone outputs audio to the jack for different apps.
Trouble is I cant - does anyone know how to access these hidden menus or perhaps just edit a config file or suchlike with the phone?
Thanks
Acne
This problem also occurs over bluetooth audio. I've tested it on the BT Audio in my car and my Jaybird bluetooth headphones.
Google Code issue, bug tracker:
http://code.google.com/p/android/issues/detail?id=15690#makechanges
Get on it and let them know
old thread but i am having the same problem on a sensation using the standard audio player over bluetooth headtset when using copilot sat nav.
anyone found a solution?
smartecosse said:
old thread but i am having the same problem on a sensation using the standard audio player over bluetooth headtset when using copilot sat nav.
anyone found a solution?
Click to expand...
Click to collapse
hi guys, just wanted to share, i had been quite bothered with bugs like these... and have been searching the web for a long time... i found a solution apparently (cant remember the site name... but some official google guys replied or something) said that u need to check ur phone tts (text to speech) settings to make sure google tts is selected
apparently, if u are using things like v-lingo or samsung powerewd by v-lingo, it becomes soft... i tested this out... was very very surprised.. apparently it got way louder.
before this i tried a volume booster which did nothing but waste space on my phone. oddly ppl swear by those apps, all i could do was swear at it...
anyway.. enough rambling... hope this fixes ur issues
I've had this phone for a little less than a year now and it was working fine (except the terrible screen issues before JB). Now with 4.1.2 the screen is fine but other stuff are messed up... Headsets basically don't exist for my phone. I've tried various one button headsets and most of the time clicks are not recognized.I haven't tried 3 buttons ones but I can guess the outcome... I mainly want to control my music when walking(Pause/Play etc.) . Every now and then the headset works fine for a few seconds then Google Now/Search or whatever takes control and then that is for headset controls... I tried :
Disabling Google = Google doesn't start whne listening to musc but no recognition for the button...
Various app solutions for controlling headsets = still no recognition..
Rooted and installed Headset Droid for the Google fix = nope
Different music players that come with headset control functionality = same problem.
Tried SmartConnect + SmartKey = it recognizes that is a headset on the event and starts Walkman but then again clicks do nothing..
This has all been tested with the official headset that comes with the phone...
My friends has the same phone bought from a different country. I've stress tested his phone with the same various headsets and it performs great with absolutely no issues,Google doesn't even launch like on mine..... I saw that although he is on the same JB as me (4.1.2) he is running an older Build. I was on 11.2.A.0.31 and he is on 11.2.A.0.21.
I thought I will reflash to an older Stock rom just to see if the software is the issue. I downloaded DooMLoRD Easy Rooting Toolkit (v17) and rooted my phone without any issues. Then I downloaded 11.2.A.0.21 No Brand ATA from this forum. I got Flashtool which recognized my phone and I granted it root access. I reflashed with the stock rom with full wipe on cache + data. Phone booted up fine afterwards and it worked quite good. Then I decided to try the headset again. I think you can guess what happened....Same Google issue and no headset functionality whatsoever...
I really like the phone as the sound quality is superior to my Philips mp3 player. I can also have up to 32GB sd which is perfect as I do have a lot of music BUT this headset issue makes listening to music more of a hassle then actual enjoyment... I normally like Sony but I have to admit they have disappointed me when it comes to phones... Not just because of this issue but also the screen problems on ICS which I had to fix with a app made by people on this forum...
I don't know what to do now. I forgot to mention I have not unlocked my bootloader and my phone says : Bootloader unlock allowed : No
in the system service menu. Should I unlock the bootloader with Flashtool and try to go down to ICS which will probably fix the headset and the Google issue but will probably introduce the nasty screen issue..? I don't even know if this is a software issue at all, I would like it to be but i am starting to think that I just have a faulty handset -__- I am probably never buying a phone second hand + phone from Sony again...
I also noticed ST26i_112A021_CE.ftf on 4shared. Is CE better than the no brand one I used ?
Any help on this would be greatly appreciated. I am a programmer myself and although this i tiny issue it is annoying me greatly..
I updated back to .31 OTA out of curiosity and headsets work alright until 5,6 times playing and pausing
music and then it does the usual no response thing until I completely reset the phone.
I was reading on Bluetooth headsets and from my understanding commands from them are on a separate audio stream from the headphone jack. Any idea if same issue will appear if I buy a Bluetooth headset ? I don't want to buy an expensive one and then regret it..
Sent from my ST26i using xda app-developers app
werk91 said:
I updated back to .31 OTA out of curiosity and headsets work alright until 5,6 times playing and pausing
music and then it does the usual no response thing until I completely reset the phone.
I was reading on Bluetooth headsets and from my understanding commands from them are on a separate audio stream from the headphone jack. Any idea if same issue will appear if I buy a Bluetooth headset ? I don't want to buy an expensive one and then regret it..
Sent from my ST26i using xda app-developers app
Click to expand...
Click to collapse
Here's what I do: Look for phillips headset app on the playstore. Install it and configure it to make the changes for a media player that you like and you'll never have problems again.
The next time you pop the headset on the phillips headset app will automatically start and it will also open up the default media player.+ you also get an extra sound boos from the app
So far I have tried :
Philips Headset app
Google Search Disabled: Probably works best, stops accepting commands once I turn the screen off or I play/pause too many times.
Google Search Enabled: The voice dialer/Google Now/Whatever will start up about 10 secs in the song and then forget about any headset control until full phone restart.
JAYS Headset app
Works alright for 5,6 times playing and pausing and then just stops registering clicks. Google Search/Voice dialer affects it in the same way
as Philips Headset.
Headset Button Controller, Ultimate Headset Controller and Headset Droid ( I tried the Google fix) act in the same manner as well....
I've tried just about anything now. I even completely removed Google Search and Voice Dialer from system apps. Even that didn't help..
I guess its just my phone and my only hope now is a bluetooth headset. Hopefully the commands from a BT headset are intercepted and processed differently...
My Nexus 5 has problems with audio skipping and stuttering in the car over bluetooth. It also sometimes fails to connect until I toggle bluetooth on and off. Googling the problem indicates that it's a common problem on Nexus 4 and 7 with no real solutions.
This happens in an '11 Subaru and a '13 Hyundai, so I'm thinking it's the phone. Our other phones stream perfectly. I have tried unpairing and re-pairing many times. Any suggestions? Should I RMA the phone?
I am also experiencing Bluetooth issues, it will randomly disconnect or just not connect until I turn it off and back on again. I had no issues with my Nexus 4. 2012 Kia Forte Koup.
I'm seeing this also between my Nexus 5 and my PC, both the poor audio and problems connecting
it seems that attenuation is a factor, at least for the poor audio, when holding the phone around the middle/upper portion of the back causes it to happen while it never happens when I set the phone down.
also did not see either issue with my nexus 4
I'm not certain if it's purely hardware or software but I'd contact Google about it regardless
did anyone come up with a solution to this?
I have the same problem in my 2013 Honda Accord EX-L. I don't remember having the issue on stock though. I feel like it just started happening after installing one of the Cyanogenmod variants.
It only seems to skip if i use my phone while music is playing.. its really annoying because the song will just skip for a few seconds pretty much every time i use my phone.
Mojo8 said:
I'm seeing this also between my Nexus 5 and my PC, both the poor audio and problems connecting
it seems that attenuation is a factor, at least for the poor audio, when holding the phone around the middle/upper portion of the back causes it to happen while it never happens when I set the phone down.
also did not see either issue with my nexus 4
I'm not certain if it's purely hardware or software but I'd contact Google about it regardless
Click to expand...
Click to collapse
Wow, mines been skipping like twice every song but when I hold the phone like you described it will completely stop and disconnect.... weird.
No issues at all with bluetooth from my Nexus 5. Works great in my Explorer.
One problem with Ford Focus. When I use Google voice search while using Bluetooth audio, I get media processes error and cannot play file. Track starts back from beginning upon resuming play.
Sent from my Nexus 5 using xda app-developers app
I have a rooted Galaxy S3's and updated the software from 4.1.2 to clean rom 4.3 this last Saturday.
I have a 2014 Chevrolet Camaro with MyLink. I've only had it a couple of weeks.
I swear that when I played music via XM, USB, or FM while I was using Google maps navigation, and my phone was connected via Bluetooth, that it would say the directions through the speakers over a lower volume of music, then raise the music volume once finished. This week this does not occur. No directions at all over the speakers yet everything else works like normal, like the audio on the car, and the navigation on just the phone speakers.
Does anyone have any experience with this sort of thing? Was there some information I missed in relation to MyLink and Android versions?
Thanks!
ReFLeX135 said:
I have a rooted Galaxy S3's and updated the software from 4.1.2 to clean rom 4.3 this last Saturday.
I have a 2014 Chevrolet Camaro with MyLink. I've only had it a couple of weeks.
I swear that when I played music via XM, USB, or FM while I was using Google maps navigation, and my phone was connected via Bluetooth, that it would say the directions through the speakers over a lower volume of music, then raise the music volume once finished. This week this does not occur. No directions at all over the speakers yet everything else works like normal, like the audio on the car, and the navigation on just the phone speakers.
Does anyone have any experience with this sort of thing? Was there some information I missed in relation to MyLink and Android versions?
Thanks!
Click to expand...
Click to collapse
I know this is old, but I'm in the same boat as you. I have seen some Iphone users find a goofy work around, but I do not know the Android method. I have my phone connected via bluetooth, bringup google maps and navigate. No audio through the truck speakers (2014 silverado with 8" mylink). Everybody wants some of your money, so GM would rather make their own apps work for you... Like Bringgo . I would even use Bringgo, but they only released it for a few vehicles. Guess you use Onstar or pay $800 for the nav module.
GPS Audio
I know this is old, but if anyone was still having this problem here is your answer. When you have your phone paired to your car you have to turn to blue tooth on your radio to here your phones GPS/you tube vid or anything coming from your phone besides phone call ( because it goes in phone mode automatically).
If anyone knows how to hack your mylink to play text msg or to mirror your phone please let me know.
thanks
is there any way to add maps and navigation to my linby on stark the factory setting only has turn by turn
If you can't hear the directions it's because you've turned down the volume for navigation. It's easy to do accidentally. To fix it, start up a new navigation route and when the music lowers to give the nav a chance to speak, turn up the volume nob. You just need to correct the balance. Happened to me and I stumbled across the fix.
I used to have the same problem. The issue is actually with how your phone talks to the car. There is usually a delay when a phone is transmitting audio by bluetooth. Some phones simply transmit the information slower than others. I had the same issue with my LG Optimus F3 and chevy cruze; i would rarely get any audio directions, and when i did, they were cut off. That all went away when i switched to an LG Vortex. Now i don't have any problem at all.