AndroidPowerSaveDebug总结
2012-03-13 16:55
274 查看
1、Try to reproduce issues复现问题
From hardware aspect:
2、PowerDown analysis, try to narrow down suspicious areas step by step做PowerDown分析,缩小问题出现的范围
From SW aspect:
3、Measure suspicious clock and GPIOs测量可以的时钟和GPIO状态,如主时钟、系统时钟、BT时钟、WIFI时钟请求信号引脚状态
4、If phone work fine from the functionality view, try to find abnormal process and variables setup如果手机工作正常,看看是否有不正常的进程或参数设置,可以利用Debug工具,例如Bugreport
If it is sleep related issue
5、Make sure if phone get into deep sleep mode and if the early suspend and suspend process is well done. We can check the flag pin that indicate CPU status, also can find a breakpoint function that can be used to check if the phone entered sleep mode, such
as Take_A_Nap, it should be called one time.确定手机是否进入sleep状态,可以通过测量CPU状态指示的GPIO脚,或者用JTAG把标识CPU 进入sleep状态的函数设为断点,检查断点被调情况。确定手机是否正常的完成了suspend的过程,可以通过在链表中添加打印信息,显示suspend的设备名称来确定没有正常suspend的设备,详细方法参考我的wiki
6、Check related power supply voltage检查相应的供电管脚
7、Find clock request status and process unexpected, but not timer and FS_Writer检查时钟状态和异常进程,而不是定时器和文件系统操作
8、If confirmed CPU is in sleep mode, then it is time to move focus on HW side, such as misconfiguration, wrong HW settings, Current leakage and so on.如果已经去顶CPU进入了睡眠模式,那就是硬件的问题了,比如系统配置、错误的硬件设置和漏电流
9、If CPU is not in sleep mode , it is should be SW side problem. Refer to item 3如果CPU没进入睡眠,接下来应改调查软件问题,参考3
10、Dump clock/GPIO/ status, check wakelock Dump时钟和GPIO管脚状态,检查wakelock
From hardware aspect:
2、PowerDown analysis, try to narrow down suspicious areas step by step做PowerDown分析,缩小问题出现的范围
From SW aspect:
3、Measure suspicious clock and GPIOs测量可以的时钟和GPIO状态,如主时钟、系统时钟、BT时钟、WIFI时钟请求信号引脚状态
4、If phone work fine from the functionality view, try to find abnormal process and variables setup如果手机工作正常,看看是否有不正常的进程或参数设置,可以利用Debug工具,例如Bugreport
If it is sleep related issue
5、Make sure if phone get into deep sleep mode and if the early suspend and suspend process is well done. We can check the flag pin that indicate CPU status, also can find a breakpoint function that can be used to check if the phone entered sleep mode, such
as Take_A_Nap, it should be called one time.确定手机是否进入sleep状态,可以通过测量CPU状态指示的GPIO脚,或者用JTAG把标识CPU 进入sleep状态的函数设为断点,检查断点被调情况。确定手机是否正常的完成了suspend的过程,可以通过在链表中添加打印信息,显示suspend的设备名称来确定没有正常suspend的设备,详细方法参考我的wiki
6、Check related power supply voltage检查相应的供电管脚
7、Find clock request status and process unexpected, but not timer and FS_Writer检查时钟状态和异常进程,而不是定时器和文件系统操作
8、If confirmed CPU is in sleep mode, then it is time to move focus on HW side, such as misconfiguration, wrong HW settings, Current leakage and so on.如果已经去顶CPU进入了睡眠模式,那就是硬件的问题了,比如系统配置、错误的硬件设置和漏电流
9、If CPU is not in sleep mode , it is should be SW side problem. Refer to item 3如果CPU没进入睡眠,接下来应改调查软件问题,参考3
10、Dump clock/GPIO/ status, check wakelock Dump时钟和GPIO管脚状态,检查wakelock
相关文章推荐
- Android调试、debug技巧总结
- android 存储联系人(save contact) 总结
- android powerkey触发小应用总结
- powersave debug
- android原生widget 电量控制(PowerSave)设计浅析
- Android Debug Bridge(ADB)学习总结
- Android Studio代码自动提示无效(not available in Power Save mode)
- Android wifi powersave
- android.cts.jank.ui.CtsDeviceJankUi--testScrolling失败原因总结和debug方法介绍
- android 存储联系人(save contact) 总结
- Android Studio代码自动提示无效(not available in Power Save mode)
- Android Studio代码自动提示无效(not available in Power Save mode)
- [03/31/2013][Android]Power off Charge 总结
- android-基础知识:android调试总结(Log日志输出, Debug, 单元测试)
- Android-Canvas.save() Canvas.restore() 总结
- Android Studio异常"The plugin org.jetbrains.android failed to save settings and has been disabled"处理总结
- android中关于canvas的rotate,save和restore的总结
- android中BuildConfig.DEBUG的使用
- 【Android New Features】—— 关于ADT 17的BuildConfig.DEBUG
- Android 动画总结-补间动画