Nexus 4: Graphic artifacts and weird colors on CM nightly 4.4.1

[GoogleCodeExporter]

I am running the latest bricked stable for Nexus 4: 
20131206_185310_master-1c6a4ae. The ROM is the latest CM 11 nightly, which is 
4.4.1. The ROM works fine without bricked kernel. When I flash the kernel, I 
see all kind of weird graphic artifacts. For one, the CM boot logo can't be 
seen at all, the whole screen is cyan with weird moving horizontal lines. 

Once booted, I still see weird artifacts when switching between apps. The 
colors are all weird too

shell@mako:/ $ uname -a
Linux localhost 3.4.0-bricked-mako-master-g1c6a4ae #1 SMP PREEMPT Fri Dec 6 
18:55:24 CET 2013 armv7l GNU/Linux

The logcat is completely full of such message blocks: 

E/qdhwcomposer(  183): configureLowRes: commit failed for low res panel
E/qdhwcomposer(  183): Failed to call ioctl MSMFB_OVERLAY_SET err=Math result 
not representable
E/qdoverlay(  183): Failed to call ioctl MSMFB_OVERLAY_SET err=Out of memory
E/qdoverlay(  183): MdpCtrl failed to setOverlay, restoring last known good ov 
info
E/qdoverlay(  183): == Bad OVInfo is:  mdp_overlay z=3 fg=0 alpha=255 mask=-1 
flags=0x860000 id=-1
E/qdoverlay(  183): src msmfb_img w=768 h=96 format=13 MDP_BGRA_8888
E/qdoverlay(  183): src_rect mdp_rect x=0 y=0 w=768 h=96
E/qdoverlay(  183): dst_rect mdp_rect x=0 y=1184 w=768 h=96
E/qdoverlay(  183): == Last good known OVInfo is:  mdp_overlay z=0 fg=0 alpha=0 
mask=0 flags=0x0 id=-1
E/qdoverlay(  183): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay(  183): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay(  183): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay(  183): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay(  183): Ctrl commit failed set overlay

Any ideas ?

Regards,
Sylaan

Original issue reported on code.google.com by sylaan@gmail.com on 8 Dec 2013 at 1:02

Attachments:

• last_kmsg

[GoogleCodeExporter]

Wanted to post a screenshot of KControl showing weird colors (i.e. text in 
yellow) but just noticed the screenshot looks fine. Just what I see on the 
screen does not. 

Original comment by sylaan@gmail.com on 8 Dec 2013 at 1:04

[GoogleCodeExporter]

CM deliberately merged patches that made them incompatible with stock and aosp. 
There is nothing I can do about that except releasing a special cm version, 
which will not happen very soon.

Original comment by showp1984 on 8 Dec 2013 at 1:06

• Changed state: WontFix
• Added labels: Type-Other
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Well, that sucks. Why would they do that ? I guess I go back to the cm kernel 
then. 

Original comment by sylaan@gmail.com on 8 Dec 2013 at 1:10

[GoogleCodeExporter]

Don't ask me.

Original comment by showp1984 on 8 Dec 2013 at 1:47

[GoogleCodeExporter]

Was just a rhetorical question :-) I'll wait for another 4.4.1 ROM and hope
it won't have the same issues.

Original comment by sylaan@gmail.com on 8 Dec 2013 at 1:53

[GoogleCodeExporter]

E/qdhwcomposer(  183): Failed to call ioctl MSMFB_OVERLAY_SET err=Math result 
not representable

I am having this exact same issue. I am using CM11 kernel on HTC One. Actually 
we are porting AndroidL to HTC One, so far managed to get it boot but screen is 
glitched and logcat has this error, not sure how exactly to fix this.

Original comment by sft.bug...@gmail.com on 9 Jul 2014 at 3:13