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. RERUN e-lifestyle MetroTV ttg programmer Gadget HARI INIpk. 11.05 WIB

Lagi ngantor kang ... :p
Sent from my BlackBerrypowered by Sinyal Kuat INDOSAT

-----Original Message-----
From: "Onno W. Purbo" <>
Date: Mon, 24 Jan 2011 07:16:21 
To: <>
Subject: [id-android] RERUN e-lifestyle MetroTV ttg programmer Gadget HARI INI
 pk. 11.05 WIB

RERUN e-lifestyle MetroTV ttg programmer Gadget
HARI INI senin 24/01/2011 pk. 11.05 WIB
isinya ANDROID vs BB :)))



2. Exceptions in user libraries

Hi there,

I am developing for Android from Eclipse running on the Windows OS. As
I have multiple projects that share certain parts of code, I have made
said code into an Android library, and then reference said libraries
to the projects. I am doing this by using the 'Library' panel under
the 'Android' section (when you right click -> Properties on a
project). The library projects have 'Is Library' ticked, and the main
projects add the library projects.

In terms of being able to build and run, this appears to work. However
I have run into two problems, one more serious than the other:

1. When I make a change to the source for a library, when I ask
Eclipse to run/debug it doesn't pick up the change. I have to instead
refresh (F5) the main project - this appears to correctly pull in
dependencies (incidentally, I also have to do this if I make a change
to native code using the NDK and rebuild the resulting .so file). Is
there a way to force these sorts of dependency checks to automatically
be taken into consideration when I debug run? I have got reasonably
used to refreshing when running, but it is somewhat easy to loose
track of what source file you are editing, and forgetting it is one in
a library that means a refresh is required. It can result in wasted
debug sessions when you are running unexpected code!

2. My more serious problem is: when an unhandled exception is thrown
in library code, it doesn't tell me about the exception in an easy
way. For example, today I had an exception raised, and it reported to
me that it was coming from the method, from - so I went through the various hoops for getting
the source code for Android onto my PC, so I could view, and saw the exception was coming from
'guardedRun', which in turn was calling 'onDrawFrame', which in turn
called out to my native render + update function (using the NDK),
which in turn called back into my Java code to load some music, and
*that* code then went onto attempt to access an array with an invalid
index. None of this was shown in the callstack (only
appeared there), instead I had to make my own version of GLSurfaceView
that had some try/catch statements that caught the exception, and gave
me a callstack of where the problem lies by using e.printStackTrace().
Once I had the callstack, I was able to fix up the offending code. I
don't remember having this problem before I made my code into a
library - I thought previously exceptions were getting caught much
earlier on. I am simply not remembering correctly? Or is there some
limitation when using libraries? If I am not remembering correctly,
clearly I just need to wrap my Java code that is being called from my
native code with try/catch/print exception blocks so I can avoid this
problem again.

I look forward to your responses,



3. samsung tab

4. custom widgets in animation

5. RERUN e-lifestyle MetroTV ttg programmer Gadget HARI INI pk. 11.05 WIB

6. [WTAsk] soal rooting HH.

7. WTNgelamun : Gadget Impian