I really want to know how to hide the keys...
Generally you try to move sensitive material outside an attackers control. Usually that means moving as much sensitive code and data to a server (and out of a client).
If possible, run the Parse.com code on the server so that the client does not need the API keys to begin with. There's little risk the keys will be leaked because they won't be on available to an attacker on the client.
If you authenticate the user, then keep the API key on your server. Provide it to the application once the user authenticates. There's still risk the key will be leaked, but it won't be hard coded into the app and easily found with an analysis tool like APKTool.
There are other steps you can take too. Proguard and encryption of the API keys come to mind. On Android 4.0 and above, you should also store them in the Keychain. It will stop the unmotivated attacker, and slow down a motivated one. Most of these are covered at Best Practice for storing private API keys in Android.
You can also encrypt the binary for distribution, but I understand this is more a DRM control from Google Play (and less a application/data security control). See, for example, Questions about Google Play application assets encryption.