The Asus MeMO Pad FHD 10 is a WiFi-only Android tablet with a 10 inch, 1920 x 1200 pixel display and an Intel Atom Z2560 Clover Trail+ processor. So you’d be forgiven for thinking Asus would keep the basic specs the same when releasing a new model with 4G LTE wireless capabilities.

But it turns out Asus had other ideas in mind. The new Asus MeMO Pad FHD 10 LTE looks a lot like the WiFi-only model, but it swaps out the Intel Atom chip for a Qualcomm Snapdragon ARM-based processor.

asus memo pad fhd 10 lte

The new model does have the same 10 inch full HD IPS display as the WiFi-only model, and Asus promises similar battery life of up to 10 hours of run time.

Asus and Qualcomm haven’t said exactly which Snapdragon chip will be in the new model, but the Snapdragon 600 or 800 quad-core processors seem like good bets.

The MeMO Pad FHD 10 LTE measures 9.9mm thick and weighs about 572 grams. That’s about 0.39 inches and 1.3 pounds.

It has stereo speakers, supports Miracast wireless display, features a microSD card slot, and has a 5MP rear camera with auto-focus.

via Engadget

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign


Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

5 replies on “Asus MeMO Pad FHD 10 LTE to pack a Qualcomm Snapdragon chip”

  1. I’m a little confused… It’s an Android tablet, but the name includes the MeMO name? Oh, MeMO, not Meego! Ok, then!
    But on a more serious note, this looks like a pretty nice tablet.

    1. While traditionally, ATOMs have long supported Linux but the Clover Trail+ Z2560 ATOM running on this model is optimized and supported only to run Android, while the Clover Trail Z2760 used in W8 tablets is only supported for W8…

      It’s still technically possible to get Linux running on the Clover Trail but definitely not a easy process as the UEFI on these tablets don’t support legacy BIOS mode and only the 64bit Linux Boot Loader works with UEFI but these 32nm ATOMs are all 32bit and there’s no open source driver support for the Imagination PowerVR GPU based GMA these use…

      So wait for the next gen Bay Trail models to come out, as of April they’re already included in Intel’s Open Source driver support and they’ll be 64bit support as well. So should be relatively easy getting any Linux distro to run on them…

      1. @CyberGusa, nice reply. We see now how UEFI is restricting our choice. That plus non-released graphics driver information is making the purchase of a device almost impossible these days.

        1. UEFI and closed driver support definitely have the effect of limiting choices…

          Though, to be clear… UEFI is different enough from traditional BIOS to require adapting to…

          A OS can’t function properly if it can’t communicate properly with the hardware…

          The Secure Boot feature just adds another layer of security that just makes it that much harder to run older software…

          Linux Boot Loader now supports Secure Boot but system needs to be 64 bits to allow the Boot Loader to both recognize and work with UEFI and to use the 64bit key for Secure Boot.

          Present 32nm Atoms were a bit rushed to market. So Intel would have something to start competing in the mobile market.

          The upcoming Bay Trail, though, is based on the new Silvermont architecture that benefits from work done for Ivy Bridge.

          It’s still doubtful there will be legacy BIOS support but 64bit and better drivers should still make it a lot easier to just run whatever you may want to.

          The only device that you really have to watch out for is the MS Surface RT because it uses a Private security key instead of a public key for Secure Boot and Secure Boot can’t be disabled for ARM devices running Windows RT.

          Also, until the second half of next year (maybe longer) ARM will remain 32bit. While the fragmented ARM hardware market and large number of closed drivers means most ARM devices aren’t ideal for running Linux distros in general… Though, they are trying to improve that and there are some exceptions but basically do a lot of research before choosing one of these mobile devices for running Ubuntu, etc…

Comments are closed.