Database Users

Camera horrible =(

how come the camera on the XDA is horrible, its grainy and dark... i tried adjusting the settings but then after i closed and reopened the camera quality was back to being bad again. is there a fix for this or is that how the camera is.

I mainly use the night mode indoors and save the auto mode for outside. Make sure you work out the settings with your computer; the best pictures on the PDA aren't always the best on the computer and vice-versa.
Oh yeah, I don't think you can make most of the settings stick other than the auto/daylight/dark etc. mode.

I have another problem with my camera...
When i take a shot, the image displayed in the viewfinder before capturing, is perfectly lit with the right brightness-contrast etc.
But when i capture an image, it brightens it up until the image bleeds, and its terrible....I tried to adjust different settings, but it still did the same.
Its good for night shots, but during day time, i get 80% of my pixels completely white!
Not too bothered, as the camera is actually pointless for me....and besides, i'm not the "take pictures often" kinda guy!
San

read my camera tweak topic.

try CoolCamera
http://www.ateksoft.com/files/CoolCameraTest.zip

i found turning off 3g, and using gsm has helped a lot with all aspects of my phone. the camera looks a LOT better compared to a week ago when it was on 3g. back then, i thought it was completely unusable..thats how bad the quality was. and i had tried night time mode indoors, and it all jjust came out blurred

where's the camera tweak post? i'm starting not to like this phone, there is way to many tweaks and changes that have to be done to it just to make it an 'ok' usable phone.

el_illumbrato said:
i found turning off 3g, and using gsm has helped a lot with all aspects of my phone. the camera looks a LOT better compared to a week ago when it was on 3g. back then, i thought it was completely unusable..thats how bad the quality was. and i had tried night time mode indoors, and it all jjust came out blurred
Click to expand...
Click to collapse
how do you turn of 3G?

thats strange the camera seams fine to me i havent had and of the note problems

alix776 said:
thats strange the camera seams fine to me i havent had and of the note problems
Click to expand...
Click to collapse
What ROM version are you using? We are all referring to the latest I-Mate and QTEK ROM. You might be using the old version of O2 which does not have those pixel dots.

dreamtheater39 said:
When i take a shot, the image displayed in the viewfinder before capturing, is perfectly lit with the right brightness-contrast etc.
But when i capture an image, it brightens it up until the image bleeds, and its terrible....I tried to adjust different settings, but it still did the same.
Click to expand...
Click to collapse
In these days i'm using camera and i have this problem, is there a solution???

If anyone is still there I havve a problem. When I tried to update it. i think it failed and got stuck on the serial v1.00 botloader. Luckily I found a way to fix that. May one of you please supply the 1.30.79 WWE QTEK-TMobile rom please I cannot find it. Also I ahve a 4gb that's not working with my device. Could it be possible that my rom is to old and the update for 4gb cards haven't been set in place fo r that rom? This the only time I've heard of a 4g card not working. Please help. I think its a 2005 rom

[Q] Note 3 Developer Options Bug: "Transition Animation Scale"

Good day people. I recently got the Note 3 and realized this annoying bug. I used the note 2 previously and turned off 3 developer options to make it run faster: "Window Animation Scale", "Transition Animation Scale" and "Animator Duration Scale". However when I turned the 3 options off on my note 3, after some time, the "Transition Animation Scale" will turn itself back on to the default of 1X. The other 2 options remain off. This "Transition Animation Scale" bug is really annoying and I wish to seek help on this matter. Thanks in advance.

anyone?

please help someone?

Steps to reproduce?
Played around with it for 2-3 hours and I wasn't able to reproduce the issue, Which model are you using, what method did you use to root. Is there a particular amount of time that leads to the Transition Scale reverting or is it possibly when the device is rebooted.
Being unable to reproduce so far I am guessing it's one of three things off the top of my head:
A system application is triggering a conflict requiring the default value.
The change is not being saved in a persistent state (reboot clears it)
A Timeout based on the setting not being applied as the file is in use ? (It's a long shot maybe reboot after change?)
See if you can't narrow down when the setting is returning to default so others can reproduce.

insanepoet said:
Played around with it for 2-3 hours and I wasn't able to reproduce the issue, Which model are you using, what method did you use to root. Is there a particular amount of time that leads to the Transition Scale reverting or is it possibly when the device is rebooted.
Being unable to reproduce so far I am guessing it's one of three things off the top of my head:
A system application is triggering a conflict requiring the default value.
The change is not being saved in a persistent state (reboot clears it)
A Timeout based on the setting not being applied as the file is in use ? (It's a long shot maybe reboot after change?)
See if you can't narrow down when the setting is returning to default so others can reproduce.
Click to expand...
Click to collapse
okay i tried turning off "adaptive display" and it actually remained good for many hours. however after i used the camera, the same "Transition Animation Scale" bug appeared again. my device is SM-N9005 and not rooted whatsoever.

ok im quite sure the culprit is the camera. when i change the camera mode from beauty face to auto, then i quit camera and open it again it will switch back to beauty face. how to fix this camera memory problem please? which in turn will fix the Transition Animation Scale

somebody please check this out. it's a very apparent bug............... HELP

please anybody help?

still searching for answers. it's confirmed the camera is the one causing this. anybody got a fix?

sirbljm said:
somebody please check this out. it's a very apparent bug............... HELP
Click to expand...
Click to collapse
Same here, it should be a bug in the firmware. Apparently reading mode only works with adapt display and not the other 3 screen mode which is a bug too! Camera mode also lacks of Night mode which is available in S4

First off relax, demanding help will get you no where especially when you are dealing with a brand new device and an issue that has not been dealt with before.
I'm glad to see you found the camera app is the culprit, i can take a look at it tomorrow and see if I can't find a workaround for the problem. Working on a stock base however our options may be limited. If you are able to reproduce the bug on demand I would also send a report to samsung dot com / support just to get it on their radar (Not saying it will help but hiccups like this usually get addressed in OTA's).
If you have a chance to check before i get back to you see if the change is effected by a reboot (i.e. change settings, reboot, verify settings) might require root to fix the bug. As well can you try another camera app and see if the problem occurs (will let me know if it is something being called from the built in camera apk).
Hopefully we'll get this sorted for you and anyone who runs into it in the future.

insanepoet said:
First off relax, demanding help will get you no where especially when you are dealing with a brand new device and an issue that has not been dealt with before.
I'm glad to see you found the camera app is the culprit, i can take a look at it tomorrow and see if I can't find a workaround for the problem. Working on a stock base however our options may be limited. If you are able to reproduce the bug on demand I would also send a report to samsung dot com / support just to get it on their radar (Not saying it will help but hiccups like this usually get addressed in OTA's).
If you have a chance to check before i get back to you see if the change is effected by a reboot (i.e. change settings, reboot, verify settings) might require root to fix the bug. As well can you try another camera app and see if the problem occurs (will let me know if it is something being called from the built in camera apk).
Hopefully we'll get this sorted for you and anyone who runs into it in the future.
Click to expand...
Click to collapse
Dear Sir Poet. I have done what you instructed me to do, I applied the same developer options settings, rebooted the phone and the settings were verified good.
However, the moment after I use the Camera app, the "Transition Animation Scale" turns on by itself again. I have tried using third-party camera apps and they do not affect the settings in developer options.
It is therefore very very obvious that the Default Camera is causing this instability in developer options settings.
Sir, kindly help us feedback to Samsung regarding this issue so that they will release an OTA update fix.
Your continual help in solving this problem is greatly appreciated. Thank you so much.

sirbljm said:
when i change the camera mode from beauty face to auto, then i quit camera and open it again it will switch back to beauty face. how to fix this camera memory problem please?
Click to expand...
Click to collapse
is this happening to the rear or front camera?
the default for the rear is auto while the default for the front is beauty.

sirbljm said:
Dear Sir Poet. I have done what you instructed me to do, I applied the same developer options settings, rebooted the phone and the settings were verified good.
However, the moment after I use the Camera app, the "Transition Animation Scale" turns on by itself again. I have tried using third-party camera apps and they do not affect the settings in developer options.
It is therefore very very obvious that the Default Camera is causing this instability in developer options settings.
Sir, kindly help us feedback to Samsung regarding this issue so that they will release an OTA update fix.
Your continual help in solving this problem is greatly appreciated. Thank you so much.
Click to expand...
Click to collapse
Dear Sir Sirbljm
You are a very pushy bloke mate.. go report this problem to Samsung yourself dont tell poet to do it.. sheesh !
He doesent even have the problem! :silly:
We all have problems with early firmware.. I have a rebooting issue.. but I'm patiently trying to fix it myself while conversing with others patiently about a workaround.. eitherway I know that my GS4 was rubbish with the first firmware..
it'll get better. be patient.

tested and reproduced the same effect.
confirmed that starting the camera (regardless of front or rear)will reset the transition animation scale to 1x.

Fade777 said:
Dear Sir Sirbljm
You are a very pushy bloke mate.. go report this problem to Samsung yourself dont tell poet to do it.. sheesh !
He doesent even have the problem! :silly:
We all have problems with early firmware.. I have a rebooting issue.. but I'm patiently trying to fix it myself while conversing with others patiently about a workaround.. eitherway I know that my GS4 was rubbish with the first firmware..
it'll get better. be patient.
Click to expand...
Click to collapse
sorry man. it's just that i'm new to this and i don't even know how to report the matter to samsung. was hoping somebody who is more experienced can help me out that's all. i'm sure it'll get better, i'll be patient.

cfchong said:
tested and reproduced the same effect.
confirmed that starting the camera (regardless of front or rear)will reset the transition animation scale to 1x.
Click to expand...
Click to collapse
thank you Corporal First Class Hong. at least i now know i'm not alone in this. :fingers-crossed:

I get the same transition animation bug. It turns on (1x) by itself after I set it to 0.

lferrante said:
I get the same transition animation bug. It turns on (1x) by itself after I set it to 0.
Click to expand...
Click to collapse
I'm getting the sam bug..
Just for the record..
It'll get fixed.. this isn't that annoying
My reboot problem.. now that... that is annoying.
Sent from my SM-N9005 using Tapatalk 4

waiting for a fix for this
has anyone figured out how to make this stop? The animation scale changes every time the camera is opened. Pretty annoying if you use your camera often

HELP: My camera no longer takes quick photos after the latest Sprint update.

First, my quick boost setting still works. This is not about that. Before taking the latest update, I could hit the shutter about 5 times a second and it would react just as quickly and take pictures. After the update, it barely takes 1 picture every 10 seconds.
Is there a shutter speed setting I'm missing somewhere?
Has this happened with anyone else?
Thanks.

Anyone? TIA.

I dont have the sprint phone, i have the att, however, i had this issue after an update. Im not on stock anymore so i cant recall what setting it is, but one of the quick settings is for a type of smart camera....where as the camera actually takes multiple shots, but only keeps one. It does this to try and get the best picture. Find it and disable it, see if it helps.

cloudraker said:
I dont have the sprint phone, i have the att, however, i had this issue after an update. Im not on stock anymore so i cant recall what setting it is, but one of the quick settings is for a type of smart camera....where as the camera actually takes multiple shots, but only keeps one. It does this to try and get the best picture. Find it and disable it, see if it helps.
Click to expand...
Click to collapse
I have gone through all of the settings and don't see anything like that. What you are explaining sounds like exactly what could be causing this though, so I am intrigued. Can anyone chime in?

[Q] Is the screen on my phone going to die?

this started a few weeks ago and it dose not bother me too much, but im worried that it will stop working.
It only happens at the lowest brightness and when turning off the screen.
i have a video you guys can check out.
https://www.youtube.com/watch?v=9UFTQDmr-aI&feature=youtu.be
let me know what you think

Try this:
Settings > Developer Options (Click more then 7 times on "Build number" in "About phone" to open these options) > Check the option "Disable hardware overlays".
After doing this, try to set lowest brightness.
I hope it will help you.

Could possibly be a hardware issue. Did it come into any physical contact?
Sent from my Nexus 4 using XDA Free mobile app

i haven't dropped it recently so im not sure about physical damage.
my only thought is that i often you blue wallpapers and as far as to my knowledge blue sub-pixels ware out the fastest on AMOLED displays.
but other than that ive got nothing, really hoping it dose not break as i can afford to repair it

I want to blame the problem on the rom, since only on low brightness did the glitch happens, have you tried backing up your phone and flashing another rom temporarily?

LancerEvoDrifter said:
I want to blame the problem on the rom, since only on low brightness did the glitch happens, have you tried backing up your phone and flashing another rom temporarily?
Click to expand...
Click to collapse
This is the first step I wuold take too...

Two fire tablets showing different brigtness

Hi guys,
I have to fire 7 in tablets both bought at the same time from same place. Both are running the same Lineage-12.1 ROM (12.1-20170802-Unofficial-ford)
But for some reason when i keep them side by side one of them has a very dull screen brightness where as the other is nice and visible. I am not sure if this has to do with the hardware or some missing setting in the one that is dull. I tried making both 100% bright from the upper menu but the screen difference is still the same.
The bottom image is the brighter one. Any idea if some setting somewhere is causing this?
Thansk
matt

amti366 said:
Hi guys,
I have to fire 7 in tablets both bought at the same time from same place. Both are running the same Lineage-12.1 ROM (12.1-20170802-Unofficial-ford)
But for some reason when i keep them side by side one of them has a very dull screen brightness where as the other is nice and visible. I am not sure if this has to do with the hardware or some missing setting in the one that is dull. I tried making both 100% bright from the upper menu but the screen difference is still the same.
The bottom image is the brighter one. Any idea if some setting somewhere is causing this?
Thansk
matt
Click to expand...
Click to collapse
On checking further I noticed that the tablet which is showing dull color seems to show the exact same even when I adjust the brightness slider in the top menu. When the slider is on 0 or 100% its the same. that tells me that the software slider is somehow broken?

amti366 said:
On checking further I noticed that the tablet which is showing dull color seems to show the exact same even when I adjust the brightness slider in the top menu. When the slider is on 0 or 100% its the same. that tells me that the software slider is somehow broken?
Click to expand...
Click to collapse
Known kernel issue with custom ROMs. Symptoms typically rectified with a reboot. If no joy try a full power down with a 5 sec pause before restarting.

Davey126 said:
Known kernel issue with custom ROMs. Symptoms typically rectified with a reboot. If no joy try a full power down with a 5 sec pause before restarting.
Click to expand...
Click to collapse
Sorry for the late response Davey126, for some reason it didn't post my reply when I used my cell phone the other day. I tried to restart a few times but still have the same screen issue the brightness controls dont respond. Will upgrading to the latest release help with this issue? Is there any other fix to permanently fix the problem?
Thanks for your help.
thanks,
Matt

amti366 said:
Sorry for the late response Davey126, for some reason it didn't post my reply when I used my cell phone the other day. I tried to restart a few times but still have the same screen issue the brightness controls dont respond. Will upgrading to the latest release help with this issue? Is there any other fix to permanently fix the problem?
Thanks for your help.
thanks,
Matt
Click to expand...
Click to collapse
Probably not. Likely have to sideload a full version of FireOS to refresh/replace the kernel - then start over. There is no known 'fix' for the problem other than keeping memory load to a minimum (or using the swap tweaks that I outlined elsewhere).

Davey126 said:
Probably not. Likely have to sideload a full version of FireOS to refresh/replace the kernel - then start over. There is no known 'fix' for the problem other than keeping memory load to a minimum (or using the swap tweaks that I outlined elsewhere).
Click to expand...
Click to collapse
Ok thanks for your help Davey126