Ask / Submit
0

Jolla C cannot be updated without battery

asked 2017-04-18 21:47:21 +0300

ArmsOfSorrow gravatar image

I'd like to report a bug I've just encountered when trying to update my Jolla C.

Steps to reproduce:

  • Turn off device
  • Remove battery
  • Plug into power outlet and let it boot
  • Go to settings and look for updates
  • Download update
  • After downloading it'll show "Battery is low. You need to connect the device to your charger", even though it is already connected and won't let me start the update.

Since the battery was broken from the get-go, there is no other possibility for me to use the device. Could you please look into that?

edit retag flag offensive close delete

Comments

10

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 )edit
1

Firstly, 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 )edit
3

If 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

2 Answers

Sort by » oldest newest most voted
8

answered 2017-04-19 12:02:27 +0300

_ _ _ _ T A _ _ _ _ gravatar image

updated 2017-04-19 16:53:21 +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.

edit flag offensive delete publish link more

Comments

1

The message that tells the user to plug in the charger is a bug, though.

Anyway, as there's the possibility to update via pkcon apparently, I've got what I needed.

ArmsOfSorrow ( 2017-04-19 12:36:54 +0300 )edit

I don't get why the message that tells the user to plug in the charger would be a bug. 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.

_ _ _ _ T A _ _ _ _ ( 2017-04-19 14:30:19 +0300 )edit
3

Because the message says "You need to connect the device to your charger" while the device is already connected to the charger. There is no dedicated message for this specific situation.

Sthocs ( 2017-04-19 17:12:54 +0300 )edit

I think it may be unpredicted or orphaned scenario, and perhaps ought to be implemented, if there are users who needs it. And seems there are some. But first it must be verified if HW design allows to do this, using it without assembled battery. It can happen that using without a battery can damage HW. I don't know how it is in this case, and this is not any general rule - it can be different for every single model if HW is designed differently for e.g. lowering costs or programmed ageing of product.

_ _ _ _ T A _ _ _ _ ( 2017-04-20 12:54:32 +0300 )edit
6

answered 2017-04-19 06:42:00 +0300

pawel gravatar image

updated 2017-04-19 06:44:38 +0300

if you do not mind to use cmd line, why dont you use search to find how to update with pkcon ?

i.e. https://together.jolla.com/question/160307/is-there-easy-way-to-downgrade-back-to-2056/

works with upgrade the same way

edit flag offensive delete publish link more

Comments

1

That's the way to go, I suppose. Thanks.

ArmsOfSorrow ( 2017-04-19 12:38:31 +0300 )edit
Login/Signup to Answer

Question tools

Follow
1 follower

Stats

Asked: 2017-04-18 21:47:21 +0300

Seen: 418 times

Last updated: Apr 19