16 Replies to “[Android] Temporary Fixes for Those With Unlucky PAD Crashes”

1. “The problem actually isn’t PAD, but Android, specifically Chrome.”

   How are we blaming Android and Chrome? They updated the game, and now it’s broken. Plenty of people across the same Android OS version, chrome version, devices, etc, that don’t experience the crashes, and plenty that do. The only common denominator is PAD. Chrome might be triggering the issue, but the problem is 100% PAD.

   1. Reworded the comment, but I wouldn’t put 100% blame on PAD. Maybe 50%. It’s not just a PAD-only problem at the moment, and it’s affecting only certain devices as they have mentioned.

      1. It’s not just PAD, but I’m sure the other games that are crashing are also using similar anti-cheating detection which Google’s recent updates seemed to have triggered. That kind of thing probably requires, er, abuse of underspecified behavior. Meaning they’re probably exploiting loopholes and gaps in Android, and making assumption about “legitimate” apps’ behavior, which held true… until now.

         In one case, Fate/Grand Order used a zero-day exploit in many popular Android devices, to bypass an Android 7 security/privacy feature that kept apps from seeing what else was running. The game wanted to detect root and prevent rooted players from accessing it. More details: https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20

         I’d like to know what other games experienced issues, if you can send me a few links or search terms. I presume they’ll be games made by Japanese companies which have close ties to each other, or are all clients of the same Japanese software security company. It’d be interesting if this is correct, and very interesting if it isn’t.

         1. Wish I could give you a list, unfortunately I don’t have one since I forgot who mentioned that to me (been a while) about the other games they play. It does leave me ponder what triggered it as well, if this is true. It might remain a mystery to us anyhow…

2. “The problem actually isn’t PAD, but Android, specifically Chrome.”

   Is it Google’s responsibility now to base their updates off PAD now? This issue doesn’t happen with any other mobile game I play.

   Dumbest comment ever.

   1. I’ll happily edit that if that’s offending people. Also, I’d suggest milder wording. 🙂 I’ll happily not post anything like this in the future if a post that is meant to help others is seen as bad.

      1. The post is helpful as it presents a work around that might work for people. But suggesting it isn’t PADs fault is misleading. Google doesn’t need to base their updates on PAD, it is PADs job to ensure it works on Android. If this was a Google issue it would effect all games, or majority of mobile games on Android.

         1. Hey if you see something that doesn’t fit well with you, mention it. Great. But don’t say it in such an offensive tone.

            And let’s just put it this way: it isn’t PAD’s fault 100% like Reni said because PAD might not have known that this problem would occur. I mean, it’s not like any one has foresight for the future, don’t they?

            It can be considered partially Android’s fault, although not directly, because some code between PAD and Android might have antagonized each other, and sometimes you can’t detect it right away until later, when the problem reveals itself.

            And, mind you, we are just so pushy towards them to update, not considering how difficult it is to code, especially when they’re trying to create new NA exclusive content.

            We don’t have the right to blame anybody, actually. If there’s a mistake, then there’s a mistake. And, for peace’s sake, no one is allowed to take the blame. We can be humbler than that.

         2. That was why I reworded it asap once I noticed too. 🙂 Again, I did see it crash not just for PAD, but other games as well for some people. I’m no app developer, so I can’t comment whether it must affect majority of games if something happens.

3. Thanks Reni,

   1. I have actually been experiencing this kind of crash for years, I guess I recent update to something just made it more prominent. I can also confirm that I have never once had the issue on an IOS device, and that it has happened at least ten or so times across two of my Android devices for the past three or four years. In fact, I had it happen again on the day that they announced the issue, after not seeing it for a few months. I also just had it happen to my account on my Fire Tablet today, which was a first, although I have only had that account for a few months. Since it does not have Chrome, or Google Play, it might be an issue with Android, Linux, versions of PAD in general. Or maybe that was simply a coincidence, and it was just a problem with my tablet.

      1. Pad has been crashing forever on Android, but not this consistently, so it has been ignored. Every 15 ranking runs or so, PAD closes, and I reopen to the screen that says I’ll get no points for the run. I don’t want to even know how many stones worth of stam have gone to crashes, but it’s a lot.

4. Thanks for the info, are I! 😁😁👍

5. A kinda soft fix: exit the app occasionally to create checkpoints so that way when pad crashes, it resets to the floor you last exited on, rather than floor 1.

6. Playing PAD for 6 years now, and I’ve never had crash issues until now. It’s literally unplayable for me since it’ll crash within the first minute or two. I tried Disabling Chrome but still nothing, so I guess I’ll have to wait until Gungho rolls out a fix. Anyways, thanks for the update Reni 👌

   1. I’ve had some crashes on Android back in my Android days, but I haven’t seen anything this bad in a while too, aside from late Android version support. (I still love Android though :D) It’s unfortunate that it happens, but at least GungHo formally admitted a problem has occurred. Let’s hope you guys on Android will have a permanent fix soon!