Posts tagged android
Intel’s $126 YOLO phone matches quad-core Samsung Galaxy S III performance
Jan 26th
New benchmark results suggest Intel may have a bright future in smartphones after all– and the first phone to show that is, appropriately, named YOLO. (though sadly it’s spelled “Yolo,” not “#YOLO”)
Low-end Android handsets in developing markets sell in the $70-200 range (without carrier subsidies). They’re typically equipped with processors from Chinese manufacturers like MediaTek, Allwinner, or Rockchip — often with anemic ARM11 performance in tow. Buyers wanting a smooth Android experience have to step up to more expensive phones.
Into this void stepped Intel, which announced its new Atom Z2420 processor at CES a few weeks ago. Formerly codenamed “Lexington,” the mobile platform features a single-core 1.2 GHz CPU with HyperThreading (a lower-clocked version of the 1.6 GHz Z2460 Medfield / Penwell chip in the Xolo X900), PowerVR SGX540 graphics, Intel XMM 6265 HSPA+ 3G radio (a variant of the XMM 6260 adding dual-SIM support– important for developing markets), MicroSD support, FM radio, and even Intel’s Wireless Display (WiDi) technology, which can stream 1080p HD video to Wifi-connected TVs. The chip supports up to 1.3 MP front and 5 MP rear cameras and can record and play back 1080p video.

As with Intel’s first smartphone processor, the new Lexington platform was accompanied by a “shipping quality” reference smartphone (“FFRD,” or Form Factor Reference Design) to help manufacturers get off the ground with its chip. Safaricom of Kenya and Lava Mobile of India are bringing variants of this design to market, as is Acer.
Today we have the first benchmark results from the Safaricom phone, dubbed “Yolo,” and they’re quite surprising. The 3.5″ HVGA (320×480) phone includes 512MB RAM, 4GB storage, 5 MP rear camera (no flash), MicroSD slot, and Android 4.0.4, and sells for 10,999 KES ($126).
Juuchini put the Yolo up against Samsung’s flagship Android phone, the Galaxy S III GT-I9300, packing an Eynos 4412 processor (quad-core 1.4 GHz ARM Cortex A9 with Mali-400MP graphics) and 1GB of RAM. As the results show, Intel’s phone comes pretty close to matching the almost 5x more expensive S III:
|
Phone |
Specs |
Antutu Benchmark (higher = better) |
Vellamo (Metal) |
Vellamo (HTML 5) |
Vellamo (Extras) |
|
Samsung Galaxy S III (GT-i9300) |
Samsung Exynos 4412, quad-core ARM Cortex A9 @ 1.4 GHz, 1 GB RAM, 1280×720 resolution |
12986 |
403 |
1360 |
110 |
|
Intel Safaricom Yolo |
Intel Atom Z2420, single-core Atom @ 1.2 GHz with HyperThreading, 512 MB RAM, 480×320 resolution |
12961 |
423 |
1009 |
49 |
Note: some versions of the Galaxy S3 (e.g. most of the U.S. versions) have a dual-core Qualcomm Snapdragon S4 processor instead of the quad-core Exynos and will thus produce different benchmark results.
See here for a review of the Yolo. The phone will hit India shortly as the Lava Xolo X500, retailing for Rs. 8,999 ($167).
Intel doesn’t appear to be targeting the U.S. market with this, which is unfortunate, as we think a Yolo with a higher-resolution (e.g. 800×480) screen could do well as an entry-level smartphone (think free-on-contract). And maybe it’d sell even better if branded “#YOLO.”
Still, the Lexington platform’s performance in such a low-priced handset bodes well for Intel’s future in the smartphone industry.
Lava announces Intel Medfield-powered Xolo X900 Android smartphone for India
Feb 28th

Lava, a player in the Indian budget smartphone market, unveiled the Xolo X900, the first handset powered by Intel’s Medfield x86 chipset (formerly codenamed Penwell). The Xolo runs Android 2.3.7 Gingerbread on top of a 1.6 GHz single-core Intel Atom Z2460 (Medfield) chip. Screen size is 4″, with 1024×600 resolution, 8-megapixel rear camera with flash, VGA front-facing camera, NFC support, HDMI output, and a 1640 mAh battery.
The phone is based on Intel’s Medfield reference design, which UK carrier Orange is also using for its upcoming phone, codenamed Santa Clara.
Pricing is unknown as of yet, but Lava says the Xolo X900 should hit the market — only in India — in April.
Hands-on videos with the X900 after the break.
HTC announces One X: quad-core Tegra 3, 4.7″ HD SLCD, Android 4.0
Feb 27th
HTC just announced its new One X superphone at the Mobile World Congress 2012 in Barcelona. The Android-powered handset features HTC’s first quad-core processor, a quad-core Nvidia Tegra 3 running at 1.5 GHz. Other specs include a 4.7″ Super LCD screen with 1280×720 HD resolution, 32 GB storage, 1 GB RAM, an 8-megapixel camera with f/2.0 lens, Bluetooth 4.0, dual-band 802.11n Wifi, NFC, DLNA, HDMI via MHL (over the MicroUSB port), Beats Audio, and a 1800 mAh battery.
The One X’s camera seems to have been a focus area for HTC, which included HDR and the ability to take pictures while recording video (pretty cool). The phone is 9.27 mm thick, weighs in at 130 grams, and will ship with Android 4.0 running HTC’s Sense 4 interface on top.
In the US, AT&T gets its own version, the One XL, with an LTE radio built in. Since Tegra 3 doesn’t seem to play well with current LTE chipsets, the One XL swaps out Nvidia’s quad-core chip for a 1.5 GHz dual-core Snapdragon S4 from Qualcomm. With half the cores as Tegra 3, S4 may appear to be a step down in processing power, but reviews suggest Qualcomm’s Krait architecture may very well match or beat Tegra for mildly threaded apps (i.e. almost everything you can do on a phone except multitasking of several heavy apps).
One X is the hero phone of HTC’s new One line, which also includes the One S (a thin, dual-core phone slotting under the X) and the One V (the entry-level model).
The HTC One S features a svelte aluminum body, just 7.9 mm thick. It features the same dual-core 1.5 GHz Snapdragon S4 processor from Snapdragon, alongside the 8 MP camera, 1 GB RAM, Bluetooth 4, Wifi, DLNA, and HDMI. However, the screen drops to a 4.3″ QHD (960 x 540) Super AMOLED (with PenTile), internal storage is down to 16 GB, and the battery is 1650 mAh. In the US, the One S will be offered by T-Mobile.
The final member of the family, One V, resurrects the HTC Legend’s design from 2010 for an entry/mid-level Android offering. The phone features a 1 GHz single-core Qualcomm Snapdragon S2, 3.7″ WVGA screen, 4GB of internal storage, 512 MB RAM, 5 MP camera (with f/2.0 aperture, 720p video recording), 115 gram weight, and a 1500mAh battery.
Android on a Budget: Huawei Ideos X5 U8800 Unboxing / Hands-on Video
Nov 13th
Is a smooth Android experience possible on a limited budget? We decided to find out by checking out the Huawei Ideos X5 U8800. At under $300 unlocked, unsubsidized, it’s one of the cheapest phones with an ARMv7 processor (needed for any semblance of smoothness in Android). The phone features a 3.8″ WVGA LCD, 800 MHz Qualcomm Snapdragon processor, 512 MB RAM, 1500 mAh battery, and an MicroSD slot (4GB card included), and runs Android 2.2 (Froyo).
The results? Watch our full video unboxing and hands-on below the break to find out.
Oh and yes, a bit after 13 minutes, we found a nice bug - if you lock the phone while in the camera app, it’ll become stuck upon waking.
More >
Google to acquire Motorola Mobility for $12.5 billion- but is it really patents they’re after?
Aug 15th

Google just announced that it’s purchasing Motorola Mobility for $12.5 billion– the search giant’s biggest acquisition to date. Motorola Mobility is Motorola’s consumer division, which was spun off in January 2011 and primarily sells mobile phones and TV set-top boxes.
In a post on the official Google blog, CEO Larry Page wrote that the primary value Google sees in the acquisition is Motorola’s arsenal of 17,000 patents. In recent months, Apple, Microsoft, and others have sued prominent Android phone manufacturers like HTC, LG, and Samsung for patent infringement, with claims largely focusing on the Android OS. With little prior mobile experience, Google has few patents of its own to help defend its licensees. Motorola, on the other hand, has made millions of phones over the last few decades, accumulating a large patent portfolio along the way.
Most media outlets have reported that by licensing Motorola’s patents to Android manufacturers, Google will be able to help them defend against Apple and Microsoft, providing them the basis for counterclaims, resulting in mutually assured destruction and thus settlements freeing Android from patent troubles. The problem with this view is that Apple and Microsoft have already sued Motorola (see battle maps here and here); the cases are pretty far along and aren’t looking too great for Motorola at this point. If Motorola’s patents couldn’t protect it, then how will they shield the rest of Android-dom? And, as Florian Mueller writes, it’d indeed be quite ironic if, by the time the deal is approved, Google were to acquire a phone manufacturer that’s been banned from importing Android handsets into the U.S.
So clearly, patent protection from Apple and Microsoft is not the primary reason for the deal. If it were, Google could’ve just licensed Motorola’s patent portfolio (as Motorola shareholder Carl Icahn proposed just a few weeks ago). The fact that Google chose to purchase the entire company instead, and thus enter the phone hardware business itself, suggests a different modus operandi. So far, Google’s primary interest in the mobile space has been to increase access to its web services– that was the whole purpose of Android. But the company’s business practices on Android, from forcing licensees to use its services (see the Skyhook case– quite damning for a supposedly “open” platform) to giving only preferred partners early access to new versions of OS, suggest that Google wants a bigger slice of the mobile pie for itself.
Android licensees like LG, Samsung, and HTC are justifiably afraid of competing against the very company they get their phones’ operating system from. It’s unrealistic to imagine that Motorola would not gain a significant competitive advantage being under Google’s roof, and Google could easily decide to go vertical, creating Google-branded Android super-phones to match the iPhone’s tight hardware/software integration and leaving other Android licensees in the dust. An ancillary benefit for Google, of course, is that Motorola’s big presence in the TV set-top box market could be an entry point for its failing Google TV product.
One interesting provision of the deal is the reverse termination fee. If Google is unable to complete the deal, it must pay Motorola $2.5 billion– a fifth of the purchase price, four times the median for deals in the last year, and apparently the largest such fee in industry history. By contrast, if Motorola decides not to sell to Google, it must only pay $375 million. This seems to reflect Google’s desperation and Motorola’s concerns about regulatory hiccups– Google’s Android-related search business practices are already under FTC antitrust investigation.
Microsoft stands to benefit in that it can now market Windows Phone 7 as the only operating system OEMs can license without competing against the licensor’s own phones. Some believe Microsoft may follow Google’s move by acquiring Nokia (which is now a key partner on the Windows Phone platform). This is quite unlikely, especially if the Motorola deal motivates HTC, Samsung, and LG to put more effort into Windows Phone 7 (which they all offer but clearly place on the strategic backburner compared to Android). Microsoft wouldn’t gain anything beyond what it already has in Nokia (a high-quality hardware manufacturer exclusively committed to Windows Phone and armed with an immense patent portfolio), and besides, outside of Xbox, Microsoft still believes in the “ubiquity” strategy it used against Apple many years ago, mobilizing a whole industry of Windows-powered PC hardware manufacturers to destroy Apple’s bundled hardware-software offering.
RIM only gains in that the Google-Motorola deal kicks the mobile industry’s patent mess up a few notches, showing that the array of BlackBerry mobile patents is probably quite valuable. The issue is, however, that the only companies still interested in RIM’s IP would be firms that lack strong software portfolios and are looking to create their own phone OS (HTC or Samsung perhaps).
Time to sit back, grab some popcorn, and watch the tech giants duke it out for mobile supremacy.
Nokia CEO responds to Google VP’s “two turkeys” tweet, clarifies WP7 strategy
Feb 11th

Two days before the Nokia-Microsoft alliance was announced, Google’s Vic Gundotra attacked the two companies by tweeting that “two turkeys do not make an Eagle.” Now Nokia’s CEO Stephen Elop has responded with a tweet saying “two bicycle makers from Dayton Ohio, one day decided to fly”– referencing the Wright brothers.
Separately, Elop and Microsoft CEO Steve Ballmer provided some more details on the deal. The arrangement is not exclusive– Microsoft will continue to work with other phone manufacturers on Windows Phone 7, though Nokia will get some “unique” benefits out of the deal. When asked if Nokia would be able to customize “everything” on Windows Phone 7 (unlike current WP7 licensees), Elop said yes, but clarified that Nokia was unlikely to do so, as it preferred maintaining full compatibility across the Windows Phone platform.
Read on for more details.
Reports: Nokia may use Windows Phone 7; Microsoft India, Google execs hint at partnership
Feb 10th

Nokia CEO Stephen Elop (L), then head of Microsoft's Business Division, with Nokia VP for Devices Kai Oistamo (R) in 2009
Observers have been wondering what Nokia’s next step will be following its CEO’s Burning Platform memo yesterday. The Wall Street Journal and Bloomberg BusinessWeek reported this morning that Nokia is in talks with Microsoft to license the latter’s Windows Phone 7 operating system for use in its devices and that a deal may be announced at an event in London tomorrow. The company has also been in talks for several months with Google about its Android OS, which seem not to have panned out. Google’s flamboyant VP of Engineering, Vic Gundotra, posted a tweet yesterday presumably bashing Nokia and Microsoft after the Android negotiations fizzled:
Nokia CEO to employees: “We poured gasoline on our own burning platform”
Feb 8th
Nokia’s new CEO Stephen Elop, formerly of Microsoft, just sent out a fairly devastating internal memo to all Nokia employees. It’s a brutally honest portrayal of the mess the company is in and an interesting example of how to kickstart a company that on the surface appears to be doing fine (positive growth, still the largest market share globally) but actually faces serious threats that it has failed to address.
On the smartphone front, Nokia’s lead has severely eroded thanks to modern platforms like the iPhone and Google’s Android OS, which Nokia’s Symbian platform is still not competitive with and its Maemo OS has yet to battle. In emerging markets, its long-standing lead has been eaten up by Chinese manufacturers (many based on the city of Shenzhen, a famed hub of knock-off electronics).
Some tidbits:
- “Chinese OEMs are cranking out a device much faster than, as one Nokia employee said only partially in jest, ‘the time that it takes us to polish a PowerPoint presentation.’”
- “The first iPhone shipped in 2007, and we still don’t have a product that is close to their experience. Android came on the scene just over 2 years ago, and this week they took our leadership position in smartphone volumes. Unbelievable.”
- “Our competitors aren’t taking our market share with devices; they are taking our market share with an entire ecosystem.”
- “We poured gasoline on our own burning platform. I believe we have lacked accountability and leadership to align and direct the company through these disruptive times. We had a series of misses. We haven’t been delivering innovation fast enough. We’re not collaborating internally. Nokia, our platform is burning.”
- “They changed the game, and today, Apple owns the high-end range.”
- “Google has become a gravitational force, drawing much of the industry’s innovation to its core.”
Full memo after the break- it’s worth a read.
HTC HD2 triple-boots Windows Phone 7, Android, WinMo 6.5
Jan 24th

Vying for the title of the most customizable smartphone ever made, HTC’s legendary HD2 can now triple-boot Windows Phone 7, Android, and Windows Mobile 6.5, courtesy to posters at XDA-Developers. The 4.3″ phone, grandfather of HTC’s current large phones, has similar specs to today’s high-end smartphones (1 GHz Qualcomm Snapdragon, 512 MB RAM) and runs all three OSes smoothly (not at the same time though).
The triple-boot system entails running Windows Mobile 6.5 as the native OS, with Android and Windows Phone 7 installed on the phone’s MicroSD card. See the thread for instructions on how to make sure you’re cooler than people who have just two OSes on their phones.
Windows Phone 7 now fully works on the phone (earlier issues with accessing Windows Live services like the Marketplace have been solved). The HD2 has also seen ports of Ubuntu and Meego, so we could soon see a quad- or penta-OS HD2.
Source: XDA-Developers
Windows Phone 7 outlasts Android, iPhone 4 in grilling contest
Nov 13th

If “Will It Blend” isn’t enough for you, the makers of EZGrill have put up a comparison video between a Windows Phone 7 device (HTC Surround), an Android phone (T-Mobile HTC G2), and an iPhone 4 to see which lasts longer on a grill. Looks like Windows Phone 7 has a stronger “firewall” than the iPhone, and the Android phone roasts the quickest.
See the video after the break.





