Android: PhoneBRICK [!] while playing.

[DarkMio]

First of all: First post and: It isn't a full brick.

First the specs:
-> HTC Desire
-> rooted
-> s-off'd
-> MIUI-ROM
-> a2sd
-> changed recovery (AMON-RA?)
-> changed mounttable:

/system 128000 kb
/data 294528 kb
/cache 25600 kb
/dev 206024 kb
/mnt/asec/ 206024 kb
/sd-ext 468840 kb
/sdcard 7460008 kb

This is the second time, that Pocket Legends bricked my phone. It is simply fixed via recovery - wiping cache and dalvik-cache.
It seems, that PL spams a little in the dalvik-cache until it is completely full and doesn't let clear this cache.
The dalvik-cache is placed in the data-partition, so it's protected - not like RAM, which cleared, when you reboot.
Maybe it's not your fault - but after some hours in some dungeons (atm Mage lvl. 20 - kill 1024 in baleford) my phone freezes, reboots, and stucked in a bootloop.

So - when this comes the next time: I can give you a logcat-output if you want (I hope it's not stored in the dalvik-cache... )

Best regards, great game,

Mio

[EvolutionCSR]

Without a stock device you can't really blame it on the game. Maybe it works fine with stock desire . Have you tried?

[darcsdude]

A lot of people root their phones if there is a compatibility issue that's occuring, it's probably with a program more so than anything else.

[EvolutionCSR]

I was not referring to his root. Root alone doesnt take it far from stock but in OP he states MiUi rom and changed recovery

[DarkMio]

I think, it is a problem witth the dalvik-cache.
Btw.: It's overclocked and undervolted too, on 1113MHz, a little more fluid on Desire.
Maybe next weekend I could try it on the Stock 2.2 ROM for the Desire.

This post is more: Heads up, guys, there is a problem, I have modification, maybe someone can give feedback too. Maybe there are the same problems.

For the devs: Maybe you can test it on android devices with the ddms turned on and track the heapsizes of the dalvik-cache.

Normally there should be an autokill, when the cache is too full - i had a totally freeze. ...

P.S.: The MIUI-ROM is still in beta, maybe there are some problems.

[Diodge]

I just had my phone go into a lock sorta like this.
I was doing the Daily :The Goblin Ritual
I was soloing it with my bear. I was in there for a good 30minutes-1hour(heals are just crazy on these guys)no fun.
I was killing the last guy when my phone started acting all weird and shut down PL, then phone. It rebooted by its self.

The boss sounds are not working. Reboot-The sound is ok now....

alogcat folder for today is empty.

[davidis57]

If you try a more stable custom rom like speed mod rom. Consult Xda forums for your device. If you just changed to your current rom than most likely thats the problem. Dl.titanium backup.and back.your apps and flash a new rom and wipe it first.

[DarkMio]

Don't worry, I know what I do, davdis57.

Today again, after I successfully traded a sword over its tradingvalue (from 1,5k to 2,5k, yeah!), the phone freezed for ... max. 5 secs and reboots - bootloop.
Dalvik-Cache wipe, reboot, everything normal.
Is the HTC Hero supported? Has someone the same issue with lower dalvik-cache? Maybe it is a VM-heap-problem, caused on my different boot tables?
I know, that HOMERUN BATTLE 3D is often kicked outta my RAM and cache, because of the new boottables and an earlier force-closing.

Suggestions?

Next weekend I try it with some more cache reserved through the boottable.
When nothing works I try it with a rooted stockrom with A2SD+ and oc/uv. If all this fails, I retry it without A2SD+ and oc/uv - and when THIS FAILS, I try to get the logcat-logs.

Mio

P.S.: I hope I get now a community shield?

[Futumsh]

It's hard to imagine your problem would even have anything to do with dalvik, if it's at all related to PL itself. PL is almost completely native code.

[DarkMio]

I have a question now:
Get I an official permission to reengeneer some pieces of the source-code?
Together with that, I can output (hopefully) the bug, that freezes.
Maybe it's related to the software or a problem with the OpenGL-Libs, or a unstable Kernel, or or or ...
With the last lines of the DalvikVM, before it freezes I get (hopefolly) the error...
It is hard to get the line, when the DDMS can't fetch any logcat-logs because it freezes.

I have to wipe the dalvik-cache to boot up again - and the recovery haven't a logcat (?I think?) or simliar to read the last pieces from the systemlogcat.
Today I played 3-4 hours and nothing freezed (atm) ... :>
I hope there is something, you could use, because such an bug / error is fatal for some players, who don't have this knowledge...

Best regards,
Mio