A patch for sound driver

Brilliant Service, who ported Android to Armadillo-500, released a patch of sound driver.
o Enabling audio on Android (Japanese)
o android-sound-patch.tar.gz

I have applied this patch to Angstrom kernel source. It works beautifully on Zaurus, too. Because Android uses /dev/eac as sound device, make a symbolic link;

$ ln -s /dev/dsp /dev/eac

If your Android is booted up by chroot, remeber to make symlink in android-root/dev, too.

Brilliant Service mentioned that this patch was originally written by Atmark Techno who is the developer of Armdallio. Big thanks to Atmark Techno.

Cheers,

Keycode Checker for Andorid

I found myself a bit of spare time last week, so I wrote a tiny utility to check the keycode and scancode on Android.

o KeycodeChecker.zip

As usual, copy the KeycodeChecker.apk in bin folder to data/app in android-root.

After launching KeycodeChecker, every time you type some key in, it show;
- key: keycode which Android uses internally.
- scan: scancode which is passed to Android from hardware driver.
- modify: true or false whether the key is modifier key or not.
- name: key name which is defined in android.view.KeyEvent as static final.

If you type [space key], [enter key] or [backspace key], the list will be refreshed.

Cheers,

telephony.db

Something interesting I found a few days ago.

$ ./emulator &
$ ./adb shell
# cd /data/data/com.google.android.providers.telephony/databases
# sqlite3 telephony.db
sqlite> .schema
CREATE TABLE android_metadata (locale TEXT);
CREATE TABLE carriers(_id INTEGER PRIMARY KEY,name TEXT,numeric TEXT,
mcc TEXT,mnc TEXT,apn TEXT,user TEXT,server TEXT,password TEXT,
proxy TEXT,port TEXT,mmsproxy TEXT,mmsport TEXT,
mmsc TEXT,current INTEGER);

sqlite> .dump carriers
BEGIN TRANSACTION;
CREATE TABLE carriers(_id INTEGER PRIMARY KEY,name TEXT,numeric TEXT,
mcc TEXT,mnc TEXT,apn TEXT,user TEXT,server TEXT,password TEXT,
proxy TEXT,port TEXT,mmsproxy TEXT,mmsport TEXT,
mmsc TEXT,current INTEGER);

INSERT INTO "carriers" VALUES(1,'T-Mobile US','310260',
'310','260','wap.voicestream.com','none','*','none',
'216.155.165.50','8080',NULL,NULL,
'http://216.155.174.84/servlets/mms’,NULL);
 :
 :
 :
INSERT INTO "carriers" VALUES(26,'Android','31099',
'310','99','internet','*','*','*',
NULL,NULL,NULL,NULL,
'null',NULL);

It seems to me that this telephony.db file contains APN information which will be required to connect Internet through PPP.

Following is a complete list of carriers contained in telephony.db.

• T-Mobile US
• T-Mobile UK
• T-Mobile D
• T-Mobile A
• T-Mobile CZ
• T-Mobile NL
• Cingular 410
• Cingular 170 Pacific Bell
• Cingular 380 ATT
• Chunghwa
• TWN GSM
• Far EasTone
• KGT-Online
• India Hutch
• SFR
• Vodafone UK
• IL Orange
• IL Cellcom
• IL Pelephone
• Jawwal Palestine
• Swisscom GPRS
• ERA
• CMCC
• Android
• UBIQUISYS
• Android

Cheers,

AT Commands

I found an emulator log of AT commands issued by Android to 3G module (well, for now it's a virtual device).

The log file can be created by following procedure.

$ cd /your/android/sdk//tools
$ ./emulator &
(wait for booting emulator up)
$ ./ddms

In the ddms menu, click [Device], then [Dump device state]. AT commands can be found in RADIO LOG section. I only checked Linux version of SDK. If other SDK doesn't have ddms, alternatively the log can be dumped by command line.

$ ./adb shell /system/bin/dumpstate
$ ./adb pull /tmp/state state.txt

Most of the AT commands match 3GPP specification. Some SMS related commands seem to be GSM based. 3GPP specification is available at a following page.

o 3GPP TS 27.007 AT command set for User Equipment (UE)

Initialization and PPP

+CMEE=1
+CGREG=2
+CCWA=1
+CMOD=0
+CMUT=0
+CSSN=0,1
+COLP=0
+CSCS="HEX"
+CUSD=1
+CGEREP=1,0
+CMGF=0
+CFUN?
+CPIN?
+CNMI?
+CSMS=1
+CNMI=1,2,2,1
+CGSN
+COPS=3,0; +COPS=3,1; +COPS=3,2; +COPS?
+CGREG?
+CREG?
+CSQ
+CIMI
+CRSM=
+CGDCONT=1,"IP","internet",,0,0
+CGQREQ=1
+CGQMIN=1
+CGEREP=1,0
+CGACT=1,0
D*99***1#

Outgoing Voice Call

D
+CLCC
+CSQ
+CHLD=1

Incoming Call

RING
+CLCC
A
+CSQ
+CHLD=1

Cheers,