Reports that HTC is working on the next Nexus tablet for Google have been making the rounds for a few weeks. Now it looks like that tablet might have just received certification from the South Korean equivalent of the FCC and @UpLeaks claims to have some new details about the tablet.

nexus logo

Neither Google nor HTC have confirmed that the tablet exists, but if you believe the rumors, here’s what we can expect from the tablet which may be called the HTC T1 and which seems to have the code-names Flounder and/or Volantis:

  • NVIDIA Tegra K1 64-bit processor
  • 4GB RAM
  • Optional 4G LTE (with CDMA2000 support for Verizon and/or Sprint networks)
  • 8MP rear camera with flash
  • 1.6MP front-facing camera
  • WiFi, GPS, NFC
  • Google Android L software

Earlier leaks have indicated that the tablet would have an 8.9 inch, 2048 x 1440 pixel display which would make it one of the first Nexus devices with a non-widescreen display. If the screen size is correct, it’s likely that Google would call the tablet the Nexus 9 if and when it launches.

via G for Games and /r/Android

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

or...

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.

24 replies on “HTC Nexus tablet leaks/rumors: Tegra K1, 4GB RAM, Android L”

  1. I’d be quite interested, despite the screen resolution, IF it has the stylus and the art program from the Shield. Supposedly it can detect a rotation of the stylus so while you would lose precision compared to a Wacom option, you would make it up in a different sort of precision/versatility.

  2. looks like an excellent set of specs.

    the only thing i will hope for is that the standard nexus spec makes it easy to port Ubuntu on their at a later date.

  3. I think 4:3 is better suited for large tablets…although a 2 inch jump in size means a $200 jump in price.

    I’d probably just pay $300 for a Shield to get K1 rather than paying $500 for a Nexus 9.

    1. The Nexus 10 was only $400, so I doubt they’d charge $500.
      I guess it’s possible though.

  4. I really like the 4:3 aspect for a tablet. It’s much more usable for web browsing, reading comic books/mags or any ebook. It’s okay for watching videos else if black bars are present, but it’s a minor annoyance. I am waiting for the RRP. And the benchmark tests!!! (same CPU as in the Acer Chromebook CB5-311, which I want!!!)

    1. Same *GPU* as the CB5-311 , the CPU is what makes the 64Bit Tegra K1 different, instead of utilising 4 Cortex A15 r3 CPUs (and a 5th low poer A15) the 64Bit TK1 uses 2 Nvidia designed “Denver” CPUs along with the Full Kepler SMX thats in the 32bit Quad-core Tegra K1

  5. I hope the 4:3 aspect is wrong. With these specs you could almost throw Linux Mint or Ubuntu on it get a keyboard and case and use it for everything except making calls. I think you can even build operating systems with this right?

    1. Probably, since Nvidia SOCs are supported by the mainline ARM Linux kernel and Nvidia supplies proper (though binary) xorg drivers for all of its SOCs.

      As of compiling/building OSes with this: You don’t need a powerful SOC like this. Even sloweer ARM SOCs can be used for building Linux kernels/app packages, you only need to wait a bit longer to complete.

  6. That’s dead sexy!
    …waitaminute…NEXUS?
    Sooo all THAT but no card slot?
    Maaaaaan…

    1. Strange thing is that Android 4.4 is the beginning of the path to making SD cards both secure and easy, iirc 5.0 is going to help that along, though I can’t remember the specifics of what they’re doing.

      1. In 4.4, Google implemented a new security policy which prevents non-certified applications (which is pretty much everything that is not made by Google AFAIK) from writing to any other directories on an SD card other than the single directory they create or claim ownership of. This does help handcuff malware apps, but it also impacts useful apps like file explorers. I had a 128 GB SD card in my M8, but didn’t find it very useful with the limitations imposed, so moved that to another device and just put in a 64.

        If you root your phone, you can remove this limitation and go back to the way it used to work (i.e. free and unfettered access to the SD card)

  7. Anyone know if the reviews are in for the K1? Is it as great as they thought it would be ?

    1. yes they’re in, since we have the jetson board, xaiomi mipad, shield tablet as K1 devices. CPU power comparable to an Intel J1900, GPU power somewhere between intel HD 4000 and 4400. So, basically, big windows tablets using proper haswell chips beat it, but otherwise it’s king of the android hill.

      1. This will be the first use of the 64-bit Denver cores. So CPU performance should be interesting. Early Antutu benchmarks show the A15 cores beating the Denver cores by ~4%. But that difference may be eliminated (or better) after the CPU and software are optimized. Also the Denver cores mean it should have monster single-thread performance – certainly beating the A7 (the A15 cores are already close on the Shield tablet), and possibly even the A8.

        1. Oh wow, if true (and with 4GB of RAM it’s not too unreasonable, though current designs could work with it) that would be fantastic, for all the good of the octocore cortex A7 designs, they still don’t compare to A15 and A57 with fewer cores. Any source on that rumour btw?

          1. All leaks that I have seen for this tablet have named the 64 bit K1 variant as the SoC of choice. Per Wikipedia, it will be dual core and “be able to execute 64-bit ARMv8 code. Each CPU will be 7-way superscalar with 128 KiB + 64 KiB of L1 cache and running at up to 2.5 GHz.” (See https://en.m.wikipedia.org/wiki/Project_Denver). The A15 cores are 3-way superscalar IIRC. So along with the 2KHz clock bump and increased cache, this could result in much better IPC. Since the A15 cores already nearly match the A7 Cyclone cores, I am speculating that Denver cores should out perform them by a fair amount.

            That’s about the extent of my knowledge. Since Google used the K1 almost exclusively at the last Google I/O conference, it seems they know a little bit more 😉

          2. I don’t believe there is. However, Fudzilla had an article where NV pointed out that they intended to put perform stock ARM core designs like the A53/57. No big surprise there. Apparently the NV CPU team is quite talented and experienced (check out https://en.m.wikipedia.org/wiki/Project_Denver), and it looks like Google prefers the Denver cores, so that adds some weight to that pronouncement. If rumors are true, we should all know within the next month 🙂

  8. 1.6MP front facing camera? Aw, I don’t like the noise from these low res cameras in low light, though if it’s a giant sensor that’d sort things out. Otherwise decent specs, bit confused by the display. Already bought a shield tablet so this isn’t for me.

  9. “Without a non wide-screen display”… it seems you have double-negated yourself into accidental irony.

    1. Yeah, I started to type “without a wide-screen…” then thought better of it… but didn’t think about what I’d already typed, clearly.

Comments are closed.