|
|
Post by lavendette on Apr 3, 2011 9:33:36 GMT -5
Cory,
I have a Nexus One, with Android 2.3.3, game version 3.6.5
I have downloaded the latest update and since my screen turns black from time to time, only way to get something back on the screen is to hit the back button. But even after that the screen turns black whatever in game button I hit.
The bug does not happen in any particular circumstances. Does not cause a force close.
Help please. Thanks
|
|
|
|
Post by cynik on Apr 3, 2011 11:45:36 GMT -5
I guess this is the bug I already menioned , it still happens.
|
|
|
|
Post by Cory Trese on Apr 3, 2011 15:15:45 GMT -5
yes please tell me more, I am searching for this bug but anything you can tell me that is specific would help a great deal. "From time to time" does not tell me much and the game has many tens of thousands of lines of code  |
|
|
|
Post by skarletlightning on Apr 3, 2011 19:37:55 GMT -5
Actually this happens to me too but i didn't consider ST might be the problem until now. I'm running GingerbreadShedBread on my Eris (Verizon Hero) and I figured it was a bug from the rom.
I'm playing the full version and after playing for a long time, maybe an hour or two there is a 50/50 chance that any action i take (any button presses or pressing back) will result in a black or frozen screen until i back out of whatever screen i'm in with the back button.
As a workaround i got the screen to re-render everything by disabling the forced portrait mode. I tilt the phone and the re-render fixes everything for a few seconds.
After restarting the phone everything works like normal again.
Although there was a single instance of this behavior carried over outside of the game for me, so maybe it is a problem in the iteration of the rom i'm using.
|
|
|
|
Post by cynik on Apr 4, 2011 13:32:41 GMT -5
I think it happens when I finish a battle and tap the screen to stop the automove.
|
|
|
|
Post by Cory Trese on Apr 5, 2011 1:43:36 GMT -5
I saw a bunch of developer and support posts for Tower Raiders 2 GOLD where they have similar issues. They claim bugs in ROMS and Android is the cause =)
|
|
|
|
Post by qhartman on Apr 21, 2011 14:18:26 GMT -5
I am seeing this too on my Nexus One running CM7. It only happens after I play for an extended period. The biggest problem I have is that once this happens the rest of the phone becomes unusable. Sometimes even long-holding the power button to power off or reboot doesn't work and I have to pop the battery.
The behavior feels like some kind of memory leak to me. Once I get my black screen the more I fiddle around with it, the more likely it is that the problem will be "fatal" and I'll have to powercycle to use anything. If I just quit the game immediately, things usually continue to work ok.
I have some experience developing software and bug hunting for OSS projects, so if there is any way I can help find the root of this I'd be happy to.
|
|
|
|
Post by sakai4eva on Apr 21, 2011 21:11:24 GMT -5
I seem to have the same problem as of the latest version. I'm trying to play without the backgrounds (I used to do this without facing the problem).
Will report later this week (busy weekend)
|
|
|
|
Post by Cory Trese on Apr 23, 2011 13:34:59 GMT -5
Thanks for all the information, I am still looking for this bug. I have still been unable to replicate it using stock Sprint Android. I'll keep looking, bound to be in there somewhere.
|
|
|
|
Post by Cory Trese on Apr 23, 2011 13:38:45 GMT -5
Regarding the reports that a memory leak in ST RPG would cause phone instability ...
Without any permissions or special native components, ST RPG should be limited in it's ability to effect the OS. Android times (in the CPU) all UX operations and uses a RT clock to fire off ANR (Application Not Responding) or OOM (Out of Memory) errors -- often called Force Closes.
I'm not saying that under some ROM or buggy (sorry) Android OS implementation it is not possible. If you are seeing it happening, something is causing it and I will continue the exhaustive line by line search.
|
|
|
|
Post by sakai4eva on Apr 26, 2011 23:42:41 GMT -5
Cory, I disabled the star map background it is worked fine. I'm running:
HTC Desire GSM (A8181) with CM7 nightly 47 at the moment. Any ideas?
|
|
|
|
Post by qhartman on Apr 27, 2011 17:48:53 GMT -5
I'll try disabling the star background too and see if that makes any difference. Thanks for your efforts Cory!
As far as my comment about the memory leak, I meant only that it felt like a memory leak, not that it actually was. I appreciate your taking the time to explain the architecture though.
Would it be at all useful to you to see a video of what it looks like when the game does this? I'd be happy to record it for you if so.
|
|
|
|
Post by Cory Trese on Apr 28, 2011 16:02:51 GMT -5
qhartman -- A video would help -- what might help more is a LogCat. There are several applications on the Market that allow you to capture my logging output. sakai4eva -- that is really good information. Perhaps somehow the Android OS is loading the background image over and over and creating the memory leak that qhartman pointed at. I will investigate specifically the star field background image loader and see if i can find a bug.
|
|
|
|
Post by qhartman on Apr 29, 2011 20:21:08 GMT -5
So, I have been playing with the star background off, and it does make it so that it takes longer for the black screen to happen, but it still happens for me. I also got a proper force close today for the first time and told the bug catcher to report it, so you should have a report on it wherever google sends those.
I will look up the information on capturing log information.
|
|
|
|
Post by Cory Trese on Apr 29, 2011 21:51:25 GMT -5
qhartman -- I will read the logs! Did you submit in Free or Elite (the buckets are different in Google error log reader -- I will fix in both versions either way!)
|
|
