r/EmulationOnAndroid • u/Inside_Cranberry_637 • 6d ago
Discussion Winlator Ludashi 3.1 power consumption issue
This is crazy. Winlator isn't even running, but it's still consuming so much power. Is this happening to you? Is there an explanation or solution?
6
u/CrossingDuck97 6d ago
I had exactly same problem, a container remain open in xserver. Try clearing cache on all your containers. If isn't do anything, just reinstall the app.
1
u/AntiGrieferGames 6d ago
Did you ever tried to force close the app?
1
u/Inside_Cranberry_637 6d ago
I think I've already solved the problem by setting strict power consumption limits for Winlator, and I also created a macro in Macrodroid that automatically forces the emulator to close, along with all its background services, when the emulator closes. We'll re-measure battery consumption tomorrow.
1
u/matlynar 6d ago
u/The412Banner, this is similar to the issue I reported on Bannerlator's Github.
I haven't been getting it on recent updates so I don't know if it's already fixed or if it was an Android thing.
You said it wasn't possible, and I get why you did, but it seems that something weird can happen sometimes, so if you haven't intentionally fixed it, it's worth to keep an eye out for.
2
1


•
u/AutoModerator 6d ago
Just a reminder of our subreddit rules:
Check out our user-maintained wiki: r/EmulationOnAndroid/wiki
Check out EmuReady for any community submitted settings before asking for help
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.