> From what you are saying, an Android-market app referring to > com.android.internal.R would work okay on another OEMs device that has > some new additional private resources inside its framework?
Only if the app is recompiled for that build. > In other words, you are saying that binary compatibility of apks are > guaranteed across devices, even if one of the frameworks has new > private resources. Correct? No, binary compatibility is guaranteed only for public resources. Either: - You are writing an OEM app meant only for your device or other OEM, and you use private resources (which means the app has to be compiled for each build it's meant to run on) - You keep using the current public resources - You put the resources in your app - You submit patches to add public resources to the Android platform -- Romain Guy Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
