Hi,
I tried multiple builds, but wifi didn't work at any of them. I found out that most probable reason is inabilty to get MAC address for wifi.
dmesg:
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
I tired to modify startup.txt, but no results. I found that similar issue was resolved for other htc devices (tilt 2, touch pro 2) by correction of wifi-nvram.txt. I couldn't find that file on builds for hd2.
It would be greate if anyone could you say which file is responsible for setting up MAC address for wifi.. Or what can I try else..
Thanks you!
What radio, wm versions and android versions have you tried? I've tried numerous builds and wifi has worked for almost all of them (if not all). I've had issues with data working but usually not wifi.
Wifi has worked on every build I've used which is 90% of the builds on xda
Sent from my HTC HD2 using XDA App
do u know what a radio is ?? I thought so ... search the forum for it and installl and use the latest then try again.
My hd2 is T-mobile US version
My radio is 2.15.50.14
Android build is MDJ FroYoSense -=Revolution=- 1.6 (tried with built in kernel and hastarin's one)
just in case, ROM build is 3.14.531.1 from T-Mobile, but I also tried Miri_Steve0007_Elegancia_V5.0_FINAL with the same results.
Actually I asked a person who doesn't have wifi problems to give me his firmware versions (rom, radio) and tried them by myself on the same android build he has. Results are the same: wifi doesnt'work.
Under WM wifi works good. Here is a link to the similar problem resolved for touch pro 2, tilt 2 and other devices: http://forum.xda-developers.com/archive/index.php/t-695230.html
Thanks!
az_registration said:
My hd2 is T-mobile US version
My radio is 2.15.50.14
Android build is MDJ FroYoSense -=Revolution=- 1.6 (tried with built in kernel and hastarin's one)
just in case, ROM build is 3.14.531.1 from T-Mobile, but I also tried Miri_Steve0007_Elegancia_V5.0_FINAL with the same results.
Actually I asked a person who doesn't have wifi problems to give me his firmware versions (rom, radio) and tried them by myself on the same android build he has. Results are the same: wifi doesnt'work.
Under WM wifi works good. Here is a link to the similar problem resolved for touch pro 2, tilt 2 and other devices: http://forum.xda-developers.com/archive/index.php/t-695230.html
Thanks!
Click to expand...
Click to collapse
you may have forgotten to copy bcm drivers when you changed kernels and that can kill your wifi.
malaeus said:
you may have forgotten to copy bcm drivers when you changed kernels and that can kill your wifi.
Click to expand...
Click to collapse
No, I have updated bcm4329.ko as described in readme file for kernel. Also I compared dmesg output and adb logcat for different kernels: they look similar.
logcat says: "Failed to disable WPA in the driver" while dmesg says "dhd_preinit_ioctl: Can't get MAC address, errno=-110" for both the kernels..
Thanks!
Just tested with different radios.. Results are still the same..
If wifi wouldn't work in WM, I though that it is a hardware problem.
Any thoughts are welcome!
az_registration said:
There is a file (startup.txt) which allows to specify mac adderss in 'Android' folder. Did you mean that one, or mac address might be specified in some other way?
Click to expand...
Click to collapse
Yes, but that's only there if you are using MAC filtering in your access point, or you're using multiple Smartphones with the same Android Build.
Just as a test to determine if it's in any way related to security settings in your Access Point, you could try to make your access point unprotected.....so NO WEP or WPA protection, SSID visible, etc.
If that doesn't work either, then I'm lost
Are you using MAC Filtering in your Access Point/Router ??
First time I tried to connect to my Access Point with Android, it didn't work either....untill I realised that the MAC Address on Adroid is NOT the MAC Address of the HD2. When I allowed the MAC Address of the Android Build on my Access Point I had no more trouble connecting, and my WIFI has worked ever since......
Be carefull however, different Android Builds use different MAC Addresses, so when you try a new Android Build you might experience the same issue.
Newer Kernels have an option to specify your own MAC Address during startup of Android.
Hope this helps.
Thank you for answering!
Pappagallo said:
Are you using MAC Filtering in your Access Point/Router ??
Click to expand...
Click to collapse
No, MAC filtering is not used. At least at one access point.
Pappagallo said:
Newer Kernels have an option to specify your own MAC Address during startup of Android.
Click to expand...
Click to collapse
There is a file (startup.txt) which allows to specify mac adderss in 'Android' folder. Did you mean that one, or mac address might be specified in some other way?
I did some more investigations and it seems that the problem might potentially be in wifi timeout settings, because there is a message in log (dmesg).
wlan: dhd_bus_rxctl: resumed on timeout
I downloaded kernel's sources to find out if this is the reason. Again, it is very weird, because wifi works in windows mobile.. Perhaps WM uses longer timeouts..
Another strange dmesg line is
wlan: firmware version: ver
perhaps wifi hardware has not been initialized correctly.. Just in case, below is related set of dmesg lines:
<4>[ 320.937774] wlan: wifi_set_power = 1
<4>[ 320.937835] htcleo_wifi_power: 1
<4>[ 321.236083] wlan: wifi_set_carddetect = 1
<6>[ 321.236114] htcleo_wifi_set_carddetect: 1
<7>[ 321.236145] mmc0: card_present 1
<6>[ 321.236145] mmc0: Slot status change detected (0 -> 1)
<4>[ 321.239715] wlan: Dongle Host Driver, version 4.218.204.2
<7>[ 323.794219] mmc0: queuing CIS tuple 0x91 length 3
<6>[ 323.794372] mmc0: new high speed SDIO card at address 0001
<4>[ 323.810180] wlan: DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 326.055175] wlan: dhd_bus_rxctl: resumed on timeout
<4>[ 326.055297] wlan: firmware version: ver
<4>[ 326.066162] wlan: Return_dpc value is : 0
<4>[ 326.066314] wlan: stop poll
<4>[ 328.065277] wlan: dhd_bus_rxctl: resumed on timeout
<4>[ 328.065399] wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
<4>[ 328.065490] wlan: dhdsdio_probe: failed
Thanks again.
Something went wrong when quoting a part of your question concerning the startup.txt file, so for some strange reason my reply is on the 1st page...(at least when I'm looking at your thread).....
Anyway, the MAC Address you can specify in the startup.txt file can be used when you ARE using MAC filtering and/or you have multiple smartphones using the same Android Build.....so you don't have duplicate MAC Addresses on your network.....
As I'm not a developer, I'm not able to help you with your debugging lines....however, if you want to be sure that it's not some kind of security setting, you could try to remove all security from your Access Point, so NO WEP or WPA, SSID visible etc.
If that doesn't work either, then I'm lost
Only time I didn't get a WIFI connection was because of the MAC Filtering in my Access Point. When that was corrected I never had problems getting a connection on WIFI.
Good luck.
Pappagallo,
I tried to turn off all security, but no effect. Anyway, thank you for the advice I just don't know to to try else...
Another suspicious line in dmesg is wlan: firmware version: ver.
It seems that wifi is not initialized correctly in Android... It would be interesting to see this line for devices with working wifi.. But to do that terminal emulator or android sdk are needed..
Can anybody show dmesg and logcat when wifi is turned on? I would be very appreciated.
Thank you in advance!
the same problem
Exactly the same problem, and I've experienced most Roms and when I return to the Windows system, the Wi-Fi works.
We need a real expert.
any help
I noticed that this problem devices in T-Mobile (TMOUS - PB81120 SS-B3)
Related
Hi,
I tried multiple builds, but wifi didn't work at any of them. I found out that most probable reason is inabilty to get MAC address for wifi.
dmesg:
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
I tired to modify startup.txt, but no results. I found that similar issue was resolved for other htc devices (tilt 2, touch pro 2) by correction of wifi-nvram.txt. I couldn't find that file on builds for hd2.
It would be greate if anyone could you say which file is responsible for setting up MAC address for wifi.. Or what can I try else..
Thank you!
* reposted from HD2 Android development.. It seems I've tried everything I could..
Hi All,
I'm trying to resolve an issue with wifi, that doesn't work in android but does in windows. So I want to repean configuration of wifi in android. So far I found the following items:
nvram.txt => windows: /windows/ android:/proc/calibration
BCM4329B1_002.002.023.0436.0439.hcd => windows:/windows android:/sytem/etc/firmware
There is also a file 'fw_bcm4329.bin' analogues of which I couldn't find. Does any body know what this file is responsible for? Are there any other files to configure wifi?
Thanks!
ps. just in case, my device is htc hd2
What do you need to configure in android?
mdebeljuh said:
What do you need to configure in android?
Click to expand...
Click to collapse
I need to make sure that the wireless hardware (bcm4329) in android has exactly the same configuration as in windows mobile. I thought that having firmware (*.hcd file) and config file (nvram) is enough. But it still doesn't work in android. It seems that the hardware is not properly configured, since neither firmware version nor MAC address are accessible..
dmesg:
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
If you need to copy mac address from windows to android you can use hastarin kernel and configure mac address through cmdline parameters
I suspect that the problem is deeper (firmware vesion could not be read).. But I will try now to install the kernel you mentioned. Thanks for help!
Just updated the kerner... Performed all the steps for "if wifi doesn't work", but no results - wlan is dead in android..
Do you have Error message? If so you need to update tun.ko and bcm4329.ko modules
Error messages are the same as with the old kernel, I mean there is nothing about miscorrespondance of *.ko files and kernel.
I noticed one interesting thing.. When I specify parameter for loading bcm4329 modue (via insmod) it works even when I specify incorrect nvram_path.. So I suspect that this parameter is just ignored or I specify it incorrectly. Anyway /proc/calibration is used even if I specify my path.
It would be nice to replace it with my data, but I don't know where it is loaded from and it seems to be a big deal to update it dynamically.
I installed MDJ android froyo build 4.3 and everything was working well.
i had to enter ip address for a certain network at work, everything got messed up, so i removed the ip address enteries i made (use static ip) and still needs ip for connecting, i also checked DLNA auto ip and nothing changed!!
keeps trying to connect (giving me obtaining ip address) and disconnects, doesn't want to connect.
i tried reinstalling android again but keeps giving me this damn problem!!!! i think there r some files not deleted
i tried connecting on WM, i found out that it doesn't connect also
what to do for that ****, really annoyed about that!!
TMOUS HD2 on stock Rom 2.10 and radio 2.08, WM 6.5 and recently installed android MDJ 4.3
Thanks in advance
sevoflurane said:
I installed MDJ android froyo build 4.3 and everything was working well.
i had to enter ip address for a certain network at work, everything got messed up, so i removed the ip address enteries i made (use static ip) and still needs ip for connecting, i also checked DLNA auto ip and nothing changed!!
keeps trying to connect (giving me obtaining ip address) and disconnects, doesn't want to connect.
i tried reinstalling android again but keeps giving me this damn problem!!!! i think there r some files not deleted
i tried connecting on WM, i found out that it doesn't connect also
what to do for that ****, really annoyed about that!!
TMOUS HD2 on stock Rom 2.10 and radio 2.08, WM 6.5 and recently installed android MDJ 4.3
Thanks in advance
Click to expand...
Click to collapse
You may need to enter correct APN settings and or change your DNS settings as well. Check my sig and thumbnail for more help.
Hi, guys
After flashing NAND Android, I found that the wifi mac address is : 00:11:22:33:44:55, and the BT mac address is :50:C3:00:00:00:00, any one can tell me how to change them ?
thx.
I've seen these possible answers:
Try changing the startup.txt from
Code:
set cmdline "nand_boot=0"
set cmdline "bt.mac=00:11:22:33:44:55 wifi.mac=00:12:23:34:45:56"
boot
To
set cmdline "rel_path=Android nand_boot=0"
boot
and
Code:
#Mdeejay FroYo Revolution v. 1.7
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "wifi.mac=00:11:22:33:44:55 bt.mac=00:11:22:33:44:55 nand_boot=0"
boot
NOTE: You need to repalce the 00:11:22:33:44:55 with the real MAC address or any of your choice...but if you're like me that have *ALL* security features turned on on your wireless router (MAC FILTERING, HIDE SSID, WPA2, 802.1X) then you need to use the real MAC address..
Click to expand...
Click to collapse
Problem is, both solutions mention startup.txt, which I simply do not see in the NAND setup folder...
Both are found in the MDJ FroYo Revolution v.2.1 threat...
I have not tested them, I would like someone to confirm this is working, someone who knows more than me...
Any help and opinion on this topic welcome...
The post above only applies to SD, NOT NAND. I want to know how to change these too
bump
Thanks
I want to find out too!
How can I spoof my mac address?
some bloke has the same mac addr as me @ the uni so I need this or I can't get online.
The uni defined that you have to REG your MAC first;
so that f¨¨king idot regged first, and now I am cut off because of him.
Anyone an idea where in nand the BT & MAC settings are stored? can this be changed with root explorer? or with cmd line?
HectiQ said:
I want to find out too!
How can I spoof my mac address?
some bloke has the same mac addr as me @ the uni so I need this or I can't get online.
The uni defined that you have to REG your MAC first;
so that f¨¨king idot regged first, and now I am cut off because of him.
Anyone an idea where in nand the BT & MAC settings are stored? can this be changed with root explorer? or with cmd line?
Click to expand...
Click to collapse
download the terminal emulator free from the android market.
-go to your setting and find out what your mac address is. write it down.
-open it
-if theres a question mark at the left of the cmd line write "su", if theres a # you can skip it
-write "ip link show"
-search for the expression having your mac address. at my phone it was eth0
-write "ip link set eth0 address 11:22:33:44:55:66" or any other mac
-write "ip link set eth0 broadcast 11:22:33:44:55:66" or any other mac
now your mac should be changed. remember that this method doesnt work at every phone, at mine it didnt work.
i read some about linux terminals to find that out, pls dont post things like "you stole it blabla".
hope that it works for you,
sallal
Correct me if I'm wrong but the Wifi Mac address has been fixed long ago, I have (I suspect) my real mac address on my phone no matter what rom I use, its the BT that I cant find how to change, even though I have a kernel with the solution but no one willing to help.
And in NAND versions of Android, you change your WIFI Mac address by changing the value in the calibration file, open it as text and change to what you need.
modules name changed. Now run stable
Awesome
I will merge this in and if all goes well, will start gutting the areas I could not before.
Ill report back.
Great work!
pershoot said:
Awesome
I will merge this in and if all goes well, will start gutting the areas I could not before.
Ill report back.
Great work!
Click to expand...
Click to collapse
dhd.ko filename modified to bcm4329.ko
put in /system/lib/hw/wlan
I tried many ways, last modified module name, unexpectedly successful, it is funny.
Chenglu said:
I tried many ways, last modified module name, unexpectedly successful, it is funny.
Click to expand...
Click to collapse
it appears to be working well from initial observation.
i too outputted the module as dhd, but it still froze up, no matter which method i took.
can you please share the other changes that you have made from the last posting?
ill diff things out now, upgrade to the latest and commit.
thx. great work!
pershoot said:
it appears to be working well from initial observation.
i too outputted the module as dhd, but it still froze up, no matter which method i took.
can you please share the other changes that you have made from the last posting?
ill diff things out now, upgrade to the latest and commit.
thx. great work!
Click to expand...
Click to collapse
i did notice it disconnect while being idle for a while. but that's ok.. that could be coincidence and/or an isolated case with my setup.
I use a new version of the driver code, modify and compiled, try several Dflags, the result is the timeout or hardlock, so I deleted all code.
Then, I started from scratch,redownload code from http://nv-tegra.nvidia.com/gitweb/?p=android/platform/system/wlan/broadcom.git, Made a small change, even successful.........
upgrade complete.
<4>[ 3654.777016] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 3654.979564] Firmware version = wl0: May 17 2010 22:38:50 version 4.218.223
.1
<4>[ 3655.177291] wlan0: Broadcom Dongle Host Driver mac=--:--:--:--:--:--
<4>[ 3655.187516]
<4>[ 3655.187527] Dongle Host Driver, version 4.218.248.18
<4>[ 3657.545885] STA connect received 1
it was the combination of your makefile flags.
let me monitor this some more, and if all holds stable, ill post src to my git.
then ill work towards bringing this section (removing pullup, keeping sdio lines high, and possibly going towards wifi abstraction and not gpio reset) forward.
the upgrade seems stable to me!
https://github.com/pershoot/gtab-2632/commit/c7ba24f773539dc986b0a0b532e83d1272fd66b4
pershoot said:
the upgrade seems stable to me!
https://github.com/pershoot/gtab-2632/commit/c7ba24f773539dc986b0a0b532e83d1272fd66b4
Click to expand...
Click to collapse
good work...
Chenglu said:
good work...
Click to expand...
Click to collapse
you as well
Is possible to make this file able to be flash? Prefer to do it that way so I can make sure I don't mess up nothing
lilgotti56 said:
Is possible to make this file able to be flash? Prefer to do it that way so I can make sure I don't mess up nothing
Click to expand...
Click to collapse
yes. flash my kernel.
Thanks, worked great for my kernel as well (2.6.32.9) but still can't enable IPv6. It would just give me an error on wifi. Any ideas?
http://nv-tegra.nvidia.com/gitweb/?...9;hb=900f1defbe1f39ca6af8356521961c249174f304
Update to FW version 4.218.248.6
Code:
<4>[ 403.288667] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 403.466861] Firmware version = wl0: Sep 15 2010 14:22:42 version 4.218.248.6
<4>[ 403.671056] wlan0: Broadcom Dongle Host Driver mac=00:27:13:f7:c6:58
<4>[ 403.679611]
<4>[ 403.679621] Dongle Host Driver, version 4.218.248.18
<4>[ 405.984640] STA connect received 1
<7>[ 414.933316] wlan0: no IPv6 routers present
Chenglu said:
http://nv-tegra.nvidia.com/gitweb/?...9;hb=900f1defbe1f39ca6af8356521961c249174f304
Update to FW version 4.218.248.6
Code:
<4>[ 403.288667] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 403.466861] Firmware version = wl0: Sep 15 2010 14:22:42 version 4.218.248.6
<4>[ 403.671056] wlan0: Broadcom Dongle Host Driver mac=00:27:13:f7:c6:58
<4>[ 403.679611]
<4>[ 403.679621] Dongle Host Driver, version 4.218.248.18
<4>[ 405.984640] STA connect received 1
<7>[ 414.933316] wlan0: no IPv6 routers present
Click to expand...
Click to collapse
Hi, pushed fw_bcm4329.bin and fw_bcm4329_apasta.bin to /system/lib/hw/wlan but I still end up with 4.218.233.1 any ideas?
If your using what's at nvidia for. 32 line for broadcom, that's the version you'll be on (what shipped with our tabs (233.1)). So that is correct what you have.
If your using my source (which I modified from AOSP; check git for mods/details done for our specific platform; check vision-2632 repo for further changes done to AOSP src), then you will get the latest version published to date (248.18).
You can test both sets of firmware independently to see which plays better with our specific tabs and specific use case(s).
Chenglu, all is well with FW update so far?
Plays ok with our specific hardware?
Ill play as well when I get a free minute and report back of any anomalies.
Good team work!
pershoot said:
If your using what's at nvidia for. 32 line for broadcom, that's the version you'll be on (what shipped with our tabs (233.1)). So that is correct what you have.
If your using my source (which I modified from AOSP; check git for mods/details done for our specific platform; check vision-2632 repo for further changes done to AOSP src), then you will get the latest version published to date (248.18).
You can test both sets of firmware independently to see which plays better with our specific tabs and specific use case(s).
Click to expand...
Click to collapse
Thanks, that cleared it up Looks like I got my Firmware up to 248.6 but my dongle driver is stuck at 233.1. I'll try IPv6 with this and see how it goes.
GOT IT!! Working IPv6 with good range