I'm using the emulator with Android Studio, and I'm experiencing the phenomenon shown in the image below.
The problem occurs only when the screen is turned sideways.
It does not happen in the default screen.
I don't know how to solve this problem, and I was wondering if you could tell me something that would help me.
Thank you very much!
You can solve this in three ways:
disable screen rotation - add this to the manifest XML under the relevant activity
android:screenOrientation="portrait"
If you want to go the long and better route it seems to me that you are using a layout that is not constraint layout, the latter supports rotation better, and when constraint correctly what is shown here should not happen.
If all else fails you can use special layout when the screen is in landscape mode, you can read more here:
Android Studio: Creating landscape layouts
Related
I don't know what's the reasons every time i try to design the screen become black i cant do any thing ( i used android studio 2021 dolphin )
i try to fix sdk tools and i done but i am not sure that the gradle file in its position in c desk
"One or more layouts are missing the layout_width or layout_height attributes" seems pretty intuitive, but if you still don't know how to fix that:
press on "Code" and copy all of the XML layout, then update your question with the code
I updated my Android Studio recently to 4.0 and now when I type code incorrectly, and I mouse over the red squiggly line to see what it expects or suggests, the tooltip appears and disappears very quickly. I can't read it. In fact, it's even harder now to get the thing to show up, it's very precise where the mouse pointer is. I've restarted everything including my computer. I've changed the tooltip settings from 700 to 2000 with no change. Anyone else have this issue and know how to fix it?
Thanks all!
I found the answer via this link:
Android Studio , tooltip disappearing so fast
Basically, put a bunch of random letters in your filter for Logcat and it will stop the messages, the tooltip will stay up. When Logcat is running it's interrupting the tooltips now for some reason. I think this must be a bug.
I'm learning Android Studio, so I clicked a few buttons to add vertical and horizontal guidelines, but how to roll back ? In the following image you can see how they look, but I can't figure out how to not show the guidelines ?
I figured it out, select it, make sure it turns blue, then hit "Delete" key to get rid of it.
Select the guidelines or just go into the COMPONENT TREE window below the Palettes and delete the guidelines you want.
I am new to android development. The mouse pointer on the design page is as shown in the screenshot. I am not able to edit anything like increasing the height and width of the widget on this page. I might be able to do it in XML but I want it done here.
I want a normal mouse pointer where I can edit the widgets.
I tried looking at some of the blogs but it didn't help.
activity.xml - design
It worked after removing the cache files and restarting the android studio
I've been experiencing some very strange behavours in an app I'm developing. The app is not very advanced, it stores a couple of places in a sqlite database and is displayed in listviews, on a mapview etc. So, when browsing through my app after deploying it to my phone everything works great, but after a while one listview doesn't get inflated. A scrollbar appears as if the items were there but I can't see them. I push the back button to close the app. When revisiting the app my first view, which has two buttons, gets all messed up. The buttons fill the viewport and the background disappears etc. I can't figure out what's wrong.
Anyone else facing these problems? My phone is a HTC Desire HD with Android 2.3.5
The app is pretty "layout heavy", if you know what I mean. The listview items has custom background images, I'm using custom fonts etc. But the app is running smoothly up to the point when it freaks out and displays/don't display everything wrong.
My first thought is there is some kind of memory issue, ideas?
EDIT:
I believe this might have something to do with defining and using #00000000 as transparent color. Use #android:color/transparent instead.
SOLUTION:
So after doing some testing I found that what I previously mentioned in the edit really is the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
After some testing I finally found the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
So to fix this problem you should use #android:color/transparent instead when you want transparency on, for example, a view background.
If there are memory errors you should be able to catch them in logcat. You'll get "VM failed on xxxx byte allocation" messages (or the like).
Silly/stupid answer: often when I run into layout issues within my app, it's because I needed to do a clean build after having changed my layouts. You might want to start there.
Edit: You might also try the emulator, and if you suspect memory issues you could start the emulator with a small heap to force the issue to occur sooner. You can also check your heap usage in DDMS or with the Eclipse MAT to see if it's leaking.
I was experiencing the same problem on Galaxy tab even with #android:color/transparent. Was able to fix it only by replacing android:background="#color/transparent" with android:background="#null".