Database Users

08 Altima Bluetooth

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.

Drag retarded Hero into 21st century

Bluetooth has been available on mobile phones for almost 10 years
My shiny new Hero which I consider to be an excellent piece of work is pretty useless in this department....file transfers hands free connection etc
If a phone that costs £30 from tescos can do this why cant the £400 quid hero?
Why is android incapable of this extremely basic functionality? Why are android phones on sale at all? the OS is not finished and will not be untill Bluetooth just works.
I have pissed off several friends by recomending this phone pre release assuming that the bluetooth profiles had been fixed on the hero. But if they cant send mates in the pub a photo of a friend falling over or use their hands free kits how can I blame them?
Is there a timescale for adding working bluetooth to android?

Ask Google. They're the ones that only programmed handsfree profiles in. Apparently it's supposed to be fairly soon.
Also, you know what they say about assuming.....
but yeah, it's a bit of a glaring omission. but then didn't the iphone do exactly the same when it first came out?

rhedgehog said:
Ask Google. They're the ones that only programmed handsfree profiles in. Apparently it's supposed to be fairly soon.
Also, you know what they say about assuming.....
but yeah, it's a bit of a glaring omission. but then didn't the iphone do exactly the same when it first came out?
Click to expand...
Click to collapse
Don't just blame Google tho... Android is open source and the Hero's version is a seperate dev branch to the cupcake 1.5 thats on standard 'Google' phones. I mean they must have fiddled with it anyway as some things that worked on the standard 1.5 build don't work on the Hero.
So HTC are just as much to blame for this... what can we call it... oversight...

Ovek said:
So HTC are just as much to blame for this... what can we call it... oversight...
Click to expand...
Click to collapse
No they are not! The reason that this functionality is not available is because the Bluetooth APIs have not be finalized. Whilst potentially HTC could have added their own, this would have fragmented Android as an OS and this is definitely not the way forward.
Unfortunately, Apple showed that the market will accept reduced functionality in devices, when they shipped the original iPhone.
However, with respect to Google, I fully agree that nearly a year down the line since the G1 was launched, they should've got further than they have with Bluetooth support.
Regards,
Dave

foxmeister said:
No they are not! The reason that this functionality is not available is because the Bluetooth APIs have not be finalized. Whilst potentially HTC could have added their own, this would have fragmented Android as an OS and this is definitely not the way forward.
Click to expand...
Click to collapse
The Android OS will become fragmented, Android is designed that way it's supposed to be a base on which mobile phone manufactures can build upon. It's also the reason you get "with Google" phones, if you want a pure Android OS those are the phones you buy.
HTC should have seized the opportunity to fix some of the glaring ommisions from Android, epecially considering that there is no indication that any more bluetooth profiles are included in donut.

rhedgehog said:
Ask Google. They're the ones that only programmed handsfree profiles in. Apparently it's supposed to be fairly soon.
Also, you know what they say about assuming.....
but yeah, it's a bit of a glaring omission. but then didn't the iphone do exactly the same when it first came out?
Click to expand...
Click to collapse
I say assume, but HTC posted bluetooth profiles on the android community as GAP SPP HSP HFP A2DP and AVRCP profile, so where are they?
I admiit I should have checked for OBEX, I was probably caught up in the hype, and the oooos and arghhs of the reviews, perhaps the reveiwers should have started with..... erm this phone does not work before we parted with our hard earned. Shame on you engadget

puckoon said:
I say assume, but HTC posted bluetooth profiles on the android community as GAP SPP HSP HFP A2DP and AVRCP profile, so where are they?
I admiit I should have checked for OBEX, I was probably caught up in the hype, and the oooos and arghhs of the reviews, perhaps the reveiwers should have started with..... erm this phone does not work before we parted with our hard earned. Shame on you engadget
Click to expand...
Click to collapse
Just get BlueX and use one of the many methods to root the phone, then you'll have full send/receive bluetooth capabilities. It's very easy.

does bluex actually work on the hero? and is it one of the ones that seems to be hidden on some hero devices?
Didn't know that HTC had put those profiles out there...but if they're just in beta or being tested, then i am sure they'll be here soon.
and besides, the base android build on the hero is the same as on the magic, it's just had a few kernel changes for any hero specific hardware, it's still running 1.5.
i personally knew the device had no obex, and still got it. I suppose it's each to their own really. Millions of people got the iphone and were rabid about how wonderful it was even though it was missing some basic features. i bet hero will have the same kinda people, on both sides of the argument.
i like it and am happy, but am certainly not going to defend the missing features, i just rely on the fact that as i am happy with it as it is, anything extra is a bonus.....

rhedgehog said:
does bluex actually work on the hero? and is it one of the ones that seems to be hidden on some hero devices?
Didn't know that HTC had put those profiles out there...but if they're just in beta or being tested, then i am sure they'll be here soon.
and besides, the base android build on the hero is the same as on the magic, it's just had a few kernel changes for any hero specific hardware, it's still running 1.5.
i personally knew the device had no obex, and still got it. I suppose it's each to their own really. Millions of people got the iphone and were rabid about how wonderful it was even though it was missing some basic features. i bet hero will have the same kinda people, on both sides of the argument.
i like it and am happy, but am certainly not going to defend the missing features, i just rely on the fact that as i am happy with it as it is, anything extra is a bonus.....
Click to expand...
Click to collapse
I for one have not beeen able to get Bluex to work on Hero neither Root explorer????

Ok (Grits teeth)
Still love the phone would still buy it (friends probably wont till bluetooth fixed) would have liked a choice on the bluetooth though.
If the reviewers were paying more attention to the bluetooth deficiency I am sure google would be urgently fixing it!
Guess will have to wait. Please dont hesitate to let us all know when you find out they've fixed it

Ovek said:
The Android OS will become fragmented, Android is designed that way it's supposed to be a base on which mobile phone manufactures can build upon.
Click to expand...
Click to collapse
Yes it is - and the bluetooth APIs are part of that base!
Google were very specific about why they chose not to ship Android with broken APIs (see http://android-developers.blogspot.com/2008/08/some-information-on-apis-removed-in.html ). If HTC had "done their own thing" they too would have been committed to support this for years to come.
As a developer, personally I'd be happy to wait for a single fit-for-purpose API to come to Android, than support a wide variety of vendor-specific extensions.
If Android wants to gain serious traction in the Smartphone market, they need to look at Apple and the iPhone. Here you've a single software and hardware platform which is going to make application development far simpler.
It is ok to build on top of the Android platform (as you said yourself), but if each handset vendor goes about changing the underlying nuts and bolts differently this will adversely affect market acceptance of the platform.
Regards,
Dave

so bluetooth does not work on shipped devices?
it works on the htcmagic hero rom but not on the dream hero rom. hack
i wonder why

bluetooth works, but only for headsets.
maybe the magic rom has bluex installed, as i know bluex works on the magic, but not on the hero

rhedgehog said:
bluetooth works, but only for headsets.
maybe the magic rom has bluex installed, as i know bluex works on the magic, but not on the hero
Click to expand...
Click to collapse
Hero supports a few more profiles than just headsets.
From the HTC website:
Q.
What Bluetooth profiles are supported?
The phone supports Bluetooth Headset, Handsfree, A2DP, and AVRCP profiles. You can connect your phone to a Bluetooth hands-free headset or a Bluetooth car kit and use those devices to listen to music and send and/or receive calls. Transferring files between your phone and PC using Bluetooth is not yet supported.
Click to expand...
Click to collapse
We won't see file transfer or OBEX until Google finalize the bluetooth APIs.
Regards,
Dave

puckoon said:
I have pissed off several friends by recomending this phone pre release assuming that the bluetooth profiles had been fixed on the hero. But if they cant send mates in the pub a photo of a friend falling over or use their hands free kits how can I blame them?
Is there a timescale for adding working bluetooth to android?
Click to expand...
Click to collapse
Agree about the file transfer (although its a smartphone so use flikr/twitter)
As for handsfree I am using just fine with my Parrot MKi9200 car kit. Full handsfree and A2DP Stereo support with controls. Full address book sync etc.
So apart from file transfer its got a full set of useful features.
Russ

RussST24 said:
Agree about the file transfer (although its a smartphone so use flikr/twitter)
As for handsfree I am using just fine with my Parrot MKi9200 car kit. Full handsfree and A2DP Stereo support with controls. Full address book sync etc.
So apart from file transfer its got a full set of useful features.
Russ
Click to expand...
Click to collapse
How did you get the address book to sync, I thought this didn't work, and it doesn't seem to with my Alpine kit. Did you install bluex?

The Bluetooth kit in my Land Rover Discovery 3 can pull the contacts list off my Hero and also notify me of who is calling in the head unit.
Pretty sure its not been pulled off my Nokia N85 when I used that as there is no storage in the kit as far as I am aware.
Its also just to note - a Nokia kit sourced / OEM'd by Land Rover and is the standard Bluetooth PTI they factory build.

ewans said:
How did you get the address book to sync, I thought this didn't work, and it doesn't seem to with my Alpine kit. Did you install bluex?
Click to expand...
Click to collapse
No, I have the same car kit, it just works as is from the box.

Hi,
I was a bit confused by this thread and all the bluetooth problems. At the moment I have a Touch Diamond but I am up for an upgrade in the next month so I am looking at either the Diamond 2 or the Hero. I have a Sony BTNX20 stereo BT headset that i use for everything, Will I still be able to use this headset for stereo music on the Hero? Also what video files can it play? Or is there something like Core Player available that will play everything? A bit off topic but i thought id ask since i had a bluetooth question!

mightycaz said:
Hi,
I was a bit confused by this thread and all the bluetooth problems. At the moment I have a Touch Diamond but I am up for an upgrade in the next month so I am looking at either the Diamond 2 or the Hero. I have a Sony BTNX20 stereo BT headset that i use for everything, Will I still be able to use this headset for stereo music on the Hero? Also what video files can it play? Or is there something like Core Player available that will play everything? A bit off topic but i thought id ask since i had a bluetooth question!
Click to expand...
Click to collapse
Your BT headset should be fine, as for video play back... well it's poor. And as for Core player it won't be out for long time (if ever!).

What's the problem with Hero based ROM's and BlueTooth?

Hello.
Before you tell me... I already searched the forum and I can see many posts about the problems with BlueTooth in the Hero based ROM's, but none of these posts I read (I could have missed some, of course) say what the problems are exactly, so I don't know if it can be a problem for me or not.
The only things that I need from BT are connection to the Parrot CK3000 handsfree on my car, and to send/receive files over BT. Ocassionally I will use the Magic as a 3G modem, but I can do it through USB if not working through BT.
Are these BT features affected by these BT problems on Hero based ROM's?
Thanks in advance.

Not sure if this applies to all hero roms but in the 'jacxheroskiv' rom the problem is a missing shared object (just a missing file in the filesystem)
http://forum.xda-developers.com/showpost.php?p=4479554&postcount=96

Hi There
At the moment Bluetooth is problematic on all hero roms for the sapphire or otherwise. Audio head sets (wireless headphones) seem to work ok but everything else doesn't. So unfortunately your car kit won't work. (I have the same one, it pairs but the audio is garbled) File sharing on the other hand is a problem for all the androids so far (There is an app on the market that provides the functionality but it's not as elegant as it could be) so don't expect that to work on hero roms. I haven't tried Bluetooth tethering because WiFi tether works so well. Perhaps someone else could comment.
Now for the difficult part...
So far as I can tell a willing developer, correct me if I'm wrong, could make the Bluetooth work if the source code for the hero was made available (should be available in a few months if the recent release of the sapphires source code is anything to go by) There seem to be quite a number of people who need this functionality so I'm sure one of the rom cookers will get to it but unfortunately there is no way to know exactly when. For this reason I've decided to stick to the ion roms for now. In any event, Touchflo/Sense UI will be made officially available for the magics in due course...for a price of course
On another note any support financial or otherwise is greatly appreciated by the developers so if you want to encourage a particular functionality a few bucks and a friendly message will go a long way. Please remember though that the developers do this kind of thing for the love of it and provide no explicit support for their roms. Any and all risk is taken upon yourself but in most cases caveats will have been picked up by someone before hand.
Sorry if I've mentioned some things you already knew but I thought to add some info applicable to other newcomers.
Enjoy hacking!!

Thanks both.
I guess I'll have to use a non-Hero ROM then. As for the BT file transfer, I've seen at least one Cupcake ROM with it enabled and available as an option in the BT menu. I don't know what ROM it was though, I think I saw it in a Youtube video.
P.S.: I noticed that this thread was moved to "Sapphire general", sorry for put it in "development", I did it for it was related to Hero ROM's. Thanks mods for move it.

A2DP works for my Sony Ericsson HBH-DS205 - music streams flawlessly.
However, the call feature does not work - is this another common bluetooth problem with the HEROs?

Bluetooth Stereo Sound Quality Not Good

All,
Does anybody have any fixes regarding the sound quality when using Bluetooth A2DP protocol? I use my Evo to mate with a Bluetooth receiver so I can listen to Rhapsody over my home stereo. The sound quality is flat. The high frequencies are not present. It sounds like a bad quality MP3. I know that its the A2DP causing the quality issue as directly connection (through 3.5 jack) is awsome.
The Apple 3GS A2DP sound quality was awsome. I am not sure why the Evo is not sounding good. Any help would be most appreciated.
Thanks,
Lance

use the cyanogen rom--this uses a bitpool of 53 giving you the best bluetooth quality possible. the stock/sprint/htc bluetooth drivers are set for a bitpool of 32

Is there any other ROM that has the bit pool set to 53?
Lance

Nope all Sense roms use HTC's ****ty low bitpool setting. This is why I'm running CM as well it's the only rom I can A2DP to my Sony Head unit and get good audio. I attempted to contact HTC about this issue here's the juicy details
Here's my initial question
I have terrible static when streaming music over A2DP on my HTC EVO to my sony mex-bt2800 car radio. If I use CyanogenMod 6.0 which uses a open source bluetooth stack my A2DP is crystal clear to my radio. I have used logcat to look at whats going on I dont know if its a bitrate problem or a bitpool problem or if my radio isn't in your acoustic database.
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
Here's the response I received
Although the android software has been updated to be more compatible with Bluetooth headsets and car kits. Most of the time a Bluetooth manufacturer will have a list on there website stating devices they have found compatible, but this is not always the case. From the information on your issue it seems that your device is simply not fully compatible. The only thing we would be able to recommend would be to try another headset.
Then my response back
I would like an Engineer to read my question if possible since I don't think you fully grasp what I'm saying here. First My EVO's Bluetooth A2DP WORKS 100% clearly when using a Open Source ROM which implements Bluez Bluetooth stack http://www.bluez.org/
When I run your Sense UI ROM the Stock ROM you release which uses your own proprietary Bluetooth Stack I get static in the background so you cant really say its my phone now can you? Its your implementation that's not working properly. I'm not about to try every car stereo till I find one that works with the EVO when I know my stereo can work perfectly with my phone when using a properly coded open source Bluetooth stack.
Here is some extra info from a logcat that shows how your Bluetooth makes a connection through A2DP and what I believe is too low of a bitrate or bitpool setting
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
PLEASE DON'T GIVE ME A ANSWER THAT YOU JUST READ FROM A SCRIPT. I would like a true response from someone who understands and can grasp my question fully like an engineer or a developer, when you give me a generic response of oh your Bluetooth headset isn't compatible keep buying new ones till you find one that works, that really makes me upset since you didn't even read my question it's a car stereo and there not cheap.
I await your educated answer.
And there final bull**** reply
We apologies for any inconvenience you may be experiencing. We will document your concern for review in development of our upcoming devices and future software updates. The situation is still an incompatibility with our device and your car kit weather on software or a hardware level. Unfortunately at this we have no further information beyond what has already been provided.

P_Dub_S said:
Nope all Sense roms use HTC's ****ty low bitpool setting. This is why I'm running CM as well it's the only rom I can A2DP to my Sony Head unit and get good audio. I attempted to contact HTC about this issue here's the juicy details
Here's my initial question
I have terrible static when streaming music over A2DP on my HTC EVO to my sony mex-bt2800 car radio. If I use CyanogenMod 6.0 which uses a open source bluetooth stack my A2DP is crystal clear to my radio. I have used logcat to look at whats going on I dont know if its a bitrate problem or a bitpool problem or if my radio isn't in your acoustic database.
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
Here's the response I received
Although the android software has been updated to be more compatible with Bluetooth headsets and car kits. Most of the time a Bluetooth manufacturer will have a list on there website stating devices they have found compatible, but this is not always the case. From the information on your issue it seems that your device is simply not fully compatible. The only thing we would be able to recommend would be to try another headset.
Then my response back
I would like an Engineer to read my question if possible since I don't think you fully grasp what I'm saying here. First My EVO's Bluetooth A2DP WORKS 100% clearly when using a Open Source ROM which implements Bluez Bluetooth stack http://www.bluez.org/
When I run your Sense UI ROM the Stock ROM you release which uses your own proprietary Bluetooth Stack I get static in the background so you cant really say its my phone now can you? Its your implementation that's not working properly. I'm not about to try every car stereo till I find one that works with the EVO when I know my stereo can work perfectly with my phone when using a properly coded open source Bluetooth stack.
Here is some extra info from a logcat that shows how your Bluetooth makes a connection through A2DP and what I believe is too low of a bitrate or bitpool setting
http://forum.xda-developers.com/showthread.php?t=708265&highlight=bluetooth+bitrate
PLEASE DON'T GIVE ME A ANSWER THAT YOU JUST READ FROM A SCRIPT. I would like a true response from someone who understands and can grasp my question fully like an engineer or a developer, when you give me a generic response of oh your Bluetooth headset isn't compatible keep buying new ones till you find one that works, that really makes me upset since you didn't even read my question it's a car stereo and there not cheap.
I await your educated answer.
And there final bull**** reply
We apologies for any inconvenience you may be experiencing. We will document your concern for review in development of our upcoming devices and future software updates. The situation is still an incompatibility with our device and your car kit weather on software or a hardware level. Unfortunately at this we have no further information beyond what has already been provided.
Click to expand...
Click to collapse
Well I commend you for trying. This is something that makes me want to tear my hair out so I would love to see this resolved as well.
good on ya mate.

anyone know how to get another bluetooth stack on stock rooted 2.2?

I asked Flipz a while ago but I don't think he's looking into it. I also asked Netarchy he said he would look into it sometime but that i shouldn't hold my breath since he hadn't even looked at the code yet. HTC has released the source for their Bluez implementation so all we need is a dev willing to look into adjusting the bitpool setting.

This is a HUGE problem. I am flashing CM6 right now. HTC I am very disappointed with you..

The cyanogen rom also has great dsp equalizer

CyanogenMod will also make you a tropical island than transform your EVO into a jet plane and take you there ;-)
But in all seriousness, yeah, CM6 has BT fixed. One of my friends nagged Cyanogen about it last month, and he patched it right away.

I wish somebody could help us by increasing the bitpool on the Bluetooth driver. The Evo would be so much more enjoyable (for me at least) if the sound quality was better thru A2DP.

lancer123 said:
Is there any other ROM that has the bit pool set to 53?
Lance
Click to expand...
Click to collapse
It would be nice if there can be a patch of some sort...

Just an update today I got a call from HTC customer service since i gave a poor review of my experience on a survey they sent me. Talked in great detail about our problem with the Bluetooth stack told him about the bitpool setting how its 53 on CM and 35 on there roms. So hopefully on the next update well get a fix for the Stock Sense UI rom.

^^LMAO!!! dont blv the hype

I read that the CM6 ROM has this issue fixed. I have also read reports that the ROM email client doesn't support word wrapping (which I really do need). Can anybody confirm this?
Also,
Can anybody in ROM land please create a patch or an update to their ROM which increases the Bitpool to 53? I understand that the Bluetooth driver code has been released.
Thanks

bump............

any roms address this yet?

greenail said:
any roms address this yet?
Click to expand...
Click to collapse
maybe:
* Added DSP Manager (Digital Signal Processing) to boost audio and equalize sound for Headset, Phone Speaker and Bluetooth devices.
wont let me post links, but you know what to do:
forum.xda-developers.com/showthread.php?t=793471

I am using the latest OTA, rooted, along with the latest pandora and the bt audio quality is much better. I have the motorola t605.
With the initial 2.2 update bt quality sucked but now it's better.
Sent from my PC36100 using XDA App

mchlwvr614 said:
I am using the latest OTA, rooted, along with the latest pandora and the bt audio quality is much better. I have the motorola t605.
With the initial 2.2 update bt quality sucked but now it's better.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That was a streaming issue, not a bitpool issue.
The BT audio was a lot better on my TP2 when I updated the registry bitpool to 48 from 32.
I wish they would fix it.

[Q] Bluetooth issues with Froyo

So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well

yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.

I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!

Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.

revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.

now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?

I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App

Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...

I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.

donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.

I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.