Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Releases iOS 7.1 With CarPlay, Touch ID Improvements, Visual Tweaks

My 5s is snappy so far hope it stays this way. Very great update so far.
 
They fixed an issue that so annoyed me!

I am so happy that they fixed the issue on the lock screen with the volume and track time. It used to dance around when you tried to adjust it. It is now stationary!! This and the better contrast in viewing text has me loving my iPhone again. Yea to 7.1!!!
 
Please give me back the darker keyboard, the larger caller picture and the slide to turn off screen! The new keyboard cap locks is confusing the darker keyboard was easier to look at.
 
v1p said:
I'll do it, but before that I'll love to hear someone using iPhone 5 telling me his Control Center is as smooth as butter on the lock screen.
Click to expand...

My iPhone 5 has a buttery smooth Control Center on the lock screen.
 
Michael Goff said:
I don't think it is a software problem that Apple can fix, to be honest. The website just needs a lot of resources, and the main one it needs more of is RAM. Software optimization can only do so much. It's gotten a lot better, but there's a reason why my RT loads it better than an Air or an iPad 4.

RAM is important.
Click to expand...

Ah, I see. Well you've convinced me but some others here just won't let up. I can see if this was happening on nearly every common website but some people here keep posting links to webpages that looked like they were coded from the same developer who coded Myspace. :eek:. Their mentality is "If it doesn't work on this crazy website then the iPad is defective or has bad ram or Apple just screwed up". They wouldn't dare blame the website developer.

Yeah, I gotcha about the RT loading better than the iPad, it's because it's using I.E. and most likely that developer coded with that browser in mind. Luckily times have changed and not many websites are dedicated to I.E. anymore.
 
trifid said:
shut, the 15-sec back/forward on lock screen for podcasts is gone. This was extremely convenient to have, now I have to do more steps to reach the podcast app :(
Click to expand...
There was an update to the Podcasts app today to address that issue.

----------
patent10021 said:
Wow, soon to be 1,000 replies. What's all the fuss about?
Click to expand...
Nothing at all, just people talking about their day and stuff.
 
Michael Goff said:
RAM is one of the least expensive component in the iPad Air. I don't know what you're talking about by saying that RAM is expensive.
Click to expand...

1 GB of LPDDR2 is cheap. 1 GB OF LPDDR3 is more expensive. 2 GB of LPDDR2 is even more expensive, and 2 GB of LPDDR3 is most expensive. Apple went one level up and I agree with them.
 
rablat said:
You can do whatever you want with the phone now. They just don't want you screwing with their software.
Click to expand...

Of all the eight people who quoted me, I am going to respond only to you. Screwing with their software? It's MY phone.

Also, yes, those of you who said they were patching security exploits are right. My bad. But the option to JB should be there and allowed, at MY risk.

Edit: I am happy though that they fixed the crashes. That was driving me crazy. Guess maybe next time Apple shouldn't release half-finished software to the masses. I have never felt that Apple had ever released a version of iOS that was buggy before, but they did it with iOS 7 in order to meet the deadline. They should have waited and not given in to the pressure to get it out there and done it right the first time.
 
Last edited:
Menneisyys2 said:
It still crashes, but, WRT Safari or third-party apps using UIWebView, much less frequently / later, after loading significantly more content. See my earlier reports.

Explanation: UIWebView (on which Safari is also based on) is a VERY memory-hungry widget - a Web page like nin.com can easily allocate over 300 Mbytes of RAM on a 32-bit (iPad3/4) Retina iPad (20-30% more on a 64-bit one - the rMini and the Air). It was one of the major causes for crashes under 7.0.x.

The situation is MUCH better in 7.1, also backed up by my independent and properly measured figures and tests.

----------



Yup, NEVER restore backups, no matter what some people say.
Click to expand...
While in some cases and for various reasons it's better to start from scratch, for majority of typical users simply updating or even restoring and putting a backup back on has worked and will work just fine.

----------
sualpine said:
Never never never do this! You are forcing the operating system to shut down uncleanly. It is a potential issue for the filesystem. You are at a risk of data corruption and data loss if you do this. Absolutely ZERO benefit to do this instead of a normal power cycle. Stop spreading the misinformation.
Click to expand...
If anything this is misinformation--nothing will happen to your phone when you restart it like that, and in some cases, for whatever reason, a restart like that will actually clear things up a bit better than a shutdown (followed by turning it back on).
 
Menneisyys2 said:
Again: you're wrong. No matter how hard you try to make your Web pages standards-compliant and clean, iOS devices will allocate heaps (at least tens of Megabytes for a casual-sized Web page on a high-res device like all Retina iPads) of memory to load them.

It's not the question of proper, well-formed Web coding but that of the memory needs of UIWebView.

Again: I've been coding & benchmarking UIWebView-based apps on iOS for years. I know all its little secrets. I do know how much memory UIWebView allocates - even with "proper" Web pages.
Click to expand...

If you're a "coder", then you'd know that no one gives a crap about how you're right and they're wrong. It just has to work. That's why if you were good at your job, you'd test against them instead of claiming they should test against you.

----------
C DM said:
While in some cases and for various reasons it's better to start from scratch, for majority of typical users simply updating or even restoring and putting a backup back on has worked and will work just fine.

----------

If anything this is misinformation--nothing will happen to your phone when you restart it like that, and in some cases, for whatever reason, a restart like that will actually clear things up a bit better than a shutdown (followed by turning it back on).
Click to expand...

I guess you've never heard of HFS+ being notorious for data loss and silent disk corruption. Please visit http://arstechnica.com/apple/2011/07/mac-os-x-10-7/12/. At the very least, you are invoking fsck_hfs and a consistency check. Most likely, you will experience a successful repair, which is why the next boot after a hard shutdown takes longer. Worst case scenario, you are causing yourself a restore, directory damage, corrupted photos database (when they are all showing black), etc. Just because there is a low repair failure rate doesn't mean you should subject yourself to the risk. Learn about the filesystem that you use and get back at me.
 
sualpine said:
Never never never do this! You are forcing the operating system to shut down uncleanly. It is a potential issue for the filesystem. You are at a risk of data corruption and data loss if you do this. Absolutely ZERO benefit to do this instead of a normal power cycle. Stop spreading the misinformation.
Click to expand...
Hm.
 
sualpine said:
If you're a "coder", then you'd know that no one gives a crap about how you're right and they're wrong. It just has to work. That's why if you were good at your job, you'd test against them instead of claiming they should test against you.

----------



I guess you've never heard of HFS+ being notorious for data loss and silent disk corruption. Please visit http://arstechnica.com/apple/2011/07/mac-os-x-10-7/12/. At the very least, you are invoking fsck_hfs and a consistency check. Most likely, you will experience a successful repair, which is why the next boot after a hard shutdown takes longer. Worst case scenario, you are causing yourself a restore, directory damage, corrupted photos database (when they are all showing black), etc. Just because there is a low repair failure rate doesn't mean you should subject yourself to the risk. Learn about the filesystem that you use and get back at me.
Click to expand...
And there are similar iOS articles and/or some reports of people suffering from any issues related to that with iOS devices?

Seems like even if the risk is not at 0 it's so close that it's pretty much inconsequential especially when compared to all kinds of more risky things that people still normally do without a second thought and do just fine with them. There is risk with anything in life realistically speaking, but it's got to be balanced against reality, otherwise pretty much no one would be able to function or do much in the real world.
 
Jjaro said:
What?! I did the ALL THE TIME on my iPhones (since the iPhone 3G) and NEVER had problems with data loss or corruption. Where ever you read this/heard this was incorrect.
Click to expand...

Read above. Every time you did it, you were successfully repaired by fsck_hfs. It could have been possible the repair failed, but in your case, it was successful.
 
Love the update and I was one of the people who hated 7.0. This feels very well polished. What in the world is the icon next to my Bluetooth? Looks like a telephone above a keyboard?
 
On my iPhone 5 the clear GPS symbol won't go away and it's killing my battery


Please help, all my apps are off
 
Aluminum213 said:
On my iPhone 5 the clear GPS symbol won't go away and it's killing my battery


Please help, all my apps are off
Click to expand...

Apps that constantly use location tracking, such as Nike+ Move, will constantly use your location even if you quit the app if Background app Refresh is on for that app. To find the culprits, go to Settings, Privacy, Location Services, and find which apps have the purple arrows next to them.
 
C DM said:
While in some cases and for various reasons it's better to start from scratch, for majority of typical users simply updating or even restoring and putting a backup back on has worked and will work just fine.
Click to expand...

All iOS forums are full of "my battery life sucks"-type of messages. Apart from real hardware failures (e.g., the notoriously bad iPhone5 batteries), most of them were caused by restoring previous backups after an upgrade. (Or an OTA upgrade.)

I, who never ever restore but always do clean, full restore-based upgrades, have never had any battery problems. (I've been an iOS user since the beginning and have almost all models even now. I even have two iPad3's.)
 
sualpine said:
Settings > Privacy > Location Services > System Services
Click to expand...

It's always been on and it's never like this, my LTE iPad Air also has location services on but th clear gps symbol isn't on


It's not supposed to be running constantly
 
Tyler23 said:
Apps that constantly use location tracking, such as Nike+ Move, will constantly use your location even if you quit the app if Background app Refresh is on for that app. To find the culprits, go to Settings, Privacy, Location Services, and find which apps have the purple arrows next to them.
Click to expand...

But why wasn't this happening before 7.1? This happened right after I updated to 7.1
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back