From a standardization and technology point of view, I would agree with that statement. Both LTE, technically LTE Advanced, and WiMax use different over-the-air signals and encoding, whereas HSPA+ maintains some backwards-compatibility with HSDPA and HSUPA.
However, from an end-user trasnfer-speed point of view, I'd agree that there's not much difference.
You are right that 3G and 4G have a lot of marketing hoopla surrounding them.
Most end-users don't care much about the underlying technologies as long as they can watch YouTube on their phones in the middle of a corn-field in Iowa. :)
Or, if they use CMOS transistors, just turn off the clock to one of the cores.
But even if you do that, the moment somebody runs an app and the OS decides to do some housecleaning, it's going to wastefully fire up the second core.
Better to build your OS to schedule everything and put everything possible on the idle queue.
A coworkering of mine had it. maybe I mentioned it already, but upgrading to os4 caused full charge battery life to be about 2-3 hours.
Obviously some software thing was spinning or turning on some high usage resource and not turning it off.
But as they built no way to downgrade from os4 to 3, and they didn't have a fix, you actually had to trade in your phone to downgrade.
iOS4 on my 3G is almost unusable.
Thu Aug 19 2010 10:27:28 AM EDT from Ahff Rowe @ UncensoredThere are supposedly ways to downgrade, and I'm about to go down that path I think.
iOS4 on my 3G is almost unusable.
As it was on my wife's 3G. Turning off all of the spotlight searches helped, a bit...but I wound up doing a full restore of the OS on her phone, and then restoring her data, and it's working a lot better, now.
I think I'm right behind you on the full restore option.
It has been reported in a few places that apparently Apple is "looking into reports" of slowness on previous generation devices. At least folks with 3GS don't seem to have been totally screwed.
It took about ten seconds for the phone to wake up enough to answer a
call from my wife last night.
And this is a perfect example of somebody having gone down the wrong path.
It's a smartphone. It's not a computer. It's a fucking phone. It should suspend ALL processess that aren't the phone and make everything else run at a lower priority than the phone application.
even games and the web and the network layer unless it's handling a phone call.
It has been suggested that AT&T and Verizon might just be deliberately
configuring their networks to prioritize traffic for the newest
devices, in order to make people think that the devices themselves are
Well AT&T probably signed something with apple saying they will achieve X response and throughput for iphones or jobs will personally hand their ass to them.
not sure verizon has an excuse except to compete with the iphone.
Alright guys, i've come back for some guru-level advice with a bit of sarcastic spin (like you usually do - IG... lol)
I've been having some trouble recently with my new net connection. In some locations I can connect to all ports on my home network, in some locations I can only view port 80. Also, (to make it even more confusing) at the locations I can't connect to my secondary http ports (8008, 8080, 10000, 5800, etc...), I can still connect to UCG BBS (port 8080).
It's leading me to believe that my ISP is selectively blocking certain connections including a connection from my work computer or from my mobile...
your friends are tcptraceroute and more modern traceroutes
and pro'lly you need to change your provider to somebody that doesn't think everything but http is evil.
I think my ISP is blocking proxy connections on all ports but 80.
Or maybe it's a firewall problem... dunno.
time to start abusing DNS infrastructure.
Tue Dec 07 2010 12:29:41 PM EST from IGnatius T Foobar @ UncensoredConsumer ISP's will generally either block a port entirely or not block it at all. If you are getting the impression that there is selective blocking, either you have something misconfigured or there is something going on from those other locations.
Well, here's how I have my regular stuff configured:
|-Main Tower (SDK-PC) - 192.168.2.1
|-+-VPS (BVS-WEB) - 192.168.2.3
The VPS is run on the main tower with a network bridge so it gets its own internal IP.
Open Ports and Directions:
80 -> 192.168.2.3:80
10000 -> 192.168.2.3:10000
8008 -> 192.168.2.2:80
8080 -> 192.168.2.1:80 (router setup page)
5800 -> 192.168.2.2:5800
5900 -> 192.168.2.2:5900
Firewall is completely disabled on both private and public domains for both the main tower and VPS.
The only time a connection is blocked or timed out is when the viewing computer connects to my server via proxy (barracuda filter'd corporate computer, aol dialup, verizon mobile device, etc..)
If the guest is on an open network (no proxies) then it's fine.
whoops.. lol my main tower's internal ip should be 192.168.2.2, not 2.1...