Phone functionality in GUI applications

Rodolphe Ortalo rodolphe.ortalo at free.fr
Thu Oct 18 09:55:21 CEST 2007


Le jeudi 18 octobre 2007 à 02:19 +0200, Thomas Seiler a écrit :
> Am 17.10.2007 um 13:58 schrieb Joachim Steiger:
[...skipped...]
> > [...] first it has to be a
> > working phone.
> 
> Ok, then lets discuss what is all needed for a minimalistic interface  
> to get the phone working:
> 
> - GSM: trigger network registration,  get registration infos, signal  
> registration info and signal strength updates
> - SIM: get state, signal PIN entry required, enter pin
> - VoiceCall: call number, end call, accept incomming, reject  
> incomming,  signal for dialing, waiting, talking, busy and ringing
> 
> Anything else ?

Personnally, I would (try to) add a GPS entry here as it's one of the
main hardware innovation of modern "phones".

 - GPS: location available/not available, trigger acquisition, get last
known location, (...?)

Apart from this (purely personal) subject, the following aspects are
probably expected too in a working phone:

 - "Energy" state/requirements: power-line available, on battery, on low
battery, low-energy target (for user-requested long duration)...
 - (Data) Network availability (zero-cost/cheap/expensive)

Lalo recommended looking at the existing Telepathy APIs. Any more
precise pointers available? (Especially for the last point.)

Rodolphe






More information about the framework-devel mailing list