After suspending mgMAPS (then shutting down) phone won't boot.

After using mgMaps for a while, tracking my way into a no cell tower area, I suspended the prog to fool with a flash game (the Tesla...screen entertainment...thing). I then powered it down to save my battery.

mgMaps was (as far as I recall) still 'suspended'.

Later, when I was going to do a GeoCache-stash; no go. When I power on, it power cycles through the two screens; root loader (AT&T with progress bar) then the 3G twirly show-off-the-new-OLED screen. Then it starts over. Power button has no effect. When I plug into charger, it doesn't charge the batt (while turned on); but will when starting from completely powered off.   

At some point, when trying to find a POST (power-on-self-test)  shortcut (using various keys <power on>, <send> <rt> <lft> <up> <dn> both <shifts> and various combinations, a error screen popped up:

Black screen, blue border with red letters.
-------------------------------------
DEMSBL BOOT Loader for MSM6298
More than Down loader v5.50
-------------------------------------

I've tried the sequence for one of the other samsung forums
(http://www.samsung-behold.com/introduce-yourself/hello-here-bc-i-need-help/msg29437/#msg29437)
which related to a bad battery...maybe... or a reset charge watch dog circuit [my own summary.]. Didn't work.

Any ideas, fellow propeller heads?

honico
//

jyg:

Good point; I also assumed volatile meant memory set aside within the RAM, unallocated other than to specified programs, in this context, mgMaps. But, I'm a newbie too to the Impression so popped the battery out for 10 minutes (arbitrarily) and, no joy.

As an aside, I also removed my SIM and u-SD card, the problem remained.

;-)

That is similiar to what happened to me. I was running mgmaps earlier that day with too big of map and later that day my phone crashed and got  stuck on the same page. However I was not running mgmaps at the time. I think the big map uses too much memory and crashes the phone. I recommend staying with a smaller map under 100mb. We worked it too hard. The map file has alot of png's in it and i think the phone tries to index all of them and that what causes the crash.

Well its not so much mgmaps that caused the phone to brick. It was the map you had made. I made a map about 1gb and it took forever to even delete off my computer. The phone would barely run mgmaps using that app. The phone tries to index all the pictures and I think that we might have stressed it a little too much. I would not even try a map over 100mb now.

There are other ones out there. I put together some that might do the tracking for you and might be able to cache maps too. Play with them and see if there is anything you like. Here is also a link to a page that might point you in the right direction too.

http://www.maps-gps-info.com/fgpfwmobile.html#Java