After installing androidx86 on VirtualBox at boot android boot in CLI and after a couple of seconds I got a black screen, with a blinking underscore at the top-left of the screen, its keep blinking without any change, it wont boot the gui.
I have tried different installations following various guides on internet, but I got ever the same problem, I have also tried with Alt+f7 key combo and putting nomodoeset in boot option in grub, but nothing.
In all tutorial I have found online they always start the gui without any problem. But I got always the black screen after 2 seconds of cli.
Found a fix posted by Val at superuser.com:
I managed to solved my problem :
I just changed the display option Graphics Controller to VBoxVGA and enabled 3D animation.
Right click on the virtual machine you are looking to modify, and hit Settings
Navigate to Display, then make sure you are on the Screen tab
Set Monitor Count to 2 or more
Set the Graphics Controller to VBoxVGA
Increase the Video Memory to 128MB (choose the maximum amount available to you)
Related
I've been doing development with Flutter. I was using a real hardware but wanted to use an emulator. I set it up but there's this issue.
I usually put my apps in virtual desktops and I switch between them with Ctrl+Meta+[arrow keys]. Each of them have a special purpose, usually desktop 1 is for browsing, desktop 2 is for development and desktop 4 is extra (for testing UI apps and emulator in this case).
However, after I launch Android emulator and switch to a different desktop, it results in the issue seen below:
The red area you see stays unresponsive for other apps such as browser, VSCode etc. (i.e. does not respond to clicks). That area is where the emulator is on Desktop 4. And it also keeps showing multitouch tool.
It's a bit annoying so I wanted to ask if anyone got this issue and if they have any solutions.
Thanks in advance.
Environment
Kubuntu 20.04
AMD Radeon R7 240/340
Solution 1
I have, somehow in a weird way, found a workaround for this issue.
After having this issue, go to the emulator window and press the magnifying glass with a plus button icon twice.
After that, it will drop that weird multitouch state and it won't bother you even as you switch desktop.
Rebooting computer will result in the same bug, however, you have to do it again.
Solution 2
Another method that works is to simply resize the window. If you have a device frame on your emulator, you can simply hold down the Meta key and hold right click and resize your window.
Solution 3
You can also maximize the window. If you have device frame around emulator window, you can press ALT+F3, which opens up window options menu, then click "Maximize". This will get rid of it.
I'm trying to run a sample Xamarin app and I think my Android emulator is acting up. I've tried enabling Hyper-V, increasing the RAM, telling it to use the host GPU, launching the virtual device from the command line instead of the GUI, and double checking that I have the correct version of the build tools for the version of Android I'm attempting to run.
As a test I've just run the emulator by itself without an app and have discovered that it still shows a white screen even when it is apparently running, somehow. The first image is what I get when I press the Screenshot button. The second image is what I actually see on my desktop. It's been like this for over 10 minutes.
Any advice? I've been Googling like crazy and can't seem to work this out.
Have you tried simply changing the renderer?
Go on the sidebar menu, click the 3 dots>Settings>Advanced and try changing the OpenGL ES Renderer
I've gone through many threads in SO but I can't get an answer.
I did everything according to instruction. Twice actually. I chose both x86 and x86_64 for CPU type. haxm_check.exe is showing everything works. sc query intelhaxm also appears to report everything OK.
Performance I get: I have to wait for about a minute until a phone app opens and a minute again to get back to home screen.
My CPU is i5-3210M # 2,5GHz, So I don't think this is a problem to at least get a decent performance.
try lowering the device ram size.
so go to the AVD Manager and press the pencil icon for editing the device.
set it at 512mb first. then try again.
this is the only thing i can think of with the information you gave.
http://tinypic.com/view.php?pic=25h1i7q&s=8#.VcISK26qpBd
Apparently since I don't have enough rep points, I cannot upload an image, so you can find the image in the link above.
Whenever I try running the virtual emulator, the emulator will start and work properly, but there is no cross/minimize button available, which not only makes it hard to quit the application, but also makes it impossible to move the window around.
I have tried disabling host GPU but that hasn't helped either.
Any ideas on how to get this working would be greatly appreciated.
Proabably its hidden up there by your titlebar of the curruntly active window ,
One thing you can try is make it smaller by adjusting the avd size from avd manager in android studio. This happens normally to me in ubuntu
I am using the hello android tutorial and creating an avd through eclipse. When starting the emulator no image is used. It simply displays a black back screen with the word ANDROID in the center and a blinking cursor at the end of the word ANDROID. I have followed the steps to the T for installing the SDK, Eclipse, and the ADT. Even starting the emulator as a standalone produces the same result. Is there a step I am missing to get the emulator to load an android environment to test in?
How long are you leaving it before you close the emulator? In my personal experience I have found the emulator to take quite a long time (Even up to a minute, sometimes longer) to fully boot up to the home screen.
I'd advise waiting a little bit longer just to make sure you're not closing it before it loads.
Edit:
Also have you tried looking at the log to the bottom of Eclipse? If for some reason there is a problem in fully loading the emulator there may be some sort of error message posted there to keep you informed.