Android Archive

Maybe Android tablet apps will be better this year

There's a new Android tablet you can go and buy, the Samsung Galaxy Tab S3. Here's our review of it, where Jake notes that apps freeze if they're not in the foreground. Which is a good reminder: Android apps on tablets have never really been very good. They usually end up feeling like stretched-out phone apps.

Things have gotten better in the past couple years, but it's still a problem. In fact, it has always been a problem. I wonder if anybody ever told Google that it was a problem and it should try to do a better job incentivizing developers to make apps that work better on tablets.

Oh, wait, somebody has.

Brutal, but true.

Devil's advocate take: since tablets don't matter, do tablet apps really matter?

Google releases Android O Developer Preview

Google has released the first Developer Preview for Android O, which is probably going to be released somewhere in the Fall. There's a lot changes in this one, but the biggest one is probably the limits Android O is going to place on applications running in the background.

Building on the work we began in Nougat, Android O puts a big priority on improving a user's battery life and the device's interactive performance. To make this possible, we've put additional automatic limits on what apps can do in the background, in three main areas: implicit broadcasts, background services, and location updates. These changes will make it easier to create apps that have minimal impact on a user's device and battery. Background limits represent a significant change in Android, so we want every developer to get familiar with them. Check out the documentation on background execution limits and background location limits for details.

There's more - improvements in keyboard navigation, Navigation Channels for managing notifications, picture-in-picture on smartphones, wide-gamut colour support for applications, several new Java 8 features, and more. A big one for audio people: Sony has contributed a lot of work to audio in Android O, adding the LDAC wireless audio codec.

It's available on the usual Nexus devices.

Android Studio 2.3 released

Android Studio 2.3 has been released.

We are most excited about the quality improvements in Android Studio 2.3 but you will find a small set of new features in this release that integrate into each phase of your development flow. When designing your app, take advantage of the updated WebP support for your app images plus check out the updated ConstraintLayout library support and widget palette in the Layout Editor. As you are developing, Android Studio has a new App Link Assistant which helps you build and have a consolidated view of your URIs in your app. While building and deploying your app, use the updated run buttons for a more intuitive and reliable Instant Run experience. Lastly, while testing your app with the Android Emulator, you now have proper copy & paste text support.

I hear a lot of negativity regarding Android Studio, but since I'm not a developer, I can't really make heads or tails of it. Is it really as bad as some people make it out to be?

BlackBerry KEYone released

One other phone I want to highlight out of MWC in Barcelona: a new BlackBerry Android phone! With a proper hardware keyboard! The BlackBerry Priv from 2015 suffered from some performance issues, so I hope they get it right this time.

Now that the BlackBerry KEYone is official, that means the full run down of specs are available now as well. For the KEYone, every component of the device, including the Snapdragon 625 was specifically chosen with the goal of lengthening the battery life in mind. Mind you, the battery itself is the largest ever put in a BlackBerry, (3505 mAh) so we're already off to a great start.

It looks nice, too. Very intrigued by this phone.

Android Wear 2.0 review: Google’s second swing at smartwatches

Android Wear 2.0 is also buggier than it should be, especially given the fact that it had an extended public beta period and its launch was delayed by months. Beyond them taking a long time to launch, it can be hard to tell when an app is actually launching, because the screen will flicker back to the list of apps before it will launch the one you just tapped. The Google Assistant also crashed often, forcing me to repeat my inquiry multiple times (or more likely, I just get frustrated with it and pull out my phone).

The changes and improvements look decent, but if you don't first get the above things right, they're all for naught. When will software makers learn that performance - especially UI responsiveness - is the single most important part of a consumer-oriented device?

Not that it matters to me - for some mysterious reason, these new watches won't be coming to The Netherlands. They're coming to the rest of Europe - just not The Netherlands. The Google Pixel is also still pretty much sold out in the two or three countries where it's supposedly available, with no indication they're ever going to be available elsewhere.

Here's a tip, Google: if you want to be a successful hardware maker, maybe make sure interested consumers can actually, you know, buy your stuff?

Chrome OS tablets with Android apps are coming soon

So if you've been wondering where all the Android tablets have gone - here's a guess. They've been held back because it seems like something better is coming: Chrome OS tablets with a real desktop browser and real Android apps. That kind of system probably has a better chance of success competing with the iPad - but let's not set Android's sights quite that high yet. A more reasonable target: undercutting the Surface and all its clones on the low end of the market.

At this point I have absolutely no clue anymore what Google wants to do with Chrome OS and Android.

And sometimes I think - neither does Google.

Android Wear 2.0 reportedly coming 9 February on 2 LG watches

The next version of Google's smartwatch operating system is slated to arrive on February 9th, according to mobile reporter Evan Blass. The leak follows last week's report that Google had notified developers of Android Wear 2.0's upcoming release so they could prepare to update apps for continued support.

I'm sure all three Android Wear users are jumping up and down with excitement.

Nokia’s first Android smartphone is now official in China

In terms of hardware, the Nokia 6 offers a 5.5-inch Full HD display with 2.5D curved glass, Snapdragon 430 SoC, 4GB of RAM, 64GB storage, microSD slot, dual-SIM connectivity, 16MP camera at the back with PDAF, Dolby Atmos sound with stereo speakers, Bluetooth 4.1, LTE, 3000mAh battery, and a fingerprint sensor. The phone runs Android 7.0 Nougat out of the box.

Not exactly the most exciting phone.

TCL introduces a QWERTY Android-powered BlackBerry

Ahead of CES 2017, TCL teased that they would be offering a look at the first device to come out of their smartphone software and brand licensing deal with BlackBerry and they've now made good on that, though, they're keeping a lot of the finer details surrounding the phone secret for just a bit longer.

It runs Android, and it's got a keyboard. What more do you need to know? The world needs more of these types of phones.

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.