LogoLogo
  • Waydroid
  • Usage
    • Install Instructions
    • Install and Run Android Applications
    • Waydroid command line options
    • Waydroid Prop Options
  • FAQ
    • Google Play Certification
    • Disable On-Screen Keyboard
    • Community Projects We Like
    • Get Waydroid to work through a VM
    • Using ADB with Waydroid
    • Setting up Waydroid only Sessions
    • Setting up a shared folder
    • Color correction in Mutter
    • Backup/Restore apps and data
    • Using custom Waydroid images
  • Development
    • Compile Waydroid - Lineage OS based images
    • Manual Patch Resolution
    • Compile Waydroid - Using Android-Generic Project
  • Debugging
    • Getting Essential Information
    • Networking Issues
    • Known Issues
    • General Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Debugging

Getting Essential Information

Useful information belongs in two places the methods of getting this information are as follows. If someone asks for the logs, it is best to give them the full output of these commands as well as include them on any issue tickets you create:

sudo systemctl status waydroid-container.service

waydroid log

sudo waydroid logcat > ~/waydroid-logcat.txt

It is also important to make sure your kernel supports binder and either ashmem or memfd, you can verify support in your kernel by using one of the following commands.

grep -i -e android -e memfd -e ashmem "/boot/config-$(uname -r)"

Or on some distros:

zgrep -i -e android -e memfd -e ashmem /proc/config.gz

If you do not have support, you may need to change to a supported kernel or look at patched anbox-modules.dkms.

Another important piece of information is knowing what linux enviroment you are using. These two commands contain the relevant information:

lsb_release -a and uname -a

PreviousCompile Waydroid - Using Android-Generic ProjectNextNetworking Issues

Last updated 2 years ago

Was this helpful?