Still no Android patch

Bcorm

It's been a month and still nothing. Are they ever going to do anything?

Unknown

Oh yeah, they said last Monday it would be fixed in a day or two, and don't send any more emails in. I'm way past tired of this whole situation. "Dedicated to creating the best gaming experience and support", indeed.

ugetnocookie

Yeah 1 month passed, 1 week since last mail and still nothing. Im tired of this aswell...

Unknown

Yet they can release Carnage, Thing, Ant-Man(sorry if I missed any...cannot play), run umpteen different events, plug those on Facebook, but say nothing about this issue which left being an annoyance behind three weeks ago. Feeling ignored here. For a company to claim that it provides the highest level of gameplay and customer support around to do this is complete and utter nonsense. I have never, ever experienced anything like this. Absolute FAIL.

Unknown

You know what I have been patient like they say but this is **** ridiculous almost a month now still nothing. While they are previewing r79 update this has been going on since the r77 update it's time someone gave us answers. And if they don't compensate us after all this I'm done and they can shove the game up there ****.

Unknown

Rob1987 wrote:

You know what I have been patient like they say but this is tinykitty ridiculous almost a month now still nothing. While they are previewing r79 update this has been going on since the r77 update it's time someone gave us answers. And if they don't compensate us after all this I'm done and they can shove the game up there ****.

I completely agree, except they may not get to wait until this issue is fixed for me to tell them what they can do with their game. I'm out of patience.

Unknown

Here's a update guys


Jul 1, 17:18
Greetings D3 Go! Customer,
Thank you for contacting D3 Go! Customer Support.
We wanted to provide an update for players like yourself that have reported crashing and access issues with some Android devices (such as the Galaxy S4).
The development team have been working on the crashes with the limited information that they have, but it has been difficult to recreate the errors on our hardware. The recent R78 update offered fixes for a few players, but not for everyone like we had hoped. The devs have continued to work on a solution, and as you've no doubt noticed, the problem has been a tough one to fix.
We wish we had a more definitive answer or even a specific timeframe for a solution for you, but we can say that the devs are hard at work in adding new coding to the game that should provide much better information to work with by next week. This should help them get a better handle on creating fixes. So, please look for and download the R78.1 update when it arrives.
We know this hasn't been any fun for those of you affected and we thank you so much for your patience while we continue to work on getting you back in the game!

Malcrof

I got the same email, even though R78 fixed it for me, but nothing in it about the other issues i had mentioned in the ticket. I am thinking that was a blanket email. Still nothing about compensation or whatnot.

Unknown

I've been suffering through this problem along with the rest of you and would be happy to blast them about not fixing it except for one thing. On my phone (Galaxy S4) I've had a few crashes in other apps since the Lollipop update (about 1 for every 100 MPQ crashes) and in most of those cases I'm prompted to send a crash report. I've never been prompted the same way following a MPQ crash. That tells me that the crashes aren't being seen the same way by the OS.

If that's true then the developers may be having a hard time finding the actual cause of the crash. Each of the patches we've been given as "fixes" may be responding to a symptom and not the cause.

I do believe they're working hard on finding a fix. Ignoring this problem and annoying a large group of users is bad for business. As long as they continue to acknowledge it's a problem and are still including repair efforts in updates I'm going to continue to give them the benefit of the doubt. Who knows, when they finally fix it maybe we'll get another "reward" for our patience.

Unknown

I got the same email. This had better work, today marks one month since R77 locked me out of the game. As much as I enjoy playing it (and am admittedly addicted to it), I'm considering this their last chance to get it right. With regards to what was mentioned about compensation, support sent me this on June 23.

"We wish to profusely thank you all for your continued patience. Recently, some issues have arisen that the developers are currently working to correct. We understand that it has been a frustrating experience, and are more than happy to explore the possibility of compensation for the issues."

Keep on them, guys.

morph3us

It might be useful to try and gather some information about the specific builds of Android you're all running that are causing you issues. Even though we're all supposed be running "Android 4.4 KitKat" or "Android 5.1 Lollipop" etc, the only users who are actually running that are those people using Nexus devices. OEM builds of Android are actually very subtle forks of the OS, which can cause huge headaches for developers when they try and troubleshoot. For instance, Samsung use some of their own proprietary library files, compared to "stock" Android, which can cause crashing issues. It's obviously impossible for the devs to test on every single device out there, so they try and optimise for some of the major builds of Android out there instead.

If you can figure out some commonality between devices with significant crash issues, it might help the devs figure where the problem is faster.

I'm running R78.1 MPQ on two devices, a Asus Nexus 7 2013, running Android 5.1.1; and an HTC One M8, running an HTC Sense 6.0 customised build of Android 5.0.1. It's running fine on both devices, with no recent crash issues, and no sync issues either.

This is definitely one area where the iOS users have it over us Android users.

Unknown

I'm using android version 2.3.6 it's a Samsung MP3 player not sure what it's called tho.

Unknown

It's a samsung Galaxy s wifi MP3 player

Unknown

morph3us wrote:

It might be useful to try and gather some information about the specific builds of Android you're all running that are causing you issues. Even though we're all supposed be running "Android 4.4 KitKat" or "Android 5.1 Lollipop" etc, the only users who are actually running that are those people using Nexus devices. OEM builds of Android are actually very subtle forks of the OS, which can cause huge headaches for developers when they try and troubleshoot. For instance, Samsung use some of their own proprietary library files, compared to "stock" Android, which can cause crashing issues. It's obviously impossible for the devs to test on every single device out there, so they try and optimise for some of the major builds of Android out there instead.

If you can figure out some commonality between devices with significant crash issues, it might help the devs figure where the problem is faster.

I'm running R78.1 MPQ on two devices, a Asus Nexus 7 2013, running Android 5.1.1; and an HTC One M8, running an HTC Sense 6.0 customised build of Android 5.0.1. It's running fine on both devices, with no recent crash issues, and no sync issues either.

This is definitely one area where the iOS users have it over us Android users.

Thank you sir, but the devs have already collected that information from any of us who have a ticket in. At the risk of sounding uppity, it isn't my problem to solve. The game worked just fine prior to the installation of R77 and has not worked since. I'd say any changes they made regarding Android with that update is a good place to start.

morph3us

Fair call. You're the one with the crashing problem, you can certainly handle it any way you see fit.

Bcorm

$3700.00. Amount spent in five months only to be screwed in patch error. All I want is to be able to play or a definitive answer.

Unknown

Bcorm wrote:

$3700.00. Amount spent in five months only to be screwed in patch error. All I want is to be able to play or a definitive answer.

And here I thought I had good reason to be upset. Good lord, man. If I'd spent actual money on this game, I'd be absolutely furious right now! Yes, I agree...I'd also like to see some kind of communication forthcoming about this issue. Over a month with little said about what's being done is simply not enough.

GothicKratos

Not to sound uppity, but what exactly to you want to hear? "We're working on it"? Would you like to hear the nuanced details of their testing and troubleshooting? Take it easy and play some Puzzle Quest 2 (it's free!) while this is being worked out.

I mean, I get it. It sucks you're locked out of the game, but as noted in your e-mail, and further explained by morph3us, it's not as easy as 'there's a problem, here's a solution'. I highly doubt the developers happen to have every device known to man at their disposal to test their program on, so these types of things happen sometimes.

At the end of the day, they have to isolate the common variables and figure out a solution, most likely without whatever devices are causing the problem. Even if you axe the whole "technology is hard" spiel, I mean, come on, can you imagine a doctor trying to diagnose a patient without seeing them first? Cut 'em some slack.

Unknown

Honestly...yes, a little simple dialogue would go a long way. Even if it were only a simple message once every two weeks or something that said, "Hey, we're sorry we don't have a fix yet, but we're trying hard to figure it out." Would be a lot better than "Don't send anymore emails, but we really do provide the best gaming experience and support around." I'm not asking for the moon, and I wouldn't expect any astronomical compensation like some other players might. I just thought I might be able to expect them to provide the service which they claim to. Apologies that this view upsets you.

Bcorm

I would just appreciate a little dialogue. It feels like I'm being ignored.

CrookedKnight

I just got an Android patch that was not R79 (because I applied it and am still on R78) - I hesitate to get people's hopes up, but maybe it was a stability fix?