01-10-2014 12:45 PM
I am testing this on the SDK OS 10.2.1.1927 for my Dev Alpha C. My app is headless long running no stop. The signal and slot work perfectly from the time deploying app onto device. My slot gets called anytime there is change made to the Notification Mode of the phone.
But once the device reboots, for whatever reason. The headless starts running, the signal and slot is THEORY connected, because i use the bool to check if the connection succeeds. And yes it returned true for the connect.
But actually, my slot doesn't get called at all. All changes made can't be received. Anyone get the same issue?
Solved! Go to Solution.
01-11-2014 07:42 AM
01-11-2014 07:57 AM - edited 01-11-2014 08:00 AM
Mine was approved to be long running no stop , and it worked correctly on 10.2.1.1055. Only 1259, 1925 leaked OS and 1927 SDK OS have issue.
01-11-2014 08:11 AM
01-11-2014 08:18 AM
Some other samples work properly, only my NotoficationGlobalSettings signal doesn't "after reboot". But it worked on the leaked OS 10.2.1.1055, that's weird.
After a reboot, the return value of the connect is true, which usually means successfuly connected. But nothing can be received in my slot. This is really weird.
01-14-2014 01:58 AM
Ok, got it fixed. I don't know if BlackBerry will fix this in the OS or not but in case you need it, then the alternative work around is to delay the connect.
Delay the connect call to connect this signal modeChanged(bb:latform::NotificationMode::Type) to your slot which handles stuff when Global Notification Mode is changed.
In my case, i have tested with 3 seconds delay and it's working properly. After reboot the device, it still works correctly.