<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Android app fail on start up - kill app needed in ArcGIS Collector Questions</title>
    <link>https://community.esri.com/t5/arcgis-collector-questions/android-app-fail-on-start-up-kill-app-needed/m-p/611261#M10469</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Whilst I think the general direction of Collector is very welcome, it is still too flaky to add to our inventory of mapping tools.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The main reason is that about 1/3 of the startups just sit on the refreshing screen without doing anything.&amp;nbsp; Only killing the android tasks gets it back.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Has anyone else noticed this?&amp;nbsp; I do wonder if it is my phone - a rare Intel powered Android phone, that never was sold in the US (so esri testing would never have happened) - the Moto XT890&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ACM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 27 Apr 2014 09:09:48 GMT</pubDate>
    <dc:creator>AdrianMarsden</dc:creator>
    <dc:date>2014-04-27T09:09:48Z</dc:date>
    <item>
      <title>Android app fail on start up - kill app needed</title>
      <link>https://community.esri.com/t5/arcgis-collector-questions/android-app-fail-on-start-up-kill-app-needed/m-p/611261#M10469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Whilst I think the general direction of Collector is very welcome, it is still too flaky to add to our inventory of mapping tools.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The main reason is that about 1/3 of the startups just sit on the refreshing screen without doing anything.&amp;nbsp; Only killing the android tasks gets it back.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Has anyone else noticed this?&amp;nbsp; I do wonder if it is my phone - a rare Intel powered Android phone, that never was sold in the US (so esri testing would never have happened) - the Moto XT890&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ACM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Apr 2014 09:09:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-collector-questions/android-app-fail-on-start-up-kill-app-needed/m-p/611261#M10469</guid>
      <dc:creator>AdrianMarsden</dc:creator>
      <dc:date>2014-04-27T09:09:48Z</dc:date>
    </item>
  </channel>
</rss>

