Develop Bugs

Pairing problem with VW Scirocco (RCD 510)

Hello everyone,
I'm having a problem with the RCD 510 Premium Bluetooth kit that is installed on the new VW Scirocco and its been troubling me for over 2 months now.
When I first got my Scirocco the Bluetooth connection was working fine (for 3-4 months). One day out of a sudden the Touch Pro II was not pairing anymore with the car's bluetooth kit.
At the time I was using Windows Mobile 6.1 that originally came along with the phone. I tried the basics - deleting the connection, re-pairing - with no success.
So I gave a shot at phone's factory reset - still no luck. The phone is recognized when I use the "Device Search" function on the car, it prompts me to enter the pass code provided, I do so, the phone loses the GSM signal (which of course is normal) but then suddenly I get a message on the RCD510's main screen "No bluetooth connection to phone" that lasts for about 2 seconds.
Since the problem began, I tried factory reset the phone (as I mentioned before), and tried pairing before installing even a single software, still no luck.
I tried multiple ROM's in the meanwhile (I mean third-party ROMs from this forum) and now I am using the official Windows Mobile 6.5 from HTC for my phone.
I also did many tests using third-party applications for the rSAP protocol (JetWare hands-free extension, SAPSettings, some patches and drivers found around the net here and there) even though there is native support for rSAP since the first firmware that came along with the device.
As I mentioned before, the phone was pairing fine the first 3-4 months.
Please note that this phone uses the Widcomm Bluetooth Stack - not the Microsoft one.
Any help/ideas would be greatly appreciated.
PS: I apologize for the big length of the post, but I believe the more the information I provide, the more the chances to get proper help

Sorry i cant help you but.. I want your CAR...
Any pics?
Well.. try this
Unhook the cars battery. Let it reset the radio (make sure you have the radio code if any) and try again.. maybe the radio is holding some sort of setting. Resetting to default (like with the device) might do the trick..

.
Thanks for the idea. I'm kind of worried though plugging out the battery, because there are many settings besides the radio that probably will be lost if I do so.
You know all these new cars and their complicated electronic sensors...I don't mind losing minor settings for the car that I have adjusted, my main concern is that if anything goes wrong, I will probably have issues with the car's warranty. I still have 2 and a half years of warranty.
I' will probably have a talk with the dealership before doing that.
Many thanks for your thought though

hi i like to know if pairing went okay with the 6.1 rom because if so maybe when you switch back to this rom problems are solved

Nop
Unfortunately no
It was one of the first things I tried. Switching back to the official 6.1 ROM. I actually kept it saved on my hard disk and I tried it a couple of times - I mean when I tried other ROMs from time to time - hoping it would resolve the issue.
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
First logical thought would be that something has changed in the car's settings. But I have an Athena X7500 that pairs fine with the car up to this day. My car's dealership isn't much of a help...
Second thought - phone settings mess-up. But as stated in my original post, no factory reset helped, no switching to other ROMs, no playing around with settings.....
I'm really desperate. I'm thinking to switch to another phone, but besides this problem I'm quite satisfied with the TP2. And I do "need" Windows Mobile based phones, because I sync with Thunderbird's Lightning via BirdieSync for a long time now, and I am not willing to revert back to the horror days of MS Outlook. I carry my TB profile for over 2 years now and its customized the way it suits me for manipulating my 10+ email accounts.
Thank you very much for your reply though
Any other thoughts/recommendations?

i downloaded firmware 1.20 from volkswagen hope this will help me will try tomorrow with my laptop i am with a touch adapter connected to rns 510 no pairing with tp 2 at the moment for me the only workable solution is a duo sim with my old blackberry bold meanwhile i love he TP2 so hope i can get it to pair with my premium touch adapter volkswagen carkit any other suggestion or solutions are very welcome cheers

And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
what radio where you on first couple of months

Nice thought about the radio....but unfortunately I don't remember.
Currently I am using v4.49.25.17 that was upgraded with the latest official HTC firmware of WinMo 6.5 if I am not mistaken.
I am 90% positive though that the problem started before even upgrading, back when I was using the first release of WinMo 6.1 and the unknown version of radio, and everything was working ok at the beginning.
I know, I am not helpful at all but frankly, this problem surprises me as much as you.
You mentioned a firmware upgrade - for the RNS right? Not the RCD....
Do you by any chance happen to know if there is a firmware upgrade for the RCD510 and where can I get it from?
Thanks for your help.

looking-g:
I just realized that you are having a problem with the RNS.
Did you had this all along? I mean, did you ever managed to get it working and then it stopped, or you never had it paired?
I am just asking to see if I can be of any help...

well the problem is not with the rns 510 but with the touch adapter which come delivered as premium carkit i use to pair everything with it blackberry,s nokia,s and also a touch dual (niki) without any problem but now with my new phone the tp2 its not pairing it also never did after i fill in the pincode it gives an error message it should connect with the touch adapter my car by the way is a golf gti mk6 cheers, mark

You kind of lost me there.
What do you mean "touch adapter"? Is this a component of the RNS 510? Because I have never heard of it...

Have you determined a solution?
I just picked up a new VW Jetta with premium bluetooth and it worked the first time and not since.....

You guys are scaring me -- I have an Audi A3 TDI scheduled for delivery in January, and it'd be a bummer if its Bluetooth didn't work. FWIW, my current car has a Sony MEX-BT3700U headunit and the Tilt 2 pairs with it in both handsfree & A2DP modes.

3waygeek: You will be probably fine. I think Audi does not have anything to do with Nokia regarding building their units.
Wish you best luck with that.

Extra info
Some more information regarding the whole subject:
I found out that when I press the "Emergency Call" option on the touch screen of the RCD510 (i.e. try to call the international emergency number - 112) and then immediately end that emergency call, the next time I try to pair the Touch Pro 2, it does pair!!! But it has no signal at all, and if you try to make a call you get a "Dial up error" (or something like that, can't remember exactly)!
Any ideas what could be the reason for that?
Thanks.

Your problem is common to VW/Audi's. Chances are the car kits have the rSAP Bluetooth unit. I had exactly the same issue in my A6 using rSAP, as soon as i upgraded to wm 6.5 the problem went away.

Yes, indeed the car kit uses the rSAP profile, as well as the Phonebook Access Protocol (PBAP), but both of these protocols are supported by the TP2. Actually the rSAP functionality I believe is support in Windows Mobile 6.1 and above - I mean besides the fact that your phone's BT radio must support it in order to work correctly. (Without being entirely sure for the above comment).
And some more info for those who are willing to give an opinion:
I did eventually decided to remove the car's battery. I left the car without battery for approximately 40 minutes. Now here's the strange part: All the settings of the card indeed reset (window settings, light settings, etc) BUT the RCD510 was not affected at all by the battery removal! Yes, as weird as it might sound, the station list was there, bass/tremble customizations were there also, everything in place (regarding the radio unit always).
Side note for all those who might remove the battery from a similar VW car:
As soon as I plugged the battery back on, I had somewhere 15+ warning indicators on my dashboard turned on. From ABS malfunctions, air pressure, EPS malfunctions etc. But after rolling the car for 3m or so everything turned off. Back to normal. Probably had something to do with the electronic sensors giving proper signal to the car's "brain". Just my opinion.
Now, besides that - the fact that removing the battery didn't perform a reset of the radio (RCD510) unit, I also tried reverting my Touch Pro II to a WM 6.1 cooked ROM - don't remember which one exactly - but that didn't helped either. Same stupid error message after pairing for 2 secs: "No bluetooth connection to mobile phone".
And to confirm again: My X7500 (Athena) with a cooked WM6.1 ROM from michy still pairs and works fine. (Tested it last night, just to make sure that battery removal didn't had any side-effects)
PLEASE help me if you can. Any suggestion/recommendation will be greatly appreciated.
PS: I decided to contact the car's dealership to inform them about the whole problem. I will post soon regarding how that went...
Thanks for your time everyone...

By the way, does anyone knows the proper way to reset the RCD 510 to it's factory default settings? Besides the function that is given inside the menu itself - I already tried that. I was just wondering if there was a "hidden" way that will entirely wipe all settings/customizations from the unit....

Hi guys! I m in the same situation: Sirocco + TP2 with 6.5 from Orange. Any progress from your side? Ideas would be greatly appreciated!! Cheers, P

Unfortunately!
No friend, sorry. No news yet.
I do keep the post open hoping that someone will give me a new year's present
It's nice to know that I am not alone though

Is'nt it supposed to first be a phone ?

Hi guys,
I can't make calls by Voice Dialing with this phone.
I tried the voice dialer available in froyo, but even though the settings are offering "french", it works only with english sentences, and it requires confirmation on the screen.
Is it me or something is going wrong with that android stuff ?
thx.

You mean you can't dial someone and call them? Or that voice dialing doesn't work?

EddyOS said:
You mean you can't dial someone and call them? Or that voice dialing doesn't work?
Click to expand...
Click to collapse
i think he means he cant call someone hands free, because voice dialer wont understand his french, and when he gets it to work in english it requires confirmation on the screen

exactly what I meant !

To answer your question - it is a phone. You can dial and make a call on it.
The issue you have is voice dialing, which isn't a feature every phone has and so isn't something the category of 'phone' comes under. The issue you've got is down to Google, even English UK isn't recognised properly...they'll sort it eventually

Here in Canada like in many other countries, it is prohibited to drive car and use a cell phone without an hands-free device, all the phones I used in the last 6-7 years were having full hands-free support .....

But not all phones have voice dialing. You'd still need to 'dial' to get a call, even though you have a hands-free kit of bluetooth headset.
It's illegal in the UK to use a phone whilst driving but I still do (if I absolutely have to, which is rare)

My previous phone, an LG8700 was doing that very well, completly hands-free with my bluettoth headset, and it was not a "smart-phone" ;-)

EddyOS said:
But not all phones have voice dialing. You'd still need to 'dial' to get a call, even though you have a hands-free kit of bluetooth headset.
It's illegal in the UK to use a phone whilst driving but I still do (if I absolutely have to, which is rare)
Click to expand...
Click to collapse
And you drive through red lights if "absolutely have to" ?

hi hi hi
bottom line, it does not make sense to me that a supposed "smart phone" not being able to do something "dumb phones" have been able to do for a decade !!!

Things could be simpler if there was a green "Call" button on Desire...

MrUsta:
If you want these buttons aim for WM or LG.
demercie:
Dumb phones don't have 1ghz processors so they recognize it much worser. And most of them can't connect to 3g, and none of them enhances voice detection through 3g.
And because you really need this function try finding older versions of the app and appeal on Google to fix this issue. No worries if it's not fixed in a month there's gotta be some bloody big problem.

Dany0,
To make a voice call, you need to press a button to activate the voice call. A dedicated "call" button could help here. For example, I have a trouble to initiate a voice call in a car using Parrot handsfree car kit (no proble to accept incoming calls though).

fredfox_uk said:
And you drive through red lights if "absolutely have to" ?
Click to expand...
Click to collapse
If you do , for ANY reason do that ;p the only smart thing about you is your phone ;p

[Q] Blutooth calling and ICS updates

Hey guys, so I bought my galaxy nexus from a guy who bought it from his own carrier(bell) and i'm using it with another carrier(rogers). For some reason, my ics is stuck at 4.0.1 and I guess I can't update untill I root the phone? Why is that?
Is there anyway to get the updates if I don't root?
Also, when I use the bluetooth in my car, the music plays through the speakers of the car, but phone calls don't and I have to hear them through the phone speakers. I can get phone calls through my car speakers with an Iphone, but not the galaxy nexus. Anyone knows a solution?

I'm not 100% on your first question but for the bluetooth, make sure under your device in the BT settings it is paired as a media device AND a headset or handsfree kit. My guess is that it is only paired for media.
Sent from my Galaxy Nexus using Tapatalk

RTContent said:
I'm not 100% on your first question but for the bluetooth, make sure under your device in the BT settings it is paired as a media device AND a headset or handsfree kit. My guess is that it is only paired for media.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
My car has a single bluetooth device and under the bluetooth settings on my galaxy nexus I only have an option to pair with that device. I can't see the option of connecting as a media device or anything else. Anyone else is having an issue like this?? With an Iphone I connect to the same bluetooth device of the car and it connects everything, like music, calls, games sounds. However the galaxy nexus connects every sound in the phone to the speakers except the calls.

*#*#CHECKIN#*#*
input that into your dialer, treat it like a phone number, no need to press the call button. This forces your phone to check for updates, maybe it will help.
Other than waiting for the update to push to your phone there is not much you can do to manually update your phone without unlocking the bootloader and rooting. But you bought a Nexus branded phone for a reason right?
If you decided to open the hacking doors: Go over to the toolkit thread and read up. unlock the bootloader (this will erase EVERYTHING, including photos/media etc so back up), flash the stock Google image of 4.0.4 (http://code.google.com/android/nexus/images.html), root, do not flash CWM (that will ensure you can receive and install OTAs in the future).

Shahinbayat.90 said:
Hey guys, so I bought my galaxy nexus from a guy who bought it from his own carrier(bell) and i'm using it with another carrier(rogers). For some reason, my ics is stuck at 4.0.1 and I guess I can't update untill I root the phone? Why is that?
Is there anyway to get the updates if I don't root?
Click to expand...
Click to collapse
You have a non-"yakju" version of ICS (aka "yakju**" or "yakjuxx").
This means that your updates are handled by Samsung instead of Google because the carrier that sold the phone had some small, regional tweaks such as radios on it.
You will get updates slightly slower than yakju devices because of this. You don't have to root to update. If you want to switch to yakju and be on that update path, it is completely possible without rooting. You will need to unlock your bootloader and use Fastboot to flash the images from Google. You will remain stock but it will 100% wipe your device (of course). You will not be rooted. You will continue to receive OTAs.
There are literally dozens of guides and threads on this already. Just search it a bit and you'll find more than enough info on this.

Hi guys, thanks for the replies. So I guess I'll change to the yakju version.
But I still haven't figured out what to do with the bluetooth calling. This is really irritating since I use my phone to make lots of calls while driving and I can't do that now after switching to this phone. Anyone has had the same problem as me on this or have figured out a way to make calls with bluetooh? Even games have a sound on the speakers while connected to bluetooh!! as soon as I get a call or make a call I have to start listening via the speakers of the phone

Voice Dialing over Bluetooth?

I haven't seen this mentioned but has anybody been able to use a BT headset to make, receive, and control calls? I can't. I get "this feature isn't supported on the connected phone" from my Blueant Q2. I know this was an issue with the Sensation and tried installing the voicedialer.apk but the phone won't allow it to be installed. I installed Vlingo but it crashes the phone and I have to do a reset to get it back. Thoughts? Experiences?
Update. We're apparently screwed. There's no native voice dialer included in ICS. I found one that installs but it loses its connection with the headset as soon as it starts. The folks on the Vivid forum are having the same issue. I tried the apps they discussed but they didn't work either. So I guess we wait for HTC to do something.
http://forum.xda-developers.com/showthread.php?t=1562886

BarryH_GEG said:
I haven't seen this mentioned but has anybody been able to use a BT headset to make, receive, and control calls?
Click to expand...
Click to collapse
Yes... ish
I posted the same question a few days ago, but I got no reply, so I bought the phone anyway and tried. Vlingo sort of works with my jawbone earpiece. What I do not like at all is the fact that it does not confirm the command before dialling, or at least I did not figure out how to set it up properly, with the result of dialing the wrong contact in case of a misunderstanding.
I am really missing the simplicity of the blackberry voice dialler, amongst other things (mostly due, I guess, to my being a newbie with android). It was a no-brainer, whilst all the solutions I have seen for android are slightly more cumbersome.
Thanks to the other thread you linked I think I am going to try cyberon voice commander. I could save a couple of dollars/euros buying their voice dialler, but as far as I can see it needs training to attach voice tags to contacts. I don't like the idea of spending time to do that.

This seems like such a basic feature these days, why the hell hasn't it got it?!!!

this is very disappointing news. all the reviews i looked at mentioned voice dialing as a feature. and i just ordered a blueant q2. just tried using voice dial on my phone menu. awful.

i found a retail site online that says the blueant q2 is not compatible with the htc one x and identified several other bluetooth items (including blueant) that are. i decided to try the jawbone era and have it on order. not as many desirable (to me) features as the q2, but if it works, it will be a step up from nothing.
online site is htcpediadotcom. i don't know how reliable it is; first time i've looked at it.

I only just noticed yesterday that the phone would not send the bluetooth connection to the head unit in my car, even though it was connected to it.
I had to use the phones loudspeaker....
All of the Android phones in the past 2 years have worked fine!

[Q] CM 10.1.3 RC1 Galay Note 2 N7100 Bluetooth Issues

Dear All,
This is the first time I am participating on such a technical forum. Please forgive me if I am a little lengthy in details. I own a Galaxy Note 2 N7100 in India. Mine is not a carrier locked unit as there is no such practice in India. I recently installed CM 10.1.3. RC1 on my phone. The installation was perfect and after installation the phone seemed to be working perfectly. I installed a large number of apps that I regularly use and there was no problem. However, later on when I tried to connect my phone with my Fiat Linea Blue & Me system via Bluetooth then it got connected with great difficulty but the phone and contacts app crashed. Thereafter if I dialled a number from my phone I could neither hear the ring going through to the other number nor the voice of the person on the other side even after the phone was connected. However, the person on the other side was able to hear my voice perfectly. I disconnected the bluetooth but the problem was not solved. I did a factory reset and without installing any apps again connected my phone to Jabra BT & Fiat Blue & Me. this time everything worked flawlessly. However, after having installed all my apps, the problem resurfaced. Finally i was compelled to unroot my stock rom and everything is back to normal. All the apps are still installed and everything works fine.
Someone please guide as to what might be the problem. I have nearly 70 apps on my phone. Can anyone please help me?

I've got the same problem. I use the final version 10.1.3. When I want to turn on Bluetooth, it instantly turns off. I've got no idea what this is. Maybe the next release helps.
Sorry for bad English.
KitCrafty