Openmoko - User contributions [en]

Talk:Gsmd

2008-09-16T09:39:29Z

Sh:

How do the new FCC regulations affect, if at all, OpenMoko development? Is the GSM module closed? If so, is the only way to interact with it through the AT interface and c library? Just wondering because it seems that it would fall under the new FCC regulations [http://linuxdevices.com/news/NS9075126639.html] that are going to take effect regarding SDR devices.

I don't think there is any effect. All power and SDR related software is on the baseband
processor (ARM 7) and is definitely not open source. It will probably be similar for the
Atheros WiFi.

Is this information outdated? There seem to be two alternatives to communicating directly with the Modem: The Trolltech Phone Stack and/or via Dbus - now which one is the method to use in the future?

--[[User:Sh|Sh]] 09:39, 16 September 2008 (UTC)

User:Sh

2007-11-22T13:40:53Z

Sh:

Sören Heisrath

soeren __ heisrath dot org

[http://soeren.heisrath.org personal homepage]

Talk:Community Updates

2007-11-22T13:33:12Z

Sh: GSM Modem firmware update

== gllin / GPS ==

Is there a target date for the discussion? Is there at least a date available for the next meeting or some such?

== GSM Modem firmware update ==

Hi,

How do I contact you, M. Shilo? I've got a neo with a gsm modem firmware that needs patching.
As far as Mr. google tells me, I'd have to send it (from Germany) to the U.S. - is there an OpenMoko developer which has signed TI's nda and lives in Germany or at least in Europe?
That would help a lot in circumventing shipping costs and especially customs...

Talk:Carriers/ATT

2007-10-01T13:32:04Z

Sh: forgot the headline...

AT&T/Cingular specifies the artwork so they should all look the same for the same SKU other than the vendor identification so I'm not sure what benefit there is in describing the images.

Except that some of the older SIM cards don't have anything, but markings to help denote what they are.

== This with Fireball success ==

I wonder if those who have been successful with AT&T 3G cards are only finding 2G access at their locations. I put in my 4020 sim card and get "REGISTRATION DENIED" in 2 seconds. Waiting for a long period of time does not change that.
--[[User:Sagacis|Sagacis]] 14:47, 6 August 2007 (CEST)

== Non-AT&T not working ==
How do i find out the SKU? There's a 13-Digit number followed by two letters on the back of my sim...

My provider isn't AT&T - it's O2 Germany and I as well have a 3G card. I've tested two 3G Cards and they both return CME Error 15, while non-3G cards from the same provider work flawless.

Full GSMD log is here: http://pastebin.com/f67ce2c25
--[[User:Sh|Sh]]

Talk:Carriers/ATT

2007-10-01T13:31:28Z

Sh:

AT&T/Cingular specifies the artwork so they should all look the same for the same SKU other than the vendor identification so I'm not sure what benefit there is in describing the images.

Except that some of the older SIM cards don't have anything, but markings to help denote what they are.

== This with Fireball success ==

I wonder if those who have been successful with AT&T 3G cards are only finding 2G access at their locations. I put in my 4020 sim card and get "REGISTRATION DENIED" in 2 seconds. Waiting for a long period of time does not change that.
--[[User:Sagacis|Sagacis]] 14:47, 6 August 2007 (CEST)

How do i find out the SKU? There's a 13-Digit number followed by two letters on the back of my sim...

My provider isn't AT&T - it's O2 Germany and I as well have a 3G card. I've tested two 3G Cards and they both return CME Error 15, while non-3G cards from the same provider work flawless.

Full GSMD log is here: http://pastebin.com/f67ce2c25
--[[User:Sh|Sh]]

Hardware:AT Commands

2007-09-25T15:20:48Z

Sh: +direct link to etsi spec

The protocol used to access the [[GSM]] chip is part of the GSM standard.

Harald wrote on 2007-01-31 on the list http://lists.openmoko.org/pipermail/community/2007-January/002708.html
"The chipset supports all of the mandatory [http://www.ctiforum.com/standard/standard/etsi/0707.pdf ETSI GSM TS 07.07] commands (use
http://pda.etsi.org/pda/queryform.asp to get it), plus some of the
optional ones. This GSM standard even has a command that lists the list of available
commands (AT+CLAC)."

On [[OpenMoko]], the commands should be used via [[gsmd]].

See also: http://wiki.openezx.org/AT_commands

German Link for AT explainations: http://www.nobbi.com/atgsm.htm

= On the Neo1973 =

== Uncommented List of AT Commands ==
(AT+CLAC) on the Neo1973 gives this list:

<pre>
AT+CACM
AT+CAMM
AT+CAOC
AT+CBC
AT+CBST
AT+CCFC
AT+CCUG
AT+CCWA
AT+CCWE
AT+CEER
AT+CFUN
AT+CGACT
AT+CGANS
AT+CGATT
AT+CGAUTO
AT+CGCLASS
AT+CGDATA
AT+CGDCONT
AT+CGEREP
AT+CGMI
AT+CGMM
AT+CGMR
AT+CGPADDR
AT+CGQMIN
AT+CGQREQ
AT+CGREG
AT+CGSMS
AT+CGSN
AT+CHLD
AT+CHUP
AT+CIMI
AT+CLAC
AT+CLAE
AT+CLAN
AT+CLCC
AT+CLCK
AT+CLIP
AT+CDIP
AT+CLIR
AT+CLVL
AT+CMEE
AT+CMGC
AT+CMGD
AT+CMGF
AT+CMGL
AT+CMGR
AT+CMGS
AT+CMGW
AT+CMOD
AT+CMSS
AT+CMMS
AT+CMUT
AT+CMUX
AT+CNMA
AT+CNMI
AT+CNUM
AT+COLP
AT+COPN
AT+COPS
AT+CPAS
AT+CPBF
AT+CPBR
AT+CPBS
AT+CPBW
AT+CPIN
AT+CPMS
AT+CPOL
AT+CPUC
AT+CPWD
AT+CR
AT+CRC
AT+CREG
AT+CRES
AT+CRLP
AT+CRSL
AT+CRSM
AT+CSAS
AT+CSCA
AT+CSCB
AT+CSCS
AT+CSDH
AT+CSIM
AT+CSMP
AT+CSMS
AT+CSNS
AT+CSQ
AT%CSQ
AT+CSSN
AT+CSTA
AT+CSVM
AT+CTFR
AT+CUSD
AT+DR
AT+FAP
AT+FBO
AT+FBS
AT+FBU
AT+FCC
AT+FCLASS
AT+FCQ
AT+FCR
AT+FCS
AT+FCT
AT+FDR
AT+FDT
AT+FEA
AT+FFC
AT+FHS
AT+FIE
AT+FIP
AT+FIS
AT+FIT
AT+FKS
AT+FLI
AT+FLO
AT+FLP
AT+FMI
AT+FMM
AT+FMR
AT+FMS
AT+FND
AT+FNR
AT+FNS
AT+FPA
AT+FPI
AT+FPS
AT+FPW
AT+FRQ
AT+FSA
AT+FSP
AT+GCAP
AT+GCI
AT+GMI
AT+GMM
AT+GMR
AT+GSN
AT+ICF
AT+IFC
AT+ILRR
AT+IPR
AT+VTS
AT+WS46
AT%ALS
AT%ATR
AT%BAND
AT%CACM
AT%CAOC
AT%CCBS
AT%STDR
AT%CGAATT
AT%CGMM
AT%CGREG
AT%CNAP
AT%CPI
AT%COLR
AT%CPRIM
AT%CTV
AT%CUNS
AT%NRG
AT%SATC
AT%SATE
AT%SATR
AT%SATT
AT%SNCNT
AT%VER
AT%CGCLASS
AT%CGPCO
AT%CGPPP
AT%EM
AT%EMET
AT%EMETS
AT%CBHZ
AT%CPHS
AT%CPNUMS
AT%CPALS
AT%CPVWI
AT%CPOPN
AT%CPCFU
AT%CPINF
AT%CPMB
AT%CPRI
AT%DATA
AT%DINF
AT%CLCC
AT%DBGINFO
AT%VTS
AT%CHPL
AT%CREG
AT+CTZR
AT+CTZU
AT%CTZV
AT%CNIV
AT%PVRF
AT%CWUP
AT%DAR
AT+CIND
AT+CMER
AT%CSCN
AT%RDL
AT%RDLB
AT%CSTAT
AT%CPRSM
AT%CHLD
AT%SIMIND
AT%SECP
AT%SECS
AT%CSSN
AT+CCLK
AT%CSSD
AT%COPS
AT%CPMBW
AT%CUST
AT%SATCC
AT%COPN
AT%CGEREP
AT%CUSCFG
AT%CUSDR
AT%CPBS
AT%PBCF
AT%SIMEF
AT%EFRSLT
AT%CMGMDU
AT%CMGL
AT%CMGR
ATA
ATB
AT&C
ATD
AT&D
ATE
ATF
AT&F
ATH
ATI
AT&K
ATL
ATM
ATO
ATP
ATQ
ATS
ATT
ATV
ATW
AT&W
ATX
ATZ
</pre>

== Results of AT Commands ==

Taken from "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; AT command set for User Equipment (UE) (Release 7)" - 3GPP TS 27.007 V7.2.0 (2006-09)

== Section 5, General Commands ==

Request manufacturer identification +CGMI

AT+CGMI
<manufacturer>

OK

Request model identification +CGMM

AT+CGMM
<model>

OK

Request revision identification +CGMR

AT+CGMR
<revision>

OK

Request product serial number identification +CGSN

AT+CGSN
<serial number>

OK

Select TE character set +CSCS

AT+CSCS?
+CSCS: "IRA"

OK

AT+CSCS=?
+CSCS: "GSM","IRA","PCCP437","PCDN","8859-1","HEX","UCS2"

OK

Request international mobile subscriber identity +CIMI

AT+CIMI
*************** (I'm not giving you my IMSI!)

OK

Request subscriber number +CNUM

AT+CNUM
+CNUM: ,"0123456789",122

OK

Multiplexing mode +CMUX

AT+CMUX?
ERROR
AT+CMUX=?
+CMUX: (1),(0),(1-5),(10-100),(1-255),(0-100),(2-255),(1-255),(1-7)

OK

PCCA STD 101 [17] select wireless network +WS46

AT+WS46=?
+WS46: (12)

OK

== Section 6, Call control commands and methods ==

Select type of address +CSTA

AT+CSTA?
+CSTA: 129

OK
AT+CSTA=?
+CSTA: (129,145)

OK

Call mode +CMOD

AT+CMOD=?
+CMOD: (0-3)

OK

Select bearer service type +CBST

AT+CBST?
+CBST: 7,0,1

OK
AT+CBST=?
+CBST: (0-7,12,14,65,66,68,70,71,75),(0),(0-3)

OK

Radio link protocol +CRLP

AT+CRLP?
+CRLP: 61,61,48,6

OK
AT+CRLP=?
+CRLP: (0-61),(0-61),(39-255),(1-255)

OK

Service reporting control +CR

AT+CR?
+CR: 0

OK
AT+CR=?
+CR: (0,1)

OK

Extended error report +CEER

AT+CEER
+CEER: 0,0,5,16,normal call clearing

OK

Cellular result codes +CRC

AT+CRC=1
OK

+CRING: VOICE

Single numbering scheme +CSNS

AT+CSNS=?
+CSNS: (0-7)

OK

== Section 7, Network service related commands ==

7.2 Network registration +CREG

AT+CREG?
+CREG: 0,0

OK
AT+CREG=?
+CREG: (0-2)

OK

7.3 PLMN selection +COPS

AT+CREG=1
OK

AT+COPS=0
OK

+CREG: 2

+CREG: 1

== Section 8, Mobile Termination control and status commands ==

8.1 Phone activity status +CPAS

AT+CPAS
+CPAS: 0

OK
AT+CPAS=?
+CPAS: (0-5)

OK

8.2 Set phone functionality +CFUN

AT+CFUN?
+CFUN: 1

OK
AT+CFUN=?
+CFUN: (0,1,4),(0)

OK

8.4 Battery charge +CBC

AT+CBC
+CBC: 0,0

OK
AT+CBC=?
+CBC: (0-3),(0-100)

OK

== Miscellaneous ==

AT+CPAS
+CPAS: 5

OK

AT+CPAS?
ERROR
AT+CPAS=?
+CPAS: (0-5)

OK

AT%BAND?
%BAND: 0

OK
AT%BAND=?
%BAND: (0-1),(1-31)

OK

AT+CSSN?
+CSSN: 0,0

OK
AT+CSSN=?
+CSSN: (0,1),(0,1)

OK

[[Category:Neo1973 Hardware]]

Wishlist/Unlikely

2007-03-12T22:02:53Z

Sh: + flux capacitor

These are ideas that are unlikely to be implementable in the near term, or indeed ever in a phone.
Some of them may be possible if technology improves in the future, or when patents expire.

=====LASER keyboard (can be a full QWERTY keyboard)=====
*On the hardware side, this would require a $5 laser diode, a $3 (in bulk) custom diffraction grating, and probably a couple of cubic centimetres volume inside the phone.
*This requires a camera pointable to the front.
*It requires an integrated stand for the phone.
*To practically use this, you've got to be 40cm or so away from the phone, which means under 25*20 of text resolution.
*In software, it's relatively easy to parse the camera output, to find changes in the known laser field.

There are major problems.
*Patent issues.
*No tactile response at all, which slows typing.
*An extra 2cc/6g.

=====Alcohol Sensor=====
Alcohol sensor adjacent to microphone. It doesn't have to be accurate, just has to detect any amount of alcohol on the speaker's breath. I understand this is a very narrow market, but alcohol is on every parent's mind.

I think those who drive cars might profit from this feature too. --[[User:Cedel|cedel]] 16:02, 20 February 2007 (CET)

:Although this is a good idea, you have to be very careful about liability here. If it gives a false positive (i.e. you're not over the limit), and you have an accident, the OpenMoko team might be liable.

=====Disinfection UV-Light=====
I had read about it in an Article on http://www.americanairandwater.com/UV-news/. But Motorola patents it.
Yes - finally a way to stop the billions of annual deaths due to cellphone infections! --[[User:Speedevil|Speedevil]] 14:04, 16 February 2007 (CET)
It´s just something that flying in my head... It´s not the first "unreal" or "useless" idea. Just for fun! --[[User:MookiE|MookiE]] 14:51, 16 February 2007 (CET)

More seriously - UV of the required frequency is inherently eye-damaging.
Also, as I understand it, there are actually no UV LEDs that will reliably produce 'germicidal' UV.
The most expensive - and they are very expensive - ones produce UV of a sort that may kill very susceptible bacteria, but comparatively few.
IIRC the LEDs are $20 per.
--[[User:Speedevil|Speedevil]] 15:11, 16 February 2007 (CET)

=====Teleportation=====
Implementing a beaming-device to the Neo would make it the first phone enabling teleportation.
See: [http://news.bbc.co.uk/1/hi/sci/tech/3811785.stm]
Possible implementation difficulties might be the lacking teleportation-support in the GSM standard as well as uncooperative mobile service providers that feel uneasy towards innovative technologies...
''

(Please get serious. You would obviously need more bandwidth to make this practical. Wifi would be better or at least 3G. maybe you could use Bluetooth with the right compression algorithms.)''

=====V12 Embedded power source=====

We'll need something beefy to power the next Neos for the above gadgets, I propose the use of a [http://www.ultimatestupidity.com/pics/1/diesel/ Embeddable Power Source], that with some miniturisation and a bit of design work should be workable as a possible solution.

=====Floppy Disk Drive=====
For people stuck in the past who just can't let go of that last 3 and a half inches.

=====PCMCIA slot=====
Extensibility would be nice. Standard pcmcia would be great for allowing wireless too. And pcmcia cards tend to be very low power.
*1. can be used for a spare battery (is this possible?)
*3. i can use my [http://www.echoaudio.com/Products/CardBus/IndigoIO/index.php Echo Audio Indigo I/O]
*2. can be used for different cards around

This is certain not to happen in a production phone, it's simply far too large, and requires complex support in hardware, which does not exist in most system on a chip devices as are used in phones.
Even for the [[Expansion_Back]] it would be too large. --[[User:Speedevil|Speedevil]] 06:05, 28 February 2007 (CET)

=====Dump the '''''egg-shaped''''' case design and go '''''rectangular''''' for more screen space=====
*I'm all for devices that look great and have great features - aside from that I really like the current design. Thus I'd like to comment that the design change request is probably not the majority's opinion. [[User:Abraxa|Abraxa]] 00:00, 18 February 2007 (CET)

There will be many OpenMoko devices, of different designs. --[[User:Speedevil|Speedevil]] 06:19, 28 February 2007 (CET)

===== Flux Capacitor =====
The device needs a [http://en.wikipedia.org/wiki/Flux_capacitor flux capacitor] instead of a battery ;)

User:Sh

2007-02-28T21:18:45Z

Sh:

Sören Heisrath

[http://soeren.heisrath.org personal homepage]