Mobile Device Max Jar Size

[harsha921]

Hi,

I would like to know is there a way to find out the target mobile device's max jar size, before OTA download. Because for some of the devices my application is running out of max size and customers keep complaining about the application installation.

Thanks in advance.

[bandarap]

Hi harsha921,

with below link you can find all the specifications of the any device:
http://www.developer.nokia.com/Devic...ions/Asha_306/

Select device in the right side combobox and in the left side unfold Memory Functions section then you will see Maximum JAR Size.

[harsha921]

Hi bandarap,

Thanks for the reply. But Whats my question is how to find those details programatically. Is there a programming technology like javascript,jquery etc. to get those details before i could download the jar file.

[bandarap]

AFAIK, there is no such API available in Java ME or Web for Nokia devices.

[petrib]

You can use the HTTP user-agent header on the server side to determine what device is browsing your site, and whether and what to return to it in your response.

http://wurfl.sourceforge.net/

[harsha921]

Hi petrib,

U mean to say, I need to check the max jar size for each and every device and handle them seperately based on the device model returned from user-agent?

Thats too complex i guess.

[wizard_hu_]

Yes, unfortunately it is missing from the user agent profile (on-line, machine-consumable description of the devices, like http://nds1.nds.nokia.com/uaprof/Nokia3050r100.xml)

[harsha921]

can u please provide a sample on how to handle that.

[wizard_hu_]

It can not help you, as it does not contain the information you need. Sorry. Just added the remark so others do not have to check it.
Otherwise if you need the profile for any other use, its link is somewhere in the user-agent headers as I know, and the profile itself is just an XML document.

[petrib]

How to do it:

- Collect (manually) the info for different models from the device specs on these pages for each model
- Create a mapping of for each user-agent header that those models send (note also that different browsers on those phones might be sending different things, different user-agent strings)
- Based on that mapping, resolve whether you should allow the download or not

Simpler, less user-friendly approach:

- On your web site show a warning note to the phone user that you cannot guarantee that it works on all models, and what your minimum requirements are (e.g., the phone has to support 2MB jar files, or whatever), and leave it to the user to known and handle (and also make sure whomever handles your support requests by users, if they have the means to contact you, knows about this and can recognize the issue and tell the people why your app doesn't work on their phone).

[harsha921]

Hi petrib,

Thanks a lot for your valuable suggestions.