I've searched all day for this, but haven't found anything.
Frequently, I have the camera zoomed and tweaked the way I want, just waiting for some action shots...and two minutes later, the camera app returns to the home screen. If I'm actively using the camera it will stay on, but after two minutes of inactivity, it returns to the home screen. Then I have to re-open the camera app and reset all my settings, focus, and zoom. It's a giant pain.
Changing the Settings > Screen Timeout option doesn't do anything, as the screen isn't actually timing out - it's just closing the camera app and bringing me home.
Does anyone know of a mod, hack, or some edit I can make to increase the length of time before the camera timeout? I know extending keeping the camera active longer will put a bigger dent in my battery life, but that isn't a concern when I'm trying to take great pics.
I have a Verizon Galaxy S6 Edge, rooted, stock, running Android 5.0.2
Thank you in advance
*bump*
bump
Related
I have an i760 smartphone with a cracked screen that I want to turn into a sort time-lapse camera. The idea is to get it all set up using EveryWAN, start snapping shots and just let it run until I stop it or it runs out of battery. The result should be a continuous record of whatever event I leave it running at. It would be a cool way to record parties and events like that without having to run around with a camera in your hand all night.
I searched for a program/hack to do this and came up with a few things that will be similar (tinycam on this board) but I would like to try the continuous shot thing anyway as it has its own cool factor.
What do you guys think? Is this something that can be altered within the system files or is it set in stone with the OS? Looking forward to your thoughts!
No one has any ideas? I would think this would be a fairly simple mod though I'm not sure how this stuff works.
Bump Bump Bump It up!!!
So I've done some playing around and here's what I've come up with...
If TinyCam or VIO for windows mobile had better/ongoing support and were modified to use higher camera resolutions and effects, etc. I would use one of those in an instant. The problem is they're both limited to picture resolutions of under 200x200 and have no support for low light shots.
I played with the registry keys on the i760 but can't get any changes to take effect or remain changed.
HKEY_CURRENT_USER>Software>Samsung>Camera
I set,
PictureShotMode = 2 (multishot/continuous)
MultiCount = x (Works for 3,6,9 but nothing above the defaults)
This makes the camera start up in multishot mode but inputing values higher than 9 resets the shot count to the default 6 in the camera settings menu. So something is obviously handling this in a different way. Can camera.exe check these settings as it is launched and revert anything back to default that is out of its set range?
Anyone have any ideas on where I can go from here?
I am having this issue using the camera app on my Sense 3.0 ROM for the Evo.
I've noticed this on all Gingerbread based ROMs.
The camera app does this thing where it increases the brightness upon clicking on the app, and reduces it after exiting.
This is problematic for me, because I am a college student who uses my phone to take pictures of presentations in class. It is distracting for other students, especially in a dimly lit PowerPoint setting, to see a bright phone lifted up so that I can take a picture.
There are already enough idiots out there with their Macs on full brightness, I don't want to be part of that problem.
Same thing happens to my Desire : screen goes full bright when in Camera.
I have tried digging in the camera settings to see if there is a way to turn it off, but I cannot seem to do so.
Do you know of any way to turn that off.
I'm sure this is helpful when you are outdoors and suddenly need to grab a picture, but it isn't in my case.
anishannayya said:
I have tried digging in the camera settings to see if there is a way to turn it off, but I cannot seem to do so.
Do you know of any way to turn that off.
I'm sure this is helpful when you are outdoors and suddenly need to grab a picture, but it isn't in my case.
Click to expand...
Click to collapse
It's not an issue it's built in to Gingerbread, just like the TV off animation...Google probably figured you'll need max brightness to use the cam, to help with viewing the screen. There's nothing you can do, if you change the brightness in settings, it doesn't change the cam setting.
But you can turn off animations if you want to.
anishannayya said:
But you can turn off animations if you want to.
Click to expand...
Click to collapse
Yeah, but the camera thing can't be toggled, perhaps you can ask a dev to take a look into the source code, there should be information on how to change the brightness there.
LOL, I don't have enough posts to post in a dev thread.
Mods, please move if this isn't the right section (I contemplated the development section but opted against it).
I'll try to be short while providing enough background to get the more knowledgeable people here the info they need to help me with this problem. Essentially, i have a 32gb P6210 that I'm going to flush mount in my dash to use for in car entertainment. With no access to the hardware buttons I did some research on what would realistically meet my needs (especially getting the screen back on without the power button).
I found Tap Tap App on the market and the widget allows me to turn the screen off and waving my hand in front of the proximity sensor four times turns the screen back on. The issue is that, randomly (has ranged from 10 minutes to 17 hours), the proximity sensor is turned off when the screen is off, making the app inconsistent, even with "never turn off sensor" checked within the app. I'm in talks with the developer and he mentioned that the proximity sensor turning off with the screen off is dependent on the underlying rules built into individual ROMs. I'm on the stock ROM.
I need to know if anyone has info on how to keep the proximity sensor on indefinitely with the screen off so Tap Tap App has the input needed to continuing working as designed. I dont care about battery drain at all, the tab will have constant power. I'm rooted with clockwork mod recovery so if anyone has a system file I can edit, a zip i can flash, a tasker profile you know will work, etc, please post it up. Thanks in advance!
Kinda lonely in here...anyways, as an observation update, the app i was using, Tap Tap App, worked far less reliably using the Power button widget vs having the button in the notification area.
Conversely, I found a very similar app called "Soft Power" and have been using it the past 3 days with no issues. It has no widget option and only has the option for turning off via notification area. I'm thinking that always running the notification area by default means a background service is running to keep it there. I have not yet been able to not wake it up by waving my hand over the prox sensor. So for anybody with similar needs to mine in terms of not wanting or being able to access the power button, this has been a good alternative thus far.
I tried it on my phone. It does not work at all.
LG Optimus 2X 2.3.4
It looks like a promising application.
Perhaps it works on ICS ?
Hi,
I would like to use Tasker to control screen on/off times based on following conditions:
1) Keep screen on when reading/using mobile:
a)IF SCREEN IS ON: If handset is in vertical position (reading position), either in portrait or landscape depending on orientation set in android then screen should stay on. This would presume mobile is being used.
b) When handset is laid down on table then screen should turn off after 7 secs automatically or when screen is manually turned off.
note: It would be nice to have a window period of 10 secs after screen off wherein if the handset is picked up within that period, (after the initial 7 secs and before another 10 secs) then screen automatically turns on.
2) NOTIFICATIONS
If notifications are received, have a window period of 15-30 secs where if position of android is changed from desk horizontal to vertical then screen automatically comes on without the need to press power button.This presumes we picked up mobile to view the notification event.
Again first rule applies and screen stays on when reading and turns off auto or manually as per first rule
I have tried but not able to configure rules.
One conflict in mind:-
What if mobile is kept in trouser pocket and notifications are received? Here the gyro won't change as it will go from vertical to vertical position....how to deal with that? Also rule 2 should not auto trigger upon receiving notifications, sensing orientation is vertical when in trouser pocket.
Any help?
Thanks in advance
About the conflict, I think I saw that you can implement a profile that check if your face is in front of the tablet or not (like on S3).
As a personal comment, I would go all way to this aproach: check if you are in front of the camera and decide when to turn screen on.
okty2k said:
About the conflict, I think I saw that you can implement a profile that check if your face is in front of the tablet or not (like on S3).
As a personal comment, I would go all way to this aproach: check if you are in front of the camera and decide when to turn screen on.
Click to expand...
Click to collapse
Hi,
The problem with using the front camera is that it will cause battery drain. The camera would constantly have to keep checking for movement and this would definitely drain battery. I am more inclined to use the gyro for this.
I agree with you, but you can at least double the gyro with camera check. even if it will consume some battery, it will avoid other problems.
Or maybe you can also use the proximity sensor?
Another way I can think is to try and detect the shakes (combination of proximity and gyro). Considering the power of Tasker, I think it can be done.
If you manage to succeed, please let me know. I am also interested in something like this, I just never have the time to build such complex scenarios.
okty2k said:
I agree with you, but you can at least double the gyro with camera check. even if it will consume some battery, it will avoid other problems.
Or maybe you can also use the proximity sensor?
Another way I can think is to try and detect the shakes (combination of proximity and gyro). Considering the power of Tasker, I think it can be done.
If you manage to succeed, please let me know. I am also interested in something like this, I just never have the time to build such complex scenarios.
Click to expand...
Click to collapse
I could not get it to work thats why asking for help.
Hi all,
Front camera is not working. Actually once I open camera's app, the option for the front camera is there, but then after a couple of seconds it disappears. Any fix for this?
Also are there any hints for power savings.? This phone runs out of battery 2 times in a day Bluetooth and wifi are always open. I have disabled adaptive brightness, I keep the brightness level constant, around 25%.
Thanks