[Android Q&A, Help & Troubleshooting] DrWu:
My phone is a Samsung Galaxy Core Prime SM-S820L (Tracphone) running Psilocelium's custom KitKat 4.4.4 ROM (rooted, build.prop tweaked, init.d support, deKNOXed, deBloated, deODEXed, ZipAligned, etc, etc) flashed with Odin. I also have TWRP recovery v2.8.7.0 installed.

This is a little involved so please excuse me if my description is disjointed.

There seems to be a problem (two, actually) caused by installing BusyBox. The first problem is that it breaks AirDroid's AirMirror function. After installing BusyBox and rebooting, AirDroid program on PC no longer can connect via AirMirror to AirDroid on the phone.

When it connects successfully, when the PC interrogates the phone, there is a one-line SuperSU pop-up message reading "AirDroid has been granted superuser permissions." There are other messages to follow, but I'm speaking only of the initial SuperSU message. But if BusyBox is installed, there is a second line included in that initial message which reads, "kill -15 ..." followed by a process number. The process number increments upward each time the attempt is made to connect. I haven't been able to find out which process it's killing but I have determined (by capturing the output from a "ps" command in Android Terminal Emulator) that it's a process number higher than anything that was running before making the attempt to connect with AirMirror (so I'm guessing it's some AiMirror process that it's killing).

If BusyBox is installed, the attempt to connect via AirMirror ALWAYS produces the two-line initial SuperSU message with the extra "kill -15" line. And the Windows-side AirMirror application ALWAYS errors out saying, "AirDroid failed to get root permissions...."

Using the AirDroid web client, AirDroid itself connects to the phone fine but when I try to run the AirMirror function the phone shows the same "kill -15" message from SuperSU and the web client displays a generic "Failed to start service" message.

On one occasion when trying to connect with AirMirror from web.airdroid.com, SuperSU pop-up displayed the usual "kill -15" message followed briefly by a "kill -9" and the same process number. So whatever it is it's killing, it wants it dead pretty bad.

I've tried using several alternate versions of Stericson's BusyBox, from 5.5 back to 4.9. All that I've tried fail in the same fashion with identical messages.

I also tried this after wiping the phone, flashing to the stock ROM and rooting with KingRoot. Psilocelium's pared-down ROM is pre-rooted so I didn't have to mess with KingRoot. With KingRoot (and after BusyBox is installed), it fails identically to the pre-rooted ROM except that there is no telltale "kill -15" message as SuperSU produces.

I know there are methods for uninstalling KingRoot and turning over its duties to SuperSU but I haven't tried that yet because the advantages of Psilocelium's custom ROM are too numerous.

The second problem (seemingly) being caused by BusyBox has only occurred (thus far) when using Psilocelium's custom ROM. It sometimes but not always provokes the "Android is upgrading..." error. Whether the error occurs might have something to do with which other apps I have installed previous to it but as yet I haven't been able to pin that down.

It goes through "Android is upgrading..." and ends with "Unfortunately, the process android.process.acore has stopped," or "Unfortunately, LogsProvider has stopped" or both. Sometiumes there is a third message but they switch back and forth too quickly to read the one sandwiched in the middle.

At that point the boot process is halted and when I long press the power button, the button on the screen offering to let me reboot is blocked by the error messages, so the only way forward is to remove the battery.

I've found quite a few claimed fixes for this but the most of them seem to involve changes that only can be made once the OS has loaded. But when my phone is experiencing this problem, the OS won't load, even if I try rebooting repeatedly. What I

have

tried is clearing the cache cache by itself, clearing the Dalvik cache by itself, and then both caches together but the problem persisted. In every case, all I need do is restore a Nandroid backup from before I installed BusyBox and it boots normally.

Another claimed 'fix' involved disabling "System Updates" from within Application Manager but there is no such applet in my (Samsung) phone. And since the phone won't boot, the best I could do would be to clear its cache beforehand anyway. I do have a "Samsung Updates" applet but turning it off does not affect the problem.

I also have found references to the problem being caused by .odex files in the /data/app directory, but I have no .odex files in that directory.

Other tips said to delete the contacts but this is a clean install and I haven't yet populated the contacts manager. Still another said to edit the file /system/csc/others.xml and change the line that reads this:

<CscFeature_Calendar_EnableLunar> TRUE </CscFeature_Calendar_EnableLunar>

... to this ...

<CscFeature_Calendar_EnableLunar> false </CscFeature_Calendar_EnableLunar>

My 'others.xml' didn't have the line to start with but out of desperation I added the 'false' version anyway. It didn't help.

So if you know how either of these might be fixed, or even can point me to a resource that might help, I'd be obliged.