Closed
Bug 959195
Opened 12 years ago
Closed 11 years ago
FOTA updates should check remaining battery
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
2.0 S3 (6june)
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
(Whiteboard: [systemsfe])
Attachments
(2 files)
46 bytes,
text/x-github-pull-request
|
etienne
:
review+
|
Details | Review |
241.60 KB,
image/png
|
jelee
:
ui-review+
|
Details |
Currently, we allow booting into recovery and applying FOTA even with very low battery. This is quite risky.
We should not let user apply FOTA updates in this case. I've been able to do this with a Peak and less than 5% of battery.
Comment 2•12 years ago
|
||
Flagging Mike to direct to whomever is best/available on System here.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(mtsai)
Flagging Neo to help on this issue.
Flags: needinfo?(mtsai) → needinfo?(nhsieh)
Comment 4•12 years ago
|
||
"we allow booting into recovery and applying FOTA even with very low battery" .
So for users, the first step is swipe down the status bar and click the update notification, right ? Or can we just press some hardware key to booting into recovery mode like other android phone ? (Ex. Power+Volumn key)
Another questions is, If user connect charger with mobile phone in low battery mode, is that safe enough to update the firmware ? Is it should use battery power only ?
If user enter FOTA mode from idle mode, I think we can inform or disable update notification function when device is low battery. But we can not stop user use hardware key enter recovery mode, except we can change recovery mode UI... (But I guess that is controlled by ODM).
Flags: needinfo?(nhsieh) → needinfo?(lissyx+mozillians)
Assignee | ||
Comment 5•12 years ago
|
||
(In reply to Neo Hsieh from comment #4)
> "we allow booting into recovery and applying FOTA even with very low
> battery" .
> So for users, the first step is swipe down the status bar and click the
> update notification, right ? Or can we just press some hardware key to
> booting into recovery mode like other android phone ? (Ex. Power+Volumn key)
>
> Another questions is, If user connect charger with mobile phone in low
> battery mode, is that safe enough to update the firmware ? Is it should use
> battery power only ?
>
> If user enter FOTA mode from idle mode, I think we can inform or disable
> update notification function when device is low battery. But we can not stop
> user use hardware key enter recovery mode, except we can change recovery
> mode UI... (But I guess that is controlled by ODM).
We are only talking about OTA/FOTA applied from Gecko, yes. Not when the users enters into recovery by hand.
Flags: needinfo?(lissyx+mozillians)
Assignee | ||
Comment 6•12 years ago
|
||
I'm unsure whether the recovery mode allows to charge the device or not.
Updated•12 years ago
|
Whiteboard: [systemsfe]
Comment 8•11 years ago
|
||
Flagging Omega on hardware related UI here.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(ofeng)
Comment 10•11 years ago
|
||
For current implementation, when FOTA is downloaded, there is a dialog:
System Update Ready
---------------------
Install update now?
[Later] [Install Now]
We can change to, when FOTA is downloaded, check the battery level, if it's >= 50%, go for the above dialog; otherwise (< 50%), go for the following dialog:
System Update Ready
---------------------
You need at least 50% battery level to install the update.
[OK]
User can charge the battery and tap the notification to show the first dialog again.
Flags: needinfo?(ofeng)
Flags: needinfo?(jelee)
Assignee | ||
Comment 11•11 years ago
|
||
Let's do this.
Status: NEW → ASSIGNED
Flags: needinfo?(lissyx+mozillians)
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(lissyx+mozillians)
Target Milestone: --- → 2.0 S3 (6june)
Assignee | ||
Comment 12•11 years ago
|
||
Attached is a link to the github pull request addressing the issue. Unit tests are okay locally, I still need to test this on device though.
Assignee | ||
Updated•11 years ago
|
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Assignee | ||
Comment 13•11 years ago
|
||
Screenshot on device, forcing battery level at 30%.
Assignee | ||
Comment 14•11 years ago
|
||
Comment on attachment 8434067 [details]
2014-06-04-13-36-26.png
Jenny, the attached screenshot shows how the UI looks to the user.
Attachment #8434067 -
Flags: ui-review?(jelee)
Assignee | ||
Comment 15•11 years ago
|
||
Comment on attachment 8433387 [details] [review]
Link to Github https://github.com/mozilla-b2g/gaia/pull/19940
Etienne, since you did quite a lot of things on this file, I'm flagging you for review.
Attachment #8433387 -
Flags: review?(etienne)
Comment 16•11 years ago
|
||
Comment on attachment 8434067 [details]
2014-06-04-13-36-26.png
Message title should be in English? Tks!
Attachment #8434067 -
Flags: ui-review?(jelee) → ui-review+
Assignee | ||
Comment 17•11 years ago
|
||
(In reply to Jenny Lee from comment #16)
> Comment on attachment 8434067 [details]
> 2014-06-04-13-36-26.png
>
> Message title should be in English? Tks!
Of course, I tested it on my Flame which was running in French locale. I'm re-using the previous system update string, so it's fine.
Comment 18•11 years ago
|
||
Comment on attachment 8433387 [details] [review]
Link to Github https://github.com/mozilla-b2g/gaia/pull/19940
The code is perfect, nothing to say there :)
But shouldn't we let the user start the update if the phone is plugged in?
Attachment #8433387 -
Flags: review?(etienne) → review+
Assignee | ||
Comment 19•11 years ago
|
||
(In reply to Etienne Segonzac (:etienne) from comment #18)
> Comment on attachment 8433387 [details] [review]
> Link to Github https://github.com/mozilla-b2g/gaia/pull/19940
>
> The code is perfect, nothing to say there :)
>
> But shouldn't we let the user start the update if the phone is plugged in?
That would be a UX decision. However, the behavior of Android device is to forbid even if the device is plugged in.
Jenny, do you have an opinion? Or should we just land as is?
Flags: needinfo?(jelee)
Comment 20•11 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #19)
> That would be a UX decision. However, the behavior of Android device is to
> forbid even if the device is plugged in.
>
> Jenny, do you have an opinion? Or should we just land as is?
We can't know for sure if the device will still be plugged in after the installation starts, so, just to be safe, let's keep the current behavior. Tks!
Flags: needinfo?(jelee)
Assignee | ||
Comment 21•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•