Related
Hi all,
i am runing my trinity with WM6 and AX3l's rom. my issue is that i cant connect to my car stereo which is a pioneer DEH-P55. My trinity see's the stereo and gives the option for hands free but the stereo cant detect the trinity. my device is visible to others but the stereo wont pick it up. Any suggestions for a fix on this would be appreciated.
thanks
corm
maybe you have to push a button on your radio to activate first time pairing, that was the solution for my bluetooth headset.
(pairing from both sides)
just a suggestion, maybe it helps.
Try the Jetware bluetooth extension it has a 30 day trial and worked for my Alpine headunit its at http://www.jetwaremobile.com/
Thanks for the replies, but still no luck. I can pair other phones to the stereo but not this. Are there any settings that i may need to activate on the device that i am missing? its abit infuriating as i need to get this up and running as soon as.
rgds
Corm
activated "receive all incoming beams" ? its in settings/connections/beam
its already activated stormyb but thanks again for helping.
I always had problems using bt and irda...
I never succeed send/receive any file using my pc (my pc irda always worked fine with others devices). Beam enabled on commManager and on settings "receive all incoming beams".
When I try to connect (pair) using (htc) BT I get this error: the connection failed or the passcode is incorrect...
---
One time I tried to send a file to a nokia phone and I needed 30 min to succeed: restart phone, restart BT, restart beam, restart phone, restart nokia, restart BT, restart, restart, ....
Now I'm using the radio 1.46.00.11, rom eLiAs2.11wwe (before I was radio 1.38 and udk rom) and when I pair from htc, on pc I don't receive the pin request. If I pair from pc, I see the request for pin no htc but when I type it: "the connection failed or the passcode is incorrect".
Only one time I was succeed pair (and saved on device list), I typed 3 times the pin code, but after I can't transfer files...
From pc, I see the htc on the device list, if I try the ftp service, htc ask me: "xxx wants to connect with your device using bluetooth. Do you want to add XXX to your device list?" I answer yes but when I insert the pin, the pc give to me this error: "error establishing the connection"
If i try the voice gateway, after type the pin on htc I get this error on pc:
"the remote device closed the connection"
Using this last rom, when I try beam a file, I can't see my pc irda (using the udk rom I can to see but without success), I only see my pc BT but always "failed" the connection.
Nobody has the same problem?!
What bluetooth comms are you using, windows or Widcomm's?
I installed widcomm onto my laptop as I was suffering the same problems as you mention and I couild not get a bluetooth serial port setup either, once installed and restarted the pc then I just powered up both BT's and set the phone to visable and the laptop found it straight away with all the services and could setup the serial port.
I seem to recall there are numerous problems with most BT's when using the default windows drivers etc..
HTH's
hi, I'm using widcomm...
I didn't test again a bt headphone, but I have problems trying to connect to a nokia phone for example (n95, n73).
The irda never works... I tried too with a nokia phone and a remote control software for wm6... nothing...
All ok using headset BT...
I installed blueSoleil BT driver and now it is ok.
same ppc, same rom, same problem with my bt bury in the car and with other ppl's triyng to bt connect to my ppc. i can "see" them they can "see" me but there is no transmission TO me. I can send.
i am using the bt phone (bury) but onlt when I initiate the connection. i think it's a rom bug.
I have installed the Faria ROM on my Hermes and I can tell I am quite happy with it. Only thing I can't get to work is to use my Hermes with my AUDI built in handsfree carkit. I am able to get connected with it and I am also able to do phone calls, only thing is that there is no access to my phonebook, I also have tried to set the bluetooth to allow remot sim access, but still doesn't work. Does anybody know if there is a nweer bluetooth driver out there? Will be happy for any suggestion.
Thanks
Duke
I have Chryslers U-Connect and it accesses my phonebook I put into U-Connect. when connected , I have never been able to access my phonebook from my phone.
@pumpiron, sorry for the silly question, but what is U-connect and where would I get that from?
It comes with Chrysler Products. Check it out...http://www.jeep.com/crossbrand/uconnect/jeep/interface.html
Sorry to bring up this oldie, but I am now having this issue when trying to connect my bluetooth to my Kenwood radio. Downloading is extremely slow. These are the things I used to be able to do before I flash my Hermes with a new WinMo 6.5 ROM:
1. Dial a number through the radio. I now have to dial from the phone.
2. Calls log is not being downloaded. The only thing that shows up is the contacts list.
3. Simultaneous actions. Before the flash I used to be able to dial a number while information was being taken from the phone to the radio. This is no longer the case. I have to wait until info is downloaded before being able to make a call. This also prevents me from answering incoming calls.
Is there anyway to check what version of bluetooth (if any) is on the phone or if there's some type of upgrade?
Appreciate any help.
I previously owned the Evo and when I paired the bluetooth in my car with the phone, it immediately asked for permission to access the phonebook on the phone via PBAP (Phonebook Access Profile - a Bluetooth standard profile). This way the handset phonebook was accessible from the display on my car and also provided the information for Caller ID for contacts that existed in my address book.
I noticed when I paired the Epic with the car that the same thing didn't occur. When I try to access the handset phonebook from my car, it shows an entry for "MyInfo" and that is it. None of my other contacts are listed.
The question is whether there is a setting somewhere to allow this, or is the PBAP profile not available? In the technical specs for the phone, the PBA is listed as a profile for Bluetooth.
Same thing is happening to me. I have Ford Sync in an 08 Sable and it downloaded the phone book but when I try to voice dial it keeps asking me about "call MyInfo." Like that is the only listing there is. I am also having problems with the voice dialing on the phone itself (and not thru bluetooth), and with trying to record a memo. I keep getting the "try again" screen or "nothing is heard" notice. It's like the microphone is turned off. Anyone else having these problems? Thanks
bluetooth voice
I notice that there is no 'handsfree' profile available for bluetooth devices in the epic. With my former windoze phone, I did not have access to voice features from a bluetooth device until I applied a 'handsfree' profile rather than the standard 'headset' profile.
Does anyone know whether this is going to be fixed anytime soon? I really want the ability to press the button on my bluetooth, thereby activating voice dial and then voice dialing right from the bluetooth device rather than from the phone. I do not like physically handling the phone at all while in the car.
Ken B said:
Same thing is happening to me. I have Ford Sync in an 08 Sable and it downloaded the phone book but when I try to voice dial it keeps asking me about "call MyInfo." Like that is the only listing there is. I am also having problems with the voice dialing on the phone itself (and not thru bluetooth), and with trying to record a memo. I keep getting the "try again" screen or "nothing is heard" notice. It's like the microphone is turned off. Anyone else having these problems? Thanks
Click to expand...
Click to collapse
This is an issue with Ford Sync. It intercepts all interaction with the phone and doesn't relay any voice to the phone I believe. A feature I loved, but with 2.2 and 3.0 will become outdated quickly (I'd like to be able to issue Voice Actions over bluetooth for sending text messages and changing pandora stations).
Voice dialing on my '10 Fusion and Phonebook downloading works perfectly fine.
megabill said:
I notice that there is no 'handsfree' profile available for bluetooth devices in the epic. With my former windoze phone, I did not have access to voice features from a bluetooth device until I applied a 'handsfree' profile rather than the standard 'headset' profile.
Does anyone know whether this is going to be fixed anytime soon? I really want the ability to press the button on my bluetooth, thereby activating voice dial and then voice dialing right from the bluetooth device rather than from the phone. I do not like physically handling the phone at all while in the car.
Click to expand...
Click to collapse
I second that question. Sprint store tech says android 2.2 is suppose to fix that and everything else (exchange setting to allow attachment download) We'll see
Same issue with BMW and Epic
I'm having this issue as well, exactly like the original poster described, but in a 2010 BMW 3-series with iDrive. This is a huge disappointment coming from an EVO and iPhone before that. Hopefully this issue will be resolved quickly or the phone might have to go back. I can deal with everything else, including the inexplicable lack of ability to move messages between folders in Exchange, but this is crucial as I spend a lot of time in my car. Ugh.
Any help?
Any help on this issue? It really is a deal-breaker for me, as I bet it is for many others.
Fixed with the maintenance update?
So, here is an update on the situation. Yesterday I applied the Epic maintenance update that was just released. Today I was in the car when I received a call. Previously, my car would just show the phone number because it couldn't read the phone book on the phone, but today it showed the name and phone number. So I went into the "handset phonebook" option on my car, and it was able to see all of my Exchange contacts in the phone, something that I wasn't able to do previously.
It appears that this might've been addressed with the latest update, although the release notes (as far as I know) don't make any mention of it.
This happened to me the first time I synced my phone to a 2009 Mini Cooper S Works (similar to the BMW systems). All I got was "My Info". I was bummed out about it, since I'm in the market for a new car soon and I really liked the Cooper. I paired it to my girlfriend's VW Tiguan. Synced fast and easy and everything worked perfectly. So I was thinking, OK, stuck with a GTI then. Out of curiostity, I tried syncing it again to the Mini, and voila! Everything worked perfectly. It wasn't fixed by the DI07 update, this worked before I installed the update.
To all those having this issue, try syncing again. There wasn't anything that popped up on the phone or anything. I literally changed nothing, just retried it and it worked.
I solved Samsung Xcover (S5690, Android 2.3.6) connection to a carkit on Renault Laguna 3.
Steps used:
1. I root phone;
2. I used ES File Explorer to access system files. In ES File Explorer settings I give root privileges.
3. I installed from Google Play program “Mount / system (rw / ro)” (free).
4. I run Mount/system (rw / ro) and I enabled "mount r/w". He is active several seconds, so it goes quickly to ES File Explorer.
5. I open ES File Explorer: --- / system / app /. I look for Bluetooth.apk and I renamed to bluetooth.apk.bak.
6. File bluetoothpbap ...... . apk does not start at all.
The biggest surprise was that the car recognizes the phone, contacts, media, everything.
I hope to work on other samsung phones (I think it's a general problem).
Hello everyone
I am running the Virtuous ROM and I'm having a small problem. Whenever I try to connect to my Kenwood car stereo (Parrot bluetooth hands-free system, I think) I can make and receive calls just fine, only the call lists don't get synced.
I might be wrong, but doesn't one usually have to give the hands-free permission to do that first? Interestingly enough, the two devices are pairing without any kind of password whatsoever. I find this rather strange and an FTP server aside, I haven't found many options to adjust in the bluetooth settings.
Am I missing something obvious here?
Regards and thank you.
Anybody? Anything?
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!