代码名称匹配下面的版本号,以及withAPI水平和了解android原生开发工具包提供了方便:释放
| Code name | Version | API level |
|---|---|---|
| (no code name) | 1.0 | API level 1 |
| (no code name) | 1.1 | API level 2 |
| Cupcake | 1.5 | API level 3, NDK 1 |
| Donut | 1.6 | API level 4, NDK 2 |
| Eclair | 2.0 | API level 5 |
| Eclair | 2.0.1 | API level 6 |
| Eclair | 2.1 | API level 7, NDK 3 |
| Froyo | 2.2.x | API level 8, NDK 4 |
| Gingerbread | 2.3 - 2.3.2 | API level 9, NDK 5 |
| Gingerbread | 2.3.3 - 2.3.7 | API level 10 |
| Honeycomb | 3.0 | API level 11 |
| Honeycomb | 3.1 | API level 12, NDK 6 |
| Honeycomb | 3.2.x | API level 13 |
| Ice Cream Sandwich | 4.0.1 - 4.0.2 | API level 14, NDK 7 |
| Ice Cream Sandwich | 4.0.3 - 4.0.4 | API level 15, NDK 8 |
| Jelly Bean | 4.1.x | API level 16 |
| Jelly Bean | 4.2.x | API level 17 |
| Jelly Bean | 4.3 | API level 18 |
第一个字母的代号是释放家庭,如F isFroyo。
第二个字母是一个分支的代码,允许谷歌identifythe确切的代码构建和R是byconvention的初级版本分支的分支。
下一个字母,两个数字是日期代码。的的信countsquarters,A为2009年第一季度。因此,F是2010年第二季度。的twodigits数天本季度内,因此F85是2010年6月24日。
最后,最后一个字母标识个别版本与向同一日期代码,开始依次用A; A是actuallyimplicit,通常为简洁起见省略。
日期码不保证是一个buildwas的确切日期,这是常见的轻微变化的existingbuild重新使用相同的日期代码添加到现有的建立。
源代码标签,并建立
从甜甜圈,标签和构建的确切名单是在如下表:
| Build | Tag | Notes |
|---|---|---|
| DRC83 | android-1.6_r1.1 | earliest Donut version, ADP1, ADP2 |
| DRC92 | android-1.6_r1.2 | |
| DRD08 | android-1.6_r1.3 | |
| DRD20 | android-1.6_r1.4 | |
| DMD64 | android-1.6_r1.5 | latest Donut version |
| ESD20 | android-2.0_r1 | earliest Eclair version |
| ESD56 | android-2.0.1_r1 | |
| ERD79 | android-2.1_r1 | Nexus One |
| ERE27 | android-2.1_r2 | Nexus One |
| EPE54B | android-2.1_r2.1p | Nexus One |
| ESE81 | android-2.1_r2.1s | |
| EPF21B | android-2.1_r2.1p2 | latest Eclair version |
| FRF85B | android-2.2_r1 | earliest Froyo version, Nexus One |
| FRF91 | android-2.2_r1.1 | Nexus One |
| FRG01B | android-2.2_r1.2 | |
| FRG22D | android-2.2_r1.3 | |
| FRG83 | android-2.2.1_r1 | Nexus One |
| FRG83D | android-2.2.1_r2 | Nexus One |
| FRG83G | android-2.2.2_r1 | Nexus One |
| FRK76 | android-2.2.3_r1 | |
| FRK76C | android-2.2.3_r2 | latest Froyo version |
| GRH55 | android-2.3_r1 | earliest Gingerbread version, Nexus S |
| GRH78 | android-2.3.1_r1 | Nexus S |
| GRH78C | android-2.3.2_r1 | Nexus S |
| GRI40 | android-2.3.3_r1 | Nexus One, Nexus S |
| GRI54 | android-2.3.3_r1.1 | Nexus S |
| GRJ06D | android-2.3.4_r0.9 | Nexus S 4G |
| GRJ22 | android-2.3.4_r1 | Nexus One, Nexus S, Nexus S 4G |
| GRJ90 | android-2.3.5_r1 | Nexus S 4G |
| GRK39C | android-2.3.6_r0.9 | Nexus S |
| GRK39F | android-2.3.6_r1 | Nexus One, Nexus S |
| GWK74 | android-2.3.7_r1 | latest Gingerbread version, Nexus S 4G |
| ITL41D | android-4.0.1_r1 | earliest Ice Cream Sandwich version, Galaxy Nexus |
| ITL41D | android-4.0.1_r1.1 | Galaxy Nexus |
| ITL41F | android-4.0.1_r1.2 | Galaxy Nexus |
| ICL53F | android-4.0.2_r1 | Galaxy Nexus |
| IML74K | android-4.0.3_r1 | Nexus S |
| IML77 | android-4.0.3_r1.1 | |
| IMM76 | android-4.0.4_r1 | |
| IMM76D | android-4.0.4_r1.1 | Nexus S, Nexus S 4G, Galaxy Nexus |
| IMM76I | android-4.0.4_r1.2 | Galaxy Nexus |
| IMM76K | android-4.0.4_r2 | Galaxy Nexus |
| IMM76L | android-4.0.4_r2.1 | latest Ice Cream Sandwich version |
| JRO03C | android-4.1.1_r1 | earliest Jelly Bean version, Galaxy Nexus |
| JRO03D | android-4.1.1_r1.1 | Nexus 7 |
| JRO03E | android-4.1.1_r2 | Nexus S |
| JRO03H | android-4.1.1_r3 | |
| JRO03L | android-4.1.1_r4 | Nexus S |
| JRO03O | android-4.1.1_r5 | Galaxy Nexus |
| JRO03R | android-4.1.1_r6 | Nexus S 4G |
| JRO03S | android-4.1.1_r6.1 | Nexus 7 |
| JZO54K | android-4.1.2_r1 | Nexus S, Galaxy Nexus, Nexus 7 |
| JZO54L | android-4.1.2_r2 | |
| JZO54M | android-4.1.2_r2.1 | |
| JOP40C | android-4.2_r1 | Galaxy Nexus, Nexus 7, Nexus 4, Nexus 10 |
| JOP40D | android-4.2.1_r1 | Galaxy Nexus, Nexus 7, Nexus 4, Nexus 10 |
| JOP40F | android-4.2.1_r1.1 | Nexus 10 |
| JOP40G | android-4.2.1_r1.2 | Nexus 4 |
| JDQ39 | android-4.2.2_r1 | Galaxy Nexus, Nexus 7, Nexus 4, Nexus 10 |
| JDQ39B | android-4.2.2_r1.1 | Nexus 7 |
| JDQ39E | android-4.2.2_r1.1 | Nexus 4 |
| JWR66L | android-4.3_r0.9 | Nexus 7 |
| JWR66N | android-4.3_r0.9.1 | Galaxy Nexus, Nexus 7 (grouper/tilapia/flo), Nexus 4, Nexus 10 |
| JWR66V | android-4.3_r1 | Galaxy Nexus, Nexus 7 (grouper/tilapia), Nexus 4, Nexus 10 |
| JWR66Y | android-4.3_r1.1 | Galaxy Nexus, Nexus 7 (grouper/tilapia), Nexus 4, Nexus 10 |
| JSR78D | android-4.3_r2 | Nexus 7 (deb) |
| JSS15J | android-4.3_r2.1 | Jelly Bean version, Nexus 7 (flo/deb) |
| JSS15Q | android-4.3_r2.2 | Latest Jelly Bean version, Nexus 7 (flo/deb) |
| JLS36C | android-4.3_r3 | Latest Jelly Bean version, Nexus 7 (deb) |
枝升级Froyo,姜饼,ICS-MR0,ICS-MR1,JB-dev的,JB-MR1-dev的,与JB-mr1.1-dev,JB-的MR2 devrepresent developmentbranches不完全匹配的配置testedby谷歌。除了tothe官方标记的版本,他们可能包含多种变化,那些没有被thoroughlytested。
蜂窝GPL模块
对于蜂窝,整个平台的源代码是不是,零件available.However蜂窝授权下GPL和LGPLare的提供在以下标签:
| Build | Tag | Notes |
|---|---|---|
| HRI39 | android-3.0_r1 | earliest Honeycomb version |
| HRI66 | android-3.0_r1.1 | |
| HWI69 | android-3.0_r1.2 | |
| HRI83 | android-3.0_r1.3 | |
| HMJ37 | android-3.1_r1 | |
| HTJ85B | android-3.2_r1 | |
| HTK55D | android-3.2.1_r1 | |
| HTK75D | android-3.2.1_r2 | |
| HLK75C | android-3.2.2_r1 | |
| HLK75D | android-3.2.2_r2 | |
| HLK75F | android-3.2.4_r1 | |
| HLK75H | android-3.2.6_r1 | latest Honeycomb version |
有没有清单包含完全相同的。然而,时,有清单,允许建立这些组件。可以做下列命令的工作3.0_r1.1,使用其他版本的git检出paramater byswitching,如有必要,-m参数inrepo初始化。 git的checkout命令输出错误的非GPLprojects的,它不能找到问题的标签。
$ repo init -b master -m base-for-3.0-gpl.xml
$ repo sync
$ repo forall -c git checkout android-3.0_r1.1
本文详细列举了Android系统的各个版本及其对应的API级别、构建标签和版本代号,包括从最初的1.0版本到JellyBean 4.3版本的所有细节。这对于理解不同Android设备上运行的操作系统版本和其开发周期非常有用。
3350

被折叠的 条评论
为什么被折叠?



