android_frameworks_base/packages/FakeOemFeatures/Android.mk

LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)

LOCAL_MODULE_TAGS := optional

LOCAL_SRC_FILES := $(call all-java-files-under, src)

LOCAL_PACKAGE_NAME := FakeOemFeatures
LOCAL_CERTIFICATE := platform

LOCAL_PROGUARD_ENABLED := disabled

include $(BUILD_PACKAGE)

include $(call all-makefiles-under,$(LOCAL_PATH))
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 2012-02-27 18:37:40 -08:00			`LOCAL_PATH:= $(call my-dir)`
			`include $(CLEAR_VARS)`

Temporarily disable FakeOemFeatures from userdebug or higher builds Change-Id: I452d079f60a087a36c20e984b38b8354327e1d5a 2012-06-01 14:07:23 -07:00			`LOCAL_MODULE_TAGS := optional`
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 2012-02-27 18:37:40 -08:00
			`LOCAL_SRC_FILES := $(call all-java-files-under, src)`

			`LOCAL_PACKAGE_NAME := FakeOemFeatures`
			`LOCAL_CERTIFICATE := platform`

Disable ProGuard for FakeOemFeatures to fix build. Change-Id: If0ccf16712bf43adb5fe490906be2a13b484f726 2012-02-28 12:53:19 -08:00			`LOCAL_PROGUARD_ENABLED := disabled`

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 2012-02-27 18:37:40 -08:00			`include $(BUILD_PACKAGE)`

			`include $(call all-makefiles-under,$(LOCAL_PATH))`