I've been around Linux for a few years now, and have had my Galaxy Tab 3 7.0 for about a year. I've run into a bit of a problem that maybe someone knows how to get around. I have some knowledge of android because of the relationship to Linux... but still rather a newbie.
I'm trying to get my Tab 3 to communicate with a Bolutek BLK-MD-BC04-B serial to bluetooth adapter. I have no problems pairing it with my tablet, but once paired only certain software packages will connect with it... and I have no use for a bluetooth communications terminal (the usual software). I can get everything to work on my main computer (running Ubuntu 12.04LTS) the way I want, but I can't find /dev/rfcomm0 on my tablet. I've tried several software packages from the Google store, but to no avail (so far).
What I'm trying to accomplish overall is getting a piece of equipment I have to work with an android tablet, that at present only works with Windows software. I've got W95 working on a virtual machine in my tablet (a tiny tad slow, but it works well enough) using the no-longer-maintained program "Limbo" and the only thing stopping me now is getting the signal from the serial port (on the equipment) to the virtual machine in my tablet. The adapter works as it should, the only problem is the android bluetooth.
Does anyone know how to get the tablet to connect to the Bluetooth adapter (it's already paired), and then assign the communications to rfcomm0 (or maybe put a virtual link to ttyS0/ttyS1)?
Better yet, is there also anyone with experience working with this Limbo software who could give suggestions how to get a serial port working in it? (It should be easy to do once I figure it out - I've got the whole thing working fine on my main system using Virtualbox, and it was easy.)
I'm on an extremely tight budget (dirt poor actually - typical graduate student) and need to work with what I have, so please no suggestions of buying a new tablet or anything like that.
Thanks!
Related
Hi all!
I need your help to get this thing working, without necessarily
1: Install Ubuntu on one of my boxes
2: Debug through VirtualBox
I have been mucking about with getting ADB to recognise my Kaiser but it's been a long run uphill without any results. I'd like to ask you guys/gals if you have a fully working adb debugging environment with your Kaiser in Windows 7, 32 bit AND 64 bit. I'd like to know for three reasons
1: I have two boxes with either version of Windows 7
2: I have a Kaiser I'd like to be able to debug so I can help out as best I can
3: It would be a great addition to the wiki I'm authoring
So, if you have and/or know a debugging environment set up, please provide details on what to get, where to get it and how to install it.
I have been searching this forum up and down and used Google but this is seriously kicking my butt right now . Thank you all in advance!
Another option would be to make a dual-boot machine, although i'm not certain how this would work with Win7, only done it on XP, however I'm sure it's relatively simple.
In fact if it wasn't for the fact that I need my desktop as a file and print server it'd be dual-boot already.
I'm resurrecting an older laptop at the moment purely as a linux box to use as a dev environment, which is fun as anyone who has an acx100 wifi chipset will tell you (having to go back to Ubuntu 6.10, which is the last fully acx100 aware version I can find).
Dual booting involves either, repartitioning your hard drive, or installing another drive for Linux, I find having about 10GB is enough with maybe 1GB or so for swap, this is usually plenty for a decent dev environment with a lightweight GUI like Xfce or even Enlightenment, if you want bells and whistles, (Gnome or KDE), maybe as high as 20GB.
Some feedback
I've been trying to do this on two Windows boxes for a couple of hours and I have to say, it's pretty amazing that I can't seem to get this working in any other way that either installing Ubuntu or Windows XP.
I've been trying the drivers that came with the Android 2.x SDK because these should be working. Is there anything preventing these drivers from working on our Kaisers and should I in that case get other ones (please provide a link)?
I'll try using a Live CD of Ubuntu and boot up my 64-bit box and see if I can get that to behave. Will report back as soon as its done.
It may be something weird, because I connected my kais130 to my old armada 500 laptop yesterday, which is running an old 6.10 version of Ubuntu, and it connected in USB with not a care in the world, powered down, swapped drives to my XP drive, and rebooted, it too detected the kais, yet on my 1.6Ghz dual core netbook, not a flicker, even running the latest 9.10 ubunto on live cd, not a thing.
I'm starting to wonder if sometimes the lack of connectivity is down to hardware on the PC side?
My old laptop however hates even ubuntu 6.10, so I may have to go to another lighter distro, probably slackware based, in order to get decent speed without the damn memory hog of a gui ( gnome or kde ) and the ability to compile my acx100 module without all the ubuntu hand-holding sudo stuff getting in the way.
I just finished a guide on the wiki I'm authoring to get debugging up and running on Ubuntu 9.(Karmic Koala) and it worked on two of the machines I got around here. One of those machines is the one with 64-bit Windows 7 which I couldn't get to work before.
I threw in a Live CD of Karmic Koala and made a couple of changes to the udev rules and it worked from the first get-go. Same with the other computer, which is a laptop which just so happens had Ubuntu installed in it already. I followed the guide I wrote and it worked without a hitch.
My limited knowledge about drivers and hardware leads me to think there's something going on with either the driver having a problem realising there is an Android based device connected to it, or it is something else entirely.
I wish I had a it more knowledge about these things, if nothing else to be able to get some kind of log/dump/debugging info out of Windows that I could share with the rest of the people around here, which might make us nail down the culprit and get rid of these problems for good. Or until the next version of Windows gets released.
Anyways, it is now up and running on my Ubuntu-laptop, so now I can at least get some more info about what's going on in Android when it locks up, freezes or just FC's.
Ditch VirtualBox. USB support on it is pretty crappy.
I build all of my roms on Ubuntu sitting on VMware Player. Very seamless experience.
BlueputDroid is the only wireless kb/mouse app I have found that uses bluetooth instead of wifi - and it's free!
I was unable to get it t work on TW roms when I tried a month ago, hence the CM7 label in the title, but it works beautifully on both Windows Vista (and later, I'm sure) and Lubuntu linux.
I have my laptop dual booting between the two OSes, and the program doesn't throw a fit about a duplicate entry - it only compares the BT address, which is hardcoded.
DUAL BOOT TIP:
It is necessary to pair your phone with the computer in each OS, otherwise the unpaired OS won't recognize the phone as a trusted device (the phone will still recognize the computer, so it will expect that the recognition is mutual - no reason to send a new pair request). The phone will recognize the computer's BT address regardless of the OS, so just unpair on the phone side, switch the computer to the second OS and re-pair - now both OSes have the phone's address stored, and the phone has the computer's address stored
Sent from my SPH-D700 using XDA App
Gonna try this now.
Hi,
i have an HP Mouse and would like to use it with my Windows RT. Normaly i would say connect the Mouse to the RT, driver will be installed automatically. But my mouse is working with the intern Wi-Fi of the deivce. So first i need to install the Software/driver before i can connect the mouse. Can someone tell me how i can do this? The mouse drivers are availabel for x86 and x64 Device.
Thank you
2 things.
First of all I have never heard of a mouse that connects via internal wifi. Only bluetooth, USB connector (which may have its own wifi or bluetooth device internally for a wireless mouse but does not need a special driver as it still appears as a normal USB mouse) or PS/2.
Secondly. You cannot install x86 drivers on windows RT.
1. You can complain about this directly by HP, but it's fact that this mouse connect directly by intern Wi-Fi. That's because there is no USB connector and the notebook has no bluetooth
2. if this is as easy as downloading a app from market i needn't to ask here? I found severel Threads saying they get Desktop Apps x86 runnying on the RT. So i thought maybe it is possible to get this driver/software running on the RT, too.
x86 drivers cannot be installed, it even says that in the thread.
I'm very crurious about this mouse; I've never heard of a WiFi mouse (the wireless ones that don't use BlueTooth use proprietary protocols of their own) and historically WiFi has been considered unsuitable for the purpose. I'd heard there was a project to try and produce a WiFi profile suitable for peripherals but hadn't heard of anything using it.
Could you please share the model name/number/whatever of your mouse?
As for using it on Windows RT, you'll probably have to wait for HP to release a Metro app that supports the mouse (if this is even possible). x86 and x64 drivers aren't supported, even to the extremely limited extent that x86 *anything* is supported, on RT. Offically, nothing is supported; the hack that we have uses a very clever emulation engine but only works on user-mode code (never kernel drivers, and probably never user-mode drivers unless the developer gets really ambitious). Open-source drivers *might* be recompilable - we've managed to get unsigned kernel-mode code execution - but even that is iffy. Closed-source ones, no chance.
http://google.com/search?q=hp+wifi+mouse
As the CNet review indicates, it only works with Win7 (and possibly Win8). I really doubt HP will actually provide driver for a 2-yr-old periph, especially since it has dumped on RT and is going with Android.
Essentially, you have an oddball periph that's limited to a particular OS. Rather than spending more time getting it to work, the simple fix is to spend the $10 and get yourself another wireless mouse.
Thank you for all your response.
here you go this is my mouse:
http://www8.hp.com/de/de/products/oas/product-detail.html?oid=5095508
Works fine with my Windows 8 Professional Notebook.
normaly i don't need the software. It's only for connecting. An other Mouse, which is older than my one, using an USB connector works with out problems with the RT. Only the USB connector into the USB hub, drivers are installed by Windows, and you can use the Mouse. I don't know maybe there are some ways to connect to the mouse. When looking for Wlan networks i found P2PHP-WIN-8. That's the Mouse-PC network connection. i tryed to login there with the RT, but it asks for a network key. And i don't have one for the mouse.
Someone an idea? I tryed the mouse ID and serial number. But doesn't worked
the mouse will use a proprietary protocol because frankly wifi mouses are so obscure that this is the first time I've ever heard of such a thing. That software likely includes the relevant drivers needed, not just initiate the connection. It just isnt going to work on RT until HP and microsoft work together to support it on RT which they likely wont.
Just go buy a normal mouse.
Wow... somebody actually used WiFi Direct for a mouse! Interesting.
It's possible that WFD will eventually be integrated into Windows as a generic driver, the way that UMS and MTP and HID and so forth are. In that case, assuming the mouse follows a reasonably standard interface convention (which is far from guaranteed from very early adopters of somewhat obscure technology...) it would probably work on whatever version of RT gets that generic driver (in the same way that BlueTooth -> HID can be used to load BT mice with a generic driver today). Otherwise, it will fall to HP and Microsoft to create a workign driver, and I doubt they'll bother.
my logitech mouse worked perfectly, just plug in the USB wireless receiver and a few secs later the mouse is working!
Turkishflavor said:
my logitech mouse worked perfectly, just plug in the USB wireless receiver and a few secs later the mouse is working!
Click to expand...
Click to collapse
this is a WiFi mouse not a usb mouse
Turkishflavor said:
my logitech mouse worked perfectly, just plug in the USB wireless receiver and a few secs later the mouse is working!
Click to expand...
Click to collapse
You didn't even bother to read the (at the time <1 page) thread, did you?
Hi guys,
I'm looking for a software which will allow me to connect any android phone to a Windows laptop or a PC and then use the Windows device as a phone - to make & receive calls and to send/review/reply to messages.
This is already implemented in a lot of vehicles when you pair the phone and then call/answer through the car's UI. I'm looking for the same thing but using a Windows device (laptop, PC - with Bluetooth) like the car in the example.
Can you advise me about such a software?
Thanks!
Solution found!
I found a solution for Samsung devices and it's called SideSync. It's a Samsung app for the phone and a pc version with Windows and Mac support. It allows you to do everything on the PC which is great.
Since I recently switched from HOX to Galaxy S6 Active it works great for me. Don't know about other phones thought. It may be restricted to Samsung devices only? You can try and advise if it works for you.
Hello All,
I'm new to this forum, so I'm not really sure if this should be general, dev, or just a technical question. Also I'm a software dev, but am not too familiar with android other than lightly using Android Studio for app dev.
Basically my problem comes down to this. I use a custom OpenWrt device as an ethernet dongle for my laptops by loading the g_ether driver. I would like to do this for an android phone as well. Right now I'm trying the s20 and s22 (pretty sure whatever solution I come to will work for both); however, when I plug my dongle in, the phone will see the dongle with all the correct device descriptors and all that, but will not connect and attempt to get an IP.
My current guess is that the phone just doesn't have the right drivers on there (cdc_ether or cdc_subset), or that it is not loading them.
Thus far I've tried poking around with termux, but have not gotten too far. I was hoping this community may be able to help me figure out how to get the phone to use the dongle.
Lastly, would really rather not root the phone unless completely necessary.
Thank you all for any advice!