blues wrote: > The thing is I need to share with those. If you're referring to built-in Android applications, in theory you should be using whatever sort of public APIs those packages are supporting (e.g., ContentProvider, a service's AIDL, Intents).
What else are you looking to "share" with these applications? Perhaps there is a way of achieving your business goals without having to try to use somebody's else's private key to sign your apps. > I hope I don't need to build the whole Andorid source and take the > risk of brick the device. Since you can't presently deploy a modified firmware image on the T-Mobile G1, bricking it is the least of your worries. You will need to use hardware that supports flashing new firmware -- hopefully some of the next wave of Android devices will support this. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
