Block all apps & SystemUI to free up RAM for WinXP Emulator
to almost, practically
multi-boot my tablet with Windows, using Bochs emulator. Bochs emulator is an Android app, so I still must have Android booted, but any apps, including SystemUI, are *not* needed (until I restart my tablet, plan on using Tasker to handle renaming apk's to bak's and vice versa.
I have a Dell Venue Andoid tablet w/ Intel, runs WinXP pretty well (emulator), and I would like to disable all apps from running while using my emulator. This is to clear up RAM and provide better speeds, along with not having other Android app interruptions/notifications/push services, including Google.
Note: Please don't suggest RAM cleaners... I'm literally turning off all apps including launcher and systemui.
I'm posting a thread because I'm specifically wondering if SystemUI is required
to complete the boot process in Android 4.3 Jellybean. I feel that the process "Android System" should be everything I need to just launch my app at boot_completed. SystemUI, however, uses over 100MB in present RAM providing for the status bar, notifications, softkeys, and that crap. You'd be surprised what's actually running on your RAM. Android App Manager is biased and doesn't display system or Google apps. I used this
app to actually figure it all out, worked great.
You guys, creating custom ROMs and such, should know about the composition of the boot process, and what affects it. So I'm asking you guys.
I already tried Boot Managers to block the boot_completed intents, even the Xposed ones, but it didn't actually free up RAM, nor did they allow me to block Google apps (such as Play Store, Youtube, they all run on present RAM--crazy).
Will renaming SystemUI.apk to .bak brick my tablet. BTW, Dell Venue tabs have unlocked bootloaders.