it took me a little while to think over the reply to your comment, so here we go:
in this case I wasn't complaining about DJI, they can mostly do good job
but they still deserve complaining, at least for two things:
- DJI GO (at least Android's version) is still very buggy and it looks like they are making things worse only
- with all those new prohibitions and conditions, it's like they are punishing users (for example it's totally inacceptable to tell users when they can fly or force them to update firmware or DJI GO)
and now to the code and decoding
with your attitude you are exactly the same as dozens of people asking us to share the decoding algorithm
it's sad that nobody has come with something like "hey, I want to help you, I found something in DJI GO / firmware that you haven't, I want to make your tool better"
for a while I was thinking about some kind of poll, where users of my tool could be able to vote if I'm (or exactly we are) to share the algorithm or not
but then I realized few things:
1. I believe DJI encrypted the logs, because they wanted to have some kind of insurance, that the logs were valid, not faked.
Because if somebody has encryption/decryption algorithm, he can abuse it and alter the logs.
I can easily see webpages offering "did you crash because of your fault? send us your TXT log, 50 bucks, and we will change the log so it will look like it was hardware fault and you can ask DJI for free repair"
It has been 19 months since DJI came up with encryption and it's 18 months since we broke it.
DJI hasn't changed the algorithm since then so I believe they are satisfied with things as they are now.
2. You say "You're not the only smart person out there; please let the rest of us help you with this".
Well, where are all those smart people? Because until now, as far as I know, there are no new services offering to read the encrypted logs, except all those old ones - Airdata, djilogs, phantomhelp and my converter.
Sadly that also means that if DJI changes the encryption in the future, there will be nobody to break it (maybe Airdata again).
So I decided I don't want to risk to lose the current win-win situation, I don't want to give DJI any reason to change the algorithm.
I don't care of what people will think of me - I'm trying to do what I think is the best for users of my tool.
I will never agree to publish the algorithm.
Anybody smart enough has to agree with me. BudWalker, the guy who invented decoding algorithm for my tool, supports me with this too.
End of story.