I have read many of the posts for logcat not displaying in Eclipse and so far nothing has solved my problem. I have two installs. Logcat in Eclipse installed on my windows laptop works, but on my Linux Mint laptop those same programs will not display in logcat and not just with my log command in the program, but nothing shows - not even a trace.
The command line options of using adb logcat shows the logs just fine. It just won't show in the logcat window in Eclipse.
I have made sure the emulator is selected on the device tab, I have reset adb, I have restarted eclipse,Under I made sure "Monitor logcat for messages from applications in workspace" was checked and selected "VERBOSE".
I don't have any filters set.
Any ideas on what to try next?
I have had other problems with this linux installation that I had to fix. For instance, the default Google Eclipse/Plugin Bundle had some bugs. Some of which were solved with a new version of Eclipse and some were solved with a new version of ADT.The version of ADT also had a bug that would not let you upgrade it through Eclipse. So, I removed that bundle install and re-installed everything manually:Eclipse 4.4, then installed the 4.4 plugin and the various build tools and API levels and extras I needed. That solved some of those bugs.
That left the logcat issue and one major bug. Eclipse would freeze-up when the android auto-complete pop-up would display. On a hunch, I decided to run Android-Studio to see if it had any freeze-ups. When I started Studio, it warned me that I was using OpenJDK and it has known GUI performance problems and hangs. It gave a message that it recommended that I install the offical Oracle JDK, which I then did. That solved freeze-ups and hangs on Eclipse with the Android auto complete popups.
Now just this one problem left to solve - on my Linux environment, making logcat within Eclipse wok. Any suggestions are appreciated.
Related
Android studio pops up error message as soon as running the IDE.
As suggested by others, I have done followings and still see the error message.
Kill all adb processes
Developer option turn off and on again
Revoke USB debug authorizations
Manually starting the adb server does not work, it seems having conflict with Android Studio as the IDE tries to initiate its own adb.
One thing I notice in the Task Manager is that as I start the Android Studio, two adb processes get initiated then I see the error message above..
New update(March 24th, 2017): just found a thread talking about this after spending 3 days on this issue...really Google!#?
Issue 258400
Whoever stumbling upon same issue, to make a long story short, the latest version(25.0.4) has bug with Windows 7 Issue posted in Google Android.. (as of March 24th, 2017).
Just revert to 25.0.3 and adb.exe runs fine.
Since yesterday, my android studio emulators don't start. It was just after i updated Android Studio Library, i don't know if it is just a coïncidence.
What happens when i press start is:
The emulator command is executed
I see emulator.exe process in windows task manager, but no window is opened
Before that, the emulators started just fine, i had no problems, so it shouldn't be hardware issues.
I tried to launch it from the command line, to see if there were errors, but there's nothing. I also checked android studio's logs but still nothing... I also reinstalled completely android studio with no effects. I also tried to let it run for awhile but nothing appears.
Does anyone have a clue about what could cause this ?
EDIT :
It was a known issue (GPU related) of the SDK Tools 25.1.1 , it has been updated about 5 days later and now it works perfectly.
I had exactly the same issue.
Removing C:Windows\System32\Wbem from system PATH variable helps me:
https://stackoverflow.com/a/36650430/1901621
I m facing a problem whenever i m running my application . it says Failed to start monitor thread and : adb server didnt ack.
I tried every possible way but it served no purpose.
Here are the following steps i did to solve it:
I opened task manager and killed adb and then restarted ADT.
in the command prompt i killed the running adb server then restarted it.
in the DDMS i tried to reset the adb but it says Plugins are not configured properly.
I have properly set my path even though these problems are popping up.
I think there is not any device issue as even my emulator failed to start.
sometime on restarting the adb server error comes as `daemon still not running"
kindly help me out...
What version of ADT are you using?
If you've recently updated the Android SDK, but haven't removed and reinstalled (from scratch) Eclipse, then that' likely the source of the problem. When Google released the newest version of the SDK, they seemed to have messed up ADT updating.
Removed ADT from your computer (you can leave the SDK Manager installed) and reinstall Eclipse from http://eclipse.org/
Once you've reinstalled Eclipse, follow these instructions to get your ADT plugin working: http://developer.android.com/sdk/installing/installing-adt.html
I upgraded to the latest android studio and as ever it breaks what was working fine before.
If I plug in my android device I can see debug in the debug monitor, it gets detected and i can select it as a device to deploy to, then I get
Waiting for device.
Target device: xxxxxxxxxxxx
and nothing else happens.. VERY frustrating. Anyone any ideas on how to resolve?
Here is the resolution:
The problem is the way i installed the newer version of Android Studio. Do not install it over your previous installation directory. Create a new directory and move over your SDK into it. This is how I resolved it.
The only error I was eventually able to get from Android Studio was if i tried to run a test I'd see
NoSuchMethodError: com.android.builder.model.AndroidArtifact.getOutputs()Ljava/util/Collection;: com.android.builder.model.AndroidArtifact.getOutputs()Ljava/util/Collection;
there has been some other posts referring to this issue. Just make sure you do a clean install and don't crap over your older version.
This issue on the AOSP bug tracker tells you what is going on. A quick fix is getting rid of builder-model-0.11.0.jar from plugins/android/lib in your Android Studio folder. A patch has already been submitted and this probably won't happen again with the next update.
I am running Eclipse Juno on Ubuntu 12.04 64bit with the ADT Plugin. I am working on an app for android and I can develop just fine, but whenever my app throws an uncaught exception while debugging, eclipse freezes and I have to force quit the program and restart again. This makes determining the bugs in my app near impossible because I can't even get the stack trace for the exception.
EDIT:
It seems to work sometimes, and I have noticed not discernible pattern as to when eclipse hangs.
I had exactly the same problem when trying to debug on a windows 8 workstation and the regular Android ADT bundle. I solved it by NOT using the standard ADT bundle. Instead I downloaded the latest eclipse (4.3.1/Kepler) and installed the SDK and eclipse plugin manually using the instructions from http://developer.android.com/sdk/index.html called "Setting up an Existing IDE".
So at least is my case the problem seemed to be Eclipse Juno version. When moving to Eclipse Kepler it worked.
Change the preferences of Android->LOgcat->Max number of logcat messages to buffer to '5000'. That should solve the problem.
[Update] You can also hit the [x] clear button on the logcat to clear all recent logcat messages.
Good luck!