[ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2 in extras] - maemo.org

laasonen · #1 2011-06-02, 01:15

Just coded a little status area applet which lets you switch between stock and bleeding edge drivers

It also has a possibility to shut down WLAN complitely.

You can find it under name status-area-wlan-driver-selector-applet on extras-testing. Please vote, if you think its stable.

All ideas and feedback are welcome

How?

Install kernel-power (>=v46-wl1)
Download the bleeding edge drivers with the applets wizard, if you don't have them allready
First time when you bleeding edge drivers, it will ask for the folder where you saved the drivers, if you didn't use the applet's wizard

Applet is not showing up? You could try to run this as root:

Code:

apt-get install python python-hildondesktop
reboot
apt-get install --reinstall status-area-wlan-driver-selector-applet

My drivers are not located in MyDocs or memory card. How to select?

Code:

gconftool-2 --type string --set /apps/wlan_driver_selector/driver_folder /path/to/drivers/

Customized osso-wlan (optional)

Quote:

This fixes a bug where WLAN gets stuck, when you are connected to an
access point and go out-of-range.

WARNING: Installing this will break seamless upgrades to new PR versions.
Most likely you will have to reinstall normal osso-wlan version
before you can do OTA upgrades.

You can also skip this step, but keep in mind that the above mentioned bug
can occur. If this bug is triggered you have 3 options:
manually unset ssid, unload and reload driver or reboot your phone.

Run this as root:

Code:

apt-get install wget #If you don't have wget already
wget http://files.laasonen.net/osso-wlan_3.0.20+0m5-1_armel.deb
dpkg -i osso-wlan_3.0.20+0m5-1_armel.deb

Or click this on MicroB and then click "Open with App. manager".
Or download this with your PC, move it to your N900 and then open it with the file browser.

zylor · #2 2011-06-02, 01:38

But... how does this applet know from where does it need to pickup the drivers? Or they are included in the deb?

Mentalist Traceur · #3 2011-06-02, 01:45

I'm guessing it either
A: Assumes that the driver is in the default path, as per the instructions in the original package from lxp that they came in.
or
B: Performs epically awesome shell script voodoo, searching the system for a directory that has all of the files with the respective kernel module names in it, then saves that location to somewhere, then, if at some point it gets an error because those files are no longer there, it repeats the search.

Cuz B would be awesome...slow, but awesome.... but it's probably A.

Mentalist Traceur · #4 2011-06-02, 02:03

Just looked at the source code - looks like (I skimmed, and I'm not that experienced with Python code making GUIs, so I might be reading this wrong), it's going to actually give you a menu to download the bleeding edge drivers, and then has a configuration option of pointing it to the directory where the bleeding edge drivers are.

laasonen · #5 2011-06-02, 02:11

Quote:

Originally Posted by Mentalist Traceur

Just looked at the source code - looks like (I skimmed, and I'm not that experienced with Python code making GUIs, so I might be reading this wrong), it's going to actually give you a menu to download the bleeding edge drivers, and then has a configuration option of pointing it to the directory where the bleeding edge drivers are.

Yes, it will ask for the folder where you have saved the drivers and then saves it to gconf. It has a download button which open the bleeding edge drivers's homepage on microb.

F2thaK · #6 2011-06-02, 02:15

is there issues with the bleeding edge?

edit: didnt realise the bleeding edge was free now either. cool. downloading!

do we need to extract the tar ?

laasonen · #7 2011-06-02, 02:25

Quote:

Originally Posted by F2thaK

is there issues with the bleeding edge?

edit: didnt realise the bleeding edge was free now either. cool. downloading!

I haven't had any issues, but I haven't used it much. Some people say it drains the battery faster, so I'm only using it when needed.

price · #8 2011-06-02, 02:31

I've installed it trough FAM but i'cant see it in status menu. i'm on CSSU.15

Mentalist Traceur · #9 2011-06-02, 02:33

I use the bleeding edge driver all the time. Some people do say there's battery issues, but I use it as my default driver all the time, and I see no noticeable battery life decrease.

laasonen · #10 2011-06-02, 02:36

Quote:

Originally Posted by F2thaK

do we need to extract the tar ?

Yes, the wl1251-maemo/binary/compat-wireless/ folder.

Quote:

Originally Posted by price

I've installed it trough FAM but i'cant see it in status menu. i'm on CSSU.15

I managed to successfully install it with FAM, HAM and APT :/ You could try to kill the hildon-status-menu and see, if it starts:

Code:

killall hildon-status-menu

The Following 63 Users Say Thank You to laasonen For This Useful Post:
101aj, AgentZ, anapospastos, anonymous, Bahador, casketizer, clasificado, codeMonkey, cvetkov.i, Daneel, datjomp, devdsp, Dr.Marcial, eefo, Erazor, Estel, EyeVisions, F2thaK, fasza2, fatcobrah, frostbyte, fw190, GameboyRMH, Garrett_PL, getnani, godofwar424, handaxe, Hotshot, hstende, HtheB, humble, ibrakalifa, ioan, ivyking, jberezhnoy, jedi, kl2010, kolos, longcat, MartinK, Mentalist Traceur, moepda, Mohammed Muid, Mr Wolf, mveplus, navsin, Netweaver, q6600, samipower, shawwawa, sifo, skykooler, SSLMM, stlpaul, SuperDumb, techno2001, Tensuke, tuxsavvy, uppercase, Verssetti, xprism, xsmabbs

The Following User Says Thank You to Mentalist Traceur For This Useful Post:
Estel

The Following 3 Users Say Thank You to laasonen For This Useful Post:
F2thaK, godofwar424, Mentalist Traceur

The Following User Says Thank You to Mentalist Traceur For This Useful Post:
Duffer