Estimated Charging Time

Dm114

Well-known member
I worked a bit in the logic of the macro and changed the variables to work with abs values. But the time is still really big, and makes sense with such low currents (mA).

I've been doing some fast research and 1 and 2 mA charging is indeed super slow. I'm confused, if the reading is correct then you would really be having a very long charging time.

"Based on the available information, 3 mA (milliamps) is a relatively low charging current for most modern smartphones. Typically, fast charging capable phones charge at currents ranging from 500-1500 mA (0.5-1.5 amps) or even higher." (mine is 67w and goes up to 12000)
I believe we are getting the readings wrong for some reason. Could this be a problem in the magic text part ?

I will anyway update the macro to work with absolute values to prevent the wrongly displayed negative values
I charged from 25% to 80% and it takes ≈1h (1½h max)
 

Shiffo

Active member
I charged from 25% to 80% and it takes ≈1h (1½h max)
Then if you charge for :
90m from 25% to 80% with a total capacity of 5000 mAh :
you are charging at an avg speed of 2000(mA) (2 amps). (I did the math)

What I find weird is that your magic text seems to record in Amps instead of miliAmps as it should ...
Like imagine charging a 5000 mAh battery at just 1mA per hour..
Imagine that charging at 5000 mA it would take you 1h. (from 0 to 100)
At 2000 mA -> 2,1/2 hs (0 to 100)
At 10000 (like me) just 30m

In short there's no way the values are correct. Or it's for some reason displaying in Amps (divided by 1000)
 

Attachments

  • IMG_20240803_075104.jpg
    IMG_20240803_075104.jpg
    208.7 KB · Views: 3

Dm114

Well-known member
Then if you charge for :
90m from 25% to 80% with a total capacity of 5000 mAh :
you are charging at an avg speed of 2000(mA) (2 amps). (I did the math)

What I find weird is that your magic text seems to record in Amps instead of miliAmps as it should ...
Like imagine charging a 5000 mAh battery at just 1mA per hour..
Imagine that charging at 5000 mA it would take you 1h. (from 0 to 100)
At 2000 mA -> 2,1/2 hs (0 to 100)
At 10000 (like me) just 30m

In short there's no way the values are correct. Or it's for some reason displaying in Amps (divided by 1000)
You're probably right (we'll have to ask @MacroDroidDev when he's back from holidays) but, obviously, Magic Text returns a value in A, instead of mA.

It's the way I interprete it since this Magic text has been added a long while ago. I've been running 2 various devices on Android v9, v12 and now v13 and I always had the same range of values.
 

Shiffo

Active member
we'll have to ask @MacroDroidDev when he's back from holidays
Yeah..

but, obviously, Magic Text returns a value in A, instead of mA.
How weird , how am I getting values above 10000 then? Lol
The screenshots are from my phone without charging. The "floating text" one is from a macro that displays the magic text in real time (note that without charging the values are + on my device)

I should check again with the other phone to compare
 

Attachments

  • IMG_20240803_115047.jpg
    IMG_20240803_115047.jpg
    397.2 KB · Views: 5
  • IMG_20240803_115027.jpg
    IMG_20240803_115027.jpg
    221.6 KB · Views: 5

Endercraft

Moderator
Wouldn't it be funny if the value was device-specific.
I get negative values whenever I'm not charging or the charger is too slow to actually charge and just makes discharge slower, and positive values when it is charging. At 100% I get 0 and at 0% I don't get anything because my device is already shut down.
 

Shiffo

Active member
Wouldn't it be funny if the value was device-specific.
I get negative values whenever I'm not charging or the charger is too slow to actually charge and just makes discharge slower, and positive values when it is charging. At 100% I get 0 and at 0% I don't get anything because my device is already shut down.
Since you are here . What about yoh, Do you get low or big values ? Like less than 10 like dm114 or in the hundreds/thousand ?
 

Dm114

Well-known member
Yeah..


How weird , how am I getting values above 10000 then? Lol
The screenshots are from my phone without charging. The "floating text" one is from a macro that displays the magic text in real time (note that without charging the values are + on my device)

I should check again with the other phone to compare
Here's what I just got a few minutes ago. I also display this raw value (with some others) in a Floating Text to not have to run the macro after its 1st run: these values are updated automatically.
Screenshot_20240803_113448_One UI Home.jpg
 

Endercraft

Moderator
Since you are here . What about yoh, Do you get low or big values ? Like less than 10 like dm114 or in the hundreds/thousand ?
I usually get negative values in the hundreds when not charging, expect when I do consuming tasks like watching videos at maximum luminosity. Usually when I charge with the charger that came with my phone, it goes in the positives thousands (I think the max I got was 4000, but that's not constant, only a spike).
 

Shiffo

Active member
I usually get negative values in the hundreds when not charging, expect when I do consuming tasks like watching videos at maximum luminosity. Usually when I charge with the charger that came with my phone, it goes in the positives thousands (I think the max I got was 4000, but that's not constant, only a spike).
Yeah more similar to mine . On your phone my macro should work . Do you want to try ?


Wouldn't it be funny if the value was device-specific
Yes that seems to be the case. Depends on the battery apparently.
I fixed that issue working with absolute values. Since it doesn't really matter whether it's +/-.
Further from 0 means faster closer slower
 

Endercraft

Moderator
I'll try it when I can charge my phone. You wouldn't mind making another post in a few hours in case I forget? I'm busy with another macro right now.
 

Endercraft

Moderator
I'm testing it right now, it seems to be accurate (gives me 1h of time remaining until 95%, right now at 22%).
Actually it seems to be alternating between 1h and 3h30m, but that's probably due to my screen being off, then on again. And also the first time running it.
 

Shiffo

Active member
I'm testing it right now, it seems to be accurate (gives me 1h of time remaining until 95%, right now at 22%).
Actually it seems to be alternating between 1h and 3h30m, but that's probably due to my screen being off, then on again. And also the first time running it.
Great ! Thank you!

Yes the fisrt time you charge, it calculates with the current values, so it will flicker quite a bit.
The second time after registering your ch speed at 95% it will work with an average (so it will be much more stable and precise) and will still alternate when the current speed goes below the average. (for example when changing from screen off to on)
 

Shiffo

Active member
@Dm114 I think the difference in the magic text lies in the info the OS is handing to MD. Yours saves values in A and mine in mA.

So i will be trying to implement a fix to get it to work with both A or mA. Wish me luck 🤞😉
 

Shiffo

Active member
I hope Jamie takes a look into it to make it the same across all devices .
Like before displaying check if it's A or mA and then convert...?

For example all my values are integer (I mean even using decimal variables ofc), and yours have decimals
 

Dm114

Well-known member
I hope Jamie takes a look into it to make it the same across all devices .
Like before displaying check if it's A or mA and then convert...?

For example all my values are integer (I mean even using decimal variables ofc), and yours have decimals
I just display the raw Magic Text content without any calculation.
 
Top