Revert "Pie Controls: Fix sound effects."

This reverts commit c2cd0dfe9da38cfa7109ff7bcf2db54aa3ae1db8.
Revert "Pie Controls: Fix snap points position."

This reverts commit 553b4b04459623198d5f8fb85f6d5af03f6f2daf.
Revert "Pie controls: A new way of activation"

This reverts commit 3fb8c3a908a27ea05e02738151cd56943b6d376e.
Revert "Pie controls: Introducing a pie delivery service"
Revert "Fix do not show snappoints if triggermask disables edge"

This reverts commit e96de205b8c1deca62a7d66d26a0af3ab3131fc1.
Revert "Disable observer and receiver if PIE is disabled"

This reverts commit 1ccf5677583f834053a01f4fc537458b286ffdde.
Revert "Take mPieScale into account to calculate estimated PIE width"

This reverts commit 80531ef71ef81a7b15759e345c9c17a43b9c5147.
Revert "Adapt navigation bar's long press behaviour for pie controls"

This reverts commit 9d82eab81f0d04c7f11a7e3bd7dda504909f8c7f.
Revert "Improving pie control's user interaction"

This reverts commit 1900ff02ddda3a97ff723d5398e2f4ed1091897c.
Revert "Make Navigation Bar and Pie Controls share the same button layout"

This reverts commit 2eb3723be49ca99bc3d8d85c364493f38e0582b0.
Revert "Fix divisions by zero on boot."

This reverts commit 7b43d33815915fa66c8942a1a2cf67aa248db81d.
Revert "FlingTracker can divide by zero and hang StatusBar in an infinite loop"

This reverts commit a312f3d70153eaa4421d5d7dff327dbb637266d5.
Revert "Fix pie controls being disabled by launcher gestures."

This reverts commit 8c15b6896211d569c16d3bcaa0138d478b1ae89d.
Revert "Add pie control optimizations for Phone UI."

This reverts commit 0d23cdbaadcb721bef21be98bfe539593c494812.
Revert "Pie controls."
Revert "Added support for multiple navigation key bars"

This reverts commit 37ac028b3bb3b2ddd239e8ea5be8cb25ed7173a7.
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.