tablet stops responding to touch events, can't debug

Hi,

I’ve tested my app and it works just fine on my galaxy mini.

Now I’m trying on a 10" tablet from dxtreme that I’ve just bought.

The game goes well, but all of a sudden, randomly, it will just stop responding to touch events.  The back key works fine (it brings up the quit menu as I’ve programmed it to, so it’s not like the whole app has crashed), but the new images on the quit menu are also not responding to touch events.  If I press the back button again, it goes back to the game (as expeced), but still nothing responding to touch events.  The only way out of this seems to be to force close the app.  Certainly not something I’d expect an everyday user to do.

So Question 1) - Anyone experienced anything like that before?

So now I’m trying to see if there’s anything coming up on the debug.  But the problem here is that I just can’t get any output from the tablet.  If I plug my galaxy phone in, then straight away i get:

C:\>adb -d logcat Corona:v *:s

  • waiting for device -
    --------- beginning of /dev/log/system
    --------- beginning of /dev/log/main

If I plug the tablet in then I just get:

C:\>adb -d logcat Corona:v *:s

  • waiting for device -

And nothing comes through.  The developer settings are set on the tablet to allow USB debugging.

If I run adb devices, then the tablet does not show up (if i plug my phone in, it does show up).

So Question 2) - Any ideas how to get adb to find my tablet?  I’m on a windows 8 laptop.

thanks!

From what I can work out, this kind of behaviour is caused by a coding error in the app, which, on the simulator, throws an error.  The app, however, continues to run on the device, but exhibits strange behaviour.

Of course, getting access to the device through adb debugging would make it easier to find the error …

From what I can work out, this kind of behaviour is caused by a coding error in the app, which, on the simulator, throws an error.  The app, however, continues to run on the device, but exhibits strange behaviour.

Of course, getting access to the device through adb debugging would make it easier to find the error …