# Android App (Build 2): Flight Map Issues

**URL:** <https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941>\
**Category:** Beta General\
**Created:** [August 5, 2011, 1:44am UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941 "2011-08-05T01:44:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![winwiz88](https://avatars.discourse-cdn.com/v4/letter/w/9dc877/32.png) [@winwiz88](https://discussions.flightaware.com/u/winwiz88)\
**Post date:** [August 5, 2011, 1:44am UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/1 "2011-08-05T01:44:17Z")

</div>

Just loaded Beta 2 this evening on to my Thunderbolt and looks like some of the original issues are gone now. However, whenever I select an aircraft on the map (I reached the map by clicking through one of my saved airports or by direct entry) it causes the app to force close. I’ve installed the aLogCat app as recommended in a previous post by a Flight Aware staffer, but is there a certain level of logging that would be most useful to the dev team for me to submit?

---

<div class="post-metadata">

**Author:** ![mduell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mduell/32/115680_2.png) [@mduell](https://discussions.flightaware.com/u/mduell)\
**Post date:** [August 5, 2011, 7:15pm UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/2 "2011-08-05T19:15:37Z")

</div>

Let’s try the default level of logging.

---

<div class="post-metadata">

**Author:** ![AJLong](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJLong](https://discussions.flightaware.com/u/AJLong)\
**Post date:** [August 8, 2011, 3:29am UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/3 "2011-08-08T03:29:21Z")

</div>

Same issue, however, instead of the whole app crashing, it returns me to the flight info. LG Ally running latest Andriod version. It additionally gives me issues when I switch from Landscape to Portrait or vice versa.

---

<div class="post-metadata">

**Author:** ![winwiz88](https://avatars.discourse-cdn.com/v4/letter/w/9dc877/32.png) [@winwiz88](https://discussions.flightaware.com/u/winwiz88)\
**Post date:** [August 8, 2011, 4:00am UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/4 "2011-08-08T04:00:46Z")

</div>

> [@mduell](#):
>
> Let’s try the default level of logging.

I have sent a copy of the log to the email address posted in a previous post. Hope it helps isolate the issue.

---

<div class="post-metadata">

**Author:** ![Betelgeuze](https://avatars.discourse-cdn.com/v4/letter/b/4af34b/32.png) [@Betelgeuze](https://discussions.flightaware.com/u/Betelgeuze)\
**Post date:** [August 14, 2011, 3:56am UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/5 "2011-08-14T03:56:26Z")

</div>

Still having the force close on the new beta 3 build too when selecting aircraft or zooming.

---

<div class="post-metadata">

**Author:** ![winwiz88](https://avatars.discourse-cdn.com/v4/letter/w/9dc877/32.png) [@winwiz88](https://discussions.flightaware.com/u/winwiz88)\
**Post date:** [August 14, 2011, 4:10am UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/6 "2011-08-14T04:10:31Z")

</div>

> [@Betelgeuze](#):
>
> Still having the force close on the new beta 3 build too when selecting aircraft or zooming.

Zooming was never an issue for me, but on Beta 3 I still have the force close on selecting aircraft. Let me know if the FlightAware dev team would like me to submit an error log report.

On a side note, I had not recieved any notice that Beta 3 was released until you said something…

---

<div class="post-metadata">

**Author:** ![Betelgeuze](https://avatars.discourse-cdn.com/v4/letter/b/4af34b/32.png) [@Betelgeuze](https://discussions.flightaware.com/u/Betelgeuze)\
**Post date:** [August 14, 2011, 4:16pm UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/7 "2011-08-14T16:16:14Z")

</div>

> On a side note, I had not recieved any notice that Beta 3 was released until you said something…

I only notice because I was going to try to download build 1 to test some things, I received no notice as well.

---

<div class="post-metadata">

**Author:** ![mduell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mduell/32/115680_2.png) [@mduell](https://discussions.flightaware.com/u/mduell)\
**Post date:** [August 24, 2011, 8:14pm UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/8 "2011-08-24T20:14:11Z")

</div>

We’re not email announcing every beta, but beta 4 is available now.

---

<div class="post-metadata">

**Author:** ![Betelgeuze](https://avatars.discourse-cdn.com/v4/letter/b/4af34b/32.png) [@Betelgeuze](https://discussions.flightaware.com/u/Betelgeuze)\
**Post date:** [August 24, 2011, 10:19pm UTC](https://discussions.flightaware.com/t/android-app-build-2-flight-map-issues/11941/9 "2011-08-24T22:19:36Z")

</div>

Force close is still occurring on beta 4 when selecting a specific airplane from the map.
