4 ms·
Going Xolo: Intel’s first x86 Medfield smartphone reviewed
- andrewcooke 14y agowith a name like that, i can see why it's not being marketed in the usa ('x' is often used to represent 'ch' in latin-american spanish [it's something that's been pulled in from indigenous languages, afaik], and 'cholo' is an ethnic/class smear term http://www.urbandictionary.com/define.php?term=xolo http://www.urbandictionary.com/define.php?term=xolo) (maybe this seems like an odd thing to post, but it jumped straight out at me - a kind of "omg they can't be calling it that?" moment. i don't for a minute think that's been through hispanic focus groups.)
- twelvechairs 14y agoYeah. You'd think marketing types would be onto urban dictionary by now... Apparently not.
- jsvaughan 14y agoWhat you really want to be reading is what Anand has got to say: http://www.anandtech.com/show/5770/lava-xolo-x900-review-the-first-intel-medfield-phone http://www.anandtech.com/show/5770/lava-xolo-x900-review-the... Much more detail in terms of performance benchmarks: http://www.anandtech.com/show/5770/lava-xolo-x900-review-the-first-intel-medfield-phone/4 http://www.anandtech.com/show/5770/lava-xolo-x900-review-the... Much better analysis of the battery life (particularly the normalized battery life graphs) http://www.anandtech.com/show/5770/lava-xolo-x900-review-the-first-intel-medfield-phone/6 http://www.anandtech.com/show/5770/lava-xolo-x900-review-the...
- sciwizam 14y agoIf only they had implemented at least a contemporary GPU, SGX540 is more than 2 years old. Will be interesting to see Motorola's design.
- dbcooper 14y agoIs there any info on if or when atom cores for mobile will switch to out-of-order execution? That + a 22nm process would make things rather interesting ...
- rbanffy 14y agoI've been using an Atom-based netbook for some time and I don't have that many complaints about its performance. The reason I opted for a larger i3-based machine for its replacement was the 2GB memory limit. I like the size-price combination of netbooks. Too bad they are being phased out in favor of much higher-margin "ultrabooks". Had an Atom-based netbook offered 4 GB of RAM, I'd have jumped for it immediately.
- macavity23 14y agoSo how does the x86/ARM difference work with regard to apps? I know most Android apps are written in not-Java-no-really so presumably they're just compiled at runtime, but isn't it possible to write Android apps using native code? How does the Android developer toolchain handle the different architectures?
- njs12345 14y agoApart from games, there's no problem really. As for native code, you can compile a fat binary similiarly to as described here (if you're using the NDK): http://stackoverflow.com/questions/5089783/producing-optimised-ndk-code-for-multiple-architectures http://stackoverflow.com/questions/5089783/producing-optimis...
- freehunter 14y agoAnandTech's article mentioned that there was no problem running a wide variety of games, including GTA III. I don't know if GTA is the most intensive game that's been released, but I know it was (at least initially) only released for a handful of phones. Xolo could run it.
- ConstantineXVI 14y agoIt sounds like if you (the developer) don't rebuild the native bits for x86, Intel rams your binary through some sort of ARM->x86 translator when you upload your app to Play. Appears the translator works fairly well, given that GTA3 was mentioned to work without issue (as the app hasn't been updated since January, I'm operating with the assumption that it wasn't built with x86 binaries)