Thanks so much, hope it solves the problem!
Printable View
Thanks so much, hope it solves the problem!
Just got this from Rogers technical support. Seems like an update on August the 21st is for bug fixes. Hopefully this fixes the notification issue!
http://communityforums.rogers.com/t5...hlight/true#M1
I hope so too!
But did the Rogers Keyone already get the august 5th security update?
Not sure. I just got the KeyOne a couple days ago, but in the description it says "bug fixes" not security patch
What is your current OS security update number and what date?
Android settings > about phone > android security patch level
It says July 5, 2017.
The description does say bug fixes, not security patch though. Maybe it'll be both.
I am sorry but only my August patience will come.
I had to switch back to my DTEK60. Couldn't go any longer with the lack of notifications. I was leaving the apps open in the background, but those were being closed automatically.
My KEYone is on the shelf for now until the issue is resolved.
Same. Back on the priv.
So disappointing on many levels.
I think I will return to Passport.
Just waiting for an update to fix it then I'll be back. It will collect dust until then.
Same for me. I liked the device. Just unusable for me right now due to this issue.
any information about BlackBerry being aware of this? I just was able to find answers from their support stating that BlackBerry cannot replicate the issue...?!
I keep saying, people need to open tickets with them. I have one open and they're saying it's a device issue, not software.
I've gone higher up, and they are aware of the issue.
thread know, but nothing do not!! [emoji34]
Maybe Yoda can fix it
Yoda?
Good idea, I'll go back to my PRIV till this is fixed.
Do you find it objectionable that they have remained silent publicly on this issue? I know I do, and I'm sure many others feel the same. I don't think they're doing themselves any favors by remaining silent.
And just LOL at the pathetic apologism in this thread. So sad yet so funny at the same time.
I am really scratching my head on this issue. I'm more concerned about why it took so long to discover such an obvious and critical bug, and why it's taking so long to correct.
I read blaze was saying some of his KEYᵒⁿᵉ doesn't have this notification issue while some of his other KEYᵒⁿᵉ has the issue. is it really possible? I have had total 4 KEYᵒⁿᵉ(replaced due to screen lifting) including the one that I am using right now, and all of them had and have the same notification issue. :(