java SE and the emulator

by kellogs » Sat, 21 Jun 2008 01:20:57 GMT


Sponsored Links
 Hi,

I am the happy owner of a desktop computer running on win xp, jdk
1.6.0.4 and android sdk m5.rc14. On this computer I have managed to
develop an application for andoid under eclipse IDE using ADT. I do
not know precisely what version of ADt is installed on my dektop
computer. All went well, my application ran flowlessly :)

Now the time has come for presenting my work .. for that, I shall need
a laptop. So I have acquired one, same XP, jdk 1.6.0.6, same android
sdk m5.rc14, same eclipse 3.3.1.1, some newer version of the ADT (of
course, if there was another release in arround 3 months), and,
surpirse: my project does not start appropiately. emulator launches
ok, but just after my first activity gets started, I get a big loooong
screen just oon the emulator saying something like:

"unresolved compilation problems: Syntax error, annotations aare only
available if source level is 5.0.
The type Map is not generic; it cannot be parametrized with arguments
<String, String>
Syyntax error, parametrized types are only available if source level
is 5.0"
etc etc...

Sooo, help please !

thank you,
kellogs

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



java SE and the emulator

by kellogs » Thu, 26 Jun 2008 23:54:04 GMT


 No more help needed. Issue solved

kellogs




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


Sponsored Links


Other Threads

1. Using Instrumentation during ActivityInstrumentationTestCase

I'm running my ActivityInstrumentationTestCase.  it runs in the
emulator.  I can watch the Intents triggering Activities in 'adb
logcat".  I see in the logcat output that the Activity was displayed:

I/ActivityManager(   50): Displayed activity my.manifest.packate/
my.package.CountingActivity: 556 ms

so I believe I've sent the keys to press the button that fire the
startActivity.  What I'm not seeing is the monitor that I've added
through the test.  My waitForMonitorWithTimeout always times out.
Here is the part of the unit test that sets up the monitor, triggers
it, then waits:

                ActivityResult result = new ActivityResult(1, null);
                String activityClassName = "my.manifest.packate/
my.package.CountingActivity";
                ActivityMonitor monitor = getInstrumentation().addMonitor
(activityClassName, result, true);

                sendKeys(KeyEvent.KEYCODE_ENTER);

                System.out.println("wait for timeout");
                Activity actualActivity = getInstrumentation
().waitForMonitorWithTimeout(monitor, 20000);
                System.out.println("after timeout");
                assertNotNull("non null activity means the monitor was invoked",
actualActivity);

The activity implementation "CountingActivity" has a sysout, it always
prints in logcat after "wait for timeout" and before "after timeout",
but the actualActivity is always null.  I show here using the full
<package>/<full-class-name> for the activityClassName.  I began with
out the "<package>/" and used just the classname, but that had the
same effect -- never triggering the monitor.  Further evidence that
I'm not registering the monitor correctly is that that addMonitor call
with true at the end should skip the actual Activity and return my
canned result.

Has anyone successfully tested with this process?
--~--~---------~--~----~------------~-------~--~----~

2. Just got a G1 HELP

I put my old SIM card into my g1 phone and its saying that there is a
problem, after trying to sign into the google network...I had a
previous phone and this one was orderd off of T-MOBILE.COM under my
account! I have tried it all...please help!

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

3. No Future Support for JNI

4. phone feature abstractions to PC

5. What's the usage of the card when register android market account

6. Android Framework

7. GMail Client Source