OK greetings to all that may see this thread. I have used these forums in the past with great success so here goes. I presently have a HTC desire that has been rooted and flashed with Cyanogen Mod 7.1.0 Desire. I chose this rom to get my phone to work in BT mode with my oldish Becker Cascade 7411 head unit and it works really well.
I have now ordered a HTC OneX from my provider Rogers here in Canada. My question is there a Rom outhere that installs new bluetooth stack that supports HFP 1.0? If someone could point me in the right direction that would really help or perhaps they can confirm that there is no way I will be able to make my One X function with a BT HFP 1.0 protocol.
Cheers
I don't know your answer, but in future please post questions in the Q&A section, not General. I'll ask for this thread to be moved for you.
Sent from my Evita
timmaaa said:
I don't know your answer, but in future please post questions in the Q&A section, not General. I'll ask for this thread to be moved for you.
Sent from my Evita
Click to expand...
Click to collapse
I read all the forum etiquette but still got it wrong thanks.
BT protocols should be backwards compatible. But I assume you have found this is not the case for your particular device and car head unit.
What BT issues are you experiencing? Does the device simply not work/pair with your head unit?
What ROM are you currently on? If its a Sense 4/4+ ROM, you might try a Sense 5 ROM. The BT stack on Sense 5 seems to be significanly upgraded from Sense 4/4+. For instance, it finally supports AVRCP 1.3 (display of track name, artist, etc. on the head unit display) which is a first for the proprietary HTC Bluetooth stack. So there may be other changes, as well.
Other than that, you might try various AOSP ROMs. But I can't tell you off hand if they support HFP 1.0, or not.
HFP v1.0
Thanks for the help!
BT protocols should be backwards compatible. But I assume you have found this is not the case for your particular device and car head unit.
Well my head unit is a 2005 unit (Becker Cascade) I know that it uses a HFP 1.0 profile, my research on the Android site suggest that the Android that ships with the phone Rogers HTC One X supports up to HFPv1.5 :
''Headset. The Headset profile provides support for Bluetooth headsets to be used with mobile phones. Android provides the BluetoothHeadset class, which is a proxy for controlling the Bluetooth Headset Service via interprocess communication (IPC). This includes both Bluetooth Headset and Hands-Free (v1.5) profiles. The BluetoothHeadset class includes support for AT commands. For more discussion of this topic, see Vendor-specific AT commands''
What BT issues are you experiencing? Does the device simply not work/pair with your head unit? I have not yet experienced the problem since I am still waiting for the phone, but already when I had my HTC Desire I had this issue, until I installed the CM 7.1.0 Desire rom. It will pair but thats it.
What ROM are you currently on? If its a Sense 4/4+ ROM, you might try a Sense 5 ROM. The BT stack on Sense 5 seems to be significanly upgraded from Sense 4/4+. For instance, it finally supports AVRCP 1.3 (display of track name, artist, etc. on the head unit display) which is a first for the proprietary HTC Bluetooth stack. So there may be other changes, as well.
[COLOR="DeepSkyBlue""]I contacted HTC and they said the stock rom will not support car kits that are that old! So I am trying to see if there are any roms out there that have modded the BT profile to include backward compatibility to Headset v1.0 so far I have not found even any description of roms that talk about modding the BT profile.[/COLOR]
Other than that, you might try various AOSP ROMs. But I can't tell you off hand if they support HFP 1.0, or not. Whats the best way to find out?
Thanks again for taking the time to read my question.
Do you have a reason to isolate it to HFP 1.0 in particular? Incompatibilities occur all the time between smartphones and various devices (headsets, car head units, etc.). The Bluetooth standard (and manufacturer compliance) is not nearly as "standard" as we would like. HTC saying your head unit is too old may just be their way of copping out or punting on an issue they have little control over (other manufacturer's hardware not being fully compatible or compliant).
Things would not necessary go any better with a newer head unit. I was having some issues with the One X playing well with my Subaru head unit (made by Kenwood, from what I understand). HTC simply gave up after having me factory reset and update the phone, and the age of the head unit was definitely not the issue (2012 Subaru, brand new at the time). Turned out all I had to do was re-initialize the settings on the head unit (which a XDA member here told me to do). It wasn't HTC's fault (not their hardware), but the moral of the story is that they will always be of limited help when it comes to Bluetooth.
The BT stack on this device is a different one from your old phone. And as I mentioned before, it also appears overhauled for Sense 5. So I'd hope for the best, and see what happens when the new phone actually arrives. Even then, you have at least a few different options to try if you run into issues (Sense 4/4+, Sense 5, and AOSP).
Will check and report
Thanks I just got the phone I will check and report back fist with the stock rom then I will start to root!!!
Related
I had thought about getting one for the G1, but I kinda forgot about it.
I remembered just now that it would be nice to have one now that I have a new phone, but I wouldn't mind knowing if any of you guys have any experiences and recommendations of a good FM transmitter that I can use.
I found one on Amazon with mostly good reviews, but it seems that most of them are for the Hero, G1, MT3G and Droid. So I'm a bit apprehensive about just buying it without researching first.
Here's the one I'm looking at:
http://www.amazon.com/Advanced-System-Transmitter-Charger-ANDROID/dp/B002UKTABI
If there are cheaper or better quality FM transmitters, please let me know.
Thanks!
I'd wait on this. It appears that an FM receiver AND transmitter is in the chipset capabilities of the G2, but the question is did they connect an antenna to it. It just got eMMC perma-root, so hold on a week or so--custom ROMs, possibly with this capability, are on their way.
Sweet. I didn't think an FM transmitter could be added within a ROM. That would be awesome!
skiptomylou11 said:
Sweet. I didn't think an FM transmitter could be added within a ROM. That would be awesome!
Click to expand...
Click to collapse
It can't, but the FM transmitter is already there, so we just need to get software to support it.
If I recall correctly, the Nexus One had the same theoretical capabilities based on it's hardware, however, at this point nobody has taken advantage if it there either :-(
JWhipple said:
If I recall correctly, the Nexus One had the same theoretical capabilities based on it's hardware, however, at this point nobody has taken advantage if it there either :-(
Click to expand...
Click to collapse
Don't we just need a kernel module and some userland software to interface with it?
Wanted to know if anyone has looked into this any further.
janus zeal said:
Don't we just need a kernel module and some userland software to interface with it?
Click to expand...
Click to collapse
It needs not only kernel module (drivers) and userland interface, but also framework support as well. This is similar to A2DP audio redirection to bluetooth. The kernel has to be able to communicate with the audio device, the framework has to be able to redirect the audio there, and the user has to be able to configure and enable/disable it. It's a big project.
MRCLrider said:
Wanted to know if anyone has looked into this any further.
Click to expand...
Click to collapse
IIRC, the MIUI team was working on FM transmission as well.
if u install the desire z rom which is sense u can use the fm radio with the wired headset plugged in on the g2. Tried,done and works
richierich118 said:
if u install the desire z rom which is sense u can use the fm radio with the wired headset plugged in on the g2. Tried,done and works
Click to expand...
Click to collapse
They are talking about an FM Transmitter not Receiver Richierich... Yes FM Receiver works fine on CM and Desire roms but we want the Transmitter so we can send audio to the car radio.
I cannot pair my vehicle's headunit to a CM-powered device, starting with CM6 RC2. (RC1 worked as expected).
I would like to build the stock Android Bluetooth stack and replace that portion of CM with it, in an effort to see if it resolves this problem for me. I'm also curious how the new Bluetooth stack in Gingerbread will behave, as it's apparently received an overhaul.
Ultimately, I'd like provide a package so that CM users could easily "flash" a new BT stack if they're having problems with CM's modified version.
I'm a junior developer, and I have Ubuntu on my machine, as well as AOSP Gingerbread and CM6/7, all building correctly. However, I lack the knowledge (or even a starting point) on what I need to do to accomplish this.
Anyone willing to offer some advice?
Additionally, if anyone else out there is having problems, please post here--once I get this working, I'll need test candidates to see if it helps resolve their issues as well.
EDIT: Starting here. http://source.android.com/porting/bluetooth.html
Never had an issue with bluetooth and my vehicle or a couple of others while running CM 6.x or any of the nightly builds of cm6. Sometimes a kernal I flashed would break it, but otherwise it worked fine. I done this one both a alpine blue tooth module and factory ones.
What are you syncing to?
aduljr, the type of headunit I have is called "BlueConnect", and is built-in to my 2009 model year Hyundai Elantra. This is the manufacturer's website: http://www.autointelligence.com/
Like I said, it worked with CM6.0.0 RC1, but stopped working starting with RC2 and hasn't worked since.
So far I've started reading about the BlueZ stack, but haven't made more progress than simply reviewing some make files.
As always, if anyone has any pointers (or if anyone is also having BT-related problems), please post.
Thanks.
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
timwoj said:
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
Click to expand...
Click to collapse
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Shidell said:
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
have you tried updating to cm6.1 and trying with a stock kernel?
jsseidel1 said:
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
Click to expand...
Click to collapse
Interesting, and appreciated. I'll look into a Google Group, although for now I'll work out of this thread unless this grows into a large project.
BrianDigital said:
have you tried updating to cm6.1 and trying with a stock kernel?
Click to expand...
Click to collapse
I have tried 6.1 with an alternative kernel (Kings) to no avail. Do you have a kernel you'd suggest I pair with 6.1 for testing purposes? I'm more than willing to do so for testing purposes.
Shidell said:
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
Basically, I'd like to be able to tether my phone over BT. The Evo doesn't provide a DUN or PAN service that OS X can see (never tried windows), so things like Android-Wifi-Tether don't work in bluetooth mode.
does you phone work with any other bluetooth device?
aduljr said:
does you phone work with any other bluetooth device?
Click to expand...
Click to collapse
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
BuddaBelly said:
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
Click to expand...
Click to collapse
+1 I have this same problem. CM has a much weaker bluetooth connection than Sense ROMs. I would love to be able to flash something over CM7 to increase bluetooth reliability, even if it hurts battery life (you could always turn bluetooth off when you need to save battery).
Shidell said:
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
Click to expand...
Click to collapse
ill try this as i have the cutting out issue as well
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
allroy1975 said:
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my wifi is never on. and even when it is it doesnt do it on sense roms.
zikronix said:
my wifi is never on. and even when it is it doesnt do it on sense roms.
Click to expand...
Click to collapse
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
BuddaBelly said:
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, wouldn't it be easier to look back into the git commits for the CM repository. And see what changed in the bluetooth files after 6.0.0? That way you should be able to drop in the older bluetooth stuff, and have it work. Then you can try to convert that stuff to work in CM7?
timwoj said:
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
Click to expand...
Click to collapse
If you use AWT and set it to Bluetooth mode and then turn it on, the PAN service will magically be created, but only while tethering is turned on. However, I still wasn't able to get Bluetooth tether to work because of some kind of IP address error in AWT. I think AWT wasn't able to set an IP address for the Bluetooth PAN adapter. My computer was able to see the Bluetooth PAN but wasn't able to pull an IP address to fully complete the connection.
Just flashed AR HD w/ no-sense for the first time last night, coming from MIUI and so far it's pretty good. I used Cyanogen for quite a while, then MIUI.us, which hasn't been able to get the code for Bluetooth A2DP yet. The "other" MIUI rom fortunately does have A2DP working, but since AR HD is the most popular ROM I'd thought I'd give it a try even though I'm not a fan of Sense.
Major dealbreaker is that I can't connect it to my car's Bluetooth stereo. I had no problems with stock, CM, or the "other" MIUI rom, but with this, I just can't connect to it.
Tried searching around, but couldn't find anything from anyone else having this problem, so I find it strange...
Any assistance would be appreciated, thanks!
CoolJunkie said:
Just flashed AR HD w/ no-sense for the first time last night, coming from MIUI and so far it's pretty good. I used Cyanogen for quite a while, then MIUI.us, which hasn't been able to get the code for Bluetooth A2DP yet. The "other" MIUI rom fortunately does have A2DP working, but since AR HD is the most popular ROM I'd thought I'd give it a try even though I'm not a fan of Sense.
Major dealbreaker is that I can't connect it to my car's Bluetooth stereo. I had no problems with stock, CM, or the "other" MIUI rom, but with this, I just can't connect to it.
Tried searching around, but couldn't find anything from anyone else having this problem, so I find it strange...
Any assistance would be appreciated, thanks!
Click to expand...
Click to collapse
Im running 3.6.7 and it quite happily connects to my built it Bluetooh in the car. Although this is for incoming phone calls and not A2DP so I dont know whether this makes any difference.
I ordered a Bluetooh Music receiver from Amazon last week to connect to my home cinema system and I was hoping to use my phone to wirelessly transmit music, now you have me worried! I will report back when it arrives and I have tested it.
Hoping to find it on the doormat when I get home from work today
Hi,
Bluetooth is notoriously poor with sense roms.
Cm7 has a very good bluetooth stack.
Hence you can work games controllers with it. And presumably your car equipment.
On sense roms, though, it can barely work my hands free ear piece.
So, if you use a lot of bluetooth, you are better off on cm7.
Thanks for your response! I've switched back to miui for now, but in searches for a2dp issues with ar HD, I couldn't find anyone having a similar problem...strange...
Sent from my TripNMiUI Pyramid using xda premium
now you found one
I have revolution hd 6.0.3 and it still doesnt work... tryed it with mercedes benz inbuilt BT ... Phoning worked music not ... trying with Sony Erricson MW600 ... not working ... pairing ok , mw600 is selectable in the sense music app ... but no sound ... still playng out of the inbuild speaker of the phone
I have the same problem with Android Revolution HD 6.0.3. Can anyone help please?
Team
Just wondering if it is possible to add this code to any of your roms? It comes pre installed in the new One series of phones. From what I have read Apt-x allows uncompressed data transmission of lossless audio files. SO out Blue Tooth audio will be much better.
I have the HTC Car SterereoClip which has this CODEC built in. I just wish my Sensation had it so I can gain the benefits.
Thanks all
Jerry
Ugh dev forum... ask questions in the q&a (question and answer). Or at least general. Follow forum rules. I'm surprised in 2 hrs I'm the first response.
Also bt is wacky right now for us (at least aosp roms). Several routing issues, so I doubt your problem will be solved until the regular bt issues get corrected.
Sent from my HTC Sensation using xda premium
wadill said:
Also bt is wacky right now for us (at least aosp roms). Several routing issues, so I doubt your problem will be solved until the regular bt issues get corrected.
Click to expand...
Click to collapse
Ok thank you
I am currently having outgoing voice quality issues while using a bluetooth headset (or in car/truck bluetooth) that I am trying to nail down with both HTC and Jawbone. I'm 90% sure at this point it's an HTC issue. I purchased an HTC One M8 on Verizon a week or so ago and immediately had issues with my Jawbone ERA. Voices sounded fine on my end but my voice on the other end sounded static-ey and overly loud - almost like the mic was too hot. I tried a ton of troubleshooting steps with both Jawbone and HTC and so far the issue remains. I also took the phone back and exchanged it for a new one and the new phone has the same issue. I've now tried 5 different bluetooth devices all with the same/similar result.
I found an old HTC One (M7 I think?) thread over on Android Central that seemed to be discussing the same issue:
http://forums.androidcentral.com/htc-one/309574-anyone-else-having-bluetooth-headset-sound-quality-issues-one.html
but no solution was found and it sounds like most people there just sort of gave up.
Sorry for the long explanation but one thing I wanted to try was using a ROM with a different bluetooth stack or system to see if that might point me to an HTC software issue vs a strict hardware issue. Does anyone have any recommendations? I'm fairly comfortable with installing ROMs though on my old Droid, Safestrap certainly made it easier for me.
Thanks!
I had a ridiculous static with my jaybirds so I just ended up returning the headphones and ditching Bluetooth sadly. I don't think a ROM will change it
Sent from my HTC6525LVW using Tapatalk
So there's no difference in bluetooth implementations between a Sense based ROM and say an AOSP or CM based ROM?
AustinML71 said:
So there's no difference in bluetooth implementations between a Sense based ROM and say an AOSP or CM based ROM?
Click to expand...
Click to collapse
Well, out of curiosity I s-off'd the phone, perma-rooted, and flashed TWRP. I installed the GPE ROM, the Viper ROM, and the latest nightly of Cyanogenmod. Interestingly, the CM rom seemed to have MUCH improved outgoing bluetooth voice quality. The other ROMs all had the same issue.
Does CM somehow use a different bluetooth stack or something that would cause this? Honestly, I'd stay on the CM but I actually like some of the HTC features (like the duo-camera) and not sure I'd want to give those things up. Would it somehow be possible to use CM's bluetooth solution in something like the GPE ROM or even stock?
AustinML71 said:
I am currently having outgoing voice quality issues while using a bluetooth headset (or in car/truck bluetooth) that I am trying to nail down with both HTC and Jawbone. I'm 90% sure at this point it's an HTC issue. I purchased an HTC One M8 on Verizon a week or so ago and immediately had issues with my Jawbone ERA. Voices sounded fine on my end but my voice on the other end sounded static-ey and overly loud - almost like the mic was too hot. I tried a ton of troubleshooting steps with both Jawbone and HTC and so far the issue remains. I also took the phone back and exchanged it for a new one and the new phone has the same issue. I've now tried 5 different bluetooth devices all with the same/similar result.
I found an old HTC One (M7 I think?) thread over on Android Central that seemed to be discussing the same issue:
http://forums.androidcentral.com/htc-one/309574-anyone-else-having-bluetooth-headset-sound-quality-issues-one.html
but no solution was found and it sounds like most people there just sort of gave up.
Sorry for the long explanation but one thing I wanted to try was using a ROM with a different bluetooth stack or system to see if that might point me to an HTC software issue vs a strict hardware issue. Does anyone have any recommendations? I'm fairly comfortable with installing ROMs though on my old Droid, Safestrap certainly made it easier for me.
Thanks!
Click to expand...
Click to collapse
I'm on CleanRom and I'm also extremely sensitive to Bluetooth quality issues. I'm using both a Plantronics Legend and the Bose ear pieces and I hook the device up to a Pioneer DEH-80PRS in my car. I have to say I've never had a better Bluetooth experience. No complaints - superb quality - both ends
MARKREIF said:
I'm on CleanRom and I'm also extremely sensitive to Bluetooth quality issues. I'm using both a Plantronics Legend and the Bose ear pieces and I hook the device up to a Pioneer DEH-80PRS in my car. I have to say I've never had a better Bluetooth experience. No complaints - superb quality - both ends
Click to expand...
Click to collapse
I'm now also on CleanRom and it is definitely better. My few tests so far weren't quite as clear as my CM tests but MUCH better than stock. This seems so strange to me. This is just a stripped down Sense ROM, like others yet a significant difference in quality. Both Viper and GPE had the same bad quality as stock. I wish I had the understanding/capability to truly root cause the issue as I'd love to have the freedom to use whichever ROM I choose. However, I do very much like CleanRom for now - the Verizon bloat on this phone was the worst I've ever had yet I do like a few of the Sense 6 features.