Related
I am running frf91 and my hotspot is working. Every time I turn on the hotspot function of my phone and connect my computer, my computer sees it remembers the SSID and password but reports a higher number than the time before. For example my SSID shows 'androidap (5)'. Five is the number of times I have turned the feature on my phone and then connected my computer. I don't know if the problem is my phone or computer. I am using a dell latitude 6400 with win7 64bit.
It has something to do with your computer, more specifically - with bloatware that is most probably installed as WiFi control application. Nothing to do with Nexus. SSID doesn't change, otherwise you wouldn't be able to connect to it.
Thanks for your input Jack. My computer is recently formatted and I am only using the windows software to manage my wireless networks. I am not using any third party software. What kind of bloatware were you thinking? I am using Microsoft security essentials for antivirus but otherwise I try to keep things very clean. Maybe it's a driver issue? Any other thoughts?
Usually laptops come preinstalled with management SW from their manufacturer - including WiFi management apps that are bundled with the WiFi driver (Intel, Dell, etc). If you didn't install it and you're using the default Win7 networking - then my answer above isn't applicable.
Any chance of a screenshot showing this number?
Also, you could try changing the SSID, registering the laptop on the new network and checking if you're getting the same number increase as before.
michaelbart0n said:
I am only using the windows software to manage my wireless networks. .............Any other thoughts?
Click to expand...
Click to collapse
'bleedin Windoze again then !!
I have a Lenovo laptop with a fresh copy of Windows 7 Professional. No other WiFi management software.
I have this same issue. Everytime I WiFi tether, I get a new network connection with an increasingly higher number. It's not the SSID that changes, though. That's always the same. Just the connection name changes.
I prefer to just tether with USB, anyway. That way my phone gets a charge a the same time. I mostly use my WiFi tether for my iPad.
I have Win7 at home, I'll test it later.
Jack_R1 said:
Usually laptops come preinstalled with management SW from their manufacturer - including WiFi management apps that are bundled with the WiFi driver (Intel, Dell, etc). If you didn't install it and you're using the default Win7 networking - then my answer above isn't applicable.
Any chance of a screenshot showing this number?
Also, you could try changing the SSID, registering the laptop on the new network and checking if you're getting the same number increase as before.
Click to expand...
Click to collapse
Thanks again. I have tried changing the ssid and I am getting the same results. I have found that if I keep tether running on the phone and connect multiple times from the computer, the number doesn't climb. But when I toggle tether on the phone and connect it creates a new, higher number. Of course my mac friend can't reproduce this error with his ipad, all is fine there. I have reproduced this error on two win7 64 machines and an XP profession 32 machine.
The screenshot you requested is attached
I noticed this too even with USB tether. I am fairly certain that this is because your computer counts each connection as a different network because your phone uses dynamic ip addresses and that creates a different default gateway for your hotspot each time it is connected.
Ok, looks like it's creating a new "public network" each time you're connected to tethering.
I couldn't replicate it on XP, since XP doesn't create network profiles for connections.
This is a stock Android issue, right? Not something screwed up in just custom ROMs?
Can someone point me in the direction of the bug report on the Issues tracker? Or isn't there one?
It's because it is in a different IP range all the time.
You're worrying about nothing. It's simply a trivial number, nothing to even concern yourself with.
GldRush98 said:
It's because it is in a different IP range all the time.
Click to expand...
Click to collapse
No it isn't.
It's the MAC addres that changes every time.
Doesn't happen with the sense HTC hot spot or with barnacle.
It's incredible that no one has looked in to this annoying bug.
GldRush98 said:
You're worrying about nothing. It's simply a trivial number, nothing to even concern yourself with.
Click to expand...
Click to collapse
Wrong. Windows 7 takes 5 minutes to connect to the network when this happens, as opposed to the usual 10 seconds or so.
If it were just the number that had changed, nobody would care.
Further info on new MAC addresses
The Solutor said:
No it isn't.
It's the MAC addres that changes every time.
Doesn't happen with the sense HTC hot spot or with barnacle.
It's incredible that no one has looked in to this annoying bug.
Click to expand...
Click to collapse
To continue THE SOLUTOR's comment, I found this article that describes the new MAC address issue as it shows up in windows, but it also doesn't have a solution.
http://www.hanselman.com/blog/iPhoneTetheringPersonalHotspotShowsUpAAsANewNetworkEachTimePlusTheSmartQuoteIsSilly.aspx#2855ecae-2f14-4f40-a807-263e9798cc4c
A few days ago I ran into a problem. My wifi wasn't connected when I turned on my tab 8.9. When I try to connect to my own network, and get into the settings page, the option 'ok' is greyed out. This means that I can only 'cancel', and in that way not connect to my own network anymore. The same thing happens when I try to connect to another network. My device is not rooted, running 3.2, and it is running the most recent firmware. Restarting the device didn't solve it. Any thoughts on this one?
Bump, same problem, or at least similar.
Android Version 3.2
Kernal Version 2.6.36.3 ([email protected] #1)
Build Number HTJ85B
Wireless works on some networks and not others. B G N do not matter, it is random. Still running stock ROM, not rooted. I have tried reseting OS, no luck.
What it does it it finds the network, tries to connect to the network, fails, remembers the network, and the cycle starts over.
Hi guys,
do you get the 'Obtaining IP address' message when connecting? mine does that constantly on some networks, it gets stuck in a loop and simply will not connect. I've found out that this is due to the tab remembering an IP address it used to use and trying to re-use it every time it connects. That is of course not always possible and so it tries - fails - tries etc.
The way to fix this apparently is to delete the dhcp_list file which holds the remembered IP addresses, only issue is that I cannot find that file anywhere. I'm running AOSP Galaxian Soup on mine with motley kernel, my home wifi works ok (probably because the same IP address is available all the time), work wifi doesn't want to work at all.
Maybe one of the devs sees this and can shed a bit more light on whether the solution is correct or not.
Regards,
dsc.
I was eventually able to solve this in a very easy way. for one reason or another the tab only wanted to log in when the password contained a capital, so I changed the WPA preshared key to something that contained a capital and a number and it was working again. very strange, because it had been working perfectly for about two months before this problem occurred. hope this helps.
Hi,
I managed to fix it by selecting static IP. I've seen this suggested a couple of times but when using the tablet in horizontal position I could see the static/dynami selection. Turns out you have to rotate the table to vertical position to see it.
Regards,
dsc.
Thanks for the discussion. my main problem is that i can't set a static at my work network. it will work at home, but i NEED it to work at both, otherwise it does me no good. I will keep banging my head against.
I will check back to see if smarter people come up with a solution, and if i come up with somthing i will post.
Hi guys,
do you get the 'Obtaining IP address' message when connecting? mine does that constantly on some networks, it gets stuck in a loop and simply will not connect. I've found out that this is due to the tab remembering an IP address it used to use and trying to re-use it every time it connects. That is of course not always possible and so it tries - fails - tries etc.
Click to expand...
Click to collapse
This is my problem exactly.
Hi,
not sure if you've seen this (I think the original solution comes from here anyway):
[tried posting an url but it was blocked, try googling:
'Tab cannot get IP address for WiFi problem + recs'
and scroll down to zakaria's post]
Some people suggest trying static, even if it fails it might delete the previously stored IP address that the Tab is trying to connect with and get a new one which should work. What I did was connected to the Wifi with my laptop, checked the IP/DNS details and after slight mods used it on the Tab. I did try setting the static to something roughly correct, connecting and reverting back to dynamic, but it wouldn't have it
Regards,
dsc.
Banderdragon said:
Thanks for the discussion. my main problem is that i can't set a static at my work network. it will work at home, but i NEED it to work at both, otherwise it does me no good. I will keep banging my head against.
I will check back to see if smarter people come up with a solution, and if i come up with somthing i will post.
This is my problem exactly.
Click to expand...
Click to collapse
Have you checked with your work network whether or not it needs ca certificate?
or you could try to download wifi ace (advanced config editor) from the playstore, and set the settings from there
Quick background before the question: I upgraded my P1000 along with a friends' to Milestone #5 today. All went well, but we were experiencing WiFi problems. After fiddling around with things a bit, we checked the MAC addresses, and both devices had the same value. Deciding that we needed to change at least one, we did a bit of searching around, but couldn't find how to change it permanently.
After that, I did a search through the AOKP contents for the mac address, and found that the file /system/vendor/firmware/nvram_net.txt contained the line
Code:
macaddr=00:90:4c:c5:34:23
A-ha, I said. I'll just change the line to:
Code:
macaddr=00:90:4c:c5:43:32
on one of the devices, and we'll be set. After some adb pushing and adb pulling, it was changed. But when I did a reboot, I saw that my new MAC address was BC:47:60:A0:4B:44 instead (which differs on the last byte by one from my Bluetooth MAC address, by the way). Since it is different, it solved the immediate problem, but I am always worried about things that do not make sense. Where does this MAC come from? Is it random, or should I also find out where it comes from, and customize it?
Eventually, there will be three P1000s running here at home, so I need to ensure the MACs are different on all of them, so I think it is important for me to get to the bottom of this. Any help or suggestions for things to check out is welcome.
TL;DR: I need to control WiFi MAC addresses on P1000 AOKP Milestone #5. How do I do that?
usually, the wifi mac is just one byte different from the BT mac address. Its usual because i deal with a lot of devices(other than mobile phones and tabs) which have more than 1 network interface. Like a wimax modem, or a WIFI router.
These have two interfaces (wifi router). One is the wifi interface, and the other is the LAN interface (provided there is an option to plug in LAN connectors for physical connection).
In these devices, the MAC address differs in the last byte. Just one hex alphabet is different. So i think when you entered an address, it wasn't valid, so it went to it's original.
The wifi MAC address is also usually written on the SGTP1000 box which you get when you buy it.
Thanks for the info. It makes sense that BT and wifi have very similar looking MAC addresses if they are implemented by a single module. So, probably my MAC address is the one specified in the hardware. Unfortunately, only the IMEI is printed on the box, so I will never be sure.
I found a script on the ROM (/system/vendor/bin/set-macaddr) that does some interesting processing: among other things, it checks /data/.nvmac.info, and if it exists, it replaces the MAC inside the nvram_net.txt file I mentioned, and copies it to /data/.nvram_net.txt. Otherwise, it just copies the file without modification. What I am thinking is that the OS reports the MAC address in /data/.nvram_net.txt, and on my first boot the other file didn't exist, so it simply used the hardwired value.
Unfortunately, I couldn't find who runs this script, or who creates the /data/.nvmac.info, so I cannot really be sure. I am not certain that it is very important either. I will just keep an eye open on identical MAC addresses on devices, and I'll try to get them to change to the hardware values if it happens.
I've notice WIFI disconnect sometimes when Tab on sleep mode
it wont receive whatsapp and twits till i click power button then reconnect to wifi
I also have problem with Bluetooth mac address.
I'm trying AOKP milestone 5, with restock.
And now the CM9 Nightly, also with restock.
But in both cases, the original bluetooth mac adrress, and also wifi mac change values from the GB stock.
Has anyone idea about?
[HELP] Wifi & Bluetooth gone, no longer functioning (Found BT AND Wifi MAC in CP!)
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Cynagen said:
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Click to expand...
Click to collapse
Have you tried a different firmware?
The Dark Lestat said:
Have you tried a different firmware?
Click to expand...
Click to collapse
I've tried V10K, V10D, V20A, V20P, V21D, and V21E, none of them restored the bluetooth (original issue), and so far V10K, V20P, and V21E have not restored the Wifi.
On V21E under settings, it's always showing as "Turning off..." under Wi-Fi. So it's definitely a hardware lockup. Is there anyway to do a full hardware reset on these things? I don't care about opening it, I'm not with AT&T anymore so the phone is mine, and frankly, I just want it to work.
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
What ROM are you currently on? Baseband as well.
The Dark Lestat said:
What ROM are you currently on? Baseband as well.
Click to expand...
Click to collapse
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Cynagen said:
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Click to expand...
Click to collapse
I would say that you should try going back to FroYo and checking those addresses again.
The Dark Lestat said:
I would say that you should try going back to FroYo and checking those addresses again.
Click to expand...
Click to collapse
I've gone back to FroYo without any change to Wifi or Bluetooth, but I'll go back to V10K and check the CP again.
Explanation
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
Please Explain Tutty. I get into the hidden screen and tried the download and nothing was downloaded, this is my first smartphone and do no that there is no MAC address for the bluetooth device. it is the only thing not working. Thanks in advance for the help.
Hi,
is there a way to get always the same mac, because of that my mobile hotspot doesn't connect correctly.
I always have to add the new mac address to trusted devices.
I know a reboot is normally not necessary, but sometimes it happens, but this my cars fault.
Some tips?
Thanks
Frank
Somebody, Anybody?
Damn this is the only thread to show up with this problem when searching. Mine does it too
I emailed atoto they said their aware and working on the issue for the next update.
I guess you could wait or try to root and install a Mac id changer and set it yourself to stay the same?
Hi, this is now solved with the update released yesterday, check out the support site the update is big, so it won't go through the OTA.