06-19-2012 03:14 PM
06-19-2012 03:26 PM
06-19-2012 03:32 PM
Well, I can't tell, from that, much more than before. As I said, you need to check your exact BB model number and exact OS level against what the app developer(s) claims to support. (FYI...I have no clue what "Airkast" is...) Your friend having the "same exact phone" doesn't necessarily mean the same exact BB/OS level combination...
But, now you've given me another hint...AppWorld. So I can take yet another guess:
I suggest that you clear the AppWorld application cache:
1. Open App World
2. Go to My World
3. Follow one (and only one!) of these steps:
3a. For keyboard-based BB's -- Hold down the ALT key and then press, in sequence R, then S, then T
3b. For Touch Screen Only BBs -- Hold the num-lock (!?123) button so it locks and then press, in sequence 3, then 4, then (
3c. For newer (e,g., OS6 and 7) BB's, see this KB:
4. AppWorld should close.
5. If your BB locks after issuing the cache clear, perform a battery pull reboot
6. Return to AppWorld/MyWorld (it may be sluggish while it re-synchronizes).
If step (4) does not happen as listed, then the clear cache did not work.
Hopefully it'll work for you! Good luck and let us know!
06-19-2012 06:33 PM
06-19-2012 06:59 PM
OK, so I guess you are confirming that you are using AppWorld to attempt this...and the version of AW you've listed is the most recent. But, I must ask for clarity (I try not to assume here):
Tried the cache clearing with no luck.
"no luck" as in, step 4 did not do what I described? Or the Clear Cache worked exactly as written, but nothing changed when you attempted to re-install these from the Uninstalled list? Did you also perhaps try, from within My World, the > Refresh List command?
FYI...the "Bundle" number on the BB OS itself isn't always recognized by the developers...many still (as do I) cling to the 4 octet format (should be the first batch of numbers, inside of the parentheses, after the Bundle number, starting with the letter v). You also need to compare to what it says inside of AppWorld specifically...the developer may or may not have gotten their updated app (for 7.1...which, as far as app development is concerned, is pretty new) fully pushed through AW. Unfortunately, that as well can be tricky since AW so often says things like "OS6 and above" when, in truth, it actually means OS6.n.n.n and OS7.0.n.n, but not necessarily 7.1.n.n.
Rather than using the "Uninstalled" section of AW, have you tried searching the AW catalog brand new from this device?
I also have a history with one other person trying to use a specific app with a specific OS package, for which it was supposed to be compatible. Turned out that, for reasons yet unknown, the app truly wasn't, and the user had to fall back to a slightly different OS package (from a different carrier) in order to get their app to work. It was very strange, but it may be causal here as well. If there is a different 7.1 OS package you can try (perhaps from a different carrier), that might help. Or it might not...there's no way to know anything about this 100%.
Have you also tried removing and re-installing AW itself? Sometimes that can help, especially when combined with plenty of Batt-pulls (e.g., batt-pull, remove AW, batt-pull, install AW, batt-pull, etc.).
06-19-2012 07:20 PM
06-19-2012 07:40 PM