Closed
Bug 1092906
Opened 10 years ago
Closed 10 years ago
[FFOS2.0][Woodduck][Battery] No warning when charge voltage too high
Categories
(Firefox OS Graveyard :: Gaia::System, defect, P2)
Firefox OS Graveyard
Gaia::System
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: howie, Unassigned)
References
Details
(Whiteboard: [POVB])
+++ This bug was initially created as a clone of Bug #1092046 +++
CONTACT INFO (Name,Phone number):
熊芳波
Office: +86-752-2639572
DEFECT DESCRIPTION:
without warning when charge voltage too high
REPRODUCING PROCEDURES:
EXPECTED BEHAVIOUR:
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:
For FT PR, Please list reference mobile's behavior:
Reporter | ||
Comment 1•10 years ago
|
||
Hi Adam & Gregor, need your input if this is worth (and feasible) to do in 2.2, thanks.
Flags: needinfo?(arogers)
Flags: needinfo?(anygregor)
Updated•10 years ago
|
Flags: needinfo?(anygregor) → needinfo?(wmathanaraj)
Updated•10 years ago
|
feature-b2g: --- → 2.2?
Comment 2•10 years ago
|
||
Howie, can you provide me with more details on this?
* What is the impact of not doing this feature in 2.2
* What is the likelihood of a user being able to charge with to high a voltage?
Flags: needinfo?(arogers)
Updated•10 years ago
|
blocking-b2g: --- → backlog
Summary: [FFOS2.0][Woodduck][Battery] Without warning when charge voltage too high → [FFOS2.0][Woodduck][Battery] No warning when charge voltage too high
Updated•10 years ago
|
Blocks: FxOS-v2.2-features
Comment 3•10 years ago
|
||
Partner request this feature but first of all they should implement API for gecko/gaia to accept the signal of charging voltage too high. Postpone until partner strong request this. Accept as it is now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Whiteboard: [POVB]
Updated•10 years ago
|
No longer blocks: FxOS-v2.2-features
Updated•10 years ago
|
blocking-b2g: backlog → ---
feature-b2g: 2.2? → ---
Updated•10 years ago
|
Flags: needinfo?(wmathanaraj)
You need to log in
before you can comment on or make changes to this bug.
Description
•