IssueTracker

I have that issue too.
I'm completely stock, unrooted, MRA58N.

Same story here. Have been looking for reports of this issue for a few days, glad I finally found the xda thread.

Please don't forget to star the issue.

Please provide Bug report and scree record for better understanding.
* Android bug report

After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Note: Please upload any information to google drive and share the folder to android-bugreport@google.com.  After sharing please provide the link for the uploaded data

[Comment deleted]

Here is one from me as well:
https://drive.google.com/open?id=0B7wB6o3UZCepZVBrTFhJV3lQaG8

Deleted my comment and resharing the bug report via Google Drive link (didn't think about the security part).  Here's the link

https://drive.google.com/drive/folders/0B3pCHihva_6mUWxRWXFHeFBWOW8

Thanks for the Bug report. We are having a look at the issue you reported, will update more on this issue as it becomes available

I also have the issue, stock Marshmallow.

This issue bothered me for a few days. I just bought the phone a week ago (brand new, never rooted). I am running MRA58N.  To recreate the issue, go to settings -> Display -> turn on "Adaptive  brightness" and then turn it off, turn it back on again. You will probably see the Brightness issue.

I would say 5 out of 10 times, when turning "Adaptive  brightness" on, the screen will be 100% brightness for a few seconds and return to the normal level.

Flashed Android 6.0.1 factory image today.  The issue still persists.

I am also dealing with this issue. MRA58R

Exactly the same issue. Running Stock MRA58N unrooted.

Same issue here also running Stock MRA58N

Seems to still be an issue on Stock MMB29K rooted.

I will continue testing this evening, as the issue was mostly noticeable (and dangerous) on my commute home at night.

Just bought a Nexus 6 last week and i immediately noticed this issue. It's especially noticeable in low light.

I have experienced this, too, on a brand new Nexus 6.  It is running MRA58X on T-Mobile.

[Comment deleted]

Another user mentioned that for him, this app causes the issue:
https://play.google.com/store/apps/details?id=com.timewarnercable.wififinder
I don't have this app installed so if apps can cause this issue there must be more than one.

When I try to share my bug report to 'android-bugreport@google.com' I get an email saying the group may not exist.

I have the same issue on my N6. I don't have the Wi-Fi analyzer app installed, but I'm a Project Fi user and Project Fi installs an app that scans for open wireless networks in the background. I'm going to try and check if this issue still occurs when I disable WiFi scanning.

I also noticed that when this issue occurs the Lux reading of the sensor is always 25457 (I used the third party "Lux Lite" app to get that reading). So it might be possible to work around this issue with a non-root Android app that controls the adaptive brightness setting based on the sensor reading.

Nexus 6P on 6.0.1. Phone randomly turns extremely bright and stays that way for a few seconds before turning the brightness back down. No moving the phone or changing lightning conditions around me.

I'm also experiencing the max brightness on wake issue... Lasting for about 5 seconds then returning to normal. I'm still on build MRA58K. The issue started recently but I've been using this build for months.

Still present in build MMB29S

I can also confirm its still present in MMB29S.

It seemed like the issue disappeared from the December security update. However, it's back in the January update MMB29S.

It has not disappeared for me ever since it started in November.

I observed this behavior before I got the Marshmallow upgrade (when on 5.1.1). It only started occurring to me after I got my smartwatch (Moto 360 2nd gen). The brightness bug only seemed to occur after I paired my watch with the phone - and persists to this day, even with the Marshmallow firmware 6.0.1. This is on a Nexus 6.

I'm encountering this on my Nexus 6 running MMB29K.

Like the user above, i only noticed this issue after buying my Moto 360 on November last year, can it be related to bluetooth always on?

I have turned Bluetooth off and rebooted the phone. The issue is still present.
It could be the Android wear app itself causing it, but I don't want to uninstall it because then I'll have to re-pair my watch. If someone else is up to it, please try it and report back.

It's not the wear app. I don't have it installed and I still have this issue.

Clearing the cache partition and the data partition (factory reset) fixed the issue for me.

I have done more then one complete factory image flash and the problem returns.

I downloaded the factory image from google loaded it more than once and still had the issue as well.

I wonder if it has something to do with a Google app, like Play Services. Has anyone tried installing a factory image and not let it update apps?

Same issue.  Had it since Marshmallow released.  Wiping the phone briefly fixes it but it comes back.

The issue is still present after the update to MMB29Q (February security patch).

120 stars and still no update from Google. It's saddening. It's been two months now.

Did a clean flash, restored my apps, and the issue is gone for two weeks. This only started happening around the time I bought my Moto360 so I'll wait a few more days until Android 6 is released for it, then I'll pair it again and keep you guys updated. I'm not saying it's a Moto360 issue but maybe it's triggering it (bluetooth always on, Wear app, etc).

Issue persists for me. I rarely use Bluetooth and don't have any wear devices.

[Comment deleted]

One thing that I noticed on my N6 is that if I disable adpative brightness each non-adaptive brightness level is _much_ brighter than the respective adaptive brightness level. So I basically have to reduce the brightness to one of the lowest levels to get an acceptable non-adaptive brightness.

Not sure if this is related to the adaptive brightness issue (and also not sure if this is an issue at all). But maybe there's some internal brightness calibration value that's somehow wrong and that triggers both issues?

Could a dev tell us how to correctly collect useful information debug it? Otherwise I no longer require a lamp in my bedroom, but sunglasses. I honestly was never before forced to look away from my phone because of brightness, now I do it at least every third unlock.

Possibly not related to the max brightness issue, but I also experience the same issue using the brightness slider on my Nexus 6 (in reference to comment 45. The screen is much brighter at the lowest possible setting while the Adaptive brightness setting is off.

Reply to #47:
The brightness slider has always worked like that, starting from Android 5.0. With adaptive brightness enabled, the slider can only adjust the brightness by a bit. The base brightness is controlled by the phone's ambient light sensor.

Well, installed Android 6 on my Moto360 yesterday and the issue is back today. Don't know about you guys, but in my case this issue seems to be triggered by my Watch.

I'm the one that reported the issue when using TWC Wifi Finder.  It started with the update that pushed the November security update.  The bug is easy to reproduce with that app, which should make it much easier to fix.  So aside from the monthly security updates, are we supposed to see bug fix updates at all?  I understand this is not the flagship model anymore and priority is assigned low.  But seeing how the Nexus line is supposed to be a standard bearer of updates, I find the 3+ year support of iPhones much more appealing.  I already feel abandoned for my 3 month old phone.

Has anyone tried do an exchange with Morotola with success?  This phone is unusable indoors now due to the extreme brightness.  Happens about 90% of the time when I unlock the phone.  If it were more intermittent, like some are reporting, it'd be livable.

Problem started for me after the Feb. security update.  Never before that.

I have had this problem since a few months ago, probably around the November timeframe. Same problem as people reported, screen turns to maximum brightness on wake. Can reproduce while awake by enabling and disabling the adaptive brightness feature.

I do not have the TWC Wifi Finder, though. Does that make a difference?

I got sick of waiting for Google to fix the issue so I am using a workaround that works fairly well. It is a third party app called Velis Auto Brightness. If you disable the built in adaptive brightness, this app will do the trick.
I must say my Nexus 6 experience has started to pt me off the Nexus line, and even Android. The problem is that no one seems to "own" the Nexus product. Motorola don't maintain it and Google just seem to care about the latest models. I have a few performance issues with the Nexus 6 now which I imagine will never be fixed! Bad.

I didn't say the TWC app caused all the issues, just one that I found that triggered it. It took adding each app I used, one at a time to figure which app caused it. I just removed the offending app and it's been fine the past 3 months. Didn't need wifi anyway with my unlimited plan.

Sure, security fixes are good, but bug fixes show quality and refinement.  A bug is a bug. They should be fixed. That's something lacking in android. I still have audio problems when previewing audio ringtones. Not something I set much, but it's little stuff like that. And on the Nexus line? C'mon Google. Sadly, I've already decided my next phone will start with an I.

I have since upgraded to a 6P and have been using my 6 as a web remote for my chromecast. I have had it this way for about a month now and with only a few basic apps, the brightness issue is not present. I wonder if it is a common app(like Facebook or Twitter) that is causing it. I have not tested it yet. The only apps that I currently have installed besides the stock Android apps are Netflix, Hulu, and HBO Now.

I haven't noticed the issue lately. I'm on build MMB29Q. I have a myriad of apps installed. The only difference from when I had the issue is an app called Twilight that puts a red tint over the entire display during the evening.

Also, I'm rooted with stock Android and the latest Franco Kernel r42.

I had the Twilight app too. But I didn't think that was the problem.

Sent from my phone On Tue, Feb 23, 2016 at 10:39 AM, <

Comment #56 on issue 36949180 by JaysonTr...@gmail.com: Strange Adaptive
Brightness issue on Nexus 6 after November security patch
https://code.google.com/p/android/issues/detail?id=196048

I haven't noticed the issue lately. I'm on build MMB29Q. I have a myriad of
apps installed. The only difference from when I had the issue is an app
called Twilight that puts a red tint over the entire display during the
evening.

Also, I'm rooted with stock Android and the latest Franco Kernel r42.

Actually, I meant that I now am using the Twilight app, as opposed to when I was still having the issue. So I don't know if it's the app that is causing me not to have the problem, or if it was the February update

The brightness app recommended in post 53 works pretty well.  Instead of waiting 5 to 20 second for the screen to normalize, it gets it down to almost instantly.

Still ridiculous that an app has to be used at all.

I've been unable to reproduce the issue of late. I haven't changed anything on the phone per se, just kept my apps up to date. There have been at least 3 updates to the Google app recently (I'm in the beta program), so maybe it's the Google app causing the issue. I'll report back if the issue returns.

I don't want to jinx it, but I disabled "always stay on when plugged in" in developer mode and I haven't seen the issue for two days.

I've never had this option enabled in the first place.
My guess is the Google app or Google Play services caused this issue and the latest version of either finally has it fixed. I still haven't seen the issue again since my last post 5 days ago.

Yes, the cause could be Play Services app, weirdly. But it's worth to mention that I got v8.7 around the same time I flashed March factory image.

Mine is still having the problem.  Going to see if the March security update happens to fix it.  If not I'm going to go through Motorola for a warranty replacement.

I don't believe it is Moto fault as users of the 6P have reported the same issue.

I am the OP of this bug report and I switched to a Nexus 6P a week after I posted this.  I have never faced this issue on my Nexus 6P.

[Comment deleted]

I have not seen the problem for a few days since the March security update. A couple of other people also seem to be having luck. I hope the problem does not come back!

Same here.  The problem started for me with the Feb. security update, and has now been fixed by the March update.  This is the last monthly update I will ever apply to this phone, security risks regardless.  Unwilling to go through this sort of bug ever again, even the chance of it happening.

I still have the issue even after the March security update. It came back for me a couple of hours after having installed the update.

I have been following this bug for months. I am having all I the issues described. I do not have twilight installed. I am not rooted. I have moto 360 first gen.

This is bug really is getting very out of hand. It has been literally 4 months and I imagine it can't be more than a 1 line fix.

It was gone for a few months and after the April security update it is back.  

It has come back for me in the past week.

My phone is also doing this.  Max brightness then adapts.

I can confirm that the issue is also back for me. Ever since the automatic update to the latest version of Google Play services.

Is it going to take months again for this to be fixed...?

This started happening on my phone with the April security update.  Still happening after the may update as well.  Very much want this fixed.

A few days after my Nexus 6 disabled Google Fit because I hadn't been using the app, I enabled Adaptive Brightness and was surprised to see that it was back to working perfectly.
Well, after several weeks of that, I decided to give Fit another chance, and re-enabled it. That same night, Adaptive Brightness went back to the whole "max brightness when I first turn the screen on" issue.
Not sure if the two are related, but has anyone looked into the possibility? I haven't bothered disabling Fit again to see what happens, but thought I'd share in case it's a step in the right direction.

I haven't noticed the issue since I've stopped using my Android wear watch.
But I still have Google fit running.

I had a feeling my problem started when I began using the watch. I've
stopped using it because it seemed to drain my battery faster and I had
other strange issues with application lag and so on.

I recently got the auto shut off from fit and coincidentally happened to
decide to turn back adaptive brightness. I had no issues from it for a few
days. Today, I saw the messages about fit and turned it back on. What'd you
know, right away I got the brightness issue in which it turns to maximum
brightness. After I force quit fit, close and disable the app, the problem
disappears after I launch another app.

I suspect this is a clue. Can anyone else confirm if they disable, force
quit Fit, and then launch some other app, that the adaptive brightness bug
goes away?

I can also confirm that killing Fit seems to resolve the issue.

Removing Google Fit does not fix the issue. Adaptive brightness issue persists...

Removing Google Fit does not fix it for me either.

Did anyone check if this issue still exists on one of the Android N previews? I might give it a try if no one else tried it yet.

running the latest Android N preview and so far I haven't encounter the issue.

[Comment deleted]

I have been on N all day and so far no problem.
I have not been using bluetooth or my Androidwear watch lately, and like many other people I suspect these have something to do with it.

After using Android N for over a week now I can confirm that the behavior is exactly the same as before the upgrade.

However, disabling "Activity Detection" in the Google Fit settings resolved this issue for me. I posted a while ago that the reason why Android bumps the brightness to max is because the brightness sensor sometimes returns a very high value right after the screen is turned on. I wouldn't be surprised if the Google Fit sensor readings in the background could somehow impact the readings of the brightness sensor.

At this point I don't think that this issue will be fixed, but I'm still going to try submitting a bugreport to the Google Fit team.

I am on 6.0.1 and Google fit does not appear to have any effect on this issue whatsoever. Brightness issue persists with or without Google fit being installed. Unfortunately i agree it appears we will not be getting a fix for this from Google... has Google even acknowledged this is an issue?

I would try disabling "Activity detection" in Google Fit settings instead of uninstalling it.
This resolved the issue for me as well, it seems.

I disabled activity detection in Fit yesterday. So far the problem has not appeared again, si it seems that could be the cause.

I've had Fit activity detection off for months now and I still experience the issue.

Do you have any other apps installed that might read sensor data? Based on the different responses to this ticket it sounds like this issue gets triggered as soon as there's a single app that reads those sensors in the background. That's probably why deactivating Fit solved this for some users, and deactivating Android Wear solved it for other users.

On my device I was not only able to verify that disabling Fit activity detection resolves that issue, but also that re-enabling activity detection causes that issue again.

I don't think its Fit's "fault". It's probably some bug in the Nexus 6 sensor code that somehow gets triggered by applications such as Google Fit and Android Wear.

Just out of curiosity how long did you disable fit activity detection for? I did try disabling activity detection and it did temporarily stop this bug. However it did return after leaving the phone untouched for a few minutes - which is why I tried uninstalling fit.

...I wish I hadn't because now fit asks me to turn on high accuracy EVERY time I open it. Any chance anyone else has encountered and solved this?

I disabled it almost 2 days ago, so far all good. Didn't try to activate it again, and I already have high accuracy on, so can't help you with that, sorry.

[Comment deleted]

Having this issue as well, started with the first or second Marshmallow 6.0 updates; the screen, sometimes, will stay at max brightness regardless of the setting / slider position, practically blinding me in bed at night for a good 15 seconds. Not buying another Android phone if this is the quality of service related to bug fixes, I didn't even get calls or texts while on Wifi for the first year I had the phone as well (Marshmallow fixed the Sprint issue there).

It seems worse on Android N DP5 then 6

This is happening less often now, maybe not at all. Maybe it's fixed?

Finally got Android 7.0 installed, and now this problem has returned!  From the looks of it, all recent Nexus phones have this issue including the 5x and 6p.  It's a big letdown considering they appear to have fixed all other issues I had encountered.  It's the lack of software support for these types of bugs in the updates that convinced me to skip the Pixel.  

I can confirm, I had this fixed in MM but now on N (7.0) the problem is back.  I'm going to reluctantly turn off adaptive brightness again.  

Same here. The max brightness bug is back since 2 days

Also on 7.0 and have the same issue. It wasn't present when I first flashed it, but various apps updated automatically over the past few days and might have triggered the issue.

Not sure if it helps, but my Nexus 6P on 6.0.1 Sept patch also has the same issue. When I wake my phone after 5 secs or less, the brightness goes to non adaptive and 50% for half a second and then it resets to my setting.

I heard it was a bug in the Google Fit app before it was fixed, and the "Activity Detection" was causing it. I disabled it and my brightness was working again. But this time, I've tried disabling Activity Detection and even disabling the app, but the problem still occurs.

Got the same issue..... Did anyone find out which app causing the problem?

Same here with a Nexus6.. Starte 3 days ago and it's very annoying.

Same issue. 7.0. Don't really know what triggered the issue. But last app I installed was OpenCamera

I have found a way to rectify this issue for myself:

(1) Go into Settings -> Apps to locate "Google Play Services"
(2) Click on the three dots -> Uninstall updates
(3) Reboot
(4) Go to Play Store and update "Google Play Services"
(5) Reboot

This issue appears to be resolved for me after I've gone through the 5 steps process. I do however need to reconfigure Android Device Manager, as well as re-adding all the cards into Android Pay.

Nexus 6 NBD90Z

I left Activity Detection in Google Fit off for a long time and didn't have the issue. Now it's back for me as well, just started today or yesterday.
I'm sick of this crap, moving on to a OnePlus 3 anyway. Sigh.
The Nexus 6 has been plagued by this issue for 50% of its lifetime now. I don't believe this will ever be fixed, since it's already that old.

I am trying the google play services reset, will report back

The problem disappear when I disabled location history on geolocalization preferences.

Nexus 6 NBD90Z

I have found root cause of this issue.
The problem is the Google Play Services 9.8.77 with location history enabled.
This bug disappear when i install the previous version of Google Play Services(9.6.83)
Only one problem is auto update.

Nexus 6 NBD90Z

So far, after disabling location history I have not had the issue return (testing for a little over an hour). I am on Google Play Services 9.8.77.

One day later with location history off and brightness issue has still not returned.

Tested again today and found that the issue returned immediately after enabling location history for this device (my Nexus 6).

NBD91P did not fix it, but can confirm disabling Google Fit activity tracking seemed to fix it for now.

i'm on google play services 9.8.77, and as suggested above, turning off location history fixed the issue for me as well, going on 3 days now.

Is google ever going to fix this?!

On my N6 with Google Play Services 10.0.84 and Location history off the adaptive brightness function behaves as it should.

Sometimes the screen is still full brightness but it adapts in milisecond and I barely notice it.

It's like the Location history setting numbs the adapt. br. reaction times when on.

nothink helped.... Today reflashed to stock 7.1.1 and this stil here!!!!!!!!!

Still have this issue. The only workaround I've found is to remove my android watch as a trusted device. This seems to greatly help with the issue.

The problem is Location history. Switch it off and no brightness issue. Turn it on, and brightness go crazy again

It's caused by having location history on. Turn of location history and adaptive brightness works flawlessly.

I'm always using Location History and I'd prefer to not turn it off. Can't
you solve the problem once and for all, since you already know that this
bug is caused by Location History?

On Apr 20, 2017 21:41, <buganizer-system@google.com> wrote:

I also have this problem in my nexus6(Android 7.1.1 N6F26R Version) and my Moto 360 gen1. It very serious. This problem occured bout every time .

I'm rooted, bootloader unlocked​, and with PureNexus rom in android 7.1.2 and still having this issue :(

I don't want to speak too early, but it seems that May security patch fixed the issue.

Same issue on May security patch N6F27C
The problem is the last Google Play Services installed with location history enabled.
This bug disappear when i install the old version of Google Play Services(9.6.83) and location history enabled.
Pease, you solve the problem once and for all.

Nexus 6 N6F27C no ROOT

Is the team still needing bug reports to fix this issue. This issue is the source of great distress.

Very disappointed by such bug stories and it's not the only one.. this one though is very annoying, every night I get flashed as I turn on my phone screen..

It's an amazing thing. Soon this bug will be a year old.

***two years old

Yep.. pretty poor effort.  I just turned off location history which stops
it happening. If they want my data again, they can fix the problem.

On 7 Jul. 2017 7:31 am, <buganizer-system@google.com> wrote:

Replying to this email means your email address will be shared with the
team that works on this product.

https://issuetracker.google.com/issues/37072678

*Changed*

*re...@gmail.com <re...@gmail.com> added comment #134
<https://issuetracker.google.com/issues/37072678#comment134>:*
***two years old

_______________________________

*Reference Info: 37072678 Strange Adaptive Brightness issue on Nexus 6
after November security patch*
component:  Android Public Tracker
status:  Assigned
reporter:  me...@gmail.com
assignee:  pa...@google.com
cc:  me...@gmail.com, pa...@google.com, ss...@google.com
type:  Bug P4 S3
blocked by:  25446451 <https://issuetracker.google.com/issues/25446451>
duplicate issue:  37106199 <https://issuetracker.google.com/issues/37106199>
hotlist:  [AOSP] duplicate <https://issuetracker.google.com/hotlists/468389>,
[AOSP] assigned <https://issuetracker.google.com/hotlists/468531>, NeedsInfo
<https://issuetracker.google.com/hotlists/468606>
AOSP ID:  196048
AndroidID:  25446451
ReportedBy:  User


Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 37072678
<https://issuetracker.google.com/issues/37072678> where you have the role:
starred.

Three years old? I experience this issue on my S9+ latest Android version.
It's pretty annoying specially when you just woke up or at the cinema lol.

I suppose this is never going to get fixed? Living with no location history for 3 years now...

Lmao you guys have to be kidding me. Thanks for the sweet update.

Hahaha. This is funny!!!

Wow, what a joke. Not even a single reply from the team after the second day and then finally this. Get fucked, Google.