From 3ef22af233f2b9c99516dd1b7eed6cd3ff3e80fe Mon Sep 17 00:00:00 2001
From: Clay Murphy As described in Section 3.2.2 of the Android 2.1 Compatibility Definition,
+ As described in Section 3.2.2 of the Android 2.1 Compatibility Definition,
only certain strings are allowable for the system property
2.1-update1 As described in Section 3.2.2 of the Android 2.2 Compatibility Definition,
+ As described in Section 3.2.2 of the Android 2.2 Compatibility Definition,
only certain strings are allowable for the system property
2.2.1 As described in Section 3.2.2 of the Android 2.3 Compatibility Definition,
+ As described in Section 3.2.2 of the Android 2.3 Compatibility Definition,
only certain strings are allowable for the system property
As described in Section 3.2.2 of the Android 4.0 Compatibility Definition,
+ As described in Section 3.2.2 of the Android 4.0 Compatibility Definition,
only certain strings are allowable for the system property
As described in Section 3.2.2 of the Android 4.1 Compatibility Definition,
+ As described in Section 3.2.2 of the Android 4.1 Compatibility Definition,
only certain strings are allowable for the system property
4.1.1 As described in Section 3.2.2 of the Android 4.2 Compatibility Definition,
+ As described in Section 3.2.2 of the Android 4.2 Compatibility Definition,
only certain strings are allowable for the system property
If you want to build a device compatible with a given Android version,
start by checking out the source code for that version, and then read the
corresponding CDD and stay within its guidelines. For additional details,
-simply examine the latest CDD.android.os.Build.VERSION.RELEASE
. The reason for this is that
applications and web sites may rely on predictable values for this string, and
@@ -19,4 +19,4 @@ allowable by an Android 2.1-based system. The only permitted values for
android.os.Build.VERSION.RELEASE
. The reason for this is that
applications and web sites may rely on predictable values for this string, and
@@ -19,4 +19,4 @@ allowable by an Android 2.2-based system. The only permitted values for
android.os.Build.VERSION.RELEASE
. The reason for this is that
applications and web sites may rely on predictable values for this string, and
@@ -14,4 +14,4 @@ allowable by an Android 2.3-based system. The only permitted values for
android.os.Build.VERSION.RELEASE
for Android 2.3 are:
\ No newline at end of file
+
diff --git a/src/compatibility/4.0/versions.jd b/src/compatibility/4.0/versions.jd
index 12039ba9..a3283c5d 100644
--- a/src/compatibility/4.0/versions.jd
+++ b/src/compatibility/4.0/versions.jd
@@ -1,7 +1,7 @@
page.title=Permitted Version Strings for Android 4.0
@jd:body
-android.os.Build.VERSION.RELEASE
. The reason for this is that
applications and web sites may rely on predictable values for this string, and
diff --git a/src/compatibility/4.1/versions.jd b/src/compatibility/4.1/versions.jd
index 9a3106c7..e3439e9e 100644
--- a/src/compatibility/4.1/versions.jd
+++ b/src/compatibility/4.1/versions.jd
@@ -1,7 +1,7 @@
page.title=Permitted Version Strings for Android 4.1
@jd:body
-android.os.Build.VERSION.RELEASE
. The reason for this is that
applications and web sites may rely on predictable values for this string, and
@@ -19,4 +19,4 @@ allowable by an Android 4.1-based system. The only permitted values for
android.os.Build.VERSION.RELEASE
. The reason for this is that
applications and web sites may rely on predictable values for this string, and
diff --git a/src/compatibility/overview.jd b/src/compatibility/overview.jd
index 184903a8..befc9461 100644
--- a/src/compatibility/overview.jd
+++ b/src/compatibility/overview.jd
@@ -99,7 +99,7 @@ result is a compatible system.
The CTS is a free, commercial-grade test suite, available for
download.
diff --git a/src/devices/audio.jd b/src/devices/audio.jd
index 657ec09f..08ed9ff4 100644
--- a/src/devices/audio.jd
+++ b/src/devices/audio.jd
@@ -291,7 +291,7 @@ see the implementation for the Nexus 10 in Warning: For the The following example enables pre-processing for the VoIP device/samsung/manta/audio_effe
VOICE_RECOGNITION
use case, do not enable
the noise suppression pre-processing effect. It should not be turned on by default when recording from this audio source,
and you should not enable it in your own audio_effects.conf file. Turning on the effect by default will cause the device to fail
-the compatibility requirement
+the compatibility requirement
regardless of whether is was on by default due to configuration file, or the audio HAL implementation's default behavior.AudioSource
and Camcorder AudioSource
.
--
cgit v1.2.3