I've been continuing to plug away at this problem as time allows.
Recently, I determined that during the lengthy resumes, one and
sometimes two threads are using 100% cpu. One of those threads is
always thread 1 as reported by gdb. Whenever I stop the app and look,
that thread is always in __epo
Hi Petar,
A private reply also pointed out to me that the long resume times I
see are highly unusual. I'm starting to change my focus now to
understanding why that is happening in the first place.
I'll check those activity options again. The last time I looked, they
didn't sound like what I wan
I have looked at Kodi and found other things of interest like where
and how they pause playback when focus is lost. I've yet to find
anything that relates to why Kodi resumes where it was sometimes and
restarts from scratch at other times.
David
On Wed, Aug 08, 2018 at 08:47:19AM +0200, René Han
Hi David.
For the past 3-4 years I've been actively doing Android/Qt development and
I have never had such an issue.
On many different Android boxes, TVs and phones I haven't had something
like that, not even on Nvidia shield.
Resume always happens in a matter of seconds even after standby or long
As far as I know, Kodi is open source. So is their Android client:
https://kodi.wiki/view/Android_development
Maybe check it out for inspiration.
/René
On Tue, 7 Aug 2018 at 21:35 David Engel wrote:
> Hi,
>
> I'm one of the developers of the MythTV, open source DVR. Over the
> last several
Hi,
I'm one of the developers of the MythTV, open source DVR. Over the
last several months, we've ported our frontend (aka client) from Linux
with Qt to run on Android with Qt. It's to the point now that some of
us are using Nvidia Shield TVs as our primary frontends.
One annoying problem that
