O
O
Oleg2020-01-05 10:24:21
Android
Oleg, 2020-01-05 10:24:21

How to debug if process is terminated?

Couldn't formulate the question better.
I'm debugging for a super budget version of a Digma smartphone with Android Go 8.1
. I have a fragment with a webView .
For the onCreate branch, rendering was divided into stages through handles.
After 2-3 seconds, a hat appears. Then the loading indicator. After 15 seconds, the rendering ends.
It turns out to be quite tolerable.
BUT !
open on top of another heavy program.
SIC! The debugger has fallen off
. We are trying to return through the list of previously opened programs
, and then I don’t see the white screen for 15 seconds and the logs.
Is there a debugging option easier than putting it into a file yourself?
Or maybe someone has already solved the problem with webview onResume ?
Zs On normal phones, everything is ok. This is a gloss for budget phones I'm trying to bring.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
O
Oleg, 2020-01-05
@402d

sorry, missed it. In logcat events continue to go. It only ended in run.
It remains to solve the problem with webview.
The cause of the original problem was.
1) Call WebView.enableSlowWholeDocumentDraw() . The method is static , but it invokes the download process of the Chrome lib . And I mistakenly believed that it is performed quickly. Moved it to the stub handler.
2) I already used the stub technique for displaying on the screen, but the handler waited 50 ms, and on the braked ones it takes at least a second.
Along the way. If the activity is a singleton and operates with fragments, then in the onNewIntent method, you also need to give
a little time to the main thread to wake the activity from sleep and only then work with the fragment manager.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question