Closed GoogleCodeExporter closed 9 years ago
I have the same kind of problem but OSMTracker only freezes for a long period.
About 1-3 mins.
Original comment by kaiwas...@gmail.com
on 3 Sep 2010 at 2:45
my galaxy s freezed also after 1-3 minutes.
Original comment by sal...@gmail.com
on 18 Sep 2010 at 2:22
Could be a samsung problem. Let's wait for froyo (23.09.)
Original comment by Maximili...@gmail.com
on 18 Sep 2010 at 9:04
Has the Froyo update changed something ? This kind of problem is particularly
difficult to diagnose as you can imagine :-(
Original comment by nguillau...@gmail.com
on 4 Oct 2010 at 4:57
Froyo is not [u]official[/u] released for Galaxy until now. I will report if
the crashes still present or not.
Original comment by kaiwas...@gmail.com
on 4 Oct 2010 at 9:31
This weekend I installed the voodoo lagfix on my phone and now osmtracker seems
to work. I guess it's a samsung problem. Maybe the froyo update will solve it.
For now a lagfix seems to be the best option.
Greetings Maxi
Original comment by Maximili...@gmail.com
on 4 Oct 2010 at 4:15
Still have sometimes problems with crashing records (froyo).
Is there the possibility to stop tracking a certain track from main menu? As
when a crash happens the track is still in 'recording' mode and I can not start
a new track. As soon as I continue the track (only possibility [at least to my
knowledge]) I crashes again. Only solution for me was reinstalling the whole
OSMTracker.
Original comment by bjoernbr...@gmail.com
on 22 Jan 2011 at 11:26
Hi,
the next release (im' not sure, when it will be released) has the option to
stop and restart every track when long clicking the track in the track manager
view.
This will help avoiding to reinstall OSMtracker but doesn't help us to figure
out the cause of this issue.
Could you provide some additional info (like logcat output)?
best regards
Matthias
Original comment by matthias...@gmail.com
on 23 Jan 2011 at 3:01
Hi,
I tried tracking today. I had no problems with OSMTrack Ver. 0.5.3 on my Galaxy
S since I am using Android 2.2.1. I guess the crashes depend on some bugs in
the crappy Samsung Software (2.1 and 2.2).
Original comment by Maximili...@gmail.com
on 10 Feb 2011 at 4:35
Hi Maximilian,
thank you for the information that the Android update seems to fix this, so
I'll mark this as "WontFix".
A short summary for all others:
This seems to be a Samsung Galaxy S specific issue that affects Android
versions prior 2.2.1
If there's no update to Android 2.2.1 for your Galaxy S it could possibly be
solved by installing something like Voodoo lagfix (see
http://project-voodoo.org/ for details) to your phone.
best regards
Matthias
Original comment by matthias...@gmail.com
on 28 Feb 2011 at 11:46
Original issue reported on code.google.com by
Maximili...@gmail.com
on 19 Aug 2010 at 5:09