My Ideal Lumia 1030 would be...


Recommended Posts

If Microsoft makes a Lumia 1030 it would be nice to see:

 

1. The Camera do a come back with minor updates (not needed in my opinion).

2. Micro SD slot for up to 128GB support.

3. Water proofing the Phone Maybe.

4. Higher Native Resolution (1080+).

5. Better front facing Camera (5MP)

6. The last and most Important thing, Make it Available in all Carriers. (no exclusive to one Carrier.)

Link to comment
https://www.neowin.net/forum/topic/1229713-my-ideal-lumia-1030-would-be/
Share on other sites

I just did a quick google search and apparently it's on the drawing board.

 

I hope it will have the same design as I find rounded edges, not just on iPhones but on all phones, to be hideously ugly. I don't care if the camera will still protrude out but I would love to have 4k video recording capability (and especially being able to snap a picture of that 4k recording). So it will have to be able to have at least 128 gb microsd support; and yepp water proofing would be fantastic.

 

Other requests of mine have to do with the operating system, so in a nutshell I should keep quiet about that ...buuuttt, I would love to be able to control the color of the tiles and being able to have a gapless playback on the default music app (as I understand it, it doesn't have gapless playback!) and being able to play the songs of boxsets in correct order!

 

 

 

My wishlist for Windows phone:
Faster camera

 

Supposedly that's coming with the Nokia Lumia Denim upgrade (granted, though only on Lumia devices; and no idea about the shutter lag - didn't even know Windows phones suffered from that). But I've been reading a little about the Lumia 930 and I would really love it if that device would have natural colors when taking photos; preferably as close to what the eye sees. That's one of the biggest downsizes with the Lumia and thus still keeping me pretty much away from buying it

I too am waiting for an updated version of the Lumia 1020.

 

Windows Phone 8.1 Update 2 just got confirmed for Oct and is rumored to add support for 2k screens and Snapdragon 805 SoC. The 805 would make a lot of sense for a 1030 as it officially supports camera sensors up to 55MP (vs 800/801 only support up to 21MP, likely why the 930/Icon/1520 all have a 20MP sensor...). They made the 41MP sensor from the 1020 work with the older Snapdragon S4 Plus SoC but as most people know there's some delay there. The 805 paired with a 41MP sensor or similar should run smoothly. Hopefully a bit after the 8.1 Update 2 release we see something from the Lumia line.

 

What I'd like to see:

4.5"~5.2" screen (I'd like 1080p but hearing some rumors of 2560x1440)

Glance screen (missing on the 930)

Snapdragon 805 SoC

41MP or similar rear camera

5MP front facing camera (from the 730/735)

2GB of RAM

Qi Wireless charging

Multiple internal storage sizes (32/64GB), or MicroSD support.

The camera will be faster on any future Lumia 1030 simply because they'll be using the faster and newer quadcore Snapdragon 8xx SoC.  The thing to remember with the 1020 is that it uses the older Snapdragon S4, 1.5Ghz Dual Core.   That SoC also didn't support the higher megapixels the PureView camera uses so, and this is why there's such a big bump, Nokia had to add in a second processor to support it.  This all adds to the camera lag you get but with that the new Snapdragon 805 you have a Quad core CPU up to 2.7Ghz and it supports cameras up to 55 megapixels on it's own, so they wouldn't have to put in a second image processor like with the 1020.

 

All of that will help with making the camera faster on the hardware side, and then all the software and firmware improvements you see with the 830 etc will add to it.  

 

The only devices that use the Snapdragon 805 are from Samsung, the s5 and the new Note 4 etc, I think MS should do something better and go with the 808, why not go for the first Lumia 8 core phone off the bat and make a splash?  Just think, 8 core, 3GB ram, 1440p screen, 41mpix or maybe more, camera?   Between 5" and 5.5" tops as well, and you'd have a monster of a Lumia on your hands, I'd rush out to buy it personally and I hardly take pictures.

I too am waiting for an updated version of the Lumia 1020.

 

Windows Phone 8.1 Update 2 just got confirmed for Oct and is rumored to add support for 2k screens and Snapdragon 805 SoC. The 805 would make a lot of sense for a 1030 as it officially supports camera sensors up to 55MP (vs 800/801 only support up to 21MP, likely why the 930/Icon/1520 all have a 20MP sensor...). They made the 41MP sensor from the 1020 work with the older Snapdragon S4 Plus SoC but as most people know there's some delay there. The 805 paired with a 41MP sensor or similar should run smoothly. Hopefully a bit after the 8.1 Update 2 release we see something from the Lumia line.

 

What I'd like to see:

4.5"~5.2" screen (I'd like 1080p but hearing some rumors of 2560x1440)

Glance screen (missing on the 930)

Snapdragon 805 SoC

41MP or similar rear camera

5MP front facing camera (from the 730/735)

2GB of RAM

Qi Wireless charging

Multiple internal storage sizes (32/64GB), or MicroSD support.

I dunno man,  4k on a cellphone, the LG3 has pretty bad reviews as it seems technology wise, we aren't quite there for use in mobile devices at least.

I dunno man,  4k on a cellphone, the LG3 has pretty bad reviews as it seems technology wise, we aren't quite there for use in mobile devices at least.

 

There's middle grounds you can go with, doesn't have to be either 1080p or 1440p, why not, say, 1200p or whatever the next res after 1080p fits the same aspect ratio?   This is what Apple does, as long as you're using the same ratio then it doesn't mess with apps.

  • Like 1

I dunno man,  4k on a cellphone, the LG3 has pretty bad reviews as it seems technology wise, we aren't quite there for use in mobile devices at least.

 

That's why I said I hope 1080p. Still very high pixel density but still get some smoothness and save a bit on battery life.

 

But also the G3 has a SD801 SoC, the 805 has a fair bit more powerful GPU, but I'd still like to see 1080p, It's a nice balance.

  • Like 1

Why cant they use Core-m for a phone? Sure its terrible for a PC, but its at least 3x faster than the S805.

It could be gamechanging if they could do it and do it right

 

Because of size maybe? and I don't think the Core-M has all the needed built in 3G/4G/LTE radio stuff and other things the Snapdragon SoCs have.  So MS would have to take those, then use other parts to fill in the gaps, maybe.

That's why I said I hope 1080p. Still very high pixel density but still get some smoothness and save a bit on battery life.

 

But also the G3 has a SD801 SoC, the 805 has a fair bit more powerful GPU, but I'd still like to see 1080p, It's a nice balance.

 

It depends on where they want to win on the specs, the 1030 should win hands down on the pureview camera but going with the better 805 or heck, going for broke with the 808 would also be a boost, then you can leave the screen res at 1080p because you're countering other phones in other key areas.

Because of size maybe? and I don't think the Core-M has all the needed built in 3G/4G/LTE radio stuff and other things the Snapdragon SoCs have.  So MS would have to take those, then use other parts to fill in the gaps, maybe.

Ok. Imagine the possibilities Core-M could bring to a windows phone if it was possible. I think it is a SoC, but idk.

The camera will be faster on any future Lumia 1030 simply because they'll be using the faster and newer quadcore Snapdragon 8xx SoC.  The thing to remember with the 1020 is that it uses the older Snapdragon S4, 1.5Ghz Dual Core.   That SoC also didn't support the higher megapixels the PureView camera uses so, and this is why there's such a big bump, Nokia had to add in a second processor to support it.  This all adds to the camera lag you get but with that the new Snapdragon 805 you have a Quad core CPU up to 2.7Ghz and it supports cameras up to 55 megapixels on it's own, so they wouldn't have to put in a second image processor like with the 1020.

 

All of that will help with making the camera faster on the hardware side, and then all the software and firmware improvements you see with the 830 etc will add to it.  

 

The only devices that use the Snapdragon 805 are from Samsung, the s5 and the new Note 4 etc, I think MS should do something better and go with the 808, why not go for the first Lumia 8 core phone off the bat and make a splash?  Just think, 8 core, 3GB ram, 1440p screen, 41mpix or maybe more, camera?   Between 5" and 5.5" tops as well, and you'd have a monster of a Lumia on your hands, I'd rush out to buy it personally and I hardly take pictures.

The 1020 doesn't use a secondary image processor, the Nokia 808 (their first device with a 41MP sensor) did but the reworked the image stack on the Snapdragon S4 Plus to work with the 41MP sensor. The hump on the 1020 is purely from the size of the sensor.

 

Nokia collaborated with Qualcomm to do a complete rewrite of the chipset's imaging stack in order to make everything work properly

 

Also the Snapdragon 808 isn't 8 cores, its 6 in a 2+4 (big.LITTLE configuration). Either the 2 Cortex-A57 cores are in use for high power applications, or the 4 Cortex-A53 cores are use during low power scenarios. See: http://en.wikipedia.org/wiki/Qualcomm_Snapdragon

 

Regardless the SD805/808/810 should be used for the next irritation of the 1020 as they all officially support sensors up to 55MP.

yea that is in the works in the next updated called denim.  Check out the IFA Event in 3 Parts here : 

I said for Windows Phone not just Lumias

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Exactly. They won't go 100 because current gen consoles are simply too old for any groundbreaking graphics or gaming experience otherwise. They will go with standard (console) price 70 or go with 80 if they really want to go premium. Of course they will have more expensive options too with some useless cosmetics as always.
    • Doesn’t surprise me at all. God is light & He gave us life so it sounds almost logical that we would therefore emit a certain amount of light.
    • This is what I want. Hey Gemini, how do I remove you from all my google products permanently?
    • I would never install install this build before rtm process. only 3 months to go. never install on your daily devices. just wait 3 months.
    • Motrix Next 3.9.6 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.6 changelog: New Features Clipboard management — App-owned copy actions no longer trigger the Add Task auto-detect popup. aria2 input compatibility — Multi-line aria2-style task input is supported for URLs with per-task options such as out=. BitTorrent IPv6 DHT — Added IPv6 DHT support and related configuration. File category URL patterns — File category rules can match URL patterns with validation and localized hints. Task status tags — Added clearer waiting and sharing states for task cards. Download event bridge — Added an aria2 WebSocket event bridge for faster download notifications. Improvements Improved task list transitions and preserved task state during tab switches. Kept RPC origin access enabled for local integrations. Restored AppImage stripping in release builds after beta validation. Added localized preference guidance across supported languages. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      75
  • Tell a friend

    Love Neowin? Tell a friend!