[Atrix 4G Android Development] android-DEP:
I see some people are also having the same issues I had with the rom. The typical motorola glitches here and there that over time become frustrating at the least. I'll point out exactly what to change real quick inside the build.prop prior to flashing so everyone should be able to do this with just the flash-able zip downloaded from the original post and notepad or notepad++ or some similar text editor utility that won't alter the original of the build.prop to some other default it has for text documents.

Grab the zip and just borrow the build.prop file so you can edit it with whatever editor you feel comfortable working with or the recommended plain old notepad or notepad++ downloadable here.

Open the build.prop in the text editor so you can go down to lines # 116 and # 119, as shown in the picture

Let's change that number from a high value to something more realistic and has been used by others to fix the black screen after phone calls issue.

So get rid of the 450 and make it 25.

If nothing else proves helpful in the end, this one tiny change will still be noticed by those that ran into screen turning off and not coming back on normally.

Then for the proximity distance can be left at 60 if you like as this is the most commonly used value. Alternatively you can lower this value to make the screen be more sensitive to touch input. This may be more annoying if you don't lift your fingers off the screen that much and rather type similarly to using a swype keyboard. This would register a touch input on some areas near where you actually are pressing and catch contact with other elements of the interface, especially if you don't have Cee Lo Green's tiny fingers and hands to hit phone buttons precisely with comfort.

Next line will be #128 which is 9 lines down from the proximity distance line if you dont have line numbers visible on your editor.

Just as shown in this picture here

I absolutely hate this annoying tweak being present by default in a rom. We've all had experiences with random reboots on different roms that have no type of consistency to them as to when they are triggered. While I can't say this is always the reason for random reboots in everyone's case, I can say for sure that this does affect the phone to have random reboots.

The benefits do not out weigh the theoretical increased battery life from this tweak. I would just delete it entirely or if you prefer to have the option of being able to undo any changes, just comment it out so it's not treated as instruction code by the system at runtime and make it "#ro.mot.deep.sleep.supported=true". Anything that's tagged as a comment doesn't actually get processed so this would be a realistic test comparable to just deleting the code entirely as I prefer.

I would rather first try this approach first in fixing the issues than just manually removing apk files that contain classes\libraries that might be shared with other parts of the system and can create even more issues by unintentionally corrupting the existing code elsewhere that calls out or relies on something in some apk that was removed.

I tested these build.prop mods when I first released a rom and included these mods to "increase battery life". Everyone that ran that first build ended up having similar issues as the ones stated by the the people who tried this rom. The next immediate update I released with all these build.prop hacks just removed completely and left out altogether, was when all the strange errors disappeared and everything ran noticeably smoother and stopped randomly rebooting\running the phone hot. Now that I look at the build.prop of this ICS build, it makes sense why my phone acted up after installing this rom and forcing me to remove the rom off my phone after 30 minutes of having it.

If these adjustments don't end up fixing the issues for good, at the least they will contribute to correcting some issues a few people ran into and hopefully make things a bit more stable for the future releases.

More information on build.prop tags and values can be read about here and additionally here plus here too