Nadie tiene un firmware o mcu actualizado de la junsun v1 1g 16g de los que se actualizan con ficheros update-ty.zip y ms51_update.bin?????
[QUOTE = "maxou2, publicación: 84151783, miembro: 4643209"]
Pregúntele a su proveedor o pruebe en algún otro lugar ... Creo que puede encontrar foros donde se identifican varios tipos de MCU y se discuten en algún lugar ...
Por cierto, ¿revisaste la antena BT? Tenga en cuenta que es solo un cable corto, verifique si hay cortocircuito o contacto a tierra ...
View attachment 5164787
It's a good idea, but I don't know if I'll be able to identify it. Thank you
Okay, I've been digging through the firmware to see where the f*** the programmers set most apps to fullscreen mode, and finally found it. In case any of you, like me, does not want to force fullscreen for all apps, you have to set this setting in /vendor/build.prop or /system/build.prop:
It took me a few hours to find, so hopefully nobody else has to go through the pain again
I've been reverse engineering the native library which controls the MCU, DSP and gets CAN messages. MCU is on /dev/ttyMT2, DSP is on /dev/ttyMT3.
My goal is to write a completely new MainUI apk, since the current one uses a lot of system resources. I'll only focus on making it work on my Junsun V1 2GB + 32GB.
Well I've got some updates.
I've posted my current progress to GitHub. Currently it basically does nothing by itself, but the code to communicate with the touchscreen works perfectly. Also, the code for the MCU seems to be partially working, but I could not get it to do anything, even something as simple as turning off the backlight.
In case any of you want to dig into the code, here it is:
It's quite messy right now, and some parts are directly copy-paste from ghidra. However, nothing crashes, which is good to see too.
Feel free to make suggestions and even pull requests if you feel like doing so. To be able to run the .apk, it has to be signed with system certificates and installed as a normal .apk as an update, or replacing the apk into /system/priv-app/MainUI.
I chose to sign it with system certificates directly so that I can just click "play" on Android Studio.
I'm quite busy at the moment and i also can't user the unit as lab test, anyway i really appreciate your work and i really hope to have spare time and knowledge so i can help you ASAP... BTW the worst about our unit is about the responsiveness, sometimes it really sucks... On my other car i have a YT9217 unit ( that has the same SOC but with only 1 GB RAM ) and it really beats our in almost everything ( except radio and DSP ), it's really a pleasure to use it... unfortunately the fw is not compatible ( i suppose ) but it seems to be optimized for the HW.
It's not getting detected by the computer at all?Gents, you are doing impressive work here however I have different question. Maybe it's wrong place to ask but you look like you know your stuff, not to mention I've tried elsewhere without success. During playing with different softwares and making my own changes I've managed to brick my V1 2/32 and I can't re-flash it back without knowing where the "TEST POINT" is in the board. Maybe you could shed some light. Any clue would be appreciated. Pics of my board attached. Thank you!
You can try those two points with a very thin and long cable (or with a 1k resistor if you have one, to avoid shorting something if it's not the correct ones)No, I have no response at all. No physical buttons as well. As described in some flashing posts, I need to press (short) Volume Button before the board is plugged to computer. Below pic is just an example found for different board...
Hola, encuentro poca información sobre mi mcu TS907. Creo que la unidad es diferente pero la misma mcu.
¿Podrías decirme si servirían para rootear tus archivos? Gracias
ver archivos adjuntos
View attachment 5164087View attachment 5164089View attachment 5164091View attachment 5164093