[Samsung Galaxy Nexus] sickopsycho:
Yeah I just dirty flashed the latest update (todays) with twrp and it ran fine. I also did a full nandroid and it went through fine as well. I have not tried a restore but I should assume there would be no problem. The problem had to do with SElinux enforcement in 4.4 ROMs and to the best of my knowledge it has been fixed in the latest build of twrp.

Also someone mentioned it earlier in this thread and I took their advise and it has worked out well for me. If you disable your screen animations under settings>developer options then you get hella less graphical glitching. I also notice fewer reboots- down to maybe 1 or 2 a day from 4 or 5... The settings to turn off are "Window animation scale", "Transition animation scale", and "Animator duration scale". They are by default set to 1, just set them to off. Not only do the glitches become much less obtrusive but the phone feels snappier- google now displays black boxes every so often but a quick flick of the screen usually makes them go away. Prior to this it was almost unusable for me. Of course you lose your pretty window animations by doing this but I've always been of a mind for performance and function rather than beauty... The animations arent that cool if theyre freezing up your phone. Anyway- it's not perfect but its a hell of a lot better imho.

---------- Post added at 09:49 PM ---------- Previous post was at 09:30 PM ----------

I agree- I'm confident that eventually it will most likely get worked out. The problem, as I understand it (and this is really for all the people posting here thinking that there is just something wrong with all the 4.4 ROMS being developed), is that since Google dropped support for the Galaxy Nexus- there will be no kernel update to 4.4. This also means no (Closed Source) binariy driver updates for our OMAP processor since TI has stopped making mobile processors and has more or less dropped support for the chip as well. Why they dont open source the drivers is anyones guess- 1 theory out there is that the code is probably so garbled they dont want anyone seeing what a mess they have made of it. Who cares- point is we arent getting it. At this point it's kind of a trial and error thing as far as what will work and what wont. Most of 4.4 worked more or less out of the box with SOME existing kernels and our existing drivers. The graphical glitching will continue to haunt ALL 4.4 roms until either a workaround is found or a proper 4.4 kernel is implemented. There is some hope, it sounds like, that other hardware (read Glass) using the same family of processor is being updated to 4.4 which might offer a workaround if not a downright fix. There is something else in the works- someone has gotten a 4.4 kernel booted but has not gotten much further- I forget the details... it was late, I was sleepy- so. In a nutshell Im hella impressed with what the developers have accomplished so far. When 4.4 was released to AOSP before the release of the first phone to sport it I was like- HELL yeah! That means I'll be able to run it on my phone in a week or two. Not 3 days later the first ROMS were sprouting up and from the jump SlimKat was more or less a daily driver as far as I'm concerned. =) I can put up with some bugs- I dont mind. The benefits far outweigh the bugs. Thanks Slim Team for your hard work! Feel free to toast me if any info contained here is inaccurate.