Hi,
On Dec 19, 8:38 am, "pavan savoy" <pavan.sa...@gmail.com> wrote:
> Hi,
>
> The wlan which I have in my setup, starts off with wlan_loader.
> But before I start off the service wpa_supplicant, there needs to be an IP
> address assigned & the interface has to be made up.
Dm: Why do you think so ? IP has nothing to do with wpa_supplicant.
>
> So is there a service which does that automatically, if from cmd line, I do
> ifconfig wlan0 <ip_address> up.
> Can I somehow do this inside the init.rc ? after wlan_loader ?
You can not do this - it doesn't make any sense. wlan_loader just
loads wifi firmware.
But for WiFi you need to be associated with AP at least.
>
> Also are there any pointers as to how to start off dhcpcd ? & who is
> starting that ? like WifiService is starting wlan_loader & wpa_supplicant
> via wifi.c in libhardware.
Network framework starts dhcpcd. There is a network layer that is
responsible for this.
Look for wifi.c and hardware library.
>
> Thanks,
> Pavan
>
> On Tue, Dec 16, 2008 at 12:16 PM, dimitr...@android.com <
>
>
>
> dimitr...@android.com> wrote:
>
> > Hi,
> > Framework supposes to start wpa_supplicant.
> > Or you can start it manually - framework will talk to it through
> > socket interface.
> > However framework will expect some data (for example from scan
> > results) in certain format.
> > For example, it expects Rssi value to be negative.
>
> > On Dec 16, 9:53 am, solca <osola...@gmail.com> wrote:
> > > On 16 dic, 10:52, borhe <boris.st...@gmail.com> wrote:
>
> > > > Hi!
> > > > I am porting android to the ARM platform, i am trying now to make WiFi
> > > > work but got stuck a little bit,
> > > > My question is how should i start wpa_supplicant service: manually or
> > > > is it done by the framework, can't figure it out .
> > > > I compiled supplicant manually and tested it outside android and can
> > > > connect to AP.
>
> > > > Please Help!
>
> > > > Bellow is a failure log:
>
> > > > I/SystemServer( 241): Starting Status Bar Service.
> > > > I/WindowManager( 241): Input configuration changed: { scale=1.0
> > > > imsi=0/0 locale=en_US touch=3 key=2/2 nav=3 orien=2 }
> > > > I/SystemServer( 241): Starting Hardware Service.
> > > > I/SystemServer( 241): Starting NetStat Service.
> > > > I/SystemServer( 241): Starting Connectivity Service.
> > > > W/dalvikvm( 241): VFY: unable to resolve virtual method 437: Landroid/
> > > > net/NetworkStateTracker;.releaseWakeLock ()V
> > > > W/dalvikvm( 241): VFY: rejecting opcode 0x6e at 0x00cb
> > > > W/dalvikvm( 241): VFY: rejected Lcom/android/server/
> > > > ConnectivityService;.handleConnect (Landroid/net/NetworkInfo;)V
> > > > W/dalvikvm( 241): Verifier rejected class Lcom/android/server/
> > > > ConnectivityService;
> > > > E/SystemServer( 241): Failure starting Connectivity Service
> > > > E/SystemServer( 241): java.lang.VerifyError:
> > > > com.android.server.ConnectivityService
> > > > E/SystemServer( 241): at com.android.server.ServerThread.run
> > > > (SystemServer.java:202)
> > > > E/AndroidRuntime( 241): Crash logging skipped, no checkin service
> > > > I/SystemServer( 241): Starting Notification Manager.
> > > > I/SystemServer( 241): Starting Location Manager.
> > > > D/LocationManagerService( 241): Constructed LocationManager Service
> > > > D/libhardware( 241): no GPS hardware on this device
> > > > D/LocationManagerService( 241): Found dir /data/location/gps
> > > > D/LocationManagerService( 241): name = gps
> > > > D/TrackProvider( 241): Loading properties file /data/location/gps/
> > > > properties
> > > > D/dalvikvm( 241): GC freed 6152 objects / 336576 bytes in 289ms
> > > > E/SystemServer( 241): Failure starting Location Manager
> > > > E/SystemServer( 241): java.lang.NullPointerException
> > > > E/SystemServer( 241): at android.net.wifi.WifiManager.getScanResults
> > > > (WifiManager.java:483)
> > > > E/SystemServer( 241): at
> > > > com.android.server.LocationManagerService.<init>
> > > > (LocationManagerService.java:487)
> > > > E/SystemServer( 241): at com.android.server.ServerThread.run
> > > > (SystemServer.java:234)
> > > > E/AndroidRuntime( 241): Crash logging skipped, no checkin service
>
> > > You can check the NITdroid patch to solve your problem:
>
> > >http://guug.org/nit/nitdroid/- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
