Crashes on Xiaomi Redmi 4 OS 6.0.1

[googlearchive]

Crashes on Xiaomi Redmi 4 OS 6.0.1

[Barazu]

It actually has an easy fix.
Add this code to the stopRecordingVideo method:

try {
           mPreviewSession.abortCaptures();
       } catch (CameraAccessException e) {
           e.printStackTrace();
       }

       Timer timer = new Timer();
       TimerTask timerTask = new TimerTask() {
           @Override
           public void run() {
               mMediaRecorder.stop();
               mMediaRecorder.reset();
           }
       };
       timer.schedule(timerTask,30);

The reason for the exception is explained here : .
The simplest workaround (that I found at least) is to call mPreviewSession.abortCaptures(); and set a short delay before calling mMediaRecorder.stop(); as abortCaptures() may take time to execute.
Hope this helps!

[rspq]

Same crash on Moto Z Play running 6.0.1.

It says something about the utter awfulness of Camera2 that even Google cannot produce working samples for it.

[JasonZhu19910601]

I have the same error.

[anonym24]

what about 1007 failed but with MediaProjection (not camera)

https://stackoverflow.com/questions/45266016/screen-recording-stop-failed-and-failure-delivering-result-resultinfo

[anonym24]

#86
https://issuetracker.google.com/issues/111433520
https://stackoverflow.com/questions/51332386/mediarecorder-and-videosource-surface-stop-failed-1007-a-serious-android-bug

many devices just don't work with Surface input source (MediaRecorder, MediaCodec)

MediaCodec works ok only with Surface and OpenGL ES but not with lockHardwareCanvas

[anonym24]

@Barazu it only may fix issue with crash (Exception 1007), but video file's size is only 19 kilobytes, so frames just weren't recorded into video file (.mp4 container)

it even doesn't always fix that crash

so there is no solution

[codingjeremy]

This sample has been migrated to a new location where we can accept Pull Requests (check README for more information).

As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.

If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!