Note that there are some explanatory texts on larger screens.

plurals
  1. POSGS-3 bug related to SMS conversations list?
    text
    copied!<p>This issue was reported several times, but still not resolved yet. I read all messages/thread which somehow related to this topic either in <a href="http://developer.samsung.com/search/searchList.do?searchTop=content://mms-sms/conversations" rel="nofollow noreferrer">Samsung's developers site</a> or <a href="https://stackoverflow.com/questions/12664101/mms-content-provider-issue-samsung-galaxy-s3">in StackOverflow</a></p> <p>Let me again describe whole problem just in few words:</p> <ol> <li><p>Developers used to get list of SMS conversations through simple query like:</p> <p><code>Uri.parse("content://mms-sms/conversations/"); Cursor cursor = context.getApplicationContext().getContentResolver().query(uri, null, null, null, null);</code></p> <p>or something like this. Key point here's URI address: <code>content://mms-sms/conversations</code></p></li> <li><p>Everyone knows that it's unofficial and one's doing it on his own risk - <a href="http://android-developers.blogspot.ru/2010/05/be-careful-with-content-providers.html" rel="nofollow noreferrer">see proof link here</a> </p></li> <li><p>But, critical point here's a simple fact this code doesn't work properly only in Samsung Galaxy S3 and some models of Galaxy Tab 2. It produces <code>NullPointerException</code> with stacktrace:</p> <p><code>java.lang.NullPointerException at android.os.Parcel.readException(Parcel.java:1431) at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:188) at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:140) at android.content.ContentProviderProxy.query(ContentProviderNative.java:366) at android.content.ContentResolver.query(ContentResolver.java:372) at android.content.ContentResolver.query(ContentResolver.java:315)</code></p></li> </ol> <p>In all other devices of the rest of the World/Universe it works well! Strange, huh?</p> <p>I know answers like: hey dude, it's your problem, since presence/correctness of aforementioned URI doesn't guaranteed, nevertheless, does someone has more productive idea?</p> <p>I have already posted question to Samsung's developers through their forum.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload