I need some theoretical knowledge about this kind of connection. I've got a router with open wifi. I have also two (this number can change up to 15) devices connected to that network and one android tablet.
The main point is to show on a tablet data from these 2 devices at the same time.
So, what's the best idea to develop that idea on Android(API 2.3)? Using sockets or wifi connection( each in one thread)? Thanks for all solutions. Cheers.
Related
In a project I am currently working on, I am using a PIPO T9 tablet to run an app that uses the USB port to communicate with a transceiver. The reason I chose this tablet is because it has a usb port and a 5vDC power input (seemingly) allowing it to be powered while the USB port is in use. I found out later that only one can be used at a time.. So now I have been searching for a way to either:
Programattically force the tablet to disable USB host while the app is not being used. Hopefully allowing the tablet to switch to charging from the 5vDC line, or
Use an OTG Y cable to charge and get data from the USB port
So far I have tried the OTG Y cable method and it seems that this wont work with the tablet. When the tablet is off it has no trouble charging but as soon as its switched back on, charging stops. I have seen some similar questions on here and the recommendation was to use USB Accessory mode but I'm struggling to find out whether this will work with a tablet running 4.42 (NOTE: This tablet has been Rooted).
As always if anyone has any advice I would hugely, hugely appreciate it.
Thank you in advance :)
I am looking for a very fast method of sending commands from my Android device to my computer.
There are 3 methods in question, Bluetooth, ADB w/ USB, and USB. A server socket connection is too slow for what I need.
All 3 seem to give me a headache when trying to implement them.
I know a straight USB connection would be faster than anything else, but I'm finding it especially difficult to implement.
Many users suggested using adb to communicate over USB.
The main method in question is using the ADB server/client implementation, where I would forward the ADB ports and use a socket connection to host a server on my Android device (Somehow the USB is involved).
More information is available here:
http://www.anothem.net/archives/2010/02/15/communicating-over-the-usb-cable/
Would this method be any faster than using a standard server/client socket connection (since there is a USB involved in this method).
I'm a little hazy about how this all works, since I don't think it's a very common request. If anyone could explain this method a bit more I would greatly appreciate it.
Thanks!
I made an application which I started with Bluetooth, after some testing I decided to go with normal TCP sockets with the WIFI interface. The application consists of one PC which handles up to 20 tablets for a commercial command entry in restaurants, discos, etc. Every time a tablet connects the server send about 100 small JPG pictures which represent the different items in the menu. It's done very fast, less than a couple of minutes, and in normal data entry I've seen no problems so far.
I don't know how fast you need it to be but WIFI sockets are as least as fast as USB (2.0) and Bluetooth. Also with sockets the tablet and the PC can be hundreds of meters away from each other, depends on your WIFI configuration which can be expanded easily. Other thing to consider is when the device goes to sleep, when it wakes up it may take some seconds before getting the WIFI up and running and, in some few strange cases you need to restart the socket connection.
Whichever you decide to use, all of this should be handled by a well define protocol of course.
I know there are devices out there that monitors i.e. glucose of a CAPD patient. My question is do you know if I can read/access those data? I'm planning to create an Android app that read those data but I am hitting a wall as I dont know other devices.
You can read data off many medical devices, BUT the interfaces differ and the communication protocols also differ, AND not all devices support outside data collection. You will have to go device by device and write a device driver for each.
Kind of like you PC printer. Can they communicate with PC? Of course they can - but some connect over USB, some over PS2, some over LAN, some over Wifi, AND almost all of them require a device driver to 'talk'.
I'm working on a basic android wifi management program, but I don't have a real device. So I have to run it on android emulator?
I have searched, and understand that I can't work real wifi network. But it's not important for now, I just want to test my program on emulator.
I want to ask that if I can add virtual wifi networks to my emulator?
Thanks.
I think this is about as close as you can get:
http://kmansoft.com/2010/07/27/debugging-wifi-in-the-emulator/
Strong suggestion: buy a small, cheap, no-contract handset. T-Mobile and Virgin both offer them, you can buy them at Target, Best Buy, Radio Shack, etc (in the U.S., at least)
http://developer.android.com/resources/samples/BluetoothChat/index.html
As you know, the emulator does not have bluetooth support. My question is: is there any workaround to test the bluetooth chat from the sample?
The documentation states there is no Bluetooth support for the emulator. And you really should just test with devices if you have access to them.
I have never tried this, but I have read over before just finding a spare device. So if you are really stuck with just the emulator you can give this a shot. It's not a guarantee but it's something to look into.
https://github.com/cheng81/Android-Bluetooth-Simulator
Last I checked it supports:
switch on/off the "radio"
discovery devices (only other android emulators)
creating bluetooth services
connecting to bluetooth
services
You probably have to test/debug with real devices - IMHO there's no way to get bluetooth working on the emulator, not even a workaround