yep, I miss-spoke. onResume is what I use.
On Dec 17, 4:46 pm, filbert wrote:
> If you close your connection in onPause, wouldn't you need to open it
> again in onResume?
>
> On Dec 13, 6:08 pm, Paul wrote:
>
> > In order to play nicely with the resources you share with other
> > applications
If you close your connection in onPause, wouldn't you need to open it
again in onResume?
On Dec 13, 6:08 pm, Paul wrote:
> In order to play nicely with the resources you share with other
> applications I think you might want to consider creating your
> connection in onCreate, and cleaning it up
In order to play nicely with the resources you share with other
applications I think you might want to consider creating your
connection in onCreate, and cleaning it up in onPause. You mentioned
an issue when you tried that earlier but it might be worth resolving
within your app. This will keep
I cleared up my problem with the SQL not closing and creating a leak
by make sure to close the connection in onDestroy. I had tried to
close the connection earlier, but that caused a different problem.
When I close it in onDestroy everything works well. Hope that might
help someone.
On Dec 13, 5:
Wondering if you ever solved this? I am getting a similar problem and
I have not found anything that works, or others solutions.
On Nov 26, 10:30 pm, "bharath kumar" wrote:
> Hi AndroidDev,
> 11-24 19:27:38.287: ERROR/Database(5891): Leak found
> 11-24 19:27:38.287: ERROR/Database(5891): java.l
5 matches
Mail list logo
