[Q] Ace II GT-i8160 CM11 4.4.4 screen problem

Search This thread

Drew Tavares

New member
Aug 8, 2014
2
0
Hi Guys, I've recently flashed my ace II to CM11 4.4.4 KitKat and when I wake my phone i get a dark screen with colourful vertical lines down my screen and so i keep having to locking it again then waking it and its fine, i just find it really annoying so can some one help me, it also happens while im in recovery and so i have to always restart it, mabey that might be the problem, i dont know, but someone please someone help me, i will be very greatful!
 

wolfensg

Senior Member
Oct 24, 2014
219
87
Kraków
Samsung Galaxy A52 5G
Hi Guys, I've recently flashed my ace II to CM11 4.4.4 KitKat and when I wake my phone i get a dark screen with colourful vertical lines down my screen and so i keep having to locking it again then waking it and its fine, i just find it really annoying so can some one help me, it also happens while im in recovery and so i have to always restart it, mabey that might be the problem, i dont know, but someone please someone help me, i will be very greatful!

Hi,
I have similar problem apart that the lines are in shades of grey.
AFAIK this could or should be caused by some problems with the display drivers in our ACE2 (two different drivers available WS2401 and S6D27A1).

However... while it has been reported that S6D27A1 causes the problem with the "black screen lock bug" and you need to either keep relocking or flash the kernel with the driver for S6D27A1... I seem to experience the same with the WS2401 driver...

Does anyone else have the same problem with WS2401 driver (and obviously WS2401 display)?

I don't have the problem on stock GB or stock JB (apart from the leak which aparently has "something wrong" ;)
 

PolishVodka

Senior Member
Oct 4, 2012
1,138
2,815
Probably its kernel problem, but.
I was have two times this (back lighted screen with greyed lines when wake up'ed device) and to test something, I'm removed from system/lib/hw/hwcomposer.montblanc.so (or you can just move up it to system/lost+found directory, just in case) and added to system/build.prop this line:
debug.composition.type=gpu
And wakeup time was less now, and doesn't expect "black screen bug"...but this is only solution which may help for you, I didn't expect from long time this bug and have WS driver.
 
  • Like
Reactions: wolfensg

wolfensg

Senior Member
Oct 24, 2014
219
87
Kraków
Samsung Galaxy A52 5G
Probably its kernel problem, but.
I was have two times this (back lighted screen with greyed lines when wake up'ed device) and to test something, I'm removed from system/lib/hw/hwcomposer.montblanc.so (or you can just move up it to system/lost+found directory, just in case) and added to system/build.prop this line:
debug.composition.type=gpu
And wakeup time was less now, and doesn't expect "black screen bug"...but this is only solution which may help for you, I didn't expect from long time this bug and have WS driver.

@PolishVodka - Thanks! I'm just testing your hint at the moment. Wakeup time seems to be improved - as for the "black lock screen with bla bla bla bla" ;) need to wait several hours as it appears few times per day but not neceserily "on demand" ;) (P.S. Stary! Jak zadziala - wisze Ci dobra wodke! :)
 

wolfensg

Senior Member
Oct 24, 2014
219
87
Kraków
Samsung Galaxy A52 5G
Unfortunately this still did not fix the issue - the wakeup is slightly faster indeed but the "black screen with lines" occurs all the time every few hours (sometimes every attempt to unlock).
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Probably its kernel problem, but.
    I was have two times this (back lighted screen with greyed lines when wake up'ed device) and to test something, I'm removed from system/lib/hw/hwcomposer.montblanc.so (or you can just move up it to system/lost+found directory, just in case) and added to system/build.prop this line:
    debug.composition.type=gpu
    And wakeup time was less now, and doesn't expect "black screen bug"...but this is only solution which may help for you, I didn't expect from long time this bug and have WS driver.