Develop Reference

vs code intellisense results are just limited to 1

Whenever I am writing the code in VS Code, then the IntelliSense is only showing one option. Doesn't matter which language I use, I am getting only one suggestion for every language. BTW I'm working with flutter. (See the mentioned images)
Expected behavior
https://i.stack.imgur.com/CDW86.png (I can't
add images because of the less reputation)
Behaviour now
Right now I can only see the very first option in IntelliSense. Maybe I have messed up my VS code settings but I'm not sure. Any help would be greatly appreciated.

I just had the same problem, and this worked for me. Literally just expanding the results to show more than one. Let me know if this was of help.
https://code.visualstudio.com/updates/v1_51#_intellisense

You need to add extensions related to your working language.

Android Lots of skipped frame errors

I have finished my initial project but facing 2 issues while finalizing. If you kindly show me light
1) I am receiving lots of skipped XXX frame errors from Choreographer. I started looking one by one, then I realized some of them most probably have nothing to do with my code. For example, I explained here Android - Skipped frames message from Choreographer.
So, How can I know which LogCat choreographer messages I should be focusing on? Again, I am receiving lots of them, so it is very tough to check one by one which are real.
2) In my whole project, I only have one warning when I open and close menu tree without choosing any option. However, I guess it is also problem with emulator as explained here.
I am using Eclipse as my emulator.
Any kind of advice is highly appreciated.
Thanks,

A lot of skipped frames (probably) means you are doing too much calculations in the UI thread. If you are doing a lot of calculations, consider moving them into another thread, which might solve your problem.

You can hide the Choreographer outputs onto the Logcat view, using this filter expression :
tag:^((?!Choreographer).*)$

Logcat issues (pausing, buffer, output redirection)

I've searched around for everything that seems to be capable of affecting logcat, but I just can't find an answer to this problem. I'm debugging a large application that dumps several hundred logcat messages to screen per second. In Eclipse, I'm using a regular expression to filter by log tag, but this is where things get weird. The "pause" button keeps on activating for no apparent reason, and given the massive volume of new messages, before I can get the logs for the specific sequence of events I'm investigating, they'll be overwritten, a little at a time. I've even set breakpoints and tried to capture the logs bit by bit with the "export" button, but the app is multithreaded and they still disappear too quickly because of messages from other threads. It would be nice to increase the buffer somehow, or make old messages stick around, though at this point I'm willing to dispense with it altogether and just output it to a file, but I'm not sure how to filter by log tag using my regular expression from the command line. What are my options?
P.S. I have been looking around and I hope this isn't redundant--I haven't found anything specifically addressing my problem, though I have of course run across abundant related threads that don't quite help. Thanks so much!

I had similar problem to this. I was working on application which communicate to web server and download a huge amount of data. I had logs almost for every variable and I had to test them to see if the result which I'm receiving from JSON is correct. So the thing that I did was to log all logs on a file on my sd card and I did something like this :
public void log2File(String filename, String log, int type){
switch(type){
case 1: // debug
case 2: //verbose
case 3: //warning
//..and etc
}
}
I didn't find anything better for my solution, so that's the way which I did it.And of course you have to add your logs on a file and save it.
Hope this solutions seems good for you.

I've found the eclipse logcat window to be fairly buggy with high logging volume - it won't even stay disabled if you try to turn it off.
To actually capture the desired data, I tend to use the adb logcat command from the commandline. On linux, or presumably cygwin or osx you should be able to do:
adb logcat | tee logfile
And both see the messages flying by and have them recorded to a file.

I know this question is old but I had the exact same problem as you. I looked everywhere for a good solution but did not find one that worked for me so I took to creating my own tool. If you are on a Mac you could use LogRabbit to do what you want to do. It could help solve your problem in two different ways.
You could use adb logcat -v threadtime on the command line and write the logs to disk and import that into LogRabbit.
The filtering mechanism should be plenty fast enough to handle the log volume you are talking about.
Have a look at http://lograbbit.com I hope this helps.

I need some info about forming my inquiries and questions, so I can get assistance

I just had a post flagged, and voted down. It wasn't even up for a minute and a moderator closed it. When some one has an app that is crashing, what is the proper info to provide, in order to recieve help. I just learned how to use some of the logcat features to help my diagnostics. What else could I provide?
(1) I have an app, and I believe I know what function is executing when it hangs.
(2) I have info provided to me in the debug window(I do not know how to interpret the info)
(3) I have logcat info.
Can someone help me with understanding what else I need to do? Getting my post closed, flagged, or voted down, before I can converse with someone is frustrating.
I have real questions, and can narrow them down, if I can get a few pointers.

Providing log cat info is helpful. I would only post the part of the log that is labeled as an error. You also need to be solving a specific problem. Don't just post a question asking why your app is crashing. Look up the line number in your logcat and ask why a specific line isn't working. If you don't know how to determine what line number the problem is on, I would suggest asking that, because locating the problem is a very important step in solving errors in android.

Any special Android deadlock debugging tricks?

I’ve been working on building a nice graphical selector for an Android project. Unfortunately, this selector is causing me lots of frustration due to a deadlock in the application’s UI thread. Parsing and rendering the various SVG layers that make up each clock is a relatively expensive operation. Locking up the user interface while doing these operations is clearly bad design, so I'm trying hard to give good feedback.
The selector consists of two columns, an image of the clock on the left and the name of the clock on the right. Using the standard ListActivity support, the goal is to show an indeterminate progress image in the left column until the clock layers have been loaded and rendered. At that point, the animated progress image is hidden and the clock image is displayed.
The implementation is simple in concept. The list adapter subclasses the standard BaseAdapter implementation to provide an implementation of the getView method. The getView method delegates loading of the clock’s image to an asynchronous executor service, keeping the user interface alive. When the asynchronous task completes, it posts a runnable to the UI thread to hide the progress indicator and show the image view. There is logic related to properly handling recycled item views as well.
While this is mostly working, I’m hitting a random deadlock condition that locks up the UI thread, usually resulting in an “Application Not Responding” (ANR) error message to the user. All of my attempts to diagnose and resolve this issue have ended with nothing but frustration. So far, I’ve tried all of the “standard” approaches to diagnose this:
Analyzed the traces.txt file generated by the ANR.
Unfortunately, the process never shows up in the log file.
Force-generated a traces.txt file using kill SIGQUIT pid while the application was still running. Again, the process doesn’t seem to show up. Instead, I see “W/dalvikvm(19144): threadid=4: spin on suspend #1 threadid=9 (pcf=0)” whenever attempting this.
Enabled kernel-level deadlock prediction, but it never showed anything
Attempted to use the standard Eclipse debugger to suspend the UI thread once it is locked up.
No big surprise that it did not work. Added lots of Log output trying to pinpoint the hang. At least from that logging, it doesn’t appear to be a hang anywhere directly in my code.
I even tried to use method tracing to see if I could figure anything out.
At this point, I’ve run out of good ideas on how to track down and fix this problem on my own. I've removed all synchronization in my code and I'm still hanging up, implying some kind of hang in the underlying platform code. Without a stack trace, I'm truly flying blind at this point. Can anyone offer any ideas?