sometimes when i work on android in eclipse the logcat output just seems to output the last line of messages and discards everything before.
this usually happens after 30mins of work but i cant find a concrete way to repro it.
any hints? thanks!
The eclipse DDMS buffer is unnecessarily small. You can click the clear log button and it will start showing the log again. I'm not sure if there's a way to increase the buffer or not. I always look at the logcat in the terminal. Here's a really good python script that adds color to the output.
http://jsharkey.org/blog/2009/04/22/modifying-the-android-logcat-stream-for-full-color-debugging/
Sometimes your device becomes unselected in DDMS. Next time you have this problem, open the DDMS perspective in Eclipse and re-click your device in the devices window.
That usually does the trick for me.
Related
This is the most frustrating thing ever, LogCat keeps deactivating/disconnecting. After running eclipse, LogCat logs for first run and after that, it goes Blank. I have to restart Eclipse to get it running again, and then same thing happens again. What is matter with it? It used to work fine. I can't recall changes I've made to undo what I (might) have done.
EDIT - Screen of Eclipse as requested.
EDIT 2 - Screen of currently installed SDK packages
If the LogCat is empty, the emulator doesn't have the focus. Go to the DDMS perspective and try clicking on the 'emulator' entry in the Devices panel (top-left screen).
Same thing with a device. You just have to click on the entry representing that device and the log messages comes.
I believe this other post with the same problem will answer this:
https://stackoverflow.com/a/11967853/241014
Essentially, set the log's buffer to a higher value by going in Eclipse to Window > Preferences > Android > LogCat. Set the "Maximum number of logcat messages to buffer" to something higher than the default of 5,000.
Most of the time Rahuls method would work, but sometimes even that doesn't work in that case, Kill the ADB and restart the eclipse.
For Eclipse only when LogCat isn't working:
1 - Open Perspective "DDMS".
2 - On the left side, click on the device you want to monitor.
3 - Change Perspective back to "JAVA".
In case if you are using cynogenmod in your mobile, try this:
In your device, open "/system/etc/init.d/" folder
If there are many files, try opening each file and find for this line:
rm /dev/log/main
Now, comment this line like this: # rm /dev/log/main
save the file and reboot.
If you close LogCat and re-open it it will display the information.
Although this question has been asked long before, I am answering for others who might stumble upon this trouble.
In Mars, eclipse 4.5 and linux using GTK 3, if Android Logcat display is missing, add the following in eclipse.ini before "--launcher.appendVmargs".
--launcher.GTK_version
2
May also refer these posts.
Logcat show invisible messages in Eclipse Mars
Eclipse GUI broken
My logcat is behaving very strange. If I have started or restarted the eclipse it is showing the logcat values but once I clicked any option For example Allmessages(nofilters) or com.applicationname(sessionfilter) then suddenly logcat is getting empty. I am not able to figure out what is the problem. This problem started once I updated my ADT to 22. Can any one please tell me what is the problem and how to solve this
Thanks
1. If you are using Eclipse, in the DDMS perspective, make sure the correct device (probably emulator-xxxx) is selected and highlighted. Only then will you get the logcat output in the logcat view.
Also, the Android plugin is a bit unstable, and sometimes only shows the last line in the logcat view. If this happens, try to clear the log. After that, you should get all the log entries again.
2. However this sometimes happens also, when you have Mylyn installed.
http://code.google.com/p/android/issues/detail?id=1808
3. If the LogCat panel is empty in Eclipse the emulator doesn't have the focus. Go to the DDMS perspective and try clicking on the 'emulator' entry in the Devices panel (top-left screen).
In my case, it usually takes 20 or more seconds for my logcat to display anything. After it does, I see "debugger waiting to settle" messages. This happens every single time.
Try waiting a while to see if it ends up showing up.
I have got a problem in my logcat screen and the problem is that,whenever I get error from my application I get blank screen in logcat and I am unable to look at the errors and fix them.How do I overcome this sort of issue?
here is my logcat screen:
Update your ADT plugin in Eclipse and right now you are using deprecated Logcat.
Help > Check for Updates
Go to DDMS->Devices and select the device that you are currently working on.
Just Try this command:---
adb shell
echo 1 > /sys/kernel/logger/log_main/enable
I run into that problem sometimes and I suggest:
Make sure you select the "V" tag to prove that why this happened is not because there is really no errors (Since you select the "E" tag).
Install the USB driver from the manufacturer of your device. Although you can connect the phone to PC as an USB storage device without the driver, you can't debug on the phone without it.
In Settings->Applications->Development, check the USB debugging choice to allow you to debug on the phone.
Make sure you have selected the proper device or emulator, not some other emulators or devices.
Sometimes, the logcat shows nothing, even if you have finished these steps above. In this case, click the "Clear" tag(at the top right, with a RED cross), unplug the phone and plug in again.
you have 3 things to do..
start emulator...
then see devices select your avd like Windows-show view-other-android-devices...
then start logcat Windows-show view-other-android-logcat..that's it and it will do..
But First you should see the emulator in devices..
If you can't then in devices click down arrow near camera icon and click on reset adb.
I ran into this issue in the Android Debug Monitor today. The reason this happened to me was because I had set the "maximum number of logcat messages to buffer" under Preferences/Android/LogCat to some very large amount like 50000000000. If you have played with this setting try setting it lower to like 5000. Once I configured mine back down to 50000 I started seeing messages come through LogCat again. You may have to restart things like the Android Debug Monitor, adb, the computer, the emulator, or the phone. At one point or another I tried all of those. Also you should see an error message when you try to configure this setting back to default. I believe it was a Java Null pointer or something. You can safely ignore the message and just check that the configuration worked when you go back into the Debug monitor. Good luck!
Although this question has been asked long before, I am answering for others who might stumble upon this trouble.
In Mars, eclipse 4.5 and linux using GTK 3, if Android Logcat display is missing, add the following in eclipse.ini before --launcher.appendVmargs
--launcher.GTK_version
2
May also refer these posts.
Logcat show invisible messages in Eclipse Mars
Eclipse GUI broken
The log tab is visible in DDMS and I have been logging data using Log.v(...) for many a week now without any problems.
Today, the log data is now longer being displayed in the Log window. Worked, then did a programming change to track a bug and now the log data is no longer showing.
Have tried running the app on an external Android phone, on the Android Simulator and it makes no difference.
Have closed down Eclipse, reloaded and still no change.
The console displays activity but only to the point of starting the activity.
The external phone is set up for debugging - not that this could be a problem since I have the same problem with the simulator
It looks like I have inadvertantly set something incorrectly but can't remember changing anything :-(
Anyone come across this problem before - have looked at previous posts but none seem relevant.
Regards,
Oliver
I had the same problem a while back. I was using the emulator and device for debugging. Apparently you have to select the device listed in the DDMS view whose logs you want to see. My logs were blank because the device that I was expecting logs from was not the one selected.
Hope that helps
Tried this:
https://stackoverflow.com/a/9826502/1238317
Check in your logcat window - TOP RIGHT corner PAUSE button || (Pause
receiving new logcat messages)
Few clicks + eventually restart eclipse (usually works in my case)
Check your LogCat window to see if you are filtering and make sure to set the debug level to Verbose.
There are possible reasons and solutions:
LogCat might have to much in cache, clear the log and see if it fixed the issue
You might need to select the device in the device view (even if it is already selected, try to click on it)
adb is not correctly working anymore, try to kill and start it again
Check if you see output if you use the command line adb logcat
Just go to DDMS perspective and click on the device's name in upper left corner and done your log cat will Start with a BOOm :P
In Android Studio, which I have found to be much more reliable and intuitive than Eclipse, I found this to be a common issue. For me what solves it (device is automatically set when running your app) besides checking code, is to Quit and restart the emulator or Quit Android Studio and Emulator and reopen/restart
Periodically LogCat will stop showing messages even though I am in debug mode. At other times it will display only one line at a time! I have a solution, restart eclipse. But I would like to understand this better. It takes too much time to restart eclipse when this happens. I have seen this behavior on the emulator and connected to a device. Either the LogCat shows one line with no history or nothing.
I was with the same problem and the solutions here didn't work for me. The solution I found is open the DDMS perspective and select the device and the running process on the Devices window. With that done, the LogCat returns to life.
Yes, I can get the normal logcat back by clear the log. Also I uncheck the "Limit console output" in Run/Debug->Console.
I solve these LogCat issues in two different ways:
Clearing the log to fix the one line at a time issue
Opening the devices window (Window -> Show View -> Other -> Android -> Devices), and clicking on the device that I want to view the log for. This seems to force Android to refresh LogCat on that device.
These are much easier options than restarting eclipse, or messing with adb.
I've had that "one line at a time" problem numerous times. I don't know why exactly it happens but there is a very simple fix that works for me every time. Just hit the clear log button. Simple and easy.
I've also had Logcat fail to show messages. Generally this has been due to a problem with the emulator and it required an emulator restart.
In eclipse you need to give more space to log buffer, default is 5000, i set it to 50000 and no have any problems.
Window->preference->android>logcat
maximum num of log message to buffer __ set some number 50k is ok
I'd recommend adjusting the Logcat buffer size and enable workspace application message monitoring in your preferences, mine are set as seen below.
On a real Device (mine is an HTC Desire in question) I've found simply disabling then enabling ADB does not always solve it. What works more often is to disable ADB, close the page (perhaps by back) then to renter the Development page, and re-enable debug mode.
Same here! What worked for me is open DDMS perspective and on devices pane I clicked
reset adb
Click "Display saved filters view" button By showing the two-pane view of your LogCat you'll be able to check the active filter in the left-pane. I once fixed the empty LogCat by selecting "All messages".
When logcat stops displaying log entries, I find that closing Eclipse and re-opening it solves the problem for me.