Database Info

[Q] Time Capsule??

Has anybody tried to connect to a Time Capsule?? I cannot get my G2X to see my router for nothing. Is the G2X compatible with a N router??

It is N compatible, but it didn't see the N network on my dual-band router.
The Time Capsule should be b/g/n, or at least g/n, so it should show up.

I will check the settings but I think I have it setup on N only

ok first off that your "Time Capsule" router works with your computer laptop etc. is basically irrelevant, other then to reassure you that it works for these devices.
i have seen so many people here and other places say, "hey it works with my "XXXX" so it is working. why can my phone not connect also"
I'm not sure if phones are just more finicky or what
What i DO know is that phones have extremely small antennas when compared to everything BUT other phones
i see the "Time Capsule" has "Simultaneous dual-band 2.4GHz and 5GHz"
i have also heard people say dual-band not working and when they select one frequency their phone connects
so heres some things to try
1) places phone no more then a few feet away from router (in this case the "Time capsule") and try and connect
2) turn off dual band and select first 2.4GHz and try connect and then try 5GHz
3) see if you can update the routers firmware and repeat steps 1 and 2
4) try other bands like B and/or G on both 2.4 and 5GHz
5) set your router to an open network (Not locked or hidden in anyway) and try to connect, you can always re-lock it down later, right now your trying to find the problem through a process of elimination
6) try changing the channel, Mine is at 10, because others near me are using 1-6, if there are allot of people using a channel, your phone will have a hard time connecting or staying connected. i think they get confused. there are android apps that will tell u what channels are being used around you. use it to pick a channel as far away from others as u can!
PS:
for firmware i found this there might be newer so make sure you check
Dec 16th, 2010
Apple has released AirPort Base Station and Time Capsule Firmware Update 7.5.2. The update "fixes some issues with AirPlay streaming." Additionally it provides:
General fixes to Wi-Fi base station stability
General fixes with USB interoperability including connection to external storage devices
Fixes some issues with NAT port mapping settings
Disables TKIP security with 802.11n rates per the Wi-Fi Alliance specifications
The firmare update is for all 802.11n capable AirPort base stations and Time Capsules and requires Mac OS X 10.5.7 or later, Windows XP SP3 or later, Windows Vista SP1 or later, or Windows 7.
http://support.apple.com/kb/DL1106
.

Finally got wifi working check this trick out.

FINALLY GOT WIFI WORKING CHECK THIS TRICK OUT.
No need to use airplane mode trick.
Stock phone not rooted.
Download WIFI ANALYZER from market.
1)Once downloaded, open app.
2)hit menu button on phone and select AP list.
3)Do you see your router, press it and should take you to the market to download a program to connect to your router.
After it downloads that follow steps 1 and 2
After step 2 second time around.
4)If Yes press and hold until it says connect to FAKE AP , Or whatever your routers name is.
Enter your password.
5)hit connect and you should be connected now.
Turns your android phone into a Wi-Fi analyzer!!
Shows the Wi-Fi channels around you. Helps you to find a less crowded channel for your.
User Reviews
Excellent app for pinpointing the best channel to set up your WiFi router!!
by Daniel– May 5, 2011
-----------------------------------------------------------------------------
Brilliantly useful tool for reducing / eliminating wireless interference.
by Dane– May 5, 2011
-----------------------------------------------------------------------------
Wonderful tool for checking local WiFi. Managed to boost my signal by selecting a ...
by Robert– May 5, 2011
Wonderful tool for checking local WiFi. Managed to boost my signal by selecting a different channel from all the other local ones.
-----------------------------------------------------------------------------
I have also did the same things as the people that reviewed the app.

my favorite WiFi Analyzer is WiFiFoFum for Android. For PC I use InSSIDer (Inside Her, lol)
I've used it back in Windows Mobile days. The cool feature I like is the WiFi Radar, which is cool for finding wifi networks in relation to your position.
It has the same thing like showing various WiFi networks and their dedicated broadcast channels.
Channels isn't something people regularly consider when setting up WiFi networks but it is a huge issue. Having 2 wifi networks with overlapping frequencies will result in serious lag, timeouts, and connectivity issues.
To get technical there are 11 channels (plus some more for 5Ghz bands) but typically you'd have 11. Only Channels 1, 6, and 11 won't overlap each other.
Selecting 2, 3, 4, 5, 7, 8, 9, or 10 will be overlapping a channel somewhere (if you are in a rural area with lots of networks). In my router, I did a wifi analyzer around my house and everyone is using 1, 6, or 11... but the key is finding the less crowded channels with the least amount of signal.
Don't select a channel that has another signal with full bars or you will degrade both of them. When I first bought a house I moved in and had HORRIBLE wifi. I looked and my neighbors are both using Channel 6... and so was I. So I moved to 11 because it was less crowded and everything is great now.
This is standard WiFi 101 but most people just use the defaulted settings which usually is set to 6.
[EDIT]
We are talking about your WiFi Routers... not your Phones. The process above simply states that you should download a WiFi analyzer for testing purposes SO THAT you can program your router properly.

The stock wifi settings connects and disconnects, And never connects.
Thanks for that info +1.
It was a problem with phone not connecting to router. After I did the trick I found out it worked.
Instant wifi connection.
The stock wifi settings connects and disconnects, And never connects.
Yesterday was my first day with wifi working , After this method.
I made this post to help someone out, Suffering from the same problems I was having.

WIFI SETTING MENU
Inside there is a setting to connect to the router. That is the only my phone can connect.

Wi-Fi Issues on MM - Original Shield Tablet

Alright, first let me say that I have had zero issues with this tablet until I upgraded to MM.
For some reason, I am having constant issues with the Wi-Fi either dropping, or changing channels. If I set the Wi-Fi to 5Ghz only, it will eventually switch over to 2.4Ghz. If I set the wireless to automatic, it will constantly switch back and forth between 2.4Ghz and 5Ghz. Setting the wireless to just 2.4Ghz still results in random drops.
So far, I have experienced this issue on all of the major MM ROMs found here in the NVidia Shield section. I event restored my tablet with the latest image from NVidia.
Is this just an inherent issue with MM on the original shield tablet? Am I going to be stuck using 5.11?
The only thing I haven't done is flash back to the original stock image and do OTAs back the latest MM update.
Any help would be appreciated.

I agree, wifi on lollipop was miles better. I also think lollipop was better on the whole. I'm on stock unrooted.

Setting the "Wi-Fi frequency Band" to "5 GHz only" shouldn't drop you to 2.4 GHz. This setting works perfectly for me as setting it to "2.4/5GHz only" results in the other band completely shut off.
If your SSID is identical for 2.4GHz and 5GHz, then yes, it can switch back and forth. However since most Wi-Fi clients are too stupid to know when to switch over, it is highly recommended to use a different SSID for 2.4 and 5GHz.
On Lollipop, there is an Android bug (it affects my phone too) where if you have SSID and SSID-5G or SSID_5G (and perhaps others), even if you never joined SSID, it'll occasionally drop the 5GHz connection and connect to 2.4GHz. This is apparently fixed on Marshmallow as my LTE tablet has remained connected to 5GHz since the update.
At least for me, my WiFi experience drastically improved with Marshmallow. So my suggestion is to make sure the 2.4 and 5GHz SSID's are different and check for interference from the neighbors using an app like WiFi Analyzer or NetX. I recommend NetX over WiFi Analyzer as it can also show you WiFi SSID's that span 40MHz.
Also note that your own home devices can also cause interference. The Roku box w/ WiFi Direct is notorious for this.

Isira said:
Setting the "Wi-Fi frequency Band" to "5 GHz only" shouldn't drop you to 2.4 GHz. This setting works perfectly for me as setting it to "2.4/5GHz only" results in the other band completely shut off.
If your SSID is identical for 2.4GHz and 5GHz, then yes, it can switch back and forth. However since most Wi-Fi clients are too stupid to know when to switch over, it is highly recommended to use a different SSID for 2.4 and 5GHz.
On Lollipop, there is an Android bug (it affects my phone too) where if you have SSID and SSID-5G or SSID_5G (and perhaps others), even if you never joined SSID, it'll occasionally drop the 5GHz connection and connect to 2.4GHz. This is apparently fixed on Marshmallow as my LTE tablet has remained connected to 5GHz since the update.
At least for me, my WiFi experience drastically improved with Marshmallow. So my suggestion is to make sure the 2.4 and 5GHz SSID's are different and check for interference from the neighbors using an app like WiFi Analyzer or NetX. I recommend NetX over WiFi Analyzer as it can also show you WiFi SSID's that span 40MHz.
Also note that your own home devices can also cause interference. The Roku box w/ WiFi Direct is notorious for this.
Click to expand...
Click to collapse
Having the same SSID for different frequencies should never be a problem. As a system administrator, I have never run into an issue such as this, unless it you have your device set to "automatic" so that it can swap back and forth between the two different bands. If I set the radio to 5Ghz only, then it should stay on 5Ghz, and vice versa with 2.4Ghz.
The issue appears to be something with MM and the original shield tablet. I reconfirmed that flashing back to the LP image I have no problems with the Wi-Fi at all.
I guess I'll keep plugging away at trying various things until I get this figured out or someone else points me in the right direction.

Just got my brand new replacement tablet from Nvidia from the battery recall. came loaded with 5.11 and zero wifi issues. I updated to 6.01 and boom! wifi issues. That means I have two tablets with the same issue. Something is up with 6.01 and the original shield tablet.

Sounds like an incompatibility with your specific network setup and the SHIELD Tablet/Google Marshmallow.
I have two SHIELD LTE Tablets both running Marshmallow 6.0.1 and I have zero issues. I find the 2.4GHz/5GHz only modes work as intended. However my 2.4 and 5GHz SSID's are different, whereas you apparently have the same SSID's for both bands.
For an experiment, I created a single identical guest SSID for the 2.4 and 5GHz networks and put the tablet in 5GHz mode. What I noticed is that 5GHz only does indeed fail occasionally, but the 2.4GHz behavior is interesting. It will only pick up all SSID signals for the single 2.4GHz channel the Guest SSID is associated with, so in my case all 5GHz channels and only Channel 1 of 2.4GHz. After a few minutes of usage, the tablet seems to go back to 5GHz only mode and the Channel 1 2.4GHz SSID signals disappear. Similarly, If I put the tablet in 2.4GHz only mode, then it will also occasionally pick up the single 5GHz channel the Guest SSID is associated with, so all 2.4GHz channels and only Channel 149 of 5GHz.
If I have my tablet connected to an SSID that is different on both 2.4/5Ghz bands, then 2.4/5Ghz only modes work as intended.
So yes, I can confirm that if you have an identical SSID for 2.4 and 5GHz modes, then the 2.4/5GHz only mode will not work properly under Marshmallow. The suggested workaround is to have different 2.4/5GHz SSID's.

Here is my question. How did I go from having zero issues on every other Android OS before marshmallow, but now this is an issue? If I load an older rom based on 5.11 onto my tablet, I don't have a single issue. To me this points to an issue with MM

TheLastBoyScout said:
Here is my question. How did I go from having zero issues on every other Android OS before marshmallow, but now this is an issue? If I load an older rom based on 5.11 onto my tablet, I don't have a single issue. To me this points to an issue with MM
Click to expand...
Click to collapse
Yes, we've already established and confirmed that there is a Marshmallow related bug with your specific use case. I have provided a workaround, which is to create a separate SSID for the 5GHz band. You have also provided a workaround, which is to downgrade to Lollipop. It is your choice to make.
You don't sound like somebody who understands software development. Basically, with every major Android OS release, Google can significantly change the underlying code which can introduce bugs. NVIDIA then takes that code and tries to make it work with the SHIELD Tablet which can introduce even more bugs.
There is a programming joke sung to the tune of "99 Bottles of Beer":
99 little bugs in the code.
99 little bugs in the code.
Take one down, patch it around,
127 little bug in the code...
Click to expand...
Click to collapse
Without a secondary Marshmallow device, I cannot confirm if the problem is on Google's end or NVIDIA's end. Nevertheless, I suggest reporting it to Google and NVIDIA. At the very least, Google can fix the problem before Android N is released, and maybe NVIDIA can fix it for a future Marshmallow release.

While I am not a programmer, I work with several programmers and do testing of software on a test system before updates are pushed out. I guess I incorrectly assumed NVidia would do the same.
Now, I've tried multiple times based off of CM and AOSP, in addition to stock (all MM based) and still have this issue, so I would assume it's an issue on Google's end.

TheLastBoyScout said:
While I am not a programmer, I work with several programmers and do testing of software on a test system before updates are pushed out. I guess I incorrectly assumed NVidia would do the same.
Now, I've tried multiple times based off of CM and AOSP, in addition to stock (all MM based) and still have this issue, so I would assume it's an issue on Google's end.
Click to expand...
Click to collapse
Honestly, this is an edge case that is rather difficult to diagnose and wouldn't even be detected under normal testing conditions. It's quite unfair to say NVIDIA didn't do any testing in this case.
I suggest submitting a highly detailed bug report to NVIDIA so that they can reproduce the issue. If NVIDIA fixes it and it is determined it is an issue with the base Android OS, they may submit the patch upstream to Google so hopefully it won't be an issue with future versions of Android.

Android Devices Unable To Maintain WiFi Connection

I have four handheld Android devices and, currently, 3 standalone WAPs plus Verizon's FIOS router.
.
None of the four devices can maintain a connection to any of the standalone WAPs or the router for more than a half-second or so: they solicit the PW, Authenticate, connect briefly, and then drop the connection.
.
I normally have only one WAP, but added the two just to make sure the problem was not in the WAP. Ditto Verizon's router, whose WiFi is normally turned off, but turned on now for troubleshooting.
.
For the life of me, I cannot think of any changes I have made in the week leading up to the onset of this problem.
.
One of the standalone WAPs is an Orbi Mesh system, but currently with no satellites - the satellites having started to act weird with onset of the problem and therefore having been turned off.
.
I also have two instances of AndroidTV running: one on a Sony Bravia TV and the other on an NVIDIA SHIELD box. And, weirdly, both of them are able to hold a WiFi connection - but UNABLE to hold a Ethernet cable connection. Same appearance as the handhelds over WiFi: connection gets dropped, only almost instantly so the screen just kind of vibrates with the connected.
.
If I turn off all standalone WAPs, leaving only the WAP in the Verizon router, the problem persists - with the Verizon router's WAP on channel three and, according to the WiFi Manager Android app, no competing signal sources on channel 3.
.
The problem persists even with the handhelds within 10 feet of the various WAPs.
This started about a week ago. Before that, no problems. And I don't *think* I have changed anything.
Right now, the only thing between me and hiring somebody to troubleshoot the problem is the weirdness of the problem - and the fear that their billing by the hour could cost me too much.
Can anybody point me in some direction?

wifi connection problemp - solved

We have set up a WiFi router at our summer house and all devices bar my OnePlus 8 connects without problem to the WiFi. My phone connects to the WiFi but not the internet. Have restarted the phone and removed and added the WiFi connection but no luck. Any idea what's going on?

I had this problem with my oneplus 8, European version, where at times internet connection would drop, but wifi was still connected so the phone was in effect blocked since I use VoWiFi both voice calls and data was blocked.
The problem turned out to be between my router and the oneplus 8. I had to go into the settings of the router and disable a feature called "band steering". This setting will make the two different wifi gateways inside the router, the 2.4 ghz and the 5 ghz appear as one and the same with the same SSID name. This is supposed to simplify setting up devices with wifi but is known to cause problems sometimes.
As soon as I had separated the two and given them different names, I no longer have a problem with internet access dropping from the wifi.
I have no idea where the fault happens, I only know that I have had to disable band steering with another router I had before. I think this feature might be a bit unstable.

No idea what's happened but this morning it just worked.