Build issue on ARMv6 raspberry pi

[Grrrolive]

Hi,
just a question, I tried to build on a raspberry pi model 1, raspbian buster-full.
But it seems the platform isn't supported. (armv).
Is there any compatibility issue or maybe is it possible to change it ?
Maybe, into the Makefile to let the build go to the end ?
Here there are my prompt returns (username/hostname modified).
Thank you.

userpi@monraspberrypi:~/scrcpy $ meson x --buildtype release --strip -Db_lto=true
Directory already configured.

Just run your build command (e.g. ninja) and Meson will regenerate as necessary.
If ninja fails, run "ninja reconfigure" or "meson --reconfigure"
to force Meson to regenerate.

If build failures persist, run "meson setup --wipe" to rebuild from scratch
using the same options as passed when configuring the build.
To change option values, run "meson configure" instead.

userpi@monraspberrypi:~/scrcpy $ ninja -Cx
ninja: Entering directory `x'
[0/1] Generating scrcpy-server with a custom command.
Error occurred during initialization of VM
Server VM is only supported on ARMv7+ VFP
FAILED: server/scrcpy-server 
/home/pi/scrcpy/server/./scripts/build-wrapper.sh /home/pi/scrcpy/server server/scrcpy-server release
ninja: build stopped: subcommand failed.

userpi@monraspberrypi:~ $ cat /proc/cpuinfo
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2835
Revision	: 000e
Serial		: 0000000067e57ca6
Model		: Raspberry Pi Model B Rev 2

[rom1v]

$ meson x --buildtype release --strip -Db_lto=true
Directory already configured.

(when you want to do it again, just rm -rf x)

Error occurred during initialization of VM
Server VM is only supported on ARMv7+ VFP

https://www.raspberrypi.org/forums/viewtopic.php?t=212040

(You could use the prebuilt server instead)

[Grrrolive]

Thank for your fast answer, but I fear I might be lost.
I downloaded manually on the pi and even decompressed the prebuilt server but didn't succeeded when trying to " meson --reconfigure (etc...)".

In addition, I fear to erase my sd card using rm -rf x in a bad way.

Could you help me a little bit more please ?
Don't understand what does I have to do.
Maybe could you write me an example of what I could type in the prompt ?

[rom1v]

When you executed meson x … the first time, it created a directory x (in your scrcpy folder).
If you do it again, it fails, because the directory already exists:

userpi@monraspberrypi:~/scrcpy $ meson x --buildtype release --strip -Db_lto=true
Directory already configured.

Just remove it (rm -rf x).

Then, do it again with the path to the prebuilt scrcpy-server you just downloaded (without "decompressing" it):

meson x --buildtype release --strip -Db_lto=true -Dprebuilt_server=/path/to/scrcpy-server

For example, if you just downloaded it into the scrcpy folder, it's in the current directory, so just pass its name:

meson x --buildtype release --strip -Db_lto=true -Dprebuilt_server=scrcpy-server

Then build:

ninja -Cx

You can run it with ./run x.

[Grrrolive]

Thank you for your helpful answers !
Seems good !

Now, I face another issue, the device is "unauthorized".
When I launch "scrcpy", I see the error "device unauthorized".
When I try adb devices, the prompt return the number and the word "unauthorized".

After some googling, it seems I should see any popup to click, but I don't have anything.

I tried to uninstall/reinstall the packages adb, and android-tools-adb.
Using the GUI, I can access the memory of my smartphone, so I don't think it could be the drivers (my first idea).

I've found this : '#179 (comment)' but it seems not to be the same issue.

Any idea ?

[Grrrolive]

[rom1v]

https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300

[Grrrolive]

https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300

Thanks for the link, but I've tried several times, still not working.

• tried to replace the adbkey file from another pc that is working. Fail.
• other methods on this forum. Fail.

I saw somewhere that the new "ambient mode" may interfere with the security parameters, especially the screen lock and connection authorization.

I may also check the user's group as described here : https://developer.android.com/studio/run/device?hl=fr

I'll look further in these ways.