KTucker [:KTucker][Inactive 3/4/2016] Reporter
	Description • 9 years ago

The estimated time remaining for the battery seems to be way off. The user had a 96% charged battery but the time remaining indicated that only 2 hours were left.

Prerequisite:
Battery is currently charged to 96%.

Repro Steps:
1) Update a Aries to 20151215145647
2) Open the settings app.
3) Tap on "Battery"
4) Pay close attention to the current level for the battery and the time remaining.

Actual:
The time remaining will not make sense compared to the current level of battery. The user had a 96% charge but it said that only 2 hours were remaining.

Expected:
The time remaining is fairly accurate depending upon the current level of the battery.

Please note that once the battery reached 94% i was given a calculated time of 7 hours remaining. 

Environmental Variables:
Device: Aries 2.6
Build ID: 20151215145647
Gaia: ee43a95f2bbe39c5ac8c9fcdec76749a56c02f2e
Gecko: cb66ffeb6725e8344818e8e2f707ae2eaeb953b4
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 46.0a1 (2.6)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Repro frequency:3/5 60%
See attached: screenshot, logcat

	Julien Wajsberg [:julienw]
	Comment 1 • 9 years ago

When you saw the issue, had you just plugged in the USB cable ?

See also bug 1163867, bug 1177221. I'd dupe to the latter if this is the case.

	KTucker [:KTucker][Inactive 3/4/2016] Reporter
	Comment 3 • 9 years ago

My phone was not plugged in at all. The battery remaining is just way off sometimes when you go into settings.

	KTucker [:KTucker][Inactive 3/4/2016] Reporter
	Comment 4 • 9 years ago

Btw this is a more recent feature in settings. The latter bug regarding the time to fully charge the device was written in June and I don't think the remaining time left on the battery in settings was implemented until much later.

	KTucker [:KTucker][Inactive 3/4/2016] Reporter
	Comment 5 • 9 years ago

This also occurs on Flame 2.6

The time remaining on the battery in settings is not close to being accurate in settings. 

Device: Flame 2.6 (Full Flash)(KK)(512mb)
BuildID: 20151217030228
Gaia: 140f6ee998b07b354d1841fed902056179c90100
Gecko: f143af51f6e35932927b8ccac2509facbbe7b539
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 46.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

======================

This does not occur on Aries 2.5

This feature does not exist. The time remaining on the battery does not appear in settings. 

Device: Aries 2.5
BuildID: 20151217165758
Gaia: eeed1451e0e48b63abe3199e4d6906adc2a762d2
Gecko: 94905dc59d7286b7fe627afbcddafc495894f08d
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 44.0 (2.5) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

	Jayme Mercado [:JMercado] (Inactive 3/4/2016)
	Comment 7 • 9 years ago

Iris can you have someone look at this?

	Julien Wajsberg [:julienw]
	Comment 8 • 9 years ago

(In reply to KTucker [:KTucker] from comment #4)
> Btw this is a more recent feature in settings. The latter bug regarding the
> time to fully charge the device was written in June and I don't think the
> remaining time left on the battery in settings was implemented until much
> later.

Yeah but I'm sure both tap into the same underlying API :) So could be a dupe of bug 1163867 (for the technical reason). Yet we might want to do some different changes, defering this decision to Settings peers.

	Iris Hsiao [:ihsiao]
	Comment 9 • 9 years ago

Hi Danny,
From comment #8, Julien mentioned that this bug could be a dup of bug 1163867. Could you help to check this issue?

	Danny Liang [:dliang]
	Comment 10 • 8 years ago

(In reply to Iris Hsiao from comment #9)
> Hi Danny,
> From comment #8, Julien mentioned that this bug could be a dup of bug
> 1163867. Could you help to check this issue?

Hmm, I think it's possible, but it should be the limitation now. The current algorithm is for stable charge/discharging behavior, and it also highly depended on the low level battery algorithm. We estimated the charging/discharging remaining time according battery level diff in a interval. So if battery drop 1% in minute, I think it's possible to get only 2 hours battery life by estimation. 

Please note this algorithm is to estimate battery life according to your current activity. In this case, it will get wrong value if you are doing heavy loading activity in the beginning then back to normal use later.

	BMO Automation
	Comment 11 • 6 years ago

Firefox OS is not being worked on