Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8922901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T06:57:54+00:00 2026-06-15T06:57:54+00:00

This issue was reported several times, but still not resolved yet. I read all

  • 0

This issue was reported several times, but still not resolved yet. I read all messages/thread which somehow related to this topic either in Samsung’s developers site or in StackOverflow

Let me again describe whole problem just in few words:

  1. Developers used to get list of SMS conversations through simple query like:

    Uri.parse("content://mms-sms/conversations/");
    Cursor cursor = context.getApplicationContext().getContentResolver().query(uri, null, null, null, null);

    or something like this. Key point here’s URI address: content://mms-sms/conversations

  2. Everyone knows that it’s unofficial and one’s doing it on his own risk – see proof link here

  3. 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 NullPointerException with stacktrace:

    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)

In all other devices of the rest of the World/Universe it works well! Strange, huh?

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?

I have already posted question to Samsung’s developers through their forum.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T06:57:55+00:00Added an answer on June 15, 2026 at 6:57 am

    In the end I’ve figured how to overcome aforementioned issue (I am not sure that it’s bug, but anyway it looks like a bug).

    List of conversations can be retrieved through this query:

    Uri.parse("content://mms-sms/conversations?simple=true"); 
    Cursor cursor = context.getApplicationContext().getContentResolver().query(uri, null, null, null, null);
    

    Keypoint here’s URI content://mms-sms/conversations?simple=true.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This issue has been previously reported, but I still have not been able to
I ran the stsadm -o preupgradecheck and I get this issue reported but I
Update: This issue was not properly explored. The real issue lies within render :json
We are having this issue with our production servers (apache-tomcat-7.0.6), which is running a
I tried Google this issue and was searched over an hour on Stackoverflow, but
This issue has been reported here and has been closed. I do see that
Strange issue- I have a complex DTO with several child objects, declared like this:
This issue has been on/off bugging me and I've written 4 wrappers now. I'm
This issue is better demonstrated than explained, so I've set up a git repo
This issue has me baffled, it's affecting a single user (to my knowledge) and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.