It seems that Qt graphics is not properly initialized. But I have no idea what is missing there.
1 Like
I tried to increase the root partition of Volla Phone (GS290) and ran into a problem. Following the guide here:
olf (Olf0) (Olf0) / SailfishX on Xperias · GitLab , chapter 3.3.1,
I entered the suggested commands into CLI on Linux laptop (Ubuntu 22.04 / Cinnamon) and got an error msg back. Above is the output of lvm lvdisplay command, below the result of sudo fastboot boot hybris-recovery.img command.
In short, I got a ‘No route to host’ error and now don’t know what to do.
Trying 10.42.66.66...
telnet: Unable to connect to remote host: No route to host
This is the whole story:
andrea@andrea-Voom-Laptop-Max:~/SailfishVolla/IncreaseRootPartition/boot$ ssh volla
Last login: Fri Apr 21 20:59:19 2023
,---
| Sailfish OS 4.5.0.19 (Struven ketju)
'---
[defaultuser@VollaPhone ~]$ devel-su
Password:
[root@VollaPhone defaultuser]# lvm lvdisplay
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Eingabe-/Ausgabefehler
--- Logical volume ---
LV Path /dev/sailfish/root
LV Name root
VG Name sailfish
LV UUID C97pdv-A98c-70eh-39Or-rzVj-AQXG-1GF7Yh
LV Write Access read/write
LV Creation host, time runner-zxwgkjap-project-18092000-concurrent-0, 2022-08-30 19:11:08 +0100
LV Status available
# open 1
LV Size 2,44 GiB
Current LE 625
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/sailfish/home_open
LV Name home_open
VG Name sailfish
LV UUID E8m2qO-8yjk-VAn2-m6nP-Dro6-sAjw-fbyxJD
LV Write Access read/write
LV Creation host, time runner-zxwgkjap-project-18092000-concurrent-0, 2022-08-30 19:11:09 +0100
LV Status available
# open 1
LV Size <50,58 GiB
Current LE 12948
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
[root@VollaPhone defaultuser]# exit
[defaultuser@VollaPhone ~]$ exit
Connection to 192.168.0.3 closed.
andrea@andrea-Voom-Laptop-Max:~/SailfishVolla/IncreaseRootPartition/boot$ sudo fastboot boot hybris-recovery.img
[sudo] Passwort für andrea:
Sending 'boot.img' (17524 KB) OKAY [ 0.806s]
Booting OKAY [ 0.184s]
Finished. Total time: 1.090s
andrea@andrea-Voom-Laptop-Max:~/SailfishVolla/IncreaseRootPartition/boot$ telnet 10.42.66.66
Trying 10.42.66.66...
telnet: Unable to connect to remote host: No route to host
andrea@andrea-Voom-Laptop-Max:~/SailfishVolla/IncreaseRootPartition/boot$
After this telnet error the phone booted into SFOS while USB cable still was connected. The phone booted and runs normally after this.
Have I forgotten something? What can I do?
edit: I guess this problem relies to computer… I have 2 USB ports on the laptop, on one there is an USB to Ethernet (RJ45) bridge for Internet connection. On the second there is an USB hub (the same with which I repeatedly successfully flashed X10 phones) and a Logitech mouse.
So, how can I tell the computer this missing ‘route to host’, as the booting itself seems to work? Can it be that Volla maybe has another numerical IP address and not ‘10.42.66.66’?
Pushed a small update to the OG Volla and Volla-X to fix the situation where sometimes when booting, the encryption wizard password entry doesnt show up, and it looks like you get stuck on the boot logo.
5 Likes
I think there is something wrong with this update. Since the update yesterday Volla shows dead Android on booting. 
I had to disconnect the battery to escape from this situation (found no other way using the buttons), reflashed the Volla with UBports Installer to 4.4.0.64 and updated in steps using sfos-upgrade [nextVersion], reboot once, check and restore network, post_sfos-upgrade, reboot twice, check and restore network, and so on. Until coming to after sfos-upgrade 4.5.0.19 and before the last post_sfos-upgrade everything was OK.
But exactly after running the last post_sfos-upgrade, on reboot: No boot, dead Android and no chance to come to flash mode. I fear I’ll have to disassemble the Volla again and disconnect/reconnect the battery… (I call this ‘power off reset’ 
)
Will report as soon I know more. Q: Other users affected, too?
BTW, is there any trick to hardware reset the Volla without disassembling it and disconnect the battery?
edit: For people interested in disassembling a Volla: Don’t try to remove the touchscreen! It’s senseless, there is only a metal plate behind it, nothing else. To disassemble, heaten the other side with a hairdryer and take care about the Wireless Charge coil connector (above battery) and the antenna connectors (top left & right corner)!
That cant be related to the change… ive tested it on Volla and Volla X on 4.5.0.19 and both are fine.
Phone should normally show volla logo while booting, a dead android sounds quite dramatic.
1 Like
Volla doesn’t do so.
After ‘power off reset’, I reflashed it to 4.4.0.64 using UBports installer on Linux laptop.
This time I installed nothing (no apps, no Storeman, no Chum) before proceeding and also didn’t any system tweaks.
Then went through the update limbo by cli, not skipping any release, installed and tested them all (WLAN and cellular connectivity, menus, generally if it ‘works’).
Reaching 19, reboot no more possible but hangs, Sailfish logo for a few seconds, than black screen forever. No senseful responsibility of buttons. Vol up + dn do nothing, PWR shows a little background light.
BTW, since 4.5.0.16, cell data is broken.
Will repeat ‘power off reset’, flash again and update to 4.4.0.72 and leave it as it is to be able to use the Volla for some basic things.
Any ideas what could be the reason? Is there any way to wipe the complete memory to start again and wipe out any remaining content of former experiments?
edit: What’s the difference between updating with zypper ref and zypper dup and sfos-upgrade, reboot and post_sfos-upgrade?
edit: updates went wonky, on 68 device slow, on 72 vol buttons doesn’t work any more.
i am on 4.5.0.19 and phone works
i did loose calling at some point and had to install proper ofono package
but rest does work
i did not play around with partitions
I reflashed now 4.4.0.64, @piggz 's port works like a charm, but every attempt to update ruins the OS, at least makes it slow, at worst leads to total crash. Now I leave it as it is and have installed a minimum of apps and will look for a mini-laptop for portable work and use the phone only as WLAN access point. I’m sick of permanently struggling against unnecessary limits e.g. the tiny root partition or have to fear that an update ruins everything and I have again to work a whole day to restore it.
maybe i should make the rootfs 8gb like other new devices
5 Likes
Yes!!! Please!!! 
(20 chars)
had problems too with 4.5.0.19. mobile network and wifi switched off sometimes. Had to reboot the device sometimes. Went back to 4.4.0.72. Works stable at the moment. Browser worked laggy. I removed calculator. feels better ( i suppose😎)
1 Like
I observed that the presence of Jolla Calculator slows down the phone, even when app is not in use. Deinstallation speeds up the device. Reason unknown. To have a calculator on the phone, I installed RPNcalc from Storeman, that I like more.
Sailfish Weather behaves similar, so I also deinstalled it. No substitute, because I don’t need it.
1 Like
removed sailfish weather! you’re right! it’s faster. thanks:+1:
1 Like
Q: Does it make sense for a, say so, advanced user and interested person (like me), but not a coder, to enable developer updates in settings - developer tools? What will then come? In case ‘yes’, how to do the required registration? Is this also possible on Volla or is it only for officially supported devices?
I can’t answer the question, but I have explicitly chosen to NOT have developer updates on. I want the state of the device to be close to what the user has. Cough.
2 Likes
Today I reflashed the Volla using UBports Installer 0.9.7.beta on Linux (as always) and saw that there is SFOS 4.5.0.19! Thank you very much for updating @piggz ! 
But a new installed SFOS is now 1,2 GB large (was 1 GB a week before / 4.4.0.64), Free space is now 1,1 GB (was 1,4 GB a week before), and mobile data connection is broken. Root partition size is still 2,4 GB Is there any hope for me? 
edit: mobile data is broken.
I know this is sort of the ‘wrong’ answer, but I would suggest taking advantage of a deal like:ebay.de/itm/385476659762 That’s a rephone, new condition, for 149 euro. If you can afford it, it has a replaceable battery and 6GB of Ram. The default install has 5+ GB of space. It’s a lot less hassle and it’s a fast phone. Sadly, even all that RAM doesn’t solve the bombing browser problem.
I’m still happy to use my original Volla for development only and I keep it at 4.4 (and a GS290 at 3.4) but that’s for testing and development purposes. Daily driver is the rephone (GS5 backup).
1 Like
@poetaster , keeping at 4.4 or 3.4, does this mean not to update or do you know a way to fresh flash a Volla from computer (without direct internet download while flashing as UBports Installer does)? Do you know an option to archive the flash files for the SFOS versions on computer and flash a Volla with a choosen one? My little problem is now, at the moment I’m only able to flash the Volla using UBports Installer and I depend on the version UPports Installer loads from the internet at flashing time. I don’t know any way to control what SFOS version will be flashed. I see this only when ready and rebooted. So it happened yesterday… Do you know how to flash 4.4.0.64 again while waiting until the bug is fixed?
Have you seen this?
2 Likes