Andoid Force Close When "Auto Find Location" Ticked

manoj-g-nair / androidedinburghbustracker

Automatically exported from code.google.com/p/androidedinburghbustracker

0 stars 0 forks source link

Andoid Force Close When "Auto Find Location" Ticked #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Having "Auto Find Location" ticked crashes the app when attempting to view 
viewing the map
2. If "Auto Find Location" is NOT ticked the app is okay

What is the expected output?
I expect to see the map view and for the application to hone on my location.

What do you see instead?
Andoid asks me to force close the app.

What version of the product are you using?
Lates version from Android Market (v0.0.3)

On what operating system?
Details on attached file.

Please provide any additional information below.
New phone ZTE Blade aka Orange San Fransisco.  I am using a modified ROM 
(details in file) though having no issues with Google Maps and GPS.

Original issue reported on code.google.com by mchun...@gmail.com on 1 Oct 2010 at 9:48

Attachments:

[bus tracker.pdf](https://storage.googleapis.com/google-code-attachments/androidedinburghbustracker/issue-9/comment-0/bus tracker.pdf)

GoogleCodeExporter commented 9 years ago

Could you please somehow get the exception stack trace. This can be obtained 
from the DDMS tool in the Android SDK, or use an app called SendLog from the 
Android Market, make sure "raw" is selected as the log type and email it to 
riverniall@gmail.com

Thanks!

Original comment by riverni...@gmail.com on 3 Oct 2010 at 1:11

Added labels: Component-Client, Milestone-Release0.0.4, OpSys-Android, Usability

GoogleCodeExporter commented 9 years ago

Hi - I've sent both logs from ddms and sendLogs to the email you specified late 
yesterday.  Took a while to get the USB drivers working to enable ddms.

Original comment by mchun...@gmail.com on 4 Oct 2010 at 8:58

GoogleCodeExporter commented 9 years ago

I have received the logs and replied to your e-mail. This issue may end up 
getting merged with issue 2 as I feel rewriting the map code may fix this 
problem.

Original comment by riverni...@gmail.com on 5 Oct 2010 at 10:59

GoogleCodeExporter commented 9 years ago

I have found a fix for this issue. Apparently it is a problem in the Google 
Maps API on certain devices. I have found a workaround for this issue. It is 
not pretty, but it will have to do. This workaround will be seen in the next 
version of the application.

Original comment by riverni...@gmail.com on 28 Oct 2010 at 12:47

GoogleCodeExporter commented 9 years ago

Work on this issue has started and the priority has been bumped up to 'high'.

Original comment by riverni...@gmail.com on 28 Dec 2010 at 10:43

Changed state: Started
Added labels: Priority-High
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

This issue has been fixed in r52.

Original comment by riverni...@gmail.com on 24 Jan 2011 at 11:06

Changed state: Fixed