michbeck
michbeck

Reputation: 194

Tab widget example not running

I'm trying to reproduce the tabwidget example (http://developer.android.com/resources/tutorials/views/hello-tabwidget.html). I'm not really sure what's the problem, I got no errors while compiling, but i cannot see the application on the emulators screen.

It would be excellent if maybe anyone could have a look at my classes and tell me what's my mistake? I've packed my project here: http://etanto.com/TabTest.zip

here's the console dump while the run:

[2010-06-10 09:18:34 - TabTest] Launching a new emulator with Virtual Device 'Virtual1'
[2010-06-10 09:18:35 - TabTest] New emulator found: emulator-5554
[2010-06-10 09:18:35 - TabTest] Waiting for HOME ('android.process.acore') to be launched...
[2010-06-10 09:19:05 - TabTest] WARNING: Application does not specify an API level requirement!
[2010-06-10 09:19:05 - TabTest] Device API version is 8 (Android 2.2)
[2010-06-10 09:19:05 - TabTest] HOME is up on device 'emulator-5554'
[2010-06-10 09:19:05 - TabTest] Uploading TabTest.apk onto device 'emulator-5554'
[2010-06-10 09:19:05 - TabTest] Installing TabTest.apk...
[2010-06-10 09:19:22 - TabTest] Success!
[2010-06-10 09:19:22 - TabTest] \TabTest\bin\TabTest.apk installed on device
[2010-06-10 09:19:22 - TabTest] Done!

Upvotes: 1

Views: 1597

Answers (1)

poeschlorn
poeschlorn

Reputation: 12440

try to add the following to your manifest:

<activity ......>
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
</activity>

This will declare the activity as "main" activity if app is started...

Otherwise you could try to specify an api level in your manifest.

I didn't read all the code, but if there are no compilation problems, the activity should be started anyway(if manifest is ok)...

Upvotes: 2

Related Questions