yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Guilherme J. Ceretta:
Thank you very much, your answer was very useful to me.
[FYT Android Head Units] Matt Devo:
so I use a custom crafted updater image to install my preferred combination of AllAppUpdate, 6315_1.zip, etc for my HUs, which includes APKs for a launcher, icons, etc installed via 7862lsec.sh to /oem/priv-app/ and that all works well. I'm trying to also use that script to update the CarLink apk (which I've removed from AllAppUpdate) to the latest (currently 2023-08-07) which has all required libraries internal to the APK. For some reason, the installed CarLink app will run, but shows a black screen and then quits when the phone connects. If I reinstall the APK from file manager it works properly. Any ideas what I'm missing here that's causing it to fail when installed via my 7862lsec script?

edit: seems I just needed to copy the arm64 libraries to an external folder like the original version of carlink, and all good
[FYT Android Head Units] olemann96:
I have a small buzzing sound from front left speaker. It disappears when i put the device in airplane mode. Any suggestions to get rid of this?
[FYT Android Head Units] AxesofEvil:
Edit: So I guess the answer is that this is a QF001 unit and not FYT. That is probably fine for my needs, but maybe means I won't be able to use it to debug as I had hoped. Now to learn more about it, and if development is possible. I opened it up, and the hardware visually looks the same.

I have an M500 that I bought in April 2022 that works fine. I just bought a 2nd unit off Aliexpress that I thought would be the same (uis7862, 4/32). I wanted to do some development on it without mucking with my in-car system, and then plan to eventually put the new unit in my old truck.

The new unit looks identical to my M500, with a different interface (it reports being Android12, but of course is just the same Api29) and it seems to have Z-Link instead of the car-Link app.

When I ran HWGetInfo, it repors it cannot find any FYT Properties, though it does dump many relevant .txt files.

If I try to use the backup or getinfo script on the USB, it does not detect it (and on manual reboot, it is not loaded), but I can open the USB drive in file explorer and see the files.

The sysyem reports:

System version: QF001.20230824.202940_v2.69_02

MCU version: QF03.V01.05.20230617.001121

Dpi: 1280x720

DSP: BU32107

Radio: TSC4745

CPU: 1.8GHz x8 - UIS7862A

Basaband: FM_BASE_19C_W20.42.1|sharkl5pro_modem|10-12-20 16:42:02

properties.txt is attached

Any ideas how I can proceed?
[FYT Android Head Units] old.splatterhand:
It's not a Fyt unit. You should take a look here: https://xdaforums.com/t/general-dis...-not-fyt-based-read-first-post-first.4525675/
[FYT Android Head Units] Dpowa:
Hi, I'm trying to figure out how to to modify the screen brightness. I have a light sensor in my dash that during the day turns the HU into night mode, therefore dimming the screen to unreadable when it has any light. Only when it's hidden from the outside or night, that it will go back to day mode and be too bright at night. This is annoying especially during dusk when it flips back and forth. And this is with the headlight switch set to off. Also, I'm looking to keep the screen off when I use the SWC.

I've been looking to see if there's a configuration that I could adjust, but I haven't found it. I figure there's some configuration as the dimming "time control" is set to 7:00 - 19:00. So there has to be a way to adjust the time control and "small light" control. As of right now, I'm unzipped AllAppUpdate.bin and looking through to see if there's a number to adjust or if I have script to add. Just looking for someone to point me in the right direction.

Full disclosure: I'm no coder but I want to figure things out.
[FYT Android Head Units] fra_dta:
Hi, some questions for You all.. hope somebody can help me

I can't understand why my Mekede M300s starts always from scratch (no time set, no apps working except Navigation, no default Radio and no Navradio+ active) when I turn on the car, but the original radio and Navradio+ show all the station correctly registered when I start one of them or both. The cables are correctly set (yellow to B+ and Red to Acc). Volume is set to 5 upper line but no sound until I start one of them manually.

I could have incorrectly set the General --> Factory --> Reverse power supply (Be careful !: Switch functionality of Cont and ACC inside radio) to ON, I don't remember if the original position were OFF or ON

Could it mean something?

What is the original position? (OFF or ON)

Edit: I decided that the normal position should be OFF, and set it in this way

I still have my Mekede M300s starts always

from scratch

(no time set, no apps working except Navigation, no default Radio and no Navradio+ active BUT some BACKGROUND NOISES at volume 5 as reported in the upper bar) when I turn on the car, and the original radio and Navradio+ show all the station correctly registered

if I start one of them or both

.

Can anybody help me to understand WHY please?
[FYT Android Head Units] Guilherme J. Ceretta:
Dolby Atmos, macrodroid
[FYT Android Head Units] samplerwrcPL:
Does anyone know of a way to force parking sensor graphics to display when driving slowly forward on "D" gear? I have only sound from the CANBox module but I have no idea how close I am to the obstacle.
[FYT Android Head Units] Cavalier Condorelli:
Is strange but I cannot find an existing answer to my question so far:

Is there a way to FURTHER increase max audio volume over the max default one?

Current settings are:

Sound -> Power Conditioning (set to max 60)

Factory -> Volume balance settings (set to max 10)

I'm using the optical audio out but RCA output is only a little bit louder.

In comparison my previous MTCB unit had a higher max volume output.

Thank you.
[FYT Android Head Units] Clandaries:
Root and use Viper4android.

Use Rootles JamesDSP.

Buy a DSP amplifier like i did an increase volume.
[FYT Android Head Units] Cavalier Condorelli:
I already have an Audison AP8.9 dsp amplifier, but the the lower sound comes from the unit.

I do not want to introduce any distorted gain in the middle, all enhancements of DSP app is set to off right now.

Maybe Viper4Android could be a solution but I would prefer if there was something in the config files to raise for example power conditionign above 60.
[FYT Android Head Units] Clandaries:
I am using this one. You can rise the volume by about 60% or more.

My max volume is now 10 atm and it is really loud.

https://de.aliexpress.com/item/1005004886754213.html?spm=a2g0o.order_list.order_list_main.19.2f2f5c5fplWme8&gatewayAdapt=glo2deu
[FYT Android Head Units] Specy01:
Excuse me @surfer63 before installing the MD Edition of @mariodantas and your OK édition, I wanted to backup my configuration using the application you inserted in post No. 4 of this treath. I had the error in red as in the attached photo, what does it mean?
[FYT Android Head Units] surfer63:
Most probably nothing other then that it couldn't backup the symbolic links . I still have to look into that.

What is the size of your AllAppUpdate.bin and check it with winzip, 7zip or something else. Does it look good? Is it not giving errors when opening in the zip program? Rename the extension to .zip if necessary.
[FYT Android Head Units] Specy01:
From the file properties it tells me 826 MB. 7zip opens it without any problems. It seems correct to me as an AllAppUpdate file.bin but I don't have enough experience to be sure. Here are the photos
[FYT Android Head Units] prokiller1199:
Sounds like a silly question, but can I change the logo to something else?
[FYT Android Head Units] surfer63:
Seems completely OK.
[FYT Android Head Units] Specy01:
Thank you for your reply
[FYT Android Head Units] Xcaptain:
Open and edit the attached (blank) logo_360.png and put it under the 'oem' directory on a USB with lsec631xupdate file. Then proceed to a normal firmware update procedure (without the actual flashing).

Video:
[FYT Android Head Units] prokiller1199:
cool thanks!
[FYT Android Head Units] fabiodedo:
exactly my unit. (y) what is the latest firmware we can use on it?

(on the manufacturer Mekede website there is no longer the link for the specific M700s model...)
[FYT Android Head Units] Specy01:
I installed the firmware of Mekede of 14/03/2023 (but I'm not sure if the right date is this). I downloaded it from Mekede's website. You have to go to support,there are various files there. While before the type of HU was specified, now there is the type of processor and the size of the screen. Then you have to download the file where it says 7862 9-10".

The password is identical to that of the HU settings. If you also have the 360 you have to download where 360 is specified.

I hope I have been helpful

I wanted to ask the experts who know more than I do. It is possible that a 6315_1.zip file may interfere with the car's ECU in some way. This question because it seems to me that since I updated the HU with the firmware of Joying (which had an updated 6315_1) my LED daytime running lights no longer work normally. For sure they work because if I put back the old standard car radio the LED daytime running lights behave normally.
[FYT Android Head Units] surfer63:
The latest version has an applications date of 31 August with a kernel date of mid May.
[FYT Android Head Units] Specy01:
Excuse me, I was referring to what I installed, that is, when I downloaded it from the site was present that version.

Surfer, do you think that the 6315_1 file can affect the behavior of my daytime running lights, as I explained above? To me it seems strange, but I only have this as a solution since they behave normally if I put back the standard stereo. Maybe I should try to leave the standard stereo in place for a few days. But certainly before everything worked perfectly even with the HU, and I could also set their meaning during the day through the "vehicle setting" app or maybe it is the update of this app that has ruined something.
[FYT Android Head Units] surfer63:
Did you flash the entire Joying firmware or only the kernel?

It can be that the CANbus apk from Joying is lsighlty different from yours. Or the Canbus configuration itself.
[FYT Android Head Units] Specy01:
I flashed the entire Joying firmware, but later, after a few months, I flashed with the entire Mekede firmware. If it was the Canbus apk different, putting the Mekede firmware back would have to work again I think. But I would like to give it a try is it possible to install an old Canbus apk? If so, what is the name of the apk? And where is it? How do I install it?

I do not think the problem is due to the configuration of the canbus, because I always set it in the same way
[FYT Android Head Units] gordgelin:
if you do not know exact version of "canbus" services or firmware version you had - nobody knows. they are updated constantly
[FYT Android Head Units] Specy01:
Thanks gordgelin, Joying's version was the:

While the current version of Mekede is:

But I'm realizing that before the update of Joying I had an app with the name "car ui"

While now, I don't have any app with this name, but I have an app called "vehicle setting

Could that be the problem?
[FYT Android Head Units] danilaur:
You have Navifly M700S and install 2 firmware ?
[FYT Android Head Units] Specy01:
No, , actually I updated more than 2 times, 🤭 but obviously at different times; Every time there is a new update I try it, in the hope of having something better
[FYT Android Head Units] surfer63:
Does anyone know how to make the splitscreen resizable?

It starts by default in 50:50 ratio but I can't change the left-right ratio by dragging the slider in the middle..

You should be able to adjust it continuously to for example 60:40 , 70:30, etcetera.

Of course I did set the "Force activities to be resizable" in the Developer options (and rebooted), but that doesn't help. I also set the "Enable freeform windows" to see if that would help (not logical), but that didn't help either (logically).

And the apps I use all support that resizable option, so actually I should not even need to use below setting, because that should only be necessary in case an application does not support to be resizable.

This worked perfectly on my old Joying FYT PX5. I can't test in on my old sc9853i as the screen doesn't work anymore.

This annoys me already for quite some time, but I still haven't found the solution.

Does anyone know a solution for this on our FYT uis7862 units?

Edit: And it is launcher independent.

Edit 2: In the config.txt there is a standard property "ro.fyt.splitscreen=0". I already changed that to see what the result would be, but definitely not what I hoped it would do.
[FYT Android Head Units] gordgelin:
splitscreen is non-resizable by design in the framework. no options will help. but it is possible to split screen in other ratios with external commands from macrodroid etc for example, not very convenient.

probably it is possible to patch firmware or create some kind of magisk module to resolve this also
[FYT Android Head Units] surfer63:
Thanks. You seem to know almost everything.

With "framework", you mean the framework-res.apk?

Edit: No, it is not in the framework-res.apk
[FYT Android Head Units] gordgelin:
no it is both android framework itself and systemui

i've seen somebody already tried approach with lsposed module here
[FYT Android Head Units] slyfurtuna:
Good morning everyone, I'm asking if you can help me, unfortunately I installed a firmware that after rebooting the screen is split in half, I then tried to install the original one and the screen always remains the same and I can't use the touch to go to the menu. Thanks (car radio and a 7862 -2000x1200)
[FYT Android Head Units] surfer63:
Below some "thinking out loud". I hope to inspire others to find a solution that I can use as well ;)

It is indeed inside the SystemUi.

I am now comparing the AOSP sources (https://android.googlesource.com/pl...ystemUI/src/com/android/systemui/stackdivider)

with the FYT SystemUI. I think it is inside com.android.systemui.stackdivider.DividerView.

But this Xposed module from pijulius seems nice.

For the Sofia and PX5 I also wrote Xposed modules, but it means I have to root my unit again.

I will spend some hours on the code and see if there is another solution by adapting the SystemUI itself, but I am already afraid I will not be successful.

It is strange though. I can find below in the FYT SystemUI code. And it also comes with the (translated) strings in res/values to tell the user what they do mean:

accessibilityNodeInfo.addAction(new AccessibilityNodeInfo.AccessibilityAction(R.id.action_move_tl_full, ((FrameLayout) DividerView.this).mContext.getString(R.string.accessibility_action_divider_left_full)));
if (snapAlgorithm.isFirstSplitTargetAvailable()) {
accessibilityNodeInfo.addAction(new AccessibilityNodeInfo.AccessibilityAction(R.id.action_move_tl_70, ((FrameLayout) DividerView.this).mContext.getString(R.string.accessibility_action_divider_left_70)));
}
if (snapAlgorithm.showMiddleSplitTargetForAccessibility()) {
accessibilityNodeInfo.addAction(new AccessibilityNodeInfo.AccessibilityAction(R.id.action_move_tl_50, ((FrameLayout) DividerView.this).mContext.getString(R.string.accessibility_action_divider_left_50)));
}
if (snapAlgorithm.isLastSplitTargetAvailable()) {
accessibilityNodeInfo.addAction(new AccessibilityNodeInfo.AccessibilityAction(R.id.action_move_tl_30, ((FrameLayout) DividerView.this).mContext.getString(R.string.accessibility_action_divider_left_30)));
}
accessibilityNodeInfo.addAction(new AccessibilityNodeInfo.AccessibilityAction(R.id.action_move_rb_full, ((FrameLayout) DividerView.this).mContext.getString(R.string.accessibility_action_divider_right_full)));

And these "action_move_tl_30" and "action_move_tl_70", etcetera are then again in the com/android/systemui/stackdivider/DividerView$2.smali.

It would mean that split ratios of 70:30, 50:50 and 30:70 are possible. I am completely fine with that, but now the question remains on how to make it work.

(And maybe it is just a very precise left-right dragging of the divider to the 70:30 or 30:70 area. I will also try that in an hour or so)

Edit: And trying to really precisely drag the the divider to the 70:30 or 30:70 position does not work. I even put marks on my screen to getthe exact position.
[FYT Android Head Units] gordgelin:
These ratios were available back in 2020 but were removed from all firmwares (including sofia) in the end of 2020. So yes, probably it is pissible to get them back
[FYT Android Head Units] surfer63:
I suppose it is because those "stupid" FYT applications are not resizable and only have a very simple if-then-else to check if displayWidth == "some number" and "this program" (music player or radio) is in (0.5 * "some number"). If "this program" is in (0.5 * "some number"), it must use the "half_horizontal" layout (or half_vertical for Tesla style screens).

I think that is why FYT blocks other splitscreen ratios.

The "initializeSnapAlgorithm()" and sub-methods in "DividerView.java" in the FYT SystemUI are simpler than the AOSP methods. FYT only checks for "null" and "middleTarget".

And FYT uses some boolean "z" which I expect is set to "true" to always have the "middleTarget". But I was not able to find/track that boolean yet.

(And let's call it "z" to make it extremely hard to find it in all that code between all those other words with a "z" inside).
[FYT Android Head Units] Specy01:
I downloaded the firmware for 7862 9-10" of 07/09/23 from the Mekede website.

I have a problem when I unzip the AllAutoUpdate.bin file with 7zip, the error is : "Heather's error". If I unzip it with winRar I have no error.

Do any of you encounter the same error? Do you think that file can be used to update the HU?
[FYT Android Head Units] surfer63:
7z gives indeed the "Header error". This can have several reasons, but it could be due to the windows CIH virus, so run a virus scan on the files. (As I run Linux I am not vulnerable to it).

I ran a fix with "zip -FF AllAppUpdate.bin --out AllAppUpdate2.bin"

Then I unzipped the original bin and fixed --2.bin respectively to folders org and fixed.

Then did a full diff (diff -bur org/ fixed/) and all files in both folders were binary identical.

Conclusion: apart from that "possible" virus, you can simply use it to upgrade your system.
[FYT Android Head Units] Specy01:
Thank you for the complete and comprehensive explanation
[FYT Android Head Units] surfer63:
The app date is from 07 September 2023 and the kernel date from 23 September. Despite earlier mentions that I would stop, I will create an OK/MD-kernel from it.
[FYT Android Head Units] Specy01:
Post erased because wrong post. Excuse me
[FYT Android Head Units] miguelangellv:
Hi. I have a UIS8141E (SC7731) .

When it connected to internet, it reboot automatically. If connect to a wifi without internet not reboot...

I try flash a firmware, but, when excecute "delete /data", it reboot too... I cant flash nothing

I think that the partition is broken, Any way to recovery the partition?
[FYT Android Head Units] ahmed68:
This is what the Mekede M400S looks like with full teyes activation , I did this to understand what activation depends on , I need this for researchdownload tool firmware for PC , for uis8581a (sc9863) firmware ready .
[FYT Android Head Units] ahmed68:
when I made the firmware mod I used product in the super block , product is the main section in the super block , many said that my method is not correct ,I saw the firmware from this who said about the May firmware that it was wrong added the entire application in a new section in the super block (vve) , this caused a reboot for the RAM because of this everyone complains that the system is working slowly .
[FYT Android Head Units] ahmed68:
File on MEGA

mega.nz

# begin fota properties

ro.fota.platform=SC8581

ro.fota.type=navigation

ro.fota.oem=normal8581

ro.fota.device=normal8581app

ro.fota.version=QP1A.190711.020 release-keys_20230922-1648

# end fota properties
[FYT Android Head Units] ahmed68:
if anyone has a question or suggestion, you can find me mod edit; Telegram link removed

ahmed68, As per Forum Rule 5 & 11 (quoted below), your link to your Telegram group and part of your statement has been removed. As the rule states, "Encouraging members to participate in forum activities on other phone related sites [which Telegram is considered; along with also being considered social media] is prohibited" as it is also considered promoting "...similar / substantially similar to XDA-Developers.com...a competitor...site with purposes and aims similar to those of XDA-Developers.com" & "self-promotion is forbidden...social media...random links will be removed." What you communicate & exchange privately & directly is out of our hands -- as long as it is not posting the link and promoting it here.

Please refrain from posting as such in the future.

If you are interested in XDA Developers Forum's stance on Telegram, it is explained in further detail in the thread/url below.

Telegram Chat Channels - Way Forward

WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...

xdaforums.com

Thank you for your cooperation,

simplepinoi177 FSM

XDA Developers Forum Rules said​

11. ​

Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.

Encouraging members to participate in forum activities on other phone related sites is prohibited.

Off-site downloads are permitted if the site is non-commercial and does not require registration.

Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:

A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.

B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)

5. ​

Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
[FYT Android Head Units] surfer63:
You did a very nice job!

According to Android specifications, the product partition is not for 3rd party software like the FYT software. But if you make a custom ROM, who cares?

In the FYT units the product partition contains the Google software, in the Chinese units it contains Huawei and Beidou software.

In your case it contains your modded software. Who cares.

But otherwise you could put it in system (like Teyes does) or create your own AllAppUpdate.bin.
[FYT Android Head Units] ahmed68:
All new firmwares are not used AllAppUpdate.bin for ota
[FYT Android Head Units] gordgelin:
it is nice to see you still trying to reverse my firmware but still you do not understand that i've added nothing to super block and you still do not understand why all teyes (and some other) software stopped working when moved to product despite i explained it to you earlier (that is why you removed all this software and replaced with working versions from different generic fyt firmwares).
[FYT Android Head Units] gordgelin:
OTA will not work on modded firmwares anyway, whether it is AllAppUpdates or not
[FYT Android Head Units] gordgelin:
main part of the job was to convince teyes support to activate m400 as x1, respect for this, it wasn't easy for sure
[FYT Android Head Units] surfer63:
I also say your replies to him about copying/modifiying modded firmwares. I had not followed that in depth.