Hi i have a problem when using the mytouch slide (rooted) with bluetooth devices. Im currently running Cyanogen nightly build 141 with a Motorola S7- hd bluetooth headset. the media Audio works fine as i can use the controls with the music app. but when switching to make a call i cant hear anything. any way to fix this issue thanks
This is a known problem with froyo builds on the Slide. I think it's partly due to the fact that HTC haven't released the source code for the bluetooth stack yet.
The simple fix is to use a 2.1 ROM, or wait for T-Mobile to deign to release a 2.2 ROM for the Slide so that the devs can incorporate the fixes into their own ROMs.
Related
i have a hero rom on my htc magic and everything works perfectly except the bluetooth audio,
is it possible to somehow install the original htc magic bluetooth instead of the one that comes with hero rom to get it working like before?
Bluetooth issues with Hero ROM's are a known, but they are not fixable at the moment.
So either run a ROM where it works or live with bluetooth audio not working.
Cheesebaron said:
Bluetooth issues with Hero ROM's are a known, but they are not fixable at the moment.
So either run a ROM where it works or live with bluetooth audio not working.
Click to expand...
Click to collapse
Yeah a MOD should post a big sticky at the top of this forum about it, gets asked way to often, must be a bigger deal in other countries. I can do without the slow transfer rate and battery sucking feature.
Clinton
Bluetooth audio is tremendously important if you spend a lot of time on the phone with bluetooth headsets. For me multitouch is one step more important. Now if only 2.0 would come out I could switch back to a rom with bluetooth!
Just wondering if it's possible to pull out everything related to bluetooth and A2DP (Stereo Bluetooth Audio) from 1.5 and insert it into damages 2.1 ROM.
I have tried every 2.1 ROM and I can't seem to get reliable bluetooth audio through my headphones, it skips and cuts out. It is very frustrating.
I have tried several headset to no avail, it always work flawless in 1.5.
I just got done running a logcat as well, and everytime it would skip or cutout nothing showed in the logcat, it was very strange!
Thanks
Roman
Roman G said:
Just wondering if it's possible to pull out everything related to bluetooth and A2DP (Stereo Bluetooth Audio) from 1.5 and insert it into damages 2.1 ROM.
I have tried every 2.1 ROM and I can't seem to get reliable bluetooth audio through my headphones, it skips and cuts out. It is very frustrating.
I have tried several headset to no avail, it always work flawless in 1.5.
I just got done running a logcat as well, and everytime it would skip or cutout nothing showed in the logcat, it was very strange!
Thanks
Roman
Click to expand...
Click to collapse
These ROMs still are not official builds from Sprint and HTC. They are leaked beta versions.
I am sure until Sprint officially releases their update that some of these things will be buggy.
Everything else in his newest ROM is flawless.
DJAscendance said:
These ROMs still are not official builds from Sprint and HTC. They are leaked beta versions.
I am sure until Sprint officially releases their update that some of these things will be buggy.
Everything else in his newest ROM is flawless.
Click to expand...
Click to collapse
Oh I realize that, I was just wondering how hard it is to do that and if it could be done!
Some of the other Roms I have tried have been complete dumps and none of them have worked either!
So far I'm pretty happy with Froyo on my phone. I've got the barebones WM for droid rom, radio version 2.12.50.02_2and a FAT32 SD card I freshly formatted prior to installation.
It's great, save for the fact that my plantronics discovery 975 headset doesn't seem to play nicely with Froyo. It pairs just fine, but I don't get any audio and the phone app seems to lockup when I attempt to answer a call while paired. This is via either the button on the handset or the headset.
I know Android for HD2 is still in dev, so I"m willing to accept this is just a problem with no fix. However, if there is a bug out there I can fix to get my headset working, I would love to know about it.
Any help would be appreciated.
Mccm v.1.5 works nicely with my SE headset. It's the only android without sense build where Bluetooth is functional with my headset. Have tried them all.
If you're into sense, Froyostone build has Bluetooth perfectly functional.
Sent from my HTC Desire using Tapatalk
That's what I'm told, but...
....the MattC Froyo Sense is a slightly moded version of the stone, if understand the txt doc that comes with it.
I'll try the straight stone installation and let you know how it goes. In the meantime, if anyone has a suggestion as to why this would be flakey, I'm really curious what the issue is.
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Hi. I had exactly same problem.
Try to push play&pause music ,start&stop voice action
before start use bt.
Another solution is push bt call button immediate after make call
Sent from my Nexus One using XDA App
That didn't work for me.
I had the same problem as the OP and thats why i switch to a sense build also
Did you try this before?
http://forum.xda-developers.com/showthread.php?p=8348326
zoftdev said:
http://forum.xda-developers.com/showthread.php?p=8348326
Click to expand...
Click to collapse
Yes, I've tried that. But those files are for sense builds, and when I transfer them to a non-sense build, BT wouldn't even turn on.
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
hastarin said:
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
Click to expand...
Click to collapse
Wow! That's superb news.
BT Works
raysacr said:
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Click to expand...
Click to collapse
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
jinharry said:
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
Click to expand...
Click to collapse
before it's only supported on RMNET or non evo kernel.. the NEW NexusHD2 that was just released now supports BT on all currently available kernels... you don't even have to do the on, off, on trick anymore for the bluetooth to work.. i think it's the closest to being the perfect android build for our HD2.. everything just works including the MMS which i'm having problem with all the sense builds (low res image)..
I will load NexusHD2 1.5 tonight and see what I find
Finally a non-sense build with working bluetooth. I was able to bluetooth music and make a call using my car stereo. I just had to post this. http://forum.xda-developers.com/showthread.php?t=804210
Hi all,
I wonder why no one is asking or investigating the AVRCP issues on ROM's without Sense? It looks like something is missing in those roms that can be found inside Sense ones.
The bt call function is working as designed but play/pause/next/prev doesn't.
Any ideas?
The issue is that HTC have used their own bluetooth stack in their Sense based roms.
This stack supports the features that you are talking about.
Unfortunately, stock roms use a different stack which do not have the same features as the Sense stack.
This isn't an issue only on the HD2.
Can we get that stack and put it to nonSense roms?
AVRCP has been working on every CM6 build I've tried until recently. Just over the last week or so since I've updated to more recent nightlies I've found its stopped working. I'm currently using ginger_hd2 and it doesn't work. Also the mdj aosp gingerbread doesn't work and mdj streak ram v0.5. All the builds I've tried today!
I was using passion nightly 270 (or bravo, can't remember) and that worked fine.
Sent from my HTC HD2 using XDA App
Never worked for me since I tried HyperDroid and other roms.
I'm going to revert back to my old build later today to see if it still works. I thought it might be a problem with my headset as I dropped it the other day but I tested it last night with Windows Media Player on my PC and it worked OK, switching tracks, play, pause, etc.
Will let you know how it goes.
Sent from my HTC HD2 using XDA App
OK - It definitely works with my previous build.
This build is based on the Passion nightly CM6.1 v270
As I say, I've had it working on pretty much every build since the beginning of Android on the HD2 - it's only stopped working on the Gingerbread-type builds.
ie. It doesn't work on MDJs actual 2.3, or the Ginger_HD2 based on 2.2.1 with Gingerbread-style notifications, etc.
I can't work out if it's coincided with me using builds which have the newer initrd.gz...
Let's hope someone who knows about this stuff reads this thread!
What is this build with CM 6.1? Can you link it?
http://www.multiupload.com/FQCU3UV070
Try this... this one's based on 293 nightly.
Mine was a hybrid I kinda created myself using michyprima's nightly build v4, then incorporating the passion 270 files. If you look at this thread:
http://forum.xda-developers.com/showthread.php?t=824601
It'll explain how to do it...
OK, well I did some trying to fix it using MDJs Gingerbread v0.8 but no joy.
I tried replacing the three bluetooth libraries (libbluedroid.so, libbluetooth.so and libbluetoothd.so) with the working ones from my build but that didn't work.
I also tried replacing the AudioBTID.csv file as it had some slight changes and whilst it didn't fix the issue, it doesn't seem to have broken anything.
I'm currently looking at the bluetooth conf files in /system/etc/bluetooth to see if there's any differences there... think we need some dev help on this one though - I'm pretty much at the limit of what I can do....
Nope, no difference in the conf files. Also changed over the two .so files in /system/etc/lib/bluez-plugin
Again, this didn't work but didn't seem to break stuff!
That's bad. Even Sense roms has problems with media controls profile such as connecting automatically to Phone Audio only.
I feel like 1 from 1000 use it, so nobody cares
Just in case anyone finds this thread again...
MDJs NAND CM7 builds now have AVRCP working again. If you want a build without sense but with this working I suggest you try them! I'm a happy camper again!
Sent from my HTC HD2 using XDA App
Any updates on AVRCP on our devices? I am on CM7 (BoyPPC HoneyComB v31), and AVRCP does not work Do the GB sense ROMs have AVRCP capability?
I tested a few SD ROMS and AVRCP works with:
RAFDROID_HD_SD_4_2 (Sense)
AmeriCanAndroid (Gb)
JaguarMIUI-V11 (Gb)