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!
I am using 1.5 and it works great, I am wanting to find out which other builds have blue-tooth working.
Afaik, 1.5 is the only build with working Bluetooth. I sure do miss my headset, #1 thing lacking with android for me.
I will be overjoyed if someone corrects me!
berardi said:
Afaik, 1.5 is the only build with working Bluetooth. I sure do miss my headset, #1 thing lacking with android for me.
I will be overjoyed if someone corrects me!
Click to expand...
Click to collapse
Dzo was/is working on BT in the kernel, AFAIK something in the library needs to be adjusted. I agree that BT is important; my objective is to perfect a 2.1 Eclair build, get GPS to a highly workable state, fix the audio lib/sleep/speakerphone issues, and then investigate BT (followed by camera), in that order.
I think GPS is well on it's way, so I should be able to focus on BT (hopefully with Dzo's help), and Polyrthymic is working on the Camera.
Shidell said:
Dzo was/is working on BT in the kernel, AFAIK something in the library needs to be adjusted. I agree that BT is important; my objective is to perfect a 2.1 Eclair build, get GPS to a highly workable state, fix the audio lib/sleep/speakerphone issues, and then investigate BT (followed by camera), in that order.
I think GPS is well on it's way, so I should be able to focus on BT (hopefully with Dzo's help), and Polyrthymic is working on the Camera.
Click to expand...
Click to collapse
That would be fantastic.
Keep up the great work, you're doing awesome Shidell! When I get a spare second (visited my parents this weekend) I definitely want to try the 2.1 build.
Shidell said:
Dzo was/is working on BT in the kernel, AFAIK something in the library needs to be adjusted. I agree that BT is important; my objective is to perfect a 2.1 Eclair build, get GPS to a highly workable state, fix the audio lib/sleep/speakerphone issues, and then investigate BT (followed by camera), in that order.
I think GPS is well on it's way, so I should be able to focus on BT (hopefully with Dzo's help), and Polyrthymic is working on the Camera.
Click to expand...
Click to collapse
Bluetooth should just be a matter of making some changes to the init.eclair.rc file you're using.
Check against the cupcake init.rc for the bluetooth settings.
Thank you...
It sure would be great to be able to have 2.1 with gps and blue-tooth working! I have seen some have said that the blue-tooth is flaky in 1.5 but I have not seen that to be true. What are they talking about? And if it is so easy to fix blue-tooth in 2.1 why hasn't any one done that for 1.6?
useable bluetooth audio is going to be dependent on having proper eclair/2.1 audio libs. which we are working on.. There's alot of changes to merge..
full 100% will always be a couple of builds behind whatever's newest and latest.
Thanks for reply
I would love to use the 2.1 but I need Blue-tooth.
What Is the Difference between each of these? I would like to know why I would want to upgrade from 1.5.
Oh boy.. lol.
1.6 and up do qvga resolution very well, but do not have working bluetooth yet
2.0 and up don't sleep properly because of the audio driver (which we are working on) unless you use a hacked kernel (which I don't recommend) and have a newer interface/livewallpapers etc..
I would suggest to try donut for now if you're thinking of upgrading.
dzo committed a change the other day that supposed to enable bluetooth in 1.6 - i didn't test it with a headset but I was able to pair it with my pc. Although no one has posted a build with that change included yet.
If that helps.
mrkite38 said:
dzo committed a change the other day that supposed to enable bluetooth in 1.6 - i didn't test it with a headset but I was able to pair it with my pc. Although no one has posted a build with that change included yet.
If that helps.
Click to expand...
Click to collapse
Do you have a link to that. Where did you read that? I would like to check it out.
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/bootenv.git;a=summary
It's currently the most recent commit.
Dear all,
Is there anyway to use bluetooth HID keyboard in HD2 android?
I found similar issue mentioned under nexus one thread.
http://i-miss-erin.blogspot.com/2009/09/connect-bluetooth-keyboard-in-android.html
tried it, but it doesn't work.
I also tried some 3rd parties software from market. All doesn't seems to work for me as well.
eg.
bluekeyboard jp
Blueinput demo
but without luck.
I am using freedom i-connex bluetooth keyboard.
Anyone facing the same problem? would be grateful if there are solution to it.
thanks!
I am surprise that no one else is using bluetooth keyboard to connect to HD2 android.
Please guide on how to get it done. Thanks.
Hi there. I did some research and found that Android builds with Cyanogen mod will allow you to use a Bluetooth keyboard.
To test this out, I went ahead and bought three BT keyboards from Fry's Electronics (Microsoft Mobile Bluetooth Keyboard 6000, Logitech diNovo Edge, and Apple Bluetooth Keyboard). I wasn't able to get any of them to successfully pair up and connect with my HD2 (running Android - MDJ Froyo Sense Revolution v.1.5 build). I keep getting a "Disconnected" message when I tried typing. After changing the build to Hyperdroid v.1.7 (which has Cyanogen Mod), I found that everyone of the BT keyboards that I bought worked. Also, Blue Input is better than Blue Keyboard JP for most of the BT keyboards. The input response is very slow/choppy with Blue Keyboard JP.
I haven't tried the other builds with Cyanogen mod yet, but I'm guessing that they support BT keyboards as well.
Hope this helps.
Only Hyperdroid 1.7 works. I've tried other Cyanogenmod_builds
My keyboard Geyes by name, Gey by nature. Advertised as WM6.5 AND Android SPP.. No it bloody well isn't..
Anyway after more hours than I care to mention. Here's my results
- NexusHD2-FRG83D_V1.8_(Froyo 2.2.1) - NO won't pair/work
- Ginger_hd2_v1.2 - Connects and pairs but still can't type a thing. (really like this build too. Big buttons/icons AND FM Radio)
- HD2ONE-0.3.4a OR B - a I can't get it to build on my hd2 B.... Connects/pairs but as above. Including the really like (FM radio, too)
- MDJ_FroYo_Streak_v.0.4_RAM_Edition - Don't remember it pairing, nor connecting and therefore it certainly didn't work... FM on this one, (haven't tried the Dec 16 build)
- Biffmod-hd2-v-1-3-1 - No pair, no connect, no woman no cry.. Cyan 6.0 not 6.1 this one...
No luck with either
bluekeyboard jp (constantly dis/connects)
or
Blueinput demo (same realm of won't pair, so cannot use it)
HyperDroid1.7.......... smaller icons/buttons no FM Radio But yes!! I type in bought quickoffice numbers and letters.. haven't quite worked out Fn keys yet.
It's a yes though....It does work.
The Holy Grail would be to combine builds. FM Radio bigger buttons.. Nope, I don't know how to do that.. Very reluctant to mess anymore. Nearly driven me mental this has... Somehow it would mean extracting the BT files from Hyperdroid1.7 and putting them into one of the others HD2ONE, perhaps?
same problem here, paired/Connected, but i get nothing when i type.
and when i type hciconfig, it shows that HD2 is actually receiving data from my BT keyboard, even blueinput can make a sound when i press keyboard
is there a solution? bcz this is driving me crazy...
Did Hyperdroid work for you? This is straight out of the box, with none of the other 3rd party services.
I haven't tried any of the 3rd party stuff with other builds where the keyboard does connect and pair, but where the keyboard doesn't actually work.
YES, HyperdroidV1.7 DOES work, with no 3rd party software, and this might be the only one I know that works, but still, Fn, Caps and some keys won't work.
I don't like the layout of Hyperdroid, the icons and fonts are too small, and the latest version of psx4Droid won't work in full screen mode, but Nesoid works perfectly well, that's for sure
what I want most is that I can directly use bluez in darkstone's SuperRAM v1.5 to connect to my BTKB, no 3rd party software, but as I say, I get nothing :-(
I figured this might be some kind of bluetooth configuration problem, bcz other android devices like nexus one, EVO, Dell Streak DO work(maybe not perfectly well)
BTW, my BTKB is iPazzPort
I've learned that for Freedom Pro Keyboard, there is an official driver to install before you can use it under android, here is the link:
www.simplemobilereview.com/step-by-step-freedom-pro-keyboard-setup-with-android
I don't know if this works for freedom i-connex BTKB as well, and havn't test it on other BTKB.
I found a solution for blueinput, and get it WORKED under other biluds !!
here is the link:
www.teksoftco.com/forum/viewtopic.php?f=30&t=2590
seems that I didn't quite understand how to use this tiny software before...
and again, the keyboard won't respond when I use Nesoid, which works perfectly well in HyperDroid, but u can type text though.
so, if I use bluez utility, the connection seems ok, the problem lies in the selection of the right keyboard, and how to switch to the right keyboard? I tried install other input method like google, but it won't help :-(
Yes, exactly my point. I've seen that Superfast Rom version and tried it. Yes, it's very fact.
I share your issues with the hyperdroid1.7 version. Smaller buttons, no FM and it's just not as slick as some of the others (HD2ONE and the Ginger_hd one.
I did find some BT files in hyperdroid, some .so files and copied them across. That didn't work though, I don't know what I'm doing. I only chose those because they seemed to be BT files.
It might be time to email 'Pongster' the guy who appears to have put Hyperdroid together from other builds. Nobody responded to me in that thread. I'm a bit reluctant to PM though, it seems to be bad form to me. It's just that we're so close. If we could identify which files it is and simply copy them across then we could ? amend any build..
Do you know of any other 3rd party BT programs? Although, to be honest I'm sick of fiddling (not sure it ever ends with this sort of things though).
Bluetooth HID list of builds that work + Dev HID Question
Status on SD builds in which BT works - Hyperdroid 1.7 and all 3 of Shubcrafts builds.
NO OTHERS to DATE (I've tried 13 Cyanogenmod builds)
Issue- Why do some builds work and not others?
Speculation - It must be some .so files, build.prob and or rootsfs
I've tried copying all the BT files I can find from Root/system (in the builds in which it's accessible and I've updated the build.prop Tried to get Ginger_HD, Nexus, HD2ONE, phiremod_SkinnyEvo_Final and Biffmod-hd2-v-1-3-1 to work. No luck.
Why is it that some Cyanogenmod_builds work and other don't (some don't pair, some do pair but you still can't type anything with the connected BT keyboard) at all.
If the files., issue can be identified then couldn't they be put into the (one so far) NAND Cyanogenmod build?
ukdutypaid said:
Status on SD builds in which BT works - Hyperdroid 1.7 and all 3 of Shubcrafts builds.
NO OTHERS to DATE (I've tried 13 Cyanogenmod builds)
Issue- Why do some builds work and not others?
Speculation - It must be some .so files, build.prob and or rootsfs
I've tried copying all the BT files I can find from Root/system (in the builds in which it's accessible and I've updated the build.prop Tried to get Ginger_HD, Nexus, HD2ONE, phiremod_SkinnyEvo_Final and Biffmod-hd2-v-1-3-1 to work. No luck.
Why is it that some Cyanogenmod_builds work and other don't (some don't pair, some do pair but you still can't type anything with the connected BT keyboard) at all.
If the files., issue can be identified then couldn't they be put into the (one so far) NAND Cyanogenmod build?
Click to expand...
Click to collapse
I would really also like to get a Bluetooth keyboard to connect to the nand roms.
Been lurking around this forum for a few months now, but only decided to post now, lol.
So we all know that the bluetooth drivers for ASOP and Sense ROMs are from different. There are quite a few threads on this forums and others regarding the issues that people have with the Sense BT driver, which range from low quality audio output to inability to pair with certain devices.
The problem that I have with all the Sense ROMs (from the older MikFroyo to the newer Synergy Sense ROMs and MikG) is that the BT connection between my phone and my car (an 09 BMW 3-series) continuously drop and reconnect whenever the phone attempts to transfer the contact list to the car. But in all the ASOP roms I have tried (CM7, Deck, SalvageZen), the phone and car paired perfectly and all the contacts transferred to the car without any issue.
I attempted to fix this issue myself. So I simply switched the bluetooth.apk file in system/app folder of the downloaded zip file for the Sense ROM with the one from CM7. And I also replaced bluetoothd file in system/bin and all the .conf files in system/etc/bluetooth with CM7 counterparts. This actually worked with the older Froyo based Sense ROMs, namely MikFroyo, which I used for the longest time.
However, when I tried to same thing with newer GB-based Sense ROMs. This method no longer work. The phone either drop connection and reconnect repeatedly like before (which was seen with Synergy, Kingdom, Virus's ROM). Or the bluetooth can't be turned on at all as in MikG ROMs (which I suspect is because the conflict between the apk and odex files).
Anyway, I am just wondering anyone can take a look into this problem and see if there is a way to replace the Sense driver with the ASOP one. I think this would solve the majority of BT that people are experiencing with all the sense roms.
Need some help here, bump!
As I understand it, you can't just replace the BT stack in a Sense ROM with the stack from an AOSP ROM because they're too integrated into the frameworks.
Also note: A-O-S-P = Android Open Source Project. ASOP wrote fables. (I know, I know, don't bother pointing out the misspelling.)
Well I figured that the BT stack is integrated into the frameworks. And I didn't really expect that simply replacing some files from AOSP stack can work in froyo based sense ROM. But it did work nonetheless.
So I figured it probably won't be too difficult to replace the BT stack in the GB based sense ROM. Maybe someone with experience can change framework a little to make this work.
shameless bump
guess no one cares enough...
No, it's not that nobody cares. It's that it wouldn't be that easy. I know you said you just dropped a few files in and boom, AOSP BT stack on FroYo. I'm not saying your wrong or making it up...but several people have tried swapping the AOSP stack in and weren't successful. It might have still worked, but it wasn't the AOSP stack (i.e., A2DP still sounded like crap). I really don't think it's as simple as just swapping a couple files, though that doesn't mean it's impossible either.
Cloud9Blue said:
guess no one cares enough...
Click to expand...
Click to collapse
Or maybe people who want AOSP Bluetooth are just using an AOSP ROM.
If you get this to work definitely let me know. I've been looking for the same thing.
swapping the kernel + .so modules may do the trick
arent the bluetooth drivers in the kernel? or as separate .so modules? how about someone trying swapping the kernel in addition to the modules.
The bluetooth stack is in the kernel. You can not use an AOSP kernel on a Sense ROM so that will not help you.
You may want to check out the Freedom kernel. This is a Sense Gingerbread kernel by lithid. He is in the process of swapping out the bluetooth stack for the AOSP stack. The kernel itself is pretty stable but the BT stack work is still very early in development. He wants to be able to support bluetooth controllers (like the PS3 and Wii) but this may also solve the problems that you are having.
The test version with the AOSP stack is Test v0.9.5 and the discussion starts in the middle of page 289 of the thread.
hootnath said:
arent the bluetooth drivers in the kernel? or as separate .so modules? how about someone trying swapping the kernel in addition to the modules.
Click to expand...
Click to collapse
Thanks for the suggestion but this doesn't work. I tried exchanging all of the related bluetooth files with the ones in Deck's rom.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
m20120 said:
The bluetooth stack is in the kernel. You can not use an AOSP kernel on a Sense ROM so that will not help you.
You may want to check out the Freedom kernel. This is a Sense Gingerbread kernel by lithid. He is in the process of swapping out the bluetooth stack for the AOSP stack. The kernel itself is pretty stable but the BT stack work is still very early in development. He wants to be able to support bluetooth controllers (like the PS3 and Wii) but this may also solve the problems that you are having.
The test version with the AOSP stack is Test v0.9.5 and the discussion starts in the middle of page 289 of the thread.
Click to expand...
Click to collapse
Hopefully this works. Thanks for the heads up!
Unfortunately the kernel did not solve me issue. I tried to combine the kernel with the zip mijjah74 created but this didn't work either. I think lithid-cm is on to something with the kernel, but I think modding the kernel isn't enough. I think the AOSP Bluetooth files have to be incorporated some way.
jpflaw00 said:
Unfortunately the kernel did not solve me issue. I tried to combine the kernel with the zip mijjah74 created but this didn't work either. I think lithid-cm is on to something with the kernel, but I think modding the kernel isn't enough. I think the AOSP Bluetooth files have to be incorporated some way.
Click to expand...
Click to collapse
Basically, yes. Lithid-cm is going to try to integrate the ASOP bluetooth stack into the next version of his kernel. The current 0.9 version does not include any kind of support for the ASOP stack and you are advised not to attempt the swap yourself. It requires code changes to the kernel and is not as simple as swapping the .so module.
MultiDev said:
Basically, yes. Lithid-cm is going to try to integrate the ASOP bluetooth stack into the next version of his kernel. The current 0.9 version does not include any kind of support for the ASOP stack and you are advised not to attempt the swap yourself. It requires code changes to the kernel and is not as simple as swapping the .so module.
Click to expand...
Click to collapse
Sounds good. I know that swapping files randomly wouldn't work but I decided to try it anyways. Thanks for the reply.
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Sent from my PC36100 using xda premium
lithid-cm said:
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Click to expand...
Click to collapse
I wish you the best of luck, but one thing at a time buddy
getting a ps3 controller to work is also going to require enabling usb-host in the kernel too(right? or do we need a dongle to do that like other phones?) as well as finding a male mini usb to male micro usb cable (do they make those?), as a ps3 controller has to be paired over USB before working wirelessly.
Honestly I don't understand what HTC did to muck up BT so badly. If everything works in plain ol' AOSP android then what the hell did they do to cripple it?
lithid-cm said:
I'm still working on it. This is a first since currently I have not seen any other sense kernel with an aosp modified bt stack. Let's hope I can figure it out. Boy I would love to play emulations with my ps3 controller over hdmi.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Thanks for taking on the challenge. Hopefully you can get this working!!