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?
Related
I just loaded my AT&T version with cyanogen 5.0.5.3, and the wireless tether app does not work.
No matter the security settings I use, it always shows unsecure network on my laptop (OSX, Ubuntu and Vista).. If I set it to unsecure in the app, it still does not connect.
I have never used it before, but I am assuming the cyanogenmod kernel has the required bits for the app to work properly.
Am I missing something stupid?
Thanks
-G
ghost_o said:
I just loaded my AT&T version with cyanogen 5.0.5.3, and the wireless tether app does not work.
No matter the security settings I use, it always shows unsecure network on my laptop (OSX, Ubuntu and Vista).. If I set it to unsecure in the app, it still does not connect.
I have never used it before, but I am assuming the cyanogenmod kernel has the required bits for the app to work properly.
Am I missing something stupid?
Thanks
-G
Click to expand...
Click to collapse
Did you turn off USB tethering?
hotweiss said:
Did you turn off USB tethering?
Click to expand...
Click to collapse
Never turned it on, and verified it is off...
how did you load the apk?
lpasq said:
how did you load the apk?
Click to expand...
Click to collapse
Downloaded to SD, and installed from browser download screen...
ghost_o said:
Downloaded to SD, and installed from browser download screen...
Click to expand...
Click to collapse
you may want to adb push method or adb install -r method instead. reboot after install. or try my rom linked in signature.
if you don't know how to use sdk's adb, do a search here on xda for one of the many basic tutorials or ask for details.
lpasq said:
you may want to adb push method or adb install -r method instead. reboot after install. or try my rom linked in signature.
if you don't know how to use sdk's adb, do a search here on xda for one of the many basic tutorials or ask for details.
Click to expand...
Click to collapse
Will do adb.. I have the linux sdk..
Thanks, will post back with results..
OK, installing with adb has the same effect.
There are posts from the google code pages where this has happened in the past (last year though), so I doubt related..
Out of ideas...!
eth0 IEEE 802.11-DS ESSID:"AndroidTether" Nickname:""
Mode:Ad-Hoc Frequency:2.437 GHz Cell: 3A:4E:3D:88:EC:41
Bit Rate=72 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementmode:All packets received
Link Quality=5/5 Signal level=-57 dBm Noise level=-57 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with WEP set.. It must have something to do with wpa_supplicant somewhere.. I'll keep digging...
maybe it might have something to do with atnt not able to do it throught there network. like us tmobile users can use data while on the phone? dont know alot but that could be a possibility
Nah, wpa_supplicant is not negotiating wep for some reason. I just replace the wpa_supplicant.conf file with a very generic open key WEP config and it still does not work..
I need to dig through my broadcom nda's and find this chip, and see if I can use the firmware.. I'll just load it up in AP mode and run hostapd and be done with it....
Ad-Hoc just plain sucks, almost as much as wep...
Cant find find wireless apk anywhere can someone please give me link
ttieder said:
Cant find find wireless apk anywhere can someone please give me link
Click to expand...
Click to collapse
http://lmgtfy.com/?q=android-wifi-tether&l=1
deprecate said:
http://lmgtfy.com/?q=android-wifi-tether&l=1
Click to expand...
Click to collapse
lmgtfy.com - that was awesome - my family members are gonna feel like idiots asking me questions now!
I had not heard of that site before.
Regarding wep-encryption & CM 5.0.5.x:
http://code.google.com/p/android-wifi-tether/issues/detail?id=292
So, wep-encryption is broken (no idea why) on the latest cyanogenmod-build. Please use CM 5.0.4.1 - it works flawlessly there.
I will take a closer look the next days ... but it's hard to tell what is causing this - I don't know which changes were made on CM.
By the way ... why was this topic moved to Q&A
This is definitely an issue which needs to be solved and should stay in development!
Thanks - I googled for quite a while, and never came across that info. Tethering is not that critical (unless I am travelling), so I will just wait for a fix sometime.
I would have figured other in this forum would have hit it though?!?!?
-G
I've installed 5.0.5.3 and downgraded the kernel which came with 5.0.4.1 - and it start working again! So, I would say that this issue is related to the latest kernel (2.6.33.1)!
I've created an issue on cyanogemod:
http://code.google.com/p/cyanogenmod/issues/detail?id=1217
i have wifi tether pre 8 on latest CM mod and its working great, wep works, and no errors in log.
I am having the same problem. I have both a nexus one and motor milestone. Tethering on milestone doesn't have problems but my nexus can't seem to connect as well no Sep security. I can see the my SSID, anyone can help?
There are obviously factors that differ between devices somehow. I too can change kernels and the issue goes away. Something is "missing" somewhere. A git pulled vanilla 2.6.33 kernel works just fine when booting the zimage from fastboot..
I have not looked at the cyanogen .config or wireless module source yet to see any modifications that would effect it...
I'm more interested in the module working in AP mode now that the driver supports it, and have been working on that...
-G
Hi all,
trying to get my feet wet with some android hacking and thought getting my AR.Drone to work with my legend would be a good start. It requires connecting to the ad-hoc network created by the drone. The normal way is to edit /system/etc/wifi/tiwlan.ini as described e.g. here: projects.ardrone.org/boards/1/topics/show/1098 but /system doesn't seem writable even though I have root. I then found this app for the desire: code.google.com/p/desire-adhoc/ but the legend has a different wifi chip, so it didn't work. Attempting to reproduce what that app does I did
$ adb shell
# su -c 'insmod /system/lib/modules/tiwlan_drv.ko'
insmod: init_module '/system/lib/modules/tiwlan_drv.ko' failed (No such file or directory)
even though that file definitely exists. Am I missing something here, or is that part of the annoying restrictions still present even on the rooted legend? Ad-hoc wifi must be possible somehow, the wifi-tether guys managed to get it to work. Unfortunately their code is a bit over my head. Any pointers?
thanks
-felix
Do it from recovery mode. We don't have access to /system in normal usage of phone (you get used to it).
okay, I guess I have to learn how to bake my own update.zip.
still curious though, why am I getting "no such file or directory" if it's clearly there (and a similar method seems to work on the desire)?
I also tried this:
forum.xda-developers.com/showthread.php?t=754961&highlight=legend
Which is a quite cleverly hacked wpa_supplicant, but that resulted in no wifi at all any more, even though the patched supplicant is officially the same version. strange.
any clue how the wifi-tether guys do it?
No, those command work. Boot your phone to recovery mode, then mount the /system partition from the ClockworkMOD menu. then you can execute your commands, they should do it.
Also, questions like this shouldn't really be in the development section. Just so you know.
You got it all wrong guys... first you dont need to su -c as you already are root. Second... you need to load sdio.ko prior to tiwlan_drv.ko. And no we do not perform these in recovery mode
I thought he was editing files... Oh well, I'll read more carefully in future. Sorry guys.
EDIT:
Yeah, look:
The normal way is to edit /system/etc/wifi/tiwlan.ini as described e.g. here: projects.ardrone.org/boards/1/topics/show/1098 but /system doesn't seem writable even though I have root.
Click to expand...
Click to collapse
So he could edit from recovery mode. But, I was still an idiot, I said to do the insmod things from recovery. I am very sorry for wasting time here, I'll learn to read carefully and give proper answers.
Sorry
TheGrammarFreak said:
Also, questions like this shouldn't really be in the development section. Just so you know.
Click to expand...
Click to collapse
hmm, okay. I figured since I'm _trying_ to develop something...
well, next time.
BlaY0 said:
you need to load sdio.ko prior to tiwlan_drv.ko.
Click to expand...
Click to collapse
aaaahhh, that got me a bit further thanks! very confusing error message...
so module loading works now, but the phone just reboots a few seconds after I set
"iwconfig tiwlan0 mode ad-hoc"
any further advice?
Also I guess the confusion was my own fault since I rolled three different ways of doing one thing into the same post...
Oh man, I've said all the wrong things today. I'm so sorry. I'll just leave this thread now.
sanktnelson said:
so module loading works now, but the phone just reboots a few seconds after I set
"iwconfig tiwlan0 mode ad-hoc"
any further advice?
Click to expand...
Click to collapse
Yes. Loading modules just isn't enough in our case. You need to load firmware too before you bring interface up otherwise your system will reboot
Check Gratiend ROM thread or look into init.legend.rc for hints on firmware loading...
thanks. found this
/system/bin/tiwlan_loader \
-f /system/etc/wifi/Fw1273_CHIP.bin -e /proc/calibration \
-i /system/etc/wifi/tiwlan.ini
after googling init.legend.rc. doesn't seem to make a difference though. also tried using tiwlan.ini from the wifi tether guys, but no luck. device still reboots after setting ad-hoc mode. I guess I give up, there's no-one answering to my question on the wifi-tether google group either. i guess just because it's open source doesn't mean it's for the uninitiated...
Try sleep for 1 or 2 seconds after you load firmware, then bring interface up or start wpa_supplicant.
I you are using patched wpa_supplicant I guess you will have one more obstacle. It supports only wext aware devices and I guess our driver is not wext aware...
I solved the problem by installing Cyanogenmod (all other tries failed)
Sent from my Legend using Tapatalk
BlaY0 said:
Try sleep for 1 or 2 seconds after you load firmware, then bring interface up or start wpa_supplicant.
I you are using patched wpa_supplicant I guess you will have one more obstacle. It supports only wext aware devices and I guess our driver is not wext aware...
Click to expand...
Click to collapse
I enter the commands by hand, so there's already a delay in between. And I'm doing this by hand precisely because the patched supplicant didn't work on the legend. I guess now I know why. Thanks for all the advice though.
exicar said:
I solved the problem by installing Cyanogenmod (all other tries failed)
Sent from my Legend using Tapatalk
Click to expand...
Click to collapse
I had a CM6 nightly installed and toyed around with it a bit, but I actually use my FM radio (I know, barely anyone else does...) so I need to use a HTC ROM. liked the CM6 in a lot of other respects though. still out of the question for now.
Also I would eventually like to contribute whatever comes out of this to a proper AR.drone app that requires root and nothing else.
Hey, guys after hours of thinkering it seems i devised a fix (at least a temporary, i guess it can be better implemented), but still wifi works with turned on radio.
I will not be doing any scripts or whatever.
DISCLAIMER
THIS IS ALL ON A BASIS OF INFORMING PEOPLE
I AM NOT RESPONSIBLE FOR ANY DAMAGE, LOSS OF DATA, OR BRICKED DEVICES IN CONJUNCTION OF TRYING OUT THESE STEPS
DO IT ON YOUR OWN RISK.
K now the requirements:
1. nonworking sim card (or att sim card)
2. RSD lite 5.0
3. stock 4.1.2.6 SBF flash file
4. Installed drivers on the computer for rsd
5. GladRoot http://forum.xda-developers.com/showthread.php?t=1016060 than you very much Ririal
6. OTA update
7. Working adb shell (there are other ways too but i prefer this one so ill write how i did it)
8. SQL editor, i used SQLite database browser (get it online its freeware)
9. titanium backup (if you wish to backup things, YOU MUST NOT RESTORE the [SETTINGS/BLUETOOTH] Settings Storage 2.2.1 however.
10. turned debug mode on when using adb
The process:
1. backup your data
2. Flash the stock image with RSD lite as its written here http://forum.xda-developers.com/showthread.php?t=991072 thank you kennethpen
3. put in the nonworking/att sim turn on the phone use wifi to configure motoblur
4. do not download the update yet
5. obtain root as described here, use the 1.5.7 method tho since we will be updating the ota http://forum.xda-developers.com/showthread.php?t=1016060
thanks again ririal
6. download and install ota update
7. do the afterupdate with the GladRoot
8. still on wifi, set up google account, update market gmail etc.
9. use adb/root explorer to copy the /data/data/com.android.providers.settings/databases/settings.db file to your sdcard into a directory you made before (name doesnt matter) example:
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard-ext/test
10. put phone into airplane mode, turn off phone
11. put in your sim card, turn on
12. let it boot and wait a min or two
13. before sliding press and hold the off button and choose airplane mode (it is IMPERATIVE that airplane mode is turned on)
14. sign into motoblur again (wifi should still work - turn it on tho since your in airplane mode)
15. repeat step 9 but copy to a second directory (lets say test1)
16. turn airplane mode off - you will loose wifi and sign into motoblur again
17. repeat step 9/15 but copy to a third directory (lets say test2)
18. copy the files from test2 and test1 to your computer - obviously to two different folders (use mass storage setting or adb pull)
19. open up the settings.db with sqlite from the not working config (in our case the one in test2) go to browse data and table secure
20. find the entry wifi_country_code and the value will be the one of your country (at least so it was with me), change that value by double clicking on it to US
21. Save the file
22. copy to your sdcard via usb to a directory lets name it "works"
23.turn off your phone, and put in the nonworking/att sim card, power it up
24. register motoblur again blah blah (ye its annoying there are ways around but that comes later and we needed it for the ota update)
25. turn the airplane mode off (its imperative to do so)
26. now we use adb again:
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/works/settings.db .
chown system settings.db
chgrp settings.db
chmod 440 settings.db
cd ..
chmod 555 databases
exit adb shell with ctrl+d (in linux dont know about windows)
27. turn off phone, put in your sim card, turn on phone, register motoblur
28. most probably wifi will work for a moment than it will stop working and youll get a notifiaction lost data connection and something on (at least so it was for me)
29. use the wifi toggle on/of button to turn off and on the wifi a few times, than at the third or fourth time turn it off than on than immediately go into the browser and click on refresh as soon as you see the wifi icon in the notification tab. WiFi should work now, you can even turn it off and on with the wifi toggle button and it still works.
30. ANOTHER WARNING THO, THERE ARE QUITE SOME DRAWBACKS TO THIS METHOD (WHICH I HAVENT DISCOVERED ALL YET, TO BE HONEST BUT IM SURE THERE ARE QUITE SOME - SINCE WE DO NOT ALLOW THE SYSTEM TO EDIT THE SETTINGS.DB ANYMORE - BY CHMODDING THE PERMISSIONS), AN ISSUE I SAW IS THAT YOU CANNOT GO INTO AIRPLANE MODE ANYMORE - that is because the airplane mode state is saved in the same settings.db as the setting that blocks wifi, and if you just change that one and dont write protect the file and the databases folder the system just overwrites it again, so for now this is it.
AGAIN this is all on your own RISK, i cannot bi liable for anything out of the ordinary that happens, damages or whatsoever your phone or even you.
So now im awaiting responses if it works for you guys.
Oh and a few of the steps are just for backup purposes
Many thanks goes to Azuzu aswell, he was of great help all the time.
What about for the Canadian Bell Atrix can you please help us.
When I insert non working sim card into the phone, wi-fi working only once, after booting. Then when phone is going to lock, wi-fi is sleep and never work again. Is it instruction help to work with wi-fi during the day without rebooting? Thanks for instruction!
---
All is fine with Wi-Fi when it in Motoblur...
What about GPS?
May be needed to add GPS ON in this instruction?
Thanks guys. Its work for me. But too much DRAWBACKS. GPS does not work, settings are not saved
my friends you figured it all out like i did after a day of testing.
As i already said before there are some rather big probles that arise with this method, however for now this is the only way i found to having a working sim +wifi working.
Basically all the issues arise from the settings menu, since the settings from there are stored in the setting.db file that we disallow changing, due to this fact, i have devised a rather simpler way to do all the above + apply your specific settings - however you still wont be able to change them once you change the permissions.
1. gps state cant be changed as reported
2. ringtone/notification tone cant be changed
3. USB mode is stuck in NONE mode or the one you changed it to before doing read only
4. Possibly you cant pair new BT devices (havent tried that but i assume it might happen)
5. cant change lockscreen type (so if you pick fingerprint afterwards it wont change the lockscreen)
6. more possible problems, still if you want wifi you will endure some of those, they are however rather easy to fix, for people who dont change things all the time.
7. i found out that you have to turn off and on wifi (with the widget or in the networks menu) 2 times to make it work and it stops working if your phone changes the network from 3g to 3g or vice versa, however you just turn wifi off and on again and its fine (eventually you can just set your phone to 2g only or 3g only - either the dialer method or edit a config file - ill post that another time)
8. airplane mode not changing as stated above
So i did it like this this time:
lets assume you already have the phone 1.5.7 rooted (you can even have 1.2.6 rooted but the ota update brings nice features like longer battery, better fingerprint reader etc) and activated. NOW THIS SHORTENS THE PROCESS BY FAR and improves on the things that werent working before, it might lower battery life minorly but, well mine is still at 70% after ~16 hours so )
YOU WILL HAVE TO DO THIS ONLY ONCE (well at least until you want to change your ringtone hahaha )
1. Put in your working sim (just into the rooted atrix and the databases dir has to be read write like before, if you followed my guide above you have to go with adb shell to /data/data/com.android.providers.settings and write chmod 755 databases)
2. turn on phone in normal mode
3. set all your settings as you like and i really mean all - ringtones notifications - everything you can think of
4. turn all the networks on - wireless (it wont work but the state has to be on), bluetooth, gps - the thing is you can always turn them off, but if you write protect the file with them off you cant turn them on properly
5. pair your bluetooth devices (all of them) - havent tried yet if necessary but i think it is
6. reboot phone into normal mode, assure yourself that all the things are as you like
7. connect phone in debug mode, and set usb to none (it will stay in the none state, but you can always copy stuff with adb over, to your sdcard/internal phone mem as opposed to choosing mass storage mode where you have no adb access to them, but that is your choice ( you can manually change the state in the settings.db before making it read only, but i wont go into those details now)
Code:
adb shell
su
cd /sdcard-ext/test
cp /data/data/com.android.providers.settings/databases/settings.db .
ctrl+c/d to exit shell
8. connect phone in mass storage mode, open the settings.db file in the /sdcard-ext/test with the sqlite editor go to the brose tab, and secure, change the wifi_country_code value to ALL (last time i wrote US but ALL works fine so its more relaxed), save it
9. change the usb connection mode back to none
10. failure to chown and chgrp the settings.db to system and chmod it correctly can results in a soft brick
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/test/settings.db .
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
cd..
chmod 555 databases
reboot
11. the phone shoudl reboot now with all the networks turned on, you can use the widgets (or int he wireless menu) to turn off wifi and bluetooth (tested it myself and it works), havent tested gps turning off yet, but its no problem since gps turns on itself only when apps use it (maps etc, weatherbug can use it aswell, so might check into it if its permanently turned on than)
12. turn wifi off and on 2-3 times, than turn it on, it should be working now
Thanks for testing this out to confirm that it works at least
Anyhow if someone might get a clue what issues the command to change the wifi_country_code hes encouraged to share, so we can only fix that problem and there wont be these side effects than
you can however change all the settings by just editing the settings.db with the sqlite editor manually, youd have to figure out all the parameters and values yourself (some are fairly easy - for instance for usb mode, some can be rather hard - for instance ringtones, cuz you must have the path and everything)
EDIT, YOU CAN LEAVE OUT THE PAIRING BLUETOOTH DEVICES STEP, pairing works, i just tried it with an apple bluetooth kb, and its fine.
RacecarBMW i cannot say anything with certainty, since i dont have one to test it on, but probably the same method would work for the bell atrix (use the method in the post above, with the ALL value for wifi_country_code), however you have no sbf to flash and its way more dangerous that you will create a softbrick, so please be very careful and its all YOUR RESPONSIBILITY. I AM AND WILL NOT BE LIABLE FOR ANY ADVERSE EFFECTS.
We need to lock only some rows in db file or creating daemon which would keep these lines in memory. Is it posible with SQLite?
crnkoj Please change on step 10 in listing:
cd /data/data/android.providers.settings/databases
to
cd /data/data/com.android.providers.settings/databases
I do all steps and my GPS works fine... Thanks
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
loggin111 said:
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
Click to expand...
Click to collapse
you can just enter to another folder to /data/data/ directory with cd and run ls -l to view directory permissions.
chmod 755 databases
and something like 755 for settings.db
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
1.5.2
crnkoj said:
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
Click to expand...
Click to collapse
hi
does it work with 1.5.2 rooted?
i flashed sbf back from unroot 1.5.7 to 1.2.6 , i didn't gladroot because i had not wifi for update & after update.bat
so i stopped @ 1.5.2 & i cannot update anymore, please help me to activate my wifi.....
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
hey guys what wifi issues? i have a ATT on vodafone UK and i dont seem to see any issues.
crnkoj said:
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
Click to expand...
Click to collapse
Hi can this fix be on a custom rom? i mean it will be included on a custom rom..
ronaldo, use search ... http://forum.xda-developers.com/showthread.php?t=1010942&page=3 lucky you arent one of us who have this issue.
emorej, if you read my first post, it says i wont be doing any scripts/cwm flashable updates/custom roms. If anyone wants to implement this in his rom hes free to do so, he has to be careful tho, since basiically the script that updates it, has to change only the wifi_country_code ALL and than make the databases folder read only, it must not copy over a generic settings.db since there are user specific things in it.
Jartyn and i are trying to figure a more source problem related fix for the issue, but that will take quite some time i fear.
Here is an even better solution from akizakian
http://forum.xda-developers.com/showthread.php?t=1058260
Simplest Solution
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Mate you are mistaken, its two totally different issues you and i are talking about, yours is that 5ghz isnt working, mine is that wifi isnt working in certain countries at all. by copying the files you supplied my wifi again stops working, because there is a country lock within the moto atrix wifi drivers (the version doesnt matter, may it be 1.2.6, 1.5.2, 1.5.7 or 1.8.3, the issue you fixed with your method is only the nonworking 5ghz on the 1.5.2. leaked sbf)
ceo.mtcl said:
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Click to expand...
Click to collapse
The LG Optimus wifi drivers fixed my simunlocked wifi problem in qatar.
The other solutions that were being thrown around did not.
seems moto is gonna fix it with an update:
https://supportforums.motorola.com/thread/50598?start=15&tstart=0
Hello xda-kaiser-android community
My configuration is :
SDCARD with 4 partitions :
FAT16 with Haret, zimage, inird, default.txt
SYSTEM (ext2)
DATA (ext2)
swap
I've managed to launch Android, and the phones does work.
Unfortunately, at the moment, some other things does not work :
WIFI : fails when getting the IP (so I scan WIFI networks well, but there is a problemn when creating the network interface...)
Modem : does not work..
Camera : not very important for the moment, but can become more...
So, I wanted to dump log files and try, with the terminal, to guess what is happening, but I COULD NOT MANAGED to SU ROOT (as a Linux user, I don't feel comfortable when I cannont be root on my personnal machine)...
When launching the "SuperUser" program the Applist is empty ?
When I set suid and root:root ownership of /bin/su on the SYSTEM partition, when SD mounted on my computer, It is not preserved when used inside Android...
After some inspection of the init scripts (see here under), my question is :
WHY SYSTEM PARTITION IS NOT MOUNTED with ROOT privileges ??
WHY is it chowned to the user 1000:1000 ?
Code:
# mount and set perms
$BB mount -o noatime,nodiratime -t auto $PARTITION $SD_EXT_DIRECTORY;
if [ "$?" = 0 ];
then
$BB chown 1000:1000 $SD_EXT_DIRECTORY;
$BB chmod 771 $SD_EXT_DIRECTORY;
log -p i -t mountsd "$SD_EXT_DIRECTORY successfully mounted";
Thank you for your comments, any help will be appreciated
Regards
Bernie
I overpost myself : My problem probably comes from the way I extracted the Froyo tarball to the SYSTEM partition...
I'll try again and inform you of my mistake.
Regards
why don't you try FAT32 instead of FAT16
bernie.discale said:
I overpost myself : My problem probably comes from the way I extracted the Froyo tarball to the SYSTEM partition...
I'll try again and inform you of my mistake.
Regards
Click to expand...
Click to collapse
Don't extract the froyo tarball. Just place androidinstall.tgz and androidupdate.tgz into the SDCARD andboot folder. Then, after you boot linux, touch and hold the center of the screen, and an install menu will appear. Then select your partitions, install system (and format data partition), install updates, and fix permissions, then exit. Android should start. Be sure your kernel (zImage) and drivers (androidupdate.tgz) match, and it also helps for the initrd.lzma to match. When wifi doesn't work, that usually means the driver is mismatched.
Hi Guys
Thnk you for your answers.
I got a more urgent issue than porting my kaiser to android : I've been forced to move my laptop back to windows again ...
So I must know workaround to dual boot linux (and, believe me, this install of windows is not the standard one)..
But A soon as I can, I will try the install stuff.
thank you again
Heydiho !
Things get better...
I caught eu-froyo-odex and installed it as is after entering the installation menu (launched by init ?)... The su command is now working. I have to tackle a few things now :
Wifi works even worse (now I clealry see an error, where, with the other distro, it was probably a permission issue)
Screen has still odd behaviors
Keymap issue with Keyboard arrows does not work in terminal
And camera to be confirmed
I'll dig the forum for topics on these subjects and get back if I'm really stuck
Best regards
Bernie
Hello
Things goes in the good direction :
Wifi is now ok (was not working with panel 1.. can this be correlated ?)
Screen works better with panel 2, but I'am still not sure if mine is 2 or 3)
Keymap Fixed : was only a matter of using bash insted of default busybox's shell
camera is not working
GPRS modem not working
Battery consumption is high with system on sdcard
Stay tuned !
I am working on a couple of things, specifically a "build.prop" mod and adding a "gps.conf" file to /system/etc, which is just a list of AGPS servers and to fix some GPS issues.
The modded build.prop that I have reworked adds some dalvik cache lines and "sleep mode" lines, as our Kaisers don't have a sleep mode implemented.
Camera and GPRS can be associated with the radio rom installed. I found that on my specific device, radio 1.70.19.09 allowed GPS and data to work smoothly, but I would lose the phone after the first call and camera had just a dark green screen. 1.65.16.25 dropped GPRS but improved data speeds and allowed the phone to work as well as the camera.
YMMV but I would say wipe any trace of WM from that phone (support is ending this May) and go directly with Android via NAND install.
Hello guys
@PoXFreak
I still have some habbits on my WM (freeOTFE encryption, contacts and some other stuffs) that are still working well on WM, and I don't feel very comfortable in switching on full Android (I mean on NAND) while I'am not very used to use Android... I would have definitely preferred to have a working platform booting from sdcard before flashing the NAND, but you confirmed that some issues may be linked to the SDCARD install...
I'm stuck since the beginning of march with the GPRS modem, and I don't clearly understand what are you talking about (have to check what you mean by radio).
My problem is, at the moment, that I don't have any mean to debug : is there a way to activate logs for users spaces programs ? Where to find em ?
If there is a better way to debug, what is it ?
As always, thank you, in advance, for any answer.
I'll try by myself a soon as I can (and, during the last weeks, it was not the case).
Best regards
I will add, moreover, that I'am still not sure of my panel (2 or 3 !!!)
Regards
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.