I never had problems using Android Studio, while debugging directly on device or via emulator. Today after a long time, i tried to install it on my workstation and it looks like there are unidentified problems, that I didn't find anywhere on google ...
Emulator:
I tried 981234912849821 different settings but i can't start an emulation, it worked only ONE time. When i opened it again, it didn't work again D:
The emulator always starts, then crashes saying:
qemu-system-i386.exe has stopped working
I tried to use it with Graphics: Software - GLES 2.0 and this is the result:
I became bored about it, so i tried to directly use my phone and i discovered that android studio wasn't finding it, even by changing type of usb connection ...
Do you have any idea about this problem guys? ^^
PS: Don't flag it as duplicate, I already saw the answers on who has these problems but nothing worked for me :\
You need an ADB driver for your phone installed on your system. Also make sure that under the Developer Settings in Settings of your phone, USB Debugging is enabled.
Note: If you cannot find Developer Settings, just go to > Settings> About Phone> tap on Build Number for 7 times> then just go back to the settings and you'll see the Developer options.
And regarding the emulator, you might want to buff the resolution and the ram of the virtual device and try again.
Related
Suddenly my Android Studio stopped detecting all my devices, none of them is working. It happen from one execution to another. I've changed a few lines of code (1 min maybe?), hit run (instant run) and then I missed all my devices.
I'm using a Mac and as devices: Nexus 5x, Galaxy s6 and Oneplus One. What can be happening? I've checked previous questions here and tried all this:
Run configurations: no matter if I chose usb device or show the window, it does not work.
Tools > Android > Enable ADB integration: didn't help
Command line adb devices does not detect any either.
I've revoked and granted again USB authorizations. Still not working.
I've tried other apps I have, none work.
Restarted phones
Restarted android studio
Restarted computer
(Note: if I start an emulator it works, but I'd prefer to use physical device since I have to scan real barcodes)
Thanks a lot in advance.
On Lollipop 5.1
Go to About Phone
Click 7 times on Build Number. Now Developer options are enabled
Go back and Click Developer options
Enable USB debugging under Debugging.
Well, I've fixed. The problem in case any faces the same was a Stetho (http://facebook.github.io/stetho/) tab in chrome, the one you open by typing: chrome://inspect/#devices not sure about the reason because it's been open for 2 days now, but it was the cause, once I closed it, it worked.
Found this unaccepted answer here: macbook adb cannot open interface That for sure should be accepted.
EDIT: I've been able to replicate the problem. It happens when you have the devices tab open and try to run a second app that has stetho configured.
It happens if your device drivers not installed Please do this.
In Case of PC
Right click my computer select manage select device manager from left panel if your phone drivers not installed there will be yellow alert on driver right click on it select update driver software then select search automatically for update driver software.
Other
Please install the missing drivers of your phone.
I had the same problem . What I've done to solve it going to Setting >> Additional Setting >> Developer Option
Now select:
Developer option on
USB debugging on
Install via USB on
USB setting security on
Verify apps over USB
OK, what finally worked for me was to go into Settings\Developer options\Select USB Configuration and change it to PTP or MIDI....either one of those worked for me and all of the sudden my phone showed up and I was able to see and run my test app on my android phone.
This woorked for me
Go To Settings
Developer Options
Enable USB Debugging
Enable Verify Apps over USB
Select USB Configuration: Choose MIDI
I hope it also works for you
I have fixed this problem before but I can't now and I need a permanent fix. Everything has been going fine in Android Studio when it comes to testing my app. I now run into the problem "The selected device is incompatible." when I go to run the app. I'd like to know how I can keep it from reading my phone's API as 1 rather than changing my minSDK to cater to this problem, if possible.
EDIT: Literally just found a fix, not sure if it is permanent. I just restored my defaults in Development Options, turned USB Debugging off and on again and that did the trick.
All I had to do was turn off USB debugging, then turn it back on and it worked immediately. I didn't have to reboot or change any other settings.
Not sure if this helps. I had a similar issue using my MotoG 2nd generation with Android Studio on Ubuntu. I switched the settings as how my phone was connected from MTP to PTP. That worked for me.
I had a very similar issue,
Usually whenever I connect the android device for usb debugging, the device will prompt me asking for the permission from to access from the development PC
In my case, for some reason, I didnt get this prompt and hence, I got this error. I have turned off developer options & USB debugging, turned on again. Then, I got the prompt and the issue is solved
I am have issues using the remote debugging feature of the Chrome Developers tools with my Android device (LG Nitro running Android version 4.0.4). It was working perfectly several days ago but now my device never appears on the about:inspect page.
I have followed and carefully considered these instructions including the troubleshooting tips. I have also searched for the answer to my problem but have not been able to find anything that works.
I am using Chrome version 35.0.1916.141 on my Android device and version 35.0.1916.114 on my PC (Windows 7). Neither says any updates are available.
Please note:
I have enabled debugging on my Android device and the small bug icon appears in the menu bar at the top of the screen when the USB cable is connected.
I have installed the necessary drivers for my phone on my PC.
Chrome is open on both devices
"Discover USB devices" is checked
I have tried restarting both the computer and my phone several times
The only thing I have changed on my computer since the last time it was working was to download 64-bit Java. Could this have any effect? If anyone has any input or ideas, it would be much appreciated!
Sounds like you may have gotten lucky. Next time this happens, try this:
1) Unplug your device.
2) Revoke USB debugging in the Developer Tools.
3) In the command line:
adb kill-server
adb start-server
Plug in device and accept fingerprint.
Voila, it appears in Chrome again. I went through a lot of pain with random problems with my Galaxy S5 not showing up, I was pulling my hair out for hours trying to figure it out.
Update: After launching my Android application from Eclipse on my device, it suddenly showed up on the about:inspect page. I am not sure why it was not recognizing my phone before but it seems to be working now.
I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.
I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.
I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..
Anyone any suggestions?
EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically
You need three things in order to make sure this update goes smoothly:
Make sure your device is actually running 4.2.2 and the problem is not something else
Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
You are on the main account of your device in case of multiple user accounts.
Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:
3tiu52839ry082j3 offline
Right about now, there should be a dialog on your device that looks something like:
Check the Always allow from this computer box if you want and click OK.
That's about it.
Some other things to check:
Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.
For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode.
Check out this blog post on how to do it.
After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.
Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.
If none of the solutions worked for you then Reset ADB.
Go to Devices ---Click the right most down arrow----Select Reset ADB from the list.
I had tried everything suggested here and suggested in every log/blog that I could find in google, but still no go. The USB cable is known to be good. ADB is version 1.0.31 (as shown with , USB Debugging is enabled in the Nexus 7 tablet, the SDK was updated to the very latest tools as available on 1-mar-2013 for 4.2.2/API 17. I had tried both Media and Camera modes for USB, rebooted windows, rebooted device over and over again, re-installed latest google USB driver, etc. etc. but ADB Devices still showed nothing.
I hard reset the Nexus 7 tablet thinking that maybe the screen to allow usb debugging had appeared but got hit with cancel. But that didn't work either.
What finally worked was:
going into windows control panel | Device Manager,
selecting NEXUS under Portable devices,
then in the Driver tab clicking on update and manually selecting the Google USB driver (the check feature said it was up to date). Previously, the date shown was in 2006, afterwards a date in 2012 (but more on this in a moment).
That didn't fix anything though.
So then I switched USB from MEDIA device to Camera device - THEN it wanted to install driver software, so I let it do that. Afterwards, I noticed that the driver for the Nexus was back with the 2006 version, BUT then ADB DEVICES FINALLY SHOWED OFFLINE!!!! HALLELUJAH AND the Nexus was displaying the Dialog to allow USB debugging, and it now all works.
What I am not sure of is what step actually solved the problem. I don't think it was necessary to hard reset the Tablet, but the fiddling with the device driver wasn't a very convincing solution either - I don't think the driver was corrupt - but maybe it had to be changed to get the right driver associated with the tablet when connected as a Camera Device. In any event, it is necessary to connect the tablet as a Camera device for ADB to work...
Restarting device or enabling USB debugging did not solve my problem.
However I changed USB PC Connection to "Camera(PTP)" mode and adb devices showed the device id of the phone.
After reading a lot post talking about this particular problem, I actually solved it by resetting user permissions on files (that were owned by root): ${HOME}/.android/adbkey and ${HOME}/.android/adbkey.pub
Go to Device Manager and uninstall your device and remove from USB
HAve you CMD opend and make sure you are at least in ADB Help.
Connect device to USB and continue with steps provided by Raghav Sood - few answers ahead of me.
Worked for me just fine
I tried with this custom build and it works for me. Now I can see my logcat in Eclipse again.
https://github.com/khaledev/ADT/releases
Download the zip file then in Eclipse menu Help > Install New Software... > Add > Archive... Just pick the downloaded zip and do the rest of the install process.
I have written some codelines with libgdx in eclipse and want to run them on my android device.(It's a tablet)
But i cant find out how to do this.
I even cant run it on the android emulator provided by the android sdk. I get an error that the app stopped unexpectedly.
The app is working fine with the desktop launcher...
I hope someone can explain me how to get it working on the emulator or on my android device.
I saw somewhere that simply connecting my device via usb should be enough that eclipse is able to create an temporary app on the device, but this also didnt work.
Regards
1st of all, download SamsungKies[latest], to get and install proper USB Drivers. Its important that it should be the latest, cuz there was a bug in the previous versions.
Now that you have the drivers, simply connect your device to your machine IN USB DEBUGGING MODE.
Go to your main activity, and run.
If it launches in an emulator, close the emulator, and again in main activity, select run configurations -> Android Applications -> target -> always prompt to pick device.
Run again, and it should install and run in your phone/tablet.
NOTE:The activity closes in emulator because, by default, the emulator doesn't support OpenGLES emulation, its too heavy for your CPU.
i know its kinda late, but i hope it helps others:)