It is easy to debug Android applications as most of them launch an activity and keeping breakpoint is all it takes. How to debug a GDK based google glass app as the service is triggered on voice and does not explictly launch an activity on install?
相关问题
- How can I create this custom Bottom Navigation on
- Bottom Navigation View gets Shrink Down
- How to make that the snackbar action button be sho
- Listening to outgoing sms not working android
- How to create Circular view on android wear?
相关文章
- android开发 怎么把图片放入drawable的文件夹下
- android上如何获取/storage/emulated/下的文件列表
- androidStudio有个箭头不认识
- SQLite不能创建表
- Windows - Android SDK manager not listing any plat
- Animate Recycler View grid when number of columns
- Why is the app closing suddenly without showing an
- Android OverlayItem.setMarker(): Change the marker
Same way any Android service is debugged. Just add the below line anywhere in the code and any breakpoint in the code after this can be used to stop the run.
Thanks to this - http://www.helloandroid.com/tutorials/how-debug-service
I tried to debug a sample GDK app with this option, but it doesn't help. I'm not sure if this option helped anyone to debug the GDK app. However the log.d function logs the message in console window. My expectation is to debug the flow to intercept variable values and modify during the flow.
* Updated * After activating DDMS perspective, I got the debug focus to code window to do the step by step walk-thru. However the glass goes to the standby mode very quickly and it blocks debugging activity. Trying to find the best practice. Will keep this thread posted. Stay tuned!