Excellent! That sounds like a fun project. I would recommend going the NetworkStateTracker route. It should get notified of state changes for your modem and convert that into standard signals for the ConnectivityService. It also provides an API for the ConnectivityService to turn your modem on and off. Currently the 3g connection is assumed to turn itself on at boot - but post boot it would be controlled by the ConnectivityService.
Regards Robert On Wed, Aug 11, 2010 at 7:16 PM, Termana <[email protected]> wrote: > > On Aug 12, 9:54 am, Robert Greenwalt <[email protected]> wrote: > > What version of android are you using - this changed a bunch in the > eclair > > timeframe I think. > I'm using Froyo (2.2) > > > Also, if you can say, what type of network is this? If > > it's generally useful it may be a nice opensource submission! > > I am apart of the effort to get Android working on the Nokia N900 > (NITdroid). It has a 3G modem, but doesn't communicate with AT > commands, and (obviously) does not have a RIL shared library written > for it. It is a GPRS (on UMTS) connection. However instead of writing > a RIL that will communicate with phonet (which is a network interface > that communicates with the phonet/isi modem, and has its own > protocol), and having to learn how to communicate directly over it, at > the moment we are working on making Android work with ofono (including > at some point writing a RIL that will communicate with ofono using d- > bus). > > The modem is powered and network registered by ofono, and when you > start the data connection it gives you a network interface - gprs0. > (And then you make sure the gprs0 interface is configured (eg. > ifconfig gprs0 gprs.ip.address.here) and add a default route in the ip > tables - route add default dev gprs0) > > When we make ofono communicate with RILD, this will obviously not > matter - so I was just looking for a temporary solution while this is > happening - since it is quite annoying have a lot of apps (including > built-in ones) refuse to work properly because the ConnectivityManager > reports no connection. > > > Thanks > > Robert > > Cheers, > Bradley Smith > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
