What happened to the HOME button in cupcake

by Mattaku Betsujin » Sat, 11 Apr 2009 05:53:43 GMT


Sponsored Links
 This is a sign to me that the HTC Magic won't come out for quite a while. I
just hope not too many people are holding off buying the G1 to wait for the
Magic.








--~--~---------~--~----~------------~-------~--~----~



What happened to the HOME button in cupcake

by Disconnect » Sat, 11 Apr 2009 06:15:33 GMT


 ..so where is the SDK that the magic google team (or whomever else, don't
get picky here) is working with?






--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


What happened to the HOME button in cupcake

by Dianne Hackborn » Sat, 11 Apr 2009 07:12:55 GMT


 




We aren't working with an SDK, we develop in the platform tree.

-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

--~--~---------~--~----~------------~-------~--~----~



What happened to the HOME button in cupcake

by David Turner » Sat, 11 Apr 2009 07:29:01 GMT


 



Right there in the public sources. The problem is really in packaging;
building a proper SDK package is tricky at the moment
and it's easy to generate one that doesn't work 100% as it should (as
experienced with the recent SD Card auto-mounting
problem which was due to a missing configuration file).

We're working on fixing this and providing detailed instructions on how to
build an SDK. However, one should expect this
kind of problem episodically when trying to build its own SDK.

And as Dianne said, most of the team works in the source tree directly,
which generates images that are a bit different than the
ones packaged for a SDK (this is also true of the "generic" product in the
open-source tree); that's why releasing an official
SDK takes time by the way, we need to ensure that everything works as it
should, even though the rest of the team often
makes modifications that work on "normal" build products, but not on the SDK
system images themselves for really corny
reasons.






--~--~---------~--~----~------------~-------~--~----~



What happened to the HOME button in cupcake

by Mattaku Betsujin » Sat, 11 Apr 2009 08:52:27 GMT


  built from GIT cupcake source as well as the HOME button in the emulator
still doesn't do anything.

I understand that the SDK, especially Windows-based one, may be lacking, but
is the HOME button in cupcake supposed to work the same way as in 1.0?

Thanks

On Fri, Apr 10, 2009 at 4:28 PM, David Turner <di...@android.com> wrote:


--~--~---------~--~----~------------~-------~--~----~



What happened to the HOME button in cupcake

by Romain Guy » Sat, 11 Apr 2009 09:00:31 GMT


 t is, this problem is just due to the fact that the SDK thinks the
system is not provisioned. The SDK usually relies on a special apk to
do this automatically and I don't know why it doesn't happen for you.

On Fri, Apr 10, 2009 at 5:52 PM, Mattaku Betsujin
<mattaku.betsu...@gmail.com> wrote:



--
Romain Guy
Android framework engineer
romain...@android.com

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

--~--~---------~--~----~------------~-------~--~----~



What happened to the HOME button in cupcake

by David Turner » Sat, 11 Apr 2009 15:34:34 GMT


 n Sat, Apr 11, 2009 at 2:52 AM, Mattaku Betsujin <
mattaku.betsu...@gmail.com> wrote:


I don't know exactly what you did, but I'm sure that the "cupcake" branch on
the open-source tree is not working properly. You need to build from the
"master" branch instead at the moment to get something working.

For the record, the cupcake changes have been integrated into the master
branch already.



Yes, HOME *should* just work. It's probably another configuration problem,
where a file is missing from the generated system image for some odd reason;
certainly not a deliberate change.



--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. " How to Import Android Package Default Projects to Eclipse "

That discussion should really move to android-platform instead of
android-developer.

Everything in the "frameworks" and "packages" sub-folders is designed
to be built using the source makefiles -- these may use the internal
APIs and are *not* designed to be built using the SDK.

You can use Eclipse to edit the Java files but you cannot build then
against the SDK.

Look in the platform group archives: some people have explained how to
configure Eclipse to do platform development.

R/




--~--~---------~--~----~------------~-------~--~----~

2. URGENT!!!!! Can't update apps in android market!!!

API levels are integers (they notion of "API level" was very
unfortunately badly named in the manifest).

1.0 implemented API level 1, 1.1 implemented API level 2, and the same
relationship exists between 1.5 and API level 3.

JBQ








-- 
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

--~--~---------~--~----~------------~-------~--~----~

3. Installation unsuccessful - Package file was not signed correctly

4. Eclipse + cupcake + referenced projects in build path = VerifyError

5. AutoCompleteTextView in 1.5 SDK

6. How does a RemoteView get drawn

7. sdcard in avd SDK 1.5