msrb21
New member
With the 8.1 Dev Preview, my Lumia 1020 runs faster. The animation and everything is faster and smoother too. Will it be the same for a Lumia 920?
With the 8.1 Dev Preview, my Lumia 1020 runs faster. The animation and everything is faster and smoother too. Will it be the same for a Lumia 920?
Theoretically yes, with the small exception being that the 920 has less breathing room. (1 GB of RAM vs 2).
Any big difference between the 920 with 1020? Not only camera and ram. I'm very tempted to pick up this or wait 1520 prices drop down
Sent from my Nokia Lumia 920 using Tapatalk
Any big difference between the 920 with 1020? Not only camera and ram. I'm very tempted to pick up this or wait 1520 prices drop down ��
Sent from my Nokia Lumia 920 using Tapatalk
I recently upgraded from 920 to 1020, but I'll tell you that i don't think it's worth paying for the upgrade. You lose wireless charging and you get an AMOLED screen which is worse than LCD in my opinion. When you look at the screen in the dark you can see imperfections on any AMOLED and when you tilt the screen, you start to get blue tint. Alsoo low light images are worse and darker (I've heard this is because of the lower F-stop) and the camera is altogether much slower. So...if you think the ability to see more when zoomed all the way into pictures is worth all the hassle, go for it, otherwise I'd say wait for the 930 or 1030 whenever it comes
WP8.1 no longer uses a quota based system. WP8.1 employs a far more sophisticated memory management system than what WP8.0 had, making it even harder to explain. It definitely would require a lot more text than what I'm willing to write here. If enough people are interested however, we could maybe open a separate thread on the issue.
You said that WP 8 doesn't let apps use the other GB; does 8.1, since you say it's changed memory management? There are other Lumias with 2 GB like the 1520; would the OS really keep wasting half the RAM on these devices?
The people engineering this stuff certainly thought of that. It's just not that simple. For one, "dumping an app out of memory" takes time. Many apps must save their state before exiting (the picture you just ran a filter on, the app's current frame a.k.a. navigation history, etc). That is often a substantial part of the delay we witness when we see the "resuming" message. That delay often includes not just the time it takes to launch the next app, but also the time it takes to tombstone a previously used one.By better policy, I mean it would be nice if it could use the 2 GB for apps, but dump them out of memory as soon as you took a picture (so taking a picture would be equivalent in terms of memory to opening a really big app). That way it would sometimes keep more things in memory when you weren't using the camera. It would never be worse, since the cached memory things the camera would kick out of memory would be things that wouldn't have been there anyway in the 1 GB implementation.