do you have an howto on how to port to MX31?
Notice: From this point what I'm writing here is neither official
advice from Google, nor legal advice. It's just a personal opinion and
I carry no weight in the balance. It's still up to you to figure out
exactly what you want to do.
As I understand, Google is worried about e.g. these possible situations:
-a case where a rogue manufacturer ship a device with the current SDK
image (that'd be bad for the image of Android, and would put Google in
a delicate position with its alliance partners).
-having people distribute modified (or unmodified) versions of the SDK
(besides potential license issues with the partners, that would cause
headaches in terms of support).
-having people "manually" extract parts of the SDK and redistribute
them individually or re-use them as part of their own projects
(Android-related or not) (that would put Google in a delicate
positions with it alliance partners).
That list is not exhaustive, there are probably other situations that
Google is worried about and would be unhappy about if they happened.
My best guess, personally (and not an advice in any way, shape or
form), is that Google isn't likely to cause you any trouble if you try
to run the SDK on your development board. Similarly, if you
disassembles a class in the SDK (especially if there's a good reason
to believe that the class in question was written by Google and not
one of the alliance partners) for the purpose of debugging you
application, I don't expect that you'd get Google's lawyers knocking
at your door. In case Google asks you do stop, just stop.
Google is not evil, they just need to protect the image of Android,
and they need to protect their partners' intellectual property. Just
don't be stupid.
JBQ
2008/3/30 patrick <cha...@gmail.com>: