Closed Bug 909628 Opened 11 years ago Closed 11 years ago

[B2G][Helix][LCD][shijinde] LCD will change form dark to light when go to setting screen first time

Categories

(Firefox OS Graveyard :: General, defect, P2)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: lecky.wanglei, Unassigned)

Details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0C; .NET4.0E; Zune 4.7; Tablet PC 2.0)

Steps to reproduce:

1、restart the phone
2、go to setting screen


Actual results:

the lcd will change from dark to light at the first time, and if go back to home screen, then go to setting screen again, the lcd is light always


Expected results:

the lcd is light always every time
Severity: normal → major
Priority: -- → P2
Summary: [B2G][Helix][LCD][shijinde]LCD will change form dark to light when go to setting screen first tiem → [B2G][Helix][LCD][shijinde] LCD will change form dark to light when go to setting screen first time
blocking-b2g: --- → hd?
Hi, what is the result about this problem? 

if you can't resolve in v1.1, please give me the information in the bug.

or if you can resolve in v1.1, also please give me the plan.

Thanks
Hi Wayne :
 Please help us to push to merge this case into V1.1 HD. It blocked the Helix Device .If you can not resolve it , please get the authorization from carrier.
hi beatriz:
Could you accept this issue? if you could not accept it on V1.1HD, could you help us to push it to be solved?There is no response for about 2 weeks
blocking-b2g: hd? → ---
Flags: needinfo?(brg)
(In reply to lecky from comment #3)
> hi beatriz:
> Could you accept this issue? if you could not accept it on V1.1HD, could you
> help us to push it to be solved?There is no response for about 2 weeks
Not critical same behaviour in v1-train branch and no plans to modify it.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(brg)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.