Hi again, some more info concering the case of Milestones not showing protected apps from one of our customers here in Germany ...
[SNIP] Dear Justin, I am one of the affected milestone users and I am far from alone. At least all of the milestones sold by amazon, Germany are affected! Milestones branded by Vodafone or O2, Germany are working perfectly. I know it is unusual for the USA but in Europe it is quite common to buy phones WITHOUT an carrier-contract. Those phones are NOT branded by Vodafone or others and they are simlock-free! Exactly those phones have no access to copy protected apps in the market. Our guess at the moment is that google missed those configuration and handles them as illegal (rootet) phones... are we right with this assumption??? But our phones are 110% legal with plain Motorola configuration right from the factory! It is not only that we can not buy or download any new copy protected apps. User who bought such an app on another Adnroid phone and now got themselves a new Milestone can not access their legally bought apps anymore!!! Google needs to react here really quick. We are honest users and your loyal fanbase! All of the affected phones have the following ORIGINAL Motorola setup: Model: Milestone Firmware-Version: 2.0 Firmware-Configuration-Version: GAS_EMEA_USASHLS00RTDACH_P001 Baseband-Version: 3GDMEPU91A_U_91.08.0DP Baseband-Configuration-Version: UCASHLSEMEAB1B803F.0R Kernel-Version: 2.6.29-omap1 a21...@ca25rhe53 #1 Build-Number: SHOLS_U2_01.03.1.125764182 PLEASE HELP US! best regards Christian [/SNIP] On 2 Dez., 05:40, rflexor <rfle...@googlemail.com> wrote: > Hi, > > thanks for participating in this thread, Justin! > > I have gathered that here in Germany we have Milestones sold by > Vodafone for their network and free Milestones usable in any network. > Currently, from what I read in the forums, those from Vodafone are > able to see copy protected apps, others are not. If you need more > details from one of the phones not able to see protected apps, let me > know. > > Ralf > > On 2 Dez., 00:20, blindfold <seeingwithso...@gmail.com> wrote: > > > Argh, thanks! I now found the small print in the documentation that > > implies this, and have added <uses-feature > > android:name="android.hardware.camera" /> to my manifest such that as > > of now my app should be visible to HTC Tattoo users (I have no Tattoo > > myself). My app sometimes uses autofocus but also works without, so > > autofocus support by the phone is not required by my app and was > > apparently inadvertently implied by the new Android defaults. It would > > be nice to have some sort of Market visibility test for a range of > > popular devices, because it is easy to overlook such details and hard > > to test for without buying tons of devices... > > > On Dec 1, 10:32 pm, "Justin (Google Employee)" <j...@google.com> > > wrote: > > > > To return to the original topic of apps with the CAMERA permission not > > > showing to Tattoo users, this is because you need to specify > > > > <uses-feature android:name="android.hardware.camera" /> > > > > in your manifest as > > > perhttp://developer.android.com/guide/topics/manifest/uses-feature-eleme... > > > . Tattoo does not include autofocus unlike all previous Android > > > devices. For this reason, you need to opt-in to being shown to devices > > > without autofocus. Likewise you can use uses-feature to specify that > > > you require autofocus. > > -- 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
