X

Android 4.4.2 KitKat Invading Canada on the Motorola Moto X

Everybody is waiting for Google’s new Android 4.4.2 KitKat, and some have to wait longer than others – well, if you bought a Moto X or Moto G, your wait was a short one, as the update has been going out at a pretty good clip.  Earlier this month Canadians with a Moto G on TELUS, Koodo, and PC Mobile were treated to their 4.4.2 KitKat update. Now, Moto X users on Rogers and Fido in Canada are getting some KitKat loving as well.  In a blog post today, Motorola Vice President Punit Soni said that the Canadian devices are the first Moto X’s to get KitKat 4.4.2.

This great news for our Canadian brethren, but still no word on the U.S. update, however, yesterday there were rumors that Sprint was rolling out testing of Android 4.4.2 KitKat, which means the rest of the carriers will not be too far behind. The Moto X and Moto G are great candidates to receive Android 4.4.2 KitKat.  Google designed KitKat to work with devices exactly like the Moto X and Moto G – devices that are not loaded with RAM and Snapdragon 800’s.  Google really concentrated on performance and the ability for Android 4.4 to work efficiently with as little as 512MB of RAM!  This should really help the performance in devices such as the Moto X and especially the Moto G.

Besides lowering the RAM requirements, Google also had to consider the many types of manufacturers and hardware their OS had to work on.  They optimized and streamed lined the way Android launches apps, keeps them in memory, and how it handles switching that information back and forth between tasks.  Getting all of this innovative technology to work on lower spec phones was no easy task, but the steps that Google took should take Android to a completely new level of fluidity and efficiency – in other words, your Moto X and Moto G should truly rock.

Do you have a Moto X or Moto G and are waiting for Android 4.4.2 KitKat update – please let us know on our Google+ Page and give us an update on your update.

Source: motorolablog | Via: androidcentral