Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always disable low-processor usage mode on mobile platforms #40981

Closed

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Aug 2, 2020

This partially addresses #19304.

Note: It may be easier to cherry-pick this PR by copy-pasting the relevant parts rather than using git cherry-pick.

@Calinou Calinou requested a review from a team as a code owner August 2, 2020 20:26
@Calinou Calinou added bug cherrypick:3.x Considered for cherry-picking into a future 3.x release platform:android platform:ios topic:porting labels Aug 2, 2020
@Calinou Calinou added this to the 4.0 milestone Aug 2, 2020
@Calinou Calinou force-pushed the low-processor-mode-ignore-mobile branch from 348c0db to bf5d16e Compare August 2, 2020 20:28
@tavurth
Copy link
Contributor

tavurth commented Aug 3, 2020

@Calinou Thank you for this! 🎉

@akien-mga
Copy link
Member

I don't think it's a good idea, the proper fix would be to make low processor usage actually work reliably on Android.
Additionally, there might still be use cases for it for non-game apps that don't use high FPS features.

I'm not against adding a workaround as a stopgap solution for now, but this should be done via feature tags, not hardcoded.

@Lauson1ex
Copy link
Contributor

Lauson1ex commented Mar 9, 2021

Instead of opening yet another issue report about this problem that have been present in the engine for almost 5 years, I would like to report that I, too, am facing this issue. Currently I'm working on a project which introduces a novelty control interface, where the project is controlled by its companion phone app. The thing is, the companion phone app doesn't need all the resources it consumes, which is undesirable — it only needs to update logic/inputs and send UDP packets every 33 millisecs. The solution is the low processor mode, which works for the most part by making the phone use less CPU resources and even enabling fast app switching, but this introduces the described graphical glitches in Control nodes in the aforementioned issue reports. Low processor mode is crucial for my project.

I don't think it's a good idea, the proper fix would be to make low processor usage actually work reliably on Android.
Additionally, there might still be use cases for it for non-game apps that don't use high FPS features.

I'm not against adding a workaround as a stopgap solution for now, but this should be done via feature tags, not hardcoded.

As @akien-mga said, it would probably be a good idea to implement a proper solution to this long-standing issue, rather than eliminating the feature altogether for Android, as it will also greatly benefit non-game mobile app developers.

@Calinou
Copy link
Member Author

Calinou commented Feb 2, 2022

Superseded by #55604.

@Calinou Calinou closed this Feb 2, 2022
@Calinou Calinou added archived and removed cherrypick:3.x Considered for cherry-picking into a future 3.x release labels Feb 2, 2022
@Calinou Calinou deleted the low-processor-mode-ignore-mobile branch February 2, 2022 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants