Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Screen Stream error

Open
  • Is something wrong?
#1,927 10 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, java, kotlin
Domain
cli, mobile-dev

Research direction

The report is a user asking how to point the screen-stream client at another device, with a connection-refused error and no reproduction steps. Start by checking how the RTSP endpoint URL is configured in the screen-stream example app and whether it is reachable from the device. Done means the user's question is answered or the bug is reproduced with a concrete endpoint, but the thread has gone 386 days without a maintainer reply.

Written by the indexing model from the issue text.

Description

Describe the bug
By using pedroSG94 i have to stream my screen when i start stream it shows connection refused by using what ip (10..116.74.19) is there in device i set it gives error,but when i create own ip ( onConnectionStarted: rtsp://192.168.0.165:8000/stream ) is shows connection scuess, how to connect other device with this ip

Image Image

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

  • Library version [e.g. 2.2.7]
  • Device: [e.g. Pixel 6a]
  • OS: [e.g. Android13]
  • Media server [e.g. srs, version 5.0]
  • Class used [e.g. RtmpCamera1]

Additional context
Add any other context about the problem here.

Dominant language
Kotlin
Stars
3k
Forks
946
Avg merge
4d 6h
Merged PRs (30d)
9

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pedroSG94/RootEncoder

All issues in pedroSG94/RootEncoder

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.