Related
We just bought an '08 Altima with the bluetooth option. I can pair the XV6800 with no problem, but quality sucks. It is super choppy on my end and the person on the other end can't hear me at all. I tried my wifes XV6800, same thing. I can pair my old E815 and it works perfectly, so it's not the car. I tried a hard reset, no difference.
I tried loading dcd's clean rom 1.6.7, no difference. Is the BT stack upgraded in this rom?
Is there a newer BT stack out there that I could try?
Its worth downloading and trying the Jetware BT Extensions and see if that helps....but usually it does not change quality so much as enable functionality.
http://www.jetwaremobile.com/
Brad
Thanks for the suggestion, but it didn't help.
Developer help with Infiniti/Nissan Bluetooth?
I've got the exact same issue with an '07 Infiniti G35 w/navigation. I've been doing lots of reading on the xv6800's bluetooth, have tried DCD's and Custel's roms, and was just about to start my own thread, but I'll bet our cars are the same bluetooth/rom wise.
Jetware didn't help me either.
Here's the best fix I've found and it works for me consistently.
-Whence the option's available depending on whether you're dialing out or receiving, click the "use handset" button (transfers call to the xv6800).
-Shortly after press the "phone" button (transfers call back through car).
-Should work as expected after that.
Anyway, at this point I'm hoping one of the kind devs on this forum (DCD or Custel to name just two of many) might find a sec to help us out, although I'm aware and appreciate the fact that many other users are keeping them very busy on their own projects.
I'm assuming the xv6800's hardware would be most similar to other HTC pda phones (not sure what happens between GSM and CDMA devices), so here's a list of their phones who's bluetooth does work with my car (from here). It supports the bluetooth in 144 phones total.
Kaiser (wasn't working with stock rom, but works after this patch from HTC)
Hermes
Atlas
Wizard
Apache
Magician
Harrier
HTC pda phones that don't work with my car (at least not 100%).
Vogue
Elf
Titan
The Titan DOES work with an '07-'08 Infiniti G35 WITHOUT navigation (buy more, get less ).
In addition to the stock Verizon rom I've tried DCD's 1.6.1, 1.6.7, and Custel's 1.1 with no change in the symptoms.
It's my understanding the dev community thinks modding the Vogue's bluetooth for the Titan shows the most promise. I found this thread mentioning an alternative, but it seems to have gone stale on another forum. I'd prefer not to use that forum.
I understand the Vogue's bluetooth might show the most promise for general bluetooth applications (which would satisfy the most users), but becuase I plan to use bluetooth solely through this car, does anyone know if I might be able to go an easier route given the information I've provided?
I'm using radio 1.40.00, could 1.47.01 make a difference?
Can anything be learned through HTC's Kaiser update patch?
Are there any bluetooth alternatives being tested that I haven't found?
Thanks for any help anyone can provide.
OK. I tried what you said and confirm the same results on the '08 Altima. If I switch to handset and back to Bluetooth, the sound is clear (weird). The only problem is, I can't switch until a call is in progress. This is a work around, but not a good one. We need a BT stack that fixes this. Or maybe firmware upgrade from the auto manufacturer.
I know this is going to sounds like a cheap shot, but it sounds to me like something needs to be fixed on Nissan's side. I've tried mine in an Accura without any problem, however both of your stereos are manufactured by Nissan.
A word of advice: I always found that auto makers should stick to what they do- namely, make cars. If Nissan were so great at BT stereos, you'd see nissan headsets.
I never bother with factory Bluetooth anymore- I swapped my stereo right away for a decent Sony Xplod system that supports A2DP (wireless stereo) as well as phone calls. The aftermarket stereo not only sounds great, but I play all my music from my phone without taking it out of my pocket. Last I checked, no stock car stereos supported this. Sony is good at stereo and bluetooth (been around the block a few times).
Complain to Nissan. Or swap your stereo for something decent.
My Sprint 6700 with BigJ Rom works great with the 08 Altima. In the fact the audio quality is better than the Sanyo Katana that I also have paired. I am dispointed that I cannt answer calls from both phones on the car headset without first selecting the phone that has an incoming call. Even my At&T home phone with bluetooth can do that although it does require you to select a cellphone for outgoing calls.
I was able to upload a contact entry from my 6700 to the car Download phonebook. However, I can not get that into the more usable phonebook directory. Anyone succeed in doing that?
shannl said:
My Sprint 6700 with BigJ Rom works great with the 08 Altima.
Click to expand...
Click to collapse
You might be in the wrong forum. The Titan is a 6800, not a 6700.
yes, but this thread is discussing the Altima BT stereo. Truthfully, this whole thread should go in a more general BT forum, since I don't think it pertains to the 6800 exactly.
08 altima bluetooth
Just wanted to say thanks to Park City for posting the name of the web site with the bluetooth extentions (jetwaremobile.com). I have just recently purchased an 08 Altima with the Nav system and bluetooth. I have an Tmobile MDA with a cooked ROM running WM6 and I could not get the entire outlook phone book to download to the car. Once I installed the jetware mobile extentions everything worked just fine. I even got some additional functionality I was not expecting like signal strengh and battery status on the nav srceen. As for voice quality, it's never been an issue for me. So far anyway
As I can see, they are currently testing the Mogul with both of your cars. I don't know what they mean by 'testing', but that's what is going on right now.
http://www.nissanusa.com/bluetooth/...gation+System&mfg=All+Manufacturers&x=51&y=16
http://www.infiniti.com/bluetooth/t...igation+System&mfg=All+Manufacturers&x=42&y=9
arcanecho said:
As I can see, they are currently testing the Mogul with both of your cars.
Click to expand...
Click to collapse
I saw that too, but I don't have a lot of confidence they'll be releasing a bluetooth update any time soon. That's why I was hoping the Titan's bluetooth hardware might be similar enough to the hardware in one of the devices that DO work with our cars (Kaiser, etc., list in my earlier post) that their bluetooth software could be ported "easily" to the Titan. I'm sure the devs here are trying to get the Titan's bluetooth to work as well as possible for everyone's devices, which makes sense. However, with California's new "handsfree driving" law starting July '08, I'm only concerned with getting the Titan to work with my car.
Apparently no one's too sure if that's possible.
1. have any of you verified first hand that the kaiser does in fact work?
2. could someone research and identify the bt hardware in the kaiser, and the titan?
3. has anyone run the kaiser bt fix on their titan and tried it?
i suppose i never thought to look at the kaiser's bt. mine still functions after applying that kaiser patch..
the kaiser patch is a replacement TIInit_4_2_38.bts file
this file did not exist in any titan roms prior to 2.16
2.16 introduced this file (i compared md5 and its not the same data)
2.17, htcs supposed 'fix', does NOT contain this file
all vogue roms i have seen DO contain this file, but again its different data
maybe you guys are on to something
i will throw something together tomorrow probably...drinking time.
dcd, thanks for the help, enjoy those drinks!
1. Not first hand, I'm going off this post. That thread's also why I believe the Kaiser wasn't working with the car before the patch.
2. I've spent a lot of time trying, but have come up empty on any detailed hardware specs.
3. I just ran the Kaiser patch and the bluetooth functions the same as it does without the patch.
I'm using a rom from your 1.6.7 kitchen with nothing else added (rom's working great, btw). I had the same issue with the stock Verizon rom.
Crazy thought, but if the cooked rom I'm using is based on a stock rom that didn't originally include the .bts file (2.17), could it be being ignored?
FZ1 said:
this post
Click to expand...
Click to collapse
good enough for me
Crazy thought, but if the cooked rom I'm using is based on a stock rom that didn't originally include the .bts file (2.17), could it be being ignored?
Click to expand...
Click to collapse
maybe...i dont know how the file functions and ties into the others yet
FZ1 said:
The Titan DOES work with an '07-'08 Infiniti G35 WITHOUT navigation (buy more, get less ).
Click to expand...
Click to collapse
i take it they are completely different head units?
I have a 07 G35 WITH Navi and yes, the quality is choppy when I connect my phone to it. I have been just using my Platronics Discover 640 for the BT these days... It'd be nice if someone can come up with a solution for this...
dcd1182 said:
i take it they are completely different head units?
Click to expand...
Click to collapse
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to, the nav runs off that hd, the gui which controls much of the car is different, voice prompts are different, the available buttons are different (see attached pics), and you lose a cd changer. I do know first hand that w/o nav the bt works great with an XV6800 (got a loaner once). Again, I've been unable to find out what's specifically different hardware wise (even with the full service manual).
riDuh7 said:
I have a 07 G35 WITH Navi and yes, the quality is choppy when I connect my phone to it.
Click to expand...
Click to collapse
Is choppy quality your only problem? Are your symptoms different from ours in my earlier post?
FZ1 said:
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to, the nav runs off that hd, the gui which controls much of the car is different, voice prompts are different, the available buttons are different (see attached pics), and you lose a cd changer. I do know first hand that w/o nav the bt works great with an XV6800 (got a loaner once). Again, I've been unable to find out what's specifically different hardware wise (even with the full service manual).
Is choppy quality your only problem? Are your symptoms different from ours in my earlier post?
Click to expand...
Click to collapse
Once connected, I get a really static noise from my end while in the conversation. Of course, it'a really not usable at all....
I'm going to try the reconnecting method that was mentioned above today. I'll come back and report the outcome. And thanks for the help BTW.
EDIT: BTW, my Wizard (Cingy 8125), Hermes (Cingy 8525), Samsung i760, and few of the Moto handsets are all fine paired to my car. MAYBE, someone can get the BT stack from Hermes to work with the Titan?
FZ1 said:
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to
Click to expand...
Click to collapse
whoa, someone hook me up with a G35 to uh, test
Wizard (Cingy 8125), Hermes (Cingy 8525), Samsung i760, and few of the Moto handsets are all fine paired to my car. MAYBE, someone can get the BT stack from Hermes to work with the Titan?
Click to expand...
Click to collapse
well, peices of it maybe. i would blindly guess that the kaiser is closer to titan than hermes, but we need to exactly identify the bt chip in each. plus its still shady then, ie the kaiser has tnetw1251 for wlan same as the titan and I cannot get their newer wlan driver to work on my device.
what we really need to look at is previous bt stack modifications for other devices. i need a better understanding of tiinit_blah. I've also noticed that the devices that work have a more extensive, or a 2nd audiopara file that sets values for some bt devices. to be completely honest right now i dont know what im looking at and i need to figure out how it all fits together before i know where to start.
Well, I tried reconnect method from both phone and the car, but neither did anything at all. The quality is still crappy as heck. Man... I reallly wish this works.
EDIT: Actually my side of the speaker was complete static, and the other side could not hear what I was saying AT ALL. This efing blows.
Is anyone cooking a rom for the T-mobile HD2 that uses the Microsoft bluetooth stack instead of widcomm. I am looking to see if Microsoft Voioce Command will work properly with this stack.
yes. it would be nice to use my by keyboard and mouse again. LOL.
Subscribing to this thread, too...
Very Unhappy
I could not wait for the HD2 to be released on Tmobile. I have been with them for almost 9 years. I thought finally I can use their 3G network with the HD2. The last thing I expected was for the basic functions of the phone to not work. The phone does so much and is very advanced yet the basic bluetooth functions have been left out. I have spoken with both Tmobile and higher level support at HTC and honestly neither is going to do anything about the bluetooth support on this phone.
Well, if this is true, then it's becoming more and more clear that this is not something they just forgot to integrate - they omitted it on purpose, like the second camera (the second big fauxpas for a "high end phone"!), in order to have something left they can put into HD3 which makes people buy a new device...
I'm still wondering about the roms though - on PC I used to fight with BT stacks years ago. But it as always possible to install a different one, no matter what BT dongle I was using. Is it definitely impossible to create a rom with another stack? Is the stack somehow hard coded into the hardware?
polera257 said:
Is anyone cooking a rom for the T-mobile HD2 that uses the Microsoft bluetooth stack instead of widcomm. I am looking to see if Microsoft Voioce Command will work properly with this stack.
Click to expand...
Click to collapse
Great question...I'm hoping there is an answer.
This would be so great if anyone could make my bt mouse running again on HD2. May be there could be a sourgeforce app or a MS BT stack cracked HD2-Rom.
If I only could use my BT mouse on HD2, may be in 2012 on WM8? Would be so nice for RDP, Virtual Machines, Gaming...
Someone tried on HD2 android with blueinput? Cannot get my BT working Android Running since my new Radio semms not to fit, will test later... I changed the BT working Android to the Phone working Android that is running fine on new Radio...
holylove02 said:
yes. it would be nice to use my by keyboard and mouse again. LOL.
Click to expand...
Click to collapse
I was able to get a BT keyboard to work on my HD2 with stock rom. I never tried a mouse.
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Is that an older Motorola Bluetooth?
I've paired the Motorola H720 with the leaked Eris. Smooth like butter. All I did was enter "0000." Worked fine. Try another bluetooth device, possibly one of more recent vintage. (Don't know how old a model your 270? is.)
I have not had any problems with my Clarion car stereo or my plantronics headset. In my car, in fact, the 2.1's have worked better than stock, since my car stereo picks up the phone and streams the audio automatically every time I get into the car without having to delete and re-pair (as I had to do with stock).
Pete
I have had no luck pairing my phone and any of my cars with any ROM based on 2.1. It pairs, but will not stay connected. Phone says "paired but not connected"; car says "paired, connected; then disconnected"; then endless loops of connected/disconnected. Sucks!
The sad thing is it seems most of these amazing ROM cookers do not use BlueTooth so it is not something they worry about. I bet this is what is holding up releasing the official Sprint update.
I too have tried searching through endless posts about bluetooth and 2.1. All I can come up with is there are some libraries missing from the 2.1 BlueZ; or something to that effect.
I love Damage's 2.0.7.2 ROM! But I have to go back to stock since driving and talking on the phone without a handsfree device is now illegal here in El Paso, TX.
I don't have a car or stereo bluetooth device to pair against. Just tried pairing my bluetooth with the new 2.0.2v2? Alysious ROM. Took 2 sec and nearly totally automatic. Amazing.
My issue with all 2.1 roms is that I can pair, dial and audio stream all day. I just cant talk as no sound or mic. I reflash back to 1.5 and all works well. BT in the car is now useless. sigh
2.1 paired fine, but its a crappy connection on 2.1, on 1.5 i had a better connection
finally used my BT last night with my phone ...worked like a champ! everything was clear to me....i don't have no sound probs and haven't used any of the fixes...
I pair with my bluetooth headset most of the time without problem. I do occasionally have to turn on and off my headset and the bluetooth on the phone to get it to reconnect. Thankfully, it only happens occasionally.....
Maybe I'm just one of the lucky ones (this time) but I have been streaming audio from my hero to the car stereo while while using google navigtion, which politely talks over the music, and have not had any problems. I'll get an occasional skip in the music (probably during downloads of map data), but nothing worth complaining about.
Pete
poor_red_neck said:
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Click to expand...
Click to collapse
Guys, sorry to revive an old post but I am having this exact same issue as the OP. If anyone has found a fix, please post. Thanks.
Looking at FroYo they have updated some Bluez stuff (what makes out BT work) maybe it will be better when we get that.
Hopefully...
So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.
Problem : car :
Peugeot 407 (2008)
device : Nexus One (Rodrig. latest)
I always had troubles getting my device paired with my car, but mostly after a while or installing "bluetooth file transfer" it worked.
However not anymore. Does anybody has an idea what the problem could be? Are more people experiencing this. The devices see each other but they can't connect/pair to each other.
I also tried the app. "bluetooth fix" but it gives an error. Even after reinstalling the "Super User" app from the market.
(sorry I wanted to replace it to Q & A)
linking and transfer of phonebook is good, but quality is very bad. It is difficult to hear the other side, most of the time I have to take it from handfree and talk into the phone directly...
using cm 6.1 rc1
Had that too. Use a kernel without audio-mod.
It works but not really at the same time ..
I can receive calls but I didn't manage to get my phonebook on the car or make a call from the car, I have to dial through the phone.. Not sure actually if its possible or not with my car anyway...
Phone: Nexus One - CM6 nightly 263, with radio 5.12 and Wildmonks 112210 kernel
Car: VW GTI 2010 - RNS510
Does anyone also have a problem with using his bluetooth?
My phone sees my car's bluetooth but can't connect.
It always gets rejected!
It used to work on early Rom releases.
I am searching the net and this forum but I don't see any solutions.
There is an app on the market to fix bluetooth but it didn't work
Problem car: 2010 Audi S4
Phone: Nexus One (ATT) 2.2.2 (unrooted) Radio 5.08
Phone pairs. Cannot answer calls through the car controls. Must answer physically on phone in order to answer call. If picked up by car controls, the car says connected but no audio.
The system used to work perfectly before while on eclair 2.1. I think Froyo screwed something up for me.
huuub said:
Had that too. Use a kernel without audio-mod.
Click to expand...
Click to collapse
I'm also on CM with audoio issues. which kernel did you use, and is it affecting other areas of your phone pos/neg? i.e. do you recommend the switch?
The latest from wildmonks without Audio Boosts are :
http://wildmonks.whoisthedrizzle.com/kernel/2.6.35/010411/No_Audio_Boost_CM6/
These are good.
However I can't even connect anymore (had the no audio boost too when in the time it could connect)
foodplz said:
Problem car: 2010 Audi S4
Phone: Nexus One (ATT) 2.2.2 (unrooted) Radio 5.08
Phone pairs. Cannot answer calls through the car controls. Must answer physically on phone in order to answer call. If picked up by car controls, the car says connected but no audio.
The system used to work perfectly before while on eclair 2.1. I think Froyo screwed something up for me.
Click to expand...
Click to collapse
I also have an A4 with nexus one on CM 6.1 (still with audio boost) and it works perfectly (except for the sound quality). So might be a specific issue on your phone side, or maybe the new audi SW (mine is from 2008). have you looked at this thread?
http://forum.xda-developers.com/showpost.php?p=5805350&postcount=26
pwvandeursen said:
I also have an A4 with nexus one on CM 6.1 (still with audio boost) and it works perfectly (except for the sound quality). So might be a specific issue on your phone side, or maybe the new audi SW (mine is from 2008). have you looked at this thread?
http://forum.xda-developers.com/showpost.php?p=5805350&postcount=26
Click to expand...
Click to collapse
I also have audi but it's an 06 a4. I'm using enoms rom and everything works good