Database Info

Question Questions before touching new unit

Hello guys,
I just found a local shop in my country for head unit and they installed the unit for me.
Everything was working except the 360 camera but they put a relay and now it's fine.
Spoiler: The Unit
Android version : 10
Baseband version :
FM_BASE_19C_W20.39.2|shark15pro_modem|09-28-2020 20:23:22
MARLIN3_20A_W21.25.1|sc2355 marlin3 Jite|06-21-202104:16:29
Build number :
QP1A.190711.020 release-keys
System Info
APP2021-07-09 10:31:45
CPU Info
CPU:UIS7862 Octa-Core [email protected] GB(Memory) + 64 GB(Storage)
MCU Version
2021.07.16 11:12:21 NOR_53_L6315_G23P48F64_V:1.0_FYT
Bluetooth Version
BLINK_2161 _RELEASE/2021:09:14:17:44:20 blink
CAN Protocol Version
XC8210910 FaOaCO
I would like to change the interface I really don't like it,
I tried different Car Launcher but still not very happy..
I prefer to ask if it's possible before crashing everything (I did a backup in case)
I don't have any information about the vendor
Then if I understand I will have to choose between Mekede, Joying and Teres
Thank you for your help

FYT = 1

Yes I found that in the backup I did with your apk
So it means that I can proceed ?

You can just install launchers and uninstall them if you don't like.
You can toggle between the home launchers also in the apps default.

Im looking for something customizable
For exemple I’d like to see my km range on the main screen or the average consumption.
Also for the speed, it use the gps value but is it possible to get this value directly from the car ? Same as the rpm

launchers are the way.
I like AGAMA but CarWebGurus has good support and customizations as well as Fcc CarLauncher or Car Launcher (free/pro)

Thank you I will check them out !

I have the exact same unit. What is the brand and model of this unit?

badai said:
I have the exact same unit. What is the brand and model of this unit?
Click to expand...
Click to collapse
There are no 'brands' only made up sellers of various chinese origin factories. FYT =1 according to first post

marchnz said:
There are no 'brands' only made up sellers of various chinese origin factories. FYT =1 according to first post
Click to expand...
Click to collapse
what does FYT=1 means?

OBDLink MX+ problem with android 9 & 10

hi,
i cant seem to pair my obdlink mx+ to my android 10 px5 or px6...it discovers it but no pairing..ive tried some commands for obdlink initialiaze found on the internet like STBTDN OBDII , STBTCOD 001F00, STBTCOD 200300 etc but nothing..before with android 8 all worked fine..chinese obd's work out of the box, but its a same to throw away my obdlink because it has some other features too..someone has the same problem with me and managed to solve it? i read some where that the reason may be that mtcd firmware asks for AA:BB:CC:11:22:33 type of mac address in obd readers...but i have no clue how to change that..

.

Search results for query: Obdlink
forum.xda-developers.com
.

marchnz said:
Search results for query: Obdlink
forum.xda-developers.com
Plus setting legacy pin. Why post that? because I know how to pair OBDlink LX and MX on MTCD platform, I have both and you completely missed the post that gave you what you need to get it to work.
Also, your post has hallmarks of joining to for support, not development. Quick to ask, not to contribute....
FYI, the seller is your first point of contact - "paid support"
On my ignore list.
Click to expand...
Click to collapse
i already saw those threads and the commands dont worked, thats why i started a new thread

Question New head unit unsure of model number. Vendor is is Navifly/mekede

Looking for some info as I got a new head unit from a friend and was looking at how to identify the specific model number and features and update firmware.
HWget info has manufacter as 116 boardtype F, platform 6315
it has a sticker that says 9inch/836/4g/6+128/720/B1/CP
I know it is a 9inch 4g capable, 6gb/128rom, 720 screen with built in carplay
I don't know what the 836 and B1 mean.
Some additional questions beyond simply identifying this:
EQ says "surround sound has been closed" when you select the surround tab
Can you get carwebguru to recognize the BT player?
How to tell if this can support 360?"
can 360 be added (am conformable with soldering on the mainboard)
carlink 2.0 does not connect to phone
what is "plug in serial device setting? Has options "accelerator / accelerator3b / kq TPMS / serial plugin 360"
I thank you in advance.

Post android system information directly from Android, including MCU version

it's a Navifly 7862

jdoe6783 said:
it's a Navifly 7862
Click to expand...
Click to collapse
No such thing

marchnz said:
No such thing
Click to expand...
Click to collapse
https://www.google.com/search?q=nav...oAA&biw=2512&bih=1336&dpr=1.5&ih=1336&iw=2512 yes it is.

jdoe6783 said:
https://www.google.com/search?q=nav...oAA&biw=2512&bih=1336&dpr=1.5&ih=1336&iw=2512 yes it is.
Click to expand...
Click to collapse
They are made up brand names. The are sellers of various factories.

marchnz said:
They are made up brand names. The are sellers of various factories.
Click to expand...
Click to collapse
Ok well that's what pops up when I copied and pasted the information you gave into Google. You can't say something isn't real when I show you proof contrary. Also if you can give more info like an MCU number instead of the vague HWinfo results people can actually help you pinpoint a specific model instead of "supposedly fake" head units.

gossipninja said:
Looking for some info as I got a new head unit from a friend and was looking at how to identify the specific model number and features and update firmware.
HWget info has manufacter as 116 boardtype F, platform 6315
Click to expand...
Click to collapse
Manufacturer ID =116 already limits it to Mekede/NaviFly, Prelincar, Hencheng, Yiling, Hopod, prelincar, coho (and a few more) where some of them use the "YIN" identifier in the firmware. So you could use a Mekede firmware which is still regularly updated (latest update firmware 23 September 2022)
jdoe6783 said:
Also if you can give more info like an MCU number instead of the vague HWinfo results ...
Click to expand...
Click to collapse
What do you mean with the MCU number? The MCU in all the 7862/8514a FYTs is identical. The MCU firmware inside that identical MCU might be slightly different dependent on the hardware, and that is determined exactly by the manufacturer id (displayed by the "vague HWInfo" , which lists much more info inside the zip, when that zip would have been shared).
Anyway, OP can flash a Mekede firmware with manufacture id 116, or a Joying with id 43 where he needs to update the AllAppUpdate.bin to put in the right manufacturer id (and/or bluetooth id). You can get that info all from the HWInfo.zip files.
The model number is completely irrelevant for a firmware flash. 9" 10" only differ in having 360 camera software or not.
Only difference make the Tesla style units as they use a different screen rotation and slightly differently built android apks.

I updated using medeke firmware to latest and eq surround sound is fixed, as is carlink.
Still no idea if carweb guru can be used for BT audio control (as I do like the look of some of the themes)
360 cannot be added internally since the IC is not sold independant the unit. maybe I'll find a donor unit someday.
Still no 100% sure on the "plug in serial device setting" but I'd imagine that is used for teyes front radar, or some other accessories. I have seen some 360 boxes that have an RX line to an android head unit so maybe that is what "serial plugin 360" is? which would let me add 360 without the IC, since the box would have it.
Appreciate the feedback.

Question Android auto looks different. Is it normal?

hello.
Just bought
EKIY T9 Car Radio For Mitsubishi Pajero V60 V68 V73 1999-2006 Tesla Vertical Screen Navigation GPS Android Stereo Receiver 2 Din​
https://www.aliexpress.com/item/1005003275616023.html?spm=a2g0o.productlist.0.0.15bb56fewlW73x&algo_pvid=3259034d-271a-49a9-b3c0-e8e335fe5a79&algo_exp_id=3259034d-271a-49a9-b3c0-e8e335fe5a79-0&pdp_ext_f=%7B%22sku_id%22%3A%2212000024973613104%22%7D&pdp_npi=2%40dis%21ILS%211010.22%21434.39%21434.39%21%21%21%21%400b0a119a16701084471075066e971a%2112000024973613104%21sea&curPageLogUid=D01agD5n8x4g
The android auto is different. I cant use maps and music at the same window. I attached a video to show you how it looks. No Split-Screen design for some reason. Maybe its related to android 10?
my questions are:
1. How can I make android auto to work regular? As I see in the pictures in the play store?
2. How can I force android auto to work on full screen mode?
3. Is there an update to android 11/12/13 for my machine? Im running android 10. Moreover, I can not find the check for updates options
any ideas? also attached the version of the machine
thanks

1) Android Auto currently does not support split-screen, only at very few top-market builtin AA screens. So certainly not on these units using a reverse-engineered CarLink apk. Android Auto is kept simple to keep it as safe as possible.
2) You can't. Android auto copies your screen to the head unit (or car builtin in screen). It will be more or less your phone screen. That works nicely on a normal 8" - 13.3" landscape unit, but not on a Tesla style vertical screen. (And why use AA??? You have such a nice screen on a fully functional Android unit)
3) There is no Android 11/12/13 for your unit. If you see Android 11/12/13 units for the FYT7862, then they are fakes.
Please first read post # of this thread. Based on your question 3) you did not much reading yet. That is what this forum is for. Learning, not only asking.
Last summer Google announced that they are working on a new AA, together with Google Assistant, for many type of screens (as more cars get Tesla style screens) and for split-screen. I have no idea when that gets released and whether the FYT CarLink.apk will support it.

surfer63 said:
1) Android Auto currently does not support split-screen, only at very few top-market builtin AA screens. So certainly not on these units using a reverse-engineered CarLink apk. Android Auto is kept simple to keep it as safe as possible.
2) You can't. Android auto copies your screen to the head unit (or car builtin in screen). It will be more or less your phone screen. That works nicely on a normal 8" - 13.3" landscape unit, but not on a Tesla style vertical screen. (And why use AA??? You have such a nice screen on a fully functional Android unit)
3) There is no Android 11/12/13 for your unit. If you see Android 11/12/13 units for the FYT7862, then they are fakes.
Please first read post # of this thread. Based on your question 3) you did not much reading yet. That is what this forum is for. Learning, not only asking.
Last summer Google announced that they are working on a new AA, together with Google Assistant, for many type of screens (as more cars get Tesla style screens) and for split-screen. I have no idea when that gets released and whether the FYT CarLink.apk will support it.
Click to expand...
Click to collapse
Thank you for commenting. I'll read the link. Sorry for that. I am new with all this.
and last question - There is no way I can see android auto as in the following picture? I mean I see here navigation+music on the same sceen. Do you know any system on Ebay that I can buy that supports it?
Thank you.

darixtorento1 said:
Thank you for commenting. I'll read the link. Sorry for that. I am new with all this.
and last question - There is no way I can see android auto as in the following picture? what is AA screens?
Thank you.
Click to expand...
Click to collapse
As far as I know: not yet.
As far as I know that is currently only available on a very selected set of built-in car units that support AA.
For my work I also regularly drive rental cars and all cars do have AA builtin (as they are never older than 1 year), but none so far with split-screen.
And please don't use webp images. The forum can't show them so I first need to download them. I don't want that.

surfer63 said:
As far as I know: not yet.
As far as I know that is currently only available on a very selected set of built-in car units that support AA.
For my work I also regularly drive rental cars and all cars do have AA builtin (as they are never older than 1 year), but none so far with split-screen.
And please don't use webp images. The forum can't show them so I first need to download them. I don't want that.
Click to expand...
Click to collapse
Ok. Thank you.
and last question-
When I hear music via Bluetooth, it works when I only enter a specific screen . Is there a way to make it work when I leave the specific screen or application?

darixtorento1 said:
Ok. Thank you.
and last question-
When I hear music via Bluetooth, it works when I only enter a specific screen . Is there a way to make it work when I leave the specific screen or application?
Click to expand...
Click to collapse
Via AA, or directly and only connected via Bluetooth?
If you simply have your phone connected and play music on your unit in the Music Player via BT, it should simply work.
For AA via CarLink I don't know. On my unit I never, ever use AA: what a waste of such an expensive unit with such great funtionality to use it as an AA unit. There are special AA /CarPlay Android units below 100 euros for sale on Amazon and AliExpress, and these do it wirelessly as well.
I only use AA in rental cars.

surfer63 said:
1) Android Auto currently does not support split-screen, only at very few top-market builtin AA screens. So certainly not on these units using a reverse-engineered CarLink apk. Android Auto is kept simple to keep it as safe as possible.
2) You can't. Android auto copies your screen to the head unit (or car builtin in screen). It will be more or less your phone screen. That works nicely on a normal 8" - 13.3" landscape unit, but not on a Tesla style vertical screen. (And why use AA??? You have such a nice screen on a fully functional Android unit)
3) There is no Android 11/12/13 for your unit. If you see Android 11/12/13 units for the FYT7862, then they are fakes.
Please first read post # of this thread. Based on your question 3) you did not much reading yet. That is what this forum is for. Learning, not only asking.
Last summer Google announced that they are working on a new AA, together with Google Assistant, for many type of screens (as more cars get Tesla style screens) and for split-screen. I have no idea when that gets released and whether the FYT CarLink.apk will support it.
Click to expand...
Click to collapse
Ive tried on another vertical screen. There is full screen

darixtorento1 said:
Ive tried on another vertical screen. There is full screen
Click to expand...
Click to collapse
Yes, you are right. I was wrong.

Still looking for a solution . thank you

Still looking for a solution . thank you

darixtorento1 said:
Still looking for a solution . thank you
Click to expand...
Click to collapse
What does the manufacturer Ekiy say? You ask us but do not mention what Ekiy answers on your questions.

surfer63 said:
What does the manufacturer Ekiy say? You ask us but do not mention what Ekiy answers on your questions.
Click to expand...
Click to collapse
He doesn't know

UP

The App on the head unit is a hacked app written by the Chinese so they do not have to pay any royalties/licencing fees. Android Auto is written only for supported Head Units using unhacked software where the maker pays the correct fee.
So every change on the Official Android Auto app does not consider what effect it has on a hacked app, so if it stops working you are reliant on the Chinese hackers fixing the hacked app. Hence no reply to your request and why I do not use Android Auto on these units.

Question Any tips on how to access pins via the MCU within an Android app?

Title says it all. I want to build an app that can read and write the pins that the MCU has access to, for example steering wheel, antenna power, etc.
Anyone know how the stock apks do that?

Is the unit an FYT, post Android system information including MCU version

cryptyk said:
Title says it all. I want to build an app that can read and write the pins that the MCU has access to, for example steering wheel, antenna power, etc.
Anyone know how the stock apks do that?
Click to expand...
Click to collapse
@marchnz is completely right: What type of unit are we talking about?
Your request is like: "I have a car. Which wires do I have to connect to a radio I bought".
If it is a FYT unit, you need to decompile the 190000000_com.syu.canbus.apk. That one contains per CANbus decoder the necessary commands.

This is a teyes cc3.
I was expecting that ST (the SOC manufacturer) or FYT used the standard Android library for connecting to the GPIO pins, or provided a library of their own. I didn't suspect that each brand would create their own unique hardware library for something as fundamental as GPIO access.
I tried the standard Android libraries and GetGpioList() doesn't return the pins.
Was hoping someone else had already gone through the effort to decompile this part and see how it works. All good if not; I can definitely do it.
@surfer63 thanks for the lead, but the canbus implementation is done with 3 dedicated bxCAN networks on the SOC which are separate from the GPIO controller.
Thanks for the notes all. I'll just start digging in and let y'all know what I find.

cryptyk said:
This is a teyes cc3.
I was expecting that ST (the SOC manufacturer) or FYT used the standard Android library for connecting to the GPIO pins, or provided a library of their own. I didn't suspect that each brand would create their own unique hardware library for something as fundamental as GPIO access.
I tried the standard Android libraries and GetGpioList() doesn't return the pins.
Was hoping someone else had already gone through the effort to decompile this part and see how it works. All good if not; I can definitely do it.
@surfer63 thanks for the lead, but the canbus implementation is done with 3 dedicated bxCAN networks on the SOC which are separate from the GPIO controller.
Thanks for the notes all. I'll just start digging in and let y'all know what I find.
Click to expand...
Click to collapse
Try this repo: https://github.com/lbdroid/MCUd/
By now very old but it might still contain some useful info.

surfer63 said:
Try this repo: https://github.com/lbdroid/MCUd/
By now very old but it might still contain some useful info.
Click to expand...
Click to collapse
Very very nice! This is a huge headstart. Thank you!