[Miscellaneous Android Development] codest3r:
Ok... so I got it to work.

Short story:

The only reliable combination I found (after a lot of variations) was to flash WFG's wfg-minions_210.zip, reboot, go back to TWRP, then flash disney frozen princess 210 zip. This worked every time reliably. However, you were right, it did require blowing out Play Market via Settings/Apps/All/Google Play Store/Uninstall updates & Clear Data & Clear cache/reboot. Play Store was the ONLY FC with this approach.

Long story:

As you know I have 3 Nabi's. The one Nabi that was taking the lockscreens fine originally was in the pink bumpers (each has a unique bumper color). Still, when I followed aic's repartitioning I went with stock system, but restored the data/add-ons from the PINK nabi. That means all 3 Nabi's had a fresh system image and the same data/add-on's from the Nabi that liked the lockscreens and didn't get FC crazy on me after flashing.

One would think that all 3 would then behave the same with this lockscreen mod. OMG no... the other two behaved the same damn way and went FC crazy after reboot of any of the lockscreen mods. I tried restoring from TWRP and trying a different lockscreen on the two of them (reboot after reboot) and finally figured out it was faster to just restore stock lockscreen (no need for restore of TWRP backup). The other thing to note: even though I had set "parent mode as default" in security settings before flashing the lockscreen, the lockscreen mod forced the Nabi each time back into child mode. ??? Then with all the FC's inc keyboard I couldn't get to parent mode and had to retreat to TWRP for a restore or flash original lockscreen.

Hence, the only 2.1 lockscreen I could get to work on these 2 misfit Nabi's was the original. I was about to give up and figured I'd try WFG's lockscreen just for shiggles. It took fine. Market worked fine. Could uninstall and reinstall apps fine. So then flashed princess frozen lockscreen. Well, what do you know? I'm still in parent mode and only Play Store is FC"ing. WTH, I'll take it. I tried flashing gapps to address Play Store FC'ing and that didn't fix it so I followed your method. It works. Pain in the arse waiting for it to update back to latest version but it works. Apps now able to uninstall/reinstall again.

Another interesting tidbit. The pink Nabi that liked all the lockscreens on first flash (e.g. arial or whatever): it had Play Store FC's too, but it did not exhibit them until I went into Play and forced an uninstall, then it threw the first FC. (so no background FC's - only foreground FC's).

Conclusion:

? Is there something different about the lockscreens you packaged? Other than the images themselves are all the other bits in the same place? Is there a tool you used of a different version or variety than aic or wfg? I'm baffled. Love the lockscreen variety, minus the install headaches. :)

---------- Post added at 11:38 PM ---------- Previous post was at 11:33 PM ----------

Awesome. Sounds like good approach.

Any benefit to JB over ICS on the Nabi? It would fell newer to me, but probably not noticed by my kids. Keep things a little more consistent with my other Android devices though.

So is another benefit to having JB being able to port in CM or something with the JB kernel/drivers?