You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am watching in horror the current batteries situation after #75361.
I am not updating my used experimental build because of this.
I feel like the right steps to resolve it are not being taken.
Solution you would like.
I would like to see an .md design document for electronics in doc/ introduced, one that would clearly specify what battery lifetime electronics should have.
Then, having such document, an implementation (battery types, what devices use what batteries, chemistries, on/off cost) can be adjusted and tests can be written that verify it.
My idea of such document would include the following expected battery life times:
flashlight (use time also takes some turning on/off from time to time into account):
I'm not clear on why this needs a design document. Things should last as long as they do irl, you can just start PRing these changes. Although I think there's still some changes to battery capacities coming down the line so you may get to experience some merge conflicts depending on how quick you are about it.
> high power/heavy duty/"high" setting: 8 hours
that's not true, manufacturers specify 8/16/whatever amount of hours this big only for the most dim mode, if you check more of them, you'll find on average they last two hours or so
besides, #76029 should be mentioned that adressed it
the biggest current limiting factor are 1) devices consume power in whole numbers, which #75912 seeks to resolve; and 2) devices cannot accept more than 1 battery at a time, which means multimag aka #75859 needs to happen
Is your feature request related to a problem? Please describe.
I am watching in horror the current batteries situation after #75361.
I am not updating my used experimental build because of this.
I feel like the right steps to resolve it are not being taken.
Solution you would like.
I would like to see an .md design document for electronics in doc/ introduced, one that would clearly specify what battery lifetime electronics should have.
Then, having such document, an implementation (battery types, what devices use what batteries, chemistries, on/off cost) can be adjusted and tests can be written that verify it.
My idea of such document would include the following expected battery life times:
flashlight (use time also takes some turning on/off from time to time into account):
mp3 player: 80 hours of continous use
smartphone: 12 hours of continous use
laptop: 6 hours of continous use
power tools (elecric chainsaw, angle grinder, and similar kW-range tools): 30 minutes of continuous use
soldering iron (battery powered): 40 minutes of continuous use
geiger counter: 2 months in "always on" mode
May have forgotten some but this should be a good start.
This could also include expected mileage for electic cars.
Describe alternatives you have considered.
Whatever is happening currently is the alternative to this.
Additional context
No response
The text was updated successfully, but these errors were encountered: