My eclipse (Android's ADT download, on Windows 7) did not see my new Sony Xperia Z2 tablet when connected by USB.
I downloaded the driver to the PC but didn't install it (long story), and switched the Xperia's USB connection to Mass Storage Mode (as recommended in other posts).
I couldn't find the "Developer Options" in the Xperia's Settings.
There is a magic trick! It's in this post "http://www.androidpolice.com/2012/11/13/reminder-tip-developer-options-are-hidden-in-android-4-2-heres-how-to-find-them/". In brief, Settings --> About tablet --> has "Build number" at bottom. Tap on this many times, and you'll get a pop-up saying (something I didn't catch), and the Developer Options now appear as Settings --> About tablet --> Developer Options. You may want to turn on USB Debugging.
Mega-Grumble!!
Old post i know but, try this.
http://developer.sonymobile.com/downloads/drivers/
You should be using Android Studio now though far better in my opinion.
Go to about phone and click on Build number 7 times.
In this way you can enable actual developer settings.
I hope this would help you.
Related
I have 2 windows phone devices on my account that I use for testing. But they get locked for no reason.. I have to unlock it almost everyday. It even happened twice in one day. I haven't figured out what is causing this...
Is anyone experiencing this same issue?
**** UPDATE MESSAGE ****
This is the latest bizzare update on this bug... I've pasted my post in Microsoft Forum below:
I'm experiencing a very strange bug that I don't know if it is on the Windows Phone SDK or in Visual Studio.
I have 2 WP 8.1 devices to test an app that I'm developing. This was the sequence of events that led to this lock down:
Suddenly one phone that I used the most started to ask, almost everyday, to develop unlock the device...
Then the other phone started to do the same.
Now everytime I make a release version and run it targeting Device in Visual Studio, VS 2013 crashes... And the phone gets developer locked again.
Then I found a workaround that was to use the Application Deployment tool from the SDK only to test the release version. (Debug version it deployed without any problems on the device)
Today I forgot the manually deploy the XAP and clicked run in VS. VS crashed... Then I tried to deploy using the SDK tool it said that phone was locked... I unlocked it and clicked on the Deploy button again. Then the error: The maximum number of developer applications on this phone has been reached appeared.
I've uninstalled the app from the Windows Phone device manually and tried again and the same error occured.
I tried the other test device and had to register it again and got the same error.
Now I can't deploy any release version and I don't know how to fix this issue.
Do you know how can I fix all this Visual Studio bugs? I can't seem to find anyone else with the same problem as I'm having.
No, i have three unlocked devices in my account but one wp8.1 and other two win10, if you can upgrade your wp8.1 devices to windows 10 do that using that app because windows has inbuilt feature to developer unlock device, so your device won't get locked again automatically.
if you don't want to upgrade to and need assistance go to this link
this link requires you to login with your outlook account or may require you to login with your windows developer account.
and extra information if don't have windows developer account and want to publish your app go to this link from your windows mobile device or directly search for "Dev Share" App in windows store.
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.
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
Anyone that has installed the new IE9 know if I can keep IE8 installed? I do a lot of web testing and don't want to update to IE9 if I loose IE8.
best way is to install a Virtual Machine
Per Microsoft:
If you are running Windows Vista or
Windows 7 on your computer, you can
install the Internet Explorer 9 Beta
to replace your existing version of
Internet Explorer. After you install
Internet Explorer 9, you can uninstall
it to restore the previously installed
version of Internet Explorer.
So no, it will overwrite IE8 (at least the Beta will. I suppose this is not guaranteed to be the same for the release version).
I use Virtual PC with images of the browsers I need to test, but also and more lately, IETester, http://www.my-debugbar.com/wiki/IETester/HomePage. It allows you to run multiple versions of IE side by side.
If you want to be able to play with the new features of IE9 without installing the entire browser (which will replace IE8) you can install the Platform Preview. The PP is stand-alone, includes the latest features and bug fixes and has been getting updated roughly every 8 weeks. You can get the latest Platform Preview at:
www.ietestdrive.com
FYI: the production IE 9 does not accurately reproduce IE 8. I've got a CSS issue I'm chasing down now because IE 9's IE 8 mode isn't the same as real IE 8.
If you are concerned with testing how your site looks in IE8/7, you can use the Developer Tools (press F12) to switch the Browser modes and Document modes so that IE9 interacts with the web server as a different user agent, and renders the HTML document according to the version rules.
http://msdn.microsoft.com/en-sg/ie/ff468705(en-us).aspx#_New_Dev_Tools
IE9 beta is released as a Windows update, so after installing it and playing around, you can remove it from Programs and Features -> Installed Updates, which will recover IE8.
hit f12 on ie9, it will pop up the debug console. In the menu there is a browser mode option where you can set the browser to display as ie8 and a bunch of other versions too.
Also, if you're mouse focus is on the console and you hit ctrl+r, it will clear your browser cache... This is a feature that all the other browser debuggers lack.. ability to quickly clear cache.... I'm rambling now.
The best way to see your site on old versions of IE is that:
If you have IE9+, open your current version of InternetExplorer, press F12, click on "Browser Mode" tab, then choose the version you want.
see screenshot here:
Works better than IE-tester, and easier than using virtual machine.