New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 617240 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
ka...@chromium.org
█ sosa@chromium.org
█ shrawan@chromium.org
█ marc...@chromium.org
█ helenzhang@chromium.org
tbroch@chromium.org
█ dbehr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

[kip] Normal mode switch alert page is not visible. ( Backlignt is "0" during Dev to Normal mode switch. )

Project Member Reported by sontis@chromium.org, Jun 3 2016 
Version:8350.16.0
OS: Chrome
What steps will reproduce the problem?
(1) Try to switch the device from Dev mode to Normal mode.
     

What is the expected output?
Normal mode conversion message should be clearly visible.

What do you see instead?
Brightness level went to  "0" when converting from Dev to Normal mode.


Please use labels and text to provide additional information.

Comment 1 by sontis@chromium.org, Jun 3 2016 

Video is present at https://pantheon.corp.google.com/m/cloudstorage/b/chromiumos-test-logs/o/bugfiles/cr/617240/IMG_2504.MOV?debugUI=CLOUD


Note: Facing this issue only when switching from Dev to Normal mode.
Normal to Dev mode switching is  working fine.

Comment 2 by ka...@chromium.org, Jun 3 2016 

sontis@, how consistent this is? 
Can you re-test several iterations of transition?
Can you try on device that was auto-updated, instead recovered?

Comment 3 by son...@google.com, Jun 3 2016

Summary: [kip] Normal mode switch alert page is not visible. ( Backlignt is "0" during Dev to Normal mode switch. ) (was: [kip] Brightness level went to "0" when converting from Dev to Normal mode.)
This issue is consistent.

Facing this issue only with the Normal mode conversion alert page.
Backlight is working fine after completing the Dev to Normal mode conversion process.

Comment 4 by marc...@chromium.org, Jun 3 2016

Cc: dbehr@chromium.org
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 4 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 7 2016

Labels: -M-53 -Pri-1 M-54 MovedFrom-53 Pri-2
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by keta...@chromium.org, Feb 17 2017

Status: Archived (was: Untriaged)

Comment 8 by ketakid@google.com, Mar 18 2017

Labels: Pri-3
Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.
Project Member

Comment 9 by sheriffbot@chromium.org, Apr 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by derat@chromium.org, Apr 12 2018

Status: WontFix (was: Untriaged)
No activity for almost two years. Assuming this is never getting fixed if it's even still a problem.
►

Sign in to add a comment