Usually in such cases we say: "The best is the device, that you have in your pocket." But users are not satisfied with this answer.
The honest answer is less positive than the one above. And it sounds like "There is no such thing as the best, if we're talking about Android devices." Every Android device has some set of problems that one user will be willing to put up with, but which may be completely rejected by another.
The most basic problem with all Android devices is that manufacturers praise their smartphones in the context of native apps only. When a manufacturer says a new device will have 60/120/240 fps mode, they are talking exclusively about their native camera app. When the manufacturer says that the new device will have 10-bit recording support, they are talking exclusively about their native camera app. When a manufacturer talks about a special HDR mode that captures a huge dynamic range, rest assured they are talking exclusively about their native camera app.
Android device manufacturers are not interested in what their device can do with third-party apps. They don't think about letting third-party developers create powerful tools that work correctly on their devices.
Samsung and Huawei tried to give third-party developers access to unique features through their own API. As a result, Samsung abandoned that idea in favor of the standard Camera2 API, but abandoned it in a way that deprived third-party developers of even fairly standard features. Huawei decided to create its own API after the problems with the sanctions. But that didn't work either. The problem with this approach is that using the API data, you can't do anything better than native app. And combining both the Camera2 API and the API from the manufacturer is difficult, double work.
What does the perfect mobile video device look like?
- All three camera sensors have the same capabilities. If 60 fps is available, it is available on all sensors. White balance calibration is the same on all sensors. And so on.
- All basic frequencies 24, 25, 30, 48, 50, 60, 100, 120, 200, 240 fps are available. And all frequencies work steadily.
- Manual WB works without any problems.
- Autofocus and manual focus work without problems. Have the same range of travel without any "duct tape".
- No problems with auto exposure and manual exposure. Have the same range for both ISO and shutter speed, without any "duct tape". It is important that the exposure does not differ between 8 and 10-bit modes.
- HDR mode is available to turn on without any "duct tape".
- All the camera sensor settings documented in the Camera2 API are available and work. At least if they are available, they work.
- All codec settings documented in the Android API are available and work.
- Good cooling.
- 10-bit recording in 4:2:2 would be a huge advantage.
2.7.1. Samsung.
Does not allow access to the telephoto lens module on any of its devices. So 8K is not available for third-party apps, the telephoto lens module is responsible for this.
Tone curve (gamma curves) may not work on younger models.
Problems with hardware noise reduction in 10-bit mode. There are a lot of complaints.
There are problems with electronic stabilization, does not work.
2.7.1.1. Exynos.
Problem with the number of tone curve points on all devices starting with the S6. We have only 32 points available to us, which makes the logarithmic curves work ugly. We have to adjust the density of tone curve points.
On the S20 and S21, the exposure of the frame changes when the exposure is locked. Correcting this problem with "duct tape" leads to the fact that zoom stops working.
2.7.1.2. Snapdragon
The problem with 60 fps mode. On S20 and S21 devices this mode makes the device to reboot.
2.7.2. OnePlus
On all devices of this manufacturer there are problems with frame rates 24 and 25 fps, does not work. On all devices of this manufacturer there are problems with electronic stabilization, it does not work. On the OnePlus 7 and 8 with Android 11, access to the secondary modules have been closed. Only the primary rear and front-facing are available. Also on Android 11 appeared pobblems with 48, 50, 60 fps, on some devices there was only one working frecuency - 30 fps.
On some devices, not very modern and modern mid-range, there are problems with automatic focus, exposure and white balance working at the same time with the manual mode of any of these functions. For example, selecting manual focus and auto exposure at the same time can stop automatic exposure from working. Or selecting manual exposure can stop the auto focus from working. There is no cure for this, it is a feature of the camera's libraries.
2.7.3. Xiaomi
On all devices of this manufacturer there is a problem with electronic stabilization, it does not work. Where optical stabilization is available, the problem can also be observed. On devices on the MediaTek processor there may be a problem with the tone curve (gamma curves). 60 fps is available mainly only on flagman devices.
2.7.4. Redmi
All the problems of the manufacturer Xiaomi. In addition, on some devices working with the tone curve (gamma curves) can be observed greens in the shadows. 60k/s has been available since the Note 9 Pro. There were previously some individual devices with 60k/s, but these are rather exceptions to the rule.
2.7.5. Huawei.
All devices (except last) of this manufacturer have problems with frame rates of 24 and 25 fps, does not work. On all devices with RYYB sensors there are problems with manual white balance, it does not work. Manual white balance affects the operation of the gamuts.
On individual devices you can observe the problem of the tone curve not working (gamma curves).
On a large number of devices, hardware sharpness and optical stabilization cannot be turned off.
2.7.6. Sony
On devices before Xperia 1, 24 and 25 fps are not available, working only in manual exposure mode. 60 fps has only been available since the Xperia 1 II. On the Xperia 1, 60 fps only worked in 1080p auto exposure mode.
On the Xperia 1 II and above, turning on 60 fps and above in resolutions above 1080p causes the zoom to break, it stops working.
Almost all of this manufacturer's devices get very warm when recording. At some point, the heating reaches a critical level, and frames start dropping out in large quantities. The exception may be Xperia Pro, there the manufacturer has worked on cooling system.
2.7.7. Google
60 fps on the latest models are activated only when using the GPU. Before the release of Android 11 on devices of the Pixel 4 and 5 family there were problems with the tone curve (gamma curves), it did not work.
2.7.8. LG
One of the most "duct tapes" manufacturers. A lot of functions available in mcpro24fps are implemented by workarounds. Thankfully their implementation, unlike other manufacturers, is not so difficult.
On some devices, not very modern and modern middle segment, there are problems with automatic focus, exposition and white balance working at the same time with the manual mode of any of these functions. For example, selecting manual focus and auto exposure at the same time can stop automatic exposure from working. Or selecting manual exposure can stop the auto focus from working. There is no cure for this, it is a feature of the camera's libraries.
Turning off hardware sharpness drops the 60 fps to 57-58 fps.
There are problems with electronic stabilization, it does not work.