* Lumia Camera here is v184.108.40.206 and the major version number is notable since it was Lumia Camera v5 that did away with the whole 'reframe later' workflow and also introduced new, more severe sharpening algorithms.
Lumia Camera is now available in the Microsoft Store for any Lumia 1020s running Windows 10 Mobile Creators Update - just search for it and it's there and installs perfectly. Amazing. It's the exact same version as on Windows Phone 8.1 and is a WinRT/Store 'universal' app, not a modern Windows 10 UWP, but it now works with Photos, thanks to recent updates to the latter and to the underlying OS. Plus the aforementioned approvals that mean that Lumia Camera is now directly accessible in the Store again, of course.
In 'DSLR' mode with the Grip on...
Why would anyone want Lumia Camera v4 on a 1020 in 2017? Because under W10M Creators Update, you're limited by default to capturing at the full 34/38MP, which is stupidly high - and there's no oversampling. Third party apps can get you around most of this, but the presence of the real McCoy is arguably even better.
Now, before you go rejoicing and putting your main SIM card back in the Lumia 1020 just because all of this is now possible again, there are a number of caveats:
- Lumia Camera takes around ten seconds to launch under Windows 10 Mobile CU. Not a problem if you're doing something arty, but it might get in the way at a fast moving human-interest event!
- Switching through to Photos takes another 10 seconds or so. It's a big app and a big module to spawn up when needed on such a relatively lowly processor.
- Working your way back from Photos to Lumia Camera often dumps you back at the Start screen because the camera app has long since gone to sleep.
- Video capture's largely broken, taking 10 seconds to start recording after pressing the capture icon, so useless for all except preplanned sequences. Plus the audio track is still mono under Windows 10 Mobile. Ah well.
Still, a worthwhile footnote to the Lumia 1020 story, now more functional again - if sometimes very slow - under the very latest Windows 10 code goodies.
Postscript: Why did Nokia - and then Microsoft - abandon this reframing workflow, if it was so wonderful? Because:
- they had ideas for multi-exposure image combination, made possible by the far faster GPUs in the later phones, and there was no practical way to do BOTH systems at the same time.
- the reframing aspect became less important away from the 41MP-sensored Lumia 1020.
- 99% of users simply didn't grasp the reframing concept - what's the point of being innovative if only AAWP readers and hard core 1020 enthusiasts are aware that a feature's there in the first place?
See also my articles here: