Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Home stops, with forced close #5

Open
GoogleCodeExporter opened this issue Mar 14, 2016 · 3 comments
Open

Open Home stops, with forced close #5

GoogleCodeExporter opened this issue Mar 14, 2016 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Pressing app on Droid, or
2. Pressing widget on Droid, or
3. No apparent reason

What is the expected output? What do you see instead?

I expect normal response, but I get this very frequently:

Sorry!

The application Open Home (process com.betterandroid.openhome2) has stopped
unexpectedly. Please try again.

(Force Close)


What version of the product are you using? On what operating system?

Version 88.  Android 2.0.1 on Motorola Droid

Please provide any additional information below.

Very frustrating and random problem.  Issue shuts down and locks up system 
for about fifteen seconds as it resets multiple times in a day...15-20 
times.  Irritating and annoying.  Can't seem to find a consistent action 
that triggers this.


Original issue reported on code.google.com by [email protected] on 11 Dec 2009 at 12:24

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I might of found a little way to slow down the problem that worked. For me and 
my backflip. It seems when I used process manager to kill running apps it takes 
out the open home in the process unless you kill aapps one by one or set an 
exception for open home in you task killing program (mine was ignore in process 
manager) after I set my exceptions for the foreground programs I powered down 
my phone powered it back up and haven't had a problem since. Personally I don't 
think betterandroid is the issue anymore rather the processes and foreground 
apps that were killed and had problems rebooting afterwards that's 
betterandroid for the outstanding app!

Original comment by [email protected] on 24 Aug 2010 at 5:27

@GoogleCodeExporter
Copy link
Author

Thanks buddy

Original comment by [email protected] on 24 Aug 2010 at 5:30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant