Sagem MyX-2

From GnokiiWiki
Jump to: navigation, search


Contents

Versions

This is this phone.

Which was tested using gnokii 0.6.31 but should work with most older versions too.

Configuration

This device can only communicate using a pl2303-based serial <-> USB cable.

model = AT
connection = serial
port = /dev/ttyUSB0
serial_baudrate = 115200  # the phone was set to a fixed-baudrate of 115200 bps too (menu: addons > data)

Kernel and hardware used:

Kernel : 3.8
Bus 001 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

gnokii --identify

IMEI         : 351X1600XXXXXXX
Manufacturer : SAGEM 
Model        : myX-2
Product name : myX-2
Revision     : SAGEM JA3,EB

Important: the communication to the phone is very unreliable: there is 1/2 chance that the ATZ command hangs-on.

In such a case you can interrupt the command and relaunch it. Pushing a phone key in order to get the phone display back seems to increase the chances of success.

Working Features

  • phonebook read
  • phonebook write (see below for details about this)
  • read sms (read all is possible, but specifying a directory didn't worked)
  • send sms


phonebook write

  • The find-free current implementation make very slow the use of --writephonebook -f
  • (probably not related to this phone): vcard formatting needs some rules (to be added)

Other commands

  • --deletephonebook ME 1 end works but must test every possible location (slow)
  • --getnetworkinfo fails to provide useful information. A simple AT+COPS=? (using cu) does work but takes several dozens of seconds)
  • chances are that AT+CALA (alarm management) may be supported
  • GPRS has not been tested so far
  • there has been a Wammu report of success reading and making calls

About My Pictures and Sound

My Pictures and Sound is the official Windows/Sagem application

  • for this phone it offers one (and only one) feature: upload medias (nothing about sms or phonebook)
  • it makes use of AT+KIPR=115200 (that could make the communication more reliable)

Sample trace of the PC -> phone USB channel, using this (garbage-prone) command and a file from sniffusb:

perl usbreplayprep.pl < win-usbsnoop.log|sed -nr -e '/:/{s/.*:[[:blank:]]//;s/ 0d/ 0a/;s/([0-9a-f][0-9a-f])/0x\1/g;p}'|xxd -r -p

Simple MP&S detection sequence:

AT+KIPR=115200
Ò#òAT+CGMI;+CGMM;+CGSN;+CMEE=1;+KDOBJ?
AT+CPIN?;+CIMI;E0V1&K3
AT+KPSV;+CSCS="UCS2"
AT+CGSN

File upload (blah.wav) sequence:

AT+CGSN
AT+CGSN
AT+KDOBJ?           # non-standard command, returns: +KDOBJ: 204800  # what seems to be phone's free space
AT+KDOBJ=1,1        # we intend to upload a media
AT+KDOBJ=2,1,3,0,4  # the file is the 4 next characters, and this is a sound
blah
AT+KDOBJ=2,1,0,1,176458    # actually the file was 17ko, not 172ko
RIFFB±WAVEfmt...           # rest of the file