Huawei and Honor are separated by manufacturer: the Honor 20 and View 30 are recognized only as Huawei, newer Honor phones as a separate brand. The main difference between Huawei and the others is the Kirin processor and RYYB sensors: they have their own colour and white balance rules.
All Huawei
- Codec. Constant bitrate modes are turned off for all codecs (does not affect Honor).
- Frame rates. The frame rate is passed through a Huawei vendor parameter up to and including Android 11; from 12 the firmware has removed it. On MediaTek the high frame rate mode through a MediaTek vendor parameter.
- Cameras. On Android 9 and 10 the logical camera is bound to the first physical module.
- Slow motion. Built-in slow motion on Kirin is allowed from Android 11.
Kirin and RYYB: colour and white balance
- From preview frames, without requests to the camera, the app determines three things: whether the firmware delivers real white balance gains or a placeholder, whether the sensor is RYYB, and what its green coefficient is. The decision is remembered per device.
- If the firmware delivers a placeholder (as on the Kirin 970), manual white balance is hidden, and the camera's auto white balance presets remain. The camera is reopened once in that case.
- On Kirin the colour matrix block (gamut, saturation, tint) is always hidden: the Kirin 990, 820 and 970 do not apply our matrix, and the 659 spoils the image.
- On RYYB the colour matrix is corrected with the green coefficient: from the "daylight" and "cloudy" presets, and without them by sensor class. The manual white balance panel on RYYB is wider than usual. In DNG the green row of the matrix is multiplied by the same coefficient.
- Until the measurement is finished, RYYB is treated as a normal sensor.
Mate 20, Mate 20 Pro, P20, P20 Pro, Mate 30, Mate 30 Pro, P30, P30 Pro, P40, P40 lite, P40 Pro, Mate 40, Mate 40 Pro, Mate 40 RS
Fourteen models with a common package of vendor parameters: sensor and video HDR, brightness, saturation and contrast at medium values, dynamic frame rate off, and with frames from 2160 lines a vendor 4K mode is turned on. Below is what each of them has individually.
- P20 Pro: in manual exposure the frame rate is set by a vendor algorithm parameter instead of the standard range. The default autofocus area is not set (on the P20 too). HEVC on the Kirin 970 is recorded without colour metadata in the stream, so the colour is written to the container; there is no 10-bit HEVC. Before the codec is stopped, the camera stream is stopped: the firmware sent frames to dead surfaces. The RAW converter on the Mali-G72 works with workarounds; HLG and HDR10 without a 10-bit encoder refuse with a message. 60 fps on the main camera 1920×1080, 2560×1440 through the GPU. Optical on/off is forcibly available on the main camera (also on the P20, Mate 10).
- P30, P30 Pro: the tone curves tab is closed (also on the Honor 20). Optical forcibly on cameras 0 and 4 (P30 Pro) or 4 (P30). 60 fps on the main camera 1920×1080, 2560×1080, 2048×1536, 3264×1840, through the GPU 2336×1080 and 2560×1440; camera 4 the same without 3264×1840; camera 6 1920×1080 without GPU; 4K at 60 does not work anywhere. On the P30 Pro camera 4 considers sizes up to 3840×2160 usable at 30 fps.
- Mate 30, Mate 30 Pro: optical on camera 6 (on the Pro also 0). 60 fps without GPU 1920×1080, 2560×1080, 2048×1536, 3840×2160, through the GPU up to 2560×1440; camera 4 as the main camera; camera 6 1920×1080. 48 and 50 as 60. On the Mate 30 Pro camera 6 up to 4K at 30 fps.
- P40, P40 Pro, P40 lite: optical on camera 6. Camera 5 is hidden on the P40 and P40 Pro. P40 Pro: 60 fps on the main camera 13 sizes up to 4096×3072, camera 1 up to 3840×2160, camera 2 up to 3264×2448 (at 48 also 4096×3072), camera 4 up to 3840×2592, camera 6 up to 3840×2160; 48 and 50 as 60; camera 6 up to 4K at 30 fps. P40: 60 fps 13 sizes up to 4096×3072. The P40 lite has no table of its own.
- Mate 40, Mate 40 Pro, Mate 40 RS: optical on camera 6 (on the Pro also 0). No frame rate table of their own.
- Mate 20, Mate 20 Pro: only the common parameter package, no table of their own.
Mate 10, P60
- Mate 10: optical on/off forcibly on the main camera; 60 fps 1920×1080, 2560×1440 through the GPU.
- P60: recognized, but has no rules of its own.
Mate 50, Mate 50 Pro
- HDR10 through CUVA vendor parameters in 10-bit, but 10-bit could not be made to work on the Mate 50, so it has been removed from the whitelist. HLG format is off. No frame rate table of their own.
Pura 70, 70 Pro, 70 Ultra, 80, 80 Pro, 80 Ultra
- 10-bit on the whitelist. Camera 2 is not considered a duplicate.
- 60 fps on cameras 0, 2, 4, 5, everything up to 4096×2160; 48 and 50 as 60; 10-bit limit 480 at 4096×3072.
Honor 20, Honor View 30
- Honor 20: the curves tab is closed; on the main camera stabilization only "off", on camera 4 optical on/off; camera 4 up to 4K at 30 fps. 60 fps 1920×1080, 2560×1440 through the GPU.
- View 30: camera 5 up to 4K at 30 fps. 60 fps on cameras 0 and 2 19 sizes up to 3648×2736 (including 3840×2160), camera 4 12 sizes up to 4608×2592; 48 and 50 as 60.
Honor 70, Magic 3 Pro, Magic 4 Ultimate
- All Honor: 10-bit HEVC with the Main10 profile and level.
- Honor 70: with stabilization, a vendor camera mode; 10-bit on the whitelist; camera 4 is not a duplicate; 60 fps on cameras 4 and 0 21 sizes up to 3840×2160; 10-bit limit 240 at 4096×3072.
- Magic 3 Pro: 10-bit on the whitelist, no table of its own.
- Magic 4 Ultimate: 10-bit on the whitelist; camera 9 is not a duplicate, cameras 6 and 7 are hidden; 60 fps 24 sizes up to 4080×3072; limit 240 at 4096×3072.
Honor Magic 5 Pro, Magic 6 Pro, Magic 7 Pro
- Cameras. On the Magic 6 Pro visible 0 is opened as actual camera 6. Camera 6 is not a duplicate. Zoom buttons: 5 Pro 0.5×, 1×, 3.5×, 5×; 6 Pro and 7 Pro 0.5×, 1×, 2.5×, 4×.
- Frame rates. 60 fps on cameras 0, 2, 6 up to 4096×3072, on 1 and 5 up to 4064×3048, on 4 up to 4032×3024 and a few more; 48 and 50 as 60; 24, 25 and 30 fps the 8K series on cameras 0, 2, 4, 6, 7. 10-bit limit 30 at 8K, 240 at 4096×3072.
Honor Magic 8 Pro
- Stabilization. On cameras 0, 2, 5 optical and digital are forcibly considered available (the camera does not declare them, but they are there).
- Cameras. Camera 2 is not a duplicate, cameras 6 and 7 are hidden. Zoom buttons: minimum, 1×, 3.7×.
- No frame rate table of its own.
Honor 400, 400 Pro
- Focus. Honor firmware moves the lens in manual focus only when the request contains a focus area with a non-zero weight. On the Honor 400 and 400 Pro in manual focus the app sets an area in the centre of the frame, 1/20 in size. Found and tested together with a user.
- Stabilization. The camera does not declare optical stabilization; the app overrides the flags on the rear cameras, as on the Magic 8 Pro. "Optical" forcibly turns off digital. According to a user's video, optical stabilization works.
