GS290 installation

They did: Buy an Xperia 10 II or III, flash SailfishOS and the root volume size will be 4000 MBytes. That is how they addressed this issue. Its up to the device porters to utilise the scheme Jolla developed for this, which I comprehensively described in some other Volla specific thread (“topic”) here at FSO.

Until now, I wasn’t couraged enough to follow this howto, because I fear to brick the phone.

Did you meant to address specifically the section 3.3 Increasing the “root” LVM volume size?

Well, at the beginning of section 3.3 I explicitly described how things should look, before one starts altering the LVM volumes: If they do look as described, I see no reason why this section should not be applicable.

But you cannot “brick your phone” (which means that one cannot reflash it any longer) by altering these SailfishOS specific LVM volumes: The partitioning scheme and the content of any other partition (e.g., the boot partition(s)) are not touched by following this section 3.3.

Also I don’t know if this howto is also working on the Volla, it’s written for the Sony.

Neither do I, because I do not own any of the Volla models.
Though IMO, solely the section 1.1 First steps contains mostly points, which are specifically for Sony Xperias.

TL;DR

If you carefully read my “Guide: Installing SailfishX on Xperias”, all sections should be applicable to any SailfishOS device, with the exception of section 1.1.

I happen to own only Xperias, hence I developed this guide on, with and for them, thus I do not claim anything else.

Feedback from users, positive and negative (e.g., criticism) is always welcome, for this guide preferably by opening a new “issue” at Gitlab.

P.S.: I still wonder why @piggz did not increase the root volume size to 4000 MBytes for his more recent ports of SailfisOS, like Jolla did for the Xperia 10 II and III. I already provided this suggestion accompanied with the technical details in some other Volla specific thread (“topic”) here at FSO.

I do see that it might turn out to be troublesome or impossible to increase the root volume size in an fully automated manner when upgrading SailfishOS etc. But to create a larger root volume when creating a new installation image for a new device appears to be quite easy: Just utilise what Jolla implemented.

1 Like

Neither did I (going into details here), because I do not run any community port of SailfishOS. One porter reported years ago, that one of his users was successfully upgrading SailfishOS with sailfshos-upgrade. As stated at many places (e.g., in its README) sailfshos-upgrade is just a frontend for ssu re A.B.C.D && version --dup; if that works, one should rather use sailfshos-upgrade (because the generally recommended GUI updater cannot be used on SailfishOS ports; I always wondered why: Is it proprietary software, does it need a Jolla account to run, or is something else the reason?).

OTOH, some porters emphasise using the “zypper dance” for upgrading their port of SailfishOS. I do not know the technical details, because I do not own a device running a SailfishOS port. But I would be happy to be informed about any special requirements device ports have and will consider to take them into account in sailfishos-upgrade.

Edit: I just saw that @Seven.of.nine and @pawel.spoon both used ssu re A.B.C.D && version --dup, not the “zypper dance” ssu re A.B.C.D && zypper ref && zypper dup.

TL;DR

Due the usual absence of positive feedback from users, I cannot tell.
You are welcome to change that!

Side note
7o9 has already provided an unusual exception from this for another piece of software, but I general I assume that of users who experience a bug in Free Software (“FLOSS”) about every 100th reports it and of users who are fond of a specific Free Software (“FLOSS”) about every 1000th denotes this to the author(s), sometimes even spiced with some helpful information, e.g., which features are most important, what works well, what does not work well, UI design goodies and flaws etc.



A “Yes” to both aspects addressed:

  • Do not try downgrade SailfishOS, unless the SailfishOS installation is foobar’ed anyway (if you are already considering to reflash, one can try; I did once and it did not even start to downgrade from A.C.x.y to A.B.x.y, but threw an error message).
  • I assumed downgrades to work between point releases of SailfishOS. Thanks to @7of9 for confirming that.
1 Like

these were the packages that got removed when I updated from .64 to the non-existant yggdrasil .68 …

patterns-sailfish-device-adaptation-yggdrasil
patterns-sailfish-device-configuration-yggdrasil

Try installing them.

1 Like

@poetaster thanks very much, please help me: what is the command to install these two packages? Is it ‘pkcon install packetname’? Or shall I better use zypper to install? Is there any difference in the result between them?
I’m now on 4.4.0.72, with …68 and …64 the cam did work fine. Bug occured when I updated to …72, and it affects all 3 cam apps - stock cam, advanced cam and Fotokopierer - in the same way: app crashes in the moment where the shot should be saved to memory, or - in case of Fotokopierer - should be further processed.
Camera under Waydroid works fine. Only native SFOS apps are affected.

I did so, using ‘zypper install packagename’. The first (patterns-sailfish-device-adaptation-yggdrasil) reported ‘is installed’, and the second (patterns-sailfish-device-configuration-yggdrasil) was installed by zypper. Then I rebooted the phone and tried if something changes.

Result is: nothing changes. All 3 apps still crash (minimize) after taking a shot.

Is there any other option that has a chance to succeed?

Hmmm. It could be that there is something else missing.

There I had somehow also been missiing busybox-symlinks-procps so try:

zypper install patterns-sailfish-device-configuration-common busybox-symlinks-procps

1 Like

I tried and got this:

andrea@andrea-Voom-Laptop-Max:~$ ssh volla
Last login: Wed Dec 28 10:55:29 2022
,---
| Sailfish OS 4.4.0.72 (Vanha Rauma)
'---
[defaultuser@VollaPhone ~]$ devel-su
Password: 
[root@VollaPhone defaultuser]# zypper install patterns-sailfish-device-configuration-common busybox-symlinks-procps
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Paketabhängigkeiten werden aufgelöst...

Problem: das zu installierende busybox-symlinks-procps-1.33.1+git3-1.7.14.jolla.aarch64 steht im Konflikt mit 'procps-ng', das vom installierten procps-ng-3.3.16+git2-1.6.2.jolla.aarch64 bereitgestellt wird
 Lösung 1: Deinstallation von procps-ng-3.3.16+git2-1.6.2.jolla.aarch64
 Lösung 2: busybox-symlinks-procps-1.33.1+git3-1.7.14.jolla.aarch64 nicht installieren

Wählen Sie aus den obigen Lösungen mittels Nummer oder brechen Sie (a)b [1/2/a/d/?] (a):

so I aborted because I don’t know what to do. How can I solve this?

Try this alone first.

For reference, I had made a log of what happened when I made the mistake of updating .64 to .68: https://poetaster.de/sfos/64-72.txt

What one can see is the following removals:

The following 5 packages are going to be REMOVED:

droid-config-yggdrasil-policy-settings
ofono-ril-binder-plugin
ofono-ril-plugin
patterns-sailfish-device-adaptation-yggdrasil
patterns-sailfish-device-configuration-yggdrasil

check those, too.

1 Like

I did so and it reported this:

[root@VollaPhone defaultuser]# zypper install patterns-sailfish-device-configuration-common
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Paketabhängigkeiten werden aufgelöst...

Das folgende NEUE Paket wird installiert:
  patterns-sailfish-device-configuration-common

1 neues Paket zu installieren.
Gesamtgröße des Downloads: 56,3 KiB. Bereits im Cache gespeichert: 0 B. Nach der Operation werden zusätzlich 56,3 KiB belegt.
Fortfahren? [j/n/v/...? zeigt alle Optionen] (j): j
Paket patterns-sailfish-device-configuration-common-1.1.6+git2-1.8.1.jolla.noarch abrufen      (1/1),  56,3 KiB ( 56,3 KiB entpackt)
Abrufen: patterns-sailfish-device-configuration-common-1.1.6+git2-1.8.1.jolla.noarch.rpm ...................................[fertig]

Überprüfung auf Dateikonflikte läuft: ......................................................................................[fertig]
(1/1) Installieren: patterns-sailfish-device-configuration-common-1.1.6+git2-1.8.1.jolla.noarch ............................[fertig]
Zusätzliche rpm-Ausgabe:
warning: /home/.zypp-cache/packages/jolla/non-oss/noarch/patterns-sailfish-device-configuration-common-1.1.6+git2-1.8.1.jolla.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 47394f23: NOKEY


[root@VollaPhone defaultuser]#

After a reboot it’s the same situation as before with the 3 apps.

edit: on installing ‘droid-config-yggdrasil-policy-settings’ the Volla says ‘latest version is installed’ (nothing to do)

edit: Isn’t ‘ofono’ the mobile phone stuff? What has this to do with saving an image to memory? I fear to damage something and brick the phone…

Ok, now try to do a:

zypper ref
zupper up

having those packages from patterns installed might bring in some dependencies.

1 Like

zypper ref says everything’s up to date, zypper up says nothing to do.

edit: now I tried also ‘zypper dup’ and got this:

[root@VollaPhone defaultuser]# zypper dup
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Warnung: Sie sind im Begriff, eine Distributionsaktualisierung mit allen aktivierten Repositorys durchzuführen. Vergewissern Sie sich, dass diese Repositorys kompatibel sind, bevor Sie fortfahren. Weitere Informationen zu diesem Kommando finden Sie unter 'man zypper'.
Distributions-Aktualisierungen werden verarbeitet...

Das folgende Paket wird durch eine ältere Version ausgetauscht:
  harbour-storeman

Das folgende Paket wird den Anbieter ändern:
  harbour-storeman  meego -> chum

1 Paket wird zurückgestuft, 1 Anbieterwechsel.
Gesamtgröße des Downloads: 479,9 KiB. Bereits im Cache gespeichert: 0 B. Nach diesem Vorgang wird kein zusätzlicher Speicherplatz
belegt oder freigegeben.
Fortfahren? [j/n/v/...? zeigt alle Optionen] (j): 

Shall I do this?

edit: out of curiosity, I did it… Result: no changes.

1 Like

Oh, dear. I’m beginning to think something is wrong at the android level. But I’d ask @piggz first how we might go further to debug.

1 Like

Astonishingly the stock cam of Waydroid and also Android app ‘Open Camera’ works perfect! But unfortunately the photos are not accessible from SFOS when they are inside the Waydroid container. At least I have no idea how to access Waydroid Android data from SFOS.

If you have Waydroid running you’ll see the result right away.

As root (sudo or devel-su)
ln -s /home/waydroid/data/media/0/DCIM/Camera /home/defaultuser/Pictures/Pics-Android

(use any name you like instead of Pics-Android; the link works when Waydroid is running and behaves nicely when it isn’t)

File Browser and Sailphoto can see the files with Sailjail disabled. Jolla Gallery lists them but can’t show them.


On my GS290 the Sailfish camera apps work just fine - but I waited for the repo Index of /obs/nemo:/testing:/hw:/volla:/yggdrasil:/4.4.0.72 to magically appear before upgrading.

This command shows the 41 GS290-specific packages I have installed:
zypper se -i -r adaptation-community
(zypper se -i | grep yggd shows just the ones that have yggd in the name)

2 Likes

@Ahtisilli Thank you very much! This works perfect on the first try!

After the command
ln -s /home/waydroid/data/media/0/DCIM/Camera /home/defaultuser/Pictures/Pics-Android
the pictures taken with Waydroid stock cam were visible in File Browser.

The Android ‘OpenCamera’ App uses a different path and so I modified your command and did additionally
ln -s /home/waydroid/data/media/0/DCIM/OpenCamera /home/defaultuser/Pictures/Pics-AndroidOC

After this, the pics from Android’s ‘OpenCamera’ are also visible in File Browser.
I’m really happy now, thanks again!

edit: As you wrote, Waydroid has to be running to access the pictures!. If Waydroid is not running, it reports a defect symlink, but after starting Waydroid again it also works again.


I have also SFOS 4.4.0.72 running on the Volla / GS290. Product info says Geräteadaption
0.0.1+hybris.
17.20210903220301.4.gbf25067.4

Output of ‘zypper se -i -r adaptation-community’ is:

[root@VollaPhone defaultuser]# zypper se -i -r adaptation-community
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                                                    | Zusammenfassung                                               | Typ
---+---------------------------------------------------------+---------------------------------------------------------------+------
i  | community-adaptation-testing                            | Community HW adaptation setup, testing flavour                | Paket
i  | droid-biometry-fp                                       | Android Biometry FingerPrint library                          | Paket
i+ | droid-config-yggdrasil                                  | Config packages for Droid HAL adaptations                     | Paket
i  | droid-config-yggdrasil-bluez5                           | yggdrasil packages for BlueZ 5                                | Paket
i  | droid-config-yggdrasil-flashing                         | On device flashing files for yggdrasil hw                     | Paket
i  | droid-config-yggdrasil-policy-settings                  | Policy settings for yggdrasil hw                              | Paket
i  | droid-config-yggdrasil-preinit-plugin                   | Preinit plugins for yggdrasil                                 | Paket
i  | droid-config-yggdrasil-pulseaudio-settings              | PulseAudio settings for yggdrasil hw                          | Paket
i  | droid-config-yggdrasil-sailfish                         | Per device configuration for sailfish for droid-hal device:-> | Paket
i+ | droid-hal-version-yggdrasil                             | SailfishOS HW Adaptation droid version package 0.0.1.4 (unk-> | Paket
i+ | droid-hal-yggdrasil                                     | Droid HAL package for yggdrasil                               | Paket
i  | droid-hal-yggdrasil-detritus                            | Straggler files for GS290 hw                                  | Paket
i+ | droid-hal-yggdrasil-img-boot                            | Kernel boot image for yggdrasil                               | Paket
i  | droid-hal-yggdrasil-tools                               | Some tools from android specific for GS290                    | Paket
i  | droid-hal-yggdrasil-users                               | Create users and groups for device: yggdrasil                 | Paket
i  | droid-hwcrypt                                           | Android Hardware-based Encrytion Tool                         | Paket
i  | droidmedia                                              | Android media wrapper library                                 | Paket
i  | hybris-libsensorfw-qt5-binder                           | Sensor Framework Qt5                                          | Paket
i  | libhybris                                               | Utilize Bionic-based HW adaptations on glibc systems          | Paket
i+ | libhybris-libEGL                                        | EGL for hybris                                                | Paket
i+ | libhybris-libGLESv2                                     | OpenGL ES 2.0 for libhybris                                   | Paket
i  | libhybris-libhardware                                   | libhardware for libhybris                                     | Paket
i  | libhybris-libsync                                       | libsync for libhybris                                         | Paket
i+ | libhybris-libwayland-egl                                | Wayland EGL for libhybris                                     | Paket
i  | libsfosdevenc                                           | Library used by Sailfish OS Device Encryption                 | Paket
i  | libtls-padding                                          | Reserve some TLS spaces                                       | Paket
i  | lipstick-qt5                                            | QML toolkit for homescreen creation                           | Paket
i+ | patterns-sailfish-device-adaptation-yggdrasil           | Sailfish HW Adaptation yggdrasil                              | Paket
i  | patterns-sailfish-device-configuration-common-yggdrasil | Jolla Configuration common                                    | Paket
i+ | patterns-sailfish-device-configuration-yggdrasil        | Sailfish HW Adaptation yggdrasil                              | Paket
i  | pulseaudio-modules-droid-hidl                           | PulseAudio Droid HIDL module                                  | Paket
i  | pulseaudio-modules-droid-jb2q                           | PulseAudio Droid HAL modules                                  | Paket
i  | pulseaudio-modules-droid-jb2q-common                    | Common libs for the PulseAudio droid modules                  | Paket
i  | qt5-qpa-hwcomposer-plugin                               | Qt 5 QPA hwcomposer plugin                                    | Paket
i  | qtscenegraph-adaptation                                 | Scenegraph adaptation for Droid                               | Paket
i  | sailfish-connman-plugin-tethering-wmtwifi               | wmtWifi plugin for tethering                                  | Paket
i  | sailfish-device-encryption-community                    | Sailfish Device Encryption Community                          | Paket
i  | sailfish-device-encryption-community-droid              | Droid based device support for sailfish-device-encryption-c-> | Paket
i  | sailfish-device-encryption-community-generator          | SystemD Generator for Sailfish Device Encryption              | Paket
i  | sailfish-device-encryption-community-service            | Service for Sailfish Device Encryption                        | Paket
i  | sailfish-device-encryption-community-settings           | Settings for Sailfish Device Encryption                       | Paket
i  | sailfish-device-encryption-community-wizard             | Startup Wizard for Sailfish Device Encryption                 | Paket
i  | sailfish-fpd-community                                  | FPD Community                                                 | Paket
i  | systemd-ask-password-gui                                | Systemd Ask Password Service Agent                            | Paket
[root@VollaPhone defaultuser]# 

Can I do something to set the Volla to a state that the Jolla + Advanced Cam also works, as you did?

Have tested now and it’s also possible to make all Android (Waydroid) data accessible from SFOS. The command
devel-su ln -s /home/waydroid/data/media/0 /home/defaultuser/Android-Data
(after creating the ‘Android-Data’ directory in /home/defaultuser)
enables full access to the Waydroid user data. Waydroid’s Documents and Downloads folder are now accessible from SFOS in the same way.

edit: As you wrote, Waydroid has to be running to access the Android files. If Waydroid is not running, a defect symlink is reported.

I had to reflash the Volla (GS290) and unfortunately I forgot what things I did (in all details) to make Waydroid work at first successful installation time a few months ago. SFOS version is now 4.4.0.64 .

Now I’m sitting here with my fresh flashed and working Volla, want to reinstall Waydroid and see in Chum the following:

Waydroid (System)
Waydroid Gbinder Config Hybris
Waydroid Gbinder Config Mainline
Waydroid Runner (System, Video)
Waydroid Sensors
Waydroid Settings

Which of them should I install for a working system and which not? There are two ‘Gbinder’ versions, Hybris and Mainline. Which one shall I install? Which of the components are needed for the Volla and which not? In what order shall I install the components? What have I do do between the single steps? When should I do the ‘waydroid init’? Is somewhere reboot or configuration needed before proceeding to the next step?

Thanks very much for any help!

I don’t know anything, but shouldn’t GitHub - sailfishos-open/waydroid: Waydroid packaging for Sailfish OS help?

There is:

  • Install waydroid-settings or waydroid-runner package.
  • Install waydroid-gbinder-config-hybris or waydroid-gbinder-config-mainline depending on the type of device you have

This gives 4 possible combinations, so I don’t know what to do, therefore I asked. Shall I first choose the ‘settings’ or the ‘runner’? Shall I second choose the ‘hybris’ or the’mainline’? (for the Volla / GS290)

edit: what is hybris, what is mainline?

edit the edit: silly me, RTFM, started with 1. …runner and 2. …hybris, 3. Do the vi command @Sheigorath suggested in post # 79, 4. Run init, 5. remove dnsmasq, 6. Reboot … Works now!

Thank you all!!!

documentation is everything

there is piggz blog, i think i did mention the link either in this thread or in volla phone thread.
and i did write the step by step installation also somewhere here in that forum

should the image not start search also for my post, where i describe how to load an older working android image.
for me everything freshed then feb 2022 did not work