Android Archive

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.

Google renames Android Wear to Wear OS

As our technology and partnerships have evolved, so have our users. In 2017, one out of three new Android Wear watch owners also used an iPhone. So as the watch industry gears up for another Baselworld next week, we’re announcing a new name that better reflects our technology, vision, and most important of all - the people who wear our watches. We’re now Wear OS by Google, a wearables operating system for everyone.

If a company changes the name of one of its operating system, but nobody cares - has the name really been changed?

Google releases first Android P preview

Google has released the first preview for Android P - again, apologies for the late coverage - and it contains some interesting improvements. Here's a few things that jumped out at me:

To better ensure privacy, Android P restricts access to mic, camera, and all SensorManager sensors from apps that are idle. While your app's UID is idle, the mic reports empty audio and sensors stop reporting events. Cameras used by your app are disconnected and will generate an error if the app tries to use them. In most cases, these restrictions should not introduce new issues for existing apps, but we recommend removing these requests from your apps.

This is a very good move, and I doubt anyone will have any objections.

In line with these changes, Android P will warn users with a dialog when they install an app that targets a platform earlier than Android 4.2 (targetSdkVersion less than 17), and future platform versions will continue to increment that lower bound.

Expect scary warning dialogs when installing older applications. This should encourage developers to update their applications as users complain in the review sections of the Play Store. Hopefully.

You can now access streams simultaneously from two or more physical cameras on devices running Android P. On devices with either dual-front or dual-back cameras, you can create innovative features not possible with just a single camera, such as seamless zoom, bokeh, and stereo vision. The API also lets you call a logical or fused camera stream that automatically switches between two or more cameras.

Definitely neat.

There's a lot more stuff in this preview release, and more features will certainly follow over the coming months.

Bad iPhone notches are happening to good Android phones

I’ve been coming to Mobile World Congress for close to a decade now, and I’ve never seen the iPhone copied quite so blatantly and cynically as I witnessed during this year’s show. MWC 2018 will go down in history as the launch platform for a mass of iPhone X notch copycats, each of them more hastily and sloppily assembled than the next.

No effort is being made to emulate the complex Face ID system that resides inside Apple’s notch; companies like Noa and Ulefone are in such a hurry to get their iPhone lookalike on the market that they haven’t even customized their software to account for the new shape of the screen. More than one of these notched handsets at MWC had the clock occluded by the curved corner of the display.

I have an iPhone X, and the notch doesn't bother me at all. Face ID works reasonably well - not as good as Touch ID, but good enough - and thus, gives the notch a reason to exist in the first place. I don't feel particularly strongly towards either Samsung's small chin/forehead solution, or Essential's/Apple's notch solution, and I'm glad it at least creates some visual difference between phones. However, if you decide to go with a notch, don't just copy Apple's shape while not actually putting anything underneath it.

I can't believe this is truly going to be a thing.

Android Go phones show how much you can get for $100

Mobile World Congress is happening this week, and we're slowly getting a better picture of what Google's new "Android Go" initiative will look like. Android Go is a special configuration of Android 8.1 (with a selection of special "Go" apps) that targets low-end devices with 1GB of RAM or less.

MWC has seen a ton of manufacturers sign up for the program and announce phones shipping with the Go config, so it's time for a hardware roundup.

We often tend to get tunnel vision and focus on expensive flagships, so here's a roundup of upcoming 100 dollar Android Go phones. These are neat little phones for a decent price.

Android One becomes the new Google Play Edition

If I look back through all of the years we have covered Android, it’s hard to argue that the introduction of Google Play Edition phones wasn’t one of the biggest moments. In those early years, the Android skin situation was bad. Those early versions of TouchWiz, MotoBlur, and even HTC Sense, weren’t what many of us wanted, to say the least. We wanted Google’s version of Android, as well as their Nexus update schedules, yet that was tough to get because Google was making average hardware at the time.

While Google Play Edition may have failed as a program, I get the feeling that Android One will now act as a proper replacement to it.

Stop trying to make timely Android updates happen. It's not going to happen.

Google’s next Android overhaul said to embrace ‘notch’

Google is working on an overhaul of its Android mobile software for a new generation of smartphones mimicking Apple Inc.'s controversial new "notch" at the top of the iPhone X, according to people familiar with the situation.

The Android update, due later in the year, will also more tightly integrate Google’s digital assistant, improve battery life on phones and support new designs, like multiple screens and foldable displays, the people added.

A key goal of this year’s update to the Google mobile operating system is to persuade more iPhone users to switch to Android devices by improving the look of the software, the people said. They asked not to be identified discussing the private plans. A Google spokesman declined to comment.

A bit short on actual details, but what's there is mostly the kind of stuff you'd expect Android to be preparing for. We're going to need to be closer to Google I/O for more concrete information.