eldoSlomo / nethack-android

Automatically exported from code.google.com/p/nethack-android
0 stars 0 forks source link

NetHack doesn't terminate on G1 #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Using NetHack on a G1.

On 'S' (save), the game is saved, you get 'Be seeing you...', but the
'window' doesn't close.  If you hit 'Home' and the restart NetHack, you get
the same window with the 'Be seeing you...'.  The same is true if you try
to quit after hitting 'q' to the 'generate your character for you' question.

Original issue reported on code.google.com by jdhedden on 15 Oct 2009 at 4:44

GoogleCodeExporter commented 9 years ago
This problem really seems to mess up the phone.  After killing NetHack with 
Advanced
Task Manager, apps like the browser don't work correctly.  I have to reboot the 
phone
to clear things up.

Original comment by jdhedden on 15 Oct 2009 at 5:20

GoogleCodeExporter commented 9 years ago
OK, that's no good. I was a little afraid of something like that as there are a
couple of threads running and so far I haven't put much effort into making it 
shut
down cleanly. However, on my G1, I don't think I ever noticed anything like 
this - if
the game wants to quit, it just throws me back to the desktop, and if I resume 
the
application it appears to just start over from the beginning ("Who are you?"), 
which
is pretty much how I would like it to behave. I think in my case it's probably
actually crashing somehow, because I don't even see a "Be seeing you..." 
screen, but
in a clean way.

I will definitely try to get this fixed soon.

Original comment by farnst...@gmail.com on 16 Oct 2009 at 9:32

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I think this should be fixed in the brand new version 1.1.1. The game now 
recognizes
being suspended, and when the application quits, it does a more proper 
shutdown, and
if the native NetHack code quit, it forcefully kills the application (because
otherwise, I couldn't get the native code to get reinitialized properly). Let 
me know
if you are still seeing something bad going on there.

Original comment by farnst...@gmail.com on 21 Oct 2009 at 9:35