Good Idea, good looking application.
have some questions
1. Firmware not changed so support usb connection not possible during online programming
2. What about sgw access
3. Support doip ?
Hi, 1. You can install any firmware you want on your TD2 yourself, but in principle it's also possible to forcefully load firmware into the shell, for example from DBScar VII which should have support, 2. This package in principle costs more than 1000 euros per year but there are also separate limits per VIN for different brands, it's simply not cost-effective for me to buy and share this subscription, online programming at the moment is shared from my PAD VII account to everyone.
3. It's much easier to add Doip support, just haven't had the means to finish it but the implementation is already laid out in X431-8.00.048-apbnu.apk and its implementation has been started not in the same way as everyone else, specifically at the apk level and without going beyond its boundaries with separate apks or modules.
If someone thinks this was easy and free for me, I'll disappoint you. The project took over 2 months, but not in the sense that I was obsessed with it and hacking away for hours. I did it in parts, did what I did. Even getting original brands over 1k is huge work. If I didn't have the original account, there would be no online access for anyone. But I don't even know how many people noticed my own AI module kernel that no one else has, because the stock Roxy is just a stupid chat based on error solving probably from the Workshopdata database and nothing more. After scanning the system, you can click on the magnifying glass with the image. AI. After clicking, a request is sent to openrouter with your full diagnostic session without the VIN number, where Claude Opus 4.8 subsequently processes it with reasoning mode enabled. It searches your error codes specifically for your brand, model, and engine type to give the most correct answer to solve the problem. It collects the most likely ways to solve this error from all over the internet and returns the answer in json format back where the server gives it to you. I just loaded 50$ to the balance as a test and I see that people are using it but no one writes anything, probably everyone thinks this is development from Launch

although each of your requests can cost me up to 0.4$ of this cost I managed to achieve by sending a report with 13 errors without erasing inactive ones, on average it comes out to 0.1$ per request yes you will say why then did you develop it if it drives you into the red, the answer is simple I'm curious how much easier it is with it to get a general list of solutions after diagnostics how much it simplifies diagnostics yes I don't argue that even after the AI answer for details you still need to dig into google and search in more detail but for the first input information it seems to me this looks perfect, after you burn through the 50$ balance I won't top up) and setting a lower model cheaper or without reasoning so it can't even return an answer in the specified JSON format it breaks it and starts the request over, this is just a reserve for the future that in six months or a year this model or its level will cost pennies for API requests
For the shell there were simply over 100 builds, rebuilds, checks. After building, inspection of work logs in different modes. After all, no one even knows that any x431 application in stock keeps full tracking and analytics on you, forms silent reports and sends tickets to Launch servers with any of your activity. After launching the APK, recording starts and it doesn't matter if you logged into your account or not. In this application X431-8.00.048-apbnu.apk it's not cut out, it's completely disabled for now, because I started cutting it out and then changed my mind. There are too many entries, there are just too many of them, and if I made a mistake somewhere, everything could break.
Yes, and for testing of course it would be worth adding all SNs that support, for example, xdiag or dz, I would agree then to test the software much faster, but honestly for each SN prefix you need to store your own directory of zip archives with brands, then the hemorrhaging will begin in terms of, for example, easydiag 2 flashed on xdiag and I need to give my shell a stock firmware almost and over-the-air recording with xdiag firmware for example is closed and pointless flooding will start across all SNs, so I limited myself to only the *9884 prefix where no breakage and improvisation is needed on stock and no hemorrhaging