[Q] AOKP Milestone #5 - WiFi Mac address - Galaxy Tab Q&A, Help & Troubleshooting

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?

Related

hotspot gives increasingly higher numbers

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

wifi problem in overcome 7 series v4.1.0

hi there i am having a problem with my sgt p1000 wifi just upgrade to 7 series 4.1.0 i noticed that my wifi connection is not stable...
Think is an hardware problem.because i have installed this rom and i have any problem with the wifi.
Galaxy Tab P1000-OVERCOME 7 SERIES 4.1.0
icy25 said:
hi there i am having a problem with my sgt p1000 wifi just upgrade to 7 series 4.1.0 i noticed that my wifi connection is not stable...
Click to expand...
Click to collapse
Get yourself over to the Overcome thread and READ through it. Your answer lies within...
No offense phlooke, but you've told a few people that, and I've already become a bit lost in the over 100 pages of posts in that overcome 4.1 thread. Unless you're gonna post a link to the page in that thread where the solution begins, how is your above post helpful?
I'm going back into that thread now, but I swear, it's full of a lot of duplicate commentary, side discussions, and very little of the content is useful. A mod should clean up that thread.
maybe this one?
http://forum.xda-developers.com/showpost.php?p=21180574&postcount=770
Overcome 4.1 wifi fix attached there by Alterbridge himself.
Well the reason the thread is so congested is because of the same questions being asked over and over again.
People are too damn lazy to do there own investigation.
If you can't be bothered to read the whole thread there's a search function.
Check the forum rules.
Lastly the post I made is helpful in pointing the op to the place containing the answer? Duh.
Sent from my GT-P1000 using XDA App
Overcome Series ROM's are awesome but I always have a screen problems on my TMO Tab. I get these little brownie prickles on my screen like a twinkling stars at night. I am not sure why, maybe it's because the LCD and RAM are under voltage. Normally, every time I flash a new ROM, I always flash back my modem.bin just to make sure that I get all the benefits of my carrier's. Right now, I use Chromed JQ8 Stock ROM with Dip7 Kernel. It's pretty much stable and fast. Chromed JQ8 and Dip7 Kernel combo works furiously fast and stable. No bugs and everything works wonderfully.
Actually not really, because if you read through the conversations on the Overcome 4.1.0 thread, that wifi fix doesn't work for many people. And now, as a new Overcome user (as of four hours ago), it doesn't work for me, either. I flashed the fix file from CWM and I still get an up, down, up, down and so on with the wifi connection. There needs to continue to be people asking some of the same questions about this, so that people like yourself don't give the mistaken impression that this problem is somehow "solved". I'm not putting you down, because I can tell from your posts on XDA that you really want to help when and where you can (as do most people on XDA including myself), but the fact remains that this wifi problem is NOT fixed, and at least for the time being, the more people who squawk about it on here or in the official Overcome thread, the more likely a true solution will present itself.
Because right now, there isn't one. The flash fix doesn't work for a lot of us, and I shouldn't have to tweak my router. That's a ridiculous notion. That, and I find myself moving from location to location, relying in a variety of wireless networks to connect to, and I certainly can't go and tweak every single router I come into contact with. It's unrealistic, and it's a *software* issue on the ROM. So a fix is possible. But isn't available just yet.
So this thread, and any other new ones... at least for the short term, they have the latent function of keeping the issue current and visible to the developer or others who might have the tech savvy to truly fix the issue.
personally, if I don't feel like helping, I will just move on.
I just don't understand why some people feel like policing the threads while not offering valuable info.
Take a deep breath and ignore the post.
As for the wifi problem, I wonder if it is modem related? It has to be either that or hardware related (batch issue with chipset?)
There is a small number of users with unstable wifi issue.
Small number of reported people with this issue. Who knows how many it actually affects, but more than three is too many. I can't see why it would be hardware related, since the devices in question work fine prior to flashing Overcome 4.1.0. Some people have switched to Overcome 4.0 and seen the problem go away (as have those who switched to other Chefs' ROMs). Of those who install 4.1.0 and see no problems, it suggests that whatever change happened between 4.0 and 4.1.0 affects only certain routers. Maybe some kind of optimization done has rendered a number of router models affected. ???
Suleeto said:
Of those who install 4.1.0 and see no problems, it suggests that whatever change happened between 4.0 and 4.1.0 affects only certain routers. Maybe some kind of optimization done has rendered a number of router models affected. ???
Click to expand...
Click to collapse
It has nothing to do with what router you have. Any router set to have no lease expiration will cause the bug. MOST routers don't even allow you to do such an asinine things. I couldn't force my router to have no lease expiration if I wanted to (which I wouldn't, because it would be stupid).
Search google for "Netgear No Lease Expiration". This is a GENERAL problem. It is not confined to Gingerbread Overcome ROM 4.1.
The bug is a combination of some routers' fault for shoddy programming and a gingerbread wifi config fault for not handling a fringe (and borderline retarded) but technically acceptable setting.
Change (FIX) your router's setting.
---
See for details: http://www.ietf.org/rfc/rfc2131.txt
According to the RFC SPEC:
The client may ask for a permanent assignment by asking for an infinite lease. Even when assigning "permanent" addresses, a server may choose to give out lengthy but non-infinite leases to allow detection of the fact that the client has been retired.
Nowhere in the spec does it say the server should give out Infinite Leases to clients that do not ask for them. If your router gives infinite leases to clients that can not or do not handle them, THE ROUTER IS THE BROKEN PART.
So you're saying that Froyo, WinMo, and other more powerful computing devices have additional functionality to deal with "fringe" features on select routers?
I am considering your explanation but you can understand how the explanation itself also might sound asinine to a layperson. I understand what DHCP servers do and how IP leases work.
My router is a newer Belkin model only a couple years old.
Edit: Because I am curious, I'll be looking into the router settings to see just what it is actually set at.
Edit 2: Yep, it's set to forever. Then again, I still can't understand why that is in your assessment considered a "bad" thing. And in my experience, it has never, NEVER been a problem with previous tech, over the years and years of wifi router use.
None of this explains or justifies why Gingerbread-based ROMs should suddenly lose this functionality. It is not like Android clients are going to change the face of what is a very common DHCP configuration among routers past and present (despite your sentiments). To me, moving from Froyo builds that can handle this to Gingerbread builds that cannot seems counterproductive for Google, as most consumers WILL NOT want to tweak their three to five year old routers that otherwise connect fine to every other computing device they can bother to try to connect with.
And like I said previously in this very thread... you can't exactly go into the back room of a Starbucks, the town library, or of local businesses, and demand they make a change to their DHCP lease configurations that for everyone else (oh! oh! oh! Including the well loved iPhone!) works without any issues whatsoever.
So I'm sorry, I'm not being a **** here, but what you're suggesting is an extremely large pill you are asking me to swallow, and it just seems like a prescription for a disease I do not possess.
LOL, checked the router and found the problem.
Was that not covered in the thread as one of the issues/fixes?
Jeez.
you can't exactly go into the back room of a Starbucks, the town library, or of local businesses, and demand they make a change to their DHCP lease configurations
Click to expand...
Click to collapse
And you'll almost never have to, because 99.5% of routers are made to the spec I linked and won't give the type of lease that your router does. Surprising that there isn't a firmware upgrade available that changes the default on the router to not be infinite - may just be because you can do it yourself in the router setup, so they didn't bother.
The "infinite-lease" by router without client request situation is not specifically defined in the spec, which means it is not necessarily defined in all clients. What makes other devices work with this router is either
a) the other clients can/do request infinite-leases
b) the other clients happen to have a lease handler that accepts an infinite lease
But nothing in the spec says the client should handle an infinite lease if it did not request one. In the case of this particular gingerbread ROM, that handler is left out, which is a case of not coding defensively enough. -Great- code would handle that in a different way than re-scanning constantly. However, there is a difference between "great code" and "meeting specs". By specification technicality it is the router that is on the wrong side of this argument.
All it means is that both sides kind-of suck. And in this situation the sucky part you have control over is the router, unless Alterbridge releases a modified wifi config that can handle this case gracefully that it shouldn't have had to handle in the first place (but honestly should have anyway, because that's what great code does).
phlooke said:
LOL, checked the router and found the problem.
Was that not covered in the thread as one of the issues/fixes?
Jeez.
Click to expand...
Click to collapse
Um I only mentioned that out of rhetoric, I am not questioning what I can do to resolve the tablet connection process AT MY HOME, I'm questioning the logic of defining the router as a "problem", which the other gentleman (darkmatter) is discussing with me. Or did you miss the point I was actually making? Jeez
darkmattar said:
And you'll almost never have to, because 99.5% of routers are made to the spec I linked and won't give the type of lease that your router does. Surprising that there isn't a firmware upgrade available that changes the default on the router to not be infinite - may just be because you can do it yourself in the router setup, so they didn't bother.
The "infinite-lease" by router without client request situation is not specifically defined in the spec, which means it is not necessarily defined in all clients. What makes other devices work with this router is either
a) the other clients can/do request infinite-leases
b) the other clients happen to have a lease handler that accepts an infinite lease
But nothing in the spec says the client should handle an infinite lease if it did not request one. In the case of this particular gingerbread ROM, that handler is left out, which is a case of not coding defensively enough. -Great- code would handle that in a different way than re-scanning constantly. However, there is a difference between "great code" and "meeting specs". By specification technicality it is the router that is on the wrong side of this argument.
All it means is that both sides kind-of suck. And in this situation the sucky part you have control over is the router, unless Alterbridge releases a modified wifi config that can handle this case gracefully that it shouldn't have had to handle in the first place (but honestly should have anyway, because that's what great code does).
Click to expand...
Click to collapse
I am not really concerned with "great code" vs. "poor code" here, I'm concerned with consumer use. I am more and more convinced this was a decision of the ROM chef and less that it's "Gingerbread" design. I can't imagine Google taking a risk of alienating even a small percentage of consumers who find themselves trying to connect to routers with default infinite leases. You claim that most new routers don't even allow that. This would mean that "infinite lease" is a legacy configuration, but again, every other device seems to have no trouble with that, because companies making these devices and their ROMs understand that the average consumer DOES NOT always know how (or have the option to) go in and change the config of a given router.
And btw... using the term "code" to criticize router design is a bit sloppy. How cleanly it's "coded" isn't at all what you're describing. It's "design philosophy" that is at work here. Not "code". Sometimes amateur programmers haven't spent enough time in the corporate development world and do not understand that the deciding factor in features and function is the COMSUMER end. Code is the guts, not the result. The result is designed based on need.
Also, you have some devices (recent ones, like my HP wireless printer for instance) that do not have an easy way to be assigned a fixed IP, and do not like frequent DHCP reassignment because the driver end on the client PC retains the IP as the pointer for the print queue. An infinite lease allows the initial assignment process to happen, and allows the client PC driver assigned IP to keep consistent with the IP assignment of the printer. This is not the only device that has this issue, but it is an increasingly common problem among a few wireless printer manufacturers in the way they set up client software connections to wireless printers.
So are you saying I should change my router config and cause printing problems in order to satisfy my apparently gutted, less-than-full featured network functionality of my custom flashed Android device?
Does that sound reasonable? Does that even address the concern that I have no control over public and other private wireless networks that I might try to connect to (and have infinite lease enabled)?
Tell you what: I will be going to not one, but three different wireless networks today. One at my local college, one at Starbucks, and believe it or not, the Denny's down the street has a brand new wifi setup installed (only about six months old). I will tell you what happens.
Even still, if I have this situation at home, then inevitably it exists elsewhere. And I would wager it's not a 1% experience, either.
I'm all for streamlining custom ROM's and trimming the fat, but not at the expense of such particularly important functionality. You call it "fringe", but from a product development point of view, we would consider it "comprehensive".
I like my "comprehensive" term a lot better than your "fringe" one. Maybe dropping this kind of functionality will happen eventually in devices, but I feel that doing so now is premature.
And I'm hoping that the chef reads this and at least offers the code in a subsequent version.
---------- Post added at 10:06 AM ---------- Previous post was at 09:50 AM ----------
From the Overcome 4.1.0 thread:
absolutab said:
Not every GB ROM. Only on 2.3.6 JQ8. Had no issues with wi-fi on previous GB versions.
OTOH, on previous versions I had market issues (even at 240 dpi and with the 60Mb cache hack) and everything's working great on 2.3.6. Go figure... If I could have overcome 7 4.0 with overcome 7 4.1 market behavior I'd be more than happy.
I've tried ICS CM9 and wi-fi seemed stable.
Click to expand...
Click to collapse
So Google may have indeed been the one to F' things up... Still, my sentiments stay the same, and it means that I might be switching to Overcome 4.0 until the situation is resolved. At least if this is the case, it's not the Chef's fault.
It has been a good discussion - I feel it is definitely clearing up the details, and I've learned a few things myself while researching to make sure my dhcp knowledge is up-to-date and at least mostly factually correct.
Also, you have some devices (recent ones, like my HP wireless printer for instance) that do not have an easy way to be assigned a fixed IP, and do not like frequent DHCP reassignment because the driver end on the client PC retains the IP as the pointer for the print queue. An infinite lease allows the initial assignment process to happen, and allows the client PC driver assigned IP to keep consistent with the IP assignment of the printer.
Click to expand...
Click to collapse
The infinite lease merely stops the Lease Handshake from occurring. The lease handshake is a different communication altogether from DHCP [re]assignment. About the only time a DHCP assignment will happen is if DHCP settings change on the router between leases, and on the rare occasion it could happen that the Lease Handshake fails (like if one of the devices is unplugged or loses power momentarily) and a different device is connected and takes the IP, requiring a new one to be given to the other device. However, on your mostly stable/unchanging home network, this should happen pretty much never. The only case worth worrying about is if a power outage lasts long enough to span the lease expiring on multiple devices, they could reconnect and get different IPs each
less-than-full featured
Click to expand...
Click to collapse
I have been quoting from the RFC on DHCP. What your router is doing is not "full featured", it's "extra featured", which means not every device is going to support it, nor does it have to support it to be approved. If you look up "infinite lease" on google, you will see that essentially all documentation recommends against it. Another humorous link is to microsoft DHCP server software, which allows setting infinite leases (it is nowhere close to the default) but then begs you not to in the documentation!
However, since the spec does not explicitly state that a device should fail and retry the connection when an infinite lease is given, there really is no wrong method.
There is certainly a "more-appealing-to-users-desiring-full-compatibility" method. But again, when one device does something not explicitly defined in the specifications for ALL DHCP devices, it is just asking for other devices to be unable to connect to it.
Does that sound reasonable? Does that even address the concern that I have no control over public and other private wireless networks that I might try to connect to (and have infinite lease enabled)?
Click to expand...
Click to collapse
As for this concern, I may be wrong, but I believe any public wifi with infinite leases will be broken 1/2 the time due to the allocated IP space being used up by devices that aren't even connected anymore. They'll be rebooting their router every few hours/days depending on how heavy their traffic is.
Almost all documentation warns against even setting your client to request infinite leases, or allowing your router to grant them
See: http://technet.microsoft.com/en-us/library/dd183602(WS.10).aspx
or: http://www.tcpipguide.com/free/t_DHCPLeasesLeaseLengthPoliciesandManagement-4.htm
or: http://blogs.technet.com/b/teamdhcp/archive/2007/02/07/configuring-lease-time.aspx
Important Excerpts from above links:
Although it is possible to configure a client with infinite lease duration, use infinite lease durations with caution. Even relatively stable environments have a certain amount of client turnover. At a minimum, computers might be added and removed, moved from one office to another, or network adapters might be replaced. If a client with an infinite lease is removed from the network without releasing its lease, the DHCP server is not notified, and the IP address is not automatically reused. Also, when using an infinite lease, options set on the DHCP server are not automatically updated on the DHCP client, because the client is never required to renew its lease and obtain the new options. We recommend that you use reservations, rather than infinite lease durations.
Click to expand...
Click to collapse
Perhaps the most relevant one of all is here:
Should I have INFINITE lease time?
It’s technically possible and most of the devices support it but the recommendation is never to have infinite lease time. The main reason is that any change in network configuration on dhcp server will not be updated on the client as the client will not trigger renew. Also it’s reported on some site that few devices don’t behave properly with INFINITE lease time and result in service crash and other issues. So if you are dhcp admin and want to avoid unnecessary issues it’s recommended not to have INFINITE lease time
Neelmani
Windows Enterprise Networking
Click to expand...
Click to collapse
See quotes above. It is way more of a router problem than a client problem.
But, in the end, I do agree that a well-designed wifi driver -should- be capable of handling an infinite lease without failing and reconnecting endlessly.
After reading all that the morning you posted it, I agree with you even before the edit. I see your point.
And I'm glad you also seem to agree with me that it could have been more comprehensive.
I've since turned my lease to two weeks (the maximum increment other than infinite). Hopefully my printer will continue to sync up to the client software later on. I will admit that I partly blame HP and other printer manufacturers for using such a LAZY workaround for their wifi printing solutions.
I suppose in a few years from now it won't matter. I still haven't visited those three other networks I wanted to try Overcome's Gingerbread on. Not yet. Been extremely busy. In a few minutes I'll be heading to a Starbucks in another town, so it might happen.
Connection problems either WiFi or physical cable have all the same similarity, Manufacturer's problem and not the OS. If I remember it correctly, way back in the 90's, Modem manufacturer's would just produce hardware and doesn't even think about the end user that will use it. We used to trash WinMo for having so many hardware problem's without realizing that some of the hardware manufacturer's doesn't go by the standards when designing and writing device drivers.They'll just re-use the same design hardware and hoping that they could just re-write the device coding to make it work whatever OS the end user would be using.A well designed hardware makes a coder job fairly easy and would work easily with the end user without a hitch. Sadly, I have to admit that until to these days some manufacturers still have problems catching up every time we have a new OS and merging two OS on a router to make a connection is still a ***** for them.I hate to say it, but "Belkin" should join the club properly .
Sometimes happens only !
I flashed overcome 4.1 over 20 times (while trying other roms and CM9 releases) and return back to it.
on 50% of the cases wifi caused problems. So wonder was about cache - wiping issue.
P.S. Yes i do use same file everytime and re-stock.
Try it.. Simple
i can smile use this because wifi easy connect... use this
1. Install Wifi Static (download from Android Market)
2. Make sure your wifi is connect.
3. Open Wifi Static, and click all box.
4. Click (add configuration) and press button option at your tablet.
5. Now u can see Generate click it.
6. Now click at IP Address change it. example:
192.168.2.1 to 192.168.2.100
7. Restart wifi.
it simple because can save configure and know
ip address/gateway/netmask/dns1/dns2
just changed ip address because you should use ip address no people take already.
easy to use at McD... or any Wifi

[Q] cannot connect to wifi anymore

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

[HELP] Wifi & Bluetooth gone, no longer functioning (Found BT AND Wifi MAC in CP!)

[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.

[Q] How to change my MAC Address

I have a Galaxy Note running Android version 4.0.3, and I'd like to change its MAC Address at will for tethering, but no matter what method I try, it never works. Does anyone know of a sure way to do it on this phone?
If I'm not mistaken, Mac address is build into the hardware.
*Convince me if I'm wrong.
Sent from my GT-N7000
You can't change a mac address, it's the hardware signature, as said above. And why would you want to anyway?
Sent from my GT-N7000 using xda premium
I want to do it so I can connect my 3DS with Streetpass relays, but that requires me to make the phone's address match the relays'. People can do it with other models, so I assumed the same would be possible on the Note, even if the method differs.
There are quite a number of mac address changing apps on play, Not sure if they work with tethering.
Just try a couple of them.
They do require root though.
If not, look up how to do it on linux and use the terminal.
Good luck.
Well, I managed to change the MAC using the terminal, but only on really weird conditions. I had to turn the tethering on, and then send the terminal command after it activated wlan0, but before it finished setting-up the tethering (or else, I'd get a weird signal with both the original MAC address and the target one, that can't connect with anything). So I guess the question now is: is there any way to turn on the tethering using only the terminal?
EDIT: Well, I managed to open the tethering app through the terminal, but is there a way to manipulate it exclusively by using command lines, without the graphical interface ever popping-up?

Categories

Resources