I'm looking forward to 2.2 but the biggest feature that was lacking in the older version was the Bluetooth Stack. Does anyone know if the OTA Froyo on the Incredible fixes the functionality of SSP?
Yes
Voice dialing through my Blue Ant Z9 worked perfectly on stock 2.2. I believe full HID support (bluetooth keyboards, etc) may still not be present in stock, and I believe it is present in Cryanogen, if you are willing to flash that.
jdmba said:
...I believe full HID support (bluetooth keyboards, etc) may still not be present in stock, ...
Click to expand...
Click to collapse
Hopefully someone can test this with the Stock version. I'll be accepting the upgrade tomorrow. I'll be flashing my phone in the future if bluetooth doesn't work properly.
Oh, and thanks for the reply.
Bingo. Froyo Fixes the Bluetooth stack. Bluetooth SPP now works with Freedom Pro Keyboard Android drivers. http://freedominput.com/freedom-accessories/freedom-pro-keyboard . If you're ever looking for a full size keyboard for your phone, this is very nice. Comes with a little phone holder too.
Now if I could only learn to type!
F. McNeely
Has anyone had any luck with the iGo slim keyboards? I've read that there is an issue with HTC's bluetooth stack but supposedly there is a way to "fix" the issue. Has anyone created an update for Froyo (or know the steps to do it manually) that would enable the keyboard?
Thanks
fmcneely said:
I'm looking forward to 2.2 but the biggest feature that was lacking in the older version was the Bluetooth Stack. Does anyone know if the OTA Froyo on the Incredible fixes the functionality of SSP?
Click to expand...
Click to collapse
on Dinc Froyo 2.2:
I cannot get my iGo keyboard or MoGo Mouse x54 Pro to work via Bluetooth.
I show paired, but the status will never switch to "connected".
Related
I read somewhere that the HD2 supports bluetooth keyboards. Does anyone know if it's the same with the EVO?
Maybe, I hope so because I intend on testing it with an apple wireless keyboard
Not natively, but it should work with third party driver/apps like KeyPro.
Sweet I have my Apple Keyboard and Mouse.
I have heard a rumor that the Incredible does not support BlueInput (because of an older BT stack implemented by HTC) like-wise the EVO. I would be unhappy given the lack of a physical keyboard on the phone.
http://www.teksoftco.com/forum/viewtopic.php?f=30&t=2414
That was the same error I was getting on my Sprint Hero, but the KeyPro guys made a version of the drivers that worked anyway. I think they can do the same if the EVO has the same issue.
galt said:
That was the same error I was getting on my Sprint Hero, but the KeyPro guys made a version of the drivers that worked anyway. I think they can do the same if the EVO has the same issue.
Click to expand...
Click to collapse
Unfortunately it may be more OS related than a BlueInput problem.. Either way it would appear we arent getting HID anytime soon.
http://community.htc.com/na/htc-forums/android/f/91/p/2201/8561.aspx
zonyl said:
Unfortunately it may be more OS related than a BlueInput problem.. Either way it would appear we arent getting HID anytime soon.
http://community.htc.com/na/htc-forums/android/f/91/p/2201/8561.aspx
Click to expand...
Click to collapse
Mmm, so that explains why Wiimote Controller does not work on "devices running Sense"
FYI, using a beta version of KeyPro I was able to connect my Freedom Universal Keyboard 2 to the EVO, but the keyboard mappings were off. I've contacted the developer of KeyPro (who has been very responsive to tweaking the app for Sprint Hero support), I'm pretty sure this is something they can resolve.
Will report back...
My bad, I forgot to change the keyboard type in the KeyPro options - it works GREAT with the EVO!
Good stuff! Thanks for the notice!
galt said:
My bad, I forgot to change the keyboard type in the KeyPro options - it works GREAT with the EVO!
Click to expand...
Click to collapse
With what keyboard?
galt said:
...I was able to connect my Freedom Universal Keyboard 2...
Click to expand...
Click to collapse
It's a pretty nice keyboard. http://www.freedominput.com/technical-support/technical-support/universal-keyboards
I should note, it provides for good text entry and some hotkey functions, but it seems that much of Android's interface isn't accessible via these kinds of devices. You are still going to have to poke at your screen to do some things. Bluetooth mouse support would make this a bit easier...
I use the v-tech virtual keyboard via KeyPro. Works quite well.
Ceger
What did you do that I can't figure out?
I've spent the best part of 8 hours trying to get my Freedom Universal 2 keyboard to connect using Keypro. The developer said not to bother purchasing the key if I couldn't get the keyboard working without it. Were you able to get it working on the trial version? Or did you have to purchase the key? I've managed to get the keyboard paired but not connected. Thanks for any tips / pointers.
Are you using the beta version from the keypro forum? The one they cooked up for the hero works for me. Which ROM are you running, and what are the symptoms of your connection problem?
The version I've been trying to get working is Keypro 2.00.08 trial.
Android version 2.2
The phone appears to pair with the keyboard when the keyboard is set to SPP, but not in HID, but they never actually connect. I've not yet been able to use the keyboard or assign shortcuts using Keypro. Thanks.
I was counting on using my think outside Serria full size folding bluetooth to work, ltd proving tto be difficult so far.
This was and perhaps is one of best keyboards but it don't matter if it doesn't even connect
Any one have an approach they could suggest?
bigwavebrian said:
The version I've been trying to get working is Keypro 2.00.08 trial.
Android version 2.2
The phone appears to pair with the keyboard when the keyboard is set to SPP, but not in HID, but they never actually connect. I've not yet been able to use the keyboard or assign shortcuts using Keypro. Thanks.
Click to expand...
Click to collapse
I recently purchased the Freedom Pro keyboard from Amazon. I figured if I could not get it to work, I could send it back to Amazon. I originally tried to use the keypro apk, but was unsuccessful. Then I downloaded the android driver from the Keyboard site, that also would connect, but not pair. I then downloaded the instruction manual and followed their directions. Still no success. Then I got the bright idea of shutting down the phone, and then trying to pair my Evo to the keyboard. Success!!!! You click on the connected part of the driver software (read the installation manual) and this time it connected. There is an area on the driver you can use to check and see if you are connected. My Evo is unrooted (since 2.2). This has replaced my laptop for on-the-go business related work.
I'm running a stock Desire and have problems with bluetooth keyboard drivers e.g. "BlueKeyboard JP" not working. I believe this is down to the stock bluetooth implementation on the Desire as other Android devices are working with the driver, including the N1.
So I can either root and use a custom rom with better bluetooth implementation or wait for froyo release. But will froyo release likely have better bluetooth? As if not, I may start experimenting with custom roms now.
I would also like to know this! I am having problems with the bluetooth in my car!
With official Froyo now just around the corner (hopefully) can anyone shed any more light on this? I want to know if my hopes are going to be dashed.
OK, an update. Having installed official Froyo, bluetooth seems exactly the same.
So no keyboard drivers are working with the Desire.
Any news on the bluetooth situation? Did the J16 change anything, or are we still screwed on BT keyboards and Wiimotes?
Propheous said:
Any news on the bluetooth situation? Did the J16 change anything, or are we still screwed on BT keyboards and Wiimotes?
Click to expand...
Click to collapse
JI6 does not allow HID mode devices.
Maybe with froyo since the Tab might have have it set up properly. Just wild speculation on my part, but it would make sense.
Unfortunately, it making sense is also one of the main reasons Samsung probably won't do it.
hi,
i was under the (possibly wrong) impression that gingerbread natively supported bluetooth keyboards. (bt hid)
im at the moment stuck with the OTA update and cant seem to get my igo bluetooth keyboard to work.
any drivers that i can use with gb + igo keyboard?
regards,
asmd.
As far as I know, the problem has been with Sense (which was not upgraded with the OTA) and not with the version of android. I have used CM7 in the past and the HID profile works great. Maybe someone here who is using a Sense 3.0 Rom can validate if HID keyboards or even Wiimotes will work with the new Sense. My guess is no...
thanks for the reply.
Snap!! anybody know how to get a Igo bluetooth keyboard working with the current evo 4G GB OTA?
regards,
asmd.
My microsoft BT keyboard pairs, but doesn't connect. Same issue I had with froyo. Running Mikg 2.15 rom. When i tried the same with cm7, it pair perfectly. Not a complete deal breaker, but would of been nice. I recall reading previously that HID support had to be part of the BT stack. Whether the BT stack is a function of sense or not, I don't know. Practical testing suggests it is.
I realize this thread became a little bit old, but did anyone ever find a solution here? Or is Sense just totally incapable of working with a BT hid keyboard?
I just this past week got a new mini BT keyboard and was excited about all the prospects of using it. I'm currently on Sense MikG 2.5 and have been for about the last 6-8 months, after about a 6 month run on CM7.
I didn't realize, I guess, that there was such a vast difference in terms of BT HID devices. Anyway, I'd seen reference to an Anthrax kernel, but now see no way of downloading it.
Can anyone help out in that regard? And would the Anthrax kernel solve that issue? I might be looking to use the Anthrax kernel anyway.
I have been working to find a way to get my Igo connected. There was some small progress last night. I've been running sense 3.5. Last night I threw in a se of but hid files. Before it would even pair. Now the keyboard pairs but will not connect. For now I am using an ics rom to be adle to use my mouse. It connects with no problem. On sense 3.5 it pairs and connects. But it disconnects in less than a second
I'm having the same problems I have an LG Bluetooth keyboard and sadly running sense I can never get it to work aosp Roms seem to work fine though
I have a Galaxy Note 2 running Jedi Master 13. Every single thing is awesome about this phone...
EXCEPT:
I have a Lincoln with the new MyLincoln Touch radio. It supports text messaging ONLY with ICS or more specifically, Bluetooth 3.x. The Bluetooth MAP (messaging access profile) is different in 4.0 and thus not supported. Is there any way to downgrade said Bluetooth version?
I only use BT stereo and phone headsets normally, never use file transfers so the 4.0 advantages wouldn't affect me (I hope).
Thanks in advance for the input! :good:
Did u try and call the dealership, maybe ur car has update they can do
BACARDILIMON said:
Did u try and call the dealership, maybe ur car has update they can do
Click to expand...
Click to collapse
Yes, yes I did. I was in touch with the people that make the MyLincoln Touch device that works with Microsoft Sync. I have the newest version, which supports up to Android 4.1.1 and the Bluetooth 3.0 software, which has advanced compatibility with MAP. The Bluetooth 4.0 doesn't work the same and makes it lose the ability to do SMS from the car itself. Ugh.
I was hoping I could somehow put the old Bluetooth stack onto my phone to make it work properly. As of right now, Ford/Lincoln say that only Android ICS' Bluetooth stack is compatible. I feel better than the Apple community, they don't even get pictures to transfer. At least It's cool having the address book picture on my phone.
So can it be downgraded or not?
I am also interested in this (for another device though). Is it possible in principle?
No this stuff is way too complex due to the new advancement of spamsung Knox controling everything, we have very little control of our devices any more