Downgrading 2 app to 1.5

by MartinM » Thu, 22 Apr 2010 22:36:23 GMT

Sponsored Links
 I've a (non-google maps) app that I want to install on a 1.5 phone.
However, it was originally built for 2 (can't remember if it was 2.0
or 2.1), and when I set the target as 1.5 I get some errors:

1. 'invalid resource directory name' - the directory exists and is
unchanged, the contents are listed in the Eclipse browser. Errors
shown on re/drawable-hdpi, re/drawable-ldpi and re/drawable-mdpi

2. 'R cannot be resolved'. This appears to be the fact that is
no longer present. I've fixed this by importing android.R (not sure
why it needed to be done again), but now

setContentView(R.layout.main); cannot be resolved.

I see that I still don't have an

A bit confused here :)


Other Threads

1. Eclipse debugger is skipping instructions!

I am debugging an app that tests an API I wrote. There is a section of
code that simply reads a DB cursor like this:

Cursor row = mDatabase.query("properties", null, where, null, null,
null, null, null);
if( row != null )
   if( row.moveToFirst() ) // A
      int n=row.getColumnIndexOrThrow("value");
      value = row.getString( n ); // B

The de{*filter*} steps through line at a time until it gets to the line
commented // A. The next line the de{*filter*} gets to is the line
commented // B!!! It completely skips over the "int n =..." line. Even
stranger, at that point the int n is not listed as being in scope at
all. Basically, as soon as it executes any method on row the de{*filter*}

I also have to step twice over each clause in any conditional. So
this: if( a==2 || b==4 ) would require four "step over" actions to get
past it. Very strange.

I re-installed the latest version of eclipse with the latest ADB and
the latest emulator. It still happens. This is running against Android
2.0, which is a requirement. I am on Windows 7 64 bit with a 32 bit
installation of eclipse.

Has anyone seen this strange de{*filter*} behavior? What should I try to



2. Incredible vs Droid X vs Evo 4G vs Nexus One vs Galaxy S

Vote Ncus .... (Barang langka)


3. Large jars in Android

4. Android on devices without batteries - unlock screen problem

5. Is it possible to create a custom system image for any currently released commercial hardware phone/netbooks?

6. CursorAdapter Problem

7. Viewable Address Field for People Contact truncated