There is no macro in camera options, neither can zoom close objects, is there any fix for this, using
CM 7.2
sorry there is no zoom in cm7.2
u didn't understand me, i cannot focus close object like before, that is macro, i dont use zoom ever
MadMaxPN said:
u didn't understand me, i cannot focus close object like before, that is macro, i dont use zoom ever
Click to expand...
Click to collapse
easy peasy..... open camera press menu button and goto advanced option... there in the botton select pre-focus option.....
it works for me... but it takes a sec or 2 to focus on macro objects
rohit25 said:
easy peasy..... open camera press menu button and goto advanced option... there in the botton select pre-focus option.....
it works for me... but it takes a sec or 2 to focus on macro objects
Click to expand...
Click to collapse
thanx for the tip
didnt notice that
I wish it had auto flash feature like vignette
didn't work for me, i already tryed that...i love macro photo, too bad...but im loving CM 7.2, its like im having a new phone, stock rom is s...t, except for the camera options :-(
MadMaxPN said:
didn't work for me, i already tryed that...i love macro photo, too bad...but im loving CM 7.2, its like im having a new phone, stock rom is s...t, except for the camera options :-(
Click to expand...
Click to collapse
glad to know that.... try using the onscreen button for macro camera.... also in some cases my phone doesn't auto-focus... so i just slightly depress the hardware camera button for it to manually focus and then use the onscreen button.....
also make sure your phone is not too CLOSE to the OBJECT you want to FOCUS too
i found a bug...when i press and release camera button, for focusing, four or five times, camera app stops responding, and then i cannot use no more camera, i must restart phone...the video recording quality is poor, very few frames, choppy playback...i hope this bugs will be resolved in future versions of CM
hey i found this: forum.xda-developers.com/showthread.php?t=911364
new fxp125, is this for x10? Where can i find whats fixed in this version, i flashed fxp124, maybe the camera is fixed in this version
MadMaxPN said:
hey i found this: forum.xda-developers.com/showthread.php?t=911364
new fxp125, is this for x10? Where can i find whats fixed in this version, i flashed fxp124, maybe the camera is fixed in this version
Click to expand...
Click to collapse
ya this is the new one but only the bug you talking about is fixed.... the camera is laggy...
but once you play the captured video on ur pc it is not laggy....
i guess the video decoder on the phone is not right or something.....
VOILA
can i upgrade to fxp 125 or i must flash the new version? do i must flash kernel again, ir just fxp?
MadMaxPN said:
can i upgrade to fxp 125 or i must flash the new version? do i must flash kernel again, ir just fxp?
Click to expand...
Click to collapse
they recommend that you must flash the new kernel....
btw http://www.mediafire.com/?bttx5mfd8qqna62
this has the kernel and gapps and rom in one file you just need to flash via flashtool....
i found it in the fxp125 cm7.2 article
i loose all my apps and settings :-(
i left my phone on charger about 4.5 hrs, and my battery was overheated, 50c, it charged about 70%, it last about two hours...i suppose that CM7 dont stop battery charging like stock Rom, right? I didnt know that, i hope it didnt impact my battery health...
by the way Rohhit thnx for answering all my questions, you was very helpfull, i will try new fxp125...
hey
no no.... it battery wud heat up few times in the start mine did too...
nothing to worry that about.... you can always wipe battery stat's that can help too...
plus it's not on the coding of the rom.... once charged the hardware stops chargin the phone anymore.... and if you r in a silent environment you cud hear a slight noise from the charger....thats it saying NO MORE CHARGING
is there a way not to loose all aplications on every rom flashing? And is there a way to extend battery time, i read on some post that i must change some cpu setting and battery should last longer...
but why then my batery depeated so quickly, less than two hours, on standby ??
easy pesy
MadMaxPN said:
but why then my batery depeated so quickly, less than two hours, on standby ??
Click to expand...
Click to collapse
first of all on the play store search for battery calibration app.....
do as the app says charge 100% then deplete till 0% then charge till 100% again....
second of all goto settings->cyanogenmod settings->cpu settings->governors->and select interactive->plus select set on boot and
interactive is the best governor out there gives max battery with max cpu efficiency....
as for losing all the apps... download titanium pro i would suggest download the full version from some torrent site....
plus in fxp rom's there is an option of modifying the settings of the apps.. like can they access the internet or not... can they access the messages or not....
its in cyanogenmod settings application.... permission management....
select it and then ban the apps that support ADs.....
VOILA
can u provide more info how to flash this file, i downloaded Flashtool 0.8.6.0, its diffrent from last time, i flashed the kernel first, this is differet now...
MadMaxPN said:
can u provide more info how to flash this file, i downloaded Flashtool 0.8.6.0, its diffrent from last time, i flashed the kernel first, this is differet now...
Click to expand...
Click to collapse
very easy..... open flashtool then select advanced... then select bundle creation.... nd select that fxp125 file
click next and
VOILA
you got the ftf version now just flash it.... like you did with fxp124
and thats it,it will flash all, kernel, caps and fxp?
Related
Hello everyone, this is my first post here so go easy on me
The battery on my optimus one doesn't see the day out, is there a ROM that can help, I noticed someone posted that their battery lasted 3 days.
I've managed to root my phone and installed recovery, just need pointing in the right ROM/kernel direction.
Many thanks in advance
http://forum.xda-developers.com/attachment.php?attachmentid=510200&d=1296962775
flash this kernel
switch off wifi,bluetooth,gps,data by dragging notification bar and tapping on the ocons.
reduce display brightness from settings>display>brightness (select lwest, atleast thts wat i use
flash void kernel, and install gapps, tapps , a2sd and blink modules.
when the rom is fully installed and running use setcpu to manage cpu 122/600.
turn off wifi, bluetooth, gps.
now your device life is about 30 hrs
The quickest fix would be to switch of 3G(2G only mode), WiFi when not in use, GPS, bluetooth, data enabled off, etc. These can be done with the Power Control widget or from the drag down notification bar. Big effect even without flashing a custom rom
Depending on your usage mate.
But yeah pretty much what everyone else said . Indoor I keep my brightness lvl almost 0. The screen ain't that shabby and it does a pretty good job even outdoors at a bit above half brightness.
I always keep my network on 2g mode OFF and I don't let my phone use data connection unless I want to use 3G network.
Also get an app for clearing memory a bit . I use android assistant which is pretty much an all in one . Great app I'd say , monitors CPU usage and has quick boost for lazy clearing up memory , manual clearing up memory and ofc you can ignore some app processes like for ex. setCPU
As a sidenote , if you have most of the time above 260-270 memory free your phone should hold in average usage for at least 2 days.
I for example on one charge's worth with the above settings , can watch 2 hours of video , at least one hour of browsing , some video games and reading books .
Going slightly off topic, how do I get into recovery mode?
When I installed it I got there, did a nand back up and the rebooted.
Now when I hit Vol down/Power/Home it just starts up as normal?
I'm not very good at this stuff clearly, ha ha
I have trouble getting into the recovery too sometimes, since I can't hold the three buttons that long. Here's how I get to the recovery: Go to your terminal and type "reboot recovery". That should reboot and take you to it.
kpbotbot said:
I have trouble getting into the recovery too sometimes, since I can't hold the three buttons that long. Here's how I get to the recovery: Go to your terminal and type "reboot recovery". That should reboot and take you to it.
Click to expand...
Click to collapse
Brilliant, thanks chief
ccdreadcc said:
http://forum.xda-developers.com/attachment.php?attachmentid=510200&d=1296962775
flash this kernel
switch off wifi,bluetooth,gps,data by dragging notification bar and tapping on the ocons.
reduce display brightness from settings>display>brightness (select lwest, atleast thts wat i use
Click to expand...
Click to collapse
Done all that thanks.
Just another off topic question - in the ROM posts the instructions usually say something about moving the zip file to the SD card from your PC via USB.
Why wouldn't I download the zipfile straight onto the phone (like I did with your kernel) and install it that way?
ccdreadcc said:
http://forum.xda-developers.com/attachment.php?attachmentid=510200&d=1296962775
flash this kernel
switch off wifi,bluetooth,gps,data by dragging notification bar and tapping on the ocons.
reduce display brightness from settings>display>brightness (select lwest, atleast thts wat i use
Click to expand...
Click to collapse
Sorry I know I shoudn't be asking so many questions in so many posts but can you confirm what was contained in your kernel please?
Cheers
Alright, so I've had my galaxy s2 for about 2 weeks and it worked perfectly, I've shot some really beautiful photos, but now suddenly it wont autofocus anymore.
What I already tried:
-reset cam settings to default
-do multiple factory / hard resets
-return to the default stock rom
Nothing works... The focus is stuck at about 20-30 cm from the phone, i've tried all the focus modes, maybe it was stuck on macro, but I didn't manage to solve the problem....
Could anyone help me out please? I'll try everything to avoid getting it changed since I'd have to buy a Jig from ebay first to reset the custom rom counter...
Bump! I really need to fix this problem guys!
Right one thing you could try is reflashing your camera firmware.
first type *#34971539# then the first option in the menu press that and see what your camera firmware is.
Next goto here
http://www.4shared.com/file/uMStvHzj/fw_camera.html
download this and look for the camera firmware that matches yours.
next when you find the one that matches your camera firmware put it on your internal sd, type *#34971539# & i think it's the second option hit that and wait for 3 mins for it to flash don't mess with ya phone while it updating.
if that fails to sort it then it looks like it a jig and a return to samsung.
i had similar bug with my camera, sometimes it wouldn't focus at all, until i tweak the settings of the camera even thou it didn't helped most of the time
but this did solve my problem, thank you
I dont want to start a new thread so i`m gonna write here sine it's related.
How can i get the SGS2 camera to take photos only when the autofocus square is green?
Or to make the camera app actually focus alone without me pressing on the screen to focus? I have stock camera app, no mods or tweaks.
This topic will be posted and discussed bugs CM7.2 by FAT. I did not give a GitHub bugtracker because the mode is more convenient forum to work with users.
Bugs:
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Total bugs:
2
Torch is not functioning, the Toggle LED Flashlight option is greyed out in Cyanogenmod Settings/ Interface/ Notification power widget/ Widget buttons.
its 1 bug not 0.5
Sent from my GT-S5830 using xda premium
kevinlekiller said:
Torch is not functioning, the Toggle LED Flashlight option is greyed out in Cyanogenmod Settings/ Interface/ Notification power widget/ Widget buttons.
Click to expand...
Click to collapse
Torch is working Oh u mean to say toggel prefrence is not working rite Under cynagoen settings rite
nice initiative.
btw bugs from previous/other cm7 version that still plague later build including yours
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Latest Google Maps not working (according to reports, haven't tested), this is an important app!!!
A Github available so you can share your code. Android is open-source, and it is important that you share your fixes with the community, not just compile "closed" ROMs!!!
iandol said:
Latest Google Maps not working (according to reports, haven't tested), this is an important app!!!
A Github available so you can share your code. Android is open-source, and it is important that you share your fixes with the community, not just compile "closed" ROMs!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1484542 this version works.
If the phone is locked and I receive a message, when I unlock the phone to read the message, the soft keys blink once. how can I fix this?
an0nym0us_ said:
nice initiative.
btw bugs from previous/other cm7 version that still plague later build including yours
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Click to expand...
Click to collapse
Massive battery drain sorry dont mind but the battery is good as far as i concern and some people also report that its having good battery life on my own experience i even noticed it is good not best ya compared to other CM version it is good
And I have problem with camera darkness plus vol up/down buttons not work for zooming (I set them in Advanced Options). Tethering not works too.
an0nym0us_ said:
nice initiative.
btw bugs from previous/other cm7 version that still plague later build including yours
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Click to expand...
Click to collapse
Same here..And I don't know why CM touch screen sensitivity always have different 'feel' compared to stock ROM, without notice I'm always touch the screen more tightly to prevent miss touch. I think you guys understand well
Ps. Since this ROM is nearest to official then I'll tell more CM bug:
The bass sound's ugly than stock. You can check with mort player with same equalizer (without DSP mgr of course). Also the equalizer freq change from 5 freq (stock) to 6 freq (CM) and if you slide bass booster on mort, the sound more awkward
Um..oh. Laggy gallery! LOL
Sent from my GT-S5830 using Tapatalk
alex0296 said:
If the phone is locked and I receive a message, when I unlock the phone to read the message, the soft keys blink once. how can I fix this?
Click to expand...
Click to collapse
Not only for messages but when someone is talking to you in WhatApp and others, with all notifications. I think this is to warn you that something happened when the phone was in standby. It's not a bug imo.
The same thing happens with others CM7 roms that I've tested and the AOSP too.
but until you use them do not light. remember that in another CM7 ROM, this does not happen if I went to Settings-> CyanogenMod-> Interface-> LED Notification, except that in this rom, there is no menu Led Notification
is a very good rom but i have a problem, i test smartass, v2, conservative and never enter in deep sleep always 245mhz (my min frequency).
ps: sorry my bad english.
alex0296 said:
If the phone is locked and I receive a message, when I unlock the phone to read the message, the soft keys blink once. how can I fix this?
Click to expand...
Click to collapse
That is common..
Market does not get updated to the latest version. In earlier CM versions, it used to get updated.
Market.
*edit Fixed the problem with market icon
Great ROM so far.
text messaging touch goes rumbled, maybe coz of sensitivity... hope to fix it on next release :clap: more power to Frozen Ace Team...
After two days of usage, I would like to report that this ROM has battery drain issues. Much more than the vo-1 version of CM 7.2
wifi?
Wifi does not work for me. It doesnt scan. When I turn it on in the notifications bar it just turns itself off again after a minute or so.
In the settings the same thing happens. (sometime here it even force-closes)
I found this in the ROM-Thread (http://forum.xda-developers.com/showthread.php?t=1263292):
"
Originally Posted by MrChaosDesire
Hmmm. Wifi does not scan. Maybe a reflash might work.
<3 CyanoAce 7.1
Wi-Fi works fine, but when you turn it ON you can`t see all points, as on stock FW. You must go to the Wireless setting and insert your password there."
When I tried several times to type in the password and SSID it still didnt connect and just turned wifi off again.
Unfortunaly, this link http://forum.cyanogenmod.com/topic/41455-cyanogenmod-7172-samsung-galaxy-ace/ does not work for some reason. (maybe just my computer...)
just checked, it worked: link is not helpfull
Do i have to delete some (or add) files to make hw keyboard work on x10 mini pro (mimmi) with minicm7 2.2.1 (stable version)?
I already know Keyboard fix by faiyyaz but it drains me the battery a lot...other solutions?
isko95 said:
Do i have to delete some (or add) files to make hw keyboard work on x10 mini pro (mimmi) with minicm7 2.2.1 (stable version)?
I already know Keyboard fix by faiyyaz but it drains me the battery a lot...other solutions?
Click to expand...
Click to collapse
hey man, first make sure if the rom only opens the keyboard lights in dark places because some roms make that happen to save battery.
Second, a trick that i use and find out myself ( so i don't know if it will work for you ) without any app is this: with screen blocked, slide the keyboard, the lights will open, after that the lights will always open when you slide the keyboard .
If i helped press thanks , good luck .
Crazy Seed said:
hey man, first make sure if the rom only opens the keyboard lights in dark places because some roms make that happen to save battery.
Second, a trick that i use and find out myself ( so i don't know if it will work for you ) without any app is this: with screen blocked, slide the keyboard, the lights will open, after that the lights will always open when you slide the keyboard .
If i helped press thanks , good luck .
Click to expand...
Click to collapse
never
ever slide open the phone when the screen is locked
ur flex cable will get damaged and ur display will be in 2 partition
Sent from my U20i using Tapatalk 2
Crazy Seed said:
hey man, first make sure if the rom only opens the keyboard lights in dark places because some roms make that happen to save battery.
Second, a trick that i use and find out myself ( so i don't know if it will work for you ) without any app is this: with screen blocked, slide the keyboard, the lights will open, after that the lights will always open when you slide the keyboard .
If i helped press thanks , good luck .
Click to expand...
Click to collapse
It doesn't work. It doesn't on even in the dark or night..But thanks for answering.
Other solutions??
yes yes yes, you should take care of your flex. just here on a thread http://forum.xda-developers.com/showthread.php?t=1935124
And about the lights, on some rom the KbFix isn't working. try it to MiniCM10 and the lights will work properly without the KbFix.
Well, i think that you could try: search files ( in the winrar of the rom ) in the other roms that are working and put those files on your rom, if that doesn't work you only have 2 choices: a Fix ( but like you say, it's more battery draining ), or install a rom that is working on that, stark v3 is working on that so give it a try .
Crazy Seed said:
Well, i think that you could try: search files ( in the winrar of the rom ) in the other roms that are working and put those files on your rom, if that doesn't work you only have 2 choices: a Fix ( but like you say, it's more battery draining ), or install a rom that is working on that, stark v3 is working on that so give it a try .
Click to expand...
Click to collapse
Ok, but which files?
Rawwr said:
never
ever slide open the phone when the screen is locked
ur flex cable will get damaged and ur display will be in 2 partition
Sent from my U20i using Tapatalk 2
Click to expand...
Click to collapse
It`s true. Firstly my proxymity sensor stoped working. After that display was in 2 partions. Status-bar was at the bottom of the screen. Also my phone was unable to boot. It was always rebooting at the start. after disassembly i saw broken flex cable. now i am waiting for replacement parts.
Hi everyone,
I hope this is the right forum, this is my first thread
I am having a problem with ANY AOSP rom I ve installed, no matter wich kernel I try with the rom. When taking a picture with flash in auto mode or ON mode, the phone shuts off and I ve to pull out my battery to reboot. It happens 8/10 times. With flash OFF it works OK
I ve reading lots of threads of people with similar problem even in different devices (nexus, etc). The weird thing is that in tw rom (wanamlite) or any stock sammy rom, the camera and flash works flawless.
I ve tried almost everything. I really want to switch to CM or PA with Halo and this is backing me down.
I ve read in other threads that sometimes is has something to be with the battery but I ve tried 3 different batteries, 2 original and a chinese one, tried taking pictures with battery full, battery low.. and still shutting off on AOSP and flawless on touchwiz.
I ve tried every single camera app in the store. All shutting off my phone in AOSP and working in touchwiz.
however I discovered that with the flash in TORCH MODE (allways on) I can take pictures without any problem. Tasker has an option to take pictures and set the flash to torch and this is what I am using. However, its anoying to use this workaround because with tasker I cannot see what I am taking photo at. And with a camera app that supports torch mode, the flash is allways on, not only when press the take photo button.
I am trying to make tasker turn flash on, press take picture button, and turn flash off, so I can create a scene over the camera app button to make tasker run this task (or use overlays to make a floating widget)
I managed to find the tasker way to press the take photo buton (input keyeven 27), and I tried to use tasker and TESLAflashlight to turn on and off the flash before an after the picture, but teslaled doesnt work while the camera is in use by the camera app.
However, if I use the system widget to toogle flashlight or the flashlight app that comes with CM, the flash on and off switch works while the camera is open!
The problem is that I cannot make tasker interact with the flashlight widget (it is not a shorcut so i cannot use autoshortcut)
Is there a shell command to run in terminal emulator that can turn on/off the flashlight while the camera app is in use? That would solve everything for me..
Any ideas?
Thanks in advance, wonderfull comunity, and sorry for my bad english..
churrolakra said:
Hi everyone,
Click to expand...
Click to collapse
Its not. It needs to go in the Q&A section
churrolakra said:
Hi everyone,
I hope this is the right forum, this is my first thread
I am having a problem with ANY AOSP rom I ve installed, no matter wich kernel I try with the rom. When taking a picture with flash in auto mode or ON mode, the phone shuts off and I ve to pull out my battery to reboot. It happens 8/10 times. With flash OFF it works OK
I ve reading lots of threads of people with similar problem even in different devices (nexus, etc). The weird thing is that in tw rom (wanamlite) or any stock sammy rom, the camera and flash works flawless.
I ve tried almost everything. I really want to switch to CM or PA with Halo and this is backing me down.
I ve read in other threads that sometimes is has something to be with the battery but I ve tried 3 different batteries, 2 original and a chinese one, tried taking pictures with battery full, battery low.. and still shutting off on AOSP and flawless on touchwiz.
I ve tried every single camera app in the store. All shutting off my phone in AOSP and working in touchwiz.
however I discovered that with the flash in TORCH MODE (allways on) I can take pictures without any problem. Tasker has an option to take pictures and set the flash to torch and this is what I am using. However, its anoying to use this workaround because with tasker I cannot see what I am taking photo at. And with a camera app that supports torch mode, the flash is allways on, not only when press the take photo button.
I am trying to make tasker turn flash on, press take picture button, and turn flash off, so I can create a scene over the camera app button to make tasker run this task (or use overlays to make a floating widget)
I managed to find the tasker way to press the take photo buton (input keyeven 27), and I tried to use tasker and TESLAflashlight to turn on and off the flash before an after the picture, but teslaled doesnt work while the camera is in use by the camera app.
However, if I use the system widget to toogle flashlight or the flashlight app that comes with CM, the flash on and off switch works while the camera is open!
The problem is that I cannot make tasker interact with the flashlight widget (it is not a shorcut so i cannot use autoshortcut)
Is there a shell command to run in terminal emulator that can turn on/off the flashlight while the camera app is in use? That would solve everything for me..
Any ideas?
Thanks in advance, wonderfull comunity, and sorry for my bad english..
Click to expand...
Click to collapse
Tried AOSP Camera Mod 2.60 in the themes and apps section?
rootSU said:
Its not. It needs to go in the Q&A section
Tried AOSP Camera Mod 2.60 in the themes and apps section?
Click to expand...
Click to collapse
I am sorry. Didnt realize.. I will post in the correct forum next time.. can I move it to the correct forum or an admin will?
Yes I ve tried that mod, and also tried a port of the tw camera (http://forum.xda-developers.com/showthread.php?t=2370869)
Same problem with both.
Also tried Camera zoom Fx, Camera 360, Pro HDR, Camera JB+, Camera MX, etc... also same problem..
churrolakra said:
I am sorry. Didnt realize.. I will post in the correct forum next time.. can I move it to the correct forum or an admin will?
Yes I ve tried that mod, and also tried a port of the tw camera (http://forum.xda-developers.com/showthread.php?t=2370869)
Same problem with both.
Also tried Camera zoom Fx, Camera 360, Pro HDR, Camera JB+, Camera MX, etc... also same problem..
Click to expand...
Click to collapse
All those camera's that you also tried, just use the existing software and libraries so if your main cam was not working, they definitely wouldn't either.
The TW port isn't fully functional. You'd need to stay with AOSP cameras.
When you say every AOSP ROM you tried, could you name some? It might be a camera firmware issue. There is a thread about camera firmware somewhere.
rootSU said:
All those camera's that you also tried, just use the existing software and libraries so if your main cam was not working, they definitely wouldn't either.
The TW port isn't fully functional. You'd need to stay with AOSP cameras.
When you say every AOSP ROM you tried, could you name some? It might be a camera firmware issue. There is a thread about camera firmware somewhere.
Click to expand...
Click to collapse
I ve tried paranoid android 3.97, cyanogenmod 10.1 , temasek 4.2.2 and temasek 4.3, cdroid, and in each test I tried siyah kernel, googy max, and of course the kernels that comes with that roms by default..
I ve also tried the huawei camera..
I ve updated the camera firmware in the way this threads mentions (http://forum.xda-developers.com/showthread.php?t=2113526)
NOW MY FIRMWARE IS LIKE THIS
Phone/CAM FW Ver Check:
REAR CAMERA:
Cam FW VER: ZDFF03 / (I used to have ZDFE02)
Phone FW Ver: ZDFI02
FRONT CAMERA
CAM&PHONE: S5K6A3
The same problem of phone shutting off used to happened before I updated the firmware..
Really driving me nuts
EDIT:
Now I ve updated the firmware once again and now It is like this
Cam FW VER: ZDFI02
Phone FW Ver: ZDFI02
booted into temasek and the problem persist
:/
Sorry - I do not know the problem then
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Sorry - I do not know the problem then
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Nevermind bro, thank you for your kindness..
UPDATE:
I ve realized that the problem has place only when my battery is below 60%. I am thinking thas the problem has to be with battery/voltage/etc..
The weird thing is that I ve got 3 batteries and in all 3 of them happens the same. And stranger than that, is the fact that on touchwiz I can take pictures with flash even when 5% battery.(so its not a hardware problem)
Maybe AOSP roms have a different way of managing voltages. I ve tried to use steaks and reduce cpu/gpu voltages a little but it didnt help.
I will buy a new battery different to the original ones that i have and try again.
If someone is interested I share my workaround.
I use tasker and use "take picture" using torch mode (I made an scene over the shutter button of the aosp camera app so when I click on it tasker takes the picture). The problem here is that the pictures are stored in tasker folder, so sometimes it takes a while to appear in the gallery.
Or the other method I am using is the following. I used overlays to put a invisible widget toggle of the system flashlight on top left corner of aosp camera, and another invisible widget over the shutter button to trigger a tasker task. The tasker task consist of a couple of console lines that simulates myself touching the screen, so it simulates a touch that toggles de flashlight, then simulates a camera button press and then again simulates a click over the flashlight widget to turn it off.
I know this sucks, but is the only way so far
I ve managed to find a workaround with tasker only
su -c "echo 1 > /sys/class/camera/rear/rear_flash" (turn flash on)
input keyevent 27 (take photo)
su -c "echo 0 > /sys/class/camera/rear/rear_flash" (turn flash off)
The result is pretty the same that the camera flash on.. no blurry pictures, torch duration the same, etc.. so thats it for me..
I hope this can be usefull for people having the same problem.
I tried taking a picture at 30% with "A better camera" with flash and it worked on CM, but with the default camera app the phone goes black
This has been pestering me for quite a while now, at first it started below 20% battery, then 30% and now 50% ... I've ordered a new battery yesterday and I have it charging now, will know when its below 50% when it's any better.
Maybe it has to do with the camera firmware, but I doubt it.
Solved. Was the battery in my case. The 3 batterys. I think that messing around with charging voltaje in stweaks made my batterys gone bad. I ve ordered 3 chinese new batterys and now never shutsoff
Enviado desde mi Galaxy Nexus mediante Tapatalk
Great
Envoyé de mon GT-I9300 en utilisant Tapatalk
Same here, bought a new battery and the problem is solved. Can snap a photo with flash at 2-3% battery left now.