Android Studio Dolphin logct log table new version features and old version recovery
The log platform has been updated in this version. This article briefly summarizes its new features and usage methods as described on the official website, as well as how to restore the logs of the old version.
Restoration of the log table of the old version
If you are used to the old version of the log console, you can press the screenshot below to enter the Setting setting item, turn off the option to enable the new console, and restart Android Studio, so that you can restore the old version.
After restarting as follows, the old version of the console is restored, but there are always reminders. If you want to know some usage methods of the new version, you can continue this article to learn about the new features of logcat.
Features of the new version of the log table
Added formatting functionality
Logcat now formats logs to make it easier to scan for useful information (such as tags and messages) and to identify different types of logs (such as warnings and errors).
Create multiple Logcat windows
You can now create multiple tabs in Logcat to easily switch between different devices or queries. Right-click a tab to rename it, and click and drag to rearrange tabs.
Additionally, to help you compare two sets of logs more easily, you can now split the view within a single tab by right-clicking on the log view and selecting Split Right or Split Down. To close split screen, right-click and select Close. Each split screen allows you to set up your own device connections, view options and queries.
Switch between view presets
Logcat now allows you to quickly switch between different view modes, including Standard, Compact, and Custom. This is done by clicking
(view mode selector). Each view mode provides different default settings for showing you more or less information, such as timestamps, tags, and process IDs (PIDs). You can also customize each of the default view modes as well as custom view modes by selecting Modify View.
Track app crash/restart logs
With the new Logcat, you can now more easily track app crash and restart logs before missing important logs for these events. When Logcat finds that your application process is stopped and restarted, you'll see a message in the output (such as PROCESS ENDED and PROCESS STARTED) like this:
Added key-value pair search
In previous versions of Logcat, you had the option to use string searches (with support for regular expressions), or you could use the Logcat interface to populate fields to create new filters. The first option makes searching more complicated, the second makes sharing and setting up queries more difficult. We've now simplified the experience by introducing key-value searches directly in the main query field.
With this new query system, you can query exactly what you want without using regular expressions, and you can undo previous queries from your history and share them with others. Also, you can still use regular expressions and exclude logs based on key-value pairs. The following example shows how to use the new query system, but you can also type directly into the query field to see related suggestions:
PID of local application project: package:mine (use local package name)
specific value:
- package:
<package-ID>
(package name) - tag:
<tag>
(the tag of the log, which is the prompt on the left line) - level:[VERBOSE | INFO | ASSERT |DEBUG | WARN | ERROR ] (corresponding to the original log level)
add - in front of the key to exclude specific values: - tag:
<exclude-tag>
Add ~ after the given key to use a regular expression on it: - tag~:
<regular-expression-tag>
- Used in conjunction with exclude tags: -tag~:
<exclude-regular-expression-tag>
You can also view the history of queries by clicking
(Query History Selector) in the query field and selecting from the drop-down list. To favorite a query so it remains at the top of the list across all Studio projects, click (Favorite Queries) at the end of the query field.
Log Desk Appearance Settings
At the same time, we can go to the setting item to set the appearance of the log platform. There are also some reserved themes to customize the log line color and foreground color corresponding to the specific level. At the same time, the output value can also be customized for the specific
corresponding position. definition