• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

web browsing = FAIL

Yea, I've been in Vegas when there were a couple bigger events going on. The local cell sites were very stressed. Don't know about wifi, I wouldn't touch the wifi in the area with 100 mile pole. (Black Hat and Defcon)
 
Last night after the National Championship game I couldn't get a single web page to load. This morning it works fine. It's not uncommon at events like CES for people to completely destroy the wifi or 3g networks.
 
This is one of the reasons I'm going to let the phone come out and wait for reviews before I pull the trigger. Also my iPhone 4 freezes a lot and apps crash. It's happened whether it's been jailbroken or not.
 
Ehh, just a itty bitty minor FAIL ... I'm sure the webkit will be tweaked before the final version hits the shelf.
 
Although this had nothing to do with signal it had everything to do with the phone freezing and being choppy but ok if that makes you guys feel better lol

It is bad publicity for Motorola and AT&T, but I and you I'm sure have seen videos with the phone working superbly. To say the phone has issues with a model out of the bunch that may have software or hardware issues is unfair. We are smarter than this aren't we? You yourself even started a thread on Engadget taking another look showing them putting the phone through its paces.
 
Although this had nothing to do with signal it had everything to do with the phone freezing and being choppy but ok if that makes you guys feel better lol

Yikes, I hadn't seen this video before, that was really bad browsing. I agree that it didn't have anything to do with the data because they guy actually stopped the loading before he tried scrolling around.

I hope that was some sort of glitch and not indicative of the general performance of the browser. I can't imagine that Moto would really allow a device to be released with that level of bad browsing, but who knows.
 
It is bad publicity for Motorola and AT&T, but I and you I'm sure have seen videos with the phone working superbly. To say the phone has issues with a model out of the bunch that may have software or hardware issues is unfair. We are smarter than this aren't we? You yourself even started a thread on Engadget taking another look showing them putting the phone through its paces.

Yes but what im saying is that if there are units like this ( and this was only one of the few they said had this issue) it is not good for the atrix means not all is well and smooth
 
Yes but what im saying is that if there are units like this ( and this was only one of the few they said had this issue) it is not good for the atrix means not all is well and smooth

Agreed, but even if none of the units displayed any issues it does not mean a bad bunch won't come off assembly. This is the rule of all hardware built in mass production unfortunately.
 
1st of all if you look at the video when he said ok it stopped loading, well it didn't stop loading. He hit the x to stop the loading. I've had that happen to me where I would hit the x before loading has completed and the browser would hesitate for a sec. I don't think this is a big deal, more of Brandon rushing things a little.
 
Could have been many things. Murphy's Law says that when you don't want things to go wrong, that's when they DO go wrong.
Still, since this was the ONLY AT&T Android phone at CES that was powered on and actually WORKING, I wouldn't read too much into a little snafu.
I'm sure they still had some earlier pre-production models floating around.
 
Although this had nothing to do with signal it had everything to do with the phone freezing and being choppy but ok if that makes you guys feel better lol

Are you saying that it has nothing to do with the signal because there are full bars next to the H symbol? I can see why would would think it must be getting great speeds, but I'm pretty sure that those bars only represent the signal strength only. So if the network is really, really strained (like at CES), you could see slow speeds, even if you're right next to a cell tower.
 
Are you saying that it has nothing to do with the signal because there are full bars next to the H symbol? I can see why would would think it must be getting great speeds, but I'm pretty sure that those bars only represent the signal strength only. So if the network is really, really strained (like at CES), you could see slow speeds, even if you're right next to a cell tower.

No im saying that when you look at it its the browser and its rendering/scrolling not weak signal
 
I will say 50/50 it did lag like nuts but that guys hand was wandering like he was jonesing for a rock, he seemed like he never touched a cellphone before. I thought it seemed to crank pretty good when running through things that had nothing to do with the web.
 
I will say 50/50 it did lag like nuts but that guys hand was wandering like he was jonesing for a rock, he seemed like he never touched a cellphone before. I thought it seemed to crank pretty good when running through things that had nothing to do with the web.

You have to give the phone a chance to load, yes he was all over the screen before the loading finished trying to pinch to zoom and scroll then killed the load before it was done. I wouldn't say it lagged or had a software issue just took a little longer to load probably from all the cell data usage at CES. The software looks pretty finished and polished to me and I can't wait to get one.
 
You have to give the phone a chance to load, yes he was all over the screen before the loading finished trying to pinch to zoom and scroll then killed the load before it was done. I wouldn't say it lagged or had a software issue just took a little longer to load probably from all the cell data usage at CES. The software looks pretty finished and polished to me and I can't wait to get one.


I agree completely, I am not saying its junk, I want one too. :)
 
I agree completely, I am not saying its junk, I want one too. :)

I wasn't implying that you said that. Just the title of this thread is a little misleading in that that OP didn't quite understand how when Brandon killed the page load caused the browser to hesitate for a sec.
 
Back
Top Bottom