Hi folx.
My camera settings are resetting every time i exit and re enter camera app.
For example if i set Burst Mode off, Flash to auto, when i re enter camera app, burst mode is on and Flash is off..
Any one having this issue or knows how to fix this problem ?
Thanks in advance folx
Related
Have a Defy with stock 2.2 Froyo dutchversion and have rooted it as i wanted to make some overclock. I also installed Defy2ndInit so i can use the multitouch app thats availble on market but i get some problems with that. When i have it installed my camera wont work as i should! When i open the camera i can't see any preview on the screen! When i take a picture it works but the display is always black.
So black display when recording or taking pictures with Defy2ndInit installed. When i unistall it the camera works fine! Anyone having a clue?
You have to restart your phone once you're entered and you've modified something in 2nd Init.
Buchko said:
Have a Defy with stock 2.2 Froyo dutchversion and have rooted it as i wanted to make some overclock. I also installed Defy2ndInit so i can use the multitouch app thats availble on market but i get some problems with that. When i have it installed my camera wont work as i should! When i open the camera i can't see any preview on the screen! When i take a picture it works but the display is always black.
So black display when recording or taking pictures with Defy2ndInit installed. When i unistall it the camera works fine! Anyone having a clue?
Click to expand...
Click to collapse
I had the same problem, and found a excellent explanation and workaround here (sorry for not pointing to the original thread, I have lost it):
the bootmenu contained in Defy2ndinit has a bug (afaik still not corrected even in newer versions) that cause mis-initialization of video4linux. This leads to black screen in camera viewfinder, but also all video playback (media playback will also lead to a black screen).
The workaround is to boot your defy without lauching bootmenu, i.e. use the default boot feature.
If you need to change something in bootmenu, change it, test it after the reboot, and if everything is ok (except video4linux of course), reboot another time using default boot ( WITHOUT entering bootmenu (do not press volup/down when blue led is on)). As bootmenu was not started, video4linux will initialize correctly and you will have a working cam preview and video playback...
gkai said:
I had the same problem, and found a excellent explanation and workaround here (sorry for not pointing to the original thread, I have lost it):
the bootmenu contained in Defy2ndinit has a bug (afaik still not corrected even in newer versions) that cause mis-initialization of video4linux. This leads to black screen in camera viewfinder, but also all video playback (media playback will also lead to a black screen).
The workaround is to boot your defy without lauching bootmenu, i.e. use the default boot feature.
If you need to change something in bootmenu, change it, test it after the reboot, and if everything is ok (except video4linux of course), reboot another time using default boot ( WITHOUT entering bootmenu (do not press volup/down when blue led is on)). As bootmenu was not started, video4linux will initialize correctly and you will have a working cam preview and video playback...
Click to expand...
Click to collapse
so you mean to say we have to set the boot to normal from 2nd init . and then reboot again so that we bypass the bootmenu ???
Edit : yes you were right . The bootmenu is causing the problem i had set the bootmenu to boot normally (Normal in menu) and hence my camera is working again . is there any workaround for that ? as of now ?
joydeep1985 said:
so you mean to say we have to set the boot to normal from 2nd init . and then reboot again so that we bypass the bootmenu ???
Edit : yes you were right . The bootmenu is causing the problem i had set the bootmenu to boot normally (Normal in menu) and hence my camera is working again . is there any workaround for that ? as of now ?
Click to expand...
Click to collapse
None that I am aware of. You can still install cm7 or other custom rom though, just have to select 2nd init booy as default boot...and always default reboot after using bootmenu. More an annoyance than a critical bug imho...
Sent from my MB525 using XDA App
gkai said:
The workaround is to boot your defy without lauching bootmenu, i.e. use the default boot feature.
Click to expand...
Click to collapse
Thanks, fixed my "black" camera problem too
Excuse me! joydeep1985, I've fixed the problem, but how do I access to the Android Boot Menu again? Because default boot now is normal, the device will not pause at Android Boot anymore.
My Defy+ suffered the blank screen using camera and video after applying 720p patch I tried to reboot in normal way but there was no effect. I tried to unnstall 2ndinit and now it works!
When you reboot defy, immediately after you See the blue led press volume down which will then boot into boot menu. Enjoy!
Sent from my MB526 using XDA App
I've just installed cyanogenmod. Really satisfied =D
Except the fact that my camera is not working. When it opens, the screen is black with a few camera options. I really need the camera function urgently as my phone is my only camera and I have a lot of notes to scan using my phone. Please help =( Thanks in advance!
Try rebooting. I had the same issue.
rebooting doesnt work.. i have the same issue.. tried a camera fix (flashable zip) but still no dice ... it mite work for u maybe try it out http://www.4shared.com/get/17jiqADA/CWR-CM4DX-CameraFix.html
just boot into recovery and install from sdcard.
default-reboot, i.e. you have to define 2ndinit boot as default boot option, and then reboot without pressing vol_down when blue led is on. Your defy has to boot by itself, without bootmenu ever being launched. It is the bootmenu that corrupt viedo4linux initialization, and v4l is needed for cam preview (among other thing, media player do not show video without v4l too)
gkai said:
default-reboot, i.e. you have to define 2ndinit boot as default boot option, and then reboot without pressing vol_down when blue led is on. Your defy has to boot by itself, without bootmenu ever being launched. It is the bootmenu that corrupt viedo4linux initialization, and v4l is needed for cam preview (among other thing, media player do not show video without v4l too)
Click to expand...
Click to collapse
i too have the same issue. when i open camera the screen is white. video player also not showing the video. can u pls tell me in detail how to fix this.
So the problem is when i go into certain apps and then
A) Press sleep
B) Quit (by pressing back button)
The soft-key/button backlight on Samsung Gio stays on BUT the screen will go off if i press sleep.
-The button-backlight DOES NOT turn of even when its been in sleep mode foor an hour
Any help will be Appreciated
THANK YOU
Solution!
Rooted devices and install GioKlight app, or open "/sys/class/leds/button-backlight/brightness" file on text editor and replace "255" to "0" for advanced user
Do you use stock rom?
Or a custom rom?
Does anybody know how we can enable RAW file format for auto mode in the default camera app. RAW appears in pro mode but not in auto mode
xpoudel said:
Does anybody know how we can enable RAW file format for auto mode in the default camera app. RAW appears in pro mode but not in auto mode
Click to expand...
Click to collapse
I think you can't capture raw photos in auto mode.
Sent from my Honor 8 pro using Tapatalk
I´m on stock rom, but since first miui 11 update the phone only vibrates when charging. I´ve tried to change all settings on accessibility and "sound and vibration", nothing solves the problem.
Any hints?
Found a solution! Looks like a bug, vibration isn't restored when phone leaves battery saving mode. Vibrations can be restored via ADB (but you need to allow write secure settings in developer options) using
settings put global battery_saver_constants "vibration_disabled=false,animation_disabled=true,adjust_brightness_disabled=false"
EDIT: after some time vibration was disabled again, even without entering battery saving mode.
I'm facing this also with PocoF1