Related
BlueInput for Broadcom is closing in
We're happy to announce that Teksoft is just a few weeks away from the release of Blueinput for devices that use the Broadcom Bluetooth stack, including the HTC HD2, HTC Touch Pro 2, Asus, and others.
BlueInput is an advanced HID driver that totally transforms your Pocket PC or Smartphone into the perfect Mobile office solution by offering easy Bluetooth connectivity to Bluetooth Mouses or Keyboards.
http://www.teksoftco.com/index.php?section=press&cat=2010#100203
fantanstic news !
I wanna use it with mouse and keyboard as mobile computer ~
Great News... Can a working version (alpha/beta/demo) be released before next Friday morning?
I leave next Friday evening for a 5 day camp where no laptops are allowed... ordered a BT Keyboard.. and have several BT Mice... would really like to use a BT Mouse on the HD2 as well...
indeed, would be great to have it asap. the news said something about "weeks away". probably it's in testing phase.
about time! hate having paid for the software and not having it working.
hopefully it supports different language/keyboardlayout. thats (beside mouse support) my only problem atm. with bluetooth on the hd2.
anyhow great news mad.
Here's a demo video:
http://www.youtube.com/watch?v=dLRXSBcu6WI&feature=player_embedded
showing a bluetooth mogo mouse working with an asus device, that has the Broadcom Stack (like the HD2 does).
looks impressive...
waiting for news
DN41
Still holding my breath too. Teksoftco's web site has everything in place except the download. Sure wish they would put up an expiring demo so we can at least have something.
Teksoft sleeping - confirmation
Ridiculous: Teksoft Broadcomm page is defunct for almost two weeks now. Are they sleeping or what? Does anyone know any details? Where are the beta testers???
Wonder if this will get around the issues with Wiimotes and Playstation Sixaxis remotes...would love to use one of those in FPSECE instead of the bgp100
Nice video showing the possibilities of blueinput. But the HD2 already has integrated bluetooth reception. I have a microsft 6000 series bluetooth keyboard, which is easily recognised by the current bluetooth software on my HD2. The current issue of the bluetooth keyboard is that not all keys are functional in the windows mobile 6.5 software. What is needed, therfore, is software that can reprogram the bluetooth keyboard keys, for more functional use. That will be a milestone for the Hd2. Has anyone heard of this software yet?
So you are saying your M$ 6000 BT mouse pairs properly and works? I have a M$ 5000 and the HD2 sees it but cannot pair with it. It works fine on a laptop.
mknewman said:
So you are saying your M$ 6000 BT mouse pairs properly and works?
Click to expand...
Click to collapse
No, he wrote "keyboard", not "mouse". No comment on your reading skills.
To be serious: back to my post on page #1: what about the blueinput software? Where are the beta testers???
Ok, Teksoftco, this thread was started by you on Feb. 5, today is June 24. 5 months seems a bit extreme for a beta test.
Hi,
totally agree with you, 5 month to issue a software is a bit long. Perhaps waiting for people to buy other/recent keyboards ;-)
Anyway, my BK600 would work with my hd2 with that software. Too bad they haven't delivered yet. What do they need developpers ? (i'm one of them , so if they need help... lol )
Anyway in the same vein, i would really like to ask for sources of freedom / Com1 / omiz BK600 to fix the to issue a driver for my hd2 ...
Kind regards,
and still waiting some driver to make my bk600 work on my htc hdé !!!
Ludovic
Don't hold your breath - the software is defunct - not working - major issues.
see my thread : developping bluetooth gateway for bk600
enough to wait for will-be-released drivers, or drivers which are not for my phone.
I'll try to make on myself. If i succedd, it won't cost $15 ^_^
Clearsceeen
BlueInput: BT Keyboard not found
I've downloaded the last/new vesion of BlueInput 1.0.101. But still it can't detect my BT keyboard (HP iPAQ foldable). It detects though my BT mouse - Logitech MX1000 and it works fine, but no any signs by the keybord.
My other BT software on my HD2 detects the keyboard and i've managed to make it work, but its inconvenient to use one program for keyboard and another for mouse.
Has anyone experienced similar problems with iPAQ BT keyboard? It cannot be detected by BlueInput software. These guys need to do some more work before i buy this software.
Bought a cheapo chinese bluetooth mouse a while back for this purpose & have been waiting AGES for Teksoft to get this software running (I guess android has been the priority for them lately).
Works OK on my HD2 3.14 official wwe ROM, although probs encountered whilst on the home screen (weather animation on) or viewing videos. Also doesn't always track screen rotation (Youtube app for one, although does using IE).
Anyone know if the stock US Galaxy Tab Wifi-only model has bluetooth keyboard support? Also, have they fixed the lag issue?
up for this question.
i, too, would like to know if the Wifi version suppots BT keyboard and and possibly, mouse?
Galaxy Tab WiFi only
I am sorry to say that it does not support Bluetooth Keyboard or mouse. HID support appears to have been disabled in the Wi-Fi only version. I have tried several different keyboards and a Logitech BT mouse. Although the status shows paired, neither works.
I am highly disappointed and am considering returning it for something else.
-Phil
PhilFromIT said:
I am sorry to say that it does not support Bluetooth Keyboard or mouse. HID support appears to have been disabled in the Wi-Fi only version. I have tried several different keyboards and a Logitech BT mouse. Although the status shows paired, neither works.
I am highly disappointed and am considering returning it for something else.
-Phil
Click to expand...
Click to collapse
that sucks .. it's good that can even return it but in my case i'm stuck with it. Samsung should have changed the labeling in their box and specifications of the product should be laid out properly.
Wow thats very odd I would have assumed they would have kept that in there.
The only solution is to use Keyboard with SPP profile like the Freedom Pro Bluetooth keyboard, there is no HID profile support for the P1010
Funny, I avoided buying the Verizon version (at $100 less) because I read they disabled the bluetooth keyboard support. Guess this one is going back now too. And I really was liking it, and the 7" size of it.
How weird that I found this question. In fact I am using a bluetooth keyboard on my Galaxy Tab (Sch-i800, Verizon). And it is working perfectly. The Bluetooth keyboard I got is a Targus. I got it at Office Max for around $60.
Also, anybody relized how steap their prices are for general electronics? 16Gb Micro SD card costed $100....
Sent from my SCH-I800 using XDA App
Since I am no longer using my P990 as a smartphone I am thinking of using it as a "mini HTPC" on my TV. I tried several ROMs and different things to get the most of it but I have a huge problem with my bluetooth mouse and keyboard.
On Gingerbread and (the new v30a) ICS I can pair the devices but I wont see a mouse pointer and the phone will simply not react to inputs I do with my mouse and keyboard.
On JB CM10 I can pair the devices and also see a pointer. Both mouse and keyboard work perfect the way I want them to but the main problem I have with CM10 is the HDMI landscape problem.
It´s quite cool to get bluetooth with my devices working but it´s also pretty useless if the TV output is rotated 90 degrees.
Is there any way I can get my devices working with the original ICS? Is bluetooth a kernel problem or can´t this be fixed easily?
I also searched for the CM10 HDMI out problem and possible fixes but couldn´t find anything. If there is something out there, please let me know.
Thanks a lot!
So I did some more tests yesterday and it seems that bluetooth is not kernel related. Are there any hacks/tools/apps to support more input devices on ICS?
Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk
shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk
agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second
I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.
I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.
I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk
Does anyone know the location in the Android file system where the Bluetooth pairings are saved?
FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.
This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?
Guys I have a problem with our beloved xperia and I'm posting only now because I am sure now it's actually the phone, not the device (I tried it on an old KitKat Samsung and a nougat moto g... Everything is fine there).
So I have an iPega 9025 bluetooth gamepad which was working all right in my previous Nexus 5.
Here's the problem: FIRST TIME I try to pair the pad everything is fine, gamepad is working as it should be in games, emulators and within the android system. After first use though, if I turn off the gamepad and turn it on again it just doesn't work. I can see the Bluetooth icon in bar system and I see it in Bluetooth settings as Connected, it just does doesn't work.
Before u ask, I already tried going in Scanning settings and play with WiFi Scanning and Bluetooth scanning (on or off) : it doesn't change anything
I also tried in Developer Options in change Bluetooth AVRCP version from 1.6 to 1,4: doesn't change anything.
Bummer, I was planning on heavyly using emulators and games...
Does somebody has my same problem? Or maybe it's just this particular ipega gamepad having some sort of conflict with our xperia? In that case, does somebody is using some other Bluetooth Gamepad and NOT having any problems?
P. S. I'm on last build 47.1.A. 2.374
Nobody...?