chi.appsc
chi.apps
Aug 20

Motorola One Hyper - fails to start video recording

Fails to start video recording (in Raw or Normal). Motorola One Hyper (Model: XT2027-1)It does however take a still picture.
ProgressIn Progress

movedfromFeaturestoBugs·Aug 25, 2026
Aug 24, 2026

Another thing I noted is that the screen on phone gives a resolution of 4160x3120, but as noted in the media info output the actual recorded resolution is 2880x2160. I can tap on the resolution and it gives 2592x1944, and in this mode that is the actual resolution of/in the video file. In this lower resolution the recording seems to start quicker.

Aug 24, 2026

Same on Windows, plays OK in VLC but reported with low FPS in the codec window. File does not import video into DaVinci Resolve, only shows as audio tracks.

Aug 24, 2026

Single stepping didn't show corrupt frames, and copying them to the local drive (D'oh) improved playback, still VLC is reporting slow than expected frame rate (ie 29.805). 'mediainfo' seems to think they are 29.97fps files. $ mediainfo CHIKAMERA_20260824_150357.mp4 General Complete name : CHIKAMERA_20260824_150357.mp4 Format : MPEG-⁠4 Format profile : Base Media / Version 2 Codec ID : mp42 (isom/mp42) File size : 89.5 MiB Duration : 15 s 131 ms Overall bit rate : 49.6 Mb/s Frame rate : 29.970 FPS Encoded date : 2026-⁠08-⁠24 21:04:13 UTC Tagged date : 2026-⁠08-⁠24 21:04:13 UTC com.android.version : 11 com.android.manufacturer : motorola com.android.model : motorola one hyper Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L5.2@Main Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 15 s 131 ms Source duration : 15 s 45 ms Bit rate : 49.6 Mb/s Width : 2 880 pixels Height : 2 160 pixels Display aspect ratio : 4:3 Frame rate mode : Variable Frame rate : 29.970 (29970/1000) FPS Minimum frame rate : 29.880 FPS Maximum frame rate : 29.980 FPS Standard : NTSC Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Bits/(Pixel*Frame) : 0.266 Stream size : 89.0 MiB (99%) Source stream size : 89.0 MiB (99%) Title : VideoHandle Language : English Encoded date : 2026-⁠08-⁠24 21:04:13 UTC Tagged date : 2026-⁠08-⁠24 21:04:13 UTC Color range : Limited colour_range_Original : Full Color primaries : BT.709 colour_primaries_Original : BT.601 PAL Transfer characteristics : BT.709 transfer_characteristics_Original : BT.601 Matrix coefficients : BT.709 matrix_coefficients_Original : BT.470 System B/G mdhd_Duration : 15131 Codec configuration box : hvcC Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-⁠40-⁠2 Duration : 15 s 83 ms Bit rate mode : Constant Bit rate : 256 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 471 KiB (1%) Title : SoundHandle Language : English Encoded date : 2026-⁠08-⁠24 21:04:13 UTC Tagged date : 2026-⁠08-⁠24 21:04:13 UTC

Aug 24, 2026

Previously (lots of zero files) was with V1.1.4, and I updated to V1.1.8 today with better performance. Still very slow to get going, and getting the 'wait for app' pop-up, but now I do not get a lot of files... if connected to phone in 'file transfer' mode I can see files getting started and then deleted, eventually getting one per recording. I also noticed that although these a left showing at zero length on my PC file browser, if I reconnect they do actually have data in them. Video contents (as viewed with VLC) shows some corrupt frames, and a frame rate below expected (for example 27.67fps). Maybe this is my phone not actually being fast enough to pull data from sensor. Storing video on the internal memory (not SDCard).

Aug 21, 2026

New release is very slow to start 'filming' taking a few seconds to change button to a 'stop' square, and produces a lot of zero length files in the process. Only once did I actually get a file with data, which looked to have some corrupt frames in it (as view on VLC).

Aug 23, 2026

Thanks for the update, does the latest release 1.1.8 have the same issue?

changed status toIn Progress·Aug 21, 2026
Aug 21, 2026

Thanks for the feedback, the fix for this is already in the works!