View Single Post
Old 06-19-2021, 07:13 AM   #21
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Hi. ANRs can be triggered in any device, you just need to follow the steps in: https://github.com/koreader/koreader...ment-752251104

Most of the time ANR's happen this way:

1. User performs an action that takes time to finish.
2. User press the touchscreen one or a few times while the action is executing.
3. If the action takes more than 5seconds Android will think the app isn't responding.

We can workaround it: see https://github.com/koreader/koreader...ment-752255904. That requires users to document what they did to trigger them on the first place.

If certain Onyx models have other kind of issues or a stricter timeout I can't say. But certainly OP issue was fixed and the bug made sense (even when it was something that doesn't affect any other device made by any other vendor)

If you can still reproduce OP issue (Suspend the device, wait 20 seconds, press the power button, KOReader not responding) then please use the "Help" -> "Bug report" to get filtered logs.

If your issues are not strictly like OP but you can make them reproducible following certain steps please describe them.
pazos is offline   Reply With Quote