[Q] anyone encountered ipv6 problem? - Nexus 4 Q&A, Help & Troubleshooting

Hello guys, sorry for my improving English.
I use a router running shibby's tomato firmware and using HE.net's IPV6 tunnel. When my Nexus 4 running 4.2.2, everything was OK. But after it install the 4.3 update, I found it losing IPV6 connection. When connect to WiFi, it goes fine at first, and some times later (e.g. 1 hour or so), when connect to a IPV6 site (e.g. ipv6.google.com), it keeps waiting for network. At this time, if I open the router's web page using it's WAN IPV6 IP, it works and ipv6.google.com opens. After a longer time (when I wake up in the morning), it can connect to no IPV6 hosts, even try to connect to my router using it's IPV6 link-local address (fe80:.........).
I flashed back to 4.2.2 and everything works again. My desktop and other devices works fine.

When I enabled LTE on my phone, I followed the instructions exactly, which said to enable IPv4/6 on your APN settings. When I did this my phone behaved normally, except Facebook stopped being able to load certain content such as pictures.
After researching for a bit and even discovering that I couldn't go to facebook.com in Chrome on my phone, I realized it was IPv6.
I have since shut it off and my phone is behaving normally now.
I suggest you just go into your APN settings and select IPv4 only. T-Mobile is apparently ready, but a lot of other providers (such as Facebook) aren't.

dcdttu said:
When I enabled LTE on my phone, I followed the instructions exactly, which said to enable IPv4/6 on your APN settings. When I did this my phone behaved normally, except Facebook stopped being able to load certain content such as pictures.
After researching for a bit and even discovering that I couldn't go to facebook.com in Chrome on my phone, I realized it was IPv6.
I have since shut it off and my phone is behaving normally now.
I suggest you just go into your APN settings and select IPv4 only. T-Mobile is apparently ready, but a lot of other providers (such as Facebook) aren't.
Click to expand...
Click to collapse
facebook claims its ready, but ive noticed that they have issues. until about a month ago, i had issues posting photos from their website via my n4, now it works(most the time). try changing the user agent of your browser to desktop.

Related

Wi-Fi connectivity problems on Legend

Hello people,
Two days ago I bought a Legend only to discover that it has some issues with Wi-Fi. Here's what I mean:
I did the initial setup fully, set up a Google account, Wi-Fi connection only. Weather and Mail (Imap, not Gmail) work perfectly with my home WLAN, but Market does not. What's even strange - I can only open .bg websites (I'm from Bulgaria) in the browser, but nothing else, not even google.com. Those two work just fine on a 3G connection, though.
I tried all sorts of tricks with my router (D-Link N in mixed-mode if it matters), but it was no good. Even set the phone to be in the Demilitarized zone so as to have no problems communicating on port 5228 as I read Market needs to use... still nothing.
Please, can anyone think of a way to solve this annoying problem?
May thanks in advance!
Did you try switching the router to only b/only g/only n mode?
My router is a D-Link DSDL 2740R N and I haven't problem.
Also the coverage is satisfactory.
Try changing your DNS settings, and check router's MTU. Although just guessing here...
Sent from my HTC Legend using the XDA mobile application powered by Tapatalk
Yes, switching the mode was the first thing I did - going to g/b did no good.
Like I said, I don't have troubles connecting now - just a very limitted access to websites and services.
And what DNS Settings? The ones on the router? But they are working perfectly with my two computers, it's the HTC Legend that has issues.
---
So, I just talked to the support desk of my ISP and they told me they had never heard of such a problem. According to the guy, everything should be working normally because they were not blocking any kind of traffic/ports.
Any ideas?

[Q] Weird wifi dns issue under CM

I should note I am running CM6.1 RC2
So, I had the strangest thing happen this morning. I went to my in-laws for thanksgiving dinner and put my G2 on their wifi. It worked fine last night, but this morning after a few moments I am having very bizzare behavior over the wifi connection.
What seems to be happen is that the DNS lookup requests seem to fail when using the android apps. Now, for some reason, the wifi calling app connects, and I can place calls over wifi, but I can't use any other applications for data.
Here is where it gets weirder. If I ping an address, it works just fine, and then, since the dns resolution is cached, I can go to that domain in the browser, however any links that leave that domain do not work.
I have tried several things, setting a static ip address, using different DNS addresses (the router, and then google's dns addresses). Nothing seems to be working. I have also rebooted the router. Other device on the network are able to connect just fine.
The funny thing is that data works fine over the cellular network, of course there is only edge out here, and somewhat spotty coverage at that, but things seem to work just fine.
Any thoughts on what the issue might be?
Thanks!
Well, I ended up fixing it by doing a nandroid backup, restoring and clearing the dvalik cache. Weird.
Sent from my HTC Vision using XDA App

Market and Gmail won't connect via wifi, but will over 2G/3G..Other internet works

We have a vibrant and a captivate.. When connected via wifi at home, the market and gmail will not connect, but both phones access the internet just fine otherwise.. They connect fine to the market and gmail using 2G or 3G, or other wifi networks..
Can anyone let me know what settings I might adjust on the router to allow connections to gmail or the market on these phones?
Strange thing is I have exactly the same problem, but this only started yesterday. The days before I was able to download several apps via market over wifi, but as of yesterday I can not even see the home screen when on wifi, no problems when on 3G. Tried opening port 5228 TCP and UDP as suggested in an older thread, but that did not work. Something changed at Google?
Update: problem went away by itself 2 days later.
I9000 stock 2.3.3
We have 3 android phones- all with the same problem.. Router is a Netgear WNR2000v3.
Edit-Reset router and the problem continues...
Check the firewall router
There is no firewall A's far A's I know. Just a wireless DSL and a router, and I have not configured any firewall...I reset the router to factory settings and it still won't work....
Sent from my SGH-T959 using xda premium
Try some other wifi area. Is the problem same or not. Maybe it's good to delete APN from settings and let it configure again.
have you tried paying you're cable bill?
seriously.. the phones all connect via other wifi networks just fine. They connect to this router just fine as well.. All internet connectivity is great except anything to do with google's apps.. youtube, maps, gmail, market.. none will work, but google.com on the browser works fine.
I had this problem 2 days ago. I have searched the web a lot for this problem. Now I found 3 solutions that you may wanna try.
1. Clear cache and reset to factory. Don't skip the sign in on google account. Sign in immediately! (had not worked for me though!)
2. Check your firewall settings. Especially, I used my laptop as a hotspot source with virtual wifi router(ht_tp://ww_w.virtualwifirouter.com/). I have tried connectify and virtual router, but they had problems on my laptop, while VWR is simple and effective! (I still couldn't connect to market and youtube at that moment though! Very very frustrated!)
3. I read someone said he tried to set the parameters of his mobile network manually, and it worked for him. I didn't expect much on this method but did give it a try. OMG! It worked! What's worth to notice is that I found that the instruction provided on my operator's website (Orange.fr) is actually a little bit different from the settings the phone automatically loaded.
3.
Hope it works for you guys!
I had same problem but reset of router helped...
You know what, I think it's the operator or google's dirty trick. For no obvious reason, I am blocked out of market again with wifi. I can surf on porn sites with wifi but no luck on market and google's stuff!
bonedriven said:
I had this problem 2 days ago. I have searched the web a lot for this problem. Now I found 3 solutions that you may wanna try.
1. Clear cache and reset to factory. Don't skip the sign in on google account. Sign in immediately! (had not worked for me though!)
2. Check your firewall settings. Especially, I used my laptop as a hotspot source with virtual wifi router(ht_tp://ww_w.virtualwifirouter.com/). I have tried connectify and virtual router, but they had problems on my laptop, while VWR is simple and effective! (I still couldn't connect to market and youtube at that moment though! Very very frustrated!)
3. I read someone said he tried to set the parameters of his mobile network manually, and it worked for him. I didn't expect much on this method but did give it a try. OMG! It worked! What's worth to notice is that I found that the instruction provided on my operator's website (Orange.fr) is actually a little bit different from the settings the phone automatically loaded.
3.
Hope it works for you guys!
Click to expand...
Click to collapse
One more thing to add: Use static IP address for your wifi connection! Mine was not stable with automatic address!
iflyabeech said:
We have a vibrant and a captivate.. When connected via wifi at home, the market and gmail will not connect, but both phones access the internet just fine otherwise.. They connect fine to the market and gmail using 2G or 3G, or other wifi networks..
Can anyone let me know what settings I might adjust on the router to allow connections to gmail or the market on these phones?
Click to expand...
Click to collapse
Try to forward the ports needed for google, 5228 i think, that helped my cappy a little bit, try clearing all your networks, see if that helps. Google around for captivate wifi problems, hundreds of threads with lots of solutions.
chschris2011 said:
Try to forward the ports needed for google, 5228 i think, that helped my cappy a little bit, try clearing all your networks, see if that helps. Google around for captivate wifi problems, hundreds of threads with lots of solutions.
Click to expand...
Click to collapse
I did try forwarded the ports for one of the phone, problem is there are three.. And port forwarding didn't work, neither did resetting the router, or resetting it to defaults, and they all had a static ip...Still no good..
If familiar with wireshark, try setting up on a computer, connecting to market with phone and see what u get. Maybe packets being blocked, hard to say.

Cannot connect to WEP secured network

I have done about everything. I can connect to my Android phone (using tether), my house, other open networks PERFECTLY, but unfortunately my gym uses a WEP network and I cannot get my tablet to connect to their network.
I have rebooted, forgot the network and set it up again (a million times) I have done EVERYTHING. My Android phone can connect to the gym network perfectly. Any suggestions?
Anyone have any suggestions? Does anyone connect to a WEP secured network and know that this works?
I had the same problem and found out the solution changing some values in the set up router.
Sent from my X10i using XDA App
I'm connected to our home browser which uses WEP. I think it's a matter of settings/wireless and networks/Wi-Fi settings/add wi-fi network. Once you are in the 'add' page, it asks about security, you should be able to input the data.
Jim
I have had same problems, honeycomb handles WPA and WPA2 enterprise networks weird compared to gingerbread. I have had problems with connections too. Try to use the "wifi advanced config editor" and make sure settings are correct for that network (after you attempt to connect to it in settings app). I hope google fixed this problem in ICS or i will be furious. Most of these kind of bugs are laziness on coders or just people who missed lines of code and then don't want to release an update (or wait till next update release rather than a hotfix).
1337GameDev said:
I have had same problems, honeycomb handles WPA and WPA2 enterprise networks weird compared to gingerbread. I have had problems with connections too. Try to use the "wifi advanced config editor" and make sure settings are correct for that network (after you attempt to connect to it in settings app). I hope google fixed this problem in ICS or i will be furious. Most of these kind of bugs are laziness on coders or just people who missed lines of code and then don't want to release an update (or wait till next update release rather than a hotfix).
Click to expand...
Click to collapse
So just to make sure I understand...
Basically the way I originally connected was that I let the tablet scan for networks, and it found the gym network. Once it found the gym network, I selected it and entered the password. I left the proxy and DHCP settings alone and pressed connect, and cannot get it to connect.
What you are suggesting that I do is delete the network, and add the network MANUALLY (where I input securtiy, SSID, passcode, etc.).. Is that right?
So I installed the Advanced Wifi tool, to no avail.
Here is the funny thing. I have a Samsung Epic 4G phone which uses Gingerbread, and it connects to the WEP just fine. I installed the Advanced Wifi on there as well, and went through the settings that were autoconfigured for the gym. Each setting matched my tablet perfectly, yet my tablet cannot pull an IP address, but my phone can.
I'm having the same issue. Thought it was the tab, just received replacement and still a No Go! Every other device in my house connects to this network. And the Gtab also connected perfectly until recently... no clue what to do now.

Tmobile unofficial tethering

So I think I got free tethering to work on my MG with tmobile $30 prepaid plan by changing the APN, but not 100% sure if I got the process down correctly since I've been tinkering, rooted and still on 4.3.
Anyways, maybe you guys can give a try and see if it works. This is aimed towards t-mobile users who don't have hotspot as part of their plan or have already exhausted their monthy tethering limit.
steps:
- go to settings > More....> mobile networks > Access Point names
- add a new APN by hitting the "+" sign
- Set "Name" to what ever you'd like (e.g. Hotspot4life)
- Set "APN" to fast.t-mobile.com
- Set "APN protocol" to IPv4/IPv6 or IPv4
- Leave everything else untouched
- hit menu button then select save
- Select the APN just created.
- Active native tethering (assuming you've adjusted ID and password already to your liking)
- If it works, go back into settings and select old APN... and check if tethering has been blocked.
Note: there's no need to reboot when switching APNs.
If it doesn't work, then a file change I did beforehand while rooted made a difference or something else was a factor.
neugenusis said:
So I think I got free tethering to work on my MG with tmobile $30 prepaid plan by changing the APN, but not 100% sure if I got the process down correctly since I've been tinkering, rooted and still on 4.3.
Anyways, maybe you guys can give a try and see if it works. This is aimed towards t-mobile users who don't have hotspot as part of their plan or have already exhausted their monthy tethering limit.
steps:
- go to settings > More....> mobile networks > Access Point names
- add a new APN by hitting the "+" sign
- Set "Name" to what ever you'd like (e.g. Hotspot4life)
- Set "APN" to fast.t-tmobile.com
- Set "APN protocol" to IPv4/IPv6 or IPv4
- Leave everything else untouched
- hit menu button then select save
- Select the APN just created.
- Active native tethering (assuming you've adjusted ID and password already to your liking)
- If it works, go back into settings and select old APN... and check if tethering has been blocked.
Note: there's no need to reboot when switching APNs.
If it doesn't work, then a file change I did beforehand while rooted made a difference or something else was a factor.
Click to expand...
Click to collapse
t mobile and Three use Packet Sniffing to check the file headers to detect tethering. If you tether an iOS device or an OSX device to your phone, often they will not get flagged and the tethering will work. If you use a Windows PC or other device it will be detected immediately. I mention this, as it could be a factor if you tried tethering with an ipad or something and got it to work. Messing with the APN on Three has no effect, so I'd be surprised if it works with T Mobile.
Thanks for the tip! I found that this works, but unreliably on my Moto G.
I just got a MG last week and was frustrated to find tethering would not work at all out of the box. I stumbled across your post and made the changes you recommended and it worked very well at first - for maybe15 minutes or so. Then I noticed my Chromebook lost connection and upon further diagnosis it was the Moto G that lost connection to the T-Mobile network. I tried to turn of tethering, but that didn't help and I finally had to reboot the phone to get it back on the network. I switched back to the default APN and the phone worked reliably again, but obviously not tethering. In the past couple days I've tried the new APN with your settings a few times and get similar results - it works for a while, but then the phone loses cell connectivity. I've since found that I toggling Airplane Mode on and off will restart the cell connection and tethering will also start working again, so it kind of works but not as well as it should.
I've been doing more searching regarding the fast.t-mobile.com APN and other threads seem to indicate that APN is specifically for LTE phones. Since the Moto G doesn't have an LTE chip, I wonder if that's causing the reliability problem?
Brandon
PS - I think there might be a typo in your instructions and fast.t-tmobile.com should be fast.t-mobile.com - with just 1 t in the t-mobile. Thanks again!
theragtopman said:
PS - I think there might be a typo in your instructions and fast.t-tmobile.com should be fast.t-mobile.com - with just 1 t in the t-mobile. Thanks again!
Click to expand...
Click to collapse
You're right. I've fixed it. Thanks.
I rarely tether, so I haven't used it in every scenario. But when I do tether, its while tethering to my tablet, my friend's phone, or desktop/laptop WITH user agent switcher on Chrome to mask the desktop/laptop as a mobile device. After reading your post, I tethered to my laptop for an hour and did not encounter any issues. Do you lose connectivity even when the phone's signal strength is strong? Have you tried tethering to a different device (mobile)?
Thanks for the follow up. I've been trying it again today from my home where I get better cellular signal strength, but I'm getting similar results. It connects up and runs for 15-30 minutes and then starts flaking out. After rebooting both the phone and Chromebook, the Chromebook kept trying to go to a T-Mobile sign-in page, but couldn't even load that. And I too am using a Chrome extension to change the user agent to Android. The Moto G seems to be working fine and not losing it's connection this time.
I have also been able to test tethering on a Nexus 4 running Android 4.4.2 today and the Chromebook is connecting just fine and staying connected - no problems at all. I compared the APN settings between the 2 phones and the Nexus has the MMSC entry filled out (which xda won't allow me to post here because i'm too new), so I added that into the Moto G, but it did not help. Darn. I really like the Moto G, but really need reliable tethering. Thanks again...
theragtopman said:
Thanks for the follow up. I've been trying it again today from my home where I get better cellular signal strength, but I'm getting similar results. It connects up and runs for 15-30 minutes and then starts flaking out. After rebooting both the phone and Chromebook, the Chromebook kept trying to go to a T-Mobile sign-in page, but couldn't even load that. And I too am using a Chrome extension to change the user agent to Android. The Moto G seems to be working fine and not losing it's connection this time.
I have also been able to test tethering on a Nexus 4 running Android 4.4.2 today and the Chromebook is connecting just fine and staying connected - no problems at all. I compared the APN settings between the 2 phones and the Nexus has the MMSC entry filled out (which xda won't allow me to post here because i'm too new), so I added that into the Moto G, but it did not help. Darn. I really like the Moto G, but really need reliable tethering. Thanks again...
Click to expand...
Click to collapse
You need install a User Agent String changer addon in your browser and change the string.
I use this one: https://chrome.google.com/webstore/...r-c/djflhoibgkdhkhhcedjiklpkjnoahfmg?hl=en-US
I have instructions for another device here: http://forum.xda-developers.com/showthread.php?t=2201062
Good luck.
Thanks for the recommendation! Sorry I didn't make it more clear in my reply above, but I am using a user agent switcher - currently the Ultimate User Agent Switcher. Just to be sure, I disabled that extension and installed the User-Agent Switcher for Chrome that you linked to, but unfortunately I'm getting the same result - the Chromebook takes forever and keeps trying to connect to the "Welcome to T-Mobile" page.
And I tried again with the Nexus 4 and the Chromebook connects up immediately and runs great - no T-Mobile page or any other problems. I did a little more research and found a post on the Nexus 4 forum recommending disabling IPV6 in the APN Protocol, so I switched both phones from IPV6/IPV4 to just IPV4 and am getting the same result on each. Both phones work fine on the cell network and Internet, but the Chromebook only tethers successfully to the Nexus 4.
theragtopman said:
Thanks for the recommendation! Sorry I didn't make it more clear in my reply above, but I am using a user agent switcher - currently the Ultimate User Agent Switcher. Just to be sure, I disabled that extension and installed the User-Agent Switcher for Chrome that you linked to, but unfortunately I'm getting the same result - the Chromebook takes forever and keeps trying to connect to the "Welcome to T-Mobile" page.
And I tried again with the Nexus 4 and the Chromebook connects up immediately and runs great - no T-Mobile page or any other problems. I did a little more research and found a post on the Nexus 4 forum recommending disabling IPV6 in the APN Protocol, so I switched both phones from IPV6/IPV4 to just IPV4 and am getting the same result on each. Both phones work fine on the cell network and Internet, but the Chromebook only tethers successfully to the Nexus 4.
Click to expand...
Click to collapse
You need to set the Firefox string in my thread. That is the only desktop browser string that works. The reason why Chromebook/Ipad/Ipod devices work is because T-Mobile allows those devices since they can all have Cellular radios in them for radio. It would block legit paying customers.
Hey - thanks for the quick follow up!
Unfortunately, I just tried all 3 of the Firefox settings in the user agent switcher and rebooted the Chromebook each time, but no joy - each time after restarting and connecting to the Moto G wi-fi hotspot the Chromebook just tries to redirect me to the T-Mobile site.
theragtopman said:
Hey - thanks for the quick follow up!
Unfortunately, I just tried all 3 of the Firefox settings in the user agent switcher and rebooted the Chromebook each time, but no joy - each time after restarting and connecting to the Moto G wi-fi hotspot the Chromebook just tries to redirect me to the T-Mobile site.
Click to expand...
Click to collapse
Do you have the T-Mobile branded Moto G? If so you may need to disable the upsell app as I did in my L9 thread. You may also need to edit /etc/apns-conf.xml
Also, use this app instead of the builtin tethering. It may be notifying the carrier of tethering.
https://code.google.com/p/android-wifi-tether/
Thanks again for more suggestions.
I am using an unlocked US GSM model of Moto G I purchased from Amazon.
I have not rooted yet, but may try that and the tethering app you linked to. I'm wondering if the stock app included on the Motorola device is the culprit, whereas the stock tethering app on the Nexus device may not be reporting back...

Categories

Resources