Android Archive

Cyanogen shuts down CyanogenMod; CM forks into Lineage

The implosion of Cyanogen, Inc., has reached its zenith. The company is shutting down all services related to CyanogenMod, effectively killing the open source community project, and since Cyanogen, Inc., owns all the trademarks regarding Cyanogen, the community project can't continue operating as-is.

As a result, CyanogenMod has forked itself into LineageOS, and plans to continue doing what it does best.

Embracing that spirit, we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches. This is more than just a 'rebrand'. This fork will return to the grassroots community effort that used to define CM while maintaining the professional quality and reliability you have come to expect more recently.

I hate saying "I told you so" but... Who am I kidding - I love saying "I told you so".

I told you so.

Google renames Brillo to Android Things

Google wants to put Android in the next wave of smart devices that'll be vying to fill up your home. It's launching a version of Android today called Android Things that can run on products like connected speakers, security cameras, and routers. The OS is supposed to make it easier for companies to start shipping hardware, since they'll be able to work with the Android dev tools they already know.

Android Things is a new name, but the operating system itself isn't strictly new. It's basically an update and a rebranding to Brillo, an Android-based OS for smart devices and Internet of Things products announced a little more than a year and a half ago. Brillo has - publicly, at least - gone close to nowhere. It was more or less a no-show at CES last year, and there's been little mention of it since.

Insert some quip about Google and naming here.

Google adds true multi-language support to Android’s keyboard

Google released a keyboard app for the iPhone some months back called Gboard, and everyone was wondering if it would come to Android. Well, now it has as the v6.0 update to Google Keyboard. It's not only a name change, though. There are a few important new features, including a search shortcut and true multi-language support.

Finally - finally - Google adds true multi-language support to the official Android keyboard. iOS added this in - I believe - iOS 10. Are the sheltered men of Silicon Valley finally realising vast numbers of people live multilingual lives on a daily basis and that technology is woefully ill-equipped to deal with that fact?

We'll know for sure once things like Wear and the Apple Watch no longer require full wipes and resets just to switch input languages.

Nokia making a comeback in 2017, Android phones inbound

Back in May, we heard that HMD Global - a new mobile company made up of ex-Nokia staffers - is looking to use the Nokia name to manufacture smartphones running Android as well as feature phones. Today, HMD has announced that it has secured exclusive licensing rights to Nokia's branding for 10 years.

The first batch of Android smartphones bearing the Nokia name will make their debut in the first half of 2017.

HMD is a Finnish company staffed with ex-Nokia people, so it makes sense they'd be working together on this. Hopefully this means Nokia can focus on what it does best - the backend - while the smaller, more nimble HMD san focus on making great phones.

The fight against Ghost Push continues

Ghost Push has continued to evolve since we began to track it. As we explained in last year's Android Security report, in 2015 alone, we found more than 40,000 apps associated with Ghost Push. Our actions have continued at this increasingly large scale: our systems now detect and prevent installation of over 150,000 variants of Ghost Push.

Several Ghost Push variants use publicly known vulnerabilities that are unpatched on older devices to gain privileges that allow them to install applications without user consent. In the last few weeks, we've worked closely with Check Point, a cyber security company, to investigate and protect users from one of these variants. Nicknamed 'Gooligan', this variant used Google credentials on older versions of Android to generate fraudulent installs of other apps. This morning, Check Point detailed those findings on their blog.

As always, we take these investigations very seriously and we wanted to share details about our findings and the actions we've taken so far.

An interesting post by Adrian Ludwig, Android's security chief, on a site called "Google Plus".

Pixel security: better, faster, stronger

Encryption protects your data if your phone falls into someone else's hands. The new Google Pixel and Pixel XL are encrypted by default to offer strong data protection, while maintaining a great user experience with high I/O performance and long battery life. In addition to encryption, the Pixel phones debuted running the Android Nougat release, which has even more security improvements.

This blog post covers the encryption implementation on Google Pixel devices and how it improves the user experience, performance, and security of the device.

These kinds of things should've been default a long time ago.

Secret backdoor in some US phones sent data to China

For about $50, you can get a smartphone with a high-definition display, fast data service and, according to security contractors, a secret feature: a backdoor that sends all your text messages to China every 72 hours.

Security contractors recently discovered preinstalled software in some Android phones that monitors where users go, whom they talk to and what they write in text messages. The American authorities say it is not clear whether this represents secretive data mining for advertising purposes or a Chinese government effort to collect intelligence.

Through Chinese manufacturer BLU, some 120.000 BLU phones in the US were affected as well. According to BLU, the company immediately removed the offending software. The original purpose of the software was, supposedly, to aid in the detection of junk messages.

“Android: choice at every turn”

A few days ago, Google filed its official response to the EU antritrust investigation into Android. The company details its main arguments on the Android Blog, and it's definitely worth a read. The blog post is remarkably open about one of Android's main shortcomings - fragmentation.

To manage this challenge, we work with hardware makers to establish a minimum level of compatibility among Android devices. Critically, we give phone makers wide latitude to build devices that go above that baseline, which is why you see such a varied universe of Android devices. That's the key: our voluntary compatibility agreements enable variety while giving developers confidence to create apps that run seamlessly across thousands of different phones and tablets. This balance stimulates competition between Android devices as well as between Android and Apple's iPhone.

Android's compatibility rules help minimize fragmentation and sustain a healthy ecosystem for developers. Ninety-four percent of respondents who answered questions on fragmentation in a Commission market survey said that it harms the Android platform. Developers worry about it, and our competitors with proprietary platforms (who don't face the same risk) regularly criticize us for it. The Commission's proposal risks making fragmentation worse, hurting the Android platform and mobile phone competition.

The whole post is worth a read. As I've said before - I'm glad the EU keeps these large companies on their toes, but the accusations regarding Android seem way off base to me. In the end, market regulation needs to benefit consumers, not harm them - and it's easy to see how fragmenting Android into incompatible Samsung, Sony, HTC, and Google Androids would definitely harm consumers and developers alike.

I think there's a lot more fodder to be found looking at the relationship between companies like Samsung and Apple on the one hand, and carriers on the other. On top of that, the EU could've invested a lot more effort into fostering alternative platforms, instead of letting Microsoft ruin Nokia and run it into the ground (speaking of places where there's fodder to be found).

Nobody wants the proverbial Android N.

Google’s plan to make Android updates suck less

We have a theory: "Android Extensions" is a plan to bring the easily updatable app model to the AOSP APIs. Like Google Play Services, we think this app will be a bundle of API shims that Google can update whenever it wants. The difference is that everything in Play Services is a closed-source Google API, while "Android Extensions" would be collections of fresh AOSP code delivered directly to your device via the Play Store. The CDD's stipulation that OEMs "MUST preload the AOSP implementation" is telling. It says that 1) this is AOSP code, and 2) OEMs aren't allowed to "customize" it.

If Ars' assumptions are correct, this looks like a decent step forward - assuming it pans out, of course. Clever, too.

Android Auto: now available in every car

But we know there are millions of older cars on the road that are not compatible with Android Auto, and many don't have a screen at all. We wanted to bring the same connected experience to these drivers too.

So today we're excited to introduce a whole new way to use Android Auto: right on your phone screen! This update allows anyone with an Android phone (running 5.0 or later) to use a driver friendly interface to access the key stuff you need on the road - directions, music, communications - without the distraction of things that aren't essential while driving.

It's not the UI of a phone that causes the distraction; it's the act of communicating with people not in your car that causes the distraction.

Don't use messaging or calling applications while driving. You are a danger to others and yourself, no matter how hard people always protest that "it doesn't apply to them". You can slap large touch targets on a dangerous activity, like Apple and Google do, but that doesn't make it any less inherently and deeply dangerous. You are toying with lives.

Android 7.1 Developer Preview released for Nexus devices

A couple of weeks ago we announced that a developer preview of Android 7.1 Nougat was on the way. You can get started with this new release today by downloading the SDK and tools. To get the 7.1 release on your eligible device, enroll your device in the Android Beta program. If your device is already enrolled, you'll receive the update automatically.

I got the update on my Nexus 6P late last night, and it installed without any issues.

Verizon, Google promise zero update delays for Verizon Pixel

Last week, I ragged on the Verizon models of the Google Pixel, so in the interest of fairness - here's Verizon and Google responding to the criticism levelled at the usual role carriers in the US play in delaying updates and adding tons of crapware. Verizon told Ars:

First and foremost, all operating system and security updates to the Pixel devices will happen in partnership with Google. In other words, when Google releases an update, Verizon phones will receive the same update at the same time (much like iOS updates). Verizon will not stand in the way of any major updates and users will get all updates at the same time as Google.

Also, the Verizon version of the Google Pixel is carrier unlocked, so you can use it where ever you like. Finally, we have three apps pre-installed on the phone Go90, My Verizon (which is your account management tool) and Verizon Messages (your messaging app). As you noted, all three can easily be uninstalled by the user.

Google further confirmed that that updates will not be held back by Verizon. Google told Ars:

OS updates and monthly security patches will be updated on all Pixel devices (Verizon and non-Verizon versions) simultaneously.

That's excellent news.

Android 7.1 Developer Preview hits later this month

Today, we're taking the wraps off of Android 7.1 Nougat, the latest version of the platform. You probably saw a sneak peek of it at last week's event. It's an incremental update based on Android 7.0 but includes new features for consumers and developers - from platform Daydream VR support and A/B system updates to app shortcuts and image keyboard support.

The first developer preview will hit later this month.

Verizon Pixels: crapware, locked bootloader, VZW controls updates

Monthly security updates will come from Google (for all models), and system updates will be managed by Verizon for Verizon models, and Google for unlocked models bought from Google Store.

Pixels bought at Best Buy are the Verizon models, so system updates for those, too, will be managed by Verizon. Combined with the news that Verizon models will have a locked bootloader and come with Verizon crapware, it's pretty clear that Americans among us should really, really opt to buy the Pixel outright from the Google Store. Yes, that means higher upfront costs, but you'll have lower monthly expenses, proper updates, and an unlocked bootloader.

Anybody with even an ounce of common sense should avoid Verizon Pixels like the plague.

Sales and support for Google’s Pixels

Tomorrow, Google will unveil two new phones, and for the first time, they won't be Nexus devices. So much has been leaked now that we know pretty much everything there is to know about these Pixel phones. With every Android manufacturer except Samsung in a death spiral, while Samsung's phones are having 'issues', it makes sense for Google to try and assert more control over what used to be the Nexus line. The result will be devices carrying Google's own Pixel brand.

One aspect of the rumours and leaks that caught my attention was this bit:

Making two high-end phones with all the bells and whistles, just as ready for the future as they are today is a step in the right direction. Buying billboards and commercial space during sports events so people know you're doing it is another step. Speculation about having a well-trained support staff that you can reach anytime from anywhere through the phone's settings points to yet another. If Google builds a better mousetrap and makes sure everyone knows they built a better mousetrap, the world may beat a path to their door.

If Google is really going to pursue a serious effort to expand the Nexus (okay, Pixel) appeal beyond us nerds, it's going to need more than billboards in New York. It's going to need these phones to be front and centre with carriers, smartphone stores, and online stores. It's going to need an aggressive marketing campaign to capture the attention of people who would otherwise just opt for an iPhone or Galaxy, and explain to them why they should abandon the two major brands they know.

Most of all, though, Google is going to need a support structure for these phones. For reasons that are still unclear to me, my Nexus 6P is not receiving its monthly security patches anymore, and I have no idea why. Sure, I can figure it out by browsing or posting on XDA or diving deep into my phone's software (and I will), but I'm a nerd, so set those options aside for a moment - where would I go with an issue like this? Who would I contact for help? Can I walk into a Google Store or whatever and get some sanctioned support for this issue?

The answer is - as with anything related to Google and support - a firm and resounding 'no'. If Google really wants to take its Pixel phones to the masses, it's going to need a sales and support structure that goes well beyond store.google.com and XDA.

Android Wear 2.0 Developer Preview 3: Play Store and more

Today we're launching the third developer preview of Android Wear 2.0 with a big new addition: Google Play on Android Wear. The Play Store app makes it easy for users to find and install apps directly on the watch, helping developers like you reach more users.

Okay that's great and all, but where's the release and where are the new watches?

We've gotten tons of great feedback from the developer community about Android Wear 2.0 - thank you! We've decided to continue the preview program into early 2017, at which point the first watches will receive Android Wear 2.0. Please keep the feedback coming by filing bugs or posting in our Android Wear Developers community, and stay tuned for Android Wear Developer Preview 4.

Oh okay. Well, not that it matters for me personally anyway - I'm an early adopter and one of those idiots who bought the first generation Moto 360.

Andromeda, Google’s Chrome OS-Android merger

Update: more confirmation!

With Google's event fast approaching on 4 October, the rumour mill is in full swing. We know we're going to get new 'made by Google' phones, which will drop the Nexus brand in favour of Pixel. However, there's going to be more to watch out for - everything is lining up for 4 October being a major turning point in Android's relatively recent history.

If the rumours are to be believed - and with so many different sources all pointing towards the same thing, you can probably believe them - Google will unveil not just a few new phones, but a new operating system altogether, dubbed Andromeda. And, just like we've been talking about for a long time, this is the operating system that combines Android and Chrome OS into a desktop/laptop operating system.

As 9to5google reports:

Why so many mentions of Nexus 9 specifically in tandem with Andromeda? We asked the same question, and from what we can gather, Google is testing the Chrome OS/Android hybrid on the tablet. An anonymous source has told us of users running early builds of Andromeda on the Nexus 9, but we have not been able to obtain direct confirmation from those users. Why would Google be testing Andromeda on the Nexus 9? We don't know.

But we do know that Andromeda is aimed at making Android better suited for devices like laptops, as well as 2-in-1s (like the unfortunately mediocre Pixel C) and perhaps tablets. Another interesting tidbit to note: it seems that the hidden free form window management feature that popped up in Nougat (but isn't user-facing) could appropriately see its debut with Andromeda. "SurfaceCompositionMeasuringActivity.java" mentions "Detect Andromeda devices by having free-form window management feature."

The fact that Google is working on merging Android and Chrome OS is hardly news, but as more and more details come out, it seems to indeed be the case that Google is working on not just a smartphone operating system or a tablet operating system, but a full-fledged laptop/desktop operating system, complete with the kind of freeform window management we've come to expect from operating systems like MacOS and Windows.

This is further confirmed by AndroidPolice:

Two independent and reliable sources have confirmed to us that Google is planning a new Pixel laptop to be released in Q3 2017. The project, known internally as 'Bison' and by the informal nickname 'Pixel 3,' will likely be the first brand-new device to showcase Google's combined Android / Chrome OS 'Andromeda' operating system in a laptop form factor. Bison, then, would be the culmination of years of work by Google's Pixel team and Google's Android and Chrome OS teams.

We are extremely confident Google plans for the device to run Andromeda. We are also confident that Andromeda is a completely distinct effort from Google's current campaign to bring Android apps to Chromebooks, and that Bison would not be marketed as a Chromebook. Android apps on Chrome OS descended from the ARC project, while Andromeda is a much larger, more ambitious initiative that is being pursued via merging Chrome features into Android, not vice versa. As such, it would be more accurate to say Bison will run Android than Chrome OS, and could finally be Google's internal commitment to releasing Andromeda.

Taking all this into account, a tweet that came out late last week from Hiroshi Lockheimer, SVP of Android, Chrome and Google Play, is quite telling: "We announced the 1st version of Android 8 years ago today. I have a feeling 8 years from now we'll be talking about Oct 4, 2016."

Much like Apple's similar efforts, I'm excited about what's happening on the Android side of things. It's clear by now that Google has very ambitious plans about moving Android forward and scaling it up to work on not just phones and tablets, but on laptops and desktops as well. Up until relatively recently, such endeavours would've been futile, because 'new' operating systems could never challenge the hegemony of Windows and OS X, but in today's world, where more and more especially younger people no longer rely on staples like Microsoft Office, or could get by just fine with the surprisingly good Android and iOS versions of Office, there's an opening for the laptop/desktop world to be shaken up.

Now, a lot of this will, as always, depend on execution. I wouldn't be at all surprised to see Andromeda take a... Less laissez-faire approach to OEM and carrier customisations, and a more Chrome OS-like update policy (which is entirely free from meddling). There's also the question regarding Andromeda's relevance on phones - will it exist alongside 'classic' Android, or will Andromeda replace Android on phones and tablets as well? My guess would be yes - why unite Android and Chrome OS only to end up with another split - but that raises a whole bunch of other questions about possibly docking phones and using them with large screens and other input methods.

I'm ready for 4 October.

Android Wear hopefuls call timeout on smartwatches

Time stands still for some in the smartwatch market.

With Apple set to release "Series 2" of its Watch and Samsung prepping its Gear S3 timepiece, many of the biggest players that have embraced Google's Android Wear software have decided to hit pause on their own efforts.

It seems like only Apple and Samsung are willing - and capable - of propping up what is at best a lukewarm product segment.

One year later: can Android 7.0 Nougat save the Pixel C?

Expecting a company that sells tablets to also provide tablet-oriented interfaces for the OS and major apps isn't unreasonable. But Google hasn't shown it is willing to provide those interfaces. My Android tablet advice still stands - I'll take Android tablets seriously once Google does.

All the interface regressions since Honeycomb still make Android tablets feel like an afterthought. While the Pixel C is a great demonstration of these problems, it's still not a great productivity device compared to the competition.

The side-by-side comparisons between Honeycomb and Nougat are damning. "Regression" isn't an adequate enough word for what's happening here.