{ "id": "92315", "key": "TIMOB-9229", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "11", "description": "Is not a bug in our product", "name": "Not Our Bug" }, "resolutiondate": "2012-06-13T14:50:54.000+0000", "created": "2012-05-24T13:42:51.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "SupportTeam", "core" ], "versions": [ { "id": "13272", "description": "Release 2.0.1", "name": "Release 2.0.1", "archived": true, "released": true, "releaseDate": "2012-04-16" } ], "issuelinks": [ { "id": "17762", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "93174", "key": "TIDOC-671", "fields": { "summary": "Android: Document (article/wiki) Android application restart scenarios", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "Medium", "id": "3" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } }, { "id": "17740", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "62543", "key": "TIMOB-1911", "fields": { "summary": "Android: Titanium apps can't survive an activity relaunch", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "Critical", "id": "1" }, "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false } } } } ], "assignee": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "updated": "2017-03-22T21:55:30.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "h6.Issue\r\nOnce an app has been put into the background after going back it hangs in splash screen.\r\n\r\nh6.Tested on\r\nLG ally 2.2 (stack trace below) > it shows a black screen then app gets restarted\r\nRazr 2.3.5 (stack trace below) > it returns to the latest window working as expected \r\n\r\nh6.Steps to reproduce\r\n1. Build & Run an app\r\n2. Hit the Home key \r\n3. Expect more-less 30 minutes \r\n4. Go back to the Titanium app\r\n\r\nh6.tiapp.xml\r\n{code}\r\n 65536\r\n true\r\n false\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n{code}\r\n\r\n\r\nh3.Stack Trace - LG ally 2.2\r\n{code}\r\n05-24 13:02:19.289: I/dun_service(1516): process rmnet event\r\n05-24 13:02:19.289: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:20.129: I/ActivityManager(1347): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=com.appcelerator.onforce/.OnforceActivity }\r\n05-24 13:02:20.169: I/ActivityManager(1347): Start proc com.appcelerator.onforce for activity com.appcelerator.onforce/org.appcelerator.titanium.TiActivity: pid=23782 uid=10065 gids={1015, 1006, 3003}\r\n05-24 13:02:20.189: W/InputManagerService(1347): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@44e9eee0\r\n05-24 13:02:20.489: I/TiApplication(23782): (main) [0,0] checkpoint, app created.\r\n05-24 13:02:20.869: I/TiApplication(23782): (main) [381,381] Titanium 2.0.1 (2012/04/12 16:36 999c68a)\r\n05-24 13:02:21.089: I/TiApplication(23782): (main) [227,608] Titanium Javascript runtime: v8\r\n05-24 13:02:21.139: W/TiBaseActivity(23782): (main) [45,653] Unsupported, out-of-order activity creation. Finishing.\r\n05-24 13:02:21.139: W/TiApplication(23782): (main) [3,656] Scheduling application restart\r\n05-24 13:02:21.439: I/ActivityManager(1347): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x4 cmp=com.appcelerator.onforce/.OnforceActivity (has extras) }\r\n05-24 13:02:21.439: W/ActivityManager(1347): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x4 cmp=com.appcelerator.onforce/.OnforceActivity (has extras) }\r\n05-24 13:02:21.469: I/TiRootActivity(23782): (main) [0,0] checkpoint, on root activity create, savedInstanceState: null\r\n05-24 13:02:22.069: I/dun_service(1516): process rmnet event\r\n05-24 13:02:22.069: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:22.489: E/TiApplication(23782): (KrollRuntimeThread) [1022,1022] APP PROXY: ti.modules.titanium.app.AppModule@44ad7eb0\r\n05-24 13:02:22.619: W/V8Object(23782): Runtime disposed, cannot set property 'userAgent'\r\n05-24 13:02:22.999: E/TiAPI(23782): !!!\r\n05-24 13:02:22.999: E/TiAPI(23782): !!! WARNING : Use of unsupported constant Ti.UI.iPhone.TableViewSeparatorStyle.NONE !!!\r\n05-24 13:02:22.999: E/TiAPI(23782): !!!\r\n05-24 13:02:23.188: I/dun_service(1516): process rmnet event\r\n05-24 13:02:23.188: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:23.819: I/dun_service(1516): process rmnet event\r\n05-24 13:02:23.819: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:24.719: I/dun_service(1516): process rmnet event\r\n05-24 13:02:24.719: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:25.159: I/dun_service(1516): process rmnet event\r\n05-24 13:02:25.159: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:25.179: I/TiAPI(23782): [13:2:25] {adroidTabGroup} adding fake event blur\r\n05-24 13:02:25.189: I/TiAPI(23782): [13:2:25] {adroidTabGroup} adding fake event focus\r\n05-24 13:02:25.519: I/ActivityManager(1347): Starting activity: Intent { cmp=com.appcelerator.onforce/org.appcelerator.titanium.TiActivity (has extras) }\r\n05-24 13:02:25.789: I/TiRootActivity(23782): (main) [0,0] checkpoint, on root activity resume. activity = com.appcelerator.onforce.OnforceActivity@44ac1d40\r\n05-24 13:02:25.819: D/TiUIView(23782): (main) [31,31] Nativeview is null\r\n05-24 13:02:26.019: I/dun_service(1516): process rmnet event\r\n05-24 13:02:26.019: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:26.199: D/TiUIView(23782): (main) [374,405] Nativeview is null\r\n05-24 13:02:26.879: D/TiUIView(23782): (main) [681,1086] Nativeview is null\r\n05-24 13:02:26.879: I/dun_service(1516): process rmnet event\r\n05-24 13:02:26.879: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:26.999: I/ActivityManager(1347): Displayed activity com.appcelerator.onforce/org.appcelerator.titanium.TiActivity: 1133 ms (total 6841 ms)\r\n05-24 13:02:27.862: I/dun_service(1516): process rmnet event\r\n05-24 13:02:27.862: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:28.657: I/dun_service(1516): process rmnet event\r\n05-24 13:02:28.657: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:29.112: I/dun_service(1516): process rmnet event\r\n05-24 13:02:29.112: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:29.443: I/dun_service(1516): process rmnet event\r\n05-24 13:02:29.443: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:29.950: I/dun_service(1516): process rmnet event\r\n05-24 13:02:29.950: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n05-24 13:02:30.671: I/dun_service(1516): process rmnet event\r\n05-24 13:02:30.671: I/dun_service(1516): rstate == DUN_RMNETSTATE_ERROR in dun_monitor_kevents\r\n{code}\r\n\r\nh3.Stack trace - Razr 2.3.5\r\n{code}\r\n05-24 13:03:23.257: D/dalvikvm(16599): GC_EXPLICIT freed 95K, 46% free 3470K/6343K, external 2357K/2773K, paused 59ms\r\n05-24 13:03:23.265: I/Gmail(16599): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 530528, normalSync: true\r\n05-24 13:03:23.992: W/Settings(884): Setting wifi_networks_available_notification_on has moved from android.provider.Settings.System to android.provider.Settings.Secure, returning read-only value.\r\n05-24 13:03:23.992: I/ActivityManager(512): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=com.appcelerator.onforce/.OnforceActivity } from pid 884\r\n05-24 13:03:24.070: D/ActivityRenderTarget(884): onPause\r\n05-24 13:03:24.156: I/gralloc(512): Allocated 0x660072 size 6488161\r\n05-24 13:03:24.187: W/InputManagerService(512): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40a76750 (uid=10035 pid=884)\r\n05-24 13:03:24.195: I/ActivityManager(512): Resumed Activity: com.appcelerator.onforce/org.appcelerator.titanium.TiActivity totalTime: 204 ms\r\n05-24 13:03:25.335: I/gralloc(512): Allocated 0x660072 size 6488161\r\n05-24 13:03:29.265: D/dalvikvm(7750): GC_EXPLICIT freed 24K, 43% free 3304K/5767K, external 2368K/2773K, paused 59ms\r\n{code}\r\n\r\n\r\n\r\nh2.Device where splash screen is hanging\r\nLG Optimus running 2.2.2, it was stuck on the splash screen after trying to relaunch the app after half an hour. \r\n\r\nh4.Here are the logs for this test:\r\n{code}\r\n05-30 14:36:53.660: INFO/ActivityManager(114): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.appcelerator.onforce/.OnforceActivity }\r\n05-30 14:36:53.700: ERROR/TiBaseActivity(7818): (main) [2019042,2082106] Layout cleanup.\r\n05-30 14:36:53.850: ERROR/TiBaseActivity(7818): (main) [157,2082263] Layout cleanup.\r\n05-30 14:36:54.120: INFO/TiRootActivity(7818): (main) [0,0] checkpoint, on root activity resume. activity = com.appcelerator.onforce.OnforceActivity@45b2b820\r\n05-30 14:36:54.580: INFO/ActivityManager(114): Displayed activity com.appcelerator.onforce/.OnforceActivity: 2087206 ms (total 2087206 ms)\r\n05-30 14:37:12.860: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:37:12.860: INFO/dun_service(243): Post event 1\r\n05-30 14:37:12.870: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:37:12.870: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:37:14.770: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:37:14.770: INFO/dun_service(243): Post event 1\r\n05-30 14:37:14.770: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:37:14.780: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:37:50.900: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:37:50.900: INFO/dun_service(243): Post event 1\r\n05-30 14:37:50.900: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:37:50.900: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:38:27.120: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:38:27.120: INFO/dun_service(243): Post event 1\r\n05-30 14:38:27.120: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:38:27.120: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:38:29.020: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:38:29.020: INFO/dun_service(243): Post event 1\r\n05-30 14:38:29.030: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:38:29.030: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:38:33.940: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:38:33.940: INFO/dun_service(243): Post event 1\r\n05-30 14:38:33.951: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:38:33.951: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:38:35.040: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:38:35.040: INFO/dun_service(243): Post event 1\r\n05-30 14:38:35.050: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:38:35.050: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:39:13.150: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:39:13.150: INFO/dun_service(243): Post event 1\r\n05-30 14:39:13.160: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:39:13.160: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:39:14.160: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:39:14.160: INFO/dun_service(243): Post event 1\r\n05-30 14:39:14.160: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:39:14.160: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:39:15.160: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:39:15.160: INFO/dun_service(243): Post event 1\r\n05-30 14:39:15.170: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:39:15.170: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:39:15.860: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:39:15.860: INFO/dun_service(243): Post event 1\r\n05-30 14:39:15.870: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:39:15.870: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:39:17.170: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:39:17.170: INFO/dun_service(243): Post event 1\r\n05-30 14:39:17.180: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:39:17.180: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:40:07.430: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:40:07.430: INFO/dun_service(243): Post event 1\r\n05-30 14:40:07.430: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:40:07.430: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:40:09.330: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:40:09.330: INFO/dun_service(243): Post event 1\r\n05-30 14:40:09.340: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:40:09.340: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:41:07.840: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:41:07.840: INFO/dun_service(243): Post event 1\r\n05-30 14:41:07.840: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:41:07.840: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:41:09.540: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:41:09.540: INFO/dun_service(243): Post event 1\r\n05-30 14:41:09.551: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:41:09.551: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:41:59.222: ERROR/HierarchicalStateMachine(114): TetherMaster - unhandledMessage: msg.what=3\r\n05-30 14:41:59.222: ERROR/HierarchicalStateMachine(114): TetherMaster - unhandledMessage: msg.what=3\r\n05-30 14:41:59.422: WARN/Smack/Packet(232): notify conn break (IOEx), close connection\r\n05-30 14:41:59.482: INFO/GTalkService(232): [ServiceAutoStarter] --- connectivity changed\r\n05-30 14:41:59.482: INFO/GTalkService(232): [ServiceAutoStarter] --- start GTalk service ---\r\n05-30 14:41:59.532: INFO/MediaUploader(504): No need to wake up\r\n05-30 14:42:06.362: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:06.362: INFO/dun_service(243): Post event 1\r\n05-30 14:42:06.362: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:06.362: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:06.862: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:06.862: INFO/dun_service(243): Post event 1\r\n05-30 14:42:06.872: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:06.872: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:08.372: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:08.372: INFO/dun_service(243): Post event 1\r\n05-30 14:42:08.372: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:08.372: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:08.972: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:08.972: INFO/dun_service(243): Post event 1\r\n05-30 14:42:08.982: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:08.982: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:12.582: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:12.582: INFO/dun_service(243): Post event 1\r\n05-30 14:42:12.592: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:12.592: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:14.392: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:14.392: INFO/dun_service(243): Post event 1\r\n05-30 14:42:14.402: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:14.402: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:15.392: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:15.392: INFO/dun_service(243): Post event 1\r\n05-30 14:42:15.402: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:15.402: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:16.402: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:16.402: INFO/dun_service(243): Post event 1\r\n05-30 14:42:16.402: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:16.402: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:19.312: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:19.312: INFO/dun_service(243): Post event 1\r\n05-30 14:42:19.312: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:19.322: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n05-30 14:42:22.422: INFO/dun_service(243): The value returned from dun_getusbmodemstate_fromsys is 1 \r\n05-30 14:42:22.422: INFO/dun_service(243): Post event 1\r\n05-30 14:42:22.432: INFO/dun_service(243): received event: DUN_EVENT_USB_UNPLUG \r\n05-30 14:42:22.432: ERROR/dun_service(243): LG_DATA: Dun Reply Functions [DUN_STATE_USB_UNPLUG --> DUN_STATE_USB_UNPLUG][52]\r\n{code}\r\n\r\n", "attachment": [ { "id": "28305", "filename": "annotated_logcat.txt", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-06-12T15:40:49.000+0000", "size": 5111, "mimeType": "text/plain" } ], "flagged": false, "summary": "Android: Certain devices aren't able to survive on activity relaunch - splash screen hangs", "creator": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "environment": "Titanium SDK 2.0.1.GA2\r\nAndroid 2.2 & 2.3.5", "comment": { "comments": [ { "id": "196102", "author": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "body": "As per customer's inputs, here is a partial list of devices that exhibit this issue. Unfortunately – we don’t have logs from their beta testers.\r\n\r\nLG Optimus V (VM670)\r\nAndroid 2.2.2\r\n\r\nMotorola Atrix 4G (MB860)\r\nAndroid 2.3.6\r\n\r\nHuawei U9000\r\nAndroid 2.2.2\r\n\r\nHTC Evo 4G (PC36100)\r\nAndroid 2.3.3 and Android 2.3.5\r\n\r\nSamsung Galaxy Tab 8.9 (GT-P7310)\r\nAndroid 3.2\r\n\r\nDroid RAZR\r\nAndroid 2.3.6", "updateAuthor": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2012-05-25T10:07:04.000+0000", "updated": "2012-05-25T10:07:04.000+0000" }, { "id": "196356", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "body": "I only see traces that show expected behavior.\r\n\r\nThe trace from the LG Ally is showing the application restarting, which happens instead of a black screen / lockup. This occurs after Android has killed off the backgrounded application (i.e., to save memory, etc.) When the user selects to go back to the application, Android tries to re-instate it back to the exact same activity that was showing when it killed it off. We can't support that in Titanium, so we have to restart the app (which is better than sitting at the black screen, which is what would happen if we didn't restart the app). We cannot support that in Titanium because when a Titanium application is re-started, we need it to go through its \"normal\" lifetime, i.e., starting out with the root activity, since we need to fire up the Javascript runtime and do loads of other things which occur only when the \"root activity\" runs.\r\n\r\nThe trace from the Razr is showing an app that was **not** killed off by Android, therefore it just comes forward again.", "updateAuthor": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-05-29T14:21:00.000+0000", "updated": "2012-05-29T14:21:00.000+0000" }, { "id": "196357", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "body": "I'll let this hang about a bit before closing it as invalid, in case there are some questions/clarifications.", "updateAuthor": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-05-29T14:23:13.000+0000", "updated": "2012-05-29T14:23:13.000+0000" }, { "id": "196470", "author": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Customer reported a hang (on the splash screen) in a partial list of devices, will gather logs to provide wider insight around this.\r\n\r\nHere is a partial list of devices that hang on resume:\r\n\r\nandroid 2.3.6 Samsung Galaxy S 4G\r\nandroid 3.2 Galaxy Tab 7.0 Plus\r\nandroid 2.3.4 HTC EVO 3D\r\nandroid 2.3.4 T-Mobile G2\r\nandroid 2.3.6 Samsung Epic 4G Touch\r\nandroid 2.3.4 HTC EVO 3D\r\nandroid 2.3.4 HTC Droid Incredible\r\nandroid 2.3.4 HTC Merge\r\nandroid 2.3.4 X500\r\nandroid 2.3.4 HTC Thunderbolt\r\nandroid 2.3.3 DROIDX\r\nandroid 2.3.4 DROID BIONIC\r\nandroid 2.3.5 HTC EVO 4G\r\nandroid 2.3.6 Samsung Galaxy S II\r\nandroid 2.3.4 Samsung Admire\r\nandroid 2.3.6 Motorola Atrix 4G\r\nandroid 2.3.6 Samsung Epic 4G Touch\r\nandroid 2.2.1 Samsung Galaxy S 4G\r\nandroid 2.3.4 Samsung Admire\r\nandroid 2.3.4 HTC Thunderbolt\r\nandroid 2.2.1 Samsung Galaxy S 4G\r\nandroid 2.3.4 HTC EVO 3D\r\nandroid 2.3.3 DROID Pro\r\nandroid 2.3.6 Samsung Replenish\r\nandroid 2.3.6 DROID RAZR\r\nandroid 2.3.5 Samsung Galaxy Prevail\r\nandroid 2.2 LG Optimus T\r\nandroid 2.3.4 HTC Glacier\r\nandroid 2.3.4 HTC Thunderbolt\r\nandroid 2.3.4 HTC EVO 3D", "updateAuthor": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2012-05-30T07:51:48.000+0000", "updated": "2012-05-30T10:08:01.000+0000" }, { "id": "196555", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "body": "Understood. Can you edit the description? Currently it says \"Issue: Once an app has been put into the background after going back (~30 minutes) it restarts.\" The fact that it restarts is not an issue, if I understand you correctly now.\r\n\r\nThe phone models are not really relevant so no need to add to this list. *We need logs*. I'm happy to give it a few (but only a few) test runs on my phones, but I'll need precisely the same version of the app that others are using who are experiencing this.\r\n\r\nIf I can't reproduce it easily, someone else is going to have to take over the attempts at reproduction.\r\n\r\n", "updateAuthor": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-05-30T13:01:18.000+0000", "updated": "2012-05-30T13:01:18.000+0000" }, { "id": "196577", "author": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Edit the description to accurately reflect what their current issue is.\r\n\r\nI've sent resources to test on some more devices and will be updating this ticket with logs little bit later today.", "updateAuthor": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2012-05-30T14:17:01.000+0000", "updated": "2012-05-30T14:17:01.000+0000" }, { "id": "196605", "author": { "name": "jyounus", "key": "jyounus", "displayName": "Junaid Younus", "active": true, "timeZone": "Europe/London" }, "body": "Tested with a Samsung Galaxy S2 running 2.3.6, it didn't crash, didn't show a black screen and it didn't hang during the splash screen. It restarted the app as normal.\r\n\r\nSecond test: LG Optimus running 2.2.2, it was stuck on the splash screen after trying to relaunch the app after half an hour. Here are the logs for this test: http://pastebin.com/sDBaV17y\r\n\r\nThe SDK I used was 2.0.1GA2 during both tests.", "updateAuthor": { "name": "jyounus", "key": "jyounus", "displayName": "Junaid Younus", "active": true, "timeZone": "Europe/London" }, "created": "2012-05-30T15:59:38.000+0000", "updated": "2012-05-30T15:59:38.000+0000" }, { "id": "198119", "author": { "name": "mstepanov", "key": "mstepanov", "displayName": "Max Stepanov", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I was able to easily reproduce the splash \"hang\" issue with Android Emulator for both V8 and Rhino. Same instructions: run the app, dashboard screen appears, navigate to \"All Work\", press Home button, wait 30mins, open the app again.\r\nThe splash \"hang\" is not the actual hang, but the the application is not navigating form the initial splash. \r\nIt seems to be very connected to the fix made in TIMOB-1911. Then no splash is set, it is effectively black as in TIMOB-1911.", "updateAuthor": { "name": "mstepanov", "key": "mstepanov", "displayName": "Max Stepanov", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-06-11T19:08:57.000+0000", "updated": "2012-06-11T19:08:57.000+0000" }, { "id": "198123", "author": { "name": "mstepanov", "key": "mstepanov", "displayName": "Max Stepanov", "active": true, "timeZone": "America/Los_Angeles" }, "body": "After adding *true* to tiapp.xml the app seems to restart normally, but logs the following to console:\r\n{code}\r\nI/ActivityManager( 62): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.appcelerator.onforce/.OnforceActivity } from pid 129\r\nD/TiBaseActivity( 463): (main) [4506471,4873234] Activity org.appcelerator.titanium.TiActivity@40683d60 onDestroy\r\nE/TiBaseActivity( 463): (main) [1,4873235] Layout cleanup.\r\nE/WindowManager( 463): Activity org.appcelerator.titanium.TiActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@406b6eb0 that was originally added here\r\nE/WindowManager( 463): android.view.WindowLeaked: Activity org.appcelerator.titanium.TiActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@406b6eb0 that was originally added here\r\nE/WindowManager( 463): \tat android.view.ViewRoot.(ViewRoot.java:258)\r\nE/WindowManager( 463): \tat android.view.WindowManagerImpl.addView(WindowManagerImpl.java:148)\r\nE/WindowManager( 463): \tat android.view.WindowManagerImpl.addView(WindowManagerImpl.java:91)\r\nE/WindowManager( 463): \tat android.view.Window$LocalWindowManager.addView(Window.java:424)\r\nE/WindowManager( 463): \tat android.app.Dialog.show(Dialog.java:241)\r\nE/WindowManager( 463): \tat ti.modules.titanium.ui.widget.TiUIDialog.show(TiUIDialog.java:253)\r\nE/WindowManager( 463): \tat ti.modules.titanium.ui.AlertDialogProxy$1.run(AlertDialogProxy.java:72)\r\nE/WindowManager( 463): \tat android.os.Handler.handleCallback(Handler.java:587)\r\nE/WindowManager( 463): \tat android.os.Handler.dispatchMessage(Handler.java:92)\r\nE/WindowManager( 463): \tat android.os.Looper.loop(Looper.java:130)\r\nE/WindowManager( 463): \tat android.app.ActivityThread.main(ActivityThread.java:3683)\r\nE/WindowManager( 463): \tat java.lang.reflect.Method.invokeNative(Native Method)\r\nE/WindowManager( 463): \tat java.lang.reflect.Method.invoke(Method.java:507)\r\nE/WindowManager( 463): \tat com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)\r\nE/WindowManager( 463): \tat com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)\r\nE/WindowManager( 463): \tat dalvik.system.NativeStart.main(Native Method)\r\nD/TiBaseActivity( 463): (main) [151,4873386] Activity org.appcelerator.titanium.TiActivity@4061f478 onDestroy\r\nE/TiBaseActivity( 463): (main) [1,4873387] Layout cleanup.\r\nI/TiRootActivity( 463): (main) [0,0] checkpoint, on root activity restart. activity = com.appcelerator.onforce.OnforceActivity@40611b88\r\nD/TiBaseActivity( 463): (main) [27,27] Activity com.appcelerator.onforce.OnforceActivity@40611b88 onRestart\r\nW/TiLaunchActivity( 463): (main) [2,29] Tasks may have been destroyed by Android OS for inactivity. Restarting.\r\nW/TiApplication( 463): (main) [2,31] Scheduling application restart\r\nD/TiBaseActivity( 463): (main) [29,60] Activity com.appcelerator.onforce.OnforceActivity@40611b88 onStart\r\n{code}\r\n\r\nThis may give some hints on what's going on.\r\n\r\n", "updateAuthor": { "name": "mstepanov", "key": "mstepanov", "displayName": "Max Stepanov", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-06-11T23:28:27.000+0000", "updated": "2012-06-11T23:28:27.000+0000" }, { "id": "198273", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "body": "After a long period of inactivity, Android will choose to \"restart\" the launch activity (what we often call the root activity) and kill off the activities above it. That's what's happening when you see the splash screen (the splash screen is the root activity).\r\n\r\nChoices:\r\n\r\n* Use the property max mentions above, which will restart the app (you can safely ignore the message he's shown there regarding the leaked window -- we're killing off the app anyway and forcing a restart.)\r\n\r\n* Put something like this in near the top of your app.js:\r\n\r\n{code}\r\nvar initialLaunchPerformed = false;\r\nTi.Android.currentActivity.addEventListener(\"resume\", function() {\r\n\tif (!initialLaunchPerformed) {\r\n\t\tinitialLaunchPerformed = true;\r\n\t\treturn;\r\n\t}\r\n\t// If we reach here we know the root activity is being resumed for the second (or greater time), such\r\n\t// as when the restart scenario explained in TIMOB-9229 occurs. Just start the application-specific code\r\n\t// again.\r\n\trunApplication();\r\n});\r\n{code}\r\n\r\nOf course for the latter you'll need to make sure your application code can handle being run a second time without any anomalies.\r\n\r\nThe nice thing about the second option is that it avoids the ugly full application restart (which is very visible) you get if you use the first option.", "updateAuthor": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-06-12T16:50:22.000+0000", "updated": "2012-06-12T16:50:22.000+0000" }, { "id": "198327", "author": { "name": "mstepanov", "key": "mstepanov", "displayName": "Max Stepanov", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Bill, I think we should document this behavior in the wiki ?\r\nAlso, does it make sense to set ti.android.root.reappears.restart=true by default ?", "updateAuthor": { "name": "mstepanov", "key": "mstepanov", "displayName": "Max Stepanov", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-06-13T10:06:41.000+0000", "updated": "2012-06-13T10:06:41.000+0000" }, { "id": "198380", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "body": "Created a doc ticket for documenting this TIMOB-9523.\r\n\r\nWe can't set that as default because some apps actually use the root activity to show UI (as opposed to it just having the default background which is the \"splash\".) Such apps don't need to be restarted. This app, however, uses a heavyweight window to display its UI.", "updateAuthor": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-06-13T14:49:49.000+0000", "updated": "2012-06-13T14:49:49.000+0000" }, { "id": "198381", "author": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "body": "cf TIMOB-9523 for us to document what's happening in this scenario.", "updateAuthor": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "created": "2012-06-13T14:50:54.000+0000", "updated": "2012-06-13T14:50:54.000+0000" }, { "id": "328234", "author": { "name": "athorne", "key": "athorne", "displayName": "Alex Bernier", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~billdawson], that code snippet worked great. Thank you. Also, I really appreciate the reproduction steps (forcing the app closed from settings) as this was hard to reproduce and test before that. Hoping this fix stands the test of time!", "updateAuthor": { "name": "athorne", "key": "athorne", "displayName": "Alex Bernier", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-10-15T20:38:44.000+0000", "updated": "2014-10-15T20:38:44.000+0000" }, { "id": "328550", "author": { "name": "athorne", "key": "athorne", "displayName": "Alex Bernier", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I actually still see black screen on resume sometimes. I'm going to try the ti.android.root.reappears.restart property.", "updateAuthor": { "name": "athorne", "key": "athorne", "displayName": "Alex Bernier", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-10-20T00:41:31.000+0000", "updated": "2014-10-20T00:41:31.000+0000" }, { "id": "415061", "author": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket as the issue mentioned here is not our bug.", "updateAuthor": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2017-03-22T21:55:30.000+0000", "updated": "2017-03-22T21:55:30.000+0000" } ], "maxResults": 21, "total": 21, "startAt": 0 } } }