Next alpha release of Necessitas

[Ruben .]

Update on ticket #22

Unfortunately, today when I tried to resume our app (which on this occasion
was in the foreground) it had frozen. Everything looked nice, but no
response on touch. I tried to use the home button and then start our app
from the desktop icon and then i just got the black screen. I had to kill
the task from task manager. One hour later the exact same happened again.

On both occasions I noticed that Google Play was running in background. Not
sure if that can have something to do with it.

So it might seem like that the fix for resume is not completely fixed after
all. However it seems to me that problem is not happening as often as
before. I'll keep you updated.

Regarding the Android OS killing background apps, thanks for some good
input on how to make it less likely to happen.

Ruben



On Tue, Jul 17, 2012 at 11:03 PM, Ruben . <colruby2 at gmail.com> wrote:

> First, thanks for explaining how to test with the latest Ministro
> repository.
>
> I've now tested our app for about 24 hours.
>
> The good "news": Our app has not hung on any resume as it normally did
> with the standard alpha3 libs. I've tested overnight, received and placed
> phone calls, started other apps etc... As long as our own app is still
> showing in the task manager it has always showed up again as it should. I
> noticed one time that it took some seconds before the app reacted on
> first touch after resume and I assume it then probably reloaded some
> necessary libs (as I would expect it to do).
>
> The bad "news": On two occasions so far our app was not running at all any
> more when I resumed the phone, gone in the task manager. I don't know if
> this is related directly to the resume problem (ticket #22).
>
> Is seems that the most important issue, resume a still running app, is
> fixed. However, if someone else experience that the app is not running at
> all when the device itself is resumed please give it a post here. Or even
> better, maybe someone know how to work around/fix it :-)
>
> Ruben
>
>
>
>
>
> On Tue, Jul 17, 2012 at 10:31 PM, Ruben . <colruby2 at gmail.com> wrote:
>
>> Hi,
>>
>>
>>
>> Our target release date is the end of this month, currently we
>> are desperately trying to put all the things together.
>>
>> Because we encounter a lot problems it may be delayed a few days (maybe a
>> week or two).
>>
>>
>>
>> What do you mean be "unstable version on alpha3"? There is  no unstable
>> version of alpha3 :)!
>>
>> If you mean Ministro's unstable repository, then it means that the
>> problem is not solved by alpha4, because now Ministro's unstable
>> repository contains a testing release of alpha4.
>>
>>
>>
>> To be sure you are testing it correctly make sure you are using the last
>> Minsitro (is not on market yet) from here
>> http://files.kde.org/necessitas/installer/MinistroActivity.apk and and
>> then use "Ministro Configuration Tool"
>>
>> to switch to "Unstable" repository and try again the issue.
>>
>>
>>
>> Cheers,
>>
>> BogDan.
>>
>>
>>
>>
>>
>>
>>
>> ----- Original Message -----
>>
>> > From: Ruben
>>
>> > To: BogDan <bog_dan_ro at yahoo.com>
>>
>> > Cc:
>>
>> > Sent: Monday, July 16, 2012 10:10 AM
>>
>> > Subject: RE: Next alpha release of Necessitas
>>
>> >
>>
>> > Hi BogDan.
>>
>> >
>>
>> > Any thoughts now about when the next release (alpha4) will be?
>>
>> > We are desperately waiting for a fix on ticket #22 (Problem resuming
>>
>> > application on device)...
>>
>> >
>>
>> > I've tried the unstable version on alpha3 but that didn't help, so I
>>
>> > assume we can't get it tested until alpha4 is released...?
>>
>> >
>>
>> >
>>
>> > Best regards,
>> > Ruben
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/necessitas-devel/attachments/20120718/34ad7c1e/attachment.html>