Rework thumbnail handling

Since ids of media file are usually not continuous, the original file of thumbnail are
sparse. When there are big numbers files on ex\
ternal storage, the size of this file will be horrible.
Ex, when the id is 20000, then the .thumbnails/.thumbdata3-xx file will be 50000*10k = 488.28M.
Can refer http://stackoverflow.com/questions/12396715/android-huge-thumbdata4-file-in-dcim-folder
Because after 4.0, MediaProvider will scan any files, this will be a big problem. So I modify MiniThumbFile.java to avoid this.
According to the id, we now produce an index file. In this index file, one id will use BYTES_PER_MINTHUMB_INDEX(8) bytes in offset (i\
d+1)*BYTES_PER_MINTHUMB_INDEX. The data of these 8 bytes is the index of thumbnail file. The first BYTES_PER_MINTHUMB_INDEX bytes kee\
p next available index. And when you need insert a thumbnail, the index increase by 1. In this way, the block data in thumbnail file \
will be continuous. And thus unnecessary zero paddings will not be saved.

Change-Id: I66005dd69b0a5c8f4353bd7a8225d163a654fd2d
Hide GlowPadView warnings

Make message verbose and contingent on DEBUG. This has been spamming
my logs everytime I touch navbar or lockscreen targets.

Change-Id: Iea1a6db86055d4034405f0ee4e20282b6c493210
reduce size of optimus4 radius by 80%

Change-Id: Iaf24d13269e0c22669fe2444ab14007058e5ea6e
Merge "Rework thumbnail handling" into cm-10.2
Merge "Hide GlowPadView warnings" into cm-10.2
Fixup cutoff lockring

Credit to Slim

[log]

Change-Id: Icf7e8a5b4940797fc8fa50f80be3fe61fffbf83f

Conflicts:
	core/res/res/layout-land/keyguard_glow_pad_container.xml
	core/res/res/layout-sw600dp/keyguard_glow_pad_container.xml
	core/res/res/layout/keyguard_glow_pad_container.xml
Merge branch 'cm-10.2' of github.com:CyanogenMod/android_frameworks_base into cm-10.2
Merge branch 'upstream/cm-10.2'