yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] mancypher:
Here you go.
[FYT Android Head Units] muzoss:
as i can understand, you flashed 7862/8581 FYT Factory by Mario Dantas first, and your device booted correctly. After after flashing bootlogo and boot animation, your device goes into bootloop, which means either of those two zip files are not suitable for your device. Delete those two files from your usb stick, and place a proper bootlogо file on the usb stick, complete with all the files from the first attempt, and flash again, I think your device will boot correctly.

Note: if your device does not start reading from the usb stick, then the problem is in the usb stick itself, try another usb stick, or format it in fat32 and start again.
[FYT Android Head Units] zelixsphere:
You are correct @muzoss , thats exactly the steps i took and how I ended up stuck on the boot screen.

Thank you very much for that guidance. I didn't consider that the usb stick could be the fault. So I will try a new one. I did try the whole new attempt of flashing from fyt factory firmware but with the unit in Fastboot mode it seems to not activate. USB has power as it does start charging my phone but nothing ready or initiated from stick. That said I have a new usb stick I can try, as well as phoenix automotive did send me to update firmware for the sc7862. Now that I finally have this firmware I will attempt both the method of FYT firmware first as ideally that would be best on a new USB drive. Alternatively will try the files (2) they sent me.

@surfer63 now that Phoenix Automotive gave me the firmware update file for the sc7862 how would u like that file? I would assume you and community would like the file copy that seems to be pain to get . Please let me know. I will update this forum thread on the outcome of the 2 tests once I get some manner of sleep.

Chris
[FYT Android Head Units] muzoss:
Do these steps:

press the rts button for 20 seconds, then release it, at the first appearance of the side lights, again briefly press the rts button and so on three times, the fourth time, press the right button 4 times together and release it. the flashing process should begin
[FYT Android Head Units] zelixsphere:
I apologize @muzoss When u say rts button are you meaning reset button? The right button. I apologize what right button. On the off chance you are unclear what specific unit I have, it's a tesla style almost no buttons screen based system. There are some buttons at bottom but they only serve specific car features and nothing like manu or volume. Here is a link to the product https://phoenixautomotiveinc.com/pr...-navigation-radio-for-dodge-durango-2011-2020

I have also attached an image of the unit which should help visual explain what the unit looks like.

- Chris
[FYT Android Head Units] muzoss:
yes the reset button
[FYT Android Head Units] j0hn83:
Quick question for those much smarter than me.

Can the 6315_1.zip from Teyes most recent update be installed on a non Teyes unit?

They are supposed to be interchangeable between units but the Teyes file is much bigger.

Looking inside the .zip it looks like the bigger file is caused by a file called elable.new.dat.br

It sounds like this update fixes a bug with the launcher window that stops the launcher app working correctly and is 1 of the last things that really annoys me about my unit so it would be nice to fix.

The update can be downloaded from here
[FYT Android Head Units] surfer63:
I know :) The first image attached to your previous post is "system information.jpeg". In that image is a heading with System Info. That part says build date 31-10-2022. Read your image.
[FYT Android Head Units] surfer63:
On the bottom left next to that P button, you have a Mic(rophone) hole and a RST (reset) hole, use a bend paperclip or something alike to reset your unit. Upon reset in the "lightest soft-brick" it should start flashing the firmware. If this doesn't work in a more severe soft-brick, you reset the unit and upon appearance of the boot logo you immediately reset it again. Do this 3 times. After the third time the unit will switch to "flashing mode", no matter what.
[FYT Android Head Units] surfer63:
I think it should be exchangeable, but you have to unzip the That elable.new.dat.br is the brotli compiled raw partition image of the /elable (/oem) partition. It contains what other systems have in the AllAppUpdate.bin.

To check for compatibility you have to compare a Mekede 6315_1.zip and the Teyes 6315_1.zip.

Inside you will find a "dynamic_partitions_op_list" file and a folder structure META-INF. Inside "META-INF/com/google/android/" you will find the "updater-script".

Compare these between the to 6315_1.zip files. You will notice (I hope) that the /elable partition has become part of the super-partition. However, if the /elable parttition is the same size as the oem parttition used for tha AllAppUpdate.bin, you are good.

Maybe you even need to dig a little bit deeper, but as I am this week on holiday I can't help you with that.

One big note: On the Mekede firmwares you can play with apks and modify them as the /oem partition is read-wrtie. Once you flash the Teyes and you want to modify one apk, you need to fully flash the entire firmware again.
[FYT Android Head Units] zelixsphere:
I was successful. Turns out @muzoss was correct, the USB thumb drive decided to be flaky, trying a new fresh USB with your firmware was what fixed my issue, along with the reset method you both mentioned as well. Unit is working once again, still wonder what in the animation I used triggered the crash. I used a gif file, that was then generated into a bootanimation file, with the desc file, as well as part0 folder. Not sure how I screwed that up, but again all is well again :) Thank you again for all the help :)
[FYT Android Head Units] mancypher:
Ah okok. I found out also is a fake android 12. API level is 29. But nvm. Here in Singapore re-sell value is high for high end units. Can even sell at profit sometimes.
[FYT Android Head Units] j0hn83:
I'm not using a Mekede firmware. I'm using a 6315_1.zip from Marios MD firmware and a custom AllAppUpdate.bin with some Joying apps inside.

I compared my current 6315_1.zip with the Teyes 6315_1.zip

The updater-script file located at "META-INF/com/google/android/" on both copies creates the exact same 4 dynamic partitions.

They are product, vendor, system and elable.

The updater-script files look identical but I'll do a proper comparison later.

The "dynamic_partitions_op_list" file differs between the 2 6315_1.zip files.

Again they create the same 4 dynamic partitions but the sizes differ.

My current dynamic_partitions_op_list has

The Teyes dynamic_partitions_op_list has

This is a bit above my ability I think. I've never touched anything within the 6315_1.zip before.
[FYT Android Head Units] spendaccia:
MOD Translation:

Hi, I want to install MD edition firmware in my Uis7862 Fyt 116 unit. After installation will I lose my car stereo settings (rear camera / steering wheel control etc...)?

Ciao, voglio installare il firmware dell'edizione MD nella mia unità Uis7862 Fyt 116. Dopo l'installazione perderò le impostazioni della mia autoradio (telecamera posteriore / comando al volante ecc ...)?
[FYT Android Head Units] DaddyFinger:
Hi all, I have a question about launchers.

Remember my Chinese language only UI/firmware? This is how the launcher looks:

The one in the middle is, of course, the music player ... but it will also switch to displaying radio information if the radio is playing instead, and the 3 buttons work as | Previous station | Play / Pause (Stop) | Next station | ...

The closest launcher to it on @mariodantas 's site would be this one ... com.android.launcher4 (Target SDK 26):

But it has radio and music player as 2 separate functions.

I don't miss having a Chinese language only UI :LOL: But I actually kinda miss the original launcher since I did the switch to the Joying firmware to get an English UI.

I don't believe there is any way to customise the launcher from @mariodantas 's site to merge radio and music player control?

I did a backup of my original firmware following @surfer63 's guide on Post #4 ... is there any way the launcher can be extracted from it and used with the Joying firmware? And if it is actually possible, would it then be in English or would it still be Chinese language only?
[FYT Android Head Units] muzoss:
orginal 6315_1.zip from Teyes

kernel 04/01/2023

system 04/01/2023

customized for all UIS7862

UIS7862_ 2023-01-04_System_1672820314-mod-muzoss

UIS7862_ 2023-01-04_System_1672820314-mod-muzoss

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[FYT Android Head Units] surfer63:
The /elable partition image in the the non-Teyes firmwares is an empty partition. Upong flashing the partition size is created. The /elable partition is pre-populated with the AllAppUpdate.bin in the Teyes kernel. That is why the kernel is so much bigger. The Teyes software comes without AllAppUpdate.bin
[FYT Android Head Units] jbleasdale:
Looks interesting muzoss.

Please can you provide a little more info on this?

How have you customised this?
[FYT Android Head Units] kfkWRX17:
Has anyone gotten an external mic to actually work with an FYT unit? I bought one from Idoing, installed it, ran external mic, tested option 1 in this post: https://xdaforums.com/t/medeke-navifly-7862.4248969/page-12#post-86341115, and still no sound picked up by the unit across every app (android auto connected or just android apps installed.

So I'm going to purchase a different external mic. Any info I need to be aware of for comptability?

Thanks in advance
[FYT Android Head Units] mancypher:
Mine is working. On Bluetooth using external mic and disabling the hardware mic. Didn't try using AA as my phone is a battery drainer [Find X3 Pro].

Btw, my mic location used to be under my steering wheel. The tape not strong keep dropping off, so i lazy. I just pull the wire and place it in the compartment under my head unit.
[FYT Android Head Units] jbleasdale:
I tried everything I could with my Owtosin branded FYT. Three different external mics, multiple software updates. No luck at all.
[FYT Android Head Units] kfkWRX17:
Ok good to know. I will keep trying with my Idoing one

Sorry to hear your's didn't work. So this is a bit of a dice roll
[FYT Android Head Units] snaske65:
Evening all,would any one know where to get a map widget like some of the launchers use or the one in the vivid launcher. Also a music wiget that will show radio stations as well as dab plus stations and other music apps all in one.

TIA.
[FYT Android Head Units] surfer63:
And how old is your iDoing? Are you really sure your FYT unit has already the separation in hardware?

I clearly mention "Method #2 (units before approximately August 2022 OR with firmware before approx. August 2022):"

If your unit is too old, you must use method #2. There is no other option.
[FYT Android Head Units] surfer63:
There is not.

The FYT launchers actually have the widget, not the radio or music player. That is how interactive they are. If you want something like the widget you want, you have to write it yourself.
[FYT Android Head Units] jbleasdale:
Thanks, but I think this is a different issue.

The guidance that you reference is for how to disable the internal mic *while the external one keeps working*.

In the case of myself and the OP, the external mic simply does not work, whatever we try.
[FYT Android Head Units] surfer63:
Sorry, you are right. I misread it.

However, know that you must really firmly plug it in until you hear a noticable "click" that it is inserted. No brute force, but really some pressure.
[FYT Android Head Units] deadeye920:
I have read in some cases the external one is being interfered by the internal microphone. Have you tried to disable it?
[FYT Android Head Units] jbleasdale:
Yes, thanks.

Tried this using both methods - software and disconnecting internal mic, both unsuccessful.
[FYT Android Head Units] deadeye920:
Perhaps your external mic is faulty.
[FYT Android Head Units] jbleasdale:
Thought that too at first, but tried three of them...
[FYT Android Head Units] deadeye920:
What headunit do you have?
[FYT Android Head Units] jbleasdale:
Owtosin C4: https://www.aliexpress.com/item/1005004176674537.html
[FYT Android Head Units] surfer63:
It does have interference but not in the way that the external mic doesn't work anymore. It simply doesn't improve and gets slightly worse, but that is something else than not functioning at all.

Or FYT has introduced a new bug ;)
[FYT Android Head Units] kfkWRX17:
Thank you all for the input. Here is my plan

Quadruple check the physical connection and ensure physical click

Test the eternal physical mic (3.5mm jack -> harness -> HU) to another device to see if it works

Try to find a known working external mic, and test this

Quadruple check that internal mic is disabled (i did this in software in the factory setting, no change, but it sounds like I need to see the manufacture date to see if was made before August, and then I might have to open the unit)

Is there anything else that you all would recommend?
[FYT Android Head Units] deadeye920:
Thank you. I’m sure I read a post on 4pda that someone had an issue with the external not working until they disabled the onboard mic. But I do agree with you. It shouldn’t
[FYT Android Head Units] deadeye920:
I was going to suggest checking the wiring harness to ensure it has a good connection in the connector.
[FYT Android Head Units] kfkWRX17:
Ok, I've torn up my dash again. thank you to everyone who gave me suggestions on the mic. Here are the results of my testing. Device details again for reference: iDoing FYT unit UIS7862 MCU 2021.04.26 15:40:55 PSTAR_53_L6315_G23P48F64_V:1.0

Validated External Mic by removing the 3.5mm jack and plugging it into the 3.5mm jack on both a microsoft surface tablet and an old Moto Z play

On the moto Z play, the phone was able to register voice via google assistance. The phone is on its last legs and died, so I switched to the surface

On the surface, I made a test call to a friend in discord, changed from the surface internal mic to the iDoing external mic during the call; friend could hear me and noticed the audio change. I also made 2 recordings, one with the iDoing external mic and one with the Surface internal mic. They sounded different but I could hear both

fully disconnected the harness from the back of the iDoing head unit and downloaded a voice recorder app directly to the head unit (phone was not paired)

Recording 1: Internal mic, "back MIC switch" in Factory menu set to "OFF - Front Mic"

Recording 2: internal mic, "back MIC switch in Factory menu set to "ON - back Mic"

firmly plugged in the harness in the correct spot (it was fully seated) and re-connected the external mic

Recording 3: external mic, "back MIC switch" in Factory menu set to "OFF - Front Mic"

Recording 4: external mic, "back MIC switch in Factory menu set to "ON - back Mic"

zero of the recordings picked up any sounds.

So my conclusions are that one, the external mic does work, and 2, either the iDoing head unit doesn't understand mic input, I have failed to enable it properly, or BOTH the harness and the internal mic are dead.

Any advice?
[FYT Android Head Units] kfkWRX17:
I just had the idea to use a USB mic since my HU came with multiple cables. Has anyone else attempted a USB mic with an FYT unit, and if so, which one and what did you have to do to get it to work?
[FYT Android Head Units] jbleasdale:
Interested in this too.

I tried with a USB Jabra conference device which didn't work but I suspect needed more power.
[FYT Android Head Units] kfkWRX17:
Ok, so low-power options. Got it. I'm going to grab a cheap USB mic that I have laying around, and then if that fails, look for other options that are specific to Android. Seeing a lot of "lapel" mics designed to record to a phone, so that's promising. May also test with a USB A-C adapter on my phone. Will update in about 10hrs. If anyone has any recommendations, please share
[FYT Android Head Units] poseidon1982':
No no, the photos are a bit grainy, but I guarantee you that everything is connected in a workmanlike manner. I will post you a good more detailed photos with the respective data of the mcu and all the rest. The isec 6521 update was working 2 years ago. But now when I repeat the reset, it completes the procedure and the screen keeps flashing and it won't let me set the resolution to 1280x480 pixels anymore. It is currently set to 1280x600. And I think some application has tampered with the resolution. Another mistake I made was not turning off automatic updates.
[FYT Android Head Units] j0hn83:
FYT have crippled Bluetooth and USB on these devices.

I would not be surprised if a USB mic didn't work.
[FYT Android Head Units] kfkWRX17:
Ack. I did get bluetooth to work on mine, and wired Android Auto via USB. Can you give me some more details on what I should try to give me the best chance of getting this to work?
[FYT Android Head Units] kfkWRX17:
I tried a random USB mic that I had lying around; no dice. Will try around with lesser audio app that was recommended to me in another thread, and maybe look for an android-specific USB app

Fully suspecting a software issue on the head Unit at this point. Any other ideas?
[FYT Android Head Units] surfer63:
You already tried a lot, but did you contact Idoing and did you ask them? They are the first to contact but you don't mention that.

If your microphone connection is really defective you should contact them.
[FYT Android Head Units] kfkWRX17:
You are correct. I did reach out to Idoing first. They gave me basic troubleshooting steps which I've already tried, said "this should work", then asked for the wiring diagram for my stock head unit, so they could try to make a harness for the stock mic. Then said they'd get back to me in Feb.

Given this troubleshooting, I don't think this is a hardware issue
[FYT Android Head Units] kfkWRX17:
So i found this comment: https://xdaforums.com/t/new-ts10-uis7862-6gb-ram-128gb-head-unit-q-as.4227947/post-87253657 and thought I'd found that by disabling the radio, I would get success. No change, went to factory settings, turned off the mic, tried with the external, and still didn't see a change.

I am fully convinced that I have super unusual software issue with my unit. Any advise on flashing the unit?
[FYT Android Head Units] marchnz:
From your earlier posts you have an FTY uis7862 based unit.
[FYT Android Head Units] gspLord:
hI friend

i need some help with my headunit, i just bought it from aliexpress. an Owtosin brand Ts10 headunit but have 4/32gb spec. i read this thread many time and some hint i tried in my head unit. my question are...

1. my unit have external mic port. and from the thread i tried to off my internal mic and use external one. i try to follow the step from this thread. but can't find BACK MIC SWITCH

2. i tried to install HWGet_apk but when i open it show that my unit not FYT

3. I can't use backup script from here

4. i tried to change the boot animation but it ask for password, tried many password none is working

hope someone can help with it

thanks before for answering
[FYT Android Head Units] j0hn83:
Your unit is a TS10 and not an FYT.

Similar hardware, different software and firmware.

None of the scripts in this section will work on your unit.

This is the wrong section of the forum to be posting in for your unit.
[FYT Android Head Units] halloj:
This is the right forum for your unit.

New TS10 UIS7862 6gb ram 128gb head unit q&a's

So I bit the bullet and bought myself this head unit: https://a.aliexpress.com/_9JZiHu Ad stated that unit is 4gb ts8, but unit shipped and arrived is 6gb TS10. Plugged everything up unit works nice and smooth as expected, but one seriously...

xdaforums.com
[FYT Android Head Units] gspLord:
Yes i think so..thanks for your info friend
[FYT Android Head Units] gspLord:
Many thanks for your info...
[FYT Android Head Units] kfkWRX17:
alright. I'm going to give IDoing until Feb 1st to propose a solution, then decide if I want to bother with a flash, or see if I can return the unit and then purchase something like a kenwood, alpine, or pioneer, with a double-din adapter.

It's really unfortunate because this unit is almost everything I need, but the mic being borked is really a dealbreaker. Slow wifi is annoying but livable.
[FYT Android Head Units] Saffy79:
Hi guys,

Apologies if i have posted on the wrong thread but i have a big problem 😭 and i’v been tearing my hair out.. i have posted before on here with few other problems few have been sorted but this ones just cropped up few weeks ago and iv messed with settings and still but getting no where so i am here for help..

I have a Chinese android headunit uis7862 6+128.. its a dual system with android 10 and switch back to original car operating system.. problem i have is the touch function on the cars operating system is not working at all.. but on the android system its working fine? Its not like there is a fault with the original operating system as i can change thru dab aux etc with steering controls and it shows on unit its changing also sat nav works as street names change as im driving and all seat functions i change on my heater control show on screen as its been changed..

So far i have changed the ribbon from android board to original multimedia unit board which is attached to back of system… i have done a reset with button under mic.. i done a firmware update with files off here 3 weeks ago abut this problem started before that..

Any one shed any light on this please as i cant set my clock without going through original system software and few other things 😡

Its a android system uis7862 fitted to a Jaguar XJ X351

Any tips? Advice please
[FYT Android Head Units] marchnz:
Options migh be:

A. Review forum topic for related posts and post questions related to findings

B. Run around in circles chanting

C. Communicate with seller
[FYT Android Head Units] surfer63:
Don't cross-post. I answered in the other thread.
[FYT Android Head Units] mariodantas:
And the problem is, when we change a partition size i.e. adding thing to product / system / vendor) how to update the *.transfer.list and the final dynamic_partition_op_list ? with the new sizes ?
[FYT Android Head Units] jonnythan:
I'm having an annoyance with my Mekede M6 Pro with T-Mobile SIM. When I start up the car, it appears to have a 2G or 3G connection that is basically useless. Only after a couple of minutes does it kick into 4G, which then works fine. Is there anything I might be able to do to fix this?
[FYT Android Head Units] surfer63:
This is not for Teyes but for the other FYT uis7862 units.

Note: below is a theoretical approach. I did not test it.

If you look at the dynamic_partitions_op_list, the first one is the unisoc partition which is the superpartition. The sizes of the partitions are in bytes.

partition	size	size (GB)
unisoc	4299161600	4.3GB

partition	size	size (GB)	total
product	1058623488	1,05
vendor	351330304	0,35
system	1322008576	1,3
elable	52436992	0,05	2,75

The oem is not mentioned in the dynamic_partitions_op_list, but is 1.4GB and has about 350~400MB free space. If it is still added to the superpartition it would grow the total of partitions inside the superpartition to 4.15GB. However, I strongly think it is not inside the superpartion otherwise it would be read-only (like it is in Teyes where it is added to the superpartition)

The /data is not mentioned either but is 52GB. This one is definitely not in the superpartition.

As you can see the superpartition is 4.3GB and the total amount of other partitions is 2.75GB and with oem in total 4.2 GB. I assume that as long as you stay below the 4.3GB, you can extend other partitions and simply change the numbers.

As the partitions are recreated upon flashing the unit, both for the kernel as well as the AllAppUpdate.bin, I think you can simply reflash when things go wrong.

But again: this is a theoretical approach.

Edit: If others think I am wrong then please correct me. We can all learn from that.