title: How does doze mode affect background/foreground services, with/without partial/full wakelocks?
body: <p>This is a simple question, seeing that there is a huge post about this on G+ (<a href="https://plus.google.com/+AndroidDevelopers/posts/94jCkmG4jff"><strong>here</strong></a>), and lack of information on official docs (<a href="https://developer.android.com/training/monitoring-device-state/doze-standby.html"><strong>here</strong></a> ):</p>
  
  <p>What happens to the app's services when the device goes to "doze" mode?</p>
  
  <p>What does it do to background/foreground services (bound/unbound, started/not-started), with/without partial/full wakelocks?</p>
  
  <p>What would you do, for example, in order to create a service that plays an audio stream while the device's screen is turned off? What if the audio stream is not from a local file, but from the network? </p>
  
  <p>Seeing that there was a claim by Google developer:</p>
  
  <blockquote>
    <p>Apps that have been running foreground services (with the associated
    notification) are not restricted by doze.</p>
  </blockquote>
  
  <p>-yet a lot of discussion after that, claiming this is not entirely true, I think it's quite confusing to know what special background-operations apps should do.</p>