We have a Java ME Midlet that uses JSR-75 to access files on the memory card. Our midlet accesses many files, so to be practical, the user must not be prompted more than a single time for read permission (and a 2nd time for write permission) per app start-up. This is a commercial product and we strongly believe it is unacceptable to instruct users to find the App Manager and manually bump permissions to "Always Allow".
We are attempting to determine the broadest distribution we might be able to achieve for S60 handsets. Specifically E71, N95, and N96. Are there any options that will meet our needs across multiple carriers?
Some additional details:
Paraphrased from from AT&T's site: The AT&T Policy for both Read & Write permission is DENIED (Application can never use respective function) for both Untrusted & 3rd Party Signed domains. For the AT&T Signed domain No, One-Shot, and Session options are presented.
From Nokia documentation: "It is also important to notice that the permissions are given in a file-to-file basis. This means that the user may be prompted for each file or directory that is being accessed."
Based on the above, I infer that even AT&T Preferred cert would be insufficient as the user would get the "session | ask first time only" permission for each file/dir. Is that correct? (This behavior would make our application horribly unusable.) Luckily, one might forge a business relationship with AT&T and upgrade to the AT&T Trusted cert giving blanket permission.
However, this only (potentially) solves the issue for devices with the AT&T branded firmware, and would not work for the many AT&T customers who purchased their devices from overseas.
Will using Java Verified meet our needs for other carriers, or will that give us 3rd Party Trusted status, resulting in a multitude of permission prompts? Will Java Verified work for AT&T as well?
Any insight on how we might solve this dilemma is greatly appreciated.