0

I've recently ported an application that is known to run with uptime of months (DIY Zoning Project) to Android (the accessory driver, the core process and the remote control). And, unfortunately, though techniques to keep running services alive were used (START_STICKY, startForeground()), sometimes the system^H service app just freezes up - until the user initiates an interaction with the service, after which it resumes normal operation. Most problematic is the fact that it is happening intermittently, and mostly after several days of uptime. The remote control works on the emulator for days at a time with no noticeable degradation, so the problem is most probably either in the service or in the accessory driver.

Currently, the system is targeted at API 10, so advanced service scheduling features are not available - that is, if they're related to the problem to begin with.

Now, what is the realistic way to debug and/or profile such a system? Remember, adb is not available for the Android hardware is connected to an ADK accessory.

vt.
  • 436
  • 6
  • 12

1 Answers1

0

Quite a late answer, however, did you try to use Wakelocks? http://developer.android.com/reference/android/os/PowerManager.WakeLock.html Possibly the system just hibernates the processor in some cases and it seems like "freezing up"

AlexN
  • 2,544
  • 16
  • 13
  • I used the word "system" ambiguously - it's not the whole Android OS that is freezing, that's the background app (the service). – vt. Sep 02 '12 at 18:10