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

MikhailT said:
Yes, that high. There's a reason Opera have a massive server farms to do all of those rendering, so that it can serve them back down to your phones as static content that the app and phone will not have to do any work on. It's like loading a book instead of loading a complex series of methods that have to be run (CSS, HTML, Images, JS code that can be from multiple sites, etc), each method would require the use of memory and they often do not overlap. Don't forget that Safari has a policy in place to render at 60FPS to keep it smooth, which requires the app to render off-screen, which eats up more memory.
Click to expand...

I still think Safari has below-optimal optimization. While it's indeed very easy to deduct the fact you've also mentioned based on simple comparative memory usage figures (by comparing the memory usage of a given page on an Retina vs. non-Retina iPads running the same iOS version and iPhones), I do think the offline buffers could have been coded much better; that is, much less memory-hungry.

After all, it's not the CSS / JS scripting support / DOM tree that eats up that much memory, but the screen buffers. Given that Opera also has very smooth scrolling (and, of course, stock widgets like UITableView's), I don't think Safari couldn't have been programmed in a much more memory-conservative way. Again: this is completely independent of the dynamic HTML / scripting support, which can also be clearly seen based on the widly different memory usage figures of different-resolution screens.

----------
watchthisspace said:
So after one hour of iOS 7.1, back to usual for me. Meh nothing amazing.
Click to expand...

The UIWebView memory usage is definitely better, also backed up by my measurements.

----------
gagaliya said:
What the hell are you talking about, what does safari tab switch auto refresh have to do with memory.

This is a bug that was introduced with iOS 7 and it is annoying as hell. It's an issue on both my ipaid air and iPhone 5

It never happened with ios6.

:mad::mad::mad:
Click to expand...

Wrong, Safari in iOS6 crashed as frequently as under iOS7.0.x. There isn't much difference between Safari under the two OS versions. And, actually, despite popular belief, iOS7.0.x uses appr. the same RAM as iOS6 did - at least on iPads.

----------
JT314 said:
First, the spotlight feature still has the same old bug. It crashes every time after you type in the first couple of letters. Then when you go back to it, it works, aggravating.
Click to expand...

As others have mentioned, restore as new. Stock iOS 7.x does NOT have that bug, not even 7.0.x on 64-bit devices.
 
Wow. All this time in beta for a few button tweaks and an ugly bold keyboard? Ok, it seems more stable, but it should have been stable all along. 7.0 was a big fat beta.

7.1 is the True Detective of updates. The early episodes were full of promise. Some of the best stuff never made it to the finale. Ultimately meh.

The pressure to release a new OS every year is going to mean we will continue to be beta testers. .1 is the new .0.
 
Ihatefall said:
While some of the updates are cool....most of the are achievable on a JB "no white point"?!? F.lux is still better, black keyboard?
Click to expand...

Yup, the lack of an f.lux-equivalent is indeed a big pain in the @ss. This is why I keep my "leisure" iPads on 7.0.6 / spoofed 7.1b3, and only update some dev-only iPads / iPhones to 7.1.

----------
nelmat said:
It has EVERYTHING to do with memory (caching the page) and happened just the same in ios6.
Click to expand...

Exactly. Safari crashing has always been an issue under iOS, regardless of the OS version.

----------
C DM said:
Not sure if most of stability, security, various bug fixes, and some overall performance improvements can be achieved through jailbreaks tweaks.
Click to expand...

This is why some people are and will keep staying JB'n on spoofed 7.1b3. It already has the Safari memory / anti-crash optimizations and "only" has major bugs like the lack of Lightning HDMI support. (This is why I only kept my 30-pin devices like my iPad 3 on 7.1b3.)

----------
ColdShadow said:
Because what is written in a release note in not necessarily what users experience.
I've updated my iPad air to 7.1 and within 15 minutes I had my first Safari low memory crash:( checked apple support comminities and there are many reports of ipad airs and rminis crashing in 7.1 just like before.. So no they haven't fixed it.
Click to expand...

They did alleviate the issue, albeit indeed not completely fixed.
 
CarlosQG said:
I was referring to the stock stability, jailbreak messed it a lot!
Click to expand...

You've done it wrong. JB, when done properly(!), in no way messes up a system. I know - I'm a hardcore user and also a JB dev. (See my tweaks over at the Hacks forum here - for example, the muted call recorder and the various camera tweaks.) For example, don't install every theme you run into. Then, a JB'n device can stay as stable as a non-JB'n one.
 
Menneisyys2 said:
I still think Safari has below-optimal optimization. While it's indeed very easy to deduct the fact you've also mentioned based on simple comparative memory usage figures (by comparing the memory usage of a given page on an Retina vs. non-Retina iPads running the same iOS version and iPhones), I do think the offline buffers could have been coded much better; that is, much less memory-hungry.

After all, it's not the CSS / JS scripting support / DOM tree that eats up that much memory, but the screen buffers. Given that Opera also has very smooth scrolling (and, of course, stock widgets like UITableView's), I don't think Safari couldn't have been programmed in a much more memory-conservative way. Again: this is completely independent of the dynamic HTML / scripting support, which can also be clearly seen based on the widly different memory usage figures of different-resolution screens.

----------



The UIWebView memory usage is definitely better, also backed up by my measurements.

----------



Wrong, Safari in iOS6 crashed as frequently as under iOS7.0.x. There isn't much difference between Safari under the two OS versions. And, actually, despite popular belief, iOS7.0.x uses appr. the same RAM as iOS6 did - at least on iPads.

----------



As others have mentioned, restore as new. Stock iOS 7.x does NOT have that bug, not even 7.0.x on 64-bit devices.
Click to expand...
Never had any Safari crashes or phone resprings or restarts in iOS 6 or earlier, but I've definitely seen all of those in iOS 7.

----------
mcdj said:
Wow. All this time in beta for a few button tweaks and an ugly bold keyboard? Ok, it seems more stable, but it should have been stable all along. 7.0 was a big fat beta.

7.1 is the True Detective of updates. The early episodes were full of promise. Some of the best stuff never made it to the finale. Ultimately meh.

The pressure to release a new OS every year is going to mean we will continue to be beta testers. .1 is the new .0.
Click to expand...
Both iOS 7.1 and True Detective have so much good stuff underneath that unfortunately just goes unnoticed or even simply ignored by different people.
 
Photos Backend

Impact: Deleted images may still appear in the Photos app underneath transparent images

Description: Deleting an image from the asset library did not delete cached versions of the image. This issue was addressed through improved cache management.

Settings - Accounts

Impact: A person with physical access to the device may be able to disable Find My iPhone without entering an iCloud password

Description: A state management issue existed in the handling of the Find My iPhone state. This issue was addressed through improved handling of Find My iPhone state.

FaceTime

Impact: A person with physical access to the device may be able to access FaceTime contacts from the lock screen

Description: FaceTime contacts on a locked device could be exposed by making a failed FaceTime call from the lock screen. This issue was addressed through improved handling of FaceTime calls.

Settings - Accounts

Impact: A person with physical access to the device may be able to disable Find My iPhone without entering an iCloud password

Description: A state management issue existed in the handling of the Find My iPhone state. This issue was addressed through improved handling of Find My iPhone state.


Atlast they fixed those issues :)
 
Jjaro said:
It's a damn shame Apple patched the jailbreak. Steve Jobs is gone, why can't they just forget about the BS and let people do what they want with their phones? ******** if you ask me.
Click to expand...

Because you will ask for their warranty service if it bricks - yes Apple will deny service if they can check; but if it can't even be turned on, then Apple will be tricked to give you a replacement unit.

----------
thadoggfather said:
Hurry jailbreakers, 7.0.6 signing window will be shut soon and then R.I.P. evasi0n7

7.1b2+JB'ers, more extraordinary we are

:apple:

On another note:

FINALLY!
Click to expand...
I still don't understand why the evaders chose to release the jailbreak when iOS 7.1 was still in beta stage. They wasted the exploit.
 
Habakuk said:
No matter if you need CarPlay or not, you have to look at this webpage:

http://www.apple.com/ios/carplay/

And keep scrolling. There is an interesting 3D effect that I've never seen before (foreground and background are moving/shifting). Works on all Safaris.
Click to expand...


Seems apple sold out to the car manufacturers with iOS 7. We are all meant to buy cars not walk. iOS 7 the iDontwalkanymoreOS

Apple ... making iOS look crap... unless you drive
 
My calender in notification center shows from 8am to midnight (I have an calender event starts on a day, finishes 15 days later).

That's a hell of a lot of scrolling down to see my reminders. Not impressed.


To me the whole look of ios 7 with its greys and blacks looks dirty.

I prefer reduce transparency on because I like the black notification center but it looks like its a I don't want to do this effort. Maybe because it resembles Scott's work too closely.

And I liked the dock. What is this **** grey bar? Wtf
 
haruhiko said:
I still don't understand why the evaders chose to release the jailbreak when iOS 7.1 was still in beta stage. They wasted the exploit.
Click to expand...

Well, but at least we have had almost 4 months of JB joy. Don't forget that the new, 64-bit devices had had no previous JB's so anyone wanting f.lux, call recorders, camera tweaks etc. couldn't have any kind of access to those.

And many of us have upgraded to 7.1b3 (the last JB'able 7.1 beta), which already has the improved memory management.
 
Menneisyys2 said:
Well, but at least we have had almost 4 months of JB joy. Don't forget that the new, 64-bit devices had had no previous JB's so anyone wanting f.lux, call recorders, camera tweaks etc. couldn't have any kind of access to those.



And many of us have upgraded to 7.1b3 (the last JB'able 7.1 beta), which already has the improved memory management.
Click to expand...


The problem is that betas will expire.
 
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