Related
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?
The purpose of this thread is to track bluetooth support, document problems, fixes, workarounds, etc.
I'd like to get a poll going in this thread. Please post:
1. what bt headset you're using
2. what build you're running
3. short review of sound quality / bt performance
Thanks!
Support
Currently, bluetooth works in 1.5 (Cupcake), 1.6 (Donut), and 2.1 (Eclair). By 'works', that means can be enabled in the wireless settings and see devices. Everything after that is just software, right?
I haven't checked donut hero or eclair hero.
IIRC it does not work in Tattoo... yet. Let's get cracking.
Profiles
Currently only the headset profile is working.
BT worked in Cupcake since early on, so we'll start with...
Donut
All that had to be fixed in donut was a missing service in the init.rc. After that was added, things worked just as they had in cupcake.
Eclair
There were three problems in Eclair -
first (same as donut) the hciattach service was missing from init.rc.
Second, starting with Android 2.0, they switched versions of bluez from 3.3 to 4.x. This meant that what had formerly been called 'hcid' was now called 'bluetoothd' and there was a directory and config file missing from our basefiles. Fortunately, the old 3.3 bluez config worked fine once it was copied into that new directory.
Third, the hciattach binary was looking for a firmware file that didn't exist in the file system. But we got lucky and were able to sub in the older hciattach from previous versions without issue (so far!)
RESERVED for version 2.++
PAN
I've done some research and cobbled together some stuff on a bt pan. It's possible to do in cupcake. I believe donut and eclair are missing the pand binary.
Personally, I was hoping to use a PAN to get internet on my vogue since I'm a cheapo with no data plan. There's a hurdle here because Android runs a connectivity check before it lets you access most internet services. For example, you can start youtube over a pan connection and it will show the first page with thumbnails, but if you try to load a video it will tell you that you're not connected. So we need to figure out where to get the pan added as a 'real' connection.
1. what bt headset you're using: Samsung WEP 410
2. what build you're running: Eclair 2.1 by mssmison, with latest BT update; SD card ext2 norootfs
3. short review of sound quality / bt performance: could not detect my headset in discovery mode, could not pair
1. what bt headset you're using: Samsung WEP 410
2. what build you're running: Donut Heroblend theme by plemen, NAND norootfs
3. short review of sound quality / bt performance: paired flawlessly, both ingoing and outgoing audio working with calls. able to answer calls by pressing headset.
additional: using Plemen's donut from nand, also able to pair with my Macbook. Using Bluetooth file transfer from my vogue, I am able to surf my public macbook folders from my phone. when looking from the mac, though, no services are available on the phone.
Motorola H300
http://www.amazon.com/Motorola-Bluetooth-Headset-2d-H300/dp/B000VMTDOG
This is the earpiece I'm using, and I'm using Plemen's "[Android] Donut AOSP Eclair - Updated 02/01 - No rootfs boot" v252
http://forum.xda-developers.com/showthread.php?t=591104
So far, it's working great. Callers say I sound fine, and I can hear them. Has chugged along through several 1-2 hour conversations. Answering calls using the button on the earpiece works, and incoming and outgoing calls seem to work fine.
Would Blutooth folder from a droid from verizon with eclair 2.01 be of any help to look at???
Typically the people who know what to do with those get them as soon as they're available. I'm not one of them, though - thanks for the offer.
Looking for a start to research more into Bluetooth and A2DP drivers, I have some linux experience and would like to help the community with testing or helping to create stereo bluetooth drivers.
Basically all that is holding me back from using as a daily OS on my vogue. Can anyone point me in the right direction?
Oh I am running 1.6 with motorola s9's, phone will pair and shift music to headphones in stereo, however is extremely laggy and plays a second of music then a second of silence to "catch up".
daganb said:
Looking for a start to research more into Bluetooth and A2DP drivers, I have some linux experience and would like to help the community with testing or helping to create stereo bluetooth drivers.
Basically all that is holding me back from using as a daily OS on my vogue. Can anyone point me in the right direction?
Oh I am running 1.6 with motorola s9's, phone will pair and shift music to headphones in stereo, however is extremely laggy and plays a second of music then a second of silence to "catch up".
Click to expand...
Click to collapse
Go search the kernel thread for 'bluetooth'. IIRC, the big hurdle to A2DP is that only the low-speed serial driver works. That means we're currently capped at 115200 bps. dzo (the kernel god) has made some attempt at backporting the driver from the 2.6.27 kernel but eventually left off in favor of other things. Last I remember he was using haret to dump some info out of Windows Mobile. Like I said, it's all in that thread.
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!!
I just purchased an A501, rooted it and am running the Alexander III rom, (very nice job on the rom!!!)
I was hoping I would get the bluetooth Headset HSP profile in the new rom but sadly it was not there.
A little research has shown that there is a Bluez driver plugin installed and various bluetooth libraries, my question is can I potentially just replace these libraries with bluez libraries from another rom that has the HSP profile?
I really need to get the bluetooth headset profile working on this A501, and am willing to pay a bounty for help in getting it working
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
haag498 said:
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
Click to expand...
Click to collapse
Still doing a little research on this. I discovered, in the Bluetooth folder, a couple of files pertaining to what Acer has deemed "black listed", which simply means, certain brands and models are not allowed to work with bluetooth. System/etc/bluetooth/
Also noted, if you modify the files, you need to make changes in a couple of other module files (android_bluetooth_ScoSocket.cpp). The info in the above files tell you where to look.
Not sure why Acer black listed those devices. Legal reasons maybe? Plain incompatibility? Who knows.
My dev skills, are not quite up to modifying .cpp files. Probably enough to muck things up really good Not to mention, I would have no way to test them. But when I get a chance, I'll see what's in them.
Of course most of this pertains to Auto pairing, so might not be of much use. As with the .so files in the Bluez folder, you'll need to de-compile them first to see what's in there.
Also, I saw some bluetooth apps onn the market that some folks had some success with getting HSP. Not the off/on widgets but an app itself. Might want to give them a try and see if you can get the headsets to connect.
Additionally, it seems bluetooth headset problems seems to be across all devices, and not just the a501, but Zoom, Transformer and Thrive as well. Hit and miss with what works. Most issues say the mic doesn't work.
I tried a couple of the apps with no joy on my plantronics earpiece but one of the widgets actually connects...for just 2 seconds...then disconnects...I think the capability is there and you are correct there is some file manipulation that needs to occur...
I have a friend in Egypt that is very good with android bluetooth, he is working on another project right now but when he finishes his current project I will send him these files...he might be able to figure it out ...
Hello Everyone!
I could not post on the developer thread so putting it up here. I flashed the zip file that was shared on this thread (http://forum.xda-developers.com/showthread.php?t=2807178) and to be honest I just loved the visual improvements that google have done in the L version. However, I found some issues which I need to know whether are resolved or not. If it happens to be posted somewhere else, please direct me to the thread.
Bluetooth Connectivity: I drive a lot with my phone connected to the car all the time. After flashing the ROM, I found that there was no option for phone audio in the bluetooth connection settings. Therefore, I was able to control the music player (since media playback option was there) from the car console but I could not access any calling functions/phonebook/recent calls, etc. from there. Has this issue been fixed? If not then I might have to go back to stock KitKat with Xposed which I was using earlier.
Regards
Me Too
I have found the same problem. It would be great to know if there is a workaround!