can anyone tell me if I can update the Bluetooth in my HTC Desire or have more profiles. the phone is branded o2 but can be rooted. I dont want to change anything else in the ROM just make the bluetooth connect automaticaly & reliably to the car.
There are newer software builds available but have no mention of updating bluetooth.
Ther are no OTA updates available.
Software Number is 2.14.207.1
Andriod 2.2
Thanks for any advice in advance.
Trampsdad
Can't you just pair the 2 devices together? I personally don't use Bluetooth so no idea on that aspect. Also, the software is so out of date because o2 cba to release and update. There are major updates since yours. It might be worth considering to root so then you can flash a newer ROM, or infact, you don't need to root and just use an RUU. With the newest software. No need to root it then and less chance of it mess up.
Hope this helps
I still have some strangeness with Bluetooth. From what I read there are some updates in Honeycomb and maybe gingerbread. But I don't have a feeling what you are looking for is in FroYo
Sent from my HTC Desire using XDA App
Well I have a Kenwood Headunit with Bluetooth and the connection to that using stock Froyo and LeeDroid showed some interesting results. Gaps in the phonebook for instance. However, putting a 2.3 ROM (Ginger Villain) sorted that out, its fine now.
Bluetooth depends on the other device too.
What exactly is the problem you are having?
What Car do you have?
What Bluetooth system is installed (is it standard)?
I have used my desire in a number of cars (Vauxhall, Ford, BMW) without any isses with pairing, using the Phonebook,etc. is a different matter.
Personally, I have just received a new BMW 528i, and it doesn't get on well with my Desire at all.
It pairs OK and can use both the phone and music, but when I leave and return to the car, it just refuses to auto-connect again, and I have to go through the pairing procedure again.
Oh, except one - the time I went back to the garage to 'complain' about it and ask for advice, when it worked perfectly. Until I got home again!
Have experimented with my old Nokia N85, and that works fine, too. So it's either the Desire or an incompatibility between it and the car.
Oh, my Desire is running MCR r9 (FroYo) at the moment. Are there known issues with this? Info on any Bluetooth updates I could apply would be gratefully received!
i have to enter my pairing code every time i connect my bt headset - i took this to be a quirk for the moment - hoping its fixed in 2.2.2/2.3.x etc.
Lothaen said:
i have to enter my pairing code every time i connect my bt headset - i took this to be a quirk for the moment - hoping its fixed in 2.2.2/2.3.x etc.
Click to expand...
Click to collapse
Im having this same problem also with a Pioneer Head Unit in my car.
Bluetooth has always been troublesome as it doesn't auto connect. It will connect if I either manually click on "Pioneer Head Unit" or turn Bluetooth off and on (which I automate with tasker).
The pin thing is new and happens with all roms I have tried except LeeDroid, (which I prefer not to use as I don't like sense much). Leedroid still has the auto connect problem.
daveaus said:
Bluetooth has always been troublesome as it doesn't auto connect. It will connect if I either manually click on "Pioneer Head Unit" or turn Bluetooth off and on (which I automate with tasker).
Click to expand...
Click to collapse
Some good hints there - thanks!
I can connect far more reliably if I initiate the connection from the phone than from the car.
Likewise, if BT is switched off on the phone and then turned on after the car is on, then it sometimes works, too. Certainly don't need to re-pair anywhere near as often.
Can I ask how you use Tasker to automate the BT switching? I've not used that (I use Setting Profiles instead which I understand does roughly the same thing), so am curious what kind of rule you have that's useful for this.
Cheers.
TheMegaMan_ said:
Can I ask how you use Tasker to automate the BT switching? I've not used that (I use Setting Profiles instead which I understand does roughly the same thing), so am curious what kind of rule you have that's useful for this.
Click to expand...
Click to collapse
I use the following rules:
On wifi connection turn off bluetooth
On wifi disconnection wait 30 seconds and turn bluetooth on.
If not wifi connected & not bluetooth connected turn bluetooth off and on every 5 minutes.
If not wifi connected & not bluetooth connected and incoming call turn bluetooth off and on.
If not wifi connected & not bluetooth connected when display switched on turn bluetooth off and on.
The battery drain hasn't been a problem, if I go away or won't be using my car for a while I disable tasker. Of course this doesn't help when it keeps asking for the pin.
daveaus said:
I use the following rules:
Click to expand...
Click to collapse
Ah, cunning! Of course...toggle it when it's not already connected. Prifile Settings doesn't seem to let me toggle things like BT directly, although I could probably do so by setting some appropriate profiles.
I'll have to experiment...or just buy Tasker, instead!
daveaus said:
Of course this doesn't help when it keeps asking for the pin.
Click to expand...
Click to collapse
True, but so far in my case, I've only had that when I've tried to initiate connection from the car. Hopefully your trick will mean I don't need to do that so often.
Anyone found a gingerbread rom (or any rom!) with improved Bluetooth?
I have found the bluetooth to be terrible on the desire. I have got about 3 devices that my phone just refuses to pair with.
Currently I am trying to get it to connect with an Elm 327 Obd scanner. No luck, it asks for a pin, then I enter the pin, but it immediately rejects it.
I have tried oxygen rom, leedroid, stock froyo, everything...
I also have a parrot hands free kit that does the same thing, asks for pin, then does nothing...
Something makes me think it might be the radio or something. Except that my phone DOES connect with my scala motorbike helmet... So frustrating
Sent from my HTC Desire using XDA App
Related
I've been struggling for several months now to get my MDAC III working with my built-in car Bluetooth hands-free. The full details are below, but in short, I'm told that the system seems to work OK with Wizard, and I'm wondering what about the Wizard could be different to the Artemis (Bluetooth stack perhaps?), and if there is a difference, is there anything I can do about it?
The full issue: The system I'm trying to connect with is in a Land Rover Freelander 2 (LR2 in the US) Initial pairing was a bit hit and miss, but now I've got the the phone paired with the PTI, that's not a problem and they automatically pair whenever I start the car.
I can succesfully initiate or answer a call from the car, but the call itself isn't routed through the car's speakers/mic, it just goes through the phone as normal. However, once in a call if I select the "privacy" option on the PTI (which would normally have the effect I've already got of passing the call to the phone), and then select the "hands free" option, it does what it should and routes the call through the car. Effectively, it's as if the system starts in "privacy" mode rather than "hands free". Once I've done this once, subsequent calls work fine, routing straight through the car, but only until the ignition's turned off. The next time I start the car up I'm still paired, but calls go through the phone again.
If anyone's got any suggestions, I'd really appreciate them.
Thanks!
Try this
Had similar in a BMW...
Try www.jetwaremobile.com
Thanks, did try that but didn't seem to help, it seemed to be more geared towards additional functions like phonebook syncing rather than just getting a working connection in the first place. Maybe I'll give it another go.
Same Probleme On 207
hi,
I have the same ....
I precise that work fine with the original m650 rom, i search many hours but i found nothing, i try bluetooth toggle with no effect...
please help us !
thank for dev for everything they do !
RE
I try many combinaison so:
if i want to use my bt car kit, i'm forced to validate hands free option at every phone call...
I think it's btaudiotoggle the cause of mly problem, he is included in the aje rom...
you think it's possible ?
TangerineTractor said:
Had similar in a BMW...
Try www.jetwaremobile.com
Click to expand...
Click to collapse
Thanks TangerineTractor!
I fixed the problem I have with car kit of OPEL ANTARA using the software you said. It works disable sending Phonebooks.
I am having a similar problem with Wizard Mobile 6 cooked ROM. Before with the official O2 ROM on my Xda Mini S, it worked fine. The car would automatically recognise the phone whenever in proximity, and all calls would go through the speaker.
Now, I have to press the car kit's button (Nokia Bluetooth) each time I get in the car, to tell it to search for devices - i.e. the phone doesn't automatically announce its presence.
So, is there a different Bluetooth Stack we can try?
My Orbit works fine with my Nokia CK-7W using a B&B ROM.
Thanks, and yep that's the same car kit I have.
When you get in the car, do you have to do anything, or does the car kit automatically detect the phone? Mine doesn't since getting the Wizard Mobile 6 cooked ROM.
Do you know what Bluetooth Stack you use, and if I can download it anywhere for the Wizard?
No, just switch on the ignition key and away it goes. Also if the car kit is set as the default hands free if the phone rings it should try to connect to the car kit.
The radio I am using is 2.95.90 I have no idea what bluetooth stack it is, Tom Codin cooked the ROM, he will know.
Okay thanks. Does anyone know if the BT Stack is part of the Radio ROM? If so I'll just try a different Radio ROM.
Hi all,
Anyone can confirm that Desire has a rSAP (remote Sim access)?
Some people are saying it doesn't work with their Nav, some say it is working.
Any one got it hooked up to their Vw/Audi/Skoda RNS Nav?
Looking to change from my TouchHD.
Cheers,
Android does not support the SAP/rSAP protocol. It may be that some people have it working on cars that use the HFP or HSP profiles.
Thanks mate, not good at all!!!
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
swissman said:
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
Click to expand...
Click to collapse
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Maybe you could check if it has another setting to retrieve data from the phone.
From what i know the new modules used in audi/vw/skoda are Novero modules (part of the nokia business) which only supports rsap.
The older modules are from harman/Becker and do support al the possible connectiontypes.
You can check which type you have under the passengers frontseat, the modules are build in under the seat, not in the radio.
If you have a Novero, tough luck. But you can always check on the local car junkyard if you can find an old car which does have a harman/becker, and build that one in
salahag said:
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Click to expand...
Click to collapse
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
salahag said:
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
Click to expand...
Click to collapse
Exactly... you can even read/send sms directly through the display and through your car multimedia system.
Ford
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Tirinoarim said:
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Click to expand...
Click to collapse
I got the stock Android and it's showing Android 2.1 update 1.... but not working ;-)
Hmm - well I'm trying to use my HTC Desire with a 2010 Audi A3 with BT and not having any luck so far. Although it paired and transferred the phonebook (took quite a few minutes with a couple of hundred contacts), it's now being really flaky and sometimes just refusing to connect at all. I tried un-pairing/re-pairing but to no avail. It just seems to work sometimes for a bit then stop again. By comparison pairing my Desire with a Jabra BT headset worked fine.
Anyone else having these problems? Anyone know of any updates for the Audi software? (if not I suppose I'll just need to wait for Froyo and hope that it fixes things )
my desire works well with my VW golf.
phone book, calls (dialing and receiving) and status dispay working. not working is SMS
Hey Folks,
there is room for some BT "education", because most people don't know the difference between rSAP and Handsfree.
Handsfree is working like a BT headset - most disadvantage - you are using the phoneunit of your mobile.
rSAP is using BT protocoll to get only the SIM card of your mobile and work together with the phoneunit of your car.
For Audi you can see on which mode your are conntected at the MMI-Display => "SIM card icon" stands for rSAP while "Mobilephone icon" represents handsfree mode.
no rSAP
I could be wrong, but I was of the impression that Nokia had patented the RSAP protocol, so you're not going to see it on non-Nokia phones. Irritating, really. Some car users have retrofitted their handsfree kits with a module that uses handsfree profile with some success but it's not going to use the car antennae etc in this case.
rSAP is a "STANDARD" for bluetooth protocoll in general.
Nokia was one of the first, thatswhy the Nokia unit has some "problems" in early releases....
Well I picked up my Skoda Superb last week, dealer told me they were fitting the new GSM 3 units that had just recently changed, not that it meant much to me.
Anyways it did work fine first couple days then started playing up with not connecting, I went into the options because I found it was connecting to media, but not phone, so I disabled the media option on the phone for the bluetooth connections and its been fine ever since.
Desire running Modaco R4, R5 & R6 now also ok.
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Will take a look though see if its connecting with a phone or sim card, I had noticed the signal always seemed really good even if the phone was berried in the car somewhere so maybe the rSAP explains it.
Tinyk said:
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Click to expand...
Click to collapse
Do you have a link to the thread that includes this file by any chance?
Do not mix up android 2.1 and 2.2.
AFAIK the modaco roms are froyo which should have a better bluetooth stack than eclair.
Well some good news! The FroYo/2.2 update on the Desire seemed to do the trick for me and I now seem to be able to get a stable BT connection with my A3. Phonebook transfer working fine too and it's reacquiring the connection when getting back into the car.
Any hope for Android 2.1?
Alanjrobertson: did you say you got your HTC Desire Android v2.1 phone working with your Audi, albeit a bit flaky? I cant get my HTC Desire Android v2.1 phone working with my VW EOS working at all.
What was the process you followed? The process I went through was to turn on phone’s bluetooth and make my phone discoverable. I then initiated a search from the car. It found my phone and displayed the correct name. However, when I chose the “connect” option on the car, it gave the error message: "mobile telephone phone is not compatible" on the car’s MFD.
Is this what you did? Is there a better way of connecting?
The car’s entertainment system is RNS510. I’m not sure if this is associated with Bluetooth or not.
My previous phone (Nokia 5800) worked OK, but my Desire doesn’t.
I am hoping that the Android v2.2 upgrade will fix my problems, but I’m still waiting for the update from Orange. It could take a while by the sounds of things.
I contacted HTC and they told me “The HTC Desire does not have the remote sim access profile. we currently have no plans to update the Bluetooth profiles on the device.” This makes me worried that when I eventually do get the Android v2.2 upgrade it will not work.
Any ideas other than waiting for the Android v2.2 upgrade?
All,
I have this small issue with my HTC Desire and the Parrot CK3000 Evolution. Until now, everything works perfectly (calling, sending contacts, voice dialing, ending calls,...)
However I have one small issue. When I enter my car, and my phone is locked, the Desire will not pair with the Parrot. From the moment I activate the screen, pairing is done within a few seconds. I already tried to leave it there for half an hour, no pairing, touched the screen, pairing within a few seconds.
It looks to me like the bluetooth is not active / alive when the phone is locked (or in sleep). From the moment the pairing is done, everything works fine, also when the phone is back in lock / sleep.
Anybody has anything similar or has a solution for this? I searched the market for some kind of Bluetooth-keep-alive application, but could not really find it...
Thanks in advance,
Best regards,
Speedygerre
Small bump, nobody any idea for a solution or somekind of workaround / app?
-------------------------------------
Sent via the XDA Tapatalk App
I have a similar situation with my Audi A5 (factory BT kit).
It will connect when the phone is locked (screen off etc) but it can take anything from 1 to 10 minutes before it does connect.
Like yourself, my Desire connects immediately if the phone is not locked.
Strangely, it appears to work OK in my Mazda MX-5 which has a Kenwood DNX8220BT system (Bluetooth, SatNav, Ipod, coffee maker etc) - and the Bluetooth is a Parrot system. Having said that, I haven't used the MX-5 much since I got my Desire so it might not be a representative sample.
There is definitely something amiss though.
I have a Parrot CK 3100, and whilst I am happy to report that I do not have the same problem as you, I did have a problem syncing my contacts.
Check out this site, and download the software to udate to the latest firmware. You will need a laptop with either built in bluetooth, or a seperate bluetooth dongle.
http://www.parrot.com/uk/support/onlinehelpguides
I updated the firmware on mine, and now my contacts sync properly.
There is a good chance that updating could fix your connection problem as well.
Sorry forgot to add, that updating the kit really is a doddle, but their software is Windows 32bit ONLY and definitely no MAC!
Thans pergolesi, I hope your suggestion workshop, I will try it when I have some time one of the next days.
However I still think it has something to do with the Desire, since syncing workshop perfectly when Desire is not locked...
-------------------------------------
Sent via the XDA Tapatalk App
I don't know about the Bluetooth but I know my wifi deactivates after about 5 minutes when it's locked even though I have it set to never turn off. Maybe the Bluetooth is doing the same.
Perhaps not much help, but I sometimes play music from my Desire on my car headunit using Bluetooth streaming, and that continues to work fine when the screen goes off and the phone is locked. It also still responds to commands from the headunit (skip, pause, etc).
Once it's connected, everything works OK for me as well, it just is the connecting moment which apparently does not always work
REB1 said:
I have a similar situation with my Audi A5 (factory BT kit).
It will connect when the phone is locked (screen off etc) but it can take anything from 1 to 10 minutes before it does connect.
Like yourself, my Desire connects immediately if the phone is not locked.
Click to expand...
Click to collapse
Can I ask what year your A5 is? I've got a 2010 A3 and BT doesn't work properly with my Desire I can get it to pair, but then it will disconnect a few minutes later and the only way to reconnect seems to be to unpair/repair or switch the car off/on. When it IS working it can make calls, etc. fine - but I just can't get it to stay connected I tried my Audi dealer but they just said it's not on the Audi list and there's no update to support it, so interested to hear you got it working on your A5.
alanjrobertson said:
Can I ask what year your A5 is? I've got a 2010 A3 and BT doesn't work properly with my Desire I can get it to pair, but then it will disconnect a few minutes later and the only way to reconnect seems to be to unpair/repair or switch the car off/on. When it IS working it can make calls, etc. fine - but I just can't get it to stay connected I tried my Audi dealer but they just said it's not on the Audi list and there's no update to support it, so interested to hear you got it working on your A5.
Click to expand...
Click to collapse
My A5 is a 2008 model with SatNav and therefore MMI High. The Desire paired straight away with no problems and both the car and the phone remember each other - it just takes awhile sometimes for one or the other to realise it and connect.
I'm pretty certain that it is the phone that has the problem as I had no such problems with several Sony Ericsson phones previously.
REB1 said:
My A5 is a 2008 model with SatNav and therefore MMI High. The Desire paired straight away with no problems and both the car and the phone remember each other - it just takes awhile sometimes for one or the other to realise it and connect.
I'm pretty certain that it is the phone that has the problem as I had no such problems with several Sony Ericsson phones previously.
Click to expand...
Click to collapse
Thanks - interesting. I wonder how many different BT stacks Audi run - I was hoping they'd share some common code and therefore be updated quickly but it sounds like this isn't the case given that it's working fine on your A5. Thanks for the info though!
Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.
It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse
jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!
Quick question whether there is an app, mod, or even build.prop edit that would allow my Note II to automatically try to connect to my car's single din Kenwood KDC‑BT952HD. Only thing the head unit tries to do when connected is re-download contacts, but it turns on as soon as my car turns on and it'd be a lot faster if my Note automatically attempted to connect to the head unit instead of the bluetooth popup with listed devices, which I don't even have considering I'm running Whompasaurus V2.9. so if there's any way I could even get the pop up that'd be great too!
I use Tasker to turn on Bluetooth and connect to my earpiece. But I need a trigger and I need to turn on my earpiece. The trigger I use is activating my map app.
So without a trigger, I don't know how to do that.
I'm new to tasker and I'm not sure how to enable the auto-connect through tasker.
I am new to Tasker too.
Task / Net / Bluetooth
will turn on/off/ toggle Bluetooth
Task / plugin / Secure Settings (separate app) / BT Connect
Will connect to your chosen Bluetooth device.
My best advice is to play around. Also, here is the first of a 3 video series on Tasker.
http://www.youtube.com/watch?v=BEhnOJl5mTo&feature=youtube_gdata_player
maybe I'm missing something here, so may suggestion by be complete off.
Maybe leaving BT tunred on your GN2 before you get in your car. Or turned it on before you get in the car. I'm assuming the ROM you're using has a BT toggle. The thinking is that your headunit will try to automatically connect to any paired BT devices. If so, the GN2 should automatically connect when the deck does it's search.
This works for me when I try connecting to Jawborn Big Jambox or Jawbone Era or other BT devices I have paired on my GN2. It may be worth nothing I'm on a deoxidized stock rom. But I this also worked when I ran AOSP roms on my Evo 4G such as CM.
If the headunit does not do a pair device search and connect when it turns on, then I would definitely try suggest above. I have no clue, and that's better than nothing.
no autoconnect on GN2
Once you had a BT connection with your car and leave it at the gas station e.g. it won't reconnect when you're back!
Sad, but since then I tried the mighty Tasker and similar apps, but was happy with the app called "Bluetooth Auto Connect".
You can define the simple trigger, when display on....
So whenever I get back into the car, I hit either the menu or start button, that's it. Without unlocking you are back connected.
The only other annoying thing that you might be able to fix with Tasker is, that right after the A2DP establishes the connection the player starts playing the last song, which I obviously don't want most of the time.
Also Play Pause Next etc over BT doesn't work too well on android.
I have a Alpine head unit and as long as my bt is on before I start the car everything syncs automatically.
Sent from my SPH-L900 using Tapatalk 2
Lord Sekhmet said:
I am new to Tasker too.
Task / Net / Bluetooth
will turn on/off/ toggle Bluetooth
Task / plugin / Secure Settings (separate app) / BT Connect
Will connect to your chosen Bluetooth device.
My best advice is to play around. Also, here is the first of a 3 video series on Tasker.
http://www.youtube.com/watch?v=BEhnOJl5mTo&feature=youtube_gdata_player
Click to expand...
Click to collapse
That's interesting, I always wonder what exactly secure settings does, but this example helps.
Sent from my SPH-L900 using xda premium
1FstYOTA said:
I have a Alpine head unit and as long as my bt is on before I start the car everything syncs automatically.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I have a Kenwood Dnx6980, and my experience has been that once my phone has been setup to sync ... The Kenwood will talk to it automagically.
This is using AOSP or non stock roms. Ofc.
Sent from my SPH-L900 using Tapatalk 2
Tasker worked for me
Skripka said:
I have a Kenwood Dnx6980, and my experience has been that once my phone has been setup to sync ... The Kenwood will talk to it automagically.
This is using AOSP or non stock roms. Ofc.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Guys I have a Chinese brand double din...MobileVision...or something like that and using Tasker along with Bluetooth autoconnect worked for me. The posts above describe exactly how to set it up and it worked for me.
[email protected] said:
Guys I have a Chinese brand double din...MobileVision...or something like that and using Tasker along with Bluetooth autoconnect worked for me. The posts above describe exactly how to set it up and it worked for me.
Click to expand...
Click to collapse
Bluetooth autoconnect's main feature works for my xperia pro (turn on bluetooth, connect to your selected devices in automatic)
Bluetooth autoconnect's tasker plugin is not working for me. I can use it, sort off, but it does nothing. Like, "Press the button, but there was no reply!"
Well that is odd. I have a Pioneer unit and my phone connects to it as soon as it detects it in range. Even if I turn off BT and then power it on, the phone automatically connects to the head unit without any intervention on my part. Sounds like an issue with your stereo.
No stereo issue. On some of the touch wiz based roms bluetooth DOES NOT auto connect. On most (if not all) aosp roms bluetooth DOES auto connect. Currently on ma7 stock with root and it auto connects. When I was on whomp, jellybombed, and labrats
Sent from my SPH-L900 using Tapatalk 4 Beta
Bluetooth Connection
Hi Guys,
Im glad i found this thread, im wondering if anyone could help me out.
My scenario is, my bluetooth is connected to my car radio playing files. When a call comes in, i need it to disconnect from the car radio and connect to my bluetooth headset, all without turning off bluetooth ( preferable )
My possible solutions are:
1 ) By using automagic, ive managed to get alot done with this app, but this seems beyond it.
2 ) Getting automagic to start an application when a call comes in which will force bluetooth connection to a specific bluetooth device and disconnected from other devices.
Anyone got any suggestions?
devilshady said:
Hi Guys,
Im glad i found this thread, im wondering if anyone could help me out.
My scenario is, my bluetooth is connected to my car radio playing files. When a call comes in, i need it to disconnect from the car radio and connect to my bluetooth headset, all without turning off bluetooth ( preferable )
My possible solutions are:
1 ) By using automagic, ive managed to get alot done with this app, but this seems beyond it.
2 ) Getting automagic to start an application when a call comes in which will force bluetooth connection to a specific bluetooth device and disconnected from other devices.
Anyone got any suggestions?
Click to expand...
Click to collapse
not sure of your rom, but both TW and CM allow you to set whether each connection is Media or Phone. put your headset to phone and your car to media only. when you answer the phone the headset should take over.
Lord Sekhmet said:
I use Tasker to turn on Bluetooth and connect to my earpiece. But I need a trigger and I need to turn on my earpiece. The trigger I use is activating my map app.
So without a trigger, I don't know how to do that.
Click to expand...
Click to collapse
Could you share how you did this? I am completely confused by the interface.
I am wanting the same setup but also for music player and Pandora
I haven't found an example to follow that even comes close.
---------- Post added at 09:54 AM ---------- Previous post was at 09:43 AM ----------
Lord Sekhmet said:
I am new to Tasker too.
Task / Net / Bluetooth
will turn on/off/ toggle Bluetooth
Task / plugin / Secure Settings (separate app) / BT Connect
Will connect to your chosen Bluetooth device.
My best advice is to play around. Also, here is the first of a 3 video series on Tasker.
http://www.youtube.com/watch?v=BEhnOJl5mTo&feature=youtube_gdata_player
Click to expand...
Click to collapse
That helps,
I was going task / setting / Bluetooth
Still not sure how to set the trigger however.
[EDIT]
The first few minutes of that video answered my questions.
Sorry, I partied late last night and still kinda loopy.
Sent from my Jedi MasterX Note 2