It seems to behave like a race condition is occurring. On refresh, sometimes the page loads, other times I get the WSOD. When it does load, it takes a long time for the page to render (from a white screen) after the browser has indicated it has finished loading the page; ie ~8-15 seconds AFTER the browser has stopped "spinning/loading".
I was able to duplicate the problem on my own Android phone running ICS as well as on my desktop using the Android SDK emulator.
This defect is preventing us from installing our first Sencha Touch application at a major steel firm, and from being able to demonstrate to a current client who is a major financial services firm. This is critical to having production web applications running on iPads. This is a a #1 prior issue for us.
the quick and dirty fix is to remove all references to Ext.Device from sencha-touch-all.js. All functions are in one place. Remove and save. Make sure your project references the newly modified .js file vs their CDN link.
I am extremely dissapointed with how Sencha handled (not handled) this problem. It's been over a month and half since I reported this problem... still nothing. They should have released an emergency hotfix to their framework... or at a minium. the CDN code base. Their silence on the issue is troubling. I'm beginning to see a track record here with how they handle support issues .. especially ones that deserve an immediate response effecting users production code.