Related
I have just started android and I created an app that was running fine a few days ago now I am working on another app but I am not able to run that and now I’m not even able to run the previous one.
now it's just showing Waiting for all the target devices to come online
and then it says Gradle build finished in 830ms or like that!
now it's just showing Waiting for all the target devices to come
online
To solve this-
Go to Device Manager>> Virtual and select launch AVD or from options select cold boot now.
Like Zobaer says, if it says waiting for devices that usually means the build has completed (you can check that in the Build panel) and it's waiting for the emulator to show up. If your emulator is already running, try closing it and running the app again. Otherwise if it's not getting started, try starting it yourself.
I'm just posting an answer to point out that you sometimes do need to be online for Gradle to run, but you can put it in offline mode:
That button in the popout panel, or you can always do Ctrl+Shift+A as usual and start typing what you're looking for!
There is very awkward thing I am facing. Logcat is shown in debugging application, but while running (not debugging) application, it is not showing Logcat.
I tried restarting it but nothing is happening.
In my case in Android 2.2, for some reason, Firebase was selected by default in the dropdown box marked above. So logs didn't drop. I just needed to change it to No Filters. Then it worked.
I even tried restarting the logcat, that didn't work too. No Filters did the magic.
Hope this helps someone.
Edit:
You can as well select Show only selected application for logcat to show only the current debugging process, i.e your app.
You may be hiding it, try pressing Alt + 6 to open Log tab.
Look at the log level:- it must be verbose.
Restart adb.
If that doesn't works restart the android studio.
In Logcat window reselect your device then reselect your app
if it didn't appear restart adb using two commands:
adb kill-server
adb start-server
Besides what other guys said, look if you have written something in the search box that causes this problem(it was my case).
Note: Even in case of a restart, what you have written in search box won't delete and you need to delete it yourself.
Try the following Steps:-
Step 1.
Goto File > Invalidate Caches and Restart > Invalidate and Restart.
Android Studio will restart automatically and logcat will work as expected.
Refer screenshots :
Step 2.
If Step(1) didn't worked then try this :
Goto Terminal > cd till your platform-tools directory (eg. in Windows default location is C:\Users\\AppData\Local\Android\Sdk\platform-tools).
Now type following command :
adb kill-server
adb start-server
Step 3:
If Step(1)&(2) both didn't worked then simply try clicking on Re-Start Logging button available in Logcat option. Refer screenshot - (Green colour curved arrow with grey box)
For real device, not for the emulator:
The only thing that I did was unplug the USB cable then plugged it in again. And it worked.
First, my problem: I was testing an app on a Samsung Galaxy A3 attached via usb cable. I was getting the usual logCat messages, including the filtered ones then all of a sudden the logCat stopped displaying filtered messages. Setting it to Verbose displayed a continues stream of messages with a message at the top left corner of the logCat stating "too much output to display".
I tried restarting Android Studio (with and without clearing the cache) but no luck. I then rebooted my phone and everything was back to normal. So it appeared that the attached phone was the problem, sending too much info to the logCat.
on The top left of logcat there is an option to choose the emulator. may it's not selected the current emulator by default. try to changing it to current emulator and it will fix.
Restart both the emulator and Android Studio.
I have solved this issue by enabling "Use libusb backend" option in Android Studio -> Preferences -> Debugger -> Android Debug Bridge (adb).
Helped restart the device (HTC)
I fixed the issue by changing the USB Options of my phone from "Charging only" to "Transfer files (MTP)"
You need to press Alt+6 twice to restart the logcat window. That way it'll show the log outputs.
Go to your sdk Folder --> Platform tools --> adb click 2 times
using this adb server restart again
Please check your Sdk Location My Location is d drive Please See This
In my case when select No Filters, I see
logcat: Unexpected EOF!
then I fixed it by:
adb logcat -G 100M
See Logcat crashes with error: unexpected EOF
I had this code:
Log.e(getMyName(),message);
The problem with this was, the variable that the getter method was accessing was null. Android Studio did not give me any error about it! Seems this was silently not letting the Log.e statement to work. I checked many blogs but couldn't find the solution. This small miss wasted my complete one hour. Hope this helps someone.
I tried to switch "Extended log" in my device settings from "Selectivly" to "Allowed" and it helped. Now debug info appears in LogCat.
I had the same issue, and I resolved it by the following actions:
First, open the terminal in android studio and navigate to the following path:
C:\Users\user_name\AppData\Local\Android\Sdk\platform-tools
Second, enter the command: adb reboot.
It takes about 2 minutes, but now logcat is functioning again and showing every logcat.
This problem appeared after reinstalling (changing) GitHub in Android Studio.
it happened when I connected the GitHub Desktop (git.exe) to the Android Studio. And right after that logcat fell.
Solution: commit + push = fixed logcat))
I did not understand how it works, but it is a fact
I had the same problem. I tried killing and restarting the adb-server, but it didn't help. I deleted the debug apk of the app in the path:
<your_app>/<your_app>_app/build/outputs/apk/debug/
And run the project again. It solved the problem for me.
If your app has crashed, there is a dropdown that has 2 process, you have to select the other process that is dead, so you can see the error message:
A better approach (for ADB wifi and USB both )and it Always works Magically!
First, run the app:
Then stop before it launch the app:
You have to stop as soon as the red stop button becomes red from gray (which happens after Gradle build complete). In this way, you will start seeing logs, errors everything in the run tab. There is no need to unplug and plug USB. No need to restart ADB server.
Make sure you repeat this process until you see the logs (usually takes 1 or 2 repeats) (One request - Please upvote)
Second Master Approach:
In your emulator or android device, launch the app manually and close it manually. Then launch it from android studio.
I had the kind of issue the way which got me the logcat to work was that I was not choosing the right filter. as I was using SQLite (Database) and in filters I had chosen Firebase.so that's why my logcat was not working.
Check you don't have something in the logcat search that returns no matches, for example a non existent package name.
I had renamed my packages, but left an old name in the logcat search field.
Result: No logcat output visible
Cleaning and then Rebuilding fixed it for me. Apparently when I ran, it wasn't actually rebuilding the APK, just running the one that had already been made.
I tried all steps and debugging just to find out that I had accidently typed a space in the filter.
Make sure that in your Logcat Windows a space is not chosen as a Filter.
There will be a search bar, keep it empty. It worked in my case.
Don't do anything, if you run app in emulator or device just uninstall and reinstall the app. Done.
Try restarting ADB using the below commands:
adb kill-server
adb start-server
Don't mark this as a duplicate. Let me explain what's wrong and tell you what I've done. So here's my problem. When I open Android Studio, it gives me an error like so:
So then I went to my windows firewall settings. Here is what I have:
As you can see, Firewall is off. Then, I went to my antivirus security program and turned the settings off there:
As you can see here too, I disabled Smart Firewall. Then, I opened Android Studio again. I got the same error here too.
I pressed the OK button and moved on. Then, Android Studio loaded up and everything. After that, ADB started loading. This is where the real error occurs.
I have also tried it with Eclipse, but it also says ADB not responding. For the past month or so, Android Studio has been working fine. I have never gotten these error or warning messages with Android Studio before, so this is rather new to me.
Here is what I have tried:
In cmd, adb kill-server then I pressed the restart button on the ADB not responding message
Restarting computer
Turning USB Debugging on and off on my Nexus 5
So, I really can't find a solution to this. Any help regarding this problem would be extremely appreciated.
Sometimes it just gets into a mess. Close your ide then Go to processes and terminate all adb processes.
Then when you open up android studio it should kick off adb again fresh (or you could run something like 'adb devices' from command prompt before opening the ide if you're worried it gets in to a bad state while the ide is waiting for it to initialize)
If none of that works you could also reboot your device. I've very rarely found it necessary, but it has helped me in the past
Kill processes bas_deamon & bas_helper Then press restart for ADB and it will work.... this what I do in WIndows 7 when I face this issue.
You may want to make sure your phone is unplugged. When it is plugged in, I have noticed this happening and the solution for me (which may be Mac specific) is to unplug my phone from the computer.
I had the same error messages, but a different problem.
Port 5037 was not in use, but still adb couldn't start.
So after hours of trying I finally realized, that it was an installed VPN-client (Checkpoint Endpoint Security). Even though there was no connection (and I even killed the process) the connection didn't work. After uninstalling everything worked like a charm.
Maybe it helps someone who reads this question, because everywhere else you just read about the blocking port. And in addition, while the client was installed some other TCP-based Frameworks and even Windows-Remotedesktop stopped working too.
This happened to me as well. I solve it by terminating all process that is using port "5037" which is, by default, the port used by adb.
Sir,
Actually Sometimes our parent control software interfere with it. but after turning off its real time protection , we got this error. so basically you need to check the whether we are using 32 bit Android Studio or 64 bit. just try to av same bit operating system as of Android Studio , u ll get this error removed after that. :)
For Windows: add a system variable as following and then restart your Computer then try again - it will be OK
ANDROID_ADB_SERVER_PORT
10501
I had the same problem on Mac OS X. After some research I've found a bad entry in my /etc/hosts file for my localhost (192.168.99.100 localhost).
I removed the bad line and left the line 127.0.0.1 localhost for ipv4 and some entries for ipv6 in.
After a reboot the Android Studio was able to communicate with adb and found my connected Android device again.
I am new to java and android and wanted to see how developing for android works
I started by downloading the SDK FROM HERE
However after I finish making the Hello World project sample given in the website HERE, if I try to run it on the emulator as explained HERE, the emulator screen appears, but nothing seems to happen. I can see the word android on the middle of the screen with some animation happening, but that's it. The website says something about unlocking the emulator, but I have no idea what that means. What I have gathered from reading other posts is that the emulator is supposed to have some kind of slider switch as in real smart phones which should be dragged to unlock it, but I can't see it in my case. Now I have no idea why this is happening or what I should check out in order to fix this. Are there any installation logs or something else that I can check to see what the settings are?
What I have tried till now:
I downloaded the SDK ADT bundle from HERE and just unzipped it. Then looked for eclipse.exe and ran it directly. Is there anything else I should have done prior to this?
When I did it for the first time, I had only JRE installed and not JDK, which I realized after reading THIS POST. So I downloaded JDK from HERE, updated the required environment variables and restarted eclipse, but still it's the same thing.
I looked at the Eclipse isn't talking to the emulator section GIVEN HERE, but all it says is to restart eclipse and the emulator, and it doesn't do anything at all.
Rant:
I can understand if the program had failed to compile when I didn't have JDK , or if the IDE gave any indication at all of a faulty program install, but that isn't the case. Everything seems ok, there are no errors, but it just doesn't do anything. This is the type of thing that makes people pull their hair out, and personally, I think the With a single download, the ADT Bundle includes everything you need to begin developing apps: in the android website is very misleading, especially for complete beginners
Anyway, what should I do to make the tutorial program run on my computer? My computer is a bit old and slow so could that be an issue? My computer is Windows XP SP3 on Intel(R) Pentium(4) 4 CPU 3.20 GHz 3.19GHz 2.50GB RAM, but if that was the case I assume the emulator shouldn't even start up
You just have to wait a bit longer. Android loads pretty long on emulator.
Tutorial says about unlocking, because when Android is loaded, your screen on emulator will be locked.
If you find emulator too slow for you, you may want to check this topic out: Why is the Android emulator so slow? How can we speed up the Android emulator?
I had the exact same problem as you when I first got into Android development a week ago. The two things I did are simply
1) Set the usable RAM on your AVD to 768MB
2) When you run your Hello World program in your emulator, give it about 5-10 minutes. Don't touch or click the window at all, just let it load up. Later you can make it persist
3) If your home screen comes up, click and hold the mouse button in the center of the screen, then drag towards the sides and release, this should unlock the device.
Try these steps first, if they don't work then there is likely a problem with your AVD configuration.
If you are launching your app first time with emulator, it will take appropriate time.After that, on Lock icon click and slide to the right. then you can view you application. If not check for your app(icon) installed.
By seeing your configuration of PC I think it will take some time to load emulator. After emulator is load (see below image)
then and then run your code and also check in eclise-device that whether emulator is online or not.
For checking emulator in eclispe :
In second image just above windows logo you can see small rectangular button with plus sign click on that you will get list from which you can select devices. You can find similar button in you eclipse at the bottom.
I had the exact same problem and followed the exact same steps, but was also unsuccessful. I ended up creating a new AVD with a Nexus 4 instead of the latest Nexus 6. The resolution of the 4 is much lower, which I think is what solved my problem. It loaded much more quickly using the 4.
Also, When I was using the 6, I could only see "ndroi" because the size of the screen was much larger than the size of the phone. Now I can see the full device.
vs.
You may just need to relaunch the Android studio 3.6.3.
I got a similar problem. The hello world app does not install on the emulator.
Problem solved after relaunch.
I have seen this problem off and on while running the Eclipse (Galileo) under Fedora 11-13, whether the target is my device or an emulator. But now with my new device, the HTC T-Mobile G2 (Android 2.2), I see it much more frequently: I successfully download the app (complete with lots of Log.d() calls), the system successfully launches it, but the LogCat pane in the DDMS perspective is completely blank.
Sometimes, only sometimes, I seem to be able to kick it into action by clicking on the tool for Debug (the little bug one). But that doesn't even work all the time. Worse yet, it forces me to restart the whole program, which is very cumbersome.
And yes, I did remember to connect the device and make sure the device shows up under "adb devices", AND make sure that is the device the ADT downloaded to. I can even hit breakpoints in the code.
I suppose I could try relying only on the debugger, but I put a lot of work into writing those Log.d statements in the right place, it would be a giant leap backwards to do without them now. So any suggestions concerning what the problem might be, workarounds, or how to find relevant bugs logged against either ADT, SDK or the G2, would be welcome.
TIA
PS: Google searches such as "android ddms logcat" have not helped so far.
PS: I have also considered running ddms from the commandline, but the instructions on how to do this wtihout conflicting with the port already chosen by ADT for running DDMS are not clear enough to inspire confidence: so I always quit Eclipse before running the command line version of ddms. But then I lose the handy ability (provided by Eclipse) of navigating my source code while reading the log, so this too, is an inferior solution. Perhaps if someone can connect a few more of the dots in Google's instructions on this by explaining how to get the device and command-line DDMS to agree on a port while still running Eclipse, that would be a good solution.
Just to suggest the basics, when you click on the DDMS tab, is the device listed on the devices tab? (If devices isn't there, click Window->Show View->Devices) If it is listed, have you clicked on the device (on the name column). Sometimes if the device isn't clicked on it will not show the logcat.
If it is and you have selected the device - try clearing the log (the icon of a page with a red cross at the bottom right corener of it - located at the top right of the logcat panel) I find if I have had it running for a long time it sometimes fills up and stops displaying the log, although normally one line is shown.
It seems that ADT looses the connection with the device or is not re-connected when you reboot the device or emulator.
I've found that if you have more than one device or emulator you can click on the other one, click on the empty log window and the logs for this other device appear, then click the device that lost connection and will be re-connected.
Yes, sounds like black magic, but it's all we have...
It worked for me when I did following.
Remove the connection to the device (i.e. unplug the USB cable), then restart Eclipse. Next time it starts, you can see the LogCat is back on action writing logs.
Hope this helps.
I have experienced the same problem on and off.
Basically the logs were coming on console using "adb logcat" but not in the logcat view of eclipse. I've noticed that restarting the emulator , then restarting the eclipse and then relaunching the emulator from eclipse gets rid of this problem.