From: "Tomas Härdin" <git@haerdin.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Bump minimum required version of Android to 5.0 Date: Fri, 12 Apr 2024 13:39:53 +0200 Message-ID: <a91d78c4e73ff4da34ac27983679ded7367f7c2b.camel@haerdin.se> (raw) In-Reply-To: <tencent_4C952637509426F167D32A8553275C7A4B06@qq.com> fre 2024-04-12 klockan 19:23 +0800 skrev Zhao Zhili: > > > > On Apr 12, 2024, at 18:50, Tomas Härdin <git@haerdin.se> wrote: > > > > tor 2024-04-11 klockan 21:57 +0800 skrev Zhao Zhili: > > > > > > > > > > On Apr 11, 2024, at 21:17, Tomas Härdin <git@haerdin.se> wrote: > > > > > > > > tor 2024-04-11 klockan 20:16 +0800 skrev Zhao Zhili: > > > > > We don’t have a minimum required version of Android in > > > > > FFmpeg. > > > > > libavdevice/android_camera requires Android 7, Java > > > > > MediaCodec > > > > > requires Android 4.1, and NDK MediaCodec requires Android > > > > > 5.0. > > > > > > > > > > Without an explicit version, it’s unclear for development and > > > > > test. > > > > > > > > > > Android 5.0 is released in 2014, is it OK to bump the minimum > > > > > required > > > > > version to Android 5.0, or any other version you prefer? > > > > > > > > Don't we already have stuff that detects the Android version > > > > and > > > > acts > > > > accordingly? Dropping 4.1 might lessen the maintenance burden > > > > though. > > > > > > Check Android API level is easy. There is [no] minimum API level > > > requirement > > > in configure script as far as I know. > > > > Would be a good idea to add one > > > > What would dropping 4.1 support actually look like? I presume it > > would > > make the code a lot simpler. > > I can remove a lot of dlsym by link directly. And it will be more > clear to > know how to handle Android version dependent API when adding new > code. > > > > > > > I have an old phone (Samsung Galaxy S5) running the most recent > > > > LineageOS possible to install on it (16.0), and that uses > > > > Android > > > > 9. So > > > > for me bumping to version 5 sounds fine. > > > > > > > > Do you have any statistics on Android versions actually in use? > > > > > > Search by "Android distribution chart" shows version >= 5.0 is > > > about > > > 99.3%. > > > > Makes me wonder what kind of devices people run that haven't been > > updated in 10+ years.. > > Like TV and OTT box. I know those devices exist, but I highly doubt > that > anyone would attempt to run FFmpeg 7.1 on it. Yeah this is what I'm getting at. Sure people may be running old devices, but are they running programs on them that have been compiled recently? That's going to be a fraction of that remaining 0.7%, assuming there are devs updating apps that use FFmpeg for such old devices. > Android toolchains also drop support of Android 4.4 now. > > "KitKat (APIs 19 and 20) is no longer supported.” > > https://developer.android.com/ndk/downloads/revision_history So at some point it won't even be possible to compile against 4.1 without digging into the archives? That's preservationist work. I'm sure they can dig into our git history as well if they're so desperate to compile old things. /Tomas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-04-12 11:40 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-11 12:16 Zhao Zhili 2024-04-11 13:17 ` Tomas Härdin 2024-04-11 13:57 ` Zhao Zhili 2024-04-11 15:00 ` Zhao Zhili 2024-04-12 10:50 ` Tomas Härdin 2024-04-12 10:51 ` Nicolas George 2024-04-12 11:23 ` Zhao Zhili 2024-04-12 11:39 ` Tomas Härdin [this message] 2024-04-12 13:47 ` Matthieu Bouron
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=a91d78c4e73ff4da34ac27983679ded7367f7c2b.camel@haerdin.se \ --to=git@haerdin.se \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git