1. 首先我们二话不说直接先看报错内容如下:

07-12 08:25:03.572: E/dalvikvm(3602): native fork pid:0 done.
07-12 08:25:03.582: E/dalvikvm(3602): threadid=6: created from interp,name=ReferenceQueueDaemon
07-12 08:25:03.582: E/dalvikvm(3602): threadid=6: calling run(),name=ReferenceQueueDaemon
07-12 08:25:03.582: E/dalvikvm(3602): threadid=7: created from interp,name=FinalizerDaemon
07-12 08:25:03.582: E/dalvikvm(3602): threadid=7: calling run(),name=FinalizerDaemon
07-12 08:25:03.592: E/dalvikvm(3602): threadid=8: created from interp,name=FinalizerWatchdogDaemon
07-12 08:25:03.592: E/dalvikvm(3602): threadid=8: calling run(),name=FinalizerWatchdogDaemon
07-12 08:25:03.642: D/ActivityThread(3602): setTargetHeapUtilization:0.25
07-12 08:25:03.642: D/ActivityThread(3602): setTargetHeapIdealFree:8388608
07-12 08:25:03.642: D/ActivityThread(3602): setTargetHeapConcurrentStart:2097152
07-12 08:25:03.662: I/System.out(3602): Sending WAIT chunk
07-12 08:25:03.662: W/ActivityThread(3602): Application com.himi.clock is waiting for the debugger on port 8100...
07-12 08:25:05.253: I/System.out(3602): Debugger has connected
07-12 08:25:05.253: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:05.454: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:05.654: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:05.854: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:06.054: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:06.254: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:06.455: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:06.655: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:06.855: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:07.055: I/System.out(3602): waiting for debugger to settle...
07-12 08:25:07.256: I/System.out(3602): debugger has settled (1411)
07-12 08:26:55.171: D/ActivityThread(4159): setTargetHeapUtilization:0.25
07-12 08:26:55.171: D/ActivityThread(4159): setTargetHeapIdealFree:8388608
07-12 08:26:55.171: D/ActivityThread(4159): setTargetHeapConcurrentStart:2097152
07-12 08:26:55.391: W/dalvikvm(4159): threadid=1: thread exiting with uncaught exception (group=0x416cd498)
07-12 08:26:55.391: E/AndroidRuntime(4159): FATAL EXCEPTION: main
07-12 08:26:55.391: E/AndroidRuntime(4159): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.himi.clock/com.himi.clock.MainActivity}: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.himi.clock/com.himi.clock.ClockActivity}; have you declared this activity in your AndroidManifest.xml?
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2092)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2117)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread.access$600(ActivityThread.java:140)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1213)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.os.Handler.dispatchMessage(Handler.java:99)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.os.Looper.loop(Looper.java:137)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread.main(ActivityThread.java:4914)
07-12 08:26:55.391: E/AndroidRuntime(4159): at java.lang.reflect.Method.invokeNative(Native Method)
07-12 08:26:55.391: E/AndroidRuntime(4159): at java.lang.reflect.Method.invoke(Method.java:511)
07-12 08:26:55.391: E/AndroidRuntime(4159): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:808)
07-12 08:26:55.391: E/AndroidRuntime(4159): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:575)
07-12 08:26:55.391: E/AndroidRuntime(4159): at dalvik.system.NativeStart.main(Native Method)
07-12 08:26:55.391: E/AndroidRuntime(4159): Caused by: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.himi.clock/com.himi.clock.ClockActivity}; have you declared this activity in your AndroidManifest.xml?
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1541)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread.resolveActivityInfo(ActivityThread.java:1903)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.LocalActivityManager.startActivity(LocalActivityManager.java:285)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.widget.TabHost$IntentContentStrategy.getContentView(TabHost.java:694)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.widget.TabHost.setCurrentTab(TabHost.java:358)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.widget.TabHost.addTab(TabHost.java:236)
07-12 08:26:55.391: E/AndroidRuntime(4159): at com.himi.clock.MainActivity.addOneTab(MainActivity.java:32)
07-12 08:26:55.391: E/AndroidRuntime(4159): at com.himi.clock.MainActivity.onCreate(MainActivity.java:20)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.Activity.performCreate(Activity.java:5086)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
07-12 08:26:55.391: E/AndroidRuntime(4159): at com.lbe.security.service.core.client.b.x.callActivityOnCreate(Unknown Source)
07-12 08:26:55.391: E/AndroidRuntime(4159): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2056)
07-12 08:26:55.391: E/AndroidRuntime(4159): ... 11 more
07-12 08:34:04.128: D/ActivityThread(6074): setTargetHeapUtilization:0.25
07-12 08:34:04.128: D/ActivityThread(6074): setTargetHeapIdealFree:8388608
07-12 08:34:04.128: D/ActivityThread(6074): setTargetHeapConcurrentStart:2097152
07-12 08:34:04.379: W/dalvikvm(6074): threadid=1: thread exiting with uncaught exception (group=0x416cd498)
07-12 08:34:04.389: E/AndroidRuntime(6074): FATAL EXCEPTION: main
07-12 08:34:04.389: E/AndroidRuntime(6074): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.himi.clock/com.himi.clock.MainActivity}: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.himi.clock/com.himi.clock.ClockActivity}; have you declared this activity in your AndroidManifest.xml?
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2092)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2117)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread.access$600(ActivityThread.java:140)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1213)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.os.Handler.dispatchMessage(Handler.java:99)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.os.Looper.loop(Looper.java:137)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread.main(ActivityThread.java:4914)
07-12 08:34:04.389: E/AndroidRuntime(6074): at java.lang.reflect.Method.invokeNative(Native Method)
07-12 08:34:04.389: E/AndroidRuntime(6074): at java.lang.reflect.Method.invoke(Method.java:511)
07-12 08:34:04.389: E/AndroidRuntime(6074): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:808)
07-12 08:34:04.389: E/AndroidRuntime(6074): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:575)
07-12 08:34:04.389: E/AndroidRuntime(6074): at dalvik.system.NativeStart.main(Native Method)
07-12 08:34:04.389: E/AndroidRuntime(6074): Caused by: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.himi.clock/com.himi.clock.ClockActivity}; have you declared this activity in your AndroidManifest.xml?
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1541)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread.resolveActivityInfo(ActivityThread.java:1903)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.LocalActivityManager.startActivity(LocalActivityManager.java:285)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.widget.TabHost$IntentContentStrategy.getContentView(TabHost.java:694)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.widget.TabHost.setCurrentTab(TabHost.java:358)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.widget.TabHost.addTab(TabHost.java:236)
07-12 08:34:04.389: E/AndroidRuntime(6074): at com.himi.clock.MainActivity.addOneTab(MainActivity.java:32)
07-12 08:34:04.389: E/AndroidRuntime(6074): at com.himi.clock.MainActivity.onCreate(MainActivity.java:20)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.Activity.performCreate(Activity.java:5086)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
07-12 08:34:04.389: E/AndroidRuntime(6074): at com.lbe.security.service.core.client.b.x.callActivityOnCreate(Unknown Source)
07-12 08:34:04.389: E/AndroidRuntime(6074): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2056)
07-12 08:34:04.389: E/AndroidRuntime(6074): ... 11 more

仔细阅读红色字体处的报错信息知道:原来是我编写的APP中含有的多个Activity,必须要在AndroidManifest.xml中进行声明,声明如下:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.himi.clock"
android:versionCode="1"
android:versionName="1.0" > <uses-sdk
android:minSdkVersion="15"
android:targetSdkVersion="17" /> <application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name=".MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity> <activity android:name=".ClockActivity" />
<activity android:name=".StopwatchActivity" />
<activity android:name=".TimerActivity" />
</application> </manifest>

再次加载程序到手机里面,发现这时候是可以运行的,没有报错了

那么为什么要这样在AndroidManifest.xml声明注册多个activity???

答:我们知道不同activity代表不同的窗口界面,Android系统只有先注册了不同的activity,系统内部才能对它操作,比如利用intent操作。

Android(java)学习笔记123:Clock app编写报错01的更多相关文章

  1. Android(java)学习笔记63:Clock App 编写报错01

    1. 首先我们二话不说直接先看报错内容如下: 07-12 08:25:03.572: E/dalvikvm(3602): native fork pid:0 done. 07-12 08:25:03. ...

  2. Android(java)学习笔记125:Clock app编写报错02

    1.首先之间看错误: 07-13 10:07:55.354: E/AndroidRuntime(8008): FATAL EXCEPTION: main 07-13 10:07:55.354: E/A ...

  3. Android(java)学习笔记65:Clock App 编写报错02

    1. 首先之间看错误: 07-13 10:07:55.354: E/AndroidRuntime(8008): FATAL EXCEPTION: main 07-13 10:07:55.354: E/ ...

  4. Android 解决Execution failed for task ':app:clean.'报错

    说实话,我还真是没见过比Execution failed for task ':app:clean.'更为恶心,更为不要脸的bug啦,代码没啥问题,一下子行让你爽爽,一下子又不鸟你啦,研究了下,终于找 ...

  5. Android自动化学习笔记:编写MonkeyRunner脚本的几种方式

    ---------------------------------------------------------------------------------------------------- ...

  6. 《Java学习笔记(第8版)》学习指导

    <Java学习笔记(第8版)>学习指导 目录 图书简况 学习指导 第一章 Java平台概论 第二章 从JDK到IDE 第三章 基础语法 第四章 认识对象 第五章 对象封装 第六章 继承与多 ...

  7. Java学习笔记4

    Java学习笔记4 1. JDK.JRE和JVM分别是什么,区别是什么? 答: ①.JDK 是整个Java的核心,包括了Java运行环境.Java工具和Java基础类库. ②.JRE(Java Run ...

  8. 20145316许心远《Java学习笔记(第8版)》课程总结

    20145316许心远<Java学习笔记(第8版)>课程总结 每周读书笔记链接汇总 ▪ 第一周读书笔记 ▪ 第二周读书笔记 ▪ 第三周读书笔记 ▪ 第四周读书笔记 ▪ 第五周读书笔记 ▪ ...

  9. Android:日常学习笔记(6)——探究活动(4)

    Android:日常学习笔记(6)——探究活动(4) 活动的启动模式 standard模式 standard是活动默认的启动模式,在不进行显示定义的情况下,所有活动都会自动使用这种启动模式. stan ...

随机推荐

  1. Application Pool Identities

    Whether you are running your site on your own server or in the cloud, security must be at the top of ...

  2. (Android Studio)ActionBar's Theme/Style [ActionBar主题风格修改]

    (1)默认theme代码如下: 运行结果: 视觉效果:ActionBar为Dark,背景为Light. (2)将theme改为Light: 运行结果: 视觉效果:ActionBar和背景都为Light ...

  3. Selenium 使用方法小结

      基本介绍: Selenium工具专门为WEB应用程序编写的一个验收测试工具. Selenium的核心:browser bot,是用JAVASCRIPT编写的. Selenium工具有4种:Sele ...

  4. opencv2.4.4 背景减除算法收集

    算法集合:https://code.google.com/p/bgslibrary/ 测试:AdaptiveBackgroundLearning算法 #include <iostream> ...

  5. Nullable问题

    在代码中经常遇到int? 其实int?是Nullable<int>的简写方式. int到int?转化 int? i=null; int j=0; i=j; int?到int转化 ; int ...

  6. DateTime和DateTime2

    1.与ANSI和ISO8601标准的一致性不同 datetime不符合该标准,datetime2符合该标准.对于新的应用,尽量使用符合标准的类型. 2.表示范围的不同 datetime:1753-01 ...

  7. HDU-4675 GCD of Sequence 数学

    题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=4675 题意:给一个大小为N的数列a[i],然后一个数M以及一个数K,要你求得一个数列b[i],其中b[ ...

  8. [Objective-c 基础 - 2.11] SEL数据类型

    A.概念 1.SEL类型代表方法 2.每个方法都有一个对应的SEL类型的数据 3.实例对象调用方法 (1)编译器会把类的方法包装成SEL类型的数据, (2)根据SEL数据找到方法地址,缓存此地址 (3 ...

  9. SQL Server 2008数据库创建,备份,还原图解及注意点

    一.新建数据库 步骤1:点击“新建数据库”. 步骤2:输入数据库名称,设置数据库文件保存位置(注意点:最好自己设置数据库文件保存位置,不要采用安装时默认的文件保存位置!),点击“确认”即可完成新库的创 ...

  10. position绝对剧中

    function loginH(){ var loginH = $('.sign-main-bg .sign-main-content'); var h = loginH.height(); logi ...