Skip to content

Say what ran on x86_64 in the 7.1.5.5 and 6.1.6.5 notes #28

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

Merged
sbokatuk merged 1 commit into from
Oct 30, 2026
Merged

Say what ran on x86_64 in the 7.1.5.5 and 6.1.6.5 notes #28

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/release-notes/6.1.6.5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,4 +66,4 @@ Against the packed packages:
- `drawtext` in `Video`, `Full` and `FullGpl`.
- All 190 package tests.

`x86_64` was not run on a device.
`x86_64` emulators ran a build of the same FFmpegKit `6.0.4` libraries after this release went out. `Audio` and `Video` on `net8.0-android34.0` pass every device check on API 31 and 35, and the example app, which uses `Full`, completes a conversion on `net10.0-android36.0` on API 35. `Min`, `MinGpl`, `Https`, `HttpsGpl` and `FullGpl` have not run on `x86_64`.
4 changes: 2 additions & 2 deletions docs/release-notes/7.1.5.5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ java.lang.UnsatisfiedLinkError: dlopen failed: can't enable GNU RELRO protection

This has nothing to do with available memory. In those builds the library's RELRO segment ends past its last loaded segment, so Android's linker tries to protect memory that isn't mapped. Upstream traces this to NDK r26c and now builds with r27c.

All five variants now pass every device check on that emulator. `Video` from `7.1.5.4` did load on an API 35 emulator and on a Pixel 10 with Android 17, so whether you hit this depends on the Android version. Other versions were not tried. Nor was `x86_64`, where `Audio` carries the same defect as these five.
All five variants now pass every device check on that emulator. `Video` from `7.1.5.4` did load on an API 35 emulator and on a Pixel 10 with Android 17, so whether you hit this depends on the Android version. Other versions were not tried. On `x86_64`, `Audio` carries the same defect as these five: `Audio` from `7.1.5.4` failed with the same error on an API 31 emulator.

### Fixed: the app freezes after an FFmpeg command

Expand Down Expand Up @@ -66,4 +66,4 @@ Against the packed packages:
- `drawtext` in `Video`, `Full` and `FullGpl`.
- All 190 package tests.

`x86_64` was not run on a device.
`x86_64` emulators ran a build of the same FFmpegKit `7.1.7` libraries after this release went out. `Audio` and `Video` on `net8.0-android34.0` pass every device check on API 31 and 35, and the example app, which uses `Full`, completes a conversion on `net10.0-android36.0` on API 35. `Min`, `MinGpl`, `Https`, `HttpsGpl` and `FullGpl` have not run on `x86_64`.
Loading