I've been working on this for hours now.
\nI have a simple event listener:
\n\n\nTitanium.Gesture.addEventListener('orientationchange', function(e){\n var orient = e.orientation;\n if(orient == 1 || orient == 2) {\n portWin.height = screenHeight;\n portWin.width = screenWidth;\n portWeb.height = screenHeight;\n portWeb.width = screenWidth;\n portWeb.evalJS('portRotate(\"port\")');\n }\n else {\n portWin.height = screenWidth;\n portWin.width = screenHeight;\n portWeb.height = screenWidth;\n portWeb.width = screenHeight;\n portWeb.evalJS('portRotate(\"land\")');\n }\n});\n\n... which works fine on thee iPhone emulator, but I can't get it\nto work at all on my Android phone. I've stripped it down to just\nproducing an alert on the event occuring and still nothing.
\nI've looked around and saw something about putting the event\nlistener in a separate .js file, but that doesn't work. I've\ninstalled the KitchenSink app to my phone and the orientationchange\nexample works fine. I honestly don't know what I'm doing different\nfor it to not work.
\nAny suggestions please?
Several pro clients are experiencing this as well. I can confirm\nthat this is true in the latest builds.
\nOn Android, Ti.Gesture.addEventListener 'orientationchange'\nnever fires.
\nWhenever the simulator or real device is rotated, this event\nshould fire.
\nAll tests done on Titanium Mobile 1.6.0 pulled January 8th,\n2011
\nBROKEN on Android Simulator, 2.2
\nBROKEN on Android Device, Epic 4G 2.2
\nWORKS on iPhone Simulator, 4.2
\n/**\n* This app displays a label with the current orientation. It will work on iPhone and update\n* as you rotate the simulator or device, but it will NOT update on Android; it will display\n* the initial orientation, but will not update for future orientation changes.\n*/\nvar win = Titanium.UI.createWindow({\n backgroundColor: '#fff'\n});\nwin.orientationModes = [\n Titanium.UI.PORTRAIT,\n Titanium.UI.UPSIDE_PORTRAIT,\n Titanium.UI.LANDSCAPE_LEFT,\n Titanium.UI.LANDSCAPE_RIGHT\n];\nvar label = Titanium.UI.createLabel({\n color: '#999',\n text: 'I am Window 1',\n font: { fontSize: 20, fontFamily: 'Helvetica Neue' },\n textAlign: 'center',\n width: 'auto'\n});\nwin.add(label);\nwin.open();\n\nfunction getOrientation(o) {\n switch (o) {\n case Titanium.UI.PORTRAIT:\n return 'portrait';\n case Titanium.UI.UPSIDE_PORTRAIT:\n return 'upside portrait';\n case Titanium.UI.LANDSCAPE_LEFT:\n return 'landscape left';\n case Titanium.UI.LANDSCAPE_RIGHT:\n return 'landscape right';\n default:\n return '';\n }\n}\n\nlabel.text = getOrientation(Titanium.Gesture.orientation);\nTi.Gesture.addEventListener('orientationchange', function (e) {\n label.text = getOrientation(e.orientation);\n});\n\nThe orientationchange event will fire in a heavyweight window\n(an activity). Setting both url: 'child.js' and one of\nnavBarHidden: true, modal: true, or fullscreen:true allows you to\nwork around this limitation in app.js.
\nFor example, your app.js may look like this:
\n\nvar win = Ti.UI.createWindow({\n url: 'child.js',\n navBarHidden: true,\n backgroundColor: '#fff'\n});\nwin.open();\n\nAnd child.js would contain the following:
\n\nvar win = Ti.UI.currentWindow;\nwin.orientationModes = [\nTitanium.UI.PORTRAIT,\nTitanium.UI.UPSIDE_PORTRAIT,\nTitanium.UI.LANDSCAPE_LEFT,\nTitanium.UI.LANDSCAPE_RIGHT,\nTitanium.UI.FACE_UP,\nTitanium.UI.FACE_DOWN\n];\nvar label = Titanium.UI.createLabel({\n color: '#999',\n text: 'I am Window 1',\n font: { fontSize: 20, fontFamily: 'Helvetica Neue' },\n textAlign: 'center',\n width: 'auto'\n});\nwin.add(label);\n\nfunction getOrientation(o) {\n switch (o) {\n case Titanium.UI.PORTRAIT:\n return 'portrait';\n case Titanium.UI.UPSIDE_PORTRAIT:\n return 'upside portrait';\n case Titanium.UI.LANDSCAPE_LEFT:\n return 'landscape left';\n case Titanium.UI.LANDSCAPE_RIGHT:\n return 'landscape right';\n case Titanium.UI.FACE_UP:\n return 'face up';\n case Titanium.UI.FACE_DOWN:\n return 'face down';\n case Titanium.UI.UNKNOWN:\n return 'unknown';\n default:\n return 'constant not recognized';\n }\n}\n\nlabel.text = getOrientation(Titanium.Gesture.orientation);\nTi.Gesture.addEventListener('orientationchange', function (e) {\n label.text = getOrientation(e.orientation);\n});\n\nThis code will work on both iPhone and Android.
The workaround does work on android, but then has the undesired\nside effect that when pressing the android previous button to go\nback from the child, the app is left at a blank app screen. In the\ncode, I can see that the window associated with child.js closes\n(added an eventListener which fires as expected). So now the app is\nleft with a zombie window in the hierarchy. Pressing previous again\nwill exit out to the home screen (or whatever was previous in the\nwindow list, I assume). But this added zombie window kind of ruins\nthe utility of the workaround.
Is there a way to force the zombie window to close when I\nreceive the close event from the child.js window? I'd like to shoot\nit in the head, as is the customary practice to effectively deal\nwith zombies.
@jimwilliams: Does 'exitOnClose' help you? See \nhttp://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI.....
It so totally does the trick.
I am still not up to speed on all the Android-only stuff in\nTitanium these days; up until 1.5.0, I tried to stay away from\nAndroid-specific things to make my life easier when supporting the\niPhone (and that went both ways, of course). But since this code is\na hack to work around Android-specific issues in the first place,\nhaving an Android-specific feature used to tune the\nAndroid-required hack is not so distasteful.
Thanks so much for the pointer.
This seems to work if you are creating a new window from an\nexisting window. I tried using the code above and also the example\nfrom the KitchenSink orientation.js by it's self in my app.js and\nit still displays the error described above.
\n\nhttps://github.com/appcelerator/KitchenSink/blob/master/KitchenSink...
Related HD ticket: http://developer.appcelerator.com/helpdesk/view/74931
We've pushed a lot of orientation changes / updates recently for\n1.6.0, Can you guys verify if these pushes have fixed your problem,\nand mark as resolved?
@Marshall: Just verified that my original code sample now works\non my device.
\nTitanium SDK version: 1.7.0 (03/03/11 10:45 87a2113...)
\nWORKS on Android Device Epic 4G 2.2
Marking resolved per conversation with Dawson.