Just a quick note: Android 2.3 and Windows Phone 7.5 (IE 9) devices have no software upgrade path; we can only wait for them to fall out of the market as devices get replaced. [Well technically Android 2.3 users could run Firefox, but getting people to switch browsers on mobile is hard!

this mean there's a lot of people who aren't turning on updates on their phone and are using an old version that shipped with the phone? Or is there something else holding back updates on some devices? With Chrome and Firefox on fast release cycles, it can be a pain to support old bugs...

From: https://github.com/bestiejs/platform.js/issues/29 "the new S4 stock browser is actually using a bastardized version of Chrome Mobile, but locked at version 18.0.1025.308". they quote the ua as: "Mozilla/5.0 (Linux; Android 4.2.2; en-au; SAMSUNG GT-I9500 Build/JDQ39) AppleWebKit/535.19 (KHTML, like Gecko) Version/1.0 Chrome/18.0.1025.308 Mobie Safari/535.19" This UA might easily be mistaken for the vanilla version of Chrome.. There might be more browsers like that. Thank you manufacterers. DJ On Wed, Apr 23, 2014 at 7:59 PM, Juliusz Gonera <jgonera(a)wikimedia.org> wrote: > Brion Vibber wrote: > >> Just a quick note: Android 2.3 and Windows Phone 7.5 (IE 9) devices >> have >> no software upgrade path; we can only wait for them to fall out of the >> market as devices get replaced. [Well technically Android 2.3 users >> could >> run Firefox, but getting people to switch browsers on mobile is hard! >> > > I know, but I'm not too worried about IE9. Its usage is already pretty > low. > When it comes to Android 2.3 a few months ago I had an idea of showing > banners to its users suggesting that they upgrade to Firefox. I'll > push more > for it so that we find some time to actually get it done. It should > not be > too difficult and I'd be curious to see if it improves Firefox metrics. > > > I'm also a little worried to see old versions of Chrome in there; does >> this mean there's a lot of people who aren't turning on updates on >> their >> phone and are using an old version that shipped with the phone? Or is >> there >> something else holding back updates on some devices? With Chrome and >> Firefox >> on fast release cycles, it can be a pain to support old bugs... >> > > I'm also not sure where this comes from. I'd wait and see if it > changes in > the next few months. If it doesn't, we could investigate why Chrome > Mobile > 18 and not any other old version is that popular. > > > -- > Juliusz > > _______________________________________________ > Mobile-l mailing list > Mobile-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mobile-l >

Juliusz, did this get posted to a wiki yet? On Fri, Apr 25, 2014 at 1:15 PM, Juliusz Gonera &lt;jgonera(a)wikimedia.org&gt; wrote: > Interesting. And sad. Thanks for tracking that down. > > > > On 04/24/2014 04:34 AM, Derk-Jan Hartman wrote: > >> From: https://github.com/bestiejs/platform.js/issues/29 >> "the new S4 stock browser is actually using a bastardized version of >> Chrome Mobile, but locked at version 18.0.1025.308". >> >> they quote the ua as: "Mozilla/5.0 (Linux; Android 4.2.2; en-au; >> SAMSUNG GT-I9500 Build/JDQ39) AppleWebKit/535.19 (KHTML, like Gecko) >> Version/1.0 Chrome/18.0.1025.308 Mobie Safari/535.19" >> >> This UA might easily be mistaken for the vanilla version of Chrome.. >> There might be more browsers like that. Thank you manufacterers. >> >> DJ >> >> >> On Wed, Apr 23, 2014 at 7:59 PM, Juliusz Gonera < >> jgonera(a)wikimedia.org&gt; wrote: >> >>> Brion Vibber wrote: >>> >>>> Just a quick note: Android 2.3 and Windows Phone 7.5 (IE 9) devices >>>> have >>>> no software upgrade path; we can only wait for them to fall out of >>>> the >>>> market as devices get replaced. [Well technically Android 2.3 users >>>> could >>>> run Firefox, but getting people to switch browsers on mobile is >>>> hard! >>>> >>> >>> I know, but I'm not too worried about IE9. Its usage is already >>> pretty low. >>> When it comes to Android 2.3 a few months ago I had an idea of >>> showing >>> banners to its users suggesting that they upgrade to Firefox. I'll >>> push more >>> for it so that we find some time to actually get it done. It should >>> not be >>> too difficult and I'd be curious to see if it improves Firefox >>> metrics. >>> >>> >>> I'm also a little worried to see old versions of Chrome in there; >>>> does >>>> this mean there's a lot of people who aren't turning on updates on >>>> their >>>> phone and are using an old version that shipped with the phone? Or >>>> is there >>>> something else holding back updates on some devices? With Chrome >>>> and Firefox >>>> on fast release cycles, it can be a pain to support old bugs... >>>> >>> >>> I'm also not sure where this comes from. I'd wait and see if it >>> changes in >>> the next few months. If it doesn't, we could investigate why Chrome >>> Mobile >>> 18 and not any other old version is that popular. >>> >>> >>> -- >>> Juliusz >>> >>> _______________________________________________ >>> Mobile-l mailing list >>> Mobile-l(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/mobile-l >>> >> > > _______________________________________________ > Mobile-l mailing list > Mobile-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mobile-l > -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687