After getting my app to work in the emulator, I now want to test it on my Sony Xperia Arc Android phone. I follow the instructions from google here http://developer.android.com/sdk/win-usb.html but can't get their USB driver to load.
When I plug the phone into the computer via the supplied USB data cable, Windows 7 installs it's own driver and doesn't give me a chance to point to the google driver located here: C:\Program Files\Android\android-sdk\extras\google\usb_driver\android_winusb.inf.
When I go to the device manager and right-click on the Device Manage and try to Update Driver Software to point to the Google driver, it says it already has the best one and won't change it! (even though it doesn't work, ie. no drive label appears for the phone plus the device manager shows an ! for it)
I've spent many hours reading dozens of posts with similar problems but no solutions work for me. Any ideas?
Download the drivers from here:
http://developer.sonymobile.com/cws/devworld/downloads/download/sonyericssonxperiaarcxperianeoxperiaplaydrivers
Related
I'm working with Microsoft Kinect for Windows using SDK 1.8.
It automatically finds all of the drivers required, except for the Kinect Camera driver. Because of this, whenever I run a progra,m it gives an exception at: sensor.Colorstream.Enable();
When I use Xbox 360 instead it works perfectly fine.
Can anyone please tell me how to get this Kinect for Windows working?
Thanks
If someone has a similar issue, I just solved it in the following way:
In the device manager the kinect can be recognized in 2 ways:
Primesense
Kinect for windows
In my case, it only works when it is installed as Kinect for Windows.
When it is recognized as Primesense, you can do the following for all 3 devices (camera, motor, audio):
right click: update driver
Choose 'search on my computer for driver'
Choose from list of drivers on my computer
Choose the Kinect for Windows driver
I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric
I've just updated my Galaxy Tab 2 7" to OS v4.1.1 (Jelly Bean). Since that I can't connect to my device (from my Windows 8 PC, via USB) anymore.
Most relevant to me is the fact that I can't even debug my Android apps using the tablet (which is actually the reason why I bought it). Eclipse does show it among the adb devices, but in an offline status.
The Android SDK is updated. I've tried to force the install of the drivers via the android_winusb.inf located in the\android-sdk-windows\extras\google\usb_driver folder, but it doesn't seem to carry the right pieces of information. Tampering the file by manually adding 'em seems to conflict with the along-coming .cat files.
I've also tried by installing Kies, but even that piece of software can't connect to the device.
What do you suggest? Thanks in advance.
Magically, a new OTA update has come "from above" right to my device just a couple of minutes ago. That fixed the whole thing (no action made on the PC side).
Looking at the "about device" data sheet, Android version is still 4.1.1.
I haven't tracked the previous kernel version nor build number, so I can't see if and how they've changed; but I can write 'em down now, just in the case it may matter for someone else to check against:
Kernel version
3.0.31 - 523998
Build number
JRO03C.P3110XXCLK7
I have the same problem with this post: MSDN Post. It seems nobody answered with a working solution on that thread.
The symptoms:
Kinect SDK 1.5 installed.
The Kinect device is recognized and drivers seem to be loaded correctly.The speech demo works correctly.
Skeleton Viewer shows "Could not enable Skeleton Tracking".
Shape Game starts, but does not track anything.
Kinect Explorer starts the small windows only showing that it has connected to the Kinect, the black window does not open. If I close the white window, the kinect explorer is still running I have to quit it through the task manager.
When I unplug and plug the USB after I open Kinect explorer; it says insufficient bandwith.
I tried:
Updated BIOS.
Updated motherboard software. (ASUS Maximus IV Gene-Z, Gen3)
Removed all USB's and plugged them all.
Restarted windows. (several million times)
I uninstalled and re installed. Kinect SDK 1.0. (but everything is the same)
My OS: Windows 7 64 bit Ultimate.
I have been struggling with this for 1 complete day. Any suggestions will be greatly appreciated.
EDIT: I tried my Kinect device on another computer (laptop), and it works.
If the Kinect shares a USB Controller with other devices, a problem such as yours can happen easily.
Try the following: Unplug all USB devices, then connect only the Kinect to your computer. If you have USB mouse and/or keyboard, plug those into a different set of ports (for example front usb ports if you have the Kinect plugged into the back of the computer). Then, try running the SDK's sample applications.
Should this approach fail, something might be wrong with your USB controller(s).
One more option: Try running the sample applications on a different Windows computer, preferably a laptop of some type, since you won't need to plug in any additional USB devices.
If this approach fails, your Kinect is most likely defective. In which case you can get a replacement or refund from your retailer, if the purchase didn't happen too long ago.
Best of luck to you!
I finally was able to made my kinect work. This MSDN Discussion helped me to do that.
The solution:
Uninstall all Kinect Drivers from Control Panel.
Reinstall Kinect SDK.
(IMPORTANT) Make sure to skip getting drivers from windows update during driver installation.
And yay! It works beautifuly ..
The same happened with me; I noticed a windows update related to Kinect, installed it. Kinect stopped working. Installing SDK from May 2d 2012 didn't fix the problem. Rolling back to February 2010 SDK didn't fix it either. At first I guessed that Microsoft doesn't want us to use Kinect for Xbox any more, and this is their way of telling us to buy Kinect for Windows... well, may be - but in my case Kinect Camera driver was somehow updated to Version 1.5 (May 2, 2012), while everything else was on version 1.0. Installing original driver fixed the problem.
This programming guide implies that this is possible, so I figure what the heck.
Right now, though, it doesn't work.
Host OS is Vista 64-bit, VMWare Workstation 6.5.3 is running Windows 7 Enterprise 32-bit.
Installed Software on the VM:
Visual C# 2010 Express
Microsoft Server Speech Platform Runtime
Microsoft Server Speech Recognition Language - Kinect
Microsoft Speech Platform SDK
Kinect for Windows SDK Beta
I plug in the Kinect, the device is recognized by the VM, then I run the Sample Shape Game and it doesn't recognize the device. It says "Plug in the Kinect and try again" which turns out to be error 0x80080014, which leads to
http://social.msdn.microsoft.com/Forums/en-US/kinectsdknuiapi/thread/4da8c75e-9aad-4dc3-bd83-d77ab4cd2f82/
which gives me two things to look at:
is it plugged in with the special cable? yes
are all 4 entries in the Device Manager? no
In the Device Manager, I see a "Microsoft Kinect" group containing Microsoft Kinect Audio Control, Microsoft Kinect Camera and Microsoft Kinect Device, but there is nothing under "Sound, video and game controllers" other than VMware VMaudio. "Kinect USB Audio" should be there.
I'm guessing that there is some further twiddling I have to do with the VMWare USB / hardware options (whatever that tray with the USB / CD / HD / floppy etc icons is called) or some deft combination of rebooting and (un)plugging, but I'm almost out of enthusiasm.
Any ideas? TIA
EDIT: I realized that I had some lingering drivers on my host (Vista) system from OpenKinect. After removing them, I can no longer see the Kinect at all in the VM. Hmm.
There is this on read.me
Virtual machines: You must run applications built with the Kinect for Windows SDK Beta in a native Windows environment. Kinect for Windows applications cannot run in a virtual machine, because the Microsoft Kinect drivers and this SDK Beta must be installed on the computer where the application is running.
just to share that (not really understood how) VM Workstation 8 running in a host win 7 x64 with guest OS Ubuntu 10.04 sucessfully detected and installed Kinect drivers.
I was able to test it with libfreenect (OpenKinect Project) http://openkinect.org/wiki/Getting_Started#Manual_Build_on_Linux
best regards,
I'm late to the party, but we've been running and developing for the Kinect with Windows 7 running under VMWare under Mac OS X Mountain Lion.
I'm not a Computer Scientist, but I thought Turing showed that a universal Touring Machine was basically the same as physical hardware. I've had Distributed COM+ running on 3 or 4 VM's on the same physical hardware, but somehow the Kinect device is different? I don't buy that at all.
The most recent version of Microsoft Kinect for Windows (v1.6, possibly slightly earlier versions) in combination with the "Kinect for Windows" hardware does work inside a virtual machine. I run this setup on a MacBook Pro, Parallels 7 and Windows 7.
Note that a Kinect for Xbox does not work inside a virtual machine.
This page from Microsoft says that the "Kinect for Windows" device should work in a VM, but that the "Kinect for XBOX" does NOT work.
First of all you just need two Things to be installed:
libfreenect
libusb
after that you should set three flags to 0x02 at the line
typedef enum {FREENECT_DEVICE_MOTOR = 0x02,FREENECT_DEVICE_CAMERA = 0x02,FREENECT_DEVICE_AUDIO = 0x02,} freenect_device_flags;
Inside the headerfile located at /usr/local/include/libfreenect libfreenect.h but you will lose the ability to control the movement and the the microphone usage will be disabled so don't even try to access them or your device might get damaged after that you should also set
#define PKTS_PER_XFER 32
#define NUM_XFERS 6
inside your libfreenect/src/usb_libusb10.h file at the linux Line
After that rebuild your libfreenect by
mkdir build
cd build cmake ..
make make install.
Than Restart your virtual System and plug and connect only the Kinect Camera Device and no other Kinect device during start of the VM. When System is up you could test your device is properly working by switching to your previously created libfreenect build directory and go to bin there you run ./freenect-camtest you should get no or only a small number of package losses if a lot of losses occur try restart your vm with the camera device pluged in and already connected to your vm. You might need to active disconnect and connect the Webcam from the VM during startup to receive images this should be done during first seconds of VM Boottime!
Works with Ubuntu 14.04 and Workstation 10 and 11 and 11.1
HOST OS Windows 7 and Kinect SDK installed and Kinectdevice for Windows
Also it seems to be quite unstable you often have to restart your virtual system if you can't receive images from your Kinect. But if you once received images don't unplug device or you won't get data until you reboot virtual system with Kinect Camera connected to it.
=> This actually solved the problem otherwise to much frames get lost and its not possible to display proper image!