Re: Phone Detection Scheme

>>These AT commands are probably fairly standard:
>>
>>AT+GMM  (Model)
>>AT+GMI (Manufacturer)
>>AT+GMR (Revision)
>>AT+GSN (ESN)
> 
> We could either create a lookup table for these, or pass the responses 
> to the phone modules.  

Make a dictionary and use them as they keys (eg if the phone responds
to 'AT+GSN' then there will be a key with that name, and a corresponding
value).

> Do you know of any phone on our list that does not support these commands?

For AT commands the phone will always respond with OK or ERROR so
it doesn't matter.  It is up to the phone module to work out what
is meaningful.

>>For "Brew" commands, the "firmwarereponse" (see p_brew.p) packet seems
>>to be pretty standard.
> 
> Can you get any useful info out of any of these BREW commands?  Something 
> along the line of manufacturer, model, etc. ??

Sometimes.  Just take the binary response and make it a key in
the dictionary as well.  Phone modules can look for whatever
sequence of bytes make sense to them.

Also add in the contents of some files if you can get the phone into
Brew mode.  That can help identify the carrier.  For example
with a VX8000 I can work out the carrier based on the contents
of the brew/version.txt file.  There are some other files in
nvm/nvm whose contents can be used to work out the carrier.

The general idea is that you gather up as much information as
possible (in parallel from the openable ports), dump it all in 
a dictionary and have the phone modules work out if their phones
are present.  Other modules can try to work out the carrier.

Roger


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click