Android Archive

Moto 360 and Wear 5.0.2: an update

Ever since my Moto 360 and Android Wear review, I've been hammering on my disappointment in Wear's unfinished, unpolished state, and the many issues that plague the platform. Since I've been using my Moto 360 again over the past few weeks, I think it's time to give a few short updates, because a seemingly minor release - from Wear 5.0.1 to 5.0.2 - has changed a few things for the better.

One of the biggest issues I encountered with Wear on the Moto 360 was laggy performance, stuttering, choppiness, that sort of stuff. After using 5.0.2 for a week or so, I've noted that this problem now seems resolved - at least for me. Touches are registered instantly, responsiveness is perfect again, and animations no longer lag and stutter. It's a world of difference.

A short note on battery life: after a full day of use, my Moto 360 usually sites at around 65%-70% battery left. In other words, with some careful planning, I could squeeze a full weekend out of my Moto 360, without needing to carry my charger with me. Quite nice.

None of this changes my overall perception of current smartwatches, though: they are too much computer, and too little watch. Still, these few improvements do lessen the blow somewhat, and that's always welcome.

Nvidia announces the new Shield, a 4K Android TV console

Speaking of TV boxes for gaming:

Tonight at a press conference scheduled to coincide with GDC 2015, Nvidia CEO Jen-Hsun Huang annouced the latest addition to its Shield line of products. Called simply "Shield," Nvidia's new device is a set-top box powered by Nvidia's Tegra X1 processor, using Google's Android OS and the search giant's new TV platform, Android TV. Shield supports 4K content encoded with H.265, and can stream local content from Nvidia-powered PCs at 1080p60. Shield also supports the company's game-streaming initiative, Grid.

New Lollipop devices not encrypted by default

Big news a few months ago: Google announced that all new devices which ship with Lollipop would have encryption enabled by default. Fast forward to today, and aside from Google's own Nexus devices, none of the new Lollipop devices actually seem to have encryption enabled by default. It turns out that Google has quietly relaxed this requirement in the Android Compatibility Definition, from 'MUST' to 'very strongly RECOMMENDED'.

Why? Performance, supposedly.

Our best guess at this point is that the encrypted-by-default requirement was relaxed to give OEMs more time to prepare their hardware for the transition. The performance problems can be offset by using faster flash memory, faster file systems like F2FS, and chips that are better at encrypting and decrypting data quickly, but phones and tablets take long enough to design that OEMs will need time to make these changes. Whether the change in policy was prompted by external pressure or an internal decision isn't clear, but the performance explanation makes the most logical sense.

Ouch. It's pretty clear Google wanted to quickly gain some positive press, especially after Apple announced it would turn encryption on by default in iOS, but failed to look at any possible performance repercussions. Sleazy move.

Samsung unveils Galasy S6, S6 Edge

Samsung, naturally, is hoping to put the Galaxy S series back on people's radar as a top device, and it's doing so by starting afresh with the Galaxy S6 and S6 edge. Though it numerically follows the GS5, the Galaxy S6 bears little resemblance to the previous model, and marks a pretty significant change in the way Samsung designs phones. At the same time, the S6 edge picks up the fun parts of the Galaxy Note Edge and leaves behind the poor software experience.

There's a brand new design philosophy in play with the Galaxy S6 and S6 edge, starting with the radical hardware change and flowing into a more considered software experience. These are the phones that Samsung's hoping will change the perception of its devices in 2015 - let us show you what they're all about.

After HTC, Samsung was up. Most of the information regarding the new Galasy S6 and Galasy S6 Edge were leaked before their official unveiling, so we already knew what to expect. I'm particularly pleased with Samsung greatly simplifying TouchWiz, and the simplified camera interface and performance are very welcome too. The all-metal construction is nice, and I personally really like the Edge's curved display - not because of any software functionality, but because it just looks really nice and ergonomic.

During the unveiling event, one thing really stood out: confidence. Rarely have I seen Samsung personnel being this genuinely enthousiastic and confident about their new phones. They didn't resort to crazy antics or heavy buzzword dropping - they showed the device, its strengths, and that was it. For the first time, it felt as if Samsung truly believes the S6 and S6 Edge can stand on their own merit, instead of being held up by marketing and similar tricks.

My contract renewal is up later this year, and the S6 looks quite intriguing, and I haven't found any Samsung phone even remotely intriguing since the SII.

HTC unveils One M9

It's hard not to have high hopes for the HTC One M9. Its immediate predecessor and the first phone in this rebirth of the HTC's flagship line - that'd be 2014's HTC One M8 and 2013's M7 - were fan favorites, and highly regarded by those of us who critique phones for a living.

But those phones were not without their flaws. And as we've seen HTC slowly address its devices' shortcomings (while growing and innovating in other areas), it's been difficult to not expect it to finally get things - all the things - right.

At least that's what we've been hoping, especially when it comes to its one tragic feature: The inconsistent performance of its UltraPixel camera.

And that brings us to this. The HTC One M9. We've spent a little time with HTC's latest, and this is what we've found thus far.

The HTC One M9 - the new one, announced today - looks very similar to the M8, but of course with better specifications and updated software. As much as I think the One series might be the best Android phones out there in terms of build quality, I just can't get myself to like its overall design. I do hope, though, that the M9 sells in large enough numbers, because HTC is going to need it.

Google to bring paid search results to Play applications

Google is bringing one familiar feature of Web search to its Google Play store: Paid search results.

The company said it will begin testing what it calls "sponsored" search results within its app store in the coming weeks. The move is intended to help developers better promote their apps in a store that boasts more than a million choices. Of course, it will also generate more revenue for Google.

Application stores are already completely and utterly useless and broken for application discovery, so I couldn't care less about this.

‘Android is ready for work’

Over a billion people today carry Android smartphones - devices that are more powerful than the computers we used just a few years ago.

For many, these phones have become essential tools to help us complete important work tasks like checking email, editing documents, reviewing sales pipelines and approving deals. But for the majority of workers, smartphones and tablets are underutilized in the workplace. Their business and innovation potential remain largely untapped.

Today we're announcing the Android for Work program to tap into that potential. With a group of partners, we're helping businesses bring more devices to work by securing, managing and innovating on the Android platform.

The elephant in the room.

Android-based Console OS available for download

Console OS, the Kickstarter project to release a distribution of Android specifically for regular PCs, has seen its first release. Sadly, for now, it only works with a relatively limited set of machines, so I can't try it out for you and tell you what it's like. I imagine it is not all that dissimilar from hooking a keyboard and mouse up to any other Android device, but it does add the ability to show two Android applications side by side. Additionally, it's based on KitKat and comes with the Google Play Store.

Interesting, but for now, the limited hardware support makes it hard to actually try it out. I'm intrigued though, and would really love to use it.

Google’s Android app requirements antitrust case dismissed

A U.S. federal judge has dismissed an antitrust lawsuit that charges Google harmed consumers by forcing Android handset makers to use its apps by default, but gave the plaintiffs three weeks to amend their complaint.

The two consumers who filed the suit failed to show that Google's allegedly illegal restrictive contracts on manufacturers of Android devices resulted in higher prices on phones, U.S. District Judge Beth Labson Freeman said in a Feb. 20 ruling.

Handset makers are free to release Android handsets without Google's applications, however, if you want one Google Android application, you got to have them all. I don't know if the latter is harmful in any way for consumers, but the plethora of insanely cheap - and sometimes, cheap and still really good - Android devices seems to contradict the complaint from the plaintiffs that it drives up prices.

Why Android Wear shipments aren’t surprising (or disappointing)

Wow. There are quite a few people talking about yesterday's Canalys estimate of 720,000 Android Wear shipments in the last six months of 2014. And most of that talk is ridiculous, with little to no perspective on the market itself. All of the doom and gloom I’m reading about Android Wear may yet come to pass, but to base it on shipment data at this point in time is premature for several reasons.

It's an interesting perspective, and the author certainly makes some good points, but disappointing or no, the real problem for me is still that Android Wear and current smartwatches in general are, simply, shit.

I've never based my opinions on popularity, and I don't intend to start now.

Android security – a Q&A with Google’s Adrian Ludwig

Very interesting interview with Adrian Ludwig, lead engineer for Android security at Google. There are a lot of fascinating answers to quote here, and I'm going for this one - do you need antivirus crap on your Android phone?

In 2014, according to Verify Apps data collected by Google and ignoring rooting apps that were intentionally installed by users, fewer than 0.15 percent of Applications installed from outside of Google Play to U.S. English devices were classified as Potentially Harmful Applications. Given the built-in protection provided by Verify Apps and the low frequency of occurrence of installation of PHAs, the potential security benefit of an additional security solution is very small.

I - and many others - have been saying this for ages, but let me just repeat it: do not install third-party security solutions on your Android phone. They are useless resource hogs that provide no additional security, and are built by scammy, untrustworthy, and needlessly alarmist software peddlers.

That being said, it'd be great if Google released more information about these background security tools in Android - more specifically, numbers, numbers, numbers.

Android 5.1 Lollipop

A few hours ago, we spotted no less than five mentions of "Android 5.1" on Google's Indonesian Android One page. Considering that 5.1 is quite a jump from 5.0.2, and something like 5.0.3 seemed more likely as the next bug fixer, we were cautious to suggest it may have been a mistake or a very persistent typo.

But as it turns out, Android 5.1 is real, and it's indeed shipping on Android One phones in Indonesia.

...but without a changelog, we have no idea what's in it, and as always, we have zero idea when anyone else is going to get it, if at all.

Androidâ„¢.

HTC: ‘an update on our Lollipop rollout’

In the spirit of continued transparency, I wanted to share a quick update on where we're at with our Android Lollipop rollout process. We've been working hard in the labs with Google and our carrier partners ever since the code release and are making great progress so far, but if you've been following the progress of this rollout you will know that Google has had to address several issues with this release. We've been diligently working to fix some of them on our end and incorporating Google's fixes as quickly as possible, but despite everyone's best efforts some carrier versions of the HTC One (M8) and HTC One (M7) will not meet our 90 day goal, which is February 1st. While we are committed to delivering within this time period, we are even more committed to ensuring these updates result in an even better experience with your device because that is what the updates are intended to do.

I applaud HTC for doing everything it can to reach its own 90 day promise, and it really sucks for them and their customers that bugs from Google itself causes delays. Android updates remain an utter and total mess, and by far Android's biggest weakness.

Microsoft to invest in rogue Android startup Cyanogen

Remember the nonsense from CyanogenMod CEO McMaster we talked about a few days ago? It turns out the motivation for the baseless comments from McMaster may not exactly be his own. As always, follow the money.

People familiar with the matter say Microsoft is putting money into Cyanogen, which is building a version of the Android mobile-operating system outside of Google's auspices.

Microsoft would be a minority investor in a roughly $70 million round of equity financing that values Cyanogen in the high hundreds of millions, one of the people said. The person said the financing round could grow with other strategic investors that have expressed interest in Cyanogen because they're also eager to diminish Google's control over Android. The identity of the other potential investors couldn't be learned.

Oh right.

CyanogenMod CEO wants to “take Android away from Google”

CyanogenMod CEO McMaster said some interesting things recently.

To remove all doubts right from the get go, here's how McMaster introduced himself: "I'm the CEO of Cyanogen. We're attempting to take Android away from Google." Asked to detail his vision, McMaster explained that Cyanogen wants to provide a version of Android that is open down to its core, that partners can use to build highly integrated services, in a way that is not possible right now with Google’s Android.

Well, either McMaster has no idea what he's talking about, or he's purposefully being disingenuous. It's most likely the latter, since he's got something to sell.

Of course, all the things McMaster claims his company will make possible with Android are already possible today, have been possible for years, and are actually actively being done all over the world. There are dozens of millions - possibly hundreds of millions - of users using Google-less Android all over the world; in China, Russia, the US, and beyond. Android's openness makes it possible to replace all of Google's applications and services with those from another company, vendor, or provider. Even you can do it! Just download Yandex.Kit, for instance.

The confusion seems to stem from people conflating Google Apps/Play Services with Android. This is an easy mistake to make for those not familiar with Android. Android itself (AOSP) is completely open source, and freely available to everyone to use as a base for a competing platform. Countless of Chinese companies, Russia's Yandex, Nokia, Amazon, and others have attracted millions and millions of users this way.

In contrast, Google has a lot of control over Google Apps/Play Services and keeps them (mostly) proprietary. However, despite a lot of rattling of chains from Apple bloggers and Ars Technica, Google Apps and Play Services are by no means a crucial, unmissable part of Android, and they, by no means, make Android "unforkable". In fact, if you look at the APIs currently part os Play Services, they are all strictly related to Google Services (as the name implies), and not Android itself (e.g. they don't deal with things like hardware access).

On top of that, despite Google Apps/Play Services being proprietary, they are "freely" available; Google basically employs a gedoogbeleid concerning their availability, and allows users of custom ROMs and non-Google Android to download them. My Jolla phone, which doesn't even run Android in the first place, has Google Apps/Play Services installed.

I am not happy with the fact that the Google Apps are proprietary, mostly because I see no need for them to be as such. Google could win a lot of goodwill by opening them up again, but Google being a company, it's unlikely they will ever do so. Play Services are a bit of a different story; while I would certainly love for them to be open as well, I understand (though not necessarily agree) Google wants to maintain control over the access to their very servers.

The article makes another common mistake: it claims that Android manufacturers are not allowed to release Android forks. This is based on leaked 2011 licensing terms covering the Google Apps/Play Services. However, despite these leaked terms, there are several manufacturers who release Android devices both with and without Google services; Huawei and Explay are good examples of that (they both sell regular Android phones with Google services, but also devices in Russia that use Yandex.Kit). This means that either the licensing terms from 2011 are outdated, or (more likely) they are custom, and do not apply to every manufacturer. In any case, the blanket statement that all manufacturers must choose between nothing but Android with Google services, or no Android services at all is clearly not true.

In any case, I'm sure McMaster knows all this just fine - you can't be the CEO of CyanogenMod without said understanding - which makes these comments all the more paper-thin. Then again, after the scummy way CyanogenMod treated OnePlus, I'm not exactly surprised.

This is Google’s latest Project Ara prototype

Google's Project Ara modular smartphone project is arriving soon, at least if you're in Puerto Rico. At its Project Ara Module Developers Conference today, Google said that it plans to launch a pilot in Puerto Rico in the second half of this year, selling phone chassis and modules through local carrier partners, as well as through a fleet of small trucks.

I like this project. I have no idea if it's going anywhere, but at least someone is having the guts to try and experiment with new and/or different ideas. That's science, and that's how we move forward.

Is Google lost? A reflection on Android navigation

I remember my first Android device, and how it differed to the ones I have now in one major point: navigation keys. My old Motorola XT316 (a mid-range phone for Latin American markets) came with Froyo 2.2 and featured 4 TFT capacitive navigation keys: menu, home, back, and the long gone "search". Android phones have come a long way since that OS, and since the early days of archaic UI design and choppy performance. Now we have the most beautiful and smoothest Android, and arguably one of the best Operating Systems... But there's something that I really think has not improved all that much despite all the optimizations, and that is navigation.

While there's always room for improvement, I do think Android has much, much bigger problems than this, like, you know, updates?

CyanogenMod for Android One

Android One represents Google's attempt at reaching "the next billion users" - starting today, CyanogenMod 11 (KitKat) builds are available for the 'sprout' devices. As the devices are currently setup for CM11 only (work on CM12 is in progress) these builds will trickle once a week, every Sunday.

This release represents a few firsts for us. Not only are these the first Android One devices and first official release of CM for these devices, the Android One device is the first ever officially supported Mediatek device. Mediatek (MTK) devices have been notoriously difficult for the developer community to complete fully functional bring-ups, and this marks a milestone in that effort.

Hopefully this also means good news for other Mediatek devices.

Android gets its own Surface clone

Microsoft, it seems, is not the only company that believes in the concept of a productivity tablet. And it's not the only company that thinks that a kickstand and a magnetic keyboard are all it takes to transform a tablet into a mobile workstation.

The Jide Remix, made by a trio of former Google engineers, is for all intents and purposes a Microsoft Surface that's built for Android.

It's about as cloney as you can get, but the fact that is still looks very nice is testament to just how pretty Surface really is, and how much sense the concept makes. Surface's hardware is excellent - it's just the software side that always let it down.

I don't think Android is going to fix that.

Google updates Android platform distribution numbers

The developer dashboard has been updated, and there's some big movement this month. In the post holiday window, KitKat is up a healthy 5.2% and Gingerbread drops another 1.3%. One thing you won't see on the chart is Lollipop. Android 5.0 still hasn't hit the 0.1% threshold to be included in the data, just like last month.

Google Play Services mitigates a lot of the concerns about updates - not that many people seem to understand that - but this is still Android's biggest weakness by a huge margin. Sadly, it's also something Google seems to be doing little about. Also, this.