ScientiaMobile

Hi,

I have a Samsung GT-I9100 (Galaxy S II), Android 2.3.3. I am using the wurfl.xml from 2012-02-12 and Java API 1.3.1.1.

The browser of this device has a so called "View mode" option in its settings. You can set this either to "Mobile" or "Desktop". When this is set to "Mobile", the device gets detected by WURFL correctly. But, when setting to "Desktop", WURFL detects it as "samsung_gt_s5830_ver1_suban22_funnyua", where model_name is "GT-S5830" and brand_name is "Samsung".

Okay, no problem, I thought, and created a WURFL patch file as follows:
But, for some reason, this does nothing change about the device being detected wrong. I have other patch-files, which are working, too, so I think there should nothing be wrong with this one.

Could you please help me to solve this problem?

Thank you in advance.

Hi there, can you please post the offending UA string?

Anyway, version 1.4 of the API (to be released shortly) totally redesigns the Android Matcher and I suspect this will improve things.

Thank you

Luca

The UA String of the Samsung GT-I9100 "Desktop View" is "Mozilla/5.0 (Linux; U; de-de; GT-I9100 Build/GINGERBREAD) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Safari/533.1" (as shown in the patch file above).

When is the 1.4 of the API is about to be released?

We hope to release it in three weeks. If you contact offline, we may provide a preview version for you to test, as long as you are willing to give it a spin and report

Since some time passed by now, I want to provide an update:

I am using now the Java API 1.4.0.1, the WURFL from 2012-04-08 and the patch file mentioned in my first post.

The results still are the same. The "desktop view mode" of the Samsung GT-I9100 still gets detected as "samsung_gt_s5830_ver1_suban22_funnyua", where model_name is "GT-S5830" and brand_name is "Samsung".

Will there be any updates in the future that may solve this problem?

Thanks for the update. Your issue seems to be Java specific, and we are able to reproduce it here. We will find the solution and let you know once it's fixed.

We are planning a 1.4.1 release in a few weeks. We will make sure that this fix finds its way there. This issue is already fixed for Cloud users.

Thank you

The Java team has fixed this also for Java. We asked them to produce an out of band build, but we won't release it right away. We want to wait a couple of weeks and see whether there are other issues that we need to address, so the next release will be cumulative.

If this issue is absolutely killing you, please send me an email at luca @ scientiamobile... and I will send you the (binary) build. Otherwise, please wait.

Thanks

Luca

Thank you Luca for sending me the current binary build for Java. I tried it out and it solved my problem!

I am looking forward to the final release of it.