# Android Instabilities

**URL:** <https://forums.unrealengine.com/t/android-instabilities/507729>\
**Category:** Mobile\
**Tags:** unreal-engine, Android, question, UE4-27\
**Created:** [March 17, 2022, 6:08pm UTC](https://forums.unrealengine.com/t/android-instabilities/507729 "2022-03-17T18:08:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![illYay](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@illYay](https://forums.unrealengine.com/u/illYay)\
**Post date:** [March 17, 2022, 11:20pm UTC](https://forums.unrealengine.com/t/android-instabilities/507729/3 "2022-03-17T23:20:40Z")

</div>

Coincidentally I’m running this on a sister device of the Quest and Quest 2 (Portal) which is more locked down, so I’m like a pioneer trying to get Unreal working on it during a hackathon.

I have actually tried this on an older version of unreal a while ago during a hackathon and had the same issues. I believe that was about 4.22. I was always able to deploy the First person demo but more complex projects tend to fail. I remember getting the same PxVehicle crash even then.

I’d hope other people ran into this exact issue on other Android devices, but I haven’t found much info online. Our devices are decently powerful too, but memory may be an issue. The devices typically run AR and even actual Unity releases in the past.

I also get this issue even in light weight projects that normally work if I force Vulkan enabled instead of Open GL ES 3.1. I get to the splash screen and eventually the logs show the PxVehicle failure.

---

_[View the full topic](https://forums.unrealengine.com/t/android-instabilities/507729)._
