Re: [android-developers] Re: Asus Eee Pad not supported by my app due to manifest settings when nothing is incompatible
On Fri, Aug 19, 2011 at 3:31 AM, Appaholics raghavs...@appaholics.in wrote: The app is Speed Ball Augmented Reality. I am attaching a screenshot of the page you mentioned. The Asus EEE Pad series are not phones. READ_PHONE_STATE *might* imply a uses-feature of android.hardware.telephony. Try adding your own such uses-feature with android:required=false and see if that helps. READ_PHONE_STATE is not on the list of permissions with this effect: http://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions OTOH, it's close enough that it could be a documentation bug. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 Available! -- 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
Re: [android-developers] Re: Asus Eee Pad not supported by my app due to manifest settings when nothing is incompatible
It is not READ_PHONE_STATE. None of my apps can be installed on his EeePad, or on another friends Dell XCD35. Even https://market.android.com/details?id=com.raghavsood.appholicsrss doesn't appear to be compatible and all it needs is the internet permission. Market bug? Thanks On Fri, Aug 19, 2011 at 4:31 PM, Mark Murphy mmur...@commonsware.comwrote: On Fri, Aug 19, 2011 at 3:31 AM, Appaholics raghavs...@appaholics.in wrote: The app is Speed Ball Augmented Reality. I am attaching a screenshot of the page you mentioned. The Asus EEE Pad series are not phones. READ_PHONE_STATE *might* imply a uses-feature of android.hardware.telephony. Try adding your own such uses-feature with android:required=false and see if that helps. READ_PHONE_STATE is not on the list of permissions with this effect: http://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions OTOH, it's close enough that it could be a documentation bug. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 Available! -- 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 -- Raghav Sood CEO/Founder/Owner/Dictator/Tyrant at Appaholics (Basically all titles required to have complete control) http://www.raghavsood.com/ https://market.android.com/developer?pub=Appaholics http://www.appaholics.in/ -- 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
Re: [android-developers] Re: Asus Eee Pad not supported by my app due to manifest settings when nothing is incompatible
On Fri, Aug 19, 2011 at 7:11 AM, Appaholics raghavs...@appaholics.in wrote: It is not READ_PHONE_STATE. None of my apps can be installed on his EeePad, or on another friends Dell XCD35. Even https://market.android.com/details?id=com.raghavsood.appholicsrss doesn't appear to be compatible and all it needs is the internet permission. Market bug? Possibly. If either of your friends have a file manager installed (e.g., Astro), email them an APK. Or, host the APK on a Web server with the proper MIME type settings for APK files. See if they can install it outside of the Market and run your app successfully. If it fails to install or run, then there's something real going on. If it works fine, it might be some Market hiccup. FWIW, I can tell you that: https://market.android.com/details?id=com.raghavsood.appholicsrss is available for all the devices I have tied into the Market, which includes two tablets and five phones. The same is true for Speed Ball AR. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 Available! -- 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
Re: [android-developers] Re: Asus Eee Pad not supported by my app due to manifest settings when nothing is incompatible
I tried that already. All of my apps work perfectly on the Dell. We tried Speed Ball AR on the tablet and it crashed with the same error that occurs on phones sometimes. So it is a market bug right? Thanks On Fri, Aug 19, 2011 at 5:16 PM, Mark Murphy mmur...@commonsware.comwrote: On Fri, Aug 19, 2011 at 7:11 AM, Appaholics raghavs...@appaholics.in wrote: It is not READ_PHONE_STATE. None of my apps can be installed on his EeePad, or on another friends Dell XCD35. Even https://market.android.com/details?id=com.raghavsood.appholicsrss doesn't appear to be compatible and all it needs is the internet permission. Market bug? Possibly. If either of your friends have a file manager installed (e.g., Astro), email them an APK. Or, host the APK on a Web server with the proper MIME type settings for APK files. See if they can install it outside of the Market and run your app successfully. If it fails to install or run, then there's something real going on. If it works fine, it might be some Market hiccup. FWIW, I can tell you that: https://market.android.com/details?id=com.raghavsood.appholicsrss is available for all the devices I have tied into the Market, which includes two tablets and five phones. The same is true for Speed Ball AR. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 Available! -- 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 -- Raghav Sood CEO/Founder/Owner/Dictator/Tyrant at Appaholics (Basically all titles required to have complete control) http://www.raghavsood.com/ https://market.android.com/developer?pub=Appaholics http://www.appaholics.in/ -- 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
Re: [android-developers] Re: Asus Eee Pad not supported by my app due to manifest settings when nothing is incompatible
On Fri, Aug 19, 2011 at 8:15 AM, Appaholics raghavs...@appaholics.in wrote: I tried that already. All of my apps work perfectly on the Dell. We tried Speed Ball AR on the tablet and it crashed with the same error that occurs on phones sometimes. So it is a market bug right? In the absence of any other theories, you are probably correct. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 Available! -- 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
[android-developers] Re: Asus Eee Pad not supported by my app due to manifest settings when nothing is incompatible
It would be helpful if you mentioned the app in question. I checked all your apps and they are all compatible with my Transformer. None of them are compatible with my phone (HTC Desire). The apps apk tab has info used for filtering (api level,supported screens,features,opengl) so maybe something is mentioned there. On Aug 18, 7:31 pm, Appaholics raghavs...@appaholics.in wrote: Hi, I have an app. I recently asked someone to install the app on their Asus Eee Pad. However he told me that his device wasn't supported. I looked at the dev console and found out that it is being excluded due to my manifest settings. However everything my manifest asks for is available. Another market bug or something else? Thanks -- Raghav Sood CEO/Founder/Owner/Dictator/Tyrant at Appaholics (Basically all titles required to have complete control)http://www.raghavsood.com/https://market.android.com/developer?pub=Appaholicshttp://www.appaholics.in/ -- 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
