Originally Posted by bdbcat
There are no widespread reports of waypoint artifacts. I've never seen one except on a crash, where the navobj changes file gets scrambled.
What are your user interactions that provoke these attacks? Maybe some others can duplicate, and we can get to the root cause.
It first occurred when when I uploaded the attached route
, my proposed route
later this summer.
I have a lot of very
detailed maps to go along with this area because of the inherent hazards of 15-20ft tides and narrow passages(300ft at the narrowest@ 6-9 knts current
It's my vague feeling that O
or my processor doesn't like large amounts of data... I have problems sometimes with the quilting not showing the correct level of data, with blank areas of larger scale maps covering smaller scale ones, I will try to qualify and quantify so we get away from touchy feely stuff.
Here is my total activity:
link to chart folder with all charts
result: dead Opencpn
, dead upon removal
solution: kill the opencpn
.config file and re-install apk
result: everything A-OK
load folders that contain individual maps one at a time(painfully because of small folders and fat fingers, as discussed)
result: mostly A-OK, scrolling with so much data present, is slower, but manageable, will have to play with quilting and maps to display to fine tune, and paring down available data.
create route ~800nmi with 130ish waypoints on laptop
, export to Google
download on tablet the GPX attached
upload into O
all is good, until artifacts start to show up on map, and continue to get worse with every session, not debilitating yet, but annoying.
out for a spin, mainly to test on-board gps
functionality and battery
Result: tracked like a champ with accuracy to about 20-30'
only used ~10% in about 30min of continuous run time.
discussion: I really need to quantify this number under the harshest conditions so I can have a good baseline to go by on the boat
, although the reality is, that it should be charging
any time possible, if being used for navigation
the only other thing I did was use the native app manager to move O to the "sdcard", whicch as far as I can tell didn't happen.
Maybe i'm doing too much at once... I will go back and try to replicate the big crash and the artifacts, and define these bugs individually, methodically.
I found this in the log
Loading World Chart Q=0 in 0 ms.
GSHHS World chart files have wrong version. Found 0, expected 210-220.
Loading World Chart Q=2 in 0 ms.
Warning: Color not found UINFR
Loading navobjects from navobj.xml
Error: Impossible to set permissions for the file '/mnt/sdcard/.opencpn/navobj.xml.5' (error 1: Operation not permitted)
Error: Impossible to set permissions for the file '/mnt/sdcard/.opencpn/navobj.xml.4' (error 1: Operation not permitted)
Error: Impossible to set permissions for the file '/mnt/sdcard/.opencpn/navobj.xml.3' (error 1: Operation not permitted)
Error: Impossible to set permissions for the file '/mnt/sdcard/.opencpn/navobj.xml.2' (error 1: Operation not permitted)
Error: Impossible to set permissions for the file '/mnt/sdcard/.opencpn/navobj.xml.1' (error 1: Operation not permitted)
Done loading navobjects
look suspicious? maybe because I "moved" it to the sdcard.
I will kill all traces of O
and then try to replicate.
P.S. the picture is all Artifacts. they seem to multiply when zoomed in. That is max zoom.