Android Archive

Android Wear smartwatches come to the iPhone

That's right: beginning today, a select set of Android Wear smartwatches (and all future watches) will work with the iPhone. The app should be rolling out worldwide soon. It’s been a long time coming - and it means that Google will be challenging the Apple Watch on its home turf. Those Android Wear watches will be both cheaper and more varied than the Apple Watch - just like Android itself.

Despite Google's claims to the contrary, though, older Wear devices seem to work just fine - reports are coming in for the Moto 360 and LG G Watch also working with the iPhone application just fine.

Your new phone will have less Google bloatware

Recent changes to the rules phone makers need to follow to get a Google approved version of Android have allowed for certain apps to no longer be mandatory. Google Play Games, Google Play Books, Google+ and Google Newsstand now join the ranks with Google Earth and Google Keep as apps that aren't a required part of the Google applications package. They are still in the Play Store, are still regularly updated and will work just as well for those of us who want them. And this is how things ought to be. In fact, we'd like to see even more Google apps get sent packing, but still be there in the Play store for those who want them.

Good. The less crapware - even stock crapware - on our phones, the better. I hope Apple follows in Google's footsteps, because iOS is accumulating a seizable amount of crapware too.

Leaked render shows off BlackBerry Android slider keyboard

Out of all the BlackBerry 'Venice' slider leaks thus far, none have really given us a full look at the keyboard on the upcoming device and that, of course, has left some folks skeptical of everything we've seen recently. Looking to end some of those doubts, @evleaks, has now posted up a follow-up to the first leaked render of the device that clearly shows off that glorious BlackBerry keyboard.

Instant buy if this comes out in time for my contract renewal in October. Finally a modern Android device with a hardware keyboard.

OnePlus 2 reviews

What does it mean to use a flagship smartphone in 2015? It likely means that you're using a phone with a great display, fast performance, good battery life, good build quality, and a great camera. If I'm being honest, I have to say that the OnePlus 2 doesn't hit all of those marks, but it hits most of them and does so at a price that's just over half that of a comparable iPhone. It's not a flagship killer by any means - this year or next - but it's a really solid smartphone that does most everything you need it to do really well. It's easily the best deal on the market right now if you want a high-end smartphone.

AndroidCentral has another review of the OnePlus 2. Looks like a great phone for the price, but with some small issues.

Android M is 6.0 and Marshmallow

Whether you like them straight out of the bag, roasted to a golden brown exterior with a molten center, or in fluff form, who doesn't like marshmallows? We definitely like them! Since the launch of the M Developer Preview at Google I/O in May, we've enjoyed all of your participation and feedback. Today with the final Developer Preview update, we're introducing the official Android 6.0 SDK and opening Google Play for publishing your apps that target the new API level 23 in Android Marshmallow.

Think twice before flashing this third Android 6.0 developer preview - you'll need to reflash to a factory image once the final version is released.

Google brings Vulkan to Android

In order to address some of the sources of CPU overhead and provide developers with more explicit control over rendering, w've been working to bring a new 3D rendering API, Vulkan, to Android. Like OpenGL ES, Vulkan is an open standard for 3D graphics and rendering maintained by Khronos. Vulkan is being designed from the ground up to minimize CPU overhead in the driver, and allow your application to control GPU operation more directly. Vulkan also enables better parallelization by allowing multiple threads to perform work such as command buffer construction at once.

How the Stagefright bug changed Android security

It's been 10 days since Zimperium's Joshua Drake revealed a new Android vulnerability called Stagefright - and Android is just starting to recover. The bug allows an attacker to remotely execute code through a phony multimedia text message, in many cases without the user even seeing the message itself. Google has had months to write a patch and already had one ready when the bug was announced, but as expected, getting the patch through manufacturers and carriers was complicated and difficult.

But then, something unexpected happened: the much-maligned Android update system started to work. Samsung, HTC, LG, Sony and Android One have already announced pending patches for the bug, along with a device-specific patch for the Alcatel Idol 3. In Samsung's case, the shift has kicked off an aggressive new security policy that will deploy patches month by month, an example that's expected to inspire other manufacturers to follow suit. Stagefright seems to have scared manufacturers and carriers into action, and as it turns out, this fragmented ecosystem still has lots of ways to protect itself.

Seeing is believing, but the signs are at least somewhat positive. I doubt all of these will get the fix, though.

That being said, as the linked article explains, this bug really isn't as worrisome as people made it out to be. Security researchers (often working for companies selling security software) have cried wolf so many times I really don't take any of them seriously at this point, no matter which operating system's users they are trying to scare into buying their crap.

Lollipop now on 18.1 percent of Android devices

After skipping the month of July, Google is back in August with the latest distribution numbers for each version of Android. The numbers show that Android Lollipop is now on 18.1 percent of devices, making the jump from 12.4 percent when distribution numbers were last reported in June. Interestingly, KitKat is now on 39.3 percent, marking a tiny increase from 39.2 percent when numbers were last reported. Jelly Bean took a slight dive, making up 33.6 percent of installs, down from 37.4 percent in June.

I always find these distribution numbers depressing.

OnePlus 2 pushes boundaries of how cheap a flagship phone can be

From a specs perspective, the OnePlus 2 features a 5.5-inch, 1080p screen, a Qualcomm Snapdragon 810 processor, and either 16GB of storage with 3GB of RAM or 64GB of storage with 4GB of RAM. The back-facing camera has a 13-megapixel sensor with optical image stabilization, while the front camera lets you shoot selfies at 5 megapixels. That back camera also includes a two-tone flash and a laser focusing system. While most of these specs are pretty standard fare for a high-end smartphone, the price remains anything but: the 16GB model will retail for $329, while the 64GB version will go for $389. That's more than last year's model, but after spending some time with the phone, I feel like the price increase is justified for what you get.

This phone's got some standout features I really like - aside from its price - such as a hardware switch on the side to cycle between the three default notification settings in Android Lollipop (all, priority, and none), similar to the hardware switch every iPhone has had since day one. I've always wondered why Android phones never included this incredibly useful feature. The software is very close to stock, so it's got that going for it as well. There's downsides too - it's still not truly stock, so yeah, expect update problems. It'll only be sold - again - through a silly invite system, and it lacks NFC and an SD card slot.

This is very close to what the Nexus 6 should have been, or what the next Nexus should be.

Ars’ Android Auto review

Ars Technica has a review of Android Auto.

While we love the interface, we just wish there was more of it. Android Auto only covers a subset of the things you would want to do on an infotainment system. The result is an interface that - depending on what you want to do - will have you bouncing back and forth between two different interfaces. It's almost like installing Windows 8 in your car - you've got one modern, incomplete interface paired with a more comprehensive legacy interface. Android Auto can't control the AM/FM radio, CD player, or satellite radio. You also can't adjust the screen brightness, pair a device with the car, or mess with any other settings. Every time you start the car, it launches the ugly stock infotainment system, and you've got to plug your phone in and hit the Android Auto icon. Expect to switch from the beautiful-but-limited Android Auto interface to the slow, chuggy, tasteless OEM interface a lot.

Can anyone with knowledge on the matter explain to me why, exactly, car manufacturers have such outdated, crappy in-car software? And why, even when we have something like Android Auto that could power everything, do they insist on only letting it do a subset, dumping you back to their own crap software for everything else? Why is the car itself running Gingerbread (yes, Gingerbread!)?

Why are they so incompetent?

Sony’s ‘Android concept’ to preview what’s to come

Got an Xperia Z3 and a home address somewhere in the Kingdom of Sweden? Sony wants your help with testing its next round of software updates for Android, which the company has rounded up in an initiative it's calling "Android concept." The goal, says Sony, is to develop new software "from the ground up," meaning no additional Google Play apps like YouTube on the test build, just the core Google communications software and Sony's stack of custom apps like Camera, Music, and Xperia Lounge.

Yet another random, disparate, limited, little, and utterly insignificant 'effort' to merely test bringing regular updates to Android devices. This is pointless. This is not what Android needs. At all.

Android needs Google to step up and reign its OEMs in.

Commodore PET Returns: as a Phone

If the name "Commodore" conjures up images of clicking keyboards, beige boxes, and blinking command lines rather than buttery smooth ballads, this one's for you. Yes, that mainstay of '80s home computing is back, this time as a mobile phone. The Commodore PET--which shares its name with the iconic all-in-one computer released in 1977--might not run Commodore BASIC, but it does feature a customised version of Android 5.0 Lollipop, a 5.5-inch 1080p IPS display, and a pair of emulators for running old Commodore software. Update: It's not quite as stylish as the Macintosh phone.

Is this BlackBerry’s upcoming Android phone?

From The Verge:

We've expected for a month or so that BlackBerry is working on an Android phone with a "dual curved display" that slides up to reveal a physical keyboard underneath. It is supposedly based on a device that was originally announced at Mobile World Congress back in March, and back then the best image we had to go off of was a low-resolution snapshot of the device being held up on stage. Now, Evan Blass (aka @evleaks) has posted a high-resolution render of the device, codenamed Venice, to Twitter.

If this is for real, and BlackBerry doesn't mess it up by tying it to carriers and making it very hard for normal people to buy it, this is my next phone. Finally a modern phone with a keyboard.

Why is Android still the second platform developers work on?

Every year we see the same promise: this is the year that Android-first development will become a reality. At the same time we see big companies like Instagram repeatedly introduce new apps that are iOS-only. Android has been able to tout more market share than iOS for quite some time, but that doesn't seem to have translated into app developers releasing Android apps at the same time as their iOS counterparts, much less Android-first. Over the past few weeks I've been talking with developers and researching why this is still the case.

A major reason not discussed in this article: the large companies - Twitter, Facebook, etc. - as well as the major technology press outlets, are all US-based, and clearly have a very US-centric view of the world (or maybe at the very least an Anglo-Saxon view). In the US, iOS and Android both sit at around ~45% market share, so it makes sense that developers working for these companies focus on iOS more than on Android, simply because iOS development tends to be an easier experience (I'm simply echoing what I hear from developers on both sides of the aisle). The same applies to the technology press.

Outside of the English-speaking countries, however, Android reigns supreme. If these companies had a more world-centric view, their Android efforts would surely improve - because as it stands right now, most major companies' Android applications lag behind their iOS counterparts considerably. Over here in The Netherlands, though, every major new local application - banks, brands, stores, etc. - are always iOS+Android on day one.

It'd be great if American companies finally started getting their acts together too. Don't assume that veteran iOS developers are automatically also good Android developers (they're not), and hire real, proper Android developers. I translate English to Dutch, and my clients would never ask me to translate, I don't know, Spanish documents into Dutch. Small indie Android developers have proven that, even if it may be a little harder, it's perfectly possible to create Android applications that are just as good as, and often even better, than their iOS counterparts.

In 2015, there's no excuse for releasing lousy, crappy Android applications. You only have yourself to blame.

The genius of Google Play Services

If you pay close enough attention to these things, you've probably seen Google Play Services updating from time to time on your Android devices. If you follow the more technical side of Android, you'll know it was announced a couple of years ago to introduce new APIs and features in a way that doesn't require a firmware update. You could be forgiven for dismissing it as a dry and technical part of the OS, but in reality it's a crucially important part of the way modern Android works.

Play Services is a blessing and a curse. It's a blessing because it makes the lives of developers easier and because it bypasses incompetent carriers and OEMs so that users get considerable updates. It's a curse because they're closed source - making it impossible to dig into the code. They make your device less your device, and that's always a bad thing, especially in today's world.

So much of this could be addressed if Google opened up as much of it, but that's very unlikely to happen.

BlackBerry ‘Prague’ the first Android-powered device?

There's been a lot of chatter lately about BlackBerry working on a device running Android, and at first, the rumour was that the portrait slider - yes, with a keyboard - the company briefly flashed before our eyes early this year was going to run Android. I got excited over this one, because I've been wanting a modern smartphone with a keyboard for a long time now. The Passport is a good example, but it's quite expensive for entry into a platform with dubious longevity (I did actually try to buy one when I was in Canada late last year, but Canadian stores were afraid of my money). So, the prospect of an Android slider from BlackBerry surely had my wallet rumbling.

Too bad. A new rumour today suggests that while BlackBerry is indeed working on an Android device, it's not the slider device, but a lower-end, Android One-like device. Still interesting, of course, but not nearly as interest-piquing as a device with a hardware keyboard.

Assuming the rumours don't change tomorrow, those of us hoping for a modern Android smartphone with a hardware keyboard will have to wait a little longer.

The more things change, the more they stay the same

When Android Wear came out over the course of last year, Google promised that the young, new platform would receive updates "early and often". While it wasn't said with so many words, it's easy to read between the lines: Google was going to make sure Android Wear users wouldn't face the same headaches as Android users when it comes to updates. Wear would be a more tightly controlled platform, built in such a way that updates could go straight to users' devices without meddling from carriers or roadblocks thrown up by crappy customisations.

Fast forward to June 2015, and Google has recently released Android Wear 5.1.1, which, despite its humble version number increase over 5.0.1, is a pretty significant update to the smartwatch platform. It enables WiFi on devices that support it, adds new ways to interact with your watch, and makes it easier to launch applications. All in all, it looks like a great update.

Sadly, I can only go by what others have told me, despite owning the poster Android Wear device - the Moto 360.