Estimated Charging Time

md_sgf

Active member
If you are looking to control the plug with MacroDroid, you may want to choose one that is compatible with this (it will save you a lot of hassle):

I have seen that thread before, but thanks for reminding me.
 

Shiffo

Active member
Additional info (good to know):
If the prediction is still off by several minutes after the first charge then it most likely means your battery is deteriorated and no longer retains the total capacity (mAh) as it used to when first bought. Try lowering the value (total battery capacity "mAh") until the prediction is on point. ¡ NOW YOU HAVE FOUND YOUR ACTUAL BATTERY CAPACITY ! (useful life)
 

Dm114

Well-known member
Hello fellow members!

I made a macro that calculates in real time how much time left until full charge (or desired % lvl) based on current speed (mA).
Meaning that we can see the difference between charging without using the phone and using it, in virtually real time.

Check it and see for yourself. All and any feedback is always apreciated.
Cheers!

I'm trying your macro (it runs for the 3rd or 4th time while device is charging) and I get a lot of strange messages (Floating Text) with odd values. Below is one of the various examples...
Screenshot_20240802_114705_Settings Suggestions.jpg
 

Dm114

Well-known member
Hello fellow members!

I made a macro that calculates in real time how much time left until full charge (or desired % lvl) based on current speed (mA).
Meaning that we can see the difference between charging without using the phone and using it, in virtually real time.

Check it and see for yourself. All and any feedback is always apreciated.
Cheers!

Another strange message: "Please wait +1%" with a countdown below 🤔
Screenshot_20240802_130253_MacroDroid.jpg
 

Shiffo

Active member
You use a very very very slow charger :ROFLMAO:
You know i tried it with my wife's charger. Very slow charge because the charging port is broken . And I get positive numbers . Because mA is above 0. Thus getting negative prediction, like your phone is UN-charging 🤣 Perhaps that's the reason ? 🤔 I definetly have to give it another look. I want it to work for everyone 😉
 
Last edited:

Qarboz

Well-known member
It's the original one (2A) delivered with the device I just bought a couple of weeks ago.

Too powerful ("fast") chargers are not very good for battery health (durability)...
I wanted to make a joke because in the picture it looks like 2164 hours (90 days!) to the end of the charge... :)
 

Shiffo

Active member
I haven't looked in the macro but I assume the time is calculated by seeing how much time it takes to get up by 1%.
Yes and no . I added that message because when you just connect the cable the current speed (mA) is very low at first and increases with time (after like a minute), so i don't want to show an early prediction that will most likely be very wrong..

It works by recording in a variable the charging speed at connection (or the highest registered mA) and also store the charging speed at destination (e.g100%)(lowest) to get an average throughout the charge.

Avg_ch_speed=(Ch_speed_at_connection+speed_at_destination)/2

And the formula goes like this:

Remaining time in minutes = (Total battery capacity - current charge)/Avg_ch_speed*(-60)

And some other magic to get a dynamic prediction. I.e if your charging speed gets below the average (for example if you are using the phone) it will work with that new number instead

I'm trying your macro (it runs for the 3rd or 4th time while device is charging) and I get a lot of strange messages (Floating Text) with odd values. Below is one of the various examples..
What values are you getting in the charging speed variables ?
In my device all numbers are negative, so I assumed that was the case for everyone else's. Check the attached screenshot.
 

Attachments

  • IMG_20240802_160819.jpg
    IMG_20240802_160819.jpg
    246.4 KB · Views: 2
Last edited:

Shiffo

Active member
Another strange message: "Please wait +1%" with a countdown below 🤔
View attachment 10649
The countodown is the charging time(how long the charger has been connected)

Btw did you charge all the way to your designated battery lvl threshold (%) ?
Because you need to record your charging speed at that point for calibration for future predictions
 
Last edited:

Dm114

Well-known member
You know i tried it with my wife's charger. Very slow charge because the charging port is broken . And I get positive numbers . Because mA is above 0. Thus getting negative prediction, like your phone is UN-charging 🤣 Perhaps that's the reason ? 🤔 I definetly have to give it another look. I want it to work for everyone 😉
It is charging between 0.800 and 2.000 depending on what is running (I have it live on my screen).
 

Dm114

Well-known member
Yes and no . I added that message because when you just connect the cable the current speed (mA) is very low at first and increases with time (after like a minute), so i don't want to show an early prediction that will most likely be very wrong..

It works by recording in a variable the charging speed at connection (or the highest registered mA) and also store the charging speed at destination (e.g100%)(lowest) to get an average throughout the charge.

Avg_ch_speed=(Ch_speed_at_connection+speed_at_destination)/2

And the formula goes like this:

Remaining time in minutes = (Total battery capacity - current charge)/Avg_ch_speed*(-60)

And some other magic to get a dynamic prediction. I.e if your charging speed gets below the average (for example if you are using the phone) it will work with that new number instead


What values are you getting in the charging speed variables ?
In my device all numbers are negative, so I assumed that was the case for everyone else's. Check the attached screenshot.
Here's an example...Screenshot_20240802_163858_MacroDroid.jpg
 

Dm114

Well-known member
I haven't looked in the macro
Neither did I.

I've been using a personal very old macro (on MD v3 😉) which is not as accurate as I'd like, but much simpler (based on the time elapsed during the last 3 battery level change). At that times, there were no Magic Text... 😀

I just wanted to check the difference in accuracy between the 2 macros.
 
Last edited:

Shiffo

Active member
Neither did I.

I've been using a personal very old macro (on MD v3 😉) which is not as accurate as I'd like, but much simpler (based on the time elapsed during the last 3 battery level change). At that times, there were no Magic Text... 😀

I just wanted to check the difference in accuracy between the 2 macros.
Well you get positives values when charging , i guess i will just use absolute values and see if that fixes it. If you want to give it some thought you are welcome 😉
Thank you for the screenshot
 

Shiffo

Active member
Neither did I.

I've been using a personal very old macro (on MD v3 😉) which is not as accurate as I'd like, but much simpler (based on the time elapsed during the last 3 battery level change). At that times, there were no Magic Text... 😀

I just wanted to check the difference in accuracy between the 2 macros.
For me it's been very accurate, with an off time of just ~1m and I can easily see the difference between charging using /not using the phone
 

Shiffo

Active member
This screenshot was taken after some 10 minutes charging
Ok thank you ! I will give it some deep thought and I will get back to you with good news 👏. I have little time today, so it will probably have to wait until tomorrow
 

Shiffo

Active 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
 
Top