02-04-2013 09:14 PM
Solved! Go to Solution.
02-05-2013 11:24 AM
Hello,
It's really up to the app developer to work with you on this. The AW catalog pages present what the developer says they are compatible with...BlackBerry does not, I believe, have the resources to validate all of that. Plus, there is an incredible amount of variation possible...specific OS level, other apps, etc...that can contribute to the (non)functionality of the app.
Here is something to try...Safe Mode:
It may take you multiple attempts to get the ESC key sequence (press/release/hold) correct, so be patient. When successfully into Safe Mode, then try the app and nothing else...see what happens.
If the app works correctly in Safe Mode, then it's something in your other 3rd party apps that is causing the conflict.
If the app does not work correctly, then there is a conflict with the core OS on your BB.
There are things you can try to determine the exact cause, but the process is tedious at best...if you want to try that, just say so and I'll gladly provide it.
pusser_uk wrote:
Am I likely to get a refund because it doesn't work on my phone?
You should exhaust working with the developer before pursuing refund. If you decide you want refund, you obtain that via your mobile service provider...they take your case/request, and escalate it to BlackBerry for processing. You can also challenge the charge via your payment method.
Good luck and let us know!
| |||||||
02-06-2013 09:24 AM
02-07-2013 08:44 AM
I reinstalled the World Clock and, as a double check, started it and, as expected, my phone froze. I removed the battery, followed the instructions about booting in safe mode and tried to run the app again. It froze the phone again, just the touch on the icon and the phone froze, just as before. A further check with Blackberry Desktop Software told me that I have the latest version of the software for my phone.
Talking about the developer, every avenue I take brings me back to appsforbb.com as the developer and any contact with support@appsforbb.com will not get an answer.
It seems that it might be better to give up if further troubleshooting is tedious and call the whole thing a lost cause.
02-07-2013 11:10 AM
That may well be your best bet, because the next steps to try and truly figure it out are indeed quite tedious. But, if you want to try them, they would be:
When the behavior presents, you know the culprit...the last thing you loaded. If the behavior presents no matter what, then the app itself is indeed the likely culprit, and only the app developer can help with that.
Good luck and let us know!
| |||||||
02-08-2013 04:25 AM
02-08-2013 09:44 AM
| |||||||