[Q] oprofile: functional after initial Android setup?
One of my Android phones (the third in my signature), with limited /data partition storage size, shows a large subdirectory, 'oprofile' in /data/bin/oprofile. Running out of space in this partition seems to be a common problem, so I'd like to keep it as lean as possible.
Some research shows oprofile to be a tool for 'tuning' an Android setup -- but exactly when it's useful is not clear, from what I've been able to find.
My question is, is oprofile purely useful while Android is being configured for a specific phone's hardware? In this case, perhaps someone just forgot to delete it, after it served its purpose -- and then, there's no harm in removing this subdirectory and regaining the space it consumes.
Or, does oprofile serve an continuing purpose, being used by the OS to continue the 'tuning' -- as the user adds new apps? In this case, that directory is functional and should be left alone. Or, is there data in these files, created during the initial 'tuning' that must be retained, for the benefits to continue?
So, what to do? Take it out, or leave it in??
- OS: Android/Linux 2.3.5 ¦ thl A3
- OS: Android/Linux 4.2.2
- OS: Mocordroid/Linux 2.3.5? ('About Phone'
displays 'Android 4.1.2') -