Calling stopManagingCursor() also solved this issue for me. In my
onResume(), I was rebuilding the cursor since it was likely data had
been added. Needed to add a call to stopManagingCursor() on the
current instance before creating the new one. Seems like I should have
been doing this all along.
@andfan22 - I am seeing the same thing. I've been able to get past it,
but only by comment out all code using FilterQueryProvider. I've tried
all I can think of to manage the lifecycle, but can't get it right.
Are you using FilterQueryProvider? I see that they are mapping the 2.x
calls into 3.0
Hi Romain,
To follow up on this question, if the list is really big, so big that
even 'what's needed to fill the screen with data' takes enougth time to
generate a timeout, what to do?
I guess it could be populated by chunks, but it gets nasty I think...
You have to do the query in a
Hi,
I'm creating a sqlite3 database on a linux box. This db is valid on
the box, I can select and all... When I download the file on the phone
(emulator in my case), and try to read it with an SQLiteDatabase, any
request will raise an exception 'invalid file'. I've checked the file
is not
Hi all,
I've been trying to create a local connection to a computer with a
Socket from the emulator thinking that it would automagically uses a
emulated wifi connection. It doesn't work, in particular because wifi
is not supported on the emulator:
- Does a Socket connection automatically
Hello,
I'd like to use an existing sqlite3 database created outside of the
phone, on a computer reachable by Wifi. I know how to download the
file using Socket. The problem I see is that android.database.sqlite
classes access databases only in /data/data/package_name/databases
and it does not
6 matches
Mail list logo
