# Android Emulator Timeout after 5400 seconds

**URL:** <https://discuss.bitrise.io/t/android-emulator-timeout-after-5400-seconds/9208>\
**Category:** Tooling Issues\
**Tags:** step, android, emulator, testing, appium\
**Created:** [June 5, 2019, 2:52pm UTC](https://discuss.bitrise.io/t/android-emulator-timeout-after-5400-seconds/9208 "2019-06-05T14:52:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mounir](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@mounir](https://discuss.bitrise.io/u/mounir)\
**Post date:** [June 5, 2019, 2:52pm UTC](https://discuss.bitrise.io/t/android-emulator-timeout-after-5400-seconds/9208/1 "2019-06-05T14:52:42Z")

</div>

Hello,  
I have an UI Appium Tests workflow which contains a step to launch an Android Emulator. Since it’s not possible to use AVD Manager Step I used this script

> [@AVDManager not going to next step on workflow](http://discuss.bitrise.io/t/avdmanager-not-going-to-next-step-on-workflow/7837):
>
> Description of the issue My workflow starts with AVDManager, and when it get “emulator: INFO: boot completed” it stuck and not go to the next step Build URL: [https://app.bitrise.io/build/c36ea69d319508b9](https://app.bitrise.io/build/c36ea69d319508b9) Which build Step causes the issue and which version of the step? AVDManager Reproducibility Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO Does a rebuild without caches help? (You …

It worked well but lately this steps always stuck and timeout after 90 mins with this message 🙂

> Waiting emulator is ready…
> 
> - adb wait-for-device shell ‘while [[-z $(getprop sys.boot\_completed)]]; do sleep 1; done; input keyevent 82’
> 
> - emulator -avd Nexus\_5X\_API\_26 -no-window -no-audio -debug-init
> 
> - daemon not running; starting now at tcp:5037
> 
> - daemon started successfully
> 
> timeout after 5400 seconds

Can you please tell me which can cause this error ?  
Url of build : [Bitrise - Mobile Continuous Integration and Delivery - iOS & Android Build Automation](https://app.bitrise.io/build/2a29443e8709e191)  
Stack env: Default (Android & Docker on Ubuntu 16.04 )

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [June 6, 2019, 6:38am UTC](https://discuss.bitrise.io/t/android-emulator-timeout-after-5400-seconds/9208/2 "2019-06-06T06:38:03Z")

</div>

Hi @mounir!

As mentioned in the other thread you’ve pasted, the script alone isn’t sufficient, in case you want to make the emulator work please try the LTS Android environment instead 🙂

---

<div class="post-metadata">

**Author:** ![mounir](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@mounir](https://discuss.bitrise.io/u/mounir)\
**Post date:** [June 7, 2019, 4:13pm UTC](https://discuss.bitrise.io/t/android-emulator-timeout-after-5400-seconds/9208/3 "2019-06-07T16:13:47Z")

</div>

thanks @bitce for your reply I changed the stack to LTS Android environnement and it works !

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [July 7, 2019, 4:13pm UTC](https://discuss.bitrise.io/t/android-emulator-timeout-after-5400-seconds/9208/4 "2019-07-07T16:13:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.