From: Zhao Zhili <quinkblack@foxmail.com> 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: Thu, 11 Apr 2024 23:00:05 +0800 Message-ID: <tencent_C9AEA745449313A84113FDF36035CF291805@qq.com> (raw) In-Reply-To: <tencent_B5654ED170B82D559AEB40CE9AA79F52AB08@qq.com> > 在 2024年4月11日,下午9:57,Zhao Zhili <quinkblack@foxmail.com> 写道: > > >> >> 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 minimum API level requirement > in configure script as far as I know. I mean there is no minimum API level requirement in configure. >> >> 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%. > >> >> /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". > _______________________________________________ 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-11 15:00 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 [this message] 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 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=tencent_C9AEA745449313A84113FDF36035CF291805@qq.com \ --to=quinkblack@foxmail.com \ --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