I have been trying to play around with Manual mode, and fully admit that I have very little idea what the settings actually do, however, sometimes (a lot of the time), the picture that is taken is almost all white, and bears no resemblance to what I saw on the screen?
Is this normal or is there something up with my phone, or (most likely) am I just not using the Manual mode properly?
Also, when I am in Auto, the option for using the flash is always greyed out? Is this normal too?
Cheers
Stewart
Lower the ISO and make the shutter speed faster (less value = faster), and it'll be fine. or disable AEL.
in Auto mode, hit the gear and make sure HDR is either AUTO or OFF so that you get a flash
Sent from my LG-H815 using Tapatalk
Thanks, I will give it a try.
I had it in HDR On mode, thats why I wasn't getting a flash option.
Cheers
Stewart
If you are using manual mode, you'd want to read up on some FAQs. There are some really good FAQs that are out there.
The only advice I can give you is that there's a histogram and a light sensor on the very top of the bar that will help you figure out what kinda settings you would want to use.
Is it only photos taken with flash that's a problem?
If so do you have a clear case on your phone that's causing the problem.
My ringke fusion clear case causes a white washed out look when using flash because the cut out for the flash isn't big enough.
Related
Hello,
I recently bought an Incredible for my girlfriend on craigslist. It was only 2 months old (in great condition to boot). Either way after flashing CM7.0 I noticed that the automatic backlight setting did not work. I just set it to around 25% and figured I would figure it out later. After 7.0.2.1 came out I flashed that and no change. I then decided to figure it out. It seems that after waking the sensor doesn't work unless really flooded with direct bright light (such as the flash light from my incredible). After that it works mostly as intended.
Here is how I tested it. I lock the phone when in the custom light levels screen. When unlocking the Sensor (filtered / raw) is at 10/10 and will not change no matter what I do until I hit it directly with a bright light. I believe that it will also change eventually letting it just sit. Most of my tests involved using bright light sources. After that the sensor works just fine and changes almost instantly when I cover it with my hand and then move it into regular room light. Is this a known issue? I checked the bug tracker briefly but did not see anything. I have had two others test. One had fine light sensor response the other had the same issue as me.
Anyone have any idea?
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
k_nivesout said:
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It does work but the sensor doesn't respond in a timely fashion.
Have you tried changing the sample interval?
Sent from my ADR6300 using XDA App
What settings are you using? I.E. do you have filtering enabled? What is your window length? Sample interval? Etc.
I've never seen anyone discuss this as a CM7 bug. Based on the way you are describing it, it sounds like you might just need to tweak your settings.
For example, if your window length is very long and sample interval slow, that might be why your readings are taking so long to update. As for why the reading changes as soon as you hit it with a bright light, you could be tripping the reset threshold.
Just in case you haven't checked it out already:
Numerical explanation of the CM7 automatic backlight settings
I will check when she gets off work. All I did was flash cm7. I didn't mess with light sensor settings.
Ok... I have checked it... Not good. Sample intervals were set to 1s. Even still they were not enabled. Messing with the settings didn't yield any results either. It was still sluggish until hitting it with bright light...
I would search, there are multiple threads around where people have posted their settings, I would try those then tweak it to your liking. Also check out byrong's thread, the man knows his stuff.
Sent from my ADR6300 using XDA App
The automatic brightness sucks on stock as well. Just turn it off. You can't see the screen in bright sunlight no matter what the setting is, and you can see it just fine at 64/255 inside. All the automatic brightness does is give you a headache.
Just noticed that the screen mode changes back to standard when using camera.
Is this normal? and is there any way to fix it?
Anyone?
Ur gonna hafto give more detail
Sent from my SGH-I317 using xda premium
What more detail is there to give??? What he said is pretty straight forward. There are four display/screen modes (including dynamic and standard which are the two that I prefer) and he is saying that whenever he uses his camera it switches the screen mode from ex- dynamic back to standard.
Android_Noob_2k12 said:
What more detail is there to give??? What he said is pretty straight forward. There are four display/screen modes (including dynamic and standard which are the two that I prefer) and he is saying that whenever he uses his camera it switches the screen mode from ex- dynamic back to standard.
Click to expand...
Click to collapse
Thats detail...whith some people around here who knows!!!!!!:banghead:
Sent from my SGH-I317 using xda premium
I'd like to know this as well, its really annoying how it changes back to default every time you exit, even when you jump to the gallery and back.
Sent from my SAMSUNG-SGH-I317 using xda premium
Im not sure if ive got this straight. So you normally keep it on something other than default then when it goes to the camera it switches to default then when you exit the camera it stays on default? is that right?
On mine it seems to change to default when i enter the camera (probobly so that pictures look the same on it and any other device you view them on) then switches to whatever i have it set to when i exit.
Hi all,
Just got a galaxy note 2 yesterday and started setting it all up and updating the software etc. I'm new at android so bear with me.
While I was testing it I found an issue with the stylus, it would work from quite a distance from the screen, so had no chance of drawing etc. a quick google revealed that slapping the stylus down hard on the table could fix it ? I tried this and amazingly it did fix it, wow
While charging it I also noticed the charger sqeals a lot of high pitched noises, so I may have to get this replaced as others have on here.
My main query though is that I notice if I have power saver enabled when I scroll up and down in a browser or sky news I see motion blur on text, more so when the text is bold. But turn power save off and it's fine. But then I left it enabled all night and it was fine this morning, wether it was on or off. Restarted the note 2 and the blur was back again ? Is this normal.
And one last thing (sorry) I notice when scrolling up and down in the photo section the image thumbnails tend to rotate anticlockwise a bit and then return to normal position, this is hard to explain but looks odd, is this normal as well ?
Thanks.
Congrats on ur new phone.
High pitch noise is pretty normal. If your phone starts charging in a long time perhaps ask for a replecement one. My uk charger always making that noise but no probs on charging.
I can not see any weird issues with my thumbnails pictures etc so I anmot help you on that one.
Check to see
In settings
Display
Auto adjust screen tone option is checked or not. This option normally changes the tone on the display for stock browser and mail app to conserve battery. If its checked please uncheck and test.
Regards
Sent from my GT-N7100 using xda app-developers app
koalauk said:
Congrats on ur new phone.
High pitch noise is pretty normal. If your phone starts charging in a long time perhaps ask for a replecement one. My uk charger always making that noise but no probs on charging.
I can not see any weird issues with my thumbnails pictures etc so I anmot help you on that one.
Check to see
In settings
Display
Auto adjust screen tone option is checked or not. This option normally changes the tone on the display for stock browser and mail app to conserve battery. If its checked please uncheck and test.
Regards
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Ok thanks for the reply. I do have that setting off, so it's not that. Only seems to relate to power saver, and I can turn off three options within that and just leave the CPU one on and it still does it. So I'm lost.
Yes the photo issue is hard to explain. If the thumbnail images are small it's fine, but when you make them bigger that's when they sort of animate anti-clockwise or tilt while scrolling, then return to normal when you stop scrolling.
Thanks again.
I’m usually the first to hit the Update button on anything I own, but after reading about all the bugs that Sony introduced with the firmware updates following .114, I chose not to update mine. I’ve been stuck with a permanent notification in my Notification Shade informing me of the update ever since but that is a small price to pay for a relatively bug-free phone.
Now that .757 is released, is it safe to take the plunge? I am in no particular hurry because I cannot think on anything in KitKat that I particularly want and I know that Sony hasn’t fixed my major issues with the phone anyway. I know the camera isn’t any better in low light, the proximity sensor lag remains and the fast dormancy “feature” that drains up to 40% of the phone’s battery every day is still there.
But if it is as stable as .114, I’d like to be on the latest and greatest again. Your opinion is welcome. Thank you.
Android 4.4 has a general bug with the sound (google problem) but apart from that I can't find anything wrong. Battery seems great. In fact I like it better than the 4.3 rom.
Sent from my D5503 using XDA Free mobile app
I did not get any bug yet.. But if u r not rooted then dont upgrade.. Else it will reduce functionality of ur sd card
Sent from my Xperia Z1 Compact (D5503)
coolkoushik07 said:
I did not get any bug yet.. But if u r not rooted then dont upgrade.. Else it will reduce functionality of ur sd card
Sent from my Xperia Z1 Compact (D5503)
Click to expand...
Click to collapse
Oh yes, I was nothing but shocked when I installed KK - I'm mean is this an open source droid or a locked down fruit phone?
Not to forget to mention that email+exchange permissions is changed (for my company mail which uses ms exchange servers).
PIN requirement is not enough on KK, only password with atleast 4 letters, 2 numbers and 3 signs
Takes a week to unlock your phone unless you root and install an old hacked version of email+exchange.apk+the risk of getting sacked (if they would find out).
Only thing I miss from KK is the Stamina icon but the GEL Xperia Xposed dev is looking into porting it :good:
coolkoushik07 said:
Else it will reduce functionality of ur sd card
Click to expand...
Click to collapse
What does this mean?
Sent from my D5503 using Tapatalk
rkelsen said:
What does this mean?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
Other apps cant perform operations in sd card in kitkat without root..
Sent from my Xperia Z1 Compact (D5503)
Thanks for the responses, guys. Are there any new features in KitKat, from either Google or Sony, worth updating for?
Google camera.
Sent from my Nexus 7 using Tapatalk
[SIC] said:
Takes a week to unlock your phone unless you root and install an old hacked version of email+exchange.apk+the risk of getting sacked (if they would find out).
Click to expand...
Click to collapse
There is an Xposed mod: http://repo.xposed.info/module/org.flacid.exchangebypass
i've been in kk using RomAur 3.0 and performs great. No bugs, wifi is more stable (but wiht the same cuts and problems of stock 757 rom) than 114.
Sent from my D5503 using Tapatalk
I considered rooting it but the process seems to be far too convoluted for me to attempt. I'm happy with stock.
Sent from my D5503 using Tapatalk
juried said:
Google camera.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Why do you think it is better than Sony’s Camera app? It does not remove the low light issue (where the camera bumps up the ISO much more than it strictly needs to and makes the photos a grainy, unusable mess) and it does not have a manual mode, so you can tackle it yourself. While I like the sparse interface, I have to stick with Sony’s app, because this phone’s camera is useless without manual mode in low light.
Also, on an unrelated note, can any one of you help me get the Personalised Recognition feature back in Google Now? I used to have it in the settings menu but don’t anymore. It disappeared while I was on .114 and I was hoping that updating to .757 would bring it back, but it hasn’t. Do you guys have it?
Sorry to keep bumping my own thread, but this message is just to help out other users who are thinking of installing this update. My recommendation is: go for it!
I had a long list of annoyances with this phone, but I updated to .757 yesterday and it has fixed almost all the issues I had on .114. The major issues that have been addressed:
The Fast Dormancy bug seems to be gone. That Android process that was eating up 40% of my battery life every day no longer shows up on the battery usage screen.
The proximity sensor delay is gone. You bring the phone away from your ear and the display turns on instantly. Magic!
So far, I have no experienced the keyboard skipping issue, so I hope that is taken care of as well.
The only major issue that remains is that the camera is still terrible in low light, thanks to the software that bumps up the ISO needlessly to insane levels. But I can live with that.
I no longer regret buying this thing.
aryayush said:
Sorry to keep bumping my own thread, but this message is just to help out other users who are thinking of installing this update. My recommendation is: go for it!
I had a long list of annoyances with this phone, but I updated to .757 yesterday and it has fixed almost all the issues I had on .114. The major issues that have been addressed:
The Fast Dormancy bug seems to be gone. That Android process that was eating up 40% of my battery life every day no longer shows up on the battery usage screen.
The proximity sensor delay is gone. You bring the phone away from your ear and the display turns on instantly. Magic!
So far, I have no experienced the keyboard skipping issue, so I hope that is taken care of as well.
The only major issue that remains is that the camera is still terrible in low light, thanks to the software that bumps up the ISO needlessly to insane levels. But I can live with that.
I no longer regret buying this thing.
Click to expand...
Click to collapse
I know it's not really a solution, but keep your cam in manual mode and alter the ISO manually. Every phone I've ever used with a camera (iPhones are particularly bad offenders) ALWAYS overcompensate on the ISO in every single environment other than outside on a bright day.
You'll get spectacular improvements if you just get into the habit of entering manual mode, and altering the ISO to the lowest you can get away with (while keeping all the other options on auto) each time you're taking a photo. As far as Im concerned it's far better that way and produces better results than either superior auto or the iPhone's one-button-capture simplicity.
Thanks. I already do that but the default camera app does not make it easy to change the ISO. It takes at least five taps from within the main camera interface to change the ISO and come back. Often, by the time you are done experimenting with the ISO settings, the subject has moved on. Or you end up with a reasonably well lit but blurry shot because the camera UI makes no attempt to inform you of the shutter speed when you take the shot. I have no found any camera apps on the Play Store that make up for these deficiencies either.
aryayush said:
Thanks. I already do that but the default camera app does not make it easy to change the ISO. It takes at least five taps from within the main camera interface to change the ISO and come back. Often, by the time you are done experimenting with the ISO settings, the subject has moved on. Or you end up with a reasonably well lit but blurry shot because the camera UI makes no attempt to inform you of the shutter speed when you take the shot. I have no found any camera apps on the Play Store that make up for these deficiencies either.
Click to expand...
Click to collapse
Yeah fair enough. Good point.
i have a screen issue. same as a problem the video has been upload to youtube. 10 fingers touch the screen not stable.. also issue is when i draw/sketch on the screen. but only happen some times. on a day happen 10 times or more.
i did flash many kind of custom rom.. but the issue still exist.
shaldi said:
i have a screen issue. same as a problem the video has been upload to youtube. 10 fingers touch the screen not stable.. also issue is when i draw/sketch on the screen. but only happen some times. on a day happen 10 times or more.
i did flash many kind of custom rom.. but the issue still exist.
Click to expand...
Click to collapse
What kind of screen issue do u have??
Sent from my Xperia Z1 Compact (D5503)
Good thing for me that went from .114 directly to .757 (i am rooted also)
Camera app have now a 15Meg option
Transparency
Bad things
Conversations.apk (the SMS/MMS app from Sony) is full of bugs. And when I mean full, I really mean it.
Sometimes messages that i already read in the conversations, disappears. All I would see is the blue bubble showing that there's a message, but without the text of the messages. So far this seems to only affect SMS, not MMS.
The color of the bubble when you type, let say blue, and the color of the bubble of the other person talking to you, let say faded blue, often get switch, so reading a conversation might become difficult.
To get the difficulty level higher in following your conversation, sometimes even the side of the screen your bubble is supposed to be attached switch. I mean here, that when you type, your message is next to right side, and your friends reply is next to left side. But now, sometimes you switch side all of a sudden, or worst, sometimes you're on the same side then your interlocutor. Reading SMS with the conversation.apk is totally hardcore now.
Another thing that really piss be off, but I do not know if this is from 757 or if it was already in 114, since I did not use this app in 114, it is the Email software. The Email software stacks/bundles all the messages with the same subjet title when someone reply or transfer your email. (like Gmail does in a browser by default). I really hate this functionality, I prefer to just scroll down to see the previous message if I need to. Unfortunately for me, there's no option in the app to unstack/ungroup emails messages.
Another problem I have with the Email app, this is a bug, because it wasn't doing this in previous build, it is that the Small yellow icon on the icon that tells you that there's 1,2,3 what ever number unread messages, and also the Mail icon in the notification bar, does not go away upon opening the email message. You need to actually press the back button to exit the new messages for it to be marked as read, so that the icon and the notification bar adjust. So if you open an email messages, press the home button to do whatever else, then look back at your notification bar or email icon, you'll think you got new email message, but in fact, it's the same one that is still marked as unread, even if you did open it and read it...
Email and SMS/MMS apps are what I use the most on my phone, I've been using them since I got my first Xperia X10 Mini Pro that was running 1.6, but I've never had that much trouble, they have so many annoying bugs right now. The only problem I've had was the notification LED bug on my Xperia Mini Pro running ICS.
Another thing that I hate, but this is not from 757, but from JellyBean. I come from ICS, and what I hate the most, is the damn white background of all apps. It use more battery and it hurts my eyes in low light room even with minimum brightness. I just wish a stable CyanogenMod with black background pops like in ICS so that I can install it. I've seen some topic about it over here, but they only explain how to uncompile and recompile, too much complicated, I'd rather simply have a package I could simply install with CWM.
EDIT: Oh yeah, I forgot to mention another bug. Somehow the auto-rotate of the screen stopped working twice in the last 2 weeks. Each time I need to go in the accessibility options and uncheck/recheck the auto-rotate option to fix this. (grrr need to wait 5 minutes to be able to edit my msg #xdaforumantispam)
This phone has an LED-backlit LCD display. It does not affect the phone's battery life whether the screen is white or black. Not enough to make a practical difference, in any case.
Sent from my D5503 using Tapatalk
I don't use my camera flash much, so I'm not sure when this started, but all photos taken with the flash have an orange cast or tint to them. In the flash preview before the actual picture, it looks fine, but once the final flash/photo is taken, they're orange. I tried several other camera apps, and they all behave the same way. The only way I could get a proper picture with the flash was to install camera zoom fx, and put the flash in torch mode, then, pictures turned out looking ok.
I was thinking it might be a hardware issue, but the pre-flash is ok, and the flash light is ok. Looking at the flash when the picture is taken, both LEDs light up.
Has any one else seen this issue?
I have an Unlocked US HTC 10 with the stock software (1.96.617.20), and HTC Camera (8.10.779478).
A bit more testing, it seems to only happen when it's fairly dark. And looking at the room when the flash fires, it's very obvious to the naked eye the flash is actually orange, so I don't think it's a camera white balance issue. When there is some additional ambient light, the flash pictures seem to come out ok, the flash itself does not have the orange tint to it.
Do you have a case on the phone? If so, try it without the case.
Had the same issue and like Rolo42 said above, I took off the Ice View case and tried it with flash in an almost pitch black room. No orange tint this time.
Sent from my HTC 10 using XDA-Developers mobile app
This is with no case.
Sent from my HTC 10 using Tapatalk
So, I've played around with this a bit more. I think the issue is when it uses a not full powered flash, that it gets the orange tint. In a completely dark room, the flash is fine. The initial focus flash is fine. It's just the flash with some ambient light that is the issue. For what it's worth, I only see this issue when I have the flash forced on. If it's on auto, and it selects to not use the flash, and I then set it to force the flash is usually when I see this. I've tried on both MM and now Nougat, with the same results. I was kinda hoping the upgrade to Nougat would fix this.
So I was looking through my past pictures looking for a specific one, and I noticed that this orange flash issue has existed since I got the phone. I don't think noticed since I usually only took flash pictures for things like the state of the plumbing under the sink before I tried to fix something. I hadn't taken many flash pictures, and when I did, it wasn't something where I much cared what it looked like, other than that I could make out what was going on.
As a result, I've done a chat with HTC, and when through all troubleshooting steps sans a factory reset. I doubt the factory reset will help it, but if it doesn't, the HTC rep said the next step was replacement under the Uh-Oh protection.
Orange tint
Did you fix your problem?
w69 said:
Did you fix your problem?
Click to expand...
Click to collapse
Yes and no. I ended up getting a replacement 10 about a year ago. The new phone didn't have the same problem. So I have a phone that works, but I didn't actually fix the phone that had the issue.
Sent from my HTC 10 using Tapatalk