|
Post by bansh33 on Mar 30, 2012 13:22:57 GMT -5
Since you asked. Happened again to me today twice, and I fixed it the same way per my previous post. I haven't noticed it happening any other times since the 15th, until today, but now that I know you thought you had fixed it, I'll keep an eye out for it in the future.
|
|
|
Post by whitegauntlet on Mar 30, 2012 19:58:00 GMT -5
Mystery solved!
|
|
|
Post by Cory Trese on Apr 1, 2012 13:16:43 GMT -5
Since you asked. Happened again to me today twice, and I fixed it the same way per my previous post. I haven't noticed it happening any other times since the 15th, until today, but now that I know you thought you had fixed it, I'll keep an eye out for it in the future. I'm pretty sure we fixed it -- I have heard many e-mails since the last update that things are improved. What device are you using?
|
|
|
Post by Cory Trese on Apr 1, 2012 13:25:29 GMT -5
If you are still able to reproduce the issue a LogCat would allow me to fix the problem on your device ... otherwise, I'm just guessing and fixing the bugs people send in "REPORT" or via LogCat
|
|
|
Post by bansh33 on Apr 2, 2012 9:29:59 GMT -5
It's a Droid X. And yes, everything is overall definitely improved, don't get me wrong.
I can't reproduce this behavior at will, but I'll try this LogCat reporting the next time I see it.
Watch it never come up again now...
|
|
|
Post by Cory Trese on Apr 2, 2012 18:41:14 GMT -5
It's a Droid X. And yes, everything is overall definitely improved, don't get me wrong. I can't reproduce this behavior at will, but I'll try this LogCat reporting the next time I see it. Watch it never come up again now... Either way I appreciate your continued efforts helping us figure it out!
|
|