Forum: General Topics
Forums / General Topics / TMJ 0.6.1 crashed and corrupt in E51
| Subject: | TMJ 0.6.1 crashed and corrupt in E51 | |
rjshv 5:13 | I am using TMJ 0.6.1 on my Nokia E51. Yesterday I was tracking a route for about an hour and suddenly the program failed to respond to switch between views - graph to 3 graph to dials etc. After a few mins the program terminated. I restarted and connected to the BT GPS and tried again and same problem. I was checking out things in the 'Other Options' menu when it crashed again and it lost the Device code and Password. Now the program says 'Settings Incomplete!' and 'Please set your TMJ Device Code and Password on the Menu/settings... etc". Moreover the values in Track(1) screen are abnormal as follows: Avg Speed: 489108km/h , Distance: 360091km, Max Speed: 24769875km/h, Grad Min/Max: -90/+90 , Alt Min/Max: -462443885/957 The program still crashes when I connect to the BT GPS. Some of my settings are: Limit Track Size to.. points: 1000, Map Cache Size (Kb): 2048 I am going to uninstall and reinstall TMJ now. | |
Stephen 9:59 Location: Phone Model: | Hi, Did reinstalling help? I don't know what might have caused the crash, hopefully it was just a one-off! I had a similar thing happen on my SE W910i a few weeks ago, but as its only happened once in two years I just put it down to a freak bug (which *might* be due to the phone, rather than TMJ itself). One thing I've suspected in the past is if the program is installed on the phones memory card (rather than in its internal memory) and the phone gets knocked or dropped, this can temporarily dislodge the memory card and possibly corrupt any programs that are running from it. (Only a guess though - probably not related in your case)...? Stephen | |
rjshv 4:14 | I did uninstall and reinstall (latest from the web). But still the same problem occurs and I'm able to replicate it. There seems to be a pattern to it: Once the travelling speed on road reaches 100kmph and above, problem starts. First, under the Navigation menu, the gradient goes haywire with Gradient value of 90degree and Vert speed showing some ridiculous 9 digit numbers.. and keeps increasing rapidly until the numbers flow out of the box alloted for the display. At this stage, when we change the display to show analog dials, the display freezes and becomes distorted. The phone stops responding for a while and then the program terminates and exits. Crashes happen when speeds are at 100kmph and typically after 30mins or so. I'v used the program earlier for long durations without a problem. It must be something related to speed. Btw, I use a bluetooth GPS receiver. It works fine with other applications like gmaps. Any solutions? Thanks. | |
Stephen 12:36 Location: Phone Model: | That sounds very odd - I can't think what might be causing it!? Do you by any chance have NMEA logging enabled? If so could you email me the log file from around the time that it has happened, so that I can try and recreate the bug using your GPS data. Or if you don't yet have a log could you enable it (Menu/GPS/Logging...) and see if you can get it to crash again, whilst logging. When it begins to go weird could you also check the Menu/Display/View Event Log to see if there are any errors listed there. Also, what settings do you use for the following: - Units - Activity Profile - Tools/Speed Limits - Settings/Other Settings/Use Speed/Bearing from GPS - Settings/Other Settings/Apply Extra Altitude Smoothing Finally, how many points would be in the recorded track when it starts going weird - I'm wondering if its to do with the phone running out of memory... Cheers, Stephen | |
rjshv 14:52 | As you suggested I've enabled logging (NMEA Text, Daily). Units are as follows: Distance-Metric, Speed-KMH, Altitude-Feet, Vert. Speed- m/min, Lat/Long-DM'S" Speed Limiter: Maximum speed active-<unchecked> (disabled), Max-21 km/h, Min-18 km/h, Alert type- Single. Settings/Other Settings/Use Speed/Bearing from GPS- <unchecked> (disabled) Settings/Other Settings/Apply Extra Altitude Smoothing- <checked> (enabled) Include Gradient in Calc.. - <checked> (enabled) Or Maybe there's a problem here?: Limit track size to..points: 1000 Map Cache size 2048Kb From the last crash, there were around 63 points recorded successfully. I dont know if any where lost. The moment the program started to act strange, I enabled web upload and got these 63 into the web. Distance travelled had been around 9.5kms, and logging had been on for 11 mins. Speeds reached beyond 100 and the crash started. Let me know if anything else's to be done before I start off on the test. Thanks. | |
Stephen 18:27 Location: Phone Model: | Can't think of anything else at the moment. I had wondered whether you had maybe ended up with a really long track, but 63 points is perfectly manageable so I dont think its that! (The 'limit track size to ..1000.. points' should only come into play when the track gets really long, so shouldn't be an issue). One other thing, does your phone otherwise have plenty of spare memory? Might be worth restarting the phone before the test too... | |
(You must be logged in to post a reply to this thread)