On 3 September 2012 11:08, Timothy Bourke <[email protected]> wrote: > On Aug 21 at 10:30 -0700, Chris wrote: > > Am Dienstag, 21. August 2012 19:21:31 UTC+2 schrieb Chris: > > > > There is no setting "Always allowed". I tried the "Ask once per > session" > > setting but there seems to be no difference compared to "Always > ask". I > > would have expected that with "Ask once per session" there would be > only > > one security prompt for each media file, but when the same audio or > image > > is shown multiple times during one session (e.g. when using the > replay > > button), the security prompt is shown each time before the audio is > played > > or the image is shown. > > > > Correction: There is no setting "Ask once per session" for "Read User > Data", > > only "Always ask" or "Not allowed". I changed the setting for > "Multimedia" to > > "Ask once per session" and that didn't reduce the number of security > prompts. > > Sorry about that. Apparently, some phones do allow "Read User Data" to > be set to "Ask once per session". My old Nokia did not, and the > constant prompting eventually pushed me to buy an Android phone. > > You could try searching to see if there are any tricks for your model > of phone to disable the security prompts. There sometimes are. > > (The J2ME security model is, in my opinion, quite broken. As I > understand things, to have an app signed requires investing hundreds > of dollars per phone, per app release, and completing a tedious > testing process, and even then success is not completely guaranteed. > All this is incompatible with open-source development. > > Yes, it is indeed an unpleasant experience for almost all concerned (except, maybe, the phone vendor who makes quite a profit). Recently, I developed an application just for personal use on my Nokia 6700 Classic, and was amazed that I could neither permit unsigned applications (as a user) to access the filesystem freely, nor generate and install my own certs on the phone without paying Nokia a large amount of money for some time-restricted certificate which _might_ work.
My first implementation used the RecordStore API, which turned out to be laughably limited, causing even small strings to be truncated. In the end, I downloaded some software which allowed me to read the phone's firmware and flash it back with some debug option which permanently allows file access to any J2ME application. Obviously a poor solution, but apparently the only one for these devices. Also, I wouldn't recommend it for non-technical users, as you can ruin your phone, which might require special hardware to fix. I look forward to a simpler, more productive development and deployment situation on Android and iPhone (although I'm not too enamoured with Apple's "pay us every year to upload your own software onto your own phone" philosophy - but it's much better than having to buy certificates for countless phone models/vendors). Oisín I bought signing keys for Blackberry devices after someone's helpful > suggestion. That only cost USD 25 for virtually unlimited signatures > that work on all Blackberry devices.) > > Tim. > > -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
