@Joe On a side-note: What do you mean by "support for multi-SIM phones"? And by that I mean, what doesn't Cordova already support in these? Also, phones with more than one SIM slots are very common here in Brazil and even some places in Europe, so you might not have to visit India for that ;)
2015-04-10 13:56 GMT-03:00 Carlos Santana <csantan...@gmail.com>: > Thanks Joe for the explanation ! > > On Fri, Apr 10, 2015 at 11:10 AM, Joe Bowser <bows...@gmail.com> wrote: > > > On Thu, Apr 9, 2015 at 6:31 AM Carlos Santana <csantan...@gmail.com> > > wrote: > > > > > On Tue, Apr 7, 2015 at 8:30 PM, Joe Bowser <bows...@gmail.com> wrote: > > > > > > > Sorry, I mis-read this e-mail. Does this Race Condition happen on > > > Lollipop > > > > proper, or just on L. If it's just on L, this isn't a priority > > because L > > > > is not a release meant to go to any users, just a Developer Preview. > > > > > > > > > Joe sorry my ignorance on Android land :-p > > > But L to me is Lollipop, and the final API is 21 and is release and in > > the > > > wild for users. > > > http://developer.android.com/preview/index.html > > > > > > > > There was a Developer Preview called L that was released six months > before > > Lollipop. The API target was L, and this was only available on the Nexus > > devices as a dev image and not intended for end users, or even OEMs. > > Developer previews are rare in Android, and usually a release process > goes > > something like this: > > > > - Source Code Drop in AOSP > > - API Release with Emulators > > - Roll out to Nexus Devices > > > > As far as getting to real world devices, that's all in relation to the > > speed of the OEM to get the image completed. Each OEM needs to polish > > their version of Android so that it differentiates from the others, and > > make sure that Android actually works on their phone. > > > > > > > I think API 22 is even out. > > > Which is the API that is not out? Some sort of API 23 beta/preview? > > > > > > > > No idea. Andrew already upped the API level to 22, which is Android 5.1. > > In related news, It may make sense to create an issue to add support for > > multi-SIM phones, but of course nobody has one AFAIK since they only > exist > > in India. > > > > > > > +1 setting cordova target to 22 > > > > > > > > > > > > > > > > On Tue, Apr 7, 2015 at 5:27 PM Nikhil Khandelwal < > nikhi...@microsoft.com > > > > > > > wrote: > > > > > > > > > The JIRA which was marked as 'Won't fix' is currently blocking > > Android > > > > > test runs on http://ci.cordova.io: https://issues.apache.org/ > > > > > jira/browse/CB-8431. > > > > > > > > > > It looks like Android L's implementation of OkHttp has a race > > condition > > > > > which hits quite consistently with our current file transfer tests. > > > There > > > > > is a comment by Andrew in the bug that points to using this plugin > on > > > > > Android L: > https://github.com/MobileChromeApps/cordova-plugin-okhttp > > . > > > > > > > > > > Should this plugin be a dependency to the file transfer plugin? Or > > the > > > > > code for it be rolled in as part of file transfer plugin itself? > > > > > > > > > > For the short term I'm leaning towards working around this issue, > by > > > > using > > > > > an older AVD (instead of Android L) on our CI setup. However, there > > is > > > a > > > > > chance developers running Cordova apps on Android L will run into > > this > > > > and > > > > > would expect some guidance here. > > > > > > > > > > Thanks, > > > > > Nikhil > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Carlos Santana > > > <csantan...@gmail.com> > > > > > > > > > -- > Carlos Santana > <csantan...@gmail.com> > -- *Frederico Galvão* Diretor de Tecnologia PontoGet Inovação Web ( +55(62) 8131-5720 * www.pontoget.com.br <http://www.pontoget.com/>
