Alex, the crash on pressing play for them two devices you described is something I've looked into.
It seems to be happening on motorola devices, I debugged it as best I could with someone on a Droid Bionic.
It's actually motorola firmware fucking up believe it or not. It's not a normal exception, but a SegFault somewhere in a core android library (libska.so) Something like this can't be caused by an app intentionally and is stupidly hard to work around since no error is thrown at which point it occurs, and the app simply dies reporting SIGEGV.
(Android is supposed to catch -all- application errors and allow you to send an error report to the developer)
I'm going to have to just leave it for now as it is just simply so hard to pinpoint without having a motorola device myself and a load of time to play with it, so unfortunaly phones on Motorola firmware may not work for now...
(If anyone doesn't believe me and thinks I'm making excuses, I can provide debug logs showing the fault occuring <:)
The workaround we did find, was installing a non-motorla ROM onto the same device. The guy I was with flashed his phone with ICS4Bionic, and it worked absolutely fine, so tell anyone that flashing their phone with a (>note< google stock, not just stock motorola) ROM is the only workaround (not that anyone would be this bothered about playing T-Aiko!....)
as for momo no hanabira, I sure like fucking that map up don't I? <:
It seems to be happening on motorola devices, I debugged it as best I could with someone on a Droid Bionic.
It's actually motorola firmware fucking up believe it or not. It's not a normal exception, but a SegFault somewhere in a core android library (libska.so) Something like this can't be caused by an app intentionally and is stupidly hard to work around since no error is thrown at which point it occurs, and the app simply dies reporting SIGEGV.
(Android is supposed to catch -all- application errors and allow you to send an error report to the developer)
I'm going to have to just leave it for now as it is just simply so hard to pinpoint without having a motorola device myself and a load of time to play with it, so unfortunaly phones on Motorola firmware may not work for now...
(If anyone doesn't believe me and thinks I'm making excuses, I can provide debug logs showing the fault occuring <:)
The workaround we did find, was installing a non-motorla ROM onto the same device. The guy I was with flashed his phone with ICS4Bionic, and it worked absolutely fine, so tell anyone that flashing their phone with a (>note< google stock, not just stock motorola) ROM is the only workaround (not that anyone would be this bothered about playing T-Aiko!....)
as for momo no hanabira, I sure like fucking that map up don't I? <: