LGVX6000 exit screen - phone bug? | developer.brewmp.com LGVX6000 exit screen - phone bug? | developer.brewmp.com

Developer

LGVX6000 exit screen - phone bug?

Forums:

i have a bug where when i press the EXIT button on LGVX6000 anywhere in the app i get a white screen instead of "get it now" good-bye screen. Exiting using "clr' button and calling on ISHELL_CloseApplet returns me into the "get it now" menu just fine, it is just the END button tha is the problem.

looks like unique problem to lgvx6000

By doing the crudest of the break points (placing while(1); ) as a very last instruction that i have control over i see the good-bye screen present and displaying. Only after that, i can guess, is where it gets cleared. There are no calls to clear screen that would do this.

One more thing i noticed is that if i use a BAR that is made with PNGs, it works fine. If I have a BMP bar it fails. So I am thinking about unloading from memory or something like that, but it does not really make sense. It is there initially- displayed during the last line excecuted in EVT_APP_STOP and then it fraks out

I read somewhere else on the forums that it might be there's an IFile still open in your app (need to IFILE_Release(pIFile) it), that's been known to bring down the phone on exit.

I read somewhere else on the forums that it might be there's an IFile still open in your app (need to IFILE_Release(pIFile) it), that's been known to bring down the phone on exit.

I've had the same problem. As far as I can tell, it happens because the phone tries to load the "goodbye" screen right when you press 'End' and before you can unload memory. Therefore if your program used nearly all memory, there not enough RAM free to load the image and a white screen is shown. I could be wrong though.

I've had the same problem. As far as I can tell, it happens because the phone tries to load the "goodbye" screen right when you press 'End' and before you can unload memory. Therefore if your program used nearly all memory, there not enough RAM free to load the image and a white screen is shown. I could be wrong though.

hi. thanks for your answers. i did have IFILE_Release - i have only load/save file that gets appended, but i tried moving it around from callback into EVT_STOP and i got nowhere - sadly. The white screen presists. Thanks for the suggestion though.
As far as the memory goes. i dont know how much faster i can unload things. it is true that i am using most of it but at end time my order of operations looks like this:
1.) Kill all timers
2.) Kill and free sound
3.) save all game states to a file (and close file)
4.) release all images (in a 'for' loop)
5.) release all text buffers / misc memory
6.) close app.
is there a different way that i could approcah this to expedite the kill so the "good-bye" screen would load?
thanks for all your help
andreja

hi. thanks for your answers. i did have IFILE_Release - i have only load/save file that gets appended, but i tried moving it around from callback into EVT_STOP and i got nowhere - sadly. The white screen presists. Thanks for the suggestion though.
As far as the memory goes. i dont know how much faster i can unload things. it is true that i am using most of it but at end time my order of operations looks like this:
1.) Kill all timers
2.) Kill and free sound
3.) save all game states to a file (and close file)
4.) release all images (in a 'for' loop)
5.) release all text buffers / misc memory
6.) close app.
is there a different way that i could approcah this to expedite the kill so the "good-bye" screen would load?
thanks for all your help
andreja

I have a bad (poor) suggestion: Disable large portions of your application until you find the chunk that is causing the Exit Crash (disable chunks until it works right, then reenable until it stops working).
Continue the process, breaking it and fixing it in smaller pieces, until you discover the problem chunk.
:D

I have a bad (poor) suggestion: Disable large portions of your application until you find the chunk that is causing the Exit Crash (disable chunks until it works right, then reenable until it stops working).
Continue the process, breaking it and fixing it in smaller pieces, until you discover the problem chunk.
:D

Quote:find the chunk that is causing the Exit Crash
I don't think he's talking about a crash. It's just that instead of showing a splash screen on exit, there's a white screen -- but it still works the same, the user is taken back to the main menu without a reboot. I've had the same problem, didn't solve it (it's not a really big bug) and still passed True Brew testing.

Quote:find the chunk that is causing the Exit Crash
I don't think he's talking about a crash. It's just that instead of showing a splash screen on exit, there's a white screen -- but it still works the same, the user is taken back to the main menu without a reboot. I've had the same problem, didn't solve it (it's not a really big bug) and still passed True Brew testing.

doh!

doh!

Hi yall,
I'm having the exact same problem. Did you find a solution to solve it?
Cheers,
Joël S.

Hi yall,
I'm having the exact same problem. Did you find a solution to solve it?
Cheers,
Joël S.

No...It passed NSTL with that "feature" without a remark. Actually we saw it in a second game we did as well. Makes me think it is a "known" issue. It does not happen on other phones to which we ported.
Good luck .

No...It passed NSTL with that "feature" without a remark. Actually we saw it in a second game we did as well. Makes me think it is a "known" issue. It does not happen on other phones to which we ported.
Good luck .