[Xoom Android Development] scoobaspeaz:
There are quite a few people in this thread alone that have reported it.

Calm down. Disrespect? The "sad" part could be taken that way but I also stated that they might be working on it as well. So its not 100% targeted as disrespectful. I am the first one to commend the devs of any project for all the hard free work they put into something. However, when you put out a product, even if its free, you should expect people to provide feedback, bugs, and complaints about issues. When you see people post over and over again about a certain issue yet no dev response it makes the perception that the issue is being ignored. To say "its free! you have no right to complain...go back to stock if you dont like it!" is the wrong stance and attitude to take. That is disrespectful to the people who provide feedback hoping their bugs are fixed because they love a particular rom and want to use it bug free. Providing bug feedback and providing criticism is a sign you have a product someone wants to use. If no one replied back or even gave a crap then that would be an issue. Criticism != disrespect. What it does equal is people caring about the hard work going into a product..even if its free.

That is very odd and I agree. The troubleshooting that has been going on with this issue seems to affect a lot of stingray users more so than everest and wingray users. But even some stingray users do not seem to have the "Black screen of death" issue. Could be hardware related who knows.

bigrushdog no intended disrespect to your team or you personally so don't take it that way. Was not intended as a "trolling" as it was more intended to bring light to this issue that has not been responded to. Many people have been posting this BSOD (might be posted as a question such as "why does it not wake up when I press the power button? I have to hit power and vol up to reboot it") issue in all of your EOS 4 Xoom threads, the CM thread, and other stingray rom threads. It seems to be ignored for whatever reason. Even the CM thread does not have a direct reply from the team acknowledging the issue or that it is being worked on. You can only find the conversation going on at the developers G+ page. However it is being worked on and talked about at least somewhere. You have to remember just because your xoom is working fine with your build does not mean that others who post issues are doing something wrong to cause theirs to have issues. I do know that the CM team has started working on it and the kernel I'm using seems to, so far, have fixed it. Only been 2 days though...but normally within one day i get the BSOD issue so signs are good.

You guys make a great product that I have used before and enjoyed it. As mentioned...not a trolling exercise but at least now people in here know you have heard of the BSOD issue before. Communication goes a long way...even on free projects...to keep a user base loyal and to make them feel important. I do apologize for the seemingly disrespectful tone my original post had. The "sad" statement perhaps couldn't have been taken any other way so that's my fault.

As for the BSOD issue itself it seems to be something in one of the newer kernels and not the OS itself. I do not think its something buggy in your coding at all. Your build is sound and solid. Your older builds, just like the older CM 10 nightlies, do not have this issue. Something changed in CM 10 final that made it over to CM 10.1. Just like something changed in your earlier builds that has made it in to Team EOS 4 builds. I hope the kernel modification that CM made will fix this issue. If it does then I would include it in yours.

----

As i feel this reply has sadly taken the direction XDA did not intend threads in this section to take I was reluctant to reply...but with so many replies to a simple little thing i said I felt it was needed to help clear it up. My apologies all and please go back to posting about this rom and not issues with my previous post.