12-05-2013 09:50 PM
I'm testing my app setting home screen wallpaper in headless part. The problem is it only works if the UI part is opening or active frame. Close the UI part then it doesn't work, run the UI part again and it works.
The setting wallpaper code stays in headless part. All other functions work fine without UI part opening.
12-06-2013 10:33 AM
12-06-2013 10:58 AM
Sure, it's not hard. All you need to do is click the link to our Developer Issue Tracker at the bottom of my signature. Log in using your BlackBerry ID credentials, and then hit the "submit new issue" button near the top.
12-06-2013 11:05 AM
12-06-2013 11:07 AM
Can you send me a private message with the email you used for your BBID? I'll take a look and see if your account is set up correctly. There is currently a bug where new accounts sometimes don't get put in the right groups.
12-06-2013 11:33 AM
12-06-2013 12:15 PM
So far, I have 3 QTimer instances in headless part, 1 is working without opening UI Part, the other 2 are not working if UI part is closed and works if UI part is fullscreen or active frame.
The one works: Headless part receiving incoming call signal, my slot starts this QTimer and things works properly.
The other 2 started properly in headless part when deploying app (via IDE) to device or after device reboot. But headless part can't catch the QTimer timeOut signal. My onTimerTimeOut slot doesn't get called. When i open the UI part, things are working properly again. Then close UI, these 2 QTimer instances stop working.
Ok, i read somewhere here that QTimer is blocked somehow or it only runs properly when headless part catches some kinda system signal (like the first above)... or it's just a bug. I'm not sure.
Hope someone has done it could answer the issue.