Android App for logging and tuning (Tunerpro'ish for Android with live tuning)

[Muncie]

So ive just tried out CHATGPT 6 burnt through some credits and have the shell of an App up and running, heres the GPT Summary and my thoughts on it mixed in.

I’ve started putting together an Android tuning/logging toolbox for our Holden PCM projects and would appreciate some suggestions from people who have worked with this.
The aim is a simple phone-based tool for logging and making a few calibration changes while parked between test runs. My initial target is VX/VY $060A Enhanced, with OneROM fitted to the PCM. Transmission tuning and deeper development will stay on the laptop.
What’s working so far:
A native Android prototype called MCS Tuner, currently v0.1.1.
Opens TunerPro XDFs and BINs, and reads ADX definition information.
Basic scalar, flag and individual table-cell editing.
Preview before applying changes, undo, changed-byte inspection and saving a separate BIN.
Installed and tested on my Samsung phone; XDF/ADX import works and the main ignition tables are straightforward to navigate.
We’ve made a separate mobile XDF with 30 entries covering main ignition, fuel/injectors, idle, fans and RPM limiters. It’s a subset of our Master XDF with the retained addresses, equations and axes preserved. Currently 26 entries are editable; base PE AFR, two fuel-trim tables and the RPM limiter table need further importer support.
Planned connections:
Envyous USB ALDL lead for initial logging, through a USB-C OTG adapter.
USB-C directly to OneROM for programming changes.
Possibly investigate OneROM ALDL pass-through later.
OneROM Web has already successfully programmed a tune from my phone, although we encountered USB access/reconnection issues along the way. The new app does not yet log live data, write to OneROM, correct PCM checksums or enforce OS compatibility. Exported edits still need verification in TunerPro before use.
The longer-term goal is a straightforward log → review → edit → write → verify workflow, with backups and protection against loading the wrong OS/calibration family. ALDLDroid is an obvious existing reference; this is an early hobby prototype, not a finished replacement.
I’d particularly welcome advice on:
Envyous cable support on Android, including USB drivers and 8192-baud operation.
ADX command sequences, echo handling, BCM chatter and reliable reconnects.
XDF interpretation and checksum handling pitfalls.
OneROM/Ostrich communication from Android.
Existing open-source projects worth contributing to or building on.
What would people recommend tackling first, and what traps should we avoid?

[vlad01]

Looks good!

I don't know if this helps or not, assuming android is similar to more mainstream linux distros, did you see my thread recently on how I got linux to support full ALDL and TP functionality?

OSE 3.0 was needed to get TP itself working with reading/writing, but wouldn't be relevant for this I'd say, but the ALDL side of things might be, I basically had to setup some custom device rules to automatically run a custom divisor for the ALDL cable to get the 8192 baud to work whenever the cable is plugged in, and it works flawlessly with the solutions AI helped me come up with.

As far as all my digging into the problem and it was also covered in the TP linux sub forum, no one had tried a custom divisor which actually is super easy and gets you pretty much bang on the 8192. Most solutions I found just ran the cable at 9600 which sort of works but is flaky at best.

[Muncie]

Another round of revisions have logging working now and basic dashboard for monitoring things while driving.

It also flashes a full-screen Knock!! Warning (for max fast and furious vibes)

Bin adx and xdf are now persistent.

Have tried on bench and in car not running yet as its 10pm all sensors are live and reading

[antus]

I dont know if there is room for it, but it'd be nice to be able to load the adx and just hit a button to start logging, and another to save to tunerpro XDL format. I would think the AI should be able to figure it out with a couple of samples, as it has been fault finding on my car for me and tuneing by directly looking at the bin and xdf and adx without having a clear spec of the formats. The nice thing would be just plugging the phone in to do the logging instead of having a full laptop to do the recording. I looks like you basically have this and would just need the XDL exporter. From what I know of the format there isnt much too it. The main thing It needs is time and/or sample counters, a header, and it updates the counters and saves the whole ALDL frames in the file.

[Muncie]

Live logging and dash work perfectly now, i will add in xdl suport in next revision ive got the onerom outputting data to an ESP32-S3 Over USB C now its not %100 yet but end goal is car connects through WIFI Open app and you can then log and live tune either through phone or laptop. So effectively the ESP32 is the logger and ostrich interface leaving the ONEROM to run car.

This runs so much faster as its not limited by ALDL anymore.