Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
How can I copy and paste to the system?
Thanks!
royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!
chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.
royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.
Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
works flawless, extreme improvement, thank you very much!
Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.
Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?
Hi all.
I am hoping someone out there can help me.
I recently bought a used Dell Streak S7.
I tried to restore the DS& back to a factory out of the box state and no luck.
Tried the follwoing three
menu ->setting-> Privacy->Factory Data reset
pin hole by sd card\
Volume + and power -> 1. and 3.
I have added info for Wi-fi and everytime DS7 is turned off and turned on the wi-fi settings are lost.
I was able to root it with One Click Superoot but when i turn DS7 off and turn it off the SU dissapears.
I read http://forum.xda-developers.com/showthread.php?t=1011654 and i can't access CWM thorugh Goggle market.
The original owner account info still remains regardless of reboot and etc.....
I don't have a SD card for it and i am not sure what impact that has.
Android Version 2.2
Baseband Version 11.809.05.03.00
OEM version GLUNB1A132233
Build Number 14291
ANy information or any ideas would greatly help.
Thanks,
Dennis
Dennis,
Did you every resolve your issues?
I am having nearly the same issues as you were.
I bought a used Dell Streak that had been updated to Froyo. When I try to reset the device to factory settings to remove the original owners email address it acts like it works but each time the device boots back up all the original owners info is still there. Their wallpaper, email accounts, facebook accounts, twitter acounts, etc.
I have tried to use the Settings>Privacy>Factory Data Rest, it seems to work but doesn't clear the system all data remains.
I have tried turning off the unit and holding the volume up and power and using the restore option from there but each time it boots back with all the original owners info.
I can not get it to do a factory reset thus I can not associate my gmail account with the device.
Does anyone have a solution?
Thanks,
Frankie4life
No luck yet.
Still waiting and hoping.
Have you guys tried restoring with NVFlash? this procedure works great and helped me a bunch. http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
If you are successful but your streak still wont get past the dell logo on boot, boot back into recovery (Vol+ and Power) and do a factory restore.
warning, this will erase EVERYTHING on your streak
Same thing here
I am having the same exact issue. I have tried restoring using nvflash... No luck
I have tried using the Fastboot method... No Luck
I even found an Update.pkg to try and update it using the built in recovery... No luck, It ends with an error of "Modem Error" says it completed successfully and then reboots to its previos state.
I have tried flashing the clockwork recovery via Fastboot and also.... No Luck
I am not a Noob and I have the the proper ADB and fastboot drivers installed, I am very familiar with using the android sdk and adb command from the SDK folder location.
I beleive at this point either due to an error or something the previous owner did the Streak is now "write protected" is this possible?
My biggest problem is when I root the devices using super one click it gives me root access and when launching the ADB SHELL i receive the "#" indicating that the shell has root, If I try and run ADB remount i receive and error
"c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>"
this indicates to me that I cannot mount any memory from the device as read/write.
Any info would be helpful
Tom
wikedbubble said:
I am having the same exact issue. I have tried restoring using nvflash... No luck
I have tried using the Fastboot method... No Luck
I even found an Update.pkg to try and update it using the built in recovery... No luck, It ends with an error of "Modem Error" says it completed successfully and then reboots to its previos state.
I have tried flashing the clockwork recovery via Fastboot and also.... No Luck
I am not a Noob and I have the the proper ADB and fastboot drivers installed, I am very familiar with using the android sdk and adb command from the SDK folder location.
I beleive at this point either due to an error or something the previous owner did the Streak is now "write protected" is this possible?
My biggest problem is when I root the devices using super one click it gives me root access and when launching the ADB SHELL i receive the "#" indicating that the shell has root, If I try and run ADB remount i receive and error
"c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>"
this indicates to me that I cannot mount any memory from the device as read/write.
Any info would be helpful
Tom
Click to expand...
Click to collapse
hi, i'm going through something similar, where did you find the update.pkg? i've been looking for it everywhere, thank you
the answer i would suggest is use nvflash like navycow suggested you have 2 choices with that you can install unrooted 2.2.2 or honeycomb, search the thread for it and if you can't find it let me know i will post a link.
It seems that alot of people are having this problem I found the link for the OTA update here.
http://www.streaksmart.com/updates/page/2/
From there you can download the update.pkg manually or OTA
Make sure you don't use the O2 update because that is for the Streak released in EU. It took a little browsing but I found it in there somewhere
HI everyone, i'm a Noob here sooo here goes:
I don't know why - but I installed CM9 Alpha 2 on my HP Touchpad and my wireless was working at the time of installation. After using it for a while then turning it off, and on again the wireless stopped working. I can see the wireless signals but when i click to connect it says "Connecting" then back to the wireless name and never connects. It came back, stayed on for a while...then when i reset it again this time to see if it would go off again - it hasn't come back since.
My question: Does anyone know what is going on? Am i missing something or doing something?
Thank you
Im having the same problem...
nightly 3/17
FWIW I have had the same problem occasionally when installing different builds but what seems to help is going into the WebOs and turning the WiFi off then on and then rebooting into whatever Android version I was using at the time. There is also a long thread covering this in the development section with thoughts on how to fix the problem.
bob
"I don't know why - but I installed CM9 Alpha 2 on my HP Touchpad and my wireless was working at the time of installation. After using it for a while then turning it off, and on again the wireless stopped working. I can see the wireless signals but when i click to connect it says "Connecting" then back to the wireless name and never connects. It came back, stayed on for a while...then when i reset it again this time to see if it would go off again - it hasn't come back since.
My question: Does anyone know what is going on? Am i missing something or doing something?"
No, you've done well...wifi has been a persistent issue with almost everyone. There are several ways to go about resolving it.
1) (from terminal emulator): enter su (hit return) then type the following....
rm (space) -rf (space) /data/misc/wifi (space) && (space) reboot
(Or if that doesn't work...)
(from root explorer): access /data/misc/wifi folder then long press wpa supplicant folder and select delete...confirm delete and reboot
Either of those methods from #1 should allow you to restore wifi but you'll probably have to repeat the process upon each reboot/restart of your TP. A more permanent resolution has been proposed by #2 below.
2) You can also look up Rohan's Supreme Mods v 1.3 (for CM9 Alpha 2) and flash that zip file over your current rom, but be sure to reboot into recovery and make a Nandroid backup before flashing the mod package.
:[MODPACK][3/10][NEW]SUPREME Mods v1.3 [Faster, Smoother, Faster Wifi, Better Battery]
http://forum.xda-developers.com/show....php?t=1519161
Make sure you select the mod package that matches your current DPI setting of your Alpha 2 rom and follow his install instructions to the letter.
Good luck!
flash these drivers. should do the trick if you're having wifi issues with the disconnect reconnects.
http://rootzwiki.com/topic/18332-new-wifi-driver-ath6kl-from-compat-wireless/
download the file and flash via Clockworkmod, do a nandroid backup first just in case something goes rogue.
another quick fix, toggle airplane mode. usually gets you back going again. As for rohan's mods, try this first. His mods won't help if you can't keep a stable wifi connection.
I'm having this problem also. Very frustrating! I will try all of this tomorrow and report back. Thanks.
Sent from my Kindle Fire using Tapatalk
This thread has a lot of useful fixes which might help.
As you may know, OpenELEC v4 beta was released yesterday.
I formatted my SD Card, used NOOBS to install OpenELEC 3.2, set up my wifi, then pushed the kernel & system + md5's to the update folder, and it successfully updated.
The system flies and is really really smooth, even with my large library in an external HD.
The problem is, my WiFi dongle that I have always used (f5d8053 v3) doesn't work, neither does the spare I have. After a couple of reboots it did work, then on the next boot it didn't.
Can anyone tell me how to pull a log file? I found the option in Setting to enable log - do I switch this on, then reboot to replicate the error, then SSH to get the log file? If so, where is it stored?
Yeah, thats right. You can read about the log here
http://wiki.xbmc.org/index.php?title=Log_file/Advanced
And location
http://wiki.xbmc.org/index.php?title=Log_file/Advanced#Location
(Linux $HOME/.xbmc/temp/xbmc.log)