Waydroid - 版の履歴

DreamChaser: テンプレートや用語の訂正などを含む

2024-09-28T14:45:10Z

テンプレートや用語の訂正などを含む

差分を表示

DreamChaser: 最新版への翻訳・加筆

2024-09-28T13:06:09Z

最新版への翻訳・加筆

差分を表示

Akku: 言語間リンクの追加 (中国語版はうまく転送されない)

2024-08-07T02:45:37Z

言語間リンクの追加 (中国語版はうまく転送されない)

← 古い版		2024年8月7日 (水) 11:45時点における版
2行目:		2行目:
	[[Category:仮想化]]		[[Category:仮想化]]
	[[Category:Android]]		[[Category:Android]]
			[[en:Waydroid]]
			<!-- [[zh-hans:Waydroid]] -->
	{{Related articles start}}		{{Related articles start}}
	{{Related\|Anbox}}		{{Related\|Anbox}}

Kusanaginoturugi: /* Wayland session manager */ 重複を削除

2023-04-03T04:51:08Z

Wayland session manager: 重複を削除

← 古い版		2023年4月3日 (月) 13:51時点における版
33行目:		33行目:
	ro.hardware.egl=swiftshader</nowiki>}} に設定する。		ro.hardware.egl=swiftshader</nowiki>}} に設定する。
	** [[再起動]]し、{{ic\|waydroid-container.service}} を起動します。		** [[再起動]]し、{{ic\|waydroid-container.service}} を起動します。

	=== Wayland session manager ===

	Waydroid only works in a [[Wayland]] session manager, so make sure you are in a Wayland session.

	Note that even if you are in X11, many Wayland session managers support nested session (so you can run it inside your X11 session), the simplest example is {{pkg\|weston}}.

	=== Wayland セッションマネージャ ===		=== Wayland セッションマネージャ ===

Kusanaginoturugi: /* Wayland session manager */ 飜訳

2023-04-03T04:50:53Z

Wayland session manager: 飜訳

← 古い版		2023年4月3日 (月) 13:50時点における版
39行目:		39行目:

	Note that even if you are in X11, many Wayland session managers support nested session (so you can run it inside your X11 session), the simplest example is {{pkg\|weston}}.		Note that even if you are in X11, many Wayland session managers support nested session (so you can run it inside your X11 session), the simplest example is {{pkg\|weston}}.

			=== Wayland セッションマネージャ ===

			Waydroid は [[Wayland]] セッションマネージャーでのみ動作しますので、Wayland セッションであることを確認してください。

			X11 にいる場合でも、多くの Wayland セッションマネージャはネストされたセッションをサポートしていることに注意してください（X11 セッションの中で実行することができます）。

	=== Kernel Modules ===		=== Kernel Modules ===

Kusanaginoturugi: /* GPU 要件 */ 飜訳

2023-04-03T04:50:01Z

GPU 要件: 飜訳

← 古い版		2023年4月3日 (月) 13:50時点における版
27行目:		27行目:
	NVIDIA GPU は現在動作しませんが、2 つの回避策があります:		NVIDIA GPU は現在動作しませんが、2 つの回避策があります:

			* 可能であれば、統合型グラフィックカードに変更する
	* Switch to integrated graphic card if possible;
			* ソフトウェアレンダリングを使用します：
	* Use software rendering:
			** すでに {{ic\|waydroid init}} が実行されていることを確認してください。(インストール]]の項を参照）。
	** Make sure that you have already run {{ic\|waydroid init}} (see [[#Installation]] section)
	** ~~Edit~~ {{ic\|/var/lib/waydroid/waydroid_base.prop}} ~~and set:~~{{bc\|<nowiki>ro.hardware.gralloc=default		** {{ic\|/var/lib/waydroid/waydroid_base.prop}} を編集し、{{bc\|<nowiki>ro.hardware.gralloc=default
	ro.hardware.egl=swiftshader</nowiki>}}		ro.hardware.egl=swiftshader</nowiki>}} に設定する。
	** [[~~Restart~~]] ~~the~~ {{ic\|waydroid-container.service}}.		** [[再起動]]し、{{ic\|waydroid-container.service}} を起動します。

	=== Wayland session manager ===		=== Wayland session manager ===

Kusanaginoturugi: 一部飜訳

2023-03-03T08:10:39Z

一部飜訳

← 古い版		2023年3月3日 (金) 17:10時点における版
9行目:		9行目:
	{{Style\|Need to improve style.}}		{{Style\|Need to improve style.}}

			Waydroidは、通常の GNU/Linux システム上で完全な Android システムを起動するためのコンテナベースのアプローチです。
	Waydroid is a container-based approach to boot a full Android system on a regular GNU/Linux system.

	== ~~Prerequisites~~ ==		== 前提条件 ==

	=== CPU ~~Requirements~~ ===		=== CPU 要件 ===

	~~The requirements depend on the~~ CPU ~~architecture. You can check~~ [https://developer.android.com/ndk/guides/abis#sa ~~table~~] ~~for more information.~~		要件は CPU アーキテクチャによって異なります。詳しくは [https://developer.android.com/ndk/guides/abis#sa テーブル]で確認することができます。

	~~You can check if you have the required~~ CPU ~~instructions with~~ {{ic\|cat /proc/cpuinfo}}.		必要な CPU 命令があるかどうかは、{{ic\|cat /proc/cpuinfo}} で確認することができます。

	=== GPU ~~Requirements~~ ===		=== GPU 要件 ===

			Waydroid は現在 Intel GPU で最適に動作します。それらはすぐに使用できるはずです。
	Waydroid currently works best with Intel GPUs. They should work out of the box.

			すべての AMD GPU はサポートされています。もし Waydroid が動作しない場合は、新しい Waydroid イメージ(Radeon 680M で動作)をビルドするか、以下の NVIDIA の手順を試してみてください。
	All AMD GPUs have been supported; if Waydroid does ''not'' work you might also want to try to build a new Waydroid image (which works for Radeon 680M), or try the NVIDIA instructions below.

			NVIDIA GPU は現在動作しませんが、2 つの回避策があります:
	NVIDIA GPUs do ''not'' work currently, but there are 2 workarounds:

	* Switch to integrated graphic card if possible;		* Switch to integrated graphic card if possible;

Kusanaginoturugi: 英語版からページを作成

2023-03-03T08:06:00Z

英語版からページを作成

新規ページ

[[Category:サンドボックス]]
[[Category:仮想化]]
[[Category:Android]]
{{Related articles start}}
{{Related|Anbox}}
{{Related|Linux Containers}}
{{Related articles end}}

{{Style|Need to improve style.}}

Waydroid is a container-based approach to boot a full Android system on a regular GNU/Linux system.

== Prerequisites ==

=== CPU Requirements ===

The requirements depend on the CPU architecture. You can check [https://developer.android.com/ndk/guides/abis#sa table] for more information.

You can check if you have the required CPU instructions with {{ic|cat /proc/cpuinfo}}.

=== GPU Requirements ===

Waydroid currently works best with Intel GPUs. They should work out of the box.

All AMD GPUs have been supported; if Waydroid does ''not'' work you might also want to try to build a new Waydroid image (which works for Radeon 680M), or try the NVIDIA instructions below.

NVIDIA GPUs do ''not'' work currently, but there are 2 workarounds:

* Switch to integrated graphic card if possible;
* Use software rendering:
** Make sure that you have already run {{ic|waydroid init}} (see [[#Installation]] section)
** Edit {{ic|/var/lib/waydroid/waydroid_base.prop}} and set:{{bc|<nowiki>ro.hardware.gralloc=default
ro.hardware.egl=swiftshader</nowiki>}}
** [[Restart]] the {{ic|waydroid-container.service}}.

=== Wayland session manager ===

Waydroid only works in a [[Wayland]] session manager, so make sure you are in a Wayland session.

Note that even if you are in X11, many Wayland session managers support nested session (so you can run it inside your X11 session), the simplest example is {{pkg|weston}}.

=== Kernel Modules ===

You need to run a kernel which comes with the binder modules and optionally the ashmem one. They are not part of Arch Linux's default kernel ({{Pkg|linux}}), thus you need to install a kernel which ships these modules.

You might also need to configure your bootloader to use a different kernel. Please refer to the wiki page of your bootloader how to boot with the new kernel. Booting into another kernel (version) is one of the few occasions when you have to reboot a Linux system. You should boot into the kernel with these modules before starting Waydroid.

{{Note|1=Since {{aur|waydroid}} 1.2.1 ''ashmem'' is not needed anymore, ''memfd'' can be used instead, see [https://github.com/waydroid/waydroid/issues/406 issue]. This because ''ashmem'' has been completely replaced by ''memfd'' in ''mainline Linux'' since version 5.18, see [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=721412ed3d819e767cac2b06646bf03aa158aaec commit].}}

To get a compatible kernel, you have multiple options:

==== Using Linux-Zen ====

The {{Pkg|linux-zen}} kernel includes the necessary modules. This might be the most comfortable way, as you do not have to compile the kernel (which takes a long time) and will receive updated versions regularly.

==== DKMS modules ====

You can install {{aur|anbox-modules-dkms-git}} and load kernel modules with: {{bc|# modprobe ashmem_linux
# modprobe binder_linux
}}

Alternatively, if your kernel is 5.18 or newer, install {{aur|binder_linux-dkms}}, which provides just binder_linux.

==== Building a kernel ====

Alternatively, you can recompile the {{Pkg|linux}} kernel — or other kernel packages (>=5.7) — with the necessary options. Also see [[Kernel#Compilation]].

When setting compilation options, you have 2 options available; ''binder'' and ''binderfs''. Instructions for both are provided below.

===== Using binder =====

The modules can either be compiled into the kernel ({{ic|y}}), into modules ({{ic|m}}), or not at all ({{ic|n}}). Also, not all combinations in the configuration are possible, and some options will require other options.

The configuration options below will compile binder as a module, while the last option specifies that there will be three devices created in the {{ic|/dev/}} directory, when the binder module is loaded.

{{bc|1=
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=n
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"
}}

When building a kernel from the AUR, one can update the configuration with the following steps:

# run {{ic|makepkg --nobuild}}, which will download the sources, verify and extract them and run the {{ic|prepare()}} function.
# edit the {{ic|.config}} file (with the dot in the filename), which is located at the base of the kernel directory.
# at the end of the {{ic|prepare()}} function was probably a command which regenerates the makefiles with information from the configuration, possibly {{ic|make olddefconfig}}. Move that to the {{ic|build()}} function, or execute it yourself.
# run {{ic|makepkg --noextract}}, which will continue from the place where {{ic|makepkg --nobuild}} stopped.

===== Using binderfs =====

The binder kernel module is known to cause some issues to several users. To address these issues, binderfs was created. One has to choose between the old and the new way when compiling the kernel. With the options below, one will use binderfs instead.

With the kernel sources comes also a simple script to set configuration options. It will not do dependency checks, just like when editing the configuration by hand. When being in the same directory where the {{ic|.config}} file lies, one can execute the following commands:

{{bc|
$ scripts/config --enable CONFIG_ANDROID
$ scripts/config --enable CONFIG_ANDROID_BINDER_IPC
$ scripts/config --enable CONFIG_ANDROID_BINDERFS
$ scripts/config --set-str CONFIG_ANDROID_BINDER_DEVICES ""
}}

When building a kernel from the AUR, it is enough to insert these lines at the right place in the [[PKGBUILD]], usually in {{ic|prepare()}}.

==== Setup binder devices ====

Make sure you have the latest version of Waydroid package, and Waydroid will take automatically care of this.

== Installation ==

[[Install]] the {{AUR|waydroid}} package.

Optionally, install {{AUR|waydroid-image}} or {{AUR|waydroid-image-gapps}} to provide the needed Android image through AUR. It is however recommended to let Waydroid itself handle downloading the images.

Afterwards init Waydroid, this will automatically download the latest Android image if it is not yet available.
# waydroid init

To init with GApps support:
# waydroid init -s GAPPS -f
Next [[start/enable]] the {{ic|waydroid-container.service}}.

Waydroid should now work.

== Usage ==

Make sure that {{ic|waydroid-container.service}} is running then run:
$ waydroid session start

The Waydroid session is now active, here are a couple of useful commands to interact with it:

''Launch GUI'':
$ waydroid show-full-ui
''Launch shell'':
# waydroid shell
''Install an application'':
$ waydroid app install $path_to_apk
''Run an application'':
$ waydroid app launch $package-name #Can be retrieved with `waydroid app list`

== Network ==

The network should work out of the box, if its not you might need to make sure [[internet sharing#Enable packet forwarding|packet forwarding]] is enabled in kernel and allow the following rules through your firewall ''before'' running ''Waydroid session start''.

Taking {{pkg|ufw}} as an example:

* Dns traffic needs to be allowed:
** {{bc|# ufw allow 67}}
** {{bc|# ufw allow 53}}
* Packet forwarding needs to be allowed:
** {{bc|# ufw default allow FORWARD}}

For {{pkg|firewalld}}, you can use those commands:

* DNS:
** {{bc|1=# firewall-cmd --zone=trusted --add-port=67/udp}}
** {{bc|1=# firewall-cmd --zone=trusted --add-port=53/udp}}
* Packet forwarding:
** {{bc|1=# firewall-cmd --zone=trusted --add-forward}}

{{Note|We assume that interface {{ic|waydroid0}} created by waydroid should be in the firewalld zone {{ic|trusted}} automatically. If not so, please adjust those commands above or move interface {{ic|waydroid0}} to {{ic|trusted}}. You may also need {{bc|# firewall-cmd --runtime-to-permanent}} to make your changes exist after a restart.}}

== Troubleshooting ==

If you run into issues, take a look at the official Issue Tracker: [https://github.com/waydroid/waydroid/issues Waydroid issue tracker]

=== General tips ===

Waydroid is in rapid developement so if you face issues, here is a good list of steps to do first:

# Make sure your Waydroid package is up to date;
# Make sure you have the latest Waydroid image by running {{bc|# waydroid upgrade}}
# Reset Waydroid: [[stop]] the {{ic|waydroid-container.service}}, run {{bc|# waydroid init -f}} and [[start]] the service again.
# You may also want to do little cleanup, run {{bc|# rm -rf /var/lib/waydroid /home/.waydroid}} {{bc|$ rm -rf ~/waydroid ~/.share/waydroid ~/.local/share/applications/*aydroid* ~/.local/share/waydroid}}

=== Rotated apps are unusable ===

See https://github.com/waydroid/waydroid/issues/70

Click ''F11'' to switch the current app to windowed mode.

=== Failed to start Clipboard manager service ===

Install {{aur|python-pyclip}}

=== Sometimes the physical keyboard does not work ===

Press ''Left Alt'' key.

=== '''dnsmasq: failed to open pidfile /run/waydroid-lxc/dnsmasq.pid: Permission denied''' ===

apparmor rule is not set, goto /etc/apparmor.d/usr.sbin.dnsmasq
and add below
{{bc|#/etc/apparmor.d/usr.sbin.dnsmasq

@{run}/waydroid-lxc/ r,
@{run}/waydroid-lxc/* rw, }}

=== Commands inside Waydroid shell outputs inaccessible or not found ===

On Arch based distributions there's a [[Linux Containers#Basic usage|"bug" that may appear while working with lxc-attach]] that may cause this issue with commands inside {{ic|waydroid shell}} like {{ic|adbd}} or {{ic|settings}}.
A possible workaround for this would be replace the {{bc|# waydroid shell}} command with {{bc|# lxc-attach -P /var/lib/waydroid/lxc/ -n waydroid --clear-env}}

=== WARNING: Service manager /dev/binder has died ===

See https://github.com/waydroid/waydroid/issues/136

You should enable [https://docs.kernel.org/accounting/psi.html PSI].
Add {{ic|1=psi=1}} to the [[kernel command line]].

== See also ==

* [https://github.com/waydroid/waydroid Waydroid GitHub repo]
* [https://docs.waydro.id/ Waydroid documentation]
* [https://matrix.to/#/#waydroid:connolly.tech Waydroid Matrix group]
* [https://t.me/WayDroid Waydroid Telegram group]