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
.
Hi there, I've had a lot of help through this forum in using my Android tablet without registering, so I thought this could be the best place to ask a question that's beginning to wreck my head.
I have a Versus 7 Touchpad, and while I know it's just a rebranded something or other made in China, it's actually a decent tablet for the price of €100. Anyway, recently I installed the TPlink TL-WA730RE wireless repeater at home and just have had no luck in getting the tablet to connect to the repeater whatsoever. My android phone (Xperia T), my wife's Nokia E5 and my Compaq PC all connect to the repeater fine and can browse the web/network no problem. However, the tablet just says 'connecting' (to the network) but then reverts back to 'saved, secured with WPA' etc. I know it's trying to connect because if I log onto the repeater through my PC every few minutes the MAC address of the tablet appears along with the status of 'STA -ASSOC', which I think means that the unit is trying to associate with the repeater, but then it just disappears. It may be worth noting at this point that the tablet connects to my TPlink TL-WR841N wireless router running DD-WRT no problem.
I've tried almost everything I can think of, like 'forgetting' the network and reconnecting, ensuring MAC address filtering is disabled, trying static instead of DHCP, resetting my router and repeater etc etc. I even tried apps such as 'wifi strongest signal' from the app store which connects you to the strongest access point in your house if you're using a repeater and walking around. The latest thing I did was to install CM10 on the rooted tablet and everything works apart from the wifi with the repeater, so it wasn't a fault with the original image. Also, the tablet was running ICS 4.0.4 I think, which was the same version of Android as my Xperia T, which connects perfectly.
The last thing I can think of trying is updating the repeater firmware, or installing DD-WRT on it also, but I'm loathe to do that seeing as all of my other equipment is working fine. Other than that maybe there is some sort of updated wifi driver I could try for the tablet itself??
Any ideas would be greatly appreciated!
Just incase anyone else has similar problems with this or any other android tablet, I managed to solve the problem after weeks of headaches.
The problem was that my TPLink wifi repeater's channel width was set to 'auto', where I had other options of 20mhz and 40mhz. Once I paired these with my router -i.e- both the router and the repeater were both set to a wireless channel of 20mhz, my tablet worked perfectly fine. Obviously some equipment can handle the difference in channel width, just not the Versus 7 Touchpad wifi.
Hope this helps someone in the future.
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.
Hi,
I've joined this forum to try and get some help with this along with any future issues as it looks like there's a smart bunch of people on here...
Please do move this to the appropriate area if I've put it in the wrong place.
I have a Samsung Galaxy S7 on a UK 'Three' contract.
However I recently bought a new car which has a WLAN feature - basically what it does is connects to your phone's portable hotspot, then broadcasts that internet connection on it's own in-car hotspot for passengers to connect to.
The benefit (because at first glance you think "why bother - why not just connect those devices straight to the phone's hotspot?") is that once the car connects to your phone's hotspot it uses the car's antenna to receive data etc which means you get a stronger and more consistent data connection.
So, the issue:
My portable hotspot works fine when connecting a device such as laptop/iPad etc directly to the phone.
However when I connect the car to my personal hotspot, and then a device to the car, it all connects up okay but I get errors on the end-user device saying that there's no internet connection.
I have done quite a lot of testing with this - for example in the following situations it works perfectly for the end-user devices - just never with my S7!!
- Connecting the car to my girlfriend's iPhone SE hotspot (on the same network)
- Connecting the car to my friend's S7 (on the same network?!!)**
- Connecting the car to my home WiFi whilst on the drive
**Interestingly, my friend's S7 was bought separately so had a pure Samsung build on it - mine came from Three so had a load of Three crap on it.
So, to tackle that, yesterday I did a cache wipe and factory data reset, then entered download mode and using Odin, loaded on the latest version of Nougat including all the new BL/AP/CP/CSC files.
Then me and my friend swapped SIM cards to see if that could be the issue, we tried using both phones. None of it worked, and now even his phone with his SIM card in it (which previously worked) no longer works with the car's WLAN.
It still doesn't work and it's driving me mad
Today I'm going to try messing with APN settings because I've read that changing the APN type to just "default" has solved some similar issues to this but without the 'middle-man' car in the middle.
I've also called Three and asked them to send me a replacement SIM card.
I'm sure it is NOT the car that's the issue, as it has worked fine on some devices.
I'm sure it is NOT the Three network that's the issue, as it has worked on 2 other devices on that network.
I suspect it's either some sort of config that needs changing, or the hardware of the phone is faulty.
I have a "remote management session" with Samsung support later today, but I don't expect them to be able to help with this remotely
Any thoughts or ideas here would be greatly appreciated, I'm sorry I've written so much but wanted to include all the info.
Thanks, Andrew
Hi,,
I would like to use my OnePlus 8 in USB tethered mode as an LTE device for my Mikrotik hAP ac lite router.
When I connect the two, OnePlus indicates that it is charging and even though I adjust that to USB tethering the Mikrotik never detects the modem.
I tried the same setup only replacing the phone with a Samsung S8 and the connection worked as expected.
Has anyone else experienced the same behaviour and has anyone else manage to find a solution?
Thanks
try using a router that uses recent version of OpenWRT and it should work, i got it to work on my openwrt router but not on my asus router. however my asus router worked fine with my older phone. Asus router needs firmware devs to fix the issue
In fact when I upgraded the Router OS firmware to Beta 7 it worked.