I don't know about the rest of you, but I have serious issues with every car dock launcher I've tried with my Infuse.
Basically, I have less than a 50% success rate launching any app from a car dock interface and I'm about to scrap all the dock apps and just use the stock Android launcher when the phone is in the dock.
Symptoms include (none of these happens every time, but most of the time)
1. Bluetooth connect failure
2. Bluetooth connects OK, but fails to deliver any sound from music apps
3. Bluetooth connects, but phone insists on using speaker instead of BT
4. Bluetooth connects, but phonebook transfer never completes.
5. Music app (Doubletwist or any other music player) hang and force close
6. GPS fails to find a satellite
7. Pandora cannot connect to server
None of these occur when I stick with ADW as the launcher in car mode.
Anyone else having these problems?
Related
Let me start off by saying this is more of a workaround than a fix. I have been hoping that the release of Donut may have fixed the A2DP skipping problem but until late I had rendered my Plantronics Voyager 855 useless for listening to music. I could not listen to anything with out i skipping so bad that it would have been better to turn off bluetooth and hold the phone to my head to listen to media. I have found a fix that may hopefully lead to someone figuring out what is actually wrong.
Step 1: turn off bluetooth and unpair your headset
Step 2: start a song on a media player
Step 3: go back turn bluetooth on and pair your headset
you may or may not have to unpair your headset sometimes it works if you just turn bluetooth off start a song and then go turn it back on again
Once it connects your media will start playing perfectly through the headset for as long as the media is playing. Unfortunately once you stop playing media for more than a few minutes and then try to start it again the skipping will also start again.
Have you also tried using a task manager to kill everything BEFORE you start the music player? That works 60% of the time for me.
Another solution that generally works the other 40% of the time is to go into your bluetooth settings, press and hold on your BT device, at menu pop-up, touch "Options" then just unlink the Media, and then re-link it.
Hope this saves you some time in the future!
q426669 said:
Have you also tried using a task manager to kill everything BEFORE you start the music player? That works 60% of the time for me.
Another solution that generally works the other 40% of the time is to go into your bluetooth settings, press and hold on your BT device, at menu pop-up, touch "Options" then just unlink the Media, and then re-link it.
Hope this saves you some time in the future!
Click to expand...
Click to collapse
its funny that unlinking media works for you because i tried that and it does nothing for me. The fastest way i can get it to work is turning bluetooth of and back on again.
I'm having the same problems with my JVC car stereo.. It skips pops etc.. with no way to fix.. i'll try this work around tomorrow but does anyone know what causes this?
I see one of you is running latest Cyanogenmod. I'm not sure what the issue is you are having with A2DP maybe your paired hardware? i typically have Pandora streaming to my car stereo in the background with Telenav running.
EDIT: I use Tunewiki instead of Music player if that makes a difference.
Well actually it does happen in CyanogenMod although its not a skipping issue... Its more of a faint popping issue that I get.
I dont hear it using the aux headphone jack on my htc adapter but i do when i switch over to bluetooth.
Right now i'm running Enomther's ASOP+ADP rom because CyanogenMod has been having freezing and rebooting issues (thanks to the switchrom script for letting me switch back and forth) and this is where i'm really getting a skipping and popping issue big time.
For both I use Tunewiki as well, for m4a's that i buy on iTunes or SHOUTcast radio (gotta love internet radio on the go...)
I thought it was because I was running Google Maps as well as tunewiki (I have a car GPS mount) but even just letting it run only Tunewiki it still has issues (although far worse at times running Google Maps)
I just can't seem to pinpoint the issue.. I could just use the aux headphone jack to my car stereo yes, but then since I have the charger connected I get the annoying ground loop noise which is far worse than the bluetooth popping and skipping issue...
EDIT: This is my Car Stereo: JVC KD-A805
Check out for workarounds in http://code.google.com/p/android/issues/detail?id=2807
os2baba said:
Check out for workarounds in http://code.google.com/p/android/issues/detail?id=2807
Click to expand...
Click to collapse
Those workarounds don't work for me. It is good to know this issue is known though and is being reported by more than one.
My Tunewiki still skips either way.. even turing off most background apps do not help.. I was looking into editing the audiopara4.csv file possibly (someone apparently added a line for his BMW and it fixed his issue) but don't know where to start.
q426669 said:
Have you also tried using a task manager to kill everything BEFORE you start the music player? That works 60% of the time for me.
Another solution that generally works the other 40% of the time is to go into your bluetooth settings, press and hold on your BT device, at menu pop-up, touch "Options" then just unlink the Media, and then re-link it.
Hope this saves you some time in the future!
Click to expand...
Click to collapse
After intense observation, I realized I experience the skipping only after I place a call. The following two steps always work for me ( I prefer #2)
1. Turn of bluetooth and turn in it back on while the music is playing
2. In bluetooth settings unlink the phone and thats it; you might have to turn off bt and back on and it works until you use the bt for phone again
I also noticed that the skipping is not ROM specific with me; I tried it when my G1 was unrooted, thru XROM. I'm not sure what causes the skipping, I experience no skipping with my S9 (works flawlessly), however my Jabra BT3030 is what gives me all the grief (better headset IMHO)
Just found a really easy way to get a2dp to work perfectly. Once you have what ever you want playing just make a call to your voice mail, once the call gets transfered to your headset hang up and what ever you are playing will play perfect through the headset.
eclair rom.
bluetooth works perfectly on them.
Is anyone else struggling with the car dock and the speakerphone fuction not being on?
I keep setting it to remeber my settings and to have both music and phone going through the dock but when I get back in the car it only has music checked so when I answer a call it doesn't use the bluetooth to the dock
Any ideas on how to get this to work everytime? Could it be something I loaded into the phone? I have been deleting all my programs to see if that helps but nothing yet.
I am unrooted normal os...
A little sporadic for me too. Although for the most part it works. What do you mean when you say "when I get back in the car"? Do you mean you:
1) Get in your car, start car and drive off, all the time with the N1 never leaving the dock.
2) Get in your car, start car, place phone it car dock...
3) Get in your car, place phone it car dock, start car....
I know it sounds pedantic but I suspect the method you use can effect how things end up. Especially considering how the power to the Car Dock usually is interrupted during ENG start. Furthermore I am not sure if the phone can or does sense that it has been placed in the car dock if the actual docking happens before you turn the IGN on. This is only speculative though.
So what I tend to do is method 2. I start my car first, to ensure power is going to the cradle during docking AND wont be interrupted. Then place the phone into the cradle. This seems to work all the time for me resulting in phone audio connecting.
Also for testing, you will have probably noticed the little BT notification it the top margin grows ears >BT< when it the phone is connected to something via BT. Unfortunately it does not differentiate between phone or media audio though. So you will have the same indication there for phone or media or both connections being active. To test your cradle placement technique is working reliably, disable the media audio pairing to the car dock for a couple of days. Then every time you dock the phone in the cradle the BT with ears appearing will confirm you successfully have phone audio connected.
there's an app car dock speakerphone that automatically turns the phone to speakerphone when in the car dock
shane8002 said:
there's an app car dock speakerphone that automatically turns the phone to speakerphone when in the car dock
Click to expand...
Click to collapse
That app would be no good for this problem. The Nexus One is not meant to be in Speakerphone mode when in the genuine google car dock. It is meant to be in BT phone audio mode. It is the car dock itself that needs to do the speakerphone bit with its inbuilt mic and speakers.
I have my dock connected to uninterupted power so it works even when the engine is off, starting, running.
I'll play with at what point I put it in for fun but I don't think that will matter.
I just hate it when I don't do it and someone calls and I have to call them back or scamble to rip the phone off the dock. Hopefully 2.2 will give us a sideways menu/phone/contacts list as well ;-)
Every time I connect A2DP in my car it launches the music app. Can't find anywhere to disable this annoying behavior.
It might be under the app Smart Connect.
no, those are things you set up. I have no actions set for such behavior.
I don't think it's the phone that take this decision. I think it's rather the bluetooth device that send the "play music" command that open the music app on the phone.
its not Sony, i dont have such issue with my BT devices, including one that is a BT speaker. If you claim its not smart connect, you might want to check other apps similar to smart connect or the BT device/'s app. If possible, also clear the BT device's app data or at least reinstall it.
if you cannot identify the root of the problem i would advise you to do a fresh start for the phone. do a comparison with the BT device's app and without the app.
Hi all. So I'm having an issue with my S6 running cleanrom lite. My bluetooth audio skips when playing on any BT speaker. The skip is similar to a cd skipping and is not the volume just lowering for another app. BT audio used to work flawlessly, here is what I have done so far. And This issue exists with multiple BT speakers, with multiple music apps, local music with default music app, spotify, spotify in offline mode, Amazon music.
1. Reboot phone
2. Toggle bluetooth
3. Unpair car BT device from phone
4. Delete phone pair from car BT headunit
5. Rollback any app updates
6. Unselected "Use Nuplayer" in development options. Then rebooted
7. Took a logcat. Everytime BT audio skips I get an event like this
"08-26 17:34:18.501 E/bt-btif (6930): btif_get_num_aa_frame() - Limiting frames to be sent from 43 to 10"
Anyone have any ideas as to anything else I can try? Or what could be causing this?
odlay75 said:
Hi all. So I'm having an issue with my S6 running cleanrom lite. My bluetooth audio skips when playing on any BT speaker. The skip is similar to a cd skipping and is not the volume just lowering for another app. BT audio used to work flawlessly, here is what I have done so far. And This issue exists with multiple BT speakers, with multiple music apps, local music with default music app, spotify, spotify in offline mode, Amazon music.
1. Reboot phone
2. Toggle bluetooth
3. Unpair car BT device from phone
4. Delete phone pair from car BT headunit
5. Rollback any app updates
6. Unselected "Use Nuplayer" in development options. Then rebooted
7. Took a logcat. Everytime BT audio skips I get an event like this
"08-26 17:34:18.501 E/bt-btif (6930): btif_get_num_aa_frame() - Limiting frames to be sent from 43 to 10"
Anyone have any ideas as to anything else I can try? Or what could be causing this?
Click to expand...
Click to collapse
That is exactly what plagues me since upgrading my i9100G to Lollipop with Omnirom 5 - Has anyone tracked it down already and knows a fix? Interestingly first time after boot bluetooth streaming works fine for me. Rebooting all the time is of course not good....
I upgraded to s22 ultra from s21. When I get into my car my Bluetooth pairs with my phone for CALLS automatically, however not for AUDIO (both connect on its own once in a while) . I have to manually go into Bluetooth settings and switch on manually. This is annoying since I have a job where I'm in and out of my car. This was never an issue with my previous phone (S21)
Things I have tried but no luck.
In Bluetooth app settings clear data.
In Bluetooth app setting unpair and delete every device in memory.
In Bluetooth agent setting - change battery saving mode to unrestricted from optimized
Hmmm that seems strange.. Maybe try making sure auto is checked in the bluetooth seetings. I have the same phone and I'm not experiencing audio issues.
maybe try running a routine for the bluetooth
There is definitely something wrong with BT in the latest firmware. I occasionally get volume drops and those are huge drops. This bug happened in one or two previous firmware too, got sorted out, but in the latest there is it again. I hope it will be fixed ASAP.
Is it a Ford ?
You have to manually select the phone in Source to play audio or anything else.
Calls take priority over any setting, so they work always without an issue.
JazonX said:
Is it a Ford ?
You have to manually select the phone in Source to play audio or anything else.
Calls take priority over any setting, so they work always without an issue.
Click to expand...
Click to collapse
It's an aftermarket Bluetooth added to an old Honda via peripheral plugged into the stock cd player unit. I am going to try and disconnecting the battery terminals for 30 mins so I can reset the Bluetooth unit itself.
When I have my car bluetooth device connected as "audio" only, then I have to manually connect to it from my phone.
When I have my car bluetooth device connected as "audio & calls" , then the s22 ultra connects automatically
I recall reading that audio+calls connects automatically
Audio only requires manual connection
I drive a 2017 Ford F150 but I think its not a Ford issue