Skip to main content
  1. Home
  2. Phones
  3. Android
  4. Mobile
  5. News

Verizon finally pushes Android 6.0 Marshmallow to the BlackBerry Priv

Add as a preferred source on Google

The Priv, BlackBerry’s first real stab at an Android-based phone, was updated to Android 6.0 Marshmallow way back in April, but it’s only now that Verizon is rolling out the update to its customers.

The original update was already a little overdue — in fact, the Priv launched a month after Android 6.0 Marshmallow was released. It took six months for customers to get a taste of Marshmallow on their BlackBerries, but only if they had GSM unlocked phones. T-Mobile and AT&T customers got the update in June and July, respectively. And now, four months later, Verizon has finally joined the party.

Recommended Videos

Unfortunately, the Priv is one of not-too-many devices running Android 6.0. As of April 4, only 4.6 percent of Android devices were equipped with Marshmallow, highlighting how fragmented the Android ecosystem really is.

Six months is quite a long time to push out an update, especially considering the fact that the Priv is BlackBerry’s only Android phone. HTC and Samsung flagships got an update for Marshmallow back in January or February, and some of LG’s phones got the update as far back as October.

Of course, that doesn’t mean BlackBerry hasn’t been doing anything — the company has been doing great on Google’s security update program, which involves updating devices on a monthly basis to patch any security issues that might exist in the software. This is despite the fact that the Priv is running an older version of Android.

Marshmallow brings a number of great features to the Priv, including user-controllable permissions, something that was ironically not present in the original Priv considering the fact that ‘Priv’ stands for privacy.

The update itself certainly took its sweet time being rolled out, and this may be one area in which T-Mobile reigned supreme over its competitors.

Article originally published in April. Updated on 11-07-2016 by Lulu Chang: Added news that Verizon has finally rolled out Marshmallow update.

Christian de Looper
Christian de Looper is a long-time freelance writer who has covered every facet of the consumer tech and electric vehicle…
TSMC might set up a price hike that could come straight for your next phone, laptop, or tablet
Here's what TSMC's rumored 10% chip price increase actually means in dollar terms, and why your next phone or laptop could end up costing more.
TSMC Fab

My wallet flinched the second I saw the words "TSMC" and "price increase" in the same headline, and honestly, yours should too.

Turns out the company behind the silicon powering basically every flagship device out there, including Apple’s A-series and Qualcomm’s Snapdragon processors, is reportedly about to make all of it a little pricier.

Read more
Samsung’s free storage doubling for preorders is gone in Austria, and the replacement isn’t as sweet
Samsung's free storage doubling deal might just be history.
The back of the Galaxy Z Fold 7

If you've pre-ordered a Samsung foldable purely for the free storage bump, tomorrow's Unpacked event might sting a little.

For years, pre-ordering a new Galaxy meant automatically getting double the storage at no additional charge. Buy the 128GB model, walk away with 256GB for the same price. The same applied to the 256GB and 512GB models. However, that might change at the upcoming Galaxy Unpacked event. 

Read more
Apple fixes Hide My Email bug that exposed users’ real email addresses
Here's how Apple's Hide My Email flaw leaked real addresses for over a year, and why it only got fixed once the story went public.
apple-merging-sign-in-with-apple-hide-my-email-icloud+

Turns out the "Hide" part of Hide My Email wasn't doing its job quite as advertised, something that I covered early in July. Security researcher Tyler Murphy reported the flaw in June 2025, but despite Apple claiming it was resolved in March 2026, independent tests confirmed it remained exploitable, at least until July 3, 2026.

So how did this bug actually work?

Read more