alp@vilnius: ~ up since 2019 · Vilnius Download cv.pdf

← ALP-OS

alp ~ $ work the-job

When it was not the firmware

A lot of firmware work happens around the code. I’ve traced about 150 support cases to a root cause, often showing with data that the firmware wasn’t at fault, and driven about 140 release tickets.

about 140release tickets driven, from base firmware to app builds

This is the work around the code at Teltonika since 2022. In that time I’ve made 903 commits, implemented about 567 tickets, investigated about 313 more, and driven about 140 release tickets.

Tickets by my role, 2022–2026

On the platform maintainer rotation, I answer the questions that QA and support bring to the firmware team. Plenty of those end with “the firmware is fine”. That answer only counts if there’s data behind it.

Releases

I own releases on the tracker platform: five base lines, about 15 customer branches, experimental builds and mobile app builds. Each release comes with notes telling QA what to test. I carry base updates and cherry-picks across the customer branches, and I cancel and redo a release when QA results call for it. One base release carried 53 tickets. I also added a CI check that blocks a customer release if its firmware entry is missing.

Support

I’ve answered about 150 support cases with a root cause found in device logs.

In one case an ACK went missing. I rebuilt the test traffic against my own TCP server. The device sent two messages, and the server received them as one 1,388 B block. The server’s parser was the problem, and I suggested splitting messages by their length field.

The device sent two messages and the server read one 1,388 B block, so its parser caused the missing ACK A support case I rebuilt with my own test: a record every 30 s and a command every 5 s, sent to a test TCP server. As tested: the device sends message 1 and message 2 as two separate sends. The server reads both in one 1,388 B block. Its parser takes the block as one message, the ACK goes missing and the link closes. Proposed fix: the parser reads the length field and splits the block into message 1 and message 2, and each one gets its ACK. The device was not at fault. QA fixed 2 problems on their side and the tests passed. The widths of the two messages inside the block are not drawn to scale. TEST LOAD · a record every 30 s, a command every 5 s, test TCP server DEVICE SENDS SERVER READS PARSER AS TESTED · one read taken as one message message 1 send 1 message 2 send 2 1,388 B in one read message 1 + message 2 parsed as one message no ACK, link closed PROPOSED · split the block by its length field message 1 send 1 message 2 send 2 msg 1 msg 2 1,388 B, cut where the length field says message 1 → ACK message 2 → ACK The device sent both messages separately. QA fixed 2 problems on their side and the tests passed. Message widths inside the 1,388 B block are not drawn to scale.
The device sent two messages and the server read one 1,388 B block, so its parser caused the missing ACK

In another, a reported 1.5–2 minute clock error wouldn’t reproduce on two modem types and many SIMs. The evidence pointed to the operator’s network time.

Networks and vendors

A carrier NAT that forgets devices after 15 quiet seconds became half of another write-up. One escalation covered thousands of devices on one network, and forcing 4G with manual band selection solved it.

When a problem might be inside the modem, I build the case. I captured the modem’s internal logs on the bench and sent them to the vendor. One case took months of back and forth, and the fix reached the customer in a base update. I also turn vendor advice into firmware work, like a work item for faster switching between 2G and 4G.

Estimates

I’ve written at least 25 research documents with effort estimates, from 30 h to 332 h. The dual APN estimate came to 116 h. It showed that only one TLS session fits in RAM, and the customer accepted a design built around that.

Conclusion

About 150 support cases with a root cause, about 140 release tickets, at least 25 estimates, and about 567 tickets implemented.

“Not our bug” is a finding too, and it needs the same proof as a fix: a rebuilt test, a trace, a modem log.

Tags release modem network field-bug