[DEV] [KERNEL] with support for L2CAP - Galaxy Tab Android Development

DEVELOPERS WANTED!!
Hello!
I want to build a kernel with support for wiimote and other gaming controllers, as our galaxy tab kernels dont support them! Im currently gathering infos about how to.integrate the support, and i would be glad if you can help me a bit!
03/08/11:
libs from cm6 dont work
03/07/11:
Research:
L2CAP server sockets stopped working around Android 1.5

I'll pay to see this happen
currently have my tab downgraded to cm6 purely to get fpse working with a wiimote...

I believe the SGT already supports the HID protocol (hence mouse & keyboard support), so that's half-way.
The Wiimote keyboard app works with (most?) Cyanogenmod 6 ports as well, so you might be able to kang the libs from there.

im willing to help out, although i dont know a whole lot, but iv been trying to look into getting the wiimote to work as well.

knightnz said:
I believe the SGT already supports the HID protocol (hence mouse & keyboard support), so that's half-way.
The Wiimote keyboard app works with (most?) Cyanogenmod 6 ports as well, so you might be able to kang the libs from there.
Click to expand...
Click to collapse
yes works with cyanogenmod 6 like a charm, using the libs from it causes a bootloop... (not really a bootloop but stuck at the samsung galaxy tab screen)
i need to look into the android sourcecode, and try to compile the bluetooth stuff from cyanogenmod for the galaxy tab (samsung roms) and pack it into an update.zip
jschmid698 said:
im willing to help out, although i dont know a whole lot, but iv been trying to look into getting the wiimote to work as well.
Click to expand...
Click to collapse
thank you

jschmid698 said:
im willing to help out, although i dont know a whole lot, but iv been trying to look into getting the wiimote to work as well.
Click to expand...
Click to collapse
Exactly what he said.
Sent from my GT-P1000 using XDA App

cm6 libs
Do the CM6 libs need ported to run correctly? or is the issue kernel based?

jschmid698 said:
Do the CM6 libs need ported to run correctly? or is the issue kernel based?
Click to expand...
Click to collapse
what i can say after my research is, that this is due to a lack of L2CAP support in the kernel, but there are private APIs which allow openening L2CAP sockets, but its VERY exhausting to learn/understand/hack them to get them work on the galaxy tab, so this is most likely a kernel issue!

Landroid said:
what i can say after my research is, that this is due to a lack of L2CAP support in the kernel, but there are private APIs which allow openening L2CAP sockets, but its VERY exhausting to learn/understand/hack them to get them work on the galaxy tab, so this is most likely a kernel issue!
Click to expand...
Click to collapse
There is l2cap support in the samsung kernel and CONFIG_BT_L2CAP=y in the config so i don't think it's a kernel issue.

Related

[Q] The TyTN II on Android...

First of all, I'd like to thank all the super-talented people on this board that have persevered and have managed to create and tweak these Android ports for our devices. You peeps truly are amazing! Never would I have imagined running Android on my nearly-ancient TyTN II, but now I can.
Now that the praise is out of the way...
Are there any (or are there any coming soon) Android ports that would allow for full functionality on my TyTN II and actually be stable? For example, USB connectivity doesn't appear to work. As soon as I connect it to my PC, it starts and stops continuously. The Bluetooth functionality seems to be present, but whenever I attempt to connect a headset to the device, it only recognizes it for music playing, not for calls or as a hands-free device. In addition, it doesn't matter whether I overclock or not, I'm still hounded by constant application crashes and it seems to get worse the longer the device is on. These things (at the least) are constants no matter which port I install.
Any ideas or suggestions?
In the end, I'm still very thankful for all the talent here at XDA and am amazed at all you've accomplished.
Thanx again.
I have had my old Tytn2 running Android fast and stable for weeks now - details in my sig. Edit the nbh for Kaiser and your panel then you just need to do two extra things:
1. Run the wifi fix
2. Get hold of an app called SD Dual Mount for USB mass storage.
Not sure about BT. I don't use it on mine.
Like you I am in total awe of these guys getting Android working so well on our ancient devices.
u can run it but its not going to be as stable as a native android phone i dont think...
Eventually it will be.
So, nothing right now to stabilize and utilize the full functionality of a BlueTooth headset? Thanx again.
Question... is the 2.6.25 supposed to be better than the 2.6.32 ??
daedric said:
Question... is the 2.6.25 supposed to be better than the 2.6.32 ??
Click to expand...
Click to collapse
Nope, they are the same as linux kernels just ported to our phones. .25 is almost two years old lol. It is stable though as it is more developed for our kaiser.
aceoyame said:
Nope, they are the same as linux kernels just ported to our phones. .25 is almost two years old lol. It is stable though as it is more developed for our kaiser.
Click to expand...
Click to collapse
What will i miss on using the .25 ? and what will i gain?
I've seen things like "2.6.25 users get the wifi patch here"
So we need a patch for wifi ?
daedric said:
What will i miss on using the .25 ? and what will i gain?
I've seen things like "2.6.25 users get the wifi patch here"
So we need a patch for wifi ?
Click to expand...
Click to collapse
yup there's a patch 4 wifi... but yaffs arent implemented over .25 right? couldnt that be intetesting????
Sent from my Full Android on Vogue using XDA App
Personally I'd go with .32 at this point. .25 isn't any more stable on my phone as far as crashes and lockups are concerned. And data loss issues with .32 seem to be mostly ironed out (I would still keep a /data backup in case tho).
Plus the performance increase from .25 to .32 is well worth it.
albertorodast2007 said:
yup there's a patch 4 wifi... but yaffs arent implemented over .25 right? couldnt that be intetesting????
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yaffs is implemented in the latest .25 kernel.
stmasi said:
So, nothing right now to stabilize and utilize the full functionality of a BlueTooth headset? Thanx again.
Click to expand...
Click to collapse
Bluetooth headset and stereo both work for me with Fresh Froyo, ever since Kallt-kaffe posted a fix for the permissions of one of the files.
daedric said:
Question... is the 2.6.25 supposed to be better than the 2.6.32 ??
Click to expand...
Click to collapse
32 is probably better at this point. For quite a while, 2.6.25 would survive crashes better, but I think they're pretty much equal now in that regard. The 25 branch doesn't get attention of developers anymore.
Not to mention the .25 kernel is right about 2 years old now.
aceoyame said:
Not to mention the .25 kernel is right about 2 years old now.
Click to expand...
Click to collapse
Don't be like that! My girl is perhaps 24 yo (i really don't know) and its still good to go
daedric said:
Don't be like that! My girl is perhaps 24 yo (i really don't know) and its still good to go
Click to expand...
Click to collapse
LOL, but kernels (and software generally) ARE NOT like wine and cheese daedric.... if that would be the case... all of us we would be windows 3.0
albertorodast2007 said:
LOL, but kernels (and software generally) ARE NOT like wine and cheese daedric.... if that would be the case... all of us we would be windows 3.0
Click to expand...
Click to collapse
Ok, i'll agree with you. Yet... i rather have a .25 working good, than a .32 faulty.
Yet... as mentioned before, they're more or less on the same quality as of this posting...
kernel update
sorry for dummies question, but...
I have tytn ii as all of you, and have same bug with all 3 versions of Android setuped on it.
The microphone not working at least, so when i call somebody, i hear him, but he isn't hear me.
All other, include wifi, internet working good.
I found that it's well-known bug, and kernel version change could help.
But how to change it?
All versions i downloaded, based on 2.6.25, it's 2.6.25-01106-g50cf5f2-dirty on my device.
I found zImage file 2.6.32 but when i change zImage in andboot and restart - it's don't help.
i found NBH file for tytn ii ( kaisimg-panel2-240x320-2.6.32-tilt-froyo-09-09-10_21.nbh) , but how to install it?
Pls help!
Try one of these:
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel-release.git;a=tree
If ur having problems look for a guy named l1qu1d, look at his signature it says something bout "atools" click on it and follow the guide....
Sent from my Kaiser.
I have already found zImage and nbh-file as well on that link, but the question is - how to install it?
as i understood atools working under Mac only, but i have Win7 on my PC.
krava1209 said:
I have already found zImage and nbh-file as well on that link, but the question is - how to install it?
as i understood atools working under Mac only, but i have Win7 on my PC.
Click to expand...
Click to collapse
its written in python. works with all os's as long as you have python installed.

What are the FRX07 features?

Since, frx07 is coming out sooon. What are features that are coming with it or fixes ?
Sent from my MSM using XDA App
madplaya1 said:
Since, frx07 is coming out sooon. What are features that are coming with it or fixes ?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
There will be a formal list when it drops. I will make a thorough post of what's changed when the time is right.
The big ones are RIL & BT. Audio routing won't make FRX07, so BT audio won't work, but pairing with BT devices & transferring data should.
Great , thanks!
Sent from my MSM using XDA App
seems silly to me to evenrelease fr0x7 without the BT and the audo routing fixes already in place at least for the rhodium users., i understand that the BT and audio routing fixes are mostly RHOD specific so why not make 2 version's of FR0x7? Those are the changes that most ppl weant they want there BT and loud speakerphone. Just curious as to why it would even be released without those things since the fixes are out, if it means having to wait to release fr0x7 than wait IMO. i donno just my 2 cents
Audio routing isn't stable,isn't for all the devices and it's still being developed
So it's a time waste adding it now,then frx08 will have it..
helicopter88 said:
Audio routing isn't stable,isn't for all the devices and it's still being developed
So it's a time waste adding it now,then frx08 will have it..
Click to expand...
Click to collapse
Couldn't have said it better myself. Audio routing will not be implemented until it's stable.
Shouldn't the dev start focusing more on gingerbread because it's newer, just wondering? Or what?
Sent from my MSM using XDA App
madplaya1 said:
Shouldn't the dev start focusing more on gingerbread because it's newer, just wondering? Or what?
Click to expand...
Click to collapse
If you think GB has been forgotten, you are sorely mistaken. Your thread asked about FroYo, so that's what we've been talking about...
Lol ok
Sent from my PG06100 using XDA App
hi there every1,
i was wondering if there is gonna be a working Camera in FRX07 for us Rhod100_nl users with the wrong board??
grtzzzz
bArAbAts said:
hi there every1,
i was wondering if there is gonna be a working Camera in FRX07 for us Rhod100_nl users with the wrong board??
grtzzzz
Click to expand...
Click to collapse
Kernel issue, not a build issue from what I can tell.
Also, from what I've gleaned - the cam works, but only in low light. See
[UPDATED 04/29][DEV - Camera ( camcorder improvement ) ] Camera tests for more information.
Bluetooth data would be great. I have an asus transformer which will not connect to an adhoc network, so WiFi tethering is out. The only solution I can find for tethering a honeycomb tablet is through pdanet tablet, which requires android on both devices and uses bluetooth. Thanks for all the hard work.
EMB Driver said:
Bluetooth data would be great. I have an asus transformer which will not connect to an adhoc network, so WiFi tethering is out. The only solution I can find for tethering a honeycomb tablet is through pdanet tablet, which requires android on both devices and uses bluetooth. Thanks for all the hard work.
Click to expand...
Click to collapse
Is there a wpa supplicant hack for the transformer? My A500 tablet has the same issue stock, but with mod or custom ROM wifi tethering to my rhodium works perfect on ad-hoc. Anyway, maybe worth looking into.
PlacidFury said:
Is there a wpa supplicant hack for the transformer? My A500 tablet has the same issue stock, but with mod or custom ROM wifi tethering to my rhodium works perfect on ad-hoc. Anyway, maybe worth looking into.
Click to expand...
Click to collapse
Yes there is. I'm on an adhoc posting this from my TF right now. check the TF section for the xoom supplicant file or just flash prime 1.5 as this fix is already implimented in that rom
Will it have the new MMS fixes? That's the biggest thing missing for me. People love to send pictures and I always have to boot WiMo and ask them to resend it.
gallahad2000 said:
Will it have the new MMS fixes? That's the biggest thing missing for me. People love to send pictures and I always have to boot WiMo and ask them to resend it.
Click to expand...
Click to collapse
Yes, it will work for all carriers assuming you set your APN. Still hashing out the best way to do this, might just have to leave it up to the end-users to configure.
I flashed prime on my TF last week. Works great and has the WPA supplicant fix already built in.
I can tether to my TP2 in winmo or whatever! Works GREAT.
Also, waiting for FRX07. Great work on FRX06!
@arrrghhh, tnx for your reaction, but im not an android expert, is there a way to implement the fixes mentioned there in frx07??
keep up the good work!!
tnx!
bArAbAts said:
@arrrghhh, tnx for your reaction, but im not an android expert, is there a way to implement the fixes mentioned there in frx07??
keep up the good work!!
tnx!
Click to expand...
Click to collapse
Not easily, there's many, many changes. The easiest way would be to pull from the XDAndroid repo (all of our code is available...) and build your own system image.
07 will be out soon. In the final stages of testing.
arrrghhh said:
Not easily, there's many, many changes. The easiest way would be to pull from the XDAndroid repo (all of our code is available...) and build your own system image.
07 will be out soon. In the final stages of testing.
Click to expand...
Click to collapse
Is there a thread or website that shows the info on FRX07

Sixaxis on Android! but not SGS II :(

This are the news about sixaxis working in android devices.. but I've used the compatibility checker from the markent and SGS II don't have the bluetooth protocols.
Maybe anyone with Cyanogen can try it?
I remember reading that someone using MIUI got the Wii controller to work, I assume that it would work for the PS3 controller as well.
I tried it on my old Milestone and it was fun, I hope someone can get this working on the Galaxy S II.
takato23 said:
This are the news about sixaxis working in android devices.. but I've used the compatibility checker from the markent and SGS II don't have the bluetooth protocols.
Maybe anyone with Cyanogen can try it?
Click to expand...
Click to collapse
It can connect when you are on a CM7 rom.
However, I cant figure out how to make it work correctly in game.
It works once you flash a AOSP rom (CM7 or MIUI) because the bluetooth driver is the stock one, and not the samsung one.
You can use it in emulators but not in games because devs doesn't support controllers for now (Hope it will not take too long for them to support it )
I can not even make it work 100% in emulators. Some og the buttons work, but most of them don't...
What emulators have you tried ? I tried with FPSE, Snes9x EX, and a GBA emulator and all worked !
I'm on MIUI ROM and i use fpse, psxdroid and also gameboid, all work on this emulator have to use hardware key mapping.
slekerz said:
I'm on MIUI ROM and i use fpse, psxdroid and also gameboid, all work on this emulator have to use hardware key mapping.
Click to expand...
Click to collapse
I use psx4droid. How is your setup in psx4droid and in the input mapping?
kbkrogs said:
I use psx4droid. How is your setup in psx4droid and in the input mapping?
Click to expand...
Click to collapse
psxdroid setting i click
-full screen mode
-screen fresh rate -60
-use input method -on
Key mapping i use the some buttons as on ps3 controllers.
Shinrow said:
It works once you flash a AOSP rom (CM7 or MIUI) because the bluetooth driver is the stock one, and not the samsung one.
You can use it in emulators but not in games because devs doesn't support controllers for now (Hope it will not take too long for them to support it )
Click to expand...
Click to collapse
Any chance we could replace the Samsung driver with the stock one?
r34p3rex said:
Any chance we could replace the Samsung driver with the stock one?
Click to expand...
Click to collapse
i will not work because samsung use a different bluetooth protocol, the only way you can use this app is use aosp rom like cm7 and miui.
slekerz said:
i will not work because samsung use a different bluetooth protocol, the only way you can use this app is use aosp rom like cm7 and miui.
Click to expand...
Click to collapse
Isn't that the point of replacing the Bluetooth stack? It's definitely not an hardware issue if you could just load up a new ROM and make it work.
Help! Sgs2 does not recognize the SIXAXIS, even though I changed the Bluetooth address. What can be wrong? I have CM7.
What are the steps you did to pair it with your phone ?
r34p3rex=> I don't understand what you want me to answer... I already said that the bluetooth stack was the stock one in CM7 and MIUI (so yes, it is possible to replace it), and that Samsung's firmwares has a different one that is not compatible with controllers. If your question is "Can we replace the bluetooth stack in Samsung's firmwares ?" then I don't know, I'm not a dev ^^
Shinrow said:
What are the steps you did to pair it with your phone ?
r34p3rex=> I don't understand what you want me to answer... I already said that the bluetooth stack was the stock one in CM7 and MIUI (so yes, it is possible to replace it), and that Samsung's firmwares has a different one that is not compatible with controllers. If your question is "Can we replace the bluetooth stack in Samsung's firmwares ?" then I don't know, I'm not a dev ^^
Click to expand...
Click to collapse
This is what I mean. It'd be pretty sweet if a ROM dev could incorporate the stock Bluetooth stack into their Samsung-based ROMs
IMO AOSP roms are better than Samsung's roms. Have you tried one of them ? I swear you won't regret it ! ^^
If I remember correctly (I think I read it somewhere, but not sure) the Samsung bluetooth stack has dependencies with TouchWiz (and all other things added by Samsung) so it will be too hard, maybe impossible, to just change this. I may be wrong, but I think it would already be available if it were possible...
I tried to pair the SIXAXIS controller motioninjoy program, with usb cable. I switch controller to the computer, I downloaded the drivers from the application menu and changed the bluetooth address in menu, but its not working! =S
AILD said:
I tried to pair the SIXAXIS controller motioninjoy program, with usb cable. I switch controller to the computer, I downloaded the drivers from the application menu and changed the bluetooth address in menu, but its not working! =S
Click to expand...
Click to collapse
Try with SixaxisPairTool instead of motioninjoy.
Yeah try SixaxisPairTool. Motioninjoy is weird... I tried it first and it didn't work. When I used SixaxisPairTool I realised that Motioninjoy was not entering the MAC address correctly (ie: Instead of 11:22:33:44:55:66 it was 66:55:44:33:22:11 with Motioninjoy) So if you want to use Motioninjoy try to invert the MAC address, that way, Motioninjoy would put it the right way. Weird, isn't it ? ^^

Sixaxis Controller Now Working!

I'm not a ROM developer so sorry if this is a dumb question, but is there any way to port kernels from another device? Or at least, the bluetooth stack? My friend has the Epic 4G Touch (Sprint version of our phone) and he has both MHL and a AOSP bluetooth stack on a Touchwiz ROM, which is what I want! I want to hook up my phone to my TV through HDMI for emulators, but none of the ROMS that we have so far are compatible with Sixaxis Controller or Wiimote Controller. Currently we can't have both:
Use MIUI or CyanogenMod 7 and Sixaxis works, but no MHL
Stock rom, MHL works, no Sixaxis
For what it's worth, this is the kernel he has flashed - http://androidforums.com/epic-4g-to...6ghz-oc-quadrant-4000-acs-pre-rooted-cwm.html
EDIT:
Update!
I just checked the market and it looks like the developer of the Sixaxis Controller has updated his app (yesterday in fact) so that it works with the Galaxy S II now. In celebration, here's a video of our little device playing some N64 with a Dualshock 3 - http://youtu.be/KOwQ9lqwgFQ
Subscribing to this thread for sure!
this is old news!!! its been working ever since we got cm7. i posted about this weeks ago and i already have it working with my ps 3 controller
But what the OP is saying is that with the new update to the SixAxis controller app you can use it with the stock ROM, which is the only rom that supports the MHL adapter streaming to your TV.
With CM7 you could use the Six Axis but weren't able to mirror the game you were playing on the TV.
THCinNYC said:
But what the OP is saying is that with the new update to the SixAxis controller app you can use it with the stock ROM, which is the only rom that supports the MHL adapter streaming to your TV.
With CM7 you could use the Six Axis but weren't able to mirror the game you were playing on the TV.
Click to expand...
Click to collapse
To add to this, SixAxis controller has worked for AOSP roms (including, but not limited to CM roms) since the beginning of time. CM roms incorporated the correct BT stacks needed for SixAxis to work properly. Stock roms, for the most part, did not. I'm guessing the dev was somehow able to bypass the need for those specific BT stacks. I wonder how far the compatibility spectrum goes, now? 2.3?
i assume pairing the Sixaxis controller with BT is required?
movieaddict said:
this is old news!!! its been working ever since we got cm7. i posted about this weeks ago and i already have it working with my ps 3 controller
Click to expand...
Click to collapse
Haha yup +1.
movieaddict said:
this is old news!!! its been working ever since we got cm7. i posted about this weeks ago and i already have it working with my ps 3 controller
Click to expand...
Click to collapse
Yea, that's not the point though. It finally works on the STOCK rom, so now you have HDMI out capabilities as well. CM7 and/or MIUI doesn't have MHL capabilities.
madman604 said:
i assume pairing the Sixaxis controller with BT is required?
Click to expand...
Click to collapse
Yep that's correct. When you run the app, it will show your phone's bluetooth MAC address. You then plug the dualshock 3 to your computer and run a pairing app that will let you change the MAC address that the controller is paired to.
tzbigworm said:
To add to this, SixAxis controller has worked for AOSP roms (including, but not limited to CM roms) since the beginning of time. CM roms incorporated the correct BT stacks needed for SixAxis to work properly. Stock roms, for the most part, did not. I'm guessing the dev was somehow able to bypass the need for those specific BT stacks. I wonder how far the compatibility spectrum goes, now? 2.3?
Click to expand...
Click to collapse
I think I read somewhere that at least Froyo is required, but don't quote me on that. I know the app works on my HD2 when it was at 2.3.2, so it goes back that far at least.
How many controllers can you hook up with this app?
tiguy99 said:
How many controllers cna you hook up with this app?
Click to expand...
Click to collapse
Up to 2 IIRC.
Nevermind. Forgot my readig glasses.
Sent from my SGH-T989 using XDA App
Does anyone know if this will work with beastmod 4.0?
Also anyone using an aftermarket ps3 controller or does it have to be original?
Can anyone chime in?
Sent from my SGH-T989 using Tapatalk
The app will work on all Roms that our device supports (Beastmod, Domination,CM 7,etc) but not sure if it will work with third party controllers. In theory it should though!
So I got it working, but i'm running into a problem. For n64 emulator the right analog stick it keeps triggering c-right while still working as a right analog stick. I've tried tweaking the keymapping but obviously i'm doing something wrong. Any ideas??
¤sent by the juggernaut¤
Hi there ! Im having a real hard time to get this working with my t989 !
when I run my Sixaxis Controller it says
Could not start driver. Check that your device is rooted and has giben permission to run Disconnected.
Im on 2.3.5 perfect stock
i though i heard that the new app work with stock now ? can anyone help me out plz ??? Thank you !!
-==-=-
Ok ! Update 1) I rooted and put a rom on my t989 and now I can use my sixaxis controller (ps3 controller) with my cell phone now !
but... for some reasons n64oid wont let me link it... it kinda freeze when im scanning for devices !! anyone else had this trouble ?
with others emu such as Snes it works flawlessly
still cant figure this out.
i have seen videos of this app working correctly on t-mobile samsung galaxy s2... mine is the white one. not that it matters... when i run it it says failed to configure bluetooth... then 2nd attempt says cant bind pipe for device... what do i do to make this work...
just emailed the developer because my friend has the same phone and it works fine on his... the only difference is the color of our devise... he has black and i have white... but the dev said that it is a known bug and he will be releasing an updated version in a couple of days... so if you have a t-mobile galaxy s2 and it is giving you these errors,.... just wait a few days because a fix is on the way as per the dev. hope this helps someone because there was nothing else on the internet about my issue.... all were reported to be working fine... and mine was not...
bigkilla2009 said:
i have seen videos of this app working correctly on t-mobile samsung galaxy s2... mine is the white one. not that it matters... when i run it it says failed to configure bluetooth... then 2nd attempt says cant bind pipe for device... what do i do to make this work...
just emailed the developer because my friend has the same phone and it works fine on his... the only difference is the color of our devise... he has black and i have white... but the dev said that it is a known bug and he will be releasing an updated version in a couple of days... so if you have a t-mobile galaxy s2 and it is giving you these errors,.... just wait a few days because a fix is on the way as per the dev. hope this helps someone because there was nothing else on the internet about my issue.... all were reported to be working fine... and mine was not...
Click to expand...
Click to collapse
Are you and your friend using the same rom? Maybe your rom didn't have the correct Bluetooth libs?
Sent from my SAMSUNG-SGH-T989 using xda premium
Umm.. always had sixaxis compatibility? Twas 1 of the reasons I got the GS2, that n my foldable BT keyboard xD..
Worked on GB wit no issues, n usin it since I first installed ICS... donno where u got ur info but its incorrect, as for MHL, can't verify, don't got the cable, can't buy here yet n never looked at importing. But to say Sixaxis don't work on stock is a load of bull, either that or my ps3 controller is magic xD which would suck, gotta get a new 1, right anolog is startin to go loose, n I donno where to buy another "magic" controller that obviously shouldn't work in the first place as per your statement.

Any roms / kernels with Bluetooth 4.0?

Do any of the custom roms or kernels have bluetooth 4.0 support? The T989 uses a Broadcom 4330 chipset which has Bluethooth 4.0+HS. From what I understand the stock rom does not have the updated 4.0 drivers. This makes many of the new devices using Bluetooth Low Energy not compatible (many of the fitbit type devices).
Any ideas?
Thanks!
From what I know it has v3.0 with A2DP, HS and that's it. Remember this phone is from 2011. But the GS3 has 4.0
Sent from my SAMSUNG-SGH-T989 using Tapatalk
I dont think our phone has bt 4.0 its a hardware limitation from what i understand
Syzee101 said:
I dont think our phone has bt 4.0 its a hardware limitation from what i understand
Click to expand...
Click to collapse
Hmm... Even with the Broadcom 4330?
https://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM4330
I've done some digging around and it appears that the 4330 can be made to enable BTLE. It requires updated Broadcom drivers and android 4.3+. There are a number of phones using this same chipset that have gotten BTLE to work (and pair with Fitbit like devices). Looks like the drivers need to be enabled in the kernel compile.
I've got a Samsung Galaxy Nexus running CM11 and it has the 4330 chipset as well. I used this .apk to check for BTLE support and it reports that it is enabled. Unfortunately I don't have any BTLE devices to test with it.
http://weimenglee.blogspot.com/2013/10/check-if-your-android-device-supports.html
If anyone is running a CM11 version can you use the file in the page I showed to check for support? If I get the time I may try CM11 on my wife's T989 and see....
EDIT:
Looks like with it is working with the Galaxy S2 ( i9100 intl.)
http://forum.xda-developers.com/showpost.php?p=48977119&postcount=147
Cool..... I may do the CM11 update then pick up a Fitbit and see if I can get it working....
oh, haha ive been misled this whole time! guess you learn something new everyday ill check it out on my device tonight. thanks for the find!
Syzee101 said:
oh, haha ive been misled this whole time! guess you learn something new everyday ill check it out on my device tonight. thanks for the find!
Click to expand...
Click to collapse
Did you get a chance to check for support?
Lost Dog said:
Did you get a chance to check for support?
Click to expand...
Click to collapse
sorry for the late reply,
I can confirm jedi mind trick 8 (4.1.2) doesn't support it... i haven't had much time to update to anything newer (CM11)
Syzee101 said:
sorry for the late reply,
I can confirm jedi mind trick 8 (4.1.2) doesn't support it... i haven't had much time to update to anything newer (CM11)
Click to expand...
Click to collapse
Thanks!
I've been trying to get CM11 working but I hit snag with the phone rebooting every few minutes (not a boot loop but after it's booted it's really unstable). Once I figure that out I can test!
Lost Dog said:
Hmm... Even with the Broadcom 4330?
https://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM4330
I've done some digging around and it appears that the 4330 can be made to enable BTLE. It requires updated Broadcom drivers and android 4.3+. There are a number of phones using this same chipset that have gotten BTLE to work (and pair with Fitbit like devices). Looks like the drivers need to be enabled in the kernel compile.
I've got a Samsung Galaxy Nexus running CM11 and it has the 4330 chipset as well. I used this .apk to check for BTLE support and it reports that it is enabled. Unfortunately I don't have any BTLE devices to test with it.
http://weimenglee.blogspot.com/2013/10/check-if-your-android-device-supports.html
If anyone is running a CM11 version can you use the file in the page I showed to check for support? If I get the time I may try CM11 on my wife's T989 and see....
EDIT:
Looks like with it is working with the Galaxy S2 ( i9100 intl.)
http://forum.xda-developers.com/showpost.php?p=48977119&postcount=147
Cool..... I may do the CM11 update then pick up a Fitbit and see if I can get it working....
Click to expand...
Click to collapse
Hi, I tested it with this app and the result was LE not supported, see attached screenshot.
I'm on SlimKat ROM.

Categories

Resources