The Volla 22 (Gigaset GS5) Thread

ric9k · 13 July 2023 17:53

About Waydroid:

Is this still necessary for the GS5?

Also, on the Waydroid Github page, it is advised to install waydroid-gbinder-config-hybris or waydroid-gbinder-config-mainline.
Which one is the good one for the GS5, please?

I tried the way described bo @Seven.of.nine, the way described on the Github page, modified /etc/gbinder.d or not, I can’t get WD to start. (Really tried and read for some hours)

Here is my log:

[waydroid-sensors-daemon] Got plugin_interface local.OrientationSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/orientationsensor
[waydroid-sensors-daemon] Got new plugin for pressuresensor with pid 4473 and session 12
[waydroid-sensors-daemon] Got plugin_string pressuresensor
[waydroid-sensors-daemon] Got plugin_interface local.PressureSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/pressuresensor
[waydroid-sensors-daemon] Got new plugin for proximitysensor with pid 4473 and session 13
[waydroid-sensors-daemon] Got plugin_string proximitysensor
[waydroid-sensors-daemon] Got plugin_interface local.ProximitySensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/proximitysensor
[waydroid-sensors-daemon] Failed to create SensorfwStepcounterSensor: Could not create sensorfw backend
[waydroid-sensors-daemon] Failed to create SensorfwTemperatureSensor: Could not create sensorfw backend
(004272) [18:37:59] % mount -o remount,ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(004272) [18:37:59] % mount -o bind /vendor/lib/egl /var/lib/waydroid/rootfs/vendor/lib/egl
(004272) [18:37:59] % mount -o bind /vendor/lib64/egl /var/lib/waydroid/rootfs/vendor/lib64/egl
(004272) [18:37:59] % mount -o bind /vendor/odm /var/lib/waydroid/rootfs/odm_extra
(004272) [18:37:59] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(004272) [18:37:59] Save config: /var/lib/waydroid/waydroid.cfg
(004272) [18:37:59] % mount -o bind /home/defaultuser/.local/share/waydroid/data /var/lib/waydroid/data
(004272) [18:37:59] % chmod 777 -R /dev/ashmem
(004272) [18:37:59] % chmod 777 -R /dev/MTK_SMI
(004272) [18:37:59] % chmod 777 -R /dev/mdp_sync
(004272) [18:37:59] % chmod 777 -R /dev/mtk_cmdq
(004272) [18:37:59] % chmod 777 -R /dev/graphics
(004272) [18:37:59] % chmod 777 -R /dev/ion
(004272) [18:37:59] % chmod 777 -R /dev/fb0
(004272) [18:37:59] % chmod 777 -R /dev/video1
(004272) [18:37:59] % chmod 777 -R /dev/video0
(004272) [18:37:59] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid – /init
(004272) [18:37:59] New background process: pid=4525, output=background
lxc-start: waydroid: utils.c: lxc_can_use_pidfd: 1772 Kernel does not support pidfds
lxc-start: waydroid: network.c: netdev_configure_server_veth: 708 No such file or directory - Failed to attach “vethdHSzBl” to bridge “waydroid0”, bridge interface doesn’t exist
lxc-start: waydroid: network.c: lxc_create_network_priv: 3419 No such file or directory - Failed to create network device
lxc-start: waydroid: start.c: lxc_spawn: 1826 Failed to create the network
lxc-start: waydroid: start.c: __lxc_start: 2053 Failed to spawn container “waydroid”
lxc-start: waydroid: conf.c: run_buffer: 323 Script exited with status 126
lxc-start: waydroid: start.c: lxc_end: 996 Failed to run lxc.hook.post-stop for container “waydroid”
lxc-start: waydroid: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: waydroid: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
(004272) [18:37:59] waiting 10 seconds for container to start…
(004272) [18:38:00] waiting 9 seconds for container to start…
(004272) [18:38:01] waiting 8 seconds for container to start…
(004272) [18:38:02] waiting 7 seconds for container to start…
(004272) [18:38:03] waiting 6 seconds for container to start…
(004272) [18:38:04] waiting 5 seconds for container to start…
(004272) [18:38:05] waiting 4 seconds for container to start…
(004272) [18:38:06] waiting 3 seconds for container to start…
(004272) [18:38:07] waiting 2 seconds for container to start…
(004272) [18:38:08] waiting 1 seconds for container to start…
(004272) [18:38:09] ERROR: container failed to start
(004272) [18:38:09] See also: https://github.com/waydroid
(004272) [18:38:09] 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

(004801) [18:40:22] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(004801) [18:40:22] *** output passed to waydroid stdout, not to this log ***

Mainly, from the log, I’d say I see:

[waydroid-sensors-daemon] Failed to create SensorfwStepcounterSensor: Could not create sensorfw backend
[waydroid-sensors-daemon] Failed to create SensorfwTemperatureSensor: Could not create sensorfw backend

and

lxc-start: waydroid: utils.c: lxc_can_use_pidfd: 1772 Kernel does not support pidfds

But… well, I’m drying a bit.

Seven.of.nine · 13 July 2023 18:11

The ‘hybris’ version.

For me it didn’t work before changing aidl2 to aidl3. This occurs 4 times in the file.

piggz · 13 July 2023 18:33

thats interesting … for the gs5, i manually create all the stock users and groups … its possible one is missing. could you compare against a regular volla?

poetaster · 13 July 2023 19:06

Ok, I’ll give it a go tomorrow. Are they just vigr / /etc/password and co?

ric9k · 13 July 2023 19:15

Thanks, @Seven.of.nine.

Progressing!
I uninstalled and removed waydroid files, then I installed from Chum:
-Waydroid
-Waydroid Runner
-with zypper: waydroid-gbinder-config-hybris.
Then, I did waydroid init.
It downloaded and extracted https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_arm64/lineage-18.1-20230422-VANILLA-waydroid_arm64-system.zip/download and https://sourceforge.net/projects/waydroid/files/images/vendor/waydroid_arm64/lineage-18.1-20230422-HALIUM_11-waydroid_arm64-vendor.zip/download

I edited the file /etc/gbinder.d/anbox-hybris.conf and changed aidl2 to aidl3.
Uncommented #bind-interfaces in /etc/dnsmasq.conf
Rebooted.

Starting WD from the app grid,
The spinner turns and it says “Starting Android session”, then "Waiting for Android UI and nothing after that.

Here is the new log:

[waydroid-sensors-daemon] Failed to create SensorfwHumiditySensor: Could not create sensorfw backend
[waydroid-sensors-daemon] Got new plugin for alssensor with pid 4278 and session 8
[waydroid-sensors-daemon] Got plugin_string alssensor
[waydroid-sensors-daemon] Got plugin_interface local.ALSSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/alssensor
(004138) [21:04:17] % mount -o remount,ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
[waydroid-sensors-daemon] Got new plugin for magnetometersensor with pid 4278 and session 9
[waydroid-sensors-daemon] Got plugin_string magnetometersensor
[waydroid-sensors-daemon] Got plugin_interface local.MagnetometerSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/magnetometersensor
[waydroid-sensors-daemon] Got new plugin for orientationsensor with pid 4278 and session 10
[waydroid-sensors-daemon] Got plugin_string orientationsensor
[waydroid-sensors-daemon] Got plugin_interface local.OrientationSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/orientationsensor
(004138) [21:04:17] % mount /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
[waydroid-sensors-daemon] Got new plugin for pressuresensor with pid 4278 and session 12
[waydroid-sensors-daemon] Got plugin_string pressuresensor
[waydroid-sensors-daemon] Got plugin_interface local.PressureSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/pressuresensor
[waydroid-sensors-daemon] Got new plugin for proximitysensor with pid 4278 and session 13
[waydroid-sensors-daemon] Got plugin_string proximitysensor
[waydroid-sensors-daemon] Got plugin_interface local.ProximitySensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/proximitysensor
[waydroid-sensors-daemon] Failed to create SensorfwStepcounterSensor: Could not create sensorfw backend
[waydroid-sensors-daemon] Failed to create SensorfwTemperatureSensor: Could not create sensorfw backend
(004138) [21:04:17] % mount -o remount,ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(004138) [21:04:17] % mount -o bind /vendor/lib/egl /var/lib/waydroid/rootfs/vendor/lib/egl
(004138) [21:04:17] % mount -o bind /vendor/lib64/egl /var/lib/waydroid/rootfs/vendor/lib64/egl
(004138) [21:04:17] % mount -o bind /vendor/odm /var/lib/waydroid/rootfs/odm_extra
(004138) [21:04:17] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(004138) [21:04:17] Save config: /var/lib/waydroid/waydroid.cfg
(004138) [21:04:17] % mount -o bind /home/defaultuser/.local/share/waydroid/data /var/lib/waydroid/data
(004138) [21:04:17] % chmod 777 -R /dev/ashmem
(004138) [21:04:17] % chmod 777 -R /dev/MTK_SMI
(004138) [21:04:17] % chmod 777 -R /dev/mdp_sync
(004138) [21:04:17] % chmod 777 -R /dev/mtk_cmdq
(004138) [21:04:17] % chmod 777 -R /dev/graphics
(004138) [21:04:17] % chmod 777 -R /dev/ion
(004138) [21:04:17] % chmod 777 -R /dev/fb0
(004138) [21:04:17] % chmod 777 -R /dev/video1
(004138) [21:04:17] % chmod 777 -R /dev/video0
(004138) [21:04:17] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid – /init
(004138) [21:04:17] New background process: pid=4330, output=background
lxc-start: waydroid: utils.c: lxc_can_use_pidfd: 1772 Kernel does not support pidfds
lxc-start: waydroid: utils.c: open_without_symlink: 1062 Too many levels of symbolic links - vibrator in /usr/lib64/lxc/rootfs/sys/class/leds/vibrator was a symbolic link!
(004138) [21:04:17] Save session config: /var/lib/waydroid/session.cfg
(004240) [21:04:18] Failed to start Clipboard manager service, check logs
(004138) [21:04:18] Failed to add service waydroidhardware: -2147483647
(004138) [21:04:18] Failed to add service waydroidhardware: -2147483647
(004378) [21:04:19] Failed to get service waydroidplatform, trying again…
(004378) [21:04:20] Failed to get service waydroidplatform, trying again…
(004378) [21:04:21] Failed to get service waydroidplatform, trying again…
(004378) [21:04:22] Failed to get service waydroidplatform, trying again…
(004378) [21:04:23] Failed to get service waydroidplatform, trying again…
(004378) [21:04:24] Failed to get service waydroidplatform, trying again…
(004378) [21:04:25] Failed to get service waydroidplatform, trying again…
(004378) [21:04:26] Failed to get service waydroidplatform, trying again…
(004378) [21:04:27] Failed to get service waydroidplatform, trying again…
(004745) [21:04:28] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(004745) [21:04:28] *** output passed to waydroid stdout, not to this log ***
(004378) [21:04:28] Failed to get service waydroidplatform, trying again…
…
(004378) [21:10:55] Failed to get service waydroidplatform, trying again…
(005474) [21:10:55] UserMonitor service is not even started
(005474) [21:10:55] Clipboard service is not even started
(004240) [21:10:56] UserMonitor service is not even started
(004240) [21:10:56] Clipboard service is not even started
(004378) [21:10:56] Failed to get service waydroidplatform, trying again…
(004138) [21:10:56] session manager stopped, stopping container and waiting…
(004138) [21:10:56] % lxc-stop -P /var/lib/waydroid/lxc -n waydroid -k
lxc-start: waydroid: conf.c: run_buffer: 323 Script exited with status 126
lxc-start: waydroid: start.c: lxc_end: 996 Failed to run lxc.hook.post-stop for container “waydroid”
(004138) [21:10:56] % /opt/waydroid/data/scripts/waydroid-net.sh stop
vnic is waydroid0
(004138) [21:10:56] % pidof waydroid-sensord
4278
(004138) [21:10:56] % kill -9 4278
(004138) [21:10:56] % umount /home/waydroid/rootfs/vendor/waydroid.prop
(004138) [21:10:56] % umount /home/waydroid/rootfs/vendor/lib64/egl
(004138) [21:10:56] % umount /home/waydroid/rootfs/vendor/lib/egl
(004138) [21:10:56] % umount /home/waydroid/rootfs/vendor
(004138) [21:10:56] % umount /home/waydroid/rootfs/odm_extra
(004138) [21:10:56] % umount /home/waydroid/rootfs
(004138) [21:10:57] % umount /home/waydroid/data
(004138) [21:10:57] % chmod 666 -R /dev/anbox-binder
(004138) [21:10:57] % chmod 666 -R /dev/anbox-vndbinder
(004138) [21:10:57] % chmod 666 -R /dev/anbox-hwbinder
(004138) [21:10:57] Container manager is waiting for session to load
(004378) [21:10:57] Failed to get service waydroidplatform, trying again…
(004378) [21:10:58] Failed to get service waydroidplatform, trying again…
(004378) [21:10:59] Failed to get service waydroidplatform, trying again…

piggz · 13 July 2023 19:35

github.com

sailfishos/connman/blob/961d05ac6ced860fb018332f94cd98fe43fdc633/connman/vpn/plugins/vpn.c#L520C24-L520C27

      
        
            	if (gid > 0 && setgid(gid))

Pasik2 · 13 July 2023 20:09

Here are the correct settings to waydroid-gbinder-config-hybris.
Kuvakaappaus - 2023-07-13 23-07-28

ric9k · 13 July 2023 20:28

Wooow,
I missed this one. I only focussed on “aidl3”.
Many thanks @Pasik2 for repeating for distracted guys!

Impressing, a whole android-alike environment has just started full screen!

Here repeated in text mode to ease copy-paste:
/etc/gbinder.d/anbox-hybris.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

poetaster · 14 July 2023 09:49

Group, Volla / GS290 (4.4)

vpn:x:1016:
openvpn:x:999:

root:x:0:
bin:x:1:
daemon:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mem:x:8:
kmem:x:9:
wheel:x:10:
cdrom:x:11:
mail:x:12:
man:x:15:
dialout:x:18:
floppy:x:19:
games:x:20:
tape:x:33:
video:x:39:defaultuser
ftp:x:50:
lock:x:54:
audio:x:1005:pulse,defaultuser
users:x:100:defaultuser
nobody:x:9999:
utmp:x:22:
utempter:x:35:
debuggerd:x:1045:
lmkd:x:1069:
iorapd:x:1071:
mediadrm:x:1031:
radio:x:1001:
net_admin:x:3005:
net_bw_acct:x:3007:
net_bw_stats:x:3006:
sdcard_rw:x:1015:
media_image:x:1057:
cache:x:2001:
net_raw:x:3004:
adb:x:1011:
input:x:1004:defaultuser
media_video:x:1056:
statsd:x:1066:
net_bt_admin:x:3001:
compass:x:1008:
secure_element:x:1068:
nfc:x:1027:
dbus:x:1038:
lowpan:x:1063:
network_stack:x:1073:
clat:x:1029:
sdcard_pics:x:1033:
trunks:x:1049:
mdnsr:x:1020:
bluetooth:x:1002:defaultuser
sdcard_all:x:1035:
logd:x:1036:
llkd:x:1070:
readproc:x:3009:
drm:x:1019:
diag:x:2002:
webview_zygote:x:1053:
ese:x:1060:
dhcp:x:1014:
sdcard_r:x:1028:
hsm:x:1064:
vehicle_network:x:1054:
gsid:x:1074:
usb:x:1018:
media_obb:x:1059:
audioserver:x:1041:
reserved_disk:x:1065:
mediacodec:x:1046:
media_audio:x:1055:
firewall:x:1048:
misc:x:9998:
package_info:x:1032:
dns_tether:x:1052:
mediaex:x:1040:
everybody:x:9997:
log:x:1007:
metricsd:x:1043:
system:x:1000:
sdcard_av:x:1034:
nvram:x:1050:
camera:x:1006:defaultuser
automotive_evs:x:1062:
dns:x:1051:
inet:x:3003:defaultuser
gps:x:1021:
shell:x:2000:
tlsdate:x:1039:
wakelock:x:3010:
graphics:x:1003:defaultuser
tombstoned:x:1058:
vpn:x:1016:
metrics_coll:x:1042:
incidentd:x:1067:
mount:x:1009:
net_bt:x:3002:
install:x:1012:
cameraserver:x:1047:
uhid:x:3011:
loop_radio:x:1030:
overflowuid:x:65534:
keystore:x:1017:
media:x:1013:defaultuser
mtp:x:1024:defaultuser
gpu_service:x:1072:
drmrpc:x:1026:
ota_update:x:1061:
webserv:x:1044:
media_rw:x:1023:defaultuser
wifi:x:1010:
shared_relro:x:1037:
openvpn:x:999:
kvm:x:36:
render:x:998:
systemd-journal:x:190:
systemd-network:x:997:
privileged:x:996:sailfish-mdm
sailfish-mdm:x:995:
sailfish-radio:x:994:
sailfish-actdead:x:993:
sailfish-system:x:992:sailfish-mdm,defaultuser
ssu:x:991:defaultuser
sailfish-alarms:x:990:defaultuser
sailfish-datetime:x:989:defaultuser
timed:x:988:defaultuser
sailfish-phone:x:987:defaultuser
sailfish-messages:x:986:defaultuser
sailfish-authentication:x:985:
pulse-access:x:984:root
pulse:x:171:
messagebus:x:82:
sshd:x:74:
account-jolla:x:983:defaultuser
account-jabber:x:982:defaultuser
account-nextcloud:x:981:defaultuser
account-onlinesync:x:980:defaultuser
account-email:x:979:defaultuser
account-yahoo:x:978:defaultuser
account-memotoo:x:977:defaultuser
account-fruux:x:976:defaultuser
account-google:x:975:defaultuser
account-webcal:x:974:defaultuser
encryption-hwcrypt:x:973:
account-twitter:x:972:defaultuser
account-vk:x:971:defaultuser
account-onedrive:x:970:defaultuser
account-dropbox:x:969:defaultuser
defaultuser:x:100000:
screen:x:84:

and GS5 (4.5)

openvpn:x:999:

root:x:0:
bin:x:1:
daemon:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mem:x:8:
kmem:x:9:
wheel:x:10:
cdrom:x:11:
mail:x:12:
man:x:15:
dialout:x:18:
floppy:x:19:
games:x:20:
tape:x:33:
video:x:39:defaultuser
ftp:x:50:
lock:x:54:
audio:x:63:pulse,defaultuser
users:x:100:defaultuser
nobody:x:65534:
utmp:x:22:
utempter:x:35:
openvpn:x:999:
input:x:998:defaultuser
kvm:x:36:
render:x:997:
systemd-journal:x:190:
systemd-network:x:996:
privileged:x:995:sailfish-mdm
sailfish-mdm:x:994:
sailfish-radio:x:993:
sailfish-actdead:x:992:
sailfish-system:x:991:sailfish-mdm,defaultuser
ssu:x:990:defaultuser
sailfish-alarms:x:989:defaultuser
sailfish-datetime:x:988:defaultuser
timed:x:987:defaultuser
sailfish-phone:x:986:defaultuser
sailfish-messages:x:985:defaultuser
sailfish-authentication:x:984:
pulse-access:x:983:root
pulse:x:171:
messagebus:x:82:
sshd:x:74:
account-jolla:x:982:defaultuser
account-jabber:x:981:defaultuser
account-nextcloud:x:980:defaultuser
account-onlinesync:x:979:defaultuser
account-email:x:978:defaultuser
account-yahoo:x:977:defaultuser
account-memotoo:x:976:defaultuser
account-fruux:x:975:defaultuser
account-google:x:974:defaultuser
account-webcal:x:973:defaultuser
encryption-hwcrypt:x:972:
mtp:x:1024:defaultuser
account-twitter:x:971:defaultuser
account-vk:x:970:defaultuser
account-onedrive:x:969:defaultuser
account-dropbox:x:968:defaultuser
system:x:1000:
radio:x:1001:
bluetooth:x:1002:defaultuser
graphics:x:1003:defaultuser
camera:x:1006:defaultuser
log:x:1007:
compass:x:1008:
mount:x:1009:
wifi:x:1010:
media:x:1013:defaultuser
dhcp:x:1014:
adb:x:1011:
install:x:1012:
drm:x:1019:
gps:x:1021:
nfc:x:1027:
shell:x:2000:
cache:x:2001:
diag:x:2002:
net_bt_admin:x:3001:
net_bt:x:3002:
inet:x:3003:defaultuser
net_raw:x:3004:
misc:x:9998:
defaultuser:x:100000:
appsupport-root:x:500000:
appsupport-system:x:501000:appsupport-root
appsupport-radio:x:501001:appsupport-root
appsupport-media_rw:x:501023:appsupport-root
screen:x:84:

ric9k · 14 July 2023 12:23

Thank you,
Do you think it is just sufficient to add vpn:x:1016: into /etc/group?
Also something to add into /etc/passwd?

I could try but am being very prudent as the GS5 is already my daily since the second day

Btw, @piggz, is there a way to clone the entire system as we can do with dd into recovery mode on the e.g. XA2’s /dev/mmcblk0p76?

poetaster · 15 July 2023 12:10

Adding the vpn group/user should be just fine.

adduser vpn --system --shell=/sbin/nologin --no-create-home

Is what I did.

poetaster · 15 July 2023 15:37

I just noticed that if I DON’T set Pin code which just happened by accident, it reboots and finds the SIM and connects just fine. So, @piggz it looks like it is the Pin code setting itself which causes issues. Perhaps can’t be read properly when set to ‘on’ … it’s odd. Right now, just to reassure myself, I rebooted without Pin code set and it immediately worked.

ric9k · 15 July 2023 23:18

I did too but withoit results. I’ll try to compare/post the log when I have time.

ric9k · 15 July 2023 23:36

I’m not sure.
Maybe, if you try again, it’ll be the opposite.
I rebooted/booted/battery away +booted tens of times. With or without PIN fiddling.
The only +/- regular behaviour I could deduce is a beauty of scientific conclusion:
“After some tries, it finally always works. Between 1 and 4, generally”.

Still in pure subjectivity, if I dare, I’d conntradict you about the PIN setting. I have the feeling it does nothing, as validation is not possible and as it seems not to influence the results.
Haha at this point, it is more clairvoyant than something else.

poetaster · 16 July 2023 11:41

Well, I only have datapoints on two devices but with the rephone and the GS5 the behaviour is the same. With the Pin code simply disabled, they both come up and get 4G without any action.

The a) turn off Pin code, b) turn it on, c) verify with Pin code, d) shut down Settings app, e) reboot dance is also the same on both devices. I’ll have to try it with two SIM cards when I get a chance.

ric9k · 16 July 2023 11:53

Ok.
I’ll try again then.
The good point is that it is always working at the end, making this port/device trustable

Pasik2 · 16 July 2023 16:06

I have two Volla 22 phones. In the second, the sim card pin query is always off. Even so, 1-4 reboots are required. On the other phone, the pin code inquiry is always on and the result is the same, 1-4 reboots for the sim to work.

teracube · 16 July 2023 19:26

I have updated successful my GS5 to 4.5.0.21 via SSU UR

poetaster · 17 July 2023 10:31

Weird. I’ve repeated my ‘Open settings, unset Pin Code, Set Pin code, Close settings, reboot’ procedure repeatedly and it always works. Just rebooted, for the hell of it, the GS5 which has Pin Code off and it just worked. I wonder if there’s something else in the mix. Something I have installed or configured. Hmmm. I’ll wait to dig until I’ve got 4.5.0.21 on those devices.

jenix · 22 July 2023 06:19

I bought a rephone (yay, 6 GB of ram) and successfully flashed the 4.4.0.72 build for the Volla 22. Thank you, piggz, for all the amazing work.
Unfortunately, I noticed that the volume buttons are not working in SFOS. The physical press seems to get detected. When the phone is suspended (sleep mode) and I press one of the buttons (Vol Up in this case), there is a wakeup event in the journal:

Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10]scp status: sleep mode
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10]suspend warning: SYS_CONN is on!!!
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10][name:spm&]NO spm_get_is_infra_pdn !!!
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10][SPM-PMIC] [dlpt_R] pre_SOC=90 SOC=90 skip
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10][name:spm&][SPM] sec = 4800, wakesrc = 0x687ddef (1)(1)
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10][name:spm&][SPM] wlk_cntcv_l = 0xed160e48, wlk_cntcv_h = 0x2
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10][name:spm&][SPM] md_settle = 99, settle = 33
Jul 22 07:56:55 Phone22 kernel: -(0)[2897:kworker/u16:10][name:spm&][SPM] suspend wake up by R12_KP_IRQ_B, timer_out = 725, r13 = 0x6046000, debug_flag = 0x1913f0 0x0, r12 = 0x4, r12_ext = 0x0, raw_sta = 0x0, idle_sta = 0x9fb, req_sta = 0x2000400, event_reg = 0x90100000, isr = 0x0, raw_ext_sta = 0x4005a0a5, wake_misc = 0x0, pcm_flag = 0x80080 0x0, req = 0x0, wlk_cntcv_l = 0xed1a9024, wlk_cntcv_h = 0x2, 26M_off_pct = 0

However, pressing the buttons when the phone is active does not change the volume. Can it be that they are wrongly mapped on the rephone? Is there any way to find out?

Also, as the screen of the Volla 22 / rephone has rounded edges and the front camera in the top middle, some of the screen content isn’t displayed properly. The major issue with that is that the clock (which sits in the middle of the top bar) gets completely covered by the front camera. I presume you can manipulate the layout of the top bar, maybe align the clock on the left (next to the battery indicator). Anyone know how to do that?