手机需要root过，不然没有权限拷贝apk到 /system/app 目录下面。

【步骤】

通过手机的【设置】--【关于手机】 查看当前系统的Android版本，例如我的手机是4.2.2。
在 http://wiki.rootzwiki.com/Google_Apps 中下载对应的服务包。

里面包含了很多的服务(system\app)app，我们只需要安装服务框架，登录服务，日历同步，通讯录同步，邮件同步即可。

拷贝到 \system\app 系统目录中。

【账户同步】

手机安装账户同步服务，首发于润物无声。

安装顺序

• 下载 GoogleMobileService(GMS)谷歌移动服务(2.3.4).zip，这是Android版本2.3的GMS服务包，里面包括了基本的google服务APP，不过我们不用那么多，只需要GoogleContactsSyncAdapter.apk, GoogleCalendarSyncAdapter.apk 和 Gmail.apk 就够了。
• 将解压后得到的3个APK放到系统目录/system/app中，然后重启手机进行自动安装
• 配置账户同步，勾选账户，日历和邮件同步的选项，稍等一会儿，所有的通讯录，日历和邮件就都同步ok了
  
  
• 这样的话，基本所有的google服务就都具备了，以后涉及到google其他的APP都木有问题了
• 如果还想安装其他的google app，方法同上，有的只能安装到系统目录中，即/system/app下，有的可以按照普通的方法进行安装，视具体情况而定

三星 S5830i 安装谷歌同步服务，首发于润物无声。

安装顺序

• 下载 google 服务包，里面包括 GoogleServicesFramework.apk 和 Vending.apk，注意我的三星手机目前的android版本是2.3.6，所以该谷歌服务适用于2.3，其他的版本我还没有测试过，不过装了也不会出现什么副作用，可以试试，点我下载。
• 将上面已经下载的两个APK放置到 /system/app 目录中，然后关机重启进行自动安装，安装以后提示google market应用升级，然后自动升级到google play store，截图如下
  
  
  
• 接下来打开play store应用绑定Google账户，填写正确的google账户信息，绑定完了就ok了，截图如下：
  
  
  
• 欧了，现在就可以利用play store进行apk安装和升级了，随心所欲的利用google服务

三星 S5830i 安装谷歌市场 Google Market，首发于润物无声。

今天我就带领大家熟悉一下基于Google+ 开放API的程序设计，本程序基于SAE平台，采用PHP语言开发，基于Java语言和Python语言也都比较好开发，google官方都有开放的lib可以直接使用，不用自己再做底层封装了。

实现步骤

1. 访问 Google API Console 开启Google+ API权限.
   
2. 访问 Google API Console 生成  developer key, OAuth2 client id, OAuth2 client secret, 和 注册 OAuth2 redirect uri.
   
   
3. 下载 google api的php开发库，google-api-php-client.
4. 更新google api开发库，因为我的运行环境基于新浪云SAE平台，所以要做一些特别的改动：
   1. 实现SAE平台的MemCache，在google-api-php-clientsrccache中建立apiSAEMemcacheCache.php文件，具体内容如下

   <?php
   /**
    * SAE Memcache
    *
    * @author Carey Zhou <zhourunsheng2008@google.com>
    */
   class apiSAEMemcacheCache extends apiCache {
     private $connection = false;
   
     public function __construct() {
   	//do nothing
     }
   
     private function connect() {
       if (! $this->connection = @memcache_init()) {
         throw new apiCacheException("Memcache init failed");
       }
     }
   
     private function check() {
       if (! $this->connection) {
         $this->connect();
       }
     }
   
     /**
      * @inheritDoc
      */
     public function get($key, $expiration = false) {
       $this->check();
       if (($ret = @memcache_get($this->connection, $key)) === false) {
         return false;
       }
       if (! $expiration || (time() - $ret['time'] > $expiration)) {
         $this->delete($key);
         return false;
       }
       return $ret['data'];
     }
   
     /**
      * @inheritDoc
      */
     public function set($key, $value) {
       $this->check();
       // we store it with the cache_time default expiration so objects will at least get cleaned eventually.
       if (@memcache_set($this->connection, $key, array('time' => time(),
           'data' => $value), false) == false) {
         throw new apiCacheException("Couldn't store data in cache");
       }
     }
   
     /**
      * @inheritDoc
      */
     public function delete($key) {
       $this->check();
       @memcache_delete($this->connection, $key);
     }
   }

   2. 更新 google-api-php-clientsrccacheapiCache.php文件，将我们新添加的SAEMemcache加进去，代码如下：

   require_once "apiSAEMemcacheCache.php";

   3. 更新 google-api-php-clientsrcioapiCurlIO.php文件，修正一个bug【当Header中出现"HTTP/1.1 100 Continue"的时候，原程序会出现解析错误，导致程序崩溃，估计也是SAE环境的特殊性导致的】，具体改正如下：

   原来的代码：

   // Parse out the raw response into usable bits
       list($rawResponseHeaders, $responseBody) = explode("rnrn", $data, 2);

   现在的代码：

   // Parse out the raw response into usable bits
       list($rawResponseHeaders, $responseBody) = explode("rnrn", $data, 2);
       if ($rawResponseHeaders == "HTTP/1.1 100 Continue") {
   	list($rawResponseHeaders, $responseBody) = explode("rnrn", $responseBody, 2);
       }

   更改原因：如果出现了"HTTP/1.1 100 Continue"的时候，还要继续向下解析一次，即出现了特殊的“双Header现象”，否则的话就会导致Header解析出错，真正的Header没有被解析出来，也混到body里面去了。

5. google plus 代码编写，获取用户公开的Activity信息流，核心代码如下：

   <?php
   /*
    * Google Plus
    *
    * @author Carey Zhou(zhourunsheng2008@gmail.com)
    */
   require_once '../libs/google-api-php-client/src/apiClient.php';
   require_once '../libs/google-api-php-client/src/contrib/apiPlusService.php';
   
   //sae_set_display_errors(true);
   
   session_start();
   
   $client = new apiClient();
   $client->setApplicationName("Google Plus Application");
   
   $client->setClientId('800611776987-kp6h5nfv5l9gp5v2qipqhc5l8dkqe0lu.apps.googleusercontent.com');
   $client->setClientSecret('5o-eK5M4iftPxB7_fhNqEAhm');
   $client->setRedirectUri('https://carey.sinaapp.com/googleplus/index.php');
   $client->setDeveloperKey('AIzaSyD6FERuKcWPn2xGUcgFmKW9Ush50nu6PYQ');
   
   $client->setScopes(array('https://www.googleapis.com/auth/plus.me'));
   $plus = new apiPlusService($client);
   
   if (isset($_REQUEST['logout'])) {
     unset($_SESSION['access_token']);
   }
   
   if (isset($_GET['code'])) {
     $client->authenticate();
     $_SESSION['access_token'] = $client->getAccessToken();
     //header('Location: http://' . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF']);
     $url = 'http://' . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF'];
     echo "<script language='javascript' type='text/javascript'>";
     echo "window.location.href='$url'";
     echo "</script>";
   }
   
   if (isset($_SESSION['access_token'])) {
     $client->setAccessToken($_SESSION['access_token']);
   }
   
   if ($client->getAccessToken()) {
     $me = $plus->people->get('me');
   
     $optParams = array('maxResults' => 100);
     $activities = $plus->activities->listActivities('me', 'public', $optParams);
   
     // The access token may have been updated lazily.
     $_SESSION['access_token'] = $client->getAccessToken();
   } else {
     $authUrl = $client->createAuthUrl();
   }
   ?>

   可以注意到，在程序中我们配置了ClientID，ClientSecret，RedirectUri，DeveloperKey和Google+的scope，然后通过OAuth2机制获取用户的授权，进而来获得用户公开的Activity信息流。

程序部署和验证

1. 把上面的代码部署到SAE平台，https://carey.sinaapp.com/googleplus/index.php
   
2. 点击Connet Me进行OAuth2用户授权
   
3. 点击Allow Access允许访问，则会回到刚才的页面，把用户的信息流抓取出来
   

小结

到此为止，google plus 基于PHP开发的基本流程就都OK了，希望google过几天能开放出更多的API来，毕竟google+是个圈，所以圈子的API才是最核心的，O(∩_∩)O哈哈~,期待中

源码下载google_plus_sae_source

Google Plus API 之 程序设计，首发于润物无声。

1) Lattitude API

2) Earth API

3) Google Map API

4) GeoCoding API

5) Google Direction API

6) Static API

7) Places API

8 ) Buzz API

9)Friend Connect API

10) Social Graph API

11) Wave API

12) YouTube API’s

13) ADwords API

14) Adsense API

15) Blogger Data API

16) Webmaster Tools API

17) Code Search API

18) Picasa Web Album  DATA API

19) Management API

20) Font API

21) URL Shortner API

Google API，首发于润物无声。

本文就简单介绍一下手机应用程序和桌面应用程序的ClientLogin的基本流程和方法。

The ClientLogin authorization process（验证过程）

Authorization with ClientLogin involves a sequence of interactions between three entities: the installed application, Google services, and the user.

This diagram illustrates the sequence:

图片中的验证流程说明如下：

1. When the third-party application needs to access a user's Google service, it retrieves the user's login name and password.

2. The third-party application then makes a ClientLogin call to Google's Authorization service.

3. If the Google Authorization service decides additional vetting is necessary, it returns failure response with a CAPTCHA token and challenge, in the form of a URL for a CAPTCHA image.

4. If a CAPTCHA challenge is received, the third-party application displays the CAPTCHA image for the user and solicits an answer from the user.

5. If requested, the user submits an answer to the CAPTCHA challenge.

6. The third-party application makes a new ClientLogin call, this time including the CAPTCHA answer and token (received with the failure response).

7. On a successful login attempt (with or without CAPTCHA challenge), the Google Authorization service returns a token to the application.

8. The application contacts the Google service with a request for data access, referencing the token received from the Google Authorization service.

9. If the Google service recognizes the token, it supplies the requested data access.

The ClientLogin interface（ClientLogin验证接口）

 1. ClientLogin

ClientLogin can be used with any application that can make an HTTPS POST request. The POST request should be structured as a form post with the default encoding application/x-www-form-urlencoded. Parameters should be included in the body of the post.

Action URL parameter: https://www.google.com/accounts/ClientLogin

Sample request（请求示例）

The first example illustrates a basic login request.

The second example shows a request containing a response to a CAPTCHA challenge. Both examples are shown not URL-encoded for clarity.

POST /accounts/ClientLogin HTTP/1.0

Content-type: application/x-www-form-urlencoded
accountType=HOSTED_OR_GOOGLE&Email=zhourunsheng2008@gmail.com&Passwd=12345678&service=ah&source=Carey-CareyDiary-1.0

~~~~~~~~~~~~~~

POST /accounts/ClientLogin HTTP/1.0

Content-type: application/x-www-form-urlencoded
accountType=HOSTED_OR_GOOGLE&Email=zhourunsheng2008@gmail.com&Passwd=12345678&service=ah&

source=Carey-CareyDiary-1.0&logintoken=DQAAAGgA...dkI1LK9&logincaptcha=abcdefg

2. ClientLogin response

In response to a login request, Google returns either an HTTP 200, if login succeeded, or an HTTP 403, if login failed.

A success response contains the authorization token, labeled "Auth", in the body of the response. Your application must reference this token in each request to the Google service for this user. Additional cookies, labeled "SID" and "LSID", are not currently active and should not be used.

A failure response contains an error code and a URL to an error page that can be displayed to the user. If the error code is a CAPTCHA challenge, the response also includes a URL to a CAPTCHA image and a special token. Your application should be able to solicit an answer from the user and then retry the login request. To display the CAPTCHA image to the user, prefix the CaptchaUrl value with "http://www.google.com/accounts/", for example: " http://www.google.com/accounts/Captcha?ctoken=HiteT4b0Bk5Xg18_AcVoP6-yFkHPibe7O9EqxeiI7lUSN".

Sample responses（回复示例）

HTTP/1.0 200 OK

Server: GFE/1.3

Content-Type: text/plain

SID=DQAAAGgA...7Zg8CTN

LSID=DQAAAGsA...lk8BBbG

Auth=DQAAAGgA...dk3fA5N

在我们的程序中，目前主要利用Auth来作为后续访问服务的token，其他两项没有作用

~~~~~~~~~

HTTP/1.0 403 Access Forbidden

Server: GFE/1.3

Content-Type: text/plain

Url=http://www.google.com/login/captcha

Error=CaptchaRequired

CaptchaToken=DQAAAGgA...dkI1LK9

CaptchaUrl=Captcha?ctoken=HiteT4b0Bk5Xg18_AcVoP6-yFkHPibe7O9EqxeiI7lUSN

Error codes（错误代码）

详细文档： Google AuthForInstalledApps

Google ClientLogin for Installed Applications，首发于润物无声。

本文编写了一个简单的shell脚本文件，可方便程序开发人员快速的获取到Auth Token来调试程序。

 本示例程序获取的Googel服务为ah，即Google App Engine，如果需要获取其他服务的token，只要修改脚本中的 service=ah 为自己的服务即可。

Google 常用服务和Service Name 对照表

 Google Service 评测请参照 Google Account Service Names（Google工程师Tony Ruscoe）

脚本代码如下（get_auth_token.sh）：

#!/bin/sh

# Get user email
read -p "Email: " EMAIL

# Get user password
stty -echo
read -p "Password: " PASSWORD; echo >&2
stty echo

# check and download cacert file
CACERTFILE="/tmp/cacert.pem"
if [ ! -f "$CACERTFILE" ]; then
  wget http://curl.haxx.se/ca/cacert.pem -O $CACERTFILE
else
  echo "cacert exist!!!"
fi

# Get a user auth token
echo Getting token from https://www.google.com/accounts/ClientLogin ... >&2
AUTH=$(CURL_CA_BUNDLE=$CACERTFILE 
	curl -S --location 

https://www.google.com/accounts/ClientLogin

	-d Email=$EMAIL 
	-d Passwd=$PASSWORD 
	-d accountType=HOSTED_OR_GOOGLE 
	-d source=carey 
	-d service=ah 
	--header 'Content-Type:application/x-www-form-urlencoded' 
	2>/dev/null 
	| awk -F= '$1 ~ /Auth/ {print $2}')

if [ -z "${AUTH}" ]; then
  echo "Auth error" >&2
  exit
else
  echo "Auth="$AUTH
fi

程序使用如下：

$ ./get_auth_token.sh

Email:            输入自己的Google帐号

Password:    输入自己的Google密码

Auth=DQAAALIAAABNfSYKsytsIx_vzFOG_iHVO4Zv8su6hyn-5cTCtObnLTd1X8K0TDoNC5zdRZTg2NQtn6S47Jw1t3ZfE2J

qDhR_x4KezoWYufUloCVA_pkC3g1vAcy6KIGcqiSH2hecJa5UH9yuURyF7_ODS6ysjYZ0JC9WnuF3vsx_9mO4xFGOGtyw

xMYfGC-j801I1Pna0AJ48T-lCeU1yEiTyUUsLPVszWrvg5ae4BPOtTaZxD_lU4lJhYAXtvLNN1ZGdLJ_huI

最后可以利用获取到的Auth Token来访问google的服务了。

脚本方式获取Google ClientLogin Auth Token，首发于润物无声。