Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8CE65D343 for ; Tue, 28 May 2013 18:09:12 +0000 (UTC) Received: (qmail 44008 invoked by uid 500); 28 May 2013 18:09:12 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 43872 invoked by uid 500); 28 May 2013 18:09:12 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 43732 invoked by uid 99); 28 May 2013 18:09:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 18:09:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of maxw@google.com designates 209.85.220.179 as permitted sender) Received: from [209.85.220.179] (HELO mail-vc0-f179.google.com) (209.85.220.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 18:09:05 +0000 Received: by mail-vc0-f179.google.com with SMTP id hz10so5608008vcb.24 for ; Tue, 28 May 2013 11:08:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=/5BukUyvNu7pZrEcWLBCzXuRC73IB9N3OWpVYJuv7ks=; b=PFzSiVHOySyjL7GMgEGGE2G68f1QpiJPl51PhPfn4LFGIbRlq4yF5ZwdXSmI35PXgM YmnsiA9wXWAmyP3xTTSUn08ZPoyNVsidLNPT/+RffRHQS3W2Otgine6iQYL3CCuYx34A Mk3+/qPDWtxUAzucsepNCGR14oDvVCFu//rq5C8roGbwf55QTAJn/P5d5KcqadLxrmZ9 qAsgTtAAOqSrzGvQhQlwip59ii4+eJR/xP0bm/1CHPd6FRyRC4zMPaGiEWMGu375TmMI iDJJlemt6DCmWfU/KfqON0M7jXduURhwSwaOWyc9qfiBbAXvQzL9KIcAM3NoXpa0qdSf RF8A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=/5BukUyvNu7pZrEcWLBCzXuRC73IB9N3OWpVYJuv7ks=; b=mWuVv7LI1J3138Ihn2ftfuYupaXujF4Am78b9SDiz/3c5fvLyhkRJRVlRCPf67egPZ Xaha/U4jCtyLpkifX8TjjKYy2HbhkeL4DjS5h7DRF7gJvIX+CwxRroOeVJGfm4rO5y35 9RfDiXSDJKCxdiDaq0XhENXkV3Kp5dfTxH6lY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-gm-message-state; bh=/5BukUyvNu7pZrEcWLBCzXuRC73IB9N3OWpVYJuv7ks=; b=R0g+p/3PvZWxgKJtJlvOh3d1yUYmdH8XqCtJW5YtvIJckRnUIa9AcR1NiL/e7qyNWP Ie78uLW+gnSuURhVlsbLQrsOGDxbwXn3+C3KIGnMt+v1o+9Qu4qRSkluT99E2/FTCA4e ee1KRn+45lN+HDxhaCvg9HhTKXOheORIYlSABzxM2h6NKfPPcjX22Z2Bdgnp3OBbXe6b 46LNaRlRBXZTgn6euCL9mDjq+D2oANfHJiix3kAZZHP9Ihu+1bbiI0cAbyh0ayKDJiO0 /C7hv55qcx4q30D/Ye0Ny3k5FsmjBomnQrUve/DFuJW+gJoDEmj1R0trRJ9HRI0+vpTi R64w== X-Received: by 10.52.28.171 with SMTP id c11mr13172634vdh.18.1369764524413; Tue, 28 May 2013 11:08:44 -0700 (PDT) MIME-Version: 1.0 Sender: maxw@google.com Received: by 10.220.183.135 with HTTP; Tue, 28 May 2013 11:08:14 -0700 (PDT) In-Reply-To: References: From: Max Woghiren Date: Tue, 28 May 2013 14:08:14 -0400 X-Google-Sender-Auth: 1lO7_aiQQUUHyug5VqdBLahfIzs Message-ID: Subject: Re: Why does deviceready take a second to load on Android? To: dev Content-Type: multipart/alternative; boundary=20cf30780ae0e76ece04ddcb2755 X-Gm-Message-State: ALoCoQmF9JSVVru08ewXIqSuboe3/PWfepkLaMUkoL1dHuI+EHCmg7xIWP+5+0RhzxB8+jx30Rx3HwiyjTbkPIywkNXkhPqHRGJSOcGWserwpmJVgeHWuKc5VHu+w2jT6fWmjVlrm8nhNdznCblKaQ52hN00ZEGbsujVbpu1P2mdRExy7Iq7mlibkns+qeYqRBer7bnwI9cH X-Virus-Checked: Checked by ClamAV on apache.org --20cf30780ae0e76ece04ddcb2755 Content-Type: text/plain; charset=ISO-8859-1 It looks like Bryan was correct; the reversion of the change he linked, which was done to fix mobile-spec on ICS, fixes this problem as well. On Tue, May 28, 2013 at 1:45 PM, Brian LeRoux wrote: > createElement would fix that > > On Fri, May 24, 2013 at 1:23 PM, Bryan Higgins > wrote: > > I bet it has to do with this change to mobile-spec. > > > > By injecting the script tag, cordova.js does not load until after the DOM > > has rendered. > > > > > https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;a=commit;h=8b1fd7d49c278d43b34b4c041f1575a1a39a664d > > > > > > > > On Fri, May 24, 2013 at 9:54 AM, Braden Shepherdson >wrote: > > > >> It might be the time spent doing the plugin loading, but I'm not sure. > We > >> should instrument some of these launch steps to see how long they each > take > >> and keep an eye on them over time. Eventually and in an ideal world, the > >> timings could be collected by the CI server so we can spot any > substantial > >> increases and figure out their cause. > >> > >> Braden > >> > >> > >> On Thu, May 23, 2013 at 6:22 PM, Joe Bowser wrote: > >> > >> > Hey > >> > > >> > I just tested Cordova with the latest JS on Android and I'm noticing a > >> > pretty solid lag in how long it takes for things like the platform > >> > name, version and UUID appear. Was there a recent change to > >> > deviceReady that causes it to be noticeably slower than it used to be? > >> > I'd figure that asking is faster than reading through the commit logs > >> > and debugging this. > >> > > >> > Anyone know? > >> > > >> > Joe > >> > > >> > --20cf30780ae0e76ece04ddcb2755--