You Are Here:

Community: Blogs

Hartti Suomela's Forum Nokia Blog

Checking out the API access settings on Nokia devices

hartti | 30 March, 2007 00:45

I have touched the security settings of operator branded phones on this blog in the past (China Unicom, Sprint, Hucthinson 3G, T-Mobile U.S. and AT&T/Cingular). However I have been pretty light on details about the API access settings on generic (non-branded phones). Time to change that.

 

Attached is an PDF file (created from an Excel sheet) containing a small sample of API access settings for a number of Nokia phones and the recommended settings from the various JSR specifications (MIDP2, MIDP2.0.1, MIDP2.1, JTWI, MSA). Note that even the recommendations from different MIDP versions are different. And the settings on generic Nokia phones differ from those. And sometimes even the firmware versions seems to affect the available settings. Oh, what a mess.

 

Yes, I know. This blog is not the optimal place for publishing this kind of info, but I was wondering if people would have some comments on how to present this information so it would be most useful to the developers. One possible, and final resting place for this stuff as well as the operator specific settings information is Forum Nokia Wiki. I was thinking of one page for each different API access settings,  and listing all the devices having those settings. Is this kind of table good, or does someone prefer the tables from JSR specs (which to me look confusing)?

 

Any other suggestions?

RSSComments

Re: Checking out the API access settings on Nokia devices

hartti | 31/03/2007, 03:50

hartti started a page on this on FN wiki
http://wiki.forum.nokia.com/index.php/Java_Security_Domains

So far I have just created one permission table page (see here http://wiki.forum.nokia.com/index.php/MIDP_2.0_API_access_rights)

what do you think? is the formatting of the table clear enough?

Hartti

Permissions

b2b4u2001 | 19/06/2008, 08:32

Hi Hartti,

my self Bhaumik.

i have created j2me app with JTWI.
is it the best way?
if not then plz let me know what would be the best way to implement to get most of the permission without signing app.

Midlet sign key can not apply

kvht | 05/07/2008, 08:07

Hi Hartti,

I have a problem with Nokia N95. I signed my Midlet with Thawte. When I install, I can see my key information (3 entry). But when I launch midlet, java.lang.SecirityException throw when I use HttpConnection.

I used WTK to sign my midlet.

Can you help me to resolve this problem. Thank you very much

Bach Pham

You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2findeE78E2ephpE3fopE3dViewArticleE26blogIdE3d32927E26articleIdE3d225X qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZBlogE45ntryQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtopicQUqfnTopicZjavaQ qfnZtopicQUqfnTopicZseriesE5f40Q qfnZtopicQUqfnTopicZseriesE5f60Q qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZBlogE45ntryQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZuserE5ftagQSxjavaX qfnZuserE5ftagQSxs60X qfnZuserE5ftagQSxseriesE2d40X qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZBlogE45ntryQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ