Back in October of this year, search engine giant Google went on to roll out the Android 12, coming with brand new features such as Material You UI as well as privacy indicators too. And while most of the changes that have in fact come about have been met with positivity, others though have indeed been criticized.

One such change then comes in the form of introducing a rather aggressive background process killer feature which goes by the name of ‘Phantom Process.’ This particular feature can indeed come in as a major hindrance for both developers as well as power users, however, it seems now as if Google is looking towards offering a solution which will allow users to disable this background app policy in future Android versions.

A report that has come forward by XDA developers makes way with a tweet by an expert on the matter, stating “An update on the phantom process issue : Google has just submitted a patch that adds a toggle in Developer Options to disable the monitoring of phantom processes!” It was further then added that this won’t probably be seen until Android 13.

Also Read: Samsung in the hopes to capture 22% of the market

Google has though indeed proceeded on to submit a patch to AOSP which goes on and adds a toggle in Developer Options so as to turn off the Phantom Process monitoring.

For those of you who aren’t aware, ‘PhantomProcessKiller’ happens to be a new feature in Android 12 that is capable to kill forked child processes which are started by apps if they are making use of excessive CPU while their parent app processes also exist simultaneously in the background. Furthermore, the change only allows for up to 32 child processes, hence greatly limiting the number of operations an app can complete while in the background. However, it looks like Google will indeed end up adding a new option which will arrive in order to turn off the Phantom Process Killer in a future Android version which is then likely to be Android 13, however, it could even end up debuting in Android 12L.


Please enter your comment!
Please enter your name here