Mayur's Posterous

Microsoft Sues Motorola Over Android

Microsoft Corp. launched a legal attack aimed at fighting the explosive growth of cellphones powered by Google Inc.'s Android software, as the technology giant struggles to find its own answer to the shift away from traditional computers in favor of mobile gadgets.

The software company sued Motorola Inc., one of the biggest backers of Google's software, claiming the cellphone maker is infringing nine patents in handsets powered by Android.

While Microsoft has struggled to win adoption of its Windows software for phones, Android, which Google gives away free, has been widely adopted by handset makers and software programmers.

1001microsoft

Microsoft plans to unveil a lineup of smartphones using the revamped version of its mobile operating system in early October. This launch is crucial for Microsoft, which has been battered by Apple's iPhone and Google's Android mobile software. Dow Jones Newswires' Roger Cheng reports.

The suit comes as Microsoft is poised to introduce its latest operating system for smartphones that can compete with Apple Inc.'s iPhone and devices running Android.

Motorola, which has stopped making phones running Microsoft's software, has bet its future on Android. The company is preparing to split itself apart, establishing an independent cellphone business.

Motorola said it hasn't received a copy of the complaint, which was filed in federal court in Seattle, but added: "The company will vigorously defend itself in this matter."

Google's mobile software is at the heart of other legal challenges. Apple has sued an Android phone maker, HTC Corp. for alleged patent infringement, while Oracle Corp. has sued Google directly. If they're successful, the lawsuits could help raise the costs for companies that use Android.

In a recent interview before it filed the Motorola lawsuit, Microsoft Chief Executive Steve Ballmer said there will still be a cost for using Android even if Google doesn't charge handset makers a traditional licensing fee for using it. "It's not like Android's free," he said. "You do have to license patents."

Microsoft's problems in the mobile business took a financial toll on Mr. Ballmer personally last year, according to a proxy report filed by Microsoft this week. For the fiscal year that ended June 30, Mr. Ballmer received a $670,000 cash bonus—only half of his total possible bonus.

Microsoft directors considered several factors in their decision, including the loss of market share for the company in the mobile-phone business and the failure of Kin, a Microsoft-designed phone for the youth market.

Any slowdown to Google's momentum could help Microsoft as it prepares to launch a new product next Monday called Windows Phone 7, an operating system that it has spent the last two years overhauling.

"We are disappointed that Microsoft prefers to compete over old patents rather than new products," a Google spokesman said. "While we are not a party to this lawsuit, we stand behind the Android platform and the partners who have helped us to develop it."

The lawsuit seeks unspecified monetary damages and a permanent injunction. Microsoft also filed a complaint with International Trade Commission.

"It's clearly an aggressive posture. My gut feeling is Microsoft is losing the handheld wars and they're using their patent portfolio to get some of it back," said Mark Kesslen, a patent lawyer at Lowenstein Sandler, who isn't involved in the case.

"When you think about the marketplace, it's Apple and Android," he added. "They're using their patent portfolio to either slow down the growth or get some piece of the market share through some other means."

An early entrant in the fledgling market for smartphone software, Microsoft began to lose ground several years ago when Apple came out with the iPhone.

The Apple product dramatically raised the technical bar for smartphones with its touchscreen interface and mobile Web surfing. In comparison, Microsoft's software, called Windows Mobile at the time, seemed outdated and was difficult to use.

The stakes in the mobile business are huge for Microsoft. In comparison with the more mature PC business, smartphones are a high-growth category, one that's increasingly attracting the creative energy of software developers.

More than two years ago, Mr. Ballmer ushered in a group of new senior executives to lead the company's mobile team, which then set about rewriting the Windows Mobile operating system. The overhaul took longer than expected, which in turn led Microsoft's key handset partners, including Motorola, HTC and Samsung Electronics Co., to expand their use of Android in phones.

Microsoft's share of the world-wide smartphone market this year is expected to fall to 6.8% from 13% in 2008, while Google is forecast to jump to 16.3% from less than 1% two years ago, according to IDC.

Microsoft executives now believe they're on the verge of a turnaround in their business. Windows Phone 7 has gotten early praise from reviewers for its user interface, which relies on a grid of text and icons on a home screen. The company is relying heavily on existing assets like its Xbox games business to jumpstart its position in gaming on Windows Phones.

"The goal is to be in the game, to establish our reputation and credibility," said Terry Myerson, corporate vice president of Windows Phone Engineering. "That's not a unit-volume and revenue goal, but it's the foundation for a real business."

The financial opportunity in the mobile business for Microsoft remains unclear. While Microsoft still seeks a licensing fee for using Windows Phone, estimated to be less than $8 a handset. Google seeks to make money instead through advertising when users conduct searches and perform other activities on Android devices. Microsoft also plans to derive revenue from advertising on Windows Phones.

"If they give away something for free and they don't pay royalties, they ruin the economics of the business," Roger Kay, an analyst at Endpoint Technologies Associates, said of Google. "They've been doing that in industry over industry."

Just as Apple sued HTC rather than Google, Microsoft has taken aim at Motorola because the cellphone maker derives revenue directly from selling Android-powered phones, making it easier to make a case for financial damages.

Microsoft's suit carries risks because it needs support from handset makers to be successful. But among the companies it has worked with in the past in the mobile business, Motorola is the biggest that hasn't signed on to use Windows Phone 7 in its products.

Microsoft deputy general counsel Horacio Gutierrez said there was no connection between Microsoft's decision to sue Motorola and the fact that the handset maker isn't making phones that use Windows Phone 7 software.

Earlier this year, Microsoft struck a patent licensing deal with another key partner for Windows Phone 7, HTC, that grants the Taiwanese handset maker rights to use Microsoft patents in HTC's popular Android phones.

In an interview before the Motorola suit was filed, HTC CEO Peter Chou said he believes the Microsoft still has an opportunity to become a player in mobile phone software, even after the troubles in its business.

"We went through a difficult time but this new thing is coming and we're all very excited," Mr. Chou said.

—Shayndi Raice contributed to this article.

Write to Nick Wingfield at nick.wingfield@wsj.com

 

Posted

Sony Ericsson LiveView™

Posted

Cute Girl Has A Catchy Dance

Yup, I've tagged this under "Android".

Posted

Mozilla’s Stunning Seabird Mobile Phone Concept

Not bad for a concept.

Posted

Nexus One Root

I just rooted my N1, running Cyanogen Mod 6 stable release with ADW Launcher :)

Not really sure if you guys know this (I've been closely following this since it came out before I tried anything), but you can now "root" your phone (essentially giving certain apps "sudo" or "super permissions") without unlocking your bootloader. I repeat, without unlocking your bootloader or voiding your warranty.

I got the APK off from http://blog.23corner.com/tag/universalandroot/ downloaded the Universal Androot 1.6.2 beta 5 APK onto my SDcard, installed it and tapped the "Go Root" button. (to unroot, go back to software and tap "Undo Root" and this leaves ZERO trace on your system). This APK also installs a program called "Superuser" onto your device which tells you which apps have superuser permissions (malicious apps can do bad things with superuser access) and also gives you the authority to deny to grant superuser access to a certain app.

Media_httpwwwtalkandr_unvrb

You can continue using stock Android 2.2 on your device and keep it rooted to run apps that run on rooted systems only. The first app I downloaded from the Market was the top rated Screenshot app and Titanium Backup - both work like a charm!

I'm a bit adventurous (at least I'd like to think so :P ), so I installed Cyanogen Mod 6 onto my device and I'm surprised that I've been using my N1 all this while without all the features that CM6 offers. I don't think I can go back to a stock system now :/ Installing the mod took me a while, I had to do a clone backup of my stock 2.2 and then screw around to my heart's content. I got thru a lot of mistakes by trial and error (best way to "learn" a device - I learnt how to jailbreak+unlock iPhones this way) and I finally completed a proper installation in about 2 hours. The best part is that I didn't lose any of my data/sms/apps/preferences - I'd like to expand exactly what I did (and didn't) do but it will be a very long (and boring) read.

I've also rooted and installed Cyanogen Mod 6 for a Droid X in less than 45 minutes :D  - for those interested read this thread http://forum.xda-developers.com/showthread.php?t=747598http://forum.xda-developers.com/showthread.php?t=747598

Posted

Nexus One update pushing out now - Android 2.2.1 and Build FRG83 | Android Central

Nexus One Android 2.2.1 update

There have been so many updates in the past week that it seems like every Android device is deciding to receive an OTA just to not feel left out. 

This time, Google's own flagship device, the Nexus One, receives an update to its OS. Here is the information on the update, courtesy of Devastatin from the XDA forums:

  • Android version: 2.2.1 (!!!!)
  • Baseband version: 32.36.00.28U_4.06.00.12_7
  • Kernel version: 2.6.32.9-27240-gbca5320
  • Android-build@apa26 #1
  • Build number: frg83

Update instructions after the break. Thanks, Anthony!

1. Download the Android 2.2.1 firmware for the Nexus One Here
2. Rename the file update.zip and copy it to your microSD card via USB. [Note: make sure the file is named update.zip and not update.zip.zip.]
3. Power down your Nexus One
4. Hold down the “Volume Down” button as you power the phone back on.
5. A screen should appear showing your phone’s system searching for various files. Scroll down to “recovery” and press the “Power” button.
6. When you see the triangle with an exclamation point symbol, press the “Power” and “Volume Up” buttons at the same time.
7. From the menu that appears, select “Apply sdcard:update.zip.”
8. When the screen displays “Install from sdcard complete” select “reboot system now” and wait for the phone to power back up. (this will take a long time)

Just a software update as far as we know. We have heard that once it is updated, some of the 3rd party keyboards have issues. Swype was reporting an issue while not working and Swiftkey wasn't predicting words. So if you do this update, watch out as you may not be able to use your favorite keyboard right away. 

This is a very new update, so we'll keep you up-to-date as we hear more. [XDA forums] Thanks to Anthony and Devastatin for providing info!

I can't find what changes does this update give.

Posted

Dual-core Android Devices by End of The Year?

 

tegra

 

Dual-core Android devices: they are the unicorn spit of Android Fan Boy dreams. There have been several claims of truth and “debunking” of those truths for dual-core powered Android devices this year. On one side of the Android Community, well known bloggers and even great pillars of the community stated that a dual core device is not possible by the end of the year. On the other side of this dual-core coin, other websites and discussions have arisen that a dual-core Android device launch is imminent.

6a00d83451c9ec69e20133f31f55ae970b-800wi


All these debates in regards to a dual-core device started when a leaked photo of the GL Benchmark for the HTC Glacier arrived on the scene, with rumors of a dual-core chipset, project emerald relations and unicorn urine. Soon after the HTC Glacier announcement, the community was set ablaze with more rumor of Android dual-core goodness, and for a good reason. As enthusiasts, we want the latest, the greatest and that means cooler, bigger and better screens; more efficient processors and better battery life. Repeatedly, naysayers have stated the HTC Glacier is in no way a dual-core powered Android device. Unfortunately, a recently leaked internal T-Mobile document revealing a “dual processor” MyTouch HD have added fuel to the rumor fire. Once again, these rumors had to be shut down again and again by members of the community who claims to be in the know. For now, the empty promise of dual-core hangs in the air, while everyone awaits for the next best and greatest…

… or do we? On the September 15th Android Show with Scotty Brown, Keyan Mobli from the hardware division of Team Douche explained the technology behind Qualcomm chipsets of now, tomorrow and beyond over-the-air. At the end of the discussion, Scotty asked Keyan about the possibility of a dual-core Android device. Although pessimistic, Keyan stated that it is possible a dual-core device could launch this year. Also standing on this side of the ring is the nVidia Tegra 2 chipset powered devices, which does not have to conform to the QualComm restrictions that Keyan spoke about.

radioandroid


So what does that leave for us? Dual-Core chips on Android are still in the air. As fans, we would love to have these powerful devices as soon as possible. All we can do as enthusiasts is to continue digging for more information. To finish the article, here are some of the best bets for a dual-core Android device this year:

LG Optimus T: This device was leaked in the T-Mobile accessory document by TmoNews. The Optimus T could go both ways, either it’s a low range LG device like the Optimus One or Optimus Chic, or it could be the LG Optimus Tablet/Highend Phone recently announced to be expected fourth quarter of this year.

lg-optimuspad-08-31-2010


Viewsonic Tablet: This device is expected to land sometime in October, just in time for my birthday. Sporting a Tegra 2 chipset, and a 1024×600 screen; although priced over $500 it could be the Christmas item every Android geek would love to have under the tree.

big_viewsonic-g-pad1

 

Sources and images courtesy of:
@kmobs, @AndroidDose, Wall Street Journal, The Droid Guy, Android Headlines, Tmonews, Engadget, AlienBabelTech, QualComm, GigaOm, RadioAndroid and HotHardware

 

Posted

Android Task Killers are dead and here's what you should be doing (MUST read for Android owners)

As a general rule, people have a hard time dealing with change. Android, being perhaps the fastest changing mobile OS in history, can leave people in the dust as the platform evolves. Things don't work the same from release to release. Some of this is user-facing, and people can adapt. But some changes are deeper system level alterations that people might not notice at first, and then might not understand why they've changed. The functionality and usefulness of task killers is one such advance. A lot has changed in the underlying Android OS regarding how background processes are managed. 

Read on to find out why task killers are obsolete, and why that's actually a good development.  

How task killing became dogma

In older versions of Android, memory management was an issue. These phones, like the G1, had too little internal memory for the heavy background processes that many apps chose to run. An app could spawn background services, but never kill them. Even if the app wasn't doing anything, these services would remain in memory. Over time this led to poor performance and overall system sluggishness. The solution, at the time, was to use task killer apps.  

Task killers like Advanced Task Manager and Advanced Task Killer became extremely popular in the Android Market because people saw performance and battery life benefits from ending background services. It was the snowball effect from here on out. Every new Android user was told to go get a task killer first thing when buying a new phone. Some carriers even included them on on phones and recommended them to customers. It became Android dogma that you had to kill tasks. 

But starting in Android 2.0, memory management got much, much better. Apps couldn't spawn processes only to leave them forever. The OS would gauge the level of system RAM, and close unneeded background services. Users on phones like the Droid could clearly tell that this was happening. With only 256MB of RAM, some memory-heavy apps would reliably cause the OS to close other apps running in the background. This is why many apps now use persistent notifications. Having that notification running will keep a background process it is connected to from being ended.  

What Froyo changed

When Android 2.2 Froyo was released, users and developers alike noticed something had changed again. Task killers didn't work properly anymore. If a user closed a particular app, it would just show up again. That's because the API for closing other tasks was removed. Now the "end" command has basically become "restart". Only the immediate background app can be closed. Associated services will stay put.

In modern versions of Android, you don't need to worry about clearing out memory, but this new tweak changed things in a bigger way. This change to the app shutdown API completely alters the risk/reward ratio. If you're not ending tasks, but rather restarting them, you actually use up more battery trying to free this memory. The apps will just restart, putting additional strain on the system. The only way to completely end a process now is to find it in the Manage Applications area of the Settings app, then tap the Force Stop button. It's just as destructive as task killing was, but it is more hidden and not accessible via an API.

Google likely changed the API because ending tasks at random can cause system glitches in the worst case. At best, you'll likely notice worse performance from your apps as they try to reconcile their assigned tasks with the fact that you are constantly interrupting them by them. 

What you should be doing

We've said in the past that the only legitimate use for a task killer is to get rid of processes that go rogue and eat up CPU. A better way to manage that is to actually monitor what's happening in the background. The app you'll want for this is called Watchdog. We told you all about it a few weeks ago in a Market Roundup. Check that out for the full rundown. 

What Watchdog basically does is poll the CPU to watch for apps that are getting greedy. This is really the holy grail of Android process management. It's quiet, sits in the background, and solves most of your task management needs. You'll be alerted is something goes wrong, and then Watchdog will allow you to restart the offending task. While doing this with an app that isn't misbehaving is a bad idea, you have little choice in cases when an app is legitimately out of control.  

Users with root on their device are able to undertake some additional steps to control tasks on Android. An app we really can't live without on our rooted handsets is called Autostarts. We introduced you to this last month, but we keep finding reasons to recommend it. Killing processes is a bad thing for system stability and battery life (especially under Froyo), but Autostarts lets you keep unneeded apps from starting up in the first place.  

Apps register with the Android OS when they need to start up based on a set of conditions. Autostarts lists all those conditions, so you can tell apps not to start up when they otherwise would. You can still launch them, but they won't launch themselves. This is perfect for those bundled apps that you use rarely, or simply don't need. If there's a lot of crapware on your handset, root users can also remove it completely with an app like Titanium Backup.  

Also for root users, is an app called AutoKiller. Don't let the name fool you; it isn't an aggressive task killer that's going to make your apps go all wonky. All it does is tweak the Android process manager to be more aggressive in ending background services. This won't end tasks midstream, it just ends unneeded apps a little sooner. You mileage may vary, some users find this helps quite a bit, others not so much. 

Most users that adopt a more modern way of managing (or not managing) their tasks see a big upside. A phone can feel faster, and the battery may last longer. When it comes down to it, killing tasks is just a hassle you don't need to deal with anymore. Everyone on Android 2.0 and higher should rely on Watchdog, or an app like it, to monitor for runaway background processes.  

     As more Android users are bumped up to Froyo, or just buy new devices, they will find their task killers inoperable. It's important they are steered away from this obsolete method of task management. Tell us about your task killing experiences in the comments.

 

Posted

Revealed: Android Honeycomb next up from Google | News | TechRadar UK

Media_httpmashablecom_oubka

Google is set to call the next iteration of its mobile OS Android Honeycomb, following on from the tablet-friendly Gingerbread platform.

Multiple sources have confirmed to TechRadar that the next version will be called Honeycomb, although details of what this upgrade will bring are still sketchy.

It's likely that it will be more of an incremental upgrade, in the same manner as Android 2.2 (Froyo) was to Android 2.1 (Éclair) as Google seeks to perfect the new platform on tablets and high-end smartphones.

That means Android Honeycomb will probably be Android 3.1 or Android 3.2, rather than a leap to the unimaginable magic of Android 4.0.

Honeycomb – a surefire way to eventual baldness

We've contacted Google about the new name, and unsurprisingly got no comment, but given each new Android iteration is named after sweets and cakes, there's not a lot to choose from.

Intriguingly, a quick Google search for 'Android Honeycomb' shows a few sites with the phrase present - but nowhere to be found when looking at the articles and sites in depth.

Gingerbread is due out towards the end of the year (or possibly leaking into 2011) with tablets from Toshiba and Samsung likely to make use of the upgrade, which will only work with fast processors and high-res screens.

However, it will be interesting to see where Android Honeycomb machines land in the marketplace against Google Chrome OS tablets, which we should start seeing in November onwards – is there a large enough tablet market to sustain two operating systems from the same manufacturer?

 

Posted

CyanogenMod boot animation

Posted