To have a working emulator can only compile it? #59
Comments
|
Related to #63. |
Source: https://wiki.lineageos.org/quirks/snet/ |
|
Wikipedia: MicroG#LineageOS for MicroG (1263368712) does not seem to mention the change of 25/02/24. |
|
GmsCore/wiki/Prerequisites seems to be met now on on LineageOS |
Open
|
https://wiki.lineageos.org/libvirt-qemu can be useful for untrusted usage.
So let us try emulator again. So maybe can use for both virtual machines to ease the workflow. Alternatively can run the emulator within a virtual machine. It may be interesting as the virtual machine documentation looks more complex. |
|
Should be able to install Google apps in not trusted setup. https://wiki.lineageos.org/libvirt-qemu#adb-sideload |
|
Should be able to update without loosing current setup preferably. |
|
Should keep data across reboots of the LineageOS setup. |
|
It can be an intermediary step to #25. To ensure portability from a computer to the other can use f/strace to figure out the files needed in build folder. https://wiki.lineageos.org/emulator#running-the-emulator
|
|
I have the feeling already to have built emulator but no according to searching emulator in these repository issues. |
|
https://wiki.lineageos.org/libvirt-qemu#known-issues is otherwise acceptable it seems. |
avdOutput: |
|
As here need to test on the compiled computer the build, let use my computer. |
mkdir -p ~/android/lineagegit lfs installdf -h /Output:export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache
ccache -M 50G |
repo init -u https://github.com/LineageOS/android.git -b lineage-22.1 --git-lfs --no-clone-bundleOutput: |
date; time repo sync; matrix-commander -m 'Repo sync finished!'Output:source build/envsetup.sh
breakfast sdk_phone_x86_64 engOutput:Could try compiling ARM on my computer and export it to Oracle Cloud to help Waydroid persons.
|
|
Could be curious and try compiling:
as they seem Emulator compatible. |
|
With 40 GB of swap. date; time mka; matrix-commander -m 'Compilation finished!'emulator
Note that we can scroll. My 200 % scale in OS settings may be to blame. emulatorOutput:on following starts, why is it so long with a computer power? |
|
DuckDuckGo search sdkmanager emulator. |
./avdmanager list deviceOutput: |
|
The Stack Overflow answer 54668368: sudo apt install -y cpu-checkerOutput:on my Debian 12 GNOME laptop. |
kvm-okOutput: |
./avdmanager create avd -n test -k 'system-images;android-35;default;arm64-v8a'Output: |
./emulator -avd testOutput: |
ANDROID_HOME=~/Desktop/android_sdk
echo $ANDROID_HOMEdoes not help. |
ANDROID_SDK_ROOT=~/Desktop/android_sdkdoes not help. |
export ANDROID_SDK_ROOT=~/Desktop/android_sdk
./emulator -avd testOutput: |
./sdkmanager --list | grep platformOutput: |
./sdkmanager --install 'platforms;android-35'Output: |
./emulator -avd testOutput: |
./sdkmanager --install 'platform-tools'Output: |
./emulator -avd testOutput: |
source build/envsetup.sh
export AB_OTA_UPDATER=false
breakfast virtio_x86_64Output:date; time m espimage-install; matrix-commander -m 'Build finished!' |
|
Have I tested my ARM emulator system image build on my Debian 12 GNOME laptop? Because it is what I am trying to do with closed-source components currently. Yes, see #issuecomment-2615408546. |
date; time m espimage-install; matrix-commander -m 'Build finished!' |
ls -lh out/target/product/virtio_x86_64/Output: |
sudo apt install -y qemu-system-arm qemu-efi-aarch64 qemu-system-x86 ovmfOutput:Source: https://wiki.lineageos.org/libvirt-qemu#install-the-virtual-machine-software |
|
Let us try non-A/B build 10 GiB of size for the first disk. |
ls -lh out/target/product/virtio_x86_64/lineage-22.1-20250204-UNOFFICIAL-virtio_x86_64.img ~/lineage-22.1-20250201-UNOFFICIAL-virtio_x86_64.imgOutput:So both |
|
Formatting options look different to #issuecomment-2629134313.
Note that I am fine running Windows in a virtual machine if necessary to be able to run ARM apps with a decent speed.
|
|
|
|
So not storage difference with #issuecomment-2629146781. I suspect the total storage quantity being faked. |
Would help the issue: |
Related to the issue: |
|
I just verified and without formatting it states the install to have failed and it does not seem to boot correctly at reboot. A screenshot would have been appreciated. |
If I am able to efficiently run ARM apps, then let know the person:He may have a Mac, I asked him, such that may try on his Mac to know if ARM apps work fine on this setup. |
Source: Wikipedia: Waydroid#Limitations (1267136573) Source: https://www.xda-developers.com/waydroid-android-apps-on-linux/ may be an interesting workaround if able to make it work within a virtual machine. Could also in theory try to run my ARM emulator from my Fairphone 4 as it is ARM but I suspect bad performances even if in theory may be quite fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://wiki.lineageos.org/emulator
Would be nice to be able to download the compiled files directly like on Waydroid.
Tracking this issue on my Waydroid fork does not seem appropriate.
See https://discord.com/channels/@me/752997802317185035/1251488897704398900.
Related to Benjamin_Loison/lineageos4microg.github.io/issues/4.
The text was updated successfully, but these errors were encountered: