Google在與業(yè)界伙伴簽署有關(guān)于 Android 平臺(tái)的授權(quán)協(xié)議時(shí)，是抱持著公平的態(tài)度嗎？筆者想聽聽來自智能手機(jī)業(yè)者與平板業(yè)者們的看法。 根據(jù)一份外流的Google與 HTC 在2011年簽署之協(xié)議，引發(fā)了Google掌控手機(jī)業(yè)者程度的疑慮；該“Google移動(dòng)應(yīng)用程序散布協(xié)議(Google Mobile Application Distribution Agreement)”，禁止制造商變更 Android 以及強(qiáng)制規(guī)定關(guān)鍵Google應(yīng)用程序在手機(jī)上的呈現(xiàn)方式。 該協(xié)議內(nèi)容并非在先前甲骨文(Oracle)與Google的專利侵權(quán)訴訟中曾經(jīng)被公開的部分，具體來說，在文件的第3.4項(xiàng)中提到： “除非額外取得Google的書面同意：1. 公司應(yīng)在每臺(tái)設(shè)備預(yù)載經(jīng)批準(zhǔn)適用于特定區(qū)域或國家的所有Google應(yīng)用程序；2. Google的手機(jī)頂端搜索引擎(Phone-top Search)，以及Android市集客戶端應(yīng)用程序圖標(biāo)，必須立即放置在與默認(rèn)手機(jī)屏幕首頁相鄰的控制面板(panel)上?！? “3. 所有的Google應(yīng)用程序應(yīng)被放置在手機(jī)頂端之下不超過一個(gè)階層的位置?！币约啊?. Google手機(jī)頂端搜索引擎必須被設(shè)定為設(shè)備上之所有網(wǎng)絡(luò)搜尋接取點(diǎn)所預(yù)設(shè)的搜索引擎。盡管有上述規(guī)定，可選的Google應(yīng)用程序沒有安裝需求?！? 此外該文件的第2.2項(xiàng)則禁止對Android的變更： “公司不得或不允許任何一家第三方伙伴采取任何可能造成或?qū)е翧ndroid分裂的行動(dòng)，包括但不僅限于透過散布之來自Android或Android兼容設(shè)備的軟件開發(fā)工具(SDK)；以及公司不得協(xié)助或鼓勵(lì)任何第三方伙伴散布來自Android兼容設(shè)備的軟件開發(fā)工具(SDK)?！? 在文件的第4.2項(xiàng)，Google還要求廠商提供“具備預(yù)載版本預(yù)載Google應(yīng)用程序之設(shè)備分布總數(shù)量月報(bào)(依據(jù)Google應(yīng)用程序種類、每個(gè)區(qū)域市場銷售的當(dāng)?shù)貦C(jī)種)。” 另外Google還要求“每臺(tái)設(shè)備必須在設(shè)備最后嵌入日期(Final Embed Date of the Device)的至少三十天以前成為Android兼容設(shè)備；最后裝載于設(shè)備上的軟件，必須要在上市以前通過兼容性測試套件(Compatibility Test Suite)?！? 對筆者來說，以上規(guī)定感覺都太過嚴(yán)苛，讓人想起英特爾(Intel)與微軟(Microsoft)的“Wintel”聯(lián)盟獨(dú)大時(shí)期；在那個(gè)時(shí)候，微軟嘗試逼迫所有廠商要讓Internet Explorer成為PC產(chǎn)品的唯一且默認(rèn)網(wǎng)絡(luò)瀏覽器，而微軟與英特爾也提供給那些在產(chǎn)品中使用較少、甚至不使用其他競爭操作系統(tǒng)的廠商們營銷資金。 Wintel 兩巨頭的做法受到反壟斷調(diào)查，歐盟則正在調(diào)查Google對Android的授權(quán)策略；Android已經(jīng)成為目前的主流移動(dòng)設(shè)備操作系統(tǒng)，被視為是蘋果 (Apple) iOS操作系統(tǒng)之外另一個(gè)開放源碼替代方案。但以上的協(xié)議文件卻讓人質(zhì)疑，Google到底是如何經(jīng)營此軟件平臺(tái)？ 筆者已經(jīng)聯(lián)絡(luò)Google要求解釋，但我們也想聽聽來自智能手機(jī)/平板制造商的看法；Google是否在Android授權(quán)上采取公平態(tài)度？ 本文授權(quán)編譯自EE Times，版權(quán)所有，謝絕轉(zhuǎn)載 編譯：Judith Cheng 參考英文原文：Android Contract Raises Questions，by Rick Merritt

相關(guān)閱讀：
• 讓你驚艷的非智能手機(jī)Android設(shè)備
• Linux基金會(huì)創(chuàng)建AllSeen聯(lián)盟，推動(dòng)物聯(lián)網(wǎng)發(fā)展
• 蘋果發(fā)布車載iOS系統(tǒng)CarPlay，大牌車企紛紛捧場FMuesmc

{pagination} Android Contract Raises Questions Rick Merritt, SiliconValley Bureau Chief SAN JOSE, Calif. -- Is Google playing fair in its Android agreements? That's what I'd like to hear from the community of smartphone and tablet makers. A leaked copy of a 2011 Android agreement between Google and HTC raises questions about the amount of control Google exercises over OEM handsets. The Google Mobile Application Distribution Agreement forbids OEMs from making changes to Android and enforces exactly where key Google applications appear on a handset. The document appears to be part of the discovery not previously made public from the Oracle vs. Google patent infringement suit. It was leaked by Ben Edelman, an associate professor at the Harvard Business School. Specifically, section 3.4 of the document states: Unless otherwise approved by Google in writing: 1) Company will preload all Google Applications approved in the applicable Territory or Territories on each Device; (2) Google Phone-top Search and the Android Market Client Icon must be placed at least on the panel immediately adjacent to the Default Home Screen; (3) all other Google Applications will be placed no more than one level below the Phone Top; and (4) Google Phone-top Search must be set as the default search provider for all Web search access points on the Device. Notwithstanding the foregoing, there are no placement requirements for Optional Google Applications. Section 2.2 forbids making changes to Android: The Company shall not or allow any third party to take any actions that may cause or result in the fragmentation of Android including but not limited to the distribution by Company of a software development kit (SDK) derived from Android or derived from Android compatible devices and company shall not assist or encourage any third party to distribute a software development kit (SDK) derived from Android Compatible Devices. In section 4.2 Google requires OEMs provide "a written report of the total number of devices distributed with a preloaded version of a Google Application during such calendar month (by Google Application, Territory sand Device model within each Territory.)" In addition, Google requires "each Device must become an Android Compatible Device at least 30 days prior to the Final Embed Date of the Device. The final software build on Devices must pass the Compatibility Test Suite prior to Launch." These requirements seem overly restrictive to me. They remind me of the contracts Intel and Microsoft used in the heyday of the Wintel monopoly. Back then, Microsoft tried to force OEMs to make its Internet Explorer the default and only browser on PC desktops. Microsoft and Intel also created marketing funds that essentially paid OEMs if they used fewer or no competing operating systems or processors in their products. The Wintel giants came under antitrust scrutiny for their practices. The European Union is investigating Google's practices with Android now. Android has become by far the dominant operating system in mobile devices. It is described as an open-source alternative to Apple's iOS. But this document suggests there are some real questions to be answered about how Google is managing its software stack. I've reached out to Google for its response. I'd also like to hear from smartphone and tablet makers, too.