GPS-Sport ForenRun.GPS SoftwareForce close problem
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von1>Letzte Seite
marcvh 19.03.2010 15:44:22 UTC

Log not clean

Yeah, it wasn't a very clean log, since it was after the failure that I installed log collector and some other stuff attempting to troubleshoot. I'll see if I can get a better log when it happens next. Thanks.
admin 19.03.2010 09:30:26 UTC



We received the Android device log you sent! Thanks!

Unfortunately it does not contain a stack trace or something similar definitely showing the cause of the crash.

Some interpretations:

03-18 23:08:13.087 E/vold ( 48): KillProcessesWithOpenFiles /sdcard

Seems that the SD card has been disabled (this happens for instance when you connect to USB and the USB connection type is not set to "None").

Since Run.GPS needs the SD card (it has open files), Run.GPS is killed in such a case ...


03-18 23:08:13.178 W/AudioSystem( 142): AudioFlinger server died!

Problems with the Audio system: I often have this on my Motorola Milestone with Android 2.0.1 ... I have to restart the device after that because the audio subsystem crashes (no sounds, no music).

03-18 23:06:13.647 I/ActivityManager( 70): Low Memory: No more background processes.

Yes this too could be the reason why Run.GPS is killed, but the protocol does not show further information about that.









marcvh 19.03.2010 07:21:03 UTC

Me too!

I experience the same issue on my Nexus One. Sent the log contents to info; hope they help give some insight. Thanks!
admin 26.01.2010 15:37:19 UTC



I have received the log - thank you! This problem should be solved by the new 2.3.5b release, but not absolutely certain because this error occors very seldom (we could reproduce this on our Droid). We're currently doing heavy testing to see if the error reoccurs.
mbroeckelmanpost 25.01.2010 16:59:55 UTC



I restarted my phone, but the problem remains, so I just sent you a copy of the log. Thanks for checking on this so quickly!
admin 25.01.2010 10:34:21 UTC



We will check this out. We did not have the problem on our test devices (which include Droid). Did you try to restart your device? Maybe some old process hangs?

Could you please also try to send us a crash report?

These are the steps to do this:
1) Install the free Log Collector from Android Market
2) Wait until the app crashes
3) Then start Log Collector and send the log to info@esymetric.de

Thanks!

mbroeckelmanpost 25.01.2010 08:20:14 UTC

Force close problem on new version

My phone (Motorola Droid) installed the newest update for Run.GPS lite a couple of days ago, and since then, every time I start the GPS (not when I start the program, but when I press the button to start tracking location, time, etc), I receive the following message "The application Run.GPS Trainer Lite (process de.esymetric.rungps_lite) has stopped unexpectedly. Please try again. I have tried to re-start the program several times and have even uninstalled and reinstalled it, but still receive the same message. Is this a bug in the newest update? If so, will it be fixed soon? Or is there something I need to do differently on my phone with the newest update?
Erste Seite<Seite1von1>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung