Display

I mentioned earlier that it’s interesting that Qualcomm, Intel, and others have identified and gone with WSVGA (1024x600) for their reference designs at around 4“. In the case of the FFRD/X900, it’s 4.03” WSVGA TFT-LCD. That works out to 295 PPI and looks extremely attractive in person. I find it quite hard to pick out individual pixels; this is definitely a high PPI display that’s right up there with the best. In addition, the capacitive digitizer is excellent; I have no complaints about tracking accuracy at all, again just like you’d expect from a shipping device.

Brightness (White)

Brightness (Black)

Contrast Ratio

The X900 also goes pretty bright, at 375 nits, and has good contrast at around 800. I’m impressed with the display again just because up until recently seeing good LCDs outside of anything but the iPhone 4/4S has been a rarity. The HTC One X and Rezound are probably the only other devices in recent memory that surpass, but suffice it to say Intel/Lava haven’t skimped here.

As you can see from the gallery above, the display's performance is pretty good. CIE shows primaries and secondaries are close to where they should be, but not perfect (but way better than AMOLED insanity). Unfortunately color temperature is around 7500K constantly, and gamma is a bit sporadic. It’s worth dealing with those inconsistencies for that high PPI though.

Outdoor viewing angles are also pretty good, basically what we're used to for LCD displays outside in direct sunlight.

Camera - Stills and Video Cellular, WiFi, Speakerphone, GPS
Comments Locked

106 Comments

View All Comments

  • vol7ron - Wednesday, April 25, 2012 - link

    I doubt windows would expect PCI channels lol. Though, it might need drivers to operate.

    Everything you need is on the phone for windows to operate (Screen, CPU, Video, RAM and Disk space) exists, even though Windows doesn't require it all. Though, Windows does need some way to communicate with those devices (device drivers), which Win7/etc probably doesn't have.
  • Shadowmaster625 - Wednesday, April 25, 2012 - link

    A few years from now it is likely I might be able to acquire one of these for dirt cheap. (Broken screen, etc) I would use it just for an ultra low power ultra low profile *single-function* pc. I would very much like to know if this hardware can run windows 7. It doesnt need to run well, it just needs to be able to go on the web and do basic things similar to an atom nettop.
  • superPC - Wednesday, April 25, 2012 - link

    it won't run windows 7. unlike windows 8, windows 7 requires standard RAM not LPDDR. windows 7 also requires some form of PCI.
  • Musafir_86 - Wednesday, April 25, 2012 - link

    -Excuse me, but IMHO, the type of physical RAM shouldn't matter. If not, we couldn't be able to load these OSes on VMs at all. :)

    Regards.
  • B3an - Thursday, April 26, 2012 - link

    Why would you even want to run Win 7 on this when Win 8 would clearly be WAY better suited, not to mention it also uses less resources and RAM while remaining faster/snappier than 7.
  • rahvin - Friday, April 27, 2012 - link

    I'd imagine he wants to know because Windows 8 is going to be only slightly less successful than Vista. Personally I'd guess around 5% of the Vista sales. It's a disaster in waiting unless they make dramatic last minute changes. You should try using it.
  • joshv - Wednesday, April 25, 2012 - link

    I am not sure why this chipset matters. Intel usually wins on x86 compatibility with older software. In the phone space there is no existing x86 code, and in fact they are stuck emulating another ABI - so they will be slower and less efficient that competitors that implement that ABI natively.

    That leaves Intel to compete on price/performance alone in a market where their competitors have 99.9% of the market. An odd position for Intel.

    Perhaps this makes more sense in a Windows 8 tablet?
  • Impulses - Wednesday, April 25, 2012 - link

    Its netbooks all over again, on a much bigger scale. ARM is moving upscale, if Intel doesn't start competing directly they will eventually start ceding some existing market share (when tablets/laptops start to overlap more, and the writing's on the wall with Windows for ARM).

    Only difference is they're up against a capable rival(s) as opposed to a limping AMD, so they can't just come out of the gate strong and them dog it and let the lower end market stagnate in order to maintain profits.

    This is a small first step but it'll allow them to ink more deals and possibly cement a strong foundation for upcoming Win8 ARM tablets which is probably their bigger long term concern.
  • dcollins - Wednesday, April 25, 2012 - link

    Did you even read the article?

    The x86 vs ARM issue is mostly a non-issue that will be completely resolved within a few months. Dalvik apps are JIT compiled to ARM and x86 and will perform similarly. In fact Intel might have an advantage here because they have the best compiler engineers in the world with decades of experience in generating high performance x86 code. NDK apps will generally be supported natively; developers only have to check a box to include x86 binaries. Even Apps that aren't compiled with x86 support are translated prior to installation on the users device. Nothing about the instruction set makes Medfield slower than ARM.

    Performance today is comparable to modern ARM processors even when running an out of date, slower OS. Performance in 4.0.x should match or outperform even Krait. Graphics performance is middle of the road, but that's a major concern for many smartphone buyers (myself included). Even in benchmarks that purposefully stress mutliple cores, Medfield holds its own against the many cored competitors. Real world usage is more lightly threaded.

    Browser performance is the most important metric for my usage and here Intel performs extremely well. If Medfield is available in a 4.x phone when it comes time for me to upgrade, I will seriously consider it versus a Krait based offering. Now imagine a next generation Atom build on 22nm with dual core, hyperthreading and possibly OoO execution: that chip will eat A15s for breakfast.
  • dcollins - Wednesday, April 25, 2012 - link

    edit: "Graphics performances... is NOT a major concern"

Log in

Don't have an account? Sign up now