I get banding in the camera when in manual mode. Haven't experienced it in auto mode yet, but TBD. I thought it was on screen only, but now I'm getting it in output. So weird. Heads cut out for privacy.
It's to do with the frequency your lights work with. If its 60hz, then you want to use 1/60 or 1/30 or 1/120
Any other shutter will produce those bands.
If your lights work at 50hz, then you have to use 1/50, 1/25 or 1/100
The shutter speed needs to be a multiple of the frequency your lights work with
Applies with video too
There's no way it's only at 60hz lights. I've had it happen in different rooms at my place, and both at my parents and at my in-laws.
If those lights run on utility power they are all flickering at 60Hz.
LED's can be different.
Did you try setting shutter for those speeds. It will make a bigger difference with video if auto isn't able to correct for it
Related
Is there a way to tweak the behaviour of the auto-brightness backlight? At the moment it correctly goes up to full brightness in sunlight, but it doesn't go as dim as I would like under artificial light. At home, after dark, under electric light, I can manually turn the screen brightness down to the minimum level, and it's still bright enough - the auto setting is much brighter than that(although clearly much dimmer than it is in sunlight, so it is doing something).
Can this be tweaked? Failing that, is there an easier way to control the brightness manually - something I can keep running all the time, and which doesn't require the stylus to change the setting?
Try GLight
http://www.ageye.de/index.php?s=glight/about
JustBored said:
Try GLight
http://www.ageye.de/index.php?s=glight/about
Click to expand...
Click to collapse
Thanks, I'll give that a try.
I find Lumos to be more stable and reliable
http://forum.xda-developers.com/showthread.php?t=450318
Ok I havn't tried either of them before but I just installed G-Light.
After a bit of config. it's ok. You need to give each backlight number a wider setting.
Otherwise it'll just flip back and forward in brightness.
So far G-Light is proving rather dissapointing. The phone's built-in "Auto" setting works well, apart from the fact that the brightness doesn't go low enough in dim light - in particular, it manages to choose a good level and then stick to it. G-Light, by contrast, keeps changing the brightness up and down all the time.
I think the notion of having absolute brightness bands may be the wrong way to go. You really want a set-up where the threshold values are in different places depending on whether the light is getting brighter or dimmer. So, as the light fades, you cross a threshold and dim the screen - but when the light goes slightly back up over that threshold, you don't brighten the screen again until it gets significantly higher than that. That way, regardless of the light level, the screen brightness will be steady unless the ambient light level is changing a lot. If you use single threshold values then whenever the ambient light happens to be very close to a threshold value you will always get the brightness going constantly up and down.
Edit: some of the things Lumos does (like averaging across multiple readings) sound hopeful, though. I'll give that a try.
Shasarak said:
So far G-Light is proving rather dissapointing. The phone's built-in "Auto" setting works well, apart from the fact that the brightness doesn't go low enough in dim light - in particular, it manages to choose a good level and then stick to it. G-Light, by contrast, keeps changing the brightness up and down all the time.
I think the notion of having absolute brightness bands may be the wrong way to go. You really want a set-up where the threshold values are in different places depending on whether the light is getting brighter or dimmer. So, as the light fades, you cross a threshold and dim the screen - but when the light goes slightly back up over that threshold, you don't brighten the screen again until it gets significantly higher than that. That way, regardless of the light level, the screen brightness will be steady unless the ambient light level is changing a lot. If you use single threshold values then whenever the ambient light happens to be very close to a threshold value you will always get the brightness going constantly up and down.
Edit: some of the things Lumos does (like averaging across multiple readings) sound hopeful, though. I'll give that a try.
Click to expand...
Click to collapse
Let me know how Lumos is.
Yes as I said earlier you need to widen those settings.
For now I have 5 set to 0-81
6 set to 82-200
8 set to 201-600
10 set to 601-1000
All the rest are disabled by setting the values to -1 to -1
HeavyComponent said:
Let me know how Lumos is.
Click to expand...
Click to collapse
Lumos is also proving dissapointing. It's partly the fault of the hardware - the sensor seems to read 0 even in surprisingly bright light, so the app has no way of telling whether you're at a light level where backlight 1 is appropriate or a light level where backlight 3 is appropriate - both read 0 on the sensor. (This is probably why the default auto option doesn't go below 3 in the first place).
As for Lumos, the author needs to realise that perception of brightness is actually based on an exponential curve. That means that all of the values between level 1 and level 5 are somewhere between 0 and 80 sensor reading. The graph interface is useless for editing custom values with that level of precision - it's trying to squeeze over 2000 values into less than 800 pixels of screen space, and the pixels are tiny! I think you can edit the values directly in the settings.txt file, but that's fiddly - there should be spinboxes, really (as with G-Light).
In any case, you don't want to be editing the values directly! What you want to be doing is taking the phone out of your pocket, looking at it, and thinking "hmm, the screen is too bright at the moment" then adjusting the brightness to whatever level is comfortable for the current ambient light level. The programme should then interpolate the curve that you want, and progressively refine it each time you decide it isn't quite right and tweak the brightness.
I haven't tried to Lumos program yet, but I've been using Glight for a few days. At first I had some issues with it but then I realized that you have to turn the auto light adjustment off in settings first. If not, they'll both be fighting against one another.
Also, you have to set your thresholds pretty carefully as has been already stated. Mine is set to go bright only in bright outside and lowest in a dark room with no light at all.
1 0 to 5
3 10 to 799
8 800 to 2500
I've got mine set low for better battery life and the screen is always readable to me no matter what anyway.
Also, if you're using a the snap on rubber protector (I got a T-Mobile one) it will interfere with the light sensor. I just got one and the lighting is all over the place now. Time to order a full body screen protector.
GLight doesn't seem to work for me. keeps crashing, and the settings don't seem to save at all.
I don't want a sliding scale that Lumos has since i don't think the light sensor is all that accurate (sometimes thinks it's too bright and sometimes thinks its too dark). would rather just have a few settings (pitch black setting, super bright setting, and in the middle) as shawndh suggested.
i have the verizon tp2 - not sure if this might be causing some of the glight probs.
I'm wondering if anyone else is experiencing this issue or maybe i have a weird setting set on my camera.
Issue: Basically in lower lighting areas (not super dark, in a room with a few desk lamps on) the front facing camera shows a good image. Then once i start recording a video (or even in snapchat) the image is light, then after about 1 second in it darkens. it looks like someone has turned off a light in the room.
Is anyone is experiencing this or knows of any tweaks?
I have the same issue.
uncheck auto brightness from settings-display
this still is happening even with the main camera/front camera doesn't seem to be an issue with the auto brightness any other ideas?
Same here, any camera app I use presents this issue. With only low light or indoors. This is the first phone I've owned where it has done this and I'm coming off of nexus 5 and the s3 before it.
I really hope(because I am rooted/custom ROM) that this can be calibrated on a rom type of level and not permanent bc of hardware.
Same issue with Moto G Turbo Edition...
set the Anti-flicker setting to 60 Hz.
I always take photos of my kids playing, but i noticed a big problem with the G4 camera that any moving object looks blurred in the photos even if the movment is slow (eg. Turning heads etc.).
I did not have this problem with my previous Galaxy S5.
Anybody noticed this problem?
Someone mentioned that the camera seems to want to use slow shutter speeds and low ISO values, when left in Auto mode.
As Auto does not provide any adjustments at all, you'd either have to use Manual mode, or try another camera app that allows a little more control. Something to force the camera to use a higher ISO setting, and a faster shutter speed, which would help reduce blurring of moving objects.
Of course, this assumes you are in a well-lit area. If you're indoors, in a moderately-lit area, then you are going to have more trouble regardless.
Manually turn on the flash, that might help. You can toggle the flash mode even if the camera is in auto.
I have kids too and sometimes my pics of them come out blurry too...this is outdoors with a ton of light. These out of focus shots are not a shutter speed thing but more of an auto focus problem.
The camera always wants to re-grab focus whenever you take a picture when the subject is moving. My kids will be in the frame, in focus (green squares on screen to confirm) I push the camera button, then the damn software tries and refocus because my kids are running around, the auto focus pics the wrong focal point and then the shutter snaps...out of focus pic.
I too came from the S5 which had better software. On that phone, if I turned off burst shot, pushing and holding down the camera button would cause the camera to focus on the subject and lock it in, then when I released my finger, it would take an almost instantaneous picture and keep focus... end result always sharp pics of my kids even when running (as long as there was lots of light).
If G4 could have that feature, all would be perfect!
Ah, in that case, maybe try touching the screen to cause the camera to focus on the spot you touched. But, instead of touching the spot where your moving kids are, try touching a non-moving spot on the ground near them, but at the same focal distance. That way, your kids will also be in focus. If that still doesn't work, then maybe switch to manual mode to hold the focus manually.
I've seen a couple posts about delays with adaptive brightness, but this is a different item. I'm seeing that the adaptive brightness alters the brightness a little too dramatically. In a somewhat dark room (not pitch black) the brightness will be at absolute minimum even when the brightness is about 1/3 up on the slider. In a moderately bright room that same brightness setting will be near maximum.
Does anyone else notice this as an issue? I'm just wondering if it's normal (ie, software calibration issue) or if the brightness sensor might not be seated correctly.
It's normal. Or at least it sounds like it is working the same way mine is. And yes, IMO it is a little too sensitive. The Lux app works beautifully if you want an alternative. Also, the goog is known for tweaking this feature over time with updates.
I've noticed this too. The biggest thing for me is walking down the street at dusk (so not dark out yet) I can't read the screen as it turns it all the way down, then, when I walk under a street light, it turns it all the way up to full! It's one extreme or the other, there seems to be no middle ground.
In other words "adaptive brightness has mind of its own!"
This is why I have always kept this setting off. The brightness just changing on its own always annoyed me.
When it works properly (and it should) for ones uses, it's great, it's automatic, what's not to like? It's a pita to always have to change brightness manually just to see a phone display depending on ambient lighting which varies immensely for many users.
jbdan said:
When it works properly (and it should) for ones uses, it's great, it's automatic, what's not to like? It's a pita to always have to change brightness manually just to see a phone display depending on ambient lighting which varies immensely for many users.
Click to expand...
Click to collapse
I agree. I have it set to maybe around 15-20% (centered over the WiFi symbol below it) and I never need to touch it. Gets dark enough for night driving and bright enough to read outside. Never found it stuck on one or the other when it shouldn't be.
Sent from my Nexus 5X using Tapatalk
If you buy the app Lux you can customize how it adapts your brightness. The free version is good to but you have to use mostly default settings. By default it only adapts brightness when the screen turns on.
Is anyone having issues with auto brightness, jumping up and down every few seconds? Im currently sat in a dimly lit room with the TV on and my screen keeps changing brightness levels every few seconds, if I pull down the notification area I can see the slider jumping about. I'm guessing the phone is reacting to the TV changing brightness levels as the picture changes but it seems way too sensitive.
Yeah known issue afaik. I'm hoping it gets resolved on an update
rosso22 said:
Is anyone having issues with auto brightness, jumping up and down every few seconds? Im currently sat in a dimly lit room with the TV on and my screen keeps changing brightness levels every few seconds, if I pull down the notification area I can see the slider jumping about. I'm guessing the phone is reacting to the TV changing brightness levels as the picture changes but it seems way too sensitive.
Click to expand...
Click to collapse
One of the fixes in the November update was "Improvements for auto-brightness response in certain lighting conditions.".
I think auto brightness has always been an issue with Pixels. Its a feature I always turn off at this point
rosso22 said:
Is anyone having issues with auto brightness, jumping up and down every few seconds? Im currently sat in a dimly lit room with the TV on and my screen keeps changing brightness levels every few seconds, if I pull down the notification area I can see the slider jumping about. I'm guessing the phone is reacting to the TV changing brightness levels as the picture changes but it seems way too sensitive.
Click to expand...
Click to collapse
Yeah it is up and down like a brides nighty when the light it low on mine, it isn't smooth like it was on my Pixel 5. It feels a bit like the sample rate needs a longer delay because just an increase in brightness on my TV can send my Pro brightness shooting up, the adaptive display needs to wait a few seconds before acting.
MrBelter said:
Yeah it is up and down like a brides nighty when the light it low on mine, it isn't smooth like it was on my Pixel 5. It feels a bit like the sample rate needs a longer delay because just an increase in brightness on my TV can send my Pro brightness shooting up, the adaptive display needs to wait a few seconds before acting.
Click to expand...
Click to collapse
Yeah my pixel 5 and 4a 5G never had this issue (same room and lighting conditions) its crap we have to pay to be beta testers nowadays, guess we will have to wait for another "fix" in next update.
crucialcolin said:
I think auto brightness has always been an issue with Pixels. Its a feature I always turn off at this point
Click to expand...
Click to collapse
Should we really have to turn things off, considering the cost of this phone? Throw in a case and charger and your over £900 in for this phone, everything should work out of the box without having to turn off features.
It's horrible. When I sit at night in a dark room watching TV, it seems to react to the TV and jump all over the place. Never had this on a phone before. Why can't Google get auto brightness right? It's ridiculous.
Personally, I've always preferred Pixel's handling of auto-brightness to that of my recent Note 10+. I thought Samsung's auto-brightness didn't adapt very well (besides the dimmest not being as dim as the Pixel when using in the dark).