I am having some very frustrating BT issues.
I only use one bluetooth device, a Kenwood KDC-BT945U car stereo. When using any vanilla android rom, the phone and deck struggle to work. They hardly ever pair and once it does, they never reconnect later and I must go through the process of trying to re-pair again.
Here is what I find odd. Any SenseUI rom that I have tried, the phone and the deck connect without issue.
My question is, would it be possible to take the bluetooth from Modaco's R23 and use it on CM6? Any advice?
Verboten
UPDATE.
I got brave and took the bluetooth.apk from Modaco's R23 ROM and pushed it to my phone running CM6 RC2 and my issues are 95% better. It works great but the phone wants to pair every time I get into the car. I wish it would auto connect but at least it is working.
That sucks. I have similar issues with stock Froyo. Just coming in to see if rooting and a custom rom would fix the issue.
Everytime I get into my car I have to turn off my bt on my phone and turn it back on for the radio and the phone to pair.
Not sure if its an Android issue(my Milestone did the same exact thing) or my radio(Clarion)
Even more annoying, is half the time as soon as the phone pairs with the radio it starts playing music. Not my preference that is for sure.
Related
For some reason when my phone connects to a headset that supports both audio and phone the audio will not auto connect. I have to open the bluetooth options and hold down on the device i want to connect to then check the audio box.
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
It worked before fresh 1.1 so maybe it was just a change in something.
I'm using the stock software and I have the problem so it is not freshrom
man we need an update HTC!!!!!!!
q1 almost over so we're that much closer to getting our official 2.1 update.
I've also got a bluetooth problem - would really appreciate any help you can offer.
I have a Tomtom and headphoned in my Bike Crash Helmet. I want to connect so I can hear music and phone calls through the phone in my helmet and also hear the TomTom.
The Tomtom connects to the Helmet, the phone connects to the Tomtom and I can get calls through the speakers via the Tomtom but music won't play (apart from an annoying second or two after dropping a call).
If I can get the phone to advertise headset features I could connect the Tomtom to the phone and the phone to the speakers (think that would work), otherwise I believe the Tomtom is not advertising media audio, only phone audio and don't expect I can change that.
Any thoughts...?
PS - Have tried the market headset app - unfortunately it doesn't fix the problem...
Time_Lord said:
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
Click to expand...
Click to collapse
well now the source for the CDMA hero is out so shouldnt be long till a lot of the little bugs arre resolved.
It's like the elephant in the room around here. The bluetooth service on 2.1 is some crazy, broken crap. No matter how many times and how many ways I try to get it to pair to my brand new Kenwood x994 it refuses to save. It will eventually link up BT audio if I search for devices and let the pairing fail, but what a PIA to mess with every time I get in the car. I rolled back to Fresh 1.1 today and I had it paired and working perfectly in 10 seconds.
So here is the question, can we put the 1.5 BT stack into the 2.1 ROM? I already tried the 1.5 libbluetooth.so in the /system/lib filesystem, but it didn't change anything about the pairing problem (obviously I have no idea what I am doing and stabbing blindly at anything bluetooth related).
Anybody have any ideas? Is the BT compiled into the kernel? Can we recompile it with the 1.5 version?
I've asked this question a few times already and the answers are usually 'no'. Gawd I wish we could as no 2.1 roms (I've tried almost all of them) will pair voice (audio is OK) with my Pioneer Avic D3 car radio. 1.5 works perfect
Mine works exactly the opposite. The hands free phone works perfectly, but the phonebook doesn't download and BT audio fails to connect.
It sounds like it may be your phone, your should update with the official 2.1, then take it to a sprint store and have them replace it.
My phone has worked flawlessly to my jeep stereo with any 2.1 rom I have used in the last several months.
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
djorijun said:
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
Click to expand...
Click to collapse
I agree, if it was the hardware it wouldnt work with 1.5 either. Besides, Dan Hesse is my boss. He'd get hacked if I took back my phone
Thread moved.
I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
czechmate said:
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
Click to expand...
Click to collapse
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Monu123 said:
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Click to expand...
Click to collapse
That is weird... When I switch back to Eclair, it works OK, back to Froyo, no HF after one phonecall...
I dont know how to work with ROMs, I managed to find out how to flash firmwares, I even handled many problems with Odin and its moods, incomplete flashes, etc... But I dont know how to use these custom ROMs...
Anyway, i would appreciate if someone told me how to resolve it without custom ROMs, as I plan to use offical Froyo when it becomes available, but with this issue, it is useless for me, as I travel a lot...
No one else?
I'm having a related problem.
I'm getting music stream cut outs (1 sec max) when streaming bluetooth to caraudio WHILE wifi on.
If i disable wifi, bluetoothaudio works fine. I know they share range bt/wifi, but this is unacceptable. They should negotiate. Everytime wifi scans, i get cutouts. Unusable. Only workaround is disabling wifi (and thats annoying because i have to be constantly activating/disabling it everytime i enter somewhere with wifi etc.
Using Docrom xxjpo v8 with voodoo.
Anyone has some software fix that makes wifi behave better when bluetooth musictream on?
Hi,
I bought a Bluetooth Car Stereo. I've paired it and it pairs fine. When I connect it, it works great and IF I leave BT permanently on, it automatically connects when I sit in the car. If I disable bluetooth to conserve battery, upon re-enabling it, it DOES NOT automatically connect. Instead, I have to go Settings, Wireless, Bluetooth and press Connect manually.
Is there no way of making my phone automatically scan or check or whatever? I'm pretty sure my old Nokia could connect automatically, in fact I'll test now!
Thanks,
Joe
Anyone? Perhaps an app you can recommend?
Bluetooth Autoconnect (by WestOneTech) ... but it's not free ...
Okay. I flashed MIUI MintBerry Edition, and guess what? It allows automatic reconnecting on bluetooth enable. So I know for a fact this isn't some android limitation and it's definitely a setting or config of some sort in SGS firmware.
There has to be a way in which this can be fixed on a stock rooted ROM.
Any help would be smashing!
That happens to me with my samsung gt-s5560 witch is a rather crappy phone. I need to manually tell the phone to connect with my car, even if it's paired and set to auto permit.
On my SGS with ICS EliteRom 1.2, however, it works perfectly. Connects automatically whenever i have bluetooth on (either if it was on before being in range or if i connect while i'm in range).
Bluetooth works as handsfree for calls - from the car interface the phone allows to take and place calls, browse through recent and lost calls, phonebook (it even downloads it) and it even streams music to my car's speakers (using Google Music) with no additional configs.
It connects rather fast, like 3 or 4 seconds after turning BT on.
Exactly Kayn and that is why I can't understand why the stock room doesn't do this and more to the point why nobody has raised this issue before. I like the stock ROM. I genuinely do. I find it intuitive. So why can't it automatically connect to my car stereo when Bluetooth is switched on. This custom ROM has no problem doing it. I simply switch on Bluetooth and boom it connects. I need that functionality on the stock ROM if possible
Im going to flash the newest value pack tomorrow and see if that helps but I doubt it will. I genuinely believe this is an issue with the stock ROM. The only thing that might have caused it if the stock ROM does support it, is if I've removed something using TiBa but I very much doubt it. I didn't touch any core system components.
Haven't flashed the latest value pack but I've worked out how to make it work. Ridiculous on Samsungs part and I think they need to get their heads out of their arses and sort it.
If I activate Bluetooth before I turn on my car stereo, then it picks it up perfectly.
So if I turn on my car stereo and then switch on bluetooth... doesn't work.
If I turn on bluetooth then switch on my car stereo... works fine.
Absolute joke on Samsungs part that this glitch is the only way I can get it to work. I'll keep investigating and I'll eventually write a guide to help people with it.
skezza said:
Haven't flashed the latest value pack but I've worked out how to make it work. Ridiculous on Samsungs part and I think they need to get their heads out of their arses and sort it.
If I activate Bluetooth before I turn on my car stereo, then it picks it up perfectly.
So if I turn on my car stereo and then switch on bluetooth... doesn't work.
If I turn on bluetooth then switch on my car stereo... works fine.
Absolute joke on Samsungs part that this glitch is the only way I can get it to work. I'll keep investigating and I'll eventually write a guide to help people with it.
Click to expand...
Click to collapse
Makes us both but i can't really cope with the battery drainage when the phone's plugged during several hours (i use loads of battery intensive like torrent-downloading apps, radio streaming, etc and the phone needs to be plugged) so i had to make the change for some custom non-samsung based rom.
Samsung has loads of this minor quirks that make the experience that much less enjoyable. I only found solution in custom roms (very thankful to the devs for that!). Don't think they ever really cared about solving some under-the-hood issues (they did add some new features though) and even went as far as to pull the "flawed by design" apple-move.
I would still tell you to give a shot at customs, some out there are really good, but i can understand not wanting to change something we really like.
Good luck with that mate!
It's not that I don't like custom ROMs, I love custom ROMs but unfortunately, none of them have the Samsung Browser and let's be honest, everyone knows the best Android browser is the stock Samsung one. The browser that came with MIUI was very choppy and laggy.
I get decent battery life out of my stock ROM, but if I had to leave BT on permanently this would go down a lot! I suppose i just need to remember that as I get into my car, turn on BT and it'll connect first time.
Just crap that other Custom ROMs can search on enable and connect. Worst still, I can't believe we're the only ones who have this issue.
I never thought samsung browser was something that good, i hardly even see it being mentioned. I never really used it much since i have not used sammy's roms since ginger bread came out, but have you tried opera mobile? This is, by far, the best browser I've used, it's not even fair to compare - it's on a totally different league. I was actually losing hope of decent browsing (tried just about anything) on Android until i came across opera. Needs to be the mobile and not the mini. Faith in Android browsing restored
if you haven't, give it a shot, free on market. If that's the main reason not to use a custom rom, you may be changing your mind soon
Sent from my GT-I9000 using xda premium
I am having just the opposite issue, I have a bluetooth headset that auto connects every time it's in range if I want it to or not, I'm running a stock rooted room kitkat on an old Nexus 7