yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] hsi1:
Hi All

Prompt please

CarAPP ->

System Version: QF001.20221105.135958

Software version: V1.3-221026.1500

About -> System Information ->

System version: QF001.20221105.135958_v1.79_01

MCU verison: QF01.V01:67.20221109.011021

About vehicle ->

Build number: QF001.20221105.135958

Software version: ums512_q0_20211130

Hardware version: QF001

adb permanently broken(loses) connection (via Wi-Fi 2.4 or 5) after some seconds of use. further connection is possible example when restarting this car radio. what to do?
[Android Head-Units] blue_one:
Have you plugged in the cable for the reverse camera? That plug also has the wlan antennas inside.

Besides that you don´t have the latest firmware installed and you could give that a try.
[Android Head-Units] marioti:
maybe try to upgrade firmware at first. then we'll see what happens

https://xdaforums.com/t/firmware-qf...-uis-7862a-7862s-not-fyt-based.4541261/page-2
[Android Head-Units] KLJ617:
Hello everyone,

My S4 prohibits me from doing ANYTHING else during calls. The only thing that works is volume. Has anyone had this problem and/or found a workaround?
[Android Head-Units] Clyde72:
This seems more like a default safety setting than a problem. Look if there are "lock & mute during call" settings in the bluetooth/phone app on the unit (with your phone connected).
[Android Head-Units] KLJ617:
Thank you for the suggestion, I don't see it in the options. I've checked options, bt options, developer options, and I don't see that setting.
[Android Head-Units] Clyde72:
Ok, sorry if it can not be changed. Asked your seller yet on that?
[Android Head-Units] parked:
Purchased a S4 model through Amazon about 3 weeks ago. Updated the system and MCU without any problems. Unit ran without any issue until today when it no longer recognizes any touch input. The 5 finger screen calibration did not work, nor the touch buttons on the side of the screen. Plugged in a mouse and was able to reflash the system and MCU, to no avail. Is this a known issue or does anyone have a workaround? Nothing changed between when it worked and when it didn't
[Android Head-Units] zerebede:
Same here but solved. Turn back to your old MCU with mouse and then go to factory-->touch learning button-->key position (and if your radio has the 5 left button on the left side)-->check left key and confirm. After this you need to program the 5 button again and save. Be carefull messing with MCU because thereªs people googling about MCU but they don`t really know what`s a MCU for. Ex: QF01.V01.71..... this is the version of a MCU..... 20230103.002121 this is date and time it was made. Same for system version.
[Android Head-Units] parked:
Thank you so much for the response. Where can I find 20230103.002121 MCU firmware?
[Android Head-Units] zerebede:
Everytime you ugrade do always the CHECKSUM and you gonna be asked if you want to change. Compare and if the new one is not the same (Ex: QF01.V.......), dont install it. Forget the 20230103..... cause its bull****. Important is the version. You can have the same version with different date and time. There are different brands working with same hardware.
[Android Head-Units] blue_one:
Next step is done: tasker can control my hardware volume keys now. No extra permissions needed. The adb shell plugin does the job. Last step is to create a profile which controls the volume by gps speed. This will be tricky because we can't set the volume in absolute values. I will have a look into this issue later.

I don't get the problem here. How could you flash a wrong mcu firmware when there is a kind of compatibility check which now prevents you from flashing the "right?" firmware? Why do you think the firmware you flashed is wrong?
[Android Head-Units] millis69:
Thank you very much when entering the code 774411 the correct MCU went away. I have an S7 model the wrong MCU was from the S4 model forum. For the S4 model another DSP the sound disappeared.
[Android Head-Units] millis69:
I don't understand why they take the wrong one. Even the DSP number is changed
[Android Head-Units] Clyde72:
What does this code do? Revert changes?
[Android Head-Units] blue_one:
You should contact the seller/manufacturer. Maybe they can give you a recovery firmware.
[Android Head-Units] aadat:
It's not, it's so you can reinstall the original. but I'm surprised that you were able to install that it's not su.
[Android Head-Units] Clyde72:
I d

I don't understand why some just want to do an mcu upgrade and not a system upgrade so all is updated. Maybe try the 26112022 system update first. And after that the 26122022 firmware update & 26122022 mcu upgrade...
[Android Head-Units] millis69:
I had upgraded the system from the forum and then the upgrade came from the vendor with a new MCU kit. Before that, I downloaded the wrong MCU on the forum and confused it with the vendor's MCU.
[Android Head-Units] Clyde72:
I hope you will be able to redo the system upgrade. Is the vendor Ossuret or Hizpo? I have an S4 unit from Ossuret and could do the system upgrade (26112022) for S8 from Hizpo. Will try 16122022 once I know what it fixes or enhances.
[Android Head-Units] Clyde72:
Seems like I will have to take a closer look at Tasker and adb shell so I can implement SVC once you've found the solution...
[Android Head-Units] nyp42:
I recently bought the S2 version of this head unit. I am very glad to find this thread because I have found this unit to be very frustrating so far. I really don't like the launcher but can't get Nova Launcher working properly. The unit has become unstable due to me installing and removing so many apps and I am unable to do a factory reset even using the passcode 22558800.

I would like to upgrade to the 16122022 firmware but I am not certain whether the same update.zip file and MCU.bin works for both S1,S2,S3,S4 and S5,S6,S7,S8 as they use different DSP chips.

It seems like all the files that have been posted so far are for S8 models. @Clyde72 have you confirmed that the audio works on your S4 unit after upgrading to 26.11.2022 firmware?
[Android Head-Units] millis69:
no need to upgrade s4 with s8 MCU file sound is gone.
[Android Head-Units] Clyde72:
All, incl. audio/DSP, works fine after the 26 11 system upgrade. And got me overall some more unlocked settings and flexibility for my unit. Nova Launcher works but I don't use it.

Not having audio would be a real bummer for an media unit and I would have noticed that right away after updating I guess... Only issue was with the touch screen but after a soft restart and some screen re calibrating it was fixed.

My unit was originally delivered with 19102022 firmware + mcu version. Were both updated to 26112022, BSD remained the same - BD37534 - so I guess DSP is not affected/concerned in updating firmware & mcu.

The 16122022 firmware & mcu come from an S4 owner FYI who got it recently from his vendor. Not tried that version myself yet.

I hope that helped you.
[Android Head-Units] millis69:
forum no S8 MCU file. They end with 002121
[Android Head-Units] Clyde72:
@****gsxr Your unit is also S4 (4/32) correct? Can you post a new screen shot showing the updated firmware and mcu please?
[Android Head-Units] millis69:
MCU from S7 https://jitu321077708mcu1216.oss-eu-central-1.aliyuncs.com/mcu.bin
[Android Head-Units] Clyde72:
I get my update files here on Xda "forum" not by going to poke and experiment with random files on Jitu's servers in Shenzhen
[Android Head-Units] millis69:
they are vendor files.the original files come from our server. The original manufactor is shenzhen jitu technology co. ltd. they were also not made by the XDA forum
[Android Head-Units] Clyde72:
I know but I prefer to go with files tested and shared by the owners in this thread and not going to search them myself and risking messing up my unit
[Android Head-Units] parked:
I'll have to learn more about CHECKSUM as well. I currently have Hardware information: 1.8Ghz x 8 - UIS7862A

System version: QF001.20230109.190922_V3.08_01

MCU version: QF01.V01.70.20221216.011021

Can you point me towards the correct system and MCU version?

TIA
[Android Head-Units] zerebede:
I see that your system version is changed. Am i right ??. Wich brand of radio do you have ??. HIZPO ??.
[Android Head-Units] parked:
Yes you are correct. I flashed a new firmware for MCU and system when I received the unit.

*** Yes, it's a Hizpo. 4gbDDR/32GB flash
[Android Head-Units] zerebede:
HIZPO ??.
[Android Head-Units] parked:
Yes, that's correct
[Android Head-Units] zerebede:
Ok. It should be (System Version : QF001.20230104_v3.06_01). Try to find this one (system and MCU). I dont know why i cant get inside the web of JITUFIRMWARE, maybe my google chrome is cheating me.
[Android Head-Units] parked:
I've tried searching both this thread and Google for system version: QF001.20230104_v3.06_01

and cannot find it anywhere

I thank you very much for your assistance
[Android Head-Units] zerebede:
Try to find it. I`ll try too. My google chrome does not get in. and my iMac update safari today for version 16.3 and dont even open my homepage. Can you believe it ? Second time this happen to me with safari update. :(
[Android Head-Units] Clyde72:
All firmware version files & mcu files links can be found in the separate firmware thread for our units. All that matters is to look for posts on "0104" e.g.

https://xdaforums.com/t/firmware-qf...-uis-7862a-7862s-not-fyt-based.4541261/page-2
[Android Head-Units] parked:
Copy that Clyde. I'm going to look through those again now. Would having the wrong firmware cause the touchscreen to suddenly stop accepting touch input the way it has? It's just odd because it's functioned normally since flashing firmware when I first got the unit 3 weeks ago and then suddenly today, everything but the touch function works
[Android Head-Units] zerebede:
Is any of you able to enter the jitufirmware links with google chrome?.
[Android Head-Units] parked:
I cannot. Returns "bucket non-existent"
[Android Head-Units] zerebede:
Same here. :(
[Android Head-Units] parked:
Would you mind linking where I can download the 0104 firmware from? I can't find it and I'm pulling my hair out over here
[Android Head-Units] andysabre:
Hi. I've the same problem with an S7 model.My touch screen dosen't work. I did the same thing as you, reflash the firmware, try the five fingers calibration without success. Actually i use the mouse too. I wrote to my seller, he said me that will send me anoter screen. I wait.
[Android Head-Units] Clyde72:
https://xdaforums.com/t/firmware-qf...62a-7862s-not-fyt-based.4541261/post-87994077
[Android Head-Units] isash:
Does anyone have the built-in DVR app working, how should it work, how to run it?
[Android Head-Units] marioti:
I join the question. I want to use to connect my existing DVR, but i can't use usb cable, not without adapter from jack av out (but i don't know is the app need digital connection via usb, or mayne tere is only analogue signal. Then it could be use a simple adater). I thinking myself also, maybe it just be enough to use adapter jack AV - chinch cable, to make non usb connection? Well, I have one like this, so definitely try

https://www.amazon.com/Q4-wtyczka-1080p-czerwonym-bialym/dp/B01N0J3CFO
[Android Head-Units] Clyde72:
When manually updating with checksum you can not update the wrong firmware so I doubt this to be the cause. I personally updated incrementally from 1910 to 0204. Always manually with checksum. Never had issues. Had to do a screen recalibration after 1612 update if I remember correctly but this recalibration procedure was mentioned with that update files.
[Android Head-Units] parked:
As noob of a mistake as it was, I passed over the checksum step. I knew better. Major props to @zerebede for going above and beyond. He sent me a PM and helped walk me through reflashing the system update, even going as far as to u/l the system firmware I needed to Mega. I'm a long time XDA user, newly registered, but that's always been what makes this such an awesome place. The people.

What I wasn't able to get was the correct MCU however. @Clyde72, I see the firmware thread and the 0204 files, but they appear to be dead links to jitu firmware. I'm sorry for asking again and I sincerely thank you for your help, but would you mind linking me to the correct MCU for the S4?

Happy Saturday everyone
[Android Head-Units] Clyde72:
i

You will have to ask if somebody has uploaded the 0204 files to Mega or some other cloud service alternelatively. I don't have access to my pc now. Otherwise 0207 files for S5-S8 has just been shared in the firmware thread.
[Android Head-Units] parked:
Copy all. So the S5-S8 MCU is compatible with the S4? Or am I misunderstanding?
[Android Head-Units] Clyde72:
No but I don't know your unit. Firmware is compatible with all. Mcu for S1-S4 and for S5-S8 are different. Mcu files also have another size, Those for the lower units are 36 kb, those for the higher models 47 kb.

Last known mcu for S1-S4 is 1612 btw, I have it running with 0204 firmware.
[Android Head-Units] parked:
I'm tracking. Much appreciated sir. 🍻
[Android Head-Units] zerebede:
Hi There

After several experiences on the S5 here is the verdict that may be affecting some of you. In QF001_v3.08_01 it is not possible to uninstall Toppal voice, since in this version it is assumed to be a system app and as such the device does not allow the activation of "OK GOOGLE" (*not allowed on this device). In turn, in QF001_v3.06_01 it is possible to uninstall Toppal voice

since it is not assumed as a system app and so the Google assistant works well and can even be woken up with the HOME button on the left side. Peace ;)
[Android Head-Units] zerebede:
S5-S8 are not compatible for S4. We had this experience last night. S4 are a QF01_V01.70 and S5-S8 are QF01_V01.71
[Android Head-Units] hsi1:
blue_one, marioti, thanks

prompt please - which firmware to flash? I read firmware-topic did not understand

s3-3Gb/32Gb-4G Hizpo

CarAPP ->

System Version: QF001.20221105.135958

Software version: V1.3-221026.1500

About -> System Information ->

System version: QF001.20221105.135958_v1.79_01

MCU verison: QF01.V01:67.20221109.011021

About vehicle ->

Build number: QF001.20221105.135958

Software version: ums512_q0_20211130

Hardware version: QF001
[Android Head-Units] yes4bb.:
Hello guys. I want an S5 unit, I am coming from a Topway TS7 platform, I am waiting with purchase a little bit to know for sure that I am going to get a version with fan app working. Meanwhile could you tell me if there is in setting an Accessibility Settings on this device. I am planning of using Tasker to automatize some processes and I need accessibility for that. By the way, I am asking because in TS7 devices accesibility is banned, is nowhere to be found.
[Android Head-Units] blue_one:
Tasker works with accessibility in general for me but I have to disable and re-enable the accessibility permission from time to time. It seems that it loses the permission randomly even if the settings menu say it's still enabled.
[Android Head-Units] blue_one:
This should fit your head unit: https://xdaforums.com/t/firmware-qf...62a-7862s-not-fyt-based.4541261/post-88040581

Disclaimer: use it on your own risk.
[Android Head-Units] yes4bb.:
So, important is there are this settings there...This was one of the wories I have had to buy the product. Another question is about microphone. I read that on newest FYT devices there is an option to dissable internal mic in settings. Maybe a question could be asked your seller about that, there are almost similar devices.
[Android Head-Units] blue_one:
Sadly this device has no known way yet to disable the internal microphone by software. But it's possible to deactivate it with a simple hardware hack. Just read the first post of this thread.
[Android Head-Units] snaker12:
Hello.

Do you mean that you just skipped the 1 wire and you just soldered the plus and minus?
[Android Head-Units] marioti:
I'am so mad on Ossuret. i have order S8 unit, which i received it todday. According to a item side , S8 unit should be build on: 1. New processor Unisoc UIS7862s. But i received unit with an old (2019r) processor Unisoc UMS512T (also named as Tiger T618) 2. It should be 8GB RAM, but it is 6GB.

I opened a dispute immediately

Of course i also mentioned that it is a fake Android 12

one more thing, as about the fan, i don't see any version numbers direct to PCB, only on external case there is a sticker with number S101008F
[Android Head-Units] blue_one:
As far as I know the UIS7862s is just a new label for the UMS512.
[Android Head-Units] marioti:
It can be true. If i compare both processor, eg. here https://gadgetversus.com/processor/unisoc-uis7862-vs-unisoc-ums512/ it shows exactly same parameters. I wonder. it compare 7862 without S, so what it is those "S", maybe just marketing. Ok. but it doesn't change it is 6Gb ram insted 8Gb.

I know. I think you've shown us that the unit is using max 6gb, but that's still a lie on their part. And i pay more for those non existing Gb
[Android Head-Units] Jelosia:
in my car there are two amplifiers for the front and a sub, how to connect it correctly and where to get the rem, the radio tape recorder is connected via canbus, сanbus works fine, all functions are displayed, doors, climate temperature, the only thing I don’t understand is why the radio does not turn off completely and pulls out the battery, and how to connect the RCA correctly, I have two of them for the subwoofer, and from the radio one comes out , sorry i use a translator
[Android Head-Units] wujek_p:
I have the same unit (8/128]. On sticker inside is 6 + 128G. Max memory for UIS7862 is 6 GB. Where is the rest of the RAM?
[Android Head-Units] Telperion:
I think these settings are read from an XML file in the vendor directory. It's been a while since I poked around, I forget the name of the file. You can edit it with a root shell.

Update: I figured out how to disable the internal microphone via root shell. Unfortunately, at present it also disables the external microphone also. I'm going to keep tinkering.

Setting "Mic Function" to 0 in the <on> block disables the internal microphone.

Spoiler content hidden.
[Android Head-Units] Telperion:
For those who don't have root or have better Android skills than me, here's a dump of a bunch of system and vendor files:

https://drive.google.com/drive/folders/1jU11FDe2IqbZAsBtjUn_D9p-EC-iE-HT/

I haven't been able to figure out how to disable just the internal microphone. Every attempt so far either disables neither or both.
[Android Head-Units] blue_one:
That was my experience too. I guess its because the vendor just used one microphone input for both microphones. So only the hardware mod works to disable the internal microphone.
[Android Head-Units] marioti:
Do you use 6x5mm condenser microphone? I measured the hole and in my case it is 5.8x3.2 mm (diameter x height). In the hole I see hmm.. a touch screen? (look at the picture) which decreases the depth
[Android Head-Units] Aaantonn:
also wanted to put a larger microphone, as written here on the forum, but it is not possible to install it because the screen really interferes! The problem is not in the microphone, as everyone here writes, but in the fact that it is very far from the hole and you get a sound, like in a pipe, but you can hear it well. You need to unsolder microphone, increase the length of the legs so that the microphone is near the hole and, when installing, cut out a small piece of paralon so that it is around the microphone. If you do this, everything should be heard well even without an external microphone. As a last resort, if you suddenly have a really bad microphone, you can take a microphone from an old mobile phone, it will definitely be of good quality there.

I'm going to redo it today. My microphone works great, without any settings, no need to shout, I calmly talk on the phone, only the sound is really butto in the pipe.

If you put a microphone 6 * 3mm, it will still be at least 2mm from the hole and will not change the situation much. Those who put a microphone 6-5mm, they have a different case.
[Android Head-Units] marioti:
"something went wrong" part 2 :) I ordered HU specific to my car (according to the item side), but ossuret shipped to me wrong adapter. The main power supply lines in the adapter are in the place where normally is an optical connector in quadlock. So i can't even run it inside my car (will try at home with mini lab. power suply). Can someon can show me the right adapter?

In the photo, the top side is original car connector, the bottom is the plug from adapter
[Android Head-Units] marioti:
ok. i try to do some mods with this mic
[Android Head-Units] Clyde72:
I allready planned to replace the front mic, widen the hole, design & 3d print some horn and condenser holder to close any gaps and space next time I get my unit out of the car.

If you plan to use an external mic deactivate the internal one as blue_one presented. Technically both mics are connected in parallell. So if the front mic stays connected when connecting and using an external mic the front mic will pick up noise deteriorating the signal to the external one... The modding depends on choice for the internal mic or external mic.
[Android Head-Units] Clyde72:
What make and model is your car?
[Android Head-Units] Clyde72:
Did you try adding such a control board in fact? A 2 wire version...
[Android Head-Units] marioti:
Can you show some more :)

And, my car is skoda superb 2012

I foud out, the adapter should be to 40 Pin quadlock, and i receive 52 Pin version
[Android Head-Units] Clyde72:
I guessed it was a VAG car with the quadlock. I have a VW Golf 2018 but didn't use the quadlock but the other harness with iso connections. I was lucky as there was allready an iso adapter kit in my dash + I don't use canbus. Ossuret is not the best but still ask them for the correct harness if you want to use quadlock & canbus.

I can't show the mic mods yet as I plan on doing them when I take the unit out for some mods. Unit is bolted in the center dash so asks for some dissassembling thus time etc. But it is based on the findings in the thread. I will replace the front mic capsule with an capsule from an old Parrot mic I have laying around (if it fits that is) & then design & print some capsule casing which sits flush on the front bezel to eliminate or reduce noise. I will probably enlarge the hole also.
[Android Head-Units] Aaantonn:
Today I put the fan control fee from temperature. But your link is not suitable, since it does not turn off the fan completely, and has 4 outputs. I introduced this fee

https://pl.aliexpress.com/item/1005001710275547.html?spm=a2g0o.order_detail.order_detail_item.9.351443ce1G2r3g&gatewayAdapt=glo2pol

It has the opportunity to set 1) the inclusion temperature, for example 50 degrees, 2) the temperature at which there will be maximum speed. I made a temperature of a 50 degrees, disconnect 45, and at 70 there will be maximum speed. That is, the fan accelerates from average to maximum speed. But at the entrance to the scheme, I had to put a resistor of 22 ohma., Since it is a maximum of 12-13.5 volts, and on the network 14. And I also staged a resistor in front of the ventor about 80 Ohms .. I bought too fast 10,000 rpm. Buy a 5000 speed fan Or Maxim 7500. It remains to check everything.
[Android Head-Units] marioti:
ossuret accuses me of using HU for 20 days, and after that report them a problem with adapter. They want me to return HU, then they will refund me. the problem is i got HU two days ago and it is easy to prove. they are not behaving right.

I just wait and see what aliexpress will do. Anyway, i found this one. I think i need 40 Pin connector. It looks like fit mine

https://a.aliexpress.com/_EJLPlgp
[Android Head-Units] Clyde72:
You would never get a full refund. Ask Aliexpress to mediate so Ossuret sends you the correct harness for free. Fingers crossed.