Awesome! If you can do 1 device per ticket, that would be best. Also make sure to tag it properly as Device data. You can use the other device tickets as a guide.
Thanks again! <div>-------- Original message --------</div><div>From: Volkan YAZICI <[email protected]> </div><div>Date:11/26/2014 9:55 AM (GMT-05:00) </div><div>To: Reza Naghibi <[email protected]>, [email protected] </div><div>Cc: </div><div>Subject: Re: Samsung SM-T and SM-G Series </div><div> </div>Thanks for the quick reply Reza! Just give me a couple of more hours. I'll create a couple of JIRA tickets with hundreds of sample User-Agent strings. On Wed Nov 26 2014 at 3:22:55 PM Reza Naghibi <[email protected]> wrote: > I can make the JIRA to track this. > > > Volkan, thanks for reporting this. Regarding reporting this as a generic > Samsung, thats a valid point and good idea. Right now that would be tricky > because that conflicts with us reporting that it's a generic Android. > However, for our 2.0 release, we plan on splitting our classification > between device, os, and browser. When that happens, it would be much easier > to classify that string as a generic samsung, running android os, running a > webkit browser (or something close to that). > > > --- > > > > -------- Original message -------- > From: Werner Keil <[email protected]> > Date:11/26/2014 8:26 AM (GMT-05:00) > To: [email protected] > Cc: [email protected] > Subject: Re: Samsung SM-T and SM-G Series > > Hi, > Do you have an Apache JIRA account or could you self-register there? > > It sounds best to file a JIRA ticket for that. > > Thanks, > Werner > > Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead | > Eclipse UOMo Lead, Babel Language Champion | Apache Committer > > Twitter @wernerkeil | @UnitAPI | @JSR354 | @DeviceMap | #EclipseUOMo | > #Java_Social > | #DevOps > Skype werner.keil | Google+ gplus.to/wernerkeil > > > On Wed, Nov 26, 2014 at 2:18 PM, Volkan YAZICI <[email protected]> > wrote: > > > Hi! > > > > I am having a rough time for identifying some certain User-Agents used by > > popular Samsung SM-T and SM-G series smart phones. Below is a small > > snippet. > > > > Mozilla/5.0 (Linux; Android 4.4.2; SM-T530 Build/KOT49H) > AppleWebKit/537.36 > > (KHTML, like Gecko) Chrome/38.0.2125.114 Safari/537.36 > > Mozilla/5.0 (Linux; Android 4.4.2; SM-T530 Build/KOT49H) > AppleWebKit/537.36 > > (KHTML, like Gecko) Chrome/38.0.2125.102 Safari/537.36 > > Mozilla/5.0 (Linux; Android 4.4.2; nl-nl; SAMSUNG SM-G900F Build/KOT49H) > > AppleWebKit/537.36 (KHTML, like Gecko) Version/1.6 Chrome/28.0.1500.94 > > Mobile Safari/537.36 > > Mozilla/5.0 (Linux; Android 4.4.2; nl-nl; SAMSUNG SM-T530 Build/KOT49H) > > AppleWebKit/537.36 (KHTML, like Gecko) Version/1.5 Chrome/28.0.1500.94 > > Safari/537.36 > > > > Here I would expect DeviceMap to at least figure out the Samsung vendor. > > But it fails to parse a majority of the attributes. > > > > > Mozilla/5.0 (Linux; Android 4.4.2; SM-T530 Build/KOT49H) > > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.114 Safari/537.36 > > displayHeight = 480 > > ajax_support_inner_html = true > > is_tablet = false > > ajax_support_getelementbyid = true > > ajax_support_javascript = true > > ajax_manipulate_dom = true > > ajax_manipulate_css = true > > id = genericAndroid > > is_bot = false > > nokia_edition = 0 > > is_wireless_device = true > > ajax_support_event_listener = true > > device_os = Android > > inputDevices = touchscreen > > nokia_series = 0 > > ajax_support_events = true > > xhtml_format_as_css_property = false > > displayWidth = 320 > > image_inlining = false > > xhtml_format_as_attribute = false > > is_desktop = false > > dual_orientation = false > > > > Any thoughts? > > >
