Merge lp://staging/~diegosarmentero/ubuntu-system-settings/update-battery into lp://staging/ubuntu-system-settings
Proposed by
Diego Sarmentero
Status: | Work in progress | ||||
---|---|---|---|---|---|
Proposed branch: | lp://staging/~diegosarmentero/ubuntu-system-settings/update-battery | ||||
Merge into: | lp://staging/ubuntu-system-settings | ||||
Diff against target: |
97 lines (+46/-4) 1 file modified
plugins/system-update/PageComponent.qml (+46/-4) |
||||
To merge this branch: | bzr merge lp://staging/~diegosarmentero/ubuntu-system-settings/update-battery | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sebastien Bacher (community) | Needs Fixing | ||
PS Jenkins bot | continuous-integration | Needs Fixing | |
Review via email: mp+225964@code.staging.launchpad.net |
Commit message
- Notify the user if the phone needs to be plug to power for update
To post a comment you must log in.
Unmerged revisions
- 750. By Diego Sarmentero
-
hide progress bar on image download complete
- 749. By Diego Sarmentero
-
fixing issue with image progress after finish
- 748. By Diego Sarmentero
-
fixing bug on install button for system update
- 747. By Diego Sarmentero
-
removing unused code
- 746. By Diego Sarmentero
-
adding battery support to updates
Thanks you for your work, some issues
- you use "label.text" there, but there is no such object (you get a runtime warning about it being undefined btw)
- I just tried on my laptop (using the "sudo system-image-dbus --testing= update- manual- success" mock) which is plugged and 100% charged, it gave me the error case/not now interface
My case on that one is th at "onRemainingCap acityChanged" is never called on my fully charged scenario, so the batterySafeForU pdate is never set
- the 50% charge seems a bit much, but the spec doesn't define what would be a reasonable level, I guess 30% should be enough ... I'm not going to be picky about that though
- clicking on "not now" brought me back to the updates list, clicking on the "install" button again made the install happen despite the incorrect charge/without asking
(that one is not a new bug I think though)