10-31-2011 04:16 AM
I am not able to update my blackberry bold 9900. Can you please suggest me the procedure to update the OS?
It will be very helpfull for me if you also provide the links from where to download the os if required.
11-01-2011 05:15 AM
11-18-2011 12:22 PM
Yes, in case anyone looks here and doesn't see the other thread, this is a known issue fixed in version 220.127.116.118 of the software.
Tracked on our issue tracker at https://www.blackberry.com/jira/browse/JAVAAPI-215
04-12-2012 04:49 AM - edited 04-12-2012 05:08 AM
Well, I hate to be the bearer of the bad news to the RIM guys who believe that this problem is solved with the latest OS updates, but it isn't.
I have had a perfectly (well near enough) NFC enabled application running for several months. On making some minor changes this week to none-NFC functionality, i.e. No changes at all to any of the code w.r.t. NFC, I repackaged, re-signed and deployed and now get this 'Listener belongs to..." message.
As the company I am working for is an Alliance Partner, I have downloaded and installed the latest OS versions available to us, so I now have:
Updated to latest available version:
Bold 9900 running 7.0 Bundle 2463; v18.104.22.1688; Platform 22.214.171.1240
Bold 9900 running 7.1 Bundle 921; v126.96.36.1997; Platform 188.8.131.52
Running latest carrier version:
Curve 9360 T-Mobile running 7.0 Bundle 2414; v184.108.40.2060; Platform 220.127.116.110
Curve 9380 O2 running 7.0 Bundle 2220; v18.104.22.1683; Platform 22.214.171.124
That is, all versions are newer than the suggested 'Fixed in 126.96.36.1998' version.
Consequently, just as we were getting some traction with a Carrier sales team, our project is (hopefully) temporarily dead in the water.
So, if any BlackBerry Development Advisors are still watching this thread; Have you any further ideas for a Workaround for this problem, because the OS update fix isn't.
04-12-2012 05:03 AM
Please send me a private message about this and we'll take this offline for now. I've heard of no other reports like this. I'll report back here for the community when we've investigated this more thoroughly together.