[Chinese] Adobe Flash Player 11可以下載安裝了

不知道我是不是Lag了，早上突然發現Adobe Flash Player 11在Android Market上可以下載更新了，真是佛心來的，感恩阿!
有圖有真相，看一下截圖吧。

要下載可以跳轉後面網址自Android Market上下載。 注意一下，它會過濾手機，所以不是所有手機都可以下載。
https://market.android.com/details?id=com.adobe.flashplayer
Have Fun!

[Chinese]Titanium Studio (Appcelerator)安裝Android ADT時有Error

安裝完Titanium Studio (Appcelerator)以後第一個步驟就是另外再安裝Android的ADT Plugin,大家應該想都不用想閉著眼睛都會做吧. 跟Eclipse裡面的步驟一模一樣,輸入Google ADT名稱,然後把下載網址https://dl-ssl.google.com/android/eclipse/輸入,收工完成!

蝦米,Hold住....發生錯誤,現在這是什麼情況ㄟ!

其實大家都忽略了一個前置步驟,要先把Eclipse內Java Programing Language的更新安裝補上. 注意一下,不是Eclipse上最新版的哦!!!

正確的更新是安裝使用Eclipse Helios的更新,輸入Eclipse Helios Update Site作為名稱,正確的下載網址是http://download.eclipse.org/releases/helios/,然後把Programing Language Support中Java部分的支援安裝起來. 借用一下Appcelerator上面的截圖(如下),然後按Next/Ok並且同意授權(License)條款,安裝成功後重新開啟Appcelerato,然後就可以順利安裝Android的ADT Plugin了. 完工收工!

原廠WiKi裡面其實有寫了說明,不過可能大家都忽略了上面筆者說的前置步驟,有興趣的讀者可以跳轉下面網址後閱讀全文. Code Strong!!

http://wiki.appcelerator.org/display/tis/Installing+the+ADT+Plugin#InstallingtheADTPlugin-InstalltheEclipseJavaDevelopmentToolsplugin

[Chinese]簡訊短消息加密

為什麼簡訊短消息需要加密,這是很多人會問的問題,透過行動網路peer-to-peer點對點傳遞(2G或3G)不是應該很安全嗎? 這個問題的答案當然是YES,不過前提當然還是對方不是警政國安單位透過LOI啦,空中攔截解碼也不是那麼容易的事.

那為什麼簡訊還需要加密呢? 這得從簡訊中心說起,一般的簡訊中心都是使用所謂store-and-forward的架構,既然是store,那會有儲存的需求,所以就會有使用database或是早期internal storage架構,那麼在這個點上,以技術上來說,如果操作的人有適當的權限或是任何人(當然一定是灰色地帶)有domain knowledge以及適當的工具,是有可能讀取到簡訊內容的.

如果您的簡訊內容是幾點開會/遲到啦/好不好啦/約吃飯...等等,應該是不需要大費周章的加密,但是如果您的簡訊內容有點小敏感,例如傳遞商務或業務上的機密訊息/報價或是.....嗯最近很夯的與小三曖昧等,那想要保有一點簡訊隱私的您可能就會想要把簡訊短消息加密了. 這時候,您可能就需要我們的程式了,基於這樣的需求考量,所以我們設計了這個Secure SMS程式軟體幫您把簡訊短消息加密以後傳送出去,那只有您的收件人又有正確的解密碼才能解密您的加密訊息.

想要下載這個程式,可以從Android Market上下載,網址是 https://market.android.com/details?id=com.ngnlive.plmn.securesms

介紹Secure SMS的文章,請參考這篇文章 http://ngnlive.blogspot.com/2011/05/chinesesecure-sms.html

如何使用Secure SMS,請參考這篇文章 http://ngnlive.blogspot.com/2011/05/chinesesecure-sms_06.html

Have fun!

Why should I encrypt content of my short message for sake of enhance privacy

People were asking why do you bother to encrypt content of your message. Shouldn't the mobile network (either 2G or 3G) be quite secure for transmitting my message over the air (OTA) in peer-to-peer communication?

Well, this is a good question. But, do you know most (if not all) of short message center (a.k.a. SMSC) of service provider operate in a kind of store-and-forward mechanism that means your message is kept in its database / internal store for handling. Technically speaking, for anyone with proper permission or someone with domain knowledge and equipped with proper tools they might be able to read your message without your awareness.

Therefore, this is the solely reason behind for the birth of "Secure SMS" application for Android. For those of you paranoid who ask for a higher level of privacy control and or for corporate who want to send one time password / sensitive information OTA to clients, Secure SMS is the right answer to your concern.

You can download it from Android Market at https://market.android.com/details?id=com.ngnlive.plmn.securesms

For a how-to guide of the application, you might want to read this article at http://ngnlive.blogspot.com/2011/05/englishhow-to-use-secure-sms.html too.

[English]How-to use Secure SMS

First of all, you have to define encrypt/decrypt key pair for people you want to exchange secure message on keys management page.
Assuming your mobile no. is 098zzzzzzz and you want to exchange secure message with a contact whose mobile is 0935xxxxxx
1. Click on the keys mgt. from menu page
2. Type in this person's mobile no. in Contact mobile file
3. Random type in a string used for encryption key for your outgoing message to this contact on "Encryption key" field
4. Type in the decrypt string given by this contact (refer explanations in next step) which will be used to decode message from him/her on the "Decrypt key" field

On your counterpart's phone (contact people with the mobile no. 0935xxxxxx mentioned in earlier steps), repeat the same procedures for keys exchange definition as below
As you can see, he/she define your mobile (098zzzzzzz) in his/her keys mgt. page where
a. Key value defined in this contact's "Encryption key" field is the same value as you entered in your "Decrypt key" field (refer above screen)
b. Key value defined in this contact's "Decrypt key" field is the same value as you entered in your "Encrypt key" field (refer above screen)

Don't forget to click on the "Add xxx" or "Update xxx" button to save the keys definition for later use after finished keys definition.
Once done, either one can send secure message to his/her counterpart using the "send" function on main screen.

Shortly after, the targeted recipient will get a notification on his/her phone's status bar
Slide down the notification page, you will see a message from Secure SMS.

He/she can click on the notification to view the decrypted encrypted message from sender immediately.
Note for message with incorrect decrypt key defined, you will only see original encrypted message instead as demonstrated in message ID 1.

1. assistant sending confidential or classified information to boss
2. lovers exchange messages and want to keep those messages confidential inside the two only
3. bank / portal send one time OTA password to clients enhance security
4. business partners exchange confidential information or price quote
... and lots more we believe your will have your own creative way of using it.

Well, that's basically all of what you need to get started. Have fun and hope you like our work.

Please don't hesitate to rate it as 5-star for our application in Android Market at https://market.android.com/details?id=com.ngnlive.plmn.securesms and "like" it on our Facebook fans' page at http://goo.gl/Dwm5S.

A big thanks to you in advance!

[English]What's Secure SMS

Secure SMS is a client-side encrypt/decrypt application which allows user who wants a bit of privacy on SMS communication to encrypt their message content before sending it out to people. Only targeted recipient who has the correct decrypt key would be able to decrypt the encrypted SMS and read the message.
Feature highlight of the application includes
1. peer-to-peer secure message communication by AES-128 encrypt/decrypt mechanism
2. remove of messages from device's default inbox for enhanced privacy control
3. separate keys for each individual contact or a default key for all (can be enabled on settings option)
4. password (PIN) required for accessing message view page (can be enabled on settings option)
5. password (PIN) required for accessing settings page (can be enabled on settings option)
6. password (PIN) required for accessing keys management page (can be enabled on settings option)
7. incoming secure message notification on status bar and one click to view
Screen shots of the application below

Decrypt of encrypted SMS (short message) on view page

You can purchase credits (Top Up points) via most popular PayPal service for use in the application.

You can download the application from Android Market at https://market.android.com/details?id=com.ngnlive.plmn.securesms
Please don't hesitate to rate it as 5-star for our application in Android Market at https://market.android.com/details?id=com.ngnlive.plmn.securesms and you can "like" it on our Facebook fans' page at http://goo.gl/Dwm5S.
For those of you who want to know more about AES-128, you can check it out from WIKIPEDIA web site at http://en.wikipedia.org/wiki/Advanced_Encryption_Standard

[Chinese]Android手機無法發送簡訊但是可以接收簡訊

最近實在跟Android手機犯沖，這幾天發現簡訊可以收但是送不出去，本來沒有特別注意一直以為只是傳遞延遲而已，今天又發生了，看簡訊狀態是Pending，想說晚上來查一下好了。

Android手機有個很陽春的工程模式，切換到撥電話的畫面輸入*#*#4636#*#*即可進入(如附圖)，然後點選手機資訊進入下一畫面捲動畫面到下方你會看到SMSC設定值，Bingo找到兇手了，原來人是依台ㄟ，SIM卡簡訊中心號碼不知道啥原因被改掉了。

打電話到最大業者客服中心詢問簡訊中心號碼，客服人員很和氣的告訴我五個號嗎請我擇一設定，但是似乎對於為何SIM卡上簡訊中心號碼不見的問題沒有興趣，個人覺得或許OP業者喪失了一個追查Root Cause的機會，筆者只是覺得身為最大業者似乎應該更積極一點防範於未然，或許更多客戶也同樣有這個問題，不是嗎? Anyway，把正確簡訊中心號碼輸入以後再按Update更新後退出工模即可正常收發簡訊了。

提供下面幾家業者的SMSC號碼，如果你也碰到類似的問題可以參考一下設定。

中華電信

+886932400821,+886932400841, +886932400851, +886932400881, +886932400882

台灣大

+886935074443, +886935874443

威寶

+886986442901

抱歉我不知道遠傳的，如果你知道請PM給筆者讓我補上去。

附註:筆者後來用Google大神搜尋了一下這個Topic發現好像Android手機蠻多碰到這樣的狀況，各家狂推Android手機的OP是不是應該正視一下這個問題找一下Root Cause也Push一下Google呢。

Android手機在internet的應用上固然是很好用，但是在原本通信領域內很多習以為常的設定似乎找不到對應的實作，這一些眉角似乎尚待加強。

[Chinese]聰明人做的不聰明的事

MOTO佛心來的在網路上放出Android 2.2 for Milestone給大家昇版，我也手癢的去給他按下去，結果只能用悔不當初來給他形容，真是慘事一樁，我想QC應該是原版未拆封的空白機去測試的吧。

不過，這件事倒不是我要說的正題，當然啦我也不夠聰明到可以稱為聰明人，雖然去昇版真的是有點給他傻。

其實我想談的是common sense，先說說昇版後的使用經驗吧。我是使用WiFi連線的(never idle, always connect)，我發現一段時間後每次要使用手機的時候一按電源鍵叫醒手機以後，手機就會「很貼心」的幫我sync email跟有的沒的，所以呢就會有一段時間手機不會動好像hang住一樣，一定要等到背景跑完才會回應user在panel上的動作(氣)，這個邏輯跟MS的PC倒是有點異曲同工之妙，各位是不是都有臨時NB/PC開機只是想要發個信或是開一個文件給大老闆看，但是登入以後發現你/妳的電腦卻是第一時間在跑Windows Update，所以也不理會你的按鍵一樣的邏輯呢?

有iphone的人可以注意一下，一段時間idle以後當你按Home鍵手機第一個動作是不是只是re-create WiFi連線然後你就可以操作手機了。那再回頭觀察一下你Android手機，你有注意到WiFi連線要什麼時候才會恢復嗎?

我想到底是應該從使用者的實際使用情境去考量實作還是純粹以工程師零與壹邏輯去思考，聰明如你/妳，應該是自有定論吧。

[Chinese][Android]sqlite exception: database not open

手冊跟範例都不會告訴你的事,大家的API Demo都很美妙.

但是如果你和我ㄧ樣一直碰到這個exception,但是程式又沒錯,有興趣看英文的,可以先跳轉看這篇文章. 原文在此 http://www.outofwhatbox.com/blog/2010/12/android-closing-those-database-objects/

原PO作者是建議在onDestroy的時候別忘了呼叫DbHelper的onClose (範例如下)

public void onDestroy() {

super.onDestroy();

// Replace mDbHelper as needed with your database connection, or

// whatever wraps your database connection. (See below.)

mDbHelper.close();

}

其實這個exception的原因都差不多,重點就是可以把DbHelper的open跟close放在真正做sql command的地方,基本上就不會看到IllegalStateException了.