logic involved

SELinux is coming to Android. Called SEAndroid, the project looks pretty interesting:

Some distinctive features of our SE Android reference implementation in comparison to prior efforts of which we are aware include:

• Per-file security labeling support for yaffs2,
• Filesystem images (yaffs2 and ext4) labeled at build time,
• Kernel permission checks controlling Binder IPC,
• Labeling of service sockets and socket files created by init,
• Labeling of device nodes created by ueventd,
• Flexible, configurable labeling of apps and app data directories,
• Userspace permission checks controlling use of the Zygote socket commands,
• Minimal port of SELinux userspace,
• SELinux support for the Android toolbox,
• Small TE policy written from scratch for Android,
• Confined domains for system services and apps,
• Use of MLS categories to isolate apps.

The JVM Serialisers project provides a very extensive comparison of dozens of different JVM serializers out there. Tested tools include several JSON libs, different XML related libs, Scala, protobuf, protostuf, msgpack and many more.
I didn’t know protostuff before – it seems to be really amazing!

(via tutego)

And here it is

Requires Android 2.1 or higher.

Usually the string resources in your Android application are being referred to by a unique ID. But sometimes you will want to recover a string by its key, e. g. when you build the key of the string at the run time of your application (“Battery_Health_2″ or “Battery_Health_3″). You can do that like this:

private String getStringResourceByName(String aString)
{
  String packageName = "com.coliena.myapp";
  int resId = getResources().getIdentifier(aString, "string", packageName);
  return getString(resId);
}

Check this link if you need to recover an image resource by its name.
More information about string resources is available in the Android Developer Documentation.