Errors on 4.15 from play users

After updating my project (https://play…com/store/apps/details?id=com.SimfoGames.SimBowl) to 4.15 I’ve got errors on some devices on Play. What could be the problem?

I rolled back to previous version on play. The problem apk file (4.15 min sdk 23) is here: https://www…com/s/hj4xc43h3qb9a9z/B_6_415-Android-Shipping-armv7-es2.apk?dl=0

,

The crash that those devices are running into are Signal 11. This is typically due to a memory segmentation that’s caused from the game on the device, such as a memory leak. If the phones are older and incapable of keeping up with what’s required from the project, the phone will throw these signals too.

I have tested on a , which has similar specs to the lg g3. What version of Android are your devices on?

Thank you!

Thanks for the response!
Here is the list of devices with errors.

LG Stylo 2 (ph1)
Android 7.01
MSM8916 (2 crashes);

Galaxy S5 (kltetmo)
Android 6.0
MSM8974;

LG K8(2017)Dual(lv3)
Android 7.0
MSM8917;

LG G3 (g3)
Android 6.0
MSM8974AC (3 crashes);

Pop4 (POP455C)
Android 6.0
MSM8909 (2 crashes);

Galaxy S5 Mini (kmini3g)
Android 6.0
MSM8228;

Galaxy S5 (kltevzw)
Android 6.0
MSM8974;

Galaxy J3(2016) (j3ltevzw)
Android 6.0
MSM8916 (4 crashes);

Galaxy J5 (j53g)
Android 6.0
MSM8216 (2 crashes);

ZTE Warp 7 (beam)
Android 6.0
MSM8916;

LG X Style (k6b)
Android 6.0
MSM8909 (3 crashes);

In the same project, but on the version 4.13 there are no errors.

Thank you!

I unfortunately do not have most of the devices you listed out. However, I tested on a Galaxy S5 and did not run into any troubles on Android Version 4.4.2 or 5.0. Did you root your devices?

Thanks!

Apparently, I was misunderstood. I’ll try again.

  1. I see these crashes in my play developer console, and I have no idea its owners were rooting their devices or not. These are not my own phones.

  2. Errors appeared only after update my game to 4.15 engine version. There were no errors on version 4.13.

  3. The game version that is now on the play store, compiled on 4.13 engine version and has min sdk 16 and target sdk 23. It works perfectly.

  4. The problem version of my game (4.15) has sdk 23 for min and for target. It’s for android 6+ only. I removed it from play. Here is the link to this problem apk again: https://www…com/s/hj4xc43h3qb9a9z/B_6_415-Android-Shipping-armv7-es2.apk?dl=0

  5. The game on 4.13 engine was installed on approximately 1500 devices. There are no any crashes.
    The same version of the game but at 4.15 engine, was installed on approximately 700 devices. I received 17 messages about crashes, then I removed this apk from play.

Before uploading the problem apk to play, I’ve check it on (android 6.0) and LG K10(android 6.0) Everything works perfectly.

UE 4.15 is excellent update! It has a lot useful things. It’s so pity I can’t use it in my work while these crashes appear so often.

,

Since we cannot rule out that the devices are rooted, that would be the first thing to come to mind. I haven’t had any trouble on the devices that I have used to test out this issue. If you’re using API 16, it should cover 4.1.2 and up without causing any trouble.

I have not been able to crash your project yet.

Regarding the number of devices not being supported is because you’re using a version of Android that requires daydream. Therefore, when you upload that project that supports daydream, it’ll lower the amount of devices supported. Some people have seen it as low as like ~7 devices. Here is a [link on how to fix the devices issue.][1]

Just as a tip, I would suggest putting a blocking volume at the back, because I did fall off the map. :slight_smile:

Play, 2500 devices removed, 7 left - Mobile - Epic Developer Community Forums

, thanks for the discovered bug with the ball! I’ll fix it.

Number supported devices for my game is 12179. I have no problen with that.

Regarding rooted devices… It seems that paragraph 5 of my previous message was not clear.

Well… I’ll try again :slight_smile:

The version of my game on 4.13 engine was downloaded and installed on users’ phones 1500 times. These users sent me 0 errors.

The version of my game on 4.15 engine was downloaded and installed on users’ phones 700 times. These users sent me 17 errors.

It’s obvious to me that the rooted phones are not the reason.

The error seen is a segmentation fault. I have not seen it while testing on the devices that we have available. It could be due to a memory leak with your project, and it’s always a possibility that rooted devices could be causing this issue, or devices that aren’t fully updated.

What I would suggest doing is seeing whether or not you can request additional information, such as exactly where in the game it’s occurring so you can find a pattern.

Another attempt to load my game on Play with 4.15.1 engine version. The result is on the graph (red color marks 4.15 engine version in release).

I found a phone for tests (Sony Xperia Z2) that works fine with version 4.13 but crashes when I running version 4.15.1. It looks like the problem is planar reflections shader. After several tests it became clear that version 4.15 works on it only if you remove the planar reflections.
Sorry for my English.

The problem apk file here https://www…com/s/cbbc60tjr9g4t2y/Bowling_415.apk?dl=0

In 4.16 everything is fine. The topic can be closed.