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.

Sign up for GitHub

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

Jump to bottom

startsWith() on null object at ScreenEncoder.java:158 #365

Closed
SwayChen opened this issue Dec 4, 2018 · 8 comments
Closed

startsWith() on null object at ScreenEncoder.java:158 #365

SwayChen opened this issue Dec 4, 2018 · 8 comments
Labels
device

Comments

@SwayChen
Copy link

SwayChen commented Dec 4, 2018

Model: Meizu 16th
OS: Flyme 7.1.1.2A base on Android 8.1.0

log like this:

MacBook-Pro:~ allconnected$ scrcpy
/usr/local/Cellar/scrcpy/1.5/share/scrcpy/scrcpy-server.jar: 1 file pushed. 1.2 MB/s (19308 bytes in 0.016s)
ERROR: Exception on thread Thread[main,5,main]
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.startsWith(java.lang.String)' on a null object reference
	at android.media.MediaCodec.configure(MediaCodec.java:1918)
	at android.media.MediaCodec.configure(MediaCodec.java:1873)
	at com.genymobile.scrcpy.ScreenEncoder.configure(ScreenEncoder.java:158)
	at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:68)
	at com.genymobile.scrcpy.Server.scrcpy(Server.java:25)
	at com.genymobile.scrcpy.Server.main(Server.java:109)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:285)
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
Invalid return value 0 for stream protocol
2018-12-04 10:17:42.744 scrcpy[1111:16013] ERROR: Could not open video stream
2018-12-04 10:17:42.789 scrcpy[1111:15936] INFO: Initial texture: 1080x2160
@rom1v rom1v added the device label Dec 4, 2018
@thinkhy
Copy link

thinkhy commented Jun 18, 2019

Refer for the blog for a workable fix: https://www.jianshu.com/p/0d29cc53199c

@SwayChen
Copy link
Author

SwayChen commented Aug 9, 2019

Thanks for temporary solution by @thinkhy

@SwayChen SwayChen closed this as completed Aug 9, 2019
@Jingle-seven
Copy link

meizu biss

rom1v pushed a commit that referenced this issue Nov 13, 2019
@act262 @rom1v
Fix meizu 16th NPE
d61c2ab 
Fill AppInfo to avoid NullPointerException on some devices.

Fixes <#365>

Signed-off-by: Romain Vimont <rom@rom1v.com>
@rom1v rom1v mentioned this issue Nov 13, 2019
Closed
@rom1v
Copy link
Collaborator

rom1v commented Nov 13, 2019

See #888

@rom1v
Copy link
Collaborator

rom1v commented Nov 13, 2019

Could you please replace scrcpy-server.jar in your scrcpy v1.10 and test again?
SHA256: b34c8ce7f8f60e6d6ef42c3b0975c6b7650755f2d50205a2e950f996e2091bbc

@SwayChen
Copy link
Author

SwayChen commented Nov 15, 2019 •
edited

@rom1v Yep, it works fine with v1.10. Thanks!

Scrcpy Version
Meizu Device Info

@rom1v
Copy link
Collaborator

rom1v commented Nov 15, 2019 •
edited

Thank you for your feedbacks, I just merged it in dev 👍

It will be in the v1.11 release (the version number is still 1.10 but it's not the 1.10 release, it's a dev version).

This was referenced Nov 15, 2019
Closed
Closed
rom1v pushed a commit that referenced this issue Nov 19, 2019
@act262 @rom1v
Fix meizu 16th NPE
9029324 
Fill AppInfo to avoid NullPointerException on some devices.

Fixes <#365>

Signed-off-by: Romain Vimont <rom@rom1v.com>
@rom1v rom1v mentioned this issue Nov 21, 2019
Closed
@rom1v
Copy link
Collaborator

rom1v commented Apr 30, 2020 •
edited

To fix #994, I changed the way the workaround is called.

Could you please take scrcpy v1.13 and replace this file:

scrcpy-server
SHA256: b64e6672eeb2b7c00c6f83673783bd8839ba65ea2ac7edcdeeca44676047328b

and confirm that it works without any error message.

Thank you.

rom1v added a commit that referenced this issue May 2, 2020
@rom1v
Apply workarounds only on error
62c0c13 
To avoid NullPointerException on some devices, workarounds have been
implemented. But these workaround produce (harmless) internal errors
causing exceptions to be printed in the console.

To avoid this problem, apply the workarounds only if it fails without
them.

Fixes #994 <#994>
Refs #365 <#365>
Refs #940 <#940>
@rom1v rom1v mentioned this issue Jun 11, 2020
Closed
@rom1v rom1v mentioned this issue Aug 18, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
device
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@thinkhy @rom1v @SwayChen @Jingle-seven