Related
Go to HKLM/Software/HTC/Camera/Common and change EnableFrameRateInfo to 1
ok now go back to either your camera or video camera and you'll see there's now a little box telling you the frames per second. If you play with it you'll notice that it gets very poor in low light (probably around 3 fps) to slightly better in bright light (15 or so). Either way, these frame rates are probably causing the blurry photos. Not sure of the answer, but this shows the problem. Any one have thoughts on if this is a software or hardware issue or any way to tweak this? If you're getting 3fps then the image needs to be entirely still to not blur...
thanks bugsy. i've tried powering off the screen while in camera mode for 10-15 secs and then turning it back on which seems to reduce some of the camera lag or low framerates and now i can more accurately judge what the difference really was. i went from 3-5 fps, to 15-20 fps.
!
10x for the tip bugsy i never got to 20fps even ouside in day lite so i really
hate the way TP is recording....if you move your hand it records like
crap...found a funny one: while using flash lite the lite is reflecting in the
picture so i try to fix it (take one photo with flash lite in dark and then
take another one with the back cover from TP off ) look in the right side of picture to see the diference ,to fix it i painted with a black marker inside the
phone back cover near camera and flash !!!
any ideas how to fix this? 3 frames per second is a total joke. I can point it at a light and move the camera all over and get 15 fps with all sorts of movement. If I move it to low light I'm at 3fps... 15 is tolerable...3 is almost unusable.
dansobolanu said:
10x for the tip bugsy i never got to 20fps even ouside in day lite so i really
hate the way TP is recording....if you move your hand it records like
crap...found a funny one: while using flash lite the lite is reflecting in the
picture so i try to fix it (take one photo with flash lite in dark and then
take another one with the back cover from TP off ) look in the right side of picture to see the diference ,to fix it i painted with a black marker inside the
phone back cover near camera and flash !!!
Click to expand...
Click to collapse
I had noticed that flash reflection too, it really ruined flash shots! Well, I did like you said and took a dark marker and marked the metal part on the inside of the back cover, and now no more crappy flash photos, THANK YOU much for this tip!
bugsykoosh said:
Go to HKLM/Software/HTC/Camera/Captparam/Common and change EnableFrameRateInfo to 1
ok now go back to either your camera or video camera and you'll see there's now a little box telling you the frames per second. If you play with it you'll notice that it gets very poor in low light (probably around 3 fps) to slightly better in bright light (15 or so). Either way, these frame rates are probably causing the blurry photos. Not sure of the answer, but this shows the problem. Any one have thoughts on if this is a software or hardware issue or any way to tweak this? If you're getting 3fps then the image needs to be entirely still to not blur...
Click to expand...
Click to collapse
On mine, that key is found under HKLM/Software/HTC/Camera/Common.
californiarailroader said:
On mine, that key is found under HKLM/Software/HTC/Camera/Common.
Click to expand...
Click to collapse
you're right - I'll change the first post
No worries, thanks for the registry tip on this!
eastvanchinaman said:
thanks bugsy. i've tried powering off the screen while in camera mode for 10-15 secs and then turning it back on which seems to reduce some of the camera lag or low framerates and now i can more accurately judge what the difference really was. i went from 3-5 fps, to 15-20 fps.
Click to expand...
Click to collapse
10x but not really working for me,but i see that it works for many other people so i think that this have something to do with the battery power then i unchek Auto adjust backlight from power menu then start the camera it shows 8 to 12fps then in 1-2secs it checks it self somehow Auto adjust backlight box automatic and gose back to 3fps .... :-?? so i think the problem is from battery power that camera uses .... !!! (sry for my english )
californiarailroader no need to Thank me mate,i'm really glad i can help xda-developers with something (more or less) !
I have been playing with my TF for a little over a month. I updated to 3.1 so I don't know it this is an issue. My problem is the ambient light sensor. It doesnt seem to work. No matter what brightness i have or if it's on auto or not I have never seen my screen get dimmer or brighter in any situation. I put a flashlight right on the sensor and I see nothing change onscreen. Anyone else have this going on?
My light sensor appears to work. It does have a fair amout of hysterisis in it otherwise it would drive you nuts.
Sounds like you're either not shining your torch at the actual sensor or yours really doesnt work. It's about an inch to the left of the front camera in case it's the former. It should poll every 4 seconds when on 'auto' brightness, and change the screen accordingly. I find that it works, but it doesnt really change the screen brightness to the best level for viewing. I'm sure there's an app to deal with this although I usually just set it manually. It's easy enough to do.
Oyeve said:
I have been playing with my TF for a little over a month. I updated to 3.1 so I don't know it this is an issue. My problem is the ambient light sensor. It doesnt seem to work. No matter what brightness i have or if it's on auto or not I have never seen my screen get dimmer or brighter in any situation. I put a flashlight right on the sensor and I see nothing change onscreen. Anyone else have this going on?
Click to expand...
Click to collapse
It's perfectly possible the sensor is sensitive to IR or some other wavelength in daylight that's not emitted by your flashlight. The sensor definitely works just fine for me.
I never notice the screen changing brightness (it's designed to gradually change according to the different light exposure so human eyes don't notice it changed, but in reality it did change). When I'm in a car however, if there's trees near by and it blocks the sun every so often, I can clearly see the brightness suddenly shooting up and dropping down. I don't think it works with lamps though (turning on my lights didn't make the display brighter), only light from the sun.
It works quite well now that I'm updated to 3.1. It went through various stages of not working or just messing up back on the 3.0 updates. Now it reacts, increases and decreases and the screen is bright enough.
Mine seems broken too. Strange, because this would be the first thing wrong with me Transformer and it doesn't even seem like a common problem.
This and the browser typing lag alone are making me think of selling it.
Okay, mine is definitely broken.
I just tried it by going out in the balcony and then going in the bathroom and shutting the door - nothing happens.
Seriously Asus, what were you doing when you designed and built this thing? My Tranformer is otherwise perfect - no light bleed, no creaks, no pubes under the screen, no issue at all. Except the light sensor... it seems maybe the perfect Transformer doesn't exist.
mine works
Okay, some progress.
Shinning my HD2's bright dual LED's right onto the sensor actually makes the sensor work.
But still, this thing is apparently not calibrated well because going from outside to a totally dark room didn't change the brightness - it doesn't matter if putting two LEDs right onto the sensor makes it work, that's not why it's there.
On my TF, it takes about a minute for the brightness to change when I move from a dark room to the great outdoors.
Give it a little time for the software loop to kick in
Is this any way to calibrate this sensor? It's works horrible!
Shawn_230 said:
Okay, some progress.
Shinning my HD2's bright dual LED's right onto the sensor actually makes the sensor work.
But still, this thing is apparently not calibrated well because going from outside to a totally dark room didn't change the brightness - it doesn't matter if putting two LEDs right onto the sensor makes it work, that's not why it's there.
Click to expand...
Click to collapse
Do you have a screen protector?
Not to go off topic but I only had keyboard lag when I was using the Asus keyboard Shawn, have you tried the default Android keyboard?
There is an app in the market called androsensor that will tellyou the values for many sensors including the light sensor.
Mine is measured in lux and ranges from 0 to 400 indoors it does not update quickly mine updates every few seconds.
Sent from my Transformer TF101
vladdt said:
Is this any way to calibrate this sensor? It's works horrible!
Click to expand...
Click to collapse
There is a paid program i use and love called lux
Well worth the price imo. It essentially lets you manually adjust the screen brightness for the various light levels over time, remembers these and will automatically put the screen at those levels next time. It alo has some logic too but i cant talk to that.
Sent from my Transformer TF101
It seems to work for me except that it doesn't adjust the levels properly. I can be in a somewhat bright room and the brightness is still at its lowest level, making it difficult to read. However, in broad daylight, the brightness shoots up.
I might try Lux as suggested previously.
lrissman said:
There is a paid program i use and love called lux
Well worth the price imo. It essentially lets you manually adjust the screen brightness for the various light levels over time, remembers these and will automatically put the screen at those levels next time. It alo has some logic too but i cant talk to that.
Sent from my Transformer TF101
Click to expand...
Click to collapse
+1 for Lux - great app
Sent from my Transformer TF101 using Tapatalkr
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux. The N4 was much better as you could make a distinction between the dim light and no light at all.
On the new N5 you have to set the zero lux level so it's bright enought for moderate light, which means it's far too bright at night.
Why is the N5 sensor so poor? Or is the kernel? Really, this is pretty basic stuff. Come on Google, we want the autobrightness to work fine without having to download apps to try and fix the most basic settings.
(As per other threads, the N5 stock autobrightness is almost unusable!)
Same here. Only occurs in the kitchen under the spotlights. I've had 2 phones and the same has happened on both using lux.
Sent from my Nexus 5 using Tapatalk
Happy to see others having this issue as well. I always figured it was a Kitkat bug.
I had some dead pixels on my first N5, so I got a replacement. The replacement is now exhibiting this weird sensor issue (also spiking up to 30,000lux based on device orientation).
I have the same issue on my N5, sudden freak peaks of 15000 lux or more, then suddenly back to normal values of 50-80. Same behavior on stock kernel and Francos Kernel.
Hoping for a quick fix by Google.
Kusie
I'm having the same issue too, but it appears to be under certain lightbulbs that I have this issue. For example in 2 different situations, one I was in a restaurant and another while I was in my bathroom, and my phone would constantly pick up either 0 lux or 30000 lux (depending on the angle of the phone under the light). This is under halogen lighting.
When I get out of the restaurant and under regular lighting and when I'm in my bedroom (LED/CCFL lights), the light sensor would behave normally.
Anyone else have these issues?
Aria807 said:
Anyone else have these issues?
Click to expand...
Click to collapse
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Can the sensor be calibrated or is it just bad hardware? This is a real annoyance. My S4 doesn't read 0 lux unless there is absolutely zero and it never jumps around. Even it's own screen reflecting on my face will cause it to read 1-10. That level of sensitivity is great for setting up lux to go subzero. Maybe the kernel is translating the sensor voltage output incorrectly?
Sent from my Nexus 5 using xda app-developers app
rabaker07 said:
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Click to expand...
Click to collapse
Lux is a measurement of brightness.
I thought it was Lux causing it, but I have tried full wipe + reflashing a new rom, and my sensors still go a lil whack. This is flashing new rom + immediately downloading a sensor tool and checking the readings before installing Lux or any other apps.
However, Lux came out with a new version a week or so ago and it seems to have been waiving those spiked readings, so my phone atm isn't acting up super dim to super bright and back.
I still have this issue on 4.2.2.,very annoying. Is this a software issue or bad sensors?
Starts to piss me off so badly I think about sending my N5 back to google.
Happens both on stock auto brightness and yaab.
Help please?
Kusie
Yeah same here, very annoying, have to use Manuel britness very often
I have this same problem too. Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
I feel like the sensor is too far recessed into the phone and causing a tunnel effect. If the phone is looking at a dark shirt or surface that's a foot away from it, it will register 0 even though there's plenty of ambient light. This seems like a design flaw or a flaw in android's API.
Using the full version of Lux app might be able to fix it since it allows you to use the camera for ambient light detection but I haven't purchased the full app yet so I don't know.
Really wish android would have a solution for this because it's quite irritating.
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
clocinnorcal said:
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
Click to expand...
Click to collapse
With the stock auto brightness it was too bright in most cases and also in some cases the brightness would spike. Downloaded the free version of lux app in order to try to fix the problem and while it can adjust the brightness to be lower, the problem is that the light sensor gives low readings straight from the api.
I just installed Lux and I can't reproduce it on my Nexus. Mine always behaves correctly in automatic brightness, so I guess it's a hardware problem that only affects some devices?
I jump now in here as i have the same problem unfortunatley. I have no clue if its hardware related or software, but on my HTC One with kitkat running the same rom i dont have such issues s i guess its a HW fault. If anyone finds a solution or something that fixes this mess, would highly appreciate if wwe could keep this thread alive
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
coolguy949 said:
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
Click to expand...
Click to collapse
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
n3ocort3x said:
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
Click to expand...
Click to collapse
I remember reading something weeks ago that the sensor doesn't work well with certain bulbs. I can't seem to locate the thread though.
Hi all, just looking for a suggestion as to what could be causing my issue.
long story short, got phone yesterday afternoon gmt, by time I got chance to play with it was around 9pm, anyway I took a quick video with 960fps, good results but bit grainy, probably due to sun beginning to set.
No problem, says it needs good lighting, I'll try it indoors later, so fast forward a couple hours and I got good lighting indoors, photos and video coming out nice and clear, but whenever I try slow mo I get an effect as if my light is on a strobe setting.
Not sure if it's faulty or just really crappy in artificial light, I suppose I can find out soon enough, but wondered what you guys thought
What kind of light do you have? Certain lights such as flourescent actually "blink" 50-60 times a second depends on what hz the electricity in your country is. It's kinda a given that those blinks will be easily distinguished when you slow down time 32 times. All artificial lights flicker but some can be used in high framerate videos while others can't. Even the sun flickers but there is currently no camera able to record in a framerate high enough to see it. When they film in high framerates in a studio setting they actually sync the flickering with the camera so all frames it records are when the light is on.
I think some types of LED lights don't flicker (but be careful, some do) so you can try with them if you have.
Incandescent lamps won't flicker for sure, you can try using them.
kot5nik said:
I think some types of LED lights don't flicker (but be careful, some do) so you can try with them if you have.
Incandescent lamps won't flicker for sure, you can try using them.
Click to expand...
Click to collapse
Ok cool, its definately the lights in the house, just tried it with curtains open n lights off, no strobe.
So i guess im limited to doing slow mo in sunlight or need to buy new light bulbs lol
I have led lightbulbs upstairs, all downstairs ones are old school filament type bulbs, due to hours i work i best get looking for some flicker free lights
I am running Honor 8 on Android 7.0.So when i switch to slow motion the video seems to be low light or gets dark.In natural day light even though it gets darker it still bright enough to see things but in artificial lighting or indoor condition the video gets too dark,Is this normal or only i am getting the issue here.