[TOHLORA] LoRa chip for Meshtastic/Meshcore/Reticulum - Discussion

I’m willing to investigate the option to produce a LoRa TOH for the 2026 Jolla but would like to discuss this first before designing the hardware.

Notably, I have seen this: COTS-LoRa 3D-printed TOH shell - #32 by BH

But I think it is worthwile to put a chip on a PCB and connect via pogo-pins and have an internal antenna for sleek design.

Here is my idea:

  • slim back case that basically integrates well with the camera bumper, from eye-balling it I think this should be enough.
  • custom PCB with pogo pins and some SX12xx LoRa chip wired directly to the Jolla
  • internal antenna should be good enough for most use cases (if you need higher +dBi this module is probably nothing for you anyways)
  • Meshcore firmware that runs natively on the Jolla as proof of concept (disclosure: I maintain meshcore-linux currently)

What do you think?

Hi! I’m going to be completely honest, I didn’t know about meshcore before and didn’t immediately know what to use it for :sweat_smile: Checked and it looks quite cool! But I don’t yet know who I would use it with :thinking: But what I quickly tried to learn about the project, I think that TOH would bring value to the project as everyone basically carries their phones 247. So as a summary, I think very cool project, but I don’t know if I would use it personally as I don’t know if I would get any benefits out of it. But egg/chicken dilemma, we need people to use it to have benefits. If price isn’t too high, I might buy it anyway for support purpose, but no guarantee there :slight_smile:

Sounds great, I definitely would get one.

I like meshcore a lot and prefer a stand alone most of the time. But a smart little extra companion would be great. Since I don’t want to use my phone for serious business an internal aerial will be just fine.

Ah: I forgot about Meshuga Core. Works for me. But… I am a stand alone guy (T-Deck+ Wadamesh).

I would be a fan of this. Can make it work with Indra.

Sounds like an interesting idea! Would it be possible to also support Meshtastic?

Just saw this: https://www.seeedstudio.com/Wio-Tracker-L2-Pro-for-Meshtastic-p-0000.html

i think an open source system like meshtastic is really great to use TOH for. In the past we used to have amateur radio (HAM) that has proven very valuable at times of disasters like the 1953 flood in the Netherlands. NOw that is really on the decline. Mashtastic may replace its role. I am an electronic designer and would like to get involved in such project.

What does exist as software natively for Meshcore on Jolla/sailfish ?

I installed Meshuga core and just get a blank screen, it doesn’t work for me…

Could you please run it from the terminal and check the output?
sailjail -p harbour-meshugacore.desktop /usr/bin/sailfish-qml harbour-meshugacore

constructing /run/firejail/mnt/privileged:  ...
mounting /run/firejail/mnt/privileged @ /home/defaultuser/.local/share/system/privileged
hiding /run/firejail/mnt/privileged
Warning: /usr/bin/bwrap was not disabled
[D] unknown:0 - Using Wayland-EGL
library "libselinux.so" not found
Could not open module param file '/sys/module/mali_kbase/parameters/large_page_conf'
[43246.422289] (sailfish-qml) [MEMPROF] Memory instrumentation via debugfs enabled
[D] unknown:0 - Got library name:  "/usr/lib64/qt5/qml/io/thp/pyotherside/libpyothersideplugin.so"
[W] unknown:99 - file:///usr/share/harbour-meshugacore/qml/harbour-meshugacore.qml:99:5: Type MainPage unavailable
         MainPage {
         ^
[W] unknown:60 - file:///usr/share/harbour-meshugacore/qml/pages/MainPage.qml:60:9: Type MapTab unavailable
             MapTab {
             ^
[W] unknown:3 - file:///usr/share/harbour-meshugacore/qml/pages/MapTab.qml:3:1: module "MapboxMap" is not installed
     import MapboxMap 1.0
     ^

Missing library. But according to pkcon they are installed:

[root@ defaultuser]# pkcon search libselinux
Searching by details
Finished
Installed   	libselinux-3.7+git3-1.8.2.jolla.aarch64 (installed)         	SELinux library and simple utilities
Available   	libselinux-debuginfo-3.7+git3-1.8.2.jolla.aarch64 (jolla)   	Debug information for package libselinux
Available   	libselinux-debugsource-3.7+git3-1.8.2.jolla.aarch64 (jolla) 	Debug sources for package libselinux
Installed   	libselinux-devel-3.7+git3-1.8.2.jolla.aarch64 (installed)   	Header files and libraries used to build SELinux
Available   	libselinux-static-3.7+git3-1.8.2.jolla.aarch64 (jolla)      	Static libraries used to build SELinux
Available   	libselinux-utils-3.7+git3-1.8.2.jolla.aarch64 (jolla)       	SELinux libselinux utilies
Available   	libselinux-utils-extra-3.7+git3-1.8.2.jolla.aarch64 (jolla) 	SELinux libselinux extra utilies
Available   	python3-libselinux-3.7+git3-1.8.2.jolla.aarch64 (jolla)     	SELinux python 3 bindings for libselinux
[root@ defaultuser]# pkcon search pyotherside
Searching by details
Finished
Installed   	pyotherside-qml-plugin-python3-qt5-1.5.9+git4-1.6.1.jolla.aarch64 (installed)	Asynchronous Python 3 Bindings for Qt 5

Have you PureMaps installed? If not, could you please try installing it?

I did, actually I did not included this part as well:

library "/vendor/lib64/egl/mt6858/libGLES_mali.so" needed or dlopened by "(unknown)" is not accessible for the namespace "(default)"
library "/vendor/lib64/egl/mt6858/libGLES_mali.so" ("/vendor/lib64/egl/mt6858/libGLES_mali.so") needed or dlopened by "(unknown)" is not accessible for the namespace: [name="(default)", ld_library_paths="/usr/libexec/droid-hybris/system/lib64:/system/lib64:/vendor/lib64", default_library_paths="/system/lib64:/system_ext/lib64", permitted_paths="/system/lib64/drm:/system/lib64/extractors:/system/lib64/hw:/system_ext/lib64:/usr/libexec/droid-hybris/system/lib64:/system/framework:/system/app:/system/priv-app:/system_ext/framework:/system_ext/app:/system_ext/priv-app:/vendor/framework:/vendor/app:/vendor/priv-app:/system/vendor/framework:/system/vendor/app:/system/vendor/priv-app:/odm/framework:/odm/app:/odm/priv-app:/oem/app:/product/framework:/product/app:/product/priv-app:/data:/mnt/expand:/apex/com.android.runtime/lib64/bionic:/system/lib64/bootstrap"]
library "/vendor/lib64/hw/mt6858/mapper.mediatek.so" needed or dlopened by "(unknown)" is not accessible for the namespace "(default)"
library "/vendor/lib64/hw/mt6858/mapper.mediatek.so" ("/vendor/lib64/hw/mt6858/mapper.mediatek.so") needed or dlopened by "(unknown)" is not accessible for the namespace: [name="(default)", ld_library_paths="/usr/libexec/droid-hybris/system/lib64:/system/lib64:/vendor/lib64", default_library_paths="/system/lib64:/system_ext/lib64", permitted_paths="/system/lib64/drm:/system/lib64/extractors:/system/lib64/hw:/system_ext/lib64:/usr/libexec/droid-hybris/system/lib64:/system/framework:/system/app:/system/priv-app:/system_ext/framework:/system_ext/app:/system_ext/priv-app:/vendor/framework:/vendor/app:/vendor/priv-app:/system/vendor/framework:/system/vendor/app:/system/vendor/priv-app:/odm/framework:/odm/app:/odm/priv-app:/oem/app:/product/framework:/product/app:/product/priv-app:/data:/mnt/expand:/apex/com.android.runtime/lib64/bionic:/system/lib64/bootstrap"]
Error: ../../src/firejail/main.c:183: clear_atexit: EUID_ROOT:seteuid(root): Operation not permitted

So there is an issue with permissions of that jail, that package is installed as well (libGLES)

Neither selinux nor GLES are the issue here. You are missing the MapboxMap qml plugin.

I’m developing an app for Reticulum, and I’ve got Bluetooth RNodes support up and running. But this project is really interesting. I might consider porting the firmware for this TOH.

Thanks, found it on CHUM and installed it. The app now opens and asks for my private key and so on.

@cypherpunks why Meshuga Core code is not available like happens with Indra? I know, you even tell using it at our own risk, so not a reprimand, just a curious question. It could be a honeypot or could be a genuine app, in the description is open.

There are several issues with Openrepos system. I find myself safer with the Jolla Store, Harpoon (which was vibe coded too, but..) or CHUM, which has better basic requirements regarding the licence, origin, etc. In that order. Also happens that is another one man operation, there was the PHP bug, and then he was on holidays, so, here we are. Nothing against him, actually thanks to him for his work. But more and more I am questioning if that’s the way to go. I guess in a small ecosystem, is what it is, but not the way to grow IMO.

  • Is it better a vibe coded app, with the licence, code, and building process open to everyone on Codeberg, Github, Gitlab and being grabbed in an obtainum-like way with harpoon?
  • Or an obscure system, breaks for weeks, you install a repo which in my understanding could potentially replace important stock apps, the code is nowhere to be seen, trust me give me your private key… because?

PS: On meshcore app on Android, I can export the private key, but the private key is on the device, so, it maybe ok that I need it here or not, how I can tell?

I opened the RPM and checked. Nothing looks fishy with a quick eye. I can see a couple of python libraries and QML code. I am a rookie and was not aware of this script language to make apps, but is quite readable. Probably the issue with the key can be sorted out in different ways, as using the secure storage of the OS and/or try to operate the device as the other clients I tried which operate issuing commands to the companion directly.

And to add, still don’t get why that is not on a public repo doesn’t even need to be opensource, could be source available, otherwise if paid and closed has to go through the Jolla Store vetting.

As result, I have removed Openrepos from my phone, checked that removing the webview required from Whisperfish will break the system, so… not sure if I will eventually reinstall it. Found some of the apps that come from there “harpoonable” like Sailfin, others like the protonmail-bridge unfortunately, gone. Will not consider again Openrepos as adequate to use.

It is available the moment you install it. :grinning:
It’s 100% Python and QML, means you can inspect the actual code that running on your phone.