[Motorola Droid 4] Jishkah:
Exactly. I don't know what went wrong, honestly. I tried installing the Gapps package with "default" partition values, and it flashed without a hitch - no error messages or anything. Booted into the CM12 environment, and it was... buggy. Definitely buggy. It was missing the Play Store, specifically; it looks like everything else was included, but without the Play Store, I can't update any of the apps, and Google Play Services can't be updated, either. I had several notifications thrown at my phone about different apps needing different Play Services permissions, and needing to update Play Services, and it was all a mess and nothing would work.

What's odd is that the problem persisted after using custom partition values, as well... I had 1000MB dedicated to the System partition, 3300MB dedicated to the Data partition, and 1010MB dedicated to the Cache partition - more than enough, in my opinion, to accommodate the Gapps package. The download wasn't corrupted, either; I downloaded the package a few times, but the problem persisted.

Haha, that's good to hear. In that case, I think that I'll try sticking around with CyanogenMod 12, for a bit longer. Looks like I jumped on the bandwagon at a buggy time, is all. Besides, one more tester couldn't hurt, right?

Yep! I saw that. I haven't tried applying those fixes, myself, however, if only because I wanted to wait until the bug was addressed in a later nightly without having to mess around with the already-sensitive APN settings. It was supposed to be fixed in the 20150308 Nightly, but that nightly hung at boot; I couldn't get it to run - not from a clean install, at least. If it's not one problem, it's another problem, lol. Hopefully the next Nightly will be released soon, and it'll fix both the Data issues and the "Oh no, it won't boot" issues.

I can't even begin to figure out why it's acting that way for you. That, along with your issues with Safestrap, are... yeah, I don't understand why it's acting up like that. That definitely sounds like a bug, on your end. Have you tried uninstalling Safestrap and then reinstalling from scratch? Make sure that you choose the Restore Defaults option in Advanced Settings after you reinstall everything - that way, it doesn't use any of the values left over from your previous Safestrap install.

Other than that, Safestrap has always been a bit finicky for me, too. Usable, stable, but finicky. I'll perform a bunch of heavy operations on it, for example, and it'll sometimes fail to auto-detect a ROM on the ROM Slot that I'm booting into - despite a ROM clearly being installed. It's not a big deal, though, and it's not like it's broken - it's just something that I need to be aware of, since the "No OS is installed" dialogue can give me a bit of a heart attack if I'm not aware that, yes, an OS IS installed.

Anyway, yeah. I think that I'm gonna bite the bullet and install the Paranoid Android Gapps package - would the Pico package work fine? I've never used the PA Gapps packages, myself... I've always figured that the CyanogenMod Gapps packages are packed the way that they are for a reason: CyanogenMod comes pre-installed with a modified AOSP "framework", of sorts, and a "normal" Gapps install tends to overwrite chunks of said framework with Google's proprietary stuff (which I don't necessarily agree with; it's why I continue to use CyanogenMod, really). I want to preserve CyanogenMod's AOSP changes, so I've always just used whatever Gapps package is available on the CyanogenMod Wiki - I figure it's packaged with showcasing CyanogenMod's AOSP changes in mind.

I'll install the PA Gapps package later today, and return with an update when I can.

Yeah, and that's what's odd, y'know? Even after resizing the System partition to its maximum value of 1000MB, the same problems occur. I'd understand if I had an internal storage of 256MB, but the phone's storage is relatively large - large enough to accommodate partition size values that'll stand the test of time, at least. I don't install anything onto the Stock ROM slot, either, outside of the stock ROM, so it's not as if I'm constrained by any hard limits. Your typical CyanogenMod installation package is ~250MB, and your typical Gapps package is ~150MB - that's 400MB, altogether. The default System partition is 700MB, which is more than enough to accommodate 400MB. So unless 400MB is capable of ballooning into 1000MB+ during the installation/set-up process, I don't think that storage is the issue, here. Surprisingly enough, the Droid 4 has more than adequate storage, when all's said and done.