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).
Craig Wiseman on IBM Think 2018 at 05:25
Stephan Perthes on Sales Wick :: Vuelo Nocturno at 09:30
Dietmar Dumke on IBM Think 2018 at 06:38
Stephan H. Wissel on IBM Think 2018 at 02:48
Gordon Inkson on Is Slack a product or a feature? at 03:22
Ian Bradbury on Is Slack a product or a feature? at 17:36
Keith brooks on Is Slack a product or a feature? at 15:23
Bill Brown on Samsung Galaxy S8 :: The verdict at 18:57
Richard Schwartz on Samsung Galaxy S8 :: The verdict at 16:01
Andy Dennis on Is Slack a product or a feature? at 16:00
Karl Heindel on Marshall Monitor BT at 15:32
Martin Funk on Is Slack a product or a feature? at 15:02
Volker Weber on Marshall Monitor BT at 11:25
Karl Heindel on Marshall Monitor BT at 11:21
Michael Klüsener on Is Slack a product or a feature? at 09:14
Patrick Bohr on Is Slack a product or a feature? at 19:56
Frank Quednau on Is Slack a product or a feature? at 18:02
Thomas Klein on Samsung Galaxy S8 :: The verdict at 15:46
Volker Weber on Samsung Galaxy S8 :: The verdict at 11:34
Patrick Bohr on Samsung Galaxy S8 :: The verdict at 08:51
Felix Binsack on Samsung Galaxy S8 :: The verdict at 16:49
Volker Weber on Samsung Galaxy S8 :: First impressions at 14:01
Volker Weber on Marshall Monitor BT at 13:59
Scott Hanson on Marshall Monitor BT at 13:23
Norbert Tretkowski on Samsung Galaxy S8 :: First impressions at 09:44