answered
2017-04-19 12:02:27 +0300
I suppose this is not a bug but a protection against problems with power during updating process, as battery would provide energy in such a case. So for me this is a protection against accidental damaging or even bricking a device.
Besides sometimes in some places current temporary does not have nominal values, here there is no place to discuss this. But shortly that mean that charger does not plays its role as needed also. And again battery is "the last line of defence" - if battery is assembled into and charged and operational (not broken).
I think this behaviour or protection should not to be removed. I am pretty sure without it now we would have less Jolla's devices and instead more bricked devices. Perhaps OS could ask 3 times "The battery is to weak or not assembled. Updating without assembled charged battery can cause damage or even bricking the device in case if would happen any break of power supply. Do you want to continue anyway to take that risk? y/n?" Or something in this way. And eventually to allow continue after risky operation would be confirmed 3 times during 5 minutes (not allowed long breaks between confirmations).
My point is: I think both power sources, plugged in and working charger and fully charged battery, should be "operational and ready" just to assure stable conditions and power supply during the whole process. That is cheaper and easier then servicing bricked/damaged device I think. Prevention over risk of troubles. I can agree with overriding by 3 confirmations, but I am against removing it at all. It would expose less careful or less experienced ones on a risk that could be avoided when alerted by this message exactly.
Why do you think its a bug / unintentional behavior? The are quite some reason why having a charged battery makes sense during the update process: spontaneous loss of electricity may leave your device in an undesirable state and, thus, may result in more support request.
bomo ( 2017-04-18 23:05:53 +0300 )editFirstly, there's no support whatsover for Jolla C anyway, since it's a development device.
I'm well aware of the repercussions, but the message suggests the possibility of an update when the charger is plugged in, which is wrong. I don't know how Sailfish implements its updater, but usually there should be at least some kind of procedure that enables the OS to roll back failed updates. Or how do you think this works on traditional PCs?
IMO, there should be a way to override that behavior. Doesn't need to be through UI, I don't mind using the command line. But if the battery is broken, it makes the phone unable to keep up with OS updates, which is important for development. A battery, less so; I can still use it while plugged in, just like my PC.
ArmsOfSorrow ( 2017-04-18 23:18:42 +0300 )editIf you have some hand soldering skills, or know someone who has them, you can see this thread to learn how to adapt a battery for use in the Jolla C.
Giacomo Di Giacomo ( 2017-04-19 10:14:31 +0300 )edit