Using SDK 1.5 to build 1.1 apps?

by jsdf » Mon, 27 Apr 2009 22:22:10 GMT

Sponsored Links
 Hi all,
I've been playing with the 1.5 SDK recently, and understand it
contains both 1.1 and 1.5 within.

The release notes contain this dire warning:
"Note: This is an early look SDK only. The tools and documentation are
not complete. The API reference documentation for the early look SDK
is provided only in the downloadable SDK package documentation for
this early look release is not available at .
To access the API reference for the early look SDK, see the
documentation in your SDK's docs/reference/ directory. "
( )

However, does this warning apply to building 1.1 applications using
this preview release for the Market?
Or, should I step back to the Android 1.1 SDK Release 1 to build my
apps for release?

(This question is triggered by my frustration in not being able to
upload a new version of one of my apps that use Maps as of this
weekend, whereby I constantly receive "The server could not process
your apk. Try again.", as described in this thread: 
, and I am somewhat scrounging for possible solutions now.)


Other Threads

1. Significant Fragment bug? onInflate() not called at the right time on a restart

I created a bug report for this a couple of days ago, but it doesn't
seem to have received any attention:

To reproduce the problem, add the following callback override to the
TitlesFragment class in under the ApiDemos project
in samples for Honeycomb Preview:

        public void onInflate(AttributeSet attrs, Bundle
savedInstanceState) {
                Bundle args = new Bundle();
                for(int i=0; i<attrs.getAttributeCount(); i++) {
                Log.v("14796", "    " + attrs.getAttributeName(i) +
                                " = " + attrs.getAttributeValue(i));
                super.onInflate(attrs, savedInstanceState);

This is doing what the the documentation says you should do. That is,
take attributes passed in and save them in the arguments bundle on the
fragment instance. However, if you launch this activity then rotate
the screen, the activity crashes with an IllegalStateException. And it
does that because onInflate() gets called way too late when Android is
rebuilding the activity and its fragments. If the layout for the other
orientation is different that the previous layout, you'll have no way
to use any of the attributes in onCreateView() for the fragment,
because onInflate() isn't being called until later.

I haven't come up with a workaround either. The fragment can't even
see the activity until onAttach(), and you can't set the arguments
bundle once onAttach() has been called.

The sample activities so far haven't tried to utilize this feature, so
perhaps it won't affect most people. But for those who need or want
it, it doesn't seem to work.


2. MarkerManager for Android

Hi all,

I have +120 markers to display on google maps.
I wish to display only a few depending of the zoom. In Javascript,
MarkerManager can manage this.
But I can't use it for my android application.

Is there another way to do this ?


3. About activity and menus for Android games

4. Antisipasilah!!! Android untuk telepon rumah

5. wifi in android

6. android porting

7. zoom