Hallo experts,
I am a newbie to this forum and a greenhorn concerning programming. But I bought the HTC Kaiser in order to get it running with my Mercedes Bluetooth SAP V2 Cradle (Article number Mercedes Benz: A204 820 0535). Unfortunately, the cradle does not work with the Kaiser. Do you know any solution (another ROM? for example) that may change the situation?
Thank you all very much for your appreciated help!
doc holiday
HTC Kaiser
Don't have a Merc....One day maybe. Had similar problems as you with a Parrot bluetooth car kit though.
Found that Dutty 29 Apr, and Laurentius' latest roms work completely with it though. Other roms may work too (don't want to tread on anybody's toes).
Some of the older cooked roms would either not route the audio properly, would only work for one call then stop routing, etc.
The latest rom I have tried is PDAViet'. Very fast in some aspects, Very slow at others. The Parrot car kit has real problems working with this rom.
Basically, try a Dutty (latest), or the latest Laurentius and I reckon everything will be fine.
Thank you very much Blartiartfast for you rapid and competent reply!
So I will try to change the Rom to the one's you mentioned and will report the result
Have a good time m8
doc holiday
HTC Kaiser
i've had problems with both a hermes and kaiser connecting up to the mercs bluetooth.
What i found i had to do was to get both the merc and the kaiser to search and connect to each other at exactly the same time. I found that if you made the merc search for the phone it wouldn't auth, and vice versa. But oddly making both connect at the same time worked.
Hope this helps.
carkit
hello,
i have a bmw , and with the Laurentius_26 rom (http://forum.xda-developers.com/showthread.php?t=389915) , my bluetooth connection works as a charm.
grtz
Thanks both of you ghostie and BeeCee
I will try it
doc holiday
HTC Kaiser
BeeeCeee said:
hello,
i have a bmw , and with the Laurentius_26 rom (http://forum.xda-developers.com/showthread.php?t=389915) , my bluetooth connection works as a charm.
grtz
Click to expand...
Click to collapse
Agreed! Laurentius_26's latest ROM works very with my ML63 AMG. Sometimes it randomly disconnects, but what Phone/Rom isnt going to?
ghostie said:
i've had problems with both a hermes and kaiser connecting up to the mercs bluetooth.
What i found i had to do was to get both the merc and the kaiser to search and connect to each other at exactly the same time. I found that if you made the merc search for the phone it wouldn't auth, and vice versa. But oddly making both connect at the same time worked.
Hope this helps.
Click to expand...
Click to collapse
This approach has worked for me several times as well. I use Dutty's April 29th ROM and have found stability to be fantastic. I haven't dropped a Bluetooth connection yet. Good luck.
T
Many thanks to all of you folks
doc holiday
HTC Kaiser
Problems always persist with HTC Kaiser and MB bluetooth SAP
As stated in the replies to my question (Thanks to all of those who answered), I tried the last Dutty ROM and the last Laurentius ROM - but in no way I have been able to establish an adequate bluetooth SAP connection between my Kaiser and the mercedes benz bluetooth sap v2 cradle (I provide the original art. no A204 820 0535 in order to be more precise about the item I use).
Does anybody have a step by step "cooking receipt" how I could establish the communication? I suppose that the MB bluetooth sap device uses A2DP, but nobody could confirm until now...
The Kaiser recognizes the MB bluetooth sap device on a regular basis as "UHI-SN3483" and sometimes as "MB-Phone". The MB device recognizes the Kaiser as "Pocket_PC" with the Laurentius ROM and as "TYTN II" with the Dutty ROM. Note that the "Remote SIM Access" was enabled in both ROM's.
I tried also to modify the registry entry
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys\COD from decimal 5898764 (Smartphone) to decimal 5374476. But no connection at all.
I didn't use JETware because I do not want an HFP but a SAP connection.
Another point I could not deal with is that the Dutty ROM features in Settings an item named "Bluetooth SIM Access". What does it is for and how to set it? pointing on it does not result in another effect than display in the header where was located Settings the term "BT Remote SIM Acce"
Sorry I have been that long, but I really need to get into this bluetooth SAP connection with my Kaiser
Thank you all
doc holiday
HTC Kaiser
hello guys... I've read in one of the threads for a diamond-rom-based rom that it includes "SIM Acess Version 3.0.xxx"... perhaps it will work with thsi new version... but until now I've not found any cooked, diamond-based rom, that includes SIM Access...
doc holiday said:
Does anybody have a step by step "cooking receipt" how I could establish the communication?
Click to expand...
Click to collapse
With every ROM that I have used before this one - it has been a rather hit and miss endeavor to link my Parrott bluetooth in my car with my phone. I USUALLY have to tell the PArrott that I want to link with a phone and step through things.
With the DEATH V3.5 ROM installed I got in my car and was in a hurry and thought I would sync them later.
After I started the car the phone indicated that the PARROTT wanted to connect and establish a connection - I indicated that it should be allowed - I was then asked for a key code on my phone- I looked at the PARROTT display device and had a 4 digit code there - keyed that into my phone and it paired easily.
Go figure...
Bill
I work for Mercedes and I paired my Kaiser 10s of times. I am guessing you are in the UK because we don't use the sim access cradles. I don't see why our technology would be better than yours. The cradle we sell that works is 6-7-87-5878 But I doubt it will work there.
I was trying to use a Nokia 616 car kit with T mobile sim in the UK, but T mobile does not support Sim acccess profile with their sims. I am about to try an o2 sim which hopefully will.
If the NB uses sim access profile and the provider does not support that use of its sim, then the Nokia will not even allow fallback to bluetooth car profile.
I hope you proble is not being caused by the above but thought you should be aware in case!
Regards
Chapelhill
It does works for MBZ. I am using it without any issue
Htc touch diamond and Mercedes SAP kit
i have a mercedes sap v2 car kit, i have the same problem being not able to pair with windows mobile based phones, the car can see the phone but phone cannot recieve the password confirm and so connection fails.
i tried many roms, added the SAP settings, and yesterday had the chance to try the new HTC touch DIAMOND on car, but same results.
i think that solving this problem is just a software issue, first in windows profiles, or as addition from Phone manufacturers (as HTC) ,because the car kit is already fixed to car and cannot be modified to use other profile.
but i still have hope that the professionals in this forum can help to solve this problem, before any of Microsoft or HTC. Please share any information to help
Thank you
Mercedes Benz makes five BlueTooth adapters that have five proprietary firmware that each adapts to a different type of phone. For example, a Vorizon CDMA BT adapter will not work with Sprint CDMA phone and vice versa. So in essence, if you have a AT&T service, and use a Motorola Phone, MBZ provides a specific BT adapter, that would be close to impossible to pair with an HTC device.
I would suggest going to an authorized Mercedes Benz parts department at their dealership and request to try all 5 adapters b4 you commit to buying one.
Only In the new 2008 and 2009 C-Class MBZ cars the BT adapter is universal and built in. In earlier models and other models (2008's), the BT adapters would need to be purchased independently; a 2X4 device that installs in the center glove box that works as a link between the media port of the car ( Hands Free) and the phone.
My 2 cents....
try the neon radio rom
i tried it in one of my friends car
if it did not work (change your car to fit your phone )
doc holiday said:
Hallo experts,
I am a newbie to this forum and a greenhorn concerning programming. But I bought the HTC Kaiser in order to get it running with my Mercedes Bluetooth SAP V2 Cradle (Article number Mercedes Benz: A204 820 0535). Unfortunately, the cradle does not work with the Kaiser. Do you know any solution (another ROM? for example) that may change the situation?
Thank you all very much for your appreciated help!
doc holiday
HTC Kaiser
Click to expand...
Click to collapse
Penske MB said:
It does works for MBZ. I am using it without any issue
Click to expand...
Click to collapse
which Penske Mercedes Benz do you work at?
doc holiday said:
Hallo experts,
I am a newbie to this forum and a greenhorn concerning programming. But I bought the HTC Kaiser in order to get it running with my Mercedes Bluetooth SAP V2 Cradle (Article number Mercedes Benz: A204 820 0535). Unfortunately, the cradle does not work with the Kaiser. Do you know any solution (another ROM? for example) that may change the situation?
Thank you all very much for your appreciated help!
doc holiday
HTC Kaiser
Click to expand...
Click to collapse
Try Htc shipped WM6.1
If not work.
Read this.
The Bluetooth® (HFP) telephone module, which is also suitable for Motorola PEBL U6, Nokia 6131, Nokia 6111, Nokia N70, Sony Ericsson K610i, Sony Ericsson W550i and BenQ-Siemens EF81 mobile phones, acts as an extension of the pre-installation for mobile phone with universal interface, a feature which is already present in many of the latest Mercedes-Benz models (optional extra Code 386). The module is simply inserted into this pre-installation in the centre armrest. The Mercedes-Benz Bluetooth® (HFP) telephone module, in independent-design closed-box format, will be available from Mercedes-Benz sales partners from March 2007, and is priced at EUR 250.00, including VAT (price applies to German market).
High-end telephony: the second generation of the Mercedes-Benz Bluetooth® (SAP) telephone module offers even more possibilities
Related
Hi all,
I have just bought a tomtom bluetooth gps system, I can bond to the gps receiver ok, but it just wn't connect. There is deffinately a connection during the bonding process but that is it, it never connects again.
Any help would be greatly appreciated.
Thanks
Steve
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Puff The Magic Wagon! said:
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Click to expand...
Click to collapse
I think the problem is that the xdaII doesn't support a bluetooth serial port profile. I have tried virtually everything and had no luck.
Please keep me posted on how you get on, I really hope we can get this sorted or I will have a gps reciever paper weight.
Steve
Hmm
Due to the nature of yesterday, it wasn't until midnight (GMT) that I could get to have a play with my XDA II & EMTAC BTGPS (& I wasn't sober )
Installed TTN2 and tried to connect - not a sauasage
There "seems" to be something using COM6 and as such TTN2 can't use that as the path to the EMTAC - check box in the GPS options won't check. Turn off BT & you can check the box, but it won't connect as something else obviously can't use it either :? Dunno - I'm not a programmer but I'm going to have to check this out.
I'll speak to a contact @ EMTAC & see if they have been sucessful in bonding to an XDA II (HTC2?) & if so how. Otherwise I'll keep on playing with it & see what I can find out.
Anyone else got any tips or ideas what might be the way of resolving this?
Have you tried turning off the "receive incoming beams" under settings/connections, that may or may not free up the first com port.
I know someone with the same problem. O2 have told him that Tom Tom are working on a new version of software to fix this specific issue and it will be downloadable from the TT site. They couldn't say when.
xdaguru
Beam off did seem to allow me to connect to COM6 but not for my device Might be worth trying Steve because TT Wireless was one I could connect to.
IIRC from iPaq Bluetooth Manager, you had to bring up the device options once bonded and then select a serial connection. Pocket Loox as well. The BT Manager in the XDA II is very basic. So I do wonder if its a TT soluble solution or does it need an upgrade to the BT Manager?
If its a problem soluble by TT then I'm prehaps more hopeful
Sorry to go off topic but I wonder if this is the same PTMW that I know?
How you doin m8?
Hello Danny
Yes it is I
Can't be that many PTMW!'s about
All's well & I'll catch you on the other side one day
Yeah I guessed there could be only one PTMW
I take it you're lucky enough to have an XDA2 already? I always knew u were a gaget fan like myself. I have a month left on my XDA1 contract
Hopefully Tom Tom will have the problem ironed out by then as I have TTN2 aswell.
Pay us a vist on Scoobycity soon. Alots changed and we're alot bigger now
Any bluetooth GPS working with the XDA2 ??
Is there anyone who got the XDA2 working with a bluetooth GPS ? I am very eager to get one (both the XDA2 and a bluetooth GPS) but I would like to hear from some who got a combination working .
Thanks,
Marco
Its being looked into Marco
It may be that the BT Manager may not have various BT options enabled, so it may need a software update/patch from O2.
Spoke to O2 this morning.
They are "aware that not everything works with BT" and are working on a software update.
No timescale offered
I have an Emtac and was going to buy the XDAii to replace my Loox but without this bluetooth connectivity I will save my money. However interestingly it does say on the XDA website...
...or use TomTom Bluetooth with Xda II and cut down the amount of wires in your car
Click to expand...
Click to collapse
I'd say this is enough to get a refund if you want one. Page in question is located here...
http://www.my-xda.com/gps.html
TomTom and Bluetooth
The fault with the TomTom software and Bluetooth lies solely in TomTom's software. TomTom have recognised this and are aggresively working to fix the problem.
The TomTom GPS software doesn't know to read the details of the virtual com port. So give them some time to fix the problem....
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Hi
I too have just upgraded to the XDA II from the Ipaq 3970, and I also have an Emtac BTGPS.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
It would be very interesting to find out if any one has a TomTom BTGPS and can serial link it to the XDA II
Dom
TomTom and Bluetooth
mother said:
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Click to expand...
Click to collapse
The fact you're able to bond with the unit shows that bluetooth is working correctly.
The issue is that the tomtom software can't read com6: (which is where bt is hiding) or do anything with it, because of the way the software works.
This is because the Bluetooth manager on Xda II is from MICROSOFT, whereas on other devices it's manufacturer specific. As far as I know this is the first ever deployment of the MS Bluetooth stack directly.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
Click to expand...
Click to collapse
Then why do they say they support TomTom on their website? Seems like a few people at O2 dont really know what's going on?
I've not known that O2 has ever supported EMTAC BTGPS 'cos the XDA (1) didn't have bluetooth support :?
Surely it is the BT manager that is at fault? Not allowing the a serial connection from the manager to the Emtac?
TomTom is looking to read Com6 (when told to) but the info its getting is not sufficient or mapable.
I've run BTGPS with a TDK B/tooth card and it needs to be told (as do other managers) to make a serial connection to the BT device.
Test for someone (I'll try & do it too)
Find an alternate mapping software that *should* accept a BTGPS device & try to connect...
I've got a Bluetooth Car audio in my Toyota from Toyota. But I cannot establish a connection between my PDA (BA) and the car.
I Know there are not all bluetooth profiles installed on the BA.
I'm using WM2003 SE and the Widcomm Stack 1.0.3900.
How can I change/enhance the Bluetooth stack?
Is it working with WM5?
greets
JEKAL
I've the same problems with Ford.
I 've already posted this problem in every forum I know - but hadn't got any answer yet.
Now shouting loud
HI FOLKS, WHO CAN HELP ???? :lol:
Dieter
@dieterpapa
I have a solution which is working for me since last night :!:
I reinstalled the MDA3 from scratch with the latest ROM version (from march this year) and applied the audio gateway patch. :!: :!: :!: Do not restore any Backup made before.
Now it is working :!::!::!:
regards
jekal
Hi jekal,
thanks for the info. Which ROM version are you using ?
To my best knowledge I believe to have the latest version, too.
I did reinstall from scratch in April with the ROM mentioned below.
What's the difference to your version ?
What type of a Ford handsfree device are you using ?
Dieter
Hi dieterpapa
I'm using the same ROM version mentioned in your signature.
Did you apply the audio gateway patch?
Well I am using a Toyota Blutooth car kit, not a Ford.
Regards
Jens
jekal said:
Hi dieterpapa
Did you apply the audio gateway patch?
Click to expand...
Click to collapse
Audio Gateway patch ?
What I still have to apply is: BA_OEM_AudioGW.CAB
Is this the correct patch ?
Dieter
PS: Jens seems quite German/Austrian/Swiss.....
Yup, it is german, but I think we should keep our english for the others.
My patch is called Version 1.33g. Latest file in Cab is from Jan 27th 2005.
If you have this applied I probably cannot be of any further help.
Regards
Jens
did try with ford - doesn`t work. Ford only supports a "handsfree" bluetooth profile - the BA only has "headset".
I`m still trying to get an information how to upgfrade the BA to "handsfree" BT profile.
dieter
Bluetooth & Toyota Prius
I have an XDA 2 (UK - marketed by O2) & have (after 5 months) discovered that Toyota admit to having a problem with bluetooth connectivity for "some models" (three newer phones belonging to garage employees also failed to bond when I took it back after trying to create a bond for a week& these were not PDA phones!).
They tell me that if the bluetooth version I have has two specific files, it SHOULD be possible to connect - the files are HFPv1 M3 Profile & OPP v 1.1 The problem I have is finding out whether I have these files - I have an e-mail in to O2 at the moment & will be happy to let you know what they come up with - from Toyota's guarded reaction the XDA is clearly a "problem" model & what I do not know is what happens if I prove I DO have these files & still can't make a bond!
Toyota say they can't supply a list of compatible phones because "it would soon become obsolete" but technically minded folks might like to know that they say you need Bluetooth 1.1, Hands Free Profile 1.0 & Object Push 1.1
As I could grow old waiting for O2 to get back to me I'm afraid I gave up - if you want the PDA function of the Xda2 & a phone which will bond with the Toyota system, the Orange SPV M600 bonded instantly & seems to work well even near my home where the signal is pretty poor!
dieterpapa said:
Ford only supports a "handsfree" bluetooth profile - the BA only has "headset".
I`m still trying to get an information how to upgfrade the BA to "handsfree" BT profile.
Click to expand...
Click to collapse
Having a similar problem with a US 2006 Acura TL and a Cingular 3125. The phonoe pairs, but only has limited features. Call waiting drops the call and routes the waiting call to voice mail. Most annoying.
I understand that the Cingular ROM build I have *should* be able to support the HFP, but it was not included in the build for some reason.
Looking for a way to push address book, handle call waiting correctly, display battery life and signal strength on car dash display. As far as I can tell, HFP should handle some or all of those.
Any thoughts??
TVBanks98 said:
Having a similar problem with a US 2006 Acura TL and a Cingular 3125. The phonoe pairs, but only has limited features. Call waiting drops the call and routes the waiting call to voice mail. Most annoying.
Click to expand...
Click to collapse
I'm considering purchasing either a 3125 or 8525, but I am very concerned about losing the ability to accept a second call via my Acura TL handsfree system. Almost all of my calling takes place in my car, and this feature is critical to me. Does anyone know if the released Cingular 8525 works with the TL?
Third party fix for some cars
Guys
I came across the following after much searching. It certainly works for me, you may wish to take a closer look at it.
http://www.jetwaremobile.com/bthfx/support.htm
Hello!
I'm looking for a nice priced mobile carkit (no headset!) wich can handle more bleutooth connections at the the same time. Like my trinity and my office phone, an good old nokia 6310i. Can anyone help me, the only ones i've found on the net are build-in things....
greetz Niels
was useless post, reffered to a carstereo with BT build in, but you want a mobile thing...
nielstheking said:
Hello!
I'm looking for a nice priced mobile carkit (no headset!) wich can handle more bleutooth connections at the the same time. Like my trinity and my office phone, an good old nokia 6310i. Can anyone help me, the only ones i've found on the net are build-in things....
greetz Niels
Click to expand...
Click to collapse
There are only two solutions. Both I think are not what you are looking for. Both are MutliPoint connections. ( you can only use one phone at a time)
1. Headset ( which you do not want ) eg jabra 5010.
2. Or the handsfree system car kit by FWD. (http://www.funkwerkdabendorf.de/con...ID=14775&dbc=648a1f6aac7531e97dba991cb0bed8d7)
AUDIO COM can be buddied with up to 4 phones and has also built-in sim car holder/ reader.This uses your car radio installation or you install a seperate speaker .
I have both my P3600 + my nokia 6310i so I can switch between my private phone & my business phone. And if I ever forget my phones there is the built in sim that I can use ( a second sim card from my business phone).
It was fairly simly to install. ( I got it done in 30 minutes) You can download the instruction booklet from the same link above.
I have looked high & low for asuch a soluton and I think I have found the best so far for 2 phones.
greeting
Rafiki
Hi Chaps,
I tried several Rom´s which are based on WM 6.1 on my T-Mobile MDA Vario 3 but I can´t get work the Bluetooth rSAP with my Volkswagen Premium Handsfree anymore.
It seems that WM 6.1 contains a different Bluetoothstack or rSAP driver.
Is it possible to extract the "old BT Stack" of the 6.0 as a .cab and add it to a actual german 6.1 Rom?
Many thanks in advance
svenna
rSAP and Diamond
Hi to all
i habe exactly the same problems with a T-Mobile Touch diamond (HTC) with the FSE Premium in my Passat ´07.
My previous Telephone Hermes, with WinMobile 6.0 works without problems with the car.
But with the Diamond the car-kit says "telephone is initialised" and then "User is connected" and begins again with "telephone .." and so on.
I also tried diffrent ROMs and Radios, without success.
VW only say "not compatible" (they also said this to hermes !)
@svenna: i think, your suggest would be a possible solution, if possible ?
thx, greetings from austria,
vtwin
Hello,
Have you at last found any solution using rSAP and WM 6.1? I am using a PREMIUM FSE (VW RNS 510) and an HTC Touch HD with wm6.1 and cannot connect at the end. I enter the 16 key pin, but then the message I got is that the HTC cannot connect. It seems that the bt stack in wm6.1 is different from wm6 and wm5. I successfully paired a wm5 P3300, but although I tried almost everything I found in related threads, I could not pair using a wm6.1 HTC touch HD.
Thanks,
Nectarios
Hi, I have the same problem with my VW FSE UHV carkit and a HTC TP with WM6.1.
I read on the german wikipedia the following about rSAP:
Die Bisherigen SAP- Freisprechanlagen unterstützen keine UMTS-SIM-Karten, da das GSM Modul nicht auf dieser Frequenz senden kann.
Which means that a WM6.1 device in combination with a UMTS SIM card does not work. Pairing a nokia with a UMTS sim card worked fine. Apparently the non-WM6.1 work differently
I tried to pair my HTC TP with an old prepaid sim card and the connection worked fine! I could even read SMS messages
Can anyone confirm this?
I have a vw passat 3c 2006 with the RNS-510 with premium kit (5N0 035 730). I use a english HTC tyTN-II with a UMTS-SIM (Provider - KPN) .
Rom on the phone is Garmin-DK2 which works for me. (Even sync's the phone-book from sim.) connect en disconnect from Rsap wotks fine...
Radio version 1.65.24.36 with hardspl Jockeyw 3.29
Also tryed Garmin DK-4 which didn't work.. haven't tried DK9 or DK10 yet....
Hope to hear from anybody who has also succes. Maybe Garmin can shed some light on the different versions of RSAP and Bleutooth stack...
confirm its 6.1 and umts sim
I have the same problem with my VW FSE UHV carkit and a HTC TP with WM6.1.
have tried man roms but WM6.1 device in combination with a UMTS SIM card does not work. Pairing a nokia with a UMTS sim card worked fine.
HTC TP with an old 32k sim card and the connection worked fine!
anyone seen any upgrades for wm 6.1 fix
Have read somewhere on the internet (But not yet tried it...)
- Install Schaps advanced config
- launch Schaps advanced config
- In bleutooth settings enable OBEX
soft reset
- disable direct push
- connect to RSAP in car..
- connection should work
- telephone-book should be synced... (only SIM-phone-book)
This should work with RSAP and wm 6.1....
As stated, i haven't tried it yet, because my setup (Garmin DK2) is working......
Hope to hear from you if this works????
mvdwolf said:
Have read somewhere on the internet (But not yet tried it...)
- Install Schaps advanced config
- launch Schaps advanced config
- In bleutooth settings enable OBEX
soft reset
- disable direct push
- connect to RSAP in car..
- connection should work
- telephone-book should be synced... (only SIM-phone-book)
This should work with RSAP and wm 6.1....
As stated, i haven't tried it yet, because my setup (Garmin DK2) is working......
Hope to hear from you if this works????
Click to expand...
Click to collapse
Great info... should be a Sticky..... I once was tinkering with similar issue with my S500 Benz and had to install the BT Stack, I uploaded to rapidShare, that was for my Wizard. It might be the same BT stack the guys are looking for. use at own risk.
http://rapidshare.com/files/183553206/BroadcomBluetoothStackX51V05.zip.html
Trying it too
Trying the proposed solutions also on my Xperia X1 using a custom rom that is based on the Touch HD rom (original ROM had no remote sim at all, tried installing it, but same result).
All the tips above have not helped. Even changing the registry entry of how the phone presents itself, did nothing.
I'm using a Skoda SuperbII with RNS-510 and premium carkit. It finds the phone, it connects, it gives me the digits and after that, my phone acknowledges the carkit, but the carkit just seems to hang and not continue anymore after that point, untill it times out.
Connection not possible it just says.
We really need to figure this out!!
Anybody tried Garmin DK2 like I did?? If someone else gets that one also to work, we would know that there is something in that version which is working right...
different sim
Okay, from what I have been able to gather, the following is going on.
The carkit is trying to log on in a frequency that it cannot handle.
I have been able to connect the carkit, download the address book and make calls with my Xperia now. No problems what so ever....except one. I was using a SIM from a collega whom has a different network!
I use t-mobile and my collegea has kpn/telfort. Doing more research, I have learned that kpn/telfort and vodaphone use the 1800 band frequency. And that t-mobile uses the 900 frequency.
I am not entirely certain at this point that this truly is the real problem, but, my phone works, my carkit and car works, so all the software bits are in sync, but only using a different sim. Rebooting the phone, changing nothing but the sim, makes it completely broken again!!
I'm using a RNS-510 with the Skoda/VW premium carkit. If anyone is able to shed some light on this and what possible fixes could be, I'd really like to hear!
I have been looking (and mailed) if a fiscon unit could potentionaly fix this problem. They also have units which intergrate with the system.
But I'd rather find a software solution, obviously. Sadly enough, manny cases can be found where people have problems, often, with no solution. This problems is *NOT* specefic to the Xperia, I do realize that now, since the new ROM, rSAP is working just fine.
The fiscon will work without a problem... (it uses only Bleutooth like a parrot carkit, not RSAP) The Skoda Unit will also work without a Problem.. (1Z0 035 729 C also a bleutooth only carkit) Both fully functional with the RNS-510 and MFA-Dash and steering-wheel buttons.
The problem is somehow in the SIM and the acces of the SIM... Is there a way to find out what is communicated thru RSAP
What you could try:
Go to comm manger, settings, Phone
select TAB- Band
and play with these settings...
Maybe that will help...
Check this out.... Maybe that will help...
http://briskoda.net/superb-ii/howto...us-rns510-using-non-compatible-mobile/131709/
@ Quindor:
Try your own SIM, and disable OBEX.. (It's some kind of security protocol) and then try to connect again...
it just got more complex!
Okay, things just more complex then ever before.
My x1 using a HTC touch HD rom base and rSAP from HTC (default in rom).
KPN sim = works and can call
Vodaphone sim = logs in but carkit crashes on trying to connect to cell towers. But car connection functions.
T-mobile sim = connection to carkit never gets finished.
I'm totally lost. Using a friends N95, all the sims work flawlessly.... which makes me even more clueless, because the carkit reads the sim data and then connects using it's own radio to the cell network.
Please, advice? How can this be fixed? Is there a different version of the HTC rSAP software available maybe?
Quindor said:
Okay, from what I have been able to gather, the following is going on.
The carkit is trying to log on in a frequency that it cannot handle.
I have been able to connect the carkit, download the address book and make calls with my Xperia now. No problems what so ever....except one. I was using a SIM from a collega whom has a different network!
I use t-mobile and my collegea has kpn/telfort. Doing more research, I have learned that kpn/telfort and vodaphone use the 1800 band frequency. And that t-mobile uses the 900 frequency.
I am not entirely certain at this point that this truly is the real problem, but, my phone works, my carkit and car works, so all the software bits are in sync, but only using a different sim. Rebooting the phone, changing nothing but the sim, makes it completely broken again!!
I'm using a RNS-510 with the Skoda/VW premium carkit. If anyone is able to shed some light on this and what possible fixes could be, I'd really like to hear!
I have been looking (and mailed) if a fiscon unit could potentionaly fix this problem. They also have units which intergrate with the system.
But I'd rather find a software solution, obviously. Sadly enough, manny cases can be found where people have problems, often, with no solution. This problems is *NOT* specefic to the Xperia, I do realize that now, since the new ROM, rSAP is working just fine.
Click to expand...
Click to collapse
I have the same problem: HTC Touch Pro-WM6.1 with VW UHV Premium and T-mobile 3G sim card does not work.
Same device without changing settings with an old pre-paid KPN sim card works fine! Connection and phonecalls without problems. I could even read sms messages on the car display.
On a German website I read that the new 3G/HSDPA sim cards do not work with rSAP.
okay, I get that
I get that, and I thought it was that also.
But using a nokia N95 with my sim in it, it worked just fine. So something is odd there.
And my phone with windows mobile 6.1 using a KPN sim connected to the 3G network, also worked fine!
:S
The plot thickigens even more!
Using my sim card in my X1, not working. Original ROM, Original ROM + rSAP extensions, cooked rom from touch HD with native rSAP. Just non-functional.
Using the exact same phone, without the t-mobile sim but with the KPN sim, works perfectly, no problems what so ever.
Using an older Nokia E50, both sims work flawlessly, also my t-mobile sim.
This leads me to one conclusion and that is that the HTC rSAP implementation is seriously bugged.
Anyone have any idea on how to proceed? Somewhere I have read that the HTC's wouldn't handle 3G or UMTS sims and only use older ones. But, using the KPN sim I connect to 3G and it works. Also the nokia E50 of N95 can use any network and it just plain works. There for that statement is wrong in my opinion and it is caused by buggy software of HTC.
Anyone have a good idea on how to proceed? Lots of people having this problem and buying nokia's, but for no real reason other then buggy software it seems.
I really like my X1, and payed a lot of money for it, so I really need this to start working.... Please assist and help, also people with a diamond or other HTC, using the same software.
I've been a frustrated HTC TytnII (P4550, Kaiser...) owner since day 1, but all the more so when I bought a new VW car with Premium car kit in it. Initially, the WM6.0 based PDA worked, but I had to manually enable the "rSAP" add-on program every time. When I learned of an official HTC WM6.1 upgrade, I installed it on the promise "rSAP build in". Which it was, except that from then on I have ridiculous problems when trying to connect. I manage, but it typically takes 5-10 minutes (!) fiddling with it - breaking the bluetooth connection while the car kit is trying (in vain) to connect several times; eventually (at best after 3 tries) it will connect. When it does however, everything works fine afterwards. I tried a collegues' identical PDA with similar results. My wife's Nokia N95 works fine all the time.
My five cents on ideas raised here:
- the frequency relation seems strange/unlikely, I did not change subscription or SIM or... between my upgrade from WM6.0 to 6.1
- similar for trying different SIM cards
This really ought to be a WM6.1 issue, or whatever modules came with it (radio? I'm not an expert - just want the damn thing to work). And I have strong suspicion that Nokia (who builds the VW kit) and Microsoft just simply did not want to get along. The compatibility list of VW is very, very short (basically Nokia and an odd Siemens) and has lots of caveats why another phone might not work. Grrrr....
still nothing
Did some tests again today, but sadly enough, no progress yet. ( tried some different rom's for my phone (xperia x1) original and based on touch HD, to no effect).
I'm going to try and get a hold of a Touch Diamond and a Touch HD and see how those preform with my sim. If my suspiciouns are correct, they will also fail, making this a combination of bad software with bugs with certain sim's.
That is the conclusion I am faced with right now... sadly enough, no idea how this can be remedied.
Are there developers whom might be able to write a reliable rsap implementation or will HTC ever come with a working version?
What do you guys think?
Called with support
I have been in contact with Sony-Ericsson support and they tell me they cannot make the X1 compatible, because it is not just software.
Off course, to me this sound like total bull****, seeying I have allready had an raap connection with the X1. But this was either using HTC software add-on's or using a rom that was based on the htc touch HD.
Sadly enough, I cannot work without this functionality... and thus will be forced to sell my phone and buy... a nokia.... not bad, since I have had nokia's all my life. But I really really do not eNjoy beying forced to do so.
touch pro same problem rSAP
i can confirm a HTC Touch Pro exhiits the same behaviour, it works fine on an older 32K non3g vodafone sim, and does not work on a 128k 3g vodafone sim.
i have tried 6 diff roms and also a sep BT stack as per the skoda link and same problem occurs, i have had the TouchPro connect a couple of times but only ever once and from then it just loops as initialising and connecting, i suspect a timing problem maybe, as the older sim syncs up quite fast
i have a new Nokia N85 and it works perfectly on both sims, note the 3G sim takes longer but it works, which leads me to the timing thought, on the nokia all phone book syncing etc also works
i also tried syncing the nokia then switching the sim to the TPro but it just loops, the car kit def tries to use the same 'user profile' as it does recognise the sim irrespective of the handset
this is all happening on an 08 VW toureg with premium kit, im thinking of going to a second sim and just leaving the nokia in the car as the n85 is useless on the email side, painful this
seems to me to be a wm6.1 / HTC / 3g(128ksim) issue
hello guys,
i'm new here and I hope im posting in the right section.
My car ist equipped with a bluetooth carkit (Blaupunkt USB/Bluetooth Interface).
It is using the handsfree-protocol (HFP) to connect the phone.
With a couple of "classical" mobiles (basicly nokia and siemens devices) it is possible to access the Phonebook and activate voice recognition by pressing the ptt-button of the carkit.
This is neither done through SimAccessProtocol (SAP) or SerialPortProtocol (SPP) nor by PhoneBookAccessProtocol (PBAP). The Carkit is nearly 2 years old, and beliving some sources i found PBAP is a newer Standard.
This Carkit connects to the phonebook using an extended Handsfree-Protocol.
My HTC Wizard didn't support the carkit at all. After a rom upgrade to some kind of wm6 rom it worked very well execpt for phonebook-access.
Some time ago i found a tool named "JETware Hands-free Extension for Windows Mobile phones" (http://www.jetwaremobile.com) which exented the HFP-Profile used by the Microsoft-Bluetooth-Stack and enabled the phonebook access.
Since my Wizard broke some days ago i bought a new phone. I thought it would be possible to use every WM6-phone with the mentioned plugin.
So i bought a LG KS20. It looks and works very well and i want to keep it. But i have a problem with it. It uses a Widcomm/Broadcom-Bluetooth-Stack (ver. 1.8.7.0600). It seems like it has much better support for bluetooth-devices than the Ms-Stack (and this must be the reason why most people want to use a widcomm-stack instead of a ms-stack).
It also has PBAP and SAP-Plugins.
BUT, since my carkit does not support PBAP or SAP, and the HandsfreeProfile seems to be just supported elementary (PTT-Button only for redial), phonebookAccess does not work on the LG.
The jetware-Extension only supports ms-stacks.
I already spend some nights on gathering information and testing settings but didn't get very far.
There are some registry settings concerning paired devices, where things like HFPfeatures are mentioned. The value is set to 257 and trying to change it to some other values didn't affect anything.
I also downloaded the Widcomm SDK and tryed to find something about these options, but since the SDK is two years old and nothing about HFP is included this also was worth nothing.
My last try was to use the MS-Stack (from wizard) instead of the widcomm-stack. The registry keys for Ms-Stack seem to be present, but all efforts ended up in about 5 hardresets.
Is there anyone here who can help me solving my problem?
Is there a cab file with a ms bt stack i could try anywhere?
Or is there an extension like jetware for the widcomm stack, respectively only a few registry changes are neccessary and someone knowns better?
many thanks,
andi
hi, I have the same problem, with my htc hd 2. have you found any solution?
bump bump bump
same problem with me as well
This is a common problem with M$ and car kits, see here : http://forum.xda-developers.com/showthread.php?t=519676&page=4 and many other threads like it.
I havent tried what he suggests yet, but i know my freelander 2 doesnt connect properly with all cooked roms i have ever tried so far (many!).
Not that this helps you as it is the software you have tried.