I recently upgraded my android version from 2.2.3 to 2.3.5 (HTC Desire HD), and now eclipse cannot find it, I had no problems prior. I had no problems before. USB debugging is enabled, and my connection type is on charge only (have tried disk drive too). Restarting the computer did nothing, nor did restarting eclipse. I have also done a factory data reset many times. I am on windows 7.
Any ideas/Know what the problem is?
Thanks.
Answer courtesy of 'Samir Mangroliya':
--> Download and install HTC Sync in your pc.
Downloading HTC Sync installed the necessary drivers to my computer.
Connect your phone to computer before starting Eclipse.
Related
I am using Android Studio version
Android Studio 3.4.1
Build #AI-183.6156.11.34.5522156, built on May 1, 2019
JRE: 1.8.0_152-release-1343-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.5
with multiple Android devices including Pixel XL with Android Q (QPP4.190502.019)
All my test devices have started repeatedly displaying the
"Allow USB debugging?" PopUp
And losing ADB connectivity
What recent update has caused this behavior?
UPDATE
I reboot my laptop daily, as do my colleagues.
I and my colleagues have not updated USB drivers.
Ive tried multiple USB leads, as have my colleagues.
I've tried multiple Android devices and versions from 21 to Q
Devices include Pixel, Pixel 2, Pixel 3 & Pixel C, and Samsung S9, as have my colleagues.
I have revoked USB privileges and re granted on all devices, as have my colleagues.
The issue still persists
try to check the changelog for android studio update or have you try to enable the usb debugging in your device.
Haven't you installed/reinstalled Android USB drivers recently, if so try to reboot your system
It can also be caused by your broken USB cable, try to replace it with another one and check
I think you haven't checked never ask again option, that is why it's asking continuously.
So you can try to check that box if you haven't done that.
For others who might run into this problem, this started happening to me after I updated the OS version of my device. Restarting the device solved the issue.
I have an iOS application codename One, which is running in normally iPhone 5 and 6, which use the iOS operating system version 10.
However, that my app is not working on iPhone 4 and 4s, which use the iOS operating system 9.
Any idea what might be happening?
Thanks in advance.
Apps should work fine all the way back to OS 6.0 without a problem (Apple made the cutoff of 6.0 mandatory).
I'm guessing you failed at the install stage which could mean one of the following:
Missing or incorrect UDID setting - if you got the device UDID from an app it's probably incorrect if it's not in the provisioning well... it's missing.
Previously installed app with the same package/id either from the appstore or a previous build with a difference certificate
Parental control settings or corporate restriction limiting installs
Apple OTA install bug - the workaround for this is simple, connect the device with a cable and try to install the IPA thru itunes. Sometimes it starts working OTA after doing this once (FYI: OTA == Over the air)
I'm trying to sideload Lollipop onto my Nexus 5 from the OTA zip file.
At this point, the adb recognizes the device after I plug in the USB cable, and spits out the serial number.
As I understand the instructions for sideloading, once I get to this point, I just need to reboot into recovery mode, (which works as expected) and then bypass the red exclamation point icon using "volume up and power" simultaneously. That works too.
At the point where the screen on the Nexus 5 says, "Now send the package you want to apply to the device with 'adb sideload <filename>' I type "adb sideload + the OTA image file name", which I renamed for convenience". The file is in the platform-tools folder.
At which point the command window reports: error: device not found
So... the device is seen by the adb, but somehow is no longer found after the device reboots in recovery mode.
I've replaced all the usb drivers, enabled usb debugging and developer mode on the Nexus device. I've tried this in windows 7 and also in Linux (both from the android sdk tool kit and from an installation of Eclipse). I'm unable to get the adb to talk to the Nexus 5.
I read the android-windows usb inf file, and there is no section specifically for the Nexus 5, but I added a line under the "generic android" section with USB\VID_18D1&PID_D001 as has been suggested elsewhere for people who couldn't get the OS to see their nexus at all. My issue is not that the OS can't see it... and the adb sees it, too, until I try to sideload the OTA file in Recovery Mode.
Anyone else having this issue, or better yet... any ideas on how to solve it?
Thanks
It turns out that I had not enabled USB debugging before I tried to do this using Linux Ubuntu / Eclipse / Android SDK. So my problem was really a windows USB driver problem, I guess (though I can't be sure, since windows did see the device until I tried to transfer the file. Maybe that message was really conveying a permissions problem, too...)
I rebooted into Ubuntu and tried again and was able to transfer the update file. The only hitch I encountered at that point was to issue the sideload command as root. I didn't do that the first time I tried it, and got a message about lacking permissions.
I suspect the posted reply with a link to a universal USB inf file would have worked, but, though I'm grateful for the tip, I can't testify to that, since I managed to transfer the file without Windows.
Thanks to all who looked at this and especially to Alex P., for posting a possible solution. FW
IW, I'm glad to have finally been able to do this, but for anyone struggling to get Lollipop ahead of the OTA update... well, it's nice, but hardly worth a lot of effort.
I have Registered my device for developer.
But after choosing device in VS2012 and start deploying , It Gives error .
Unable to install application. The maximum number of developer applications on this phone has been reached. Please uninstall a developer application and try again.
I am new to deployment on device . Please suggest .
Do you happen to have multiple Windows Phone 8 devices? It turns out that if you register two devices under the same name, this problem arises. I had registered two Windows Phone Devices for development, but I hadn't given them a unique name (they were both named the default, which is Windows Phone, I think). On the first device, I had multiple test apps installed and, obviously, on the second device, nothing was installed, hence my frustration regarding the error. I did the following to make it work:
Remove the phone(s) from the dev portal,
Unregister both devices using Windows Phone Developer Registration.
Rename the devices, making sure their names are not the same.
Re-register the phones again, now with new, unique names.
I hope it works for you as well.
Uninstall the unwanted applications from the device.
Restart the device
Try to deploy the solution. It will work now.
It means you have installed three(3) testing app. windows phone have limit of max 3 app installation for debug.
Uninstall one of your previously installed application.
Now deploy your new application again.
Hope will work now.
I have several applications in WPF that periodically crash on 2 different servers (a dell poweredge and a HP proliant). The problem is that the WPF applications both crash within d3d9.dll. Rebooting the servers always fixes the problem. The problem only occurs a few times a month. Both servers are running Windows XP instead of Windows 2003.
Here is the event viewer application log entry for the crash
Faulting application iqlayer.exe, version 5.3.1.14, stamp 4a9d0d63, faulting module d3d9.dll, version 5.3.2600.2180, stamp 41109693, debug? 0, fault address 0x0003a756.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Once this problem occurs, all further WPF applications will not run until I reboot. I even tried running a test application which showed a blank window. The test app crashed immediately on start at d3d9.dll.
I found this KB which i think is related to my problem. However, i didnt install directX SDK on my server and dont know where to uncheck "Break on D3D9 Error".
Did you upgrade your video card drivers to the latest version?
I reckon there is no answer. I have rebooted the server and cant reproduce the problem :(