Piotr Wittchen

Thanks for reporting this issue! I'll take a look on that. Moreover, PR with this improvement is also welcome. I think, this functionality should be configurable and disabled by default...

I think, in this case, there is no need for additional strategy. Strategies are for different Android versions because, in different OS versions, network monitoring should be implemented in a...

Now, I understand your point better. Is it possible to trigger connectivity change in idle mode? Proposal with the additional receiver will trigger a change when device idle mode will...

I googled more about this issue. I'm not sure if it's possible to trigger network change in a doze (idle) mode and it may be an Android bug or intended...

That sounds more reasonable if we know for sure that network call cannot be done in Doze mode. In such case, the additional broadcast receiver makes sense. Nevertheless, I would...

Hi, It should be already fixed for the latest Android version. Regards 03.11.2017 10:53 PM "Alexander Perfilyev" napisał(a): > @pwittchen so it seems there is another > one broadcast being...

Thanks for reporting this. I'll have a look on that. I'm also open for PRs related with this issue.

Hi @Ankit0080, Under the hood library uses broadcast receivers for detecting application idle state or network change depending on the Android version installed on the device. If your activity is...

It's strange. I have never heard of such issues before. My only guess is the fact that broadcast receivers inside the library cannot work with your custom broadcast receivers, but...

You can do that now. It's described in documentation here: https://github.com/pwittchen/ReactiveNetwork#chaining-network-and-internet-connectivity-streams Sometimes, `switchMapSingle` may be a better choice than `flatMapSingle` to discard first stream.