-
Pretty muchwhy do you think CB got it? because VZW testers don't follow their NDAs
. My guess is most of the testers are people who field the complaints. They are so sick of them, they figure what the h#ll. It can't hurt. Tell you this much, I'm glad they did this time. Except for the crappy Audible app, everything works the way I expect for the first time. 
05-20-09 10:26 PM - I understand that 3rd party applications have to adapt to the OS, not the other way around.
So what you download as "official" from a provider isn't byte-identical to the leak?
We are often told here that there is NO difference between the leak and the official for a given version. Does the .exe that the provider tells their customers to download include their third-party applications (such as VZ-NAV) and configuration tweaks? I am just trying to understand what is different between installing a leak, and waiting (and waiting, and waiting) for the "official" version. Does the infamous vendor.xml file fit in here somewhere?
One reason I am asking is because on Motorola phones, there are low-level configuration files called "seams", and the Motorola counterparts to the Crackberry community spend a great deal of effort to decipher the seam files, to see if some nifty functionality is waiting in the executable code, if only the appropriate bits were set in a particular seam file to "liberate" it (such as the OBEX Bluetooth profile on the VZW version of the 815). Visual and functional behavior could be changed quite a bit (or completely broken) by manipulation of the seam files. Is there anything like "seams" in the RIM OS? This could lead to differences between how the "official" vs. the leaked version behave, even though the executable code is identical.Last edited by CharlesH; 05-22-09 at 02:55 AM.
05-22-09 12:50 AM - the .exe file has no impact on the carrier provided apps...they're available in the leak as well. they should be service book based, so your carrier provisions your account to support the app, and when you send service books, it compares against your VZW/RIM provisioning and sends the according books required to run particular apps, like MMS or VZ-NAV...etc. the device comes pre-loaded with the place holders for many carrier provided apps, that are actually launchers for the DL site on the mobile browser through the mobile.blackberry.com site...if that's what you're implying as compared to the seam files, i can see the relation. but they're not part of the OS, they're included apps. docs to go for example, i used a hybrid shrink-an-OS and it was one of the things removed, and when i loaded .148, it wasn't there anymore. same with VZ nav...they're not on my phone as part of the install.I understand that 3rd party applications have to adapt to the OS, not the other way around.
So what you download as "official" from a provider isn't byte-identical to the leak? We are often told here that there is NO difference between the leak and the official for a given version.
Does the .exe that the provider tells their customers to download include their third-party applications (such as VZ-NAV) and configuration tweaks? I am just trying to understand what is different between installing a leak, and waiting (and waiting, and waiting) for the "official" version. Does the infamous vendor.xml file fit in here somewhere?
One reason I am asking is because on Motorola phones, there are low-level configuration files called "seams", and the Motorola counterparts to the Crackberry community spend a great deal of effort to decipher the seam files, to see if some nifty functionality is waiting in the executable code, if only the appropriate bits were set in a particular seam file to "liberate" it (such as the OBEX Bluetooth profile on the VZW version of the 815). Visual and functional behavior could be changed quite a bit (or completely broken) by manipulation of the seam files. Is there anything like "seams" in the RIM OS? This could lead to differences between how the "official" vs. the leaked version behave, even though the executable code is identical.
hope i clarified.05-22-09 09:54 AM - Thanks for the explanation. There are real differences between how one deploys software on a mass consumer device like a cell phone, and enterprise software intended to be installed on big servers by IT people, that I am familiar with!
Only one question left: how does RIM OS deal with carrier-specific OS tweaks, like CDMA configuration parameters? Is that also a service book that the carrier pushes to the phone? Could the problem some people are having with .148 where the phone app is missing be a service book problem? I understand some BES administrators specifically remove the ability to make phone calls from the phones they control (they want the BB to be used only with their applications).Last edited by CharlesH; 05-22-09 at 12:26 PM.
05-22-09 12:20 PM
