OpenCPN for Android Beta test 4.1.530

[Ptizef]

Hi Dave

Z3 Compact A 5.0.2 no hardware key
menu bar OK but without icon
Jean Pierre

[barnakiel]

Acer Iconia

Nmea over wifi (tcp, router) and via the ethernet all work fine (gps + ais, in both scenarios).

Functionality: not sure why ais ship icons become gray, have to look up the manual. It looks odd when they start green then turn grey. They look dead even though they move.

b.

[barnakiel]

Waypoint attack may result from screen taps when we are trying to evoke the sleeping tool bar. I too am getting this, even though I have relatively small fingerprints.

Another idea possibly for Dave over the whole O spectrum: ship distance rings, which are custom spaced: is there any way to display an indicator distance number at the rings? Let's cal it ring distance labels? Would be nice and assuring.

b.

[spiv]

Hi Dave,

Galaxy Note 2, GT-N7105.
Android V4.1.2 rooted.
Screen size set to "Manual 230mm"

All seems to work ok for now.
I get an error every time I start up, selecting "No" starts O.
Tracks work Ok.
Have not tried routes as it gets too fiddly with fingers.
The pen doesn't work well at this stage. I can scroll with finger, not with pen.

[joel383]

Samsung galaxy tab 3
Android 4.4.2

Lots of room on the screen for navigation. I love it!


sent from my I-gloo

[Ido Nap]

Used the beta app on trip from holland to Bretagne last week.
App remained stable. Issues:
Routing is not a pleasant task as yet. The userinterface is not 'tab'friendly. Setting a mark at the right spot is difficult. Sometimes the app would keep scrolling by itself, seemingly trying to put a routepoint somewhere in the atlantic.
As routing is important for tripplanning and editing the route is something you'll do repeatedly on a multiday journey, I suggest that this feature gets some priority, before releasing a normal version of the app.
The constant demand for gps info drains the battery. On an android device, you only need accurate gps info when you're looking at the screen. (Unless you want to save your track)
If the gps use could be disengaged when the app is running in background, it would save battery life. I now did that manualy, but inexperienced users might need this feature.
Long tap on the screen gives a popup menu. That menu is now not useble when sailing in challenging wheater. You keep poking the wrong items.☺

That's all for now

Verstuurd vanaf mijn GT-P5210 met Tapatalk

[Wrong]

A helpful hint.

*Create your routes with a computer, then import the .gpx file into OpenCPN for android. Easier and faster.
*When creating routes in OpenCPN for android initially create a route with two waypoints. One each reasonably near your point of departure and destination. Employ the drag, insert and append waypoint functions to complete the route.
*To simplify managing routes, waypoints and marks later on make sure you name them as you go.

[Ido Nap]

I agree with your hint Wrong. Thanks for that.
However, using the android tablet version of OpenCPN, for me also means that I don't want to use the pc at the same time. I'd like to leave the pc at home.
Routing shouldn't be that difficult for the user. Look at how navionics handles it. I don'suggest autorouting, the way they offer. As an add-on at a later time perhaps?
But an easy clickable routing feature would be appreciated.


Verstuurd vanaf mijn GT-P5210 met Tapatalk

[Wrong]

Originally Posted by Ido Nap

I agree with your hint Wrong. Thanks for that.
However, using the android tablet version of OpenCPN, for me also means that I don't want to use the pc at the same time. I'd like to leave the pc at home.
Routing shouldn't be that difficult for the user. Look at how navionics handles it. I don'suggest autorouting, the way they offer. As an add-on at a later time perhaps?
But an easy clickable routing feature would be appreciated.


Verstuurd vanaf mijn GT-P5210 met Tapatalk

I have never, ever needed to create routes on my laptop underway. Have always known my itinerary long in advance of casting off, so access to an a.c. outlet for the p.c was no problem.

Creating a route in OpenCPN on an android is not difficult if you follow the suggestions in my last post. Practice is important though in order to develop the right 'touch'.

Leave the P.C. at home AFTER you've obtained a backup android device loaded with OpenCPN and identical routes.

[joel383]

A few more bugs: when editing routes sometimes phantom waypoints are set that are only viewable after the app is manually closed or tablet is restarted.

Sometimes when editing a route "O" seems to freeze up, but will resume partial functionality, although most features are available some are not... like long tapping a waypoint to bring up the menu. Menu pops up fine, but nothing happens when properties is tapped.

sent from my I-gloo

[joel383]

The second issue in the above post is actually what i think is leading to the first.

sent from my I-gloo

[joel383]

I totally agree with routing via computer... im planning on having 2 laptops aboard and 2 tablets also for my trip.

Here is what im talking about in the previous post with the help of screen shots:

First shot is route that i would like to add waypoint to.

Second shot i have long tapped on the route to add waypoint, uhhhmm no waypoint visable but O thinks there is one there, probably left over from precvious attemps.

Third i have inserted waypoint on the route, and move around to verify it is on route line. All looks good. Close app manually and reopen.

Fourth and fifth and sixth this is what i see... it is no longer attached to route, move around to verify. Delete waypoint. Hide offending chart for 100th time (why wont it stay hidden, resets when app is closed and reopened.) Close app and...

Seventh reopen O, facepalm, phantom waypoints not so phantom anymore.

Conclusion: ALL editing to be done on pc, need to set up easy wireless transfer between devices pc to tablet via wifi... any suggestions?

Thanks for all the hard work guys!

Android 4.4.2
Galaxy tab 3


sent from my I-gloo

[joel383]

Interesting though...
It appears as though it is still there... i will do more testing to better define this later.

sent from my I-gloo

[joel383]

Also, i have confirmed: with O running in the background, even with location manually turned off, device will not charge

sent from my I-gloo

[Ido Nap]

We seem to have different ideas about routing. Still: in a fully functional app on android you shouldn't need windows to plan your routes.
The power issue is something I detected as well. Charging via a lighter plug won't work with O running. I had to use the power converter and charge with a 220V plug.
That might be a samsung thing though. Same problem when running navionics.

About the screen image above: i don't get to see those purple blocks when runnjng O. Mine shows a yellow bar.


Verstuurd vanaf mijn GT-P5210 met Tapatalk