Keep OSNews alive by becoming a Patreon, by donating through Ko-Fi, or by buying merch!

Android Archive

Google makes two different versions of Android

We go through this every time a new version comes to Google's own phones while we wait for it to come to the rest. And the outcome is always the same - Pixel phones (and previous Nexus phones) look the way Google wants them to look and the rest of the phones look however the company that made them want them to look. That's because you can't see Android - it's simply software that supports the things you're looking at.

It's confusing. And tech bloggers (myself included) don't help ease the confusion very well when we write about the things we see on a software update for the Pixel. It's too difficult to try and break everything down every time we write something, and while we are good at a lot of things, we tend to shy away from "difficult". To compound it all, when we do try to break "Android" down, we usually make it worse. I'm going to try here because I'm feeling courageous and want to face "difficult" head on today. If I don't come back, tell my wife I love her.

Android is quite a complicated term, entity, and operating system.

Hands-on with the RED Hydrogen One

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".

I doubt this phone will ever have any mass-market success, but that's not really the point anyway. I like that RED is trying something new, something different, and takes it to the extreme with this industrial design. The module system here is different from previous failed attempts at doing so in that it's designed to tie in with RED's popular and expensive camera's and lenses from other big camera brands, instead of trying to appeal to the mass market.

This might actually work out.

Android P apps crash silently instead of showing dialogs

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.

You know how some people will insist that iOS applications are more stable than Android applications? That's because on iOS, when applications crash, they just... Vanish. No dialog, no notification, nothing. Android will now be adopting the same behaviour, which, while less informative, does remove a silly dialog that you couldn't really do anything useful with anyway.

Good move. Dialogs you can't take any actions with are useless.

Android P’s gestures are a jagged pill you should learn to swallow

I bring this up because when Google introduced its new pill-shaped gesture area on Android P's first public beta, it was immediately apparent that Google was not aiming to recreate the simplicity, or even the convenience, of its decade-old three-button navigation scheme. Swiping up does not, in fact, go to the home screen but to the multitasking menu. Swiping up again, and only from that in-between state, reaches the app drawer. Indeed, reaching the home screen requires tapping the pill, something that's not at all obvious from its shape, or from precedent set by Apple and the rest of the industry.

I don't have a Pixel or one of the other supported devices to test the new navigation scheme on, but it only makes sense that people are weary whenever big changes to core parts of a UI like these are made. People were up in arms over the removal of the home button on the iPhone X, but it took me less than hour to get used to, and Android P will be no different.

Google to require OEMs to roll out Android security patches

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.

Every little step in this department is a welcome one. It's not yet clear what, exactly, the requirements entail, but hopefully, it's a strict and hard requirement to publish every monthly security update.

Google releases Android P beta

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.

There's tons of new features, mostly about Android trying to anticipate what you want to do next. Android P takes Android's already pretty good inter-application communication a step further, by exposing actions and even parts of applications outside of the applications themselves, with App Actions and Slices.

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.

Other than that, Android P also brings gesture navigation to Android, to deal with phones with smaller bezels. Furthermore, Google put a lot of emphasis on what it calls "digital wellbeing", which aims to make you more aware of how and how often you use your phone. For instance, a feature called Wind Down will make the screen go black and white at a chosen time, encouraging you to put the phone down and go to sleep, and Dashboard gives you detailed information about how you use your phone.

The beta version of Android P is available starting today, for Pixel phones and a variety of other phones.

Android P should be about privacy

Now that iOS and Android are approaching technical maturity, new updates to these operating systems no longer feel revolutionary. The new stuff we get every year is boiling down to smarter notification handling, under-the-hood upgrades, screen notch adaptations, and “borrowing” good ideas from one another. As Google prepares to take the wraps off its next big iteration, Android P, at Google I/O 2018, I have an idea for an alliterative theme: make it Android P for Privacy.

Fully agreed with Vlad Savov. Sadly, the lack of encryption in Google's new chat feature doesn't bode well.

Android P DP2 possible leak shows navigation gestures, more

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.

Some interesting possibilities for Android P, which will probably be demoed later today during the Google I/O keynote.

Android Things 1.0 released

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.

Google is promising three years of security updates, straight from Google itself.

Android will finally restrict apps from monitoring network activity

A years-old privacy flaw will finally be coming to an end on Android. It's an issue you've probably never heard of, but one that you should absolutely be concerned about. Currently, apps on Android can gain full access to the network activity on your device - even without asking for any sensitive permissions. These apps can't detect the content of your network calls, but they can sniff any outgoing or incoming connection via TCP/UDP to determine if you are connecting to a certain server. For instance, an app can detect when another app on your device connects to a financial institution’s server. Don’t believe me? Just download one of the many netstat apps on the Play Store and see for yourself.

I had no idea this was an issue at all. Good to see it fixed, and since it'll probably be part of a monthly security update, it'll propagate to most Android devices.

Google, please fix Android’s slow, bloated share UI

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.

The share sheet on Android is, indeed, a mess. It's odd how such an important aspect of one of Android's major strong points - inter-application communication - is being left to rot.

De-Googling my phone

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.

One of those topics not particularly suited for most smartphone users, but among OSNews readers, there are sure to be quite a few people who are interested in this.

“I switched from iPhone to the Pixel 2: one-week report”

All those little features add up: The phone is fun and easy to use. And so far, there's no serious downside. I mentioned it above; the experience is simultaneously high-end luxury yet while staying informed and in control of the device. I believe this is a very difficult mix to get right. IMO, Apple's been drifting away from the keep-the-user-in-control value.

Maybe this sounds naive, but I'm completely surprised by how the product stands on its own. It's not in the shadow of iOS, not playing catch-up with Apple. I'm continuously seeing common problems solved in new ways.

I'm sure we can have a civil, informed, and respectful discussion about this. To facilitate such, I'm going for a walk. With my iPhone 10, AirPods, and Apple Watch.

Android Go review

Ars Technica takes a good look at Android Go, and concludes:

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.

Chat is Google’s next big fix for Android’s messaging mess

The Verge has a big exclusive - Google has managed to corral carriers into supporting something called the "Universal Profile for Rich Communication Services", or Chat, which basically replaces SMS in every Android phone.

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.

Most people in the world, whether they buy an iPhone or an Android phone, dump all the preinstalled chat applications into a junk folder, install WhatsApp or WeChat (or Telegram in repressive dictatorships like Russia and Iran), and forget this American obsession with iMessage vs. Google's 238437 chat apps even exists.

That being said.

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.

Sounds like something they should've done ten years ago, but as you dive further into the details, a whole bunch of huge red flags pop up:

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.

In the current political and societal climate, the lack of end-to-end encryption is absolutely bonkers. Obviously, there's no encryption because carriers (and our governments) want to snoop on our communications, but with end-to-end encrypted options readily available, why even bother going 2-3 years back in time?

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.

Isn't the point to get away from under carrier control, not slide back under it?

I just don't see how such an archaic service like this will ever gain any traction, when most of the world has already settled on its chat service, mostly dictated by what your friends and family uses. Without end-to-end encryption and while under carrier control, this service seems like a massive step backward - not forward.

Liberating MediaTek bootloaders and modem firmware

On the right you can see photos of a Coolpad Modena 2, which was built around MediaTek's MT6735P SoC (System on a chip). In case you are wondering why we're not showing a picture with postmarketOS running on it: we can't! This is because the vendor decided to ship it with a closed down bootloader, which prevents users from running custom kernels.

The postmarketOS team details how they are cracking open the bootloader and the cellular modem firmware on MediaTek-based devices.

How Android phones hide missed security updates

Google has long struggled with how best to get dozens of Android smartphone manufacturers - and hundreds of carriers - to regularly push out security-focused software updates. But when one German security firm looked under the hood of hundreds of Android phones, it found a troubling new wrinkle: Not only do many Android phone vendors fail to make patches available to their users, or delay their release for months; they sometimes also tell users their phone's firmware is fully up to date, even while they've secretly skipped patches.

On Friday at the Hack in the Box security conference in Amsterdam, researchers Karsten Nohl and Jakob Lell of the firm Security Research Labs plan to present the results of two years of reverse-engineering hundreds of Android phones' operating system code, painstakingly checking if each device actually contained the security patches indicated in its settings. They found what they call a "patch gap": In many cases, certain vendors' phones would tell users that they had all of Android's security patches up to a certain date, while in reality missing as many as a dozen patches from that period - leaving phones vulnerable to a broad collection of known hacking techniques.

Android is a mess.

Android Studio 3.1 released

New to Android Studio 3.1 is a C++ performance profiler to help troubleshoot performance bottlenecks in your app code. For those of you with a Room or SQLite database in their your app, we added better code editor support to aid in your SQL table and query creation statements. We also added better lint support for your Kotlin code, and accelerated your testing with an updated Android Emulator with Quick Boot.

Google blocks GApps from running on uncertified devices

Even though Android is open source, virtually every Android device sold outside of China contains a chunk of closed code from Google in the form of Google Play Services and the GApps. These two deeply related software packages turn a rather stale mobile operating system into the full-on Google Android most of us know. There aren't a whole lot of Android users (again, outside of China) who aren't using these.

Since these packages aren't open source, custom Android ROMs ship without them; you have to sideload them manually after installing your ROM image. Luckily for us, Google has always allowed this, but it's always been a bit tenuous. It's about to get a whole lot more tenuous, since Google appears to be blocking GApps from running on uncertified Android devices - but thankfully, they're allowing custom ROM users to register their Android device to get an exception.

Earlier this week, we received an anonymous tip from a person claiming to be within the industry. This person, who said they worked for an OEM/ODM, notified us that Google has started entirely locking out newly built firmware from accessing Gapps. This change apparently went into effect March 16th and affects any software builds made after this date (Google Play Services checks ro.build.fingerprint for the build date apparently).

You can register your device to get an exception, and you can register up to 100 devices per user - which should be enough for virtually everyone, I assume.

Introducing the LineageSDK for developers

LineageOS is an operating system for everyone: from the average user to the advanced developer. While users have a giant playground in their hands with many customization options, we also want to make LineageOS a fun place for developers. The standards for official builds help ensure developers that their app will not end up in a bad state because of inappropriate Android API changes or broken hardware support, but this is not enough for us; we're announcing some new APIs that will allow your apps to do more when they're running on a LineageOS-powered device.

The Lineage platform SDK (LineageSDK for short) is a powerful resource that allows us to both keep our features out of the core Android frameworks (for better security and easier bringup processes) and expose some extra functionality to app developers.

We'll have to wait and see if developers are willing to add some code to their Android applications for the features in this SDK.