Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am working on a similar application that runs a service that establishes a persistent TCP connection to a server upon launch in order to be able to receive messages from the server. The service does not acquire any locks. This part of the application has been implemented a while ago, and so far I haven't had any problems with not being able to receive messages from the server. After reading your question I decided to test why I wasn't having this problem.</p> <p>I thought that even if I am not holding any locks, maybe there are other applications that are, which therefore keep the CPU alive. Running <code>adb shell dumpsys</code>, I noticed that this wasn't the case: <code>mLocks.size=0</code>.</p> <p>This must mean that the application is still able to receive packets, even if the device is asleep. I could not find anything official on this, but several posts on the internet seem to agree:</p> <blockquote> <p>Although I haven’t found a good example of where this is documented, it seems that even if your phone is asleep, if data is received on the connection, your code will be woken up [...] (<a href="http://dalelane.co.uk/blog/?p=1599" rel="nofollow">source</a>)</p> </blockquote> <hr> <blockquote> <p>> Say that the device is in deep sleep and the network stack receives an incoming packet. Will that wake the device up?</p> <p>It should. (<a href="https://groups.google.com/forum/?fromgroups#!topic/android-platform/xTU1UeckGcM" rel="nofollow">source</a>)</p> </blockquote> <p>However, note that both sources recommend that you should acquire a wake lock to process the packets, in order to prevent the device from falling asleep during this processing. I don't do that in my application (maybe I should), but my processing is really short.</p> <p>When you say that your requests are not reaching your application, are you sure that they aren't? Maybe they are, but your application falls asleep before it can send a reply? Try acquiring the wake lock when you receive data on your socket and releasing it after you are done with your processing.</p>
    singulars
    1. This table or related slice is empty.
    1. POUDP/RTCP Packets not reaching Device/Application Whens device screen is Locked
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USArtyom
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COtotally agree with @Artyom . I guess his problem is using of native code for "all business logic of login/Logout etc.." - meaning everything! That is why he is keeping WAKE_LOCK too long, which of course drain battery..
      singulars
      1. PO
      1. USEwoks
    2. COBut application works on S2 Device like charm!! Issue is with Samsung Rugby Smart I847
      singulars
      1. PO
      1. USNitZRobotKoder
    3. CO@NitZRobotKoder Maybe on S2 the device stays awake long enough for your processing to finish. Have you tried what I suggested in my answer?
      singulars
      1. PO
      1. USArtyom
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload