Okay, I achieved something. I'm able to activate WiFi now (using
moduled driver and patch for this bug:
http://code.google.com/p/android/issues/detail?id=17255&q=wifi%20loop&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars)

But after 10-20 seconds it gets deactivated again. In logcat I found
this line:

E/WifiHW (  1021): Unable to open connection to supplicant on "/data/
system/wpa_supplicant/wlan0": No such file or directory

What could that possibly mean?

Thanks,
Cyberworm

On 2 Jun., 13:42, Cyberworm <cybaw...@gmail.com> wrote:
> Hi, thanks for you help.
>
> I managed to enable Wi-Fi using the driver as a module. But after that
> Android was in an endless reboot loop. I then tried to use the built-
> in driver way, but this way doesn't really work as I'm not able to
> activate Wi-Fi (logcat just saying something about not being able to
> bring up wlan0).
>
> I'll try to post some logcat messages here, as I can't access my
> device via adb. It would be great if panic had a version of that
> reboot fix patch for moduled driver.
>
> Greetings,
> Cyberworm
>
> On 1 Jun., 13:28, Amit Pundir <pundira...@gmail.com> wrote:
>
>
>
>
>
>
>
> > On Tue, May 31, 2011 at 8:48 PM, Cyberworm <cybaw...@gmail.com> wrote:
> > > Using a modified su program I finally got root access.Wifistill
> > > isn't working. Is there no one who can help me?
>
> > Difficult to help unless you post relevant logcat output here.
>
> > Anyways few pointers to get you started:
>
> > 1. wpa_supplicant relies heavly on private ioctls specially for
> > scanning and other purposes. Make sure either yourwifidriver is
> > supporting those ioctl or use this workaround 
> > fromhttp://blog.linuxconsulting.ro/https://gitorious.org/picopc-android-g......
>
> > 2. By default Android also requires you to build yourwifidriver as a
> > module which can be inserted/removed at the time you enable/disable
> >wififrom UI. Do that or use this workaround (same source) if driver
> > is built into the kernel 
> > itselfhttps://gitorious.org/picopc-android-gingerbread/hardware-libhardware...
>
> > 3. Set the correctwifioptions and paths for driver & firmware in
> > Boardconfig.mk
> > e.g.
> > BOARD_WPA_SUPPLICANT_DRIVER := {CUSTOM or WEXT etc}
> > WPA_SUPPLICANT_VERSION      := VER_0_6_X
> > WIFI_DRIVER_MODULE_PATH     := "path_to_wifi_driver.ko if built as a module"
> > WIFI_DRIVER_MODULE_NAME     := ""
> > WIFI_FIRMWARE_LOADER        := "firmware_loader_if_you_need_any"
> > WIFI_DRIVER_MODULE_ARG      := ""
> > WIFI_DRIVER_FW_STA_PATH     := "path_to_firmware_location"
>
> > 4. Correct permissions are applied to corresponding files in init.rc
>
> > Regards,
> > Amit Pundir
>
> > > On 17 Mai, 20:10, Cyberworm <cybaw...@gmail.com> wrote:
> > >> Hi all,
>
> > >> I'm trying to portGingerbreadto my OpenPandora device 
> > >> (seehttp://www.openpandora.orgfordetails). Keyboard and Touchscreen work
> > >> fine and now I'm working onWifi. I basically followed this 
> > >> guide:http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-androi...
> > >> but I guess it's kinda outdated. I also modifiedwifi.c as panic
> > >> suggested in the most recent comment (March 22, 2011).
>
> > >> It just doesn't work. When trying to activate it I only get "Error". I
> > >> tried starting it manually but that doesn't work either.
>
> > >> I can't even use logcat or netcfg because these program complain that
> > >> they don't have permission to open files.
>
> > >> So, could someone help me out please?
>
> > >> Thanks,
> > >> cyberworm
>
> > > --
> > > unsubscribe: android-porting+unsubscr...@googlegroups.com
> > > website:http://groups.google.com/group/android-porting

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to