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.
iOS 10.3 Beta 1
- Thread starter GrievingFob606
- Start date
- Sort by reaction score
iPhone 7 Plus app switcher seriously smooth finally. Animation on opening and closing apps - way smoother but sometimes on some apps like Messages and Safari, the very end of the animations judder. This can be gotten rid of completely by selecting a dynamic wallpaper as your background. The whole OS is smoothest with one of these dynamic wallpapers selected IMO.
This is probably due to some API changes. Beta cycle will give developers enough time to adapt.
Here ya go
Settings
Settings > Name
Settings > Name > Device
Settings > Privacy
Settings > Privacy > Analytics
Thanks - much appreciated!
I was curious how they were laying out all this info, and where Family Sharing was going to end up.
How is the scrolling performance on 6s Plus? Does it still have the bad loading pauses and jitters when scrolling that has plagued all iOS 10 releases? It was so bad in Safari for me as to render it unusable due to annoyance, so I went back to 9.3 while I could and have stayed there ever since (at least scrolling was smooth). If this gets fixed on the 6s Plus and returned to 9.3 level smoothness, than I can finally update.
Hell...i'd be happy if they would at least fix the field test for qualcomm. The new fields would be helpful, especially for CA information, but haven't been able to see bandwidth and connected band now a couple of years...
In iOS10 they’ve made change how UI is given to user: parts of screen/webpage/app that are invisible to the user are pre-rendered and should be presented with much more fluidity than on previous releases. But in many cases instead of fluidity users got stutter. Mostly because app developers didn’t dequeue their table or collection view’s correctly, or heavy javascript web pages didn’t conform to the DOM.
Also: with APFS focused on foreground app tasks - you should see performance gains and overall more fluid feel.
Don't thin
heres the new email thing
Looks stupid
Everything's a ****ing bubble now
Last edited:
Interesting technical aspect. I had read previously where scrolling was supposed to be "improved" in iOS 10, yet I never saw this. In fact, it felt like a huge regression. I've noticed the scrolling is the worst in Safari (Apple's own app which you would think would be updated - perhaps because more visual content needs to be loaded while scrolling). I've also seen it in Messages, Twitter, Mail, and Music. Really, anything where there is a lot of information or a long list to scroll through. I never had a performance issue like this before on iOS 9, so when updating to iOS 10 to see the extreme jitters and white space pauses as the content is loaded was quite jolting, and had the effect of making it seem like a large performance regression. Besides, it's just plain annoying if you are scrolling a web article and have to wait multiple times for it to load and see these visual jitters when this just worked on iOS 9 without issue. Perhaps APFS will help, but it seems this just isn't much of an issue for Apple as it has not improved much throughout any of the iOS 10 releases.
Only major issue I can foresee is that iTunes backups won't work until iTunes is updated. I updated on 3 devices (5, 7 and iPad Air) had no problems.
The scrolling overall is better, no doubt about it. However it still lags when you scroll through the list of apps in Settings - Data Usage.
I'm on a 7 Plus.
I'm on a 7 Plus.
Already happened in iOS 10.Also, was it possible to play YouTube previews within iMessage as full screen before? If not, it is now. Only found this out nowPretty cool to be able to watch a vid fullscreen without leaving the messages app.
There is a couple of things that makes the whole „simply showing a webpage” complicated.
iOS apps can be constructed from various APIs - UITableView, UICollectionView, WKWebView, to name most popular; all of those api’s have to conform to very strict rules if you want them to work fluidly on iOS devices. Conforming to those rules or following guidelines to create your custom views are time-consuming and are slowing down development, so we end up with everyone using code that are bloated, are repeating itself, don’t care about strong reference cycle (long story short: when object - like image you see scrolling through an app - is created and is no longer used: should be freed from memory, iOS provides it with ARC, but noone really cares - it is held in memory because some completely pointless variable in app stills refers to that object). That is our first problem.
If you open app written without consideration of memory constrains of mobile platform - firstly it works fluid, as it is empty or filled with not that much data (and it is indirectly related to actual amount of data, as app with hundreds of megabytes can work much more fluid that app only uses only 20 megabytes of ram). But in time you will see that once it was an fluid app it becomes more and more bloated. There could be a couple of reasons: reading and hoarding temporary objects in memory, problems with asynchronous - as it is, reading in background thread - reading from database, using JSON connections that have a long time to complete request.
As iOS have become more and more fully-front-multitasking (and with many processes running in the background) operating system - things that once were really simple, like forcing app to save it’s state and quit - became complicated. There is a base of tasks that cannot be force-quitted to free memory. And there are apps that, even if they are in background, finishing their tasks, uploading data, or doing whatever is allowed by iOS (they even may fetching data, if they received push notification, even if their state was suspended or you have force-quitted them recently).
So: first you have some very memory consuming and racing for the memory (even if force-quitted) apps like facebook (which abuses couple of iOS guidlines and probably uses some dirty workarounds for staying always-alive, VOIP kit to name the one), twitter, maybe instagram (I’m not familiar with it’s memory management, but I suppose it’s similiar, as in: whatsapp, google hangouts, etc.).
Second: iOS memory management frees amount of memory that is within a scope of your request: it doesn’t know if you scroll back in your imessage history and there is 15 megabytes animated GIF. If it is requested: it would free memory that are being used by some app - and provide it to imessage. (And no, making iPhone or iPad 64 gb RAM version would not help in this case).
APFS can help in cases when reading from disk (like scrolling in imessage, providing app with GIF file) because it will have higher priority, and probably could be prefetched with some system options.
And there is a problem with web pages: modern web pages are full of javascript and whatever they think that they are loading data. They mostly do it synchronously, even if a lone developer thought thoroughly to make his chunk of work conforms to DOM. When you view a webpage you should see only a part of a webpage that is a part of the DOM structure, not all of crazy api-css-style-json-ajax-with references to twenty or so web pages providing some sort of code needed to work-code. That is when you browse through an bloated webpage you receive subpar user experience.
Web view have to rebuild from http/json/yourmomma request (still: in memory) to show the portion of screen you want to view.
It’s only a scratch of the problem. But: yes, this is why web/web-js-based-app/apps are causing a not-fluid scrolling.
Did it really? I rely on those weekly to purge Real Racing 3 data I no longer need. That could be problematic for me. I wonder if an update can bring it back, or if its permanently gone.
This blows. Tried resetting network settings and still didn't help. Really not in the mood to revert back to 10.2.1 lol
Won't be able to restore back to 10.2.1 since 10.3 updated to the new APFS. Can't go back.
I only use ATTWS for my iPhones, VZW for iPads and iPhones. I roam between USCC and VZW territory often, and get that "no data" bit on my iPads mainly when I'm in USCC territory for a day or more, re-provisioning the line's account always fixes it, at least until I need to roam again for more than 24 hours or so.
Try re-provisioning your account, see if that fixes your issues. The VZW version: https://www.verizonwireless.com/support/knowledge-base-41067/
what? like any other way to revert when its still being signed...restore as new then restore backup....like im doing now cause even steam app dont work anymore on it.