OpenCPN for Android Beta test 4.1.718

[joel383]

7 days until GO time... I will try to report back before I leave on my big trip, but I'm having the same crashing issues others are having.

Samsung galaxy tab 3
Android 4.4.2

[bdbcat]

joel...

What crashing issues, specifically, please?

Thanks
Dave

[bdbcat]

jp...

re:
"I tried to use AO in nav condition but I was unable to get a track."

Known bug, fixed for next Beta.

Thanks
Dave

[Roel Smidt]

Originally Posted by Hans Fix

Hi developers,

Thanks for the good work, although I have an issue to report.
Tablet: Asus transformer TF700.
I am using waypoints which I download from Nautin.nl, they also provide icons with them.
On my telephone, it is all working, icons in directory UserIcons and everything shows perfect.
On the ASUS it does not work, or in fact most of the time it does not work.
When does it work? Well I discovered that when I just had a look in the usericons directory with the file manager, and directly after it I start up OA, they are shown! If I don't open the directory in the file manager only the rounds are shown (indicating no icon available).

Whatś happening, what am I doing wrong, or what is my tablet doing wrong?

Hi Hans,

I also use your/Nautin's splendid UserIcons and they show up fine in both my phone (Samsung S7710) and my tablet (Samsung Galaxy Tab 7.7). No need to look first in the directory UserIcons. So your UserIcons work perfectly!

Or, to be precise, did work perfectly...

Because I made the wise decision to delete my installed charts in order to completely re-install them. And now every time I try to "add a chart-directory", O crashes...

Luckily the weather today in our country is just fine to spend the whole day figuring out what the heck I did /do wrong....

Roel

[bdbcat]

Roel...

Lets start by looking at the logfile...

Thanks
Dave

[Roel Smidt]

Originally Posted by citlab

Further observations on the "show grid" topic.

1) the same goes for AIS target outlines. See pics. On the top the outline is drawn, when on the bottom of the screen the outline dissappears.

2) Here is where it gets interesting. Both for the AIS targets and for the grid: the region where they show correctly is the physical top of the tablet, not the "rotated" top. All four orientations, i.e., the front camera side is good, the opposite is not.

Antti

Hello Antti,

I see you've got AIS working in OA. But how did you manage to get your AIS-receiver to talk to OA? I've got a Digital Yacht AIS100 USB receiver connected to my Samsung Galaxy Tab 7.7 and I just can't figure out how to set up a connection. I just don't get any serial ports to choose from.

I know the DY receiver is OK because it works fine when connected to O on my desktop computer and also when connected to my tablet running BoatBeacon.
On my tablet I use a Samsung USB OTG connector.

Any ideas? Anyone?

Roel

[Hans Fix]

Originally Posted by Roel Smidt

Hi Hans,

I also use your/Nautin's splendid UserIcons and they show up fine in both my phone (Samsung S7710) and my tablet (Samsung Galaxy Tab 7.7). No need to look first in the directory UserIcons. So your UserIcons work perfectly!

Or, to be precise, did work perfectly...

Because I made the wise decision to delete my installed charts in order to completely re-install them. And now every time I try to "add a chart-directory", O crashes...

Luckily the weather today in our country is just fine to spend the whole day figuring out what the heck I did /do wrong....

Roel

Hi Roel,

Thanks for the compliment about Nautin, we are doing our best. :-)
The icons do work on my phone, so I have no idea why they don't appear on my tablet.

I had almost the same problem adding the charts, after selecting them, they don't show up in the list, so I added the directory manually in the opencpn.conf,
almost at the end I added:
[Directories]
S57DataLocation=
InitChartDir=/mnt/sdcard/opencpn
GPXIODir=
TCDataDir=
[ChartDirectories]
ChartDir1=/mnt/sdcard/opencpn/cm93 2011
So perhaps you can try that.

regards
Hans

[Hans Fix]

Originally Posted by Roel Smidt

Hello Antti,

I see you've got AIS working in OA. But how did you manage to get your AIS-receiver to talk to OA? I've got a Digital Yacht AIS100 USB receiver connected to my Samsung Galaxy Tab 7.7 and I just can't figure out how to set up a connection. I just don't get any serial ports to choose from.

I know the DY receiver is OK because it works fine when connected to O on my desktop computer and also when connected to my tablet running BoatBeacon.
On my tablet I use a Samsung USB OTG connector.

Any ideas? Anyone?

Roel

Well I'm using a longer route:
AIS-receiver connected via a multiplexer to a BlueTooth module (dx.com a couple of dollars) that transmits to a service on my tablet, making the BT-stream available on a TCP-port. I can connect with a couple of apps at the same time to that BlueTooth to TCP service, e.g. iRegatta, WinGPS and OA. Works very good.
regards
Hans Fix

[Ptizef]

Originally Posted by bdbcat

jp...

re:
"I tried to use AO in nav condition but I was unable to get a track."

Known bug, fixed for next Beta.

Thanks
Dave

Thanks Dave and sorry for the repetition
JP

[Hans Fix]

Hi Dave,

Can I somehow debug the error I'm encountering with the UserIcons?
And is there a way to contribute to this project? I'm an experienced software engineer (also with Android software), so is it possible to also download a development environment and help with debugging issues?

regards
Hans Fix

[seandepagnier]

My guess as to why there are gridlines disappearing is because these lines are perfectly vertical or horizontal and the width is too low.

Maybe we can disable blending or smooth lines but depending on the driver, who know what will happen. The most reliable way would be to use fatter lines.

To verify this: could someone try switching to course-up mode (when the course is also not 0) so that the grid lines are rotated and see if now they are correct?

[seandepagnier]

Originally Posted by Hans Fix

Hi Dave,

Can I somehow debug the error I'm encountering with the UserIcons?
And is there a way to contribute to this project? I'm an experienced software engineer (also with Android software), so is it possible to also download a development environment and help with debugging issues?

regards
Hans Fix

It would be great if you can help debug. I want to get on it myself but I have a very slow connection so it's difficult to set things up, and I have no real android hardware. Maybe I can run android on a raspberry pi but it's not really my intention.

I think maybe opengl works on an x86 android build in the emulator but I didn't try it yet.

The arm emulator is very slow and doesn't support opengl (even software emulated)

Maybe you can also improve the development environment or documentation for how to build opencpn on android as I know this is a deterring factor for others. Basically if you clone the opencpn source code you will find a directory "buildandroid" which has some readme files explaining things. You could ask questions here if you get stuck.

[citlab]

Originally Posted by boat_alexandra

My guess as to why there are gridlines disappearing is because these lines are perfectly vertical or horizontal and the width is too low.

Maybe we can disable blending or smooth lines but depending on the driver, who know what will happen. The most reliable way would be to use fatter lines.

To verify this: could someone try switching to course-up mode (when the course is also not 0) so that the grid lines are rotated and see if now they are correct?

This theory would not explain why AIS target outlines do behave exactly the same way as the grid lines. Target outlines are drawn to all directions.

Antti

[citlab]

Originally Posted by Roel Smidt

Hello Antti,

I see you've got AIS working in OA. But how did you manage to get your AIS-receiver to talk to OA? I've got a Digital Yacht AIS100 USB receiver connected to my Samsung Galaxy Tab 7.7 and I just can't figure out how to set up a connection. I just don't get any serial ports to choose from.

I know the DY receiver is OK because it works fine when connected to O on my desktop computer and also when connected to my tablet running BoatBeacon.
On my tablet I use a Samsung USB OTG connector.

Any ideas? Anyone?

Roel

My DY AIS is connected to a serial to USB adabter that is connected to my sub-notebook pc. The pc runs O and sends AIS to a Bluetooth serial port. Pc and tablet are bt-paired . On the tablet I run "Connection terminal" to feed the bt data to the tablet internal tcp feed that O on the tablet reads. I have not succeeded to use the bt-spp on the O which would eliminate one link.

Antti

[bdbcat]

Ahoy testers...

Regarding OCPN crash on exit from hibernation of device:

I have not yet reproduced this fault on my tablets in a way that can be debugged. So I ask this:
If you experience this crash, please IMMEDIATELY do this:

1. Go to Android settings, and enable Developer Mode.
2. In Android settings, Developer Options, select "Take Bug Report".

3. Alternatively, if you phone is rooted, you may find and retrieve the latest Tombstone file, found in /data/tombstones.

It is important to capture the crash info right after the crash, since Android re-cycles the storage to avoid using too much space on crash reports.

4 Edit the Report
This Report will contain a crash dump, and stack trace, which will look something like this (with details altered):

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 28011, tid: 28031, name: opencpn.opencpn
    r0 563bdb68  r1 00000080  r2 fffffed8  r3 00000000
    r4 563bdb68  r5 563bdb64  r6 fffffed8  r7 000000f0
    r8 00000000  r9 00000000  sl 03000000  fp 00000016
    ip 00000000  sp 58ddee60  lr 4008e420  pc 40098104  cpsr 60000010
    d0  0000000000000000  d1  0000000000000000
    d2  0000000000000000  d3  0000000000000000
    d4  0069006f00720064  d5  00740051002e0064
    d6  0072007400780045  d7  0065007400630061
    d8  0000000000000000  d9  0000000000000000
    d10 0000000000000000  d11 0000000000000000
    d12 0000000000000000  d13 0000000000000000
    d14 0000000000000000  d15 0000000000000000
    d16 0000000000000017  d17 0000000000000000
    d18 0f0f0f0f0d0d0d0d  d19 0000000000000000
    d20 0f0f0f0f0d0d0d0d  d21 020202020f0f0f0f
    d22 0707070703030303  d23 0000001700000016
    d24 00f300f300f300f3  d25 00f100f100f100f1
    d26 00f100f100f100f1  d27 00fe00fe00fe00fe
    d28 0100010001000100  d29 0100010001000100
    d30 0000000100000001  d31 0000000100000001
    scr 60000010

backtrace:
    #00  pc 00018104  /system/lib/libc.so (__futex_syscall3+8)
    #01  pc 0000e41c  /system/lib/libc.so (__pthread_cond_timedwait_relative+48)
    #02  pc 0000e478  /system/lib/libc.so (__pthread_cond_timedwait+60)
    #03  pc 0005e03c  /system/lib/libMali.so
    #04  pc 0005da44  /system/lib/libMali.so
    #05  pc 0000e3d8  /system/lib/libc.so (__thread_entry+72)
    #06  pc 0000dac4  /system/lib/libc.so (pthread_create+160)

stack:
         58ddee20  598d1e60  
         58ddee24  5f50aba0  
         58ddee28  598d1e60  
         58ddee2c  589cf05c  /system/lib/libMali.so
         58ddee30  598d1e60  
         58ddee34  5f50aba0  
         58ddee38  00000000  
         58ddee3c  563bd740  
         58ddee40  563c4700  
         58ddee44  5e1754d0  
         58ddee48  589cf160  /system/lib/libMali.so
         58ddee4c  58937fd4  /system/lib/libMali.so
         58ddee50  5e4fc598  
         58ddee54  563c4700  
         58ddee58  5e1754d0  
         58ddee5c  5e4fc598  
    #00  58ddee60  563bdb68  
         58ddee64  00000000  
    #01  58ddee68  00000000  
         58ddee6c  563bdb64  
         58ddee70  563bdb68  
         58ddee74  563bdb68  
         58ddee78  589cf160  /system/lib/libMali.so
         58ddee7c  4008e47c  /system/lib/libc.so (__pthread_cond_timedwait+64)
    #02  58ddee80  00010000  
         58ddee84  563bdb60  
         58ddee88  563bdb64  
         58ddee8c  563bdb60  
         58ddee90  563bdb64  
         58ddee94  58938040  /system/lib/libMali.so
    #03  58ddee98  563bdb28  
         58ddee9c  00000000  
         58ddeea0  00000000  
         58ddeea4  58937a48  /system/lib/libMali.so
    #04  58ddeea8  00000000  
         58ddeeac  00000000  
         58ddeeb0  00000000  
         58ddeeb4  00000000  
         58ddeeb8  00000000  
         58ddeebc  00000000  
         58ddeec0  00000000  
         58ddeec4  00000000  
         58ddeec8  58ddef00  [stack:28031]
         58ddeecc  563bdb78  
         58ddeed0  58937a08  /system/lib/libMali.so
         58ddeed4  563bdb28  
         58ddeed8  58937a08  /system/lib/libMali.so
         58ddeedc  00100000  
         58ddeee0  563bdb28  
         58ddeee4  4008e3dc  /system/lib/libc.so (__thread_entry+76)
    #05  58ddeee8  563bdb28  
         58ddeeec  58ddef00  [stack:28031]
         58ddeef0  400c1f80  /system/lib/libc.so
         58ddeef4  563bdb78  
         58ddeef8  00000078  
         58ddeefc  4008dac8  /system/lib/libc.so (pthread_create+164)
    #06  58ddef00  58ddef00  [stack:28031]
         58ddef04  563bdb78  
         58ddef08  00000000  
         58ddef0c  00000000  
         58ddef10  00000000  
         58ddef14  00000000  
         58ddef18  00000000  
         58ddef1c  00000000  
         58ddef20  00000000  
         58ddef24  00000000  
         58ddef28  00000000  
         58ddef2c  00000000  
         58ddef30  00000000  
         58ddef34  00000000  
         58ddef38  00000000  
         58ddef3c  00000000  
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---

This is the (only) part of the report that I need to see.
The Bug Report will be fairly large, and I don't want you to spend the bandwidth uploading mostly useless data...


I'll keep trying, but it sure would help to see a stack trace from the crash as reported by BugReport/Tombstone.

In fact, this is the general procedure for reporting crashes on Android, and can be very helpful in diagnosing unexpected faults....

Thanks
Dave