Android Archive

Replacing Google with microG

A common criticism of free-software projects built for Android is that they all too often rely not just on the frameworks and libraries that are part of the official Android Open Source Project (AOSP), but on the proprietary APIs implemented in various add-ons from Google - such as the Google Maps API or the Google Cloud Messaging message-broker service. Working around these Google-supplied components is not trivial, but there is at least one effort underway to provide a drop-in free-software replacement: microG.

We talked about microG over two years ago.

Google is actively breaking my Android workflow

Speaking of software sucks, take a look at this screenshot of Chrome for Android. Do you notice something out of the ordinary? While you look, let me give you a little history.

Way back when Android Lollipop was released, Google introduced a feature called "merge tabs and apps" and enabled it by default for all Lollipop users. Basically, what it did was turn individual Chrome tabs into application windows in Android's application switcher. If you have an understanding of how Android works, this makes perfect sense; this turns tabs into full citizens of the Android application and intents workflow.

Starting with - I think? - Android Marshmallow, Google turned the feature off, but kept it as an option in Google Chrome, so that those of us that liked it could turn it back on. Obviously, this was the first thing I always turned on when setting up any new Android device; it just makes sense from an Android perspective. It smooths out the workflow, and makes sure that tab management becomes a thing of the past; they are discarded just like other Android applications.

Sadly, starting with Chrome 51, released a few weeks ago, the Android or Chrome or whatever team decided to remove the option altogether. The release notes stated:

When Android Lollipop was released last year, we moved Chrome tabs to live alongside apps in Android’s Overview app switcher. Our goal was to make it easier for you to switch between your open apps and websites. However, we heard from many of you that you could not find the tabs you created. This was especially difficult on phones that do not have a dedicated Overview button. While considering how to make Chrome work better for everyone, we brought the tab switcher back into Chrome so you can find your Chrome tabs in a single place. Look for a new way to manage your open tabs in coming releases.

This single change has thoroughly ruined the way I use my phone. I now have upwards of 60 - and growing - "open" tabs, because the Chrome team wants me to manually keep track of and close every individual tab that gets opened while using Twitter, Facebook, WhatsApp, and other applications. I now have to keep track of not only running applications in the switcher, but also open tabs in the tab switcher, the latter of which can only be opened with a button in Chrome all the way at the top of my ginormous Nexus 6P display. The tab switcher itself, meanwhile, is a finicky clusterfuck of imprecise swipes and physics nonsense, making it all incredibly frustrating to use.

Update: this paragraph was added later as clarification. In addition, if you tapped on a link in, say, Fenix (Twitter) and read the website in the tab and then pressed back, said tab was automatically closed. This automatic closing of tabs with the back button does not happen with the inferior new method, hence the asinine clutter build-up.

Trying to switch to a specific tab I may have opened earlier in the day is an exercise in frustration now, since instead of just opening the application switcher and finding it a few swipes up (I don't use many applications), I now have to first find Chrome or launch it from my homescreen, find the tab switcher button all the way at the top, count to ten as I try to use the asinine tab switcher, and then hope I can find it somewhere among the more than 60 - and growing - "open" tabs and UI input lag caused by having to render all these tabs in that weird 3D space.

As someone who keeps track of world news, things like UEFA Euro 2016, technology news, and so on, all throughout the day, I end up with countless interesting tabs that get opened on Twitter, other social media, instant messenger, and so on. The Chrome team has actively decided to break my workflow, and there's no way for me to get it back - probably just because instead of looking at the how or why, they just looked at their precious, precious user data, and called it a day.

Looking to the future, with (freeform) windowing coming to Android, the change makes even less sense. Having tabs as part of the regular application switcher surely makes sense from a multitasking and multiwindow perspective, automatically giving Android users the ability to have multiple tabs side-by-side, in a way that is consistent with using other applications side-by-side. How are they going to implement this now? Will Android users have to deal with multiple Chrome windows, each with their own tab switcher? Where do tabs of closed windows go? What madness is this?

I find solace in that I'm not alone. Countless friends have expressed their hatred for the removal of merge tabs and apps (I've seen some of my programmer friends with well north of 100 "open" tabs), and the Chrome for Android reviews in the Play Store are riddled with angry one-star reviews. Google's forums, too, are filled with angry users. I'm hoping the angry comments and one-star reviews will make the Chrome team reconsider and bring back the option to merge tabs and apps, the Only True Android Wayâ„¢ to manage tabs.

I'm sure tons of people here will consider this whining, but imagine if you're a programmer, and someone randomly took away your ability to insert tabs, forcing you to use spaces instead (or vice versa). That twitch you feel? That's us right now, every time we use Android.

For the first time in my life, I actually rated an application on an application store. Guess how many "stars" (why is it always stars?) I gave to Chrome for Android.

“Android’s 10ms problem solved”

Our testing, technical analyses and audio latency measurement database of more than 4,238 different Android models/builds shows that Google has been making great progress in order to solve the Android round-trip audio latency problem, however progress seems to be slowing as the current media server internals are not likely to be hacked much further unless fundamental changes should happen. To date, we have seen no improvements with Android N with regards to audio latency.

We receive emails from all around the world, almost on a daily basis, where developers beg us for a solution to Android Audio's 10 ms Problem. Which is why we're proud to announce a solution to Android Audio 10ms Problem, which you can install and demo today.

Few regular users will ever care, but for those users that do need low audio latency for music/audio creation applications, this is a godsend.

Marshmallow is in use on 10.1% of all Android devices

Google's data shows that Marshmallow actually claimed 10.1% of all Android installs, based on data collected on June 6. The previous Android version, Lollipop, went down slightly from 35.6% in May to 35.4%, but it is still the version of Android with the most installs.

Pathetic.

Are you men and women tired of me bringing this up all the time yet? Yes?

Good. Expect more. Until Google gets its act together, I will keep talking about this.

Google adds Raspberry Pi 3 to AOSP

The Raspberry Pi 3 is not hurting for operating system choices. The tiny ARM computer is supported by several Linux distributions and even has a version of Windows 10 IoT core available. Now, it looks like the Pi is about to get official support for one of the most popular operating systems out there: Android. In Google's Android Open Source Project (AOSP) repository, a new device tree recently popped up for the Raspberry Pi 3.

A great little device for Android on the desktop - where Android is going.

Google’s Project Ara is about more than just modular phones

Ara is going to be the first ever phone that Google is making itself (it has already made laptops and a tablet, among other things). And even though what I saw last week was just a prototype, it was working well enough that I believe Google can fulfill its promise to release a consumer product next year. Yes, we've seen Google kill off hardware before, but this is a high-profile launch from a newly independent division. It's the first truly big swing from Google's new hardware group under Rick Osterloh, and to back off now would be a colossal embarrassment.

Given all that, really the only questions that matter are simple: Is Google really making a phone? Will this plan to make it modular really work this time? Is this more than just an experiment?

Coming out of the meeting, had I shaken a Magic 8 ball, it would have said, "Signs point to yes."

I want this to succeed - finally something new, beyond the square slab - but this is so radical in the smartphone (or feature phone and PDA before that) market that I honestly just don't know if it'll work out.

In any case, people are taking sides, but a this point in time, I think either option - "this will be a massive success" or "this is nonsense" - is equally shortsighted, and especially the latter not at all unlike this infamous quote.

Play Store comes to Chrome OS, but not the way we expected

It's really happening. Android apps are coming to Chrome OS. And it's not just a small subset of apps; the entire Google Play Store is coming to Chrome OS. More than 1.5 million apps will come to a platform that before today was "just a browser," and Android and Chrome OS take yet another step closer together.

In advance of the show, we were able to sit down with members of the Chrome OS team and get a better idea of exactly what Chrome OS users are in for. The goal is an "It just works" solution, with zero effort from developers required to get their Android app up and running. Notifications and in-line replies should all work. Android apps live in native Chrome OS windows, making them look like part of the OS. Chrome OS has picked up some Android tricks too - sharing and intent systems should work fine, even from one type of app or website to another. Google is aiming for a unified, seamless user experience.

Interestingly enough, this project is actually not ARC, the technology Google used before to bring Android applications to Chrome. ARC wasn't good enough for Google, as it still required developers to make changes to their code. In fact - and this is kind of funny - ARC didn't even pass Google's own Compatibility Test Suite Android variants have to comply with. So, they started from scratch, and used containers instead.

The new model dumps the native-client based implementation for an unmodified copy of the Android Framework running in a container. Containers usually bundle an app up with all of its dependencies, like the runtime, libraries, binaries, and anything else the app needs to run. This allows the difference between application environments to be abstracted away. In this case, Google is putting the entire Android Framework into a container, all the way down to the Hardware Abstraction Layer.

I'm hoping Google will eventually bringing Android applications to all variants of Chrome, including the one on Windows.

The explosion of lock screen adware in the Play Store

The once beloved ES File Explorer was revealed recently to be little more than a Trojan Horse, used to get adware installed on thousands of devices with one update. This was apparently just the beginning. Users have started compiling a spreadsheet of apps that sneak the same adware-infused charging lock screen onto your device. There are already about 20 of them. Google, where are you?

Google needs to address this grotesque abuse of its users quickly and decisively, and remove all applications that install this adware from the Play Store, no questions asked. This is in direct violation of the Play Store rules.

Google’s Andy Rubin defends Android to jury

During hours of unrelenting cross-examination today, Andy Rubin, Google's former Android chief, was on the stand in the Oracle v. Google trial defending how he built the mobile OS.

Rubin's testimony began yesterday. He's another one of the star witnesses in this second courtroom showdown between the two software giants in which Oracle has said it will seek up to $9 billion in damages for Google's use of certain Java APIs in the Android operating system. Since an appeals court decided that APIs can be copyrighted, Google's only remaining defense in this case is that its use of those APIs constitutes "fair use."

The "API's are copyrightable"-ruling is one of those rulings we will look back on decades from now and point to as "that's where it all went wrong", much like how we now look back upon disastrous rulings like Citizens United or the slew of bad rulings that legitimised software patents.

And we have the despicable Oracle to thank for that. As I've pointed out before, it's no coincidence that the three-pronged legal attack on Android - from Apple, Microsoft, and Oracle - all started at around the same time, and that Larry Ellison was a very close friend of Steve Jobs.

When all this stuff hits the fan even harder, you know who to thank.

Only 7.5 percent of Android phones are running Marshmallow

Two weeks shy of Google detailing the next big revision of Android at its annual developer conference, the current Android version is still struggling to make its way out to devices. Android 6.0 Marshmallow is currently running on just 7.5 percent of active Android devices that have access to the Google Play Store. The rest of the field is dominated by 2014's Android Lollipop at 35.6 percent, 2013's KitKat at 32.5 percent, and 2012's Jelly Bean at 20.1 percent. 2011's Ice Cream Sandwich still clings on to a stubborn 2 percent and the immortal Android Gingerbread (version 2.3!) accounts for 2.2 percent of Android smartphones.

Using an iPhone 6S since it came out has made me appreciate more and more just how much better Android is than iOS - but it's all for naught if Google doesn't get off its bum and fixes this long-running problem. Now that Android at 6.x is definitively better than iOS, it's way, way, way, way beyond time for Google to drop everything they're doing and somehow find a way to forcefully and resolutely address this deficit.

If the latest version of Android is the best (i.e., the least crappy) mobile operating system out there, but nobody is running it, is it really the best mobile operating system?

Google Play Store headed to Chrome OS

Google first brought the ability to run Android apps on Chrome OS with a project called the "App Runtime for Chrome (ARC)." Google built an Android runtime on Chrome OS and partnered with select developers to port a handful of Android apps. Now it sounds like Google is ready to unleash millions of Android apps onto the platform by bringing the entire Play Store to Chrome OS.

This is great news, because the more exposure Android applications get to the proper desktop world, the more developers will take that into account when developing Android applications. We need these applications to become properly resizable to prepare them for the future of the desktop/laptop Android Google claimed it's working on.

In addition, it makes Chrome OS - which is going to be phased out in the process - a lot more useful.

EU formally lodges Android antitrust complaint

The European Commission has formally lodged an antitrust complaint regarding Android.

The European Commission has informed Google of its preliminary view that the company has, in breach of EU antitrust rules, abused its dominant position by imposing restrictions on Android device manufacturers and mobile network operators.

The Commission's preliminary view is that Google has implemented a strategy on mobile devices to preserve and strengthen its dominance in general internet search. First, the practices mean that Google Search is pre-installed and set as the default, or exclusive, search service on most Android devices sold in Europe. Second, the practices appear to close off ways for rival search engines to access the market, via competing mobile browsers and operating systems. In addition, they also seem to harm consumers by stifling competition and restricting innovation in the wider mobile space.

Google has already responded in a blog post (read the whole thing):

The European Commission has been investigating our approach, and today issued a Statement of Objections, raising questions about its impact on competition. We take these concerns seriously, but we also believe that our business model keeps manufacturers’ costs low and their flexibility high, while giving consumers unprecedented control of their mobile devices. That's how we designed the model.

This EU antitrust complaint is one of the biggest jokes in EU antitrust history; an even bigger joke than the Windows N editions. Not only is Android open source, the operating system has created a vastly more open and consumer- and competition friendly mobile operating system than anything else that has ever existed on the market. The situation before Android was absolutely dreadful - dozens, if not hundreds, of closed little feature phone platforms, the closed-source Windows Mobile, the completely locked-down iOS, the heavily fragmented, obtuse, and effectively locked-down Symbian.

The situation after Android is that any user has a lot of control over the software they run on their phone, with tons of cheap, yet high quality devices to choose from. You can install whatever software you want, from whatever source you want, without having to go through Google or anyone else. Developers can target a vast segment of the market - Android has 80% market share in Europe - without being beholden to the nonsensical whims of a single corporation. In addition, users can run Android on pretty much any phone without any additional Google software or services.

The situation clearly isn't perfect by any means, but the real problems with mobile software are not in Android - or iOS for that matter - but in the baseband processors, firmware, and similar software. Far less sexy, of course, and yet a far bigger problem that needs to be tackled.

This entire antitrust complaint is a complete waste of money and taxpayer resources - which, coincidentally, makes it a very EU thing to do.

Ars HTC 10 review: “HTC builds the best Android flagship of 2016”

The HTC 10 takes the HTC design formula and distills it down to its purest form. There's nothing but excellent smartphone here - no silly gimmicks or odd design decisions. Even the software was treated rather well, with any curiosities relegated to optional parts of the OS that can be turned off or replaced.

HTC really seems to have taken the feedback from the One M9 to heart. The design is much more compact, with less bezel dead space dedicated to speakers and an HTC logo. The SoC is improved by dumping one of the first and hottest Snapdragon 810 implementations for the cooler, faster 820. The ugly side ridge design of the M9 is gone. The camera is a lot better, too, particularly when it comes to low light.

I have a soft spot for HTC, but with Nexus phones being the Android enthusiasts' phones, and with Samsung taking everything else, it's going to be hard for them to sit somewhere in the middle. People who buy Samsung aren't going to suddenly buy an HTC, and toned-down Sense or no, this is still not Android-proper, so updates will be a mess (it's already running outdated software), so enthusiasts won't really be enticed either.

I'm not really sure where HTC's smartphone business is going.

Android Studio 2.0 released

Android Studio 2.0 is the fastest way to build high quality, performant apps for the Android platform, including phones and tablets, Android Auto, Android Wear, and Android TV. As the official IDE from Google, Android Studio includes everything you need to build an app, including a code editor, code analysis tools, emulators and more. This new and stable version of Android Studio has fast build speeds and a fast emulator with support for the latest Android version and Google Play Services.

This is Android N’s freeform window mode

We'll get to the instructions, but first let's talk about what's actually here. Freeform Window Mode is just what we imagined. It's a dead ringer for Remix OS - multiple Android apps floating around inside windows - and might be the beginnings of a desktop operating system. It works on Android N phones and tablets, and once the mode is enabled, you'll see an extra button on thumbnails in the Recent Apps screen. To the right of the "X" button that pops up after a second or two, there will be a square shape - the same ugly placeholder art Google used for the split screen mode in the Android M Developer Preview.

Press the square symbol for an app and you'll be whisked away to a screen showing that app in a floating window that sits on top of your home screen wallpaper. The windows aren't floating above the Android desktop; it's just a blank wallpaper without any of your icons or widgets. The floating apps all have title bars like in Recent Apps. You can drag the apps around by the title bars or use the close and maximize buttons. Apps can be resized exactly how you would expect - press or hold on the edge of and all and move your finger, and you'll see the app change shape. Just like in split screen mode, apps will auto-switch between their tablet and phone layouts (with some apps dealing with this better than others). You can only resize in one direction at a time though; there doesn't seem to be a corner hotspot that will let you adjust the width and height.

It's honestly kind of amazing that we get to see both Apple and Google work on scaling up their mobile operating systems for desktop use, with the eventual end goal of replacing Chrome OS and OS X (get used to it, people - OS X is on its way out), and unify everything from desktop, to laptop, to tablet, to phone, in a single user interface that scales from top to bottom.

It's what Microsoft tried to do by scaling down, which honestly didn't pan out very well. We'll see if scaling up is a better approach, but exciting and interesting as it is to see this take shape before our very eyes, I still have my considerable doubts.

Google releases Android N developer preview with multiwindow

Just a random Wednesday in March, and Google releases the first Android N developer preview. The biggest new feature in this Android N developer preview is, as Google promised, multiwindow.

Multi-window - A new manifest attribute called android:resizableActivity is available for apps targeting N and beyond. If this attribute is set to true, your activity can be launched in split-screen modes on phones and tablets. You can also specify your activity's minimum allowable dimensions, preventing users from making the activity window smaller than that size. Lifecycle changes for multi-window are similar to switching from landscape to portrait mode: your activity can handle the configuration change itself, or it can allow the system to stop the activity and recreate it with the new dimensions. In addition, activities can also go into picture-in-picture mode on devices like TVs, and is a great feature for apps that play video; be sure to set android:supportsPictureInPicture to true to take advantage of this.

As you can see in the video The Verge has up, the multiwindow feature is fairly straightforward, and it looks quite smooth considering it's a beta - see the video on The Verge, or this one for a tablet view. Unlike iOS, the feature is not restricted to just certain tablets; multiwindow on Android N is available on both phones and tablets, in landscape and in portrait.

There's a number of other new features as well, such as improvements to the power-saving Doze feature, notification grouping (finally!), direct replies to notifications, several Java 8 language features, and more. Digging a little deeper into the changes, there's an interesting tidbit about future releases possibly bringing an end to unbound background services.

You can install the Android N developer preview on a Nexus 5X, 6, 6P, 9, 9G, Player, and the Pixel C. You can also enroll your device in Android's new beta program, allowing you to upgrade your device using over-the-air updates, so you don't lose all your data. This program will go live later today.

Cyanogen introduces MODs

As mods, 3rd party applications that were previously isolated can now take advantage of platform APIs to implement unique experiences directly within Cyanogen OS. Users can install a variety of mods to extend the functionality of their devices. For example, through Cyanogen's partnership with Microsoft, a user can install the Skype mod directly into their dialer to add VoIP calling functionality or they can install the Cortana personal assistant mod to power features like voice-activated selfies.

Cyanogen OS, which isn't CyanogenMod, is introducing MODs, that plug into Cyanogen OS and CyanogenMod. At this point, they are intentionally muddying the waters, right? This is the system Microsoft is using to integrate its services into Android, and now, everybody can use them. The wording here is a bit strange, though, because one of the core strengths of Android is that applications are not isolated, unlike on iOS, where every application looks, feels, and functions like an island.

It's all pretty nifty, and all made possible because of two things: first, Android in and of itself is incredibly extensible, and it contains a ton of APIs for these sorts of things. A lot of this integration can be achieved simply by installing applications from Google Play. Second, it's made possible because Android is open source, so that Cyanogen can make a few changes and claim they're taking Android away from big, bad Google who is giving them Android in the first place, and without whom Cyanogen wouldn't exist, or wouldn't continue to exist.

In any case, let's see if other 3rd parties are going to adopt this. It seems like Android as-is is extensible enough, so I don't see much life in this for most developers and users.

Samsung, LG announce new flagship phones

Both Samsung and LG announced their new flagship phones for the year, and lo and behold, there's actually something interesting to discuss. First, let's get the new Galaxy S7 and Galaxy S7 Edge out of the way: even though they look very similar to the S6 and S6 Edge, Samsung has brought back a few things that many here will like: water resistance, and a microSD card slot. In addition, Samsung has revolutionised the smartphone industry by making the S7 and S7 edge slightly thicker to fit a much, much bigger battery and to reduce the camera hump.

The new LG G5 is more interesting. The phone is, of course, kitted with all the latest processors and RAM and whatever, but at the bottom of the device, there's a slot that you can use to snap on all kinds of additional hardware.

Two of these new accessories plug directly into the LG G5's bottom. A small key on the side of the phone pops open its lower section, which can be pulled out along with the battery, then the battery is fitted into the next module and that straps back into the phone. The whole process sounds finicky, but there's nothing flimsy about the way LG has constructed either the phone, its battery, or the extras, so everything can be done quickly and forcefully. And yes, it really does feel like loading a fresh clip into your gun.

If this reminds you of Handspring's Springboard, you're not alone. As with virtually everything in mobile today - everything can be traced right back to Palm.

In any event, as much as I personally always like these kinds of experiments, the problem is that generally, nobody ever builds anything worthwhile for it. These expansion slots always tend to kind of fizzle out, with few actually, really good accessories to ever be released. Which, in turn, raises the question of why you would invest in it in the first pace.

That being said, let's give it a year or so and see what LG and possible third parties are going to do with this. I like the G5 overall, and the expansion slot is a fun and gutsy move (the fact that it is tells you a lot about the state of the industry, sadly).

As always, be careful with these phones if you care about running the latest Android: flagships or no, updates for these things will be messy.

Remix Mini wants your next PC to be Android

After initially thinking this would be great for people who want to do some of the stuff usually done on PC without the expense, now I'm not so sure who it suits. It fits only very simple work, ideally just in the browser or in Google apps; it's not enjoyable or smooth enough for leisure time use; for viewing content you'd be better off with a set-top box; and you can just plain forget playing games on it.

The Remix Mini has its appeals and uses only for pretty basic work. But as it is, here and now, it's not the post-Windows solution that some of us are looking for.

I applaud what Jide is trying to do, but at this point, with Google having openly stated they are working on bringing Android to the desktop, and giving it proper multi-window and all other features that come with it, I see little to no reason to invest too much into these products.

Google rolling out Marshmallow for Android Wear

Evidence has been mounting over the last few days and it looks like it's finally happening: Android 6.0 for Wear is starting to roll out. Googler Wayne Piekarski just announced on his Google+ feed that OTAs have begun and should continue over the next few weeks.

An official blog post by Google lists some of the new features we can expect in the new firmware, including: newly navigation gestures, audio support on speaker-equipped watches, and expanded support for messaging clients.

The update itself seems a bit 'eh', but the interesting thing here is that all Android Wear devices will be getting this update to Marshmallow, even the first generation Wear smartwatches.

Goes to show that Google does, in fact, know how to do this - now they just need to apply this to phones and tablets.