Android 3.1 have USB api. Actually I want to detect USB scanner and change its permission to extract fingerprint impression fro it. Can Detection and changing the permission possible in android 3.1 without rooting the device?
Can this be done with USB api in android 3.1?
Also the emulator does not detect the usb scanner. Is there any way to test this in emulator first?
thanks
USB API functionality is not available in the emulator at the moment.
For an actual device, you may only plug in the devices from the supported devices list, which, as far as I remember, did not include any fingerprint scanners. If you root the device and compile/install the missing modules you may get fingerprinting hardware support, but it's still very unclear to me, how to get access to that hardware from Java.
So, unless you're going for device rooting and kernel module tweaking, I'm afraid it might be quite difficult to get your fingerprint scanner working with Android device.
Other than that, there's a Motorola Atrix phone, which has a built-in fingerprint scanner, and Authentec has released SDK for that device.
Related
I've got an Android application which can be remote controlled by USB midi devices. The app itself is running fine with google ARC but the USB module doesn't detect any USB device.
I already found that it is possible for Chrome apps to use usb but only when declaring each specific device in the manifest (https://developer.chrome.com/apps/app_usb).
Does Google ARC support USB access?
Will it be possible to get a list with all USB devices without declaring them first in the manifest?
Sorry, ARC does not currently implement a USB service that proxies to the Chrome USB interface.
Feel free to file a bug however.
If we do implement it, is will likely have the same limit where you must predeclare the devices you want access to, for the same reason listed on the page you link to.
Related note: a bug on UsbManager access within ARC was reported: https://code.google.com/p/chromium/issues/detail?id=475419
I'm trying to create a simple Android testing app with Flash CS6. I've put a circle onto a blank canvas and plugged in the Android device (a Google Nexus 4), enabled developer mode/ USB debugging, created a digital certificate and tried to publish the app, but whenever I do so it tells me no device is plugged in. I've heard something about a USB driver for Flash CS5, but heard nothing about CS6... How do I fix this?
Thanks, any help is appreciated. :)
The problem might be that you need a debugging USB driver for your app. The easiest way to get it is to install the PC management application from mobile manufacturer (Samsung, for example has Samsung Kies), which usually includes debugging drivers.
If I wanted to implement an app for 2 Android devices so I can connect from one to the other via bluetooth, how can I do that via emulator?
HINT: I don't have an Android phone for simulating.
Thanks.
There are few limitations for the Android Emulator. The functional limitations include:
No support for placing or receiving actual phone calls. You can simulate phone calls (placed and received) through the emulator console, however.
No support for USB connections
No support for device-attached headphones
No support for determining network connected state
No support for determining battery charge level and AC charging state
No support for determining SD card insert/eject
No support for Bluetooth
Source Link
I've found the way to debug bt-enabled application on virtual android with real devices. That is not ADK emulator, and it has some flaws, but it definitely works.
Host computer works under Windows 7 64-bit with standard BT stack. Step by step:
Install VMWare Player. It's free for non-commercial usage
Create virtual machine. Set "Other linux 2.6" guest OS type.
Choose reasonable amount of RAM. Remove SCSI disk and printer. Add IDE disk at least 1 GB, keep USB controller, ensure if bluetooth devices are shared with host computer.
Download android installation from android-x86.org. I recommend Android 4.0 RC2 for EEE PC
Point VM's CD to the ISO file.
Start the VM and install android. Unfortunately, it's impossible to add google account there for now.
Switch to android console(Alt-F1 inside virtual machine) and ask for IP address(use netcfg command, look at eth0 network interface), then switch back to GUI(Alt-F7)
On host machine, run adb.exe connect your-vm-ip
Enjoy!
Here is an illustrated tutorial in Russian
You can't use an emulator to test bluetooth apps. The BluetoothAdapter will remain null in emulator. You would need a bluetooth device.
Reference link of accepted no longer exists and I can't seem to find any other pages the mentioned the exact same details. However, it is mentioned in this docs:
What's not supported
The Android Emulator supports most features of a device, but doesn't include virtual hardware for:
WiFi
Bluetooth
NFC
SD card insert/eject
Device-attached headphones
USB
The watch emulator for Android Wear doesn't support the Overview (Recent Apps) button, D-pad, and fingerprint sensor.
While most end users of phones and tablets tend to use earlier API levels, Android Wear and Android TV users tend to use the latest releases. Using recent releases can give you a better experience using the emulator.
In addition to elmot's method (which I have seen on various places on the net and has been reported to work), you may also consider this utility which seems to do exactly what you would need:
https://github.com/cheng81/Android-Bluetooth-Simulator
I don't expect you to correct my code, since it should be working, at least works on emulator. Unfortunately gives different output on the devices. My question is:
How to debug in such cases, when the device is not working as the emulator, and what could cause that (device model, a custom ROM?)
I heard some rumors some time ago, about possibility using the device instead an emulator somehow connected to the SDK. Could you also confirm or deny that?
You'll find it's not uncommon to find little quirks between devices. Many developers will have several physical devices to test their software on.
You can find information on using a physical device for debugging (including using it inside Eclipse, just as you would the emulator) on the Android website: http://developer.android.com/guide/developing/device.html
Yes you can do that. Just put your device into debugging mode, and connect it to the computer with the micro-usb port on the device. You will also need to download the drivers from the manufactures website.
I am a relatively new Android developer but have gotten pretty familiar with the SDK, using LogCat, etc. However, I'm now working on an app (for a Galaxy Tab 7-plus) that utilizes USB Host mode to talk to an external USB device and I've run into an issue.
My question is: What is an ideal environmental setup that will allow me to take advantage of all of the SDK tools (adb, debug, LogCat, DDMS, and so forth) when I am unable to be connected to my PC via USB (since the external USB device my tablet is talking to is using my tab's only USB port)?
Is there an emulator available somewhere (I've searched in vain) that will allow me to simulate USB Host mode using a USB port on my PC?
Do I need to go to some type of on-board logging app?
Is there some kind of 30-pin splitter available so I can connect to both the external device and my PC? (I'm guessing this is impossible, but I'm a hardware idiot... in addition to a run-of-the-mill idiot).
Thanks in advance for your help!
-KR
As I posted in the comments, If the tablet is rooted you can use AdbWireless (Application on the Market)
This can also be done without rooting. Google/Android officially supports this, as described at the bottom of this page:
http://developer.android.com/guide/topics/usb/index.html
But AdbWireless is easier if you are rooted.