jk-bk-vk wrote: > 2. i will pursue with T-Mobile and return here just to finalize/report > "their soln" so anybody stumbling on this thread will know where/what/ > how.
Particularly if the problem is indeed the provisioning bit getting flipped back, T-Mobile may have a way to re-provision it at the store, for example. > I did want to make sure on one inference I'm making from your > response: that is, if it was a 3rd party market app this wrote these > settings, that app had to have a cert issued from HTC, Google, or T- > mobile? If you know the answer, please elaborate or point me to the > same info in the docs. AFAIK, the database in question can only be accessed by the firmware, or possibly by applications signed with the same signing key that signed the firmware. Firmware is signed by the device manufacturer, so it would be an HTC signing key. Since that stuff isn't part of the public SDK, it's not formally documented there. Most of what we know about those databases come from the emulators, rooted devices, the source, and various posts. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
