"content://sms/"

by Ralph Bergmann » Fri, 14 May 2010 16:18:17 GMT


Sponsored Links
 Hi,


I have a question about the "content://sms/" provider.

I use it in my app but can't find any official documentation about it :-(

Is it to old? Or to new? Can I use it or is it deprecated and will 
removed in future?



Ralph

--



"content://sms/"

by Mark Murphy » Fri, 14 May 2010 18:18:54 GMT


 


It is not supported. It may not work on some devices. It may not work in
future versions of Android.

 http://android-developers.blogspot.com/2010/05/be-careful-with-content-providers.html 

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://github.com/commonsguy 
 http://commonsware.com/blog  |  http://twitter.com/commonsguy 

Android Training...At Your Office:  http://commonsware.com/training 

--


Sponsored Links


"content://sms/"

by Mike dg » Sun, 16 May 2010 01:13:33 GMT


 It may also not work with third part SMS apps.





>



"content://sms/"

by Jesper » Thu, 08 Jul 2010 02:33:13 GMT


 Is there any official way of reading sms? I have been reading on some
pages and seems it was removed without any information on why, and it
has not been replaced with something new. What would be the reason of
removing it? hard to believe it is security if they left a
undocumented provider that is still usable.
Any thoughts?





>



"content://sms/"

by Mark Murphy » Thu, 08 Jul 2010 03:02:52 GMT


 


You would have to ask the developer of each SMS application on each
phone that question.

For the Messaging application, there is no documented and supported
content provider for that client. And, that's not the only client.


Sometimes, it it because they are not ready to support the interface
for the next decade-plus.

Sometimes, it is because they want to give OEMs the freedom to replace
AOSP apps and do not want to tie the OEMs hands by forcing them to
implement certain APIs.

Sometimes, it is a matter of engineering priorities.

And, of course, as you note, sometimes it is tied to security.

There are probably other reasons as well -- those are the four I know
off off the top of my cold-fogged head.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://github.com/commonsguy 
 http://commonsware.com/blog  |  http://twitter.com/commonsguy 

_Android Programming Tutorials_ Version 2.8 Available!

--



Other Threads

1. Android Initialization (specifically, where does screen timeout get set ??)

Try looking in frameworks/base/packages/SettingProvider/res/values/
defaults.xml

Of course, you don't need to change this if the keys are defined
correctly to wake the system up. Check the laytout file that is being
used in /system/usr/layout and see the documentation for how to define
keys that can cause wake up in:

http://pdk.android.com/online-pdk/guide/keymaps_keyboard_input.html

Mike




--

2. Ask Camera FX

Baru nyoba V3.1 tp koq kalo kita zoom display jd pitih

Rgds
Jus
~ android dream g1 eclair ~

-- 
"Indonesian Android Community [id-android]" 

3. Getting Jamaica on the list of certified countries

4. eclair build error

5. Gesture Builder - no gestures found

6. Temen2 Di Jogja Ngariung .. eh ngumpul yuk .. jgn mpe ketinggalan .. he he

7. Stopping thread when last activity finishes