There used to be a "Tasks" tool window in Android Studio where I keep and manage the tasks I'm working on. It used to be accessible on the right side, next to "Gradle" and "Device Manager", but it seems to be missing from Android Studio Electric Eel 2022.1.1, after an update.
Is there a way to bring this tool window back?
Update: I've just realized that this is not a built-in tool window, as I initially thought, but a plugin installed from here: https://github.com/NLSurfMan/tasks - this probably makes it a bug in the plugin's code that causes incompatibility with the Electric Eel version. I should report it on its Github.
Related
Today I updated my Android Studio from the Arctic Fox to Bumblebee 2021.1.1, and I realized my AVD and emulator windows changed a bit. They were on separate windows, now they are on the right side-menu.
I windowed the emulator again to get the old style, but the mobile-phone on the emulator is not separated from the menu. In the older version, I only had the phone as a separate window, I didn't have window bars and side fillers that are marked on the picture below. How can I get rid of them and only get the phone instead of the whole window? I don't want it as "emulator window" but rather plain "phone".
If you want the old look in Arctic Fox, go to
File->Settings->Tools->Emulator and unselect "Launch in a tool window".
This way it will launch it seperately which is the same as in the old version.
For Mac go to Android Studio Preferences - Tools - Emulator and uncheck Launch in a tool window.
I upgraded to Android Studio Bumblebee 2021.1.1 and realized that I cannot fully control the emulator with the touchscreen of my notebook anymore. Press events on the touchscreen (like mouse clicks) are still recognized correctly, but when I swipe nothing happens in the emulator.
Unfortunately, I did not note down the previous version of Android Studio that I had installed before, but with previous Android Studio versions I was always able to fully control the Android emulator via the touchscreen (as if I was actually testing my app on a real mobile phone).
My Google searches did not show any results related to this issue. Does anyone have an idea what the root cause could be and if it is possible to fix it?
Disabling launch in tool window in Settings::Tools::Emulator fixed it for me (requires emulator restart to take effect).
Credits to YuriBlaise on reddit
After upgrading to Intellij Idea 2017.3 and to Android Studio 3.1 canary 6 I noticed the project tool window doesn't show the little lock icons next to files anymore.
This is very useful to have a bird's eye view on the visibility of each file (public, package protected...).
Is there a setting to bring them back?
Marco, please check this comment on YouTrack: https://youtrack.jetbrains.com/issue/IDEA-172513#comment=27-2150075
Older versions of Android Studio had a Refresh option in the layout preview in the IDE, but in v2.2 it has vanished. I am finding repeatedly that I update drawable bitmaps in the project with updated files, that new version is not reflected automatically, and I do not see the preview. Problems like this are so common with Android Studio, it's such an utterly infuriating IDE and so flaky, despite the speed it is advancing.
Where did the refresh option go? I can't believe I'm having to actually ask this, but maybe I missed it somewhere obvious!
Running Android Studio 1.0.2 for Windows
Using a new Blank Activity or Blank Activity with Fragment project (bug happens with both). Haven't modified anything in the code yet. Using API 10: Android 2.3.3
Often immediately, sometimes shortly after I drag or edit my first/any UI element into activity_main.xml, Android Studio freezes and I have to close the process in task manager to get it to close.
I notice that in Task Manager the Android Studio Windows Launcher is taking about 25-30% of my CPU while its frozen.
What's going on here? Any ideas?
....
I may have found a solution for this.
I theorized that perhaps it was just the windows display that was frozen (the visual rendering of the Android Studio program itself) and guessed that perhaps this was using a DirectX device to do the rendering of the Android UI.
I happen to have another app running on my computer that uses a DirectX device for rendering (SimpleJungleTimer, an app I programmed with a DirectX overlay for League of Legends jungle timers). After I shut down this app Android Studio appears to be working properly (not freezing when working with the UI anymore)
Ultimately it sounds like this is a bug with Android Studio itself where they don't properly kill / reload the DirectX rendering device when it is in conflict with another app's active DirectX device (something that the android studio developers should probably fix), however until the android studio developers fix this you should be able to get around this bug by making sure any other applications that might use DirectX for rendering are shut down while coding in Android Studio so that their DirectX rendering devices don't conflict with Android Studio's DirectX device.