Android Archive

With the launch of Android 8.0 last year, Google released Project Treble into the world. Treble was one of Android's biggest engineering projects ever, modularizing the Android operating system away from the hardware and greatly reducing the amount of work needed to update a device. The goal here is nothing short of fixing Android's continual fragmentation problem, and now, six months later, it seems like the plan is actually working.

In the past, device makers have focused on safeguarding these keys by storing the keys in secure locations and severely restricting the number of people who have access to them. That's good, but it leaves those people open to attack by coercion or social engineering. That's risky for the employees personally, and we believe it creates too much risk for user data.

To mitigate these risks, Google Pixel 2 devices implement insider attack resistance in the tamper-resistant hardware security module that guards the encryption keys for user data. This helps prevent an attacker who manages to produce properly signed malicious firmware from installing it on the security module in a lost or stolen device without the user's cooperation. Specifically, it is not possible to upgrade the firmware that checks the user's password unless you present the correct user password. There is a way to "force" an upgrade, for example when a returned device is refurbished for resale, but forcing it wipes the secrets used to decrypt the user's data, effectively destroying it.

Big news for those of you who have NVIDIA Shield TV - which, by the way, is the only Android TV box you should consider right now. The Android 8.0 Oreo update (which brings it up to the latest major version of Android) is available starting today.

This'll bring along a major update to the user interface. You'll get new sections along the left side of the screen, with your favorite apps (customizable, of course), play next (where what you've been watching and playing recently will appear) and channels (which is what apps are now called, sort of).

In addition, Amazon Prime Video will get a major refresh, Plex Media Service is improved, and a whole bunch more.

Instead, the problem with the gestures in the current iteration of the Android P beta is one that is sadly familiar to Android users: jank. That's the technical term (no really) that Google itself uses to describe the behavior of the System UI on this beta. "Jank" is usually translated as weird jitters, effects, and scrolling behavior.

I trust that much of that will be resolved in later iterations of the software, but I'm frankly terrified that the subtler issues won't be. I'm speaking about the basic feel of moving elements around on the screen. It needs to be as close to perfect as possible - as good as it is on the iPhone X in my opinion - otherwise that sense of "jank" is going to permeate everything.

We just got a look at the upcoming RED Hydrogen One smartphone at an event meant for "RED Pioneers" (read: superfans). It is, without a doubt, one of the most ambitious smartphones in years from a company not named Apple, Google, or Samsung. It's an Android phone with a 5.7-inch display and top-tier phone specs, but that description doesn't do justice to what RED is trying to accomplish here.

The company better known for high-end 4K cameras with names like "Weapon" and "Epic-w" isn't entering the smartphone game simply to sell you a better Android phone (though it does have both Verizon and AT&T signed on to support it). No, this phone is meant to be one piece of a modular system of cameras and other media creation equipment - the company claims it will be "the foundation of a future multi-dimensional media system".

Among all the new additions to Android P including new navigation gestures, Slices API, and new biometrics API, there are some other changes which may also be impactful in a more subtle way. One of these is the removal of App Not Responding (ANR) dialogue boxes for foreground apps. The ANR dialogue appears when something is preventing the main UI thread from responding. When this happens in Android Oreo or below, the ANR dialogue is shown to the user to let them know. Now, in Android P, the application will just crash without any kind of notification for the user.

Updates are easily the biggest problem facing the Android ecosystem, and Google is working hard to fix that. Project Treble has proven that it's capable of making updates easier, and now Google is stepping up requirements for OEMs when it comes to security patches.

Ten years ago, when we launched the first Android phone - the T-Mobile G1 - it was with a simple but bold idea: to build a mobile platform that's free and open to everyone. Today, that idea is thriving - billions of people around the world rely on their Android phone every day.

To make Android smarter and easier to use than ever, today we're unveiling a beta version of Android P, the next release of Android.

App Actions, for instance, help you get to your next task more quickly by predicting what you want to do next. Say you connect your headphones to your device, Android will surface an action to resume your favorite Spotify playlist. Actions show up throughout Android in places like the Launcher, Smart Text Selection, the Play Store, the Google Search app and the Assistant.

Actions are a simple but powerful way for helping you get what you need quickly; but what if we could surface part of the app itself, right when you need it most? Slices do just that, giving you an even deeper look into your favorite apps. If you search for "Lyft" in Google Search, you can see an interactive Slice that gives you the price and time for a trip to work, and it’s interactive so you can quickly order the ride.

We're taking this leak with a grain of salt: it's either a perfectly executed set of Photoshopped images (along with very accurate timestamps) or the real deal. Supposing that it's real, Gabriel Bryne, whom I can't find anything tangible about, has somehow managed to get his hands on the Android P DP2 beta and installed it on his Pixel. He then did what any sensible man with a super secret Android release would do and took a bunch of screenshots and images of the interface.

Android Things is Google's managed OS that enables you to build and maintain Internet of Things devices at scale. We provide a robust platform that does the heavy lifting with certified hardware, rich developer APIs, and secure managed software updates using Google's back-end infrastructure, so you can focus on building your product.

After a developer preview with over 100,000 SDK downloads, we're releasing Android Things 1.0 to developers today with long-term support for production devices. Developer feedback and engagement has been critical in our journey towards 1.0, and we are grateful to the over 10,000 developers who have provided us feedback through the issue tracker, at workshop events, and through our Google+ community.

Sharing from one app to another has been a mainstay of Android for years and years. It was one of the features that first drew me to Android: no more copying and pasting, no more having to open Twitter or WhatsApp to send a picture I just saw in my Gallery. Apps could talk to each other and the experience felt more cohesive and seamless.

But with time, the Share UI in Android has languished, stuck with the same features and same problems. It switched from a vertical list to a horizontal one, it added direct share in Android 6.0 and app pinning in Android 7.0, yet these felt like putting lipstick on a pig: the Share UI remains slow, bloated, convoluted, and if you pay close attention to it, one of the most inconsistent experiences on Android to date. Android P, like Oreo before it, appears to bring no improvements to the Share interface, but that's a big oversight in our opinion. It's high time Google gave it the attention it deserved and fixed its many issues.

I’ve been a professional Free Software developer in the GNU/Linux area for 14 years now, and a hobbyist developer and user for much longer. For some reason that never extended much to the smartphone world, beyond running LineageOS on my older phones (my current Sony Xperia is still under warranty and I’m fine with the officially supported Android), and various stabs at using the Ubuntu phone (RIP!).

On a few long weekends this year it got a hold of me, and I had a look over the Google fence to see how Free Software is doing on Android and how to reduce my dependency on Google Play Services and Google apps. Less because I would actually severely distrust Google, as they have a lot of business and goodwill to lose if they ever majorly screw up; but more because of simple curiosity and for learning new things. I want to note down my experience here for sharing and discussing.

I started experimenting on my old Nexus 4 by completely blanking it and installing current LineageOS 14.1 without the Google apps. This provides a nice testing ground that is completely free of any proprietary Google stuff. From that I can apply good solutions on my "production" Xperia.

The best thing about Android Go is that it doesn't force anything on users. If you're like me and find Google Maps Go to be nearly useless, you are totally free to download the full version of Google Maps. Because of this, Android Go is never an "inferior" version of Android. In the current builds, at least, it's purely a lighter, less resource-intensive version of Android. If you can't stand the functionality reduction, you can easily fix it by downloading the full versions of apps.

However scattershot the overall package seems, Android Go does succeed in lowering the bar for what it takes to run Android. It's certainly more useful than something like Firefox OS or Tizen. Hardware this is cheap still doesn't result in a user experience I can call "good" though. If you can afford something better, spend the extra money.

top-tier Android phone can cost upwards of a thousand dollars, and for that money, you'll get some amazing features. It will have a stellar screen, top-flight camera, gobs of storage, and an absolutely atrocious texting experience.

Now, the company is doing something different. Instead of bringing a better app to the table, it's trying to change the rules of the texting game, on a global scale. Google has been quietly corralling every major cellphone carrier on the planet into adopting technology to replace SMS. It's going to be called "Chat", and it's based on a standard called the "Universal Profile for Rich Communication Services". SMS is the default that everybody has to fall back to, and so Google's goal is to make that default texting experience on an Android phone as good as other modern messaging apps.

But remember, Chat is a carrier-based service, not a Google service. It's just "Chat", not "Google Chat". In a sign of its strategic importance to Google, the company has spearheaded development on the new standard, so that every carrier's Chat services will be interoperable. But, like SMS, Chat won't be end-to-end encrypted, and it will follow the same legal intercept standards. In other words: it won't be as secure as iMessage or Signal.

If you're still trying to wrap your head around the idea that Google won't have a standalone consumer chat app, well, so am I. "The fundamental thesis behind the RCS protocol is it's a carrier service," Sabharwal says. That means that the carriers will be the final arbiters of what Chat can and can't do - and whether it will be successful. The good news is that Google appears to have herded all the carrier cats into a box where their Chat services will actually be interoperable.