Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Android Build a Simple Android App (retired 2014) Interrogating the App Debugging: Troubleshooting Line by Line

Debugger not working after Incoming Call

Hi, after I call the debugger is not working anymore.

When starting debug, I click F8 two times to get over the first two breaking points and after this our app is running fine. Then I call and the debugger is disconnected... What should I do? I thought the program would continue to run and stop at the onPause() method...


05-16 05:37:52.586: D/MobileDataStateTracker(379): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default 05-16 05:37:52.606: D/MobileDataStateTracker(379): default: Received state=SUSPENDED, old=CONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.606: D/MobileDataStateTracker(379): default: setDetailed state, old =CONNECTED and new state=SUSPENDED 05-16 05:37:52.606: D/ConnectivityService(379): ConnectivityChange for mobile: SUSPENDED/SUSPENDED 05-16 05:37:52.616: D/ConnectivityService(379): tryFailover: set mActiveDefaultNetwork=-1, prevNetType=0 05-16 05:37:52.616: D/ConnectivityService(379): Attempting to switch to wifi 05-16 05:37:52.676: D/MobileDataStateTracker(379): fota: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=fota 05-16 05:37:52.686: D/MobileDataStateTracker(379): fota: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.696: D/NetUtils(379): android_net_utils_resetConnections in env=0xb8618e40 clazz=0x66800001 iface=eth0 mask=0x3 05-16 05:37:52.696: D/ConnectivityService(379): resetConnections(eth0, 3) 05-16 05:37:52.716: D/MobileDataStateTracker(379): ia: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=ia 05-16 05:37:52.726: D/MobileDataStateTracker(379): ia: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.756: D/MobileDataStateTracker(379): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl 05-16 05:37:52.766: D/MobileDataStateTracker(379): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.796: D/MobileDataStateTracker(379): hipri: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=hipri 05-16 05:37:52.826: D/CallNotifier(543): RINGING... (new) 05-16 05:37:52.826: D/CallNotifier(543): onNewRingingConnection(): state = RINGING, conn = { incoming: true state: INCOMING post dial state: NOT_STARTED } 05-16 05:37:52.856: D/CallNotifier(543): SignalInfoTonePlayer.run(toneId = 98)... 05-16 05:37:52.866: D/MobileDataStateTracker(379): hipri: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.866: D/MobileDataStateTracker(379): ims: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=ims 05-16 05:37:52.886: D/MobileDataStateTracker(379): ims: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.906: D/MobileDataStateTracker(379): mms: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=mms 05-16 05:37:52.916: D/MobileDataStateTracker(379): mms: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted 05-16 05:37:52.916: D/MobileDataStateTracker(379): cbs: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=cbs 05-16 05:37:52.926: D/MobileDataStateTracker(379): cbs: Received state=DISCONNECTED, old=DISCONNECTED, reason=2GVoiceCallStarted : E/(): Device disconnected

2 Answers

Ben Jakuben
Ben Jakuben
Treehouse Teacher

There was a recent Forum post about this, but I don't have a good solution yet. My advice in the other post was to simply log information instead of using the debugger for this particular test.

Don't know about this particular case, but I have managed to work with the debugger in other projects. So it's fine for now. Maybe I will soon try it with an incoming call again..