A few days ago I just typed android:debuggalbe="true into my manifest and plugged in my phone, when I ran the app it automatically ran on the phone. Im using a mac if that information has anything to do with it, now nothing happens it won't recognize the phone, I enabled usb debugging on the phone. Is there any way to see if it is even registering? I am really getting angry at this because I've done everything the exact way it says to on the developer website and nothing works.
check your log filter.
Open eclipse android devices view(windows > show view > devices),and click any process in your device;
reBoot your phone.
Related
The apps were debugging on my phone before, I had uninstalled the app but it didnt fully uninstall and didnt allow me to debug, So I used adb commandline to uninstall app fully. Before I used the command line, I went into apps section in my phone settings and uninstalled "Xamarin.Support" or "Xamarin.Android" in the apps section. After that any app, (tried making a new vs xamarin file) no app will debug on my android phone now.
I have tried turning Developer settings off and on, usb debugging on and off. Tried making a new vs xamarin file. All of these debug on Android simulator and on another phone but not on mine! When I try to debug any app on my phone. It builds, takes some time. and crashes immediately after starting.
I am thinking it is the "Xamarin.Support" app that I deleted of my phone that is effecting this. Please help!
The other phone that the debugging is working on, I went into their, went into apps in settings and searched xamarin. It had "Xamarin.Android API-27..." My phone also had something similar to that but I uninstalled it accidentally, and I dont know how to get it back to make it debug on my phone if that was indeed the issue.
I'm using Eclipse+ADT on Mac OS. I have a Nexus 5 connected via USB, but it does not show up in the Android Device Chooser when I run my app from Eclipse. Actually, it did show up once, and I could deploy my app to the phone, but then it just disappeared from the Android Device Chooser.
The really weird thing is that the device is listed when I run
adb devices
on the terminal. I even get the debug messages from the phone in Eclipse's LogCat, so it clearly is connected and recognized – but it still doesn't show up in the Device Chooser. I have tried all the solutions proposed here (rebooting the phone, turning debug mode on and off, restarting adb, restarting Eclipse, etc.) – to no effect.
Any ideas?
I had the same problem. I couldn't see my Nexus 4 in the Device Chooser list even though I could see it in the DDMS. I found out it is just hidden from view. Click the device chooser list and scroll up with your mouse wheel. The device should now be visible in the list.
Eerily similar to what I just spent the last hour figuring out. OS X, Nexus 5, shows up in adb devices, tried everything under the sun.
In my case, it turned out that even though the device wasn't listed, I was able to press the OK button and it launched just fine. (seen below)
I'm not sure if it also helped, but before I stumbled upon that solution, I edited my Launch config options to change from "Always prompt to pick device" to "Launch on all compatible devices/AVS'S" and selected the "Active Devices" options. I ran that and it worked! I expected the device to start showing up in the above menu afterwards, but it didn't. Then I realized it didn't matter and I could hit OK and it would build. Go figure.
The solution of blazeline worked for me but it was a little bit tricky to scroll up to make appear the device.
Another way to do it and to make appear the device more clearly is to disconnect your device when the Device Chooser List is opened and to reconnect it. It will clearly appear now in the device chooser list.
Eclipse is really sometimes strange...
My case was same as mentioned here and obviously i did all tricks with no success but solution was very logic:
device i was missing in pickup list had lower API then allow by AndroidManifest.xml
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 have a problem debugging apps on my Samsung Galaxy S3, (GTI9300, I believe this is also known as the international version) from Eclipse.
The thing is, debugging actually worked for a time and then it just stopped working. I've tried quite a few things to make it work again. I'll describe my whole experience briefly, to keep you from suggesting things I've already tried, and save us all some time.
When I first got my phone, debugging didn't work. When I plugged in my phone, the system detected it, and I could use it almost like a storage drive (using Media Transfer Protocol or some such thing) But when I started Eclipse and tried to debug, the debugger didn't see the phone.
I googled some, learned that I had to install some specific driver. I honestly don't remember which driver it was, but I believe it was an official one (from Samsung's website). Once I installed this driver, Windows would no longer detect my phone as a storage device. But the debugger did see it, and I was able to debug a few simple apps that I'd made. I could easily live with this tradeoff.
Then I got busy with other stuff and set Android development aside. I came back to it this weekend - after 2 or 3 months - only to find that it no longer works. No matter what I do, the debugger does not detect my phone (Windows still won't detect it either).
I tried all the first aid solutions like restarting Eclipse, rebooting my computer and rebooting the phone. Just for the sake of completeness, I do have usb debugging enabled on my phone.
The only major change of the whole setup that I can think of is that my phone's OS has recently updated. I don't know the exact version it was before, right now it's Android version 4.1.2 (Kernel version 3.0.31-1160235, if this is useful to anyone). I tried plugging the phone into other computers, it gets recognized as a media/storage phone. I can't install the Android development tools and try debugging on any of these computers - I'm stuck with the one I've got.
I've tried reinstalling the usb drivers for my phone. It didn't help. In desperation (and against my better judgement) I tried installing Samsung's software, first AllShare Control, and eventually Kies. None of it helped. When I run Kies, it gives me the option of connecting through USB or via WiFi. However it won't detect my phone when I plug it in. When I click "Troubleshoot connection" (or some such thing, unfortunately Kies decided to use my native language instead of English) it starts reinstalling the USB driver. This process takes quite a while, and fixes nothing.
I'm basically out of ideas, I don't know what to try next. Any help would be appreciated.
The emulator won't launch my apps even on a real device! I've tried every solution online, even reinstalling android sdk,ADT plugin. The app run SOMTIMES(4x to be exact) though, like awhile ago, when i got home i tried it again, and it run on my first try then i began working on the code again then i tried to run it, won't run again. Even basic apps like hello world won't run most of the time. I've set the run configuration to let me choose my device everytime, but even the device chooser wont show up(showed up once only), i tried waiting for 30 minutes(also tried the kill-server start-server) but it just wont run! my real device, or the emulator is listed on the DDMS perspective and there's nothing on console. please help, cause I've wasted 2 days for this already.
Have you also tried, taking the USB cable then disabling debugging and then enabling debugging and putting the USB cable back.
I remember this happen to me, so I did what I mentioned and surprisingly it works. Hope it work for you too.
Maybe you should try deleting your emulator and creating a new one. Make sure that all your settings are correct and that you are targeting the right OS version.
I've had quite a few problems with the emulator and wiping them and starting from scratch worked more often than not.
As for the real device, the first real hurdle is getting the right drivers so that your PC can recognize it, after that kill-server start-server usually does it. I'm surprise that didn't work for you.