Fixed
Status Update
Comments
bp...@googlemail.com <bp...@googlemail.com>
pl...@gmail.com <pl...@gmail.com> #2
I have that issue too.
I'm completely stock, unrooted, MRA58N.
I'm completely stock, unrooted, MRA58N.
ta...@gmail.com <ta...@gmail.com> #3
Same story here. Have been looking for reports of this issue for a few days, glad I finally found the xda thread.
md...@gmail.com <md...@gmail.com> #4
Please don't forget to star the issue.
ka...@gmail.com <ka...@gmail.com> #5
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
* 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
do...@gmail.com <do...@gmail.com> #6
[Comment deleted]
ro...@android.com <ro...@android.com>
le...@gmail.com <le...@gmail.com> #8
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
le...@gmail.com <le...@gmail.com> #9
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
pl...@gmail.com <pl...@gmail.com> #10
I also have the issue, stock Marshmallow.
lo...@gmail.com <lo...@gmail.com> #11
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.
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.
py...@gmail.com <py...@gmail.com> #12
Flashed Android 6.0.1 factory image today. The issue still persists.
an...@gmail.com <an...@gmail.com> #13
I am also dealing with this issue. MRA58R
zv...@gmail.com <zv...@gmail.com> #14
Exactly the same issue. Running Stock MRA58N unrooted.
zv...@gmail.com <zv...@gmail.com> #15
Same issue here also running Stock MRA58N
ma...@gmail.com <ma...@gmail.com> #16
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.
I will continue testing this evening, as the issue was mostly noticeable (and dangerous) on my commute home at night.
ma...@gmail.com <ma...@gmail.com> #18
Just bought a Nexus 6 last week and i immediately noticed this issue. It's especially noticeable in low light.
pl...@gmail.com <pl...@gmail.com> #19
I have experienced this, too, on a brand new Nexus 6. It is running MRA58X on T-Mobile.
ma...@gmail.com <ma...@gmail.com> #21
[Comment deleted]
pl...@gmail.com <pl...@gmail.com> #22
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.
I don't have this app installed so if apps can cause this issue there must be more than one.
go...@umito.nl <go...@umito.nl> #23
When I try to share my bug report to 'android-bugreport@google.com' I get an email saying the group may not exist.
la...@gmail.com <la...@gmail.com> #24
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.
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.
de...@gmail.com <de...@gmail.com> #25
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.
ru...@gmail.com <ru...@gmail.com> #26
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.
[Deleted User] <[Deleted User]> #27
Still present in build MMB29S
Description
• Create a spannable string with multiple paragraphs.
• In a paragraph other than the first one, add a styling span that starts within a word such that the line will be broken to the start of the word.
An IndexOutOfBoundsException will be thrown with the following backtrace:
E/AndroidRuntime( 3070): java.lang.IndexOutOfBoundsException
E/AndroidRuntime( 3070): at android.graphics.Paint.getTextRunAdvances(Paint.java:1731)
E/AndroidRuntime( 3070): at android.graphics.Paint.getTextRunAdvances(Paint.java:1704)
E/AndroidRuntime( 3070): at android.text.MeasuredText.addStyleRun(MeasuredText.java:164)
E/AndroidRuntime( 3070): at android.text.MeasuredText.addStyleRun(MeasuredText.java:204)
E/AndroidRuntime( 3070): at android.text.StaticLayout.generate(StaticLayout.java:281)
...
I think the offending bit of code is this section in StaticLayout.java:
if (here < spanStart) {
// The text was cut before the beginning of the current span range.
// Exit the span loop, and get spanStart to start over from here.
measured.setPos(here);
spanEnd = here;
break;
}
The 'here' variable is an offset from the start of the string. The MeasuredText.setPos method just sets the mPos member of the object. Within MeasuredText mPos is treated as an offset from the start of the current paragraph. MeasuredText has a char[] array that just contains the subsection of the text for the current paragraph. Thus when the loop is restarted addSpan will be called and it will try to index the char[] array using mPos which will be way off the end of the array.
Maybe it should be measured.setPos(here - paraStart) instead?
I'll attach an example Activity which replicates the problem. The example depends on the size of the display which in my case is WVGA800.