History log of /frameworks/base/packages/FakeOemFeatures/Android.mk
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
569ca8b7dd6931d21babb94839dc6029b9c652df 01-Jun-2012 Justin Ho <justinho@google.com> Temporarily disable FakeOemFeatures from userdebug or higher builds

Change-Id: I452d079f60a087a36c20e984b38b8354327e1d5a
/frameworks/base/packages/FakeOemFeatures/Android.mk
04a3a4350e320b65bda9fae6500250c4880e4bf2 28-Feb-2012 Ying Wang <wangying@google.com> Disable ProGuard for FakeOemFeatures to fix build.

Change-Id: If0ccf16712bf43adb5fe490906be2a13b484f726
/frameworks/base/packages/FakeOemFeatures/Android.mk
d459f4bbfcfe4989a0e2298b3cfd36064b386b88 28-Feb-2012 Dianne Hackborn <hackbod@google.com> You could think of this as what an OEM might do.

Except it does nothing.

But eat resources.

Yum, yum!

Current we create five processes. The main process sucks up 16MB of
RAM and creates a full-screen window; only on high-end devices does
the window (and process) use the GPU.

The second through fourth processes just sits there not really doing
anything except using process overhead.

The fifth process runs a background service, slowing eating RAM until
it gets killed by the system (as the system will ultimately do with
background services). It also creates a full-screen window, and always
uses the GPU even on low-end devices.

Change-Id: Ibe9e25f7dbd889f4dc83eed6a3c09b9b0437b4e3
/frameworks/base/packages/FakeOemFeatures/Android.mk