replicant-vendor_replicant/products/cyanogen_fascinatemtd.mk

# Inherit AOSP device configuration for fascinatemtd.
$(call inherit-product, device/samsung/fascinatemtd/full_fascinatemtd.mk)

# Inherit some common cyanogenmod stuff.
$(call inherit-product, vendor/cyanogen/products/common_full.mk)

#
# Setup device specific product configuration.
#
PRODUCT_NAME := cyanogen_fascinatemtd
PRODUCT_BRAND := samsung
PRODUCT_DEVICE := fascinatemtd
PRODUCT_MODEL := SCH-I500
PRODUCT_MANUFACTURER := samsung
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SCH-I500 BUILD_ID=GINGERBREAD BUILD_FINGERPRINT=uscc/SCH-I500/SCH-I500:2.3.4/GINGERBREAD/EH09:user/release-keys PRIVATE_BUILD_DESC="SCH-I500-user 2.3.4 GINGERBREAD EH09 release-keys"

# Extra fascinatemtd overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/fascinatemtd

# Add the Torch app
PRODUCT_PACKAGES += Torch

# Release name and versioning
PRODUCT_RELEASE_NAME := Fascinate
PRODUCT_VERSION_DEVICE_SPECIFIC :=
-include vendor/cyanogen/products/common_versions.mk

#
# Copy galaxys specific prebuilt files
#
PRODUCT_COPY_FILES +=  \
    vendor/cyanogen/prebuilt/hdpi/media/bootanimation.zip:system/media/bootanimation.zip
add fascinatemtd target 2011-07-14 22:28:14 +00:00			`# Inherit AOSP device configuration for fascinatemtd.`
			`$(call inherit-product, device/samsung/fascinatemtd/full_fascinatemtd.mk)`

			`# Inherit some common cyanogenmod stuff.`
			`$(call inherit-product, vendor/cyanogen/products/common_full.mk)`

			`#`
			`# Setup device specific product configuration.`
			`#`
			`PRODUCT_NAME := cyanogen_fascinatemtd`
			`PRODUCT_BRAND := samsung`
			`PRODUCT_DEVICE := fascinatemtd`
			`PRODUCT_MODEL := SCH-I500`
			`PRODUCT_MANUFACTURER := samsung`
Update Galaxy S build fingerprints All of the supported Galaxy S devices besides the Vibrant have gingerbread builds using release-keys, so they should be used instead of the crespo keys as they are more suited for the device. Might also stop the random e-mail new users get from Google welcoming them to their "Nexus S." Change-Id: I8fec9999fb6dd1ba4aae79fd9c8ea1e898d40e09 2011-10-15 20:05:47 +00:00			`PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SCH-I500 BUILD_ID=GINGERBREAD BUILD_FINGERPRINT=uscc/SCH-I500/SCH-I500:2.3.4/GINGERBREAD/EH09:user/release-keys PRIVATE_BUILD_DESC="SCH-I500-user 2.3.4 GINGERBREAD EH09 release-keys"`
add fascinatemtd target 2011-07-14 22:28:14 +00:00
			`# Extra fascinatemtd overlay`
			`PRODUCT_PACKAGE_OVERLAYS += vendor/cyanogen/overlay/fascinatemtd`

build Torch for Fascinate, Mesmerize, and Showcase devices 2011-09-12 20:33:19 +00:00			`# Add the Torch app`
			`PRODUCT_PACKAGES += Torch`

vendor: Externalize common version and release names We have been using a system where each vendor makefile needed to be updated for each release. This leads to both redundancy and inconsistency across devices. This patch externalizes version code to the common_versions.mk. As we all know CyanogenMod versioning works as such: MAJOR.MINOR.MAINTENACE.DEVICE_SPECIFIC (i.e. 7.1.0.1) common_versions.mk now contains the first three in the form of the following variables: PRODUCT_VERSION_MAJOR, PRODUCT_VERSION_MINOR, PRODUCT_VERSION_MAINTENANCE. Additionally, each device makefile contains two additional flags which control both the release name (the name that appears in the generated zip) and the device-specific version (empty by default, to be bumped on a per device basis), example: PRODUCT_RELEASE_NAME := XperiaArc-LT15i PRODUCT_VERSION_DEVICE_SPECIFIC := .1 Change-Id: I15d18e27b89ea00109a61cb66e3bffbb061a2ed4 2011-10-13 16:39:00 +00:00			`# Release name and versioning`
			`PRODUCT_RELEASE_NAME := Fascinate`
			`PRODUCT_VERSION_DEVICE_SPECIFIC :=`
			`-include vendor/cyanogen/products/common_versions.mk`
add fascinatemtd target 2011-07-14 22:28:14 +00:00
			`#`
			`# Copy galaxys specific prebuilt files`
			`#`
			`PRODUCT_COPY_FILES += \`
			`vendor/cyanogen/prebuilt/hdpi/media/bootanimation.zip:system/media/bootanimation.zip`