[Sprint Samsung Galaxy Note 3] GAPO:
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.

Device: SM-N900P

Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).

The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:

-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).

-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.

-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.

The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.

I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://xdaforums.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .

After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://xdaforums.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.

Then I installed this mod to pump sound out of both speakers: http://xdaforums.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.

Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://xdaforums.com/showthread.php?t=2752379 . Again, no problems.

I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://xdaforums.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.

I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://xdaforums.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://xdaforums.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.

This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://xdaforums.com/galaxy-note-3/themes-apps/mod-camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://xdaforums.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.

Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://xdaforums.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .

I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.

I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.