Does it have something to do with on_start_up, or device_ready or app_ready events ?
its possible to fix.
please check docs/api.
one option is to have a local page that checks that the device has a good IP address before navigating to the remote page.
You can have a similar problem during usage of an app on a remote website if you leave the device in stand-by and then try to fire it up and navigate immediately to a new link. on Windows Mobile/CE devices usually it takes some time to recover WiFi connectivity...
In this second cases there're a couple of workarounds that involve using something like SymScript or using the defaultMetaTags option in the Config.xml of the Motorola Webkit rendering engine like the attached sample that at power on, wait for a valid IP and than navigate to the previous page.
Because you're effectively navigating to a different page and than back to the latest shown before suspension, you are effectively reloading the page and any changes done to it (editing, selection, etc) is lost.
Attached a video that shows this behaviour.