I think the whole 1013 is kind of a bug with Spare Parts. A lot of people see that, as can be seen from a google search. I've seen it myself, for that matter. If it was a PID, that would be a heck of a coincidence. PIDs are not that consistent, with the exception of the first few (0 and 1 for example have to always be the same). 1013 is likely a UID, as was basically said before. All processes run under a specific UID. Anything in the 1000 range is reserved. Whenever you see "Android System" for example, it's running under UID 1000. That doesn't mean you can find it running using ps with the number 1000. That isn't it's PID. 1013 is the reserved UID for some media process, apparently. I think what it reports is a bug with Spare Parts. It causes it to force close, anyway. The same can happen with non-reserved UIDs. Under partial wake usage, I see 10019. Anything in the 10000 range is for other apps. All running apps are running under a specific UID. It would seem that some of them use the same UIDs even though those in this range are apparently not reserved. 10019, for example, is gapps. Every time I see it in partial wake usage (even though it's only a few seconds or a minute) I can trace it down to gapps. Now, if I go look for the gapps process, I can see that it running as PID 616. That number is somewhat arbitrary, and will not the same every time I look.