No root required - works on any Android phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Teksoft said:
Despite the current Bluetooth limitations in the Google Android SDK, in early 2009 we've developed a first version of our Bluetooth Keyboard driver for Android. It was an OEM Project targetting a major hardware manufacturer, and it wasn't released to end users. The initial version also required root priviledges, so it needed extra skills to be used on normal Android devices.
Almost a year after, some considerable development progress has been made and we're now announcing the Teksoft BlueInput for Android, a Bluetooth Driver that allows you to connect a Bluetooth Keyboard to your mobile device for increased typing speed, more productivity, and a new feel of comfort gained by using high tech all arround you.
BlueInput is an advanced HID driver that totally transforms your Android into the perfect Mobile office solution by offering easy Bluetooth connectivity to Bluetooth Keyboards. And it is ready and waiting for you to try it right away.
Click to expand...
Click to collapse
This application is not free, but the trial version can be used as much as you want, but has a limitation on using the SPACE and ENTER keys.
Source: http://www.teksoftco.com/index.php?section=blueinputandroid
Related
I want to buy Dicota Beat . I just want to know. Does Dicota support the HD2?'
Link : http://www.dicota.com/start.php?page=page_productDetails&office=23&ds=1302
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The question should be 'does Dicota support the HD2?' as you will need drivers from Dicota for the HD2 to recognise it I beleive.
seems very unlikely as it looks like a windows gamepad, not for mobile devices as shown by the usb connection at the end of the cable
No.
It's working perfectly on my Toshiba TG01 (WinMo 6.5, but has a "real" USB host that accepts USB pens, keyboard, mouse, etc)
Using the HIDgamep.dll drivers I've found here, at XDA and a new key in the registry, it was working perfectly (I used it for FpseCE mainly)
But I've tried to do exactly the same on my HD2 in vain, the gamepad is not recognized.
The only strange thing that occured, is that as long as my dicota gamepad was plugged, my screen ratated to landscape when I clicked on "start" and was back to normal for the today screen.
I wonder if it was not recognized like kind of a keyboard.....
What is the probability of future work of the Dicota ?
Sorry for my english , I'm using google translate
Is there any progress?
You can now use your Transformer to work as a terminal emulation program via Blue Tooth with a serial blue tooth dongle and the SENA Terminal APP available Android Market (Free). See below response From CS at SENA. I have not tried this as the Parani-SD1000 BT dongle goes for around $100.00.
Thank you for your interest in Sena product, Zigbee.
SENA BTERM is terminal emulation program for Android OS. From our knowledge, Android OS does not support ZigBee protocol. However, Android OS does support Bluetooth and you can use our Bluetooth Serial adapters Parani-SD1000 (http://www.sena.com/products/industrial_bluetooth/sd1000.php) to communicate with Android device through SENA BTERM.
If you have additional questions or need any assistance, please feel free to contact me any time.
Thanks.
Dan Kim
Sena Technologies, Inc.
Customer Support Engineer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great, but it'd cost £75 to get one here in the UK, when a similar thing can be made with a PIC and a bluetooth module for under £10...
I just want a USB serial dongle to work
I've been working with the Kernel's Displaylink (udlfb) driver for a few days now. After some trouble I was able to get initial support for the legacy 2.0 USB devices working. Lucky, this early work was possible due to a few earlier projects. I had to work out a few power issues as our chosen device does not have enough power to run the display with out being chained to a powered hub.
So, currently I have an active framebuffer /dev/graphics/fb13 which I can push static frames to, but the display stack for the OS is not aware of the devices existence and so it can not be used with any of the API calls. I am looking for documentation or help on where to start. From reading the source pages on android.com I believe the extensions to the framebuffer need to be done in the Display HAL, but I'm not even sure where in the source tree those files exist. Its also possible that the display driver itself needs to be extended to report itself as an available display. If anyone has any insight I would be very grateful.
Link up and running.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
References:
https://sites.google.com/site/voyageofbeagleboard/Home/displaylink-for-android
http://antweb.me/index.php/blog-reader/items/displaylink-on-an-android-powered-beagleboard-xm.html
http://events.ccc.de/congress/2009/Fahrplan/events/3353.en.html
I have a 32GB HP Touchpad that had seen little use for a while, I got an ION iCade cab which connects via Bluetooth to the Touchpad. Although sold as (and originally designed for) iPads they work well with Android .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I flashed the Touchpad with Android 5.1.1 removing the WebOS first. This leaves enough space for the full Mame4droid 0.139 u1 ROMset, the smaller 16GB Touchpad will still host a huge selection of games.
I flashed 5.1.1 because the Bluetooth works well, this is critical for connecting to the iCade, or any Bluetooth controller.
TPToolbox was used to install 5.1.1
Bluez IME was necessary to force the iCade to connect the first time, after that it works every time. This is keeping my 7 year old entertained no end, and was to replace my full sized MAME Cab that had to go as it was (apparently) taking up too much space.
I'm posting this from my phone and will update it from my laptop with more detail.
Hey there!
I recently spend some time reverse-engineering the custom protocol the Galaxy Buds/Buds+ use to communicate with the original Samsung Wearable app. Based on the knowledge I got while doing that, I managed to develop a fully-fledged Galaxy Buds Manager app for Windows with several new features.
Link to the project: https://github.com/ThePBone/GalaxyBudsClient
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is killer. Thank you for publishing.
VIRUS
cOMES UP AS A VIRUS UNDER 5 ENGINES...
Antiy-AVL
Trojan[Dropper]/Win32.Scrop
SecureAge APEX
Malicious
Cybereason
Malicious.7c7527
Gridinsoft
Ransom.Win32.Filecoder.dd!s1
McAfee-GW-Edition
BehavesLike.Win32.AdwareAdload.tc
Acronis
Undetected
Cool.
Guess it can't support the SSC codec just SBC, AptX?
this is amazing! a wonderful yet so simple and elegant
thank you for the amazing project!
That's great!
Its possible port to wear os apk?
How do I install it? I downloaded the .zip with the files in the link, but there's no install file.
great work, works great but there is still lag in audio in windows
Hi, is there anything that can be done for the SBC Bitpool or maybe loading custom firmware that addresses this issue? For me, the Buds+ sound terrible with my Windows 10 Bluetooth stack (and yes, I checked that I'm not in hands-free mode).