Christian reports the first February update on his BlackBerry PRIV. Let the games begin. None of my devices gets it, even with Checkin (dial *#*#2432546#*#*).
Update 07 Feb: DTEK60 is my first phone to receive an update. Build AAJ051.
My PRIV has it. No idea why it takes so long for you.
Exactly. No idea. That is the problem.
Not really familiar with the mechanisms involved in distribution of patches it still looks to me like carrier-dependent firmware version might play a role here?
My PRIV is an unlocked AT&T phone. It came with Android Lollippop and AT&T's apps on it which were not uninstallable. Since I was not in AT&T's network there was no way to upgrade my phone to Marshmallow.
Hence I did a clean install from the firmware image that was provided by Blackberry for owners of unlocked AT&T phones like mine.
After that I was able to uninstall AT&T's apps, and ever since I've got all patches on the very day they were announced by Blackberry.
Maybe, just as an experiment, a fresh install from a firmware image provided by Blackberry will make a difference? That would at least answer part of your question.
Maybe it would. But most likely it will not. Wouldn't it be nice if BlackBerry explained the mechanics?
None of my devices is a carrier phone.
BlackBerry made some modifications to the update process for the AT&V PRIV variant: http://support.blackberry.com/kb/articleDetail?articleNumber=000038204&language=English. That is why Martin is getting the updates on his AT&T PRIV.
Thank you Abdelkader.
I have four reports so far: all PRIV, two STV100-4, two STV100-1.
One of them mine :)
And: yes, I think that BB should address this issue. I would be very interested to understand how it works anyway. Things like these used to be carrier-dependent.
E.g. I never got updates for my BB10 devices while in eplus network because my carrier did not explicitly support BB10 devices. I resolved this issue by getting myself a Vodaphone prepaid SIM, performing the updates that would now come in and then put my original SIM back in. Ever since then I got updates.
Hence unless I find any information showing that this is really not the case I would not rule out carrier politics behind this. This IS bad, because it still means that BB cannot keep their promise. But in that case carriers should be told to change their way of handling this, too.
Nothing at 11am, download & install at noon (afetr manual check).
Volker Weber on How to download IBM Connect 2017 session presentations at 14:31
Christopher Schmidt on Two questions about Notes & Domino at 14:18
Erik Schwalb on How to download IBM Connect 2017 session presentations at 14:05
Daniel Kirstenpfad on How did February work out for you? #dontbreakthechain at 13:49
Volker Weber on How did February work out for you? #dontbreakthechain at 12:39
Matthias Lorz on How did February work out for you? #dontbreakthechain at 12:35
Daniel Kirstenpfad on How did February work out for you? #dontbreakthechain at 12:09
Daniel Haferkorn on Insta360 :: First impressions at 11:33
Volker Weber on How did February work out for you? #dontbreakthechain at 09:49
Thomas Gamradt on How did February work out for you? #dontbreakthechain at 09:48
Volker Weber on Porsche Design BOOK ONE at 09:43
Horia Stanescu on Porsche Design BOOK ONE at 09:41
Thomas Kahmann on Love it at 20:20
Tobias Vogel on Lenovo Connect at 14:59
Hans-Helmut Bühmann on Lenovo Connect at 09:49
Volker Weber on IBM Connect 2017 :: Watson über alles at 08:15
Jörg Rafflenbeul on IBM Connect 2017 :: Watson über alles at 05:27
Torsten Pinkert on Love it at 00:00
Volker Weber on Week 8/2017 #dontbreakthechain at 21:46
Markus Jabs on Week 8/2017 #dontbreakthechain at 21:30
Johannes Matzke on Apple Watch charging at 20:50
Volker Weber on Apple Watch charging at 20:30
Karl Heindel on Apple Watch charging at 20:10
Sascha Troll on Week 8/2017 #dontbreakthechain at 20:04
Volker Weber on Apple Watch charging at 19:50