Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: Unable to find child device via discovery if child device has screen closed/off #22

Open
Waester opened this issue Jan 22, 2025 · 3 comments

Comments

@Waester
Copy link

Waester commented Jan 22, 2025

Noticed that the discovery service does not work if the child device enters some sort of sleep mode (screen off).
If the screen is on, then the child device can be found via the discovery service.
I have turned off all identifiable battery optimization for Child Monitor on the child device, but that didnt help.
Connecting via IP always work, as far as I can tell.

Child device is running Android 12.

@enguerrand
Copy link
Owner

"Turning off battery optimization" is a mess on android in my experience, and the required steps vary greatly from vendor to vendor. Sometimes the options are hidden in submenus that are hard to discover.

I am afraid this is nothing I'll be able to help you with.
You may be able to work around the problem by keeping the screen on. There is a developer option to never turn of the screen while charging.
Since the audio streaming is pretty battery intensive I tend to keep the child device on a power cable anyway, so in combination with the above mentioned option it is easy to keep the screen on.

Let me know if this helps.

@Waester
Copy link
Author

Waester commented Jan 25, 2025

Connecting with IP works fine. (even when the child screen is off)
Just wanted to highlight that the Android Network Service Discovery (NSD) stops working in that specific use-case above and is something that maybe can be improved in the future.

@enguerrand
Copy link
Owner

Ok thanks for the clarification. That sounds weird, maybe this can indeed be improved.

It might take a while but I'll try to reproduce (and possibly fix) this when I get the chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants