<![CDATA[Gizmodo: coms]]> http://tags.gizmodo.com/assets/base/img/thumbs140x140/gizmodo.com.png <![CDATA[Gizmodo: coms]]> http://gizmodo.com/tag/coms http://gizmodo.com/tag/coms <![CDATA[Pandora Released for BlackBerries]]> We've heard that BlackBerry users aren't supposed to care about music, only typing on full QWERTY keyboards during marathon power lunches. In case we've been lied to, you should know that Pandora v1 is out for BlackBerry—so long as you aren't on T-Mobile. [Pandora via BGR]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5173494&view=rss&microfeed=true
<![CDATA[Acer's First Smartphone Has Awkward Style, Solid Potential]]> As Acer's entry into the smartphone market approaches, details of handsets are beginning to leak. BGR has pictures of one: a touchscreen QWERTY phone with a decidedly novel approach to pop-out keyboarding.

BGR's sources didn't have much to say about the device, except the easily-guessable fact that it would run either Windows Mobile or Android (you can imagine which one we're hoping for). The keypad, as pictured, looks kind of bizarre. A portrait-mode QWERTY may be all we're seeing here, but if Acer has managed a swivel system by which the keyboard can work in portrait and landscape modes, the form-factor could be an instant winner.

The tipster also claimed the Acer would display an iPhone competitor alongside this handset at MWC on the 16th, which—assuming the conventions of the last few years hold—just means that they've got a full-touchscreen handset. [BGR]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5146003&view=rss&microfeed=true
<![CDATA[Compulab Exeda: A Stocky Phone Stuffed Full of Features and OSs]]> The Compulab Exeda won't be the most high profile Android/WinMo handset coming to the market, but the squat candybar features enticing half-Blackberry, half-80s calculator styling and a robust feature set.

Promising to support both GSM and CDMA when released (unlocked) this March, the Exeda also includes a 520MHz Marvel processor, 3.5-inch sun-readable touchscreen, QWERTY, mini trackpad, about 1GB of built-in storage, GPS, Wi-Fi, Bluetooth, 10/100Base-T ethernet port, 2MP camera and MicroSD expandability. It's also slated to support Android, WinMo 6.1, Windows CE 6 and Angstrom Linux.

There's no price on the Exeda just yet, but at 4.9” x 3.7” x 0.6”, it's a hair taller and thicker than the iPhone, as well as quite a bit wider. But I just kind of like it. [Exeda via Ubergizmo]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5131507&view=rss&microfeed=true
<![CDATA[AT&T Wants All Its Smartphones Running the Same OS, Eventually]]> AT&T plans to run a single mobile OS on all of its branded smartphones, citing the "support nightmare" of maintaining multiple platforms at once. Curiously, this announcement was made at a Symbian conference. Updated 19:26 EST.

It's not entirely clear what AT&T means by this announcement, but one question was addressed right off the bat: the iPhone, which the company described as "a third-party device" that generally isn't supported or interfered with by the company, is immune. Such a consolidation would push all but one of Microsoft, RIM, Nokia or even Google out of AT&T's stable, which might be construed as brash.

Even more bizarre are the implicit expectations for phone manufacturers. Would RIM, assuming their phones aren't deemed "third party products", be expected to adopt a new OS? Will Nokia phones be excluded from AT&T's lineup unless they run Windows Mobile? Simultaneously stating that the plan would only include AT&T branded smartphones (of which there are few) and that it would be a "dramatic restructuring", the company has left the scope of this initiative a mystery.

As for which OS would be chosen, the location of the announcement and mentions of a preference for an "open" platform are all we have to go on. I could imagine these statements raising a few eyebrows around the industry, so don't be surprised to see some kind of clarification issued in the next few days. [Yahoo]

UPDATE: Although it is possible some quotes in the original story came from a post-speech interview with AT&T's Roger Smith, commenter Sinecure saw the presentation and took awy a completely different message:
I sat through the entirety of Roger Smith's presentation at the Symbian show yesterday and I did NOT come away with that impression one single bit. Methinks some Yahoo reporter just got a little over-excited for an interesting headline. I'm calling major BS and misinterpretation on this one.

Frankly it makes me even more suspect of some of the reporting on technical subjects out there.

Bottom line: I heard this supposed "announcement" first hand and I did not hear him say anything approaching what the reporter is saying.

UPDATE II: And now for that clarification I was talking about. AT&T's statement on the matter:
We have no plans to standardize on one platform for our smart devices.

We want to give our wireless customers maximum choice – in innovative devices, applications, operating systems, and more. One way to maximize customer choice is to begin to reduce fragmentation in the wireless OS environment. That is why we are a member of the Symbian Foundation.

That fragmentation puts a heavy burden on wireless carriers, handset makers, and especially apps developers, who have to create for multiple operating systems and sometimes for multiple versions of the same operating system.
]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5102331&view=rss&microfeed=true
<![CDATA[Mobile Browser Battlemodo: Which Phones Deliver The Real Web]]>

Before 2007, using the internet on your phone would make you want to kill yourself, if you were dumb enough to believe the crap splattered across that tiny screen even was the "internet." But the combination of increased bandwidth and better mobile software means that more phones really are promising to deliver the real internet, in living color. We tested eight different browsers, and while some put smiles on our faces, others proved that rendering HTML correctly is a far cry from actually giving you an awesome web experience. And what about 3G vs. Wi-Fi? Everything the carriers have told you is a lie. This is the true state of mobile web.

Before we give you the rundown of each of the most prevalent mobile browsers, here's how they all stacked up in a timed test of how fast (and how well) they could render websites, chosen for their diversity and particular challenges:

CHART KEY: Number value is time for complete page load in seconds; page rendering is rated from "Fail" to "Excellent" for each; and the color (red, yellow, green) indicates overall performance taking into account both speed and rendering accuracy: Green = good overall, Red = fail overall.

This second chart runs through the same procedure with all of the phones that had Wi-Fi options:

It's a pretty daunting pile of numbers, so let's break it down into standard prose, rating each browser as we go:
Android
A fast, smart mobile browser based on WebKit. It tackles most sites with (almost) unrivaled grace and speed. Panning and zooming could be smoother and more responsive, but with a ton of options for getting around a page—various touch methods and the trackball—few sites will be challenging to zip around. The only thing we really miss is multitouch for zoom. Buttons just aren't a very elegant or precise solution, and while the whole-page magnifying glass technique is nice, we'd love something a bit more refined. Overall though, we're happy campers on Android's browser. Grade: B+

BlackBerry Bold
Leaps and bounds ahead of the browser BlackBerry users have put up with for years, it renders most pages correctly, even if scripts give it a conniption fit (hence its long load times for Wikipedia and the WSJ). It uses the standard "click to zoom" metaphor, which works well enough, though getting around a page with the trackball can be kind of a work out for you thumb. The Column View, which squeezes a whole page into a single column, is fairly convenient and makes it easier to get around wider pages, even if it doesn't work equally as well on every site (nice on Wikipedia, ugly on Giz). Hopefully they fix the script performance in the Storm, which is using an updated version of the Bold's browser. We humbly suggest they ditch their home-baked browser for one based on WebKit, which would help out there. Grade: B-/C+

iPhone
What can we say? It's still got the best mobile browser around. It crushes basically everything but Android's browser—which is also based on WebKit—in speed and outclasses its still classy brother-from-another-mother (and everyone else) with the ease and elegance of its multitouch zooming. Some pages still give it fits, and it's missing Flash support, but it really does deliver an unrivaled mobile web experience. We love it, but make no mistake we're eagerly waiting for something better. (Mobile Firefox? Is it you?) Grade: A-

Nokia E71 Symbian S60
Hey look, another web browser with WebKit guts! It doesn't perform quite as well as Android's or iPhone's iteration where speed or render accuracy are concerned (can any Symbian nuts explain why?), but it does a serviceable job. The big thing it has going for it is Flash Lite 3 support, though performance there is kinda assy and memory intensive. Navigation is tougher with the E71's d-pad than with a trackball, but the whole page magnifying approach makes it easy enough to get around (too bad you have to dig through a menu or two to get to it). Not bad, but short of excellent. Grade: B-

Internet Explorer on Windows Mobile
Jesus Christ. This is a joke, right Microsoft? Hahaha. No really, this is the worst smartphone browser on the planet. It couldn't render its way out of an ASCII-art paper bag. It totally screwed up every single test page, except for Wikipedia, which it only mostly screwed up. Good luck navigating a page if you're granted the miraculous occurrence of it being rendered in a state that's usable. Grade: F-

Opera Mobile on Windows Mobile
Microsoft's own intentions notwithstanding, you can use the internet on a Windows Mobile phone. You just need Opera Mobile. It's kind of hobbled by Windows Mobile's assy performance, but it usually gets the job done. Not as quickly or always as accurately as its WebKit rivals, but it's definitely usable. Interestingly, it benefits more from the extra bandwidth offered by Wi-Fi than the WebKit browsers do. Menu-based zoom is annoying and imprecise. Touch-based panning worked okay, though a little laggy. We mostly navigated with the Samsung Epix's optical cursor, which worked pretty well, somewhere in between a d-pad and a trackball. Grade: C

Sprint Instinct
Holy CRAP. This is not the painfully lousy browser the Instinct shipped with not by a long shot. The original was slow and fairly feeble, even if it was the head of its (dumbphone) class. The new 1.1 browser really is a life-changing upgrade. It suffers in the chart because it's much slower than most other browsers, and zooming is still clumsy, but once the page loads, it's much smoother to pan and actually move around. I got a bit annoyed that it lied about pageload time, hanging at the last 2 percent of the status bar for half the load, but it usually gets things right. This is the best non-smartphone browser you can get. Grade: C+

LG Dare
Like the Instinct, the Dare proves you can actually get a usable browsing experience on a feature phone. It's a little nimbler at loading pages than its Korean blood rival, but the reason it ultimately posts lower marks than the Instinct is that it buckles way more easily under a moderate to heavy pageload, turning it into an unresponsive picture of the website you were trying to look at. Still, it renders most pages fairly accurately, and we like the sliding zoom scroll bar, at least in theory, since it seems like an intuitive way to deal with the zoom issue. Unfortunately, it works more like a glorified pair of buttons. (Note: I don't think the speed was actually a piddly 300 Kbps—I think it just had a problem dealing with DSL Reports' mobile speedtest, even though it's text-based for the dumbest of phones.) Grade: C

Methodology
We tested every browser only using the full—not mobile—versions of selected sites, over 3G and, whenever possible, Wi-Fi. All scripts were turned on, and the cache was cleared before each round of testing. We took the average of a series of five sequential speedtests to give us an idea of the bandwidth we're dealing with, and timed how long it took to completely load a site according to each browser's progress bar. We assessed whether or not it rendered the page correctly, on a scale ranging from "excellent" to "good" (a couple things out of place) to "utter fail" (I've seen prettier train wrecks).

A few additional issues to note: Internet Explorer would not work on Wi-Fi. Opera yes, our Skyfire install, yes, Internet Exploder, no. (Samsung suggested it might be because of Opera.) We didn't pursue the matter because of how IE did in the 3G tests: A page that looks like a pile of blended dog poo is going to look like that no matter how much faster it loads. Sprint's updated Instinct and Verizon's Dare, which we included as best-of-class examples of feature phones, don't have Wi-Fi capabilities. We left out Opera Mini and Skyfire, since they both leave most of the hard work to servers which essentially spit out a kind of image file—besides, we don't think this kind of internet-by-proxy browser will be around for much longer.

The Big Gulp
Remember our mantra it's code that counts? It's true for mobile internet too. An awesome browser can make up for a mediocre network, but a terrible browser delivers a crappy experience no matter how great the network is. It's all about the browser. As it stands, WebKit is clearly the best thing going, but even then, software implementation matters, or Nokia would deliver as good a performance as Android and iPhone. Proving the point, it's striking how little Wi-Fi actually boosted speed beyond 3G—hell, WebKit browsers on 3G slid past some of the others that were running on Wi-Fi.

Another thing to note is that the zoom metaphor is a tricky thing to nail. Buttons are too brutish, the magnifying glass is imprecise. Multitouch seems to be the best way to handle zooming in and out in a way that's intuitive and precise. Hopefully we'll see other developers start to use multitouch interfaces in touchscreen phones (*cough*ANDROID!*cough*).

As much as this blow-by-blow battlemodo shows you all the problems we encountered, the big picture is that really, mobile web is pretty dandy right now, and getting dandier. It could be more reliable, faster, maybe a little more versatile, but for the most part, yes, you can access the internet on your phone. Compared to just two years ago, that's really saying something. We can't wait to see what it'll look like in two years. Maybe Internet Exploder will actually work. Nah, that's a little too sci-fi.

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5090988&view=rss&microfeed=true
<![CDATA[VMware Pushing Virtual Machines for Smartphones, Will Support Parallel OSes]]> VMware, which consumers know mostly for their Fusion desktop virtualization software, is moving into the mobile space, albeit surreptitiously. The company has announced VMware MVP, a thin layer of software that will interface between handsets' hardware and operating system, allowing for a standardized development platform across any handsets that include it. What does this mean for regular consumers? For now, not much. If the tech finds enough support for hardware vendors, though, the consequences could be major.

For developers, having this VMware abstraction layer is pretty attractive from the start. If the layer is installed in, say, Blackberry, HTC and Motorola smartphones, then the developer will only have to write the software to run on the virtual machine's universal simulated hardware, rather than each phone's different hardware. VMware is promoting this capability as sort of a Java VM on steroids, which — with wide enough deployment and high enough efficiency — could mean an end to platform-specific apps. But that's not the most exciting part.

VMware's European product director told ZDNet that MVP could "make it possible for various mobile operating systems, such as Symbian, varieties of Linux and Windows Mobile, to 'co-exist on the handset as well'." In other words, due to the low-level nature of the solution, a VMware MVP-equipped handset could not just run platform-agnostic programs, it could run entirely different OSes in parallel. Whether anybody will take the time to make that happen remains to be seen, but just the possibility that new hardware could support pretty much any mobile OS is pretty exciting. [ZDNet]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5083023&view=rss&microfeed=true
<![CDATA[CNN Fortune: Blackberry Storm as Low as $99 on Verizon?]]> Fortune's Techland blog is reporting that with Vodafone's recent announcement that they would fully subsidize the Blackberry Storm, Verizon might be considering similar low cost options to compete against the iPhone. While some inside sources claimed Verizon may go as far as to make the phone free with a two-year contract, other anonymous blabbermouths from the Verizon camp shot that notion down.

Most analysts believe the Storm will be equally priced to the 8 GB iPhone at the very least, but its realistic to see it at a $99 or $150 price point. The goal is to move some serious units during the holiday season, but for that to happen, Verizion needs to actually release the Storm first. [Techland]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5072948&view=rss&microfeed=true
<![CDATA[Smartphone Is a Dumb Word: We Need a New Name]]> It's 2008. Why are we still calling the devices we carry in our pockets "phones." The difference between cordless phones and cell phones is just one word, though the difference in functionality is vast. Even more clumsily, we call phones with email and web browsing "smartphones," despite most modern geeks using less than 10% of their battery to make calls. With so many disparate core features—emailing and browsing, plus texting, video calling, video recording, pic snapping, music listening, video watching, game playing and day organizing—shouldn't we be ditching the word "phone"? The term is so...1876. We need a new name, and I humbly suggest "com." Follow me on this one:

Why com? I admit, the word may bring to mind web addresses, military jargon or even sci-fi, but it makes a lot of sense here. It's simple—like "phone" which was colloquially adapted because "telephone" was two syllables too long—and it's short for both "communicator" and "computer," both of which describe the device in my pocket better than "phone" does.

Sticking a "smart" in front of "phone" is no better. The prefix made sense years ago, when PDAs were slowly merging with phones, but even the free-with-activation phones of today have cameras, games, apps and organizational software better than the best phones before. As phones get smarter, all phones become smartphones. So again, why com?

After all, your phone is primarily a communicator. While making voice calls will always be a major part of the device, you're already using it to communicate with everyone in many other ways. Today. Right now.

Text messages took many, many years to get to the point where it was both super usable, reliable and ubiquitous, Americans now send more text messages than they make phone calls. Email's just about at that point as well, with many devices offering desktop-class email that gets beamed to you only seconds after it's sent. It's so good, many business professionals are able to live off BlackBerries alone for days. Also, instant messaging on phones with proper keyboards can often be even faster than text messaging, and more immediate than email. Then there's video calling. It may not be as prevalent in the US, but people in countries like Japan have been two-way video chatting from their handhelds for years.

And none of this advanced communication would be possible if your phone weren't a miniature computer.

It's true that most phones are only weak computers now compared to what you're running at home or work. They have kinda-usable keyboards, decent music and video playback, passable web browsers (on some devices), so-so picture taking and blurry video shooting, but you can bet these features are only going to get better as phones are able to run desktop-class applications. Think about the amount of power you have in your phone today. Even crappy phones are capable of more processing than your PC was 8 or 10 years ago. Just imagine where your handheld will go in another 8 to 10.

"Smartphone", or "mobile device", or "PDA", or "handheld computer" just won't do. We need something different. Something not clunky. And I think com could be it.

If com evokes thoughts of "comm", the Star Trek communicator (and by association the Tricorder, that ultimate do-everything handheld), that's good. We're talking about a device that doesn't just carry a conversation, but enables you to have face to face interaction, get instant text, image or video streaming updates on anything you're interested in and run the type of games that used to be only playable on living room consoles. Being able to talk to anybody while you're walking on the street was the stuff of science fiction 50 years ago and we're doing it now; there's no reason why the future features won't be just as amazing to people today.

The term com is supposed to be a little forward thinking and a feel just a little bit awkward. New things often are. It's a word I think we'll have to grow into. If you've got a better name in mind, let us know in comments. But if com does take off, it could be the word we use for these handheld communicators and computers for the next fifty years. Com. My com. Your com. Our coms.

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5061705&view=rss&microfeed=true