Hello All,

Version 7.1.1 is now available from the usual places:

http://pypi.python.org/pypi/pywurfl/
http://celljam.net/

- Updated to Java API version 1.0.1 of the two step analysis algorithm.
- Fixed a few bugs.

Thanks to Malcolm Box for the bug reports and fixes.
Thanks to WURFL Pro for the open sourced code.


--

Armand

Thanks to Armand for all your work on pywurfl - it's been invaluable.

One thing that would help with ports like this would be a regression test for UA
strings to wurfl IDs.  This could be quite simple e.g. a CSV file with lots of
different "real life" UA strings and the value returned by the current API.

That would make validating that other implementations have got the algorithms
right easier, and also allow regressions etc to be spotted easily.

Does such a thing exist, or would someone with a suitable set of UA strings + a
copy of the Java API be prepared to knock one up?

Cheers,

Malcolm

First I would like to thanks all the developers of this project to develop such a wondering project for mobile device. I develop a wap portal for games. My problem is to detect  handset device perfectly. My games provider provide me the handset list like this:

Nokia6300, SGH-X200, MOT-C261, SIE-CX70, SAMSUNG-SGH-Z140

So, I have to detect the supported games for the particular wap user.

I can easily detect the handset for nokia devices using below command:

$brand_name = $wurflObj->getDeviceCapability("brand_name

");

$model_name = $wurflObj->getDeviceCapability("model_name

");

$handset=$brand_name. $model_name;

//Nokia6300,Nokia6600 etc.

But the problem is for siemence ,Motorola ,some Samsung sets,and lot of others.

Let say the user agent:

SIE-CX70/36 UP.Browser/7.0.2.2.156(GUI) MMP/2.0 Profile/MIDP-2.0 Configuration/CLDC-1.1

Provide me the model name: CX70 and Brand Name: Siemens

So if I concatenate then get the value: SiemensCX70.But the actual is: SIE-CX70. 

So, Information mis-match.

Now my question is how can I detection the perfect handset.

Please help me to retrieve the actual info.

If it's  new be question I m sorry for that

Thanks

Jaferson riad

Hi Malcolm,

What I did was scrape this page:

http://www.tera-wurfl.com/tera_wurfl_test/tera_wurfl_test.php

Then ran pywurfl with the two step algo against the user agents and checked to
see what wurfl id I got back. 90% were exact matches, the rest were very close.
Here's an example of what was close:

user agent
tera wurfl | pywurfl

MOT-A-2B/00.03 UP.Browser/4.1.27a1 UP.Link/5.1.2.16
mot_i830_ver1_sub0000 | mot_i830_ver1_sub0001

MOT-A-2B/01.02 UP.Browser/4.1.27a1 UP.Link/5.1.2.16
mot_i830_ver1_sub0000 | mot_i830_ver1_sub0001

MOT-A-2B/01.06 UP.Browser/4.1.27a1 UP.Link/5.1.2.16
mot_i830_ver1_sub0000 | mot_i830_ver1_sub0001

MOT-V3/0E.41.C3R MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0
UP.Link/6.3.1.17.0
mot_v3_ver1_sub0e4039r | mot_v3_ver1_sub0e403er

MOT-V3/0E.41.C3R MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0
UP.Link/6.3.1.17.06.3.1.17.0
mot_v3_ver1_sub0e4039r | mot_v3_ver1_sub0e403er

Nokia3110c/2.0 (07.21) Profile/MIDP-2.0 Configuration/CLDC-1.1
nokia_3110c_ver1_sub0491 | nokia_3110c_ver1_sub0501

Nokia6030/2.0 (5.11) Profile/MIDP-2.0 Configuration/CLDC-1.1 Novarra-Vision/7.3
nokia_6030_ver1_suby341 | nokia_6030_ver1_sub343

Nokia6030/2.0 (5.40) Profile/MIDP-2.0 Configuration/CLDC-1.1
nokia_6030_ver1_suby341 | nokia_6030_ver1_sub343


I didn't check what version of the wurfl that tera-wurfl was using to generate
that page.


I just noticed that one in my logs does look erroneous:

Motorola RAZR V3x
mot_a1000_ver1_subua | generic


So when I have time, I'll have to check that out. I'll send you the files that I
used.

--

Armand

Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en) AppleWebKit/534.1+ (KHTML, like
Gecko) Version/6.0.0.135 Mobile Safari/534.1+

http://www.blackberry.net/go/mobile/profiles/uaprof/9800_edge/6.0.0.rdf

I didn't find it in wurfl_db.

New root?

BR, Rok.

Hi Rok

Yeah, you're right! This is the newest Blackberry device running Blackberry 6 OS: Blackberry Torch 

BR,
Igor

--- In wmlprogramming@yahoogroups.com, "Rok" <san.liaonovak@...> wrote:
>
> Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en) AppleWebKit/534.1+ (KHTML, like Gecko) Version/6.0.0.135 Mobile Safari/534.1+
>
> http://www.blackberry.net/go/mobile/profiles/uaprof/9800_edge/6.0.0.rdf
>
> I didn't find it in wurfl_db.
>
> New root?
>
> BR, Rok.
>

Hi Cristiano,

Yes, RIM already published them. You also can check the UAProf and the Torch specifications.

BR,
Igor

--- In wmlprogramming@yahoogroups.com, Cristiano Diniz da Silva <cristiano@...> wrote:
>
> Do you have more info on it? Like screen size and resolution?
>
> Cristiano Diniz da Silva
>
> ________________________________
> Web Development & Solutions
> http://mcloide.wordpress.com
> PHP Series - http://www.amazon.com/gp/product/0557374022/
> PHP Series (pdf) -
> http://www.lulu.com/product/file-download/php-series---the-encore-beginner-version/6499638
>
> p. + 1 954 840 4010
> c. + 1 561 809 1928
> Coral Springs, Fl
> PHP5 Zend Certified Engineer
> Before printing, just keep in mind your commitment with the environment!
>
>
>
>
>
> ________________________________
> From: igorlemasson le_masson@...
> To: wmlprogramming@yahoogroups.com
> Sent: Mon, August 9, 2010 11:11:23 AM
> Subject: [wmlprogramming] Re: New BlackBerry user agents
>
>
> Hi Rok
> Yeah, you're right! This is the newest Blackberry device running Blackberry 6
> OS: Blackberry Torch
>
> BR,
> Igor
>
> --- In wmlprogramming@ yahoogroups. com, "Rok" <san.liaonovak@ ...> wrote:
> >
> > Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en) AppleWebKit/ 534.1+ (KHTML,
> >like Gecko) Version/6.0. 0.135 Mobile Safari/534.1+
> >
> > http://www.blackber ry.net/go/ mobile/profiles/ uaprof/9800_ edge/6.0. 0.rdf
> >
> > I didn't find it in wurfl_db.
> >
> > New root?
> >
> > BR, Rok.
> >
>

[just back from a few days off]

Jeferson, I support what Alejandro wrote 100%.

Just stressing a more general point. Every mobile project/application
tends to be one off. One of the largest challenges in managing WURFL is
making sure that it stays relevant for most people, by avoiding that
single contributors bend everyone's data in one specific directions.

In your case, you'll need to figure out a way to map *your* list of
devices to device profiles in *everyone's* WURFL

cheers

Luca



Alejandro Guerrieri wrote:
>
> What you call the "perfect handset" is just your game provider's
> naming convention.
>
> You either need to:
>
> a) Use a WURFL patch file to override the values one by one (tedious
> and error prone).
> b) Do a translation table to convert from WURFL's brand and model to
> your provider's proprietary naming convention (I'd recommend this
> approach).
> c) Rename your provider's device names to match WURFL's concatenated
> brand+model (assuming you hold that information locally and are
> willing to maintain it current across updates).
>
> As I said, I'd recommend the #2 as the cleaner and more maintainable.
>
> Regards,
>
> Alex
>
>
> On Tue, Aug 10, 2010 at 3:39 PM, riad hasan <riad_edu_info@...
> <mailto:riad_edu_info@...>> wrote:
>
>
>     Is their no body can give me the solution?or any guideline to
>     retrieve from the problem?
>
>     Jeferson Riad
>
>     ------------------------------------------------------------------------
>     *From:* riad_edu_info <riad_edu_info@...
>     <mailto:riad_edu_info@...>>
>     *To:* wmlprogramming@yahoogroups.com
>     <mailto:wmlprogramming@yahoogroups.com>
>     *Sent:* Thu, August 5, 2010 4:19:28 PM
>     *Subject:* [wmlprogramming] Proper Handset Detection
>
>
>
>     Dear All,
>
>
>
>     First I would like to thanks all the developers of this project to
>     develop such a wondering project for mobile device. I develop a
>     wap portal for games. My problem is to detect  handset device
>     perfectly. My games provider provide me the handset list like this:
>
>
>
>     Nokia6300, SGH-X200, MOT-C261, SIE-CX70, SAMSUNG-SGH-Z140
>
>
>
>     So, I have to detect the supported games for the particular wap user.
>
>
>
>     I can easily detect the handset for nokia devices using below command:
>
>
>
>     $brand_name = $wurflObj->getDeviceCapability("brand_name
>
>     ");
>
>     $model_name = $wurflObj->getDeviceCapability("model_name
>
>     ");
>
>
>
>     $handset=$brand_name. $model_name;
>
>
>
>     //Nokia6300,Nokia6600 etc.
>
>
>
>     But the problem is for siemence ,Motorola ,some Samsung sets,and
>     lot of others.
>
>     Let say the user agent:
>
>
>
>     SIE-CX70/36 UP.Browser/7.0.2.2.156(GUI) MMP/2.0 Profile/MIDP-2.0
>     Configuration/CLDC-1.1
>
>
>
>     Provide me the model name: CX70 and Brand Name: Siemens
>
>     So if I concatenate then get the value: SiemensCX70.But the actual is:
SIE-CX70.
>
>     So, Information mis-match.
>
>
>
>     Now my question is how can I detection the perfect handset.
>
>     Please help me to retrieve the actual info.
>
>
>
>     If it's  new be question I m sorry for that
>
>
>
>     Thanks
>
>     Jaferson riad
>
>
>
>
>
>
>

Found a post about Tera-Wurfl:
http://labs.thesedays.com/2010/07/29/an-easy-way-to-detect-mobile-devices/

djn



--
-----------------------------------------
Dejan Kozina Web design studio
Dolina 346 (TS) - I-34018 Italy
tel./fax: +39 040 228 436 - cell.: +39 348 7355 225 skype: dejankozina
http://www.kozina.com/  - e-mail: dejan@...

Good one Armand. Please do send the files you used as I have to make a
decision between using the remote webservice of terawurfl and pywurfl
for a django-based app and I want to have an idea of the performance
of each in terms of speed.

Thanks.

On 8/7/10, itukaj <itukaj@...> wrote:
>
>
> Hi Malcolm,
>
> What I did was scrape this page:
>
> http://www.tera-wurfl.com/tera_wurfl_test/tera_wurfl_test.php
>
> Then ran pywurfl with the two step algo against the user agents and checked
> to see what wurfl id I got back. 90% were exact matches, the rest were very
> close. Here's an example of what was close:
>
> user agent
> tera wurfl | pywurfl
>
> MOT-A-2B/00.03 UP.Browser/4.1.27a1 UP.Link/5.1.2.16
> mot_i830_ver1_sub0000 | mot_i830_ver1_sub0001
>
> MOT-A-2B/01.02 UP.Browser/4.1.27a1 UP.Link/5.1.2.16
> mot_i830_ver1_sub0000 | mot_i830_ver1_sub0001
>
> MOT-A-2B/01.06 UP.Browser/4.1.27a1 UP.Link/5.1.2.16
> mot_i830_ver1_sub0000 | mot_i830_ver1_sub0001
>
> MOT-V3/0E.41.C3R MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0
> UP.Link/6.3.1.17.0
> mot_v3_ver1_sub0e4039r | mot_v3_ver1_sub0e403er
>
> MOT-V3/0E.41.C3R MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0
> UP.Link/6.3.1.17.06.3.1.17.0
> mot_v3_ver1_sub0e4039r | mot_v3_ver1_sub0e403er
>
> Nokia3110c/2.0 (07.21) Profile/MIDP-2.0 Configuration/CLDC-1.1
> nokia_3110c_ver1_sub0491 | nokia_3110c_ver1_sub0501
>
> Nokia6030/2.0 (5.11) Profile/MIDP-2.0 Configuration/CLDC-1.1
> Novarra-Vision/7.3
> nokia_6030_ver1_suby341 | nokia_6030_ver1_sub343
>
> Nokia6030/2.0 (5.40) Profile/MIDP-2.0 Configuration/CLDC-1.1
> nokia_6030_ver1_suby341 | nokia_6030_ver1_sub343
>
>
> I didn't check what version of the wurfl that tera-wurfl was using to
> generate that page.
>
>
> I just noticed that one in my logs does look erroneous:
>
> Motorola RAZR V3x
> mot_a1000_ver1_subua | generic
>
>
> So when I have time, I'll have to check that out. I'll send you the files
> that I used.
>
> --
>
> Armand
>
>
>


--
Tim Akinbo

I recently got my hands on a Nokia 5130 XpressMusic that had UC
Browser installed on it. While checking the wurfl database and
t.wurfl.com, I noticed that UCWEB and UC Browser form part of the user
agent for this device (though they represent the same browser) and I
was curious to understand how detection is done for these browser
types.

An example of a user agent is:
Nokia5130c-2/2.0 (07.91) Profile/MIDP-2.1 Configuration CLDC-1.1
nokia5130c-2/UCWEB7.1.0.42/69/351 UNTRUSTED/1.0



--
Tim Akinbo

Hi List,

I got a problem when identifying an iPhone 4.
So does Tera Wurfl: http://bit.ly/9VT1UH .
Why do I get 320 as the resolution_width? Isn't it 960?

Best regards,

Bruno Verachten

Hi Maximiliano,

> Check this post about iPhone 4 detection
> http://www.mobilexweb.com/blog/iphone4-ios4-detection-safari-
> viewport
Thanks a lot for this link.

Best regards,

Bruno Verachten

That fact that it says UNTRUSTED makes me think that the bropwser is actually a
midlet.

Does anyone know more about what the browser is and whether it comes
pre-installed on devices (Nokia or otherwise)?

also, can you capture a full set of headers at http://db.wurflpro.com/h

thank you

Luca

On 13/08/2010 10.15, Tim Akinbo wrote:
>
> I recently got my hands on a Nokia 5130 XpressMusic that had UC
> Browser installed on it. While checking the wurfl database and
> t.wurfl.com, I noticed that UCWEB and UC Browser form part of the user
> agent for this device (though they represent the same browser) and I
> was curious to understand how detection is done for these browser
> types.
>
> An example of a user agent is:
> Nokia5130c-2/2.0 (07.91) Profile/MIDP-2.1 Configuration CLDC-1.1
> nokia5130c-2/UCWEB7.1.0.42/69/351 UNTRUSTED/1.0
>

Yep, I agree too.

On my previous job we worked with several game providers, and each of
them handled different conventions for the handsets models, it was a
real pain.

Something more automatic could be handled, but mostly due to the fact
that even the same provider used different names for the same handset
on different games, we ended up creating a web interface where we
manually selected the devices which were compatible for each game,
associating them to the WURFL devices.

Regards,

Juan


On Wed, Aug 11, 2010 at 7:36 AM, Luca Passani <luca.passani@...> wrote:
>
> [just back from a few days off]
>
> Jeferson, I support what Alejandro wrote 100%.
>
> Just stressing a more general point. Every mobile project/application
> tends to be one off. One of the largest challenges in managing WURFL is
> making sure that it stays relevant for most people, by avoiding that
> single contributors bend everyone's data in one specific directions.
>
> In your case, you'll need to figure out a way to map *your* list of
> devices to device profiles in *everyone's* WURFL
>
> cheers
>
> Luca
>
>
>
> Alejandro Guerrieri wrote:
>>
>> What you call the "perfect handset" is just your game provider's
>> naming convention.
>>
>> You either need to:
>>
>> a) Use a WURFL patch file to override the values one by one (tedious
>> and error prone).
>> b) Do a translation table to convert from WURFL's brand and model to
>> your provider's proprietary naming convention (I'd recommend this
>> approach).
>> c) Rename your provider's device names to match WURFL's concatenated
>> brand+model (assuming you hold that information locally and are
>> willing to maintain it current across updates).
>>
>> As I said, I'd recommend the #2 as the cleaner and more maintainable.
>>
>> Regards,
>>
>> Alex
>>
>>
>> On Tue, Aug 10, 2010 at 3:39 PM, riad hasan <riad_edu_info@...
>> <mailto:riad_edu_info@...>> wrote:
>>
>>
>>     Is their no body can give me the solution?or any guideline to
>>     retrieve from the problem?
>>
>>     Jeferson Riad
>>
>>     ------------------------------------------------------------------------
>>     *From:* riad_edu_info <riad_edu_info@...
>>     <mailto:riad_edu_info@...>>
>>     *To:* wmlprogramming@yahoogroups.com
>>     <mailto:wmlprogramming@yahoogroups.com>
>>     *Sent:* Thu, August 5, 2010 4:19:28 PM
>>     *Subject:* [wmlprogramming] Proper Handset Detection
>>
>>
>>
>>     Dear All,
>>
>>
>>
>>     First I would like to thanks all the developers of this project to
>>     develop such a wondering project for mobile device. I develop a
>>     wap portal for games. My problem is to detect  handset device
>>     perfectly. My games provider provide me the handset list like this:
>>
>>
>>
>>     Nokia6300, SGH-X200, MOT-C261, SIE-CX70, SAMSUNG-SGH-Z140
>>
>>
>>
>>     So, I have to detect the supported games for the particular wap user.
>>
>>
>>
>>     I can easily detect the handset for nokia devices using below command:
>>
>>
>>
>>     $brand_name = $wurflObj->getDeviceCapability("brand_name
>>
>>     ");
>>
>>     $model_name = $wurflObj->getDeviceCapability("model_name
>>
>>     ");
>>
>>
>>
>>     $handset=$brand_name. $model_name;
>>
>>
>>
>>     //Nokia6300,Nokia6600 etc.
>>
>>
>>
>>     But the problem is for siemence ,Motorola ,some Samsung sets,and
>>     lot of others.
>>
>>     Let say the user agent:
>>
>>
>>
>>     SIE-CX70/36 UP.Browser/7.0.2.2.156(GUI) MMP/2.0 Profile/MIDP-2.0
>>     Configuration/CLDC-1.1
>>
>>
>>
>>     Provide me the model name: CX70 and Brand Name: Siemens
>>
>>     So if I concatenate then get the value: SiemensCX70.But the actual is:
SIE-CX70.
>>
>>     So, Information mis-match.
>>
>>
>>
>>     Now my question is how can I detection the perfect handset.
>>
>>     Please help me to retrieve the actual info.
>>
>>
>>
>>     If it's  new be question I m sorry for that
>>
>>
>>
>>     Thanks
>>
>>     Jaferson riad
>>
>>
>>
>>
>>
>>
>>
>
>
>
> ------------------------------------
>
> As of July 14 2005, it's much easier to be banned from WMLProgramming!
> Please fail to read http://tech.groups.yahoo.com/group/wmlprogramming/ before
you post.Yahoo! Groups Links
>
>
>
>



--
Juan Nin
3Cinteractive / Mobilizing Great Brands
http://www.3cinteractive.com

This one is fresh out of the presses:
http://jquerymobile.com/2010/08/announcing-the-jquery-mobile-project/

djn


--
-----------------------------------------
Dejan Kozina Web design studio
Dolina 346 (TS) - I-34018 Italy
tel./fax: +39 040 228 436 - cell.: +39 348 7355 225 skype: dejankozina
http://www.kozina.com/  - e-mail: dejan@...

Interesting stuff. My impression is that this (and similar jQuery-based
libraries) are suited for Applications, more than mobile websites.

If these libraries are successful, we may support them in WURFL with
capabilities which indicate which version of the library should be used on which
device.

Luca



On 14/08/2010 8.07, Dejan Kozina wrote:
>
> This one is fresh out of the presses:
> http://jquerymobile.com/2010/08/announcing-the-jquery-mobile-project/
>
> djn
>
> --
> -----------------------------------------
> Dejan Kozina Web design studio
> Dolina 346 (TS) - I-34018 Italy
> tel./fax: +39 040 228 436 - cell.: +39 348 7355 225 skype: dejankozina
> http://www.kozina.com/ - e-mail: dejan@... <mailto:dejan%40kozina.com>
>
>

People, we need to move the WURFL schema to something a bit more "structured".
In the future, we will be able to build more powerful tools because of this.

The <device> object is currently "overloaded" in WURFL, since it represents both
devices (for ex: nokia_n97_ver1) and families of devices (for ex:
nokia_generic_series60).

The convention which we are going to enforce applies to <device> elements when
it represents families.

- the UA string will have form DO_NOT_MATCH_* (for ex:
DO_NOT_MATCH_NOKIA_SERIES60_DP_3_0)

- the ID will contain the substring "generic" (for ex: ms_mobile_browser_ver1 =>
generic_ms_mobile_browser_ver1)

This convention has already been used for some time. What we will do is to
change the family IDs that do not comply and make them consistent with this
rule.

This change is not supposed to impact WURFL users who will upgrade to the newer
WURFL, but it may impact your patches, so be aware of this next time you
upgrade.

Steve, if you wish, we can sync off-line about IDs hard-wired in our APIs.

Thank you

Luca