If I recall correctly, I had the same or a similar problem. Check your platform-tools / fastboot version. I have fastboot version 33.0.3-8952118 installed myself while my package mananger has installed fastboot version 34.0.4-android-tools.
Might be a bug in the more recent version.
Good luck
was already weighing that probability.
I think that’s the problem…
thank you very much
Hello,
I am trying to install waydroid by following GitHub - sailfishos-open/waydroid: Waydroid packaging for Sailfish OS but I have not been able to get it to work.
Is it possible to get it working?
I install the packages following another thread where they indicate to do it through Chum.
@jmdlpino I can provide what I did successfully on my Volla:
You have to install packages from Chum - waydroid and waydroid-runner.
Then install from terminal -
$ devel-su
# zypper in waydroid-gbinder-config-hybris
Then as devel-su:
# vi /etc/gbinder.d/anbox-hybris.conf
Change aidl2 to aidl3, (appears 4 times in the file)
Save file.
# waydroid init
edit /etc/dnsmasq.conf to uncomment the following line (Volla, 4.4.0.72: line 124):
#bind-interfaces
# vi /etc/dnsmasq.conf
systemctl disable --now dnsmasq
Then reboot and start waydroid
Many thanks to @Sheigorath , who gaves me this hint long time ago.
And: NEVER update Waydroid if it reports an available OTA update. This may work a few times, but sooner or later it will break the system and even if it works it brings nothing.
Exactly, stick with a working image
Sorry,
I had high hopes with your instructions, because I was missing the step of modifying the /etc/dnsmasq.conf file.
I thought the problem was there.
But when I run it, it stays on the “Starting Android session/Waiting for Android UI” screen.
I have to clarify that I’m running SailfishOS from Boot Manager…
Thank you very much for your help.
When i had your issue, i had to use an older image. If you search my posts, you might find the description. Usually i do note evrything down.
The thing is: based on installation time you might endup with different image, some work, some not. At least my experience
It is in gs290 installation thread
check my posts, somewhere i had issues with space then image
I am using 4.4.0.72
you mean using older versions?
Thank you.
no
Older version of waydroid image or better the image of os running in waydroid i think it is.
if you would read my posts, you would see that i do init waydroid with an specified image version not with default.
if you run just waydroid init it will take some current vanilla android version i think.
i did download an older, working version and told waydroid to init with that.
i would suggest that you comment on my posts in the other thread, cause that i do not need to jump between them, might be easier for us
so while this post wont help you, it shows that i actually did download the image separately and then did waydroid init with the option to specify the path to downloaded image
problem is: i did switch my laptop and doubt to more details available on the topic.
but if you would check waydroid init options you could start from there, same as i did
ok i did find two download adresses:
https://master.dl.sourceforge.net/project/waydroid/images/vendor/waydroid_arm64/lineage-17.1-20220514-HALIUM_10-waydroid_arm64-vendor.zip?viasf=1
i assume this is it, my working images … that’s all i can do for you
hope that helps
thank you very much.
more than grateful.
hello everyone
appologies for bumping this old thread… i’m late to the party.
in a nutshell: when installing sailfishos on my volla X23
using flash.sh, i am never prompted to encrypt a partition.
after the flash.sh exits, the volla x23 ‘k6789v1_64’ boot loops. .
in details:
downloaded ubports 0.10.0 (deb x64), used it to install volla OS
booted phone, went into its settings, enabled developper, usb debugging, and unlocked the phone.
rebooted in fastboot
executed flash.sh
(archive.zip is from #5696826776)
was asked if i wanted to reboot. said y.
from there i’m in a boot loop.
__
i have tried unbuntu touch it works fine, i have tried vollaOS it works fine. both instaled with ubports.
__
any help would be very much appreciated.
Did you use an USB3 socket (blue) on your computer?
If yes, try again using a USB2 socket (white) or use an USB hub with a USB2 socket when flashing.
I have the same problem with the same device. I think the kernel or bootloader or something, sfos was built for is older than the ones provided by Ubuntu and volla os. I tried finding an Android image for gigaset gx4 pro, which is the same device, but no luck there and i also tried flashing the older volla os via fastboot and didn’t succeed, because it wasn’t booting either.
I only installed that device once and don’t own one anymore. But, as a general rule, use the android recovery to clear all data to make sure that the sfos install has enough room for the layout. Then try flashing again and attend carefully to the messages indicating success/failure of writes.
But an older version of ubports did boot this way
after checking, my motherboard only has USB3.2 ports.
i got an usb2 hub, used that, still same behavior: i am never asked to encrypt.
Did you clear all user data in android recovery, after installing vollaos? After that, you should have a base appropriate for sfos + space.
yes i did
process is:
install vollaOS, boot it, activate dev mode, usb debuging, oem unlock
reboot into recovery, format system and data
reboot into fastboot
patch.sh
no errors, but not asked to encrypt.