View Poll Results: Will BB OS6 top iPhone OS4?
- Voters
- 68. You may not vote on this poll
-
Yes
11 16.18% -
No
52 76.47% -
Other
5 7.35%
-
It's not the nativity of database/app that is the problem. It is the coding that pulls that data out and presents it to the user. There are issues here. There are also parts of apps that poll different databases in order to present the user with a set of information... this coding sometimes pulls incorrect data. Also, the apps sometimes change the way the data is being saved into these databases, meaning that with some OS releases, the info within the database becomes formulated in a new way, so the restored data from a user doing a database restore after an OS update, actually can contribute to corrupt/problamatic databases. Of course, since we don't know when this happens, it's hard to sometimes pinpoint if these are the causes of the issues.
A good example of the above is the threaded SMS redesign. The coding was (and is still) so buggy that sometimes you have threads that that get corrupt for certain users. The only way to clear this up is a complete wipe of the SMS database or just delete all your SMSs and start fresh.
With some of the redesigns in OS5, for some reason RIM coders have also introduced additional databases which double up on something that was already there. Now there's a Phone Call Logs and Phone Call History database. What's the need for this redundancy? I have a feeling it has something to do with them wanting to filter out some things like VoiceMail calls and Unknown Caller calls (which no longer show up in the Call Log view in the Phone app, but they do show if you go to Messages/View Call Logs. Again, stupid move because some people want to see ALL these calls listed... now we can't even easily delete them from the Call Log view in the Phone app, we have to take multiple steps to get to Messages/Menu/View Folder/Phone Call Logs... dumb!
Anyway, there's a lot of issues which some of you don't even realize... but this is starting to become a explaining/debating thread for issues which should be discussed in the appropriate threads for this... most of which I've written when the bugs were found (yes, they've been happeing for a while in multiple OS5 builds and some even in 4.7). Some of you (synthmole) should go and read some of those detailed threads so that we don't have to rediscuss these issues in threads like this and end up derailing the topic and hijacking the thread.
No offense synth, I think you're just curious, but I wish I could show you all the issues without having to retype them all out. Check out the Storm section for a lot of bug reporting threads... keep in mind that a couple of months ago, I kinda gave up on the constant reporting (with details) of bugs and started on my RIM bashing spree. I felt it was a waste of my time since even once reported to RIM, the bugs would take several builds to fix and it seems we're not going to see further releases for the S1 that will resolve a lot of these. Let me put it this way... myself and a few others have found several bugs and procedures for duplication and reporting to RIM which both RIM testers and carrier testers HAVE MISSED... and they were the ones getting paid to do the job.
When you put that time in to detail out bugs and how to duplicate them and then get people to report them to the proper people (which actually shoot it back as "we can't duplicate the issue" or "it doesn't exist") and then you reexplain it step by step like you would to a child and they actually try it per the writeup AGAIN, then notice the issue is real and tell you they'll fix it... and then you don't even see a freaking handout of a leaked OS containing the fix because RIM expects those same careless carrier employees (i.e. Verizon testers) to certify the builds before release... ya, you get bitter... and you start bashing their ways of doing things... from fixing issues, to developing, to updating, to building, etc.04-18-10 09:22 PM
)
