You want to unleash the “developer” in you, by introducing mods and tweaks on your Android phone. However, it keeps asking you if you have Init.d support.
The Android system uses a custom init process while booting. But, this is not the one we are talking about, as the functionality of the default init is limited.
For optimizing the phone, you will randomly require flashing mods and tweaks to it. If you are scratching your head, wondering how to enable init.d support on your Android phone, look no further. This brief guide should help you in finding the right track.
Prerequisites for enabling init.d
One reason, for which you are unable to make the intended changes, is because your Android phone is not rooted. So, you must do the needful to root it.
You will also need Terminal Emulator (an app available on the Google Play Store) for accessing the Android system’s inbuilt Linux command line shell.
The BusyBox applets are the next requirement. The app is readily available on Play Store. It is a must-have for any rooted phone. Remember, all the rooted applications require these applets for working correctly.
The last requirement will be the term-init script which you can easily download from various trusted sources.
How to Enable init.d Support in Android
The script will execute immediately, and you need to follow the on-screen instructions to make it work.
Below are the things you can do by enabling init.d support on your Android phone:
- By allowing the init.d support, you can now modify various kernel parameters when the device boots. The days of relying on an app to do so will become alien. Now, you can save a lot of memory, and the app storage space.
- You will get the convenience of swapping right at the time it boots.
- Freely create scripts, which will function in the background and do a plethora of tasks.
- If you are an advanced user, you can commence native processes and stop them at your will. A good time to stop the process is when you connect your Android device for charging.
How to check if init.d support is already enabled?
Probably, the developer entity residing in you, propels you to perform several experiments with your Android phone.
If you are unsure if you already had enabled init.d in the past, then there is a way to check it. Why on earth should you redo all these steps, when it is already present? Here is how to check:
Get a Root file manager, and navigate to /system/etc. If you find a folder named as init.d this signals, you have already enabled it previously.
You can also check if the folder has the scripts in it. For double checking, you can further use an app for checking whether the ROM is supporting those scripts.