Georg Lukas

Thanks, that change improved something. Now it will print a garbage line, stay there for a second, then print the bottom two thirds of the kitty demo image: 

That's an excellent question. I've checked the [supported NMEA sentences](http://aprs.gids.nl/nmea/), and none of them, not even [`$PNTS`](https://www.manualslib.com/manual/450827/Alinco-Ej-41u.html?page=23) feature any symbol information. Maybe this is just a misunderstanding left-over?

The timestamp is optional, and normally the code should be able to properly parse the position packets it generates. Can you provide example strings?

Looks like some magic in raspbian prevents wifi from going up if you have usb0 configured. Adding this to `/etc/network/interfaces` should help: ``` auto wlan0 allow-hotplug wlan0 iface wlan0 inet...

I am planning a "full customization" feature, together with some reworking of the dice UI... however my time does not permit it currently. Please stay tuned :-)

Hi scoute-dich. thank you for the work, I'm actually interested in a material design update, as well as in making the number of dice dynamic based on the screen width...

I can provide the respective screenshots, but I don't know the process to add them to the f-droid metadata. I suppose this is something that needs to be addressed in...

After verifying that the NX300 uses a [TI TSU61111a](http://www.ti.com/lit/ds/symlink/tsu6111a.pdf) USB multiplexer, and that it supports resistor-based port switching, I was brave enough to attach a USB-OTG-UART cable, and tested **150K**...

I also tried this approach on the NX500, but it doesn't even put anything into dmesg :'(

Sorry for the confusion. This is not a real OTG cable of course, it is a micro-USB connector soldered to a breakout board, with actual resistors connected. It was prepared...