[ 
https://issues.apache.org/jira/browse/CB-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wayne Fisher updated CB-587:
----------------------------

    Attachment: PGexample-2.0.0.zip

I have attached my v2.0.0 based example project for you to try. It is built 
using the example source from the v2.0.0 release with the only change being 
that I added the Cordova version to the title.

I exported this from eclipse, renamed my original copy and installed from this 
archive. I ran it by "Debug As" "Android Application". I started the 
accelerometer and the compass. I disabled WIFI once and it kept running (still 
updating the display). Re-enabled WIFI, went back to the app, watched it for a 
few seconds and then disabled WIFI again. This time it died.

Please try this app to see if you get the same result. Maybe there is enough 
different about the mobile-spec test that it doesn't occur there.

                
> CallbackServer.run()  SocketException on ICS 4.0.4
> --------------------------------------------------
>
>                 Key: CB-587
>                 URL: https://issues.apache.org/jira/browse/CB-587
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.4.0, 1.7.0
>         Environment: Motorola Xoom ICS 4.0.4.
> PhoneGap 1.7.0rc1 example application.
>            Reporter: Wayne Fisher
>            Assignee: Joe Bowser
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: PGexample-2.0.0.zip, log.txt
>
>
> I have recently started to see SocketExceptions from CallbackServer.run() on 
> my Motorola Xoom. I don't know exactly when it started, but it would appear 
> to line up with the update of the Xoom to ICS 4.0.4 that occurred a couple of 
> weeks (or so) ago. I don't recall seeing it on the previous version of ICS 
> (4.0.3?).
> The exception information from LogCat follows:
> {quote}
> 04-26 15:57:58.730: W/System.err(10655): java.net.SocketException: sendto 
> failed: ETIMEDOUT (Connection timed out)
> 04-26 15:57:58.730: W/System.err(10655):      at 
> libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:496)
> 04-26 15:57:58.730: W/System.err(10655):      at 
> libcore.io.IoBridge.sendto(IoBridge.java:465)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> java.net.PlainSocketImpl.write(PlainSocketImpl.java:507)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> java.net.PlainSocketImpl.access$100(PlainSocketImpl.java:46)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> java.net.PlainSocketImpl$PlainSocketOutputStream.write(PlainSocketImpl.java:269)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> java.io.OutputStream.write(OutputStream.java:82)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> java.io.DataOutputStream.writeBytes(DataOutputStream.java:156)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> org.apache.cordova.CallbackServer.run(CallbackServer.java:275)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> java.lang.Thread.run(Thread.java:856)
> 04-26 15:57:58.740: W/System.err(10655): Caused by: 
> libcore.io.ErrnoException: sendto failed: ETIMEDOUT (Connection timed out)
> 04-26 15:57:58.740: W/System.err(10655):      at 
> libcore.io.Posix.sendtoBytes(Native Method)
> 04-26 15:57:58.750: W/System.err(10655):      at 
> libcore.io.Posix.sendto(Posix.java:146)
> 04-26 15:57:58.750: W/System.err(10655):      at 
> libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:177)
> 04-26 15:57:58.750: W/System.err(10655):      at 
> libcore.io.IoBridge.sendto(IoBridge.java:463)
> 04-26 15:57:58.750: W/System.err(10655):      ... 7 more
> {quote}
> This may be related to another issue that I have noticed with ICS 4.0.4 which 
> is that it drops the WIFI connection a lot.  It drops it *WAY* more 
> frequently than the previous version did even with "Keep Wi-Fi on during 
> sleep" set to "Always".
> My app is based on PhoneGap v1.4.0. I see this exception with my app on the 
> Xoom. I have not seen it on my Samsung Galaxy S with 2.3.3 on it.
> The LogCat information above is from the 1.7.0rc1. For this test I simply 
> created a new Android application in Eclipse using the Android example code 
> as is. The exception happens even without interacting with the example app. 
> Just leave it sit there and eventually... boom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to