Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I don't need to lie, I am 21. I need the phone to do research, to study, and I need tabs to stop reloading, because I waste time (time that I don't have) waiting Safari to reload, and then locate what I was reading.

It is not a big deal, but it wastes time. Maybe someday I will laugh about it, but not today. If you don't care, then that's fine. But people who use the phone for something serious do. Specially since it doesn't need to happen. And the issue could be fixed.

Thanks for replying with your age, 21 explains it all. Not saying thats bad, wish I was 21 again, just saying you're 21, you're years away from not caring about these things. I can't wait until these things mean zero to you, life is going to be awesome from then on.

Good luck on your phone research.

Since I'm closing in on being twice as old as Soni, tell me oh ancient one how old I have to be to not care about these things anymore?
 
First of all, I have a Nexus 7 2013 with 2GB of RAM, on KitKat, and I had a Galaxy S4 , with KitKat, tweaked, alot of applications disabled, and they BOTH still had app reloading problems also, as a matter of fact the apps reload noticeably quicker on iOS then on the Android devices I have, apps still refresh quite often on 2gb of RAM on Android, so cry all you want, 2GB would of been really nice, but it's not so serious.

Also, sometimes the page does reload on Safari for me on my 5S that I have, but the times it did reload and I was typing something, it actually came back what I had typed, and the page reloads quite quickly on a A7, if a app refreshes on my 5S, it literally comes back to use within a second and a half or two, its really, really, not that serious.

obviously would of been nice though, but Android is the least optimized OS out of all 3 (windows phone, iOS, Android)
 
Spot on!

People say **** about android users and their forums but you know what... I've been attacked and ridiculed more here than I have on any other tech forum in all my years.

1gigers (any koolaid drinkers) are rude and show absolutely nothing but bitter anecdotes to back their claims. 1gigers, you are the vocal minority. Many forum members won't jump in to voice their opinion because you make this a hostile forum. One that is worth leaving for greener pastures.

We're just tired of arguing. People will believe what they want to believe. I've seen Safari in iOS 8 GM require a refresh with as little as 3 tabs open with only a few Apple apps "open". I doubt anyone would believe me.

If I were to tell people how fast the multitasking app switching was in early iOS 8 betas and the current speed on my 5S using iOS 8 GM is significantly slower people would call me a liar. I remember the switching animation was faster and I could tap on the next app before the animation ended and iOS would recognize the tap. It made the OS so much better to use. People here will tell me it's not a big deal. Yes, it is a big deal. It's the little things that end up bugging the hell out of me.
 
I'm so shocked


But thank god Apple has a higher profit margin, that's what is most important

Right? That $4 wholesale per device with their buying power would have just tanked them.

I love the article saying it would "hurt performance."

Come on... no, less ram hurts performance. Battery life is hardly the same thing, and I think most people will give up a the tiny bit of battery life this would actually eat into. You know, because when a program stalls and isnt usable it's not killing your battery or anything as it tries to get memory and load...

----------

First of all, I have a Nexus 7 2013 with 2GB of RAM, on KitKat, and I had a Galaxy S4 , with KitKat, tweaked, alot of applications disabled, and they BOTH still had app reloading problems also, as a matter of fact the apps reload noticeably quicker on iOS then on the Android devices I have, apps still refresh quite often on 2gb of RAM on Android, so cry all you want, 2GB would of been really nice, but it's not so serious.

Also, sometimes the page does reload on Safari for me on my 5S that I have, but the times it did reload and I was typing something, it actually came back what I had typed, and the page reloads quite quickly on a A7, if a app refreshes on my 5S, it literally comes back to use within a second and a half or two, its really, really, not that serious.

obviously would of been nice though, but Android is the least optimized OS out of all 3 (windows phone, iOS, Android)

Yeah, but IOS isn't really multitasking anything. Your comparison is not valid. On Android, your apps can really still be running in real time behind another running app, and depending on what those apps are can make a difference.
IOS doesn't even allow this!

My G2 lets me run two apps side by side, and I've had no performance hits. If there is one gripe about it, it's that you can disable select apps from running in the background (I'm talking to you Farm Heros saga that drains my battery if I forget to force you closed).

Android is however, very optimized these days. It's devices enabling multitasking this way, like the G2, that break it because of their in house side by side features that are not stock android.

Your Nexus 7 I can't speak to, but doesn't sound like the performance other people have had.

I will give Apple props though because it is the most optimized... and to do this, they also inhibit developers from deploying features in apps and the devices owners from having a great and many options. So it's a preferences game.
 
Right? That $4 wholesale per device with their buying power would have just tanked them.

I love the article saying it would "hurt performance."

Come on... no, less ram hurts performance. Battery life is hardly the same thing, and I think most people will give up a the tiny bit of battery life this would actually eat into. You know, because when a program stalls and isnt usable it's not killing your battery or anything as it tries to get memory and load...

----------



Yeah, but IOS isn't really multitasking anything. Your comparison is not valid. On Android, your apps can really still be running in real time behind another running app, and depending on what those apps are can make a difference.
IOS doesn't even allow this!

My G2 lets me run two apps side by side, and I've had no performance hits. If there is one gripe about it, it's that you can disable select apps from running in the background (I'm talking to you Farm Heros saga that drains my battery if I forget to force you closed).

Android is however, very optimized these days. It's devices enabling multitasking this way, like the G2, that break it because of their in house side by side features that are not stock android.

Your Nexus 7 I can't speak to, but doesn't sound like the performance other people have had.

I will give Apple props though because it is the most optimized... and to do this, they also inhibit developers from deploying features in apps and the devices owners from having a great and many options. So it's a preferences game.

There are certain API's that allow good multi tasking on iOS, virtually almost the same as Android apps, there are alot of apps on iOS that can run in the background real time and in iOS 8, which comes out tommorow, will be even more powerful apps that come with iOS 8, (iOS extensions, 4000 new API's, etc)

Dual apps on a screen is pretty cool I guess, quite cumbersome and counter productive though, only is good on devices with LARGE screens (5+inches)

and many have actually reported the same things as I have said, 2GB of RAM on Android still causes decent app and page reloading,

If a stock Android Nexus 7 tablet running the latest Android OS, with literally very little apps on the device, with all of them updated, with the Chrome Browser on Android tweaked to use even more memory then standard, still has app reloading and tab reloading, it happens to alot of Android users then, you don't get more bareboned and tweaked then my Nexus 7 running also in ART mode. its actually quite a bit slower on the Nexus 7 over a Apple A7, a Apple A7 reloads apps EXTREMELY fast if they happened to pause and need to reload.

You mean stock Android is pretty well optimized these days, A Galaxy S5 is pretty clunky and laggy out the box, that TouchWiz skin is pretty bad with all those tons of preloaded apps and every single home screen filled with garbage, HTC's Sense Skin is pretty light on RAM, much lighter then TouchWiz, not 100% sure of the LG skin and how it performs.

As a heavy user of my tablet and smartphone and these devices ( I have used Android alot and i have used iOS alot also) there really is really not much of a difference in what i can do with multi tasking on both OS's at all

Apple A7 has a L3 cache on board , virtually no SoC's have L3 cache right now, it helps tremendously
 
I have crash issues all the time on my Galaxy Note 3, reboot it several times a week. Wished I had my Galaxy Note 2 back.

I never have crash issues on my Note II.

Before I'm labeled a troll, I do have a MacBook and an iPad.

Hopefully we'll get a good confirmation on the RAM issue after Friday.
 
Quite the contrary. It is you that believes it needs more RAM for completely arbitrary reasons: you think it should have "more" of something because of how much it costs. It's like me saying my car is expensive so it should come with 6 wheels, not 4 and a spare.

Opposite to that, I know it doesn't need more, because if it did, it would be there. Shockingly...Apple is not stupid. Nor are they in the business of shipping sub par hardware.

Right...just like the ipad air. Youre a good apple puppet. That a boy.
 
It's disappointing. But Apple has a tradition of limiting the RAM amount (and harddisk space) to bare minimal on their Macs. So it's not surprising either. I don't care about the RAM amount IF & ONLY IF they can fix the Safari reloading problem on my iPad Air.
 
I don't care about the RAM amount IF & ONLY IF they can fix the Safari reloading problem on my iPad Air.
It's not as if Apple doesn't know about the issue, and user experience aside I don't think Apple's engineers are stupid enough to think that constantly reloading data (especially when done over LTE) uses less power than not. I conclude that Apple management simply doesn't care. You do not fix what you deem irrelevant.
 
It's not as if Apple doesn't know about the issue, and user experience aside I don't think Apple's engineers are stupid enough to think that constantly reloading data (especially when done over LTE) uses less power than not. I conclude that Apple management simply doesn't care. You do not fix what you deem irrelevant.

Page reloading is slower when using wifi. I think Apple expects everyone to be on LTE so it considers the page reloading only a minor bother.
 
Page reloading is slower when using wifi. I think Apple expects everyone to be on LTE so it considers the page reloading only a minor bother.
I don't want more RAM just to prevent reloading, nice though that would be, I want more RAM to improve battery life.
 
I don't want more RAM just to prevent reloading, nice though that would be, I want more RAM to improve battery life.

I don't know if more RAM would cure the Safari page reloading issues. Maybe it will, maybe it won't. But this is a problem that needs fixing. I bet if I file a bug Apple will ask me to use less tabs and try again. Ok, I'll use a max of 2 tabs when any other app is "open" in the background.
 
Page reloading is slower when using wifi. I think Apple expects everyone to be on LTE so it considers the page reloading only a minor bother.


Page reloading is almost instant on wifi , it's ridicuously fast, is your LTE speeds faster then your Wi Fi?
 
Time for a re-cap:

Thread title: "iPhone 6 Plus Might Be Limited to 1 GB of RAM"

Regain your focus and composure, those of you losing your marbles over this.
Keywords are "might" and "be"; it also MIGHT NOT be limited.

Incredulous...

It shouldn't matter, 16 pages in and the experts have convinced me 1 GB is enough!
 
I hear the one handed mode is needed to easily use the phone with one hand... How could that not be useful? "Needed" is up to the person I would think.

In the long run maybe a bad idea. Would be better to encourage developers to move commonly accessed controls (that can't be replaced with gestures) to the bottom of the screen. Having this mode as a crutch may slow down developers reworking their UI's because less necessity. (In the mean time I am busy updating apps, though it's tough to know what works and what doesn't without a phone in hand).
 
Please let's stop with this: "IT'S SAFARI'S FAULT". It is not!! My problem is multitasking. If I switch from one app to the other, the previous is always reloaded because there's no more RAM available. This doesn't happen with my iPhone 5 since it's not 64 bit and thus has more mem available.
 
First of all, I have a Nexus 7 2013 with 2GB of RAM, on KitKat, and I had a Galaxy S4 , with KitKat, tweaked, alot of applications disabled, and they BOTH still had app reloading problems also, as a matter of fact the apps reload noticeably quicker on iOS then on the Android devices I have, apps still refresh quite often on 2gb of RAM on Android, so cry all you want, 2GB would of been really nice, but it's not so serious.

Also, sometimes the page does reload on Safari for me on my 5S that I have, but the times it did reload and I was typing something, it actually came back what I had typed, and the page reloads quite quickly on a A7, if a app refreshes on my 5S, it literally comes back to use within a second and a half or two, its really, really, not that serious.

obviously would of been nice though, but Android is the least optimized OS out of all 3 (windows phone, iOS, Android)

Ummm... either you have 2 very crippled Android devices (maybe Chinese fakes) or you are lying.

I made a video for you...

https://www.youtube.com/watch?v=7brKqKCrvY4&index=1&list=UUeh4nHtj_u5Bwj8WotKtePA

No tab reloads, no app reloads (except email which I purposely set up to reload every time)... and the RAM status says it all. I suspect you have NO idea how Android manages RAM. You should check google on that matter.
 
I've mentioned this earlier in this post. iOS does not page out to the flash storage. Page outs in iOS simply mean that (certain) existing pages are cleared out in memory, so your main storage isn't affected. Performance and battery life can however, benefit from additional memory - it is similar to the CPU's race to sleep concept, where you try to preserve CPU cycles to do useful work.



Virtual memory is indeed supported, but you are correct in that iOS does not page out to a backing store unlike OS X.

Your post is correct, Virtual Memory doesn't necessary mean you are writing pages to the file system.
iOS simply dump apps from memory when it needs more ram for current running application. So more RAM means more apps in memory at the same.
 
The only good news is that the screenshot indicates that not much memory is allocated for graphics ... which might indicate that the GPU has separate graphics memory... on the other hand the phone isn't exactly doing a lot in that screenshot and I'm sure the GPU gets memory dynamically rather than statically, so it might mean nothing.
 
While you're using an application you would likely not experience crashes unless the underlying code was poorly written. But that aside, I believe that the reason why more people are not more vocal about this is that most users would not normally attribute memory to be an issue. Macrumors users consist of a small subset of total iDevice users; many people that do not frequent technology sites (or have other sources of knowledge) would not know what RAM is (e.g. often confusing storage and memory).

Safari reloading aside, that applications cannot multi-task properly is a manifestation of inadequate amounts of memory; to be fair, iOS isn't really designed that way either, as applications are generally suspended soon after you hit the home button, with some exceptions, notably music players. Read through (for instance) game reviews on the app store and you may notice users complaining of crashes or losing progress. This is especially prominent on the iPad line, where games generally take up more memory compared to on the iPhone. When players switch out (e.g. using the home button), it therefore becomes common for them to experience the game reloading entirely once they switch back into it because iOS has killed it. My personal conjecture is that most users do not know what happened, and place fault at the developers for releasing a shoddy app.

Apple has done a fantastic job with providing users with extremely responsive user interfaces, especially because some are prioritized in terms of resource allocation. But if you attempt to be aware of what goes on with iOS (or just how computers work in general), it's difficult not to spot "problem" areas.

Some good points here. I guess the multitasking thing for me is somewhat over rated. I tend to do one thing at a time or play a single game at one time. Sure, a music player might be going in the background but the idea of furiously switching between heavy memory using apps just doesn't seem to be a very common use case.

Good call on people not really knowing what killed an app though. It's easy and makes sense for them to blame the app maker when in fact it could be RAM. I guess overall, it wouldn't have killed apple to throw an extra GB in there. Unless apple can substantiate why adding RAM would have compromised battery performance or something else too much. I doubt it though.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.