I've had my captivate for quite some time now. After trying a few different roms I slowly gravitated towards Continuum. The fact it lets me use netflix, fully customize my look and feel built in, as well as having some of the most popular mods just seems like a win-win to me. It appears they still don't use the original bluez stack for bluetooth functions.
After doing some research, it appears that CM7 have changed the proprietary samsung blue tooth for the linux based bluez stack that allows wii remote pairing with the device.
Does anyone know if theres a kernal you could flash over continuum to be able to do just that? If not, what features might I lose if I were to switch to CM7. With so many nightly builds, its hard to keep up to date with CM7.
Any help on this subject would be greatly appreciated.
Related
Has anyone been able to get a bluetooth keyboard to work with the incredible?
I know their are some issues with spp.
I would love full b/t support as well. Am I correct in assuming that if new .32 kernels built for 2.2 come out, the issue should resolve itself? The chip supports it, and HTC did release the source, or am I missing something? Maybe the OTA remedies the problem.
does anyone know if the new 3.0 versions of cognition will ever have bluez inplace of the stock samsung bluetooth? I am looking for a bluetooth stack in a rom where I might be able to use a wiimote app to control emulators.
thanks in advanced
I BELIEVE that the issue with BT is using a Captivate Based Rom (Cogs) and an i9000 based kernel/modem
In theory if you keep your ROM/KERNEL/MODEM all in the Captivate based realm it SHOULD work?
I personally don't use my BT so I'm not positive... Anyone correct me if I'm wrong
Hi Guys....
I change my HTC Kaiser TYTN II to Android from Winmo rom cooked by shifu
suvil.com/products_freeaudiobt_en.html#product/gallery/free_audio_bt_2.jpg
My Bluetooth headset Suvil works fine to WinMO
Hard SPL 3.29
Radio 1.70.19.09
WinMO rom By shifu
Then i tried Android rom
Not so super froyo by kyle
fresh froyo by dark prince
I cant make my bluetooth headset media buttons to work
I tried to update the:
Hard SPL
3.34
3.56
Radio
1.71.09.01
1.65.21.18 downgrade
Kernels
L1q1d .32/.25
dzo .25
myns .32
still no luck! Cannot use the play/pause rewind/forward button functions
if i click the play/pause twice , it calls the last person on my log
Please help me Masters. TIA!
Thanks for letting me know that. Cheers!
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
n2rjt said:
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
Click to expand...
Click to collapse
As a diamond user, i hope you can fix the whole pack... Rhodium, Fuse, Diamond, and Topaz
n2rjt said:
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
Click to expand...
Click to collapse
OMG!!! Some Masters did reply to my post!...Hope im not too late for this!
I have a friend who is using Samsung I5510 built with Froyo 2.2.2
and media buttons on my headset works fine
Well the problem is dont know how to extract the driver or configuration of that ROM and install it to my kaiser. (i dont know as well if android works that way)
Just the forward/next Play/Pause buttons are not working, never mind the Volume control as Bluetooth headset has its own controller
Hope this helps and thanks in advance!!!
If you look here:
https://opensource.samsung.com/index.jsp
you can see that samsung released its I9000 ginger kernel and platform.
However I keep reading in many places that samsung didn't release all the I9000 drivers.
Therefore I have a couple of questions
Which drivers have been released by samsung (phone, bluetooth, screen, camera, ...)?
Which drivers have not been released (grapich hardware acceleration, camera, phone, ....)?
Since I have been using CM7, I have wondered if at least the phone, bluetooth and all the radio stuffs work as a stock rom. In other word if the phone and BT work for some exploits or if they work exactly as a stock rom because they use an official driver.
I'm asking that because I don't like the thought of my brain unecessary burned with too much EM power just because the phone and BT part work for some fancy exploit.
The same things for 3G and all radio stuff.
I do not care if the video acceleration or other non radio stuff are an hack and do not rely on official drivers.
Can anyone clarify the situation?
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
DBak451 said:
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
Click to expand...
Click to collapse
I've got it to work, will try it on lollipop.