Edge (Chromium) for Android drains battery too fast

Have you tried Edge Canary? I see a very noticeable improvement in performance and battery consumption.

I suspect that a good deal of the battery drain may be due to the huge amount of cpu involved with the scheduling of a many,many,many threaded app that (due to Android design) is not permitted to exit (releasing resources) the way it would be able to on a normal OS (such as Linux or even Windows), and perhaps worse, the app's fallure to respond to depressing the "kill tab"  "x"  at the right edge of a tab's label, a failure which in turn prevents release of the schedulable threads corresponding to each of the unwanted tabs that remain. As long as they can't be released,  CPU is wasted determining all of their scheduling priorities and related underlying functions, not to mention the CPU expended when they actually need and are given given time slices for running.

Android needs, but does not provide, a means for the user to say "I don't want any of the threads associated with an app to be considered for scheduling".  Most systems do this by actually allowing a process to exit when the user says "you're done; quit" via some mechanism available to the user, often just a "quit" menu entry.  But with Android, even if an app provides such a menu item, it turns out to do nothing other than obscure the user's view of the app, and is otherwise non-functional when invoked! Only a "Stop app" function that warns of "causing errors" can actually remove it from scheduling.  This is the strongest hint that the app and its threads actually comprise a subroutine (or worse, a discrete coroutine) of a process unrelated to the functionality of the app itself.

Please lobby the Android Developers as follows:  "If you really want an app to stick around when not being used, provide an "opt-in" capability to allow it, but make the default be not to stick around when the user doesn't need it to.  Instead of all apps being effectively subroutines of a single piece of code (which is what they now appear to behave as), perhaps you could replace it with two pieces of code, one for those you wish to always remain in virtual memory and thus be more quickly schedulable (if that's the purpose of such a design), and one from which to run apps that don't want or need that (and thus can be permitted to exit), but which need to be be more robust (such as Edge)."

That would be much better than continuing to accumulate resources until so little is left that some app must be killed and restarted, resulting in data the user had entered (sometimes over a lengthy period of time) being discarded in the process and having to be re-entered.  At least their notebook app appears to be checkpointed, so that one can periodically save a message such as this one there, during its composition, reliably enough that one's typing doesn't need to be re-entered all over again before being complete and ready for submission.

( I truly hate it when a browser, such as Edge, is the app that ends up being killed and restarted for that purpose, and a message or tweet, or whatever must be retyped from scratch)

Microsoft: 

1. Could you fix the difficulty in getting rid of CPU-eating tabs that aren't needed, even without the control character workaround usable by those with keyboards attached?
2. Could you add a limited editing ability that allows removal of entries within the middle of a tab's own history list?
3. Could you automatically and frequently checkpoint what one types into Edge so that when Android kills and restarts it, one does not lose much, so that one needn't manually use another app, such as notepad, to checkpoint one's text entry by hand? (At least until Android Developers fix what affects their CPU scheduling as suggested above) (if ever).

I've contacted them loads of times including here but not one response because MS aren't interested in the Android version and I don't know any other Android browser that drains the battery like Edge

I suspect that a good deal of the battery drain may be due to the huge amount of cpu involved with the scheduling of a many,many,many threaded app that (due to Android design) is not permitted to exit (releasing resources) the way it would be able to on a normal OS (such as Linux or even Windows), and perhaps worse, the app's fallure to respond to depressing the "kill tab"  "x"  at the right edge of a tab's label, a failure which in turn prevents release of the schedulable threads corresponding to each of the unwanted tabs that remain. As long as they can't be released,  CPU is wasted determining all of their scheduling priorities and related underlying functions, not to mention the CPU expended when they actually need and are given given time slices for running.

Android needs, but does not provide, a means for the user to say "I don't want any of the threads associated with an app to be considered for scheduling".  Most systems do this by actually allowing a process to exit when the user says "you're done; quit" via some mechanism available to the user, often just a "quit" menu entry.  But with Android, even if an app provides such a menu item, it turns out to do nothing other than obscure the user's view of the app, and is otherwise non-functional when invoked! Only a "Stop app" function that warns of "causing errors" can actually remove it from scheduling.  This is the strongest hint that the app and its threads actually comprise a subroutine (or worse, a discrete coroutine) of a process unrelated to the functionality of the app itself.

                    

Please lobby the Android Developers as follows:  "If you really want an app to stick around when not being used, provide an "opt-in" capability to allow it, but make the default be not to stick around when the user doesn't need it to.  Instead of all apps being effectively subroutines of a single piece of code (which is what they now appear to behave as), perhaps you could replace it with two pieces of code, one for those you wish to always remain in virtual memory and thus be more quickly schedulable (if that's the purpose of such a design), and one from which to run apps that don't want or need that (and thus can be permitted to exit), but which need to be be more robust (such as Edge)."

That would be much better than continuing to accumulate resources until so little is left that some app must be killed and restarted, resulting in data the user had entered (sometimes over a lengthy period of time) being discarded in the process and having to be re-entered.  At least their notebook app appears to be checkpointed, so that one can periodically save a message such as this one there, during its composition, reliably enough that one's typing doesn't need to be re-entered all over again before being complete and ready for submission.

( I truly hate it when a browser, such as Edge, is the app that ends up being killed and restarted for that purpose, and a message or tweet, or whatever must be retyped from scratch)

Microsoft: 

1. Could you fix the difficulty in getting rid of CPU-eating tabs that aren't needed, even without the control character workaround usable by those with keyboards attached?
2. Could you add a limited editing ability that allows removal of entries within the middle of a tab's own history list?
3. Could you automatically and frequently checkpoint what one types into Edge so that when Android kills and restarts it, one does not lose much, so that one needn't manually use another app, such as notepad, to checkpoint one's text entry by hand? (At least until Android Developers fix what affects their CPU scheduling as suggested above) (if ever).

Sorry, but I disagree with you. As I understand, you tell about background CPU usage. Good written apps don't drain battery on background. Microsoft developers don't care about Android users because all Microsoft apps are terrible if speak about battery usage. Outlook, Teams, Edge - they can kill 4000mah battry just in few hours. Chrome has x2.5 lower battery usage than latest Edge Canary. Microsoft just doesn't profile their apps. Also maybe they use some frameworks like React Native or Xamarin or smth else and this is additional and, almost always, uncontrolled layer in your app. So from my point of view the main problem not inside Android, but inside minds of Microsoft developers and managers.

Have you tried Edge Canary? I see a very noticeable improvement in performance and battery consumption.

I tried Edge Canary and it worked well for a few weeks, then after an update it started draining my battery just like Edge & Chrome.

Best browser I have found to help with battery drain is VIA Browser.

Also, I did find Google Services putting drain on battery (may be tied to browser drain?).

I did a Data Clear on my Google Services to reset it and that has helped.

Moto Z4 with Android 10.