hey guys!
im a proud owner of a n7 since tuesday.
setup:
after the first setup of the n7 i unlocked the bootloader and flashed superuser. (did setup again after unlocking bootloader)
problem:
the screen turns off after a few minutes playing with the device and can not be started again.
turned out that the problem was the brightness (i was scared to have bricked it )
i could reflash the factory image, and set the brightness to manual setup. (rooted again, because factory image did not fix the problem)
the device works fine (except of some flickering and auto brightness), but its annoying.
it seems that some more owner of a nexus 7 have this issue.
see the folowing youtube video:
*/watch?v=enzWLwVKSHs
(sry, im not allowed to post links, so just replace the "*" with "youtube.com" )
is there any solution for this issue? (i think its software related, because the manual brightness would also let you disable the whole background lightning)
thanks in advance, lucas
nobody has a fix or a suggestion to fix this issue?
bump
I would return it to Google and get a new one. I had a screen flickering problem as well as image burn and they sent me a new one now problem.
Sent from Sexus 7
I not think they will send you a brand new one, they just give refurbish. As told me someone, the auto brightness problem is not hardwares problem.
Sent from my GT-N7000 using xda premium
i do also think, it is not hardware related.
so i think, i will wait for a fix.
anybody found a fix already??
testcenter said:
i do also think, it is not hardware related.
so i think, i will wait for a fix.
anybody found a fix already??
Click to expand...
Click to collapse
After upgrade to 4.2, the problem became more apparent, cycling from dim to a bit brighter every one minute or so in a pretty constant ambient lighting. Called the customer service, told to do a factory reset, did that and the cycling is much less frequent. But factory reset method is too painful: lost all my customizations and files. It got to have a simpler solution, clear some setting property, perhaps.
Related
Hi, i like to have some advice, i'm having some issues with my N10 and i like to know another opinion.
A friend of mine brought for me the N10 from Google (US), and send it to me (Mexico), so right now the N10 its in Mexico.
-The accelerometer has some kind of miscalibration, because the gps never says the right direction i'm going, some driving games turn themself to the right and when i try to take a photosphere, the gray tiles of the bottom are always unaligned.
-I have a dead (or exited) pixel (very tiny) it's always light blue, almost white. It notices on black backgrounds and 100% brightness.
-The screen gets warm on 100% screen brightness (i don't know if it's normal)
-It gets DAMN hot when i'm having a videocall (Hangouts or anything), if i'm recording video, or anything that uses the camera, asi if i was gaming Nova 3 or something, sometimes the device froze and reboot.
-Lately, if i'm recording a video with the led light on, the led blinks and the video freeze when it does.
I've already tried factory reset's, unlocked the bootloader, used Paranoid Android, AOSP of Mr Robinson's, used KTManta Kernel, Trinity Kernel (with the more stable results) and now i'm back stock with the bootloader re-lock. The issues had persisted.
If it was your's, do you return it?
And if it so... What should i do? Call Google? Or should i send it back to my friend and ask him to help me for the warranty? Do i need to be the original owner?
Someone knows the Warranty Number? Do they speak spanish? sorry, but i'm a bit lost.
Thanks for your time and help. Anything would be appreciated.
supertaco said:
Hi, i like to have some advice, i'm having some issues with my N10 and i like to know another opinion.
A friend of mine brought for me the N10 from Google (US), and send it to me (Mexico), so right now the N10 its in Mexico.
-The accelerometer has some kind of miscalibration, because the gps never says the right direction i'm going, some driving games turn themself to the right and when i try to take a photosphere, the gray tiles of the bottom are always unaligned.
-I have a dead (or exited) pixel (very tiny) it's always light blue, almost white. It notices on black backgrounds and 100% brightness.
-The screen gets warm on 100% screen brightness (i don't know if it's normal)
-It gets DAMN hot when i'm having a videocall (Hangouts or anything), if i'm recording video, or anything that uses the camera, asi if i was gaming Nova 3 or something, sometimes the device froze and reboot.
-Lately, if i'm recording a video with the led light on, the led blinks and the video freeze when it does.
I've already tried factory reset's, unlocked the bootloader, used Paranoid Android, AOSP of Mr Robinson's, used KTManta Kernel, Trinity Kernel (with the more stable results) and now i'm back stock with the bootloader re-lock. The issues had persisted.
If it was your's, do you return it?
And if it so... What should i do? Call Google? Or should i send it back to my friend and ask him to help me for the warranty? Do i need to be the original owner?
Someone knows the Warranty Number? Do they speak spanish? sorry, but i'm a bit lost.
Thanks for your time and help. Anything would be appreciated.
Click to expand...
Click to collapse
You can try to flash the factory image.
mrgnex said:
You can try to flash the factory image.
Click to expand...
Click to collapse
I'm already on the factory image. I restored everything...
supertaco said:
I'm already on the factory image. I restored everything...
Click to expand...
Click to collapse
Could try recalibrating the censor, but thats only 1 issue maybe solved
Likely in
settings>advanced>censors>calibrate
Requires a flat surface & .5 seconds of your time (minus the 2-5seconds it takes to get to the setting)
Or similar , but with dead pixal n crap, ye if its under warrenty, exchange it
Warrenties are there for a reason, use n abuse em while you got em, trust me, when its up, you will wish you did xD
supertaco said:
Hi, i like to have some advice, i'm having some issues with my N10 and i like to know another opinion.
A friend of mine brought for me the N10 from Google (US), and send it to me (Mexico), so right now the N10 its in Mexico.
-The accelerometer has some kind of miscalibration, because the gps never says the right direction i'm going, some driving games turn themself to the right and when i try to take a photosphere, the gray tiles of the bottom are always unaligned.
-I have a dead (or exited) pixel (very tiny) it's always light blue, almost white. It notices on black backgrounds and 100% brightness.
-The screen gets warm on 100% screen brightness (i don't know if it's normal)
-It gets DAMN hot when i'm having a videocall (Hangouts or anything), if i'm recording video, or anything that uses the camera, asi if i was gaming Nova 3 or something, sometimes the device froze and reboot.
-Lately, if i'm recording a video with the led light on, the led blinks and the video freeze when it does.
I've already tried factory reset's, unlocked the bootloader, used Paranoid Android, AOSP of Mr Robinson's, used KTManta Kernel, Trinity Kernel (with the more stable results) and now i'm back stock with the bootloader re-lock. The issues had persisted.
If it was your's, do you return it?
And if it so... What should i do? Call Google? Or should i send it back to my friend and ask him to help me for the warranty? Do i need to be the original owner?
Someone knows the Warranty Number? Do they speak spanish? sorry, but i'm a bit lost.
Thanks for your time and help. Anything would be appreciated.
Click to expand...
Click to collapse
1 - try recalibrating it like suggested before
2 - That's a real problem, however I don't believe you should send to warranty for that if it doesn't annoy you, however if you don't like do it!
3 - 100% screen brightness is really normal to be hot, almost every device is like this.
4 - Mine used to get really hot, with the update to 4.3 became better.
5 - Weird... That's probably a hardware issue for sure!
My opinion: if the dead pixel is really a problem and you intend to use this tablet for recording videos, I believe you should send it back to your friend, it's a more sure way that warranty will work. Now if they aren't really an issue, I believe it will be only waste of money sending a package to international shipping, also remember it can take some good time to arrive, at least here in Brazil it can take from 1-3 months to arrive something from US. Well, as the user above me said "Warranty exists to be used and abused." If you're not happy with your product send it back!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Silly cuestion... Where's the advanced menu? I couldn't find it...
Enviado desde mi Nexus 10 usando Tapatalk 4
I received my N10, opened the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted.
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Even CM withouf GAPPS wouldnt work
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
No I re-locked it, unrooted it and I am running stock 4.3: same problem
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. I'm past the 15 day return period and the overall experience of sending it back fromhere would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
Thoughts?
supertaco said:
Hi, i like to have some advice, i'm having some issues with my N10 and i like to know another opinion.
A friend of mine brought for me the N10 from Google (US), and send it to me (Mexico), so right now the N10 its in Mexico.
-The accelerometer has some kind of miscalibration, because the gps never says the right direction i'm going, some driving games turn themself to the right and when i try to take a photosphere, the gray tiles of the bottom are always unaligned.
-I have a dead (or exited) pixel (very tiny) it's always light blue, almost white. It notices on black backgrounds and 100% brightness.
-The screen gets warm on 100% screen brightness (i don't know if it's normal)
-It gets DAMN hot when i'm having a videocall (Hangouts or anything), if i'm recording video, or anything that uses the camera, asi if i was gaming Nova 3 or something, sometimes the device froze and reboot.
-Lately, if i'm recording a video with the led light on, the led blinks and the video freeze when it does.
I've already tried factory reset's, unlocked the bootloader, used Paranoid Android, AOSP of Mr Robinson's, used KTManta Kernel, Trinity Kernel (with the more stable results) and now i'm back stock with the bootloader re-lock. The issues had persisted.
If it was your's, do you return it?
And if it so... What should i do? Call Google? Or should i send it back to my friend and ask him to help me for the warranty? Do i need to be the original owner?
Someone knows the Warranty Number? Do they speak spanish? sorry, but i'm a bit lost.
Thanks for your time and help. Anything would be appreciated.
Click to expand...
Click to collapse
Call Samsung Repair Center (it's free by Skype) - +18553926398
It's a dedicated line for NEXUS devices. They told you how to manage a warranty request. But they can send back repaired device only to the US address (I had similar problem, but I am from Poland, so maybe for Mexico they have some other rules).
warranty dont take the device back for only one pixel. i know that the limit is minimum 5 pixels
Hi Guys I got me a Nexus 7 3G Prod Date was March 2013, I thought the screen flickering wouldn´t be an issue anymore. But I seem to have it...
Just wanted to check if anybody else has this special issue of my nexus too.
It´s occuring when I´m going online with 2g connection and the brightness at its lowest (or very low). Everytime there´s data connection and I am loading a webpage for example, the screen begins to flicker occassionally more or less. Even when im going to homescreen while loading a page in the background the flickering is visible.
I reflashed the 4.3 Android but that did not help.
Already sent the Tablet in, and Asus changed the LCD part but that did not help either.
Could it be software related or should I send it in again and hope they fix it this time for real?
I am not standing the fact that I searched the internet and can´t really find anything about this special fault of my nexus which makes me wonder (just screen flickering in general but not when being online with 2g)...
pieceofphil said:
Hi Guys I got me a Nexus 7 3G Prod Date was March 2013, I thought the screen flickering wouldn´t be an issue anymore. But I seem to have it...
Just wanted to check if anybody else has this special issue of my nexus too.
It´s occuring when I´m going online with 2g connection and the brightness at its lowest (or very low). Everytime there´s data connection and I am loading a webpage for example, the screen begins to flicker occassionally more or less. Even when im going to homescreen while loading a page in the background the flickering is visible.
I reflashed the 4.3 Android but that did not help.
Already sent the Tablet in, and Asus changed the LCD part but that did not help either.
Could it be software related or should I send it in again and hope they fix it this time for real?
I am not standing the fact that I searched the internet and can´t really find anything about this special fault of my nexus which makes me wonder (just screen flickering in general but not when being online with 2g)...
Click to expand...
Click to collapse
It's software related, i would just wait because it happened to me as well, if you want you can downgrade to 4.1.2
click thanks if i helped
pieceofphil said:
Hi Guys I got me a Nexus 7 3G Prod Date was March 2013, I thought the screen flickering wouldn´t be an issue anymore. But I seem to have it...
Just wanted to check if anybody else has this special issue of my nexus too.
It´s occuring when I´m going online with 2g connection and the brightness at its lowest (or very low). Everytime there´s data connection and I am loading a webpage for example, the screen begins to flicker occassionally more or less. Even when im going to homescreen while loading a page in the background the flickering is visible.
I reflashed the 4.3 Android but that did not help.
Already sent the Tablet in, and Asus changed the LCD part but that did not help either.
Could it be software related or should I send it in again and hope they fix it this time for real?
I am not standing the fact that I searched the internet and can´t really find anything about this special fault of my nexus which makes me wonder (just screen flickering in general but not when being online with 2g)...
Click to expand...
Click to collapse
It's software related, i would just wait because it happened to me as well, if you want you can downgrade to 4.1.2
click thanks if i helped
Has anyone else been experiencing a bug in the way the system handles the backlight on CM11. For example, i have the backlight set to halfway. When I hit the sleep button and turn the phone back on (from sleep), the backlight is completely turned off. Hitting the sleep button again (and then waking it) sometimes yields the backlight going back to the way i had previously set it and sometimes it just stays turned off. I was wondering if there was a fix for this.
This exists very long ago without a solution and most people including devs are aware of it... I reckon we need drivers/files from official KitKat to fix it, but I'd love to be wrong.
Sent from Google Nexus 4 @ CM11
AndyYan said:
This exists very long ago without a solution and most people including devs are aware of it... I reckon we need drivers/files from official KitKat to fix it, but I'd love to be wrong.
Click to expand...
Click to collapse
I'd say all it takes is at least one Razr M to be in the hands of a developer, that's all .
(No one reported this issue for Razr HD, Photon Q or Atrix HD so far...)
I guess that the Razr M display panel driver (in kernel) needs some small fix for this.
Ok, thanks guys. Its not a big deal as it only happens once in a while. I just wanted to see what the general consensus was. I might just make an app that restores the backlight on each wake. Do you think that this issue will be fixed now that the KK Firmware for the M was leaked? (We now have the right kernel?)
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
steveindajeep said:
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
Click to expand...
Click to collapse
I haven't heard of any display issues in this regard since the X's initial release, and that was fixed pretty quickly with an OTA. None sense then... The "display driver" is built into the kernel, and if this was an issue I'm sure we would have heard more about it.
Sorry to hear, but this sure sounds like a hardware problem.
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
_arxn said:
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
Click to expand...
Click to collapse
Later on the same day: So I fell asleep for about 4 hours with brightness on low. (damn I sleep a lot) woke up and the issue returned. But I had the brightness on full for a while and it seems to have resolved again when I put it back to low brightness.
That's all so far. Still monitoring
I'm glad someone else noticed that when you slide the brightness bar it effects the way this display issue behaves. I was starting to think I was alone on this. Now this is just my experience on my phone of course. It seems to be around 2/3 way to full bright that it starts to flash the white lines on and off and then 3/4 + it is pretty much acts as it should, they go away! So I took a screenshot as acejavelin suggested and the screenshot was clear. So this would explain why updates don't seem to change anything since it does seem to be a certain batch with bad hardware. Can this hardware be solder changed? Guess I will keep an eye out for sale of xpure with busted digitizer/good lcd to test and possible mb swap.
Yes 1575 definitely has a display driver issue, i've noticed this too. I don't think there is a way to fix this, unless it would be fixed in Nougat.
But how sure are you that it's a driver issue and not hardware? That's why I'm waiting for nougat. If it doesn't fix the issue then I'm just going to have to retire the phone.
Sorry bro
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Mine has the same issues now and then but a restart fixes it always.
Bill720 said:
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Click to expand...
Click to collapse
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
But the Op!
onupirat said:
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
Click to expand...
Click to collapse
steveindajeep said:
I've already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
Click to expand...
Click to collapse
Oh. I just read this and assumed that we were all talking about the same thing. In your case, I'd perform some experimentation to make absolute certain that your findings aren't just coincidence.
Question re: hardware vs software
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
Hi ~ just read your msg, and tried your "screenshot test." The grayish area on my screen (which over time, comes & goes - haven't detected a pattern as to why/when) DOES show up on the screenshot.
If I understand correctly, that would tend to indicate that I am experiencing a software issue? (Not hardware)
I did do a Factory Data Reset, and am experiencing the same issue. I had not added any apps for an extended period of time, prior to this gray-area occuring. I did, however, drop the phone. I don't recall for certain, but I don't think the problem occurred immediately, rather, it started very shortly thereafter (1 -3 days).
And I am waiting for delivery of a battery, since that's shot (runs down very quickly, & shuts down with anywhere from 30% - 60%+ battery level).
Any suggestions for resolving this? I hope this post makes sense... And thank you for any ideas or assistance you can offer!
Hello everybody. I have the same problem.
And who ever changed the display? Do you want to understand this is the problem of the display, motherboard or drivers?
I think it's a software problem, a hardware will not stop glitches when you flash a different software until and unless you fix it. In my experience, after my phone break because of downgrade to marshmallow stock firmware, and with an unlock bootloader i update my phone using OTA update, suddenly it stop working. blank screen and i tried try to recovery it with xt1575 IMG file to boot it again, mine it was xt1572(India) then I start facing a lot of problem, glitches, can go back to marshmallow stock firmware so and so... Now I'm trying to find a solution !!!! Custom ROM, CM13 work better and no glitches till now... I will Report soon
Moto x style/pure display problem
steveindajeep said:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
Click to expand...
Click to collapse
I think maybe due to brightness control problem, could be the software or hardware problem
Hi guys I have a problem on my s8.
Auto brightness always worked for me, but I just noticed that now it stopped working at all. Like, usually if i set brightness to max and then set autobrightness on, it auto reduces it to like 25%, meanwhile now it doesnt change the brightness ever. I have the feeling that auto brightness stopped working after i installed the last patch with odin (the UK unbranded one) since I patched it like 4 days ago and in the past weeks it worked fine. I dont think its a hardware problem because I tried sensor box app and in a black room it shows 0 while in a light one it goes to over 100 and next to a lamp over 2000.
Any idea what could be the problem? And how to fix it? I really would hate to do a hard reset since i'd lose too much stuff... could it be the patch that has a bug? Thanks in advance!
tharghan said:
Hi guys I have a problem on my s8.
Auto brightness always worked for me, but I just noticed that now it stopped working at all. Like, usually if i set brightness to max and then set autobrightness on, it auto reduces it to like 25%, meanwhile now it doesnt change the brightness ever. I have the feeling that auto brightness stopped working after i installed the last patch with odin (the UK unbranded one) since I patched it like 4 days ago and in the past weeks it worked fine. I dont think its a hardware problem because I tried sensor box app and in a black room it shows 0 while in a light one it goes to over 100 and next to a lamp over 2000.
Any idea what could be the problem? And how to fix it? I really would hate to do a hard reset since i'd lose too much stuff... could it be the patch that has a bug? Thanks in advance!
Click to expand...
Click to collapse
I have similar issue with my phone after latest update. I did hard reset without luck. All we have to do is to wait until new patch will be released and hopefully fix this issue. Regards
Sent from my SM-G950F using Tapatalk
ojkajoj said:
I have similar issue with my phone after latest update. I did hard reset without luck. All we have to do is to wait until new patch will be released and hopefully fix this issue. Regards
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
I'm really surprised that Samsung will go live with a firmware with bugs like this, I guess they really dont test anything.
I think is the same for me ! With AQG5 firmware (the last one) when you change the brightness with auto brightness on, the phone memorise the setting with the ambiant light condition : you can see it by doing the following : turn auto brightness on and then set brightness up or down. Then uncheck auto brightness of and place the curser at the opposite. At last put auto brightness back on and the brightness will jump where you put it before like the phone memorised it.
Also with auto brightness on you can put your thumb on the sensor in the upper left side of the phone to simulate darkness. The screens goes darker and as soon you remove your thonger he goes lighter.
I dont understand why just some of us have this problem. They should released a fix soon because its really annoying not to have it working, I dont want to have to wait a month or more like this...
It pissed me off so I downgraded to AQF7 : the issue is now gone =)
Same thing over here!
The AQF7 update was by far the best and most stable one to date. Now my home button problem is back and lag also!
Before it I had home button issues with response and lag whille scrolling. Whit the current update everything came back!
Samsung really needs to get their s*** together!
Well... when they released the AQH3 in the changelog it said they fixed the auto brightness thingie, yet I just installed it and guess what? I still have the same problem. Auto brightness still doesnt work, like in the firmware that came out a month ago.
Anyone else tested it? What the **** is Samsung doing?
No one tried yet?
I agree with you, the autobrightness still doesn't work.
Sent from my SM-G950F using Tapatalk
Any way to fix this? I am using an app called lux, but it's not perfect, still better than nothing
I have the same problem. I saw another thread that said it's not a bug. They made it that it learns your patterns, so it won't change when you hit the auto brightness button, but it still does become brighter when you go outside, and dimmer when you go inside.
I'm not happy with it though, as it worked perfectly for me before this update, and this is just very annoying.
Atomsk said:
Any way to fix this? I am using an app called lux, but it's not perfect, still better than nothing
Click to expand...
Click to collapse
What build/baseband/firmware are you running?