Messages

I totally agree, berkley! But you know, not everybody knows their best, so I was just thinking that there is a large market there for Menion, so if the iPhone users won't come to you, you need to come to them.  

Custom screens: amazing!! This is so great! Thank you!!! The tree included screens are great. I guess this is an area where a lot of users would be interested in submitting their own custom screens such that they can be included into the official Locus.

Congratulations  Menion - I think you have created a new arena with unlimited potential that will shoot Locus even further ahead of the rest of the crowd!

My brother has iPhone and was searching for a good GPS program. None of  the apps he pulled out from Apple's AppStore was not even close to Locus - of courses. Would you consider porting Locus to iPhone?

I have some intersting results (which are good new for Locus):
On a trip today, I used MyTracks directly to record my tracks. I had two recordings. Both caused the phone to hang! And now Locus was not invloved in the recording.

==> So this should actually prove that Locus recording is NOT the root cause of this issue. I have started thinking this is rather related to the GPS receiver and calculation of positions. It is a fact I have experienced after about dozens of recordings that the more often I store points, the sooner the phone hangs. I looked at the CPU load today: with Locus recording a point every 1s, the average CPU load was 20%, but CPU still running at minimum frequency 245 MHz. With recording a point every 10s, the load went down to 2%, but jumping up to 20% for every point (i.e. every 10 seconds). Is position calculation so CPU demanding that point writing can be interrupted and times out? Maybe this is why some users with other phone models do not experience this issue at all?

I have now set the sampling interval to 10 seconds and just have to accept that the phone will hang once in a while, but hopefully not that often.

I guess there is nothing more you can do with this issue, Menion, since this may be out of your control?

I have done a lot more testing. Here are the new results:
- I replaced the kernal to Cyanogen Mod 7 with no HTC Sense. ==> That made zero difference: Locus recording is crashing and phone goes completely dead just as before
- I also tried Settings/Track recording/"Use MyTracks" on. No difference. ==> Crashes just as often.
- On a trip yesterday I was watching the screen, could see the position and movement on the screen, then suddenly the message "Application Locus Pro does not respond" and the phone went completely dead. Battery out.
- MyTracks is writing the tracks to the internal memory, so the issue is not related to writing points to the SD card.

Last trip while running to work this morning, I started with Locus's own recording. Phone dead after about 5 minutes. Battery out. Changed to Locus recording with "Use MyTracks". Crashed after just some few minutes. Battery out again. Then started recording with MyTracks directly (not via Locus). No crash. But no conclusion based on just one trip. However, I used MyTracks recording a lot before I discovered Locus and never experienced any crash.

CONCLUSIONS:
- The problem is not HTC Sense related.
- It is directly related to recording through Locus, being with Locus's own recording or with Locus "Use MyTracks". As long as Locus is involved, the issue is there.
- I have given up recording with Locus. I have tried absolutely everything. I have to go back to MyTracks and do all recordings with MyTracks directly (not via Locus).
- With Locus being such a brilliant GPS app on everything else, this severe crash issue should be taken very seriously and resolved.

Recording with MyTracks is not a good solution, since it doesn't leave a live track on the screen.

===> Menion: will you look into this?

When app crashes, I normally do not see any dialog or error message. Sometimes the phone is dead when I try to turn on the screen. Sometimes I can turn on the screen, I can see the Locus map, but then the phone just stops responding. So it is not possible to start any LogCat program at that point.

I have not changed the ROM. But this week I will probably change to a new ROM with no HTC Sense. I am hoping that could make a difference. But that is not the correct way to solve such a problem. What about other users? I am curious if other people are having the same problem.

One thing I could think of: this could be connected to the process of writing a new track point to the SD card. If for some reason this writing is interrupted by another system routine, maybe Locus doesn't get the expected acknowledge of the write command it is stuck waiting. Any way you can control this or implement a write timeout or something?

Track points are written directly to the log on the SD card, right?
==> Would it be an idea to instead write track points to a temporary file in internal memory and then write the complete track to the SD card when the recording is completed (stopped) ? Can you control this?

This issue - phone hangs while recording a track - has been discussed here at the forum before. Several weeks ago Menion rewrote the recording code and it go silent on the forum after that. Is it really true that nobody else is experiencing hang issues? I can't believe it is only me having serious trouble? This issue drives me crazy. About one out of 3 recordings causes the phone to go completely dead and I have to take out the battery to restart the phone. I once saw this message on the screen as the last message from a dying device: "Application Lotus does not respond".

I have tested track recording during 4 weeks now.
Here ere are my observations:

- not temperature dependent: one person on the forum claimed Desire has a main board overheat problem. That is definitely *not* the problem here. With Locus not running, the phone has never hang even though it has been so hot (inside the car windshield on a sunny day) that I have got a warning message. With Locus recording, it has hang even with free air cooling and 0 degrees C.

- doesn't matter if Locus is installed in internal memory or on the SD card: I have rooted my Desire, so I have moved most apps to the SD card. I later moved Locus back into internal memory to see if it made a difference. 50MB free memory space. Same hang issue.

- doesn't matter if other GPS apps are running: I have tried all kind of combinations. Hang happens just as often even if no other GPS apps are running.

- it ONLY happens when Locus is recording a track.

This is most likely an OS problem, either an Android problem or HTC Sense problem.

I know Menion said some weeks ago that the recording code is not water proof and recommended to use MyTracks or other apps to do track recording. However, I do not find it interesting to use Settings/Track Recording/"Use MyTracks" since it doesn't leave a real time track line on the map, and I do not get the same great features as from Locus recording.

Locus track recording is such a rich, useful and key feature, and everything else is so perfect with Locus now, so it is really sad that this problem is still there. When I go flying, I use Locus for recording, navigation and guiding. It is then really serious that the phone hangs during the flight, and I have to struggle with taking the battery out and restart the phone. Last Saturday I flew 5 legs, and the phone went dead on two out of those 5 recordings.

Any hope for a better world here, Menion?

Agree. That would be very convenient!
+1

There is a funny error in Settings/Track Recording/Interval (seconds):
- if I go into the menu, set a new value, and press OK, the settings displays (in yellow) "xx m", i.e. METERS. Now, if I return to the map view and then go back into the menu settings, the field correctly displays "xx s" (seconds). If I just go into the Interval menu again and press Ok for the existing value, the settings menu again shows "xx m".

- The chart grid lines are so dimmed that they are really hard to see, even indoors. Outdoors no chance.

- Also, would it be possible to step up the font size of the text along the axis? Indoors not too hard - outdoors in sunshine hard to see.

My thinking was that since I can place next point precisely using map center, why shouldn't I also be able to move the middle point precisely? It is a good reason you are supporting precise placement of new points. Hence it seems a bit inconsistent to me that moving a point is done so unprecisely. Since you included this new feature of moving a point, I assume you thought it was a useful feature. And it is, but why don't do it just as precisely as placing new points? Moving a point with today's technique will guarantee that the new position will not be along the street you want to follow, but at some point nearby.  The result is that your new route gets a small leg to this point you actually do not want to go, and then back to your main route. I tried this a lot. creating a

Anyway, this was just my feedback. This is not an important issue for me.

Aaah, I see! I do have moved area selection when downloading maps, but I was not aware of that functionality for track points during creation.
There are three issues with this approach:
 1) you don't see exactly where you move the point to because of your finger tip .
 2) you have to be within the map area currently displayed on the screen.
3) it is hard to hit the point. If you miss slightly, you end up moving the map instead. Annoying!

 So may I suggest the following alternative (keep your current solution, just add this one):
- move the map such that the point you want to move is at map center (red cross)
- tapping the point today pops up a menu with two choices: the two track segments to this point. Add a new choice here: "Move point".
- moving the map will cause the point to stay at map center and you can place it exactly where you want.
- tap the red cross again to leave the point at the new position. (Since that is not very obvious, you could alternatively have a small pop up window that says "Place point". This pops up when you select the command "Move point" above. This would be just like the POI alert STOP pop up window).
 - placing the point at its new position will trigger the new route calculation.

This approach would have several benefits:
- much easier to hit the point
- you can place it accuractly at the new position
- you can move ithe point outside the current map area while still keeping the zoom level for accurate placement.

What do you think?

That is what I am doing. I have not saved the track yet. I am still in the creation mode.

1.6.1.7:
The new way of creating a track with routing is really great!
Menion - your comment to this release: "Also is very nice when you move with some middle point on already computed path."
What do you mean?

oh it's just ... start creating new track with this tool and let locus compute path for example for car for more parts. To be clear, start manual creating, start directions compute and draw three points. All will be connected together by computed path. and now move with middle one You should see recompute for parts ... I think it's nice

I am sorry, Menion, I still do not get this. I do not see how to move the middle point. I create and compute the route as you describe, and I put map center on the middle point. But - move? I tap the point and can choose the track segment. But there is no way to move it. Some time when I tap a point, it displays "working ...", but nothing is changed and the point doesn't move.

1.6.1.7:
The new way of creating a track with routing is really great!
Menion - your comment to this release: "Also is very nice when you move with some middle point on already computed path."
What do you mean?

Version 1.6.1:
- MyTrack tracks are now sorted correctly according to criteria. Thanks.
- Altitude verified and correct now. Thanks.
- I have no map issues as MaleSurf reports.