| Issue 5: | Torch flashlight turns off when screen goes off | |
| 2 people starred this issue and may be notified of changes. | Back to list |
* What steps will reproduce the problem? 1. Turn on torch 2. Wait for screen timeout to kick in, or just push the power button * What is the expected output? What do you see instead? Expect the LED flashlight to continue being lit. Instead, it turns off. Also, the torch icon in the notification dropdown still indicates it is on. * What version of the product are you using? On what operating system? CM9 Alpha 6 * Please provide any additional information below. Logcat spams a metric ****ton of lines when torch is activated: I/QualcommCameraHardwareZSL( 156): request capture mode normal I/QualcommCameraHardwareZSL( 156): requested preview size 640 x 480 I/QualcommCameraHardwareZSL( 156): requested picture size 640 x 480, mCaptureMode 0 I/QualcommCameraHardwareZSL( 156): requested jpeg thumbnail size 512 x 384 I/QualcommCameraHardwareZSL( 156): requested jpeg quality 85 D/QualcommCameraHardwareZSL( 156): flip-video = 0 D/QualcommCameraHardwareZSL( 156): setZoom pre_value 0 value 0 I/QualcommCameraHardwareZSL( 156): Set zoom=0 40 I/QualcommCameraHardwareZSL( 156): request burst picture count 1 D/QualcommCameraHardwareZSL( 156): setSharpness pre_value 10 value 10 D/QualcommCameraHardwareZSL( 156): initDefaultParameters AfArea : (0,0,0,0,0) D/QualcommCameraHardwareZSL( 156): initDefaultParameters AecArea : (0,0,0,0,0) D/QualcommCameraHardwareZSL( 156): setAecLock pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setAwbLock pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setAntibanding pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setSceneMode pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): requested video size 640 x 480 D/QualcommCameraHardwareZSL( 156): virtual bool android::QualcommCameraHardware::recordingEnabled() recordingState=0 I/QualcommCameraHardwareZSL( 156): setRecordingHint value 0 actual-camera-mode 0 cam-mode -1 recordingEnabled 0 I/QualcommCameraHardwareZSL( 156): requested Fps Range min: 1 x max: 200000 D/mm-camera( 156): config_proc_CAMERA_SET_PARM_FPS: 30 D/QualcommCameraHardwareZSL( 156): setAutoExposure pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setExposureCompensation pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setISOValue pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setSaturation pre_value 5 value 5 I/QualcommCameraHardwareZSL( 156): requested effect 0 D/QualcommCameraHardwareZSL( 156): setEffect mColorEffectState 0 D/QualcommCameraHardwareZSL( 156): setEffect pre_value 0 value 0 D/QualcommCameraHardwareZSL( 156): setWhiteBalance pre_value 1 value 1 D/QualcommCameraHardwareZSL( 156): pre_mColorEffectState value = 0 mColorEffectState 0 D/QualcommCameraHardwareZSL( 156): setContrast pre_value 5 value 5 I/QualcommCameraHardwareZSL( 156): Setting flash 3 D/ ( 156): [GECameraParameters::getGPUEffect] enter D/ ( 156): [GECameraParameters::getGPUEffect] leave. no key GPU-effect D/ ( 156): [GECameraParameters::getGPUEffectParam] leave. no key GE-param0 D/ ( 156): [GECameraParameters::getGPUEffectParam] leave. no key GE-param1 I/GPUPostEffect( 156): int mlabs::GPUPostEffect::setParameters(mlabs::GPUPostEffect::GPUTask*): old effect = -1, new effect = -1. D/GPUPostEffect( 156): setParameters: isGEInit == false: no call to ChooseEffect. D/QualcommCameraHardwareZSL( 156): previewEnabled() E, mZslEnable 0 D/QualcommCameraHardwareZSL( 156): previewEnabled() X, mCameraRunning=0 mPreviewStartInProgress=1 This loops over and over.
Jul 27, 2012
#1
lthomas...@gmail.com
Jul 28, 2012
This isnt device specific, default cm behavior as of now.
Status:
WontFix
Aug 24, 2012
I really disagree that this is the right way for the torch to behave. When you're using the torch, you're obviously _not_ looking at the screen: you're looking at something that you needed a torch to see. Yet the delicate touchscreen _needs_ to remain on for the torch to remain on, which is just asking for accidental inputs from the screen. Not to mention the screen timeout being a real pain too! In CM7 I could turn on the LED, put down the phone somewhere nearby and leave the area lit up for many minutes at a time. Now, the torch constantly needs attention to remain on. I can't believe this would be a hard thing to fix. Hope somebody will take it up.
Jul 10, 2013
this isnt the case on a lot of other devices like the s3 and s4 for example its a bug with specific hardware i think (HTC mostly?) |