Android emulator boots, but shows black screen thereafter.
adb shell works, connecting to the emulated device and giving root access etc without an issue. I've googled everything I can think of, and tried all sorts of stuff. If you have a suggestion I haven't tried, I'd love to hear it.
Things I've tried:
Delete and reinstall Android studio (basicly, find $HOME | grep -i "android" | xargs rm -rf, though manually so as not to kill my projects)
X86, X86_64, and "armeabi-v7a" ABI's
Turn on/off using host GPU support/emulation
Changing memory amount (1.5, 2, 4GB)
Different API levels (21, 25, 26)
Rotate device's virtual screen to force a redraw
Remove hardware from virtual device (camera)
Creating fresh, brand-new flutter app to run on it.
(app doesn't run.
claims device is "offline" when I try to run it, despite having shell access and connecting with adb just fine)
Swearing a lot.
Phoning a friend.
Hardware I'm running on:
AMD FX(tm)-8350 Eight-Core Processor
32GB RAM
NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
Linux herb 4.15.0-42-generic #45~16.04.1-Ubuntu SMP Mon Nov 19 13:02:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Xfce4 (I hate gnome & kde and it's stupid useless eyecandy & bloat)
ZFS file system (2TB capacity 653GB w/ 256G Flash drive configured as cache/zlog)
Emulator DOES show the boot screen, either B&W "Android" or fancier google logo depending on the API level. After a few minutes, it goes to a black screen, and refuses to show anything else unless I cold boot it again.
HAXM is not installed. It's not only intel-only, but also windows/mac only, and I'm running linux on an AMD processor.
Related
No matter how I configure my system, Android Studio shows the "We have detected that your system can run the android emulator in an accelerated performance mode. Linuxed-based systems support virtual machine acceleration through the KVM. Search for install instructions for your particular Linux configuration hat KVM is enabled for faster Android emulator performance."
egrep -c '(vmx|svm)' /proc/cpuinfo gives 8
kvm-ok gives INFO: /dev/kvm exists
KVM acceleration can be used
grep kvm /etc/group gives kvm:x:108:currentLoggedInUser
How should I configure KVM correct on Ubuntu 19.10? And how could I tell if Android Studio is running the VM using KVM?
Thanks.
i had same issue, but the other way around. To make it work, first make sure you've enabled virtualization in the BIOS and added your username in libvirt.
Click cancel on the screen that shows Android KVM
Android Studio will offer you to two options. Choose the one "don't start the setup wizard" (not the recommended one), so it will take you to the welcome screen.
Start a new project as usual and Android Studio will say couldn't find the SDK.
Choose the libraries and emulators to download and the rest is the same as usual.
I had installed ubuntu 18 in my acer aspire. Then i installed windows 10 in dual boot mode. After installing the windows i can not access the ubuntu. The grub loader is not shown.
And there is no way to access my ubuntu.
I even tried to change the path of bootloader to ubuntu in cmd.
But no success. Please help me out.
check this link: https://askubuntu.com/questions/602602/cant-access-ubuntu-after-creating-dual-boot
"YOUR COMPUTER BOOTS DIRECTLY TO WINDOWS
This is a common problem and if you do not get a GRUB menu , re-installing or repairing grub will NOT HELP
Every BIOS is different, it might look like one of the following pictures:
UEFI 1
UEFI 2
Notice the "UEFI Boot Option Priority" or "Boot Option Menu" . Usually Windows is the default and Ubuntu (or as in the second picture elementary OS) will be an option.
Once you select Ubuntu on the UEFI boot menu you will then get a grub menu. You should be able to boot either Ubuntu or Windows from the grub menu.
Another issue that could make the system boot directly to Windows (without even showing the GRUB menu) is if either Windows took hold of the boot manager or after installing Ubuntu, the EFI partition was not properly configured for Windows. To solve this, simply go to Windows and open a terminal, then type the following (Need Administrative Privileges):
bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi This will configure the Windows Boot Manager to take into consideration the GRUB Boot Manager. This could still happen even after running the Boot Repair from within Ubuntu. So making sure that Windows reads the Ubuntu EFI partition will solve it."
My external monitor, connected via HDMI was working fine but now is not being detected (it says 'No video input'). I'm pretty sure I didn't make any changes to make it stop - it was working on the same setup yesterday.
I'm a pretty new linux user and also don't know much about graphics hardware and drivers. Appreciate any help, I'd like to understand what's going on!
I'm running Ubuntu 16.04.3 kernel 4.10.0-33
lshw -c video gives:
*-display
description: VGA compatible controller
product: Sky Lake Integrated Graphics
vendor: Intel Corporation
physical id: 2
bus info: pci#0000:00:02.0
version: 07
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:124 memory:f0000000-f0ffffff memory:e0000000-efffffff ioport:e000(size=64) memory:c0000-dffff
I've tried booting from grub into kernel 4.8.0 and the monitor still wasn't detected.
I've also tried to no avail:
sudo apt-get update
sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
I've also tried running the Intel graphics update tool and this also hasn't solved anything.
EDIT: It seems like I get the 'No video input' probelm if I plug in the HDMI cord before the computer has finished booting.
Pretty much the only answer one can give here based on the available information is, try checking the display cables, and, if that doesn't help, file a bug. Debugging display problems like this can be fairly involved, with several cycles of requesting and providing more information. That doesn't really work all that well here.
The alternatives for filing the bug are Ubuntu Launchpad and drm/i915 upstream. Upstream has the best knowledge about the driver and the hardware, but, depending on the issue, you might be expected to build and run the userspace components or the kernel from upstream git repositories.
I come across the problem and solve it with exactly the same card (i had same lshw -c video) by searching the NVIDIA X-Server settings (search inside apps) on my Ubuntu 16 LTS and activate the NVIDIA drivers for this card (I have a NVIDIA GEFORCE GTX)
After i log out and i have a bad errors display and i was blocked " this computer is running in low display mode" .
I just switch off the computer and restart it...and taatatatat HDMI was working and was able to display on my external Sansumg 27''
I had the exact same issue as OP. lshw not showing HDMI port, nada. Reinstalling xserver* did not work either.
May the gods of stack overflow smile upon you for that EDIT line, because plugging only after boot was complete, it did work for me as well.
This is quite interesting, as I am running 20.04. This issue came out of nowhere, just turned on the computer and voila, it was not working. There had been no updates, no changes that could affect this during previous session.
Would love to know if someone else has bumped into this problem.
I'm using the following configuration:
Linux Mint 17.3 Cinnamon 2.8.6
kernel 3.19.0-32-generic
amd radeon r5 m330
driver: xserver-xorg-video-ati v 1:7.3.0-1ubuntu3.1
Eclipse Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200
When I scroll the page I obtain this graphical problem (you can see the code duplicated, I imagine is a refresh problem of the GPU):
How can I solve the problem? I also tried to used fglrx-updates v. 2:15.200, but i didn't solve anything
I also tried to use an external monitor (samsung screen 23" connected with an hdmi) instead of the laptop screen but the problem doesn't goes away.
That seems to be related to libgtk3 usage in Linux Mint which is somewhat incompatible with Eclipse.
I had the same problem and I cured it adding:
--launcher.GTK_version
2
in eclipse.ini before --launcher.appendVmargs.
Unfortunately that doesn't seem to be the whole story as I still have "strange" crashes, but might be JavaFX-related, so YMMV.
I have been trying maybe weeks now to figure out how to configure VirtualBox to have 1366x768 resolution on a linux guest, which is on a windows 8.1 host.
My configuration:
Windows 8.1 as host
Linuxmint 17.1 as guest (tried ubuntu and debian too but no luck)
Virtualbox 4.3.26 and its extension pack
Laptop is powerful with 16GB ram and 4GB Nvdia
My problem is that it doesn't matter what I used, nothing worked.
Please do not post the answers on most known websites, I tried them already.
Once your VM is started, you need to run the VBox Linux Guest Additions.
First try to run it from the VirtualBox window's menu:
Devices >> Insert guest Additions CD image...
and follow the instructions.
If that fails, open a terminal and go to the directory where you CD reader is mounted (/run/media/ on Fedora or /media/ on Ubuntu for example).
Then type command sudo ./VBoxLinuxAdditions.run
Complete instructions can be found on the VirtualBox user manual
Once Guest Additions are installed, reboot your virtual machine. You should be able to resize your screen to your heart's content.
I installed the new VirtualBox 5.0.0_BETA2 and it solved my all problems. Great product is getting ready! Cant wait the latest release. more than a PERFECT software. Now you can remove top bar and/or bottom bar easily. Show what you need.
If you are having problem like me with 1366x768 I recommend you to install latest versin of VB even if it is Beta!