-
-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with android-v11.0.0-pre4 (Samsung Galaxy S4 Mini, LineageOS 16.0, Android 9) #2206
Comments
Thanks, we're looking into it. |
@Helium314 Could you tell what the model number of the phone is? Should be in the settings somewhere. To debug this we need to buy this phone (luckily they are not expensive anymore). |
The model is GT-9195. |
Maybe there is some other issue... I just tested it on my other S4 Mini VE (9195I), which has Snapdragon 410 instead of 400, and got the same crash. Both use the older 32 bit armeabi-v7a (even though SD410 could run arm64-v8a). |
Interesting, that might be a 32-bit problem then. If you can, could you build the Android demo application in this repository and run it on these devices? Building everything in debug mode will also hopefully provide a full call stack with C++ symbols. |
Is the tombstone file generated on the phone? Its path is written in logs if so. |
This one? |
yes, this is the file. I was hoping to see symbols, but it's not helpful. we need to reproduce the crash with a debug library. |
How do you build the debug version? |
Can you share a snippet of the error being generated? The gradle file needs to get updated but manually installing a newer version of CMake should work. You might need to clear out the old files generated by CMake. You can try deleting the following, if they exist: |
Thanks! Is there a debug apk I can download? I fear building this might take a lot of time... |
Sounds like you might be missing the submodules. Run |
@Helium314 If you are still having trouble I can make a debug build and share it with you. |
The crash happens when I choose "add markers from json api". Everything above seems to work. Edit: zooming in the simple map also crashes |
In case this crash is not specific to the device but generally occurs for devices that only support the |
@westnordost I'll try another 32-bit device. |
@westnordost From what I can tell the Samsung Galaxy A13 uses a MediaTek MT6833 CPU which uses a 64-bit set. |
AWS Device Farm has a Samsung Galaxy J7 that I could test on (although it runs Android 8, so it would be some work). |
As I mentioned, it does not only happen on S4 Mini, but also on S4 Mini VE, which is 2 years newer and has a 64 bit processor (SD410) but can for other reasons only run a 32 bit OS. |
@louwers That information originated from the Google Play console. That is the frontend for application publishers on Google Play, it offers all kind of statistics. In the Device catalogue, I am able to see which devices can run my app, I can see the number of installs of my app on devices for each model and finally I can filter by various parameters, one of these is the ABI. When I filter by the minimum system requirements of MapLibre: ABI = armeabi-v7a, Android SDK ≥ 21, OpenGL ES ≥ 3.0, I get the following list. I reordered it by Android SDK versions descending. Maybe it is helpful. |
Is there any more useful info I can provide? |
For pre-06, debug symbols have been added. I suspect that debugging the source of the issue will be easier now. |
I hope this contains more usable information: |
Looks like it crashed trying to link a permuted symbol layer shader. Both devices run Adreno 3xx GPUs which apparently have some pretty cursed conformance issues with OpenGL ES 3.0. I'll try and get one of these devices to debug the shaders with, but it looks like there are a few known issues with those drivers. |
I have access to this data. Here is a list of all devices that use a Adreno 3xx GPU (, are supported by my app, i.e. have minimum Android API level of 21) and support at least OpenGL ES 3.0: |
Note that this list appears as if it contains a lot of duplicates, e.g. there are 18 devices named Samsung Galaxy S4 in there. This is because each configuration is listed separately - different batches of Galaxy S4s have apparently different amounts of RAM, different CPU, GPU and chipset. |
Thank you for this list, even with duplicates there are still quite a few devices with 304/305 GPUs out there. I'll provide further updates in a future PR linking to this issue when I track down the root cause in the shaders. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@kodebach I'm not sure it's the same crash. The one I see is always there on GT-9195 and GT-9195I and makes the app unusable for those phones with MapLibre 11, but I did never observed it on SM-A320FL. |
You're right, I re-read the comments in this thread again and it is probably a different issue. I've created #2579. |
@Helium314 maybe worth re-testing this with |
|
@Helium314 Ha, that means your device does not support Vulkan. We still need to figure out how best to implement a runtime switch. |
(Don't know if it is related, but I've just noticed that this |
Is there any way how people who have device where this appears can help? If they are unable to send PR fixing this issue? (streetcomplete/StreetComplete#5954 seems to have another case) |
The same crash was repeated by one of my users with a Sony SGP511 Android api 23. |
Matches the problematic HW; SGP511 also seems to use Adreno 330 GPU. |
If it is really the same problem as the simulator crash, we will likely have a fix for that out soon. Turns out it was not a problem with the simulator after all. |
@louwers was that #2791, fixed in (I'm encountering some kind of crash in StreetComplete v59.3 -- I haven't yet confirmed that it is map/graphics related - but it is occurring with an Adreno 3xx graphics card, so some of these bugs seem possibly relevant) |
So, I'm too wondering is this issue supposed to be fixed in latest android-v11.7.0 version (OpenGL)? Or is that work still in progress? Is there anything people affected by this bug can try to help in resolving the issue? |
Describe the bug
App crashes on start
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Normal startup
Platform information (please complete the following information):
Additional context
Works on other devices.
S4 Mini supports OpenGL ES 3.0 in case the question comes up.
The text was updated successfully, but these errors were encountered: