The Volla 22 (Gigaset GS5) Thread

Hardware Adaptation
#712

I have been using a Rephone (thanks to @Pingutux ) with SOFS, directly installed to the phone (not via SD card).

Compared to the VP22, which is still unlocked and SFOS runs only on the SD card, the Rephone works much better. Everything is smoother, faster and I have no real problems with the memory. On the VP22, SFOS is however at 4.4 while on the Rephone I have the latest 4.5.

On both phones, I have problem listing to music with any music app if the app was running when I had a call. The respect app has to be restarted.
What really does not work is taking videos on the rephone, this is really a pitty. It has been mentioned already, but is there really no way to make it work? How das Volla OS / Ubuntu Toch works with taking videos? Does anyone know?

I have sometimes the problem, that the FP sensor stops working. Only reboot helps.

Waydroid works nicely. I can use DKB and Ing DiBa banking apps (haven’t tested a transfer yet). However, after starting waydroid, SFOS is not able to get a GPS fix as the sensors might be blocked. This is known and should be fixed for waydroid on ubuntu touch

For a ported device, this works brilliant (waydroid does what I need) apart from taking videos.

A happy new year to all :slight_smile:

#713

Rephone with UT works with video.

#714

Your picture of UT shows OTA 21 - that is an old xenial 16.04 build. New UT like Rephone, Volla 22 run on Focal 20.04. Aktuell on OTA 3.

#715

So this might either be an unrelated bug or a regression with waydroid.
However, it seems it might be a bit unclear with a more recent version:

And of course, I don’t know how well SFOS and UT compare with respect to waydroid or how I could dig deeper into the issue.

#716

Waydroid is very experimental on both. If someone realy needs android, waydroid is not yet the way to go. In this case the official sfos on xperias with android support is the right way.

#717

Yeah, I think experiments need protocoled results, even computer experiments. Hence, I was writing this. And even more, if there is a chance to fix it. Although I have not figured anything out. But using waydroid similar to official android way with several open windows is with some tricks although possible and I suppose even having the Icons in the app grid.

Since Rephone and UT work with video, could there be chance to make video recording work on SFOS?

And furthermore, sometimes the fingerprint reader doesn’t work anymore. This:

does not help, as the service is called
sailfish-fpd-community
but restarting this doesn’t help either. So the only way to make fingerprint work again is restarting ( similiar to the GPS problem after waydroid, but without a real reason).

#718

I’ve observed this but very rarely (less than one time every couple of weeks). Do you have it more often? On a Volla/GS5 or rephone?

#719

I had it once in half a year using the Volla Phone and several times within 1 month for the rephone. Right now, for example. So I could try something :slight_smile:

#720

I don’t have an idea yet, but I’ll ask @piggz I think it’s not such a big deal since other issues exist.

#721
#722

So I ran the update for 4.6.0.13…and got stuck at Volla splash screen. FML :slight_smile:

#723

the new lxc in 4.6 breaks halium and waydroid loading … i need to comment out the line in the config that mentions apparmor.

You can fix it by booting into recovery, using adb to pull the config file, use adb shell to remount system as rw, then adb push the file back.

Would you like exact instructions or can you figure it out?

1 Like
#724

I have reflashed the system back to previous version. I am good for now

P.S.: MyBackup is awesome.

#725

You are referring to the lxc.service, right?

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=/usr/libexec/lxc/lxc-apparmor-load
ExecStart=/usr/libexec/lxc/lxc-containers start
ExecStop=/usr/libexec/lxc/lxc-containers stop
ExecReload=/usr/libexec/lxc/lxc-apparmor-load
# Environment=BOOTUP=serial
# Environment=CONSOLETYPE=serial
Delegate=yes
#726

no, the lxc config file in /var/lib/android/config. needs the line referencing apparmour commented out

1 Like
#727

Found it.

/var/lib/lxc/android/config

lxc.apparmor.profile = unconfined

So…comment it and run update with ssu like before and it should be fine?

#728

no, do the update, then before reboot, make the edit becuase it will be installed as part of the update

1 Like
#729

Gotcha. Will give it a go.

EDIT: Alright, the comment stayed after I pushed the update, so it looks like the config wasn’t overwritten. Successfully updated to 4.6 with no further incidents. Which means, now I can continue in recovering from backups.
So far, I only noticed Manufacturer and Product name under ‘About product’ showing UNKNOWN, but that’s about it.

EDIT 2: Camera is not working either.
Think I am gonna revert back on 4.5.0 and stay there for now.

#730

Yeah, looks like Waydroid is busted.

(003446) [22:34:20] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(003446) [22:34:20] New background process: pid=3647, output=background
lxc-start: waydroid: ../src/lxc/network.c: netdev_configure_server_veth: 711 No such file or directory - Failed to attach "veth7zZ5S2" to bridge "waydroid0", bridge interface doesn't exist
lxc-start: waydroid: ../src/lxc/network.c: lxc_create_network_priv: 3427 No such file or directory - Failed to create network device
lxc-start: waydroid: ../src/lxc/start.c: lxc_spawn: 1840 Failed to create the network
lxc-start: waydroid: ../src/lxc/start.c: __lxc_start: 2107 Failed to spawn container "waydroid"
lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 126
lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run lxc.hook.post-stop for container "waydroid"
lxc-start: waydroid: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: waydroid: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
(003446) [22:34:20] waiting 10 seconds for container to start...
(003446) [22:34:21] waiting 9 seconds for container to start...
(003446) [22:34:22] waiting 8 seconds for container to start...
(003446) [22:34:24] waiting 7 seconds for container to start...
(003446) [22:34:25] waiting 6 seconds for container to start...
(003446) [22:34:26] waiting 5 seconds for container to start...
(003446) [22:34:27] waiting 4 seconds for container to start...
(003446) [22:34:28] waiting 3 seconds for container to start...
(003446) [22:34:29] waiting 2 seconds for container to start...
(003446) [22:34:30] waiting 1 seconds for container to start...
(003446) [22:34:31] ERROR: container failed to start
(003446) [22:34:31] See also: <https://github.com/waydroid>
(003446) [22:34:31] Traceback (most recent call last):
  File "/opt/waydroid/tools/__init__.py", line 68, in main
    actions.container_manager.start(args)
  File "/opt/waydroid/tools/actions/container_manager.py", line 131, in start
    raise OSError("container failed to start")
OSError: container failed to start
1 Like
#731

So…reverted to 4.5.0.25.
Camera is now black (same with Advanced Camera).

sigh Not my day today it would seem.

1 Like