Froyo: camera to camcorder back to camera = crash

Search This thread

ibegary

Senior Member
Nov 28, 2009
279
40
Bowling Green, KY
Does anyone else have this issue in froyo?

1. Open camera
2. Move slider to camcorder
3. Move slider back to camera

My application then freezes and nexus one reboots

Im on stock froyo radio and kernel?
 
F

frenchtom

Guest
just went back and forth a couple of times and no issues on my phone
 

supersonic215

Member
May 15, 2009
12
0
I have the same issue. Plus when I'm in camcorder mode and try to change any setting it freezes and reboots also......... don't know what's up

Would also like to add that when installing the update (multiple times) I was met with the following message:

"E:Error finishing BOOT
E:Failure at line 72
write_raw_image PACKAGE:boot.img BOOT:

Installation aborted."

Every time this happens I reboot the phone and definitely still have Froyo... but the camera issue remains prevalent... oh, and I updated from Cyanogen 5.0.6 if that helps any
 

ibegary

Senior Member
Nov 28, 2009
279
40
Bowling Green, KY
I'm going to format the SD Card and then do a total wipe (anything with the word wipe in it on Amon_RA) and then re-flash Paul's Froyo.

Will report back.
 

ibegary

Senior Member
Nov 28, 2009
279
40
Bowling Green, KY
All the wipes and no change, still crashes (before I logged in with a google account or anything. Here is what the logcat shows:

Code:
E/AuthorDriver(   59): setParameter(max-filesize = 15838380032) failed with resu
lt -5
E/AuthorDriver(   59): Ln 928 handleSetParameters("max-filesize=15838380032") er
ror
E/AuthorDriver(   59): Command (12) failed
E/MediaRecorder(  455): setParameters(max-filesize=15838380032) failed: -2147483
648
I/MediaRecorderJNI(  455): prepare: surface=0x2d12b8 (id=3)
E/PVOMXEncNode(   59): PVMFOMXEncNode-Video_AVC::DoPrepare(): Got Component OMX.
qcom.video.encoder.avc handle
W/CameraInput(   59): refCount 0
E/VENC_ENC(   59): VENC_ERROR update_param_port_def::1643 Frame rate is for inpu
t port (refer to OMX IL spec)
E/VENC_ENC(   59): VENC_ERROR get_parameter::952 unsupported index 0x700000b
E/VENC_ENC(   59): VENC_ERROR set_parameter::2720 unsupported index 0x700000b
E/VENC_ENC(   59): Bitrate 3000000
E/VENC_ENC(   59): VENC_ERROR get_parameter::952 unsupported index 0x6000005
E/VENC_ENC(   59): VENC_ERROR set_parameter::2720 unsupported index 0x6000005
E/VENC_ENC(   59): VENC_ERROR get_parameter::952 unsupported index 0x6000008
E/VENC_ENC(   59): VENC_ERROR set_parameter::2720 unsupported index 0x6000008
E/PVOMXEncNode(   59): PVMFOMXEncNode-Audio_AMRNB::DoPrepare(): Got Component OM
X.PV.amrencnb handle
D/CameraInput(   59): Intended mFrameWidth=720, mFrameHeight=480
D/CameraInput(   59): Actual mFrameWidth=720, mFrameHeight=480
I/ActivityManager(   82): No longer want com.android.bluetooth (pid 244): hidden
 #16
I/ActivityManager(   82): Starting activity: Intent { act=android.media.action.S
TILL_IMAGE_CAMERA flg=0x6000000 cmp=com.google.android.camera/com.android.camera
.Camera }
V/videocamera(  455): stopVideoRecording
V/videocamera(  455): Releasing media recorder.
V/videocamera(  455): Empty video file deleted: /mnt/sdcard/DCIM/Camera/VID_2010
0523_182949.3gp
D/CameraInput(   59): DoReset: E
D/CameraInput(   59): DoReset: X
E/CameraInput(   59): Unsupported parameter(x-pvmf/media-input-node/cap-config-i
nterface;valtype=key_specific_value)
E/CameraInput(   59): VerifiyAndSetParameter failed on parameter #0
D/audio_input(   59): DoReset: E
D/audio_input(   59): DoReset: X
E/audio_input(   59): unsupported parameter: x-pvmf/media-input-node/cap-config-
interface;valtype=key_specific_value
E/audio_input(   59): VerifyAndSetParameter failed
W/ActivityManager(   82): Activity pause timeout for HistoryRecord{44b4de20 com.google.android.camera/com.android.camera.VideoCamera}
 

ibegary

Senior Member
Nov 28, 2009
279
40
Bowling Green, KY
Tried other SD cards and tried other .34 Kernals but have the same result. Flash backed to the older radio and had the same issue.

Not sure where the incompatibilities lie. Going to keep Froyo despite the error since I don't do much video recording anyways.

Plus I have a nandroid backup when I was on Cyan 5 where I had the audio unplug bug with the car dock. That's more annoying than the video recording for me.
 

pendo

Senior Member
Jun 3, 2010
1,971
759
Tulsa, OK
Mine does this as well. Actually as soon as I put it in video mode and try to record, crash.

I don't use the video recorder that much, so I was just planning on waiting for the OTA....I'm still a little uncomfortable with the whole 'flashing' stuff....I'm more used to working with Cyberduck.
 

eirij.qureshi

Member
Feb 10, 2010
15
2
Lahore
Reflash with stock ERE27 (update-nexusone-ERE27-signed.zip) and 32.26.00.24U_4.04.00.03_2 radio (update-nexusone-radio-32.26.00.24U_4.04.00.03_2-signed.zip) also solved the problem.
 

pendo

Senior Member
Jun 3, 2010
1,971
759
Tulsa, OK
is there a way to flash just the radio? I really don't want to go back and reinstall everything like I did when I unlocked the bootloader and flashed froyo...
 

mangavideo

Member
Aug 17, 2009
15
0
London
not working either....

I tried everything from flashing froyo with and without radio, CM 5.0.8 test3 with 4.04.00.03_2 radio and still have the same annoying problem with the recording video.....

Please anyone with a different idea to try to fix it? I'm open to anything at this moment......
 

charronegro1971

Senior Member
Apr 21, 2010
99
8
Harlingen, TX
I just noticed the problem as well. I don't use the FroYo ROM alot but when I do I've rarely had problems. I've opened the camera and switched to camcorder then exited out to the main screen but when I press the camera widget to reopen the app, I get a reboot. Pretty damn annoying :(. I'm using Froyo (FRF50) but I'm using the 4.04.00.03_2 radio because I also use Enomther's latest ROM as well as Modaco's latest Desire ROM. The stock FroYo radio borks video playback on the aforementioned ROMs so I don't use it at all.
 
Last edited:

SBS_

Senior Member
Jul 13, 2007
506
19
Bergen
So... let me get this straight: People use a radio not fully compatible with Froyo and wonder why it's not completely stable? A new radio is not always just for ****s n giggles...