Why cannot start appium sometimes?

I have been using appium for automated testing for while now. Now I am using the appium1.2.0.
When I use the simulator to restart appium, often can not start.When I use the mobile phone ,the success rate of starting appium is greatly improved.Is there any method provided to capture this error?

debug: Getting focused package and activity
debug: executing: “E:\sdk32\sdk\tools\adb.exe” -s 192.168.56.101:5555 shell “dum
psys window windows”

then prompting an error,the current package /activity never started.

debug: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
debug: [BOOTSTRAP] [debug] Got command of type SHUTDOWN

debug: Getting focused package and activity
debug: executing: “E:\sdk32\sdk\tools\adb.exe” -s 192.168.56.101:5555 shell “dum
psys window windows”
debug: Getting focused package and activity
debug: executing: “E:\sdk32\sdk\tools\adb.exe” -s 192.168.56.101:5555 shell “dum
psys window windows”
debug: Getting focused package and activity
debug: executing: “E:\sdk32\sdk\tools\adb.exe” -s 192.168.56.101:5555 shell “dum
psys window windows”
error: com.jsmcc/.ui.WelcomeActivity never started. Current: com.jsmcc/.ui.Featu
reActivity
debug: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
debug: [BOOTSTRAP] [debug] Got command of type SHUTDOWN
debug: [BOOTSTRAP] [debug] Returning result: {“value”:“OK, shutting down”,“statu
s”:0}
debug: [BOOTSTRAP] [debug] Closed client connection
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.boot
strap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
debug: [UIAUTOMATOR STDOUT] Time: 21.103
debug: [UIAUTOMATOR STDOUT] OK (1 test)
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
debug: Sent shutdown command, waiting for UiAutomator to stop…
debug: UiAutomator shut down normally
debug: Cleaning up android objects
debug: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: com.jsmcc/.ui.WelcomeA
ctivity never started. Current: com.jsmcc/.ui.FeatureActivity
debug: Error: com.jsmcc/.ui.WelcomeActivity never started. Current: com.jsmcc/.u
i.FeatureActivity
at null. (C:\Users\Administrator\AppData\Roaming\npm\node_modules
\appium\node_modules\appium-adb\lib\adb.js:1317:12)
at null. (C:\Users\Administrator\AppData\Roaming\npm\node_modules
\appium\node_modules\appium-adb\lib\adb.js:1259:7)
at null. (C:\Users\Administrator\AppData\Roaming\npm\node_modules
\appium\node_modules\appium-adb\lib\adb.js:173:9)
at ChildProcess.exithandler (child_process.js:645:7)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:755:16)
at Process.ChildProcess._handle.onexit (child_process.js:822:5)
debug: Responding to client with error: {“status”:33,“value”:{“message”:“A new s
ession could not be created. (Original error: com.jsmcc/.ui.WelcomeActivity neve
r started. Current: com.jsmcc/.ui.FeatureActivity)”,“origValue”:“com.jsmcc/.ui.W
elcomeActivity never started. Current: com.jsmcc/.ui.FeatureActivity”},“sessionI
d”:null}
info: <-- POST /wd/hub/session 500 25799.697 ms - 288

You’re expecting WelcomeActivity and it’s on FeatureActivity. You can expect multiple activities by using a comma.