Upgrading to 1.5

by radiolistener » Sat, 06 Jun 2009 21:56:42 GMT

Sponsored Links
 Hi All,

My phone was updated to 1.5 this week.  I have been waiting to update
my development environment, until the phone was upgraded.

The ide started out smoothly, I even updated my new Colorthon program
library and posted the compiled version on the marketplace.

Next I decided to upgrade Radio's Exercise Buddy.  Got a signature
error.  I worked around it by giving it a new namespace, but this is
far from ideal, because now my users will have to use a migration
tool, to bring their data over.  Is there a better way to do this?
Also, If I change the namespace, can I still have my paid users get a
free upgrade?

Any insights would be appreciated.  Also, I know that many developer's
have upgraded earlier, but I wanted to wait until I had the updated
phone.  If this is a common problem, please refer me to the thread to

John aka Radiolistener
RadiolistenersElectricEasel.com, Inc.


Upgrading to 1.5

by Marco Nelissen » Sat, 06 Jun 2009 23:13:04 GMT

 On Sat, Jun 6, 2009 at 6:56 AM, radiolistener

A signature error normally means that you signed your update with a
different key than the previous version. It doesn't have anything to do with
your phone being updated to 1.5. You should sign your updates with the same


Sponsored Links

Upgrading to 1.5

by radiolistener » Sun, 07 Jun 2009 03:20:01 GMT

 This is the exact error:

[2009-06-06 15:13:29 - REBC] Automatic Target Mode: using device
[2009-06-06 15:13:29 - REBC] Uploading REBC.apk onto device
[2009-06-06 15:13:30 - REBC] Installing REBC.apk...
[2009-06-06 15:13:31 - REBC] Application already exists. Attempting to
re-install instead...
[2009-06-06 15:13:33 - REBC] Re-installation failed due to different
application signatures.
[2009-06-06 15:13:33 - REBC] You must perform a full uninstall of the
application. WARNING: This will remove the application data!
[2009-06-06 15:13:33 - REBC] Please execute 'adb uninstall
REBC.exercise' in a shell.
[2009-06-06 15:13:33 - REBC] Launch canceled!

And it's more than the phone I updated to 1.5, this morning I updated
my development environment.


Upgrading to 1.5

by Marco Nelissen » Sun, 07 Jun 2009 04:45:33 GMT

 The error message confirms what I said earlier: you signed your application
with a different key, and this is why updating the app fails.

On Sat, Jun 6, 2009 at 12:19 PM, radiolistener


Upgrading to 1.5

by radiolistener » Sun, 07 Jun 2009 06:24:18 GMT

 Maybe I'm just not getting it, but I haven't signed this one yet.  For
Colorthon I used the automatic signing option and uses the export
signed option, to utilize the automatic signing and everything worked

For REE, I am just running it in the ide, any signing is just the
default debug, is it somehow using the key from Colorthon?  I doubt
it, because it didn't ask for a password or anything.  Can the default
debug key be changed? And if so, how do I change it back?



Upgrading to 1.5

by radiolistener » Sun, 07 Jun 2009 07:47:37 GMT

  found my default debug keystore   C:\Users\'TheUser'\.android
\debug.keystore It is brand new as of today. I also found where the
last debug.key was located c:\users\'TheUser'\local\android. Did a
little switcheroo. Then adjusted the manifest, and voila, lift-off.

Many Thanks for your help, you had the answer all along, I just didn't
understand it at First. I'll be putting in today's exercises into the
program, if all works well, I'll try and release the Android 1.5
version tonight.

Would have thought this was a problem others have encountered. They
changed the placement of this file in Vista. It's probably mentioned

Thanks Again,

John aka Radiolistener

On Jun 6, 6:24pm, radiolistener <radioliste...@optonline.net> wrote:

Other Threads

1. Gallery missing attribute / method


What is the equivalent for these in SDK 0.9?

android:drawSelectorOnTop or setDrawSelectorOnTop(boolean)

android:spinnerSelector or setSelectorSkin(Drawable)


2. v0.9 beta - SystemClock.setCurrentTimeMillis() failed

I am using v0.9 beta SDK, got the following warning when I call

WARN/SystemClock(516): Unable to open alarm driver: Permission denied

Does anyone know which permission should be specified?

3. Inconsistent usage of setResult(..) Intent.

4. how can i solve

5. Errors when trying to build an example from a guide...how can I resolve.

6. Android violating the LGPL

7. WebView loadUrl and SD card