yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] yakupA:
I've read the topic.

Since then now Rooting, Xposed, not sure about systemless root but i guess those are solved, right ?

And your reverse camera issue is also solved ?

Regarding the remaining worrying points are :

1) Hotter intel CPU especially during summertime, but surfer 63 was saying that PX6 also can get quiet hot...

2) Software support on intel CPUs vs Rockschip and MTC-X devices

As an alternative found this PX6 unit :

https://www.amazon.de/gp/product/B07QPDX41M/ref=ox_sc_act_title_1?smid=A3PKET4Y6J8HFV&psc=1

But is is not Dasaita and wondering whetheer it is a MTC-x unit ?

How do we know whether a unit is MTC-x ?

For Joing i was thinking to buy this one and eventually keep it when i will be changing my E220 for a GLA around 2 years later...

The integration of Joing with W211 E220 is also worrying me :

https://www.joyingauto.com/joying-1...een-car-navigation-system-with-4g-module.html

Just FYI, there is a guy who built himself his unit ..but ok he's an artist and a lot of skills :

https://www.artifex-babel.de/en/car-pc/car-pc_en.html

Really crazily impressive...

Only things he had to put the device upside down...now considering hotter Intel CPU not sure it will last in time but still impressive work !
[FYT Android Head Units] nvstelmach:
I Want to contribute with an issue, I have found on my unit (JY-UO134N4). Hard to tell if it's isolated to just my unit, so time will tell if other try USB DAB on sc9853i:

Issue: USB DAB+ seem to only be working correctly when it's the only USB device connected to the unit.

Observed behaviour:

-When USB DAB+ adapter is the only usb device connected it has full dab signal and clear dab audio stream

-As soon as any other USB device is connected to secondary USB the signal drops to minimum strengh and audio becomes broken and unusable

Resolutions tried:

-Tried 2 seperate USB adapters + antennas, and have antenna correctly placed in window (and I currently have the type with independent 12v power to ensure maximum signal strengh)

-Tried usb cable with +power usb to supply the adapter with additional 5v/2A directly from cigaret outlet (in case of insufficient power from unit)

-Tried 12v industrial USB hub using just 1 usb connector on unit (but same result when other USB besides DAB+ is connected to hub)

-Tried 3 different firmware releases

Suspected culprits (I'm not an expert):

-USB bus issue - In case the USB connectors are using the same bus on the mainboard, it could be the DAB+ adapter is simply using all of the USB 2.0 bandwidth by itself

-Hardware issue with just my unit

-Hardware issue with this particular mainboard or SC9853i in general

-Firmware issue

-Oreo 8.1 issue

So atm I can't use the DAB+ functionality at all as I can't have it be the only USB device on the unit, since I have a USB camera which is more important to me.
[FYT Android Head Units] julien_blanche:
1- Currently only root is available, but without xposed it is some kinda pointless to me and I wont expect xposed will come to intel anytime soon cos nobody uses the intel except a bunch of people :)

2- Reverse camera delaying is not solved and i think its a hardware problem maybe its related with input transistors or resistors causing some kind of delaying with the transportation of input 12v voltage to unit

3- Bluetooth screen minimize problem still exist, [MENTION=2550900]surfer63[/MENTION] has solved this with JET apk

4- When you navigate at white backgrounds top navigation bar invisible along with the lettering, home and back buttons and you can not see anything

5- When you are using Wifi and Bluetooth together, wifi speeds drops dramatically

6- Temperature and speed of the cpu should not be considered as a buying option itself

7- You have to end up with joying regarding the software support..

maybe somebody contribute to the some of the above bugs and then we can send them together to the joying support..
[FYT Android Head Units] rigattoni:
I don´t need xposed, I just need root rights to get some tasks in Tasker running. So I even did not try to get it working.

My reverse camera is available latest after ~ 1 second, so the delay could be related to your setup.

Point 4 --> agreed... but you should know where to press to get back to your home screen. ;)

Point 5 --> I can´t agree here. I always have BT and WiFi in use. the data rate is completely OK.

Point 6 --> Temp is around 65° - 70°C in car use with navigation, DAB+, Blitzer.de (German speed control warning), Skype and ReadIt2Me, even on long term drive.

Point 7 --> agreed for the moment. I think some other supplier will come up soon with Intel Airmont chipset...

New Points:

Point 8 --> German translation of the settings menu is terrible bad and completely muddled up.

Point 9 --> Backlight current adjustment in Factory Settings (PW: 5768) is not usable... at least it is not clear what the message means if you change the brighness settings. The customercfg.txt is written in <Main Storage/customercfg>, but as far as I could see not used.... :confused:

Point 10 --> There is some strange behavior, that it is not allowed to start any application from a background task (Tasker --> start application). There is a workaround, but something in the firmware stops seeing other apps while in background... really strange. :confused:
[FYT Android Head Units] julien_blanche:
--Camera problem is related with hardware problem of the unit which i bought and some members that not reported in here

--Point 4 --> agreed... but you should know where to press to get back to your home screen. ;)

-If you would like to do button/touch combination to get back to the home screen while driving good luck with that..

--Point 5 --> I can´t agree here. I always have BT and WiFi in use. the data rate is completely OK.

-Wifi speed without bluetooth is 45mpbs, with both turned on wifi speed is 5-10 mpbs so there is something that effecting wifi performance and most of the users maybe did not conduct that test but it does not mean there is no problem so okay word is subjective term and depends on the person..

do not get me wrong, i am not trying to proof anything in here just trying to make things more clear and to be known by maker so that owner of this product has more smooth experience..

cheers..
[FYT Android Head Units] surfer63:
Both Wifi 2.4GHz and Bluetooth 3/4 use the same 2.4 GHz frequency. This CAN cause interference (but not necessarily) and therefore WiFi speed loss. But it doesn't have to.

See if you can change the WiFi channel for the hotspot from your phone or from your router to improve WiFi speeds.

If these units could use 5GHz WiFi, there wouldn't be a problem.
[FYT Android Head Units] julien_blanche:
Agree but while driving i am using phone hotspot and for the moment changing wifi channel of the ios hotspot impossible. For the home environments that may work depends on the situation.

Adding external wifi antenna gains 5-7 mpbs extra power
[FYT Android Head Units] rigattoni:
Yes, unfortunately the unit does not use 5GHz.

May be I am just a single user who does not run into this issue, but I only can talk about my observations.

Regarding the white background: I did not write that it is okay like it is.... I just mentioned that you should know where to touch. I use my Stearing wheel button to switch back to the main screen...

One thing forgotten:

Point 11 --> There is no possibility to add long click commands to any buttons. This is quite bad...

IOS is completely different I use an Android phone and not running into this issue.
[FYT Android Head Units] Theo164:
Thanks!

acc12v+ (joying harness red cable)

I didn’t use the up cover because there is no space for a top cover mounted fan to suck air, it’s blocked by a plastic mount (VW mk5 gti '07)

[IMG="hu"]https://img.xda-cdn.com/0qL0XcSVtUVi5U3qKwLqrrXMgiE=/https%3A%2F%2Fi.imgur.com%2FBi3CbYe.jpg[/IMG]
[FYT Android Head Units] victorvcunha:
2019-5-15 Rom's points (maybe it's just with me):

- Google Play Music doesn't play online musics;

- TPMS doesn't working;

- Google Maps no audio;

- Waze sometimes freezing
[FYT Android Head Units] nvstelmach:
Tasker is not allowed to start on boot - you can check "running services" in Dev. options immediately after boot to see only system apps are running regardless of what you configure in Tasker setting. So when it's not running on boot it can't start any tasks background or foreground, doesn't matter.
[FYT Android Head Units] surfer63:
Why do you think so? I assume you are referring to the "Implicit Broadcast exceptions" that have been introduced in Android 8.x. However, the BOOT_COMPLETED broadcast is still accepted as literally tens of thousands of apps use this broadcast. If you do a real reboot, I'm almost 100% sure that Tasker does work because then the BOOT_COMPLETED is broadcasted again. It's exactly the same issue I'm running into with my FytHWOnekey apk: I want to use that broadcast as well, but it only works in case of a real reboot.: not with the 20-40 "deep sleep / wakeup" cycles in between.

So the problem here is that the Joyings are not doing a reboot/cold start, like all those inferior MTCD/E units do. The Joyings go into "deep sleep". If they wake up, there is no "boot_completed" broadcast. Joying (FYT actually) works with ACC_ON and ACC_OFF broadcasts and Tasker can't listen to these. Only system apps having the same signing are allowed to "listen" to these broadcasts.

That is reason 1 why Tasker doesn't function.

So the far superior behavior of the Joyings (in this case) is for tasker (and my app), and for what you want, now a negative effect.

The second, just as important reason, is that the Joying kills all apps when going into deep-sleep. That includes tasker. So it can't do a lot of other tasks either, which it could have done when still in memory. For those "tasks" you would need a nokill version of the main server.

The only work-around in this case if you always connect something via bluetooth, like your phone or some OBD device. The bluetooth broadcasts are not protected, so tasker could use them when coming out of deep sleep. (USB is protected as well so tasker can't use these either).
[FYT Android Head Units] rigattoni:
Thanks a lot for your background information [MENTION=2550900]surfer63[/MENTION]

I think you got me wrong. I know about the broadcasts to be used by Tasker. I now use your nokill version with full success so far.

I am talking about the circumstance that apps are not "visible" for Tasker if a task is working in the background. That means that you can´t start any app if Tasker is in background. You get a "App not found" message.

If you bring Tasker to the foreground, any app is available and can be started as expected.... makes no sense for me, but anything seems to block background apps to correspond with other apps... As I said: the work-around temporarily fixes this strange behavior.

By the way, I sent a PM to you to add a reset after setup the nokill.
[FYT Android Head Units] surfer63:
Yes, I have seen that and answered it with another question.
[FYT Android Head Units] elabjer:
Hi.

I also ordered a Joying SC9863i unit, so reading thru this thread has been incredibly insightful.. thank you very much.

I used to tinker w/ Android a lot a few years back, as in: modding of stock apps by disassembling and reassembling, I wrote a few Xposed modules, etc.. been away on other projects for the past few years, but I intend to jump back in, now that I'm gonna be modding my car's new upgrade.

I'm hoping you can provide me w/ some pointers, [MENTION=2550900]surfer63[/MENTION]. Like - how would I go about mitigating these hurdles Joying put in our path? I'm referring to this "crippling" you're describing.. ie: do you consider it's possible to find a way around this blacklist Joying imposed? Eg: I ordered a Kiwi 3 OBD, and although I have yet to receive and try it, it seems from the company's official tutorial videos that it identifies itself as "KIWI BD", which, according to you, won't work (as it doesn't contain the "OBD" string in its name). May I ask how did you find this out? Did you disassemble their BT app? If this is the case - do you consider its possible to modify it?

I'm not looking for a set of instructions - just your knowledgeable insight and a general approach you would take to undertake such a task (ofc, if you deem it's even possible).

Thank you and best regards!
[FYT Android Head Units] surfer63:
I did indeed decompile the BT apk and the mainserver apk using jadx(-gui) and apktool.

In the BT-app is a String check (strName.startsWith("OBD") and 2 others) for driver name (com/syu/app/ipc/IpcObj.java) and platform (Sofia = 5, PX5 = 7, 9853i = 8), but that is more related to whether the pairing needs a pin-code or not. That could be modified.

The actual discovery is not done by the BT app, but by the mcu binary. There the discovery takes place (command

Bt.PROXY.cmd(20, 1);

) in Ipc_New and that's where "the filtering" takes place. That is, as far as I was able to trace back.

So I'm afraid it is not possible (but also see the last paragraph :) )

I think that FYT also changed the behavior somewhere in Android 6.0. Treel, one of the expert users, was able to modify the BT apk to couple "every device" in Android 5.1.1 and the early 6.0.1 versions.

Note that I'm not a real java programmer. I'm just stumbling ahead as (hardly) nobody else does it, and as I need/want functionality that is not available or blocked in the units.

I think my analysis is correct, but maybe a "real" java programmer can do better.
[FYT Android Head Units] Theo164:
I had the same issue with GMaps audio 3 times so far, first time gmaps crashed- hu freezed and i pressed reset button to reboot it

Only fix was reinstalling 2019-5-15 rom

I don't use GPM, TPMS and waze
[FYT Android Head Units] zmylna:
Hi,

After update to tha may-firmware i lost ability to switch music tracks (next/prev).

I try to set this option and nothing changed. Still can't use steering wheel buttons to switch songs :(

Before update buttons works fine.

Anyone can help with this ?
[FYT Android Head Units] julien_blanche:
try the steering wheel learn menu and remap the all buttons again..
[FYT Android Head Units] surfer63:
The 15 May version also came with new MCU firmware. After new MCU firmware you sometimes need to reconfigure your CAN bus in the settings.
[FYT Android Head Units] Caroline_Don:
Could you please provide the link of the update firmware? Maybe I can help you check. Please tell me your model number, thanks
[FYT Android Head Units] zmylna:
Firmware:

https://drive.google.com/file/d/1wXAq7buphpz6cY7slVMteALwIG6PrgpM/view

From this site: https://www.joyingauto.com/blog/pos...i-2gb-16gb-4gb-32gb-car-stereo-latest-update/

My unit: JY-VO131N4G

Thank You :)

---------- Post added at 07:38 AM ---------- Previous post was at 07:33 AM ----------

I checked twice that canbus driver is set correctly.

Before update was XP and now is XP. I was try to select something else and back to XP. Unfortunelly the problem still exist.

---------- Post added at 07:42 AM ---------- Previous post was at 07:38 AM ----------

The mapping application to the steering wheel looks like it does not work. I can not map anything.

Works only Volume keys.

Next/prev works only in original radio app and music app.

Before upgrade works with Poweramp V3 too.
[FYT Android Head Units] Caroline_Don:
Does the steering wheel control of previous/next songs not work when you are using the Zlink?

---------- Post added at 06:06 AM ---------- Previous post was at 06:03 AM ----------

Does the steering wheel control of previous/next songs not work when you are using the Zlink?

If yes, you need to update your unit with another firmware. Thanks
[FYT Android Head Units] zmylna:
No, i do not use Zlink. Just keys on steering wheel.
[FYT Android Head Units] thomasorr:
New update from Joying!

https://drive.google.com/open?id=1vAbaNvcRYD79zYK5NU4l45zGlUwbXgdO

I received this by email from them this morning so not had a chance to try it but it should fix the TPMS issue as that is the problem I have been emailing them about, not sure what other fixes are there.

Update is dated 06.12

P.S I've seen some people having issues with the notification bar having the wrong text colour in some apps so you can't see what it says, why don't you use the global immersive mode to completely disable the notification bar (you can still swipe down from the top to bring it up) I don't see any reason to have it especially with some of the nice car dashboard home screens. It just takes up precious screen real estate and most of the buttons on there have hardware buttons on the left hand side of the unit.
[FYT Android Head Units] Caroline_Don:
You can try to update your unit with this files, it's the latest firmware for joying SC9853i head unit. Please check the it:

https://drive.google.com/open?id=1vAbaNvcRYD79zYK5NU4l45zGlUwbXgdO

After update, please choose the CAN again, check the picture.

https://drive.google.com/open?id=1ZpwVsoYc1QnSbuF9QRMXkLgN3PcnOoKc

Choose the Canbus through the Canbus box.

Thanks
[FYT Android Head Units] rigattoni:
Yes I got the same update today.

Google Voice and notification issues should be fixed as written by Joying.

I just updated and rooted the device... We´ll see if some other issues have been fixed too, as:

Accessibility service on some cold boots not available

Backlight current adjustment without function.
[FYT Android Head Units] rigattoni:
Update:

Notification listener seems to be fixed. Further tests ongoing.

Unfortunately the Joying Extra Tools are not working as in the last firmware from Joying.

The sp98531 main server mods don´t show any entries to install.
[FYT Android Head Units] SummerLiu:
The android auto can work with android 9.0 phone now on the new intel 9853i system unit
[FYT Android Head Units] Busk07:
I've got a EU-JY-UOS02N4. (Can't post the link to the website because I'm a new user).

The MCU Version seems to be a little bit different than with MTCB units, mine says:

2019.01.09 09:22:15 JY_53_C63L_G32P48F64_Ver: 1.0

Is there anything we can do at the moment besides waiting for a first firmware update?
[FYT Android Head Units] surfer63:
Did anyone try to enable adb over tcpip?

And then logon to the unit using adb?

That would give a lot of info about what's possible and what's not.
[FYT Android Head Units] rackxp:
how is the bluetooth call quality on these units. I purchased the PX5 unit with the DSP and i cant use the phone phone due to the really bad echo. The sound is next level over the previous Hot Audio unit.
[FYT Android Head Units] edit:
Hello Surfer,

I am also curious because I am planning on upgrading to this one from my Sofia for the speed, DSP (so I don't have to worry about how to install viper4android), ram and maybe the 4G... maybe.

I am curious if it's possible to data tether via BT with the phone... is the BT chip on the SOM on these units?

I hope these units will get some love here on XDA... it's hard to move from an ultra custom Sofia to these stock units...
[FYT Android Head Units] prrlhkr:
Good News Everyone,

I just got an update file from Joying! Unzip the file to the root of a USB stick then plug it in to your head unit and it'll update.

https://drive.google.com/file/d/1xc9AxzgCb4iWg8max_Nh0YefIsYXNoNb/view?usp=drivesdk

To fix OBDII, go into settings / factory settings (3368) then turn on "OBD".
[FYT Android Head Units] fabien_m2002:
Hello

what is this update file? A new firmware which solves what?
[FYT Android Head Units] edit:
I think you are asking too much here, haha

Joying rarely.... if ever, released an firmware specifying exactly what were all the improvements that they made.
[FYT Android Head Units] surfer63:
Yes, the BT chip is on the SOM. For the rest I'm just as curious as you.

Just unpacking the new firmware to see what's in the system and vendor stuff, but I first have to compile brotli on linux.
[FYT Android Head Units] surfer63:
I completely unpacked the new firmware. That contained quite a number of steps (unzip firmware, unzip 6521_1.zip, brotli decompress vendor and system .dat.br files, sdat2img the uncompressed .dat files, loop mount the ext4 images).

First finding:

This is a user build (ro.build.type=user). This can be derived from the build.prop.

This means that you can't access the unit as root over adb, which makes it impossible to root this unit via adb, like the previous Sofia3GR and PX5 FYT units (and I had not expected that all based on the previous FYT units and this is a FYT unit).

(The PX5 FYT and Sofia 3GR FYT units are userdebug builds, allowing root access over adb (ro.build.type=userdebug)).

So, that option to completely root the unit is not possible.

Second finding:

There is no su binary to enable root access in the terminal via the su command (switch user). This means that you can't use the su binary itself to replace it by an extended su binary from e.g. SuperSU or so.

Third finding:

Inside the "9853i 1024X600 2019.3.5.zip" you will find the 6521_1.zip containing the brotli compressed sparse Android image files (.dat) containing the system.img and vendor.img.

This 6521_1.zip is a signed zip file, just like those 6026_8.zip files inside the PX5 firmware zips and the 5009_60.zip files in the Sofia3GR 6.0 firmwares.

This means that you can't make a custom rom by modifying the contents of the .dat files inside the 6521_2.zip (for the Intel Airmont).

Conclusion:

Maybe, just maybe, some "non persistent" rooting options like Kingo Root or Kingroot might work.

Otherwise it means that "someone" needs to make a custom TWRP recovery image especially for this new unit. Only then it will be possible to root the unit and/or install Xposed and/or install a custom ROM.

From this ROM analysis I can only detect that it has no modding options apart what's possible via non-rooted apps. Actually the same as on A-brand phones like the Pixels, Motorola, Samsung, etc.

(And of course I can be wrong. I hope so for these users wanting to mod their units)
[FYT Android Head Units] Busk07:
Thanks for looking into this. Is there any way to modify the existing system services & apps without a root?

I saw that some of the older joying units have the ability to put different configuration on the steering wheel controls like short press, long press, etc.

I’d like to have that as well and I wouldn’t mind looking into doing it myself, but I’m not very experienced with Android on a system level (i got basic experience building normal apps).

Also stuff like modding the radio app, auto volume adjustment based on speed, etc...

It’s a shame this unit is so locked down. The specs are quite good.
[FYT Android Head Units] prrlhkr:
Thanks for digging into it, so far I've had no luck with any of those "one click" root methods. It's surprising how secure this rom seems. Very different than previous Joying units.
[FYT Android Head Units] edit:
Oh man these are sad news.... so sad and discouraging news. Basically if you buy the unit there is little to no customization possible... bummer.

Given the fact that there aren't many people here left that know how to do things like TWRP recovery images... well... I say it's a slim chance that this unit will be as popular as Sofia was.

Also besides the people that buy it for the digital out because it's the cheapest headunit with digital out and android... and possibly the only one... I don't see many people interested in it... or maybe it's too new?!

I still don't know if I should buy one... I might and try and root it... since Sofia I will have a hard time NOT having at least a SofiaNoKill mod on it... not sure if anyone will build it though... Also I think I am dreaming thinking of Xposed BTmod...

---------- Post added at 06:52 AM ---------- Previous post was at 06:40 AM ----------

Wow, even more bad news... It'a quite strange how suddenly they went the most secure ever... Having an easy root was a major bonus on the Sofia... although this time I don't need it as bad because I don't feel the need to install Viper since they have a pretty good DPS (EQ), I guess the GPS speed works since it worked fine on the PX5 units... still...
[FYT Android Head Units] fabien_m2002:
Hello

i asked JY Support about new firmware logs.

Their answer: system optimizations