yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] mariodantas:
Wish to knpw what can we do with this kind of file ?
[FYT Android Head Units] PaWill:
could you give your signapk and bat file?

when signing, the process issues a lot of warnings

"java -jar zipsigner.jar testkey.x509.pem testkey.pk8 ../build.zip ../build_sig.zip"

java version "15.0.1" 2020-10-20

Java(TM) SE Runtime Environment (build 15.0.1+9-18)

Java HotSpot(TM) 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)

Signing

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by org.bouncycastle.jcajce.provider.drbg.DRBG

(file:/G:/Teyes/work/_Kithen/tools/zipsigner.jar) to constructor sun.security.p

rovider.Sun()

WARNING: Please consider reporting this to the maintainers of org.bouncycastle.j

cajce.provider.drbg.DRBG

WARNING: Use --illegal-access=warn to enable warnings of further illegal reflect

ive access operations

WARNING: All illegal access operations will be denied in a future release
[FYT Android Head Units] surfer63:
Please share with us what you did, like Mario already asked. What are your improvements? This is a forum where we share knowledge and code with each other. If you want to keep everything for yourself, you don't need to expect further help.

However, there are some issues here.

First of all: I don't use windows and don't have a bat file. I do (almost) everything on my debian linuxd raspberry pi, and the rest on my Chromebook inside a linux sandbox. But that is actually not relevant.

I also gave the command to sign a zip in post #346.

You use zipsigner instead of SignApkv2.jar. Your zipsigner uses trhe bouncycastel alternative which conflicts with the sun.security package.

User SignApkv2 with a java 8 build. Select the java8 JRE for Windows from https://adoptopenjdk.net/releases.html?variant=openjdk8&jvmVariant=hotspot

Or use a Sun java v8 version.

If you are continuing with zipsigner, I can't help you. I have not much experience with it.
[FYT Android Head Units] PaWill:
I'm trying to port some useful features from other devices. Without details. It is not working correctly yet.
[FYT Android Head Units] PaWill:
Thank you @surfer63. I figured out how to create workable ZIP files.

A new sadness has appeared. The rebuilt framework.the jar turns out to be inoperable. I used small 2.3.4. I'm trying other smali.

Upd. I checked all sorts of versions. The result is negative.

Created-By: soong_zip
[FYT Android Head Units] mariodantas:
And where can we found that georgeous work of @gordgelin ?
[FYT Android Head Units] surfer63:
⚡ МОДИФИКАЦИИ ⚡

🧙‍♂️ Разработчик — Виталий (gordgelin)

vk.com

He asks some money for most roms though.

Also: Due to the fact that you change the partitions, the first flash is a complete "twipe_all" flash. Upgrades after that can be easily flashed and the way of adding patches like on the sc98531/7731 can be easily done again.
[FYT Android Head Units] mariodantas:
Ok thanks for that @surfer63
[FYT Android Head Units] dnfm:
I presume there's no way to keep the accessibility service enabled for specific apps without root on these things?
[FYT Android Head Units] mariodantas:
I think that the below intents....

<intent-filter>
<action android:name="com.fyt.boot.ACCON" />
</intent-filter>
<intent-filter>
<action android:name="com.glsx.boot.ACCON" />
</intent-filter>

Never happen in this UIS7862 firmware, or, at least I can't caugh them
[FYT Android Head Units] djneji:
Hello everyone, I have this headunit and in my car the buttons are covered by a plastic piece in order to fit the screen, making it impossible for me to reach the volume buttons. Unfortunately the original buttons are not compatible it seems with the model of my car, so at the moment my only option to lower the volume or increase it is to touch the icon of the volume in the status bar and scroll the volume to a specific value, which is quite impractical while driving. I tried multiple on-screen buttons to change the volume, but none of them worked. Do you have any idea on how can I get two floating buttons on screen increasing/reducing the volume? I have a UIS7862 proc and It's been now a week of researching without success.
[FYT Android Head Units] danilaur:
photo with headunit ?
[FYT Android Head Units] djneji:
Of course! As you can see, the buttons are covered by the plastic adaptor... The volume control is especially important when android auto is enabled, in which I have to use the touch assistant in order to be able to fix the volume
[FYT Android Head Units] Sahbaz73:
Does anyone know how to make aa full screen? I have uis8581a unit with car link 2.0.
[FYT Android Head Units] surfer63:
Is this not simply that you have a 10" panel inside a 9" plastic facia?
[FYT Android Head Units] djneji:
The plastic piece fits perfectly. It's done like that to mimick the appearance of the original radio LCD, while reducing the vertical space the head unit takes. So I can't and won't be able to access anyway the buttons, but would like to have something on the screen instead, which I've been unable to use.
[FYT Android Head Units] danilaur:
need 9 inch display, it is to big for you this, no ?
[FYT Android Head Units] djneji:
To be honest, no. I feel it fits well inside the car. The only problem is that I can't reach the volume buttons. But the LCD is fully uncovered, so it's a matter of simply finding a way of increasing/decreasing the volume. I tried this app https://xdaforums.com/t/joying-andr...853i-4gb-ram-32gb-flash.3897206/post-79802106 and it works like a charm, however I would like to have a sort of floating on-screen button that does exactly that. Do you by any chance know an easy way of doing this?
[FYT Android Head Units] surfer63:
You read from multiple users that your unit is too big. You should be able to use the home, back, vol-up and vol-down key.

So what you feel is not correct. The unit is simply too big if you can't use the dedicated buttons for those functions.

If you want to keep that unit you will have to live with that.

You don't mention whether you have steering wheels buttons and a CAN-bus. That would be the ideal way to increase/decrease volume.

Orherwise order an SWC universal wireless unit for your car, like this one (but there are more)

My previous car didn't have SWC buttons, so I used one of those universal ones for years.
[FYT Android Head Units] djneji:
Hi @surfer63, I'm not complaining at all of the fact that I can't access those buttons. I know the limitation this esthetic plastic mod causes and I'm living with those. I'm just looking for suggestions on alternatives. I have steering wheels buttons and a CAN-bus, but my mechanic was not able to make both the steering wheel commands and the front one to work properly. The seller has not been super helpful in explaining how to connect everything together either... The SWC universal unit is actually a very nice solution if I'm not able ultimately to make the buttons work. What I have right now is just this "schematic" here. Do you know by any chance where in my car should I connect the steering wheel buttons and how? I'm definitely inexperienced and trying to learn. I have a 2011 ford fiesta mk7, if that can help.
[FYT Android Head Units] ptuchik:
Hi everyone, does anyone know how to change the stock Music Player, Bluetooth App and Bluetooth Music App on Mekede M6 Pro 3D. The original ones look UGLY!

And also does anyone have issue where bluetooth pairable devices disappear, the list got empy, but the device itself is connected?
[FYT Android Head Units] j0hn83:
On the power port on the rear of the new head unit, pins 6 and 7.

These are for connecting 2 resistive wires from the steering wheel to work the physical steering wheel buttons. Using this method the buttons need to be learnt/programmed on the head unit.

That doesn't work with all vehicles though.

On my Kia the steering wheel controls (SWC) aren't resistive and can't be learnt and reprogrammed by the head unit. I have a canbus box that converts a digital signal in to something the head unit understands.

If your current canbus box (or SWC decoder box) isn't working the SWC buttons correctly then you need to either:

1. Try different car models in the canbus settings and see if you can find 1 that works correctly. You need to pick the correct canbus box type (XP, RCZ, Hi-world, etc), correct car manufacturer, and then try various different models of car. Unfortunately you need to reboot the unit every time you try a new car model.

2. You might need a new canbus box. There are many many types with some needing to be the exact 1 for your vehicle.

Without knowing your car make, model, year, spec, original head unit type, canbus box make/model, etc etc, there's no way for us to tell if you have all the correct bits or not

Edit: looks like the Chinese call it a Ford Fiesta MK6. It has a 9.5" screen already and they are sold from some sellers with a warning that the left hand buttons will be covered.

The older 9" model has no such issue (from Teyes at least).

So it was available in some form with the buttons working. Both Fascias from Mekede appear to have the buttons on show but that means nothing.

9" with buttons

9.5" without buttons
[FYT Android Head Units] surfer63:
Read! Read! Read!

So many info about these topics.
[FYT Android Head Units] ptuchik:
I tried to find, but with no luck, it’s impossible to read the whole forum
[FYT Android Head Units] djneji:
Thank you for the very detailed answer, I will think about your points and decide what to do.
[FYT Android Head Units] thestupidbloke:
Hi all, I just installed M6 Pro Plus 3D in my Seat Ibiza 2011 6J, it has a raise can bus decoder but doesn't seem to be working, it was set in the settings to VW > PQ, there are two options, I have tried both, neither work. I also tried VW > POLO > 2008-2018 (I think) and that didn't work either. Any ideas how to get the canbus working for steering wheel controls etc? Should this just be plug and play? As when I try the steering controls, nothing happens, but the unit does seem to recognise when I go in reverse gear (camera comes up although blank as not connected yet, and volume lowers).

An even bigger problem I now have is that the volume slider seems to be not functioning, it stays at the same volume whether I turn it all the way up or down. I have tried restarting the device as well as leaving car off for a few days for it to dona cold boot, but no luck. It was working at first but then I started changing some settings in the settings menu and it stopped functioning, now I am stuck on the same volume constantly. Does anyone have any ideas? I've searched around but couldn't find any answers.

Thanks in advance for your help.
[FYT Android Head Units] ptuchik:
Does anyone know the full list of available options in config.txt?
[FYT Android Head Units] gordgelin:
nobody knows full list since it is not a config.txt options but system variables, there can be literally thousands of them. some can be deprecated in new firmwares, some new may appear
[FYT Android Head Units] ptuchik:
I am mostly interested in enabling Wireless ADB by giving the port number and if there is an equivalent for `wm overscan [reset|LEFT,TOP,RIGHT,BOTTOM]` like `ro.sf.lcd_density` for example.
[FYT Android Head Units] nickrod93:
Anyone know why when I try to install launchers from mariodantas site it tells me "app not installed"?
[FYT Android Head Units] surfer63:
Again search! If you would have simply searched for "wireless adb" in this thread or forum, you would have found this (and more). So don't tell me you can't find it if you did not even search on the two words in your own question.

Unfirtunately there is no property to set the overscan parameters. It remains a command.
[FYT Android Head Units] ptuchik:
Man, stop writing me "search" because:

1. I am doing deep deep search before posting, I have more than 20 years experience in research

2. What you found and mentioned I found on my first search, but it doesn't have any relation with what I asked

3. Try to moderate on some others, who is really spamming or asking random repeating questions.

My questions are TO THE POINT and never REPEATING!!!! So if you don't know the answer or don't want to answer just don't answer, NEVER write me "search" again!!!
[FYT Android Head Units] surfer63:
Whatr kind of unit do you have? Please share system info from your unit. These launchers will only install on FYT models, but not on the latest real Android 12 Qualcomm units.
[FYT Android Head Units] surfer63:
I did not say you are repeating. I said that you are not searching.

I did type "read! read! read!" though. That is indeed incorrect. I should have typed "search, search, search" (and then read it of course).

You mention "I am mostly interested in enabling Wireless ADB by giving the port number and ...".

If you had search on "wireless adb" you would have found multiple answers, including the one I already provided to you. To me that has nothing to do with deep search.

And as another example your earlier question about the bluetooth paring: If you had searched on "bluetooth paring failed" you would have many results.

Again: where is that deep searching?
[FYT Android Head Units] ptuchik:
As I said already I did deep search with various keywords and checked each and every result, by reading the next and previous 20+ posts to check the overall discussion and find something related to my question, but found out that either it is not related to what I exactly need, or the topic left incomplete, or it was 2 years old discussion, and as we all know every day Chinese bring something new and blocking something old...

That other example was not about pairing failed, if you read my post, it was about successful pairing, but after closing the bluetooth app and coming back the "Pairable Devices" list is totally empty, but the phone is still connected and fully working. It seems to be a bug with showing already paired devices

P. S. You are just not focusing on the main meaning of the post, just finding some keywords and writing "go and search" to keep the forum clear, which is not bad, but sometimes not to the right people and post...

So again: Please, if you don't know the answer to my question or don't want to help me just ignore and let others help.
[FYT Android Head Units] surfer63:
I am sorry. You are completely right about that one. I did read it as that your phone was paired and other devices not.

I just checked my car unit (M500S) and it simply shows my phone (immediately connected) and my wifes phone (not connected) and my OBD dongle.

Only one phone can be paired at one moment though.

That does indeed seem to be a bug in the new firmware.
[FYT Android Head Units] ptuchik:
That's ok to have only one phone connected at a moment, that's a normal behavior, but the issue is that for example I have 4-5 phones pre-paired (not connected, just previously paired) but the list is empty, so to connect a previously paired phone I need to do a new search, find that phone and then connect (which works as a workaround), however the last used phone connects automatically, without appearing in the list
[FYT Android Head Units] ptuchik:
I can record a video a bit later if you need. And also as the "Pairable devices" list doesn't show any phone, even the currently connected one, to disconnect it you need to go to dialer, which is showing the connected phone on top, then disconnect from there, then come back to that "empty" list and tap on search to connect the other phone
[FYT Android Head Units] surfer63:
Now that I understand you correctly, I believe what you say.

I think it is better to record the video for Mekede to show them what is going wrong.

And I would not post in this thread, but in the Mekede M6Pro thread. There are possibly more users having the same issue.

And did you already download the 5 December firmware? Or is your unit newer than that?
[FYT Android Head Units] ptuchik:
I wrote to them, they don’t understand what I need. And the firmware is December 5, it came with September 23 firmware with the same issue, and now on December 5, still the same.

And by the way I just flashed with MD-Edition based on MKD M6Pro December 5 firmware, it successfully passed the process but FYT management app says “This device isn’t compatible with MD-Edition”, is known thing (not searched yet) or I need to check in optimized kernel thread?
[FYT Android Head Units] surfer63:
This is a bug in the latest FMC, but unfortunately Mario is already long time unavailable. Mario made a version for Teyes and a version for non-Teyes FYT units as Teyes is different (stupidly different). In the latest versions he reversed the plaftoform check by accident.

I fixed that check already earlier by reverse engineering Mario's FMC app.

The next step you will get when you pass this screen as that it will request for registration (see image below. Click to get full sizee. Sorry in Dutch). That doesn't work either.

I tried to bypass this screen, but could not succeed. Nowadays all java is obfuscated and the same for smali.

What I now did is when you click "Cancel", it will not stop the app but continue (I removed the finishAffinity() and system.exit(0)).

I did that Yesterday.

If you want to test, please find attached an installer. Unzip it to a clean usb-stick and flash it.

Note: Mario already mentioned that his version is beta, so this is certainly beta. It will not do any harm to your system, but it might not work entirely correct. I tested it myself and screen lock doesn't seem to work without registration. I will see if I can work-around that as well. As I don't have (or want) a rooted system, I did not test the root functions yet.
[FYT Android Head Units] ptuchik:
Thanks a lot, then I will roll back to original version, and wait for the stable one. Thanks for your help
[FYT Android Head Units] arca114@gmail.com:
A Happy New Year to everyone. What happened to our friend Mário Dantas??
[FYT Android Head Units] casper9679:
Firstly, I apologize, I am weak in English. Secondly, I did not understand mucho_O.

I would like you to help me by giving me the link to the correct file for my device, please.

I have a problem with my voice on calls being very weak, and I heard that this problem can be solved, knowing that I have two microphones, internal and external.

My device information is below

______

Please I need a new Firmware link

MEKEDE M600S Carplay 6Gram+128G (4G+wifi) android 11 (Ips Screen 1280*720 )

(DSP+RDS)

________

UIS7862 Octa-Core 1.8GHz FYT 7862

kernel:#209 SMP PREEMPT Tue Dec 14 08:41:01 CST 2021

platform: (63)6315 F Full Band carplay3

touch:goodix 911_1060 (c3fa42ce)E:0

panel:L4-MIPI-SAT-ICN9707_720*1280_1_460M 20201224 16:16:584

radiotype:tda7708_7708(0)

audiotype:dsp55

cs0mr:12010701,cs1mr:52010701

f_v:Ls50

App 1280*720 2021-09:57:06 10-11

System 2021-12-14 09:01:45 Tuesday
[FYT Android Head Units] j0hn83:
Everything is explained in the 1st 4 posts n this thread. Please take the time to read them over a couple times.

The latest Mekede firmware can usually be found on their site. They use an upload site called the nutstore, but their account is currently inaccessible so you can't download from there.

Message Mekede and they should send you the latest firmware.

Your unit is Android 10, not 11 (despite what it says). There is no way to upgrade above 10.

Your unit has an internal and external mic, both always on. There is a very small tweak that increases the gain of the mic but it does very little. You need to connect a good quality external mic and open the unit to manually disable the internal mic, or deal with both at the same time.

No way to fix this.
[FYT Android Head Units] casper9679:
Is there a problem if I install this ROM?

Joying UIS7862 System Car Stereo Latest Update

Joying UIS7862 System Car Stereo Latest Update 　 Note: this update is only workable for the UIS7862 System car radio. Please contact us if you are not c

www.joyingauto.com

____

As in the attached picture

____

File link

Android 10.0 1280X720 MIPI Screen New UI 2023.8.31.zip

drive.google.com
[FYT Android Head Units] j0hn83:
Yes. Please take time to read the 1st 4 posts.

Installing a firmware from another manufacturer with a different ID of your Mekede (116) will give a permanent error on the screen unless you make changes to it.

You can use the Joying firmware but it requires a small change be made to it. It's all explained on the 1st 4 posts.

Alternatively install the Joying firmware and use the tool to change hardware ID after this. Again this is explained in 1st 4 posts
[FYT Android Head Units] casper9679:
I express my gratitude to you

Thanks
[FYT Android Head Units] abd alaa:
Does it work with M6Pro ?
[FYT Android Head Units] abd alaa:
Can you re-upload it please as it is removed from Mekede's website.
[FYT Android Head Units] Specy01:
I'm sorry, but I don't know how to do it, it was among the apps present in the firmware. You can search if you can find it elsewhere, I didn't find it on the "play store
[FYT Android Head Units] abd alaa:
Can I flash it on the normal M6Pro ?
[FYT Android Head Units] Barykelo:
I would guess not because on the MEKEDE website the M6Pro has its own software.
[FYT Android Head Units] abd alaa:
But if the same H/W and other specs, It should work, that's why I'm asking.
[FYT Android Head Units] j0hn83:
It's not the same hardware. The M6 Pro has a different motherboard and different ms.apk
[FYT Android Head Units] abd alaa:
Are you sure ?

Because on the product page on Aliexpress, I can see that it is the same H/W.

https://aliexpress.com/item/1005004863969016.html?gatewayAdapt=glo2nld
[FYT Android Head Units] Matt Devo:
the M500/600/700, M6Pro, and M6proPlus can all run the same firmware. I resell all 3 models and use the same (M6-based) software on all, only the config.txt differs.
[FYT Android Head Units] j0hn83:
Reading back I'm really not sure what you're asking. You quoted a post back in August asking if it will run on the M6 Pro.

I've assumed you meant an older Mx00s device.

They are different hardware to the M6 Pro/M6 3D.

The page you linked shows the different motherboards and explains the differences.

@Matt Devo has confirmed the M6 firmware now works across devices.

I can tell you for 100% it did not work the other way round at release. They have completely different DSP's and flashing the M6 with the Mx00s AllAppUpdate.bin resulted in no audio.

Comparing the main ms.apk they are still quite different in the latest firmware so I hadn't personally tried flashing between them
[FYT Android Head Units] j0hn83:
Do you happen to know if it works the other way as well.

The Mx00s AllAppUpdate.bin resulted in no audio on an M6 Pro (at least at launch) as the M6 runs a newer DSP(39 vs 38 on the older devices).

I don't know if they have updated the ms.apk in the older devices firmware to include the newer DSP used on the M6.
[FYT Android Head Units] Matt Devo:
no, it does not. Additionally, the Mx00 firmwares don't have support for the UIS7862s used in the M6 line. But there's nothing in the Mx00 firmware not in the M6 firmware, so there's no reason to run it at all IMO.
[FYT Android Head Units] j0hn83:
Didn't know that, cheers.

Edit: but doesn't the Mx00s line up now have the UIS7862S?

So newer Mx00s firmware must work with the 7862S now at least, if not the newer DSP's