yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] mil_house:
Hello

have the same problem, but i cant not find stm8ud.bin on stock firmaware image, can you please be more specifict where i cant get this file?Thanks and sorry for my bad english
[FYT Android Head Units] surfer63:
To start with: This is for a really old unit. Do you have a Sofia unit?

the MCU upgrade file is simply not in all firmwares. Sometimes it comes with a firmware when it is required to update the MCU firmware and sometimes not.

First check your unit and firmware level via https://www.joyingauto.com/blog/tag/joying-intel-sofia-android-car-stereo-software-update/
[FYT Android Head Units] mil_house:
Yes i have sofia unit, and works perfect, but right know i have loop boot problem, thats why i deside to change the rom

i try to rollback to get the file,becouse i cant not find it on joying software, i restore the recovery but when i plug in the pen drive with oficial rom nothing happen and the supost detect and boot it to install

The instruccions for the rom are no complete , so i can not roll back

Thanks

Nicolas
[FYT Android Head Units] surfer63:
Connect the pen drive and reset your unit with a needle or so.

As soon as the boot logo appears, reset it again. Do this 3 times.

The fourth time it should read your standard Joying firmware.

And if that does not work, you probably still have the special recovery image in place. You say you restored it, but if the official rom does not auto flash, the twrp recovery is still in place.

Then use the custom.apk to put the original recovery image in place. Then you can flash the original firmware again. Or repeat the triple reset.
[FYT Android Head Units] mil_house:
Works exactly you say!thanks!i all ready update my MCU and then go back to GTX again!!!Thanks al lot!
[FYT Android Head Units] mil_house:
thanks!
[FYT Android Head Units] KikoTs2:
@surfer63 , Sorry to directly tag you but as much as I can see you can only help me, I have FY_(NOR)_90_C9_7703_6023_Newlap_18E as much as I saw in settings, checked it it should be FYT and did a log compare with another user uploaded file, now to the issue, after few days the device glitched and I couldn't diagnose the problem (It was a bad Wi Fi Certificate due to incorrect date detection) so without any thoughts i just did a factory reset, thinking it will solve the issue, well it did but then the audio cut off, when I was in the radio application there is sound, but when I switch to another app like the Music Player or Youtube Music the audio immediately cuts off and only reappears after I switch back to the Radio App, So I was thinking about flashing this ROM only cuz of that issue (the Original Firmware really doesn't bother me in anyway, used to slow systems like this) so I started looking for other people that have this issue and one forum pointed me out to look at the extra settings that require pass code, and the Choose the Correct Car Model, so I tried doing that but no matter what I do it doesn't save the changes and it points to NULL, tried to do "CAN Upgrade", still nothing, went into the files which HWGetInfo Tool Provided and saw that sys.fyt.mcu_cus_id pointed to 0 not sure if it should be like that, also to mention that I haven't connected the cables for the steering wheel and have no control with it, not sure if this effects the CANBus or if this is the main issue, please let me know if switching to this ROM is good idea and if there are any other possible fixes for this issue, also how do i determine the MCU Update needed for my Joying in order to get the ROM working Google Drive Link . Thank you in Advance.
[FYT Android Head Units] surfer63:
I have seen some other remarks about your reported issue, but did not follow them. So for that issue I do not know a reason or solution. I think that a complete reflash with either the stock rom or this custom rom might solve it.

Some of the FYT settings are not stored in the /data/data section, but on several places of the file system. Doing a system reset to factory defaults only clears what is in the (dalvik) cache and in /data/data. But this default android reset does not clear the settings in /sys/fytver for example and on a few other locations.

Flashing this ROM can give you a better functioning and especially a slightly faster functioning unit. Please read very careful what you need to do with the recovery partition.

The MCU version as such is not that important. The only point is that if your MCU file is too old, you will get a yellow error bar in the top of your screen that the MCU is not the correct version. gtxaspec somewhere mentioned in post 1-3 what the lowest MCU level was, but then still it is not that important. And with my SofiaTweaker or XFytTweaker xposed modules you can disable that yellow error bar.

The problem is that this unit is no longer supported. So everything you try is on your own risk.
[FYT Android Head Units] blitzcat:
I also experienced this issue out of nowhere, to fix this I have to [go to Date & Time settings, turn off automatic date and time, then turn it on again] every time I start my car and the HU connected to WiFi.

Now I'm interested to try this GTX rom as well :)
[FYT Android Head Units] Nightmare[ITA]:
I am having this issue as well. Everytime I turn off the ignition, the date jumps back to the default value somewhere in august 2001, which causes many services not to work anymore because of certificate issues. So i have to toggle auto detect time to fix it.

Let me know if the GTX ROM solved the issues for you, was already thinking about reflashing the stock ROM.
[FYT Android Head Units] surfer63:
To start with: the gtx rom will certainly not solve this. It is simply not part of the ROM.

I never checked this for the Sofia units, but "in the old days" on PCs, the date/time module was powered by a tiny battery. After some years, this battery could die and you needed to replace it with a new battery.

I hardly can believe this works the same for the Sofia units, but now that they are 5 years old, it almost seems like it. And if we talk about Chinese build quality, certainly of 5 years ago, it gets more likely.

But that's a guess.
[FYT Android Head Units] Nightmare[ITA]:
Hey there

Nice to see you are still sticking around and helping users out right and left, amazing!

I guess that would be a good place to look, but it actually started happening after I updates my system to the latest version 1 week ago.

:D

Just reflashed the system yesterday, but didn't have time to test it yet. Will check if the issue is gone in the next few days and update my previous post.

Do you have any recommendation for a new unit? Are the Joying units still the way to go?

I'm still very happy with the units I bought years ago, besides the few issues I'm having now.
[FYT Android Head Units] becreative:
+1 exactly the same issue..
[FYT Android Head Units] Miedzio:
Hello,

For several weeks / months, I have a problem with application updates (I have Joying unit with GTX ROM). For example I can't update Google App or Gboard. The update is downloaded in Google Play, then installing, and finally I get an error.

Has anything changed on Google Play? Too old Android? Or it is only problem with my unit?

Does anyone have a similar problem?
[FYT Android Head Units] blitzcat:
Yes! This GTX ROM has solved the issue for me. But looks like your issue is bit different than mine :)

Just want to share my experience on my JY-UM135N2:

1. Upgrade my firmware to 20180126 version (https://www.joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update)

2. Root the device:

2a: Enable adb over WiFi using Joying Extra Tools (https://github.com/hvdwolf/Joying-RootAssistant/releases)

2b: Run install.bat <device IP address> from my laptop using Superuser-Sofia3GR-Intel.zip (https://github.com/hvdwolf/Joying-RootAssistant/releases/tag/20180107)

3. Install custom.apk (https://drive.google.com/open?id=1qJQmzh1bPlA-vEbnps2FjoLzoGzOdu_S)

4. Follow the steps on 1st page.

My hiccups:

- First attempt to "Install Custom" failed (Signature Verification failed), second attempt successful.

- During first boot, suddenly got restarted with the same symptom when my device got "reset" (lost my settings, but the apps are intact)

- Happens 3-4 times like unstable OCed system, then suddenly the display turns into command prompt showing:

Verifying update package...

E: failed to verify whole-file signature

E: signature verification failed

Installation aborted.

Last Flaged sofia6.0 !

- I shut down my car (with thoughts rolling back to stock firmware :()

- I started my car again, then the system surprisingly boot up normally :D and running fine until now.

And yes, I feel that this GTX ROM is a bit faster than stock firmware :)
[FYT Android Head Units] blitzcat:
same here, I haven't been able to update Google and Google Text-to-Speech, but this happens with the stock firmware as well hmm...
[FYT Android Head Units] IG_Vasilich:
our units (also with stock ROM) have problems updating/installing apps with bundled packages. I assume Google just haven't implemented it in Google Play services/Play store combo.

Though i don't have problems installing or updating bundled apps even on older tablet with Intel and Android 5.

So i am not really know why our units have problems with it. Maybe because our units aren't certified for Google play?
[FYT Android Head Units] dalu14:
the same for me - bad time and date = no internet from wifi hotspot, I have a gtx rom, I do not know what to do with it?
[FYT Android Head Units] becreative:
GTX rom here as well. It was happened suddenly since some weeks ago I would say. I suspect GPS clock sync or.. maybe there is some battery on-board and it simply needs replacement... I didn't find any solution yet.. Maybe someone will have some other hints.. Let's hope for the best :)
[FYT Android Head Units] IG_Vasilich:
This is known problem with GPS WNRO. We need a fix for it in FYT Server, but, unfortunately, i cannot patch Smali code (have no idea how to do it). So if anyone can patch Smali - pls report here, i can prepare java code for our FYT server.
[FYT Android Head Units] becreative:
Thanks for some additional infos. I checked the wrong date, its exactly ~1024 weeks backward, so it's definitely this GPS Week Number Rollover issue. Now the question is: how to fix it and how to stop sync this clock with device date. I tried to set the date manually, it always went back to this wrong 2001 according to GPS.

Interesting, thank you for some more input, definitely we are moving forward... slowly 😁
[FYT Android Head Units] mil_house:
+1 exactly the same issue..
[FYT Android Head Units] IG_Vasilich:
just disable GPS time sync - there is a slider in "car settings" - GNSS (GPS).

After that you can set correct time in Android settings - Date and time (and set it every time HU gets rebooted, because our HUs do not have backup battery for RTC).
[FYT Android Head Units] joooe:
I'm loosing network connection now and then, can't figure it out why. Mainly when using WAZE.

I'm using an USB wifi carrier pen connected to the Joying USB cable. With OEM Rom and Waze, wifi worked fine.

Help?
[FYT Android Head Units] becreative:
Wrong date / time probably. You can check it out.
[FYT Android Head Units] WishiHadAnR32:
So far this is working for me, I don't even need to reset it everytime the HU reboots it just corrects itself. How close are we to having a permanent solution for this?
[FYT Android Head Units] joooe:
Any solution to save user settings in Joying Equalizer? Everytime I start the car, the custom settings are gone. Even if I select a predifined equalization, it doesn't stick. It defaults to no equalization.
[FYT Android Head Units] localos:
Fix GPS date
[FYT Android Head Units] Fredheg:
Hello I have touch button of the left side. WENN I flash the gtx rom I need to re learn the keymap!

Go to car setting, then the advanced setting (password 3368), then learn button !

After learn it, push the record button to save it !

For me it's works

Edit : from joying forum's :

https://www.carjoying.com/blog/joying-head-unit-after-sale-support/59.html

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[FYT Android Head Units] dyabolikarl:
I am not sure I think i might have noticed it on the stock December rom. But it's all a blur going from may -> dec -> gtxv5.
[FYT Android Head Units] gtxaspec:
[MENTION=309187]edit[/MENTION] do you know anyone on the april or may rom? i need a partition dump from them...

dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img

to try and get viper working...
[FYT Android Head Units] surfer63:
A user on the carjoying forum found a bug in the code of the gpsspeedfix module that might very well be the cause of the issue in your sygic and my MagicEarth.

I patched it already. You might try out. Unfortunately I can not try out myself any sooner then this evening. If it works I will of course add it to my apk again.

temporary link: https://drive.google.com/open?id=1UDLQuLVqPUIL2ubPZWN2Qhz8lTgAP1jK
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION] i hacked up xposed-battery-percentage, custom keys works using this as a template, with prefs. did you get anywhere in your coding?
[FYT Android Head Units] ste2002:
gtxaspec, here is the link to 4pda post with "strings" for RU on January FW by gorlexx: http://4pda.ru/forum/index.php?showtopic=793304&view=findpost&p=69929548

The guy himself is rather shy to contact you directly, I could not make him at least ;).
[FYT Android Head Units] dyabolikarl:
Would this fix google maps? It's always thinking i am turning left down every street so it recalculates and does werid stuff.

I'll chuck the apk on anyways and see.
[FYT Android Head Units] surfer63:
Yes, it might as wel solve it. It was an issue in the GPS bearing (= the direction you are moving to).
[FYT Android Head Units] dyabolikarl:
Sweet i will put it on tomorrow and report back.
[FYT Android Head Units] surfer63:
I also expect some German translated strings from the German china-rns forum. I just asked how far they are.
[FYT Android Head Units] myxcon:
So just installed the software and been running it about 2-3 hours and can report the following:

a) button backlight stays on after turning off the car (the car lights switch is off) and turns off after about 4 minutes. This was not happening in stock joying software (december update). Also the buttons backlight turns on when the unit turns on even if the light switch is to 0.

ab in stock joying software, somewhere in car settings there was an option to select the type of amp installed with 3 options: off/none, amp ext and amp in (as in internal). Now this option is nowhere to be found and the volume for me is awfully low (i was using digital am internal settings - this was one of the reasons i bought this specific unit).

c)i am also using a can decoder, for the car steering wheel buttons, that is setup in CAR MODEL menu. Option 1 - RZC -> VOLSKWAGEN -> ALL ->RZC.XP(L) sound is low (as if no digital amp internal selected, point b), steering wheel works. volume works.

Options 2 RZC -> VOLSKWAGEN -> ALL ->RZC.XP(H.AMP) sound is higher, as if option with digital amp internal selected (see point b) , steering wheel works, VOLUME doesnt work. No matter how high or how low it is, it stays the same level. (just mutes if turned to 0 or muted).

Also when trying to chose other car model in the list, i just get an error that says : No matching MCU upgrade file, check whethere the MCU upgrade file is complete. This worked before on stock (how do i know? when i upgraded to december patch, i had to browse to several car models in that menu till i found one that works for the can decoder i use - it is not written anywhere on it)

I will gladly provide any information needed to debug, as much as i can manage; as the rom is obviously a better choice than stock.

LE: This is a copy paste from joying, but it describes the option that is currently missing for users who need to select amp internal.

3) Enter the Car Settings application- go to the lower right tab (the one with the screwdriver) click on it and enter 3368-?

go to the AMP Enable option and turn it off-Go to the EQ menu (second lower tab from right to left) of the car settings and now have the keyboard pitch option.

Note: If your android car radio is with digital amplifier, please choose AMP (in).
[FYT Android Head Units] edit:
No, I am sorry, I don't know anyone with these old ROMs on their units...

I personally moved away from them because of the many BT issues i had.
[FYT Android Head Units] farmerjohn:
I'm still using original December Update and my unit behaves in the same way. So I doubt that this is a gtx-specific problem.
[FYT Android Head Units] myxcon:
Gonna update to january joying update now, to make notes about stock behavior and will reflash gtx. That internal amp setting is a must if I am to keep using gtx mod.
[FYT Android Head Units] surfer63:
This is indeed definitely not a gtx rom problem. The Joying stock ROMs do exactly the same. It is an issue that started indeed on the December stock ROM.
[FYT Android Head Units] myxcon:
So quick update.

Just flashed stock january update (followed by fctory reset to make sure everything is clean):

1. the button lights is NOT present on stock update. Can take a video if you require actual proof.

2. in car settings the following option is missing (see first 2 pictures.) which enables or disables the internal amp.

3. regarding the car model, which affects the can decoder installed (for use with steering wheel buttons and car info app) there are several options as to which can decoder is installed. When either one is sellected the system auto updates itself with proper MCU files. See third and forth picture. In the gtx mod, those files needed for MCU update have probably been removed as part of the debloating process.

If you require more information from stock rom, as I still have it installed (january update MCU 05-25 1024x600 rez) do not hesitate to contact me.
[FYT Android Head Units] ste2002:
I've experience this button backlit behavior on my previous Sept stock FW (now on Dec - it did not show yet, but I guess it was a result of some random Car settings; but I also feel that you are right saying about some apps running which can not be shut down right away).
[FYT Android Head Units] IG_Vasilich:
i have stock ROM from 25.05.2017, but it is hard to connect to it (can't drive too near to house with wifi). Is it possible to get the dump on HU itself? maybe with terminal (i have it installed on HU)?
[FYT Android Head Units] surfer63:
Yes, you can do that on the unit itself in a rootedterminal. And then copy the file onto usb orsd-card.

---------- Post added at 01:47 PM ---------- Previous post was at 01:01 PM ----------

1. I believe you but I really did have it on the December stock room and still on the gtx V4 rom (not on V5 yet, also trying other things and it is currently again way too cold to stay in the car).

Maybe it is one of those weird "things" in the Joying roms.

2. "in car settings the following option is missing (see first 2 pictures.) which enables or disables the internal amp. "

Yes, I see that too.

[MENTION=520205]gtxaspec[/MENTION]: you removed the amp settings from the customerfg.txt. The fact that joying stupidly keep it on the same setting for 4 ROMS already, forcing you to disable the amp in the settings, switch off the beep, and re-enable the amp again, might be due to a bug. Maybe they have to do it this stupidly, otherwise you might not have an amp setting at all.

It is just a guess, but we have already encountered so many weird bugs etcera, that this might not even be so far fetched (to joying standards that is).
[FYT Android Head Units] myxcon:
Is there something that I can do to reenable that amp thingie in latest v5?
[FYT Android Head Units] WishiHadAnR32:
For all Joying units? Just checking before I install👍
[FYT Android Head Units] becreative:
Is anyone tried this already? This updated SofiaServer.apk?

As I thought it contains some trojan.. 😄 So just be aware guys.
[FYT Android Head Units] D3LTA:
Does not work
[FYT Android Head Units] D3LTA:
Does it work for anyone here?
[FYT Android Head Units] level5music:
Date seems to be fixed but now my volume control is centered in the screen.
[FYT Android Head Units] pwood999:
Didn't work for me. Reverted my HU to manual Date & Time
[FYT Android Head Units] SuperSalty:
Hi everyone,

I've been using a JY-UMS03N for about 3 yrs now. And I've also been using the GTX rom for quite some time now. Yesterday the unit randomly rebooted and greeted me with a screen about that it's now wiping everything. Since then the HU doesn't boot into Android anymore. After the set manufacturer logo it just continues to spam "Last copy navi fail!" and "E: unknown volume for path [/ment/external_sd]" at me.

I have read a lot of threads but it appears that noone really encountered that issue in combination with not being able to boot into Android at all before.

I hope someone has an idea about what could be the cause and a possible solution to this.

Thanks for the help!

SuperSalty
[FYT Android Head Units] IG_Vasilich:
@SuperSalty

do you have any SD card in any slot? Have you had any somewhen?
[FYT Android Head Units] SuperSalty:
@IG_Vasilich Yes at some point there was an SD card in the GPS-Card slot. However I removed it after losing the mapdata that was on there through a factory reset. Since then there was no SD Card installed anymore.
[FYT Android Head Units] surfer63:
Maybe, but I assume that the navi app is still installed and is still looking for its maps on the now missing SD-card.

Or some persistent property makes the system look for an SD-card, because some program later started (the navi app, maybe no longer installed), might want to access the SD-card. Please try with a cleanly formatted SD-card and see if it runs through the boot process.
[FYT Android Head Units] SuperSalty:
Thanks for the fast replies from you guys! I really appreciate that!

@surfer63 I just tried what you suggested.

Interestingly with a completely formatted FAT32 SD-Card the HU showed the "not fully started 3 times" message which it did not before. Unluckily, after the reboot it just continued to display the said error message.

So no luck with that either.

Additionally, I also tried to put the GTX rom on a fresh formatted SD-Card which did not bring any luck either. I tried the same with the original firmware off of Joying's homepage but no luck aswell.
[FYT Android Head Units] surfer63:
I'm afraid you have to flash your unit again, and you have to start with the Joying firmware.

Put the Joying firmware on a fat32 scdard.

Put it in your unit and reset your unit via the pinhole. When the bootlogo appears, reset it immediately. Do this 3 times.

The fourth time it should flash the Joying firmware. When everything is again up and running, you can use the suctom apk to replace the recovery image again and then flash the gtx rom again (if you want to)
[FYT Android Head Units] SuperSalty:
I tried it now.

So basically no matter how often I reset the HU it always continues to boot to the error message.

Only if I insert a formatted SD-Card with nothing on it, the machine will display the "machine did not fully start 3 times". However, it does not install anything. It does not check for any USB media and so on. And if I insert the SD-Card with the original Joying firmware on it, it again just boots to the error message.

Further, if I have a USB-Stick plugged in with the firmware, the HU just ignores the empty SD-Card and just boots to the "unknown volume" error.

If I plug in the USB Stick while it's displaying the "machine did not fully start" message, the HU either freezes or it doesn't reboot and continues to the main error message.

Just to get things straight, and I'm not messing up any formats and stuff.

The SD-Card has to be formatted in FAT32, and the ZIP of the firmware needs to be extracted to the root of the SD-Card?

Lastly, doesn't the path "/mnt/external_sd/" point to the internal storage? AFAIK SD-Cards are labeled "/sdcard1" by android. USB-Sticks normally have the path "/usb1".

So could there be a possibility that the HU just fried the internal storage and thus is unable to mount it to boot from it? Or am I just too dumb to properly reflash the HU? :/