debugging – Android Studio 3.0 – Logcat window can not show filter input control-ThrowExceptions

Exception or error:

I can not type a text filter in the logcat input text control on Android Studio 3.0.1, because it is too small.

My screen is big enough. I did an event switch to fullscreen but this did not solve the problem.

See the screenshot below.

Has anyone seen this problem? How do you solve it?

enter image description here

enter image description here

How to solve:

Try clicking on the setting (cog-wheel icon) inside the logcat window and select the windowed or the floating modes, and then try to stretch the window size as long as you can

###

This issue is regarding the resolution of screen size specially causing in windows platforms or desktop with small resolution.

(For windows users)

-If you have a slider toolbar set in left or right side set it to bottom.

-Check for resolution size that suits your desktop better.

-Update the windows graphic driver(Important) if you don;t see one in device manager better install it.

Note: I had the same issues for the slider toolbar(refer 1st point) set to bottom and now it works fine.

###

use CTRL+F in logcat to find or filter logcat. then a new search bar comes below to that bar you can filter there.

enter image description here

###

Actually the problem is with the device name, which is too long and due to this it squeezes the Logcat search. So to the solution I got for this name issue is to change the device name (whether its Genymotion or AVD). So to change your device name follow below steps :

For AVD : Go to Tools –> Android –> AVD Manager –> Select your device and then change the device name to shorter one.

For Genymotion : Open you VirtualBox –> Select your device and then Click on Settings –> Change the name to shorter one.

And other option is Right click on Logcat tab and then enable Floating mode. Then just resize the floating window so that the Logcat search can expand.

###

Android Studio 3.1-beta in the canary channel has solved this issue.

Large Enough

Leave a Reply

Your email address will not be published. Required fields are marked *