bareboat-necessities / lysmarine_gen Goto Github PK

Document suggested post install steps

Such as:

• WiFi country
• Locale/Time Zone
• OpenCPN plugin updates
• WideVine
• Disabling WiFi power saving
• Passwords
• Add-ons
• Safe power off with known Pi cases
• Audio set up
• HDMI set up
• WiFi hotspot vs cient
• Weather applet
• Bluetooth
• SignalK updates
• PyPilot notes
• Sensors (Env, IMU, etc)
• O-Charts (dongle or not)
• SDR notes
• Offshore features (Inmarsat, Iridium, Weather Fax, NavTex, Satellite Weather, SailMail/ WinLink, Weather Routing, Climatology, Radars, Weather GRIBs, Celestial Navigation, WindVane Pilot)
• Cameras set up
• Power Monitoring (Victron/Venus, etc)
• Engine Sensors
• Keyboard Layouts

Build arm32 (armhf) version of the os
This will have less issues and run on more hardware but will be extra support effort

More history on it (seems happen with touchscreens only and touch events)

https://bugs.launchpad.net/raspbian/+bug/1915131

X server is not supposed to crash regardless of what its client does.
So it is really a bug in x server.

In the bbn lysmarine image as a workaround the X Server is pre-set up to restart on crash.
So there is at least a workaround so release might have this bug as a known issue.

See OpenCPN/OpenCPN#2194

Like this:

if [ $LMARCH == 'arm64' ]; then
echo 'chromium --headless &' >>/home/user/.config/openbox/autostart
else
echo 'chromium-browser --headless &' >>/home/user/.config/openbox/autostart
fi

java crashes on start with armhf image when booted with arm64 kernel

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0xf5f3a828, pid=2548, tid=0xf5be5460
#
# JRE version:  (8.0_212-b01) (build )
# Java VM: OpenJDK Client VM (25.212-b01 mixed mode linux-aarch32 )
# Problematic frame:
# V  [libjvm.so+0x15e828]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid2548.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Aborted

As workaround do:

sudo apt install openjdk-11-jdk openjdk-11-jdk-headless openjdk-11-jre openjdk-11-jre-headless

sudo apt remove openjdk-8-jdk openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless

oeSENC USB dongle doesn't work on arm64

I get conflicting reports.
oeSENC with keys (certificates) do work.
USB key lock doesn't work for some people

Consider adding HackerFleet HFOS

https://hackerfleet.eu/

https://github.com/Hackerfleet/hfos

While the current distribution is set up with defaults which do not suffer from this issue
it's still should be noted as enhancement

See also:
https://trac.wxwidgets.org/ticket/18941

Well is up to open plotter to support it
the way it is designed and implemented

motioneye requires python2 but is installed with python3

Not a big issue for a first release but issue none the less.
Hopefully motioneye guys will make it python3 compatible in time
given there are number of pull requests submitted for them

motioneye-project/motioneye#1978
motioneye-project/motioneye#2013
motioneye-project/motioneye#1805
motioneye-project/motioneye#1629
motioneye-project/motioneye#1572

QtVlm menus do not work on touchscreen

https://github.com/VladimirKalachikhin/Galadriel-map

SdrGlut install script fails on compilation under armhf

Radio/RaceFastsdr.cpp: In function \u2018int setFilters(playData*, Filters*)\u2019:
Radio/RaceFastsdr.cpp:1199:45: error: invalid conversion from \u2018int\u2019 to \u2018liquid_ampmodem_type\u2019 [-fpermissive]
f->demodAM = ampmodem_create(0.5, mode, iflag);
^~~~~
Radio/RaceFastsdr.cpp:1199:50: error: too few arguments to function \u2018ampmodem_s* ampmodem_create(float, float, liquid_ampmodem_type, int)\u2019
f->demodAM = ampmodem_create(0.5, mode, iflag);
^
In file included from Radio/RaceFastsdr.h:11,
from Radio/Radio.h:11,
from Radio/RaceFastsdr.cpp:3:
/usr/include/liquid/liquid.h:5906:10: note: declared here
ampmodem ampmodem_create(float _m,
^~~~~~~~~~~~~~~
make: *** [: Radio/RaceFastsdr.o] Error 1

Sailcut on arm32 (armhf) fails to find shader

program lacks a fragment shader

Replace Xorg with Wayland at some point
not for initial release
but down the road

See

SignalK/signalk-server#987

Issue displaying fonts in java on arm32 build

Changing default passwords post install should be simplified with some kind of GUI

Use IMU input (ex from autopilot) in Stellarium to create real augmented reality app

See idea here

https://bareboat-necessities.github.io/my-bareboat/#_celestial_navigation

For inmarsat decoders mono needs to be installed manually using add-ons scripts

OpenCPN and gtk2 apps sometimes stop reacting to touch in menus/tabs/scrolls

Well it is a tough one.
It seems affects only gtk2 apps. And after some time they can recover from it.
GTK2 is dead. There were issues reported against it.

https://gitlab.gnome.org/GNOME/gtk/-/issues/3372

https://gitlab.gnome.org/GNOME/gtk/-/issues/945

Not just that one, multiple.
The issue seems doesn't exist in apps compiled with GTK3.
Since OpenCPN is still on GTK2 in raspberry OS
the issue still affects it.

There is a report with request to make OpenCPN Gtk3 based

OpenCPN/OpenCPN#2138

None of the fixes are expected to appear soon. So here are workarounds

There are workarounds though which make it not so bad.

1. evdev-rce (right click emulation) helps. As menus act same way on right click. So try to press for longer time

2. onboard keyboard for tabs and scrolls you can go into onboard keyboard. Click on mouse pointer key
   (tooltip of it says 'Toggle Click Helpers') and click on 'Activate Hover Click' button which is mouse with a clock icon
   second bottom right. In this mode you can perform your actions with touch and hover. After you done with it you likely want to disable 'Hover Click' though

3. GTK2 programs have the "hover not clicking" behavior on some windows until you move the window decorations then the content become clickable

For a cockpit touchscreen display you shouldn't get into scenario 2 unless you go into editing some settings which is not common underway anyway. I do not know any other raspberry pi distribution which would have solved it so far.

Stellarium fails to start on arm32 (armhf)

Unable to find an X11 visual which matches EGL config

While current implementation works
it can be done cleaner

udev rules for disconnect devices needs more work

Issue in upstream mopidy/mopidy-spotify#285

Realistically not a big deal anymore

You should be able to cast spotify or other audio from iPhone to bbn lysmarine
using shairport-sync which will be preinstalled and configured in the release.

Will release with this as a know issue.

wxtoimg from add-ons on arm64 kernel displays corrupted fonts

works fine on armhf

Add spotify support for 32-bit version (armhf) mopidy.
mopidy on armhf can support spotify

Just like https://github.com/LASER-WOLF/OnboardComputerSystem
has it

DeskPi Pro hardware issues do not give full speed with usb SSD.
Early released models of DeskPi Pro have hardware issues acknowledged by the vendor.
There is some workaround to make it work reasonably fast (still way faster than SD card)

See DeskPi-Team/deskpi#29

See

raspberrypi/userland#630 (comment)

Moitessier Hat 2 is not supported on arm64 by Moitessier Hat vendor

Thunar won't start from 'Files' desktop icon if Thunar settings app was run before it.
It's because Thunar settings leaves behind a running daemon which confuses 'onlyOne' script.

Workaround: Start thunar from app menu

Sound quality issues from phones jack.
Some distortion and reverb. Seems arm64 raspberry OS specific

Budgie doesn't render System Tray icons properly placing one on top of another sometimes

Freeboard-sk page doesn't load

qt4 app menus do not work with touch

see for example app boats

Budgie desktop crashes with touch

See
solus-project/budgie-desktop#2073

While it is allegedly fixed the fix still didn't make it into debian packaging for buster.

In some cases budgie desktop restarts itself in some cases it just leaves you with a desktop.

In that case BBN gives you ability to restart budgie by selecting an option (seconds desktop screen, the icon called
'Commands') and pick 'Restart Desktop' from the options. That's the workaround for touchscreen

See: OpenCPN/OpenCPN#2097

gtk3 app menus do not work with touch

example terminal app

Bluetooth support is too limited

1. Setting WiFi country
2. Setting Locale
3. Setting TimeZone
4. Setting Passwords
5. Own Vessel parameters

While it's not that important some plugins which are still not ported to arm64 could be used
for offshore sailing

WeatherFax, Weather Routing, Search and Rescue Patterns (SAR)

Really is known issue for OpenCPN team

Add JTides

See

https://github.com/cutiepi-io/cutiepi-shell

While I was able to implement a fix it required use of unreleased upstream libraries.

WxWidgets need to release version 3.2
and OpenCPN has to be compiled with it and with GTK3 support
(so do not expect a fix soon)

More on the fix and existing patch from me in the C++ code

OpenCPN/OpenCPN#2057

Realistically it's not a big usability issue on touchscreen as '+' and '-' icons do work.
Right click emulation work fine with bbn patched version of evdev-rce.
(which is more required for a touchscreen)

See also

https://www.meltemus.com/index.php/en/forum/qtvlm-application/119-qtvlm-pour-raspberry-pi-4-64bit

In SKWiz settings default port 3000 needs to be changed manually to 80 postinstall

Here is linked issue in raspberry pi OS

raspberrypi/linux#4162

on armhf image pypilot web dark theme is not initialised by default

See:
https://www.reddit.com/r/raspberry_pi/comments/lahsow/raspberry_pi4_8gb_seems_useless_as_media_player/glsi86w?utm_source=share&utm_medium=web2x&context=3

Someone just posted that gpu_mem set to 384 (no larger) solves the issue for them.