I googled for this failure and found out that this error occurs if the application is just taking too long to handle for example an onClick event. The Framework has a timeout for UI events and will show the "frozen" dialog if processing takes too long.

I tested the app by increasing the number of sites to 1000 and couldn't reproduce it. Then I followed the stack trace and found out that it must be occurred while loading sparklines. Therefore it is the combination of many sites and enabled sparklines beside each site. I still was not able to reproduce this error with enabled sparklines and 1000 sites. But I can imagine that this combination ends in a frozen app if the device has not enough free memory or for example a lot of apps running in parallel. However, we can't prevent this error as the framework renders each row containing the sparkline image and it works for me (using Titanium 1.5 nightly build, maybe they optimized something).

As no other user had this failure and this failure only occurred once, I would close this issue. Do you agree? I think it is better to write an entry about this possible issue in future Piwik Mobile FAQ.

considering this error showed up very rarely, it sounds good!

I just looked up and saw that the error Exception class java.lang.NullPointerException

• Source method TextView.onTouchEvent()

was reported 14 times. Probably just the same time of errors, that we can't really control and fix?

Exact, we can't really control and fix this. But Appcelerator is currently fixing a lots of bugs. Titanium 1.5 will be mainly a maintenance release for Android (regarding to stability, bugfixes, performance, memory leaks, ...). I look forward to this release and think that the next release will reduce the number of errors.