Smooth Spinners: Makes the loading "spinner" animation smoother in non-holo apps

The loading "spinner" animation is quite jerky by default when the progress xml's from
drawable are called in applications that don't use the holo progress animation. The holo
"spinner" animation is already smooth by default. This makes every other "spinner"animation smooth.We've been changing this value in all ROM's we release, both AOSP and CM based ones as well as stock ROM's, since it gives a more polished look to the entire system. In the past
3 years we've been using this small tweak we have not noticed anything that would adversely affect battery life or system operations as a whole. Signed-off-by: Sar Castillo <sar.castillo@gmail.com>
Change-Id: Iad0a71a5154848a35405e4a199ce1d65d01846fc
locations: core/res/res/drawable/progress_large.xml, core/res/res/drawable/progress_large_white.xml, core/res/res/drawable/progress_medium.xml, core/res/res/drawable/progress_medium_white.xml, core/res/res/drawable/progress_small.xml, core/res/res/drawable/progress_small_titlebar.xml, core/res/res/drawable/progress_small_white.xml, core/res/res/drawable/search_spinner.xml


*
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
Change-Id: I040d710cf0927394f36b2e3da251ac5a988ce1d6
Signed-off-by: Dirk Rettschlag <dirk.rettschlag@gmail.com>  
location: policy/src/com/android/internal/policy/impl/keyguard/KeyguardSelectorView.java


*Fix layout of MultiWaveView and GlowPadView.
If the calculated size of the rings is much smaller than the measured
size (which is happening e.g. on mdpi 600x1024 tablets), the glow pad
appeared shifted to the right.
This happened due to the insets being calculated as difference of
available and needed size, and later on being added to the available
size. Example numbers (Nexus 4 with density forced to 160):
- computed size in onMeasure: 768x505
- scaled size in onMeasure: 505x505
- thus, insets are calculated as 131/0
- in onLayout, placementWidth (364) and max target width (108) are much
  smaller than width (768)
- thus, center is calculated as 131 + (768 / 2) = 515, thus shifted to
  the right

Fix that by not using width in the calculation, as the inset size
already takes it into consideration.
JIRA:CYAN-829
Change-Id: Ifc2a93214f812f554a8fed3243eed66aec9f00c9