When I press run and choose the device (I'm using Genymotion) it says everything went right but nothing shows up.
I also get this error message.
What should I do?
On your device go to Settings > Application.
Probably you have the app still installed for other users.
Try to find it and remove the app for all the users.
If the problem is this one you will find that app at the end of the list (in Settings > Apps > All)
All the apps marked as Not installed are still there, you can not install the same apps with Android Studio until they are there
NOTE: I haven't already had this problem personally, but I think if you click Yes in that dialog menu it should automatically remove your app/
If not, please try to follow above steps.
Hope it help
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
I am a java beginner. I am going through a book right now actually called Java in 24 Hours sixth edition by Rogers Cadenhead learning java and android programming. Anyways, to my problem. I am using eclipse to make a simple app and I want to transfer it to my galaxy s 2. I am ready to debug it and pick my device.... except its not there. I have installed Kies, the drivers, made sure its in USB debug mode but it will not recognize it. Any suggestions? This is not a duplicate! It is different because even though its in debugging mode, even though Ive reinstalled kies twice, even though Ive made sure the USB port or cord is not a problem it still does not work! But whats strange is my My Touch will work perfectly with the app. What am I missing here? HELP PLEASE.
You are most likely having a problem with the adb in your platform-tools folder. It is the android device bridge. Go to the android-sdk folder and then go to platform-tools and inside you will see adb. Press shift + right click anywhere in an empty spot of that folder and click on 'open a command line here.' Type: adb devices. It should show you a list of usable devices. If that doesn't show your galaxy (it will be a big number/letter sequence like: 3ANIWRN42408) or anything than try adb kill-server then adb start-server. And then see if adb devices shows your device.
If that is hard to follow, check this out: adb/usb tutorial
I'm just getting started with Android dev, done a few tutorials, now I'm working on a simple app. On both the emulator and my phone (Android 4.0.3 emulator, Android 4.1.1 Atrix HD) apps are displaying in what I think is Holo Light. I'd rather have it be Holo Dark, but when I add the following line to the application block in the Android Manifest file: android:theme="#android:style/Theme.Holo" the app compiles fine but force closes as soon as I open it.
What am I doing wrong? I'm sure it's something really simple, but as I said I'm new to this. Thanks in advance, y'all!
If you want to use a theme for all the activities of your application then you need to use
<application android:theme="#style/CustomTheme">
in AndroidManifest.xml.If you want a theme applied to just one Activity in your application, then add the android:theme attribute to the activity tag instead.So need to know what type you use in your application.However see these things which will clear you more..
http://developer.android.com/guide/topics/ui/themes.html
http://www.androidengineer.com/2010/06/using-themes-in-android-applications.html
The simplest thing you can do and you should always do is to read logs why does it crash. The log will tell you the reason of you crash. Please post the reason including logs from Logcat and only then ask about fixes:)
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.