Develop Bugs

Browser - max 4 pages open

My browser will only let me open 4 pages. Why is this, any ideas? To prevent excessive memory usage?

I remember reading somewhere that it has something to do with how thumbnails are displayed.
The only way around it is installing an alternative browser like Opera Mini, Dolphin, Steel, etc.
Though I don't see why would you need more that a couple of tabs open on a phone.

Well I do seem to need more than 4 tabs open, just habit I suppose...
I have used Steel and Dolphin before, but I'm really liking the built-in browser, apart from a couple of niggles - the second one being that when long-pressing a link (to bring up the "open in new window" menu), half the time it launches the text highlighting tool :-(
Any idea what I'm doing wrong?

setspeed said:
Well I do seem to need more than 4 tabs open, just habit I suppose...
I have used Steel and Dolphin before, but I'm really liking the built-in browser, apart from a couple of niggles - the second one being that when long-pressing a link (to bring up the "open in new window" menu), half the time it launches the text highlighting tool :-(
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Might want to calibrate the screen?

I'm also finding that after browsing for a while, the browser will refuse to open a new page at all, it seems to start loading the new page, then stops loading part-way through.

setspeed said:
I'm also finding that after browsing for a while, the browser will refuse to open a new page at all, it seems to start loading the new page, then stops loading part-way through.
Click to expand...
Click to collapse
This problem is now starting to really bug me.
I'm browsing for half an hour or so, and then the browser will just freeze up, and refuse to completely load the current page, links won't work, bookmarks won't open. Clearing the cache doesn't fix the problem, and since there's no way to exit the browser then I'm having to reboot the phone.
Anyone else suffering this way?

setspeed said:
This problem is now starting to really bug me.
I'm browsing for half an hour or so, and then the browser will just freeze up, and refuse to completely load the current page, links won't work, bookmarks won't open. Clearing the cache doesn't fix the problem, and since there's no way to exit the browser then I'm having to reboot the phone.
Anyone else suffering this way?
Click to expand...
Click to collapse
Hi
I have the similar issue, but it appears only when I switch from Wifi to mobile connection. The only solution I've found is kill browser. Can you please check if it's the same at your side ? if yes it's propably bug in web browser app, because market and everything else is working fine.

kubino99 said:
Hi
I have the similar issue, but it appears only when I switch from Wifi to mobile connection. The only solution I've found is kill browser. Can you please check if it's the same at your side ? if yes it's propably bug in web browser app, because market and everything else is working fine.
Click to expand...
Click to collapse
No, it's happening to me whether I'm on wifi or 3G (and not switching between the two). I don't have a task manager installed to kill the browser, so I'm having to reboot. Very annoying.
Also another persistent problem is that sometimes the browser will just quit with no warning, when clicking links. It's happened about 6 or 7 times, during (estimated) 4 or 5hrs browsing. When you restart the browser any open windows you had are gone.
I'm not at all impressed with the lack of stability of this browser. I know I could use Steel or Dolphin (with no Flash) instead.
I'm getting a replacement tomorrow, due to the "pink screen" issue, so I'm hoping this handset I have now is just a lemon.
Sadly, I'm thinking maybe they will all be the same. These issues, along with the poor calibration/recognition of where my finger is on the touchscreen sometimes, and the lack of a physical keyboard, are starting to make me re-think my decision about getting this phone.
Even more sadly, my friend's iPhones are looking increasingly more and more attractive :-(

If you don't mind for not having Flash (like iPhone), then you can download "Opera Mini 5" from the Market.
It is much faster and probably will give you better browsing experience.
I am using it for my WM device for years and cannot live without it.
The speed is just so damn fast!
setspeed said:
No, it's happening to me whether I'm on wifi or 3G (and not switching between the two). I don't have a task manager installed to kill the browser, so I'm having to reboot. Very annoying.
Also another persistent problem is that sometimes the browser will just quit with no warning, when clicking links. It's happened about 6 or 7 times, during (estimated) 4 or 5hrs browsing. When you restart the browser any open windows you had are gone.
I'm not at all impressed with the lack of stability of this browser. I know I could use Steel or Dolphin (with no Flash) instead.
I'm getting a replacement tomorrow, due to the "pink screen" issue, so I'm hoping this handset I have now is just a lemon.
Sadly, I'm thinking maybe they will all be the same. These issues, along with the poor calibration/recognition of where my finger is on the touchscreen sometimes, and the lack of a physical keyboard, are starting to make me re-think my decision about getting this phone.
Even more sadly, my friend's iPhones are looking increasingly more and more attractive :-(
Click to expand...
Click to collapse

will tmobile ends "free" tethering policy affects us SGN owners?

I just read the article here: http://www.androidpolice.com/2012/0...e-tethering-if-you-ever-had-it-to-begin-with/
I am on tmobile prepaid plan and use the tether once in a while. But I absolutely would not pay extra to pay for tethering my own data that I already paid for.

it shouldn't unless you decide to install their version of ics

I'm going to quote my own G+ post on these one:
All phones that T-Mobile has released since the Amaze 4G and the Galaxy S II have had a separate APN built in to their tethering that automatically flags your device as tethering. This includes the new LG MyTouch devices, the HTC Radar, etc. ALL phones released for the last 6 months. This has been the status quo for a long time, and for some reason everyone is throwing a fit now that the new software for the Sensation is doing exactly the same thing that all of these other phones have been doing since they were released.
Also, several of these articles state that T-Mobile is using some kind of sinister monitoring methods on your data traffic in order to determine that you are tethering. This is not true. It is being done in a very similar way to how I understand the iPhone has reported tethering to carriers for a long time, by using a completely separate tethering APN instead of the customary data APN typically used for T-Mobile handsets. This is why on some newer devices if you enabled tethering and then tried to browse on your handset it would either fail or send you to a upsell that would ask you to purchase tethering, because it is flagged as completely different traffic.
Click to expand...
Click to collapse
This is a software change handled on each device. It has little to do with the network outside of the network authorizing the tethering APN from the newer handsets when the tethering option has been enabled. It is possible that T-Mobile may be passively monitoring user agent strings to 'detect' tethering, however, this is a very unreliable method for them to use as using the desktop user agent option in your browser would trigger that. AT&T appears to do this, but to my knowledge, T-Mobile does not. At least not presently. However, some users have reported they are being given the tethering upsell when using desktop user agents, so I could easily be wrong.
Personally, I don't believe that this is the correct thing for carriers to do, as long as you aren't going over you data limit. I believe that you should be able to use your data limit how you see fit, whether the traffic is coming from your phone or through tethering. For me, this kind of nonsense is exactly the same as ISPs using QOS to throttle bandwidth for competing services, such as, theoretically, if Comcast were to throttle Netflix traffic. Unfortunately, my voice alone isn't going to change the status quo, and carriers in the US have decided that charging for tethering is the new way to make a profit.
TL;DR
No. This will not affect the GN in any way, nor is this a new development. This policy for new devices / software for T-Mobile phones has been in place for around for 6 months and is a software 'feature'. Also, that article is poorly written and researched in general, as well as the horde of other bad articles in the past couple of days over this so-called 'revelation'.

lettcco said:
I just read the article here: http://www.androidpolice.com/2012/0...e-tethering-if-you-ever-had-it-to-begin-with/
I am on tmobile prepaid plan and use the tether once in a while. But I absolutely would not pay extra to pay for tethering my own data that I already paid for.
Click to expand...
Click to collapse
The only reason they can block it on their own devices is because they control the final software. T-Mobile doesn't control the software on the Galaxy Nexus.
That being said, T-Mobile attempts to "block" tethering on unlocked/unbranded devices by sniffing UAstring of your browser and redirecting you to their tethering upsell page if they notice you're on a desktop browser (they're assuming you're tethered to a desktop). I'm going to save myself some time and not elaborate on this. It's how they do it and it's all over the internet in XDA and other places.
Its a horrible policy that many people have been fighting with for a long time now. Not only does it not work stopping any moderately sophisticated user on their desktop (because spoofing is SO easy), but it inadvertently "blocks" anyone trying to request desktop sites on their phones. Many browsers (especially Chrome Beta for Android) by default browse in desktop mode (or let you easily request desktop sites), and get redirected inadvertently.
Long story short, the UAstring sniffing method is starting to redirect Chrome Beta for Android users (including myself), as it has nearly an identical UAstring to desktop Chrome. They're currently "working to resolve this issue" which may mean a change in the way they try to detect tethering. More than likely they'll keep doing it they way they are and will come up with a workaround for Chrome for Android. Either way they have to figure it out, as they're selling ICS 4.0 devices that use Chrome for Android now.
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
cade80 said:
it shouldn't unless you decide to install their version of ics
Click to expand...
Click to collapse
T-Mobile doesn't have a "version" of ICS. Especially not for the GNex

Thanks all for the insightful comments.

Same of custom GB breads, or any custom on phones in general. Tethered on my G2x all the time on CM7 with no problems at all.
Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2

http://code.google.com/p/android-wifi-tether/

martonikaj said:
The only reason they can block it on their own devices is because they control the final software. T-Mobile doesn't control the software on the Galaxy Nexus.
That being said, T-Mobile attempts to "block" tethering on unlocked/unbranded devices by sniffing UAstring of your browser and redirecting you to their tethering upsell page if they notice you're on a desktop browser (they're assuming you're tethered to a desktop). I'm going to save myself some time and not elaborate on this. It's how they do it and it's all over the internet in XDA and other places.
Its a horrible policy that many people have been fighting with for a long time now. Not only does it not work stopping any moderately sophisticated user on their desktop (because spoofing is SO easy), but it inadvertently "blocks" anyone trying to request desktop sites on their phones. Many browsers (especially Chrome Beta for Android) by default browse in desktop mode (or let you easily request desktop sites), and get redirected inadvertently.
Long story short, the UAstring sniffing method is starting to redirect Chrome Beta for Android users (including myself), as it has nearly an identical UAstring to desktop Chrome. They're currently "working to resolve this issue" which may mean a change in the way they try to detect tethering. More than likely they'll keep doing it they way they are and will come up with a workaround for Chrome for Android. Either way they have to figure it out, as they're selling ICS 4.0 devices that use Chrome for Android now.
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
T-Mobile doesn't have a "version" of ICS. Especially not for the GNex
Click to expand...
Click to collapse
overriding the user agent in chrome doesn't seem to help. strange.
i was tethering for about an hour just now and the redirect page just popped up.

I ran into the same problem today. After coming really close to paying the $12/month to use the data I'm already paying for, I decided to come here and ask for help. I got 2 solutions.
1. Change the user agent for my browser. Once I did this it was surfing as usual with the built in tethering app. Only problem is Netflix isn't supported by android2.2 browser.
2. PDA net, I read somewhere that a it hides what type of traffic. It seems to work. No restrictions, no redirects.
I'm going to stick with the second alternative because it behaves the way I'm used to.

turbosix said:
overriding the user agent in chrome doesn't seem to help. strange.
i was tethering for about an hour just now and the redirect page just popped up.
Click to expand...
Click to collapse
yeah once they've flagged you it's hard to get around it on the phone.
Ironzey said:
I ran into the same problem today. After coming really close to paying the $12/month to use the data I'm already paying for, I decided to come here and ask for help. I got 2 solutions.
1. Change the user agent for my browser. Once I did this it was surfing as usual with the built in tethering app. Only problem is Netflix isn't supported by android2.2 browser.
2. PDA net, I read somewhere that a it hides what type of traffic. It seems to work. No restrictions, no redirects.
I'm going to stick with the second alternative because it behaves the way I'm used to.
Click to expand...
Click to collapse
PDAnet should work, but T-Mobile filtering and checking for UAstring can potentially get around this. Depending on how PDAnet tries to "hide" or change your final connection you may be successful.

It happened to me as well. I was using Chrome on OSX but after the redirect page started manifesting itself, I wondered if it would be the same with all browsers. I tested Safari and no redirect page
Sent from my Galaxy Nexus using Tapatalk 2

Wi-Fi Tethering Workaround

There seems to be threads around about bypassing the tethering without actually adding it to your plan. Some seems to work, some doesn't. So I'm just gonna post here what works for me. If mods find that it is inappropriate to be posted or what not, you may delete this post. Anyways I'm running a CM10 nightly ROM and I was tethering fine for awhile. It wasn't until recently at Starbucks I was hit with a ADD HOTSPOT TO YOUR PLAN blah blah blah page and I'm like WTF?! Anyways I recently swapped from the 5GB plan to the Unlimited 4G plan so I lost the native tethering from the plan itself. After some searching online I came across a solution (not sure where I saw it anymore but credits to whomever it was).
Step one: Use chrome as browser for device. (Tablet, PC, Laptop, whatever it may be)
Step two: https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg Go there and download User Agent Switcher for Chrome. It should install right into Chrome and have a little sign on the top right.
Step three: You could pick the default Android user agent that comes with the application and pages SHOULD load up fine. (Works for me) Unfortunately pages load up in mobile mode, sure you could request desktop mode at the bottom of most pages but that gets annoying. Then there is step four which is optional.
Optional
Step four: You go to settings of the User Agent Switcher, and under the Custom User Agent tab start creating a new User Agent. Fill in the blanks with the first box on the left with what you want to name it. I just named mine Android 4.1. In the second box, enter "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.45 Safari/535.19" without the quotes. The third box should autofill to Chrome, if not put Chrome in there. I picked the option Append for the next box (not sure if it really matters which you pick). Finally for the last box under Indicator Flag, I put AND. Now click Add, and start using this newly created User Agent to browse pages. This way pages seem to load automatically as desktop mode and doesn't seem to flag the T-mobile hotspot message.
This seems to be working fine for me as of the time being. For how much longer I cannot guarantee. I cannot guarantee if it'll start working for everyone either, but I figured I'll share the information. Hopefully this doesn't go too main stream and T-mobile some how fixes it. That's the downside of TOO many people knowing eh? Enjoy!

jayr415 said:
T After some searching online I came across a solution (not sure where I saw it anymore but credits to whomever it was).
Click to expand...
Click to collapse
lol yeah the workaround was probably spread around since... the sensation days? maybe even mytouch 4g days? it's also found in this pretty large thread http://forum.xda-developers.com/showthread.php?t=1883483.. probably mentioned about 30 times in there.
btw i prefer this user agent switcher https://chrome.google.com/webstore/detail/user-agent-switcher/lkmofgnohbedopheiphabfhfjgkhfcgf
another note: all the "mac" ones work so you can run CHROME on MAC and it'll work flawlessly.
Another funny thing. Rockmelt, although is based off chrome works completely fine without running user agents.
Windows Chrome and Firefox are blocked by t-mobile.
Heck since I already been mentioning all this...
If you're stuck without a user agent switcher and want to use chrome the manual way to switch it for the page that you're on is
right click > inspect element > settings button (gear icon) (bottom right corner) > overrides tab > check and enable user agent.
You can now download an user agent switcher for chrome on that page... and that page alone

T-Mobile Hotspot false positive: Can only browse offers.t-mobile.com.

At Midnight EST, Morning of 17 December 2012, Web browsing on my phone stopped working. When I tried to access Web pages not already in my cache, I was redirected to:
http://offers.t-mobile.com/tethering/upsell.do?source=redirect
A new Website set up by T-Mobile to sell tethering service. I don't want to purchase this service, but the Web page kept coming up, no matter where I tried to browse. Of course, rebooting did NOT fix the problem.
After debugging a handful of possibilities, I realized the likely culprit was an interaction between Google Chrome, T-Mobile, and Chrome UA Switcher. Opening Chrome UA Switcher and resetting to defaults mitigates the problem, temporarily returning Web browsing functionality.
In particular, I was using Chrome UA Switcher to tweak the user agent string that Chrome was sending to websites for each page request. I hate when websites try to push their limited "mobile" HTML versions on me, and I really hate when they try to push their "apps" on me--I just want to browse the Internet like an ordinary desktop user. So I was using Chrome UA Switcher to tweak a Chrome setting to force websites to offer their normal desktop HTML versions.
That's where T-Mobile comes in. Apparently, too many T-Mobile users are tethering their phones to their computers without purchasing the T-Mobile tethering service, because T-Mobile decided to block all HTTP requests that use a desktop-like user agent string. When a T-Mobile user tries to visit a website with either a legitimate phone with a desktop user agent string, or an illegitimate computer tethered to the phone, T-Mobile's overeager police system detects both as an illigitimate user, resulting in false positives that effectively disable 100% of Web browsing for hapless customers. Good job with QA there.
I motion to roll back this overeager police system. Find a more accurate way to detect tether-stealers, because the current system classifies normal users as thieves, and doesn't even have the guts to say so.
Specs:
* Chrome 18.0.1025469
* Chrome UA Switcher 1.20
* Samsung Galaxy SIII SGH-T999
* T-Mobile Unlimited Plan

mcandr said:
At Midnight EST, Morning of 17 December 2012, Web browsing on my phone stopped working. When I tried to access Web pages not already in my cache, I was redirected to:
http://offers.t-mobile.com/tethering/upsell.do?source=redirect
A new Website set up by T-Mobile to sell tethering service. I don't want to purchase this service, but the Web page kept coming up, no matter where I tried to browse. Of course, rebooting did NOT fix the problem.
After debugging a handful of possibilities, I realized the likely culprit was an interaction between Google Chrome, T-Mobile, and Chrome UA Switcher. Opening Chrome UA Switcher and resetting to defaults mitigates the problem, temporarily returning Web browsing functionality.
In particular, I was using Chrome UA Switcher to tweak the user agent string that Chrome was sending to websites for each page request. I hate when websites try to push their limited "mobile" HTML versions on me, and I really hate when they try to push their "apps" on me--I just want to browse the Internet like an ordinary desktop user. So I was using Chrome UA Switcher to tweak a Chrome setting to force websites to offer their normal desktop HTML versions.
That's where T-Mobile comes in. Apparently, too many T-Mobile users are tethering their phones to their computers without purchasing the T-Mobile tethering service, because T-Mobile decided to block all HTTP requests that use a desktop-like user agent string. When a T-Mobile user tries to visit a website with either a legitimate phone with a desktop user agent string, or an illegitimate computer tethered to the phone, T-Mobile's overeager police system detects both as an illigitimate user, resulting in false positives that effectively disable 100% of Web browsing for hapless customers. Good job with QA there.
I motion to roll back this overeager police system. Find a more accurate way to detect tether-stealers, because the current system classifies normal users as thieves, and doesn't even have the guts to say so.
Specs:
* Chrome 18.0.1025469
* Chrome UA Switcher 1.20
* Samsung Galaxy SIII SGH-T999
* T-Mobile Unlimited Plan
Click to expand...
Click to collapse
Well T-Mobile is ridiculous and we who tether are not thieves. We can't steal date we have already played for so o that note T-Mobile can choke on one. Its my data I pay for monthly and I should be able to use how ever when ever.
Sent from my SGH-T999 using xda premium

yeislak said:
Well T-Mobile is ridiculous and we who tether are not thieves. We can't steal date we have already played for so o that note T-Mobile can choke on one. Its my data I pay for monthly and I should be able to use how ever when ever.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
That may be, but it helps to be agnostic on this issue. Even IF we consider unpaid tethering to be stealing, it still doesn't make sense to hurt phone users who aren't tethering at all but simply using a tweaked user agent string. We can't control T-Mobile's policy on paid vs nonpaid tethering, but we can request that T-Mobile not falsely block users who are fully abiding by the stated payment plans.

mcandr said:
At Midnight EST, Morning of 17 December 2012, Web browsing on my phone stopped working. When I tried to access Web pages not already in my cache, I was redirected to:
http://offers.t-mobile.com/tethering/upsell.do?source=redirect
A new Website set up by T-Mobile to sell tethering service. I don't want to purchase this service, but the Web page kept coming up, no matter where I tried to browse. Of course, rebooting did NOT fix the problem.
After debugging a handful of possibilities, I realized the likely culprit was an interaction between Google Chrome, T-Mobile, and Chrome UA Switcher. Opening Chrome UA Switcher and resetting to defaults mitigates the problem, temporarily returning Web browsing functionality.
In particular, I was using Chrome UA Switcher to tweak the user agent string that Chrome was sending to websites for each page request. I hate when websites try to push their limited "mobile" HTML versions on me, and I really hate when they try to push their "apps" on me--I just want to browse the Internet like an ordinary desktop user. So I was using Chrome UA Switcher to tweak a Chrome setting to force websites to offer their normal desktop HTML versions.
That's where T-Mobile comes in. Apparently, too many T-Mobile users are tethering their phones to their computers without purchasing the T-Mobile tethering service, because T-Mobile decided to block all HTTP requests that use a desktop-like user agent string. When a T-Mobile user tries to visit a website with either a legitimate phone with a desktop user agent string, or an illegitimate computer tethered to the phone, T-Mobile's overeager police system detects both as an illigitimate user, resulting in false positives that effectively disable 100% of Web browsing for hapless customers. Good job with QA there.
I motion to roll back this overeager police system. Find a more accurate way to detect tether-stealers, because the current system classifies normal users as thieves, and doesn't even have the guts to say so.
Specs:
* Chrome 18.0.1025469
* Chrome UA Switcher 1.20
* Samsung Galaxy SIII SGH-T999
* T-Mobile Unlimited Plan
Click to expand...
Click to collapse
Well said. Can you tell me what you have done since you posted this? Have you just accepted the fact that you cannot use the desktop versions of sites? This is killing me on my Nexus 4.
I'm probably going to call them and talk to someone just to see if there's anything they can do, I fully expect to waste my time. I am going to file a complaint with the FCC if they don't fix this. I mean c'mon, it's defective by design. They only give you 5 GB, so even if I was tethering, I'd only be able to use up to 5 GB. Why would t-mo care how I use the 5 GB they give me? And that point is moot: I'm not even trying to tether, I just want to view desktop sites and they are filtering that. Are there any laws in place that prohibits carriers from filtering content that I can reference in my complaint?

I just started getting this annoying redirect and I've not been tethering on my phone- I don't think I've ever actually tethered from my phone since being on t-mobile, though I am running a custom rom and it does have an option to do this I've not actually ever set it up or run it once.... ?
I do have an unlimited unthrottled plan, and will use it do get torrents from time to time, but I'm not being a data hog and racking up any huge monthly data use rates.
I really can't figure out how I was browsing normally on my phone and then did a google search for something I was interested in and boom... now every websearch or link I want to open automatically is redirecting me to this stupid notification!?
anyone figure it out?

XDA not loading well in Chrome

For months now i've had problems using xda. The loading would hang and wait. If I looked at the developer tools in chrome, I can clearly see that for some reason it was constantly pending loading at objects attached to hosts like this:
www1-lw.xda-cdn.com
www2-lw.xda-cdn.com
forum.xda-cdn.com
forum-lw-1.xda-cdn.com
forum-lw-2.xda-cdn.com
It was failing to load with Chrome on Android, Linux, and Windows. Firefox would load correctly. Interesting thing is that when I connect via a VPN and then test with Chrome it would load fine. I would say it is just my IP address and routing but this has been over a period of time when my ISP IP address has changed. I've verified that and it is still an issue. I have no other issues with any other site.
If there are details I can provide, let me know. If this is the wrong forum for a problem like this, let me know that too. I've gotten to the point that I block the listed cdn addresses in my hostfile so that they immediately fail and my pages load but obviously that rids me of images and other elements along with not letting you guys recoup cost for ADs.
There seems to be something with the CDNs XDA uses.

calisro said:
For months now i've had problems using xda. The loading would hang and wait. If I looked at the developer tools in chrome, I can clearly see that for some reason it was constantly pending loading at objects attached to hosts like this:
www1-lw.xda-cdn.com
www2-lw.xda-cdn.com
forum.xda-cdn.com
forum-lw-1.xda-cdn.com
forum-lw-2.xda-cdn.com
It was failing to load with Chrome on Android, Linux, and Windows. Firefox would load correctly. Interesting thing is that when I connect via a VPN and then test with Chrome it would load fine. I would say it is just my IP address and routing but this has been over a period of time when my ISP IP address has changed. I've verified that and it is still an issue. I have no other issues with any other site.
If there are details I can provide, let me know. If this is the wrong forum for a problem like this, let me know that too. I've gotten to the point that I block the listed cdn addresses in my hostfile so that they immediately fail and my pages load but obviously that rids me of images and other elements along with not letting you guys recoup cost for ADs.
There seems to be something with the CDNs XDA uses.
Click to expand...
Click to collapse
how is your internet connection? and do you use a an add blocker?

simms22 said:
how is your internet connection? and do you use a an add blocker?
Click to expand...
Click to collapse
Connection is fine. Its a 100M UP/DOWN connection. No adblocking. Zero issues for anything else. I stream a lot of data from various sources. Im a very heavy user and never have any issues with any site but XDA. The fact that it works over the VPN is interesting since it would route it through a different path. The fact that it loads fine without the VPN connection in firefox only is also interesting. As I said, this has been going on for a long time. I'm quote sure it isn't my 'connection'. Of course it could be routing or a problem with the CDNs.
All other page elements load correctly except for all the CDN URLs according to the developer tools in Chrome. The problem is the page won't actually 'render' anything until the CDNs timeout.

calisro said:
Connection is fine. Its a 100M UP/DOWN connection. No adblocking. Zero issues for anything else. I stream a lot of data from various sources. Im a very heavy user and never have any issues with any site but XDA. The fact that it works over the VPN is interesting since it would route it through a different path. The fact that it loads fine without the VPN connection in firefox only is also interesting. As I said, this has been going on for a long time. I'm quote sure it isn't my 'connection'. Of course it could be routing or a problem with the CDNs.
All other page elements load correctly except for all the CDN URLs according to the developer tools in Chrome. The problem is the page won't actually 'render' anything until the CDNs timeout.
Click to expand...
Click to collapse
i know ill probably get a talking to, but try an ad blocker. xda is chalk full of ads, very very many! that could have an affect. btw, i use adfree http://adfree.odiousapps.com/adfree.apk

It goes further. Even with an adblocker, the page doesn't load properly. Some of those CDNs load real elements. So even with ads being blocked, page would still not load.

Same here. Browser is irrelevant. "Waiting for www1-lw.xda-cdn.com..."

I'm having the same issue. "Waiting for www1-lw.xda-cdn.com..."

calisro said:
For months now i've had problems using xda. The loading would hang and wait. If I looked at the developer tools in chrome, I can clearly see that for some reason it was constantly pending loading at objects attached to hosts like this:
www1-lw.xda-cdn.com
www2-lw.xda-cdn.com
forum.xda-cdn.com
forum-lw-1.xda-cdn.com
forum-lw-2.xda-cdn.com
It was failing to load with Chrome on Android, Linux, and Windows. Firefox would load correctly. Interesting thing is that when I connect via a VPN and then test with Chrome it would load fine. I would say it is just my IP address and routing but this has been over a period of time when my ISP IP address has changed. I've verified that and it is still an issue. I have no other issues with any other site.
If there are details I can provide, let me know. If this is the wrong forum for a problem like this, let me know that too. I've gotten to the point that I block the listed cdn addresses in my hostfile so that they immediately fail and my pages load but obviously that rids me of images and other elements along with not letting you guys recoup cost for ADs.
There seems to be something with the CDNs XDA uses.
Click to expand...
Click to collapse
Are you using chrome 53? Upgrade to Chrome application and platforms with version 55, then try again.
https://knowledge.rapidssl.com/supp...ntent&id=ALERT2165&actp=LIST&viewlocale=en_US

---

My chrome will load slow/hang if i visit xda(open many tabs) with whitelisted adblock(ublock). When hang I can see under taskmanager the page consuming 1gig+ ram. Sites like gsmarena is fine whitelisted, no performance issues so maybe you can see what they're doing right.

I haven't been able to go to the main xda page for over a week now on Chrome, with or without adblock on, it loads in IE but who wants to use that?

dave2103 said:
I haven't been able to go to the main xda page for over a week now on Chrome, with or without adblock on, it loads in IE but who wants to use that?
Click to expand...
Click to collapse
You can try Upgrade to Chrome application and platforms with version 55.

I have the same issue. The issue is not present in Firefox. Difference ? MAYBE due to the limit of open connections pr host in google is lower than in Firefox.
---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------
Actually, disabling adblock plus helps.

jakobfriis said:
I have the same issue. The issue is not present in Firefox. Difference ? MAYBE due to the limit of open connections pr host in google is lower than in Firefox.
Click to expand...
Click to collapse
The issue is also present on Firefox and is rather network related. I often have issues loading xda at home and it stucks at opening www1-lw.xda-cdn.com, but at work it works fine almost ach time. This is happening for at least half a year now and there are days (not often tho) where everything loads instantly.

calisro said:
For months now i've had problems using xda. The loading would hang and wait. If I looked at the developer tools in chrome, I can clearly see that for some reason it was constantly pending loading at objects attached to hosts like this:
www1-lw.xda-cdn.com
www2-lw.xda-cdn.com
forum.xda-cdn.com
forum-lw-1.xda-cdn.com
forum-lw-2.xda-cdn.com
It was failing to load with Chrome on Android, Linux, and Windows. Firefox would load correctly. Interesting thing is that when I connect via a VPN and then test with Chrome it would load fine. I would say it is just my IP address and routing but this has been over a period of time when my ISP IP address has changed. I've verified that and it is still an issue. I have no other issues with any other site.
If there are details I can provide, let me know. If this is the wrong forum for a problem like this, let me know that too. I've gotten to the point that I block the listed cdn addresses in my hostfile so that they immediately fail and my pages load but obviously that rids me of images and other elements along with not letting you guys recoup cost for ADs.
There seems to be something with the CDNs XDA uses.
Click to expand...
Click to collapse
You should disable add blocker.

Same issue, waiting for www1-lw.xda-cdn.com on XDA frontpage, been like this for around a year now. uBlock is disabled. To remedy this, I have to load the XDA Forums in another tab, refresh XDA Frontpage and it's all working good

Same here. I would logon to the site way more often if this dind't happen.

Same here, @theBIGone, I see you're in Amsterdam as well, maybe it's location based as well?

Netherlands here too. Exact same issue.

I was having terrible lockups whilst browsing XDA for ages, to the point that I thought xda was running one of these CoinMining scripts on users. I actually enabled adblockers and the issue totally vanished. Weird.