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

Black screen w/ Vivo Y19C #188

Open
Yonle opened this issue Mar 5, 2022 · 12 comments
Open

Black screen w/ Vivo Y19C #188

Yonle opened this issue Mar 5, 2022 · 12 comments

Comments

@Yonle
Copy link

Yonle commented Mar 5, 2022

Device

  • Mobile (Android 8.1)
  • vivo 1820 (Y91C)
  • aarch64
  • Linux localhost 4.9.77+ #1 SMP PREEMPT Thu Jul 15 19:11:41 CST 2021 aarch64 Android (Not AVD)

MultiVNC version
2.0.7 (Play Store)

VNC server i'm connecting to

  • VNC server vendor: tigervnc
  • VNC server version: 1.10.0
  • OS version: 8.1
  • OS language: English

Describe the bug
When connected into VNC server, I only see a mouse with a black screen.

To Reproduce

  • Open MultiVNC
  • Connect to server

Expected Behavior
The remote screen shows up

Screenshots
Screenshot_20220305_150352

Other VNC client (RealVNC viewer):
Screenshot_20220305_150430

Logcat (Coming soon)

@bk138
Copy link
Owner

bk138 commented Mar 5, 2022

Thanks for the report @Yonle ! A few ideas:

  • might it be that MultiVNC shows the upper left corner of the remote screen and one has to scroll down to see the other content?
  • How would I be able to reproduce your setup? Is it termux?

@Yonle
Copy link
Author

Yonle commented Mar 6, 2022

  • might it be that MultiVNC shows the upper left corner of the remote screen and one has to scroll down to see the other content?

Does not seems that it's there.

  • How would I be able to reproduce your setup? Is it termux?

It's in termux and reproduceable with the following command:

vncserver -geometry=1280x750 -securitytypes=none -zliblevel=0 :0

Can also done with Xvfb + x11vnc:

Xvfb :0 &
x11vnc --display :0 --forever

@bk138
Copy link
Owner

bk138 commented Mar 6, 2022

I see. Do you also get a black screen when connecting to another server that's not running on localhost?

@Yonle
Copy link
Author

Yonle commented Mar 6, 2022

I see. Do you also get a black screen when connecting to another server that's not running on localhost?

Yes. I also tried to connect to my VPS VNC server, unfortunately no luck.

@bk138
Copy link
Owner

bk138 commented Mar 6, 2022

I see. Do you also get a black screen when connecting to another server that's not running on localhost?

Yes. I also tried to connect to my VPS VNC server, unfortunately no luck.

I have two ideas:

@Yonle
Copy link
Author

Yonle commented Mar 7, 2022

Hi @bk138.

  • At this point, AVNC works well as expected. Got no error at it.
  • MultiVNC 2.0.0 also result the same black remote screen. Also tried with other VNC server.

@bk138 bk138 changed the title Black screen Black screen w/ Vivo Y19C Mar 7, 2022
@bk138
Copy link
Owner

bk138 commented Mar 7, 2022

Hi @bk138.

* At this point, AVNC works well as expected. Got no error at it.

* MultiVNC 2.0.0 also result the same black remote screen. Also tried with other VNC server.

No good idea at this point. It seems it's a combination of your device model and MultiVNC. You could try looking at the adb logs and scan for any errors, but that's about it :-/

@Yonle
Copy link
Author

Yonle commented Mar 7, 2022

Hi @bk138.

* At this point, AVNC works well as expected. Got no error at it.

* MultiVNC 2.0.0 also result the same black remote screen. Also tried with other VNC server.

No good idea at this point. It seems it's a combination of your device model and MultiVNC. You could try looking at the adb logs and scan for any errors, but that's about it :-/

Well. See whenever i have a chance to get logcat error log.

@bk138
Copy link
Owner

bk138 commented Mar 8, 2022

Did a bit of googling:

@bk138
Copy link
Owner

bk138 commented Mar 8, 2022

@Yonle you could also the last version of the 1.8 series give a try. If this works, the issue might be related to the new VNC engine.

@Yonle
Copy link
Author

Yonle commented Mar 9, 2022

@Yonle you could also the last version of the 1.8 series give a try. If this works, the issue might be related to the new VNC engine.

And it actually doing it's job well

Screenshot_20220309_070356

@bk138
Copy link
Owner

bk138 commented Mar 9, 2022

Interesting! In that case, an adb log from session setup from a recent MultiVNC version probably can shed some light on this if you're interested.

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

No branches or pull requests

2 participants