Android: Server disconnects app after device sleeps. But Java socket never detects disconnection when device wakes up -


in android app have written service connects server. calling java socket .getoutputstream().write , .getinputstream().read write requests , read responses , server. plain , simple that.

everything works fine until device sleeps.

when device sleeps, server disconnects app connection. when device wakes up, app service starts running. never detects disconnected connection. .getinputstream().read keeps waiting responses forever , .getoutputstream().write writes requests socket successfuly. weird.

thus java, socket normal though disconnected server. , there no way detect same.

ideally, .getinputstream().read should return -1 after device wakes , service starts running. doesn't happen. neither .getoutputstream().write throws ioexception. , user has way stop application forcefully through app settings, not @ acceptable app perspective.

what tried?

  1. i have gone through relevant question this, this , this answers there suggests write or read socket check if still connected (like heartbeats suggested here). however, stated doesn't work in case (i.e. socket read keeps waiting , write doesn't throw exception, if socket still connected)

  2. as workaround thought of closing , reconnecting connection compulsory (regardless connected or not) after device wakes up. couldn't find specific intent device wake up. (some posts on suggested android.intent.action.screen_on device wake up. don't want reset connection every time when screen turned on. no, has device wakeup intent.)

i badly stuck , know how handle situation in many other apps stay connected servers.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more