DETERMINING THE BATTERY CONDITION OF A MOBILE ELECTRONIC DEVICE

Abstract

A method for use in determining a condition of a battery of a mobile electronic device, comprises receiving, at a server, mobile electronic device data from a mobile electronic device, receiving, at the server, information relating to each candidate method of a plurality of candidate methods, each candidate method being configured for determining a value of a corresponding battery condition, wherein the battery condition value corresponding to each candidate method is representative of the condition of the battery of the mobile electronic device. The method further comprises determining whether any of the candidate methods are capable of determining a corresponding battery condition value based at least in part on the mobile electronic device data and the information relating to each candidate method, and, in response to determining that one or more of the candidate methods is capable of determining one or more corresponding battery condition values, performing one or more of the capable methods to thereby determine the one or more corresponding battery condition values. The method may be suitable for use in determining a condition of a battery of a mobile electronic device and, in particular though not exclusively, for use in determining a condition of a battery of a mobile electronic device which comprises or runs an Android operating system.

Claims

1. A method for use in determining a condition of a battery of a mobile electronic device, the method comprising: receiving, at a server, mobile electronic device data from a mobile electronic device; receiving, at the server, information relating to each candidate method of a plurality of candidate methods, each candidate method being configured for determining a value of a corresponding battery condition, wherein the battery condition value corresponding to each candidate method is representative of the condition of the battery of the mobile electronic device; determining whether any of the candidate methods are capable of determining a corresponding battery condition value based at least in part on the mobile electronic device data and the information relating to each candidate method; and in response to determining that one or more of the candidate methods is capable of determining one or more corresponding battery condition values, performing the one or more of the capable methods to thereby determine the one or more corresponding battery condition values.

2. The method of claim 1, wherein the mobile electronic device data comprises at least one of a make, a model, an operating system, and a version of the operating system of the mobile electronic device and, at least one of: data relating to the battery of the mobile electronic device; a design capacity Q.sub.des of the battery; a make and/or a model of the battery of the mobile electronic device; and historical battery performance data.

3. The method of claim 1, further comprising extracting historical battery performance data from the mobile electronic device data, for example from a battery cycle information file stored on the mobile electronic device or from a battery stats log file stored on the mobile electronic device.

4. The method of claim 1, comprising transmitting the mobile electronic device data from the mobile electronic device data to the server.

5. The method of claim 1, comprising running an app on the mobile electronic device to extract the mobile electronic device data from data stored on the mobile electronic device and to transmit the mobile electronic device data from the mobile electronic device data to the server.

6. The method of claim 1, wherein the information relating to each candidate method comprises instructions for performing each candidate method.

7. The method of claim 1, comprising: transmitting, from the server to the mobile electronic device, instructions for performing each one or more of the capable methods; and executing, at the mobile electronic device, the instructions for performing each one or more of the capable methods.

8. The method of claim 1, comprising selecting an optimum one of the one or more capable methods based at least in part on the mobile electronic device data and the information relating to each candidate method and performing the optimum method to thereby determine a corresponding battery condition value, wherein the battery condition value determined using the optimum one of the one or more capable methods is known to provide a more accurate representation of the condition of the battery of the mobile electronic device than the battery condition value determined using any other one of the capable methods.

9. The method of claim 8, comprising: transmitting, from the server to the mobile electronic device, instructions for performing the optimum one of the one or more capable methods; and executing, at the mobile electronic device, the instructions for performing the optimum one of the one or more capable methods.

10. The method of claim 1, wherein the information relating to each candidate method comprises a corresponding battery condition threshold value and the method comprises comparing each determined battery condition value with the corresponding battery condition threshold value and determining whether the battery condition is compliant or non-compliant with a predetermined battery condition test according to the result of the comparison.

11. The method of claim 1, wherein receiving the information relating to each candidate method of a plurality of candidate methods comprises fetching the information relating to each candidate method from a database to the server.

12. The method of claim 11, comprising: updating or modifying the information in the database relating to one or more of the candidate methods; or storing, in the database, information relating to one or more additional candidate methods, each additional candidate method being configured for determining a corresponding battery condition value, wherein the battery condition value corresponding to each candidate method is representative of the condition of the battery of the mobile electronic device.

13. The method of claim 1, comprising making each determined battery condition value available at the mobile electronic device by displaying each determined battery condition value at the mobile electronic device, and/or transmitting, from the mobile electronic device to the server and/or to a further server, each determined battery condition value.

14. The method of claim 1, wherein the historical battery performance data comprises a battery cycle count value representing the number of full discharge/charge cycles associated with the battery of the mobile electronic device and the method comprises returning the battery cycle count value as at least one of the determined battery condition values.

15. The method of claim 2, wherein the historical battery performance data comprises historical battery charge data and the method comprises determining one or more of the battery condition values based at least in part on the historical battery charge data.

16. The method of claim 15, wherein the historical battery charge data comprises time information and battery charging status information, wherein the method comprises using the time information and the battery charging status information to identify one or more battery charge intervals during which the battery was charged; wherein the historical battery charge data comprises a plurality of historical battery charge data points for each battery charge interval, wherein each historical battery charge data point comprises time information, battery charging current information, and battery charge information; wherein the time information comprises a relative time value or time stamp; wherein the battery charging current information comprises a value of charging current supplied to the battery; wherein the battery charge information comprises a fractional value of the present or actual capacity Q.sub.act of the battery, expressed as a fraction or as a percentage of the present or actual capacity Q.sub.act of the battery; and wherein the method further comprises: identifying one or more battery charge ranges within each of the one or more battery charge intervals; determining, for each battery charge range, an estimate Q.sub.act (k) of the present or actual charge capacity Q.sub.act of the battery, where k is an index assigned to each battery charge range according to the numerical order in which the fractional values of the present or actual capacity Q.sub.act of the battery in the battery charge ranges occur; estimating the present or actual capacity Q.sub.act of the battery by averaging the estimates Q.sub.act(k) of the present or actual capacity of the battery for all of the battery charge ranges according to the formula: $Q_{\mathrm{act}}=\frac{1}{N_k}\underset{\forall k}{.Math.}{Q}_{\mathrm{act}}\left(k\right)$ where N.sub.k is the total number of battery charge ranges; and determining one or more of the battery condition values based at least in part on the present or actual capacity Q.sub.act of the battery.

17. The method of claim 2, wherein the historical battery performance data comprises historical battery drain data and the method comprises determining one or more of the battery condition values based at least in part on the historical battery drain data.

18. The method of claim 17, wherein the historical battery drain data comprises a lower limit min(Σ ΔQ) for a cumulative charge consumed over a drain period, and an upper limit max(Σ ΔQ) for the cumulative charge consumed over the drain period, wherein the drain period is defined as a time period elapsed since the last full charge of the battery of the mobile electronic device, and wherein the method comprises determining an average value avg (Σ ΔQ) for the cumulative charge consumed over the drain period according to $\mathrm{avg}\left(.Math.\Delta Q\right)=\frac{1}{2}\left[\min \left(.Math.\Delta Q\right)+\max \left(.Math.Q\Delta \right)\right].$

19. The method of claim 18, wherein the historical battery drain data comprises a cumulative percentage drop in charge Σ Δp over the drain period and the method comprises: determining an actual capacity Q.sub.act of the battery according to Q.sub.act=avg (Σ ΔQ)×100/Σ Δp; and determining one or more of the battery condition values based at least in part on the present or actual capacity Q.sub.act of the battery; or wherein the historical battery drain data comprises a cumulative fractional drop in charge Σ Δf over the drain period and the method comprises: determining an actual capacity Q.sub.act of the battery according to Q.sub.act=avg (Σ ΔQ)/Σ Δf; and determining one or more of the battery condition values based at least in part on the present or actual capacity Q.sub.act of the battery.

20. The method of claim 16, comprising returning one or more of the following quantities as one or more of the battery condition values: the ratio Q.sub.act/Q.sub.des; the percentage 100×Q.sub.act/Q.sub.des; a percentage wear value W.sub.p determined according to W.sub.p=100×(1−Q.sub.act/Q.sub.des); and a fractional wear value W.sub.f determined according to W.sub.f=1−Q.sub.act/Q.sub.des.

21. The method of claim 1, wherein the mobile electronic device comprises or runs an Android operating system such as Android Marshmallow Versions 6.0-6.0.1, Android Nougat Versions 7.0-7.1.2, Android Oreo Versions 8.0-8.1 or Android P Version 9.

22. An app which, when executed on a mobile electronic device, causes a method to be performed as claimed in claim 1.

23. Instructions for a server for use in determining a condition of a battery of a mobile electronic device, which instructions, when executed by a processing resource of the server, cause the server to perform the method of claim 1.

24. A server for use in determining a condition of a battery of a mobile electronic device, the server comprising a processing resource and a memory containing instructions which, when executed by the processing resource, cause the processing resource to: receive mobile electronic device data from the mobile electronic device; receive information relating to each candidate method of a plurality of candidate methods, each candidate method being configured for determining a value of a corresponding battery condition, wherein the battery condition value corresponding to each candidate method is representative of the condition of the battery of the mobile electronic device; determine whether any of the candidate methods are capable of determining a corresponding battery condition value based at least in part on the mobile electronic device data and the information relating to each candidate method; and in response to determining that one or more of the candidate methods is capable of determining one or more corresponding battery condition values, cause the one or more of the capable methods to be performed to thereby determine the one or more corresponding battery condition values.

25. A system comprising the server of claim 24 and a database storing the information relating to each candidate method of the plurality of candidate methods, wherein, when executed by the processing resource of the server, the instructions cause the processing resource of the server to fetch the information relating to each candidate method of the plurality of candidate methods from the database.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0097] A method and system for use in determining a condition of a battery of a mobile electronic device will now be described by way of non-limiting example only with reference to the following drawings of which:

[0098] FIG. 1 is a schematic of a mobile electronic device and a system for use in determining a condition of a battery of the mobile electronic device;

[0099] FIG. 2 is a generic example of historical battery charge data stored in a battery stats log file of the mobile electronic device of FIG. 1;

[0100] FIG. 3 is a generic example of historical battery drain data stored in a battery stats log file of the mobile electronic device of FIG. 1;

[0101] FIG. 4 is a flow chart illustrating a method for use in determining a condition of the battery of the mobile electronic device of FIG. 1;

[0102] FIG. 5 shows a method for determining a battery condition value of the mobile electronic device of FIG. 1 using historical battery charge data;

[0103] FIG. 6 shows step 208 of the method of FIG. 5 in more detail;

[0104] FIG. 7 shows an example of two overlapping battery charge intervals in a battery stats log file;

[0105] FIG. 8A shows pseudo code instructions for selecting an optimum method for use in determining a condition of the battery of the mobile electronic device of FIG. 1; and

[0106] FIG. 8B shows pseudo code instructions for comparing determined battery condition values with corresponding battery condition threshold values and determining whether the battery condition is compliant or non-compliant with a predetermined battery condition test.

DETAILED DESCRIPTION OF THE DRAWINGS

[0107] One of ordinary skill in the art will understand that one or more of the features of the embodiments described below with reference to the drawings may produce effects or provide advantages when used in isolation from one or more of the other features of the embodiments and that different combinations of the features are possible other than the specific combinations of the features of the embodiments described below.

[0108] Referring initially to FIG. 1 there is shown a mobile electronic device generally designated 2 and a system generally designated 20 for use in determining a condition of a battery of the mobile electronic device 2.

[0109] The mobile electronic device 2 includes the battery 4, a memory 6, a processing resource 8, and a user interface 10. The memory 6 stores an operating system in the form of an Android operating system 12 and mobile electronic device data 14. The mobile electronic device data 14 includes at least one of a make, a model, and a version of the Android operating system 12 of the mobile electronic device 2. The mobile electronic device data further includes data relating to the battery 4 of the mobile electronic device 2. Specifically, the mobile electronic device data 14 further includes historical battery performance data for the battery 4 of the mobile electronic device 2 in the form of a battery cycle information file and a battery stats log file stored in the memory 6 of the mobile electronic device 2. The battery stats log file may be output from a batterystats service of a dumpsys tool that runs on the mobile electronic device 2. The mobile electronic device data 14 may further include a make and/or a model of the battery 4 of the mobile electronic device 2.

[0110] The battery cycle information file includes a battery cycle count value representing the number of full discharge/charge cycles associated with the battery 4.

[0111] FIG. 2 illustrates the format of the battery stats log file which includes historical battery charge data in the form of a first set of historical battery charge data points corresponding to a first battery charge interval 101 and a second set of historical battery charge data points corresponding to a second battery charge interval 102.

[0112] Each historical battery charge data point of the first battery charge interval 101 comprises time information and corresponding battery charging current and battery charge information. The time information takes the form of relative time values or time stamps expressed as a date and a time in hours, minutes and seconds, t.sub.start1, . . . t.sub.j, . . . t.sub.finish1. The battery charging current information comprises an absolute value of charging current expressed in mA, I.sub.start1, . . . I.sub.j, . . . I.sub.finish1 supplied to the battery at each time t.sub.start1, . . . t.sub.j, . . . t.sub.finish1 respectively. The battery charge information comprises a fractional value q.sub.start1, . . . q.sub.i, . . . q.sub.finish1 of the actual charge capacity Q.sub.act of the battery expressed as a fraction or percentage of the actual charge capacity Q.sub.act of the battery at each time t.sub.start1, . . . t.sub.finish1 respectively.

[0113] Similarly, each historical battery charge data point of the second battery charge interval 102 comprises time information and corresponding battery charging current and battery charge information. The time information takes the form of relative time values or time stamps expressed as a date and a time in hours, minutes and seconds, t.sub.start2, . . . t.sub.j, . . . t.sub.finish2. The battery charging current information comprises an absolute value of charging current expressed in mA, I.sub.start2, . . . I.sub.j, I.sub.finish2 supplied to the battery at each time t.sub.start2, . . . t.sub.j, . . . t.sub.finish2 respectively. The battery charge information comprises a fractional value q.sub.start2, . . . q.sub.i, . . . q.sub.finish2 of the actual charge capacity Q.sub.act of the battery expressed as a fraction or percentage of the actual charge capacity Q.sub.act of the battery at each time t.sub.start2, . . . t.sub.j, . . . t.sub.finish2 respectively.

[0114] The battery stats log file also includes battery charging status information such as a battery charging status flags 110, 112, indicating when battery charging started, and a battery charging status flags 120, 122 indicating when battery charging finished.

[0115] One of skill in the art will understand that, an actual battery stats log file may include other information not shown in FIG. 2 or that an actual battery stats log file may present the historical battery charge data in a different format to that shown in FIG. 2.

[0116] FIG. 3 illustrates a specific example of a further portion of the battery stats log file which includes the historical battery drain data. Specifically, as shown in FIG. 3, the historical battery drain data includes a value for the design capacity Q.sub.des of the battery 4 which is expressed in mAh and which is identified in FIG. 3 using the label “Capacity”. For the specific data shown in FIG. 3, the design capacity Q.sub.des of the battery 4 is 2700 mAh. The historical battery drain data also includes a range of values for the cumulative charge consumed by the battery 4 over a drain period identified in

[0117] FIG. 3 using the label “actual drain”, wherein the drain period is defined as a time period elapsed since the last full charge of the battery 4. Specifically, the range of values for the cumulative charge consumed by the battery 4 over the drain period includes a lower limit min(Σ ΔQ) expressed in mAh and an upper limit max(Σ ΔQ) expressed in mAh. For the specific data shown in FIG. 3, min(Σ ΔQ)=4887 mAh and max(Σ ΔQ)=5427 mAh. The historical battery drain data further includes a cumulative percentage drop in charge Σ Δp over the drain period which is identified in FIG. 3 using the label “Amount discharged (upper bound)”, where each percentage drop in charge Δp is expressed as a percentage drop in charge relative to a full charge of the battery e.g. if during a drain period, a percentage charge of the battery 4 drops from 100% to 20% (i.e. a percentage drop of 80%), the battery is then charged so that the percentage charge of the battery 4 rises from 20% to 70%, and the percentage charge of the battery 4 then drops from 70% to 30% (i.e. a percentage drop of 40%), then the cumulative percentage drop in charge Σ Δp over the drain period is 120%. For the specific data shown in FIG. 3, the cumulative percentage drop in charge Σ Δp over the drain period is 201%.

[0118] One of skill in the art will understand that, in general, the historical battery drain data values in the battery stats log file may be different to the specific historical battery drain data values shown in FIG. 3, the battery stats log file may include other information not shown in FIG. 3, and that the battery stats log file may present the historical battery drain data in a different format to that shown in FIG. 3.

[0119] Referring back to FIG. 1, the memory 6 also stores an app 16 which is configured to determine a battery condition value which is representative of a condition of the battery 4 of the mobile electronic device 2, as will be described in more detail below.

[0120] The system 20 includes a battery profiler cloud 22 which includes a server in the form of a battery profiler server 24 and a database in the form of a battery profiler database 26. The battery profiler server 24 includes a processing resource 24a and a memory 24b containing instructions which, when executed by the processing resource 24a, cause the processing resource 24a to perform various operations as will be described in more detail below. The battery profiler database 26 stores information relating to each candidate method of a plurality of candidate methods, each candidate method being configured for determining a corresponding battery condition value, wherein the battery condition value corresponding to each candidate method is representative of the condition of the battery 4 of the mobile electronic device 2. The battery condition value may, for example, be a battery cycle count value of the battery 4; a ratio of a present or actual charge capacity of the battery 4 to a design charge capacity of the battery 4 expressed as a percentage or as a fractional value; a proportion of a life-time of the battery 4 which remains expressed as a percentage or as a fractional value; a proportion of a life-time of the battery 4 which has elapsed expressed as a percentage or as a fractional value; or a present or actual wear value of the battery 4 expressed as a percentage or as a fractional value. The information relating to each candidate method may include instructions for performing the candidate method and a battery condition threshold value corresponding to the candidate method. The battery profiler server 24 is configured for two-way communication with the mobile electronic device 2 and for two-way communication with the battery profiler database 26.

[0121] Referring to FIG. 4 there is shown a method generally designated 50 for use in determining a condition of the battery 4 of the mobile electronic device 2. The method 50 begins at step 52, with a user of the mobile electronic device 2 running the app 16. Running the app 16 causes the app 16 to extract at least some of the mobile electronic device data 14 from the mobile electronic device 2 via one or more application programming interfaces (APIs) and to transmit at least some of the mobile electronic device data 14 from the mobile electronic device 2 to the battery profiler server 24 at step 54. Specifically, at step 54, the app 16 extracts at least one of the make, the model and the version of the Android operating system 12 of the mobile electronic device 2 from the memory 6 of the mobile electronic device 2 and transmits at least one of the make, the model and the operating system of the mobile electronic device 2 to the battery profiler server 24.

[0122] At step 56, the method continues with the processing resource 24a of the battery profiler server 24 fetching information relating to each candidate method of the plurality of candidate methods from the battery profiler database 26, each candidate method being configured for determining a corresponding battery condition value. Specifically, the processing resource 24a of the battery profiler server 24 fetches instructions from the battery profiler database 26 for performing each of the candidate methods stored in the battery profiler database 26.

[0123] At step 58, the method continues with the processing resource 24a of the battery profiler server 24 determining whether any of the candidate methods are capable of determining a corresponding battery condition value based at least in part on the mobile electronic device data 14 and the information relating to each candidate method. Specifically, the processing resource 24a of the battery profiler server 24 identifies a set of input parameters required by the instructions for performing each of the candidate methods stored in the battery profiler database 26 and compares the required set of input parameters for each of the candidate methods with a set of parameter values known to be stored in a memory of any mobile electronic device which has the same make, model and version of the Android operating system as the mobile electronic device 2. If the required set of input parameters for any candidate method matches the set of parameter values known to be stored in a memory of any mobile electronic device having the same make, model and version of the Android operating system as the mobile electronic device 2, then the processing resource 24a of the battery profiler server 24 identifies the candidate method concerned as a method which is capable of determining a corresponding battery condition value for the battery 4 of the mobile electronic device 2 based on the historical battery performance data which must be stored in the memory 6 of the mobile electronic device 2. For the specific example of the mobile electronic device 2, the processing resource 24a of the battery profiler server 24 uses at least one of the make, model and version of the Android operating system of the mobile electronic device 2 to identify that the memory 6 of the mobile electronic device 2 must have historical battery performance data in the form of a battery cycle information file specifying a battery cycle count value and a battery stats log file including both historical battery charge data and historical battery drain data as described with reference to FIGS. 1-3. Step 58 then results in the processing resource 24a of the battery profiler server 24 identifying three candidate methods from the plurality of methods stored in the battery profiler database 26, each candidate method being capable of determining a corresponding battery condition value for the battery 4 of the mobile electronic device 2, namely a battery cycle method for determining a battery cycle count as the corresponding battery condition value, a battery charge method for determining a corresponding battery condition value based on a present or actual charge capacity of the battery derived from the historical battery charge data, and a battery drain method for determining a corresponding battery condition value based on a present or actual charge capacity of the battery derived from the historical battery drain data. Each of these three capable methods will be described in detail below.

[0124] In response to the processing resource 24a of the battery profiler server 24 determining that one or more of the candidate methods are capable of determining a corresponding battery condition value, the method continues at step 60 with the processing resource 24a of the battery profiler server 24 transmitting instructions for performing one or more of the capable methods to the mobile electronic device 2. The app 16 then causes the processing resource 8 to perform one or more of the capable methods to thereby determine one or more corresponding battery condition values at step 62.

[0125] For example, where the processing resource 8 performs the battery cycle method, the processing resource 8 simply looks up the battery cycle count value stored in the battery cycle information file in the memory 6 of the mobile electronic device 2 and returns the battery cycle count value as at least one of the determined battery condition values.

[0126] Where the processing resource 8 performs the battery charge method, the processing resource 8 performs the method 200 described with reference to FIGS. 5-7. The method 200 begins at step 202 with the processing resource 8 accessing the design capacity Q.sub.des of the battery 4 from the battery stats log file stored in the memory 6 of the mobile electronic device 2.

[0127] The method continues at step 206 with the processing resource 8 using the battery charging status flags 110, 112, 120, 122 to identify one or more battery charge intervals during which the battery 4 was charged.

[0128] As will be described in more detail below, the method continues at step 208 with the processing resource 8 identifying one or more battery charge ranges within each of the one or more battery charge intervals and determining, for each battery charge range, an estimate Q.sub.act(k) of the actual charge capacity Q.sub.act of the battery, where k is an index assigned to each battery charge range according to the numerical order in which the fractional values of the actual capacity Q.sub.act of the battery in the battery charge ranges occur.

[0129] At step 210, the processing resource 8 estimates the actual capacity Q.sub.act of the battery 4 by averaging the estimates Q.sub.act(k) of the actual capacity of the battery 4 for all of the battery charge ranges according to the formula:

[00003]$Q_{\mathrm{act}}=\frac{1}{N_k}\underset{\forall k}{.Math.}{Q}_{\mathrm{act}}\left(k\right)$

where N.sub.k is the total number of battery charge ranges. It is known that the charge behaviour of a battery of a mobile electronic device is generally non-linear such that the accuracy of the measurement of the battery charge information may vary across the full range of fractional values of the actual capacity Q.sub.act of the battery 4. Consequently, averaging the estimates Q.sub.act(k) of the actual capacity of the battery 4 for all of the battery charge ranges in this way may improve the accuracy of the estimate of the actual capacity Q.sub.act of the battery 4 because it may average out or reduce any variations in the accuracy of the battery charge information across the full range of fractional values of the actual capacity Q.sub.act of the battery 4. It is also thought that the accuracy of the measurement of the battery charge information may vary with usage of the mobile electronic device 2 during charging. Averaging the estimates Q.sub.act(k) of the actual capacity of the battery 4 for all of the battery charge ranges in this way, may also help to account for any variation in the accuracy of the measurement of the battery charge information with usage of the mobile electronic device 2 during charging, thereby helping to improve the accuracy of the estimate of the actual capacity Q.sub.act of the battery 4.

[0130] At step 212, the processing resource 8 returns one or more of the following quantities as one or more of the battery condition values: [0131] the ratio Q.sub.act/Q.sub.des; [0132] the percentage 100×Q.sub.act/Q.sub.des; [0133] a percentage wear value W.sub.p determined according to:

[00004]$W_p=100\times \left(1-\frac{Q_{\mathrm{act}}}{Q_{\mathrm{des}}}\right);$

and [0134] a fractional wear value W.sub.f determined according to:

[00005]$W_f=1-\frac{Q_{\mathrm{act}}}{Q_{\mathrm{des}}}.$

[0135] Step 208 of the method of FIG. 5 will now be described with reference to FIGS. 6 and 7. At step 220, the processing resource 8 identifies any common and any unique battery charge ranges. Specifically, the processing resource 8:

[0136] identifies any common battery charge ranges in which the fractional values of the actual capacity Q.sub.act of the battery 4 of one battery charge interval overlap with the fractional values of the actual capacity Q.sub.act of the battery 4 of any one or more other battery charge intervals; and

[0137] identifies any unique battery charge ranges in which none of the fractional values of the actual capacity Q.sub.act of the battery 4 of one battery charge interval overlap with the fractional values of the actual capacity Q.sub.act of the battery 4 of any one or more other battery charge intervals.

[0138] For example, referring to FIG. 7 there are shown two overlapping battery charge intervals: a first battery charge interval for which the fractional values of the actual capacity Q.sub.act of the battery range from 0% to 60% and a second battery charge interval for which the fractional values of the actual capacity Q.sub.act of the battery range from 30% to 90%. Accordingly, the processing resource 8 identifies three battery charge ranges: [0139] i. a first battery charge range, battery charge range 1, which has fractional values of the actual capacity Q.sub.act of the battery ranging from 0% to 30% and which is unique to the first battery charge interval; [0140] ii. a second battery charge range, battery charge range 2, which has fractional values of the actual capacity Q.sub.act of the battery ranging from 30% to 60% and which is common to the first and second battery charge intervals; and [0141] iii. a third battery charge range, battery charge range 3, which has fractional values of the actual capacity Q.sub.act of the battery ranging from 60% to 90% and which is unique to the second battery charge interval.

[0142] Referring back to FIG. 6, the method continues at step 222 with the processing resource 8 determining, for each common battery charge range (e.g. battery charge range 2 of FIG. 5) and for each battery charge interval to which the common battery charge range is common (e.g. the first and second battery charge intervals of FIG. 7), an estimate Q.sub.act(i, k) of the actual capacity of the battery according to the formula:

Q.sub.act(i, k)=ΔQ(i, k)×100/[p.sub.final (i, k)−p.sub.initial(i, k)]

[0143] where p.sub.initial(i, k) is the initial fractional value of the actual capacity of the battery expressed as a percentage at the beginning of the k.sup.th battery charge range in the i.sup.th battery charge interval;

[0144] where p.sub.final(i, k) is the final fractional value of the actual capacity of the battery expressed as a percentage at the end of the k.sup.th battery charge range in the i.sup.th battery charge interval; and

[0145] where ΔQ(i, k) is the total charge supplied to the battery over the k.sup.th battery charge range in the i.sup.th battery charge interval.

[0146] For the example shown in FIG. 7, there is only one common battery charge range, namely battery charge range 2, and two battery charge intervals, namely the first and second battery charge intervals. Accordingly, step 222 results in the processing resource 8 determining:

p.sub.initial(1,2)=30 and p.sub.final(1,2)=60; and

p.sub.initial(2,2)=30 and p.sub.final(2,2)=60.

[0147] The processing resource 8 also determines, for each common battery charge range (e.g. battery charge range 2 of FIG. 7) and for each battery charge interval to which the common battery charge range is common (e.g. the first and second battery charge intervals of FIG. 7), the total charge ΔQ (i, k) supplied to the battery 4 over the k.sup.th battery charge range in the i.sup.th battery charge interval according to:

ΔQ (i, k)=I.sub.avg(i, k)×T(i, k)

where t.sub.initial(i, k) is the average battery charging current supplied to the battery 4 over the k.sup.th battery charge range in the i.sup.th battery charge interval, and T (i, k) is the duration of the k.sup.th battery charge range in the i.sup.th battery charge interval determined according to the formula:

T(i, k)=t.sub.final(, k)−t.sub.initial(i, k)

where t.sub.initial(i,k) is the relative time value or time stamp corresponding to the first battery charge data point of the k.sup.th battery charge range in the i.sup.th battery charge interval, and t.sub.final(i, k) is the relative time value or time stamp corresponding to the last battery charge data point of the k.sup.th battery charge range in the i.sup.th battery charge interval.

[0148] For the example shown in FIG. 7, there is only one common battery charge range, namely battery charge range 2. Accordingly, for the example shown in FIG. 7, the processing resource 8 determines:

ΔQ(1,2)=I.sub.avg(1,2)×T(1,2)

ΔQ(2,2)=I.sub.avg(2,2)×T(2,2)

where:

[0149] I.sub.avg(1,2) is the average current determined for battery charge range 2 from the battery charging data in the first battery charge interval;

[0150] T(1,2) is the duration associated with battery charge range 2 from the time data in the first battery charge interval;

[0151] I.sub.avg(2,2) is the average current determined for battery charge range 2 from the battery charging data in the second battery charge interval; and

[0152] T(2,2) is the duration associated with battery charge range 2 from the time data in the second battery charge interval.

[0153] The processing resource 8 determines, for each common battery charge range and for each battery charge interval to which the common battery charge range is common, the average battery charging current I.sub.avg(i, k) supplied to the battery 4 over the k.sup.th battery charge range in the i.sup.th battery charge interval according to the formula:

[00006]$I_{\mathrm{avg}}\left(i,k\right)=\frac{1}{N_j\left(i,k\right)}\underset{\forall j\in i,k}{.Math.}{I}_j$

where I.sub.j is the battery charging current supplied to the battery corresponding to the j.sup.th historical battery charge data point, ∀j ∈ i, k indicates that the summation should be performed over all of the historical battery charge data points in the k.sup.th battery charge range in the i.sup.th battery charge interval, and N.sub.j (i, k) is the total number of historical battery charge data points in the k.sup.th battery charge range in the P battery charge interval.

[0154] For the example shown in FIG. 7, there is only one common battery charge range, namely battery charge range 2, and two battery charge intervals, namely the first and second battery charge intervals. The processing resource 8 determines the average battery charging current I.sub.avg(1,2) supplied to the battery 4 over battery charge range 2 in the first battery charge interval according to the formula:

[00007]$I_{\mathrm{avg}}\left(1,2\right)=\frac{1}{N_j\left(1,2\right)}\underset{\forall j\in i=1,k=2}{.Math.}{I}_j$

where I.sub.j is the battery charging current supplied to the battery corresponding to the P historical battery charge data point, ∀j ∈ i=1, k=2 indicates that the summation should be performed over all of the historical battery charge data points in battery charge range 2 in the 1.sup.st battery charge interval, and N.sub.j(1,2) is the total number of historical battery charge data points in battery charge range 2 in the 1.sup.st battery charge interval.

[0155] Similarly, the processing resource 8 determines the average battery charging current I.sub.avg(1,2) supplied to the battery over battery charge range 2 in the second battery charge interval according to the formula:

[00008]$I_{\mathrm{avg}}\left(2,2\right)=\frac{1}{N_j\left(2,2\right)}\underset{\forall j\in i=2,k=2}{.Math.}{I}_j$

where I.sub.j is the battery charging current supplied to the battery corresponding to the P historical battery charge data point, ∀j ∈ i=2, k=2 indicates that the summation should be performed over all of the historical battery charge data points in battery charge range 2 in the 2.sup.nd battery charge interval, and N.sub.j(2,2) is the total number of historical battery charge data points in battery charge range 2 in the 2.sup.nd battery charge interval.

[0156] As shown in FIG. 6, the method continues at step 224 with the processing resource 8 determining, for each common battery charge range, an average of the estimates Q.sub.act(i,k) of the actual capacity of the battery 4 over each battery charge interval to which the common battery charge range is common so as to provide an improved estimate Q.sub.act(k) of the actual capacity Q.sub.act of the battery for the k.sup.th battery charge range according to the formula:

[00009]$Q_{\mathrm{act}}\left(k\right)=\frac{1}{N_{\mathrm{icom}}\left(k\right)}\underset{\forall i\in i_{\mathrm{com}}}{.Math.}{Q}_{\mathrm{act}}\left(i,k\right)$

where ∀i ∈ i.sub.com indicates that the summation should be performed over all of the battery charge intervals to which the k.sup.th battery charge range is common and N.sub.icom(k) is the number of battery charge intervals to which the k.sup.th battery charge range is common. Averaging the estimates of the actual capacity of the battery 4 in this way across each battery charge interval to which each common battery charge range is common, may help to account for any variation in the usage of the mobile electronic device during charging in the common battery charge range in different battery charge intervals, thereby helping to improve the accuracy of the estimate of the actual capacity of the battery 4.

[0157] For the example shown in FIG. 7, there is only one common battery charge range, namely battery charge range 2, and two battery charge intervals. Accordingly, for the example shown in FIG. 7 at step 224, the processing resource 8 simply averages the estimates Q.sub.act(1,2) and Q.sub.act(2,2) to determine an estimate of the actual capacity of the battery for battery charge range 2 according to the formula:

[00010]$Q_{\mathrm{act}}\left(2\right)=\frac{1}{2}\underset{i=1,2}{.Math.}{Q}_{\mathrm{act}}\left(i,2\right)$

Averaging the estimates of the actual capacity of the battery 4 in this way over a battery charge range for different battery charge intervals, helps to account for any variation in the usage of the mobile electronic device 2 during charging, thereby helping to improve the accuracy of the estimate of the actual capacity of the battery 4.

[0158] At step 226 of FIG. 6, the processing resource 8 determines, for each unique battery charge range, an estimate Q.sub.act(k) of the actual capacity of the battery according to the formula:

Q.sub.act(k)=ΔQ(i, k)×100/[p.sub.final(i, k)−p.sub.initial(i, k)]

where p.sub.initial(i, k) is the initial fractional value of the actual capacity of the battery 4 expressed as a percentage at the beginning of the k.sup.th battery charge range in the i.sup.th battery charge interval;

[0159] where p.sub.final(i, k) is the final fractional value of the actual capacity of the battery 4 expressed as a percentage at the end of the k.sup.th battery charge range in the i.sup.th battery charge interval; and

[0160] where ΔQ(i, k) is the total charge supplied to the battery over the k.sup.th battery charge range in the i.sup.th battery charge interval.

[0161] For the example of FIG. 7 there are two unique battery charge ranges, namely battery charge ranges 1 and 3. Accordingly step 226 results in the processing resource 8 determining:

p.sub.initial(1,1)=0 and p.sub.final(1,1)=30; and

p.sub.initial(2,3)=60 and p.sub.final(2,3)=90.

The processing resource 8 also determines, for each unique battery charge range, the total charge ΔQ(k) supplied to the battery over the k.sup.th battery charge range in the i.sup.th battery charge interval according to:

ΔQ(k)=I.sub.avg(i, k)×T(i, k)

where I.sub.avg(i, k) is the average battery charging current supplied to the battery over the k.sup.th battery charge range in the i.sup.th battery charge interval, and T(i, k) is the duration of the k.sup.th battery charge range in the i.sup.th battery charge interval determined according to the formula:

T(i, k)=t.sub.final(i, k)−t.sub.initial(i, k)

where t.sub.initial(i, k) is the relative time value or time stamp corresponding to the first battery charge data point of the k.sup.th battery charge range in the i.sup.th battery charge interval, and t.sub.final(i, k) is the relative time value or time stamp corresponding to the last battery charge data point of the k.sup.th battery charge range in the i.sup.th battery charge interval.

[0162] For the example shown in FIG. 7, there are two unique battery charge ranges, namely battery charge ranges 1 and 3. Accordingly, for the example shown in FIG. 7, the processing resource 8 determines the total charge ΔQ(1) supplied to the battery over battery charge range 1 in the 1.sup.st battery charge interval according to:

ΔQ(1)=I.sub.avg(1,1)×T(1,1)

and the total charge ΔQ(3) supplied to the battery over battery charge range 3 in the 2.sup.nd battery charge interval according to:

ΔQ(3)=I.sub.avg(2,3)×T(2,3)

[0163] The processing resource 8 determines, for each unique battery charge range, the average battery charging current I.sub.avg(i,k) supplied to the battery over the k.sup.th battery charge range in the i.sup.th battery charge interval according to the formula:

[00011]$I_{\mathrm{avg}}\left(i,k\right)=\frac{1}{N_j\left(i,k\right)}\underset{\forall j\in i,k}{.Math.}{I}_j$

where I.sub.j is the battery charging current supplied to the battery corresponding to the j.sup.th historical battery charge data point, ∀j ∈ i, k indicates that the summation should be performed over all of the historical battery charge data points in the k.sup.th battery charge range in the i.sup.th battery charge interval, and N.sub.j (i, k) is the total number of historical battery charge data points in the k.sup.th battery charge range in the i.sup.th battery charge interval.

[0164] For the example shown in FIG. 7, there are two unique battery charge ranges, namely battery charge ranges 1 and 3, wherein battery charge range 1 is unique to the first battery charge interval and battery charge range 3 is unique to the second battery charge interval. The processing resource 8 determines, for unique battery charge range 1, the average battery charging current I.sub.avg(1,1) supplied to the battery over battery charge range 1 in the first battery charge interval according to the formula:

[00012]$I_{\mathrm{avg}}\left(1,1\right)=\frac{1}{N_j\left(1,1\right)}\underset{\forall j\in i=1,k=1}{.Math.}{I}_j$

where I.sub.j is the battery charging current supplied to the battery corresponding to the j.sup.th historical battery charge data point, ∀j ∈ i=1, k=1 indicates that the summation should be performed over all of the historical battery charge data points in battery charge range 1 in the 1.sup.st battery charge interval, and N.sub.j (1,1) is the total number of historical battery charge data points in battery charge range 1 in the 1.sup.st battery charge interval.

[0165] Similarly, the processing resource 8 determines, for unique battery charge range 3, the average battery charging current I.sub.avg(2,3) supplied to the battery over battery charge range 3 in the second battery charge interval according to the formula:

[00013]$I_{\mathrm{avg}}\left(2,3\right)=\frac{1}{N_j\left(2,3\right)}\underset{\forall \in i=2,k=3}{.Math.}{I}_j$

where I.sub.j is the battery charging current supplied to the battery corresponding to the j.sup.th historical battery charge data point, ∀j ∈ i=2, k=3 indicates that the summation should be performed over all of the historical battery charge data points in battery charge range 3 in the 2nd battery charge interval, and N.sub.j(2,3) is the total number of historical battery charge data points in battery charge range 3 in the 2nd battery charge interval.

[0166] Returning to step 210 shown in FIG. 5, for the example of FIG. 7, the processor 6 estimates the actual capacity Q.sub.act of the battery by averaging the estimates Q.sub.act(k) of the actual capacity of the battery 4 for all of the battery charge ranges k=1, 2 and 3 according to the formula:

[00014]$Q_{\mathrm{act}}=\frac{1}{3}\underset{k=1,2,3}{.Math.}{Q}_{\mathrm{act}}\left(k\right)$

[0167] It is known that the charge behaviour of the battery 4 of the mobile electronic device 2 is generally non-linear and it is thought that the accuracy of the measurement of the battery charge information may vary across the full range of fractional values of the actual capacity Q.sub.act of the battery 4. Consequently, averaging the estimates Q.sub.act(k) of the actual capacity of the battery 4 for all of the battery charge ranges in this way may improve the accuracy of the estimate of the actual capacity Q.sub.act of the battery 4 because it may average out or reduce any variations in the accuracy of the battery charge information across the full range of fractional values of the actual capacity Q.sub.act of the battery 4. It is also thought that the accuracy of the measurement of the battery charge information may vary with usage of the mobile electronic device 2 during charging. Averaging the estimates Q.sub.act(k) of the actual capacity of the battery 4 for all of the battery charge ranges in this way, may also help to account for any variation in the accuracy of the measurement of the battery charge information with usage of the mobile electronic device 2 during charging, thereby helping to improve the accuracy of the estimate of the actual capacity Q.sub.act of the battery 4.

[0168] Where the processing resource 8 performs the battery drain method, the processing resource 8 determines one or more of the battery condition values based at least in part on the historical battery drain data. Specifically, with reference to the description of the historical battery drain data of FIG. 3 above, the processing resource 8 accesses the design capacity Q.sub.des of the battery 4, the lower limit min(Σ Q) for the cumulative charge consumed over the drain period, the upper limit max(Σ Q) for the cumulative charge consumed over the drain period, from the battery stats log file stored in the memory 6 of the mobile electronic device 2. The processing resource 8 then determines an average value avg(Σ Q) for the cumulative charge consumed over the drain period according to

[00015]$\mathrm{avg}\left(.Math.Q\right)=\frac{1}{2}\left[\min \left(.Math.Q\right)+\max \left(.Math.Q\right)\right].$

[0169] For the specific battery drain data shown in FIG. 3, this results in an average value avg(Σ Q) for the cumulative charge consumed over the drain period of

[00016]$\frac{1}{2}\left[4887+5427\right]=5157\mathrm{mAh}.$

[0170] Where the historical battery drain data includes a cumulative percentage drop in charge Σp over the drain period, the processing resource 8 determines an actual capacity Q.sub.act of the battery 4 according to Q.sub.act=avg(Σ Q)×100/Σp. For the specific battery drain data shown in FIG. 3, this results in Q.sub.act=5157×100/201=2566 mAh.

[0171] The processing resource 8 then returns one or more of the following quantities as one or more of the battery condition values: the ratio Q.sub.act/Q.sub.des; the percentage 100×Q.sub.act/Q.sub.des; a percentage wear value W.sub.p determined according to W.sub.p=100×(1−Q.sub.act/Q.sub.des); and a fractional wear value W.sub.f determined according to W.sub.f=1−Q.sub.act/Q.sub.des. For the specific battery drain data shown in FIG. 3, this results in the processing resource 8 returning one or more of the following: a ratio Q.sub.act/Q.sub.des=2566/2700=0.95; a percentage 100×Q.sub.act/Q.sub.des=95%; a percentage wear value W.sub.p=5%; or a fractional wear value W.sub.f of 0.05.

[0172] Referring back to FIG. 4, following step 62, the app 16 causes the user interface 10 to display each determined battery condition value and/or causes the mobile electronic device 2 to transmit each determined battery condition value to the battery profiler server 24 or a further server such as a report server (not shown in FIG. 1) at step 64.

[0173] It will be appreciated by one of ordinary skill in the art that various modifications may be made to the foregoing system and method without departing from the scope of the present invention as defined by the claims. For example, a first alternative method may include an additional step performed between steps 58 and 60 of FIG. 4, which additional step includes the processing resource 24a of the battery profiler server 24 selecting an optimum one of the one or more capable methods based at least in part on the mobile electronic device data 14 and the information relating to each candidate method, wherein the battery condition value determined using the optimum one of the one or more capable methods is known to provide a more accurate representation of the condition of the battery of the mobile electronic device than the battery condition value determined using any other one of the capable methods. In this regard, the processing resource 24a of battery profiler server 24 may select the optimum method from the one or more capable methods according to a priori knowledge of an accuracy of each capable method. For example, it is known that a battery condition value determined using the battery cycle method is more accurate than a battery condition value determined using the battery charge method which is, in turn, more accurate than a battery condition value determined using the battery drain method. Accordingly, if the processing resource 24a of the battery profiler server 24 fetches the battery cycle method, the battery charge method, and the battery drain method from the battery profiler database 26 and determines that the battery cycle method, the battery charge method and the battery drain method are each capable of determining a corresponding battery condition value based on the mobile electronic device data 14, the processing resource 24a of battery profiler server 24 may select the battery cycle method as the optimum method in preference to either the battery charge method or the battery drain method. Similarly, when the processing resource 24a of the battery profiler server 24 fetches the battery cycle method, the battery charge method and the battery drain method from the battery profiler database 26, but determines that the battery cycle method is not capable of determining a corresponding battery condition value based on the mobile electronic device data 14, the processing resource 24a of the battery profiler server 24 may select the battery charge method as the optimum method in preference to the battery drain method. Moreover, when the processing resource 24a of the battery profiler server 24 fetches the battery cycle method, the battery charge method and the battery drain method from the battery profiler database 26, but determines that neither the battery cycle method nor the battery charge method are capable of determining a corresponding battery condition value based on the mobile electronic device data 14, the processing resource 24a of the battery profiler server 24 may select the battery drain method as the optimum method. In addition, when the processing resource 24a of the battery profiler server 24 fetches the battery cycle method, the battery charge method and the battery drain method from the battery profiler database 26, but determines that none of the battery cycle method, the battery charge method and the battery drain method are capable of determining a corresponding battery condition value based on the mobile electronic device data 14, the processing resource 24a of the battery profiler server 24 is not able to select an optimum method or to determine a battery condition value.

[0174] Rather than transmitting instructions for performing each of the one or more of the capable methods to the mobile electronic device 2 as described with reference to step 60 of FIG. 4 above, the first alternative method further includes the processing resource 24a of the battery profiler server 24 transmitting instructions for performing only the optimum one of the capable methods to the mobile electronic device 2, and performing the optimum one of the capable methods to thereby determine the corresponding battery condition value.

[0175] In a variant of the first alternative method described above, rather than the processing resource 24a of the battery profiler server 24 performing the additional step of selecting the optimum one of the one or more capable methods based at least in part on the mobile electronic device data 14 and the information relating to each candidate method between steps 58 and 60 of FIG. 4, the app 16 may perform the additional step of selecting the optimum one of the one or more capable methods based at least in part on the mobile electronic device data 14 and the information relating to each candidate method at step 62 of FIG. 4.

[0176] In a second alternative method, the information relating to each candidate method which the processing resource 24a of the battery profiler server 24 fetches from the battery profiler database 26 at step 56 of FIG. 4 includes a corresponding battery condition threshold value and an additional step is performed which includes comparing each determined battery condition value with the corresponding battery condition threshold value and determining whether the battery condition is compliant or non-compliant with a predetermined battery condition test according to the result of the comparison. The additional step may, for example be performed by the processing resource 24a of the battery profiler server 24 between steps 58 and 60 of FIG. 4 or the additional step may be performed by the app 16 at step 62 of FIG. 4.

[0177] FIGS. 8A and 8B together illustrate a combination of the first and second alternative methods described above. Specifically, FIG. 8A shows pseudo code instructions for execution by the processing resource 24a of the battery profiler server 24 for performing an additional step between steps 58 and 60 of FIG. 4 of selecting an optimum one of the one or more capable methods based at least in part on the mobile electronic device data 14 and the information relating to each candidate method. FIG. 8B shows pseudo code instructions for execution by the processing resource 24a of the battery profiler server 24 for performing an additional step between steps 58 and 60 of FIG. 4 of comparing one of the determined battery condition values with the corresponding battery condition threshold value and determining whether the battery condition is compliant or non-compliant with a predetermined battery condition test according to the result of the comparison at step 62 of FIG. 4. Specifically, FIG. 8B shows pseudo code instructions for execution by the battery profiler server 24 for comparing a determined battery cycle count value “Battery_Cycle” with a corresponding battery condition threshold value “cycle_threshold” and determining whether the battery condition is “Good” or “Bad” according to the result of the comparison.

[0178] In a third alternative method, the app 16 extracts historical battery performance data from the memory 6 of the mobile electronic device 2 and transmits the historical battery performance data to the battery profiler server 24 at step 54 of FIG. 4.

[0179] Specifically, the app 16 extracts the battery cycle information file stored in the memory 6 of the mobile electronic device 2 and the battery stats log file stored in the memory 6 of the mobile electronic device 2 and transmits the battery cycle information file and the battery stats log file to the battery profiler server 24 at step 54.

[0180] In a fourth alternative method, rather than the processing resource 24a of the battery profiler server 24 transmitting instructions for performing one or more of the capable methods to the mobile electronic device 2 and the app 16 performing the one or more of the capable methods to thereby determine one or more corresponding battery condition values, the processing resource 24a of the battery profiler server 24 may perform one or more of the capable methods to thereby determine one or more corresponding battery condition values and the processing resource 24a of the battery profiler server 24 may transmit the one or more corresponding battery condition values to the mobile electronic device 2. Such a method may avoid any requirement for the processing resource 24a of the battery profiler server 24 to transmit any instructions for performing one or more of the capable methods to the mobile electronic device 2. In a variant of the fourth alternative method, the processing resource 24a of the battery profiler server 24 may execute some of the instructions for performing each one or more of the capable methods at the battery profiler server 24 and the app 16 may execute some of the instructions for performing each one or more of the capable methods at the mobile electronic device 2.

[0181] A fifth alternative method may comprise the following steps: [0182] i. a user installs an application onto the mobile electronic device; [0183] ii. the application accesses via APIs available mobile electronic device data stored on the mobile electronic device and available battery data stored on the mobile electronic device; [0184] iii. the application sends the available mobile electronic device data and the available battery data to a cloud server; [0185] iv. the cloud server compares the received mobile electronic device data and the received battery data to information maintained on a database and identifies the best (e.g. most accurate) battery condition estimation method based on the make, model and version of the Android OS of the mobile electronic device and the battery data; and [0186] v. instructions for executing the identified battery condition estimation method are downloaded from the cloud server to the mobile electronic device and the instructions are executed to estimate the battery condition.

[0187] A sixth alternative method may comprise the following steps: [0188] i. a user installs an app onto an Android device; [0189] ii. the app is launched; [0190] iii. the app fetches the manufacturer, model and OS version of the Android device and a design capacity of the battery from Android APIs; [0191] iv. the app fetches battery cycle information from a battery cycle information file stored on the Android device, and battery drain log and battery current information from a battery stats log file stored on the Android device; [0192] v. the app uploads the battery cycle, battery drain log and battery current information to a battery profile cloud; [0193] vi. the battery profile cloud includes a list of methods that calculate battery life based on device information received from the app; [0194] vii. the battery profile cloud determines or selects the method to be used for calculating a battery life; [0195] viii. the battery profile cloud sends the selected battery life calculation method as well as any required threshold values to the Android device; [0196] ix. the app uses the selected battery life calculation method as well as any required threshold values to calculate a battery life and/or to determine a battery grade or condition parameter; [0197] x. the app displays the calculated battery life and/or to battery grade or condition parameter on a user interface of the Android device; and [0198] xi. the app uploads the calculated battery life and/or to battery grade or condition parameter to a report cloud along with the manufacturer, model and OS of the Android device.