Strange Exceptions when deleting and reading contacts

by Samuh » Wed, 08 Sep 2010 19:29:56 GMT


Sponsored Links
 I am getting following exceptions when I try to read/delete contacts
from my application using Contacts Content Provider.
What does the following mean?

ERROR/IMemory(1349): binder=0x490f38 transaction failed
fd=-2147483647, size=0, err=-2147483646 (Unknown error: 2147483646)
ERROR/IMemory(1349): cannot dup fd=-2147483647, size=0,
err=-2147483646 (Bad file number)
ERROR/IMemory(1349): cannot map BpMemoryHeap (binder=0x490f38),
size=0, fd=-1 (Bad file number)
ERROR/JavaBinder(1349): *** Uncaught remote exception!  (Exceptions
are not yet supported across processes.)
ERROR/JavaBinder(1349): java.lang.RuntimeException: No memory in
memObj
ERROR/JavaBinder(1349):     at
android.database.CursorWindow.native_init(Native Method)
ERROR/JavaBinder(1349):     at
android.database.CursorWindow.<init>(CursorWindow.java:518)
ERROR/JavaBinder(1349):     at
android.database.CursorWindow.<init>(CursorWindow.java:27)
ERROR/JavaBinder(1349):     at android.database.CursorWindow
$1.createFromParcel(CursorWindow.java:493)
ERROR/JavaBinder(1349):     at android.database.CursorWindow
$1.createFromParcel(CursorWindow.java:496)
ERROR/JavaBinder(1349):     at
android.content.ContentProviderNative.onTransact(ContentProviderNative.java:
96)
ERROR/JavaBinder(1349):     at
android.os.Binder.execTransact(Binder.java:287)
ERROR/JavaBinder(1349):     at dalvik.system.NativeStart.run(Native
Method)

Thanks.

--



Strange Exceptions when deleting and reading contacts

by Arjun » Thu, 09 Sep 2010 08:24:35 GMT


 I guess you cannot delete contacts  either you can read or write
contacts but you cannot delete contacts.
might be the reason for transaction failure exceptions
Thanks,
Arjun.




--


Sponsored Links


Strange Exceptions when deleting and reading contacts

by William Ferguson » Thu, 09 Sep 2010 11:54:35 GMT


 I recall getting something similar when trying to retrieve too big a
dataset.
Ie I was trying to retrieve lots of columns. Reducing them to as small
a set as possible removed the error.

I put it down to some hard allocation llimit in the SqlLite DB that
didn't express it well.





--



Other Threads

1. Ignoring magnetic field sensor, calibrating the accelerometer

I'm trying to use the accelerometer sensor for a game.

1) I am currently ignoring the magnetometer and using a static value
for the magnetic field vector. My reasoning is that the magnetometer
is subject to interference and will likely give more varied values
than the accelerometer, so I'd like to not use it if possible. I'm
also not sure that it is necessary for most motion-based game
control.  Does this make sense?

2) I'm attempting to get a baseline accelerometer value, but it
appears as if the sensor returns a junk/default value for a given axis
unless a change is detected along that axis. So it seems as if I can't
get an accurate baseline value while the phone is lying perfectly
still -- am I understanding this right? Is there any way to work
around this problem?

Thanks.

-- 

2. Android shared preferences assignments not persisting between emulator sessions

I am using the following code to save data to my Android application's
shared preferences:

    private SharedPreferences getOurSharedPreferences() {
        return getSharedPreferences(SHARED_PREFS_FILENAME,
MODE_PRIVATE);
    }

    SharedPreferences sharedPrefs = getOurSharedPreferences();
    SharedPreferences.Editor editor = sharedPrefs.edit();
    editor.putString(keyName, theString);
    if (!editor.commit())
        throw new RuntimeException("Unable to save new string.");

    // Get it back as a test.
    String s2 = getStringFromStorage(keyName);

Where SHARED_PREFS_FILENAME is a private final static string and
keyName is the name of whatever key I'm currently using as a field
name. The commit works fine, I don't get an exception. As you can see
I added a test that retrieves the recently committed string and when I
check it (s2) the value is fine. So I am not having any problems with
shared preferences storage during the lifetime of my app. However,
when I relaunch the application in the emulator the shared preferences
storage area is empty and I can't find the values I stored in the last
emulator session. I did some reading and as far as I can see the
stored values should persist across sessions, apparently they are
saved in an XML file belonging to the emulator. Yet I am having
problems.

Can anyone tell me why my shared preferences storage values are not
persisting between Android emulator sessions?

-- roshcler

-- 

3. Display list of saved tables to be opened

4. path to sqlite3 database

5. <WTS> Xoom, thunderbolt ama pix plus palm

6. ListActivity Memory leak with onConfigurationChanged

7. parsing an image from an xml file from a network