BT GNSS Mobile based in Raspi

[Corsair63]

hi all,

I've been facing quite a lot of problem to get the GNSS data from mobile in Raspi OCPN (5.8.4-3), because this operative system is not user friendly at all, so if I could help with my experience should be fine.

I'm using Pixel 8 Android 14 with app "Bluetooth GPS output", I have this device as a GNSS of emergency, just in case.

These are the parameters of connection:

Pi@S-212:~ $ neofetch
Pi@S-212
-------------
OS: Debian GNU/Linux 12 (bookworm) aarch64
Host: Raspberry Pi 4 Model B Rev 1.5
Kernel: 6.6.22-v8+
Uptime: 21 hours, 39 mins
Packages: 1659 (dpkg)
Shell: bash 5.2.15
Resolution: 1920x1080
DE: LXDE
Theme: PiXflat [GTK3]
Icons: PiXflat [GTK3]
Terminal: lxterminal
Terminal Font: Monospace 10
CPU: (4) @ 1.800GHz
Memory: 742MiB / 7808MiB

# I've done the configuration steps as root, because some of these commands are not accepted as normal user.

Pi@S-212:~ $ su
Password:
root@S-212:/home/Pi# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

root@S-212:/home/Pi# hcitool scan
Scanning ...
xx:xx:xx:xx:xx:xx Pixel 8 Pro
yy:yy:yy:yy:yy:yy A-BBBB

#keep above data

root@S-212:/home/Pi# sdptool browse xx:xx:xx:xx:xx:xx
Browsing xx:xx:xx:xx:xx:xx ...
...
# it would be a lot of services, but the important one is below
...

Service Name: SPP slave
Service RecHandle: 0x10011
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 28 <----- Important ch. number
Profile Descriptor List:
"Serial Port" (0x1101)
Version: 0x0102

root@S-212:/home/Pi# rfcomm bind "Pixel 8 Pro" xx:xx:xx:xx:xx:xx 28

root@S-212:/home/Pi# exit
exit

Pi@S-212:~ $ rfcomm
rfcomm0: xx:xx:xx:xx:xx:xx channel 28 config [tty-attached]
rfcomm1: zz:zz:zz:zz:zz:zz channel 1 config [tty-attached]
Pi@S-212:~ $

and now in OCPN settings - connections you must select:
- "new connection"
- Data port: /dev/ttyS0
- Protocol: NMEA 0183
- baud rate: 4800
- List position: the one you consider
- User comment: a user-friendly name for your device to clearly recognize it.

of course, any suggestion for doing it better will be welcomed, at least has worked for me.