Well according to www.apple.com.au for a long time new iPad had LTE in Australia (and of course, it did not).
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
New Features in iOS 6 Receive Spotty Support from Older Devices
- Thread starter MacRumors
- Start date
- Sort by reaction score
Well according to www.apple.com.au for a long time new iPad had LTE in Australia (and of course, it did not).
I'm confused and I think this article is wrong. I have the iphone 4 and ipad 2 with iOS 6 Beta and the turn by turn works on iphone 4, just no flyover, also the flyover functionality works on ipad 2 as well.
I did however just try facetime over 3G and it didn't work, said that I need to connect to wi-fi. However, we all know that there is no technical reason for this not to work so Apple need to pull their finger out here.
I did however just try facetime over 3G and it didn't work, said that I need to connect to wi-fi. However, we all know that there is no technical reason for this not to work so Apple need to pull their finger out here.
This week has been the perfect storm against going with iPhone 5 this fall.
1. Only 4 inches
2. Lackluster iOS upgrades
3. Verizon family plan
I have until June 28 to upgrade my phone in order to keep unlimited data. So I'm going Samsung S3. Not paying full retail on the next iPhone to keep my grandfathered data plan. Try doing LTE facetime when sharing data.
1. Only 4 inches
2. Lackluster iOS upgrades
3. Verizon family plan
I have until June 28 to upgrade my phone in order to keep unlimited data. So I'm going Samsung S3. Not paying full retail on the next iPhone to keep my grandfathered data plan. Try doing LTE facetime when sharing data.
I read a comment yesterday explaining the difference between a 3GS and iPad1. They both have 256MB of RAM, and the iPad has a faster CPU than the 3GS. However the iPad1 has to use more RAM to drive the graphics for the screen. Using more RAM to drive the screen of the iPad1 may cripple the iPad1 more than the 3GS.
----------
Not the iPad 2
I didn't even like the guy, so you're barking up the wrong tree.
Just ignore the Jobs part, what sort of defense is that they've been doing it for a quite a while? WTF, officer, I've been beating my wife for years, why do you have to go and arrest me now?
Or maybe you're not defending them and just agreeing by being disagreeable? IDK, I you have to work at flushing out what you're trying to say.
Is it a good thing or a bad thing they're denying new features to old hardware? In my book it's a dumb move today, and was dumb back a year ago when they kept Siri from the iPhone 4.
I can answer what hardware will be on iPhone 5 that isnt on iPhone 4S (or 4, or 3GS or 3)-
4G LTE Connectivity and whatever other improvements that brings will be the differnce
LOL! All I can say is that i'm happy i have an iPhone 4S if the next iPhone will look anything like the leaks. I'll probably hold out until the 8th Generation iPhone, since this year the 6th generation iPhone is going to be released.
Also, it makes no sense to call the next iPhone, the iPhone 5 when it'll be the 6th generation iPhone. I can see Apple calling it the iPhone 4G or The New iPhone though.
For me, until i see an official name, i go by the generation number or year, so iPhone 6 and 2012 MacBook Pro.
Also, it makes no sense to call the next iPhone, the iPhone 5 when it'll be the 6th generation iPhone. I can see Apple calling it the iPhone 4G or The New iPhone though.
For me, until i see an official name, i go by the generation number or year, so iPhone 6 and 2012 MacBook Pro.
It does blow. Unfortunately... most of these companies only make money on the initial hardware sale. Of course they want you to buy a new model.
At least Apple can make some money from apps and games.... but the bulk of their income is from hardware.
Other manufacturers only have that initial sale to make any money from a phone... and you wonder why they drag their feet on updates.
----------
So wait... you don't think Apple tested iOS 6 on an iPad 1? I bet Apple does more testing than any other manufacturer on the planet.
But I don't know why Apple does what it does. I'm just a guy reading MacRumors.
Only Apple knows why...
I'm sure somebody's already posted this, but I want to vent. I'm annoyed that Apple's not putting Siri on the iPad2. The iPad2 and iPhone 4s have basically the same specs. Its not like the iPad2 is incapable of running Siri. Its really frustrating that Apple relegated this feature only to the iPad3. :-/
Are you Tim Cook? It's like you're masochistic and don't understand that other people don't like getting shafted.
Sorry, I expect Apple to update it's iOS, just as I would if I had an Android. Thankfully, Apple does a pretty good job of this, but they sure could do better. Namely, stop using software to updates to differentiate and prod people to upgrade. It's not like they aren't making enough money. And, fair is fair, they can do what they want, but I don't have to like it or rationalize it's somehow in my best interest.
LOL... you're right... I didn't think that comment out.
But do you know who did think it out? Apple.
They made a decision... and we're all stuck with the consequences.
It seems appropriate to share my experience/thoughts regarding fragmentation on the Android home front. It's probably not as bad as some people make it out to be, but in some ways it can get ya.
There are forms of fragmentation that arise from having so many different hardware configurations and it's not always easy to account for this, even as you try to create a system that is designed to work around this issue. Look at the ultimate of fragmentation. The home computer, Windows. Its a mess! Microsoft has done well though to minimize the impact of fragmentation. I dont think Android is quite there yet in some regards.
On Apple, you're dealing with different generation of phones. The supposed fragmentation that people say is going on; I don't really consider it fragmentation. Certainly Apple blocks certain features because the older hardware can't handle it and in some cases because they want to encourage users to upgrade to the latest hardware.
In any case, it's natural to assume that older hardware will slowly be phased out. Its silly for people to think any company should support older technology and hardware indefinitely. We cant push them and desire them to constantly improve, but also impose upon them the need to make everything backwards compatible. It only breeds problems. It makes things needlessly complex and stifles the newest innovations from being fully realized.
When we come to Android, we find that we have a number of current generation phones that have differing specifications. This is the problem of fragmentation, right here, as I see it. With Apple we have the iPhone and the iPad and less than a dozen antiquated models to deal with. Esentally though we have two target platforms and its a little easier to roll things back for the older models. When dealing with Android this gets a little more complex because we have such a vast number of current generation models and then also a larger number of antiquated models we have to deal with.
For simple applications this may not be that big of a deal. Android has a great setup that allows your application to scale and adjust for whatever hardware it finds itself on. As your application becomes more complex though, this becomes more of a difficult task.
The best way I can relate this is screen size. This is what I had to deal with in the development of my own application. I was developing an application for a touchscreen device, mainly a slate computing device like the iPad. I started developing it on Windows in response to the news of Windows8 and looked into pushing it onto the ipad and/or Android tablets.
The application I made was very graphic/ui driven. Android has a great toolset for creating a UI that can be dynamically adjusted for different screen sizes. The problem with my application is that it didn't lend itself well to being dynamically sized in that manner. My graphic elements were very specific and deliberate. I created my interface for a set aspect ratio. You can make an argument against creating an interface the way that I did, but it was part of the design goal of my program. It did a function which other applications did, but those other applications were crude and ugly at best. The goal of my application was to create something beautiful, that part of the experience of using it, was seeing it.
This is where Android let me down and Apple really showed what a great system it can be to develop for. Even with the addition of retina displays in the mix, the aspect ratio was kept the same. I didnt have to recreate my graphic driven interface for so many different screen sizes. What really frustrated me is that I couldnt do in Android what I could easily do in Windows with their development tools. This frustrated me with iOS too, but for a different reason.
My application was originally developed on Windows using their development tools. The application would dynamically scale for whatever screen size it was put on. It would letterbox automatically if the aspect ratio changed. I really liked this. I didnt mind the letterboxing; it allowed me to keep my vision of what I wanted and didnt restrict me to just one specific hardware setup. Furthermore it was extremely easy to develop for. Android was easy to program for, but their UI system didnt lend itself well to my style of application at all, it was frustrating. Apple was better with their development tools when it came to this sort of graphic driven UI, but I felt their development tools were a bit clumsy and a pain to work with.
Both Apple and Android though, they suffered from trying too hard to push you into their design philosophies of how the interface should look and function.
Fragmentation isnt the black and white subject people make it out to be. It isnt just about showing charts of what features are and arent supported. It manifests itself in small ways that can be simple, or can be very frustrating. To the end user it may not be something they see at all, but to the developer, it can be everywhere. The sort of fragmentation that exists in Android isnt the same as what you would see with Apple. Android approaches fragmentation thoughtfully and wonderfully, but even with the way theyve approached it, youll still run into it. Apple can be argued to have similar issues, but theirs is more the issue of supporting older models, and not so much of supporting 100 different configurations of a current generation of hardware.
There are forms of fragmentation that arise from having so many different hardware configurations and it's not always easy to account for this, even as you try to create a system that is designed to work around this issue. Look at the ultimate of fragmentation. The home computer, Windows. Its a mess! Microsoft has done well though to minimize the impact of fragmentation. I dont think Android is quite there yet in some regards.
On Apple, you're dealing with different generation of phones. The supposed fragmentation that people say is going on; I don't really consider it fragmentation. Certainly Apple blocks certain features because the older hardware can't handle it and in some cases because they want to encourage users to upgrade to the latest hardware.
In any case, it's natural to assume that older hardware will slowly be phased out. Its silly for people to think any company should support older technology and hardware indefinitely. We cant push them and desire them to constantly improve, but also impose upon them the need to make everything backwards compatible. It only breeds problems. It makes things needlessly complex and stifles the newest innovations from being fully realized.
When we come to Android, we find that we have a number of current generation phones that have differing specifications. This is the problem of fragmentation, right here, as I see it. With Apple we have the iPhone and the iPad and less than a dozen antiquated models to deal with. Esentally though we have two target platforms and its a little easier to roll things back for the older models. When dealing with Android this gets a little more complex because we have such a vast number of current generation models and then also a larger number of antiquated models we have to deal with.
For simple applications this may not be that big of a deal. Android has a great setup that allows your application to scale and adjust for whatever hardware it finds itself on. As your application becomes more complex though, this becomes more of a difficult task.
The best way I can relate this is screen size. This is what I had to deal with in the development of my own application. I was developing an application for a touchscreen device, mainly a slate computing device like the iPad. I started developing it on Windows in response to the news of Windows8 and looked into pushing it onto the ipad and/or Android tablets.
The application I made was very graphic/ui driven. Android has a great toolset for creating a UI that can be dynamically adjusted for different screen sizes. The problem with my application is that it didn't lend itself well to being dynamically sized in that manner. My graphic elements were very specific and deliberate. I created my interface for a set aspect ratio. You can make an argument against creating an interface the way that I did, but it was part of the design goal of my program. It did a function which other applications did, but those other applications were crude and ugly at best. The goal of my application was to create something beautiful, that part of the experience of using it, was seeing it.
This is where Android let me down and Apple really showed what a great system it can be to develop for. Even with the addition of retina displays in the mix, the aspect ratio was kept the same. I didnt have to recreate my graphic driven interface for so many different screen sizes. What really frustrated me is that I couldnt do in Android what I could easily do in Windows with their development tools. This frustrated me with iOS too, but for a different reason.
My application was originally developed on Windows using their development tools. The application would dynamically scale for whatever screen size it was put on. It would letterbox automatically if the aspect ratio changed. I really liked this. I didnt mind the letterboxing; it allowed me to keep my vision of what I wanted and didnt restrict me to just one specific hardware setup. Furthermore it was extremely easy to develop for. Android was easy to program for, but their UI system didnt lend itself well to my style of application at all, it was frustrating. Apple was better with their development tools when it came to this sort of graphic driven UI, but I felt their development tools were a bit clumsy and a pain to work with.
Both Apple and Android though, they suffered from trying too hard to push you into their design philosophies of how the interface should look and function.
Fragmentation isnt the black and white subject people make it out to be. It isnt just about showing charts of what features are and arent supported. It manifests itself in small ways that can be simple, or can be very frustrating. To the end user it may not be something they see at all, but to the developer, it can be everywhere. The sort of fragmentation that exists in Android isnt the same as what you would see with Apple. Android approaches fragmentation thoughtfully and wonderfully, but even with the way theyve approached it, youll still run into it. Apple can be argued to have similar issues, but theirs is more the issue of supporting older models, and not so much of supporting 100 different configurations of a current generation of hardware.
Which Apple website (country)? I think Apple in the US is being forced to cripple the iPhone 4 by the carriers?
Are their countries that allow FaceTime over 3G on the iPhone 4 right now?
It makes equally little sense that the 5th generation iPhone was called the 4s. If we were numbering off by generation, the history of iPhone would've been different
according to this from the apple ios 6 page facetime is not available for the iphone 4.
"FaceTime over a cellular network requires iPhone 4S or iPad (3rd generation) with cellular data capability. Carrier data charges may apply. FaceTime is not available in all countries."
The AU page for me is showing the iPhone 4 and iPad 2 supporting FaceTime on 3G for me.
Do you really think Apple even bothered testing Face Time over 3G with the iPhone 4? they are forming a pattern of holding back something to push sales...
And sorry, despite all the hardware excuses about Siri on the iPhone 4, it's been found to work just fine. Perhaps not as accurate... but crappy cheap nearly free android phones do dication better than Siri on the 4S....
It's simply called GREED. It's not complainers... it's called educated. Graphics related items I can see... but speech and video calling? No.
Agreed, I thought this gen should've been called 5 for sure, but guess Apple decided to go against common sense.
Still, i think they can get away calling a 5th gen a 4S.. i don't think they can get away calling a 6th gen a 5.
Remember iPhone 4 users. Be sure to upgrade to ios 6 so you can get a crap map program. This is the 1st upgrade since the 3G release I am NOT looking forward to and probably won't put on.
All I wanted was turn by turn for my iPhone4, Wahh. Oh well, Im due for an upgrade in January, hopefully Apple has something nice planned for the iPhone5 or whatever you want to call it.