The Volla 22 (Gigaset GS5) Thread

Hardware Adaptation
790

@poetaster I checked on their Website and in this thread, unfortunately no active link seems to be available. Therefore I will contact them.

For documentary reasons, here the summary of my trials:

  • Trying to flash so far only SFOS 4.4 build.

  • From VollaOS12 → leads to boot process stucked in Vollalogo (no SFOS logo was there)

  • From VollaOS13 → leads to only fastboot loading

  • From VollaOS14 → leads to only fastboot loading

I will try to optain VollaOS11 and give an update here.
Parallely I am wondering, if I should try SFOS 4.5 build. Or wait for the next build from @piggz. But when will it be ready? And from what base is it supposed to be flashed?

Finally, here the console messages for VollaOS13 → SFOS 4.4 build. I had to remove the fastboot check from the script, as it was stucked there. Also, an error appeared, when asking for reboot. Anyways it rebooted successfully.

Linux terminal:~/Schreibtisch/SailfishOS-mimameid$ fastboot devices 
GS5...	fastboot
Linux terminal:~/Schreibtisch/SailfishOS-mimameid$ sh flash.sh 

Be aware, the flashing process might take up to 10 minutes.
The screen is expected to go black. This is fine, flashing continues.

product: k69v1_64_k419
Sending 'boot_a' (32768 KB)                        OKAY [  1.103s]
Writing 'boot_a'                                   OKAY [  0.558s]
Finished. Total time: 1.867s
Sending sparse 'super' 1/18 (131069 KB)            OKAY [  4.269s]
Writing 'super'                                    OKAY [  6.026s]
Sending sparse 'super' 2/18 (125000 KB)            OKAY [  4.254s]
Writing 'super'                                    OKAY [  2.011s]
Sending sparse 'super' 3/18 (131068 KB)            OKAY [  4.289s]
Writing 'super'                                    OKAY [  2.692s]
Sending sparse 'super' 4/18 (120196 KB)            OKAY [  4.042s]
Writing 'super'                                    OKAY [  2.313s]
Sending sparse 'super' 5/18 (123840 KB)            OKAY [  4.264s]
Writing 'super'                                    OKAY [  3.183s]
Sending sparse 'super' 6/18 (131068 KB)            OKAY [  4.275s]
Writing 'super'                                    OKAY [  2.414s]
Sending sparse 'super' 7/18 (127240 KB)            OKAY [  4.201s]
Writing 'super'                                    OKAY [  3.038s]
Sending sparse 'super' 8/18 (127972 KB)            OKAY [  4.319s]
Writing 'super'                                    OKAY [  2.648s]
Sending sparse 'super' 9/18 (125140 KB)            OKAY [  4.155s]
Writing 'super'                                    OKAY [  3.217s]
Sending sparse 'super' 10/18 (128732 KB)           OKAY [  4.438s]
Writing 'super'                                    OKAY [  3.480s]
Sending sparse 'super' 11/18 (130512 KB)           OKAY [  4.332s]
Writing 'super'                                    OKAY [  2.817s]
Sending sparse 'super' 12/18 (126876 KB)           OKAY [  4.300s]
Writing 'super'                                    OKAY [ 42.612s]
Sending sparse 'super' 13/18 (131050 KB)           OKAY [  4.647s]
Writing 'super'                                    OKAY [ 59.754s]
Sending sparse 'super' 14/18 (127775 KB)           OKAY [  4.140s]
Writing 'super'                                    OKAY [ 20.477s]
Sending sparse 'super' 15/18 (130678 KB)           OKAY [  4.224s]
Writing 'super'                                    OKAY [ 25.926s]
Sending sparse 'super' 16/18 (129523 KB)           OKAY [  4.217s]
Writing 'super'                                    OKAY [ 26.909s]
Sending sparse 'super' 17/18 (126804 KB)           OKAY [  4.102s]
Writing 'super'                                    OKAY [ 37.939s]
Sending sparse 'super' 18/18 (37537 KB)            OKAY [  1.329s]
Writing 'super'                                    OKAY [ 33.256s]
Finished. Total time: 355.399s
Setting current slot to 'a'                        OKAY [  0.161s]
Finished. Total time: 0.164s

Flashing process successful.
Reboot now? [Y/n] 

flash.sh: 47: read: Illegal option -s
Rebooting                                          OKAY [  0.003s]
Finished. Total time: 0.053s
Linux terminal:~/Schreibtisch/SailfishOS-mimameid$
791

Ok, as @piggz mentioned the mimameid (volla22) firmware is android 11 based and is moving to 12 with the 4.5 (err, I think) release which is not quite 100% (no video recording, which is why my main phone is still 4.4).

I just looked around and found the ubports firmware for volla11.

volla-11.1-20221017-stable-SPFLASH-mimameid.zip
volla-12.1-20240228-stable-SPFLASH-mimameid.zip
volla-mimameid-11.0-ubports-installer-bootstrap.zip

I think the the 11 files might be what you need?

2 Likes
792

hy…
i have a Rephone with android 12 can i flash Volla OS via UB Port installer…over Android 12?

793

@poetaster Thanks for you help and explanation, I agree, thats whats needed. Both VollaOS11 files seems not be online anymore. I will check, if there is still an archive.

794

For new images for the V22 based on android-12, please see Releases · HelloVolla/sailfish-release-halium-mimameid · GitHub

1 Like
795

Oh, way. So, that’s a 5 which requires flashing the latest volla os first, correct? So I can stop testing the 4.5 image :slight_smile: EDIT: @piggz you move to github actions for a particular reason?

796

Correct, ive tested against 12, and would like ti know if it aso works on 13 or 14. The github change is due to gitlab limiting builder minutes on non foss projects, and i cant be bothered with the admin of sortibg that out.

2 Likes
797

Thanks! I’ll give it a go as soon as I come up for air from under the solder fumes!

798

Just now flashed a Vollaphone 22+ from VollaOS12 to the new Sailfishport 5.0.0.62 from Mr.Piggz and it worked like a charm! @piggz Thank you very much, awesome work!

Just as side note, the two issues with the flash.sh script I still had (fastboot check and reboot confirmation).

2 Likes
799

Hello,

audio jack working ?

800

Jack detection works, but audio output doesnt … ill look into that.

1 Like
801

my Volla Phone 22Plus (Rephone) is on latest Android 14 can i flash the new Sailfish OS?

802

Does anyone has experienced that a VollaPhone 22 can not be unlocked via fastboot although OEM unlocking and USB debugging is enabled. I upgraded Volla OS to the latest version via Settings.

803

I have successfully update my Rephone (the VP22 is still locked) and the new release feels nicely. However, I can not get waydroid running:

waydroid init

doesnt do anything at all
and the system partition tends to fill itself quickly, but I dont know why.

Edit: As soon as I try to cop waydroid images to /home/waydroid, the root partition fills up. And the waydroid init problem can be partly solved by disabling IPV6

sysctl -w net.ipv6.conf.default.disable_ipv6=1

to end up

[17:07:04] ERROR: Failed to get vendor OTA channel: https://ota.waydro.id/vendor/waydroid_arm64/HALIUM_12.json
[17:07:04] See also: <https://github.com/waydroid>
Run 'waydroid log' for details.

One more edit:
If I copy the waydroid images via sftp to my home directory and then from there to /home/waydroid the system partition just fills, although (approx 3.5 GB) I have only operated in /home

And another:
Is this related to the encryption? I found a home.img in /userdata which increases as I operate in my home directory. But this whould then limit the size of the home partitation to the size of the system partition?

Last edit for today:
The Volla 22 (Gigaset GS5) Thread - #429 by teracube did the trick for the full partition
Waydroid is still an open question

1 Like
804

python has a problem with IPV6, which also affects python apps like tidalplayer. I dont know, if it is a Volla 22 specific problem or SFOS 5

sysctl -w net.ipv6.conf.all.disable_ipv6=1

And I suppose, I can confirm, that with the current config for waydroid, waydroid is not running on a fresh SFOS installation on a finally unlocked original VP 22

[defaultuser@Phone22 ~]$ cat /etc/gbinder.d/anbox-mainline.conf
[Protocol]
/dev/anbox-binder = aidl3
/dev/anbox-vndbinder = aidl3
/dev/anbox-hwbinder = hidl

[ServiceManager]
/dev/anbox-binder = aidl3
/dev/anbox-vndbinder = aidl3
/dev/anbox-hwbinder = hidl

I constantly get

[FullUI] [21:00:03] Failed to get service waydroidplatform, trying again…

which is not nice, some android are still important and they worked on the older SFOS 4.5 in the Rephone and VP22

Edit:
Another thing: I can not create a hotspot and share the connection. It was unreliable in the older SFOS versions on the VP22/Rephone and has not improved with this update.

805

Hey everyone. Is anyone running Mullvad VPN on their GS5? I can import the config file, but SFOS doesn’t prompt for a username and password just leading to a connection error.

I use the Android .opvn file by the Mullvad website.

807

I used to have rephone, just the same like GS5 / Volla22, but with 6 GB Ram and battery to change, with Sailfish. But it seems that there is no progress anymore, no updates, I guess no future for it. Correct me please if I am wrong. I changed to UT and this is good and ongoing, especially when 24.04. will come this September. Works stable and good, even with Waydroid.

1 Like
808
1 Like
809

The volla phone 22 user builds are updated to 5.0.0.71.

This includes changes to the repo names to use just 5.0, so all future updates in the 5.0 series will work without me having to rebuild/republish things.

To update a current device, manually edit /usr/share/ssu/features.d/adaptation-community.ini

to

[repositories]
adaptation-community = https://repo.sailfishos.org/obs/nemo:/testing:/hw:/volla:/halium-mimameid:/%(releaseMajorMinor)/sailfishos_%(releaseMajorMinor)_%(arch)
adaptation-halium = https://repo.sailfishos.org/obs/nemo:/testing:/hw:/halium:/13:/%(releaseMajorMinor)/sailfishos_%(releaseMajorMinor)_%(arch)

Then run

ssu ur

zypper ref

zypper dup

6 Likes
810

There is still the ‘kernel’ repo which causes issues:

Repository ‘adaptation-community-kernel’ is invalid.
[adaptation-community-kernel|plugin:ssu?repo=adaptation-community-kernel] Valid metadata not found at specified URL
History:

  • [adaptation-community-kernel|plugin:ssu?repo=adaptation-community-kernel] Repository type can’t be determined.

Should one ignore that?

EDIT: and I’m not sure this is important but:

adaptation-halum.ini

is present along with

adaptation-community-common.ini
adaptation-community.ini
adaptation-halum.ini