Samsung announces the Ativ Q, a Windows and Android convertible laptop with an insane screen resolution


If you were to talk about an insane amount of specs all crammed into one device, the Ativ Q would definitely be part of that list. Today Samsung announced their Ativ Q device and it sure packs a wallop. The Ativ Q is essentially a dual-booting device that can run both Windows and Android and sports a 13.3″ screen with a resolution of, wait for it, 3200 x 1800! To make things even better, it also has what I deem as some sort of convertible mode that changes it to a tablet mode, laptop mode, and an odd mode where it’s floating on top of the keyboard.


As for internal specs, this will don Intel’s Core i5 Haswell processor, and according to Samsung will produce around 9 hours of battery life. The tablet/laptop will also come with Samsung’s popular S-Pen, so you can expect it to have plenty of features that will utilize it.

This is certainly a device to watch for. The dual-booting feature and the different ways you can use this device will be a huge selling point for Samsung, so I’m definitely anxious to see more of this device as the months pass. Stay tuned!


  • Bonedatt

    Way to go Samsung!

  • phor11

    Since it’s using an x86 processor I’m guessing they’re just running Android inside a VM on top of Windows?

    • Krzysztof Kajdasz

      Android compiles and works natively on x86 CPU-s, no need for a VM.
      The only issue can be games, because many publishers distribute them compiled only for the ARM architecture.
      Apps written in Java that don’t have native code will work OOTB.

      • phor11

        Intel has been working on an x86 optimized version of Android for quite some time now but as far as I know it’s still in Pre-Alpha (or at least it was in mid March).

        The Android x86 project just released an r1 version of their ICS code, but only for a few devices and their Jellybean code is still in test.

        So while you CAN compile it to work on x86, it doesn’t work very well just yet. The projects trying to rectify that are still in their infancy.

        And as you mention, if you compile directly for x86 instead of running inside a VM or emulator, anything that utilizes the NDK won’t work (will have to be re-written). I wish I could find a statistic to show how many apps use the NDK. Would be interesting to know if a native x86 version is even worth pursuing when we already have pretty well optimized emulation.