Has anyone tested the wiiMote connect aps after the *unofficial* 2.2 update? My understanding was HTC altered the bluetooth stack in 2.1 which was why it never worked.
thx!
It won't work with any ROM that has Sense. Get over it.
I really don't know, but what does Sense have to do with it? Couldn't a new BT stack be put in to a Sense ROM?
SilverZero said:
I really don't know, but what does Sense have to do with it? Couldn't a new BT stack be put in to a Sense ROM?
Click to expand...
Click to collapse
No. There was just a topic about this the other day...
Related
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.
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
ItsDon said:
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
Click to expand...
Click to collapse
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
CharlyDigital said:
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
Click to expand...
Click to collapse
Nope. I tried everything possible but nothing got the phone and radio to pair. I just can't go back to 1.5 so I've resorted to using a BT earpiece until the official 2.1 is released. Hopefully it will have an updated Bluetooth.
If you come across something I'd love to be kept in the loop.
Truely sorry i cant be much help...but you might consider posting your question in damages thread, or pm him.
Cheers
Just a quick question. I searched but couldn't find what I was looking for. I am wondering about using the wiimote app on 2.2. I know all the devs say that wiimote wont work with sense because of a bluetooth stack (no idea what that means other than that's what they say the issue is). Because froyo will be fixing BT voice dialing i figured something with the BT must be changing. Will this change allow me to use wiimotes now? Thanks in advance for the replies.
Sent from my ADR6300 using Tapatalk
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
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!!