Hi, so I recently upgraded the stereo in my car to an appradio 3, I did this so I could mirror my phone onto the screen of the radio. I chose this unit because it is mirrorlink compatible just as our HTC one m8s are. Street several attempts at connecting I have had no luck at getting it to work. I'm doing everything right as far as instructions but something is going wrong. My question is has anyone been able to get this phone working with this radio? And if so, what have you done to make it work?
Edit: forgot to mention that connecting to two of my friends Sony units it works perfectly. Is it possible I have a defective device? Any info would be greatly appreciated.
Have you changed the USB settings on the phone to activate the mirror link through usb?
It's in Settings > More > Mobile Network Share > USB Network Settings, then select the last one (translated from German to English, hope the entry's are similar)
Honestly haven't tried it myself
Gesendet von meinem unknown mit Tapatalk
@tomoffel hey tried your advice and still a no go. When I connect my phone it automatically switches to mirrorlink and it says connection is active however nothing changes on the head unit. I might just have to contact Pioneer hope my unit is not defective.
Have you opened the 'car' app in the app drawer? it does not open itself first time its used.
@TheAngelus Hi tried opening up the app beforehand and still a no go. The phone makes the connection and all however the head unit fails to show the mirrorlink app.
dzaster89 said:
Hi, so I recently upgraded the stereo in my car to an appradio 3, I did this so I could mirror my phone onto the screen of the radio. I chose this unit because it is mirrorlink compatible just as our HTC one m8s are. Street several attempts at connecting I have had no luck at getting it to work. I'm doing everything right as far as instructions but something is going wrong. My question is has anyone been able to get this phone working with this radio? And if so, what have you done to make it work?
Edit: forgot to mention that connecting to two of my friends Sony units it works perfectly. Is it possible I have a defective device? Any info would be greatly appreciated.
Click to expand...
Click to collapse
I have a 2014 Honda Civic with the Display Audio Unit that supports Mirrorlink. Although the screen mirroring and audio seem to transfer only through the USB connection, it still requires that the phone has been paired using Bluetooth. I'm not sure if that is a requirement of the phone or the car's Display Audio unit. It needs to be connected by both USB and Bluetooth to work though. Once both connections are established, the HTC Car app becomes available on the car's display audio unit.
Is your phone rooted or with a custom rom? i've read that can break the mirrorlink app as the M8 has only just got added as an acceptable mirrorlink device with the latest firmware. Also, check if your headunit has the latest firmware?
TheAngelus said:
Is your phone rooted or with a custom rom? i've read that can break the mirrorlink app as the M8 has only just got added as an acceptable mirrorlink device with the latest firmware. Also, check if your headunit has the latest firmware?
Click to expand...
Click to collapse
That is a good point.
I would imagine that if the custom ROM does not include the mirrorlink functionality, then it obviously won't work. Having a rooted phone and being S-Off is ok, but if the bootloader is unlocked, it will not work. I have an AT&T HTC One M8. When I got the phone, it had Android 4.4.2 on it with HTC SDK API 6.17. All worked well with my phone and my car's Display Audio unit. When AT&T released the new OTA update, it upgraded to Android 4.4.3 and HTC SDK API 6.25, which really screwed things up for me. When I would put the car into drive, the HTC Car App that gets mirrored to the car's Display Audio unit was replaced with a message that said, "For safety reasons, this application cannot be displayed while driving". So, there was no longer any way to view any Navigation, Music or anything else when the car was in drive. My only option was to try to downgrade. So, I unlocked my bootloader, rooted, then S-Off'd (using Sunshine) my phone. I then used an HTC ruu to downgrade my phone. Once that was all done, I was greeted with a message saying "Smartphone not compatible" any time I plugged my phone into the car's Display Audio unit, which ended up being because my bootloader is unlocked. I relocked my bootloader and everything started working again normally. My phone is re-rooted and still S-Off and that causes no problems.
TheAngelus said:
Is your phone rooted or with a custom rom? i've read that can break the mirrorlink app as the M8 has only just got added as an acceptable mirrorlink device with the latest firmware. Also, check if your headunit has the latest firmware?
Click to expand...
Click to collapse
Well my phone is rooted and I'm on a custom rom, I am running the latest viper currently. Also as far as I know the head unit is also on the latest firmware but the last update was from Oct 2013, maybe they need to update their mirrorlink app to support latest added devices. Still what is strange to me is that it will run perfect on my friends Sony head unit even with custom rom. I guess I can try going back completely stock and locking my boot loader to see if that works. I will report back once I get the time to do this. Hopefully someone else can chime in with a solution before this. Haha
One M8 with 4.4.4 not working
ericksonline said:
upgraded to Android 4.4.3 and HTC SDK API 6.25, which really screwed things up for me. When I would put the car into drive, the HTC Car App that gets mirrored to the car's Display Audio unit was replaced with a message that said, "For safety reasons, this application cannot be displayed while driving".
Click to expand...
Click to collapse
I just bought a new One M8 and updated it right away. Now I'm on 4.4.4 and only the Music app would show up while driving. I really wanted to use Google Maps as navigaton app but it always gets hidden whit a simmilar message as ericksonline's when I start driving. I find this very frustrating. Is downgrading the only option to get this working?
Should it be the only option, I think I'll send the One M8 back to the seller and will look for another smartphone...
dogo2 said:
I just bought a new One M8 and updated it right away. Now I'm on 4.4.4 and only the Music app would show up while driving. I really wanted to use Google Maps as navigaton app but it always gets hidden whit a simmilar message as ericksonline's when I start driving. I find this very frustrating. Is downgrading the only option to get this working?
Should it be the only option, I think I'll send the One M8 back to the seller and will look for another smartphone...
Click to expand...
Click to collapse
What kind of device are you connecting your phone to? What phone carrier are you using (AT&T, Verizon,...)?
Downgrading was the only way I could get it to work.... and it was a long, scary road to accomplish. I had to unlock the bootloader, add SuperSU, and S-Off my phone (using the paid Sunshine method). After doing all of that I was able to use an RUU that I downloaded directly from HTC and downgrade the phone. Now, I'm running 4.4.2 again. My phone is still unlocked, s-off and has SuperSU installed. I can connect my phone to the car and I get the HTC Car app startup. But the really cool part is that with the Xposed framework I was able to re-map the home button to go back to my phone's home screen (instead of the HTC Car home screen). Now I can do anything on it while I'm driving - and it looks really cool. It was a long road to getting it working this way, but it is now pretty awesome.
Some solution thread?
ericksonline said:
What kind of device are you connecting your phone to? What phone carrier are you using (AT&T, Verizon,...)?
Downgrading was the only way I could get it to work.... and it was a long, scary road to accomplish. I had to unlock the bootloader, add SuperSU, and S-Off my phone (using the paid Sunshine method). After doing all of that I was able to use an RUU that I downloaded directly from HTC and downgrade the phone. Now, I'm running 4.4.2 again. My phone is still unlocked, s-off and has SuperSU installed. I can connect my phone to the car and I get the HTC Car app startup. But the really cool part is that with the Xposed framework I was able to re-map the home button to go back to my phone's home screen (instead of the HTC Car home screen). Now I can do anything on it while I'm driving - and it looks really cool. It was a long road to getting it working this way, but it is now pretty awesome.
Click to expand...
Click to collapse
Hi this sounds really cool. I was hoping that it would work out of the box....
I have a radio "Composition Media" - this is the marketing name. It was preinstalled in my VW. Unfortunately I haven't found out what the exact model name of the headunit is. I bought my phone directly from amazon.de and it has no branding. My carrier is Vodafone Germany, but i don't see how this is relevant.
Can you point me to the some thread, that describes how you managed to get it working?
Thanks a lot!
dogo2 said:
Hi this sounds really cool. I was hoping that it would work out of the box....
I have a radio "Composition Media" - this is the marketing name. It was preinstalled in my VW. Unfortunately I haven't found out what the exact model name of the headunit is. I bought my phone directly from amazon.de and it has no branding. My carrier is Vodafone Germany, but i don't see how this is relevant.
Can you point me to the some thread, that describes how you managed to get it working?
Thanks a lot!
Click to expand...
Click to collapse
Yeah. It is pretty awesome! It isn't perfect though. One problem is that when I use the phone on the headunit, all audio must come from the phone. That means I can't just listen to the radio on the car. I must listen to audio from something on the phone. This can be problematic. Although the Mirrorlink connection requires both USB and Bluetooth, it appears that all audio is passed through the USB when Mirrorlink is active. The Mirrolink service must have a low priority. If there are too many things running on with the phone, the audio can become choppy. Now that I understand what causes the audio to be choppy, I can usually prevent the problem. Usually just rebooting the phone is enough to make it work perfect. Still, it can be annoying when it is happening.
The reason that I wondered what headunit and carrier that you have is because I only know how it works using my own devices. It is possible that the headunit in the VW works a little different than the one in my Honda Civic. I am thinking that they are probably similar enough that they should both work the same though. All of the brains for the Mirrorlink lives in the phone. The car seems to simply provide a feedback to the phone to say when it is driving. So, I am pretty sure you will be ok with your headunit. The phone carrier is important only because of how the RUU's are packaged. I used an AT&T RUU from HTC to downgrade my phone. I was 100% confident that the RUU would work with my phone's hardware because it was installed on the phone previous to me updating. I'm pretty sure that the version of Android doesn't matter too much. It is more likely that what causes the Mirrorlink to work differently is the version of HTC Sense (mine is currently 6.0) or the HTC SDK API level (mine is currently 6.17). You can find this information under settings, about, software information. If you want to try to downgrade, I think you will want to find an RUU that has a similar version of HTC Sense and HTC SDK API that I have.
Now that I have explained some of the difficulties, if you are still interested in trying to downgrade, I can write something up for you. There isn't just one thread. I used many threads for each step and asked many questions along the way. The risk is that you can do all of this and it may NOT work for you as your setup is a bit different than mine. You have to make many changes to your phone. Some could partially or completely void your phone's warranty. Some can brick your phone if done incorrectly. It is a lot of risk, but the results are pretty awesome if it works.
Related
Hi Guys,
I've just ordered 17 touch pro 2's for work and I'm very impressed with them so far. Absolutely awesome phone. We've just got one issue which is the fact that when the phone is locked (we used centralised policies with exchange) you can't dial from our Parrots. The phone says you must unlock the device to allow bluetooth connection.
Does anyone know a way around this without taking the locks off of the phone which is a big no no. Tested it with a collegue's Omnia and it works fine.
You can replicate this issue by using the Bluesoleil dialer which is what I've been doing for testing.
The parrot receives calls fine, just can't make them he the phone is locked.
TIA.
Same problem
Hi there,
I'm having the same issue for dialling out via bluetooth whilst the phone is locked. The TP2 says it needs to be unlocked before answering the call.
There MUST be some registry key to change to prevent this "feature" ... none of the previous HTC phones I have had have had this problem.
Thanks in advance for any help!
i have the same problem, i installed s2u2, which solves the not being able to dial out when its locked, but it's not the most reliable solution.
i'd rather have it working like it did on my kaiser before this phone.
hope someone helps us out.
I tried out S2U2, but the problem is it's only a keypad lock, so plug the phone in USB for example and you still have full access to the device.
S2U2 also does not stop you sliding out the keyboard and pressing the mail button to read the emails on the phone, so this isn't a solution we can use, it's not even a compromise
Haven't had much luck with HTC support either. They are very quick to respond but don't respond with anything of value.
I just wanted to bump this thread -- I picked up a Tilt2 and have the same problem -- really annoying when trying to dial from the car and having to unlock (didn't have this issue on my Fuze).
Yeah this is the most annoying thing I have ever seen. There must be a way to turn it off. I use Ford Sync and really don't want to have to worry about my phone being locked or unlocked. Seems like this goes against all those phone laws. You are making me look at my phone first to make sure it isn't locked before I can safely dial.
Wish I had found this thread before I went ahead with getting a Tilt 2. Didn't have this problem with my Tilt.
Is this a WM6.5 limitation? Hopefully there is an obscure setting that I'm too stupid to find.
Cheers
... and I was just about to ask on this thread whether or not this was still a problem in WM6.5 but I guess I have my answer now.
It's definitely an issue in WM6.0
I contacted AT&T and they said to contact HTC.
HTC gave me this answer:
Thank you for contacting HTC Technical Assistance Center. I apologize for the length of time it took me to respond to your email. I understand how important it can be to use Bluetooth from your device when your device is locked. I will be happy to address the concern for you.
There is not a setting on your ATT Tilt 2 for enabling Bluetooth when your device is locked. When pairing Bluetooth with your vehicle your device must remain unlocked to use the correct functionality. I would suggest placing your device into hibernation mode and keeping your device in a carrying case.
Hi,
I have upgraded by TP2 with the offical HTC rom for 6.5 and installed my blackberry connect 1.06 client. Now, even with the BB lock enforced, as it was with the TP2 using 6.0 and it is working perfectly handsfree in my CAR, locked or not. Previously the TP2 with the stock 6.0 ROM wouldn't make calls when locked.
If people are reporting here that is didn't work in 6.5, then there must be a registry setting somewhere to enable or disable it.
I am just happy that I can make a call in the car, without having to pull over and unlock my phone.
If someone can give me a hint as to where in the registry to look I can compare some settings?
I have a stock AT&T Tilt-2, I loaded loaded "smartlock 1.7" to autolock the phone at power off and also when "in-call" to avoid random dialing. I don't use the PIN for locking.
I can dial hands free BT in my car and with headsets with no issues, power on/off whatever.
Maybe it'd disabled when locked with the PIN?
I am seeing the same issue with two of my users:
One is using a Verizon Wireless TP2 with MW6.1 stock ROM
The other is using an Unlocked HTC touch Pro 2, on the AT&T wireless network (not a Tilt2) with the HTC WM6.5 ROM upgrade.
The Verizon users is using Sync on his Ford Vehical. The other is using whatever system is in his BMW.
Both can pair with the car's system, but if the phone is locked with a PIN the user is not able to place a call without first unlocking the phone.
Has anyone found any information on this?
If MSVC is an option then it has the ability to dial while password protected.
Just noticed this has been bumped. I upgraded all of our phones to the standard Windows Mobile 6.5 from Vodafone when it came out a month ago and this problem is now resolved you'll be glad to know.
I've got 25 handsets currently working fine with no real issues. All the niggles that I had have gone away with 6.5 so it's definately worth the upgrade.
6.1 was screwed and no use with handsfree dialing if you use windows lock which we enforce on our exchange server.
Seems like every provider is a little different.
I have the AT&T Tilt 2 which came with WM6.5, AT&T support claims its a Microsoft and HTC problem. HTC claims its a Microsoft problem.
Anyone have a good support link to Microsoft to get this problem resolved?
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Registry
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
black88mx6 said:
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Click to expand...
Click to collapse
erenken said:
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
Click to expand...
Click to collapse
erenken,
Thanks for the info. The only item different on my 6.5 Tilt2 is that I also have a key "DontAskHfpCallFailOnDeviceLock"=1. Sounded very promising.
Unfortunately, changing this key to 0 and even deleting it doesn't make a difference: I still cannot dial via bluetooth while the phone is locked with a pin. I tried these changes both with and without a soft reset between.
mnunes:
Were you able to find a fix for this? I am in the same boat.
DaBody1 said:
mnunes:
Were you able to find a fix for this? I am in the same boat.
Click to expand...
Click to collapse
No, so far no luck. I can't say I've been looking very hard, though. It's one of those things I've started to learn to live with, as annoying as it is.
I might have to exchange my tilt 2 because the BT doesn't seem to be working properly. Anyone know where to find the oem att tilt to rom installer? all i've been able to find is a "untested" version, and i want to make sure its the same ROM that it was shipped with if i have to return it.
The stock SHIPPED rom isn't available anywhere yet, the cooked stock from herg is the only option right now.
ugh...no wonder i couldn't find it. Well, i download the herg dump that was posted. Anyone think i'll be able to get away w/ using that ROM for a return, or should i just wait until there's an actual leaked/released ATT package available.
The ROM was cooked for warranty return purposes, read the first few pages of the thread, there are a few steps required to take the phone back to stock (ROM, RADIO, SPL).
Whats up with the BT? There may be a fix for it.
stesul411 said:
The ROM was cooked for warranty return purposes, read the first few pages of the thread, there are a few steps required to take the phone back to stock (ROM, RADIO, SPL).
Whats up with the BT? There may be a fix for it.
Click to expand...
Click to collapse
i tried a few different ROMs which led me to think it was a problem w/ the phone itself and not one of the roms. I tried the 10.28 EnergyROMs 6.5.1 and 6.5, TPC 6.5 rom, and an earlier release of the 6.5 EnergyROM as well. All of them had the problems with bluetooth. Basically the phone would sync to a headset, and work just find (playing stereo bluetooth), but after a softreset it would loose the Stereo Audio connection, and i wouldn't be able to playing audio through my headphones anymore. That, and for some reason the tilt 2 keyboard fix wouldn't work with any of the ROMs.
Did you install tomtom nav 7? I installed TT7, the newest version, the one that doesn't mess with the BT and had problems. I uninstalled TT7, went into the registry and deleted anything associated with TT7, soft reset, and my BT works much better now. Aside from that, I wish I could be of more help.
As you can see from my sig this is my third AT&T/HTC phone, and as I recall they all had some initial problems with BT stereo headphones. The problems were in the A2DP software and registry settings.
no TT here. actually, i just noticed that it looks like the phone doesn't recognized any of the AVCTP commands from my headset. i just tried the nov 2 NRG ROM right now, and it was able to play the music over the headphones right after i flashed, but before i installed my sim. It seems that, whenever i update the phones settings (and choose ATT) if then breaks the connection and refuses to reconnect. But either way, even when it was connected its still not able to do any of the AVCTP commands (skip, play, resume, etc).
May be something about your SIM card, AT&T will give you a new sim, no charge. I had them give me one when got my T2.
May be something about your SIM card, AT&T will give you a new sim, no charge. I had them give me one when got my T2. Take your old Tilt or Fuse and just put the SIM in it when you go in. Hell it might clear up your problems.
stesul411 said:
May be something about your SIM card, AT&T will give you a new sim, no charge. I had them give me one when got my T2. Take your old Tilt or Fuse and just put the SIM in it when you go in. Hell it might clear up your problems.
Click to expand...
Click to collapse
i doubt thats it, im using my fuze now...but when i tried uaing my headset on my phone this morning, it kept sayinng bluetooth cannot be turned on.
go ahead and exchange away!
the more tilt 2 exchange requests, the quicker the (re)stocking @ the warranty dept
I really need to get rid of my fuze and have it warranty exchanged!
stesul411 said:
The ROM was cooked for warranty return purposes, read the first few pages of the thread, there are a few steps required to take the phone back to stock (ROM, RADIO, SPL).
Whats up with the BT? There may be a fix for it.
Click to expand...
Click to collapse
maybe i'm too tired, or i skimmed across the pages too quickly, but as far as bringing it back to stop Rom, radio and spl...well, the rom is the herg dump, radio (theres only one for att) so thats pretty much set. i'm assuming all i would have to do is relock it through hardspl. The only thing that has me somewhat worried is the startup screen which has the "test rom" information on it, anyone know if there's an official animation screen....or one that doesn't have that on it.
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
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
Hi all,
I recently purchased a CarExc PX6 from AE Everything works great besides the unit did not have a CarPlay/AutoKit APK/Module installed.
I've tried searching for a couple of different options but no luck with one that connects to my phone. I either get a "Product not authorized" message or once updating the unit crashes or freeze's each time opening. Without the module the USB transmitts power to my phone so its strictly a software issue.
Has anyone had any luck with a good .APK/Module for these CarExc headunits?
Many Thanks
Cant you just download an autokit apk from the internet? Some where on reddit there is a february version of the autokit i advise you to use that one and dont update it.
I bought a official carlinkit wireless version from amazon (the global online store of carlinkit) i installed the apk from there site at first every thing worked fine but after that i tought i need to update the software as i had a weird graphical glitch with volume up/down. So i updated it with in the app to the latest version. Should have never done that, i also get the same issues you have, and i bought it at there offical store at amazon. Any way its still very buggy the carlinkit i have for CarPlay. Its not reliable, and doesnt work flawlessly..
Not an MTCB, what is the unit? Posting in the right forum might yield better results/replies