Recommended Posts

Last week, Nokia's outgoing chairman spilled the beans on the company's plans for a range of tablets and 'hybrid' devices. Although Nokia later attempted to distance itself from his comments, let's face it: the arrival of a Nokia tablet is a certainty - a question of when, not if.

Given Nokia's increasingly close and interdependent relationship with Microsoft - not just through Windows Phone, but also with services and software development - it seems equally inevitable that the OS of choice for Nokia's tablets will be Windows. But that's about all we really know about the company's plans for its new slates, and that got us thinking: what could the first Nokia tablet look like?

Something believable

While the web is littered with make-believe devices with wishlist specs that only a fanboy could dream of, we wanted to try to conceive of something a little more grounded in reality. It's just not terribly likely that Nokia's first Windows tablet will have sixteen cores, a 3D 4K-resolution display, telepathic controls and a built-in holodeck - maybe next time around, but for a first-gen device, we're pretty confident that those specs are a bit far-reaching.

In all likelihood, Nokia's first Windows tablet isn't going to have the kind of OTT specs that would make a techie drool, but much like the Lumia range of Windows Phones, we imagine it'll be stunning to look at, with very capable hardware that does everything you could need incredibly well.

So with those caveats established, where did our imagination take us? Well, we've dreamt up a 10.1" Windows RT tablet, called the Nokia Tiviti 9210. Take a look at the pics, scan through the spec sheet below them, and then answer the poll question: would you buy this Nokia tablet?

post-389204-0-05166000-1336732682_thumb.

NOKIA

Tiviti 9210 with Windows RT

Processor: Dual-core 1.5GHz Qualcomm MSM8960 Pro Snapdragon S4

Dimensions: 260.2 x 177.5 x 8.8 mm

Weight: 575g

Display:

10.1" capacitive multitouch display

Super IPS+ LCD | ClearBlack | 1920x1200px Full HD

Corning Gorilla Glass 2

Storage and memory:

32GB/64GB integrated local storage + SkyDrive cloud storage

1GB SDRAM

Power management:

Integrated 7700mAh battery for up to 12 hours of usage

Connectivity:

Wi-Fi (802.11a/b/g/n)

Bluetooth 4.0

4G LTE | UMTS/HSPA/HSPA+/DC-HSDPA | CDMA EV-DO Rev.A | GSM/EDGE

DLNA/PlayTo

Micro USB

3.5mm AHJ connector

Imaging with Carl Zeiss Optics:

Front camera: 2MP for video calling

Rear camera: 8MP

- Rear F number / aperture: 2.2

- Camera focal length: 28mm

- Video recording with rear camera, Full HD (1080p) up to 30fps with stereo audio capture

Sensors:

Accelerometer | Ambient light sensor | Assisted GPS + GLONASS | Compass | Gyroscope | Proximity sensor

Hardware keys:

Power | Volume | Camera | Rotation lock | Windows button

Pricing off-contract:

32GB WiFi + 4G: $499 USD | ?449 GBP | ?529 EUR | $659 AUD

64GB WiFi + 4G: $629 USD | ?549 GBP | ?649 EUR | $759 AUD

- - - - -

You can vote in the Neowin poll by going to the article page - but we also want to hear your thoughts about how you might improve the Tiviti 9210 hardware and design, and what you think Nokia needs to make its first real tablet a success.

With that, it's over to you.

The left and right edges need a little more work, more tapered. And it looks a little TOO thick. LOL @ resolution, that'd be expensive... I'd rather it be $500. Lose the back camera, keep the front camera for Skype. Don't 'really' need it to be connected to anything other than WiFi if using a phone for tethering, which you likely would.

I'd buy one, 32GB for $500, the 12hr battery life and higher res seals the deal for me. It might be nice to have more GPU power for a tablet though so I'd first be checking out what nVidia does on that end.

If you can replace the OS, then yes - I quickly used W8 on an Intel proto tablet at my old work when I visited them 2 days ago and I wanted to use it as a frisbee after a few minutes.

And before you start moaning, I don't own nor am I interested in an iPad either.

At this stage I'm just not sure if I want a tablet based on ARM or x86. I know what to expect from the former so at this stage I'm really just waiting to see what OEMs will do with the latter before I decide. I like the idea of a dockable tablet that can be used as a full PC but it needs to be able to compete with ARM in terms of battery life and speed waking from sleep.

Having said that, if Nokia produced something that looked similar to the renders above I would seriously consider it. IMO, the Lumia 800/900 are the best looking phones on the market at the moment and a tablet with similar styling would be quite desirable.

  • 2 weeks later...
This topic is now closed to further replies.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!