Hi, been having an issue when running lots of buzztouch apps on my android phone. When I start the app up it works fine. It goes to the background and I do other things. After a short while, I go back to the app and I get the 'no screen is connected to this' error, even on home menu. It is the same for every menu choice. I go back out of the app, wait a long time and the app eventually is stopped. When I go back into the app, I get the 'app was stopped' message, I start the app back up again and it works fine once more. I understand the app being stopped and needing to restart after some time in the background, but what I can't understand is the app not being able to find its screens. This is happening to multiple apps on the phone. Has anyone else seen this problem?

I see it all the time on Android older devices. Usually fix it with restarting, cleaning and running again. Not certain but I always just put it down to older Android devices. Not a huge Android dev but just bought an old SII and it seemed to stop, was using an older HTC when it was happening.

Just went through this with a client. He was using an app killer, that is the problem.

Hi, brand new phone, no app killer. It is an htc though which is interesting considering MacApple's comment. Could it possibly the mail client - aqua mail which is always running?

Does the log cat say anything? Is your config file up to date?

Log cat just says the screen (by its name) cant be found. The config file is up to date. This is happening to all the buzztouch apps on the phone. If I stop the app and restart it, there's no problem

HTC Gadget: Cool. What version of Android is this thing running?

Hi, it's running android 4.0.3. Deleted all of the other stuff I thought might be messing things up, but it's still happening. It wouldn't be a problem if the app could be forced closed when leaving it, is there any way that I could make it do this? Thanks for your time guys, Liz

This is happening on my Note2 also. If I press the home button and leave my app running in the background, then open it again a few hours later (in this case 6 hours later), everything on the main screen says No screen connected to this, and when you press the menu button to refresh all you get is the Ok- Close option, Refresh all data has disappeared. Fortunately all I have to do is hit the back button to exit out and restart the app to fix it, but it is quite annoying. Could this be a memory leak?

The new Android OS has a built in app killer, sort of. I've found that all my apps that are PDF heavy, all of them, do this on the newest devices. Wish someone had a fix, but I fear it's not so easy. Tim

Thanks, I just got finished reading your thread on the problem too. I don't have any PDFs, but I do have a lot of images I'm loading, plus a lot of screens (it's basically a directory app). Wish there was a way to just close the app after it has been idle for so long.

Yeah, I think that would solve it. Or somehow telling Android which stuff in the background is connected to each other so if part gets killed all of it does. Tim

I finally figured how to close an app after idling too long, in case anyone wants to do this in the future: http://stackoverflow.com/a/14361698 I pasted the first half under this line in BT_activity_base.java: public class BT_activity_base extends Activity implements LocationListener{ The second half goes in the onResume section, paste it below this line: super.onResume(); change ...your move... to finish(); You'll need the following added to the import section: import java.util.Timer; import java.util.TimerTask;