Hi @ all,
just got my HD2 with german ROM and one of the first things I tried out was to get a connection to my car (Audi A6) through the remote sim access profile (SAP, rSAP) - but it didn't work...
Does someone use the HD2 in his car using the sim access profile, as available in Audi or VW cars?
I have
- Audi A6 Avant (model 03/2008)
- using the "Audi rSAP Adaptor" in the car cradle, located in the arm rest
- everything in the HD2 is activated for Sim Access
Result:
HD2 and car are connecting, I have to put the 16 digit security code in my phone, but after that the SAP mode does not start, and so I have no access to my phonebook. It seems that I only have a "normal" bluetooth handsfree connection, because the HD2 still shows that he is booked into the mobile network - and when rSAP is active, the phone itself disconnects from the network and "falls asleep".
I restarted my HD2 several times, also the rSAP-Adapter by turning ignition of the car off and on until the adaptor switches off, deleting the connections, creating new connections, but nothing helps...
Any comments or experiences from other users are highliy appreciated
Finally, I have to remark that my HTC Snap, which I just upgraded to WM 6.5, works very good im my car with the rSAP - no problems at all, I get all my contacts in the MMI.
Thanks in advance,
Jolig
Just got my HD2 and am having the same problem.
I'm trying to connect with a 2009MY Skoda Superb with the rSAP bluetooth kit.
This works fine with my E71 and my HTC Touch Cruise.
I've been told that there used to be an issue with OBEX authentication on previous versions of Windows Mobile. Apparently, it was important to disable this authentication. However, I can't see the checkbox in the version of WM that the HD2 is running.
Does anyone know what registry entry this checkbox might have been changing?
Thanks,
Bagpuss.
Thanks Bagpuss,
who gave you this information?
I hope someone can solve this problem....but I fear we have to wait until we have more HD2 - owners
-----------------------------------------------------
EDIT:
I just have read something about the "Schaps Advanced Configuration Tool" where someone with similar problems activated OBEX (but it was an older Win Mobile device, and some months ago) - perhaps this could help?
But I just installed version 3.3 of this tool, but it doesn't work on my HD2...
Hi Jolig,
Check out this thread:
http://briskoda.net/superb-ii/howto...us-rns510-using-non-compatible-mobile/131709/
on Briskoda.net.
One of the guys there had lots of problems getting his WM phone to work, and posted the fruits of his labours.
From what I can tell, we can't use the CAB file he mentions, as rSAP is built into the OS version that the HD2 uses.
I've actually logged this issue with HTC, and am awaiting their response. My company is considering the HD2 as our next standard handset, and we won't go for it unless the rSAP functionality works with all VW/Audi group cars.
I'll let you know if they get back to me.
Bagpuss.
Thx Bagpuss,
and yes, in my opinion it's a mess that the rSAP is apparently VERY unimportant for most people or manufacturers...otherwise we wouldn't have this trouble....
I will come back too if I should find some news.
Had the same problem, tried lots of stuff but none of my WM devices is able to work with the rSap protocol. Gave up on it and then my Skoda Columbus system was stolen.
Replaced it with a JVC 7000 with detachable front. Disabled the rSap carkit and am now using the JVC BT carkit wich is working great. The problem is in the MS BT stack. It is not supporting the rSap the way it should. Only phones that work flawlessly are Nokia's I'm afraid...
The lack of rSAP support is what made me ignore the iPhone this time around.
I was hoping that the HD2 would be a viable alternative, but sadly, it doesn't look like this is going to be the case.
As I bought it over the phone, then I've got 7 days in which to return it. If I can't get it to work, then I guess I'll be getting an N97 or N97 Mini (which will definitely work). :-(
Bagpuss.
@ Bagpuss,
otherwise, as I wrote, I can recommend trying the small HTC Snap (or also called Maple?).
Ok, this one has no touch screen and also a very small screen - but I can confirm he works with rSAP and is not too expensive. I will keep this one, although I now have the HD2
As to Bagpuss' information concerning the OBEX, I tried the following:
- installed the newest .NET framework version
(that was necessary to get Advanced Config Tool v 3.3 running)
- install Schap's Advanced Config Tool
- in the menu "Bluetooth", I enabled OBEX
- after that the config tool does a soft reset
...still no success....no SAP and no phone book
I also wrote an email to HTC - it's really annoying, having SAP in the phone etc. and nothing works.
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Hi Binks821,
Binks821 said:
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Click to expand...
Click to collapse
Can you confirm if your Golf has the premium bluetooth preparation?
There are two different versions of factory bluetooth kit for the RNS510, one which simply acts as a handsfree device, and the other (premium) which is a complete GSM phone.
It's the premium kit which uses rSAP, and which seems to be incompatible with the HD2.
You can tell if your Golf is using rSAP by checking to see if the signal strength meter on the HD2 shows any bars when connected to the car. If it does, then it's not using rSAP. If you see the signal meter with a little x in the corner, then it is using rSAP.
If you do have rSAP working, then I'd really like to know which firmware version your RNS510 is running, and also which firmware version you have in your HD2.
Thanks,
Bagpuss.
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Hi Binks281,
Thanks for the confirmation.
I've now done some further testing in my car, and managed to have some success.
This is what I did.
In the car:
1) Remove all device pairings from the bluetooth system in the car.
On the HD2:
1) Perform a hard reset.
2) Turn on bluetooth. Make HD2 permanently discoverable.
3) Make sure rSAP is enabled (it is by default).
4) Turn off SIM pin (turns out this isn't necessary, but I wanted to make things simple).
So, at this point, I have the car system with no paired phones, and the HD2 with factory settings and no personal data (contacts etc.). I also made sure there were no contacts on the SIM card.
Back in the car, I perform a device search, and it detects the HD2.
I select the HD2, and the car displays the pairing password (1111 2222 3333 4444).
On the HD2, I enter the password.
I then get a prompt saying that Skoda_rSAP is trying to connect to the remote sim access service. I say allow, and also tick the box to allow all future connections.
After about 10 seconds, the maxidot in the car says 'New SIM card recognised', and prompts me to create a new user profile. I called it 'HTC_HD2'.
After about another 15-20 seconds, the car should extract the SIM details from the phone and the phone name, network and signal bars should appear in the car display.
You can now make calls, but there is no phonebook.
Given what others have said about the phonebook access, I'm pretty sure that this is what was stopping the pairing from working the first time I tried it. I've heard various stories, some which say that the phonebook access only works with SIM card contacts, some which say it only works with OBEX authentication switched off and so on.
If you look at the paired devices screen in the phone, then you can see connections coming into phone. First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
I'm still trying to work out what is causing the problem with the phone, but I have done the following things:
1) Told the car to only sync phone memory contacts. By default, it's set to sync both SIM and phone memory. You can configure this on the car by going to Settings -> Phonebook -> Select Memory, and choosing 'Mobile Phone'.
2) Created four contacts in phone memory, one with only 1 mobile number, one with 2 numbers (mobile and home) and another two with three numbers (mobile, home and work). I've then gone into Settings -> Phonebook -> Upload and sync these across to the car.
So far, this has worked fine and disconnecting and reconnecting to the car works without a hitch.
I'm now going to try syncing a small subset of my contacts with ActiveSync to see if this also works.
If it does, then I'll gradually increase the number until it either works, or fails.
I'll report my progress here.
Bagpuss.
Thanks Bagpuss,
sounds interesting!
I think tomorrow I will try this also:
- remove all paired phones in the car-system
- delete all contacts
- disable SIM Pin
Temporarily I am not sure if I will do a hart reset in the first step because I've already installed so much... When the work fails, I thing I must do it
I will report what happened.
---------------------------
EDIT:
Ah, come on...TV this evening nothing interesting, wife in bed...I tried it, including hardreset
No success.
Bagpuss, what I detected:
First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
Click to expand...
Click to collapse
This connection to the Sim Access Profile I see also, but only for one second, then it dissappears and then the connection "Handsfree" comes up - and this one remains....
I do not know else what to do.
I now reconnected my beloved HTC Snap/Maple, and now I will start installing my apps on the HD2....
Hi Jolig,
Sorry to hear that it didn't work.
By the sounds of it, the Audi system is somewhat different to the VW/Skoda one. From what I can tell, your system also appears to support using phones in handsfree mode (I'm guessing that the iPhone works in your car).
In the VW/Skoda cars, you can either have a car kit that acts as a handsfree device or one that uses rSAP, but not both.
It could just be that the HD2 isn't responding to the rSAP request quickly enough to satisfy the MMI. In that event, it falls back to using handsfree mode.
When it shows 'handsfree' on the HD2, can you use the MMI to make calls?
This whole area seems to be a bit flaky on the HD2, as I still can't work out why mine didn't work when I first tried.
Bagpuss.
Binks821 said:
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Click to expand...
Click to collapse
Hello Binks821,
I believe that I have the same hardware situation like you but I can't get my HD2 started on my VW Passat with the Premium FSE. The problem is, that I can go through the whole "finding and connecting process" and can save the PIN but then the Connection gets lost between the HD2 and the PFSE. If seems that the PFSE can't connect to the Network (E-Plus) but why the BT-Connect gets lost in this case.
Maybe you can help me to get it work. Thanks a lot!
Negropo
Hello everybody,
maybe I found a solution that work for every sap-handsfree-set. I tried the hint was given on the german car forum "motor-talk" for the connection problem between a vw pfse and the htc touch diamond with wm 6.1 or 6.5.
The trick is that you have to disconnect the HD2 from the pfse by manual when the car first want's to connect automatically. You have to go to the BT-Setup to the tab where are the connected devices listed. If you click on the "+" right of the name of the device you should be seen the tab "Remote Sim Access" or in german "Sim-Zugriff". When the car connect's to the HD2you have to stop this by pressing disconnect in the right below corner of the HD2 screen. Then the connection is terminated. Now you have to start the connection manual over the menu in your car. In a VW you have to press only "connect" in the MFA. And then the HD2 should connect without problems. I don't know why it works but it does. Maybe there is someone here who can explain it and find another "automatic" solution for this problem.
Regards Norman
Well, I don't have a VW but an Audi with an rSAP-Adaptor in the middle arm rest. I fear this also doesn't work for me.
The problem is that this Tab "Sim Access" only appears for just one second, so I have no chance to make anything whithin this single second....and after disppearing of the tab "sim access" another tab "handsfree" appears - and stays. So it seems my Audi only recognizes a handsfree profile. I don't know why,
Temporarily I am happy that I still have my HTC Snap, which is working very fine with rSAP
@ Negropo, can you tell me in which thread at motor-talk you found that?
Thanks,
Jolig
Hi guys,
rSAP works fine with my Audi A4 BTA. I made the HD2 discoverable for any device and I activated the SIM access in the HD2 BT settings. Then I start searching for Bt device on my Audi BT and initiated the connection with the HD2.After inserting the 16 character pin everything works fine.
By the way ... the connections seems to be very stable. With the Touch Diamond I had from time to time connection interrupts where it was necessary to reset/restart the Touch Diamond again.
Best regards,
Matthias
@ Matthias,
"BTA" means that you have the built-in phone with rSAP, right? Is it a brandnew A4?
Related
Firstly, I love this phone, it almost does exactly what I want, Ok Windows Mobile 6.x would be good but I can without that, what I can't live with is the Bluetooth problem I have.
My device will not connect to the integrated bluetooth within my Skoda Octavia - it pairs up OK, but won't transfer the phonebook, and then after 5-10mins the connection is dropped! While it's connect it'll receive calls OK. The BT in the car is identified as SKODA_UHV, which I understand is the same of other VAG (Volkswagen Audi Group) cars, albeit with a different name.
It's been back to HP three times, the last time it came back with different BT version software installed, but that hasn't helped.
The car works fine with my old Nokia phone (and the HTC S710), the BT kit installed is the latest Skoda version....
Beer tokens await anyone who can provide a fix.....
do you see "hand free" on this connection? more things iI can think of is that lots of problems are due to lack of memory (device not card) pleas look at other thread on this issue it dose happen with new users ,one more thing is that you can set the connection to be not scure go over the settings
Yes the icon appears - everything is fine and works well for around 10mins, the the connection is broken.
The same happens if the unit is cold booted (thus ensuring maximum memory) and regardless of the security settings.
look for "ms-bt-stock" on xda ,you can also use google like "xda ms-bt..." see if one f the cabs will do the trick but from that day on you will not have your current bt screen (you can uninstall orHR) backup your device before installing so you can hr and restore ,good luck
Hi,
I have a HTC Touch 3G:
The phone is recognised (the name), it seems to pair ok (had to put in a 16-digit PIN), but then the car (Passat 2008) kit cannot connect to the phone for some reason.
Is there any solution for this subject?
Regards,
SpiderXman
I believe, you have to turn on the rSAP-Profile in the BT section of your Jade.
The VW vehicles have a BT-Unit, that only works with mobiles, that have the rSAP (remote SIM Access-Profile) enabled.
You know, how to enable it ?
Start-->Settings--> Bluetooth --> SIM Access
Hope this helps.
Greetings from Cologne,
Arniebirdy
Thanks for your help,
However I have done this procedure without success.
SpiderXman
Emanuel Ferreira said:
Hi,
I have a HTC Touch 3G:
The phone is recognised (the name), it seems to pair ok (had to put in a 16-digit PIN), but then the car (Passat 2008) kit cannot connect to the phone for some reason.
Is there any solution for this subject?
Regards,
SpiderXman
Click to expand...
Click to collapse
Hi/ I have the same problem with BMW X5 2004. paring is OK, but it dosn't work. it looks like connect and then disconnect (on phone screen headset icon appear and disappear). SIM access anable but no sucses
With touch 3452 it was not a problem. HTC support team told me that it is a conflict with BT kit on BMW. Now I see not only.... What to do???????
For most of the things discused here no one has paid.
For the things people have paided for go to the garage, i know i would!
Tom Lenferink said:
For most of the things discused here no one has paid.
For the things people have paided for go to the garage, i know i would!
Click to expand...
Click to collapse
You know you can, but how to resolve this issue ???? I think any payment can't, can it?
Hi,
using Jade's BT SAP with BMW 3 series (E91).
Works like a charm, except one issue: names in BMW phonebook appear sorted by first name.
In Jade its sorted - as it should be - by last names.
No solution found until now.
Anybody an idea?
Thanks
@ConsultantR
Try this for older BT Kits: http://www.jetwaremobile.com/
ConsultantR said:
Hi/ I have the same problem with BMW X5 2004. paring is OK, but it dosn't work. it looks like connect and then disconnect (on phone screen headset icon appear and disappear). SIM access anable but no sucses
With touch 3452 it was not a problem. HTC support team told me that it is a conflict with BT kit on BMW. Now I see not only.... What to do???????
Click to expand...
Click to collapse
Hi there,
I have a similar problem with my Volvo S40 2009. My Jade and the car connects each other but every 15-30 seconds the connection cuts off. It is very annoying while talking to someone, just in the middle of the conversation the radio starts to run again, since Jade loses connection to the car.
Is this some kind of configuration or setup issue? Any help?
I had this on / off problem too.
It was a fault in the phonebook contacts (some signs are obviouly not allowed in this bluetooth stuff (e.g. / or ")
So i moved all contacts to a folder, that wasn´t synchronised and that worked fine. Afterwards i added this removed contacts back step by step and was able to identify the problematic ones.
The easy way instead is to set up the phonebook to SIM only and copy the most used contacts to the SIM
Regards Quirlsen
Quirlsen said:
I had this on / off problem too.
It was a fault in the phonebook contacts (some signs are obviouly not allowed in this bluetooth stuff (e.g. / or ")
So i moved all contacts to a folder, that wasn´t synchronised and that worked fine. Afterwards i added this removed contacts back step by step and was able to identify the problematic ones.
The easy way instead is to set up the phonebook to SIM only and copy the most used contacts to the SIM
Regards Quirlsen
Click to expand...
Click to collapse
Thanks for the hint Quirlsen. Is it only the Name and Surname lines, which I have to correct? Otherwise it would be impossible, since I also have the Windows Live(Msn Messenger) contacts in the Contact List.
By the way is there a way to remove those Msn Messenger Contacts from the phonebook? They just popped up after I logged in once to Windows Live.
To be honest, i don´t know.
I´ve exported my whole contact list to csv, cleand it up with Control+H and imported it back (i had to add all picvtures afterwards
Your Win Live prob you could solve by defining different phonebooks for sync with phone and other stuff.
Apologies if this has been asked before, i've tried searching and now found a question that matches this, similar but not exact.
I have a Touch and now a Touch HD.
My Touch would connect to the cars bluetooth (Renault Laguna) and happily send over my phonebook so I could browse through it using the controls in the car.
My Touch HD connects ok, but doesn't send the phonebook (contact list always reports as empty). I've checked the Remote SIM Access box in case that makes a difference and ensured i'd copied over my contacts to the SIM first. I've even unpaired and repaired the phone, still 'empty'
I've tried using Jetware to get around this, which provides me with a "Windows encountered a problem with services.exe" which isn't very inspiring - but ultimately surely I shouldn't need to use a piece of software to 'add' a feature that existed on my older phone? Needless to say after all of this is done
Am I missing something? Any help anyone can provide me with would be appreciated.
My ROM version reports itself as 1.56.405.1 (43972) WWE, Protocol is 52.62.25.34U and radio is 1.13.25.24 if that offers any help?
Thanx in advance
I have to use Jetware BT to connect to my Alpine unit from http://www.jetwaremobile.com/
Does mean I can select the type of contacts i want to sync as well
Sorry, maybe I didn't make it clear.
Jetwaremobile doesn't appear to work properly on my Touch HD - it causes Windows Mobiles to report services.exe as needing to be closed. Performing a Soft-Reset makes no difference either.
I've emailed HTC about it but i'm not holding my breath on a response, its seems ridiculous that it did work on the old phone and now doesn't work on the newer model
The annoying thing is that I really really like the phone, but the inability to work with my cars built in BT 'headset' is something that makes me consider sending it back.
Hey guys,
I'm trying to connect my HD Mini with my Audi's rSAP adaptor (which is located in the center arm rest, so it's not the Audi in-built MMI-phone module). As far as I know the rSAP adaptor is identical to the adaptors available for VW and Skoda cars(?).
My Mini ist Vodafone branded, the ROM-Version is 1.11.162.1 (87652) GER, Manila-Version is2.5.20131825.1.
All of the first attempts to connect by SAP failed. After entering the 16-digit pin the HD Mini shows a message that the "Sim-Access-Adapter" wants to use a SAP connection. After accepting this screen the Mini shows the SIM Access profile on the bluetooth configuration screen for less than a second and then the HD Mini falls back to a hands-free connection.
After playing around with settings, resetting both devices I gave up and started a support call at Audi and HTC. When Audi tried at least to provide some helpful information, HTC provided less than nothing, their DACH support totally refused to provide anything! :sad: My previous HTC devices all connected fine to the rSAP-adaptor (though they weren't listed to be compatible with the adaptor). My Rose worked fine for months and also my S710 (by using the additional rSap sw-tool) are still able to establish a SAP connection while the HD Mini can't.
Then occurred the strange thing: My Audi MMI display showed the network strength symbol which is only shown if the Audi phone module have booked into my provider's net correctly.
I looked at the rSAP module: Same thing. It actually has booked into the net, which means the adaptor was able to read the SIM-card information. Next look to the HD Mini's display: It was booked into the net too but showed the "Sim-Access-Adapter" connected with Hands-free mode.
Since I'm using a Vodafone twin-card contract (second card is currently unused) having 2 devices booked into the provider's net can be explained but of course this state was extremly unstable:
My car's adaptor catched an incoming call and when I spoke and heard the voice in my car's speakers the HD Mini stroke back, catched the connection including the ongoing-call and I needed to continue on the HD Mini, while the MMI car's display showed no connection anymore.
Just a few seconds later I must recognize that the battle wasn't over: The car adaptor catched the call, (right now without SAP-mode but Hands-free mode) and I heard my colleague on the speaker again...for 10 seconds and this toggled again and again...
Since my older HTC gadgets worked fine and also the HD Mini is showing the adaptor's attempt for a SAP mode connection but then falls back to Hands-free-mode, I think that there must be some changes on the phone, bluetooth stack implementation, perhaps something with WM 6.5, it simply looks like a timing issue?
So right now I'm hoping that anyone can provide something useful. Perhaps an expert can point me to the right direction?
My last try would be to clear my second SIM-card on the weekend so that there are no contacts - perhaps this can make the difference... :-\
Any help is greatly appreciated of course!
Thanks and cheers, Alf.
Btw: Great board with tons of helpful information!
Quick Update:
I completed a hard reset to Audi MMI, Audi rSAP-adaptor, HTC HD Mini and removed all contacts and SMS saved on my second SIM-card but unfortunately no change in the behaviour of the HD Mini.
But then surprisingly another HTC support guy dropped me a line today so it seems that my support call at HTC is currently still in progress although the first HTC support contact refused any help...so let's see and wait...
Cheers, Alf.
Hallo!
Did you get any useful information from HTC support?
I'm using a HTC HD mini in a new VW Sharan with Premium FSE (so via rSAP). In general it works, but ...
a) often the connection process fails and I have to klick on "connect" manually.
b) sometimes I only get a standard FSE connection (not premium) and when I leave my car for some minutes and come back, it works again with "premium"
c) sometimes my HD mini does not reactivate the phone module after I left my car.
Michael
Although they tried to help and provided a tracking tool which logged status information about the bluetooth communication stack I never received additional help after providing my bluetooth log.
I ended in using the HDMini with the Audi built-In Bluetooth module of the MMI instead of the rSap adapter. :-(
That way the internal antenna of the car is not in use but at least the MMI is displaying the phone contacts...
Cheers, Alf.
Hello everyone, I bought a new 2015 Jeep Cherokee Trailhawk, it has the 8.4N Uconnect system installed.
I can connect with bluetooth with any other devices, and everything works properly....EXCEPT my phone which is a:
Samsung Galaxy S4
Branded by Fido in Canada
It is rooted, still using the default rom that came with it, but I'm running Nova Settings instead of Touchwiz
SGH-I337M
Android 4.4.2
-----------------------------------------------------------------------------------------------------------------------------------------------
In my car, I goto Phone/Bluetooth settings, have option to change PIN to anything I like but left it at '0000'
On my phone I goto Bluetooth, turn it on, make it visible, hit scan......it finds UCONNECT
I press on it to connect and THEN.......
On the car:
if it is the first time trying since reboot, you can see the passcode show up (six digits - 3 digits a space and then 3 more) and an ACCEPT button. This immediately disappears and it says 'There was a problem connecting with your bluetooth device. Please try again'
If it is not the first attempt after a reboot of phone, it just blinks that first screen showing the weird seperated 6 digit pin and immediatley goes to the error messager.
On the phone:
When it finds UCONNECT and u choose it, a message pops up saying to confirm the passkey and press OK or CANCEL.
It always shows a random 6 digit number.
At the same time, a system message appears for a couple seconds at the bottom of the phone that says 'Incorrect PIN or Passkey. Please try again'
Pressing OK or CANCEL just returns you to the bluetooth scanning screen which shows UCONNECT as an option.
If i try to set the pin on the car with what was shown in the phone, it doesn't work as each attempt to connect generates a random pin on the phone.
I have restarted phone, car etc. Reset car radio completely. Removed all devices remembered on the phones bluetooth. Checked with UConnect support that my phone is compatible -- they say that it might be that Fido in Canada has done something to the phone to prevent it to connect to cars, as it works fine with Verizon/At&T/ and apparently people on Rogers in Canada with S4 works too.
I have commented out the blacklist entries on the phone in /etc/bluetooth/auto_pair_devlist.conf - no change
I have removed all files in /etc/bluetooth - no change
Other phones connect to Uconnect with no problems.
My phone connect to my TV and a bluetooth receiver connected to my home stereo and a second TV different brand no problems.
This is my main phone, also my new car. It really sucks that I cannot get it to pair. Fido, Uconnect support can't help - they have never seen this issue before.
I don't understand why the car shows a pin of six digits with the space between the two groups of 3.
Also, why the phone says incorrect pin or passkey.
PLEASE HELP!! I am going crazy over this!
I really don't want to, but if there is no fix, I will have to backup everything, format the phone, install perhaps a Verizon or something build of Android and then try to connect with that (hoping it has no issues with phone/data use with Fido network over here)
Updated info
I just tested with anothers car....
2009 Nissan Rogue...works fine (is used as an audio device only...no phonebook etc features)
Also tested with an Iphone 5 to my Jeep and that phone connects fine.
I tried using an app called 'Bluetooth Fix Repair' from the app store. It gives an error at startup:
"Sorry this application cannot find your bluetooth setup folder on this device"
Can this be the issue?
The bluetooth folder I was working with in the OP was on the phone at etc/bluetooth
Should I have another one somewhere...maybe missing or corrupted?
Any help!?! Cannot find anyone else with this same issue here (xda) or on google etc.