scrcpy
scrcpy copied to clipboard
flatpak package
Hi,I have packaged scrcpy with flatpak.You can find it in https://github.com/12wk34/scrcpy-flatpak Could you add it to flathub.org cause they require the developer to do it. The more information about app submission: https://github.com/flathub/flathub/wiki/App-Submission
Bump :slightly_smiling_face: Could you take a look at it, please?
@12wk34 Sorry for the delay.
Thank you for your work. :+1:
Could you add it to flathub.org cause they require the developer to do it.
I am happy if scrcpy is packaged for many systems, but I have no time to work/maintain them.
It seems it is not a strong requirement for the author to be involved.
If you are interested, you could maintain the flatpack package like @sisco311 does for the snap package.
However, you should not include binaries/zip of sources, but reference the links from github (and the matching sha256) from the json, so that everyone can be sure that the "flatpack recipe" builds the expected sources.
A minor remark: why do you need x264 (the encoder) and other stuff for ffmpeg? I guess --enable-decoder=h264
should be sufficient.
Hi,I have packaged scrcpy with flatpak.You can find it in https://github.com/12wk34/scrcpy-flatpak Could you add it to flathub.org cause they require the developer to do it. The more information about app submission: https://github.com/flathub/flathub/wiki/App-Submission
@12wk34 ... could you create a new PR on flathub repo ... just quote this thread there to show you have the approval of upstream(@rom1v ) ... i believe they would add it to flathub once they see that upstream is ok with it ...
Any news here?
An flatpack package is strongly appreciated…
A problem is that I dont know how to use a custom adb build. the binary from google is not free. It is what need be done before add to flathub
I guess the source code for adb should be in the AOSP project, somewhere... 😄
At least distros build this in their packages, so it has to be FLOSS. (And you may also look there, Debian or Fedora or so, how they build it.)
https://android.googlesource.com/platform/system/core.git/+/refs/heads/master/adb/
Building adb from source is a PITA.
But according to the NOTICE.txt file included in the zip from https://dl.google.com/android/repository/platform-tools_r28.0.3-linux.zip the binary is licensed under the Apache License, Version 2.0
Any news? Can't you bundle the one from the platform-tools zip file if this is using the APL-2?
Building the adb
from source would be ideal but for the time-being we can adopt the approach : https://github.com/flathub/org.godotengine.Godot/pull/38
i.e. adb needs to be present on host, and the scrcpy can run it via flatpak-spawn
Also, confirming on flatpak IRC:
<uajain> Is a binary distributable (adb from android-tools in this case) via a flatpak package, provided it's licensed under Apache license 2.0
<uajain> My reading says is OK to distribute, but am not an expert here.
<barthalion> uajain: unless binary is under different license, it's fine
@sisco311 @maggu2810 Looks like it's OK to bundle it.
Any news? I have snap installed just for scrcp, so flatpak package would be really helpful.
Sorry for the postpone.I dont think it is a goold idea to compile library like ffmpeg in each app in flathub. So i was beeing waiting.
I just push a request in flathub( https://github.com/flathub/flathub/pull/1551 ). And the build is sucess.
By the way, is there a plan to give scrcpy an icon?
By the way, is there a plan to give scrcpy an icon?
There is currently no plan to do that (no designer).
And there is already an awesome icon </troll>
Hi @rom1v , I installed SCRCPY with Flatpak, however an error happens: emanuel@emanuel:~$ flatpak run com.Genymobile.Scrcpy INFO: scrcpy 1.13 https://github.com/Genymobile/scrcpy
- daemon not running; starting now at tcp:5037
- daemon started successfully /app/share/scrcpy-server.jar: 1 file p...ped. 49.4 MB/s (27694 bytes in 0.001s) [server] INFO: Device: Xiaomi Mi A3 (Android 10) ERROR: Could not initialize parser INFO: Renderer: opengl INFO: OpenGL version: 4.6 (Compatibility Profile) Mesa 20.0.5 INFO: Trilinear filtering enabled INFO: Initial texture: 720x1560 WARN: Device disconnected Can you help me?
ERROR: Could not initialize parser
Something is very wrong.
https://github.com/Genymobile/scrcpy/blob/e99b896ae2b6a59d5f7f2b76a3dd9c29f4838013/app/src/stream.c#L217-L219
Does it work with a non-flatpak version?
ERRO: Não foi possível inicializar o analisador
Algo está muito errado.
https://github.com/Genymobile/scrcpy/blob/e99b896ae2b6a59d5f7f2b76a3dd9c29f4838013/app/src/stream.c#L217-L219
Funciona com uma versão não flatpak?
I tried on Win 7 with the same phone, same USB cable and it worked, but when I try endless End (which only accepts Flatpak) it doesn't work
I'd appreciate a Flatpak build, as I don't use Snap. Unfortunately, this issue seems to have been abandoned.
One alternative/workaround might be the flatpak version guiscrcpy
.
my note:
-
the "latest"(though released in 2021)
v4.11.3
includesscrcpy v1.24
(well I don't know why and how ... -
I did get able to use it on my Xiaomi Mi11 LE MIUI13 Android 12 Phone (take care the security setting of the phone)
-
However, after using a little while (even without much interacting), it seems usually to lag, and even crash
Not digged into yet. Some detail info:
My case is wifi, Debian 11.5 stable, KDE, and
-m 1024
.The errors are often as follows:
DEBUG: End of frames DEBUG: Receiver stopped WARN: Device disconnected DEBUG: quit... DEBUG: Server disconnected DEBUG: Server terminated
-
seems that not work when multiple devices connected ?
Some other might noteworthy things:
One alternative/workaround might be the flatpak version
guiscrcpy
.
* I did get able to use it on my Xiaomi Mi11 LE MIUI13 Android 12 Phone ([take care the security setting of the phone](https://github.com/Genymobile/scrcpy/issues/70#issuecomment-1223436139)) * However, after using a little while (even without much interacting), it seems usually to lag, and even crash
nearly months, this works okay:
- turn on the
wlan debug
option (in chinese无线调试
) (inside thedebugging
section part ofDeveloper options
), which would generate aip:port
- use
/var/lib/flatpak/app/in.srev.guiscrcpy/x86_64/stable/active/files/bin/adb
to manually connect device with the aboveip:port
- go in
guiscrcpy
, just pick the correct candidate device and start ~
NOTE: a bad thing is, the port may change ... so that need manually re-connect
Hello, since the last Flatpak packaging attempt stalled, I made another one at Fei1Yang/[email protected] which addressed two problems mentioned by Flathub maintainers in the last attempt using a wrapper script. this method works fairly well during my testing.
Regarding the adb issue, there is a more lightweight method to compile it at nmeum/android-tools (and it's being used by Fedora's Anitya project to monitor new releases for adb), but I'm not sure if a switch is necessary since the Google binary is already Apache-2.0 licensed.
If the scrcpy developers are satisfied with this manifest, I will try to submit it to flathub.
@rom1v Could you take a look at @Fei1Yang 's flatpak repackage request above? I'd really love to get a working, updated scrcpy flatpak going, and I know I'm not alone here.
Thank you very much for your time, and Fei1Yang, thank you also for your efforts.