The Duo and Duo 2 are finally on Android 12L!

Whenever there’s some Surface news, we can always count on some derisive tech commentary. The folks all too happy to show you how CLEVER they are in panning a niche device.

“I knew it wasn’t going to sell as many units as a POPULAR phone.”

To be fair, there is SOME fun in that. Folks who genuinely enjoy the Surface Duo can get a chuckle out of how small our community really is.

The idea I consistently need to push back against is this lazy notion that Microsoft’s updates for the Surface have been poor. It takes a terrific tech hack to look at the Duos, only look at an Android “number”, and say:

“It needs to be gooder BIGGER Android number!”

Niche Devices Are Different

There’s SO little room for nuance in tech commentary these days.

Portable compute devices built outside the accepted norm of mainstream smartphones rarely get a fair assessment. Reviews for alternative devices often focus on what the device is NOT.

It’s NOT a familiar clone of a popular phone.

“Ww-w-what about the AVurAj CunZoOmeRs?!?!?”

Techies will feign concern for “average” folks, but really, it’s just an excuse to not dig any deeper. That TechTuber doesn’t need to spend more time on an insightful video. That would be additional effort they likely won’t be compensated for. It’s MUCH easier to put out another video on a decimal point software update for a popular phone. Less effort, more money.

I believe manufacturers have done a fantastic job of explaining their products.

There’s rarely any real consumer confusion at play. My non-techie family and friends have seen some WILDLY different devices like the Duos, Blackberrys, LG experiments, and more. I’ve never needed to spoon feed these people the “how” or the “why”. They understand what a niche device is.

There’s a rich tradition of using open-source Android to power “alternative” devices. Why reinvent the wheel, and create an entirely new operating system, when you can take the core Android code and customize it?

These products are not “Android Smartphones” or “Android Tablets”.

The most successful version of this strategy would be Amazon Fire tablets. Amazon promises “at least four years of software security updates”.

The Fire HD 10 was released in 2021. Do you know what build of Android it runs? Is that important to the use of a Fire tablet?

Android But Not Android

Amazon is a more extreme example of this strategy, as Amazon has the resources to replicate their own app store.

Companies like Microsoft (and formerly Blackberry) walked a different balance. Using Android to power devices, maintaining support for the Google Play store and services, but they still heavily customize the experience for unique hardware.

A Duo is a RADICAL departure from a traditional phone, and it takes a mountain of code to make Android work on such a unique device. The Duos were YEARS ahead of the Android curve for delivering better tablet interactions.

Early days on the Duo 1 were certainly frustrating, but the underlying idea was clearly accessible. A Duo had better support for streamlining multi-tasking, and  it incorporated gestures Android was sorely lacking. From Android 10 to Android 11, Microsoft created bespoke software solutions to make the best SURFACE device they could.

The Duo has never been an attempt to make the best ANDROID phone Microsoft can make. The Duo is a platform to make better SURFACE tablet experiences.

Android 12L

Android 12L is here, and I think it’s fair that some techies are underwhelmed with the update. Thanks to how poorly the Duos have been covered, a lot of enthusiasts don’t really understand what was already on a Duo. Looking at earlier Duo coverage, it’s understandable to look at 12L and just see aesthetic differences.

The changelog from Microsoft is a little dry:

• Upgrades the Android operating system to Android 12L for foldable devices. For general information about Android 12, see Android 12 (opens in new tab).
• Addresses scenario outlined in the Android Security Bulletin—October 2022.
• New Fluent UI—redesigned Quick Settings and Settings, refreshed Microsoft feed design, new acrylic system effects.
• Windows accent color styles and dynamic theming based on chosen wallpaper.
• New Windows inspired wallpaper.
• Pen menu for Surface Slim Pen 2.
• Transfer Microsoft Teams meeting through the Time widget.
• Optimize battery usage and performance for Microsoft Teams through hardware offloading.

Out of all those new features, the most direct consumer benefit might be the new Pen menu. Bringing some of the LG/Moto/Samsung stylus polish to the Duo is a WELCOME upgrade for folks who like a pen interface.

The whole experience is definitely prettier with cleaner animations, smoother transitions, and blur effects. The Duo has always been a “practical multi-tasker”, but a little eye candy never hurts.

Additionally, we see improved performance on the camera app, and better low light / night performance. No one would confuse a Duo 2 with being a top tier content creation device, but it’s now a much more capable daily shooter.

Shane Craig has been detailing some interesting potential uses for remote desktop work and desktop modes. I’ve linked his most recent video here, but please give his channel a follow.

A LOT of Duo functionality won’t seem terrifically different, but that’s a good thing.

Tech commentary regularly stops at a shallow assessment of a product. The look of a skin, or the shape of toggles in a notification shade might generate HOURS of video discussion on YouTube these days. There isn’t always the same interest in digging deeper.

The Duos’ Android 12L updates are a prime example of this lack of understanding.

Let’s break down one specific feature: dragging a notification to launch an app.

A notification pops up on your screen. You can tap on the notification to open it, or you can long press on the notification.

Long pressing will deliver a little haptic pulse, and then you can drag the notification to either screen panel. The user has a choice on how and where they want to interact with a notification, and dragging a notification feels a LITTLE more like dragging a window on a desktop.

Android 11 did not have a native solution for this kind of interaction. Microsoft had to build a way for Android 11 to perform this action. This was a difficult challenge, and required a lot of custom code, for what looks like a simple interaction.

Based on the work done by Microsoft and Samsung, Google added some of this dragging functionality into Android 12L. This is fantastic. This kind of functionality is a boon to Android users, and will make Android tablets a more viable option for productivity.

For Microsoft though, it’s not as easy as just swapping A11 for A12L and calling it a day.

How Microsoft created the effect of dragging and dropping notifications in A11 is likely a little different than how Google built that effect into A12L. It takes time to sort out those differences, and then apply the update to unconventional hardware like the Duo.

If Microsoft stumbled on the functionality of the A12L update, it would have come with a severe tech commentary backlash. There was NO benefit for Microsoft to rush the update. Why risk the negative commentary if the Microsoft flavor of Android 11 already had a reasonable solution for a similar action?

Every tablet interaction on a Duo likely faced this kind of scrutiny.

The Duos launch apps in split screen. The Duos have drag and drop image support in select apps. The Duos can slide apps and “snap” them to different screens. The Duos have to be aware of single screen and dual screen orientation.

It’s an incredible challenge getting everything right, and there are some early A12L gremlins that need to be polished up. I have confidence that Microsoft will be improving on these features in future updates. They’ve earned that confidence in their support.

Microsoft Updates Have Been Excellent

The challenge of bringing Android 12L to the Duo was certainly worth the effort. A12L brings much better tablet tools for app developers. Immediately, Duo owners have benefited from apps that are already using A12L APIs.

In this era of Android, and listening to the general tone of reactions to an update like this, I’m not “excited” about Android 12L. More, I’m mostly relieved that Android 12L is here AND it’s running as smoothly as it is.

Android 12 has been a roller-coaster of expectations. Microsoft dodged most of the early Android 12 teething pains, and delivered a well-polished update later than many might have hoped.

Just because we did not see the settings page jump from A11 to A12 immediately on A12’s release, does NOT mean that Microsoft has just been sitting on their hands. The Duos have received significant updates, bug fixes, improved functionality, new features, and Microsoft has consistently delivered some of the fastest security patches on any Android powered devices.

What’s really more important? Being current on the Android number (often at the expense of stability), or delivering the best user experience?

The Differences Matter

It is nice to get some new features to play with on Android 12L.

I would have been critically disappointed in Microsoft if we had followed in the early footsteps of Android 12 like other Android manufacturers. Google, Samsung, and OnePlus all had to pull Android 12 updates to re-work significant issues. The effects of those early bugs, on a radically different form factor like a Duo, likely would have been significantly worse.

More, I’m just critically disappointed (again) in a tech commentary industry that lazily slaps on hack criticisms of products that require a little more examination.

It’s easy (and lazy) to conflate Apple’s update strategy with Microsoft’s and declare the Duo updates “worst-in-class”. It might LOOK like that, but the reality is significantly different. This tone of commentary severely muddies the waters on real-world use, and might dissuade someone from giving an alternative product a chance.

Apple rolls out big over the air updates. Apple OTAs include EVERYTHING. Bug fixes, security patches, new features, app updates. This is really clumsy. If a component in Siri is ready for consumers, or a patch to Safari security is needed, why should users wait for a system level update?

Android is “messier”, but it can be more practical. The Duo is an extreme example of this. Updates come by way of large OTAs, Google Play updates, monthly security patches, and individual component updates in the Play Store.

The Duos weren’t “out of date” because they ran Android 11. Microsoft maintained consistent security patching while fixing bugs and other exploits.

It’s one of the worst aspects of tech commentary online today.

Of course there are far more folks familiar with Apple’s style of support. That doesn’t mean Microsoft’s different style of support is worse for consumers. If a reviewer can’t acknowledge those differences honestly and consistently, they’re doing a disservice to the tech conversation.

If we’re concerned about “avuraj cunzoomers”, maybe we should stop trying to confuse consumers in our reviews and editorials?

The Shadow of Blackberry

If you’ll pardon me closing this out with a quick trip down memory lane, this style of support from Microsoft reminds me of the TCL era of Blackberry devices. Another example of techies completely missing the point of what a manufacturer was trying to accomplish.

The Blackberry Key and Key2 were heavily customized Android devices. Not only including support for a rich hardware keyboard experience, they were also HEAVILY modified to focus on security.

Sitting down at a briefing with TCL and Blackberry reps, it was made very clear, these phones weren’t going to be handled like traditional Android phones. There wasn’t going to be as much effort made in applying Android OS updates, as they were focused on security and messaging performance.

The Key2 launched in 2018, and it was never updated beyond Android 8.1.

This was by design.

Blackberry and TCL supported the software, pushed out bug fixes and OTAs, but they weren’t trying to make an Android phone. They were trying to make the best Blackberry they could.

It looked like Android Oreo. It had Google Play Services. It installed apps from the Play Store.

However, there were significant under-the-hood software differences, and the Key2 proved to be one of the most secure devices released of its generation.

Looking through old forum posts, there have been several bounties offered for exploits on old Blackberry phones that might lead to root access or the ability to flash custom ROMs. To my knowledge, none of those bounties have ever been claimed.

The Blackberry Key2 is SO secure, that even today (in 2022) we’re still hoping to find ANY way to unlock its bootloader. This Reddit thread is searching for developer devices that might have leaked out of TCL’s offices to find any clues on what might crack the phone open.

Running Android Oreo today probably wouldn’t be much fun, but it’s still a remarkably secure device considering how old the software is. Someone casually making a comment about a Key2 being “not secure because it’s stuck on Android 8”, is glossing over some significant differences in how that phone really ran Android 8.

Yes, it’s Android 8, but it’s not REALLY Android 8. The nuance matters.

If you still have a Blackberry Key2 (I know, DOZENS of us) your device is likely still safe to use so long as YOU don’t go out doing irresponsible things with your phone. You should probably be a bit more worried about social media apps handling your data.

Google updated Play Protect to support devices running older versions of Android, which helps against many common threats through apps and browsers. We’ve seen better support for removing permissions from unused apps. Numerous Google components on the phone are still being updated today through Play Store App updates.

Google improves on generations old device security, and on top of that we haven’t seen a significant security hole exploited that can really compromise the device.

The Key2 mission was successful. It was a DIFFERENT mission than other Android phones of its era.

Wrapping This Up…

The Duo and Duo2 are fascinating devices that I love to revisit. They’re currently my favorite tablets. They’re unique and fun, and nothing feels quite like a Duo.

I really don’t care about “Android” when I’m using them.

Android 12L is a welcome update. I hope this helps streamline some of the development process for Microsoft, and future updates won’t be as labor intensive to deliver. I’m really not that concerned when the settings page gets “Android 13”.

Microsoft has earned significant credibility that the Duos will be supported, maintained, and improved regardless of what Android “number” is on the settings page.

We should be focused on the best device performance and functionality. Good software support is more than just an OS number getting bigger on the spec sheet.