Hi, Kostya. Thanks for your response, and for info on your strange experience with WiFi on the Galaxy Tablet.
My problem is not to make SMS-functions work on the Galaxy Tab (which they do), but to make SMS apps visisble to devices which support SMS (including the Galaxy Tabs) - and only those. One could obviously try something like what you suggest, but in that case you need to make the app visible to all sorts of devices, also those which do not support SMS. Starting/running an app on deviced on which it will not run properly, would probably result in lots of angry users and bad/low ratings. Which we do not want. At some stange it seemed that the Market would try to solve this general problem - once and for all: Read about "The 5 steps to future harware happiness": http://android-developers.blogspot.com/2010/10/five-steps-to-future-hardware-happiness.html The Market may have thought that they had solved this issue, but it seems not. Or could there be other ways ? Terry On 22 Des, 13:55, Kostya Vasilyev <kmans...@gmail.com> wrote: > While I don't have a workaround - sorry - but this particular device > is.... quite weird... > > FWIW, this is what I recently ran into, it has to do with WiFi: > > http://wp.me/pSrdQ-lg > > Have you tried calling SmsManager.getDefault() and checking for null? > > -- Kostya > > 22 ÄÅËÁÂÒÑ 2011šÇ. 16:48 ÐÏÌØÚÏ×ÁÔÅÌØ Terry <terb...@gmail.com> ÎÁÐÉÓÁÌ: > > > > > > > > > As no one has responed to this issue yet, I shall try to explain it in > > more detail. > > > In order to DO make an app visible for e.g. the Galaxy Tab 10.1 model > > GT-P7500, one could put the following in the Manifest file: > > > <uses-feature android:name="android.hardware.telephony" > > android:required="false"/> > > > In the app code, one could e.g. use the following too check what > > features are available: > > > PackageManager pm = getPackageManager(); > > boolean hasTelephony = > > pm.hasSystemFeature(PackageManager.FEATURE_TELEPHONY); > > > However, the Galaxy Tab 10.1 model GT-P7500 returns a false on that > > method. > > > The problem would be solved if there existed a constant like > > PackageManager.FEATURE_SMS or similar, but there is no such thing. > > > I think that the Market is still not prepared for the type of products > > like the Galaxy Tab 10.1 model GT-P7500. > > > Any ideas as to how I can solve this? > > > Terry > > > On 21 Des, 12:38, Terry <terb...@gmail.com> wrote: > >> I have tried to ask this question elsewhere, but without getting any > >> answer I can use. So I try it here also. > > >> I have some apps which send and receive SMSs. They are invisible for > >> the new Galaxy Tablets on the Market, and they cannot be dowloaded to > >> them. > > >> WHY? > > >> As e.g. the Galaxy Tablet 10.1, model GT-P7500 does NOT support audio > >> phone calls - but it DOES support sending and receiving SMSs, there > >> should be no problem. In fact, when I download these apps to the GT- > >> P7500 šlocally, they work as expected. > > >> The Market however, sees the permissions to SEND_ and RECEIVE_SMS in > >> the Manifest file of the apps, and interprets this so as to require > >> hardware.telephony from the Galaxy Tabs. Which is does not seem to > >> support. > > >> Any idea how to make a work-around for this problem? > > >> Terry > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
