After applying a System Update (can't remember if that's the correct term) Waydroid no longer starts, dmesg is filled with constant messages like
[ 3427.920971] binder: 6467:6323 cannot find target node [ 3427.920984] binder: 6323:6467 transaction call to 0:0 failed 5324/29189/-22, size 0-0 line 3151 [ 3428.718964] binder: 952:952 cannot find target node [ 3428.718977] binder: 952:952 transaction call to 0:0 failed 5325/29189/-22, size 0-0 line 3151 [ 3431.721986] binder_debug: 10 callbacks suppressed [ 3431.721992] binder: 952:952 cannot find target node [ 3431.722001] binder: 952:952 transaction call to 0:0 failed 5331/29189/-22, size 0-0 line 3151 [ 3431.925081] binder: 6467:6323 cannot find target node [ 3431.925092] binder: 6323:6467 transaction call to 0:0 failed 5332/29189/-22, size 0-0 line 3151
Rebooting didn't help. Any ideas? I'm not sure if this is even a Waydroid bug since it wasn't an update in the waydroid package that triggered it.
The terms might have been "System Image" and "Vendor Image". There was a new version 18.1 dated around Jan. 25 (same number as the previous one from a month earlier). After it downloaded those, I clicked the button to restart Waydroid and that's when it failed to start again.
Filed https://bugzilla.redhat.com/show_bug.cgi?id=2343301 . Turns out the problem is that my CPU doesn't support SSE4.2. There are images that are supposed to work for such CPUs but some SSE4.2 code got into the recent ones which is why my setup stopped working. Reverting to earlier images, it works again (until the latest images are fixed so they no longer contain SSE4.2 code).
On Mon, Feb 10, 2025 at 8:17 PM Andre Robatino robatino@fedoraproject.org wrote:
Filed https://bugzilla.redhat.com/show_bug.cgi?id=2343301 . Turns out the problem is that my CPU doesn't support SSE4.2. There are images that are supposed to work for such CPUs but some SSE4.2 code got into the recent ones which is why my setup stopped working. Reverting to earlier images, it works again (until the latest images are fixed so they no longer contain SSE4.2 code).
Man, that's an old cpu. Circa 2008 or so. Hat tip for keeping it on life support.
I have a couple of machines like that for regression testing. I don't use them as a daily driver.
Jeff
On Mon, Feb 10, 2025 at 8:17 PM Andre Robatino robatino@fedoraproject.org wrote:
Filed https://bugzilla.redhat.com/show_bug.cgi?id=2343301 . Turns out the problem is that my CPU doesn't support SSE4.2. There are images that are supposed to work for such CPUs but some SSE4.2 code got into the recent ones which is why my setup stopped working. Reverting to earlier images, it works again (until the latest images are fixed so they no longer contain SSE4.2 code).
Android requires SSE4.2 + POPCNT for x86_64; and SSSE3 for x86. See https://developer.android.com/ndk/guides/abis.html.
You probably need to ensure your cpu has the minimum Android cpu features for Waydroid.
Jeff
When you install Waydroid, it automatically checks the CPU for those features, so the user doesn't have to. When I did it on the x86_64 machine in question, it said the CPU didn't support SSE4.2 and downloaded the x86 images, which shouldn't require it. (The problem is that there's currently a bug where those images have some SSE4.2 code anyway.) When I tried installing on an even older x86_64 machine (while trying to debug the original problem), it said it didn't support SSSE3 and stopped there. (Which is how I found out SSSE3 was required.) When I installed on a laptop with a CPU that does support SSE4.2, it just went ahead and downloaded the x86_64 images without comment.
-
Andre Robatino -
Jeffrey Walton