Guys - I have a customer that is piloting some rev B MC40 units running KK. Hopefully if everything goes well we will roll out Rev c units later this year. Its early days but weve had a comment back suggesting that battery life is pretty poor - ~3hrs. The customer is just using a web based app - no voice and occasional scanning.They have MC91 and 92 in their stores and get 8hrs +. I will get on site in the next day or so to get a first hand view on whats happening.
Do we have any comparative testing with rev B units running KK and JB ? Concerned that the up tick in the cpu speed MAY be having a side affect here.
Thanks,
Andy
2 Replies
Andy
I have run three MC40s today as a rough test. Two were original Rev A hardware (originally GB then JB) One was upgraded to the latest KK release. The third was a Rev C hardware DV unit for comparison.
The summary is that there was only just over an hour of battery life difference between KK and JB on the same Rev A hardware, and KK lasted longer! The 2 Rev A units lasted 5 1/2 and 6 1/2 hours each. So much better than your reported 3 hours.
A Caveat. These MC40s are my test and development kit so have not been heavily used as a live device may have been. Could be the reported device just has an old and 'tired' battery.
The 3 units were configured as follows. WiFi Always On. Connected to A band wifi. PTT Ex active. Browser running. occasional PTT transmissions. Occasional scans using Data Wedge demo. Display brightness to manual and max. Display timeout to 30 minutes.
All MC40s charged until showing 'green' charge status lights, not necessarily a full 100% reported charge (but close)
NB. any 'activity' was completed on all 3 devices just to work the battery a little. eg scanning, PTT etc, but there is no consistency of activity over time, eg X scans every 10 mins. so nothing can be learned from battery performance hour to hour. Battery charge level and elapsed time are taken from SETTINGS > BATTERY
MC40 1
MC40 2
MC40 3
HW
Rev A
Rev A
Rev C (DV)
OS
Ex GB > JB
exGB >JB>KK
KK
BSP
020815
070315
070315
Android
4.1.1
4.4.4
4.4.4
40 Manf Date
23-Jan-13
23-Jan-13
27-Mar-15
Batt Ver
Rev A
Rev A
Rev B
Scanner
SE4500
SE4500
SE4710
Display
WinTek
WinTek
GiantPlus
Touch
Novatech
Novatech
FocalTech
Indicated Battery Charge Level
MC40 1
MC40 2
MC40 3
12 mins
93%
96%
95%
Elapsed Time
Lost Charge
30mins
88%
92%
91%
18m
5%
4%
4%
1h 2m
81%
87%
87%
32m
7%
5%
4%
1h 35m
73%
80%
79%
33m
8%
7%
8%
2h 7m
66%
76%
75%
32m
7%
4%
4%
2h 38m
59%
69%
68%
31m
7%
7%
7%
3 h 16m
46%
61%
61%
38m
13%
8%
7%
3h 44m
38%
57%
56%
28m
8%
4%
5%
4h 5m
29%
54%
51%
21m
9%
3%
5%
4h 33m
20%
49%
46%
28m
9%
5%
5%
5h 3m
17%
44%
38%
30m
3%
5%
8%
5h 31m
14%
39%
32%
28m
3%
5%
6%
5h 42m
FLAT
37%
31%
11m
2%
1%
6h 36m
FLAT
15%
22%
58m
22%
9%
6h 48m
FLAT
FLAT
19%
12m
3%
The extra life from the Rev C hardware could just be the unit is nearly 2 years newer.
Andrew,
We have been doing extensively battery life comparison between JB and KK and we have not seen any big degradation between them using same test conditions for both.
Earlier KK versions did have a slight higher current using VOIP mode but I don't think that would cause this much difference.
One thing to note is that KK OS might have some API or default settings different than JB so it might be possible that either the OS is in a mode where it uses higher power (DataWedge Mode, Brightness, Timeout, Radio configuration, etc) or customer APP is causing extra current due to differences from JB to KK.
Do you know the KK version that is loaded?
Can you share the profile used?
Thanks
Marcelo