Ever since I got this phone I've been bothered by the bad framerate of the picture preview while in the Auto modes in the camera app, I thought this was a problem across all LG phones from the past year
Today I had the chance to check out a G5, the camera framerate was noticeably higher when in Auto, not only that, it didn't have just the simple, auto and manual modes, it also had a so called "basic" which is like the auto view with controls on the left which allow you to quickly change settings such as HDR and so, in less taps than on the V20 and without obstruction of the preview.
What is the meaning of this? If you don't take into account the manual video mode, the camera app is much better on the G5, could it be that my phone hasn't received this version of the app yet? Its an H990DS
Hi there, I've got rooted A1 with Camera 2 API enabled.
So, low-light photography on A1 is plain terrible, I've found out that the camera automatically bumps up ISO to values like 6400, and the photos are noisy. Manual mode of A1 allows up to 3200.
This can be fixed by setting ISO manually to lower values, however then you're stripped of HDR in low light and all the different modes.
Next thing is, that in RAW files white dots appear. I've read the same problems existed in ZTE Axon 7 however it was fixed. (https://www.google.pl/amp/s/forum.x...s-pattern-raw-photos-zte-axon-7-t3579684/amp/)
And Oneplus 5 https://forums.oneplus.com/threads/...s-by-third-party-cameras-on-oneplus-5.612091/
The app I used for Raw pics was lightroom, however.
Besides all this, I've got older post on Google camera (gcam), and I don't well, that's another thing I suppose.
So, can anybody try taking raw pics in lightroom with good light and show me results? Did xiaomi fail to implement camera 2 api properly? Did I screw something up?
I wonder if I screwed up something while modding my phone and now I've got some weird issues
[Raw sample](https://i.imgur.com/RO91ThC.jpg)
Take care, peeps.
Xiaomi didnt implement camera api 2, the device out Of the box has no cam2api.
Has anyone noticed Display keeps flickering when auto brightness is on. Even if phone is kept at a fixed position & same amount of light is exposed to the sensor it still keeps flickering. I mean if I'm watching movie it automatically dems or increases the brightness. please confirm how many user experiencing this problem! as per i know it was not resolved from 301 to till 331 update. is it manufacturing defect particularly with specific variant ?
I wouldn't call it it a flicker. More like the auto-brightness feature is so badly programmed that it doesn't transition from dim to bright and vice versa in a smooth, gradual or dynamic manner, like in older and cheaper phones.
My eyes get a shock every few seconds, trying to adjust to the sudden jumps in screen brightness. It's a real pain.
And yes, the issue has persisted through all the OTA updates without any sign of improvement.
Instead of addressing this most basic and "glaring" issue, Asus seems to be intent on introducing bloatware and EIS for the phone and announce it like it's the second coming.
The latest update was supposed to bring with it, system optimization but I don't see any form of basic optimization, let alone calibration, with the screwy display.
I can only guess at Asus' sense of priorities. Or if they're actually blind and/or stupid.
May be it was true that autobrightness was programmed badly manner it was not transist smoothly from dim to bright. But afterall we are facing it at serious level and uptill now asus has not solved yet. I just want to confirm that How many user experiencing screen flicker issue after enabling auto brightness or it was particularly manufacturing defect with specific varient.
its an autobrightness calibration issue,software update will fix it in future,lets hope so
Hello everybody! I found a bug: brightness is flickering even when "auto brightness" ("adaptive brightness") is disabled. Brightness can encrease for few seconds and then decrease to previous level. I read in some reviews that max pro m1 has adaptive brightness which changes depending on content on the screen. I tried to change a lot of display settings, developer settings, i tried to adjust CABC (Content Adaptive Brightness Control) through Nova Launcher (but later I read that CABC controls only autobrightness), and even hard reset. I flashed custom ROMs but it didn't help. Only Lux Dash app helps avoid this bug. But it is not very comfort to use it and I think there must be desicion on firmware level. Did anybody has this problem and any solution? May be somebody has this issue and found custom ROM without flickering brightness?
Sorry for my English, it's not my first language. And thank you for answers!
Hey guys,
so far I’m really happy with my new 6T. But I’ve found one bug which I’d like to see fixed.
I like to use either the sRGB or the DCI-P3 color profile as the standard color profile is just too saturated and contrasty for my liking. And at night, I’d like to use the display night mode, to reduce blue light. Unfortunately, if the screen is off and I wake up the phone, (doesn’t matter if it’s via face unlock or screen unlock) the screen changes itself to Standard color profile and you can slowly see the night mode take effect – but on top of the standard color profile which is, as mentioned above, not my cup of tea. It happens with both sRGB and DCI-P3 profiles and night mode enabled.
Only if you then turn night mode off again, you can literally see the colors jump back to your original set profile. Which obviously cannot and should not be the intended way night mode works, as night mode also reduces contrast and saturation. This can be seen if you have set the color profile to Standard in the first place and then turn on night mode, which basically shifts the colors to sRGB. Curiously enough, if you then lock the phone and wake it up, everything is as it should be and as I'd like it to be when sRGB is the set profile, meaning the color profile stays sRGB like and night mode is in effect.
I’m running completely stock Oxygen OS 9.0.5., no root, didn’t unlock bootloader or anything.
Does anyone else experience this behavior? Any help or suggestions are greatly appreciated!
Thanks!
I've been trying to find an answer to this issue since I got the phone. It is appalling that both ambient display and the lock screen are not affected by night mode. It is completely counteractive to how night mode should work.
And I have no idea why they disable color profiles when in night mode. In the settings menu, once you enable night mode, the screen calibration option is greyed out. But it is clearly not a technical limitation because enabling sRGB and then night mode produces the proper effect of a night-shifted sRGB color space. Waking the phone at night turns night mode off on the lock screen, and puts it in standard profile, then shifts to night-shifted standard profile after unlocking. I hate it.
If you come across an answer, please post it back here so others (and I) can find it.
Also, small technical note: night mode does not affect saturation or contrast or color space, only color temperature. sRGB is an entirely different color space with different saturation and gamma curves.
rriegner said:
I've been trying to find an answer to this issue since I got the phone. It is appalling that both ambient display and the lock screen are not affected by night mode. It is completely counteractive to how night mode should work.
And I have no idea why they disable color profiles when in night mode. In the settings menu, once you enable night mode, the screen calibration option is greyed out. But it is clearly not a technical limitation because enabling sRGB and then night mode produces the proper effect of a night-shifted sRGB color space. Waking the phone at night turns night mode off on the lock screen, and puts it in standard profile, then shifts to night-shifted standard profile after unlocking. I hate it.
If you come across an answer, please post it back here so others (and I) can find it.
Also, small technical note: night mode does not affect saturation or contrast or color space, only color temperature. sRGB is an entirely different color space with different saturation and gamma curves.
Click to expand...
Click to collapse
Thanks for your reply. Glad I'm at least not the only one noticing this issue.
As to your last statement, I would've thought so too. But this does not seem to be the case here. If you set the color profile to standard and then turn on night mode, the color space gets changed to sRGB, at least from what I can see. It looks completely different than the falsely activated night shifted standard profile, and looks exactly like the night mode in top of the sRGB mode, so less saturation and contrast (gamma). I don't know if this is intentional but makes it all the more confusing, because it retains the combination of sRGB + night mode even after locking and unlocking.
ef_x said:
Thanks for your reply. Glad I'm at least not the only one noticing this issue.
As to your last statement, I would've thought so too. But this does not seem to be the case here. If you set the color profile to standard and then turn on night mode, the color space gets changed to sRGB, at least from what I can see. It looks completely different than the falsely activated night shifted standard profile, and looks exactly like the night mode in top of the sRGB mode, so less saturation and contrast (gamma). I don't know if this is intentional but makes it all the more confusing, because it retains the combination of sRGB + night mode even after locking and unlocking.
Click to expand...
Click to collapse
Wow, you are exactly right. I never thought to try that method, but I agree with your assessment. In standard calibration, night mode also toggles sRGB on and off. This is not affected by lock.
In both sRGB and DCI-P3, toggling night mode does not change calibration, but waking from lock leaves it stuck in standard calibration until you toggle night mode again.
And in all scenarios, the lock screen is never in night mode. Also, the add fingerprint page disables night mode and sticks you back into standard calibration with night mode, no matter which calibration you had selected. So the add fingerprint page acts exactly like the lock screen. This leads me to believe that the fingerprint sensor needs a very specific color of light to operate. But that doesn't excuse the fact that calibration keeps switching and getting stuck. I would think they can override that though.
I just made a post about this on reddit. Maybe up vote it to help increase visibility as this is the first mention I've seen about this issue other than this reddit post.
https://www.reddit.com/r/oneplus/comments/9wkkgj/_/
The whole night mode issues and ambient display going max brightness are super frustrating. This is my first non Nexus/pixel since the oneplus 1, and these small issues are making me question if leaving for a less stable manufacturer was a good idea
After doing some more testing, I've determined this whole ordeal is tied to the fingerprint sensor. Deleting all my fingerprints (disabling it entirely) has resolved all the issues of switching calibrations an night mode toggling. Everything works as it should, except ambient display never is night mode. But the lock screen is in night mode.
I'm personally ok with this for now. Face unlock is very quick, and smart lock keeps my phone unlocked at home at night. Hopefully this gets fixed for real in a future update.
rriegner said:
After doing some more testing, I've determined this whole ordeal is tied to the fingerprint sensor. Deleting all my fingerprints (disabling it entirely) has resolved all the issues of switching calibrations an night mode toggling. Everything works as it should, except ambient display never is night mode. But the lock screen is in night mode.
I'm personally ok with this for now. Face unlock is very quick, and smart lock keeps my phone unlocked at home at night. Hopefully this gets fixed for real in a future update.
Click to expand...
Click to collapse
Exactly what i discover. Night mode not works when fingerprint senor is active which means on screen lock and app lock.Don't know weather they do it intentionally(to work fp sensor fine) on not but this is seriously irritating and painful to eyes.
I have a strange behavior that when I play an hdr videos on YouTube or sevice memory or captured in HDR by the mobile it self the full brightness is not engaged automatically as it should
When I first got the phone it was always switching to full brightness with HDR content same with older Samsung phones but now it suddenly stopped
Any help!!
Mine does the same thing. Sometimes it works, other times not. I just chalk it up to Android being Android. It never works properly or consistently.