Searched but can't find an answer.
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Would it work if I use a matching OEM headset? For example, get the OEM EVO headset to use with EVO based build?
what is it ur specifically trying to do
hey what is it u wanna do bc I have the desire build and I use the headphones that came with my hd2 to control my music thats about it u can do with it and u know the basic use it to talk and what not but even than u have to have winamp installed on ur phone which u can get from the android market for free or it also works as a music controller on the htc music on android idk if it works for the other builds tho, hope this helps
Try the headphone come with iphone, it,s work!
silvscorp said:
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Click to expand...
Click to collapse
What are you talking about? Headsets have been working properly almost since the start of Android porting.
Fedr0 said:
What are you talking about? Headsets have been working properly almost since the start of Android porting.
Click to expand...
Click to collapse
I think he means for controlling music. It may be a non-sense build issue. My original HD2 headset buttons don't work for skip forward, back or play/pause. This is on Bangsters V1.5. My bluetooth headset does work for these functions though. When I used desire builds the headset buttons would work, but only if the screen was on.
trmacdonal said:
I think he means for controlling music. It may be a non-sense build issue.
Click to expand...
Click to collapse
That's strange, I've never had that problem and I never use Sense builds. This with the screen either on or off, it doesn't make any difference.
Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/
npocmo said:
Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/
Click to expand...
Click to collapse
yes me too and I have found any solution the call/answer button enable only Voice Recognition and the (next/back) button enable nothing
@npocmo: I think that dosent work with the desire HD build portage. Did you tried with a nand Desire ?
i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?
wow this thread is so old !! has anyone found the solution ? i flashed [Feb 02][DL DesireZ v3.4][DL Data2SD/Ext4 v2.7][Nand/SD/MAGLAR] yesterday and have the same problem, the remote doesn't do anything other than make the music player go crazy. solution please ? should i try with another android build ?
I have the same problem with this build!
actually these devs were saying that it was infact gingerbread who wasnt supporting the headset controls.. but now most of them do.. only thing you can do is thoroughly search the build thread to make sure that they work before flasshing them unto your phone so you know exactly what your getting into
Try changing kernel to gauner
Yes, the problem on kernel mdj.If you change kernel on to gauner it will works.
soberlam said:
i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?
Click to expand...
Click to collapse
I changed the kernel and it working
Can someone explain how to fix it? I did not understand..
I have on my Leo's -= MDJ CyanogenMod 7 v. 2.6 [+ A2SD] [GRH78C] [RMNET] [Kernel: MDJ S10.4 OC]. Excuse my English but I'm Italian
Anyone can help me?
mylove299 said:
I changed the kernel and it working
Click to expand...
Click to collapse
so can i use NAND MDJ but use gauner kernel ?
How do I change only the kernel? without losing data?
where can i get gauners kernel please
Related
I did a search in here but there are so many results...
I have been playing with the 1.5 build DZO posted on his page. Bluetooth seems to work, but I am having a hard time synching my contacts. Anyone know other builds with functional Bluetooth?
have u tried to
is ur data the problem or is it just ur contacts?
I actually got the contacts synched after a bit of tinkering. Still, I am wondering what other builds have the working bluetooth. I am assuming this is a different beast than the xROMs of a few months ago as it was taken directly from DZO's site.
Does that mean limited bluetooth drivers have been developed for the touch? I was playing around with mine tonight and it was working. If I can have bluetooth on say a 1.6 or a 2.x version of Android, then I may really give up win-mo for good.
yea
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.
lgevo said:
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.
Click to expand...
Click to collapse
I'm pretty sure a 1.6 build (like Donut AOSP by plemen) flashed on NAND with dzo's latest kernel will have bluetooth enabled...along with GPS and usb headset audio
Has anyone got a list of senseless builds at the title suggests!
Im currently running Dans froyo 1.1 which i love, and if it had BT support i would use without fail, but its kinda annoying me now !
Thanks guys
kiteboarderni said:
Has anyone got a list of senseless builds at the title suggests!
Im currently running Dans froyo 1.1 which i love, and if it had BT support i would use without fail, but its kinda annoying me now !
Thanks guys
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=756491
darkstone FroyostoneSeries V1 is working with audio Bluetooth, even A2DB stereo
Sent from my HTC Desire using XDA App
I am using Darkstone HD2Froyo V2 - Release Date: 16.Aug.2010
I have a Toyota Prius with bluetooth build in, I can connect the phone to the car, I can pickup and end calls, but I can't get audio. The other side hears me, but I can't hear them.
EDIT:
Found this, so it makes sense that it doesn't work (for now)
======================
Whats working:
- Wifi
- GPS
- 3G
- Camera with flash
- Bluetooth (No Headset in calls support)
- Everything thats working on other builds
- LED status notification
- Keypad LED control
Whats not working:
- Camcorder
- Bluetooth Audio in calls
- Compass is inaccurate, this is known.
- USB Storage mode is disabled, I have done this on purpose. File corruption seems to occur when using android to transfer files. Are you really suprised though? You're running the O/S off the memory card too remember...
======================
caedanne said:
http://forum.xda-developers.com/showthread.php?t=756491
Click to expand...
Click to collapse
Not senseless dude
kiteboarderni said:
Has anyone got a list of senseless builds at the title suggests!
Im currently running Dans froyo 1.1 which i love, and if it had BT support i would use without fail, but its kinda annoying me now !
Thanks guys
Click to expand...
Click to collapse
I'm also would love to see something like that, but for now I'm using mattc Leo + Froyo w/Sense and removing most of Sense stuff leaving only Gallery(it's fastest of all I've found) and Contacts(for providing "Search in contacts" as a direct app).
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)
I bought the Mini Bluetooth Keyboard direct from Chinavision. It works OK in WInMo, but nothing will make it work in Android. I would post the link, but posting rules don't allow it.
Has anyone else bought a similar keyboard (I believe they sell a similar one on Amazon) and got it to work? If so, how?
I can pair it OK, but nothing will make it work. I tried the supplied Android driver, but that won't install properly. I tried the various BlueInput apps, but none will connect at all.
Chinavision themselves are not at all co-operative, so I thought I'd ask here.
Thanks in advance,
--
Pete
Just ordered something simular on ebay and waiting for delivery.
I noticed it said that it wouldn't work in Android v2.2 so I guess it will be a bit of a challenge to get it working.
I tried again today. I installed BlueInput v1.8 and had some results, but nothing useful. A click sound comes from the HD2 every time a key is pressed, as per the settings, but no text.
So, something is happening ...
I'm running darkstone SuperRAM Froyo 1.5 on SD.
--
Pete
use cm7. cm implemented support for bluetooth hids.
lolmensch said:
use cm7. cm implemented support for bluetooth hids.
Click to expand...
Click to collapse
cm7?
---
Pete
PeteMy said:
cm7?
---
Pete
Click to expand...
Click to collapse
cyanogen mod 7. it is a popular custom rom. (cyaongen mod 6 will also work but there are almost no roms around here anymore.)