# Difficulty with Browser/Chromium on android emulator and chromedriver

**URL:** <https://discuss.appium.io/t/difficulty-with-browser-chromium-on-android-emulator-and-chromedriver/1017>\
**Category:** Support\
**Created:** [October 23, 2014, 9:16am UTC](https://discuss.appium.io/t/difficulty-with-browser-chromium-on-android-emulator-and-chromedriver/1017 "2014-10-23T09:16:10Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![crichmond](https://discuss.appium.io/letter_avatar_proxy/v4/letter/c/49beb7/32.png) [@crichmond](https://discuss.appium.io/u/crichmond)\
**Post date:** [October 28, 2014, 2:00pm UTC](https://discuss.appium.io/t/difficulty-with-browser-chromium-on-android-emulator-and-chromedriver/1017/8 "2014-10-28T14:00:33Z")

</div>

I’m testing with .NET. For what it’s worth, I was able to install Chrome on android emulators (I’m not exactly sure what that works, perhaps because I’m using an ARM CPU instead of an Intel CPU – the chrome.apk might only work with an ARM simulated processor).

My trouble now is: webpages take longer than 60 seconds to load, and no matter what I specify the command timeout to be, that command timeout is always the default value of 60 seconds.

I believe that is a bug that I’ve mentioned in the issues/bugs section:

> [@Command timeout not changeable for .Net Appium](https://discuss.appium.io/t/command-timeout-not-changeable-for-net-appium/1098):
>
> The default command timeout is 60 seconds. I set this value to TimeSpan.FromSeconds(300). Yet Appium still times out after 60 seconds instead of 300 seconds. Please fix/advise. thanks, Chris

---

_[View the full topic](https://discuss.appium.io/t/difficulty-with-browser-chromium-on-android-emulator-and-chromedriver/1017)._